Credit Note (UBL) Guide — When and How to Issue Credit Notes

What Is a Credit Note?

A credit note is a financial document issued by a seller to a buyer that reduces or cancels the amount owed from a previously issued invoice. It is not a separate e-invoicing format in the way that Peppol BIS 3.0 or ZUGFeRD are formats — rather, it is a document type within the UBL 2.1 standard that mirrors the structure of an invoice but serves the opposite purpose.

When you issue an invoice and later need to reverse it — because goods were returned, a billing error was discovered, a discount needs to be applied, or a price adjustment was agreed — you issue a credit note. The credit note references the original invoice and specifies the amount to be credited back to the buyer. In accounting terms, it reduces the seller's accounts receivable and the buyer's accounts payable.

In the EU's e-invoicing ecosystem, credit notes are subject to the same EN 16931 compliance requirements as invoices. This means a credit note must contain the same mandatory fields — seller, buyer, line items, tax breakdown — and must be exchanged through the same channels (Peppol network, government portals, PDPs). If your country mandates e-invoicing, it also mandates electronic credit notes.

When to Issue a Credit Note

Credit notes are issued in these common business scenarios:

• Goods returned: The buyer returns products (partially or fully), and the seller needs to reverse the corresponding invoice amount.
• Billing errors: The original invoice contained incorrect quantities, prices, or tax calculations. A credit note corrects the error by crediting the wrong amount, and a new corrected invoice may be issued.
• Price adjustments: A post-sale discount, volume rebate, or contractual price adjustment requires reducing the invoiced amount.
• Early payment discounts: Some businesses issue credit notes for cash discounts (Skonto) when payment is received before the due date.
• Service cancellations: A subscription or service contract is cancelled mid-period, and the unused portion needs to be refunded.
• Full invoice reversal: The entire transaction is cancelled, and a credit note for the full amount is issued against the original invoice.

In all cases, the credit note must reference the original invoice — typically by including the original invoice number and issue date. This creates a clear audit trail that tax authorities can follow.

Technical Structure

A UBL 2.1 Credit Note is structurally very similar to a UBL invoice. The key differences are:

• Root element: <CreditNote> instead of <Invoice>. The XML namespace is urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2.
• Document type code: 381 (credit note) instead of 380 (commercial invoice).
• Invoice reference: The <BillingReference> element contains the number and date of the original invoice being credited.
• Line items: Uses <CreditNoteLine> instead of <InvoiceLine>. The amounts represent credits (money flowing back to the buyer).
• Monetary totals: All amounts are positive, but they represent a reduction in what the buyer owes rather than an increase.

Everything else — seller party, buyer party, tax calculations, payment information — follows the same structure and validation rules as a standard UBL invoice. If you can generate a UBL invoice, generating a credit note requires minimal changes.

Within Peppol BIS 3.0, credit notes are covered by the same specification as invoices. The Peppol business rules apply equally — the same validation checks run on both document types. The Peppol network processes credit notes through the same Access Points and delivery infrastructure as invoices.

Credit Notes Across Different Formats

• Peppol BIS 3.0: Full credit note support using the UBL <CreditNote> document type. Same business rules as invoices. Transmitted through the Peppol network identically to invoices.
• XRechnung: Supports credit notes in both UBL and CII syntax. The same German-specific business rules (including Leitweg-ID for B2G) apply to credit notes as to invoices.
• ZUGFeRD / Factur-X: Credit notes are supported through the CII XML structure, using the document type code 381. The hybrid PDF/XML approach works the same way — the PDF shows the credit note visually, and the embedded XML contains the structured data.

Regardless of which format you use, the fundamental concept is the same: a credit note is a structured document that references and reverses (fully or partially) a previously issued invoice.

Country-Specific Considerations

Most EU countries treat credit notes the same as invoices for e-invoicing mandate purposes. Some specifics to be aware of:

• Belgium: Credit notes must be sent via Peppol in the same BIS 3.0 format as invoices from January 2026.
• Germany: Credit notes (Gutschriften/Stornorechnung) fall under the same E-Rechnung mandate. XRechnung-compliant credit notes must include the same Leitweg-ID for B2G submissions.
• France: Credit notes (avoirs) must be exchanged through the same PDP infrastructure as invoices when the mandate takes effect.
• Italy: Credit notes (note di credito) must be submitted through SDI using FatturaPA format with document type TD04.

How InvoicePeppol Helps

InvoicePeppol generates fully compliant UBL 2.1 Credit Notes that pass EN 16931 and Peppol BIS 3.0 validation. You can convert an existing credit note PDF or create a credit note from scratch using our invoice builder — simply specify the original invoice reference, and we handle the correct document structure, type codes, and validation rules.

Frequently Asked Questions