InvoiceGlass

The invoice type code is unusual for an XRechnung · BR-DE-17

  • Severity · Warning
  • Applies to · UBL / CII
  • Editorial review pending

The invoice type code (BT-3) says what kind of document this is. XRechnung expects only a few codes: 380 (commercial invoice), 326 (partial invoice), 384 (corrected invoice), 381 (credit note), 389 (self-billed invoice) and 875, 876 and 877 for partial, partial final and final construction invoices. This invoice uses a different code. It is still valid, but the code should be changed because some receiving systems cannot process other codes properly.

As of

Who can correct it?

The sender can correct the invoice.

How to fix it

  1. The invoice is valid; you can normally process it.
  2. When convenient, ask the sender to use one of the expected codes. For an ordinary invoice that is 380.
  3. If you issued the invoice yourself: check the document type setting in your software.

Rule text and source

Paraphrase · XRechnung checks BT-3 against document type codes 326, 380, 381, 384, 389, 875, 876 and 877.

Message to the sender

Subject: Invoice {invoiceNumber} – note on the invoice type

Hello,

Thank you for your invoice {invoiceNumber} dated {issueDate}. Our check flagged that the invoice type code is not one of the codes expected for an XRechnung (rule BR-DE-17). The invoice is valid, but for future invoices we would be grateful if you could use one of the expected codes, 380 for an ordinary invoice.

Kind regards

Example

A commercial invoice is exported with code 999, which is wrong for the document type. The software exports code 380 for this commercial invoice.

Related rules

Business terms

Rule versions

KoSIT · XRechnung Schematron 2.6.0

Validate a file