Guide
VAT and rounding: find an invoice XML total mismatch
Resolve invoice XML total differences: reconcile lines, discounts, tax and payable amounts without hiding the underlying error with arbitrary rounding.
A one-cent difference can originate in line calculations, a discount, VAT grouping or the payable amount. Before adding a rounding adjustment, rebuild the calculation in order. The PDF may show shortened values while the exported data followed a different precision policy.
Separate calculation levels
Start with net line amounts: BR-CO-10 checks their sum. Then review document-level discounts and charges, followed by tax breakdowns. BR-CO-15 reconciles the tax-inclusive total with the tax-exclusive total and VAT amount. A problem at one level is not necessarily solved by changing another total.
A diagnostic example
In a simplified example, a net total of 100.00 and tax of 20.00 produce a tax-inclusive total of 120.00. If the export states 119.99, investigate which value changed and when. This example illustrates addition; it does not recommend a VAT rate for an actual transaction. Recalculate from exported values rather than relying only on rounded display text.
Do not conceal errors with rounding
The payable rounding amount, BT-114, has a specific purpose and its own limits. It does not repair an incorrect taxable base. Correct the source software’s precision policy, regenerate the file and repeat validation. Also test an invoice with multiple lines to expose differences between rounding each line and rounding their sum. Keep expected totals in the test case so that a future software update can be compared against the same calculation.
Check your own case reproducibly
Work on a copy first and retain the unchanged original. Record the expected result, the action actually performed and the software version used. Afterwards, compare the document number, parties, currency and amounts with the original invoice. Investigate any difference before reusing the result. A small anonymised example is more useful for diagnosing a failure than indiscriminately sharing complete customer records. Repeat the test after changing an export setting and, where relevant, confirm that the actual business partner can receive and process the resulting document.
Sources and next steps
Tools for this topic
More guides
- Electronic credit notes: references, amounts and XML checks
- EN 16931 explained: the European norm behind every e-invoice format
- How to fix an invoice XML validation failure
- E-invoicing in Belgium: getting ready for Peppol
- EDI, Peppol and XML: format or delivery channel?
- Peppol identifiers, EndpointID and buyer references
No legal advice. Dates and obligations follow the official publications cited in the text; where a date is not final, the text says so.