PEPPOL-EN16931-P0112 The invoice type code (BT-3) is "384", which Peppol permits only when both the seller and the buyer are German — and here the seller country (BT-40) is "DE" and the buyer country (BT-55) is "FR"
The invoice type code (BT-3) is "384", which Peppol permits only when both the seller and the buyer are German — and here the seller country (BT-40) is "DE" and the buyer country (BT-55) is "FR". Code 384 is a corrected invoice: a document that replaces an earlier one rather than adjusting it with a credit note. Both describe a German invoicing practice (Abschlagsrechnung and Rechnungskorrektur) that receiving systems elsewhere do not implement, so Peppol confines them to domestic German exchanges rather than letting them arrive somewhere that will mis-post them. 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.
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 / BT-40 / BT-55- Severity
fatal
What the library returns
The exact object in result.errors when this rule fires.
Generated by running @attestwire/en16931, not transcribed:
{
"rule": "PEPPOL-EN16931-P0112",
"field": [
"BT-3",
"BT-40",
"BT-55"
],
"severity": "fatal",
"message": "The invoice type code (BT-3) is \"384\", which Peppol permits only when both the seller and the buyer are German — and here the seller country (BT-40) is \"DE\" and the buyer country (BT-55) is \"FR\". Code 384 is a corrected invoice: a document that replaces an earlier one rather than adjusting it with a credit note. Both describe a German invoicing practice (Abschlagsrechnung and Rechnungskorrektur) that receiving systems elsewhere do not implement, so Peppol confines them to domestic German exchanges rather than letting them arrive somewhere that will mis-post them. 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\" and express the correction through a credit note, or through 380 with precedingInvoices naming the document you are replacing. If both parties really are German, set seller.address.countryCode and buyer.address.countryCode to \"DE\" — and consider whether the xrechnung-ubl profile is the better target, since it is built for exactly this case.",
"example": "\"invoiceTypeCode\": \"380\"",
"xpath": "/ubl:Invoice/cbc:InvoiceTypeCode",
"docsUrl": "https://attestwire.com/rules/PEPPOL-EN16931-P0112"
}
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
"invoiceTypeCode": "380"The fix
Use "380" and express the correction through a credit note, or through 380 with precedingInvoices naming the document you are replacing. If both parties really are German, set seller.address.countryCode and buyer.address.countryCode to "DE" — and consider whether the xrechnung-ubl profile is the better target, since it is built for exactly this case.