BR-CL-01 — E-Invoice Validation Rule & Fix

Fixture ID: badInvoiceType · XPath: /ubl:Invoice/cbc:InvoiceTypeCode

1. Why This Rule Triggers (Diagnostic Message)

The document type code (BT-3) must be a code from the invoice-related or the credit-note-related subset of UNTDID 1001, but "999" is in neither. The two lists decide which document you get: an invoice code emits a ubl:Invoice carrying cbc:InvoiceTypeCode (50 codes, beginning "71", "80", "81", "82", "84", "102"), a credit-note code emits a ubl:CreditNote carrying cbc:CreditNoteTypeCode (13 codes: "81", "83", "261", "262", "296", "308", "381", "396", "420", "458", "502", "503", "532"). In CII both live on one ram:TypeCode and the schematron tests the union of the two lists.

2. How to Fix BR-CL-01

Use "380" for an ordinary commercial invoice and "381" for an ordinary credit note. Other codes you are likely to want: "326" partial invoice, "384" corrected invoice, "389" self-billed invoice, "875"/"876"/"877" construction invoices, "261" self-billed credit note. Under XRechnung the list narrows sharply — BR-DE-17 admits only 326, 380, 381, 384, 389, 875, 876 and 877.

3. Valid Code / Payload Example

"invoiceTypeCode": "380"