Belgium Peppol BIS Billing 3.0 is the mandatory invoice standard for all B2B e-invoicing transactions in Belgium from January 2026. Understanding this standard in detail — its mandatory fields, validation rules, error handling requirements, and ERP integration implications — is essential for every Belgian business planning its compliance implementation.
This guide explains what the Belgium Peppol BIS Billing standard requires, how it defines the structure and content of every compliant invoice, and how businesses can implement it successfully across their ERP or accounting environment. The Advintek Belgium e-invoicing platform provides certified Peppol BIS Billing 3.0 integration for Belgian businesses across all major ERP systems.
What is Peppol BIS Billing 3.0?
The European Standard for B2B Invoice Exchange
Belgium Peppol BIS Billing 3.0 is the European standard for structured business invoice exchange, adopted by Belgium as the mandatory format for all domestic B2B transactions. BIS stands for Business Interoperability Specification — the document profile that defines exactly how a structured invoice must be constructed and transmitted through the Peppol network. The 3.0 version is the current standard in use across all European Peppol markets.
UBL 2.1 as the Underlying Format
BIS Billing 3.0 is built on Universal Business Language (UBL) version 2.1 — an ISO/IEC-standardised XML document format for business documents. Every compliant invoice is a UBL 2.1 XML document structured according to the BIS Billing 3.0 profile’s specific requirements. This means the invoice data is machine-readable, schema-validated, and interoperable across all Peppol-connected systems regardless of the ERP platform the sender or recipient uses.
Why Belgium Chose BIS Billing 3.0
Belgium adopted Belgium Peppol BIS Billing 3.0 as its mandatory B2B invoice format to align with the pan-European Peppol framework, ensuring Belgian businesses can exchange structured invoices with trading partners across all EU member states that use the Peppol network. This alignment reduces the technical overhead for internationally operating Belgian businesses, which can use a single structured invoice format for both domestic Belgian and cross-border EU transactions.
Mandatory BIS 3.0 Invoice Fields Explained
Supplier Information Requirements
Every BIS Billing 3.0 invoice must include the supplier’s full legal name, the supplier’s VAT number in the required format (BE followed by ten digits), the supplier’s Belgian Enterprise Number (KBO/BCE), the supplier’s complete registered address, and the supplier’s Peppol Participant Identifier. Missing or incorrectly formatted supplier identification causes an Access Point validation failure.
Buyer Information Requirements
Buyer identification fields include the buyer’s full legal name, Belgian Enterprise Number, VAT number, and registered address. For buyers without a Belgian VAT number — for example, buyers subject to VAT exemption — alternative buyer identification codes must be used as specified in the BIS Billing 3.0 profile. Businesses using ERP platforms such as SAP Ariba Belgium or Microsoft Dynamics 365 Finance Belgium should verify that buyer master data configurations populate all required BIS 3.0 buyer fields correctly.
Invoice Header Fields
Belgium Peppol BIS Billing 3.0 mandates specific header-level fields: a unique invoice number within the supplier’s invoicing sequence, the invoice issue date in ISO 8601 format, the document currency code (typically EUR for Belgian transactions), the due date where payment terms are specified, and the reference to the purchase order number where applicable. Invoice number uniqueness must be maintained across all invoices transmitted through the system — duplicate invoice numbers cause rejection.
Line-Item Level Data Requirements
Each invoice line must include: a line identifier, a product or service description, the quantity and unit of measure, the unit price, any applicable discounts, the line-level VAT category code (S for standard rate, Z for zero rate, E for exempt), the applicable VAT rate percentage, and the calculated line total. VAT categorisation must be accurate at line level — a line categorised as zero-rated when it should be standard-rated constitutes a BIS 3.0 compliance failure.
Invoice Validation Rules
Arithmetic Validation
BIS Billing 3.0 specifies exact arithmetic rules for how line totals, VAT amounts, and invoice totals must be calculated and reconciled. The sum of all line totals (net of VAT) must equal the invoice’s total net amount. The sum of all line-level VAT amounts must equal the invoice’s total VAT amount. The total net amount plus total VAT must equal the total payable amount. These calculations must be internally consistent — any arithmetic discrepancy causes rejection.
VAT Number Format Validation
Peppol BIS Belgium is Billing 3.0 Access Point validation includes checking that Belgian VAT numbers conform to the required format: the prefix ‘BE’ followed by exactly ten digits. Businesses whose ERP systems store VAT numbers without the country prefix, with spaces, or with an incorrect digit count will experience systematic validation rejection until the master data format is corrected across all affected records.
Document Reference and Sequence Requirements
Credit notes under BIS Billing 3.0 must reference the original invoice number they are correcting. Debit notes require similar reference linkage. This document referencing requirement ensures that adjustments can be traced back to the original transaction in both parties’ accounting systems, supporting accurate VAT reporting and audit trail integrity.
Common BIS 3.0 Validation Errors
Missing or Incorrectly Formatted Mandatory Fields
The most common Belgium Peppol BIS Billing 3.0 error category is missing or incorrectly formatted mandatory fields — particularly VAT numbers without the ‘BE’ prefix, invoice dates in non-ISO formats, and line-level VAT category codes using invalid enumerated values. ERP systems must be configured to output all mandatory fields in their correct format before Peppol testing begins.
Arithmetic Inconsistencies
Arithmetic inconsistencies — where line totals, VAT amounts, and invoice totals do not reconcile according to BIS 3.0’s calculation rules — are the second most common rejection cause. These typically arise from rounding differences between line-level and invoice-level calculations, or from discount application logic that differs between the ERP system’s internal calculation and the BIS 3.0 arithmetic rules.
Incorrect VAT Categorisation
Applying the wrong VAT category code to invoice lines — for example, using the zero-rate code for a standard-rated supply — creates both a BIS 3.0 schema error and a potential VAT compliance issue. Businesses should complete a VAT treatment mapping exercise before ERP integration testing, confirming that each product or service category their system uses maps to the correct BIS 3.0 VAT category code.
ERP Integration Best Practices for Peppol Compliance
Field Mapping and Data Transformation
Implementing Belgium Peppol BIS Billing 3.0 in an ERP environment requires a detailed field mapping exercise that identifies which ERP data fields correspond to each BIS 3.0 mandatory field, how data transformations are required (for example, VAT number prefix addition), and which BIS 3.0 fields must be populated from sources outside the standard invoice data (such as buyer Peppol IDs stored in customer master records). Platforms including Oracle Belgium require specific Belgian tax configuration before Peppol integration testing can begin.
Australia E-Invoicing as a Comparable Reference
Businesses operating across multiple markets can reference the Australia e-Invoicing framework as a comparable Peppol BIS Billing 3.0 implementation — Australia uses the same underlying standard with country-specific extensions. Understanding cross-country BIS 3.0 implementation patterns helps international groups design more consistent multi-market ERP configurations.
Reviewing Peppol BIS Message Types
Belgium Peppol BIS Billing 3.0 covers the invoice and credit note document types. Businesses requiring other structured B2B document exchange — such as order confirmations, despatch advice, or catalogue updates — should review the full range of Peppol in Australia supported by their Access Point to understand which additional message types can be activated within the same Peppol network registration.
Preparing Your Business for Peppol BIS Billing 3.0 Compliance
• Complete a field mapping exercise between your ERP’s invoice data model and the BIS Billing 3.0 mandatory field requirements
• Audit and correct all customer and supplier VAT number formats before Peppol testing begins
• Configure VAT category code mapping between your ERP’s tax codes and BIS 3.0’s enumerated VAT category values
• Test at minimum: standard invoices, credit notes, multi-VAT-rate invoices, and zero-rated supply invoices in the Peppol sandbox
• Establish a monthly BIS 3.0 schema update monitoring process to catch mandatory changes before they cause live rejections
Conclusion
The Peppol BIS Billing 3.0 standard demands careful ERP configuration, accurate master data, and thorough pre-go-live testing. Businesses that invest in understanding the BIS Billing 3.0 standard’s requirements in detail — rather than assuming their existing invoicing setup will pass Access Point validation unchanged — consistently achieve faster, more stable Peppol go-lives with significantly lower first-month rejection rates. Advintek’s implementation team provides BIS Billing 3.0 configuration, testing, and validation support for Belgian businesses across all major ERP environments.
Frequently Asked Questions
Q1. What is Peppol BIS Billing 3.0 and why must Belgian businesses use it?
BIS Billing 3.0 is Belgium’s mandatory structured invoice format for B2B Peppol transactions — it defines exact XML structure, mandatory fields, and VAT categorisation rules.
Q2. What happens if a BIS Billing 3.0 invoice fails Access Point validation?
The invoice is returned to the sender with a specific error code. It must be corrected and retransmitted before it is considered legally issued.
Q3. Does BIS Billing 3.0 require separate line-level VAT categorisation?
Yes. Each invoice line must carry the correct VAT category code and applicable rate — invoice-level VAT totals must reconcile with all line-level amounts.
Q4. How does the BIS Billing 3.0 standard handle credit notes?
Credit notes under BIS Billing 3.0 must reference the original invoice number they correct, maintaining a traceable document chain in both parties’ systems.
Q5. How often is the BIS Billing 3.0 standard updated?
OpenPeppol releases BIS updates periodically. Certified Access Points and ERP connectors receive schema updates automatically — monitor release notes for impact.
Q6. Can a BIS Billing 3.0 invoice be corrected after it has been successfully transmitted?
Once transmitted and acknowledged, the original invoice cannot be retracted — a credit note referencing the original must be issued to correct it.
Source by:
Image by Gemini
