Rules

1,177 rule identifiers: CEN EN 16931 UBL 1.3.17 (981 assertions), the CEN 1.3.16 copy bundled with Peppol (979), Peppol BIS Billing 3.0.22 (165) and this service's own input checks.

How the results are compared with the official rules

On 2026-11-16 the official Schematron files were evaluated with an independent XPath processor on 2,611 documents (703 example and unit-test files published by CEN and OpenPeppol, 1,908 generated variants). For every document and rule set the failed rule identifiers had to be identical. Mismatching documents: 0.

Limit of this evidence: 199 of the 981 EN 16931 assertions failed at least once in that corpus; for the others the comparison shows agreement on documents that pass them.

Which CEN release runs

Plain EN 16931 invoices are checked against CEN 1.3.17. Invoices whose CustomizationID names Peppol BIS Billing 3.0 are checked the way Peppol access points check them: OpenPeppol 3.0.22 (the October 2026 hotfix) ships CEN 1.3.16, so that release runs together with the Peppol rules. The two CEN releases differ in a few code lists and rules; each rule page says which release defines the identifier. A hotfix replaces its predecessor, so earlier Peppol releases are not offered.

Input and structure checks

RuleSeverityRequirement
RS-XML-01fatalThe document is not well-formed XML.
RS-XML-02fatalDOCTYPE declarations and custom entities are not allowed.
RS-XML-03fatalThe document must be encoded in UTF-8.
RS-XML-04fatalThe document exceeds the processing limits of this validator.
RS-UBL-01fatalThe root element must be a UBL 2.1 Invoice or CreditNote.
RS-UBL-02fatalThe element is not allowed at this position by the UBL 2.1 schema.
RS-UBL-03fatalThe element is out of sequence. The UBL 2.1 schema fixes the order of child elements.
RS-UBL-04fatalA child element required by the UBL 2.1 schema is missing.
RS-UBL-05fatalThe value does not match its UBL 2.1 data type (decimal, date or boolean).
RS-UBL-06fatalThe element may occur only once at this position according to the UBL 2.1 schema.
RS-PRF-01fatalA field required by the validation profile is missing.

EN 16931 core business rules (BR)

RuleSeverityRequirement
BR-01fatalThe invoice must have a specification identifier (BT-24, cbc:CustomizationID).
BR-02fatalThe invoice must have an invoice number (BT-1, cbc:ID).
BR-03fatalThe invoice must have an issue date (BT-2, cbc:IssueDate).
BR-04fatalThe invoice must have an invoice type code (BT-3).
BR-05fatalThe invoice must have an invoice currency code (BT-5, cbc:DocumentCurrencyCode).
BR-06fatalThe seller name (BT-27) is required in PartyLegalEntity/RegistrationName.
BR-07fatalThe buyer name (BT-44) is required in PartyLegalEntity/RegistrationName.
BR-08fatalThe seller postal address (BG-5) is required.
BR-09fatalThe seller postal address must contain a country code (BT-40).
BR-10fatalThe buyer postal address (BG-8) is required.
BR-11fatalThe buyer postal address must contain a country code (BT-55).
BR-12fatalThe sum of invoice line net amounts (BT-106, LineExtensionAmount) is required.
BR-13fatalThe invoice total without VAT (BT-109, TaxExclusiveAmount) is required.
BR-14fatalThe invoice total with VAT (BT-112, TaxInclusiveAmount) is required.
BR-15fatalThe amount due for payment (BT-115, PayableAmount) is required.
BR-16fatalThe invoice must have at least one invoice line (BG-25).
BR-17fatalThe payee (BG-10) needs a name (BT-59) and must differ from the seller by name and identifier.
BR-18fatalThe seller tax representative (BG-11) must have a name (BT-62).
BR-19fatalThe seller tax representative must have a postal address (BG-12).
BR-20fatalThe tax representative postal address must contain a country code (BT-69).
BR-21fatalEach invoice line must have an identifier (BT-126).
BR-22fatalEach invoice line must have an invoiced quantity (BT-129).
BR-23fatalEach invoiced quantity must have a unit of measure code (BT-130, unitCode).
BR-24fatalEach invoice line must have a line net amount (BT-131).
BR-25fatalEach invoice line must have an item name (BT-153).
BR-26fatalEach invoice line must have an item net price (BT-146).
BR-27fatalThe item net price (BT-146) must be present and must not be negative.
BR-28fatalThe item gross price (BT-148) must not be negative.
BR-29fatalThe invoicing period end date (BT-74) must not be earlier than its start date (BT-73).
BR-30fatalThe invoice line period end date (BT-135) must not be earlier than its start date (BT-134).
BR-31fatalEach document level allowance must have an amount (BT-92).
BR-32fatalEach document level allowance must have a VAT category code (BT-95).
BR-33fatalEach document level allowance must have a reason (BT-97) or a reason code (BT-98).
BR-36fatalEach document level charge must have an amount (BT-99).
BR-37fatalEach document level charge must have a VAT category code (BT-102).
BR-38fatalEach document level charge must have a reason (BT-104) or a reason code (BT-105).
BR-41fatalEach invoice line allowance must have an amount (BT-136).
BR-42fatalEach invoice line allowance must have a reason (BT-139) or a reason code (BT-140).
BR-43fatalEach invoice line charge must have an amount (BT-141).
BR-44fatalEach invoice line charge must have a reason (BT-144) or a reason code (BT-145).
BR-45fatalEach VAT breakdown must have a taxable amount (BT-116).
BR-46fatalEach VAT breakdown must have a tax amount (BT-117).
BR-47fatalEach VAT breakdown must have a VAT category code (BT-118).
BR-48fatalEach VAT breakdown must have a VAT rate (BT-119), unless the category is O (not subject to VAT).
BR-49fatalEach payment instruction must have a payment means type code (BT-81).
BR-50fatalA credit transfer (payment means 30 or 58) must state the payment account identifier (BT-84).
BR-51warningOnly the last 4 to 6 digits of a card number (BT-87) should be given; the value is longer than 10 characters.
BR-52fatalEach additional supporting document must have a reference (BT-122).
BR-53fatalWhen a VAT accounting currency (BT-6) is given, the total VAT amount in that currency (BT-111) is required.
BR-54fatalEach item attribute must have a name (BT-160) and a value (BT-161).
BR-55fatalEach preceding invoice reference must contain the preceding invoice number (BT-25).
BR-56fatalThe seller tax representative must have a VAT identifier (BT-63).
BR-57fatalA deliver-to address must contain a country code (BT-80).
BR-61fatalPayment means 30 or 58 (credit transfer) requires the payment account identifier (BT-84).
BR-62fatalThe seller electronic address (BT-34) must have a scheme identifier (schemeID).
BR-63fatalThe buyer electronic address (BT-49) must have a scheme identifier (schemeID).
BR-64fatalThe item standard identifier (BT-157) must have a scheme identifier (schemeID).
BR-65fatalThe item classification identifier (BT-158) must have a scheme identifier (listID).

EN 16931 BR-CO rules

RuleSeverityRequirement
BR-CO-03fatalThe VAT point date (BT-7) and the VAT point date code (BT-8) must not both be present.
BR-CO-04fatalEach invoice line must have an item VAT category code (BT-151) under tax scheme VAT.
BR-CO-05fatalAllowance reason code and reason must describe the same allowance (not machine-checked).
BR-CO-06fatalCharge reason code and reason must describe the same charge (not machine-checked).
BR-CO-07fatalLine allowance reason code and reason must describe the same allowance (not machine-checked).
BR-CO-08fatalLine charge reason code and reason must describe the same charge (not machine-checked).
BR-CO-09fatalA VAT identifier (BT-31, BT-48, BT-63) must start with an ISO 3166-1 alpha-2 country prefix.
BR-CO-10fatalSum of line net amounts (BT-106) must equal the sum of all invoice line net amounts (BT-131).
BR-CO-11fatalSum of allowances (BT-107) must equal the sum of document level allowance amounts (BT-92).
BR-CO-12fatalSum of charges (BT-108) must equal the sum of document level charge amounts (BT-99).
BR-CO-13fatalTotal without VAT (BT-109) must equal BT-106 minus allowances (BT-107) plus charges (BT-108).
BR-CO-14fatalTotal VAT amount (BT-110) must equal the sum of the VAT breakdown tax amounts (BT-117).
BR-CO-15fatalTotal with VAT (BT-112) must equal total without VAT (BT-109) plus total VAT (BT-110), with exactly one VAT total in the invoice currency.
BR-CO-16fatalAmount due (BT-115) must equal total with VAT (BT-112) minus paid amount (BT-113) plus rounding (BT-114).
BR-CO-17fatalVAT breakdown tax amount (BT-117) must equal taxable amount (BT-116) times rate (BT-119) / 100, within 1 currency unit.
BR-CO-18fatalThe invoice must have at least one VAT breakdown group (BG-23).
BR-CO-19fatalAn invoicing period (BG-14) must have a start date, an end date, or both.
BR-CO-20fatalAn invoice line period (BG-26) must have a start date, an end date, or both.
BR-CO-21fatalEach document level allowance must have a reason (BT-97) or reason code (BT-98).
BR-CO-22fatalEach document level charge must have a reason (BT-104) or reason code (BT-105).
BR-CO-23fatalEach invoice line allowance must have a reason (BT-139) or reason code (BT-140).
BR-CO-24fatalEach invoice line charge must have a reason (BT-144) or reason code (BT-145).
BR-CO-26fatalThe seller must be identifiable by a seller identifier (BT-29), legal registration identifier (BT-30) or VAT identifier (BT-31).

EN 16931 BR-DEC rules

RuleSeverityRequirement
BR-DEC-01fatalDocument level allowance amount (BT-92) allows at most 2 decimals.
BR-DEC-02fatalDocument level allowance base amount (BT-93) allows at most 2 decimals.
BR-DEC-05fatalDocument level charge amount (BT-99) allows at most 2 decimals.
BR-DEC-06fatalDocument level charge base amount (BT-100) allows at most 2 decimals.
BR-DEC-09fatalSum of line net amounts (BT-106) allows at most 2 decimals.
BR-DEC-10fatalSum of allowances (BT-107) allows at most 2 decimals.
BR-DEC-11fatalSum of charges (BT-108) allows at most 2 decimals.
BR-DEC-12fatalTotal without VAT (BT-109) allows at most 2 decimals.
BR-DEC-13fatalTotal VAT amount (BT-110) allows at most 2 decimals. The published test cannot fail; UBL-DT-01 enforces the limit.
BR-DEC-14fatalTotal with VAT (BT-112) allows at most 2 decimals.
BR-DEC-15fatalTotal VAT in accounting currency (BT-111) allows at most 2 decimals. The published test cannot fail; UBL-DT-01 enforces the limit.
BR-DEC-16fatalPaid amount (BT-113) allows at most 2 decimals.
BR-DEC-17fatalRounding amount (BT-114) allows at most 2 decimals.
BR-DEC-18fatalAmount due for payment (BT-115) allows at most 2 decimals.
BR-DEC-19fatalVAT category taxable amount (BT-116) allows at most 2 decimals.
BR-DEC-20fatalVAT category tax amount (BT-117) allows at most 2 decimals.
BR-DEC-23fatalInvoice line net amount (BT-131) allows at most 2 decimals.
BR-DEC-24fatalInvoice line allowance amount (BT-136) allows at most 2 decimals.
BR-DEC-25fatalInvoice line allowance base amount (BT-137) allows at most 2 decimals.
BR-DEC-27fatalInvoice line charge amount (BT-141) allows at most 2 decimals.
BR-DEC-28fatalInvoice line charge base amount (BT-142) allows at most 2 decimals.

EN 16931 BR-CL rules

RuleSeverityRequirement
BR-CL-01fatalThe document type code must be an invoice or credit note code of UNTDID 1001.
BR-CL-03fatalEvery currencyID attribute must be an ISO 4217 alpha-3 code.
BR-CL-04fatalThe invoice currency code (BT-5) must be an ISO 4217 alpha-3 code.
BR-CL-05fatalThe VAT accounting currency code (BT-6) must be an ISO 4217 alpha-3 code.
BR-CL-06fatalThe VAT point date code (BT-8) must be 3, 35 or 432 (UNTDID 2005).
BR-CL-07fatalThe invoiced object identifier scheme must be a UNTDID 1153 code.
BR-CL-08fatalA note subject code written as #CODE# (BT-21) must be a UNTDID 4451 code.
BR-CL-10fatalA party identifier scheme must be an ISO 6523 ICD code (SEPA is allowed for seller and payee).
BR-CL-11fatalA legal registration identifier scheme must be an ISO 6523 ICD code.
BR-CL-13fatalAn item classification scheme (listID) must be a UNTDID 7143 code.
BR-CL-14fatalA country code must be an ISO 3166-1 alpha-2 code.
BR-CL-15fatalThe item country of origin (BT-159) must be an ISO 3166-1 alpha-2 code.
BR-CL-16fatalThe payment means code (BT-81) must be a UNCL 4461 code.
BR-CL-17fatalA VAT category code must be one of AE, L, M, E, S, Z, G, O, K, B (UNCL 5305).
BR-CL-18fatalAn invoiced item VAT category code (BT-151) must be one of AE, L, M, E, S, Z, G, O, K, B.
BR-CL-19fatalAn allowance reason code must be in the UNCL 5189 subset.
BR-CL-20fatalA charge reason code must be a UNCL 7161 code.
BR-CL-21fatalAn item standard identifier scheme must be an ISO 6523 ICD code.
BR-CL-22fatalA VAT exemption reason code (BT-121) must be a VATEX code.
BR-CL-23fatalA unit code must be a UN/ECE Recommendation 20 or 21 code.
BR-CL-24fatalAn attachment MIME code must be PDF, PNG, JPEG, CSV, XLSX or ODS.
BR-CL-25fatalAn electronic address scheme (BT-34-1, BT-49-1) must be an EAS code.
BR-CL-26fatalA delivery location identifier scheme must be an ISO 6523 ICD code.

EN 16931 VAT category rules

RuleSeverityRequirement
BR-S-01fatalAn invoice with a line, allowance or charge in VAT category S (standard rated) must have at least one VAT breakdown (BG-23) with that category, and none otherwise.
BR-S-02fatalInvoice lines in VAT category S (standard rated) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-S-03fatalDocument level allowances in VAT category S (standard rated) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-S-04fatalDocument level charges in VAT category S (standard rated) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-S-05fatalAn invoice line in VAT category S (standard rated) must have a VAT rate greater than zero (BT-152).
BR-S-06fatalA document level allowance in VAT category S (standard rated) must have a VAT rate greater than zero (BT-96).
BR-S-07fatalA document level charge in VAT category S (standard rated) must have a VAT rate greater than zero (BT-103).
BR-S-08fatalFor each rate in VAT category S (standard rated), the taxable amount (BT-116) must equal line net amounts plus charges minus allowances at that rate, within 1 currency unit.
BR-S-09fatalThe tax amount (BT-117) of VAT category S (standard rated) must equal the taxable amount (BT-116) times the rate (BT-119) / 100, within 1 currency unit.
BR-S-10fatalA VAT breakdown in category S (standard rated) must not have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-Z-01fatalAn invoice that uses VAT category Z (zero rated) must have exactly one VAT breakdown (BG-23) with that category.
BR-Z-02fatalInvoice lines in VAT category Z (zero rated) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-Z-03fatalDocument level allowances in VAT category Z (zero rated) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-Z-04fatalDocument level charges in VAT category Z (zero rated) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-Z-05fatalAn invoice line in VAT category Z (zero rated) must have a VAT rate of 0 (BT-152).
BR-Z-06fatalA document level allowance in VAT category Z (zero rated) must have a VAT rate of 0 (BT-96).
BR-Z-07fatalA document level charge in VAT category Z (zero rated) must have a VAT rate of 0 (BT-103).
BR-Z-08fatalThe taxable amount (BT-116) of VAT category Z (zero rated) must equal its line net amounts plus charges minus allowances.
BR-Z-09fatalThe tax amount (BT-117) of VAT category Z (zero rated) must be 0.
BR-Z-10fatalA VAT breakdown in category Z (zero rated) must not have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-E-01fatalAn invoice that uses VAT category E (exempt from VAT) must have exactly one VAT breakdown (BG-23) with that category.
BR-E-02fatalInvoice lines in VAT category E (exempt from VAT) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-E-03fatalDocument level allowances in VAT category E (exempt from VAT) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-E-04fatalDocument level charges in VAT category E (exempt from VAT) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-E-05fatalAn invoice line in VAT category E (exempt from VAT) must have a VAT rate of 0 (BT-152).
BR-E-06fatalA document level allowance in VAT category E (exempt from VAT) must have a VAT rate of 0 (BT-96).
BR-E-07fatalA document level charge in VAT category E (exempt from VAT) must have a VAT rate of 0 (BT-103).
BR-E-08fatalThe taxable amount (BT-116) of VAT category E (exempt from VAT) must equal its line net amounts plus charges minus allowances.
BR-E-09fatalThe tax amount (BT-117) of VAT category E (exempt from VAT) must be 0.
BR-E-10fatalA VAT breakdown in category E (exempt from VAT) must have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-AE-01fatalAn invoice that uses VAT category AE (reverse charge) must have exactly one VAT breakdown (BG-23) with that category.
BR-AE-02fatalInvoice lines in VAT category AE (reverse charge) require a seller VAT or tax registration identifier (BT-31, BT-32) or tax representative VAT identifier (BT-63), and a buyer VAT identifier (BT-48) or legal registration identifier (BT-47).
BR-AE-03fatalDocument level allowances in VAT category AE (reverse charge) require a seller VAT or tax registration identifier (BT-31, BT-32) or tax representative VAT identifier (BT-63), and a buyer VAT identifier (BT-48) or legal registration identifier (BT-47).
BR-AE-04fatalDocument level charges in VAT category AE (reverse charge) require a seller VAT or tax registration identifier (BT-31, BT-32) or tax representative VAT identifier (BT-63), and a buyer VAT identifier (BT-48) or legal registration identifier (BT-47).
BR-AE-05fatalAn invoice line in VAT category AE (reverse charge) must have a VAT rate of 0 (BT-152).
BR-AE-06fatalA document level allowance in VAT category AE (reverse charge) must have a VAT rate of 0 (BT-96).
BR-AE-07fatalA document level charge in VAT category AE (reverse charge) must have a VAT rate of 0 (BT-103).
BR-AE-08fatalThe taxable amount (BT-116) of VAT category AE (reverse charge) must equal its line net amounts plus charges minus allowances.
BR-AE-09fatalThe tax amount (BT-117) of VAT category AE (reverse charge) must be 0.
BR-AE-10fatalA VAT breakdown in category AE (reverse charge) must have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-IC-01fatalAn invoice that uses VAT category K (intra-community supply) must have exactly one VAT breakdown (BG-23) with that category.
BR-IC-02fatalInvoice lines in VAT category K (intra-community supply) require a seller VAT identifier (BT-31) or tax representative VAT identifier (BT-63), and a buyer VAT identifier (BT-48).
BR-IC-03fatalDocument level allowances in VAT category K (intra-community supply) require a seller VAT identifier (BT-31) or tax representative VAT identifier (BT-63), and a buyer VAT identifier (BT-48).
BR-IC-04fatalDocument level charges in VAT category K (intra-community supply) require a seller VAT identifier (BT-31) or tax representative VAT identifier (BT-63), and a buyer VAT identifier (BT-48).
BR-IC-05fatalAn invoice line in VAT category K (intra-community supply) must have a VAT rate of 0 (BT-152).
BR-IC-06fatalA document level allowance in VAT category K (intra-community supply) must have a VAT rate of 0 (BT-96).
BR-IC-07fatalA document level charge in VAT category K (intra-community supply) must have a VAT rate of 0 (BT-103).
BR-IC-08fatalThe taxable amount (BT-116) of VAT category K (intra-community supply) must equal its line net amounts plus charges minus allowances.
BR-IC-09fatalThe tax amount (BT-117) of VAT category K (intra-community supply) must be 0.
BR-IC-10fatalA VAT breakdown in category K (intra-community supply) must have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-IC-11fatalAn intra-community supply (category K) requires an actual delivery date (BT-72) or an invoicing period (BG-14).
BR-IC-12fatalAn intra-community supply (category K) requires a deliver-to country code (BT-80).
BR-G-01fatalAn invoice that uses VAT category G (export outside the EU) must have exactly one VAT breakdown (BG-23) with that category.
BR-G-02fatalInvoice lines in VAT category G (export outside the EU) require a seller VAT identifier (BT-31) or tax representative VAT identifier (BT-63).
BR-G-03fatalDocument level allowances in VAT category G (export outside the EU) require a seller VAT identifier (BT-31) or tax representative VAT identifier (BT-63).
BR-G-04fatalDocument level charges in VAT category G (export outside the EU) require a seller VAT identifier (BT-31) or tax representative VAT identifier (BT-63).
BR-G-05fatalAn invoice line in VAT category G (export outside the EU) must have a VAT rate of 0 (BT-152).
BR-G-06fatalA document level allowance in VAT category G (export outside the EU) must have a VAT rate of 0 (BT-96).
BR-G-07fatalA document level charge in VAT category G (export outside the EU) must have a VAT rate of 0 (BT-103).
BR-G-08fatalThe taxable amount (BT-116) of VAT category G (export outside the EU) must equal its line net amounts plus charges minus allowances.
BR-G-09fatalThe tax amount (BT-117) of VAT category G (export outside the EU) must be 0.
BR-G-10fatalA VAT breakdown in category G (export outside the EU) must have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-O-01fatalAn invoice that uses VAT category O (not subject to VAT) must have exactly one VAT breakdown (BG-23) with that category.
BR-O-02fatalInvoice lines in VAT category O (not subject to VAT) do not allow a seller VAT identifier (BT-31), tax representative VAT identifier (BT-63) or buyer VAT identifier (BT-48).
BR-O-03fatalDocument level allowances in VAT category O (not subject to VAT) do not allow a seller VAT identifier (BT-31), tax representative VAT identifier (BT-63) or buyer VAT identifier (BT-48).
BR-O-04fatalDocument level charges in VAT category O (not subject to VAT) do not allow a seller VAT identifier (BT-31), tax representative VAT identifier (BT-63) or buyer VAT identifier (BT-48).
BR-O-05fatalAn invoice line in VAT category O (not subject to VAT) must not have a VAT rate (BT-152).
BR-O-06fatalA document level allowance in VAT category O (not subject to VAT) must not have a VAT rate (BT-96).
BR-O-07fatalA document level charge in VAT category O (not subject to VAT) must not have a VAT rate (BT-103).
BR-O-08fatalThe taxable amount (BT-116) of VAT category O (not subject to VAT) must equal its line net amounts plus charges minus allowances.
BR-O-09fatalThe tax amount (BT-117) of VAT category O (not subject to VAT) must be 0.
BR-O-10fatalA VAT breakdown in category O (not subject to VAT) must have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-O-11fatalAn invoice with a VAT breakdown in category O must not contain any other VAT breakdown.
BR-O-12fatalAn invoice with a VAT breakdown in category O must not contain invoice lines in another VAT category.
BR-O-13fatalAn invoice with a VAT breakdown in category O must not contain document level allowances in another VAT category.
BR-O-14fatalAn invoice with a VAT breakdown in category O must not contain document level charges in another VAT category.
BR-IG-01fatalAn invoice with a line, allowance or charge in VAT category L (IGIC, Canary Islands) must have at least one VAT breakdown (BG-23) with that category, and none otherwise.
BR-AF-01fatalAn invoice with a line, allowance or charge in VAT category L (IGIC, Canary Islands) must have at least one VAT breakdown (BG-23) with that category, and none otherwise.
BR-IG-02fatalInvoice lines in VAT category L (IGIC, Canary Islands) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-AF-02fatalInvoice lines in VAT category L (IGIC, Canary Islands) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-IG-03fatalDocument level allowances in VAT category L (IGIC, Canary Islands) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-AF-03fatalDocument level allowances in VAT category L (IGIC, Canary Islands) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-IG-04fatalDocument level charges in VAT category L (IGIC, Canary Islands) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-AF-04fatalDocument level charges in VAT category L (IGIC, Canary Islands) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-IG-05fatalAn invoice line in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-152).
BR-AF-05fatalAn invoice line in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-152).
BR-IG-06fatalA document level allowance in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-96).
BR-AF-06fatalA document level allowance in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-96).
BR-IG-07fatalA document level charge in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-103).
BR-AF-07fatalA document level charge in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-103).
BR-IG-08fatalFor each rate in VAT category L (IGIC, Canary Islands), the taxable amount (BT-116) must equal line net amounts plus charges minus allowances at that rate, within 1 currency unit.
BR-AF-08fatalFor each rate in VAT category L (IGIC, Canary Islands), the taxable amount (BT-116) must equal line net amounts plus charges minus allowances at that rate, within 1 currency unit.
BR-IG-09fatalThe tax amount (BT-117) of VAT category L (IGIC, Canary Islands) must equal the taxable amount (BT-116) times the rate (BT-119) / 100, within 1 currency unit.
BR-AF-09fatalThe tax amount (BT-117) of VAT category L (IGIC, Canary Islands) must equal the taxable amount (BT-116) times the rate (BT-119) / 100, within 1 currency unit.
BR-IG-10fatalA VAT breakdown in category L (IGIC, Canary Islands) must not have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-AF-10fatalA VAT breakdown in category L (IGIC, Canary Islands) must not have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-IP-01fatalAn invoice with a line, allowance or charge in VAT category M (IPSI, Ceuta and Melilla) must have at least one VAT breakdown (BG-23) with that category, and none otherwise.
BR-AG-01fatalAn invoice with a line, allowance or charge in VAT category M (IPSI, Ceuta and Melilla) must have at least one VAT breakdown (BG-23) with that category, and none otherwise.
BR-IP-02fatalInvoice lines in VAT category M (IPSI, Ceuta and Melilla) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-AG-02fatalInvoice lines in VAT category M (IPSI, Ceuta and Melilla) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-IP-03fatalDocument level allowances in VAT category M (IPSI, Ceuta and Melilla) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-AG-03fatalDocument level allowances in VAT category M (IPSI, Ceuta and Melilla) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-IP-04fatalDocument level charges in VAT category M (IPSI, Ceuta and Melilla) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-AG-04fatalDocument level charges in VAT category M (IPSI, Ceuta and Melilla) require a seller VAT identifier (BT-31), seller tax registration identifier (BT-32) or tax representative VAT identifier (BT-63).
BR-IP-05fatalAn invoice line in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-152).
BR-AG-05fatalAn invoice line in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-152).
BR-IP-06fatalA document level allowance in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-96).
BR-AG-06fatalA document level allowance in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-96).
BR-IP-07fatalA document level charge in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-103).
BR-AG-07fatalA document level charge in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-103).
BR-IP-08fatalFor each rate in VAT category M (IPSI, Ceuta and Melilla), the taxable amount (BT-116) must equal line net amounts plus charges minus allowances at that rate, within 1 currency unit.
BR-AG-08fatalFor each rate in VAT category M (IPSI, Ceuta and Melilla), the taxable amount (BT-116) must equal line net amounts plus charges minus allowances at that rate, within 1 currency unit.
BR-IP-09fatalThe tax amount (BT-117) of VAT category M (IPSI, Ceuta and Melilla) must equal the taxable amount (BT-116) times the rate (BT-119) / 100, within 1 currency unit.
BR-AG-09fatalThe tax amount (BT-117) of VAT category M (IPSI, Ceuta and Melilla) must equal the taxable amount (BT-116) times the rate (BT-119) / 100, within 1 currency unit.
BR-IP-10fatalA VAT breakdown in category M (IPSI, Ceuta and Melilla) must not have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-AG-10fatalA VAT breakdown in category M (IPSI, Ceuta and Melilla) must not have an exemption reason (BT-120) or exemption reason code (BT-121).
BR-B-01fatalVAT category B (split payment) is allowed only on a domestic Italian invoice: every country code must be IT.
BR-B-02fatalAn invoice using VAT category B (split payment) must not also use category S (standard rated).

EN 16931 UBL syntax binding

RuleSeverityRequirement
UBL-SR-01fatalOnly one contract reference (BT-12) is allowed.
UBL-SR-02fatalOnly one receiving advice reference (BT-15) is allowed.
UBL-SR-03fatalOnly one despatch advice reference (BT-16) is allowed.
UBL-SR-05fatalOnly one payment terms (BT-20) is allowed.
UBL-SR-08fatalOnly one invoicing period (BG-14) is allowed.
UBL-SR-09fatalOnly one seller name (BT-27) is allowed.
UBL-SR-10fatalOnly one seller trading name (BT-28) is allowed.
UBL-SR-11fatalOnly one seller legal registration identifier (BT-30) is allowed.
UBL-SR-14fatalOnly one seller additional legal information (BT-33) is allowed.
UBL-SR-15fatalOnly one buyer name (BT-44) is allowed.
UBL-SR-16fatalOnly one buyer identifier (BT-46) is allowed.
UBL-SR-17fatalOnly one buyer legal registration identifier (BT-47) is allowed.
UBL-SR-24fatalOnly one delivery information (BG-13) is allowed.
UBL-SR-39fatalOnly one project reference (BT-11) is allowed.
UBL-SR-40fatalOnly one buyer trading name (BT-45) is allowed.
UBL-SR-45fatalOnly one payment due date (BT-9) is allowed.
UBL-SR-49fatalOnly one VAT point date code (BT-8) is allowed.
UBL-SR-54fatalOnly one payment card information (BG-18) is allowed.
UBL-SR-55fatalOnly one direct debit information (BG-19) is allowed.
UBL-SR-56fatalOnly one tender or lot reference (BT-17) is allowed.
UBL-SR-04fatalOnly one invoiced object identifier (BT-18, document type code 130) is allowed.
UBL-SR-06fatalEach billing reference allows only one preceding invoice reference (BT-25).
UBL-SR-07fatalA billing reference must contain the preceding invoice number (BT-25).
UBL-SR-12fatalOnly one seller VAT identifier (BT-31) is allowed.
UBL-SR-13fatalOnly one seller tax registration identifier (BT-32) is allowed.
UBL-SR-18fatalOnly one buyer VAT identifier (BT-48) is allowed.
UBL-SR-19fatalThe payee allows one name (BT-59), and it must differ from the seller name (BT-27).
UBL-SR-20fatalThe payee allows one identifier (BT-60), and the payee name must differ from the seller name (BT-27).
UBL-SR-21fatalThe payee allows one legal registration identifier (BT-61), and the payee name must differ from the seller name (BT-27).
UBL-SR-22fatalOnly one seller tax representative name (BT-62) is allowed.
UBL-SR-23fatalOnly one seller tax representative VAT identifier (BT-63) is allowed.
UBL-SR-25fatalA deliver-to party must have exactly one name (BT-70); release 1.3.16 only forbids more than one.
UBL-SR-26fatalEach payment instruction allows only one payment reference (BT-83).
UBL-SR-27fatalEach payment instruction allows only one payment means code (BT-81).
UBL-SR-28fatalOnly one mandate reference identifier (BT-89) is allowed.
UBL-SR-29fatalOnly one bank assigned creditor identifier (BT-90, scheme SEPA) is allowed.
UBL-SR-30fatalA document level allowance allows only one reason (BT-97).
UBL-SR-31fatalA document level charge allows only one reason (BT-104).
UBL-SR-32fatalA VAT breakdown allows only one exemption reason text (BT-120).
UBL-SR-33fatalA supporting document allows only one description (BT-123).
UBL-SR-34fatalAn invoice line allows only one note (BT-127).
UBL-SR-35fatalAn invoice line allows only one referenced purchase order line (BT-132).
UBL-SR-36fatalAn invoice line allows only one line period (BG-26).
UBL-SR-37fatalAn invoice line allows only one item price discount (BT-147).
UBL-SR-42fatalThe seller allows at most two tax scheme registrations (VAT identifier and tax registration identifier).
UBL-SR-43fatalA scheme identifier or document type code on a supporting document is allowed only for the invoiced object (type code 130), or type code 50 in a credit note.
UBL-SR-44fatalAll payment instructions must carry the same payment reference (BT-83).
UBL-SR-46fatalOnly one payment means text (BT-82) is allowed.
UBL-SR-47fatalAll payment instructions must use the same payment means code (BT-81).
UBL-SR-48fatalAn invoice line must have exactly one classified tax category.
UBL-SR-50fatalAn invoice line allows only one item description (BT-154).
UBL-SR-51fatalA postal address allows at most one address line element (third address line).
UBL-SR-52fatalAn invoice line allows only one object identifier (BT-128).
UBL-SR-53fatalA party tax scheme must contain a company identifier and a tax scheme identifier.
UBL-SR-57fatalSeller, buyer, payee and tax representative each allow only one legal entity element.
UBL-SR-58fatalA payment service provider (BT-86) must be given as exactly one financial institution branch identifier.
UBL-DT-01fatalAmounts allow at most 2 decimals (prices and price discounts are exempt).
UBL-DT-06fatalAn embedded document must state its MIME code (mimeCode).
UBL-DT-07fatalAn embedded document must state its file name (filename).
UBL-DT-18warningThe name attribute should be used only on the payment means code.
UBL-DT-08warningThe attribute "schemeName" is not used by EN 16931 and should be removed.
UBL-DT-09warningThe attribute "schemeAgencyName" is not used by EN 16931 and should be removed.
UBL-DT-10warningThe attribute "schemeDataURI" is not used by EN 16931 and should be removed.
UBL-DT-11warningThe attribute "schemeURI" is not used by EN 16931 and should be removed.
UBL-DT-12warningThe attribute "format" is not used by EN 16931 and should be removed.
UBL-DT-13warningThe attribute "unitCodeListIdentifier" is not used by EN 16931 and should be removed.
UBL-DT-14warningThe attribute "unitCodeListAgencyIdentifier" is not used by EN 16931 and should be removed.
UBL-DT-15warningThe attribute "unitCodeListAgencyName" is not used by EN 16931 and should be removed.
UBL-DT-16warningThe attribute "listAgencyName" is not used by EN 16931 and should be removed.
UBL-DT-17warningThe attribute "listName" is not used by EN 16931 and should be removed.
UBL-DT-19warningThe attribute "languageID" is not used by EN 16931 and should be removed.
UBL-DT-20warningThe attribute "listURI" is not used by EN 16931 and should be removed.
UBL-DT-21warningThe attribute "listSchemeURI" is not used by EN 16931 and should be removed.
UBL-DT-22warningThe attribute "languageLocaleID" is not used by EN 16931 and should be removed.
UBL-DT-23warningThe attribute "uri" is not used by EN 16931 and should be removed.
UBL-DT-24warningThe attribute "currencyCodeListVersionID" is not used by EN 16931 and should be removed.
UBL-DT-25warningThe attribute "characterSetCode" is not used by EN 16931 and should be removed.
UBL-DT-26warningThe attribute "encodingCode" is not used by EN 16931 and should be removed.
UBL-DT-27warningThe attribute "schemeAgencyID" is not used by EN 16931 and should be removed.
UBL-DT-28warningThe attribute "listAgencyID" is not used by EN 16931 and should be removed.
UBL-CR-002warningcbc:UBLVersionID should be omitted or set to 2.1.
UBL-CR-412warningcac:PaymentMeans/cbc:PaymentDueDate is not used in an invoice; use cbc:DueDate.
UBL-CR-665warningA scheme identifier on a supporting document reference should be used only for the invoiced object (type code 130).
UBL-CR-666fatalAn invoiced object reference (type code 130) must not carry an attachment.
UBL-CR-673fatalAn invoiced object reference (type code 130) must not carry a document description.

Peppol BIS Billing 3.0

RuleSeverityRequirement
PEPPOL-EN16931-R001fatalThe business process (cbc:ProfileID) is required.
PEPPOL-EN16931-R002fatalOnly one note is allowed on document level, unless seller and buyer are both German.
PEPPOL-EN16931-R003fatalA buyer reference (BT-10) or a purchase order reference (BT-13) is required.
PEPPOL-EN16931-R004fatalThe specification identifier must start with urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0.
PEPPOL-EN16931-R005fatalThe VAT accounting currency (BT-6) must differ from the invoice currency (BT-5).
PEPPOL-EN16931-R007fatalThe business process (cbc:ProfileID) must be an approved Peppol profile identifier.
PEPPOL-EN16931-R008fatalThe document must not contain empty elements.
PEPPOL-EN16931-R010fatalThe buyer electronic address (BT-49, cbc:EndpointID) is required.
PEPPOL-EN16931-R020fatalThe seller electronic address (BT-34, cbc:EndpointID) is required.
PEPPOL-EN16931-R040fatalAllowance or charge amount must equal base amount times percentage / 100 (tolerance 0.02).
PEPPOL-EN16931-R041fatalAn allowance or charge with a percentage must also state the base amount.
PEPPOL-EN16931-R042fatalAn allowance or charge with a base amount must also state the percentage.
PEPPOL-EN16931-R043fatalcbc:ChargeIndicator must be exactly 'true' or 'false'.
PEPPOL-EN16931-R044fatalA charge on price level is not allowed; ChargeIndicator must be 'false'.
PEPPOL-EN16931-R046fatalItem net price must equal gross price minus price discount when a gross price is given.
PEPPOL-EN16931-R051fatalEvery currencyID must equal the invoice currency code (BT-5), except the VAT total in accounting currency.
PEPPOL-EN16931-R053fatalExactly one tax total with tax subtotals is required.
PEPPOL-EN16931-R054fatalExactly one tax total without subtotals is required when a VAT accounting currency is given, and none otherwise.
PEPPOL-EN16931-R055fatalVAT total and VAT total in accounting currency must have the same sign.
PEPPOL-EN16931-R061fatalA mandate reference (BT-89) is required for direct debit (payment means 49 or 59).
PEPPOL-EN16931-R080fatalA credit note allows only one project reference (document type code 50).
PEPPOL-EN16931-R100fatalAn invoice line allows only one invoiced object reference.
PEPPOL-EN16931-R101fatalA line document reference may be used only for the invoiced object (type code 130).
PEPPOL-EN16931-R110fatalA line period start date must not be earlier than the invoice period start date.
PEPPOL-EN16931-R111fatalA line period end date must not be later than the invoice period end date.
PEPPOL-EN16931-R120fatalLine net amount must equal quantity x (net price / base quantity) + line charges - line allowances (tolerance 0.02).
PEPPOL-EN16931-R121fatalThe price base quantity must be greater than zero.
PEPPOL-EN16931-R130fatalThe unit code of the price base quantity must equal the unit code of the invoiced quantity.
PEPPOL-EN16931-CL001fatalAn attachment MIME code must be PDF, PNG, JPEG, CSV, XLSX or ODS.
PEPPOL-EN16931-CL002fatalAn allowance reason code must be in the UNCL 5189 subset.
PEPPOL-EN16931-CL003fatalA charge reason code must be a UNCL 7161 code.
PEPPOL-EN16931-CL006fatalThe invoice period description code must be 3, 35 or 432.
PEPPOL-EN16931-CL007fatalA currencyID must be an ISO 4217 code.
PEPPOL-EN16931-CL008fatalAn electronic address scheme must be in the Peppol Electronic Address Identifier Scheme list.
PEPPOL-EN16931-F001fatalA date must be formatted YYYY-MM-DD, without time zone.
PEPPOL-EN16931-P0100fatalThe invoice type code is not allowed for the Peppol profile.
PEPPOL-EN16931-P0101fatalThe credit note type code must be 381, 396, 81, 83 or 532.
PEPPOL-EN16931-P0104fatalExemption reason code VATEX-EU-G requires VAT category G.
PEPPOL-EN16931-P0105fatalExemption reason code VATEX-EU-O requires VAT category O.
PEPPOL-EN16931-P0106fatalExemption reason code VATEX-EU-IC requires VAT category K.
PEPPOL-EN16931-P0107fatalExemption reason code VATEX-EU-AE requires VAT category AE.
PEPPOL-EN16931-P0108fatalExemption reason code VATEX-EU-D requires VAT category E.
PEPPOL-EN16931-P0109fatalExemption reason code VATEX-EU-F requires VAT category E.
PEPPOL-EN16931-P0110fatalExemption reason code VATEX-EU-I requires VAT category E.
PEPPOL-EN16931-P0111fatalExemption reason code VATEX-EU-J requires VAT category E.
PEPPOL-EN16931-P0112fatalType codes 326 and 389 are allowed only between German parties; 384 only between German or between Slovak parties.
PEPPOL-COMMON-R040fatalA GLN (scheme 0088) must be numeric with a valid GS1 check digit.
PEPPOL-COMMON-R041fatalA Norwegian organisation number (scheme 0192) must be 9 digits with a valid check digit.
PEPPOL-COMMON-R042fatalA Danish CVR number (scheme 0184) must be 8 digits, optionally prefixed with DK.
PEPPOL-COMMON-R043fatalA Belgian enterprise number (scheme 0208) must be 10 digits with a valid mod-97 check.
PEPPOL-COMMON-R044warningAn Italian IPA code (scheme 0201) should be 6 alphanumeric characters.
PEPPOL-COMMON-R045warningAn Italian tax code (scheme 0210) should be 11 digits or a 16-character codice fiscale.
PEPPOL-COMMON-R046warningAn Italian tax code (scheme 9907) should be 11 digits or a 16-character codice fiscale.
PEPPOL-COMMON-R047warningAn Italian VAT code (scheme 0211) should be IT plus 11 digits with a valid check digit.
PEPPOL-COMMON-R049fatalA Swedish organisation number (scheme 0007) must be 10 digits with a valid Luhn check digit.
PEPPOL-COMMON-R050fatalAn Australian Business Number (scheme 0151) must be 11 digits with a valid checksum.
PEPPOL-COMMON-R052fatalA Danish P number (scheme 0096) must be 10 digits.
PEPPOL-COMMON-R053fatalA Danish SE number (scheme 0198) must be DK followed by 8 digits.
PEPPOL-COMMON-R054warningA Dutch KVK number (scheme 0106) should be 8 digits.
PEPPOL-COMMON-R055warningA Dutch OIN (scheme 0190) should be 20 digits.
PEPPOL-COMMON-R056-1warningA Dutch VAT number (scheme 9944) should have the format NL123456789B12.
PEPPOL-COMMON-R056-2warningA Dutch VAT identifier should have the format NL123456789B12.
PEPPOL-COMMON-R057warningA Dutch KVK establishment number (scheme 0217) should be 12 digits.
GR-S-008-1warningFor Greek sellers, one invoice URL (description ##INVOICE|URL##) should be provided.
GR-S-011warningGreek sellers should provide one VAT identifier starting with EL and containing a valid TIN.

Peppol national rules (NO)

RuleSeverityRequirement
NO-R-001fatalA Norwegian seller VAT number must be NO, a valid 9-digit organisation number, then MVA.
NO-R-002warningNorwegian sellers should state 'Foretaksregisteret' as tax registration (tax scheme TAX).

Peppol national rules (DK)

RuleSeverityRequirement
DK-R-002fatalDanish sellers must provide a legal entity identifier (CVR number).
DK-R-003fatalFor Danish parties, a UNSPSC item classification (listID TST) must use version 19.05.01 or 26.08.01.
DK-R-004fatalFor Danish parties, reason code ZZZ needs a 4-digit reason or a reason of the form text#text.
DK-R-005fatalFor Danish parties, the payment means code must be 1, 10, 31, 42, 48, 49, 50, 58, 59, 93 or 97.
DK-R-006fatalFor Danish parties, payment means 31 and 42 require a bank account and a registration number.
DK-R-007fatalFor Danish parties, payment means 49 requires a mandate identifier and a payer account identifier.
DK-R-008fatalFor Danish parties, payment means 50 requires a payment ID starting 01#, 04# or 15# and a 7 or 8 digit giro account.
DK-R-009fatalFor Danish parties, a payment ID starting 04# or 15# must be 19 characters long.
DK-R-010fatalFor Danish parties, payment means 93 requires a payment ID starting 71#, 73# or 75# and an 8 character creditor number.
DK-R-011fatalFor Danish parties, a payment ID starting 71# or 75# must be 18 or 19 characters long.
DK-R-013fatalFor Danish parties, a party identifier must have a schemeID.
DK-R-014fatalFor Danish sellers, the legal entity identifier must use schemeID 0184 (CVR).
DK-R-016fatalFor Danish parties, a credit note must not have a negative payable amount.
DK-R-017fatalFor Danish buyers, the legal entity identifier must use schemeID 0184 (CVR).

Peppol national rules (IT)

RuleSeverityRequirement
IT-R-001fatalFor Italian sellers, the tax registration identifier (BT-32) must be 11 to 16 characters (A-Z, 0-9).
IT-R-002fatalItalian sellers must provide address line 1 (BT-35).
IT-R-003fatalItalian sellers must provide the city (BT-37).
IT-R-004fatalItalian sellers must provide the post code (BT-38).

Peppol national rules (SE)

RuleSeverityRequirement
SE-R-001fatalA Swedish seller VAT number must be 14 characters long.
SE-R-002fatalA Swedish seller VAT number must have 12 digits after the SE prefix.
SE-R-003fatalA Swedish organisation number must be numeric.
SE-R-004fatalA Swedish organisation number must be 10 characters long.
SE-R-005fatalFor Swedish sellers, a tax registration identifier must read 'Godkänd för F-skatt'.
SE-R-006fatalFor Swedish sellers, a standard VAT rate must be 6, 12 or 25.
SE-R-007warningA Swedish Plusgiro account identifier should be numeric.
SE-R-008warningA Swedish Bankgiro account identifier should be numeric.
SE-R-009warningA Swedish Bankgiro account identifier should be 7 or 8 characters long.
SE-R-010warningA Swedish Plusgiro account identifier should be 2 to 8 characters long.
SE-R-011warningSwedish sellers should use payment means 30 with SE:BANKGIRO or SE:PLUSGIRO instead of 50 or 56.
SE-R-012warningBetween Swedish parties, a credit transfer should use payment means 30, not 31.
SE-R-013fatalA Swedish organisation number must have a valid Luhn check digit.

Peppol national rules (GR)

RuleSeverityRequirement
GR-R-001-1fatalFor Greek sellers, the invoice number must have 6 segments separated by '|'.
GR-R-001-2fatalFor Greek sellers, invoice number segment 1 must be the valid TIN of the seller or tax representative.
GR-R-001-3fatalFor Greek sellers, invoice number segment 2 must be the issue date as DD/MM/YYYY.
GR-R-001-4fatalFor Greek sellers, invoice number segment 3 must be a non-negative integer.
GR-R-001-5fatalFor Greek sellers, invoice number segment 4 must be a Greek document type (1.1, 1.6, 2.1, 2.4, 5.1, 5.2).
GR-R-001-6fatalFor Greek sellers, invoice number segment 5 must not be empty.
GR-R-001-7fatalFor Greek sellers, invoice number segment 6 must not be empty.
GR-R-002fatalGreek sellers must provide their registered name in cac:PartyName.
GR-R-003fatalA Greek seller VAT identifier must start with EL and contain a valid TIN.
GR-R-004-1fatalFor Greek sellers, exactly one MARK number (description ##M.AR.K##) is required.
GR-R-004-2fatalFor Greek sellers, the MARK number must be a positive integer.
GR-R-005fatalGreek sellers must provide the buyer name in cac:PartyName.
GR-R-006fatalFor a Greek seller and buyer, the buyer VAT identifier must start with EL and contain a valid TIN.
GR-R-008-2fatalFor Greek sellers, at most one invoice URL (description ##INVOICE|URL##) is allowed.
GR-R-008-3fatalFor Greek sellers, an invoice URL reference must contain an external reference URI.
GR-R-009fatalA Greek seller electronic address must use scheme 9933 with a valid TIN.
GR-R-010fatalFor a Greek seller and buyer, the buyer electronic address must use scheme 9933 with a valid TIN.

Peppol national rules (IS)

RuleSeverityRequirement
IS-R-001warningFor Icelandic sellers, the document type code should be 380 or 381.
IS-R-002fatalIcelandic sellers must provide a legal identifier with schemeID 0196.
IS-R-003fatalIcelandic sellers must provide street name and post code.
IS-R-004fatalFor Icelandic seller and buyer, the buyer legal identifier with schemeID 0196 is required.
IS-R-005fatalFor Icelandic seller and buyer, the buyer street name and post code are required.
IS-R-006fatalFor Icelandic sellers, payment means 9 requires a 12 digit account identifier.
IS-R-007fatalFor Icelandic sellers, payment means 42 requires a 12 digit account identifier.
IS-R-008fatalFor Icelandic sellers, an EINDAGI supporting document identifier must be a date YYYY-MM-DD.
IS-R-009fatalFor Icelandic sellers, an EINDAGI supporting document requires a due date.
IS-R-010fatalFor Icelandic sellers, the EINDAGI date must be the same as or later than the due date.

Peppol national rules (NL)

RuleSeverityRequirement
NL-R-001fatalFor Dutch sellers, a credit note must reference the original invoice.
NL-R-002fatalFor Dutch sellers, the seller address must contain street, city and post code.
NL-R-003fatalFor Dutch sellers, the legal entity identifier must be a KVK or OIN number (schemeID 0106 or 0190).
NL-R-004fatalFor Dutch seller and buyer, the buyer address must contain street, city and post code.
NL-R-005fatalFor Dutch seller and buyer, the buyer legal entity identifier must be a KVK or OIN number (schemeID 0106 or 0190).
NL-R-006fatalFor Dutch sellers with a Dutch tax representative, the representative address must contain street, city and post code.
NL-R-007fatalFor Dutch sellers, payment means are required when an amount is due.
NL-R-008fatalFor Dutch seller and buyer, the payment means code must be 30, 48, 49, 57, 58 or 59.
NL-R-009fatalFor Dutch sellers, an order line reference requires an order reference on document level.

Peppol national rules (DE)

RuleSeverityRequirement
DE-R-001fatalBetween German parties, payment instructions (BG-16) are required.
DE-R-002fatalBetween German parties, a seller contact (BG-6) is required.
DE-R-003fatalBetween German parties, the seller city (BT-37) is required.
DE-R-004fatalBetween German parties, the seller post code (BT-38) is required.
DE-R-005fatalBetween German parties, the seller contact point (BT-41) is required.
DE-R-006fatalBetween German parties, the seller contact telephone number (BT-42) is required.
DE-R-007fatalBetween German parties, the seller contact email address (BT-43) is required.
DE-R-008fatalBetween German parties, the buyer city (BT-52) is required.
DE-R-009fatalBetween German parties, the buyer post code (BT-53) is required.
DE-R-010fatalBetween German parties, the deliver-to city (BT-77) is required when a delivery address is given.
DE-R-011fatalBetween German parties, the deliver-to post code (BT-78) is required when a delivery address is given.
DE-R-014fatalBetween German parties, every VAT breakdown must state the VAT rate (BT-119).
DE-R-015fatalBetween German parties, the buyer reference (BT-10) is required.
DE-R-016fatalBetween German parties, VAT categories S, Z, E, AE, K, G, L or M require a seller tax identifier or a tax representative.
DE-R-017warningBetween German parties, the type code should be 326, 380, 384, 389, 381, 875, 876 or 877.
DE-R-018fatalBetween German parties, Skonto lines in payment terms must follow #SKONTO#TAGE=n#PROZENT=n.nn# and end with a line break.
DE-R-019warningBetween German parties, the account identifier for payment means 58 should be a valid IBAN.
DE-R-020warningBetween German parties, the debited account identifier for payment means 59 should be a valid IBAN.
DE-R-022fatalBetween German parties, attachment file names must be unique.
DE-R-023-1fatalBetween German parties, credit transfer (30, 58) requires payee account information (BG-17).
DE-R-023-2fatalBetween German parties, credit transfer (30, 58) must not carry card or direct debit information.
DE-R-024-1fatalBetween German parties, card payment (48, 54, 55) requires card information (BG-18).
DE-R-024-2fatalBetween German parties, card payment (48, 54, 55) must not carry credit transfer or direct debit information.
DE-R-025-1fatalBetween German parties, direct debit (59) requires mandate information (BG-19).
DE-R-025-2fatalBetween German parties, direct debit (59) must not carry credit transfer or card information.
DE-R-026warningBetween German parties, a corrected invoice (type 384) should reference the preceding invoice.
DE-R-027warningBetween German parties, the seller telephone number should contain at least three digits.
DE-R-028warningBetween German parties, the seller email address should have one @ with a dot in the domain part.
DE-R-030fatalBetween German parties, direct debit requires the bank assigned creditor identifier (BT-90, scheme SEPA).
DE-R-031fatalBetween German parties, direct debit requires the debited account identifier (BT-91).
DE-R-T02warningBetween German parties, an external document location should be an absolute URL.

Plus 673 generated rules for UBL elements that EN 16931 does not use: see the list.