Multi-entity Peppol setup for Belgian groups
How Belgian groups with several KBO entities choose one Access Point or many, which Peppol identity sends, and how to avoid shared-inbox misrouting.
Updated
- Belgium
One group, several legal senders
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. See What is Peppol? and Peppol registration in Belgium.
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.
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. See Share your Peppol ID with suppliers.
- 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.
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?
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.