Last update: November 1, 2026

---

Slide deck

---

 

---

Click on the logo to visit the website

Belgium – E-Invoicing & E-Reporting Framework

Status as at 1 November 2026 – based exclusively on external sources (Revenue, Oireachtas, EU, Big 4 and specialist advisors).

1. Introduction & Country Context

1.1 Digitalisation journey

• Belgium built its e-invoicing infrastructure first in public procurement. Regional receiving mandates appeared from 2017, and federal B2G obligations were progressively expanded under the Public Procurement Act and the Royal Decree of 9 March 2022. Mercurius connects public entities to Peppol. The European Commission’s 2026 country sheet confirms mandatory B2G receipt and processing, with regional implementation in Flanders, Brussels and Wallonia (European Commission country sheet; Royal Decree of 9 March 2022).
• The next step was domestic B2B. The Act of 6 February 2024 amended the Belgian VAT Code and Income Tax Code 1992 and introduced the legal concept of a structured electronic invoice. The Act was published on 20 February 2024 and took effect for the mandate on 1 January 2026. The legal definition requires a structured form that enables automatic and electronic processing; an emailed PDF is therefore not sufficient for an in-scope transaction (Act of 6 February 2024; FPS Finance).
• Belgium is now preparing the reporting layer. On 18 July 2026, the federal Council of Ministers approved a pre-draft measure for near-real-time domestic invoice-data reporting from 1 January 2028, using a Peppol five-corner model. At the reporting cut-off date, this remained a proposal rather than enacted law, so the date, scope, fields and sanctions must still be monitored (2026 update timeline; 2028 proposal analysis).

1.2 Policy rationale

• The 2026 mandate is designed to standardise business data, reduce manual entry, automate accounts-payable and accounts-receivable processes, improve payment speed and reduce invoice-processing errors. The official Belgian programme presents Peppol as an interoperable network rather than a tax-authority clearance portal, allowing businesses to exchange machine-processable invoices directly through service providers (Belgian e-invoicing FAQ; FPS Finance).
• The tax-policy rationale becomes more prominent in the proposed 2028 stage. Near-real-time reporting would give FPS Finance transaction-level visibility, allow supplier and customer data to be reconciled and make the annual client listing redundant. This would move Belgium from digital document exchange to continuous transaction controls while preserving the decentralised Peppol architecture (five-corner analysis; 2028 proposal).

1.3 EU and international positioning

• Belgium is an early EU mover in mandatory domestic B2B e-invoicing, with a single go-live date and no turnover-based phasing. The country uses EN 16931 and Peppol BIS Billing 3.0, which supports technical interoperability with other Peppol jurisdictions. The European Commission’s October 2026 country sheet confirms that Belgium has both B2G and B2B mandates, but no B2C mandate and no live VAT real-time reporting system yet (European Commission; Belgian technical FAQ).
• Belgium’s proposed 2028 reporting layer anticipates the EU ViDA Digital Reporting Requirements that apply to intra-EU B2B transactions from 1 July 2030. Businesses can therefore view the 2026 Peppol implementation as the document-exchange foundation, the proposed 2028 regime as domestic CTC capability, and ViDA as the cross-border expansion (Directive (EU) 2025/516; five-corner model).

1.4 EU authorisation

• Belgium requested an Article 395 derogation from the VAT Directive on 6 October 2023. The final ViDA package, approved in March 2025, removed the need for Member States to obtain a separate derogation to mandate domestic structured e-invoicing, provided the European-standard framework is respected. Belgium therefore proceeded on the basis of the revised EU framework rather than relying on a separate country derogation decision (official B2B FAQ; Directive (EU) 2025/516).

2. Regulatory Framework

2.1 Primary legislation

• The central legal instrument is the Act of 6 February 2024 amending the VAT Code and Income Tax Code 1992 concerning compulsory electronic invoicing. Article 2 inserted the definition of a structured electronic invoice into Article 1(13) of the VAT Code. Article 3 introduced Article 53(2bis), requiring Belgian-established taxable persons, subject to stated exclusions, to issue structured invoices for specified domestic B2B supplies (Act of 6 February 2024).
• The Act also creates tax incentives in the Income Tax Code for qualifying e-invoicing software costs, illustrating that the policy combines compulsion with implementation support. The mandate does not replace substantive VAT rules on taxable amount, rates, chargeability or deduction; it changes the legally required invoice form and transmission model for in-scope transactions (Act of 6 February 2024; official B2B FAQ).

2.2 Implementing measures

• Royal Decree No. 1 and related VAT implementing decrees contain invoice-content and issuance rules. FPS Finance’s 2025 regulatory page lists amendments to Royal Decrees Nos. 1, 8 and 44 dealing with structured invoices and related adaptations for special regimes. Those measures must be read together with the 2024 Act and current administrative guidance (FPS Finance e-invoicing page; official programme FAQ).
• For B2G, the Royal Decree of 9 March 2022 established supplier e-invoicing modalities for public procurement and concessions. B2G rules therefore coexist with the broader 2026 VAT mandate. Where a public-sector invoice is also a domestic B2B VAT invoice, the public-procurement requirements, Mercurius routing and customer-specific references may apply in addition to normal VAT data (Royal Decree; B2G FAQ).

2.3 Administrative guidance

• The main practical source is the federal e-invoice portal, which separates general explanations, B2B, B2G, archiving, Peppol, developer/tax-specialist and future e-reporting questions. The FAQ was materially updated on 6 May 2026, including specialist questions on self-billing, credit notes, deduction, reverse-charge wording, wrong recipients and sanctions (FAQ index; specialist FAQ).
• FPS Finance also confirmed practical 2026 fallback treatment where a recipient cannot receive a structured invoice for technical reasons. In that exceptional situation the supplier may issue a conventional invoice, but the recipient remains obliged to remedy its inability without delay. The fallback is not a general opt-out and should be supported by evidence of the technical failure and remediation efforts (KPMG Belgium; official B2B FAQ).

2.4 Current legal status of e-reporting

• Belgium does not yet operate mandatory real-time invoice-data reporting. The live 2026 system is a four-corner exchange model and FPS Finance does not automatically receive each invoice. The proposed 2028 five-corner model was approved only as a pre-draft by the Council of Ministers on 18 July 2026. Parliament had not enacted the proposal by 1 November 2026 (European Commission; proposal analysis).
• Consequently, references to a 1 January 2028 go-live should be presented as a government target, not as final enacted law. The reporting data set, timing tolerance, buyer-side reporting mechanics, rejection handling and penalties remain subject to legislation and technical specifications (five-corner model; 2026 timeline).

3. Scope of the Mandate

3.1 Domestic B2B

• From 1 January 2026, structured invoicing applies to nearly all domestic supplies for which a Belgian-established VAT taxpayer must issue an invoice to another Belgian-established VAT taxpayer. Both supplier and recipient must be established in Belgium for VAT purposes, which includes a qualifying Belgian fixed establishment involved in the transaction. The rule covers goods and services, including domestic reverse-charge scenarios and credit notes connected with in-scope transactions (Act of 6 February 2024; official B2B FAQ).
• An emailed PDF, scanned paper document, Word file or image is not a structured invoice and cannot by itself satisfy the mandate. The legally relevant invoice is the structured message. A human-readable rendition can still be supplied for convenience, but it does not replace the XML and should be reconciled to avoid two documents being interpreted as separate invoices (FPS Finance; general electronic-invoicing FAQ).

3.2 Domestic B2G

• B2G e-invoicing predates the B2B mandate. Public administrations must receive and process EN 16931 invoices, and suppliers must use structured e-invoices for covered public contracts. The federal threshold was progressively reduced, with the framework generally covering public contracts of EUR 3,000 or more from March 2024, subject to procurement-specific exclusions and regional rules (European Commission; B2G FAQ).
• Mercurius acts as the public-sector interface to Peppol. Suppliers should not assume that a generic B2B invoice is sufficient: public customers may require purchase-order numbers, contract references, delivery references and third-party payment information. Those operational requirements should be captured in customer master data and order-to-cash controls (B2G FAQ; specialist FAQ).

3.3 Domestic B2C

• The mandate does not require structured invoices for supplies to private consumers. Paper and PDF invoices remain legally possible for B2C transactions, and Belgian registered cash-register or receipt obligations continue separately. A business with mixed B2B and B2C sales must therefore determine customer VAT status reliably rather than routing all documents through the same legal workflow (European Commission; official B2B FAQ).
• There is no announced Belgian B2C digital-receipt or QR-code mandate tied to the 2026 reform. Voluntary Peppol exchange may nevertheless be possible where the recipient has an addressable business identity, but consumer privacy and identity considerations make this distinct from the statutory B2B regime (general FAQ).

3.4 Cross-border flows

• Intra-EU supplies, intra-EU acquisitions, exports, imports and other transactions with a counterparty established outside Belgium are outside the domestic 2026 mandate. Existing invoice rules, customs evidence, Intrastat, VAT returns and EC Sales Listings continue to apply. Businesses may use Peppol voluntarily for cross-border exchange if both parties and their systems support it (official B2B FAQ; VATCalc analysis).
• From 1 July 2030, ViDA will require structured e-invoicing and digital reporting for specified intra-EU B2B transactions. Cross-border designs should therefore use EN 16931-compatible data and avoid a Belgium-only implementation that cannot be extended to ViDA (Directive (EU) 2025/516; Belgium programme).

3.5 Special transactions

• Self-billing remains permitted and, where the underlying transaction is in scope, the self-billed invoice must be structured. Credit notes issued in 2026 must generally use a structured format even when they correct a 2025 invoice, because the legal form is determined when the credit note is issued. Summary and simplified invoices remain possible if the substantive VAT conditions are met and the structured message can represent the required information (specialist FAQ; official B2B FAQ).
• Margin schemes, reverse charge, exempt supplies and zero-rated transactions require the appropriate Peppol VAT category and legal basis. The XML must also retain Belgian mandatory wording where required. The technical FAQ expressly addresses tax-category codes, VATEX exemption codes and extended reverse-charge clauses, meaning businesses should not rely only on a generic EN 16931 mapping (specialist FAQ).

3.6 Explicit exclusions

• The 2024 Act excludes taxpayers under the Article 56 flat-rate regime and bankrupt taxable persons for the activity for which bankruptcy was declared. Persons carrying out exclusively Article 44 exempt activities are generally outside the issuance obligation because no qualifying VAT invoice is required. Non-established taxable persons without a Belgian fixed establishment are outside the 2026 domestic mandate even if they hold a Belgian VAT number (Act of 6 February 2024; KPMG Belgium; VATCalc).
• The small-business VAT exemption is not a general exclusion. A Belgian-established small enterprise remains a taxable person and must exchange structured B2B invoices even though it does not charge VAT under the exemption scheme. The absence of a turnover threshold is particularly important for freelancers and sole traders (official B2B FAQ; SME/freelancer analysis).

4. Taxable Persons in Scope

4.1 Established Belgian taxpayers

• The obligation applies to companies, partnerships, associations, public bodies acting as taxable persons, sole traders and professionals that are established in Belgium and VAT registered. There is no general size, turnover, invoice-value or sector threshold. A business that falls under the small-enterprise exemption remains in scope for B2B exchange because the scheme exempts collection of VAT, not the entity’s taxable-person status (official B2B FAQ; freelancer guide).
• VAT groups require careful design. Transactions between members of a Belgian VAT group are normally outside VAT invoicing rules, while supplies by the VAT group to external Belgian customers remain subject to the mandate. Peppol participant identification, seller legal-entity data and the group’s VAT number must be aligned to avoid mismatches between the contractual seller and tax identity. Final group-specific examples should be checked against the specialist FAQ and provider guidance (specialist FAQ).

4.2 Fixed establishments and non-established registrations

• A foreign legal entity with a Belgian fixed establishment can be in scope where that establishment participates in the domestic supply. The analysis should follow VAT establishment principles and should not be based solely on the existence of a Belgian enterprise or VAT number. Master data should identify which establishment is the supplier or customer for each flow (Act of 6 February 2024; official B2B FAQ).
• A non-established business that merely has a Belgian VAT registration is excluded from the 2026 issue-and-receive obligation. FPS Finance confirmed this practical treatment for 1 January 2026. Such businesses may still exchange Peppol invoices voluntarily, and Belgian customers may prefer structured receipt, but the transaction should not be incorrectly described as mandated (KPMG Belgium; VATCalc).

4.3 Sector and status nuances

• Entities carrying out exclusively Article 44 exempt supplies, such as many financial, insurance, medical or educational activities, are generally excluded from issuance. Mixed taxpayers may nevertheless be in scope for taxable domestic activities and should route invoice types at transaction level. Agricultural, flat-rate and special regimes require specific analysis because legislation and implementing decrees contain tailored rules (Act of 6 February 2024; FPS regulatory information).
• Businesses in bankruptcy are excluded only for the activity for which bankruptcy has been declared. Liquidating companies, fiscal representatives, authorised representatives and third-party invoice issuers are not automatically excluded; the structured invoice must correctly identify the legal supplier, customer and representative where relevant (Act of 6 February 2024; specialist FAQ).

5. Implementation Timeline

5.1 Legislative and operational milestones

• Belgium requested an EU derogation on 6 October 2023. The Act was adopted on 6 February 2024 and published on 20 February 2024. B2G obligations had already been phased in, with the broad federal procurement tranche taking effect in March 2024. Preparatory guidance, provider lists and software onboarding continued throughout 2024 and 2025 (Act; European Commission).
• The domestic B2B mandate went live on 1 January 2026 for all in-scope businesses. There was no company-size phase-in. Administrative tolerance applied during the first quarter where taxpayers could evidence good-faith preparation, after which the progressive non-compliance penalty regime became operational from 1 April 2026 (2026 update timeline; Peppol Validator).

5.2 2026 enforcement period

• From April 2026 the mandate should be treated as fully enforceable. Businesses cannot rely on the transition tolerance as a continuing defence. A technical fallback remains available where a recipient is genuinely unable to receive, but this does not excuse the recipient from onboarding or the parties from documenting the failure and resolving it promptly (KPMG Belgium; official B2B FAQ).
• By mid-2026 Belgium had more than two million Peppol registrations according to market monitoring. High registration numbers do not by themselves prove that all ERP mappings, self-billing flows, credit notes, attachments and exception processes work correctly; post-go-live control testing remains necessary (2026 update timeline).

5.3 Future milestones

• The government target for domestic near-real-time reporting is 1 January 2028. The pre-draft proposal would add FPS Finance as a fifth corner and abolish the annual client listing for covered businesses. Because the legislative process was incomplete at 1 November 2026, organisations should prepare architecture and data-quality requirements but avoid treating unconfirmed fields and deadlines as final (2028 proposal; five-corner model).
• EU ViDA cross-border structured invoicing and DRR apply from 1 July 2030. Belgian businesses should build a plan that links 2026 domestic exchange, proposed 2028 domestic reporting and 2030 cross-border reporting, rather than operating three disconnected projects (Directive (EU) 2025/516; Belgium FAQ).

6. Operating Model

6.1 Four-corner model in 2026

• Belgium uses the decentralised Peppol four-corner model. The seller creates the invoice in its ERP or accounting system; the seller’s Peppol Access Point validates and routes it; the buyer’s Access Point receives it; and the buyer imports it into its system. FPS Finance is not in the invoice flow and does not clear or approve the invoice before issue (FPS Finance; five-corner explainer).
• The legal invoice is issued between the parties without a government fiscal stamp, clearance code or tax-authority UUID. Peppol transport evidence, message identifiers and acknowledgements are operational evidence, but businesses remain responsible for VAT correctness, invoice timing and record retention (general FAQ; specific FAQ).

6.2 End-to-end lifecycle

• Creation begins with tax determination, customer status, seller and buyer identifiers, line-level data, VAT categories, payment terms and references. The invoice is converted to Peppol BIS Billing 3.0 UBL, validated against EN 16931 and Peppol business rules and sent through the Access Point. Schema or rule failures should block transmission and trigger a controlled correction workflow (technical FAQ; PeppolCheck).
• The receiving Access Point resolves the recipient through Peppol’s directory services and delivers the message. The customer imports the invoice into accounts payable and can create a human-readable view. A business response can communicate processing status, but commercial acceptance and VAT validity remain governed by contract and tax law. The original structured file and associated evidence should be archived (general FAQ; specific FAQ).

6.3 Identification and access

• Belgian participants are normally registered using the CBE/KBO enterprise number under Peppol identifier scheme 0208. A VAT-number identifier under scheme 9925 may be used in specific situations. Participant registration and endpoint discovery should be managed by a certified provider, with controls to prevent duplicate registrations or routing to an obsolete endpoint (PeppolCheck guidance).
• Belgium does not require each business to obtain a tax-authority API certificate for invoices. Trust is established through Peppol PKI and certified Access Points. Businesses should nevertheless secure ERP credentials, provider interfaces and user permissions because Peppol network security does not prevent an authorised user from creating an incorrect invoice (general FAQ).

6.4 Contingency and fallback

• There is no clearance outage mode because the tax authority does not approve invoices. If a provider or recipient endpoint is temporarily unavailable, the seller should retain the invoice, monitor retry responses and issue through the structured channel when service resumes. The 2026 fallback allows a conventional invoice where the recipient cannot receive for technical reasons, but only as an exception (KPMG Belgium; official B2B FAQ).
• A robust contingency procedure should define evidence to retain, escalation ownership, how to prevent duplicate issue when Peppol becomes available, and whether a later structured replacement or credit/correction is necessary. Belgium’s FAQs warn about duplicate invoices and wrong recipients, making message-level traceability essential (specific FAQ).

6.5 Proposed five-corner model

• The proposed 2028 model retains the four business corners and adds FPS Finance as the fifth corner. A structured data extract would be sent close to invoice issuance, and market reporting indicates a dual-sided design in which issued and received data may be reconciled. This is reporting, not pre-clearance: the invoice would still flow directly between parties (five-corner model; 2028 proposal).
• Final routing, acknowledgements, correction events, timing tolerance and data fields are not enacted. Businesses should ensure that their provider can add reporting without changing core invoice creation and should establish reconciliation between Peppol messages, VAT ledgers and returns before near-real-time reporting becomes mandatory. The reviewed sources do not yet provide a final rule or technical specification as at 1 November 2026; this point should therefore be treated as open rather than inferred.

7. Acceptable E-Invoice Formats

7.1 Mandatory reference format

• Peppol BIS Billing 3.0 is the principle reference format and is based on UBL 2.1 and EN 16931. It contains a structured header, supplier and customer parties, invoice and tax dates, line items, quantities, prices, allowances and charges, VAT breakdown, totals, payment information and references. Belgian and Peppol validation rules apply in addition to pure XML schema validity (FPS Finance; European Commission).
• A PDF representation may accompany or be generated from the XML, but the PDF is not the legal structured invoice for an in-scope flow. Systems should designate one legal invoice and prevent the XML and rendering from acquiring different numbers, dates or amounts (general FAQ; official B2B FAQ).

7.2 Alternative formats and channels

• The law allows an alternative EN 16931-compliant structured format and transmission method where supplier and customer agree. The agreement can be contractually documented and must not undermine automatic processing. A proprietary EDI message is not automatically acceptable: the parties need to demonstrate semantic alignment with EN 16931 and preserve required Belgian VAT information (general FAQ; Act).
• Peppol remains the safest default because it provides open interoperability and endpoint discovery. Bilateral formats increase mapping, evidence and onboarding costs and may need an additional bridge when Belgium introduces e-reporting. Businesses should therefore reserve alternatives for established high-volume EDI relationships with clear governance (official programme; five-corner model).

7.3 Attachments and hybrid documents

• Peppol BIS supports attachments as embedded or referenced supporting documents, subject to size and provider controls. Purchase orders, delivery notes, timesheets and contract evidence may accompany the invoice. The official FAQ expects invoice attachments to travel through the same channel where they form part of the invoice package, while purely supplementary documents may require agreed handling (official B2B FAQ; specific FAQ).
• Attachments do not correct missing mandatory XML fields. A VAT clause, purchase-order reference or amount cannot be placed only in a PDF and omitted from the structured message if it is legally or operationally required. Mapping governance should classify every attachment and determine which data must also be represented structurally (specific FAQ).

8. Technical & Functional Requirements

8.1 Mandatory invoice information

• The structured invoice must contain the information required by Belgian VAT law: issue date, unique sequential number, supplier and customer identity and address, VAT numbers where required, description and quantity, supply or payment date where relevant, taxable amount, unit price, discounts, VAT rate and amount, exemption or reverse-charge ground and totals. Peppol business terms must be mapped to these legal requirements (Act; specialist FAQ).
• Conditional information includes purchase-order and contract references, payment account, delivery location, tax representative, self-billing marker, margin-scheme notation, reverse-charge text, legal form, enterprise court register/RPM information and liquidation status. Some are Belgian company-law requirements rather than EN 16931 core fields and may need appropriate extension or note fields (specialist FAQ).

8.2 Data validation

• Validation occurs at several levels: XML syntax, Peppol BIS rules, EN 16931 semantic rules, code-list values, numerical checks, VAT category consistency and Belgian legal requirements. An invoice can be valid XML but still legally deficient, for example where reverse-charge wording is incomplete or the seller identity does not match the VAT registration (specific FAQ; PeppolCheck).
• Controls should cover net-line arithmetic, allowances and charges, taxable bases by VAT category, VAT rounding, payable amount, currency, dates and references. Businesses should test positive and negative scenarios, not only a standard 21% domestic invoice. Particular attention is needed for mixed rates, exemptions, reverse charge, credit notes, summary invoices and self-billing (specific FAQ).

8.3 Digital signatures and integrity

• Belgium does not impose a qualified electronic signature on each Peppol invoice. Authenticity of origin, integrity of content and legibility must be guaranteed from issue through the end of retention. Peppol’s secure network and business controls can provide this assurance, but businesses remain responsible for the connection between commercial events and the invoice (official archiving/basic-principles page; general FAQ).
• An audit trail should connect the invoice to orders, contracts, dispatch or service evidence, approval, payment and accounting entry. If an alternative format or channel is used, equivalent integrity and authenticity evidence must be retained. A visual PDF alone is not sufficient evidence of unchanged structured content (general FAQ).

8.4 E-reporting specifications

• No mandatory e-reporting file or API applies in 2026. The proposed 2028 system is expected to transmit key invoice data through Peppol in near real time and to support supplier/customer reconciliation. There is no final published data model, reporting deadline, rejection code catalogue, outage protocol or effective-date legislation by the cut-off date (European Commission; 2028 proposal).
• The proposal would replace the annual client listing, not the periodic VAT return. Businesses should therefore expect e-reporting, VAT return and accounting-reconciliation obligations to coexist. Whether pre-filled VAT returns will later follow has not been announced. The reviewed sources do not yet provide a final rule or technical specification as at 1 November 2026; this point should therefore be treated as open rather than inferred.

9. Correction of Errors

9.1 Rejected or undelivered messages

• A technical rejection means the invoice did not complete the intended electronic exchange. The sender should correct schema, identifier or business-rule errors and retransmit under controlled procedures. Whether the same invoice number can be reused depends on whether the original was legally issued and received; systems should distinguish pre-delivery technical failures from post-delivery commercial or tax corrections (specific FAQ).
• Delivery to a wrong recipient is not solved by deleting the message. The sender should notify the unintended recipient, preserve evidence, correct master data and issue to the correct party. Where an invoice was legally issued, a structured credit note and replacement may be required. The FAQ specifically addresses misidentified recipients in both incoming and outgoing scenarios (specific FAQ).

9.2 Credit notes and corrective invoices

• Credit notes are exchanged through Peppol and should reference the original invoice, state the reason and reverse or adjust the relevant taxable base and VAT. A 2026 credit note relating to a 2025 paper/PDF invoice is generally a 2026 document and therefore must be structured when the parties and transaction are in scope (specific FAQ).
• If an invoice contains incorrect mandatory reverse-charge information, the recipient should request correction rather than silently amend its own copy. A corrected rendering attached to an unchanged XML does not correct the legal structured invoice. The supplier’s tax and message workflows must generate a formal structured correction (specific FAQ).

9.3 Reporting corrections

• Because the 2028 reporting law and technical specifications are not final, there is no confirmed correction-event process for reported invoice data. A workable system will need to distinguish invoice cancellation, credit note, data correction, duplicate and status change and reconcile all events to the VAT ledger. The reviewed sources do not yet provide a final rule or technical specification as at 1 November 2026; this point should therefore be treated as open rather than inferred.
• For 2026, VAT-return errors continue to be corrected under existing Belgian VAT procedures. The e-invoice itself does not amend the return, and correcting a return does not correct the invoice delivered to the customer. Both document and tax-reporting workflows must be completed where necessary.

10. Transmission & Workflow

10.1 Peppol and service providers

• Businesses normally connect through an accredited Peppol Access Point embedded in accounting software or supplied separately. The provider registers the participant, validates and routes messages and provides logs and support. Selecting a provider does not transfer the taxable person’s legal responsibility for invoice content, timing, archiving or VAT treatment (official Peppol FAQ; PeppolCheck).
• Provider due diligence should cover Belgian participant identifiers, BIS version management, service availability, retry logic, attachment limits, self-billing, business responses, archive export, GDPR, incident notification, portability and readiness for proposed 2028 reporting. Provider lock-in is a material risk if historical XML and evidence cannot be exported.

10.2 Mercurius and public procurement

• Mercurius is the Belgian public-sector receiving environment connected to Peppol. Suppliers typically send through their own Access Point rather than upload directly to a tax portal. Public-sector buyers may return status information and require procurement references that private buyers do not (B2G FAQ; European Commission).
• B2G teams should validate the customer in the Crossroads Bank for Enterprises and check whether it has the capacity ‘contracting authority’. Procurement scope and VAT scope are related but not identical; the public-procurement obligation can apply because of the contract even where a transaction would otherwise require separate VAT analysis (B2G FAQ).

10.3 Issuance and processing timing

• The e-invoicing reform does not replace existing Belgian VAT deadlines for issuing invoices. The structured invoice must be issued within the same substantive timeframe that would apply to a paper or electronic invoice. Peppol transmission should occur promptly enough that the invoice is legally issued and reaches the customer within that period (Act; official B2B FAQ).
• There is no T+1 or clearance deadline in 2026. The proposed 2028 regime uses the concept of near-real-time reporting, but no final number of hours or days has been enacted. Organisations should avoid setting contractual compliance representations based on unconfirmed market summaries. The reviewed sources do not yet provide a final rule or technical specification as at 1 November 2026; this point should therefore be treated as open rather than inferred.

11. Self-Billing

11.1 Legal permissibility

• Self-billing is permitted where the customer issues the invoice in the supplier’s name and on the supplier’s behalf under a prior agreement and an acceptance procedure. The 2026 mandate does not abolish self-billing. For an in-scope Belgian domestic transaction, the self-billed invoice must be structured and exchanged through the agreed compliant channel (official B2B FAQ; specialist FAQ).

11.2 Technical operation

• The structured message must identify the legal supplier and customer correctly and use the self-billing invoice type or marker supported by Peppol. The buyer’s Access Point sends the invoice, but tax responsibility and invoice data must reflect the supplier’s supply. ERP roles, number ranges and accounting interfaces should prevent the buyer being misidentified as the seller (specialist FAQ).
• Some software was not fully capable of self-billing at the start of 2026. The FAQ recognises implementation challenges but does not create a permanent exemption. Parties should document the self-billing agreement, provider limitations, remediation plan and temporary process, and should not treat a PDF as automatically compliant (official B2B FAQ).

11.3 Approval and corrections

• Supplier acceptance can be explicit or operated through an agreed procedure. Commercial disputes do not automatically invalidate the invoice, but errors must be corrected by structured credit notes or replacements. Self-billing partners should exchange status information and reconcile buyer-created documents with the supplier’s VAT ledger to avoid duplicate output VAT.
• For a foreign self-billing customer, the Belgian domestic mandate applies only if the customer-side establishment and supplier satisfy the domestic scope conditions. Cross-border self-billing remains subject to ordinary EU VAT rules and voluntary electronic exchange until ViDA broadens cross-border obligations.

12. Triangulation & Special Scenarios

12.1 Triangulation and chains

• EU triangulation and intra-EU chain transactions are outside the 2026 domestic mandate because at least one relevant supply is cross-border. Existing invoice statements, EC Sales Listings, Intrastat and evidence for the zero rate remain applicable. Peppol can be used voluntarily, but mandatory domestic routing should not be imposed merely because an intermediary has a Belgian VAT number (official B2B FAQ; Directive (EU) 2025/516).
• A chain may contain a separate domestic Belgian leg between two Belgian establishments. That leg can be in scope even though the wider commercial chain is international. Transaction mapping must therefore analyse each legal supply, supplier establishment, customer establishment and place of supply independently.

12.2 Reverse charge

• Domestic reverse-charge invoices remain in scope where a Belgian structured invoice is required. The invoice must carry the correct VAT category, the legally required reverse-charge reference and any detailed wording required by Royal Decree No. 1, including construction-sector wording where applicable. The customer should request correction if mandatory information is absent (specialist FAQ; VATCalc).
• Inbound cross-border reverse-charge invoices are outside the domestic mandate, although Belgian recipients may receive them through Peppol voluntarily. The buyer must still self-account in the VAT return. E-invoicing status does not determine the substantive reverse-charge treatment.

12.3 Zero-rated, exempt and margin-scheme supplies

• The XML should use the applicable EN 16931/Peppol VAT category and provide the exemption or zero-rate reason. Where VATEX does not contain an exact Belgian legal phrase, the official technical guidance explains how to use available codes and free-text legal references. Different VAT categories can appear on one invoice if validation rules are respected (specialist FAQ).
• For margin schemes, the invoice must not improperly disclose deductible VAT and must retain the statutory margin-scheme reference. Article 44 exempt entities and mixed taxpayers require transaction-level routing: exclusion of an entity from issuance should not be assumed from one exempt activity.

12.4 Discounts, deposits and reimbursements

• Allowances, charges and payment discounts must be represented using structured elements so that taxable bases and totals reconcile. Cash-discount terms should not be placed only in unstructured notes where they affect VAT calculation. Advance invoices, final invoices and credit notes should cross-reference each other to prevent double accounting.
• Pure disbursements outside the taxable amount, reimbursements that form part of consideration and compensation payments require substantive VAT analysis before mapping. The Peppol format does not decide whether an amount is consideration; the tax determination must drive the document type and VAT category.

13. Archiving & Retention

13.1 Retention period and original format

• Belgian invoice records are generally retained for ten years under current VAT record-keeping rules. The official portal states that archiving rules remain unchanged by the mandate, but the structured invoice must remain available, readable and capable of being produced during the retention period. Keeping only a PDF rendering risks losing the legal structured data (official B2B resources; programme articles).
• Businesses should retain the original XML, human-readable rendition where used, attachments forming part of the invoice, transmission evidence, acknowledgements, corrections and links to accounting entries. Retention policy should also cover archived Peppol messages when a service provider is changed.

13.2 Authenticity, integrity and readability

• Authenticity of origin, integrity of content and readability must be guaranteed from issue until the retention period ends. Belgium does not prescribe one technology; business controls, Peppol transport evidence, logs and secure storage can be combined. Any transformation must preserve the original and a verifiable relationship between XML and visual display (general FAQ; official FAQ).
• Access controls, immutable logging, version management, backup, disaster recovery and periodic retrieval testing are important. The ability to receive an invoice is not the same as the ability to reproduce it ten years later with code lists, attachments and audit context.

13.3 Storage location and audit access

• Electronic storage can be outsourced and may be located outside Belgium provided legal accessibility, integrity and prompt access for FPS Finance are maintained. GDPR, professional secrecy and cross-border transfer rules must also be considered. The taxpayer remains responsible when a provider stores the documents.
• During an audit, records must be supplied in a usable form and linked to books and VAT returns. A provider portal that permits viewing but not bulk export may be operationally inadequate. Contracts should guarantee export in original format throughout the retention period and on termination.

14. Penalties & Enforcement

14.1 Administrative tolerance

• FPS Finance applied a practical tolerance from 1 January through 31 March 2026 for businesses making demonstrable good-faith efforts. That tolerance ended on 31 March 2026. It should not be described as a continuing statutory grace period, and newly created businesses do not receive a separate three-month exemption (2026 update timeline; Peppol Validator).

14.2 Specific non-compliance fines

• The published progressive penalty framework is EUR 1,500 for a first infringement, EUR 3,000 for a second infringement and EUR 5,000 for subsequent infringement. Market summaries describe the escalation as applying where the business remains unable to issue or receive compliant structured invoices, with repeat penalties subject to the applicable infringement interval (Peppol Validator; 2026 mandate guide).
• The exact assessment depends on facts and official penalty provisions. In addition to fixed fines, an invoice that does not satisfy legal requirements can create input-VAT deduction disputes, delayed payment, commercial rejection and audit exposure. Deliberate false invoicing or fraud is subject to broader VAT and criminal sanctions, not merely the e-invoicing fine.

14.3 Enforcement risks by failure type

• Failure to activate a receiving endpoint, persistent use of PDFs, incorrect participant identification and inability to send structured credit notes can each evidence non-compliance. A temporary documented network outage is materially different from a business choosing not to onboard. The fallback cannot be used as a standard operating model (KPMG Belgium; official B2B FAQ).
• Incorrect VAT amounts, missing reverse-charge wording, duplicate issue and wrong-recipient transmission remain invoice-quality failures even when the XML passes Peppol validation. Enforcement readiness therefore requires both connectivity controls and substantive VAT controls (specialist FAQ).

14.4 E-reporting penalties

• No final 2028 e-reporting penalty regime was enacted at the cut-off date. It is premature to assume that current e-invoicing fines will apply unchanged to late, missing or inconsistent reporting. Businesses should track the parliamentary text and implementing rules. The reviewed sources do not yet provide a final rule or technical specification as at 1 November 2026; this point should therefore be treated as open rather than inferred.

15. Pre-Filled VAT Returns

15.1 Current position

• Belgium does not currently provide a fully pre-filled periodic VAT return based on Peppol invoices. The 2026 four-corner model does not send invoice data to FPS Finance, so it cannot by itself populate return boxes. Taxpayers continue to prepare and submit periodic returns using accounting records and existing electronic filing channels (European Commission; five-corner explainer).

15.2 Future potential

• The proposed 2028 five-corner reporting system would create transaction-level data that could support risk analysis, reconciliation and eventual pre-filling. The announced simplification is abolition of the annual client listing; no official commitment has been made to pre-fill specific periodic VAT-return fields or to shift legal responsibility from the taxpayer (2028 proposal; 2026 timeline).
• Even if administrative pre-filling is introduced later, businesses would need to reconcile tax-authority data to general ledger, corrections, imports, self-assessed VAT and non-invoice adjustments. Peppol data should be treated as one source of return evidence rather than a complete VAT determination system.

16. ViDA Readiness

16.1 Alignment

• Belgium’s use of EN 16931, Peppol BIS and structured credit notes is strongly aligned with ViDA’s objective of interoperable digital invoices. The proposed domestic five-corner model also anticipates transaction-level reporting. Belgium is therefore ahead in infrastructure, though final ViDA cross-border data and timing rules still require separate implementation (European Commission; Directive (EU) 2025/516).

16.2 Gaps to address

• The 2026 mandate covers domestic established-to-established transactions, while ViDA applies to specified intra-EU B2B flows from 1 July 2030. Businesses must add cross-border VAT-rule determination, intra-EU identifiers, DRR timing, correction events and Member State interoperability. A domestic Peppol connection alone is not complete ViDA compliance (Directive (EU) 2025/516).
• Belgium’s proposed reporting scheme must ultimately coexist with EU reporting and avoid duplicate transmission. The final domestic reporting law should therefore be reviewed for data reuse, buyer-side reporting, how domestic and cross-border legs are distinguished and whether current periodic statements are removed.

16.3 Business implications

• A multinational should establish a common invoice data model with country extensions rather than separate Belgian mappings. Master-data governance, legal-entity and establishment logic, tax-code mapping, message monitoring and archival controls can then be reused for France, Germany, Ireland and ViDA.
• Early investment in high-quality structured data delivers operational benefits before 2030 and reduces the risk that the proposed 2028 layer becomes an emergency project. Provider contracts should include roadmap commitments for both Belgian CTC and ViDA.

17. Impact on SMEs and Startups

17.1 Scope and onboarding burden

• There is no turnover threshold or later date for SMEs, freelancers or startups. Belgian-established persons under the small-business exemption must comply for domestic B2B invoices. This places small businesses on the same legal timeline as large enterprises, although invoice volumes and system complexity are lower (official B2B FAQ; freelancer guide).
• The principal burden is selecting software, activating Peppol, cleansing enterprise and VAT identifiers, learning exception handling and ensuring that accountants can access both sales and purchase documents. Businesses that previously issued Word or PDF invoices face a larger process change than cloud-accounting users.

17.2 Support and incentives

• The federal portal publishes a software-solution list, FAQs, training calendar and a scope tool. The government does not operate a universal free invoice-creation portal equivalent to some clearance jurisdictions; businesses normally obtain connectivity through commercial accounting or invoicing software (official B2B FAQ; FPS Finance).
• Tax incentives include increased deduction for qualifying digital investments and a temporary enhanced cost deduction for e-invoicing subscription expenses, subject to statutory conditions. SMEs should verify eligibility, period and interaction with accounting treatment rather than assuming all provider charges qualify (Act of 6 February 2024; official B2B FAQ).

17.3 Costs and operational benefits

• One-time costs include setup, data migration, process redesign, staff training and customer/supplier communication. Ongoing costs include software subscriptions, Access Point services, archive storage and support. Complex EDI, self-billing or high-volume integrations require more investment than a standard cloud package.
• Benefits include reduced re-keying, fewer duplicate invoices, faster approval, improved cash forecasting and more reliable data for accountants. Benefits are not automatic: poor master data and weak exception processes can shift manual work from data entry to rejection handling (general FAQ; official programme).

17.4 Cash flow and market effects

• Structured delivery can shorten processing and dispute cycles, but it does not change contractual payment terms or create automatic acceptance. SMEs should monitor delivered, rejected and approved statuses and avoid assuming that successful Peppol transmission guarantees payment.
• The mandate accelerates consolidation around software vendors and Access Points. SMEs benefit from embedded connectivity but may face switching costs. Portability of participants, historical XML and accounting data should be evaluated when selecting a provider.

17.5 Readiness for 2028

• SMEs already connected to Peppol have the basic transport layer needed for proposed 2028 reporting, but invoice completeness and accounting reconciliation become more important when data is visible to FPS Finance. Businesses should ask providers whether their product roadmap includes five-corner reporting and automated correction flows (five-corner model; 2028 proposal).

18. Official References & Sources

18.1 Official Belgian sources

• Federal e-invoice portal – FPS Finance partner page, FAQ index, B2B scope FAQ, specialist technical and tax FAQ, B2G FAQ and FPS Finance VAT e-invoicing page. These should be treated as the primary operational guidance and checked for updates before implementation decisions.

18.2 Legislation

• Act of 6 February 2024, published 20 February 2024, is the core B2B legal basis. Royal Decree of 9 March 2022 addresses B2G supplier obligations. The OpenJustice links reproduce Belgian Official Gazette content; for formal legal reliance, users should follow the embedded eJustice official link.

18.3 EU sources

• European Commission 2026 Belgium country sheet provides a current comparison of B2G, B2B, standards, governance and reporting status. Directive (EU) 2025/516 contains the ViDA amendments relevant to domestic mandates and 2030 cross-border DRR.

18.4 Advisory and technology sources

• KPMG Belgium covers the 2026 scope and technical fallback. 2026 mandate guide, 2026 update timeline, five-corner explainer, VATCalc, Peppol Validator and PeppolCheck provide market interpretation. Advisor statements on 2028 should be read with the caveat that the proposal was not enacted at the cut-off date.

18.5 Source limitations

• The analysis is current to 1 November 2026. The official FAQ is dynamic and may change without a consolidated version history. Detailed 2028 reporting legislation and specifications were unavailable, so no reporting fields, reporting deadline or penalty amounts are presented as final. Where official English guidance is abbreviated, the Dutch/French official text and enacted law prevail.

19. Summary & Key Takeaways

19.1 Scope and status

• Belgium’s domestic B2B mandate has been live since 1 January 2026 and fully enforced since 1 April 2026. It covers nearly all invoices between Belgian-established VAT taxpayers, including small businesses in the exemption scheme, and requires both issue and receipt. B2C, cross-border transactions and non-established registrations without a Belgian fixed establishment are outside the mandate (official B2B FAQ; KPMG Belgium).

19.2 Technology and workflow

• Peppol BIS Billing 3.0 through the four-corner Peppol network is the default. Alternative EN 16931-compliant arrangements are possible by agreement. The system is not clearance: FPS Finance does not approve invoices or assign a fiscal code. The original XML, not a PDF, is the legally relevant structured invoice (FPS Finance; general FAQ).

19.3 Main compliance risks

• Key risks are incorrect scope determination, incomplete Peppol onboarding, untested self-billing and credit notes, missing Belgian legal text, wrong participant identifiers, weak fallback evidence and failure to retain native XML. Progressive fixed penalties of EUR 1,500, EUR 3,000 and EUR 5,000 apply to non-compliance, alongside broader VAT and deduction risks (Peppol Validator; specialist FAQ).

19.4 E-reporting and ViDA

• Near-real-time domestic reporting from 1 January 2028 is a government proposal based on a Peppol five-corner model and intended to replace the annual client listing. It was not enacted by 1 November 2026. ViDA cross-border invoicing and DRR apply from 1 July 2030 (2028 proposal; Directive (EU) 2025/516).

19.5 Recommended actions

Businesses should complete a transaction-level scope matrix; confirm establishment and VAT status; validate seller, customer and Peppol identifiers; test standard invoices, credit notes, self-billing, reverse charge, exemptions and attachments; implement message monitoring and fallback controls; retain original XML and logs; and reconcile invoice data to VAT ledgers. Provider roadmaps should be reviewed for the proposed 2028 five-corner model and ViDA 203

---

• See also
  • E-Invoicing/Real Time Reporting – What can you find on VATupdate.com
  • Worldwide Upcoming E-Invoicing mandates, implementations and changes – Chronological
  • Collection of E-Invoicing Guides – Worldwide – VATupdate
  • Briefing / Comprehensive Guides (incl. podcasts)

• Join the Linkedin Group on Global E-Invoicing/E-Reporting/SAF-T Developments, click HERE

---

---

---