What it means
The rule checks that schemeID exists on ram:URIID inside the final delivery party's ram:URIUniversalCommunication. It checks presence only, so even an empty attribute passes this particular test.
Why it matters
The scheme identifies how the electronic address should be interpreted.
How to fix it
Add schemeID to the affected ram:URIID under the line's ram:SpecifiedLineTradeDelivery/ram:UltimateShipToTradeParty/ram:URIUniversalCommunication. Use the scheme that matches the address, for example EM for email. If your software generates this XML, ask its supplier to correct the export. Export again and recheck.
Once the file is corrected, check it again for free: Validate a ZUGFeRD invoice
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice Beta
The rule as published
Attribute '@schemeID' is required in this context. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-001124 still fails, and which other rules do.
Related rules
- FX-SCH-A-001125 Electronic address scheme of a line's delivery party must be valid
- FX-SCH-A-001126 Reference type of a document referred to on a line must be valid
- FX-SCH-A-001127 Document type code of a line's referenced document must be valid
- FX-SCH-A-001128 Tax category code on a line must be allowed
- FX-SCH-A-001129 Tax point date code on a line must be allowed
- FX-SCH-A-001130 Exemption reason code on a line must be allowed