Attestwire

Rule reference

BR-DE-17 XRechnung restricts the invoice type code (BT-3) to 326, 380, 381, 384, 389, 875, 876 and 877 from UNTDID 1001, but "999" was supplied

XRechnung restricts the invoice type code (BT-3) to 326, 380, 381, 384, 389, 875, 876 and 877 from UNTDID 1001, but "999" was supplied. The wider UNTDID list is legal under core EN 16931 and will be rejected by a German receiving portal.

This rule is implemented and its error payload below is real, but the long-form write-up — normative text, worked example, divergence note — is not written yet. Everything the library knows about this rule is on this page. Ask and we will prioritise it.

Business term
BT-3
Severity
fatal

What the library returns

The exact object in result.errors when this rule fires. Generated by running @attestwire/en16931, not transcribed:

TeachingError
{
  "rule": "BR-DE-17",
  "field": "BT-3",
  "severity": "fatal",
  "message": "XRechnung restricts the invoice type code (BT-3) to 326, 380, 381, 384, 389, 875, 876 and 877 from UNTDID 1001, but \"999\" was supplied. The wider UNTDID list is legal under core EN 16931 and will be rejected by a German receiving portal.",
  "fix": "Use \"380\" for a commercial invoice, \"381\" for a credit note, \"384\" for a corrected invoice (and then also supply the preceding invoice reference, BR-DE-26), \"326\" for a partial invoice, \"389\" for self-billing.",
  "example": "\"invoiceTypeCode\": \"380\"",
  "xpath": "/ubl:Invoice/cbc:InvoiceTypeCode",
  "docsUrl": "https://attestwire.com/rules/BR-DE-17"
}

xpath locates the element in the generated UBL document, which is where a KoSIT or Peppol validator will report the same problem.

A passing value

the shape this field expects
"invoiceTypeCode": "380"

The fix

Use "380" for a commercial invoice, "381" for a credit note, "384" for a corrected invoice (and then also supply the preceding invoice reference, BR-DE-26), "326" for a partial invoice, "389" for self-billing.

All 58 rules →

Nearby: BR-DE-27 — The seller contact telephone number (BT-42) should contain at least three digits, but "call us" contains 0; BR-DE-16 — XRechnung requires that, when the tax codes S, Z, E, AE, K, G, L or M are used, at least one of the seller VAT identifier (BT-31), the seller tax registration identifier (BT-32) or a seller tax representative party (BG-11) is present; BR-DE-28 — The seller contact email address (BT-43) must contain exactly one "@", flanked by at least two characters on each side and by neither a space nor a dot, and must not begin or end with a dot.

Check this rule against your invoice via the hosted API → https://api.attestwire.com/docs

Arrived from a stack trace? The docsUrl on every error links straight here. Something wrong on this page — tell us.