Enterprise rollout: entities, Peppol, acceptance tests and go-live
Roll out OrdoGrid one Belgian entity at a time: receiving and plan decisions per company, a real-network acceptance pack and a recorded go/no-go decision.
- Updated
- Content owner
- Implementation team
- For
- Implementation leads · Finance directors and controllers · Finance operations teams
At a glance
Release one verified Belgian entity at a time. Give each its own OrdoGrid company, Peppol authorisation, receiving channel and plan, prove issuing, receiving, settlement and retrieval with real invoices to the cent, and go live only on a dated go/no-go decision. OrdoGrid has no test mode and no approval workflow, so the gates live in your own project records.
Before you begin
- A named sponsor, implementation lead and finance owner for each entity
- A list of the legal entities with enterprise number, VAT status and current Peppol provider
- Owner or administrator access to each OrdoGrid company (owners and administrators edit Profil entreprise, including numbering formats; viewers cannot), or the right to create each company
- Pilot customers and suppliers who agree to exchange real invoices
What you will achieve
- An entity register with a sending, receiving and plan decision for every company
- A passed acceptance pack with expected and actual amounts matching to the cent
- A dated go/no-go decision, an observation period and a handover to operations
On this page
A rollout is finished when each finance team can issue, receive, reconcile and retrieve its own documents without the project team. A signed authorisation and a first invoice are milestones. They do not prove that every entity can receive, that every VAT treatment is transmitted correctly, or that a lost response can be recovered without a duplicate.
This playbook is for implementation leads, finance directors and operations teams introducing OrdoGrid across one or more Belgian legal entities, or adding an entity or integration. It covers phases, gates, the acceptance pack and the go-live decision. Group identity and routing are in Peppol for Belgian groups, integration design in Public API integration, and daily checks in billing controls.
What the law fixes, what you decide, what OrdoGrid does
What the law requires. Since 1 January 2026, a taxable person established in Belgium issues structured e-invoices for its B2B supplies to Belgian-established taxable customers, art. 44-exempt supplies excepted (art. 53 §2bis VAT Code). The default is Peppol BIS over the Peppol network; another EN 16931 format needs the parties' agreement (art. 13ter Royal Decree no. 1). Those customers must be able to receive them. Lacking the technical means to issue and receive incurs a fine of €1,500, then €3,000, then €5,000 per further infringement (Royal Decree no. 44 annex, section 2, heading I, point C). An infringement counts as a repeat only if established at least three months after the previous fined one. The first-quarter tolerance ended on 31 March 2026. Every Belgian company on Peppol must be registered at least under 0208: plus its ten-digit enterprise number from the KBO/BCE (Crossroads Bank for Enterprises).
What we recommend. Release in waves of one or a few entities, each passing written gates with a named owner, a deputy and a dated decision.
What OrdoGrid does. Each legal entity is a separate OrdoGrid company with its own VAT number, numbering, team, plan, Peppol authorisation, reception and API keys. Peppol sending needs a Belgian VAT number (see the API reference). There is no test mode, no approval workflow, no SSO and no custom role: every acceptance send is a real invoice on the production network, and sign-offs belong in your own project tool.
Plan the rollout in gated phases
| Phase | Gate to pass before the next phase | Accountable | Evidence |
|---|---|---|---|
| 1. Scope | Every entity has a scope verdict, a receiving decision and a plan | Finance lead | Approved register version |
| 2. Configure | Each in-scope company shows Autorisé and its receiving channel on Peppol → Statut | Implementation lead | Statut tab capture, lookup result |
| 3. Accept | Every acceptance case passes at the agreed thresholds | Controller | Acceptance log, expected and actual values |
| 4. Decide | Go/no-go recorded with exclusions and residual risks | Sponsor | Dated decision |
| 5. Observe | One full billing cycle reconciled at 100% | Operations lead | Cycle reconciliation |
| 6. Hand over | Deputies resolve a drill without help | Operations lead | Drill record |
Give each role a named deputy, and keep the register, acceptance log and decision in one versioned place. OrdoGrid stores documents and delivery evidence, not your approvals.
Register every entity before configuring
Create one row per legal entity and document flow: legal name and form, enterprise number, VAT status (separate company, VAT unit member, small-business exemption), Belgian establishment, current Peppol provider, monthly volume and peak, document types, VAT treatments, source system, payment sources, archive owner, and the future Owner (the person who will create the company in OrdoGrid) and Administrator.
Decide receiving per entity
Reception is optional in OrdoGrid ("Optionnelle — l'envoi fonctionne sans"); in law it is not. Decide from a lookup of 0208: + the enterprise number on lookup.peppol.org. Once the company exists and its Autorisation Peppol is signed (OrdoGrid redirects every Peppol page there until then), Peppol → Réception Peppol shows the matching state:
| What Réception Peppol shows | Meaning | Decision |
|---|---|---|
| Pas encore trouvé sur le réseau Peppol (not yet found) | No provider receives for this enterprise number | Activer la réception: OrdoGrid registers 0208: + the enterprise number |
| Déjà inscrit sur le réseau Peppol (already registered) | Another provider holds reception | Continuer en envoi seul (send only) and record that provider, or move reception: the old provider deregisters, then you activate the same day |
| Référencé sur Peppol, access point non vérifié (listed, access point not verified) | Listed on Peppol, but OrdoGrid could not verify which provider holds reception | Check lookup.peppol.org, then try Activer la réception: OrdoGrid refuses it if another provider holds the ID, and that provider must deregister it first |
| Déjà présent sur Peppol via notre access point | Registered through the access point OrdoGrid uses | Try Activer la réception; if refused, see the next row |
| Activation refused: Réception déjà liée sur la plateforme | Another OrdoGrid company with this VAT number holds reception | Use Ouvrir … to go there; keep one company per legal entity |
OrdoGrid connects to Peppol through a certified access point and does not support migration keys, so the old provider must deregister first; see switch access point. A send-only entity complies only if another provider really receives for it. Check on lookup.peppol.org with 0208: and the enterprise number, which shows the ability to receive, not to send.
Size the plan per company
Each OrdoGrid company has its own subscription under Billing & Subscription. As of October 2026, the pricing page lists one Peppol invoice sent per month on Free, unlimited Peppol invoices on paid plans, credit notes and email sending on paid plans only, and API access and an unlimited team on Business only. A second Peppol send in a month on Free stops with Limite du plan gratuit atteinte (free plan limit reached), or PEPPOL_LIMIT_REACHED through the API. Size each company for its peak month before acceptance.
Configure each company
- Switch company. In the profile menu, use Changer d'entreprise (switch company), or Créer une nouvelle entreprise (create a new company) and enter the VAT number to prefill data from the Belgian register. Check the company name before each step.
- Complete the profile. In Profil entreprise (company profile, editable by owners and administrators), check Nom de l'entreprise, the VAT number, address, IBAN and Mentions légales (pied de page des factures) (legal footer) against the KBO/BCE record. Langue des documents is one language per company. For an operating seat in the Dutch-language area, such as the Vercauteren companies in Ghent, the legally required invoice parts must be in Dutch (Flemish decree of 19 July 1973), so choose NL there.
- Fix numbering before the first save. Numbers are committed at the first save, drafts included. Under Formats de numérotation, click Modifier and set the formats (defaults
F-{YYYY}-{####}andNC-{YYYY}-{####}). If the entity already invoiced in 2026 elsewhere, decide whether to continue that series; see invoice numbering and migration cutover. OrdoGrid does not enforce gapless numbering. - Invite the team. The user who creates a company is its only Owner, and OrdoGrid cannot assign or transfer that role, so have the future owner create it. Under Team, invite the others as Administrator or Viewer per company. Only owners and administrators create documents, record payments and manage API keys.
- Sign the authorisation. On Autorisation Peppol, the signer types a name in Nom complet du signataire, ticks the declaration and clicks Signer et confirmer l'autorisation. This is a recorded confirmation, not a qualified electronic signature; decide internally who may sign.
- Apply the receiving decision on Réception Peppol.
- Check the result on Peppol → Statut: Envoi (Outbox) shows Autorisé, Réception (Inbox) the registration, Annuaire Peppol the Identifiant Peppol for suppliers (and, when shown, Access point de réception: Notre access point for an entity that receives in OrdoGrid), and Autorisations who signed. If Statut warns that another provider manages the Peppol ID, suppliers' invoices still go to that provider: contact OrdoGrid support.
- For an integration, create a key in API keys inside that company, with a Name, the narrowest Permissions and an Integration ID such as
crm. CallGET /api/v1/meand compare the company and capabilities with the register.
Build a representative acceptance pack
Acceptance runs on real invoices to agreed customers and suppliers: OrdoGrid has no test mode, and every saved invoice takes a number in your legal series. Pick cases from the pilot entity's real business, never create invoices to delete them, and agree in advance that the counterparties will receive and answer. Include one case per document type, VAT treatment and channel the entity actually uses:
| Case | Pass when |
|---|---|
| Mixed-rate invoice with a PO number | Net, VAT per rate and Montant à payer match the controller's figures to the cent; the PO appears in the Peppol XML; the badge reaches Traité |
| Credit note on part of that invoice | It refers to the invoice on the PDF and in the XML (art. 12 Royal Decree no. 1), travels on Peppol like the original (art. 53 §2bis) and lowers Outstanding by its gross amount |
| Partial payment, and a refund if the entity makes refunds | Settlement shows the expected Payments (including prepayments), Credits, Outstanding and Refund due |
| Received supplier invoice | It appears in the right company's Inbox; its reference is entered in your accounting system (OrdoGrid has no purchase ledger) |
| Misaddressed supplier invoice, if one occurs | Rejected with Répondre → RE Rejetée and not booked |
| Customer not on Peppol | The send popover shows Peppol — ignoré, the invoice goes by Email, the fallback is logged |
| Retrieval | Someone outside the project finds the exchanged XML and PDF from the invoice number: Peppol → Outbox, then XML or PDF; an integration calls GET /api/v1/peppol/documents/{id}/xml with the peppol_document_id |
| Recovery drill | Diagnosis and recovery without a second numbered invoice (below) |
Traité means network delivery, not the buyer's acceptance or payment. Delivery usually takes minutes to a couple of hours; if a document stays En file, En attente or Nouvelle tentative for more than one working day, contact OrdoGrid support. OrdoGrid validates each document against EN 16931 and Peppol BIS Billing 3.0 rules before sending, but a readable PDF alone never proves that the structured document went through.
Recovery drills
- Lost API response. Create an invoice with an
external_idand anIdempotency-Key, discard the response, then callGET /api/v1/invoices/lookup?external_id=…or repeat the identical request. Pass when the same invoice and number come back and the next new invoice takes the next number. - Uncertain Peppol send. A send that returns
PEPPOL_TRANSMISSION_UNCERTAINis never retried as a new invoice: read its status and reconcile with OrdoGrid support first. In the app, use Vérifier on the Outbox row. - Correction after sending. Try to change an amount on an invoice sent on Peppol or with a recorded payment: OrdoGrid refuses with
DOCUMENT_FINANCIAL_CONTENTS_LOCKED. An invoice that was only emailed is not locked, so your procedure must forbid editing issued invoices. The team corrects with a credit note and, if needed, a new invoice.
Worked example: the Vercauteren group, wave 1
The Vercauteren group in Ghent has three companies. Its implementation lead, Thomas Lambert, builds the register in September 2026:
| Vercauteren Advisory BV | Vercauteren Logistics BV | Vercauteren Logistics Nederland BV | |
|---|---|---|---|
| Enterprise number | 0765.432.146 | 1002.345.639 | None (Dutch company) |
| Peppol ID | 0208:0765432146 | 0208:1002345639 | — |
| Belgian obligation | In scope | In scope | Outside: not established in Belgium |
| Réception Peppol | Pas encore trouvé sur le réseau Peppol → Activer la réception | Déjà inscrit sur le réseau Peppol (its ERP provider) → Continuer en envoi seul | Not available: no BE VAT number |
| Volume and plan | 80 invoices a month, Business (API access) | 140 a month, paid plan from wave 2 | — |
| Integration | CRM key, Integration ID crm | None | — |
| Wave | 1 | 2 | Open decision with the Dutch adviser |
Logistics' number starts with 1 because the company was registered after 19 September 2023, when new enterprise numbers began to start with 1; its systems must accept both forms. Controller Nadia El Amrani writes the expected values before anything is created:
| Step | Document | Expected |
|---|---|---|
| A1 | Invoice F-2026-0418 to Delvaux Retail SA, 1 October 2026, PO PO-77812: 8 h × €125.00 at 21% and 4 × €50.00 at 6% | Net €1,200.00; VAT €210.00 + €12.00 = €222.00; Montant à payer €1,422.00 |
| A2 | Credit note NC-2026-0031, 6 October, for the 6% line | €200.00 + €12.00 = €212.00, referring to F-2026-0418 |
| A3 | Bank transfer of €500.00 received on 9 October | Invoice total €1,422.00, Credits €212.00, Payments (including prepayments) €500.00, Outstanding €710.00, no Refund due row |
F-2026-0418 continues the series of the entity's old tool. The 6% rate comes from the finance lead's tax mapping: the test checks that OrdoGrid computes and transmits it, not the classification. Had Delvaux paid €1,422.00 before the credit note, Refund due would show €212.00 until the actual repayment is recorded with Record refund.
Every case passes, with one finding: a fuel-card supplier sends an invoice for Logistics' lorries to Advisory's Peppol ID. Advisory rejects it with RE Rejetée, reason code UNR (transaction not recognised) and a note giving 0208:1002345639; nothing is booked. On 12 October the sponsor releases Advisory and keeps Logistics out until its suppliers correct their data (see supplier onboarding). The report says "limited release, one entity", not "group live".
Go/no-go: thresholds and the decision record
These thresholds are our recommendation: adapt them, but write them down before testing.
| Criterion | Go when |
|---|---|
| Amounts | Every case matches the expectation to the cent; any difference is explained and accepted in writing by the controller |
| Delivery | Every outbound case is Traité or has a logged fallback; none in Erreur or waiting without explanation |
| Uncertainty | No send with an unknown outcome; no number consumed by a failed attempt without explanation |
| Reception | At least one real inbound invoice per entity, no unidentified recipient |
| Identity | Statut shows Autorisé and the receiving channel; lookup shows the 0208: ID |
| Capacity | The plan covers the peak month |
| People | Each role has a deputy who completed a drill unaided |
The decision record lists the entities and flows released, excluded flows with an owner and a date, accepted cosmetic defects, residual risks, the observation period, the tester and the person who accepted the financial results. Never hide a failed case behind a new invoice number.
Edge cases and common mistakes
| Situation | What you see | What to do |
|---|---|---|
| Group company without a Belgian VAT number | Sends refused: "Peppol n'est disponible que pour les entreprises enregistrées en Belgique" | Record an open decision; OrdoGrid can still produce its invoices |
| Customer not on Peppol | Peppol — ignoré: Le client n'est pas enregistré sur le réseau Peppol | Send by Email. This fallback invoice is valid (art. 53 §2bis al. 6 VAT Code); a customer subject to the obligation remains in breach of its own receiving duty. Do not resend it as structured later |
| Supplier invoice meant for a sister company | It sits in the wrong Inbox | Répondre → RE Rejetée with a reason code and the correct ID; do not book it |
| Payment entered around month-end | Occurrence time (UTC) | 00:30 on 1 November in Brussels is 23:30 UTC on 31 October; enter the UTC time |
| Editing an invoice sent on Peppol or with a recorded payment | DOCUMENT_FINANCIAL_CONTENTS_LOCKED | Credit note, then a new invoice if needed. An emailed-only invoice is not locked: correct it the same way, never by editing |
| Email and Peppol both ticked in the send popover | The customer gets the Peppol invoice and a PDF email | Set a policy: the Belgian Peppol service providers' forum recommends avoiding dual sending to customers who receive on Peppol, and Peppol cannot detect duplicates |
Evidence to keep
For each acceptance case, keep the source reference, expected result, OrdoGrid number and document_id or peppol_document_id, actual result, UTC timestamps, tester, approver and file location. Store with it:
- the Statut tab of each company and the lookup result for its
0208:ID; - the exchanged XML and PDF from Peppol → Outbox, or a ZIP of selected rows with
xml/andpdf/folders; - the Original document and Current statement from Settlement;
- the Invoice Responses sent from the Inbox;
- the dated go/no-go decision.
Keep secrets and unnecessary personal data out of captures and tickets. The invoices themselves are legal records, kept seven years from 1 January of the year after issue, longer in some immovable-property cases. OrdoGrid gives no retention guarantee, so plan regular archive exports; see invoice archiving.
Hand over, observe, then expand
Give operations the entity register, field mapping, key owners and Integration IDs, the reconciliation calendar, the exception queue, the acceptance evidence and the change calendar. During an observation period of at least one full billing cycle, month-end included, reconcile every invoice rather than a sample. Daily checks then move to billing controls, failures to incident response.
Escalate to OrdoGrid support with the invoice number, document_id or peppol_document_id, the UTC time, the badge or transmission_state and the error code. Internal response targets are your team's commitments; this guide sets no service level.
Re-run the affected acceptance cases after any change of entity, VAT treatment, numbering, source mapping or receiving provider. After the first cycle, check the human side too: was each inbound invoice picked up, each failed send noticed, each piece of evidence found without a developer? Expand only when the previous entity runs without the project team.
FAQ
Can two group companies share one Peppol inbox in OrdoGrid?
No. Each company with its own VAT number is a separate OrdoGrid company with its own 0208: ID and Inbox. One login can belong to several companies and switch between them; see Peppol for Belgian groups for VAT units and intra-group invoices.
Is there a test or sandbox environment for acceptance?
No. API calls and Peppol sends act on real data and the real network, and every saved document takes a number. Use real invoices with agreed counterparties; the API option "send": false creates a real invoice without transmitting it.
What if an entity is already registered on Peppol with another provider?
Réception Peppol shows Déjà inscrit sur le réseau Peppol. Choose Continuer en envoi seul, and suppliers keep delivering to the other provider. To move reception to OrdoGrid, the old provider must deregister first, because OrdoGrid does not use migration keys.
Is a send-only entity compliant?
Only if another provider receives for it. The law requires the means to issue and receive structured invoices, and lacking them incurs a fine of €1,500, then €3,000, then €5,000 per further infringement.
Who signs the Peppol authorisation and the go-live?
OrdoGrid records a typed name, a ticked declaration, the user and the date; it is not a qualified electronic signature. Who may sign, and who approves go-live, is your internal governance: record both in your project records.
Sources and references
- OpenPeppol – Peppol BIS Billing 3.0
- Law of 6 February 2024 – art. 53 §2bis VAT Code (Belgian Official Journal)
- Royal Decree of 8 July 2025 – arts. 13ter–13quater RD no. 1 and fines in RD no. 44 (Belgian Official Journal)
- Law of 10 February 2026 – art. 53 §2bis amended: established parties only, fallback (Belgian Official Journal)
- FPS Finance – FAQ General questions on the B2B obligation (fallback, customer not ready)
- FPS Finance – FAQ General questions about Peppol (0208 ID, lookup, delays)
- FPS Finance – FAQ Specific questions about e-invoicing (credit notes, misaddressed invoices)