Peppol Validation Errors

An Invoice shall have a Specification identifier (BT-24).

Every invoice must declare which specification it conforms to (e.g. urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0). Without it, receivers cannot determine how to interpret the document.

An Invoice shall have an Invoice number (BT-1).

Every invoice must carry a unique sequential number for identification and legal traceability. This is a mandatory legal requirement in most jurisdictions.

An Invoice shall have an Invoice issue date (BT-2).

An issue date is required because it determines VAT reporting periods, payment due dates, and legal validity. The invoice cannot be processed without it.

An Invoice shall have an Invoice type code (BT-3).

The type code distinguishes invoices (380) from credit notes (381) and other document types. Receivers need this to determine how to process the document.

An Invoice shall have an Invoice currency code (BT-5).

All monetary amounts in the invoice are expressed in this currency. Without it, amounts are ambiguous and cannot be booked correctly.

An Invoice shall contain the Seller name (BT-27).

The seller's legal or trading name must be present for the buyer to identify who issued the invoice and for tax compliance purposes.

An Invoice shall contain the Buyer name (BT-44).

The buyer's legal or trading name must be present so the invoice can be matched to the correct entity in the receiver's system.

An Invoice shall contain the Seller postal address.

The seller's postal address (BG-5) is required for tax jurisdiction determination and legal identification of the seller.

The Seller postal address (BG-5) shall contain a Seller country code (BT-40).

The country code within the seller's address is mandatory because it determines the applicable VAT regime and tax rules.

An Invoice shall contain the Buyer postal address (BG-8).

The buyer's postal address is required for tax compliance, particularly for determining the place of supply and applicable VAT rules.

The Buyer postal address shall contain a Buyer country code (BT-55).

The buyer's country code is essential for cross-border VAT determination and correct tax treatment of the transaction.

An Invoice shall have the Sum of Invoice line net amount (BT-106).

The sum of all invoice line net amounts must be stated explicitly. This is the starting point for the invoice total calculation and must equal the sum of all cbc:LineExtensionAmount values.

An Invoice shall have the Invoice total amount without VAT (BT-109).

The total amount excluding VAT must be present. It equals the sum of line net amounts plus document-level charges minus document-level allowances.

An Invoice shall have the Invoice total amount with VAT (BT-112).

The total amount including VAT must be stated so the buyer knows the full amount being invoiced. It equals the tax-exclusive amount plus total VAT.

An Invoice shall have the Amount due for payment (BT-115).

The amount due for payment must be present so the buyer knows exactly how much to pay, accounting for any prepayments or rounding.

An Invoice shall have at least one Invoice line (BG-25).

An invoice without any lines has no items being invoiced. At least one line is required to describe what is being charged.

The Payee name (BT-59) shall be provided in the Invoice, if the Payee (BG-10) is different from the Seller (BG-4).

When payment goes to a party other than the seller (e.g. a factoring company), the payee must be clearly identified by name to avoid payment errors.

The Seller tax representative name (BT-62) shall be provided in the Invoice, if the Seller (BG-4) has a Seller tax representative party (BG-11).

When a seller uses a tax representative (common for non-resident suppliers), the representative's name must be stated for tax authority identification.

The Seller tax representative postal address (BG-12) shall be provided in the Invoice, if the Seller (BG-4) has a Seller tax representative party (BG-11).

When a tax representative is declared, their postal address is required for tax authority communication and jurisdiction determination.

The Seller tax representative postal address (BG-12) shall contain a Tax representative country code (BT-69), if the Seller (BG-4) has a Seller tax representative party (BG-11).

The tax representative's country code determines which country's tax rules they represent the seller under.

Each Invoice line (BG-25) shall have an Invoice line identifier (BT-126).

Every invoice line needs a unique identifier so it can be referenced in disputes, credit notes, or buyer's purchase order matching.

Each Invoice line (BG-25) shall have an Invoiced quantity (BT-129).

The quantity of items being invoiced must be stated on each line so the buyer can verify the amount charged matches what was delivered.

An Invoice line (BG-25) shall have an Invoiced quantity unit of measure code (BT-130).

The unit of measure (e.g. pieces, hours, kilograms) must accompany the quantity so amounts can be verified. Without it, the quantity is ambiguous.

Each Invoice line (BG-25) shall have an Invoice line net amount (BT-131).

The net amount per line (quantity times price, adjusted for line-level allowances and charges) must be present so totals can be verified.

Each Invoice line (BG-25) shall contain the Item name (BT-153).

Every line item must have a name or description so the buyer can identify what they are being charged for.

Each Invoice line (BG-25) shall contain the Item net price (BT-146).

The price per unit after any item price discount must be present on each line so the line net amount can be verified.

The Item net price (BT-146) shall NOT be negative.

A negative unit price is not allowed. If you need to represent a credit or refund, use a credit note document type or an allowance instead.

The Item gross price (BT-148) shall NOT be negative.

The gross price (price before any item-level discount) cannot be negative because it represents the original catalogue or list price.

If both Invoicing period start date (BT-73) and Invoicing period end date (BT-74) are given then the Invoicing period end date (BT-74) shall be later or equal to the Invoicing period start date (BT-73).

When the invoice covers a specific period (e.g. a monthly subscription), the end date cannot be before the start date as that would be logically invalid.

If both Invoice line period start date (BT-134) and Invoice line period end date (BT-135) are given then the Invoice line period end date (BT-135) shall be later or equal to the Invoice line period start date (BT-134).

At the line level, when a service period is specified, the end date must be on or after the start date to represent a valid time span.

Each Document level allowance (BG-20) shall have a Document level allowance amount (BT-92).

When a document-level allowance (discount) is applied, the amount must be stated so the invoice total can be calculated correctly.

Each Document level allowance (BG-20) shall have a Document level allowance VAT category code (BT-95).

The VAT category must be assigned to each document-level allowance so the correct tax treatment can be applied in the VAT breakdown.

Each Document level allowance (BG-20) shall have a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98).

Every document-level allowance must explain why the discount is given, either as free text or using a standard UNTDID 5189 reason code.

Each Document level charge (BG-21) shall have a Document level charge amount (BT-99).

When a document-level charge (e.g. shipping, handling) is applied, the amount must be stated for correct total calculation.

Each Document level charge (BG-21) shall have a Document level charge VAT category code (BT-102).

The VAT category must be assigned to each document-level charge so tax is correctly allocated in the VAT breakdown.

Each Document level charge (BG-21) shall have a Document level charge reason (BT-104) or a Document level charge reason code (BT-105).

Every document-level charge must explain its purpose, either as free text or using a standard UNTDID 7161 reason code.

Each Invoice line allowance (BG-27) shall have an Invoice line allowance amount (BT-136).

When a line-level allowance (discount) is given, the amount must be specified so the line net amount can be calculated correctly.

Each Invoice line allowance (BG-27) shall have an Invoice line allowance reason (BT-139) or an Invoice line allowance reason code (BT-140).

Every line-level allowance must have a reason so the buyer understands why the discount was applied.

Each Invoice line charge (BG-28) shall have an Invoice line charge amount (BT-141).

When a line-level charge (surcharge) is applied, the amount must be stated so the line net amount can be verified.

Each Invoice line charge shall have an Invoice line charge reason or an invoice line allowance reason code.

Every line-level charge must explain its purpose so the buyer understands the additional cost.

Each VAT breakdown (BG-23) shall have a VAT category taxable amount (BT-116).

The taxable amount (tax base) must be present in each VAT breakdown line so the tax amount can be verified against the applicable rate.

Each VAT breakdown (BG-23) shall have a VAT category tax amount (BT-117).

The calculated tax amount must be present in each VAT breakdown line so the total tax can be verified.

Each VAT breakdown (BG-23) shall be defined through a VAT category code (BT-118).

Each VAT breakdown line must specify which VAT category it applies to (e.g. Standard rate, Zero rate, Exempt) so the tax treatment is unambiguous.

Each VAT breakdown (BG-23) shall have a VAT category rate (BT-119), except if the Invoice is not subject to VAT.

The tax rate percentage must be stated in each VAT breakdown so the tax amount can be verified, unless the invoice falls entirely outside the scope of VAT.

A Payment instruction (BG-16) shall specify the Payment means type code (BT-81).

When payment instructions are included, the payment method must be identified (e.g. credit transfer, direct debit, card payment) so the buyer knows how to pay.

A Payment account identifier (BT-84) shall be present if Credit transfer (BG-17) information is provided in the Invoice.

When the invoice specifies credit transfer as the payment method, the account number (IBAN) must be provided so the buyer can make the payment.

In accordance with card payments security standards an invoice should never include a full card primary account number (BT-87). At the moment PCI Security Standards Council has defined that the first 6 digits and last 4 digits are the maximum number of digits to be shown.

For PCI DSS compliance, a full credit card number must never appear on an invoice. Only a truncated version (first 6 and last 4 digits) is permitted.

Each Additional supporting document (BG-24) shall contain a Supporting document reference (BT-122).

When additional documents are attached or referenced (e.g. timesheets, contracts), each must have a reference identifier so they can be located.

If the VAT accounting currency code (BT-6) is present, then the Invoice total VAT amount in accounting currency (BT-111) shall be provided.

When the invoice uses a different currency for VAT reporting (e.g. invoicing in USD but reporting VAT in EUR), the VAT total in the accounting currency must be stated.

Each Item attribute (BG-32) shall contain an Item attribute name (BT-160) and an Item attribute value (BT-161).

When custom item properties are added (e.g. color, size), both the attribute name and value must be present as a pair.

Each Preceding Invoice reference (BG-3) shall contain a Preceding Invoice reference (BT-25).

When referencing a previous invoice (e.g. in a credit note or corrective invoice), the referenced invoice number must be provided.

Each Seller tax representative party (BG-11) shall have a Seller tax representative VAT identifier (BT-63).

A tax representative must be identified by their VAT number so tax authorities can verify their registration and authority to represent the seller.

Each Deliver to address (BG-15) shall contain a Deliver to country code (BT-80).

When a delivery address is specified, the country code is mandatory because it can affect the place of supply for VAT purposes.

If the Payment means type code (BT-81) means SEPA credit transfer, Local credit transfer or Non-SEPA international credit transfer, the Payment account identifier (BT-84) shall be present.

Credit transfer payment methods (codes 30, 58) require a bank account number so the buyer knows where to send the payment.

The Seller electronic address (BT-34) shall have a Scheme identifier.

The seller's electronic address (e.g. Peppol participant ID) must include a scheme identifier so the address type is unambiguous and routable.

The Buyer electronic address (BT-49) shall have a Scheme identifier.

The buyer's electronic address must include a scheme identifier so it can be properly resolved in the Peppol network or other routing systems.

The Item standard identifier (BT-157) shall have a Scheme identifier.

When an item has a standard identifier (e.g. GTIN/EAN), the scheme must be specified so the receiver knows which identification system is used.

The Item classification identifier (BT-158) shall have a Scheme identifier.

When an item has a classification code (e.g. CPV, UNSPSC), the scheme identifier is required so the receiver knows which classification system is being referenced.

An Invoice shall contain maximum one Payment Card account (BG-18).

Only one card payment account may be specified per invoice to avoid ambiguity about which card was or will be charged.

An Invoice shall contain maximum one Payment Mandate (BG-19).

Only one direct debit mandate may be referenced per invoice. Multiple mandates would create ambiguity about which mandate authorizes the collection.

Value added tax point date (BT-7) and Value added tax point date code (BT-8) are mutually exclusive.

The invoice supplies both a literal VAT point date and a code that derives one. Only one mechanism may be used to determine when VAT becomes chargeable.

Each Invoice line (BG-25) shall be categorized with an Invoiced item VAT category code (BT-151).

An invoice line is missing its VAT category classification. Every line must declare how it is taxed (standard-rated, zero-rated, exempt, etc.).

Document level allowance reason code (BT-98) and Document level allowance reason (BT-97) shall indicate the same type of allowance.

A document-level allowance has a reason code and free-text reason that contradict each other. The UNTDID 5189 code must match the textual description.

Document level charge reason code (BT-105) and Document level charge reason (BT-104) shall indicate the same type of charge.

A document-level charge has a reason code and free-text reason that do not match. The UNTDID 7161 code must correspond to the textual description.

Invoice line allowance reason code (BT-140) and Invoice line allowance reason (BT-139) shall indicate the same type of allowance reason.

A line-level allowance has a mismatched reason code and reason text. Both must describe the same type of allowance per UNTDID 5189.

Invoice line charge reason code (BT-145) and Invoice line charge reason (BT-144) shall indicate the same type of charge reason.

A line-level charge has a mismatched reason code and reason text. Both must describe the same type of charge per UNTDID 7161.

The Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48) shall have a prefix in accordance with ISO code ISO 3166-1 alpha-2 by which the country of issue may be identified. Nevertheless, Greece may use the prefix 'EL'.

A VAT identifier is missing the two-letter country prefix or uses an invalid one. VAT numbers must start with an ISO 3166-1 alpha-2 country code (e.g., DE, NL, FR), except Greece which uses EL instead of GR.

Sum of Invoice line net amount (BT-106) = Σ Invoice line net amount (BT-131).

The sum of all individual line net amounts does not equal the document-level LineExtensionAmount. This usually happens when rounding is applied at the line level and the document total is calculated independently.

Sum of allowances on document level (BT-107) = Σ Document level allowance amount (BT-92).

The AllowanceTotalAmount does not equal the sum of individual document-level allowance amounts. This fires when a document-level allowance is added or removed without updating the total.

Sum of charges on document level (BT-108) = Σ Document level charge amount (BT-99).

The ChargeTotalAmount does not equal the sum of individual document-level charge amounts. This fires when a document-level charge is added or removed without updating the total.

Invoice total amount without VAT (BT-109) = Σ Invoice line net amount (BT-131) − Sum of allowances on document level (BT-107) + Sum of charges on document level (BT-108).

The tax-exclusive total does not match the formula. A common cause is forgetting to subtract document-level allowances or add document-level charges.

Invoice total VAT amount (BT-110) = Σ VAT category tax amount (BT-117).

The total VAT amount does not match the sum of VAT amounts per category in the tax breakdown. This fires when rounding is applied inconsistently between the breakdown and the total.

Invoice total amount with VAT (BT-112) = Invoice total amount without VAT (BT-109) + Invoice total VAT amount (BT-110).

The tax-inclusive total does not equal the tax-exclusive amount plus VAT. Often caused by a rounding discrepancy of one cent.

Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) − Paid amount (BT-113) + Rounding amount (BT-114).

The amount due for payment does not match the formula. This commonly fires when a prepaid amount is specified but not subtracted, or a rounding adjustment is not added.

VAT category tax amount (BT-117) = VAT category taxable amount (BT-116) × (VAT category rate (BT-119) / 100), rounded to two decimals.

The tax amount in a VAT breakdown does not equal the taxable amount multiplied by the rate. The most common cause is incorrect rounding: the spec requires rounding the final result to 2 decimals, not truncating.

An Invoice shall at least have one VAT breakdown group (BG-23).

The invoice has no VAT breakdown. Even zero-rated or exempt invoices need at least one <cac:TaxSubtotal> in the <cac:TaxTotal>.

If Invoicing period (BG-14) is used, the Invoicing period start date (BT-73) or the Invoicing period end date (BT-74) shall be filled, or both.

An <cac:InvoicePeriod> element exists at the document level but contains neither a start date nor an end date. The period element is meaningless without at least one date.

If Invoice line period (BG-26) is used, the Invoice line period start date (BT-134) or the Invoice line period end date (BT-135) shall be filled, or both.

An <cac:InvoicePeriod> exists on an invoice line but has no start or end date. A line period must contain at least one date to be valid.

Each Document level allowance (BG-20) shall contain a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98), or both.

A document-level allowance has neither a reason text nor a reason code. At least one must be present so the allowance can be understood and categorized.

Each Document level charge (BG-21) shall contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both.

A document-level charge has neither a reason text nor a reason code. At least one must be present so the charge can be understood and categorized.

Each Invoice line allowance (BG-27) shall contain an Invoice line allowance reason (BT-139) or an Invoice line allowance reason code (BT-140), or both.

A line-level allowance has neither a reason text nor a reason code. At least one must be present to describe why the allowance was applied.

Each Invoice line charge (BG-28) shall contain an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145), or both.

A line-level charge has neither a reason text nor a reason code. At least one must be present to describe why the charge was applied.

In case the Amount due for payment (BT-115) is positive, either the Payment due date (BT-9) or the Payment terms (BT-20) shall be present.

The invoice has a positive amount due but specifies neither a payment due date nor payment terms. The buyer needs to know when or how to pay.

In order for the buyer to automatically identify a supplier, the Seller identifier (BT-29), the Seller legal registration identifier (BT-30) and/or the Seller VAT identifier (BT-31) shall be present.

The seller has no identifying number at all -- no party identification, no legal entity ID, and no VAT number. At least one must be present for automated processing.

The allowed maximum number of decimals for the Document level allowance amount (BT-92) is 2.

The document-level allowance amount has more than 2 decimal places. This can happen when computing a percentage-based discount on a base amount that produces 3+ decimals.

The allowed maximum number of decimals for the Document level allowance base amount (BT-93) is 2.

The base amount from which a document-level allowance is calculated has more than 2 decimal places. The base amount must be a rounded monetary value.

The allowed maximum number of decimals for the Document level charge amount (BT-99) is 2.

The document-level charge (e.g. shipping or handling fee) has more than 2 decimal places. This can occur when a percentage-based surcharge is applied to a base amount.

The allowed maximum number of decimals for the Document level charge base amount (BT-100) is 2.

The base amount for a document-level charge has more than 2 decimal places. All monetary base amounts must be rounded to 2 decimals.

The allowed maximum number of decimals for the Sum of Invoice line net amount (BT-106) is 2.

The sum of all invoice line net amounts has more than 2 decimal places. This typically happens when individual line amounts are not rounded before summing.

The allowed maximum number of decimals for the Sum of allowances on document level (BT-107) is 2.

The total of all document-level allowances has more than 2 decimal places. Ensure each allowance is rounded individually before summing.

The allowed maximum number of decimals for the Sum of charges on document level (BT-108) is 2.

The total of all document-level charges has more than 2 decimal places. Ensure each charge is rounded individually before summing.

The allowed maximum number of decimals for the Invoice total amount without VAT (BT-109) is 2.

The invoice total excluding VAT has more than 2 decimal places. This is the sum of line totals plus charges minus allowances, which must be rounded to 2 decimals.

The allowed maximum number of decimals for the Invoice total VAT amount (BT-110) is 2.

The total VAT amount has more than 2 decimals. This often happens when summing VAT amounts per category that individually have 2 decimals but produce a result with more.

The allowed maximum number of decimals for the Invoice total amount with VAT (BT-112) is 2.

The grand total (net + VAT) has more than 2 decimal places. This is the final invoice amount and must be a clean monetary value.

The allowed maximum number of decimals for the Invoice total VAT amount in accounting currency (BT-111) is 2.

The VAT total expressed in the accounting currency (when different from the document currency) has more than 2 decimal places. Currency conversion often introduces extra decimals.

The allowed maximum number of decimals for the Paid amount (BT-113) is 2.

The prepaid or previously paid amount has more than 2 decimal places. This is a monetary amount and must be rounded.

The allowed maximum number of decimals for the Rounding amount (BT-114) is 2.

The rounding adjustment amount has more than 2 decimal places. The rounding amount itself must be a valid monetary value with at most 2 decimals.

The allowed maximum number of decimals for the Amount due for payment (BT-115) is 2.

The amount due for payment has more than 2 decimal places. This is the final payable amount (total with VAT minus prepaid, plus rounding) and must be a clean monetary value.

The allowed maximum number of decimals for the VAT category taxable amount (BT-116) is 2.

The taxable base amount for a VAT category has more than 2 decimal places. This is the sum of line net amounts for that VAT category and must be rounded.

The allowed maximum number of decimals for the VAT category tax amount (BT-117) is 2.

The VAT amount for a specific category has more than 2 decimal places. This often happens when taxable amount × rate produces 3+ decimals (e.g. 33.33 × 21% = 6.9993).

The allowed maximum number of decimals for the Invoice line net amount (BT-131) is 2.

A line-level net amount has more than 2 decimal places. The Invoice line net amount (BT-131, cbc:LineExtensionAmount) in Peppol and EN16931 can have at most 2 digits after the decimal point. This commonly happens when quantity × price produces a result like 33.333.

The allowed maximum number of decimals for the Invoice line allowance amount (BT-136) is 2.

A line-level allowance (discount) amount has more than 2 decimal places. This can happen when computing a percentage discount on the line amount.

The allowed maximum number of decimals for the Invoice line allowance base amount (BT-137) is 2.

The base amount for a line-level allowance has more than 2 decimal places. The base from which the discount percentage is applied must be a rounded monetary value.

The allowed maximum number of decimals for the Invoice line charge amount (BT-141) is 2.

A line-level charge (surcharge) amount has more than 2 decimal places. This can occur when a percentage-based surcharge is applied to the line amount.

The allowed maximum number of decimals for the Invoice line charge base amount (BT-142) is 2.

The base amount for a line-level charge has more than 2 decimal places. The base from which the surcharge percentage is applied must be a rounded monetary value.

Unit code MUST be coded according to the UN/ECE Recommendation 20 with Rec 21 extension.

Every unitCode attribute on cbc:InvoicedQuantity, cbc:CreditedQuantity and cbc:BaseQuantity must be a code from UN/ECE Recommendation 20, or a Recommendation 21 packaging code with the X prefix. Values like PCE, pcs or Stk are not on the list. In XRechnung the KoSIT rules lower BR-CL-23 to a warning; in Peppol BIS Billing 3.0 it is a fatal error.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Reverse charge" shall contain in the VAT Breakdown (BG-23) exactly one VAT category code (BT-118) equal with "VAT reverse charge".

If any line, allowance, or charge uses VAT category AE, the invoice must include exactly one cac:TaxSubtotal with cbc:ID = 'AE' in the VAT breakdown.

An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Reverse charge" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48) and/or the Buyer legal registration identifier (BT-47).

Reverse-charge lines require seller tax identification (VAT ID, tax registration, or tax rep VAT ID) and buyer identification (VAT ID or legal registration ID).

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Reverse charge" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48) and/or the Buyer legal registration identifier (BT-47).

Same as BR-AE-02 but triggered by a document-level allowance with category AE. Both seller and buyer tax identifiers are required.

An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Reverse charge" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48) and/or the Buyer legal registration identifier (BT-47).

Same as BR-AE-02 but triggered by a document-level charge with category AE. Both seller and buyer tax identifiers are required.

In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Reverse charge" the Invoiced item VAT rate (BT-152) shall be 0 (zero).

Reverse-charge invoice lines must have a VAT rate of 0% because the buyer accounts for the VAT.

In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Reverse charge" the Document level allowance VAT rate (BT-96) shall be 0 (zero).

Document-level allowances classified as reverse charge must carry a 0% VAT rate.

In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Reverse charge" the Document level charge VAT rate (BT-103) shall be 0 (zero).

Document-level charges classified as reverse charge must carry a 0% VAT rate.

In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Reverse charge" the VAT category taxable amount (BT-116) shall equal the sum of Invoice line net amounts (BT-131) minus the sum of Document level allowance amounts (BT-92) plus the sum of Document level charge amounts (BT-99) where the VAT category codes (BT-151, BT-95, BT-102) are "Reverse charge".

The cbc:TaxableAmount in the AE tax subtotal must equal Σ line net amounts − Σ allowances + Σ charges for all items categorized as reverse charge.

The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Reverse charge" shall be 0 (zero).

The seller does not charge VAT on reverse-charge supplies, so cbc:TaxAmount in the AE subtotal must be 0.00.

A VAT breakdown (BG-23) with VAT Category code (BT-118) "Reverse charge" shall have a VAT exemption reason code (BT-121), meaning "Reverse charge" or the VAT exemption reason text (BT-120) "Reverse charge" (or the equivalent standard text in another language).

Reverse-charge subtotals must explain the exemption via cbc:TaxExemptionReasonCode (BT-121) or cbc:TaxExemptionReason (BT-120).

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "IGIC" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "IGIC".

If any line, allowance, or charge uses VAT category L (IGIC), the VAT breakdown must contain at least one cac:TaxSubtotal with cbc:ID = 'L'.

An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

IGIC invoice lines require at least one seller tax identifier to be present on the invoice.

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-AF-02 but triggered by a document-level allowance with IGIC category. At least one seller tax ID is required.

An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IGIC" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-AF-02 but triggered by a document-level charge with IGIC category. At least one seller tax ID is required.

In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IGIC" the invoiced item VAT rate (BT-152) shall be 0 (zero) or greater than zero.

IGIC lines must have a non-negative VAT rate (0% or higher). A missing or negative rate is not allowed.

In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IGIC" the Document level allowance VAT rate (BT-96) shall be 0 (zero) or greater than zero.

IGIC allowances must carry a non-negative VAT rate.

In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IGIC" the Document level charge VAT rate (BT-103) shall be 0 (zero) or greater than zero.

IGIC charges must carry a non-negative VAT rate.

For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "IGIC", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "IGIC" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119).

For each distinct IGIC rate, cbc:TaxableAmount must equal Σ line net amounts + Σ charges − Σ allowances for items at that same IGIC rate.

The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "IGIC" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119).

The cbc:TaxAmount in each IGIC subtotal must equal cbc:TaxableAmount × cbc:Percent / 100, rounded to two decimals.

A VAT breakdown (BG-23) with VAT Category code (BT-118) "IGIC" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120).

IGIC is a taxed category, so exemption reason fields must not be present in the IGIC subtotal.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "IPSI" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "IPSI".

If any line, allowance, or charge uses VAT category M (IPSI), the VAT breakdown must contain at least one cac:TaxSubtotal with cbc:ID = 'M'.

An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

IPSI invoice lines require at least one seller tax identifier to be present on the invoice.

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-AG-02 but triggered by a document-level allowance with IPSI category. At least one seller tax ID is required.

An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IPSI" shall contain the Seller VAT Identifier (BT-31), the Seller Tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-AG-02 but triggered by a document-level charge with IPSI category. At least one seller tax ID is required.

In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "IPSI" the Invoiced item VAT rate (BT-152) shall be 0 (zero) or greater than zero.

IPSI lines must have a non-negative VAT rate (0% or higher). A missing or negative rate is not allowed.

In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "IPSI" the Document level allowance VAT rate (BT-96) shall be 0 (zero) or greater than zero.

IPSI allowances must carry a non-negative VAT rate.

In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "IPSI" the Document level charge VAT rate (BT-103) shall be 0 (zero) or greater than zero.

IPSI charges must carry a non-negative VAT rate.

For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "IPSI", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "IPSI" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119).

For each distinct IPSI rate, cbc:TaxableAmount must equal Σ line net amounts + Σ charges − Σ allowances for items at that same IPSI rate.

The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "IPSI" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119).

The cbc:TaxAmount in each IPSI subtotal must equal cbc:TaxableAmount × cbc:Percent / 100, rounded to two decimals.

A VAT breakdown (BG-23) with VAT Category code (BT-118) "IPSI" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120).

IPSI is a taxed category, so exemption reason fields must not be present in the IPSI subtotal.

An Invoice where the VAT category code (BT-151, BT-95 or BT-102) is “Split payment” shall be a domestic Italian invoice.

The split-payment mechanism (category B) is only valid for domestic Italian invoices. Both seller and buyer must be in Italy.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is “Split payment” shall not contain an invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is “Standard rated”.

Split-payment invoices cannot mix category B with standard-rated category S. All lines, allowances, and charges must consistently use the split-payment category.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Exempt from VAT" shall contain exactly one VAT breakdown (BG-23) with the VAT category code (BT-118) equal to "Exempt from VAT".

If any line, allowance, or charge uses VAT category E, the invoice must include exactly one cac:TaxSubtotal with cbc:ID = 'E' in the VAT breakdown.

An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Exempt from VAT" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

VAT-exempt invoice lines require at least one seller tax identifier to be present on the invoice.

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Exempt from VAT" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-E-02 but triggered by a document-level allowance with exempt category. At least one seller tax ID is required.

An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Exempt from VAT" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-E-02 but triggered by a document-level charge with exempt category. At least one seller tax ID is required.

In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Exempt from VAT", the Invoiced item VAT rate (BT-152) shall be 0 (zero).

VAT-exempt invoice lines must have a VAT rate of 0% since no VAT applies.

In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Exempt from VAT", the Document level allowance VAT rate (BT-96) shall be 0 (zero).

Document-level allowances classified as exempt must carry a 0% VAT rate.

In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Exempt from VAT", the Document level charge VAT rate (BT-103) shall be 0 (zero).

Document-level charges classified as exempt must carry a 0% VAT rate.

In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Exempt from VAT" the VAT category taxable amount (BT-116) shall equal the sum of Invoice line net amounts (BT-131) minus the sum of Document level allowance amounts (BT-92) plus the sum of Document level charge amounts (BT-99) where the VAT category codes (BT-151, BT-95, BT-102) are "Exempt from VAT".

The cbc:TaxableAmount in the exempt subtotal must equal Σ line net amounts − Σ allowances + Σ charges for all items categorized as exempt.

The VAT category tax amount (BT-117) In a VAT breakdown (BG-23) where the VAT category code (BT-118) equals "Exempt from VAT" shall equal 0 (zero).

No VAT is charged on exempt supplies, so cbc:TaxAmount in the exempt subtotal must be 0.00.

A VAT breakdown (BG-23) with VAT Category code (BT-118) "Exempt from VAT" shall have a VAT exemption reason code (BT-121) or a VAT exemption reason text (BT-120).

Exempt subtotals must state why the exemption applies, via cbc:TaxExemptionReasonCode or cbc:TaxExemptionReason.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Export outside the EU" shall contain in the VAT breakdown (BG-23) exactly one VAT category code (BT-118) equal with "Export outside the EU".

If any line, allowance, or charge uses VAT category G, the invoice must include exactly one cac:TaxSubtotal with cbc:ID = 'G' in the VAT breakdown.

An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Export outside the EU" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63).

Export invoice lines require the seller's VAT ID or tax representative VAT ID. Note: unlike other categories, BT-32 (tax registration) alone is not sufficient.

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Export outside the EU" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63).

Same as BR-G-02 but triggered by a document-level allowance with export category. Seller VAT ID or tax representative VAT ID is required.

An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Export outside the EU" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63).

Same as BR-G-02 but triggered by a document-level charge with export category. Seller VAT ID or tax representative VAT ID is required.

In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Export outside the EU" the Invoiced item VAT rate (BT-152) shall be 0 (zero).

Export lines are zero-rated for VAT, so cbc:Percent must be 0.

In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Export outside the EU" the Document level allowance VAT rate (BT-96) shall be 0 (zero).

Document-level allowances classified as export must carry a 0% VAT rate.

In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Export outside the EU" the Document level charge VAT rate (BT-103) shall be 0 (zero).

Document-level charges classified as export must carry a 0% VAT rate.

In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Export outside the EU" the VAT category taxable amount (BT-116) shall equal the sum of Invoice line net amounts (BT-131) minus the sum of Document level allowance amounts (BT-92) plus the sum of Document level charge amounts (BT-99) where the VAT category codes (BT-151, BT-95, BT-102) are "Export outside the EU".

The cbc:TaxableAmount in the export subtotal must equal Σ line net amounts − Σ allowances + Σ charges for all items categorized as export.

The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Export outside the EU" shall be 0 (zero).

Export supplies are zero-rated, so cbc:TaxAmount in the export subtotal must be 0.00.

A VAT breakdown (BG-23) with the VAT Category code (BT-118) "Export outside the EU" shall have a VAT exemption reason code (BT-121), meaning "Export outside the EU" or the VAT exemption reason text (BT-120) "Export outside the EU" (or the equivalent standard text in another language).

Export subtotals must explain the zero-rating via cbc:TaxExemptionReasonCode or cbc:TaxExemptionReason.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Intra-community supply" shall contain in the VAT breakdown (BG-23) exactly one VAT category code (BT-118) equal with "Intra-community supply".

If any line, allowance, or charge uses VAT category K, the invoice must include exactly one cac:TaxSubtotal with cbc:ID = 'K' in the VAT breakdown.

An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Intra-community supply" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48).

Intra-community lines require the seller's VAT ID (or tax rep VAT ID) and the buyer's VAT ID. Both parties must be VAT-registered in the EU.

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Intra-community supply" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48).

Same as BR-IC-02 but triggered by a document-level allowance. Both seller and buyer VAT IDs are required.

An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Intra-community supply" shall contain the Seller VAT Identifier (BT-31) or the Seller tax representative VAT identifier (BT-63) and the Buyer VAT identifier (BT-48).

Same as BR-IC-02 but triggered by a document-level charge. Both seller and buyer VAT IDs are required.

In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Intracommunity supply" the Invoiced item VAT rate (BT-152) shall be 0 (zero).

Intra-community supply lines are zero-rated because the buyer pays VAT in the destination country.

In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Intra-community supply" the Document level allowance VAT rate (BT-96) shall be 0 (zero).

Intra-community allowances must carry a 0% VAT rate.

In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Intra-community supply" the Document level charge VAT rate (BT-103) shall be 0 (zero).

Intra-community charges must carry a 0% VAT rate.

In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" the VAT category taxable amount (BT-116) shall equal the sum of Invoice line net amounts (BT-131) minus the sum of Document level allowance amounts (BT-92) plus the sum of Document level charge amounts (BT-99) where the VAT category codes (BT-151, BT-95, BT-102) are "Intra-community supply".

The cbc:TaxableAmount in the intra-community subtotal must equal Σ line net amounts − Σ allowances + Σ charges for all items categorized as intra-community.

The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" shall be 0 (zero).

No VAT is charged on intra-community supplies, so cbc:TaxAmount must be 0.00.

A VAT breakdown (BG-23) with the VAT Category code (BT-118) "Intra-community supply" shall have a VAT exemption reason code (BT-121), meaning "Intra-community supply" or the VAT exemption reason text (BT-120) "Intra-community supply" (or the equivalent standard text in another language).

Intra-community subtotals must explain the zero-rating via cbc:TaxExemptionReasonCode or cbc:TaxExemptionReason.

In an Invoice with a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" the Actual delivery date (BT-72) or the Invoicing period (BG-14) shall not be blank.

Intra-community invoices must specify when the goods were delivered or the period covered, for VAT reporting in the destination country.

In an Invoice with a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Intra-community supply" the Deliver to country code (BT-80) shall not be blank.

Intra-community invoices must specify the destination country to determine which member state has taxing rights.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Not subject to VAT" shall contain exactly one VAT breakdown group (BG-23) with the VAT category code (BT-118) equal to "Not subject to VAT".

If any line, allowance, or charge uses VAT category O, the invoice must include exactly one cac:TaxSubtotal with cbc:ID = 'O' in the VAT breakdown.

An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Not subject to VAT" shall not contain the Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) or the Buyer VAT identifier (BT-48).

When lines are outside the scope of VAT, the invoice must not contain seller VAT ID, tax representative VAT ID, or buyer VAT ID. This is the opposite of other categories.

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Not subject to VAT" shall not contain the Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) or the Buyer VAT identifier (BT-48).

Same as BR-O-02 but triggered by a document-level allowance. VAT identifiers for seller and buyer must be absent.

An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Not subject to VAT" shall not contain the Seller VAT identifier (BT-31), the Seller tax representative VAT identifier (BT-63) or the Buyer VAT identifier (BT-48).

Same as BR-O-02 but triggered by a document-level charge. VAT identifiers for seller and buyer must be absent.

An Invoice line (BG-25) where the VAT category code (BT-151) is "Not subject to VAT" shall not contain an Invoiced item VAT rate (BT-152).

Lines outside the scope of VAT must not specify a VAT rate at all -- not even 0%. The cbc:Percent element must be omitted.

A Document level allowance (BG-20) where VAT category code (BT-95) is "Not subject to VAT" shall not contain a Document level allowance VAT rate (BT-96).

Allowances outside the scope of VAT must not specify a VAT rate. The cbc:Percent element must be omitted.

A Document level charge (BG-21) where the VAT category code (BT-102) is "Not subject to VAT" shall not contain a Document level charge VAT rate (BT-103).

Charges outside the scope of VAT must not specify a VAT rate. The cbc:Percent element must be omitted.

In a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Not subject to VAT" the VAT category taxable amount (BT-116) shall equal the sum of Invoice line net amounts (BT-131) minus the sum of Document level allowance amounts (BT-92) plus the sum of Document level charge amounts (BT-99) where the VAT category codes (BT-151, BT-95, BT-102) are "Not subject to VAT".

The cbc:TaxableAmount in the O subtotal must equal Σ line net amounts − Σ allowances + Σ charges for all items categorized as not subject to VAT.

The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where the VAT category code (BT-118) is "Not subject to VAT" shall be 0 (zero).

Items outside the scope of VAT have no tax, so cbc:TaxAmount in the O subtotal must be 0.00.

A VAT breakdown (BG-23) with VAT Category code (BT-118) "Not subject to VAT" shall have a VAT exemption reason code (BT-121), meaning "Not subject to VAT" or a VAT exemption reason text (BT-120) "Not subject to VAT" (or the equivalent standard text in another language).

The O subtotal must explain why VAT does not apply via cbc:TaxExemptionReasonCode or cbc:TaxExemptionReason.

An Invoice that contains a VAT breakdown group (BG-23) with a VAT category code (BT-118) "Not subject to VAT" shall not contain other VAT breakdown groups (BG-23).

Category O is exclusive: if the invoice has an O subtotal, no other VAT categories (S, Z, E, AE, etc.) may appear in the breakdown.

An Invoice that contains a VAT breakdown group (BG-23) with a VAT category code (BT-118) "Not subject to VAT" shall not contain an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is not "Not subject to VAT".

When category O is used in the VAT breakdown, every invoice line must also use category O. No mixing is allowed.

An Invoice that contains a VAT breakdown group (BG-23) with a VAT category code (BT-118) "Not subject to VAT" shall not contain Document level allowances (BG-20) where Document level allowance VAT category code (BT-95) is not "Not subject to VAT".

When category O is used in the VAT breakdown, every document-level allowance must also use category O.

An Invoice that contains a VAT breakdown group (BG-23) with a VAT category code (BT-118) "Not subject to VAT" shall not contain Document level charges (BG-21) where Document level charge VAT category code (BT-102) is not "Not subject to VAT".

When category O is used in the VAT breakdown, every document-level charge must also use category O.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Standard rated" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "Standard rated".

If any line, allowance, or charge uses VAT category S, the VAT breakdown must contain at least one cac:TaxSubtotal with cbc:ID = 'S'.

An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Standard rated" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Standard-rated invoice lines require at least one seller tax identifier to be present on the invoice.

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Standard rated" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-S-02 but triggered by a document-level allowance. At least one seller tax ID is required.

An Invoice that contains a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Standard rated" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-S-02 but triggered by a document-level charge. At least one seller tax ID is required.

In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Standard rated" the Invoiced item VAT rate (BT-152) shall be greater than zero.

Standard-rated lines must have a positive VAT rate (e.g., 21%, 19%, 25%). A rate of 0 is not valid for category S.

In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Standard rated" the Document level allowance VAT rate (BT-96) shall be greater than zero.

Standard-rated allowances must have a positive VAT rate.

In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Standard rated" the Document level charge VAT rate (BT-103) shall be greater than zero.

Standard-rated charges must have a positive VAT rate.

For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "Standard rated", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "Standard rated" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119).

For each distinct standard rate, cbc:TaxableAmount must equal Σ line net amounts + Σ charges − Σ allowances for items at that same standard rate.

The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "Standard rated" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119).

The cbc:TaxAmount in each standard-rated subtotal must equal cbc:TaxableAmount × cbc:Percent / 100, rounded to two decimals.

A VAT breakdown (BG-23) with VAT Category code (BT-118) "Standard rate" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120).

Standard-rated VAT is a taxed category, so exemption reason fields must not be present in the S subtotal.

An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "Zero rated" shall contain in the VAT breakdown (BG-23) exactly one VAT category code (BT-118) equal with "Zero rated".

If any line, allowance, or charge uses VAT category Z, the invoice must include exactly one cac:TaxSubtotal with cbc:ID = 'Z' in the VAT breakdown.

An Invoice that contains an Invoice line where the Invoiced item VAT category code (BT-151) is "Zero rated" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Zero-rated invoice lines require at least one seller tax identifier to be present on the invoice.

An Invoice that contains a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Zero rated" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-Z-02 but triggered by a document-level allowance. At least one seller tax ID is required.

An Invoice that contains a Document level charge where the Document level charge VAT category code (BT-102) is "Zero rated" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63).

Same as BR-Z-02 but triggered by a document-level charge. At least one seller tax ID is required.

In an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Zero rated" the Invoiced item VAT rate (BT-152) shall be 0 (zero).

Zero-rated lines must have a VAT rate of exactly 0%.

In a Document level allowance (BG-20) where the Document level allowance VAT category code (BT-95) is "Zero rated" the Document level allowance VAT rate (BT-96) shall be 0 (zero).

Zero-rated allowances must carry a 0% VAT rate.

In a Document level charge (BG-21) where the Document level charge VAT category code (BT-102) is "Zero rated" the Document level charge VAT rate (BT-103) shall be 0 (zero).

Zero-rated charges must carry a 0% VAT rate.

In a VAT breakdown (BG-23) where VAT category code (BT-118) is "Zero rated" the VAT category taxable amount (BT-116) shall equal the sum of Invoice line net amount (BT-131) minus the sum of Document level allowance amounts (BT-92) plus the sum of Document level charge amounts (BT-99) where the VAT category codes (BT-151, BT-95, BT-102) are "Zero rated".

The cbc:TaxableAmount in the zero-rated subtotal must equal Σ line net amounts − Σ allowances + Σ charges for all items categorized as zero-rated.

The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "Zero rated" shall equal 0 (zero).

Zero-rated supplies have no VAT, so cbc:TaxAmount in the Z subtotal must be 0.00.

A VAT breakdown (BG-23) with VAT Category code (BT-118) "Zero rated" shall not have a VAT exemption reason code (BT-121) or VAT exemption reason text (BT-120).

Zero-rated VAT is a taxed category (at 0%), so exemption reason fields must not be present in the Z subtotal.

Mime code must be according to subset of IANA code list.

Peppol restricts attachment MIME types to a specific subset of IANA media types (e.g. application/pdf, image/png, image/jpeg, text/csv, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet). This is stricter than the base EN16931 rules which do not constrain MIME codes.

Reason code MUST be according to subset of UNCL 5189 D.16B.

Peppol requires that allowance reason codes use values from the UN/CEFACT code list 5189 (revision D.16B). This ensures interoperability by restricting allowance reasons to a well-defined, machine-readable set.

Reason code MUST be according to UNCL 7161 D.16B.

Charge reason codes must come from the UN/CEFACT code list 7161 (revision D.16B). This is the Peppol-mandated code list for describing why a charge is applied.

Invoice period description code must be according to UNCL 2005 D.16B.

When an invoice period description code is provided, it must use a value from UN/CEFACT code list 2005 (revision D.16B). This standardizes how the invoicing period is described (e.g. delivery date, payment date, invoice date).

Currency code must be according to ISO 4217:2005.

All currency codes used in the invoice must be valid ISO 4217:2005 three-letter currency codes. Peppol enforces this to guarantee machine-readable currency identification across borders.

Electronic address identifier scheme must be from the codelist "Electronic Address Identifier Scheme".

The @schemeID attribute on buyer and seller electronic addresses must use a value from the Peppol Electronic Address Identifier Scheme code list (e.g. '0088' for EAN/GLN, '0184' for Danish CVR, '0192' for Norwegian organization number). This is a Peppol-specific requirement not present in base EN16931.

A date MUST be formatted YYYY-MM-DD.

Peppol requires all dates to use ISO 8601 format (YYYY-MM-DD) without time components. The base EN16931 rules check date presence but Peppol additionally enforces strict formatting.

Invoice type code MUST be set according to the profile.

For Peppol invoices, the invoice type code (BT-3) must be one of the allowed UNCL 1001 subset values for invoices (e.g. 380 for commercial invoice, 383 for debit note, 386 for prepayment invoice). Credit note codes are not allowed here.

Credit note type code MUST be set according to the profile.

For Peppol credit notes, the credit note type code (BT-3) must be '381' (credit note) or another allowed value from the Peppol subset. Invoice type codes are not allowed on credit notes.

Tax Category G MUST be used when exemption reason code is VATEX-EU-G.

When the VAT exemption reason code is 'VATEX-EU-G' (export outside the EU), the tax category code must be 'G'. Peppol enforces a strict mapping between VATEX codes and tax category codes to ensure consistency.

Tax Category O MUST be used when exemption reason code is VATEX-EU-O.

When the VAT exemption reason code is 'VATEX-EU-O' (not subject to VAT), the tax category code must be 'O'. This ensures that out-of-scope VAT items use the correct category.

Tax Category K MUST be used when exemption reason code is VATEX-EU-IC.

When the VAT exemption reason code is 'VATEX-EU-IC' (intra-Community supply), the tax category code must be 'K'. This enforces the Peppol mapping between intra-Community VAT exemptions and tax categories.

Tax Category AE MUST be used when exemption reason code is VATEX-EU-AE.

When the VAT exemption reason code is 'VATEX-EU-AE' (reverse charge), the tax category code must be 'AE'. Peppol requires this specific pairing to flag reverse-charge transactions correctly.

Tax Category E MUST be used when exemption reason code is VATEX-EU-D.

When the VAT exemption reason code is 'VATEX-EU-D' (intra-Community acquisition from second-hand goods, works of art, collectors' items, and antiques), the tax category must be 'E' (exempt). Peppol maps several distinct EU Directive exemptions to category E.

Tax Category E MUST be used when exemption reason code is VATEX-EU-F.

When the VAT exemption reason code is 'VATEX-EU-F' (exemption under Article 132 of the VAT Directive, e.g. medical, educational, and social services), the tax category must be 'E' (exempt).

Tax Category E MUST be used when exemption reason code is VATEX-EU-I.

When the VAT exemption reason code is 'VATEX-EU-I' (exemption under Article 135 of the VAT Directive, e.g. financial and insurance services), the tax category must be 'E' (exempt).

Tax Category E MUST be used when exemption reason code is VATEX-EU-J.

When the VAT exemption reason code is 'VATEX-EU-J' (exemption under Article 136 of the VAT Directive, e.g. supplies of certain second-hand goods), the tax category must be 'E' (exempt).

Invoice type code 326 or 384 are only allowed when both buyer and seller are German organizations.

Invoice type codes 326 (partial invoice) and 384 (corrected invoice) are German CIUS extensions. Peppol only permits them when both trading partners have German country codes, ensuring these national variants do not leak into cross-border exchanges.

Business process MUST be provided.

Peppol requires a business process identifier (BT-23) in every invoice. This is not required by base EN16931 but is mandatory in the Peppol BIS profile to enable correct message routing on the Peppol network.

No more than one note is allowed on document level, unless both the buyer and seller are German organizations.

Peppol restricts the invoice to a single document-level note (BT-22) to keep invoices concise. An exception is made for German-to-German invoices where multiple notes are allowed per the German CIUS.

A buyer reference or purchase order reference MUST be provided.

Peppol requires either a buyer reference (BT-10) or a purchase order reference (BT-13) to enable the buyer to match the invoice to their internal processes. At least one must be present.

Specification identifier MUST have the value 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0'.

The specification identifier (BT-24) must be the exact Peppol BIS Billing 3.0 customization ID. This tells receivers that the invoice conforms to the Peppol profile of EN16931.

VAT accounting currency code MUST be different from invoice currency code when provided.

If a tax currency code (BT-6) is provided, it must differ from the document currency code (BT-5). There is no point specifying a separate VAT accounting currency if it is the same as the invoice currency.

Business process MUST be in the format 'urn:fdc:peppol.eu:2017:poacc:billing:NN:1.0' where NN indicates the process number.

The business process identifier (BT-23) must follow the exact Peppol URN pattern. This validates the format of ProfileID to ensure it matches one of the recognized Peppol billing processes.

Document MUST not contain empty elements.

Peppol forbids empty XML elements (elements with no text content and no meaningful attributes). This is stricter than EN16931 and ensures data quality across the network. In Peppol BIS Billing 3.0 the rule has the flag fatal: it is an error, not a warning, so one empty element makes the whole invoice invalid.

Buyer electronic address MUST be provided.

Peppol requires the buyer's electronic address (BT-49) with a scheme identifier. This is essential for message routing on the Peppol network and is a Peppol-specific requirement beyond EN16931.

Seller electronic address MUST be provided.

Peppol requires the seller's electronic address (BT-34) with a scheme identifier. This enables return messages and is mandatory for Peppol network identification.

Allowance/charge amount must equal base amount * percentage/100 if base amount and percentage exists.

When both the base amount and percentage are provided on an allowance or charge, the calculated amount must match: amount = base amount * percentage / 100. Peppol enforces arithmetic consistency.

Allowance/charge base amount MUST be provided when allowance/charge percentage is provided.

If a percentage is given on an allowance or charge, the base amount it applies to must also be present. You cannot specify a percentage without the base amount to compute from.

Allowance/charge percentage MUST be provided when allowance/charge base amount is provided.

If a base amount is given on an allowance or charge, the percentage must also be present. The base amount and percentage are a pair; you cannot provide one without the other.

Allowance/charge ChargeIndicator value MUST equal 'true' or 'false'.

The ChargeIndicator element must be exactly 'true' (for charges) or 'false' (for allowances). Other boolean representations like '1', '0', 'yes', or 'no' are not accepted.

Charge on price level is NOT allowed. Only value 'false' allowed.

At the price level (cac:Price → cac:AllowanceCharge), only allowances (discounts) are permitted, not charges. The ChargeIndicator must be 'false' to indicate a price discount.

Item net price MUST equal (Gross price - Allowance amount) when gross price is provided.

When a gross price is provided with a price-level allowance, the net price must equal the gross price minus the allowance amount. This ensures pricing arithmetic is consistent.

All currencyID attributes must have the same value as the invoice currency code (BT-5), except for the invoice total VAT amount in accounting currency (BT-111).

Every @currencyID attribute in the invoice must match the document currency code, except for the tax total that represents VAT in the accounting currency. This prevents mixing currencies within a single invoice.

Only one tax total with tax subtotals MUST be provided.

An invoice must contain exactly one cac:TaxTotal element that includes cac:TaxSubtotal children. This is the primary tax breakdown in the document currency.

Only one tax total without tax subtotals MUST be provided when tax currency code is provided.

When a separate tax currency (BT-6) is specified, there must be exactly one additional cac:TaxTotal element without cac:TaxSubtotal children. This element carries the VAT total in the accounting currency.

Invoice total VAT amount and Invoice total VAT amount in accounting currency MUST have the same operational sign.

Both the VAT amount in document currency and the VAT amount in accounting currency must be either both positive or both negative (or both zero). A sign mismatch indicates a conversion error.

Mandate reference MUST be provided for direct debit.

When the payment means code indicates direct debit (code '49'), a mandate reference identifier must be provided. This is required for SEPA direct debit processing.

Only one project reference is allowed on document level.

Peppol limits the invoice to a single project reference (BT-11) at the document level. Multiple project references are not supported in the Peppol BIS profile.

Only one invoiced object is allowed per line.

Each invoice line may reference at most one invoiced object identifier (BT-128). This Peppol restriction ensures clear one-to-one mapping between lines and referenced objects.

Element Document reference can only be used for Invoice line object.

At the line level, cac:DocumentReference is only permitted for referencing an invoiced object (BT-128). Other document reference types must be placed at the document level, not on individual lines.

Start date of line period MUST be within invoice period.

If both an invoice-level period and a line-level period are specified, the line period start date must fall within (or equal) the invoice period boundaries. This prevents lines from claiming service outside the invoice scope.

End date of line period MUST be within invoice period.

If both an invoice-level period and a line-level period are specified, the line period end date must fall within (or equal) the invoice period boundaries.

Invoice line net amount MUST equal (Invoiced quantity * (Item net price/item price base quantity) + Sum of invoice line charge amount - sum of invoice line allowance amount.

The line extension amount (BT-131) must be arithmetically correct: quantity times unit price (adjusted for base quantity), plus line charges, minus line allowances. Peppol enforces this calculation with rounding tolerance.

Base quantity MUST be a positive number above zero.

The price base quantity (BT-149) must be greater than zero. A zero or negative base quantity would make the unit price calculation undefined or nonsensical.

Unit code of price base quantity MUST be same as invoiced quantity.

The unit of measure on the price base quantity (BT-150) must match the unit on the invoiced quantity (BT-130). You cannot price by kilograms but invoice by pieces. For a wrong line net amount, see PEPPOL-EN16931-R120.

Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16) enthalten.

XRechnung makes the PAYMENT INSTRUCTIONS group (BG-16) mandatory, although it is optional in EN 16931. German public buyers need to know how to pay before they can approve the invoice, so at least one payment means block with a Payment means type code (BT-81) must be present.

Die Gruppe "SELLER CONTACT" (BG-6) muss übermittelt werden.

XRechnung requires the SELLER CONTACT group (BG-6), so the buyer always has a named contact with phone and email for queries. In EN 16931 this group is optional; in XRechnung it is mandatory and its sub-elements are checked by BR-DE-5, BR-DE-6 and BR-DE-7.

Das Element "Seller city" (BT-37) muss übermittelt werden.

XRechnung requires the Seller city (BT-37) in the seller postal address. EN 16931 only requires the country code, but German public buyers need the full address.

Das Element "Seller post code" (BT-38) muss übermittelt werden.

XRechnung requires the Seller post code (BT-38) in the seller postal address, in addition to the country code that EN 16931 requires.

Das Element "Seller contact point" (BT-41) muss übermittelt werden.

The seller contact (BG-6) must name a Seller contact point (BT-41): a person or department the buyer can contact about the invoice.

Das Element "Seller contact telephone number" (BT-42) muss übermittelt werden.

XRechnung requires the Seller contact telephone number (BT-42) in the seller contact (BG-6). BR-DE-27 additionally expects at least three digits in the value.

Das Element "Seller contact email address" (BT-43) muss übermittelt werden.

XRechnung requires the Seller contact email address (BT-43) in the seller contact (BG-6). BR-DE-28 additionally checks that the value looks like a valid email address.

Das Element "Buyer city" (BT-52) muss übermittelt werden.

XRechnung requires the Buyer city (BT-52) in the buyer postal address. EN 16931 only requires the buyer country code.

Das Element "Buyer post code" (BT-53) muss übermittelt werden.

XRechnung requires the Buyer post code (BT-53) in the buyer postal address.

Das Element "Deliver to city" (BT-77) muss übermittelt werden, wenn die Gruppe "DELIVER TO ADDRESS" (BG-15) übermittelt wird.

If the invoice contains a DELIVER TO ADDRESS (BG-15), XRechnung requires the Deliver to city (BT-77) in it. An address without a city is not usable for the receiving authority.

Das Element "Deliver to post code" (BT-78) muss übermittelt werden, wenn die Gruppe "DELIVER TO ADDRESS" (BG-15) übermittelt wird.

If the invoice contains a DELIVER TO ADDRESS (BG-15), XRechnung requires the Deliver to post code (BT-78) in it.

Das Element "VAT category rate" (BT-119) muss übermittelt werden.

Every VAT breakdown (BG-23) must carry a VAT category rate (BT-119) in XRechnung, although EN 16931 itself makes this element optional. Use 0 when no VAT is charged in that category.

Das Element "Buyer reference" (BT-10) muss übermittelt werden.

XRechnung requires the Buyer reference (BT-10) on every invoice. For invoices to German public authorities this is normally the Leitweg-ID, the routing identifier the buyer gives you (format like 991-12345-67). Without it the invoice cannot be routed to the correct office and is usually rejected. For non-public buyers, use the reference the buyer asked for.

Wenn in einer Rechnung die Steuercodes S, Z, E, AE, K, G, L oder M verwendet werden, muss mindestens eines der Elemente "Seller VAT identifier" (BT-31), "Seller tax registration identifier" (BT-32) oder "SELLER TAX REPRESENTATIVE PARTY" (BG-11) übermittelt werden.

If any VAT category code S, Z, E, AE, K, G, L or M is used (on the document, on a document-level allowance or charge, or on a line), the seller must be identifiable for tax purposes: provide the Seller VAT identifier (BT-31), the Seller tax registration identifier (BT-32, the German Steuernummer) or a SELLER TAX REPRESENTATIVE PARTY (BG-11).

Mit dem Element "Invoice type code" (BT-3) sollen ausschließlich folgende Codes aus der Codeliste UNTDID 1001 übermittelt werden: 326 (Partial invoice), 380 (Commercial invoice), 384 (Corrected invoice), 389 (Self-billed invoice) und 381 (Credit note),875 (Partial construction invoice), 876 (Partial final construction invoice), 877 (Final construction invoice).

XRechnung only expects a subset of UNTDID 1001 invoice type codes (BT-3): 326 partial invoice, 380 commercial invoice, 384 corrected invoice, 389 self-billed invoice, 381 credit note, and 875, 876, 877 for construction invoices. Other codes produce this warning.

Skonto Zeilen in [Element] müssen diesem regulärem Ausdruck entsprechen: [XR-SKONTO-REGEX]. Die Informationen zur Gewährung von Skonto müssen wie folgt im Element "Payment terms" (BT-20) übermittelt werden: Anzugeben ist im ersten Segment "SKONTO", im zweiten "TAGE=n", im dritten "PROZENT=n". Prozentzahlen sind ohne Vorzeichen sowie mit Punkt getrennt von zwei Nachkommastellen anzugeben. Liegt dem zu berechnenden Betrag nicht BT-115, "fälliger Betrag" zugrunde, sondern nur ein Teil des fälligen Betrags der Rechnung, ist der Grundwert zur Berechnung von Skonto als viertes Segment "BASISBETRAG=n" gemäß dem semantischen Datentypen Amount anzugeben. Jeder Eintrag beginnt mit einer #, die Segmente sind mit einer # getrennt und eine Zeile schließt mit einer # ab. Am Ende einer vollständigen Skontoangabe muss ein XML-konformer Zeilenumbruch folgen. Alle Angaben zur Gewährung von Skonto müssen in Großbuchstaben gemacht werden. Zusätzliches Whitespace (Leerzeichen, Tabulatoren oder Zeilenumbrüche) ist nicht zulässig. Andere Zeichen oder Texte als in den oberen Vorgaben genannt sind nicht zulässig.

XRechnung defines a machine-readable syntax for cash discount (Skonto) terms in Payment terms (BT-20). Each Skonto line must look like #SKONTO#TAGE=14#PROZENT=2.00# with an optional #BASISBETRAG=n.nn# segment, in upper case, without extra spaces, and the text must end with a line break after the last Skonto line.

"Payment account identifier" (BT-84) soll eine korrekte IBAN enthalten, wenn in "Payment means type code" (BT-81) mit dem Code 58 SEPA als Zahlungsmittel gefordert wird.

When the Payment means type code (BT-81) is 58 (SEPA credit transfer), the Payment account identifier (BT-84) should be a valid IBAN. The rule checks the format and the IBAN check digits.

"Debited account identifier" (BT-91) soll eine korrekte IBAN enthalten, wenn in "Payment means type code" (BT-81) mit dem Code 59 SEPA als Zahlungsmittel gefordert wird.

When the Payment means type code (BT-81) is 59 (SEPA direct debit), the Debited account identifier (BT-91) should be a valid IBAN of the buyer's account.

Das Element "Specification identifier" (BT-24) soll syntaktisch der Kennung des Standards XRechnung entsprechen.

The Specification identifier (BT-24) should be the XRechnung identifier, so receivers know the invoice follows the German CIUS. For XRechnung 3.0 the value is urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0 (or the extension or CVD variants). This validator runs the KoSIT rules only when BT-24 contains the XRechnung 3.0 URN, so here the warning means the value is close but not exactly one of the three valid identifiers (standard, extension, CVD), for example because of surrounding whitespace or an extra suffix.

Das "filename"-Attribut aller "EmbeddedDocumentBinaryObject"-Elemente muss eindeutig sein

Every embedded attachment (BT-125) must have a unique filename attribute. Duplicate file names make it impossible for the receiver to store or reference attachments reliably.

Wenn BT-81 "Payment means type code" einen Schlüssel für Überweisungen enthält (30, 58), muss BG-17 "CREDIT TRANSFER" übermittelt werden.

When the Payment means type code (BT-81) is a credit transfer code (30 or 58), the CREDIT TRANSFER group (BG-17) must be present, so the buyer knows which account to pay into.

Wenn BT-81 "Payment means type code" einen Schlüssel für Überweisungen enthält (30, 58), dürfen BG-18 und BG-19 nicht übermittelt werden.

A credit transfer (code 30 or 58) cannot also carry PAYMENT CARD INFORMATION (BG-18) or DIRECT DEBIT (BG-19) data in the same payment means.

Wenn BT-81 "Payment means type code" einen Schlüssel für Kartenzahlungen enthält (48, 54, 55), muss genau BG-18 "PAYMENT CARD INFORMATION" übermittelt werden.

When the Payment means type code (BT-81) is a card payment code (48, 54 or 55), the PAYMENT CARD INFORMATION group (BG-18) must be present.

Wenn BT-81 "Payment means type code" einen Schlüssel für Kartenzahlungen enthält (48, 54, 55), dürfen BG-17 und BG-19 nicht übermittelt werden.

A card payment (code 48, 54 or 55) cannot also carry CREDIT TRANSFER (BG-17) or DIRECT DEBIT (BG-19) data in the same payment means.

Wenn BT-81 "Payment means type code" einen Schlüssel für Lastschriften enthält (59), muss genau BG-19 "DIRECT DEBIT" übermittelt werden.

When the Payment means type code (BT-81) is 59 (SEPA direct debit), the DIRECT DEBIT group (BG-19) must be present.

Wenn BT-81 "Payment means type code" einen Schlüssel für Lastschriften enthält (59), dürfen BG-17 und BG-18 nicht übermittelt werden.

A direct debit (code 59) cannot also carry CREDIT TRANSFER (BG-17) or PAYMENT CARD INFORMATION (BG-18) data in the same payment means.

Wenn im Element "Invoice type code" (BT-3) der Code 384 (Corrected invoice) übergeben wird, soll PRECEDING INVOICE REFERENCE BG-3 mind. einmal vorhanden sein.

A corrected invoice (Invoice type code BT-3 = 384) should reference the invoice it corrects through PRECEDING INVOICE REFERENCE (BG-3).

In BT-42 sollen mindestens drei Ziffern enthalten sein.

The Seller contact telephone number (BT-42) should contain at least three digits. Placeholder values such as "-" or "n/a" trigger this warning.

In BT-43 soll genau ein @-Zeichen enthalten sein, welches nicht von einem Leerzeichen, einem Punkt, aber mindestens zwei Zeichen auf beiden Seiten flankiert werden soll. Ein Punkt sollte nicht am Anfang oder am Ende stehen.

The Seller contact email address (BT-43) should be a plausible email address: exactly one @, no spaces, and a domain with at least one dot that does not start or end with a dot.

Wenn "DIRECT DEBIT" BG-19 vorhanden ist, dann muss "Bank assigned creditor identifier" BT-90 übermittelt werden.

If DIRECT DEBIT (BG-19) is present, the Bank assigned creditor identifier (BT-90, the SEPA creditor ID) must be given, because the buyer's bank needs it to execute the debit.

Wenn "DIRECT DEBIT" BG-19 vorhanden ist, dann muss "Debited account identifier" BT-91 übermittelt werden.

If DIRECT DEBIT (BG-19) is present, the Debited account identifier (BT-91) must be given: the buyer's account that will be debited.

Das Element "Contract reference" (BT-12) muss übermittelt werden.

Applies only to XRechnung invoices that declare the CVD (Clean Vehicles Directive) specification identifier. These invoices must carry a Contract reference (BT-12) so the vehicle procurement can be reported.

Das Element "Tender or lot reference" (BT-17) muss übermittelt werden.

Applies only to CVD (Clean Vehicles Directive) XRechnung invoices. They must carry the Tender or lot reference (BT-17) of the procurement.

In einer Rechnung muss mindestens eine INVOICE LINE (BG-25) enthalten sein, in der der Scheme identifier von "Item classification identifier" (BT-158) den Wert 'CVD' und der "Item attribute name" (BT-160) den Wert 'cva' enthält.

A CVD (Clean Vehicles Directive) invoice must contain at least one invoice line (BG-25) that identifies a vehicle: an Item classification identifier (BT-158) with scheme CVD and an item attribute (BT-160) named cva.

Ein "Item classification identifier" (BT-158) mit dem Scheme identifier 'CVD' muss einen Wert aus der Liste der zulässigen Fahrzeugkategorien enthalten.

In a CVD invoice, an Item classification identifier (BT-158) with scheme CVD must be a permitted vehicle category: M1, M2, M3, N1, N2 or N3.

Wenn innerhalb von ITEM ATTRIBUTES (BG-32) der "Item attribute name" (BT-160) den Wert 'cva' hat, muss der "Item attribute value" (BT-161) einen der zulässigen Werte enthalten.

In a CVD invoice, the item attribute named cva (BT-160) must have one of the permitted values (BT-161): clean, zero-emission or other.

Wenn der Scheme identifier von "Item classification identifier" (BT-158) mit dem Wert 'CVD' angegeben ist, muss in derselben Rechnungszeile genau ein "Item attribute name" (BT-160) mit dem Wert 'cva' vorhanden sein.

In a CVD invoice, a line with a CVD item classification (BT-158) must have exactly one item attribute named cva (BT-160).

Wenn "Item attribute name" (BT-160) mit dem Wert 'cva' angegeben ist, muss in derselben Rechnungszeile genau ein "Item classification identifier" (BT-158) mit dem Scheme identifier 'CVD' vorhanden sein.

In a CVD invoice, a line with an item attribute named cva (BT-160) must have exactly one item classification (BT-158) with scheme CVD.

Eine Rechnung sollte zur Angabe des Liefer-/Leistungsdatums entweder BT-72 "Actual delivery date", BG-14 "Invoicing period" oder in jeder Rechnungsposition BG-26 "Invoice line period" enthalten.

German VAT law requires the date of delivery or service on an invoice. XRechnung therefore recommends one of: Actual delivery date (BT-72), an Invoicing period (BG-14), or an Invoice line period (BG-26) on every line. This is an information-level hint and does not make the invoice invalid.

Das Element [Element] "Attached Document" (BT-125) benutzt einen nicht zulässigen MIME-Code: [mimeCode]. Im Falle einer Extension darf zusätzlich zu der Liste der mime codes (definiert in Abschnitt 8.2, "Binary Object") der MIME-Code application/xml genutzt werden.

Applies only to invoices that declare the XRechnung extension identifier. Attached documents (BT-125) may use the standard MIME codes (application/pdf, image/png, image/jpeg, text/csv, xlsx, ods) plus application/xml. Other MIME codes are rejected.

Der Wert von "Invoice line net amount" (BT-131) einer "INVOICE LINE" (BG-25) oder einer "SUB INVOICE LINE" (BG-DEX-01) soll der Summe der "Invoice line net amount" (BT-131) der direkt darunterliegenden "SUB INVOICE LINE" (BG-DEX-01) entsprechen.

XRechnung extension invoices can use sub invoice lines (BG-DEX-01). The Invoice line net amount (BT-131) of a line that has sub lines should equal the sum of the net amounts of its direct sub lines.

Eine Sub Invoice Line (BG-DEX-01) muss genau eine "SUB INVOICE LINE VAT INFORMATION" (BG-DEX-06) enthalten.

In an XRechnung extension invoice, every sub invoice line (BG-DEX-01) must carry exactly one VAT information block (BG-DEX-06).

Any scheme identifier in [Element] MUST be coded using one of the ISO 6523 ICD list.

In an XRechnung extension invoice, the schemeID of a party identifier must be an ISO 6523 ICD code (the SEPA scheme is also allowed for the seller and payee creditor ID).

Any scheme identifier in [Element] MUST be coded using one of the ISO 6523 ICD list.

In an XRechnung extension invoice, the schemeID of a legal registration identifier must be an ISO 6523 ICD code.

Any scheme identifier in [Element] MUST be coded using one of the ISO 6523 ICD list.

In an XRechnung extension invoice, the schemeID of an item standard identifier must be an ISO 6523 ICD code (e.g. 0160 for GTIN).

Any scheme identifier for an Endpoint Identifier in [Element] MUST belong to the CEF EAS code list.

In an XRechnung extension invoice, the schemeID of an electronic address (endpoint) must be a code from the CEF EAS code list (e.g. EM for email, 0204 for Leitweg-ID, 9930 for German VAT number).

Any scheme identifier for a Delivery location identifier in [Element] MUST be coded using one of the ISO 6523 ICD list.

In an XRechnung extension invoice, the schemeID of a delivery location identifier must be an ISO 6523 ICD code.

Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) - Paid amount (BT-113) + Rounding amount (BT-114) + Σ Third party payment amount (BT-DEX-002).

In an XRechnung extension invoice, the Amount due for payment (BT-115) must equal Invoice total with VAT (BT-112) minus Paid amount (BT-113) plus Rounding amount (BT-114) plus the sum of third party payments (BT-DEX-002).

Das Element "Third party payment type" BT-DEX-001 muss übermittelt werden, wenn die Gruppe "THIRD PARTY PAYMENT" (BG-DEX-09) übermittelt wird.

In an XRechnung extension invoice, each THIRD PARTY PAYMENT group (BG-DEX-09) must state the Third party payment type (BT-DEX-001).

Das Element "Third party payment amount" BT-DEX-002 muss übermittelt werden, wenn die Gruppe "THIRD PARTY PAYMENT" (BG-DEX-09) übermittelt wird.

In an XRechnung extension invoice, each THIRD PARTY PAYMENT group (BG-DEX-09) must state the Third party payment amount (BT-DEX-002).

Das Element "Third party payment description" BT-DEX-003 muss übermittelt werden, wenn die Gruppe "THIRD PARTY PAYMENT" (BG-DEX-09) übermittelt wird.

In an XRechnung extension invoice, each THIRD PARTY PAYMENT group (BG-DEX-09) must have a Third party payment description (BT-DEX-003).

Die maximale Anzahl zulässiger Nachkommastellen für das Element "Third party payment amount" (BT-DEX-002) ist 2.

The Third party payment amount (BT-DEX-002) may have at most two decimal places, like all other amounts in EN 16931.

Die Währungsangabe von "Third party payment amount" BT-DEX-002 muss BT-5 ("Invoice currency code") entsprechen.

The currency of the Third party payment amount (BT-DEX-002) must be the Invoice currency code (BT-5).

This CII file might use the concept of Sub Invoice Lines. However XRechnung does not support this.

In a CII file with the XRechnung extension identifier, ram:ParentLineID suggests sub invoice lines. XRechnung only supports sub invoice lines in UBL, so the hierarchy will not be understood by receivers.

BT-124 "External document location" muss eine absolute URL mit gültigem Schema enthalten.

The External document location (BT-124) must be an absolute URL with a valid scheme, such as https://example.de/delivery-note.pdf. Relative paths or bare host names are rejected.

Wenn BT-149 (Item price base quantity) sowohl in GrossPriceProductTradePrice als auch in NetPriceProductTradePrice vorhanden ist, müssen die Werte identisch sein. Wenn BT-150 (unit of measure code) auf dem NetPrice-Pfad vorhanden ist, muss es auch auf dem GrossPrice-Pfad vorhanden und identisch sein.

CII only. If the Item price base quantity (BT-149) is given on both the gross price and the net price, the two values must be the same. If the net price carries a unit of measure (BT-150), the gross price must carry the same unit.

BT-123 "Supporting document description" (ram:Name) darf innerhalb von "Additional supporting documents" (BG-24) höchstens einmal vorkommen.

CII only. Within an additional supporting document (BG-24, type code 916), the Supporting document description (BT-123, ram:Name) may occur at most once.

BT-125 "Attached document" (ram:AttachmentBinaryObject) darf innerhalb von "Additional Supporting documents" (BG-24) höchstens einmal vorkommen.

CII only. Within an additional supporting document (BG-24, type code 916), the Attached document (BT-125, ram:AttachmentBinaryObject) may occur at most once.

Datumsangaben in UBL müssen im Format JJJJ-MM-TT (YYYY-MM-DD) übermittelt werden.

UBL only. Dates must be written as YYYY-MM-DD without time or time zone. The rule checks cbc:IssueDate, cbc:DueDate, cbc:StartDate, cbc:EndDate, cbc:ActualDeliveryDate, cbc:TaxPointDate and cbc:PaymentDueDate.

Datumsangaben in UNCEFACT/CII müssen das Attribut format="102" tragen und im Format JJJJMMTT (YYYYMMDD) übermittelt werden.

CII only. Date values must carry format="102" and be written as YYYYMMDD.

Das Bildungsschema für "Item classification identifier" (BT-158) ist aus der Codeliste UNTDID 7143 zu wählen.

In a CVD invoice, the scheme of an Item classification identifier (BT-158) must come from the UNTDID 7143 code list, with CVD added as an allowed value.

Allowance/charge ChargeIndicator value MUST equal 'true' or 'false'.

KoSIT adopted Peppol rule R043 into the XRechnung CII schematron and split it in two. R043-1 checks document-level and line-level allowances and charges (ram:SpecifiedTradeAllowanceCharge): the charge indicator must be exactly 'true' (charge) or 'false' (allowance). Values such as '1', '0', 'yes' or an empty indicator fail.

Allowance/charge ChargeIndicator value MUST equal 'true' or 'false'.

The second half of the KoSIT CII version of Peppol rule R043. It checks the price discount on an item price (ram:AppliedTradeAllowanceCharge in ram:GrossPriceProductTradePrice, BT-147): the charge indicator must be exactly 'true' or 'false'. For a price discount it is normally 'false'.

Danish suppliers MUST provide legal entity (CVR-number)

When the seller is located in Denmark, the invoice must include the seller's CVR number (Central Business Register number) as the legal entity identifier.

If ItemClassification is provided from Danish suppliers, UNSPSC version 19.05.01 or 26.08.01 should be used.

When a Danish supplier provides commodity classification codes on invoice lines, only UNSPSC versions 19.05.01 or 26.08.01 are accepted by the Danish infrastructure.

When specifying non-VAT Taxes for Danish customers, Danish suppliers MUST use the AllowanceChargeReasonCode="ZZZ" and MUST be specified in AllowanceChargeReason; Either as the 4-digit Tax category or must include a #, but the # is not allowed as first and last character

Danish invoices with non-VAT taxes (e.g., environmental or excise taxes) must encode the tax category in allowance/charge reason fields using specific Danish conventions, with reason code ZZZ and a structured reason string.

For Danish suppliers the following Payment means codes are allowed: 1, 10, 31, 42, 48, 49, 50, 58, 59, 93 and 97

Only a restricted set of payment means codes are valid for Danish supplier invoices. Other codes such as 30 (credit transfer) are not permitted in the Danish Peppol profile.

For Danish suppliers bank account and registration account is mandatory if payment means is 31 or 42

When a Danish supplier specifies payment by debit transfer (31) or payment to bank account (42), the bank account number and registration number must be provided.

For Danish suppliers PaymentMandate/ID and PayerFinancialAccount/ID are mandatory when payment means is 49

When a Danish supplier uses payment means code 49 (direct debit), the direct debit mandate ID and the payer's financial account must be specified.

For Danish Suppliers PaymentID is mandatory and MUST start with 01#, 04# or 15# (kortartkode), and PayeeFinancialAccount/ID (Giro kontonummer) is mandatory and must be 7 or 8 numerical characters long, when payment means equals 50 (Giro)

Danish Giro payments (code 50) require a structured PaymentID starting with the kortartkode prefix (01#, 04#, or 15#) and a valid 7- or 8-digit Giro account number.

For Danish Suppliers if the PaymentID is prefixed with 04# or 15# the 16 digits instruction Id must be added to the PaymentID eg. "04#1234567890123456" when Payment means equals 50 (Giro)

When using Danish Giro payments with kortartkode 04 or 15, the PaymentID must include a 16-digit instruction ID after the prefix to form a complete payment reference.

For Danish Suppliers the PaymentID is mandatory and MUST start with 71#, 73# or 75# (kortartkode) and CreditAccount/AccountID (Kreditornummer) is mandatory and MUST be exactly 8 characters long, when Payment means equals 93 (FIK)

Danish FIK payments (code 93) require a structured PaymentID starting with 71#, 73#, or 75# and an 8-character creditor number (Kreditornummer).

For Danish Suppliers if the PaymentID is prefixed with 71# or 75# the 15-16 digits instruction Id must be added to the PaymentID eg. "71#1234567890123456" when payment Method equals 93 (FIK)

When using Danish FIK payments with kortartkode 71 or 75, the PaymentID must include a 15- or 16-digit instruction ID after the prefix.

For Danish Suppliers it is mandatory to use schemeID when PartyIdentification/ID is used for AccountingCustomerParty or AccountingSupplierParty

Danish invoices require that every party identification (for both supplier and customer) includes an explicit schemeID attribute to identify the numbering scheme used.

For Danish Suppliers it is mandatory to specify schemeID as "0184" (DK CVR-number) when PartyLegalEntity/CompanyID is used for AccountingSupplierParty

The Danish supplier's legal entity CompanyID must use schemeID "0184", which designates the Danish CVR (Central Business Register) number.

For Danish Suppliers, a Credit note cannot have a negative total (PayableAmount)

Danish credit notes must have a zero or positive PayableAmount. A negative total on a credit note is not allowed in the Danish Peppol profile.

When the Supplier is Greek, the Invoice Id should consist of 6 segments

Greek suppliers must use a structured invoice ID format with 6 segments separated by pipe characters, as required for integration with the Greek IAPR/myDATA tax reporting system.

When the Supplier is Greek, the Invoice Id first segment must be a valid TIN Number and match either the Supplier's or the Tax Representative's Tin Number

The first segment of a Greek invoice ID must be a valid Greek TIN (AFM) that matches the supplier or their tax representative, ensuring consistency with IAPR/myDATA reporting.

For the Greek Suppliers, the VAT must start with 'EL' and must be a valid TIN number

Greek supplier VAT numbers must use the 'EL' country prefix (not 'GR') followed by a valid 9-digit Greek TIN (AFM), as required by the Greek tax authority.

When Supplier is Greek, there must be one MARK Number

Greek invoices must include exactly one MARK (Unique Registration Number) assigned by the IAPR/myDATA system, which proves the invoice was reported to the Greek tax authority.

When Supplier is Greek, the MARK Number must be a positive integer

The MARK number assigned by Greece's IAPR/myDATA system must be a positive integer value, as it is a sequential registration number from the tax authority.

Greek Suppliers must provide the VAT number of the buyer, if the buyer is Greek

When both supplier and buyer are Greek, the buyer's VAT number (BT-48) must be provided for domestic transaction reporting via IAPR/myDATA.

When Supplier is Greek, there should be no more than one invoice url

Greek invoices transmitted via Peppol must not contain more than one invoice URL in the additional document references, as this could cause ambiguity in IAPR/myDATA processing.

Greek suppliers that send an invoice through the PEPPOL network must use a correct TIN number as an electronic address according to PEPPOL Electronic Address Identifier scheme (schemeID 9933).

The Greek supplier's Peppol endpoint must use scheme 9933 (Greek TIN-based electronic address) with a valid Greek TIN number.

Greek Suppliers that send an invoice through the PEPPOL network to a greek buyer must use a correct TIN number as an electronic address according to PEPPOL Electronic Address Identifier scheme (SchemeID 9933)

When a Greek supplier invoices a Greek buyer via Peppol, the buyer's endpoint must also use scheme 9933 with a valid Greek TIN as the electronic address identifier.

When Supplier is Greek, there should be one invoice url

Greek suppliers are expected to include an invoice URL in the additional document references, typically linking to the invoice on the IAPR/myDATA platform for verification.

Greek suppliers must provide their Seller Tax Registration Number, prefixed by the country code

Greek suppliers should include their tax registration number (BT-32) with the 'EL' country prefix for proper identification in Greek tax reporting.

If seller is icelandic then invoice type should be 380 or 381

Icelandic suppliers should use invoice type 380 (commercial invoice) or 381 (credit note). Other invoice type codes may not be supported by Icelandic systems.

If seller is icelandic then it shall contain sellers legal id

Icelandic suppliers must provide their kennitala (Icelandic national ID / business registration number) as the seller's legal entity identifier (BT-30).

If seller is icelandic then it shall contain his address with street name and zip code

Icelandic suppliers must provide a complete postal address including both street name (BT-35) and postal code (BT-38).

If seller and buyer are icelandic then the invoice shall contain the buyers icelandic legal identifier

When both seller and buyer are located in Iceland, the buyer's kennitala (Icelandic national ID / business registration number) must be included as the buyer's legal entity identifier (BT-47).

If seller and buyer are icelandic then the invoice shall contain the buyers address with street name and zip code

When both seller and buyer are Icelandic, the buyer's postal address must include both the street name (BT-50) and postal code (BT-53).

If seller is icelandic and payment means code is 9 then a 12 digit account id must exist

When an Icelandic supplier uses payment means code 9 (national payment claim / krafa), the payment account must be a 12-digit Icelandic bank account number consisting of bank number, ledger code 66, and account number.

If seller is icelandic and payment means code is 42 then a 12 digit account id must exist

When an Icelandic supplier uses payment means code 42 (bank transfer), the payment account must be a valid 12-digit Icelandic bank account number.

If seller is icelandic and invoice contains supporting description EINDAGI then the id form must be YYYY-MM-DD

When an Icelandic supplier includes an EINDAGI (final due date) as a supporting document description, the associated ID must be a valid date in YYYY-MM-DD format.

If seller is icelandic and invoice contains supporting description EINDAGI invoice must have due date

When an Icelandic invoice includes an EINDAGI (final due date) entry, the invoice must also have a regular due date (BT-9) specified.

If seller is icelandic and invoice contains supporting description EINDAGI the id date must be same or later than due date

The Icelandic EINDAGI (final due date) must be equal to or later than the invoice's regular due date (BT-9), as the final due date cannot precede the standard payment term.

BT-32 (Seller tax registration identifier) - For Italian suppliers BT-32 minimum length 11 and maximum length shall be 16.

Italian suppliers must provide a tax registration identifier (BT-32) that is between 11 and 16 characters, accommodating the Italian Codice Fiscale (16 chars) or Partita IVA (11 chars).

BT-35 (Seller address line 1) - Italian suppliers MUST provide the postal address line 1.

Italian suppliers are required to provide the first line of their postal address (street name) as mandated by Italian e-invoicing regulations.

BT-37 (Seller city) - Italian suppliers MUST provide the postal address city.

Italian suppliers must include their city name in the postal address, as required by Italian fiscal regulations.

BT-38 (Seller post code) - Italian suppliers MUST provide the postal address post code.

Italian suppliers must provide their CAP (Codice di Avviamento Postale / Italian postal code) in the seller's address.

For suppliers in the Netherlands, if the document is a creditnote, the document MUST contain an invoice reference (cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID)

Dutch credit notes must always reference the original invoice they relate to. This is a mandatory requirement for Dutch suppliers to enable proper matching of credits to invoices.

For suppliers in the Netherlands the supplier's address (cac:AccountingSupplierParty/cac:Party/cac:PostalAddress) MUST contain street name (cbc:StreetName), city (cbc:CityName) and post code (cbc:PostalZone)

Dutch suppliers must provide a complete postal address with street name, city, and postal code. Partial addresses are not accepted under Dutch Peppol requirements.

For suppliers in the Netherlands, the legal entity identifier MUST be either a KVK or OIN number (schemeID 0106 or 0190)

Dutch suppliers must identify themselves using either a KVK number (Kamer van Koophandel / Chamber of Commerce, schemeID 0106) or an OIN number (Organisatie Identificatie Nummer, schemeID 0190).

For suppliers in the Netherlands, if the customer is in the Netherlands, the customer address (cac:AccountingCustomerParty/cac:Party/cac:PostalAddress) MUST contain the street name (cbc:StreetName), the city (cbc:CityName) and post code (cbc:PostalZone)

When a Dutch supplier invoices a Dutch customer, the customer's address must also be complete with street name, city, and postal code.

For suppliers in the Netherlands, if the customer is in the Netherlands, the customer's legal entity identifier MUST be either a KVK or OIN number (schemeID 0106 or 0190)

When both parties are Dutch, the buyer must also be identified with either a KVK number (schemeID 0106) or OIN number (schemeID 0190).

For suppliers in the Netherlands, if the fiscal representative is in the Netherlands, the representative's address (cac:TaxRepresentativeParty/cac:PostalAddress) MUST contain street name (cbc:StreetName), city (cbc:CityName) and post code (cbc:PostalZone)

When a Dutch supplier has a Dutch tax representative, that representative's postal address must include street name, city, and postal code.

For suppliers in the Netherlands, the supplier MUST provide a means of payment (cac:PaymentMeans) if the payment is from customer to supplier

Dutch invoices where the customer owes payment to the supplier must include payment means information. This is mandatory so the buyer knows how to pay.

For suppliers in the Netherlands, if the customer is in the Netherlands, the payment means code (cac:PaymentMeans/cbc:PaymentMeansCode) MUST be one of 30, 48, 49, 57, 58 or 59

Domestic Dutch-to-Dutch invoices only allow specific payment means codes: credit transfer (30), bank card (48), direct debit (49), standing agreement (57), SEPA credit transfer (58), or SEPA direct debit (59).

For suppliers in the Netherlands, if an order line reference (cac:OrderLineReference/cbc:LineID) is used, there must be an order reference on the document level (cac:OrderReference/cbc:ID)

Dutch invoices that reference order line numbers at the line level must also include the order number at the document level, to ensure the line references can be resolved.

For Norwegian suppliers, a VAT number MUST be the country code prefix NO followed by a valid Norwegian organization number (nine numbers) followed by the letters MVA.

Norwegian VAT numbers must follow the strict format NO + 9-digit organisation number + MVA (e.g., NO123456789MVA). The organisation number is assigned by the Bronnoysund Register Centre.

For Norwegian suppliers, most invoice issuers are required to append "Foretaksregisteret" to their invoice.

Norwegian companies registered as AS (aksjeselskap), ASA (allmennaksjeselskap), or foreign branch companies must include the text "Foretaksregisteret" (the Norwegian Register of Business Enterprises) on their invoices, as required by the Norwegian Business Register Act section 10-2.

For Swedish suppliers, Swedish VAT-numbers must consist of 14 characters.

Swedish VAT numbers must be exactly 14 characters long, following the format "SE" + 10-digit organisation number + "01" (e.g., SE1234567890 01).

For Swedish suppliers, the Swedish VAT-numbers must have the trailing 12 characters in numeric form

After the "SE" prefix, all remaining 12 characters of a Swedish VAT number must be digits. Letters or special characters in the numeric portion are not allowed.

Swedish organisation numbers should be numeric.

Swedish organisation numbers (organisationsnummer) must consist entirely of numeric characters. They are 10-digit numbers assigned by Bolagsverket (Swedish Companies Registration Office).

Swedish organisation numbers consist of 10 characters.

A Swedish organisation number (organisationsnummer) must be exactly 10 digits long, in the format NNNNNN-NNNN (though without the hyphen in the XML).

For Swedish suppliers, when using Seller tax registration identifier, 'Godkand for F-skatt' must be stated

Swedish suppliers who provide a tax registration identifier (BT-32) must include the text "Godkand for F-skatt" (approved for F-tax), which is a legal requirement for Swedish businesses holding F-tax certification.

For Swedish suppliers, only standard VAT rate of 6, 12 or 25 are used

Sweden has three standard VAT rates: 6% (books, newspapers, transport), 12% (food, hotels, restaurants), and 25% (standard rate). No other non-zero VAT rates are valid.

For Swedish suppliers using Plusgiro, the Account ID must be numeric

When a Swedish supplier provides a Plusgiro account number, it must contain only numeric characters.

For Swedish suppliers using Bankgiro, the Account ID must be numeric

When a Swedish supplier provides a Bankgiro account number, it must contain only numeric characters.

For Swedish suppliers using Bankgiro, the Account ID must have 7-8 characters

Swedish Bankgiro account numbers are 7 or 8 digits long. Account IDs outside this range are invalid Bankgiro numbers.

For Swedish suppliers using Plusgiro, the Account ID must have 2-8 characters

Swedish Plusgiro account numbers are between 2 and 8 digits long. Account IDs outside this range are invalid Plusgiro numbers.

For Swedish suppliers using Swedish Bankgiro or Plusgiro, the proper way to indicate this is to use Code 30 for PaymentMeans and FinancialInstitutionBranch ID with code SE:BANKGIRO or SE:PLUSGIRO

Swedish Bankgiro and Plusgiro payments must be indicated using payment means code 30 (credit transfer) combined with FinancialInstitutionBranch/ID set to "SE:BANKGIRO" or "SE:PLUSGIRO".

For domestic transactions between Swedish trading partners, credit transfer should be indicated by PaymentMeansCode="30"

Domestic Swedish-to-Swedish invoices should use payment means code 30 (credit transfer) rather than other codes like 58 (SEPA credit transfer).

The last digit of a Swedish organization number must be valid according to the Luhn algorithm.

Swedish organisation numbers use a Luhn check digit as the last digit. This rule validates the mathematical correctness of the organisation number to catch typos and invalid numbers.

The PDF cannot be read

The file starts like a PDF, but its structure (cross-reference table, objects or the embedded file stream) cannot be parsed, so no invoice XML can be taken from it.

The PDF is encrypted

The PDF has an /Encrypt dictionary (a password or permissions). PDF/A-3, and so ZUGFeRD and Factur-X, do not allow encryption, and the embedded invoice XML cannot be read.

No invoice XML is embedded in the PDF

A ZUGFeRD or Factur-X PDF carries the invoice as an embedded file named factur-x.xml (Factur-X, ZUGFeRD 2.1 and later), xrechnung.xml (XRECHNUNG profile of ZUGFeRD 2.1.1), zugferd-invoice.xml (ZUGFeRD 2.0) or ZUGFeRD-invoice.xml (ZUGFeRD 1.0). None was found in the /EmbeddedFiles name tree or the catalog /AF array, and the XMP names no other embedded file.

More than one invoice XML is embedded

The PDF embeds more than one file with an invoice XML name. A ZUGFeRD or Factur-X PDF holds exactly one invoice XML, so a receiver cannot tell which one is the invoice. The one named in the XMP DocumentFileName is checked.

The invoice XML does not have the file name its standard requires

The file name of the embedded invoice XML must match the standard declared in the XMP: factur-x.xml for Factur-X and ZUGFeRD 2.1 and later (xrechnung.xml is also accepted with ConformanceLevel XRECHNUNG), zugferd-invoice.xml for ZUGFeRD 2.0 and ZUGFeRD-invoice.xml for ZUGFeRD 1.0. Receivers look the XML up by this name.

The file specification has no valid /AFRelationship

PDF/A-3 requires every embedded file to state its relationship to the document (/AFRelationship). ZUGFeRD and Factur-X allow Alternative, Source or Data for the invoice XML (Alternative for the EN 16931 based profiles in Germany, Data or Source in France).

The invoice XML is not listed in the catalog /AF array

PDF/A-3 associates an embedded file with the document through the /AF (associated files) array of the document catalog. ZUGFeRD and Factur-X require the invoice XML to be associated this way.

The embedded invoice XML has no MIME type

PDF/A-3 requires the embedded file stream to state its MIME type in /Subtype. For the invoice XML it is text/xml.

The MIME type of the invoice XML is not text/xml

ZUGFeRD and Factur-X give the invoice XML the MIME type text/xml. Another value (for example application/xml, or a name with a stray #) is accepted by most receivers, but does not follow the specification.

The PDF has no readable XMP metadata

The document catalog must have a /Metadata stream with XMP. It declares PDF/A-3 and the ZUGFeRD / Factur-X properties (DocumentType, DocumentFileName, Version, ConformanceLevel). The stream is missing or is not well-formed XML.

A ZUGFeRD / Factur-X property is missing from the XMP

The XMP must have the Factur-X (urn:factur-x:pdfa:CrossIndustryDocument:invoice:1p0#) or ZUGFeRD properties DocumentType, DocumentFileName, Version and ConformanceLevel. Receivers read the profile and the file name from them.

The XMP DocumentType is not INVOICE

For an invoice or credit note, DocumentType in the XMP is INVOICE.

The XMP Version is not a known value

Version in the XMP is the version of the XMP schema: 1.0 for Factur-X and ZUGFeRD (1p0 and 2p0 occur in older files), or the XRechnung version (1.2 to 3.0) for the XRECHNUNG profile.

The XMP ConformanceLevel is not a known profile

ConformanceLevel in the XMP names the profile: MINIMUM, BASIC WL, BASIC, EN 16931 (COMFORT in ZUGFeRD 1.0), EXTENDED, EXTENDED-CTC-FR or XRECHNUNG.

The XMP ConformanceLevel does not match the profile of the XML

The profile in the XMP must be the profile of the embedded XML, given by its specification identifier (BT-24, ram:GuidelineSpecifiedDocumentContextParameter/ram:ID). For example urn:cen.eu:en16931:2017 is EN 16931 and urn:factur-x.eu:1p0:basicwl is BASIC WL.

The XMP DocumentFileName does not match the embedded XML

DocumentFileName in the XMP must be the file name of the embedded invoice XML.

The XMP does not declare PDF/A-3

ZUGFeRD and Factur-X are PDF/A-3 files: the XMP must have pdfaid:part 3 and pdfaid:conformance A, B or U. Only PDF/A-3 allows embedded XML files. This checks the declaration only, not that the PDF meets PDF/A-3.

The XMP has no PDF/A extension schema for the ZUGFeRD / Factur-X properties

PDF/A allows XMP properties outside the standard schemas only when the XMP describes them in a PDF/A extension schema (pdfaExtension:schemas with pdfaSchema:namespaceURI). The ZUGFeRD / Factur-X specification includes this block; without it a PDF/A validator rejects the file.

No PDF/A output intent for the device colours used

The pages use device colours (DeviceGray, DeviceRGB or DeviceCMYK), so PDF/A requires an output intent in the catalog: /OutputIntents with /S /GTS_PDFA1 and an ICC profile (/DestOutputProfile). Default colour spaces (DefaultGray, DefaultRGB, DefaultCMYK) on the page are accepted instead. Content streams are scanned in a basic way only.

A font is not embedded

PDF/A requires every font used to show text to be embedded (FontFile, FontFile2 or FontFile3 in its font descriptor), so the invoice looks the same everywhere. This checks the fonts in the resources of the pages and their form XObjects; Type 3 fonts need no embedding.

The embedded XML is ZUGFeRD 1.0, which is not checked

ZUGFeRD 1.0 uses its own XML (CrossIndustryDocument), not the EN 16931 CII syntax (CrossIndustryInvoice), and does not meet EN 16931. It is no longer a valid e-invoice in Germany or France, so the XML checks do not run on it.

Empty element

An element has no value and no child elements (attributes do not count). EN 16931 has no rule against empty elements, so a plain EN 16931 CII invoice or a Factur-X MINIMUM or BASIC WL invoice with one passes the official rules. Peppol BIS, XRechnung and the Factur-X BASIC, EN 16931 and EXTENDED rules report them (PEPPOL-EN16931-R008), so this hint runs only where that rule does not. Many receivers read an empty element as an error or as a missing value. ram:ApplicableHeaderTradeDelivery is not flagged: the CII schema requires it even without delivery information.

VAT identifier not in its compact form or not in the format of its country

Checks the Seller VAT identifier (BT-31), the Buyer VAT identifier (BT-48) and the Seller tax representative VAT identifier (BT-63). The official rules check only the two-letter prefix (BR-CO-09); a few country rules check more. A VAT identifier with spaces, dots or hyphens, or one without the format of its country, is not found in VIES or in the receiver's master data. The formats are those VIES uses for the EU member states (Greece: EL, Northern Ireland: XI), and the known formats for GB, NO (with MVA) and CH (CHE, optionally with MWST, TVA or IVA; the official notation CHE-123.456.789 MWST is fine too). A field an official rule already reports (NO-R-001, SE-R-001, SE-R-002, GR-R-003) gets no hint. This checks the format only, not whether the number is registered.

IBAN with spaces or hyphens, the wrong length or wrong check digits

Checks the Payment account identifier (BT-84) and the Debited account identifier (BT-91) when they look like an IBAN (two letters of a country that has IBANs, then two digits): UBL cac:PayeeFinancialAccount/cbc:ID and cac:PaymentMandate/cac:PayerFinancialAccount/cbc:ID under any payment means code, and CII ram:IBANID. Other account numbers, such as a Swedish Bankgiro, are not checked. ISO 13616 writes the IBAN without spaces or hyphens in electronic form, with a fixed length per country and check digits that pass the mod 97 test. The official rules do not check the IBAN, except KoSIT BR-DE-19/20 and Peppol DE-R-019/020 for German invoices; where one of them reports an account, it gets no hint.

Unusable electronic address

Checks the Seller electronic address (BT-34) and the Buyer electronic address (BT-49) for a placeholder (unknown, n/a, none, test, - or 0), for scheme 0204 a Leitweg-ID with the wrong syntax or check digit, and for scheme EM a value that is not an email address. The official rules check the scheme (BR-CL-25) and the value only for some schemes (e.g. 0088 GLN, 0208 Belgian enterprise number), so such an address can pass, but no invoice can be delivered to it. Whether an address is registered in the Peppol network is not checked.