Peppol or EDI invoicing in Belgium: what is compliant from 2026
Is an EDIFACT, AS2 or portal invoice flow still valid for Belgian B2B in 2026? Which EDI formats qualify, how EDI and Peppol coexist, and how to avoid duplicates.
- Updated
- Content owner
- Customer education team
- For
- Finance and accounts-receivable teams of suppliers to large buyers · IT and ERP owners who run EDI links · Accountants advising Belgian businesses
At a glance
Since 1 January 2026, an invoice between businesses established in Belgium must be a structured invoice under EN 16931, by default Peppol BIS over the Peppol network. An EDI link may carry it instead only by agreement and only as an EN 16931 invoice in UBL or CII, never as a classic EDIFACT message, and you must still be able to send and receive on Peppol.
Before you begin
- A list of your business customers with their VAT numbers and the channel each one uses today (Peppol, EDI, portal, email)
- The EDI specifications or supplier handbook your large customers sent you
- To send from OrdoGrid: a company with a BE VAT number and a signed Autorisation Peppol (Peppol authorisation)
What you will achieve
- Classify each EDI or portal flow as compliant, compliant by agreement, or not compliant
- Decide per customer which channel carries the legal invoice
- Run EDI and Peppol side by side without duplicate invoices
- Keep the agreements and evidence an audit will ask for
On this page
Since 1 January 2026, an invoice between two businesses established in Belgium must be a structured electronic invoice that follows the European standard EN 16931. The legal default is Peppol BIS (UBL) sent over the Peppol network. An existing EDI link can carry these invoices instead only if both parties agree and the message is an EN 16931 invoice in UBL 2.1 or UN/CEFACT CII; a classic EDIFACT invoice message does not qualify. Whatever you agree, your business must still be able to send and receive Peppol BIS.
This guide is for suppliers whose large customers run EDI, VAN or portal flows, and for the finance and IT teams that maintain them. It helps you classify each flow, pick the legal channel per customer and run EDI and Peppol together without duplicate invoices. Who falls under the obligation is explained in the Belgian B2B e-invoicing obligation; the fields inside a structured invoice in EN 16931 and UBL.
The rule: what an EDI link may carry from 2026
What the law requires. A taxable person established in Belgium must issue a structured electronic invoice for supplies to a taxable customer that is established in Belgium and must give the supplier its Belgian VAT number (art. 53 §2bis VAT Code). Royal Decree no. 1 sets the format and the channel:
| Provision | What it says |
|---|---|
| Art. 13ter, first paragraph | The invoice follows EN 16931 in Peppol BIS (UBL version) and travels over the Peppol network |
| Art. 13ter, second paragraph | Another format or channel is allowed only by agreement between the parties, and the format must still comply with EN 16931 and with the EU list of syntaxes under Directive 2014/55/EU |
| Art. 13quater | A business that agreed another format must still have the technical means to issue and receive Peppol BIS |
FPS Finance (the federal tax administration) recommends making any agreement on another format or channel explicit and written, because an implicit agreement can only be inferred from conduct and is hard to prove (FAQ on electronic invoicing, question 13). Neither side can impose its preference: a customer cannot require you to use its portal without your clear written consent (B2B FAQ, question 18), and a customer registered on Peppol has thereby agreed to receive structured invoices there (question 9).
- EU syntax list
- The list, adopted under Directive 2014/55/EU, of the two syntaxes in which an EN 16931 invoice may be expressed: UBL 2.1 invoice and credit note messages, and the UN/CEFACT Cross Industry Invoice (CII) D16B. The European Commission states that UN/EDIFACT is not on the list.
The standard does have a technical binding for EDIFACT (CEN/TS 16931-3-4, INVOIC D16B). Because EDIFACT is not on the syntax list, Belgian law does not accept it, even when it is fully mapped to EN 16931 (European Commission, required syntaxes).
- Classic EDI
- Electronic data interchange set up per trading relationship: a message format (often EDIFACT, such as the EANCOM subset used in retail, or the buyer's own XML) sent over a channel built for that partner, such as a VAN (value-added network), AS2, SFTP or a supplier portal.
Which flows are valid for an in-scope Belgian B2B invoice
| Flow | Valid as the invoice? | Condition |
|---|---|---|
| Peppol BIS Billing 3.0 (UBL) over Peppol | Yes, the legal default | Both parties reachable on Peppol |
| EDIFACT INVOIC (D96A, EANCOM or any other subset) over a VAN or AS2 | No | Not on the EU syntax list; an agreement does not cure it |
| EDIFACT mapped to EN 16931 (CEN/TS 16931-3-4) | No | Same reason: EDIFACT is not on the syntax list |
| UBL 2.1 or CII D16B invoice conforming to EN 16931, over AS2, SFTP or a VAN | Yes, by agreement | Written agreement recommended; both parties keep the means to send and receive Peppol BIS |
| The buyer's own XML, CSV or flat-file format | No | Not an EN 16931 syntax |
| PDF uploaded to a buyer portal or emailed | No | A PDF is not structured, whatever the channel |
| Invoice keyed into a buyer portal that generates the structured file | Only by agreement | Your written consent, an EN 16931 file in UBL or CII, and a copy you can download and keep |
| Buyer portal or platform that receives through Peppol | Yes | This is a Peppol send: address the buyer's Peppol identifier |
Outside the Belgian obligation (customers established abroad, private individuals), an EDIFACT invoice remains an ordinary electronic invoice that needs the customer's agreement. Messages that are not invoices, such as orders (ORDERS) and despatch advices (DESADV), are not covered by the obligation and can stay on EDI.
Peppol and classic EDI compared
Peppol is itself a form of EDI: structured data exchanged between systems. The difference is that the network, the identifiers and the rulebook are shared, so one connection reaches every registered business. For the network basics, see Peppol access points.
| Peppol | Classic EDI | |
|---|---|---|
| Network model | Open four-corner network: you and your customer each use your own certified service provider (access point) | Point-to-point link or VAN hub, set up per trading partner |
| Addressing | Every Belgian participant must be registered at least under 0208: plus its 10-digit enterprise number (KBO/BCE, the Crossroads Bank for Enterprises); the sending access point finds the receiver through the SML and SMP registries | Partner identifiers, often GS1 GLNs, exchanged when the link is set up |
| Transport | AS4 only (Peppol AS4 profile 2.0); Peppol's AS2 profiles were removed on 6 September 2023 | AS2, VAN mailbox, SFTP, portal; sometimes AS4 |
| Invoice format | Peppol BIS Billing 3.0, a profile of EN 16931; UBL mandatory, CII optional for receivers; release 3.0.21 mandatory since 17 August 2026 | EDIFACT subsets, proprietary XML, sometimes UBL or CII |
| Rulebook | One shared set of rules and code lists; Belgium adds no national rules | A message implementation guide per partner |
| New customer | No set-up if it receives on Peppol: look it up and send | Usually a mapping, a test cycle and a go-live per partner |
| Beyond invoices | Peppol BIS also covers ordering, despatch advice, catalogues and invoice responses | Orders, despatch advices and many sector messages |
| Status for in-scope Belgian invoices | The legal default | Only as UBL or CII under EN 16931, by agreement |
What ‘certified’ means for a Peppol access point
In Belgium a Peppol service provider joins OpenPeppol, signs the Peppol service provider agreement with the Belgian Peppol Authority, passes conformance tests with test certificates, receives production certificates and is then added to OpenPeppol's and the Authority's lists of certified providers (Belgian Peppol Authority). FPS BOSA has held that role since 2016; FPS Finance takes it over from 2027. To check a provider, including an EDI provider that also offers Peppol, look for it on OpenPeppol's list of certified service providers, which shows each provider's Peppol Authority. OpenPeppol also requires its service providers to hold ISO/IEC 27001 or an approved equivalent by 1 October 2027; that obligation is on the provider, not on you.
Costs to compare
| Cost item | Peppol | Classic EDI |
|---|---|---|
| Set-up | Often part of an invoicing software or provider subscription | Mapping and testing per partner, often billed as a project |
| Each new customer | Nothing extra if it receives on Peppol | Often a new mapping and test cycle |
| Running costs | Subscription or per-document fees | VAN mailbox and message fees, AS2 certificate renewals |
| Rule changes | Handled by your provider with each BIS release | Partner-specific changes |
Ask for quotes line by line, because prices vary by provider and volume. Small companies and self-employed natural persons can deduct 120% of their invoicing-software costs for issuing, sending and receiving structured invoices, such as subscriptions and implementation advice but not depreciation, for taxable periods 2024 to 2027 (Law of 6 February 2024); ask your accountant whether a given EDI or VAN fee qualifies.
Test an existing EDI invoice flow in six questions
Run this check for each customer that receives your invoices outside Peppol.
- Which syntax is the invoice message? EDIFACT, a proprietary XML or a flat file: not compliant for an in-scope customer, so go to the channel decision below. UBL 2.1 or CII D16B: continue.
- Does it declare and pass EN 16931? The specification identifier (BT-24) should start with
urn:cen.eu:en16931:2017, and your provider should show a clean validation report against the official EN 16931 rules for real invoices and credit notes. - Is there a written agreement naming the format, the channel, the document types (invoices and credit notes) and the start date?
- Can both parties still issue and receive Peppol BIS? Look up your own registration and the customer's on lookup.peppol.org by entering
0208:followed by the enterprise number. The lookup shows the ability to receive, not to send: for sending, ask the customer (or your own provider) to confirm in writing. - Do attachments travel inside the message? Supporting documents legally form part of the invoice and must use the same channel, not a separate email (B2B FAQ, questions 19 to 22).
- Is it the only channel for those invoices? We recommend one channel: a second copy as a Peppol invoice, PDF or portal upload is not forbidden (a PDF copy is optional), but Peppol cannot detect duplicates and the Belgian Peppol service providers' forum advises against dual sending.
A flow that passes all six questions can stay. Questions 1, 2, 4 and 5 are legal conditions: any ‘no’ means moving that customer to Peppol or fixing the flow before the next invoice. Questions 3 and 6 are our recommendations: an agreement can legally be implicit, but a written one makes the flow provable, and a single channel prevents double booking.
Choose the channel per customer
| Your situation | What applies | What to do |
|---|---|---|
| Belgian business customers, none asks for EDI | Peppol BIS is the default | Send and receive on Peppol; no EDI needed |
| A Belgian customer asks for EDIFACT invoices, for example in its supplier handbook | EDIFACT does not meet art. 13ter | Propose sending Peppol BIS to its Peppol identifier; keep orders and despatch advices on EDI if both sides want |
| The customer insists on its own EDI channel | Allowed only with an EN 16931 invoice in UBL or CII, by agreement | Agree in writing on UBL 2.1 or CII D16B over that channel; both of you stay Peppol-capable |
| The customer asks you to upload invoices to its portal | It cannot impose the portal; a PDF upload is not structured | Send on Peppol. If you accept a portal that generates an EN 16931 file in UBL or CII, confirm in writing and keep a copy of each file; a PDF upload stays non-compliant even with your consent |
| The customer cannot receive on Peppol at all | Fallback: you issue an ordinary invoice in another form; the customer breaches its own duty to receive | Follow client not on Peppol and keep a dated lookup |
| Customer established abroad, without a Belgian seat or fixed establishment | Outside the Belgian obligation; intra-EU e-invoicing follows under ViDA from 1 July 2030 | EDI, Peppol or PDF as agreed; check the rules of its country |
| Belgian public authority | Public-procurement rules; public buyers receive over Peppol through Mercurius | Send on Peppol |
| Your ERP only produces EDIFACT | You must still issue an EN 16931 invoice | Use a provider that converts the output into Peppol BIS and sends it as your access point; keep the converted file as the invoice |
Run EDI and Peppol side by side without double invoicing
What we recommend.
- Record one legal invoice channel per customer and note it in the customer file (in OrdoGrid, the client's Notes field).
- Never send the same invoice through two channels. Peppol cannot detect duplicates (FPS specific FAQ, question 4), and on 8 September 2026 the Belgian Peppol service providers' forum recommended sending only via Peppol when the recipient receives there.
- Send a credit note in the same format as the invoice it corrects, and through the same channel. For a structured invoice the same format is a legal requirement (art. 53 §2bis, al. 3 VAT Code) and the same channel is our recommendation; a credit note for an invoice issued before 2026 has no format requirement.
- Keep Peppol receiving active even if all your customers use EDI: your Belgian suppliers will send their invoices to your Peppol registration.
- If some invoices are issued from another system, give them their own number series. Numbering may be based on one or several series, each sequential and unique (art. 5 §1, 1° Royal Decree no. 1).
In OrdoGrid: Peppol, not EDI
What OrdoGrid does. OrdoGrid connects to Peppol through a certified access point. It does not offer EDIFACT, AS2, VAN connections or uploads to buyer portals: it produces the UBL file only for a Peppol send, and its emails carry the PDF without XML. Peppol sending requires a company with a BE VAT number and a signed Autorisation Peppol (Peppol authorisation). Many labels stay French in every interface language. The complete first send is in send your first Peppol invoice.
To check whether a customer that asks for EDI can receive on Peppol, and to send it the invoice:
- In Clients, open or create the client with its N° de TVA (VAT number). If the customer requires a purchase order, tick Exiger un bon de commande pour les factures (require a purchase order for invoices). There is no Peppol ID field: OrdoGrid finds the customer from its VAT number when you send.
- Create the invoice with Nouvelle facture (new invoice) and enter the order number in N° bon de commande (purchase-order number). OrdoGrid sends it as the buyer reference (BT-10); Peppol BIS requires a buyer reference or an order reference on every invoice (rule PEPPOL-EN16931-R003). OrdoGrid has no separate order-reference field (BT-13): if the buyer matches invoices to orders only on BT-13, agree with it that it reads BT-10.
- Click Envoyer (send). During Vérification de l'éligibilité... (checking eligibility) OrdoGrid looks the customer up; when it is found, Envoi électronique via Peppol (electronic sending via Peppol) is ticked.
- Untick Email unless the customer asked for a copy, then click Sauvegarder & Envoyer (Save & Send).
- Follow the send in Peppol → Outbox. Traité (processed) means network delivery, not acceptance. If the customer sends an Invoice Response and OrdoGrid holds your reception, it appears with the invoice.
If the window shows Peppol — ignoré (skipped) with Le client n'est pas enregistré sur le réseau Peppol (client not registered on Peppol), check the VAT number with the customer and look up 0208: plus its enterprise number on lookup.peppol.org before you use the fallback.
Receiving when your EDI provider has already registered you. Reception of a Peppol document type can sit with only one provider at a time. If your EDI or ERP provider has registered you, Réception Peppol (Peppol reception) shows Déjà inscrit sur le réseau Peppol (already registered on Peppol): choose Continuer en envoi seul (continue send-only) and keep receiving there. In send-only mode, the Invoice Responses that customers send about your OrdoGrid invoices are also routed to that registration, so they arrive at your other provider, not in OrdoGrid: check them there. To move reception to OrdoGrid, the current provider must deregister you first, because OrdoGrid does not support the Peppol migration-key procedure. When you click Activer la réception (activate reception), OrdoGrid registers 0208: plus your enterprise number, including the self-billing document types, and Peppol → Statut shows your Identifiant Peppol (Peppol identifier).
What to do for an agreed EDI channel. If you and a customer agree on UBL or CII over its EDI channel, OrdoGrid cannot deliver it. Issue that customer's invoices from your EDI provider's tool, in a separate number series, and do not also send them from OrdoGrid.
Worked example: a retailer that asks for EANCOM invoices
Cartonnages Lemaire SRL, a packaging maker in Mouscron, invoices 38 Belgian business customers on Peppol from OrdoGrid. In September 2026 it wins a contract with Bouwmarkt Verhaegen NV, a DIY chain in Mechelen. Verhaegen's supplier handbook, written in 2019, says orders go out as EANCOM ORDERS messages and invoices must come back as EANCOM INVOIC messages (EDIFACT, directory D96A), both over its VAN.
- Check the buyer. Lemaire's office manager enters
0208:and Verhaegen's enterprise number on lookup.peppol.org and finds it registered to receive Peppol BIS Billing invoices and credit notes. She saves a dated screenshot. - Classify the flow. EANCOM INVOIC is EDIFACT, so it cannot be the legal invoice for this Belgian customer, with or without an agreement. Verhaegen's accounts payable confirms by email that invoices and credit notes will come on Peppol only, from the first invoice, with no PDF or EDIFACT copy. Orders keep arriving over the VAN; the law does not cover them.
- Send the invoice. The first delivery is invoiced as F-2026-0318, dated 5 October 2026 and due 4 November 2026, with Verhaegen's order number 4500098812 in N° bon de commande.
| Line | Quantity × unit price | Net | VAT 21% |
|---|---|---|---|
| Double-wall shipping boxes | 2,400 × €1.35 | €3,240.00 | €680.40 |
| Display trays | 600 × €4.20 | €2,520.00 | €529.20 |
| Total | €5,760.00 | €1,209.60 |
The total including VAT, and the amount due, is €6,969.60. EN 16931 computes VAT on the 21% category total: 21% × €5,760.00 = €1,209.60. OrdoGrid validates the file before delivery, so €5,760.00 + €1,209.60 must equal €6,969.60 exactly. A few minutes after Sauvegarder & Envoyer, the Peppol → Outbox row shows Traité. OrdoGrid sends 4500098812 as the buyer reference (BT-10); it has no separate order-reference field (BT-13). Before the first send, Verhaegen's accounts payable confirmed to Lemaire's office manager that it matches Peppol invoices to orders on BT-10, so the invoice is matched to its EDI order without retyping.
- Correct with a credit note. On 9 October Verhaegen reports 100 display trays damaged in transit. Lemaire selects F-2026-0318 in the Factures (invoices) list and clicks Note de crédit (credit note). OrdoGrid prefills every line of the invoice, so the shipping-box line is deleted and the display-tray quantity is set to 100. Credit note NC-2026-0027 covers 100 × €4.20 = €420.00 plus €88.20 VAT, €508.20 in total, and refers to F-2026-0318. Lemaire's accountant confirms that art. 79 of the VAT Code applies, and OrdoGrid adds the mention ‘T.V.A. à reverser à l'Etat dans la mesure où elle a été initialement déduite’ (Royal Decree no. 4, art. 4 §1) itself, because the credit note refunds Belgian VAT to a customer with a VAT number. The credit note goes on Peppol like the invoice. The amount outstanding on F-2026-0318 falls to €6,969.60 − €508.20 = €6,461.40.
- The variant. Had Verhaegen insisted on its VAN, the only compliant option would have been a written agreement on an EN 16931 invoice in UBL 2.1 or CII D16B over that VAN, with both companies still able to use Peppol. Lemaire would then have issued Verhaegen's invoices from its EDI provider's tool in a separate series, for example V-2026-0001, and not from OrdoGrid.
Edge cases and common mistakes
| Situation | Correct action |
|---|---|
| ‘We already do EDI with our biggest customer, so we are covered’ | An EDI link covers one customer at most, and only with UBL or CII under EN 16931. You must still issue and receive Peppol BIS for everyone else |
| The same invoice went out by EDI and by Peppol | You issued one invoice: tell the customer which message to book and ask it to reverse the duplicate entry |
| The buyer's portal asks for a PDF upload after your Peppol send | Do not upload a second version. Point to the Peppol invoice; using the portal needs your consent |
| The customer self-bills over EDI (it draws up the invoices for your supplies) | Self-billing needs a prior agreement and your acceptance of each invoice. On Peppol it uses separate self-billing document types that you, the supplier, must be registered to receive. The format rule is the same: an EDIFACT self-billed invoice is not compliant for an in-scope supply; it must be Peppol BIS Self-Billing or, by agreement, an EN 16931 invoice in UBL or CII |
| A customer with a Belgian VAT number but a foreign seat asks for EDIFACT | Check where it is established: without a Belgian seat or fixed establishment it is outside the obligation, and EDIFACT is possible by agreement |
| An EDI provider offers to convert your EDIFACT into Peppol on the buyer's side | What counts is the invoice you issue. Prefer a conversion on your side that sends Peppol BIS as your access point, and keep the converted file |
| Nobody watches the Peppol inbox because ‘our suppliers use EDI’ | Belgian suppliers send to your 0208: registration by default; assign someone to the inbox |
Evidence to keep
What the law requires. Keep the invoices you issue and receive for seven years from 1 January of the year after issue (art. 60 VAT Code, as amended by the Law of 18 December 2025), with authenticity of origin, integrity and legibility guaranteed for the whole period. Keeping the original XML is not mandatory, but FPS Finance strongly recommends it.
What we recommend.
| Flow | Keep |
|---|---|
| Peppol | The XML and PDF as sent, the Traité date, any Invoice Response and the dated lookup of the customer |
| Agreed UBL or CII over EDI | The written agreement (format, syntax, channel, document types, start date), the files as sent and the transport receipts, such as AS2 MDNs |
| Buyer portal you accepted | Your written consent and a downloaded copy of each structured file |
| EDI kept for orders and despatch advices only | The customer's confirmation that invoices go on Peppol, with the switch date |
| Your own Peppol capability | A dated screenshot of Peppol → Statut showing Enregistré (registered) next to Réception (Inbox), or your other provider's confirmation |
What OrdoGrid does. For each Peppol send it archives the exact XML and PDF transmitted, with their hashes. Download them from the Outbox row (XML or PDF), or select rows to get a ZIP. OrdoGrid is not a legal archive and guarantees no retention period.
FAQ
My retailer demands EDIFACT invoices. Am I compliant?
Not if the retailer is a business established in Belgium: EDIFACT is not on the EU syntax list, so it cannot carry the legal invoice, even with an agreement. Send Peppol BIS, or agree in writing on an EN 16931 invoice in UBL or CII over its EDI channel.
Is Peppol just another kind of EDI?
Technically it is structured exchange between systems, but over an open network with shared identifiers, transport (AS4) and rules, which you join through a single certified provider of your choice. In Belgium it is also the legal default for B2B invoices.
Can my customer force me to use its EDI network or portal?
Not unilaterally. The default is Peppol BIS; another format or channel needs both parties' agreement, and FPS Finance says a portal needs your clear written consent. A supplier contract can still create commercial pressure, so negotiate its invoicing clause.
Can we keep EDI for orders and despatch advices?
Yes. The obligation covers invoices and the credit and debit notes that correct them. Orders, despatch advices and other messages can stay on EDI.
If we agree on UBL over AS2, do we still need Peppol?
Yes. Art. 13quater of Royal Decree no. 1 requires the technical means to issue and receive Peppol BIS even when another format is agreed. Lacking them is fined €1,500 for a first infringement, €3,000 for a second and €5,000 for each further one.
Can my EDI provider and OrdoGrid both handle our Peppol traffic?
Sending can run from several tools. Receiving a document type can sit with only one provider; in OrdoGrid, choose Continuer en envoi seul (continue send-only) if another provider holds your registration. Invoice Responses to your invoices then go to that provider.
Can OrdoGrid send EDIFACT or upload to a buyer portal?
No. OrdoGrid sends Peppol BIS through a certified access point and emails PDFs. It creates no EDIFACT files and has no AS2, VAN or portal connection.
Does Traité in the Outbox mean the buyer accepted the invoice?
No. It confirms network delivery. Only an Invoice Response, optional in standard Peppol, gives the buyer's decision, such as AP (accepted) or RE (rejected).
Sources and references
- Royal Decree no. 1 on VAT (consolidated, Justel), arts. 13ter and 13quater
- FPS Finance — FAQ: general questions on electronic invoicing (question 13, alternative formats)
- FPS Finance — FAQ: general questions on the B2B obligation (questions 8, 9, 18 to 22)
- European Commission — Required syntaxes for EN 16931 (UBL 2.1 and UN/CEFACT CII; EDIFACT not listed)
- OpenPeppol — Peppol AS4 profile 2.0 (the only Peppol transport profile)
- FPS BOSA — Belgian Peppol Authority (service provider agreement and certification)