Accountant Peppol client onboarding playbook
How Belgian accountants and tax advisors onboard multiple clients onto Peppol: identity hygiene, dual send/receive, common blockers, and a clean handoff checklist.
Updated
- Belgium
You are the bottleneck or the accelerator
Belgian accountants and tax advisors sit between mandate pressure and client inertia. After the 2026 structured e-invoicing obligation, firms that still treat Peppol as "software the client will figure out" accumulate failed deliveries, incomplete archives, and year-end cleanup. Firms that run a repeatable onboarding playbook turn Peppol into a controlled handoff: identity correct, send and receive live, exceptions documented.
This article is written for the advisor running a portfolio of Belgian SMEs and sole traders, not for a single end-user learning Peppol from scratch.
Onboarding job, in one sentence
For each in-scope client entity, make the KBO/BCE-based Peppol identity discoverable, enable dual send and receive, prove both with a short test, then hand ownership of day-to-day inbox and issuance to the client (or keep it in a managed service model you explicitly sell).
Identity hygiene before any tool click
Peppol registration fails when the legal entity is fuzzy. Collect once, reuse everywhere:
| Field | Why advisors care |
|---|---|
| Enterprise number (KBO/BCE) | Becomes 0208:… participant ID |
| Legal name as in BCE | Access Point verification mismatches |
| VAT number / status | Mandate and franchise nuances |
| Who signs provider terms | Mandate holder vs accountant login |
| Existing Access Point | Avoid duplicate or stale SMP entries |
One legal entity, one primary Peppol identity. Groups and multi-VAT setups need a matrix, not a shared inbox. Mechanics live in Peppol registration for Belgian businesses.
- Advisor-led Peppol onboarding
A controlled process where the accountant or tax advisor verifies client identity data, drives Access Point registration for send and receive, validates discoverability, then hands off operational ownership with a written checklist.
Dual send/receive as the default acceptance criterion
Do not close an onboarding ticket when the client can "send a PDF somehow." Acceptance means:
- Participant published via a certified Access Point.
- Outbound: structured Peppol BIS Billing invoice leaves the client's (or your) invoicing tool.
- Inbound: supplier invoices land in a usable Peppol inbound inbox.
- Directory lookup shows the client as reachable for billing.
Franchise or exempt clients still need a reception story when VAT-liable suppliers send structured invoices. Point them to VAT exemption, franchise regime, and receiving Peppol invoices and record the agreed emission stance in the file.
Common client blockers (and how you unblock)
| Blocker | What you see | Advisor move |
|---|---|---|
| Wrong enterprise number | Lookup miss, failed send | Reconcile BCE extract before re-registering |
| Receive never advertised | Suppliers cannot deliver | Complete SMP profile for inbound billing |
| Send-only "pilot" | Mandate half-met | Force dual capability before go-live |
| Stale previous Access Point | Intermittent routing | Coordinate deregistration and cut-over |
| Client not on Peppol (your client's customer) | Outbound delivery fail | Use client not on Peppol; do not invent mandate bypasses |
| Login confusion (firm vs client) | Orphaned documents, missed inbox | Decide managed vs client-owned access in writing |
| "We still email PDFs" | Cultural resistance | Separate human PDF copy from structured legal channel |
Batch these into office hours or a weekly Peppol clinic: identity pack, registration status, send test, receive test, exception list.
Handoff checklist (per client entity)
Close the engagement only when each box is true or explicitly deferred with a date:
- Identity pack filed (BCE number, VAT status, signatory, chosen Access Point).
- Registration live; self-lookup succeeds.
- Send proven with one structured invoice to a Peppol counterparty or provider test.
- Receive proven with one inbound document opened and archived.
- Who monitors the inbox named (client staff, bookkeeper, or your firm).
- Customer master data process updated: enterprise number collected and looked up before first invoice.
- Exception path documented for unreachable buyers.
- Franchise/exempt nuance noted where relevant, with emission guidance confirmed.
- Credentials and mandate clarified: who can change Access Point or deregister.
- Next review date set (software change, entity change, or quarterly hygiene).
What this playbook is not
It is not legal advice on whether a specific invoice falls under the mandate, and it is not a substitute for What is Peppol? for end users. Your value is operational: clean identities, dual capability, fewer blocked invoices, and a handoff the client (and your team) can run without heroics.