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
| Rule | Severity | Requirement |
|---|---|---|
| RS-XML-01 | fatal | The document is not well-formed XML. |
| RS-XML-02 | fatal | DOCTYPE declarations and custom entities are not allowed. |
| RS-XML-03 | fatal | The document must be encoded in UTF-8. |
| RS-XML-04 | fatal | The document exceeds the processing limits of this validator. |
| RS-UBL-01 | fatal | The root element must be a UBL 2.1 Invoice or CreditNote. |
| RS-UBL-02 | fatal | The element is not allowed at this position by the UBL 2.1 schema. |
| RS-UBL-03 | fatal | The element is out of sequence. The UBL 2.1 schema fixes the order of child elements. |
| RS-UBL-04 | fatal | A child element required by the UBL 2.1 schema is missing. |
| RS-UBL-05 | fatal | The value does not match its UBL 2.1 data type (decimal, date or boolean). |
| RS-UBL-06 | fatal | The element may occur only once at this position according to the UBL 2.1 schema. |
| RS-PRF-01 | fatal | A field required by the validation profile is missing. |
EN 16931 core business rules (BR)
| Rule | Severity | Requirement |
|---|---|---|
| BR-01 | fatal | The invoice must have a specification identifier (BT-24, cbc:CustomizationID). |
| BR-02 | fatal | The invoice must have an invoice number (BT-1, cbc:ID). |
| BR-03 | fatal | The invoice must have an issue date (BT-2, cbc:IssueDate). |
| BR-04 | fatal | The invoice must have an invoice type code (BT-3). |
| BR-05 | fatal | The invoice must have an invoice currency code (BT-5, cbc:DocumentCurrencyCode). |
| BR-06 | fatal | The seller name (BT-27) is required in PartyLegalEntity/RegistrationName. |
| BR-07 | fatal | The buyer name (BT-44) is required in PartyLegalEntity/RegistrationName. |
| BR-08 | fatal | The seller postal address (BG-5) is required. |
| BR-09 | fatal | The seller postal address must contain a country code (BT-40). |
| BR-10 | fatal | The buyer postal address (BG-8) is required. |
| BR-11 | fatal | The buyer postal address must contain a country code (BT-55). |
| BR-12 | fatal | The sum of invoice line net amounts (BT-106, LineExtensionAmount) is required. |
| BR-13 | fatal | The invoice total without VAT (BT-109, TaxExclusiveAmount) is required. |
| BR-14 | fatal | The invoice total with VAT (BT-112, TaxInclusiveAmount) is required. |
| BR-15 | fatal | The amount due for payment (BT-115, PayableAmount) is required. |
| BR-16 | fatal | The invoice must have at least one invoice line (BG-25). |
| BR-17 | fatal | The payee (BG-10) needs a name (BT-59) and must differ from the seller by name and identifier. |
| BR-18 | fatal | The seller tax representative (BG-11) must have a name (BT-62). |
| BR-19 | fatal | The seller tax representative must have a postal address (BG-12). |
| BR-20 | fatal | The tax representative postal address must contain a country code (BT-69). |
| BR-21 | fatal | Each invoice line must have an identifier (BT-126). |
| BR-22 | fatal | Each invoice line must have an invoiced quantity (BT-129). |
| BR-23 | fatal | Each invoiced quantity must have a unit of measure code (BT-130, unitCode). |
| BR-24 | fatal | Each invoice line must have a line net amount (BT-131). |
| BR-25 | fatal | Each invoice line must have an item name (BT-153). |
| BR-26 | fatal | Each invoice line must have an item net price (BT-146). |
| BR-27 | fatal | The item net price (BT-146) must be present and must not be negative. |
| BR-28 | fatal | The item gross price (BT-148) must not be negative. |
| BR-29 | fatal | The invoicing period end date (BT-74) must not be earlier than its start date (BT-73). |
| BR-30 | fatal | The invoice line period end date (BT-135) must not be earlier than its start date (BT-134). |
| BR-31 | fatal | Each document level allowance must have an amount (BT-92). |
| BR-32 | fatal | Each document level allowance must have a VAT category code (BT-95). |
| BR-33 | fatal | Each document level allowance must have a reason (BT-97) or a reason code (BT-98). |
| BR-36 | fatal | Each document level charge must have an amount (BT-99). |
| BR-37 | fatal | Each document level charge must have a VAT category code (BT-102). |
| BR-38 | fatal | Each document level charge must have a reason (BT-104) or a reason code (BT-105). |
| BR-41 | fatal | Each invoice line allowance must have an amount (BT-136). |
| BR-42 | fatal | Each invoice line allowance must have a reason (BT-139) or a reason code (BT-140). |
| BR-43 | fatal | Each invoice line charge must have an amount (BT-141). |
| BR-44 | fatal | Each invoice line charge must have a reason (BT-144) or a reason code (BT-145). |
| BR-45 | fatal | Each VAT breakdown must have a taxable amount (BT-116). |
| BR-46 | fatal | Each VAT breakdown must have a tax amount (BT-117). |
| BR-47 | fatal | Each VAT breakdown must have a VAT category code (BT-118). |
| BR-48 | fatal | Each VAT breakdown must have a VAT rate (BT-119), unless the category is O (not subject to VAT). |
| BR-49 | fatal | Each payment instruction must have a payment means type code (BT-81). |
| BR-50 | fatal | A credit transfer (payment means 30 or 58) must state the payment account identifier (BT-84). |
| BR-51 | warning | Only the last 4 to 6 digits of a card number (BT-87) should be given; the value is longer than 10 characters. |
| BR-52 | fatal | Each additional supporting document must have a reference (BT-122). |
| BR-53 | fatal | When a VAT accounting currency (BT-6) is given, the total VAT amount in that currency (BT-111) is required. |
| BR-54 | fatal | Each item attribute must have a name (BT-160) and a value (BT-161). |
| BR-55 | fatal | Each preceding invoice reference must contain the preceding invoice number (BT-25). |
| BR-56 | fatal | The seller tax representative must have a VAT identifier (BT-63). |
| BR-57 | fatal | A deliver-to address must contain a country code (BT-80). |
| BR-61 | fatal | Payment means 30 or 58 (credit transfer) requires the payment account identifier (BT-84). |
| BR-62 | fatal | The seller electronic address (BT-34) must have a scheme identifier (schemeID). |
| BR-63 | fatal | The buyer electronic address (BT-49) must have a scheme identifier (schemeID). |
| BR-64 | fatal | The item standard identifier (BT-157) must have a scheme identifier (schemeID). |
| BR-65 | fatal | The item classification identifier (BT-158) must have a scheme identifier (listID). |
EN 16931 BR-CO rules
| Rule | Severity | Requirement |
|---|---|---|
| BR-CO-03 | fatal | The VAT point date (BT-7) and the VAT point date code (BT-8) must not both be present. |
| BR-CO-04 | fatal | Each invoice line must have an item VAT category code (BT-151) under tax scheme VAT. |
| BR-CO-05 | fatal | Allowance reason code and reason must describe the same allowance (not machine-checked). |
| BR-CO-06 | fatal | Charge reason code and reason must describe the same charge (not machine-checked). |
| BR-CO-07 | fatal | Line allowance reason code and reason must describe the same allowance (not machine-checked). |
| BR-CO-08 | fatal | Line charge reason code and reason must describe the same charge (not machine-checked). |
| BR-CO-09 | fatal | A VAT identifier (BT-31, BT-48, BT-63) must start with an ISO 3166-1 alpha-2 country prefix. |
| BR-CO-10 | fatal | Sum of line net amounts (BT-106) must equal the sum of all invoice line net amounts (BT-131). |
| BR-CO-11 | fatal | Sum of allowances (BT-107) must equal the sum of document level allowance amounts (BT-92). |
| BR-CO-12 | fatal | Sum of charges (BT-108) must equal the sum of document level charge amounts (BT-99). |
| BR-CO-13 | fatal | Total without VAT (BT-109) must equal BT-106 minus allowances (BT-107) plus charges (BT-108). |
| BR-CO-14 | fatal | Total VAT amount (BT-110) must equal the sum of the VAT breakdown tax amounts (BT-117). |
| BR-CO-15 | fatal | Total 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-16 | fatal | Amount due (BT-115) must equal total with VAT (BT-112) minus paid amount (BT-113) plus rounding (BT-114). |
| BR-CO-17 | fatal | VAT breakdown tax amount (BT-117) must equal taxable amount (BT-116) times rate (BT-119) / 100, within 1 currency unit. |
| BR-CO-18 | fatal | The invoice must have at least one VAT breakdown group (BG-23). |
| BR-CO-19 | fatal | An invoicing period (BG-14) must have a start date, an end date, or both. |
| BR-CO-20 | fatal | An invoice line period (BG-26) must have a start date, an end date, or both. |
| BR-CO-21 | fatal | Each document level allowance must have a reason (BT-97) or reason code (BT-98). |
| BR-CO-22 | fatal | Each document level charge must have a reason (BT-104) or reason code (BT-105). |
| BR-CO-23 | fatal | Each invoice line allowance must have a reason (BT-139) or reason code (BT-140). |
| BR-CO-24 | fatal | Each invoice line charge must have a reason (BT-144) or reason code (BT-145). |
| BR-CO-26 | fatal | The 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
| Rule | Severity | Requirement |
|---|---|---|
| BR-DEC-01 | fatal | Document level allowance amount (BT-92) allows at most 2 decimals. |
| BR-DEC-02 | fatal | Document level allowance base amount (BT-93) allows at most 2 decimals. |
| BR-DEC-05 | fatal | Document level charge amount (BT-99) allows at most 2 decimals. |
| BR-DEC-06 | fatal | Document level charge base amount (BT-100) allows at most 2 decimals. |
| BR-DEC-09 | fatal | Sum of line net amounts (BT-106) allows at most 2 decimals. |
| BR-DEC-10 | fatal | Sum of allowances (BT-107) allows at most 2 decimals. |
| BR-DEC-11 | fatal | Sum of charges (BT-108) allows at most 2 decimals. |
| BR-DEC-12 | fatal | Total without VAT (BT-109) allows at most 2 decimals. |
| BR-DEC-13 | fatal | Total VAT amount (BT-110) allows at most 2 decimals. The published test cannot fail; UBL-DT-01 enforces the limit. |
| BR-DEC-14 | fatal | Total with VAT (BT-112) allows at most 2 decimals. |
| BR-DEC-15 | fatal | Total VAT in accounting currency (BT-111) allows at most 2 decimals. The published test cannot fail; UBL-DT-01 enforces the limit. |
| BR-DEC-16 | fatal | Paid amount (BT-113) allows at most 2 decimals. |
| BR-DEC-17 | fatal | Rounding amount (BT-114) allows at most 2 decimals. |
| BR-DEC-18 | fatal | Amount due for payment (BT-115) allows at most 2 decimals. |
| BR-DEC-19 | fatal | VAT category taxable amount (BT-116) allows at most 2 decimals. |
| BR-DEC-20 | fatal | VAT category tax amount (BT-117) allows at most 2 decimals. |
| BR-DEC-23 | fatal | Invoice line net amount (BT-131) allows at most 2 decimals. |
| BR-DEC-24 | fatal | Invoice line allowance amount (BT-136) allows at most 2 decimals. |
| BR-DEC-25 | fatal | Invoice line allowance base amount (BT-137) allows at most 2 decimals. |
| BR-DEC-27 | fatal | Invoice line charge amount (BT-141) allows at most 2 decimals. |
| BR-DEC-28 | fatal | Invoice line charge base amount (BT-142) allows at most 2 decimals. |
EN 16931 BR-CL rules
| Rule | Severity | Requirement |
|---|---|---|
| BR-CL-01 | fatal | The document type code must be an invoice or credit note code of UNTDID 1001. |
| BR-CL-03 | fatal | Every currencyID attribute must be an ISO 4217 alpha-3 code. |
| BR-CL-04 | fatal | The invoice currency code (BT-5) must be an ISO 4217 alpha-3 code. |
| BR-CL-05 | fatal | The VAT accounting currency code (BT-6) must be an ISO 4217 alpha-3 code. |
| BR-CL-06 | fatal | The VAT point date code (BT-8) must be 3, 35 or 432 (UNTDID 2005). |
| BR-CL-07 | fatal | The invoiced object identifier scheme must be a UNTDID 1153 code. |
| BR-CL-08 | fatal | A note subject code written as #CODE# (BT-21) must be a UNTDID 4451 code. |
| BR-CL-10 | fatal | A party identifier scheme must be an ISO 6523 ICD code (SEPA is allowed for seller and payee). |
| BR-CL-11 | fatal | A legal registration identifier scheme must be an ISO 6523 ICD code. |
| BR-CL-13 | fatal | An item classification scheme (listID) must be a UNTDID 7143 code. |
| BR-CL-14 | fatal | A country code must be an ISO 3166-1 alpha-2 code. |
| BR-CL-15 | fatal | The item country of origin (BT-159) must be an ISO 3166-1 alpha-2 code. |
| BR-CL-16 | fatal | The payment means code (BT-81) must be a UNCL 4461 code. |
| BR-CL-17 | fatal | A VAT category code must be one of AE, L, M, E, S, Z, G, O, K, B (UNCL 5305). |
| BR-CL-18 | fatal | An invoiced item VAT category code (BT-151) must be one of AE, L, M, E, S, Z, G, O, K, B. |
| BR-CL-19 | fatal | An allowance reason code must be in the UNCL 5189 subset. |
| BR-CL-20 | fatal | A charge reason code must be a UNCL 7161 code. |
| BR-CL-21 | fatal | An item standard identifier scheme must be an ISO 6523 ICD code. |
| BR-CL-22 | fatal | A VAT exemption reason code (BT-121) must be a VATEX code. |
| BR-CL-23 | fatal | A unit code must be a UN/ECE Recommendation 20 or 21 code. |
| BR-CL-24 | fatal | An attachment MIME code must be PDF, PNG, JPEG, CSV, XLSX or ODS. |
| BR-CL-25 | fatal | An electronic address scheme (BT-34-1, BT-49-1) must be an EAS code. |
| BR-CL-26 | fatal | A delivery location identifier scheme must be an ISO 6523 ICD code. |
EN 16931 VAT category rules
| Rule | Severity | Requirement |
|---|---|---|
| BR-S-01 | fatal | An 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-02 | fatal | Invoice 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-03 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category S (standard rated) must have a VAT rate greater than zero (BT-152). |
| BR-S-06 | fatal | A document level allowance in VAT category S (standard rated) must have a VAT rate greater than zero (BT-96). |
| BR-S-07 | fatal | A document level charge in VAT category S (standard rated) must have a VAT rate greater than zero (BT-103). |
| BR-S-08 | fatal | For 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-09 | fatal | The 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-10 | fatal | A VAT breakdown in category S (standard rated) must not have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-Z-01 | fatal | An invoice that uses VAT category Z (zero rated) must have exactly one VAT breakdown (BG-23) with that category. |
| BR-Z-02 | fatal | Invoice 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-03 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category Z (zero rated) must have a VAT rate of 0 (BT-152). |
| BR-Z-06 | fatal | A document level allowance in VAT category Z (zero rated) must have a VAT rate of 0 (BT-96). |
| BR-Z-07 | fatal | A document level charge in VAT category Z (zero rated) must have a VAT rate of 0 (BT-103). |
| BR-Z-08 | fatal | The taxable amount (BT-116) of VAT category Z (zero rated) must equal its line net amounts plus charges minus allowances. |
| BR-Z-09 | fatal | The tax amount (BT-117) of VAT category Z (zero rated) must be 0. |
| BR-Z-10 | fatal | A VAT breakdown in category Z (zero rated) must not have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-E-01 | fatal | An invoice that uses VAT category E (exempt from VAT) must have exactly one VAT breakdown (BG-23) with that category. |
| BR-E-02 | fatal | Invoice 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-03 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category E (exempt from VAT) must have a VAT rate of 0 (BT-152). |
| BR-E-06 | fatal | A document level allowance in VAT category E (exempt from VAT) must have a VAT rate of 0 (BT-96). |
| BR-E-07 | fatal | A document level charge in VAT category E (exempt from VAT) must have a VAT rate of 0 (BT-103). |
| BR-E-08 | fatal | The taxable amount (BT-116) of VAT category E (exempt from VAT) must equal its line net amounts plus charges minus allowances. |
| BR-E-09 | fatal | The tax amount (BT-117) of VAT category E (exempt from VAT) must be 0. |
| BR-E-10 | fatal | A VAT breakdown in category E (exempt from VAT) must have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-AE-01 | fatal | An invoice that uses VAT category AE (reverse charge) must have exactly one VAT breakdown (BG-23) with that category. |
| BR-AE-02 | fatal | Invoice 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-03 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category AE (reverse charge) must have a VAT rate of 0 (BT-152). |
| BR-AE-06 | fatal | A document level allowance in VAT category AE (reverse charge) must have a VAT rate of 0 (BT-96). |
| BR-AE-07 | fatal | A document level charge in VAT category AE (reverse charge) must have a VAT rate of 0 (BT-103). |
| BR-AE-08 | fatal | The taxable amount (BT-116) of VAT category AE (reverse charge) must equal its line net amounts plus charges minus allowances. |
| BR-AE-09 | fatal | The tax amount (BT-117) of VAT category AE (reverse charge) must be 0. |
| BR-AE-10 | fatal | A VAT breakdown in category AE (reverse charge) must have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-IC-01 | fatal | An invoice that uses VAT category K (intra-community supply) must have exactly one VAT breakdown (BG-23) with that category. |
| BR-IC-02 | fatal | Invoice 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-03 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category K (intra-community supply) must have a VAT rate of 0 (BT-152). |
| BR-IC-06 | fatal | A document level allowance in VAT category K (intra-community supply) must have a VAT rate of 0 (BT-96). |
| BR-IC-07 | fatal | A document level charge in VAT category K (intra-community supply) must have a VAT rate of 0 (BT-103). |
| BR-IC-08 | fatal | The taxable amount (BT-116) of VAT category K (intra-community supply) must equal its line net amounts plus charges minus allowances. |
| BR-IC-09 | fatal | The tax amount (BT-117) of VAT category K (intra-community supply) must be 0. |
| BR-IC-10 | fatal | A VAT breakdown in category K (intra-community supply) must have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-IC-11 | fatal | An intra-community supply (category K) requires an actual delivery date (BT-72) or an invoicing period (BG-14). |
| BR-IC-12 | fatal | An intra-community supply (category K) requires a deliver-to country code (BT-80). |
| BR-G-01 | fatal | An invoice that uses VAT category G (export outside the EU) must have exactly one VAT breakdown (BG-23) with that category. |
| BR-G-02 | fatal | Invoice 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-03 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category G (export outside the EU) must have a VAT rate of 0 (BT-152). |
| BR-G-06 | fatal | A document level allowance in VAT category G (export outside the EU) must have a VAT rate of 0 (BT-96). |
| BR-G-07 | fatal | A document level charge in VAT category G (export outside the EU) must have a VAT rate of 0 (BT-103). |
| BR-G-08 | fatal | The taxable amount (BT-116) of VAT category G (export outside the EU) must equal its line net amounts plus charges minus allowances. |
| BR-G-09 | fatal | The tax amount (BT-117) of VAT category G (export outside the EU) must be 0. |
| BR-G-10 | fatal | A VAT breakdown in category G (export outside the EU) must have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-O-01 | fatal | An invoice that uses VAT category O (not subject to VAT) must have exactly one VAT breakdown (BG-23) with that category. |
| BR-O-02 | fatal | Invoice 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-03 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category O (not subject to VAT) must not have a VAT rate (BT-152). |
| BR-O-06 | fatal | A document level allowance in VAT category O (not subject to VAT) must not have a VAT rate (BT-96). |
| BR-O-07 | fatal | A document level charge in VAT category O (not subject to VAT) must not have a VAT rate (BT-103). |
| BR-O-08 | fatal | The taxable amount (BT-116) of VAT category O (not subject to VAT) must equal its line net amounts plus charges minus allowances. |
| BR-O-09 | fatal | The tax amount (BT-117) of VAT category O (not subject to VAT) must be 0. |
| BR-O-10 | fatal | A VAT breakdown in category O (not subject to VAT) must have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-O-11 | fatal | An invoice with a VAT breakdown in category O must not contain any other VAT breakdown. |
| BR-O-12 | fatal | An invoice with a VAT breakdown in category O must not contain invoice lines in another VAT category. |
| BR-O-13 | fatal | An invoice with a VAT breakdown in category O must not contain document level allowances in another VAT category. |
| BR-O-14 | fatal | An invoice with a VAT breakdown in category O must not contain document level charges in another VAT category. |
| BR-IG-01 | fatal | An 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-01 | fatal | An 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-02 | fatal | Invoice 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-02 | fatal | Invoice 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-03 | fatal | Document 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-03 | fatal | Document 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-04 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-152). |
| BR-AF-05 | fatal | An invoice line in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-152). |
| BR-IG-06 | fatal | A document level allowance in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-96). |
| BR-AF-06 | fatal | A document level allowance in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-96). |
| BR-IG-07 | fatal | A document level charge in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-103). |
| BR-AF-07 | fatal | A document level charge in VAT category L (IGIC, Canary Islands) must have a tax rate of zero or greater (BT-103). |
| BR-IG-08 | fatal | For 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-08 | fatal | For 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-09 | fatal | The 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-09 | fatal | The 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-10 | fatal | A VAT breakdown in category L (IGIC, Canary Islands) must not have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-AF-10 | fatal | A VAT breakdown in category L (IGIC, Canary Islands) must not have an exemption reason (BT-120) or exemption reason code (BT-121). |
| BR-IP-01 | fatal | An 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-01 | fatal | An 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-02 | fatal | Invoice 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-02 | fatal | Invoice 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-03 | fatal | Document 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-03 | fatal | Document 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-04 | fatal | Document 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-04 | fatal | Document 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-05 | fatal | An invoice line in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-152). |
| BR-AG-05 | fatal | An invoice line in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-152). |
| BR-IP-06 | fatal | A document level allowance in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-96). |
| BR-AG-06 | fatal | A document level allowance in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-96). |
| BR-IP-07 | fatal | A document level charge in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-103). |
| BR-AG-07 | fatal | A document level charge in VAT category M (IPSI, Ceuta and Melilla) must have a tax rate of zero or greater (BT-103). |
| BR-IP-08 | fatal | For 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-08 | fatal | For 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-09 | fatal | The 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-09 | fatal | The 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-10 | fatal | A 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-10 | fatal | A 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-01 | fatal | VAT category B (split payment) is allowed only on a domestic Italian invoice: every country code must be IT. |
| BR-B-02 | fatal | An invoice using VAT category B (split payment) must not also use category S (standard rated). |
EN 16931 UBL syntax binding
| Rule | Severity | Requirement |
|---|---|---|
| UBL-SR-01 | fatal | Only one contract reference (BT-12) is allowed. |
| UBL-SR-02 | fatal | Only one receiving advice reference (BT-15) is allowed. |
| UBL-SR-03 | fatal | Only one despatch advice reference (BT-16) is allowed. |
| UBL-SR-05 | fatal | Only one payment terms (BT-20) is allowed. |
| UBL-SR-08 | fatal | Only one invoicing period (BG-14) is allowed. |
| UBL-SR-09 | fatal | Only one seller name (BT-27) is allowed. |
| UBL-SR-10 | fatal | Only one seller trading name (BT-28) is allowed. |
| UBL-SR-11 | fatal | Only one seller legal registration identifier (BT-30) is allowed. |
| UBL-SR-14 | fatal | Only one seller additional legal information (BT-33) is allowed. |
| UBL-SR-15 | fatal | Only one buyer name (BT-44) is allowed. |
| UBL-SR-16 | fatal | Only one buyer identifier (BT-46) is allowed. |
| UBL-SR-17 | fatal | Only one buyer legal registration identifier (BT-47) is allowed. |
| UBL-SR-24 | fatal | Only one delivery information (BG-13) is allowed. |
| UBL-SR-39 | fatal | Only one project reference (BT-11) is allowed. |
| UBL-SR-40 | fatal | Only one buyer trading name (BT-45) is allowed. |
| UBL-SR-45 | fatal | Only one payment due date (BT-9) is allowed. |
| UBL-SR-49 | fatal | Only one VAT point date code (BT-8) is allowed. |
| UBL-SR-54 | fatal | Only one payment card information (BG-18) is allowed. |
| UBL-SR-55 | fatal | Only one direct debit information (BG-19) is allowed. |
| UBL-SR-56 | fatal | Only one tender or lot reference (BT-17) is allowed. |
| UBL-SR-04 | fatal | Only one invoiced object identifier (BT-18, document type code 130) is allowed. |
| UBL-SR-06 | fatal | Each billing reference allows only one preceding invoice reference (BT-25). |
| UBL-SR-07 | fatal | A billing reference must contain the preceding invoice number (BT-25). |
| UBL-SR-12 | fatal | Only one seller VAT identifier (BT-31) is allowed. |
| UBL-SR-13 | fatal | Only one seller tax registration identifier (BT-32) is allowed. |
| UBL-SR-18 | fatal | Only one buyer VAT identifier (BT-48) is allowed. |
| UBL-SR-19 | fatal | The payee allows one name (BT-59), and it must differ from the seller name (BT-27). |
| UBL-SR-20 | fatal | The payee allows one identifier (BT-60), and the payee name must differ from the seller name (BT-27). |
| UBL-SR-21 | fatal | The payee allows one legal registration identifier (BT-61), and the payee name must differ from the seller name (BT-27). |
| UBL-SR-22 | fatal | Only one seller tax representative name (BT-62) is allowed. |
| UBL-SR-23 | fatal | Only one seller tax representative VAT identifier (BT-63) is allowed. |
| UBL-SR-25 | fatal | A deliver-to party must have exactly one name (BT-70); release 1.3.16 only forbids more than one. |
| UBL-SR-26 | fatal | Each payment instruction allows only one payment reference (BT-83). |
| UBL-SR-27 | fatal | Each payment instruction allows only one payment means code (BT-81). |
| UBL-SR-28 | fatal | Only one mandate reference identifier (BT-89) is allowed. |
| UBL-SR-29 | fatal | Only one bank assigned creditor identifier (BT-90, scheme SEPA) is allowed. |
| UBL-SR-30 | fatal | A document level allowance allows only one reason (BT-97). |
| UBL-SR-31 | fatal | A document level charge allows only one reason (BT-104). |
| UBL-SR-32 | fatal | A VAT breakdown allows only one exemption reason text (BT-120). |
| UBL-SR-33 | fatal | A supporting document allows only one description (BT-123). |
| UBL-SR-34 | fatal | An invoice line allows only one note (BT-127). |
| UBL-SR-35 | fatal | An invoice line allows only one referenced purchase order line (BT-132). |
| UBL-SR-36 | fatal | An invoice line allows only one line period (BG-26). |
| UBL-SR-37 | fatal | An invoice line allows only one item price discount (BT-147). |
| UBL-SR-42 | fatal | The seller allows at most two tax scheme registrations (VAT identifier and tax registration identifier). |
| UBL-SR-43 | fatal | A 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-44 | fatal | All payment instructions must carry the same payment reference (BT-83). |
| UBL-SR-46 | fatal | Only one payment means text (BT-82) is allowed. |
| UBL-SR-47 | fatal | All payment instructions must use the same payment means code (BT-81). |
| UBL-SR-48 | fatal | An invoice line must have exactly one classified tax category. |
| UBL-SR-50 | fatal | An invoice line allows only one item description (BT-154). |
| UBL-SR-51 | fatal | A postal address allows at most one address line element (third address line). |
| UBL-SR-52 | fatal | An invoice line allows only one object identifier (BT-128). |
| UBL-SR-53 | fatal | A party tax scheme must contain a company identifier and a tax scheme identifier. |
| UBL-SR-57 | fatal | Seller, buyer, payee and tax representative each allow only one legal entity element. |
| UBL-SR-58 | fatal | A payment service provider (BT-86) must be given as exactly one financial institution branch identifier. |
| UBL-DT-01 | fatal | Amounts allow at most 2 decimals (prices and price discounts are exempt). |
| UBL-DT-06 | fatal | An embedded document must state its MIME code (mimeCode). |
| UBL-DT-07 | fatal | An embedded document must state its file name (filename). |
| UBL-DT-18 | warning | The name attribute should be used only on the payment means code. |
| UBL-DT-08 | warning | The attribute "schemeName" is not used by EN 16931 and should be removed. |
| UBL-DT-09 | warning | The attribute "schemeAgencyName" is not used by EN 16931 and should be removed. |
| UBL-DT-10 | warning | The attribute "schemeDataURI" is not used by EN 16931 and should be removed. |
| UBL-DT-11 | warning | The attribute "schemeURI" is not used by EN 16931 and should be removed. |
| UBL-DT-12 | warning | The attribute "format" is not used by EN 16931 and should be removed. |
| UBL-DT-13 | warning | The attribute "unitCodeListIdentifier" is not used by EN 16931 and should be removed. |
| UBL-DT-14 | warning | The attribute "unitCodeListAgencyIdentifier" is not used by EN 16931 and should be removed. |
| UBL-DT-15 | warning | The attribute "unitCodeListAgencyName" is not used by EN 16931 and should be removed. |
| UBL-DT-16 | warning | The attribute "listAgencyName" is not used by EN 16931 and should be removed. |
| UBL-DT-17 | warning | The attribute "listName" is not used by EN 16931 and should be removed. |
| UBL-DT-19 | warning | The attribute "languageID" is not used by EN 16931 and should be removed. |
| UBL-DT-20 | warning | The attribute "listURI" is not used by EN 16931 and should be removed. |
| UBL-DT-21 | warning | The attribute "listSchemeURI" is not used by EN 16931 and should be removed. |
| UBL-DT-22 | warning | The attribute "languageLocaleID" is not used by EN 16931 and should be removed. |
| UBL-DT-23 | warning | The attribute "uri" is not used by EN 16931 and should be removed. |
| UBL-DT-24 | warning | The attribute "currencyCodeListVersionID" is not used by EN 16931 and should be removed. |
| UBL-DT-25 | warning | The attribute "characterSetCode" is not used by EN 16931 and should be removed. |
| UBL-DT-26 | warning | The attribute "encodingCode" is not used by EN 16931 and should be removed. |
| UBL-DT-27 | warning | The attribute "schemeAgencyID" is not used by EN 16931 and should be removed. |
| UBL-DT-28 | warning | The attribute "listAgencyID" is not used by EN 16931 and should be removed. |
| UBL-CR-002 | warning | cbc:UBLVersionID should be omitted or set to 2.1. |
| UBL-CR-412 | warning | cac:PaymentMeans/cbc:PaymentDueDate is not used in an invoice; use cbc:DueDate. |
| UBL-CR-665 | warning | A scheme identifier on a supporting document reference should be used only for the invoiced object (type code 130). |
| UBL-CR-666 | fatal | An invoiced object reference (type code 130) must not carry an attachment. |
| UBL-CR-673 | fatal | An invoiced object reference (type code 130) must not carry a document description. |
Peppol BIS Billing 3.0
| Rule | Severity | Requirement |
|---|---|---|
| PEPPOL-EN16931-R001 | fatal | The business process (cbc:ProfileID) is required. |
| PEPPOL-EN16931-R002 | fatal | Only one note is allowed on document level, unless seller and buyer are both German. |
| PEPPOL-EN16931-R003 | fatal | A buyer reference (BT-10) or a purchase order reference (BT-13) is required. |
| PEPPOL-EN16931-R004 | fatal | The specification identifier must start with urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0. |
| PEPPOL-EN16931-R005 | fatal | The VAT accounting currency (BT-6) must differ from the invoice currency (BT-5). |
| PEPPOL-EN16931-R007 | fatal | The business process (cbc:ProfileID) must be an approved Peppol profile identifier. |
| PEPPOL-EN16931-R008 | fatal | The document must not contain empty elements. |
| PEPPOL-EN16931-R010 | fatal | The buyer electronic address (BT-49, cbc:EndpointID) is required. |
| PEPPOL-EN16931-R020 | fatal | The seller electronic address (BT-34, cbc:EndpointID) is required. |
| PEPPOL-EN16931-R040 | fatal | Allowance or charge amount must equal base amount times percentage / 100 (tolerance 0.02). |
| PEPPOL-EN16931-R041 | fatal | An allowance or charge with a percentage must also state the base amount. |
| PEPPOL-EN16931-R042 | fatal | An allowance or charge with a base amount must also state the percentage. |
| PEPPOL-EN16931-R043 | fatal | cbc:ChargeIndicator must be exactly 'true' or 'false'. |
| PEPPOL-EN16931-R044 | fatal | A charge on price level is not allowed; ChargeIndicator must be 'false'. |
| PEPPOL-EN16931-R046 | fatal | Item net price must equal gross price minus price discount when a gross price is given. |
| PEPPOL-EN16931-R051 | fatal | Every currencyID must equal the invoice currency code (BT-5), except the VAT total in accounting currency. |
| PEPPOL-EN16931-R053 | fatal | Exactly one tax total with tax subtotals is required. |
| PEPPOL-EN16931-R054 | fatal | Exactly one tax total without subtotals is required when a VAT accounting currency is given, and none otherwise. |
| PEPPOL-EN16931-R055 | fatal | VAT total and VAT total in accounting currency must have the same sign. |
| PEPPOL-EN16931-R061 | fatal | A mandate reference (BT-89) is required for direct debit (payment means 49 or 59). |
| PEPPOL-EN16931-R080 | fatal | A credit note allows only one project reference (document type code 50). |
| PEPPOL-EN16931-R100 | fatal | An invoice line allows only one invoiced object reference. |
| PEPPOL-EN16931-R101 | fatal | A line document reference may be used only for the invoiced object (type code 130). |
| PEPPOL-EN16931-R110 | fatal | A line period start date must not be earlier than the invoice period start date. |
| PEPPOL-EN16931-R111 | fatal | A line period end date must not be later than the invoice period end date. |
| PEPPOL-EN16931-R120 | fatal | Line net amount must equal quantity x (net price / base quantity) + line charges - line allowances (tolerance 0.02). |
| PEPPOL-EN16931-R121 | fatal | The price base quantity must be greater than zero. |
| PEPPOL-EN16931-R130 | fatal | The unit code of the price base quantity must equal the unit code of the invoiced quantity. |
| PEPPOL-EN16931-CL001 | fatal | An attachment MIME code must be PDF, PNG, JPEG, CSV, XLSX or ODS. |
| PEPPOL-EN16931-CL002 | fatal | An allowance reason code must be in the UNCL 5189 subset. |
| PEPPOL-EN16931-CL003 | fatal | A charge reason code must be a UNCL 7161 code. |
| PEPPOL-EN16931-CL006 | fatal | The invoice period description code must be 3, 35 or 432. |
| PEPPOL-EN16931-CL007 | fatal | A currencyID must be an ISO 4217 code. |
| PEPPOL-EN16931-CL008 | fatal | An electronic address scheme must be in the Peppol Electronic Address Identifier Scheme list. |
| PEPPOL-EN16931-F001 | fatal | A date must be formatted YYYY-MM-DD, without time zone. |
| PEPPOL-EN16931-P0100 | fatal | The invoice type code is not allowed for the Peppol profile. |
| PEPPOL-EN16931-P0101 | fatal | The credit note type code must be 381, 396, 81, 83 or 532. |
| PEPPOL-EN16931-P0104 | fatal | Exemption reason code VATEX-EU-G requires VAT category G. |
| PEPPOL-EN16931-P0105 | fatal | Exemption reason code VATEX-EU-O requires VAT category O. |
| PEPPOL-EN16931-P0106 | fatal | Exemption reason code VATEX-EU-IC requires VAT category K. |
| PEPPOL-EN16931-P0107 | fatal | Exemption reason code VATEX-EU-AE requires VAT category AE. |
| PEPPOL-EN16931-P0108 | fatal | Exemption reason code VATEX-EU-D requires VAT category E. |
| PEPPOL-EN16931-P0109 | fatal | Exemption reason code VATEX-EU-F requires VAT category E. |
| PEPPOL-EN16931-P0110 | fatal | Exemption reason code VATEX-EU-I requires VAT category E. |
| PEPPOL-EN16931-P0111 | fatal | Exemption reason code VATEX-EU-J requires VAT category E. |
| PEPPOL-EN16931-P0112 | fatal | Type codes 326 and 389 are allowed only between German parties; 384 only between German or between Slovak parties. |
| PEPPOL-COMMON-R040 | fatal | A GLN (scheme 0088) must be numeric with a valid GS1 check digit. |
| PEPPOL-COMMON-R041 | fatal | A Norwegian organisation number (scheme 0192) must be 9 digits with a valid check digit. |
| PEPPOL-COMMON-R042 | fatal | A Danish CVR number (scheme 0184) must be 8 digits, optionally prefixed with DK. |
| PEPPOL-COMMON-R043 | fatal | A Belgian enterprise number (scheme 0208) must be 10 digits with a valid mod-97 check. |
| PEPPOL-COMMON-R044 | warning | An Italian IPA code (scheme 0201) should be 6 alphanumeric characters. |
| PEPPOL-COMMON-R045 | warning | An Italian tax code (scheme 0210) should be 11 digits or a 16-character codice fiscale. |
| PEPPOL-COMMON-R046 | warning | An Italian tax code (scheme 9907) should be 11 digits or a 16-character codice fiscale. |
| PEPPOL-COMMON-R047 | warning | An Italian VAT code (scheme 0211) should be IT plus 11 digits with a valid check digit. |
| PEPPOL-COMMON-R049 | fatal | A Swedish organisation number (scheme 0007) must be 10 digits with a valid Luhn check digit. |
| PEPPOL-COMMON-R050 | fatal | An Australian Business Number (scheme 0151) must be 11 digits with a valid checksum. |
| PEPPOL-COMMON-R052 | fatal | A Danish P number (scheme 0096) must be 10 digits. |
| PEPPOL-COMMON-R053 | fatal | A Danish SE number (scheme 0198) must be DK followed by 8 digits. |
| PEPPOL-COMMON-R054 | warning | A Dutch KVK number (scheme 0106) should be 8 digits. |
| PEPPOL-COMMON-R055 | warning | A Dutch OIN (scheme 0190) should be 20 digits. |
| PEPPOL-COMMON-R056-1 | warning | A Dutch VAT number (scheme 9944) should have the format NL123456789B12. |
| PEPPOL-COMMON-R056-2 | warning | A Dutch VAT identifier should have the format NL123456789B12. |
| PEPPOL-COMMON-R057 | warning | A Dutch KVK establishment number (scheme 0217) should be 12 digits. |
| GR-S-008-1 | warning | For Greek sellers, one invoice URL (description ##INVOICE|URL##) should be provided. |
| GR-S-011 | warning | Greek sellers should provide one VAT identifier starting with EL and containing a valid TIN. |
Peppol national rules (NO)
Peppol national rules (DK)
| Rule | Severity | Requirement |
|---|---|---|
| DK-R-002 | fatal | Danish sellers must provide a legal entity identifier (CVR number). |
| DK-R-003 | fatal | For Danish parties, a UNSPSC item classification (listID TST) must use version 19.05.01 or 26.08.01. |
| DK-R-004 | fatal | For Danish parties, reason code ZZZ needs a 4-digit reason or a reason of the form text#text. |
| DK-R-005 | fatal | For Danish parties, the payment means code must be 1, 10, 31, 42, 48, 49, 50, 58, 59, 93 or 97. |
| DK-R-006 | fatal | For Danish parties, payment means 31 and 42 require a bank account and a registration number. |
| DK-R-007 | fatal | For Danish parties, payment means 49 requires a mandate identifier and a payer account identifier. |
| DK-R-008 | fatal | For Danish parties, payment means 50 requires a payment ID starting 01#, 04# or 15# and a 7 or 8 digit giro account. |
| DK-R-009 | fatal | For Danish parties, a payment ID starting 04# or 15# must be 19 characters long. |
| DK-R-010 | fatal | For Danish parties, payment means 93 requires a payment ID starting 71#, 73# or 75# and an 8 character creditor number. |
| DK-R-011 | fatal | For Danish parties, a payment ID starting 71# or 75# must be 18 or 19 characters long. |
| DK-R-013 | fatal | For Danish parties, a party identifier must have a schemeID. |
| DK-R-014 | fatal | For Danish sellers, the legal entity identifier must use schemeID 0184 (CVR). |
| DK-R-016 | fatal | For Danish parties, a credit note must not have a negative payable amount. |
| DK-R-017 | fatal | For Danish buyers, the legal entity identifier must use schemeID 0184 (CVR). |
Peppol national rules (IT)
| Rule | Severity | Requirement |
|---|---|---|
| IT-R-001 | fatal | For Italian sellers, the tax registration identifier (BT-32) must be 11 to 16 characters (A-Z, 0-9). |
| IT-R-002 | fatal | Italian sellers must provide address line 1 (BT-35). |
| IT-R-003 | fatal | Italian sellers must provide the city (BT-37). |
| IT-R-004 | fatal | Italian sellers must provide the post code (BT-38). |
Peppol national rules (SE)
| Rule | Severity | Requirement |
|---|---|---|
| SE-R-001 | fatal | A Swedish seller VAT number must be 14 characters long. |
| SE-R-002 | fatal | A Swedish seller VAT number must have 12 digits after the SE prefix. |
| SE-R-003 | fatal | A Swedish organisation number must be numeric. |
| SE-R-004 | fatal | A Swedish organisation number must be 10 characters long. |
| SE-R-005 | fatal | For Swedish sellers, a tax registration identifier must read 'Godkänd för F-skatt'. |
| SE-R-006 | fatal | For Swedish sellers, a standard VAT rate must be 6, 12 or 25. |
| SE-R-007 | warning | A Swedish Plusgiro account identifier should be numeric. |
| SE-R-008 | warning | A Swedish Bankgiro account identifier should be numeric. |
| SE-R-009 | warning | A Swedish Bankgiro account identifier should be 7 or 8 characters long. |
| SE-R-010 | warning | A Swedish Plusgiro account identifier should be 2 to 8 characters long. |
| SE-R-011 | warning | Swedish sellers should use payment means 30 with SE:BANKGIRO or SE:PLUSGIRO instead of 50 or 56. |
| SE-R-012 | warning | Between Swedish parties, a credit transfer should use payment means 30, not 31. |
| SE-R-013 | fatal | A Swedish organisation number must have a valid Luhn check digit. |
Peppol national rules (GR)
| Rule | Severity | Requirement |
|---|---|---|
| GR-R-001-1 | fatal | For Greek sellers, the invoice number must have 6 segments separated by '|'. |
| GR-R-001-2 | fatal | For Greek sellers, invoice number segment 1 must be the valid TIN of the seller or tax representative. |
| GR-R-001-3 | fatal | For Greek sellers, invoice number segment 2 must be the issue date as DD/MM/YYYY. |
| GR-R-001-4 | fatal | For Greek sellers, invoice number segment 3 must be a non-negative integer. |
| GR-R-001-5 | fatal | For 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-6 | fatal | For Greek sellers, invoice number segment 5 must not be empty. |
| GR-R-001-7 | fatal | For Greek sellers, invoice number segment 6 must not be empty. |
| GR-R-002 | fatal | Greek sellers must provide their registered name in cac:PartyName. |
| GR-R-003 | fatal | A Greek seller VAT identifier must start with EL and contain a valid TIN. |
| GR-R-004-1 | fatal | For Greek sellers, exactly one MARK number (description ##M.AR.K##) is required. |
| GR-R-004-2 | fatal | For Greek sellers, the MARK number must be a positive integer. |
| GR-R-005 | fatal | Greek sellers must provide the buyer name in cac:PartyName. |
| GR-R-006 | fatal | For a Greek seller and buyer, the buyer VAT identifier must start with EL and contain a valid TIN. |
| GR-R-008-2 | fatal | For Greek sellers, at most one invoice URL (description ##INVOICE|URL##) is allowed. |
| GR-R-008-3 | fatal | For Greek sellers, an invoice URL reference must contain an external reference URI. |
| GR-R-009 | fatal | A Greek seller electronic address must use scheme 9933 with a valid TIN. |
| GR-R-010 | fatal | For a Greek seller and buyer, the buyer electronic address must use scheme 9933 with a valid TIN. |
Peppol national rules (IS)
| Rule | Severity | Requirement |
|---|---|---|
| IS-R-001 | warning | For Icelandic sellers, the document type code should be 380 or 381. |
| IS-R-002 | fatal | Icelandic sellers must provide a legal identifier with schemeID 0196. |
| IS-R-003 | fatal | Icelandic sellers must provide street name and post code. |
| IS-R-004 | fatal | For Icelandic seller and buyer, the buyer legal identifier with schemeID 0196 is required. |
| IS-R-005 | fatal | For Icelandic seller and buyer, the buyer street name and post code are required. |
| IS-R-006 | fatal | For Icelandic sellers, payment means 9 requires a 12 digit account identifier. |
| IS-R-007 | fatal | For Icelandic sellers, payment means 42 requires a 12 digit account identifier. |
| IS-R-008 | fatal | For Icelandic sellers, an EINDAGI supporting document identifier must be a date YYYY-MM-DD. |
| IS-R-009 | fatal | For Icelandic sellers, an EINDAGI supporting document requires a due date. |
| IS-R-010 | fatal | For Icelandic sellers, the EINDAGI date must be the same as or later than the due date. |
Peppol national rules (NL)
| Rule | Severity | Requirement |
|---|---|---|
| NL-R-001 | fatal | For Dutch sellers, a credit note must reference the original invoice. |
| NL-R-002 | fatal | For Dutch sellers, the seller address must contain street, city and post code. |
| NL-R-003 | fatal | For Dutch sellers, the legal entity identifier must be a KVK or OIN number (schemeID 0106 or 0190). |
| NL-R-004 | fatal | For Dutch seller and buyer, the buyer address must contain street, city and post code. |
| NL-R-005 | fatal | For Dutch seller and buyer, the buyer legal entity identifier must be a KVK or OIN number (schemeID 0106 or 0190). |
| NL-R-006 | fatal | For Dutch sellers with a Dutch tax representative, the representative address must contain street, city and post code. |
| NL-R-007 | fatal | For Dutch sellers, payment means are required when an amount is due. |
| NL-R-008 | fatal | For Dutch seller and buyer, the payment means code must be 30, 48, 49, 57, 58 or 59. |
| NL-R-009 | fatal | For Dutch sellers, an order line reference requires an order reference on document level. |
Peppol national rules (DE)
| Rule | Severity | Requirement |
|---|---|---|
| DE-R-001 | fatal | Between German parties, payment instructions (BG-16) are required. |
| DE-R-002 | fatal | Between German parties, a seller contact (BG-6) is required. |
| DE-R-003 | fatal | Between German parties, the seller city (BT-37) is required. |
| DE-R-004 | fatal | Between German parties, the seller post code (BT-38) is required. |
| DE-R-005 | fatal | Between German parties, the seller contact point (BT-41) is required. |
| DE-R-006 | fatal | Between German parties, the seller contact telephone number (BT-42) is required. |
| DE-R-007 | fatal | Between German parties, the seller contact email address (BT-43) is required. |
| DE-R-008 | fatal | Between German parties, the buyer city (BT-52) is required. |
| DE-R-009 | fatal | Between German parties, the buyer post code (BT-53) is required. |
| DE-R-010 | fatal | Between German parties, the deliver-to city (BT-77) is required when a delivery address is given. |
| DE-R-011 | fatal | Between German parties, the deliver-to post code (BT-78) is required when a delivery address is given. |
| DE-R-014 | fatal | Between German parties, every VAT breakdown must state the VAT rate (BT-119). |
| DE-R-015 | fatal | Between German parties, the buyer reference (BT-10) is required. |
| DE-R-016 | fatal | Between German parties, VAT categories S, Z, E, AE, K, G, L or M require a seller tax identifier or a tax representative. |
| DE-R-017 | warning | Between German parties, the type code should be 326, 380, 384, 389, 381, 875, 876 or 877. |
| DE-R-018 | fatal | Between German parties, Skonto lines in payment terms must follow #SKONTO#TAGE=n#PROZENT=n.nn# and end with a line break. |
| DE-R-019 | warning | Between German parties, the account identifier for payment means 58 should be a valid IBAN. |
| DE-R-020 | warning | Between German parties, the debited account identifier for payment means 59 should be a valid IBAN. |
| DE-R-022 | fatal | Between German parties, attachment file names must be unique. |
| DE-R-023-1 | fatal | Between German parties, credit transfer (30, 58) requires payee account information (BG-17). |
| DE-R-023-2 | fatal | Between German parties, credit transfer (30, 58) must not carry card or direct debit information. |
| DE-R-024-1 | fatal | Between German parties, card payment (48, 54, 55) requires card information (BG-18). |
| DE-R-024-2 | fatal | Between German parties, card payment (48, 54, 55) must not carry credit transfer or direct debit information. |
| DE-R-025-1 | fatal | Between German parties, direct debit (59) requires mandate information (BG-19). |
| DE-R-025-2 | fatal | Between German parties, direct debit (59) must not carry credit transfer or card information. |
| DE-R-026 | warning | Between German parties, a corrected invoice (type 384) should reference the preceding invoice. |
| DE-R-027 | warning | Between German parties, the seller telephone number should contain at least three digits. |
| DE-R-028 | warning | Between German parties, the seller email address should have one @ with a dot in the domain part. |
| DE-R-030 | fatal | Between German parties, direct debit requires the bank assigned creditor identifier (BT-90, scheme SEPA). |
| DE-R-031 | fatal | Between German parties, direct debit requires the debited account identifier (BT-91). |
| DE-R-T02 | warning | Between 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.