Multi-entity Peppol in Belgium: one group, several KBO identities
How Belgian groups with several KBO entities set up Peppol: one access point or many, which participant identity sends, shared-inbox routing, and a go-live checklist.
Updated
- Belgium
A holding or multi-company group often runs one finance team and several Belgian enterprise numbers (KBO/BCE). Peppol addresses legal entities, not org charts. Each VAT-liable company that must send or receive structured B2B invoices needs its own participant identity (0208 + that entity’s enterprise number).
Registering only the parent means suppliers invoice the wrong party and VAT evidence points at the wrong company. Network: What is Peppol?. Listing: Peppol registration in Belgium. Identifiers: Peppol ID explained.
One group, several legal senders
| What you share | What you must not share |
|---|---|
| Finance team, AP clerks, group reporting | One Peppol ID for several KBO numbers |
| Often one access point contract | The supplier party on the invoice |
| Billing product tenants, if isolated by entity | A single inbound folder with no routing |
Central controllers are fine. Collapsing several KBO numbers into a single participant is not.
- Participant identity
The Peppol address of one legal entity (in Belgium typically
0208:+ KBO/BCE). Groups need one published identity per company that exchanges structured invoices.
One access point or many?
An access point can host many participant IDs. You do not need one AP contract per company.
| Model | When it fits | Watch-outs |
|---|---|---|
| One AP, many IDs | Central IT, shared billing product | Routing must be entity-aware |
| One AP per entity | Strict ring-fencing, different stacks | Higher cost; heavier supplier packs |
| Shared AP, separate apps | Own ERP per entity, one network provider | Clear certificate and contract ownership |
Prefer one AP with multiple IDs when systems isolate senders and inboxes by enterprise number. Split APs only when compliance or M&A truly separates stacks. Switching later: switch access point.
Which identity sends?
The Peppol sender must be the legal supplier on the invoice: same name, VAT number, and 0208 ID as the company that made the supply.
| Rule | Practice |
|---|---|
| Invoice issued by Entity A | Send as Entity A’s participant ID |
| Shared services bills for Entity B | Still Entity B’s ID if B is the contractual supplier |
| Parent pays the AP provider | Parent may pay; it must not borrow B’s identity |
Never reuse another company’s Peppol ID because accounting is centralised. Counterparties look up the enterprise number on the PO. Packs: share your Peppol ID with suppliers.
Shared inbox pitfalls
| Pitfall | Symptom | Fix |
|---|---|---|
| Single queue for all IDs | Entity A cost booked into Entity B | Route by recipient participant ID before triage |
| Only parent published for receive | Suppliers cannot deliver to subsidiaries | Publish receive capability per entity |
| Same supplier master across entities | Wrong PO match / VAT return | Scope supplier records per company |
| Orphaned documents | Received at AP, no company match | Map ID → tenant; see inbound inbox |
Multi-entity adds one gate before normal triage: which company was this addressed to?
Accountants onboarding several clients: accountant Peppol onboarding. Mandate list: Belgian e-invoicing obligation.
Operating checklist
- List every Belgian KBO entity in scope of the 2026 mandate.
- Decide one AP vs many; document SMP and certificate ownership.
- Publish send and receive for each in-scope entity.
- Ensure each invoice’s supplier party matches the sending ID.
- Give suppliers a separate Peppol pack per entity.
- Route inbound by recipient ID; do not rely on an unfiltered shared folder.
- Spot-check: send from Entity A, receive into Entity A only.
Worked example: Nord Holding
Nord Holding BV owns Atelier Nord SRL (0123.456.789) and Nord Logistics SRL (0987.654.321). One AP contract, two published IDs: 0208:0123456789 and 0208:0987654321. Joinery invoices send as Atelier Nord. Freight invoices send as Nord Logistics. Inbound wood invoices addressed to Atelier Nord never land in the logistics tenant.
The failed design was one ID on the holding “because finance is central”. Suppliers looked up the joinery KBO, found nothing, and emailed PDFs. VAT evidence named the wrong company on the few files that did arrive.
FAQ
Does each Belgian company in a group need its own Peppol ID?
Yes if that company must send or receive structured B2B invoices. Peppol addresses the legal entity (typically 0208 + KBO), not the group org chart.
Can one access point serve several entities?
Yes. One certified provider can host many participant IDs. You still publish and route per company.
May the parent send invoices for a subsidiary?
Only if the parent is the legal supplier on the invoice. Paying the AP bill does not let the parent borrow the subsidiary’s identity.
Why do suppliers still email PDFs to a subsidiary?
Often the subsidiary is not published for receive, or only the parent ID is listed. Publish each in-scope entity and share a pack per KBO number.
How do we avoid booking Entity A invoices into Entity B?
Route inbound by recipient participant ID before anyone posts. A shared mailbox without that gate is the usual failure.
Do we need one AP contract per company?
No, unless ring-fencing or different software stacks require it. Prefer one AP and many IDs when isolation is done in the product.
What belongs in each supplier pack?
That entity’s Peppol ID, legal name, VAT / enterprise number, and confirmation that receive is published. Do not send one holding ID for every PO.
Is this the same as multi-user access in one company?
No. Several users in one SRL share one identity. Several SRLs need several identities, even with one login product.