What it means
The seller can be identified by a global identifier (BT-29), such as a GLN or a DUNS number. It comes with a scheme (BT-29-1), a four-digit code from the ISO 6523 list that says what kind of number it is, for example 0088 for a GLN or 0060 for a DUNS number. The rule checks ram:GlobalID in the seller party and fails when a scheme is filled in that is not on the list.
Why it matters
Codes are read by software, not by people. A scheme outside the agreed list cannot be interpreted, so the recipient cannot tell what kind of identifier it has been given and the invoice fails the check.
How to fix it
Open the seller identifiers in your invoicing software and choose the scheme from the list instead of typing it. If the number is only an internal supplier number, it does not need a scheme and should not be sent as a global identifier. If you build the XML yourself, the code is the schemeID attribute of ram:GlobalID under ram:SellerTradeParty.
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
Value of '@schemeID' is not allowed. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000579 still fails, and which other rules do.
Related rules
- FX-SCH-A-000580 Use a listed seller country code
- FX-SCH-A-000581 Use a listed seller registration scheme
- FX-SCH-A-000582 Use a listed seller electronic address scheme
- FX-SCH-A-000583 Use format 102 for the delivery date
- FX-SCH-A-000584 Include one receiving advice identifier
- FX-SCH-A-000585 Use a listed delivery location scheme