Common Peppol BIS 3.0 validation errors and how to fix them
Peppol BIS 3.0 validation failures fall into a predictable set of categories. The error messages reference business rule codes (BR-xx) and business term numbers (BT-xx) from the EN16931 standard, which requires reading the spec to understand. This article maps the most common failures to their causes and provides concrete fixes.
All examples use UBL 2.1 syntax. For CII equivalents, see UBL vs CII.
BR-01 through BR-06: missing mandatory header fields
These rules enforce the presence of top-level mandatory fields. They fail when an element is absent or empty.
| Rule | Field | BT | Fix |
|---|---|---|---|
| BR-01 | Specification identifier | BT-24 | Add CustomizationID with the exact Peppol BIS 3.0 URI |
| BR-02 | Invoice number | BT-1 | Add non-empty ID element |
| BR-03 | Invoice issue date | BT-2 | Add IssueDate in YYYY-MM-DD format |
| BR-04 | Invoice currency code | BT-5 | Add DocumentCurrencyCode with ISO 4217 code |
| BR-05 | Seller name | BT-27 | Add AccountingSupplierParty/Party/PartyName/Name |
| BR-06 | Buyer name | BT-44 | Add AccountingCustomerParty/Party/PartyName/Name |
The value of BT-24: BR-01 only checks that CustomizationID is present. A wrong value is caught by the Peppol rule PEPPOL-EN16931-R004, which is fatal: the value must begin with the Peppol BIS 3.0 identifier and may not contain ::. A common mistake is the EN16931 base URI. Another is the suffix ::2.1, which belongs in the Peppol document type identifier, not in CustomizationID:
Wrong (EN16931 base):
<cbc:CustomizationID>urn:cen.eu:en16931:2017</cbc:CustomizationID>
Correct (Peppol BIS 3.0):
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
R004 checks that the value begins with this identifier and contains no ::. See Peppol BIS 3.0 introduction for context on why this matters.
BR-CO-10: sum of line amounts does not match total
[BR-CO-10]-Sum of Invoice line net amount (BT-106) =
sum of Invoice line net amount (BT-131).
This rule requires that LegalMonetaryTotal/LineExtensionAmount (BT-106) equals the sum of all InvoiceLine/LineExtensionAmount values (BT-131).
The failure is almost always a rounding error. Each line net amount (BT-131) may have at most two decimals (BR-DEC-23), so every line is rounded first. BR-CO-10 then compares BT-106 with the sum of those rounded line amounts. If you compute BT-106 from the raw, unrounded values and round only the total, the two can differ by a cent.
Wrong (summing raw values, rounding the total once):
// Line 1: 3 × 33.335 = 100.005, so BT-131 = 100.01
// Line 2: 3 × 33.335 = 100.005, so BT-131 = 100.01
// BT-106 from the raw sum: 200.01
// Sum of the line amounts (BT-131): 200.02, so BR-CO-10 fails
The difference grows with the number of lines whose raw amount ends in a fraction of a cent.
Correct approach: round each line net amount to two decimals, then sum the rounded amounts:
var lineNetAmounts = invoiceLines
.Select(l => Math.Round(l.Quantity * l.UnitPrice, 2, MidpointRounding.AwayFromZero)) // BT-131
.ToList();
var lineNetTotal = lineNetAmounts.Sum(); // BT-106, already two decimals
BR-CO-14: invoice VAT amount arithmetic failure
[BR-CO-14]-Invoice total VAT amount (BT-110) =
sum of VAT category tax amount (BT-117).
The total VAT amount in TaxTotal/TaxAmount must equal the sum of TaxTotal/TaxSubtotal/TaxAmount values across all tax categories.
For a single-rate invoice this seems trivial, but failures occur when:
- There are multiple VAT rates and
TaxTotal/TaxAmountis computed from the overall total instead of from the category amounts, which are each rounded to two decimals (BR-CO-17) - A category’s
TaxSubtotal/TaxAmountis missing; every category needs one, also0.00for zero-rated and exempt categories (BR-46, BR-Z-09, BR-E-09) - The
TaxAmountat theTaxTotallevel is computed independently from theTaxSubtotalamounts
Fix: compute all TaxSubtotal/TaxAmount values first, sum them, and use that sum as the TaxTotal/TaxAmount value. Do not compute TaxTotal/TaxAmount separately.
BR-CO-16: amount due for payment
[BR-CO-16]-Amount due for payment (BT-115) =
Invoice total with VAT (BT-112) - Paid amount (BT-113) + Rounding amount (BT-114).
If BT-113 (paid amount) and BT-114 (rounding amount) are not present, this simplifies to BT-115 = BT-112. The failure occurs when PayableAmount and TaxInclusiveAmount differ by more than the allowed rounding tolerance.
Common cause: computing PayableAmount from rounded line amounts and TaxInclusiveAmount from a separate total calculation that produces a slightly different result.
Fix: compute one canonical grand total, use it for both TaxInclusiveAmount and PayableAmount.
BR-S-08 and BR-S-09: VAT rate and amount consistency
[BR-S-08]-For each different value of VAT category rate (BT-119) where the
VAT category code (BT-118) is "S", the VAT category taxable amount (BT-116)
in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts
(BT-131) where the VAT category code of the Invoice line (BT-151) is "S"
and the VAT rate for the Invoice line (BT-152) equals the VAT category rate.
This rule groups all lines by VAT rate and verifies that the taxable amount in each TaxSubtotal matches the sum of lines with that rate. It fails when:
- A line has a VAT rate that does not have a corresponding
TaxSubtotal - A
TaxSubtotalexists for a rate but no lines use that rate - Rounding differences accumulate between line-level and subtotal-level calculations
Fix: build the TaxSubtotal elements dynamically from the line items, grouping by (VAT category code, VAT rate), rather than constructing them independently.
BR-E-01 / BR-AE-01: reverse charge and tax-exempt invoices
[BR-E-01]-An Invoice that contains an Invoice line (BG-25), a Document level
allowance (BG-20) or a Document level charge (BG-21) where the VAT category
code (BT-151) is "E" shall contain exactly one VAT breakdown...
Invoices with exempt (E), reverse charge (AE), or zero-rate (Z) VAT require specific TaxCategory structures that differ from standard (S) rate invoices.
Common mistakes:
- Using
IDvalueSfor all lines regardless of the actual VAT treatment - Omitting the
TaxExemptionReasonCodeorTaxExemptionReasonelements required for exempt categories - Missing
AccountingSupplierParty/Party/PartyTaxSchemewhen the invoice uses reverse charge
For reverse charge (AE), the VAT identifier of the buyer’s tax scheme must be present, and the seller’s VAT identifier must also be present.
German extension rules: XRechnung (BR-DE)
XRechnung, the German CIUS of EN16931, adds BR-DE rules on top of the EN16931 base. They come from the KoSIT validation for XRechnung, not from Peppol BIS, which has its own German rules (DE-R). Common messages:
BR-DE-TMP-32: an information message, not an error. XRechnung asks for the date of delivery or service: the actual delivery date (BT-72), an invoicing period (BG-14), or a period on every invoice line (BG-26). In UBL, BT-72 is Delivery/ActualDeliveryDate in YYYY-MM-DD format.
BR-DE-16: if the invoice uses VAT category S, Z, E, AE, K, G, L or M, at least one of the seller’s VAT identifier (BT-31), tax registration identifier (BT-32) or tax representative (BG-11) must be present. Missing all three causes rejection. A seller without a VAT identifier provides BT-32 with the tax registration number.
BR-DE-15: BT-10 is mandatory; for public buyers it carries the Leitweg-ID.
Debugging efficiently
The Schematron error output includes an XPath location:
<svrl:failed-assert location="/Invoice[1]/cac:LegalMonetaryTotal[1]">
<svrl:text>[BR-CO-10]-Sum of Invoice line net amounts...</svrl:text>
</svrl:failed-assert>
Use the XPath location to navigate directly to the failing element. For arithmetic rules, add debug output that logs the raw values before rounding so you can trace where the discrepancy originates.
The pre-compiled XSLT files from the Peppol BIS GitHub releases are the authoritative validation artifacts. Run them with Saxon HE as described in generating Peppol BIS 3.0 invoices in C#. Running against the latest release is important: rule sets are updated with each Peppol BIS release, and a rule that passes against an older XSLT may fail against the current one.
SealDoc and validation errors
SealDoc checks every invoice it generates against the pinned rule sets of its format; for Peppol BIS 3.0 these are the UBL 2.1 schema, the EN16931 rules and the Peppol BIS rules. When validation fails, the API refuses the invoice with a 422 response that lists each finding with its code, message and location.
For organizations debugging an existing invoice generation pipeline, the SealDoc public validator checks PDF/A-3 and ZUGFeRD/Factur-X/XRechnung conformance and shows the first errors it finds, with the rule in each message.