What it means
In the EN 16931 and Extended profiles of Factur-X and ZUGFeRD, ram:SpecifiedTradeSettlementHeaderMonetarySummation may contain zero or one ram:RoundingAmount. This rule counts those elements; it does not check their values or calculate the amount due.
Why it matters
The profile provides one field for the rounding adjustment to the amount due. Repeating it exceeds that field's limit, even when the repeated values are identical.
How to fix it
Check the rounding amount in your invoice totals. If you edit the XML, keep at most one ram:RoundingAmount inside ram:SpecifiedTradeSettlementHeaderMonetarySummation. Do not simply add repeated values together, as they may be duplicates. Check separately that the amount due (BT-115) equals the invoice total including VAT (BT-112), minus the amount already paid (BT-113), plus the rounding amount (BT-114). Export and recheck the file.
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:RoundingAmount' may occur at maximum 1 times. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000290 still fails, and which other rules do.
Related rules
- FX-SCH-A-000291 A payment instruction can have only one text
- FX-SCH-A-000292 A bank entry must contain exactly one BIC
- FX-SCH-A-000293 Only one object reference is allowed in a line's settlement details
- FX-SCH-A-000294 An item attribute needs exactly one name
- FX-SCH-A-000295 An item attribute needs exactly one value
- FX-SCH-A-000296 A classification code must say which scheme it uses