What it means
In the EN 16931 profiles of Factur-X and ZUGFeRD, this rule counts ram:DefinedTradeContact elements directly under ram:SellerTradeParty in ram:ApplicableHeaderTradeAgreement. It allows no contact element or one contact element. It does not require a contact or check which contact details have been supplied.
Why it matters
These profiles represent the seller contact (BG-6) as one optional contact block. Multiple blocks do not follow that structure, even if they describe the same contact.
How to fix it
Choose the seller contact to include on this invoice. In the XML, keep only that contact's ram:DefinedTradeContact under the header ram:SellerTradeParty, with their details together where supplied. Do not combine unrelated contacts' details or delete other contacts from your company's records. If your software exports several contacts, ask its supplier to correct the export. Export and recheck your invoice.
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
Element 'ram:DefinedTradeContact' may occur at maximum 1 times. 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-000576 still fails, and which other rules do.
Related rules
- FX-SCH-A-000577 The seller contact email needs one address element
- FX-SCH-A-000578 The seller's contact phone must hold exactly one number
- FX-SCH-A-000579 The seller identifier scheme must be an ISO 6523 code
- 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