XRechnung 7 min readPublished

XRechnung Credit Note: Type Code 381 vs Self-Billing (389)

How to issue an XRechnung credit note: when to use type code 381, 389 or 384, the UBL CreditNote root element, an XML sample and the KoSIT rules that apply.

docutools.pro Editorial TeamEditorial Team

Key takeaways

  • The German word Gutschrift covers two things: self-billing by the customer under § 14(2) sentence 5 UStG, and a commercial credit note from the supplier.
  • XRechnung 3.0.2 separates the cases in BT-3: 389 for self-billing, 381 for a commercial credit note and 384 for a corrected invoice.
  • In UBL, code 381 belongs in a separate CreditNote document; inside an Invoice it fails rule BR-CL-01.
  • Self-billed invoices fall under the German e-invoicing mandate like any other invoice (BMF letter of 15 October 2024, para. 17).
On this page

An XRechnung credit note is identified by the invoice type code BT-3. Code 381 marks a commercial credit note from the supplier, 389 marks a self-billed invoice that the customer issues under § 14(2) sentence 5 of the German VAT Act, and 384 marks a corrected invoice. In UBL, code 381 requires a separate CreditNote document.

The pitfall for foreign suppliers and ERP teams is the German term Gutschrift, which means both "credit note" and "self-billed invoice". Pick the wrong code and the document is rejected, booked incorrectly or has a different VAT effect than intended. This guide maps each case to its code and shows the XML.

What you need to decide first

Before you set a type code, answer three questions:

  • Who issues the document? The supplier (price reduction, correction) or the customer (self-billing, Gutschriftsverfahren).
  • Is there a prior agreement? Self-billing is only valid if it "was agreed in advance" (§ 14(2) sentence 5 of the German VAT Act, Umsatzsteuergesetz or UStG).
  • What should the document do? Bill a supply for the first time, reduce the price of an earlier supply, or fix an incorrect invoice.

In German VAT law, a Gutschrift is an invoice that the recipient of the supply issues, for example a publisher that settles royalties with its authors. In everyday business German, the same word also means a commercial credit note, the "kaufmännische Gutschrift". Section 13.1 of the XRechnung 3.0.2 specification asks implementers to "clearly distinguish" the two.

Which type code fits which case?

The coordination office for IT standards (KoSIT) assigns one code from the UNTDID 1001 code list to each scenario in section 13.1 of the XRechnung 3.0.2 specification:

ScenarioBT-3Code nameIssued byReference to earlier invoice (BG-3)
Self-billing under the UStG (Gutschrift)389Self-billed invoiceCustomernot needed, it is the first bill
Commercial credit note, voucher381Credit noteSupplier"not necessary" per the specification
Correction of an invoice384Corrected invoiceOriginal issuershould be present (BR-DE-26, warning)

The specification still cites "§ 14 Abs. 2 Satz 2 UStG" for code 389. In the current statute, self-billing is in § 14(2) sentence 5 UStG, and the Federal Ministry of Finance (BMF) cites that sentence too. The meaning is the same.

Rule BR-DE-17 recommends eight codes for BT-3: 326, 380, 384, 389, 381, 875, 876 and 877. Another valid UNTDID 1001 code triggers a warning, not an error, in the KoSIT validation configuration 2026-08-31.

Step by step: build an XRechnung credit note

  1. Classify the case. Your customer bills your supply: 389. You reduce an amount you already invoiced, for example after a complaint: 381. You correct an invoice that contained an error: 384.
  2. Pick the syntax. In UBL, 389 and 384 go into an Invoice document, while 381 goes into a CreditNote document with its own namespace. In CII, every code goes into rsm:ExchangedDocument/ram:TypeCode. The comparison UBL vs CII explains the two syntaxes.
  3. Fill the party roles. The specification describes BG-4 as information "about the seller" and BG-7 as the buyer. Code 389 does not change this. In self-billing, the supplier still goes into BG-4, even though the buyer in BG-7 creates the file.
  4. Reference the original invoice. For 384, put the original invoice number in BT-25 and its date in BT-26 (group BG-3). For 381, the reference is optional but helps the receiver match the document.
  5. State amounts as positive values. The root element and the type code carry the credit meaning. Negative prices are not allowed: BR-27 and BR-28 forbid negative values in BT-146 and BT-148.
  6. Add the German wording. For 389, § 14(4) sentence 1 no. 10 UStG requires the term "Gutschrift". There is no dedicated field; a sentence in the invoice note BT-22 serves human readers as well.
  7. Validate, then send. Check the file against the current validation configuration and transmit it on the same channel as your invoices, for example Peppol or the federal portals.

What a UBL CreditNote with code 381 looks like

This abridged sample with fictitious data shows the header of a commercial credit note in UBL. Note the root element CreditNote, the element cbc:CreditNoteTypeCode instead of cbc:InvoiceTypeCode, and the lines as cac:CreditNoteLine with cbc:CreditedQuantity:

<ubl:CreditNote xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2"
  xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
  xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
  <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
  <cbc:ID>CN-2026-0007</cbc:ID>
  <cbc:IssueDate>2026-11-17</cbc:IssueDate>
  <cbc:CreditNoteTypeCode>381</cbc:CreditNoteTypeCode>
  <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
  <cbc:BuyerReference>04011000-1234512345-06</cbc:BuyerReference>
  <cac:BillingReference>
    <cac:InvoiceDocumentReference>
      <cbc:ID>RE-2026-0042</cbc:ID>
      <cbc:IssueDate>2026-10-15</cbc:IssueDate>
    </cac:InvoiceDocumentReference>
  </cac:BillingReference>
  <!-- parties, payment, tax and totals as in an invoice -->
  <cac:CreditNoteLine>
    <cbc:ID>1</cbc:ID>
    <cbc:CreditedQuantity unitCode="HUR">2</cbc:CreditedQuantity>
    <cbc:LineExtensionAmount currencyID="EUR">300.00</cbc:LineExtensionAmount>
    <!-- item, tax category, price -->
  </cac:CreditNoteLine>
</ubl:CreditNote>

cac:BillingReference is the UBL binding of group BG-3 with BT-25 and BT-26. Rule BR-55 requires BT-25 whenever that group is present. For namespaces and the remaining mandatory groups, see XRechnung XML structure. A self-billed invoice with 389 keeps the root element Invoice with cbc:InvoiceTypeCode.

Common mistakes with e-invoice credit notes

MistakeSymptomFix
381 inside a UBL InvoiceError BR-CL-01: the code is not in the invoice code listGenerate a CreditNote with CreditNoteTypeCode, or switch to CII
Commercial credit note sent as 389No validation error, but for VAT purposes it is the customer billing youUse 381; reserve 389 for agreed self-billing
Correction sent as 381 with no referenceNo validation error; the receiver cannot match itUse 384 with BG-3 for corrections
384 without BG-3Warning BR-DE-26Add BT-25 (and BT-26 if possible)
Negative unit price in a 380 invoiceError BR-27Issue a credit note document instead
Code 261 (self-billed credit note)Warning BR-DE-17Ask the receiver whether it processes codes outside the recommended list

The BR-CL-01 code lists come from the CEN Schematron 1.3.16 in the KoSIT configuration 2026-08-31. For a UBL Invoice the list contains 326, 380, 384 and 389, among others, but not 381. The CreditNote list contains 381 and 261. In CII, BR-CL-01 checks one combined list that includes all of these codes. Our reference of XRechnung validation errors explains further rules; the KoSIT rule text always takes precedence.

What German VAT law says about credit notes

The technical choice follows the tax rules. Four points matter:

  • The mandate covers self-billing. Para. 17 of the BMF letter of 15 October 2024 states that the e-invoicing rules apply "in the same way" to invoices issued as a Gutschrift under § 14(2) sentence 5 UStG.
  • Corrections in the same form. Under para. 49, an e-invoice must be corrected as an e-invoice "using the corresponding invoice type". Sending missing details in another form is not enough.
  • Price reductions do not always need an invoice. If the taxable amount changes under § 17 UStG, for example through a year-end bonus, the original e-invoice does not have to be corrected. A document under § 17(4) UStG "can, but need not" be issued as an invoice, and therefore as an e-invoice (para. 51). According to a summary by IHK Hannover, the BMF letter of 15 October 2026 also accepts a general reference to a written bonus, rebate or cash-discount agreement.
  • Transition rule for 2027. Businesses with prior-year turnover of no more than EUR 800,000 may still issue other invoice formats in 2027. For self-billing, the turnover of the issuer of the Gutschrift, which is the customer, counts (para. 64). The special cases are in our guide to the EUR 800,000 threshold.

Validation tells you whether a file is technically valid. Whether it has the right VAT effect depends on the type code and the underlying agreement. The difference between the error classes is explained in e-invoice format error vs content error.

How to check a credit note with docutools.pro

Our tools do not cover every credit note case. These steps work today:

  1. Inspect the type code and root element. Open the file in the XML viewer. It runs in your browser, and the file does not leave your computer. The tree shows whether the root is Invoice, CreditNote or CrossIndustryInvoice and which code sits in BT-3. It does not check rules.
  2. Validate a CII credit note. Upload a CII file with 381 or 389 to the XRechnung validator. The file is sent to our server and checked the way the KoSIT validator does with configuration 2026-08-31. The "Extracted data" table does not show the type code. The free plan allows 2 uploads per day up to 500 KB; the Pro plan has no daily limit.
  3. Check UBL CreditNote files elsewhere. The viewer does not read UBL CreditNote documents. For those files, run the KoSIT validator itself.
  4. Look up the messages. If BR-CL-01, BR-DE-17 or BR-DE-26 appears, the KoSIT error hub has background on the rules.

Our generator only creates invoice type 380. Create credit notes and corrected invoices in your invoicing software.

Checks after sending

  • Did the supplier accept the self-billed invoice without objection? Under § 14(2) sentence 6 UStG, an objection removes its effect as an invoice.
  • Is the credit note number in BT-1 unique, so that receivers do not confuse it with an invoice number?
  • Are the original invoice and the credit note archived together? See e-invoice archiving in Germany for the retention rules.

The fields that a credit note must carry, like any XRechnung, are listed in XRechnung mandatory fields. More field guides and special cases are in our XRechnung guides.

Sources

Last reviewed: November 2026

This article is general information, not tax or legal advice.

Tags:XRechnungCredit NoteE-InvoicingUBL

Tools for this article

Frequently asked questions

Is a credit note an invoice under German e-invoicing rules?

It depends on the type. A self-billed invoice, which the customer issues under § 14(2) sentence 5 UStG, is an invoice and must follow the e-invoicing rules. A commercial credit note that reduces a price is a document under § 17 UStG. The BMF letter of 15 October 2024, para. 51, says such a document can, but need not, be issued as an invoice and therefore as an e-invoice.

Can an XRechnung credit note have negative amounts?

No negative prices are allowed. Business rules BR-27 and BR-28 forbid a negative item net price (BT-146) and item gross price (BT-148). A credit note states positive amounts, and the document type, a UBL CreditNote or type code 381 in CII, tells the receiver that the amounts are credited. Use a credit note document instead of an invoice with minus prices.

Does a German self-billed invoice need the word Gutschrift?

Yes. § 14(4) sentence 1 no. 10 UStG requires the term Gutschrift when the customer issues the invoice. XRechnung 3.0.2 has no dedicated field for it; type code 389 marks the case for machines. Neither the law nor the specification says whether the code alone is enough, so adding the word Gutschrift in the invoice note (BT-22) is a simple precaution.

Which type code does a ZUGFeRD or Factur-X credit note use?

ZUGFeRD and Factur-X use the CII syntax, where every document type sits in the same element, ram:TypeCode under rsm:ExchangedDocument. A commercial credit note uses 381 and a self-billed invoice uses 389. CII has no separate root element for credit notes. Which ZUGFeRD profiles accept these codes is stated in the specification of each profile.

Topic hubMore on XRechnungStructure, mandatory fields, Leitweg-ID and submission of XRechnung, Germany's standard for structured e-invoices.