AttestwireRule referencePEPPOL-EN16931-P0100

PEPPOL-EN16931-P0100 The invoice type code must be one Peppol billing allows

noun · Peppol BIS · fatal · BT-3

For a sample invoice, the library reports: The invoice type code (BT-3) is "325", which billing process 01 does not admit. Peppol's rules are scoped by business process — the ProfileID this library emits is urn:fdc:peppol.eu:2017:poacc:billing:01:1.0, "billing", and each process declares which UNTDID 1001 codes make sense inside it.

Business term
BT-3
Severity
fatal

The fix

Use "380" for a commercial invoice, "384" for a corrected invoice, "386" for a prepayment invoice, "875"/"876"/"877" for the construction-industry partial invoices. A credit note is a separate document in UBL and is governed by PEPPOL-EN16931-P0101, not this rule.

A passing value

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

What the library returns

The full error returned by @attestwire/en16931. It includes the rule ID, affected field and suggested correction. Developers can use this object in their application:

TeachingError
{
  "rule": "PEPPOL-EN16931-P0100",
  "field": "BT-3",
  "severity": "fatal",
  "message": "The invoice type code (BT-3) is \"325\", which billing process 01 does not admit. Peppol's rules are scoped by business process — the ProfileID this library emits is urn:fdc:peppol.eu:2017:poacc:billing:01:1.0, \"billing\", and each process declares which UNTDID 1001 codes make sense inside it. The permitted set here is 71, 80, 82, 84, 102, 218, 219, 326, 331, 380, 382, 383, 384, 386, 388, 393, 395, 553, 575, 623, 780, 817, 870, 875, 876 and 877. Note that this is a *different* narrowing from BR-CL-01, which admits a wider list, and from XRechnung's BR-DE-17, which admits a narrower one — three lists, three ids, and passing one says nothing about the others. This is a Peppol BIS Billing 3.0 profile rule: it applies because profile is \"peppol-bis-3\". It does not apply to the en16931, xrechnung-ubl or xrechnung-cii profiles, whose validators will accept the same document.",
  "fix": "Use \"380\" for a commercial invoice, \"384\" for a corrected invoice, \"386\" for a prepayment invoice, \"875\"/\"876\"/\"877\" for the construction-industry partial invoices. A credit note is a separate document in UBL and is governed by PEPPOL-EN16931-P0101, not this rule.",
  "example": "\"invoiceTypeCode\": \"380\"",
  "xpath": "/ubl:Invoice/cbc:InvoiceTypeCode",
  "docsUrl": "https://attestwire.com/rules/PEPPOL-EN16931-P0100"
}

xpath is always a UBL path. On a CII invoice, look for the matching CII field instead.