Guide
Electronic credit notes: references, amounts and XML checks
Prepare an electronic credit note: choose the document type, preserve its link to the original invoice and check amounts, taxes and reconciliation.
A credit note corrects a commercial situation; it is not simply an invoice with a minus sign in front of every number. Document type, connection to the original invoice and format conventions must agree. Start by identifying what is being corrected: quantity, price, discount or the entire transaction.
Choose the right document
UBL distinguishes documents including Invoice and CreditNote. Use the software’s credit-note export instead of renaming invoice XML. The expected profile then determines fields and rules. Confirm with the recipient how a credit note is matched to an invoice and how partial adjustments are processed.
Preserve references
Retain the credit-note number, preceding invoice reference and information identifying corrected lines. A clear description helps the accounting team but does not replace a structured reference when required. Do not reuse the original document number as though the new file were merely an updated attachment.
Test signs and totals
Check quantities, taxable bases and amounts against the chosen profile’s rules. Automatically reversing every value can produce an unintended double sign reversal. Test a full credit and a partial adjustment; compare the result with the expected customer-account balance. Technical validation does not decide the correction’s tax or accounting treatment. Record who approves the commercial correction before exporting it so that a technically valid document cannot accidentally cancel the wrong transaction.
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
- VAT and rounding: find an invoice XML total mismatch
- 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.