Invoice incident response: failed Peppol sends, outages, duplicates
Handle a failed or uncertain Peppol send, an API outage or a duplicate risk in OrdoGrid: triage, roles, Belgian deadlines, customer messages and closing evidence.
- Updated
- Content owner
- Service operations
- For
- Finance and billing teams · Freelancers and small business owners · Integration and support engineers · Service delivery leads
At a glance
Stop the affected flow, then establish for each document whether it was created, delivered, rejected or is uncertain before you act. Never answer an incident with a new invoice number, a deletion or an email copy: retry the same invoice, hold uncertain sends until OrdoGrid support confirms the outcome, and close only on a reconciled inventory.
Before you begin
- Owner or administrator access to the affected OrdoGrid company
- Access to Peppol → Outbox and, for integrations, to sanitised API logs with your external IDs
- A named incident lead and a finance decision-maker (one and the same person in a small business)
What you will achieve
- Know for each affected invoice whether it was created, delivered, rejected or is uncertain
- Recover without duplicate invoice numbers, double sends or a missed invoicing deadline
- Keep customers and your accountant informed with facts, not guesses
- Close the incident on a reconciled inventory with the evidence to prove it
On this page
An invoicing incident is any event after which you no longer know for certain what your customers received: a Peppol send that failed or never confirmed, an integration that stopped halfway through a batch, an expired API key, invoices that may exist twice. At every scale, stop the flow, establish what happened to each document, then recover with the same invoice numbers and identities. A new number, a deleted draft or an email copy "just in case" turns a transport problem into a duplicate debt.
This playbook covers coordination (triage, severity, roles, Belgian deadlines, customer messages, closure) whether you are a freelancer with one failed invoice or a team running an ERP connector. Badge meanings are in Peppol delivery status, the fix for one failed or rejected invoice in Fix a failed Peppol send or a rejected Peppol invoice, and retry design in Integration reliability. Peppol pages in OrdoGrid are in French in every interface language, so labels are quoted as on screen with a translation in brackets.
The first 15 minutes: five rules
- Stop adding to the problem. Pause sending where it starts: your connector or ERP queue, or the colleagues who click Sauvegarder & Envoyer (save and send). Once the scope is known, pause only the affected company, customer or document type.
- Do not create, delete or renumber. No new invoice for a sale that may already exist, no deleted drafts, no new
external_idfor a transaction already submitted. - Do not email a copy to a customer that receives on Peppol. Peppol cannot recognise duplicates (FPS Finance FAQ, Q4), so the customer may book the sale twice. The send popover ticks Email by default whenever the customer has an email address and sends that email alongside the Peppol attempt, whatever its outcome: untick it for such customers, and if the Email line of the results shows it as sent, record that copy in your inventory.
- Capture evidence now. Screenshot the message; note the time with its timezone, the invoice numbers, the badge in Peppol → Outbox and any error code. Messages disappear and badges change.
- Name one person who decides, the incident lead. Anything that changes amounts, VAT or what the customer owes goes to the finance owner and, where needed, your accountant.
A transport failure never requires a new invoice or a credit note. A credit note is for an invoice whose content is wrong.
Triage: what you see, what it means, who acts
In the app
| What you see | What it means | First check | Who acts |
|---|---|---|---|
| Des erreurs sont survenues. (errors occurred) next to Peppol after Sauvegarder & Envoyer | The send stopped before or during transmission; the outcome may be unknown | Peppol → Outbox: find the row by Numéro, click Vérifier (check) | Sender |
| Créé, En file, En attente, Nouvelle tentative (created, queued, pending, retrying) | Delivery under way | Do not send again; no Traité (processed) after one working day: Vérifier, then OrdoGrid support | Sender |
| Erreur, and a retry is refused because the earlier outcome must be reconciled first | The first attempt may have reached the network | Stop: no retry, no email, no new invoice | Incident lead with OrdoGrid support |
| Pas sur Peppol (not on Peppol), or Peppol — ignoré (Peppol — skipped): Le client n'est pas enregistré sur le réseau Peppol (the customer is not registered on the Peppol network) | No registration found for the VAT number on the invoice | Compare that VAT number with the customer's; search lookup.peppol.org for 0208: plus the enterprise number | Sender, with the customer |
| Limite Peppol atteinte (Peppol limit reached) or Limite du plan gratuit atteinte (free plan limit reached) | Monthly Peppol allowance of the plan used up; nothing sent on Peppol | Billing & Subscription | Owner |
| Signature requise pour activer l'envoi Peppol (signature required to enable Peppol sending), or Peppol opens on Autorisation Peppol | No signed authorisation for the company's VAT number, for example after a change (Nouveau numéro de TVA détecté, new VAT number detected) | Sign the authorisation | Owner or administrator |
| Traité, but the customer says it has nothing | Delivered to the customer's Peppol provider | Customer checks with its provider, using the invoice number and date; no resend | Sender, with the customer |
| Rejetée (rejected, RE) or Sous question (under query, UQ) under Réponses reçues (responses received) | Business dispute, not transport | Read the reason; fix or credit | Finance owner |
Two signals are often misread. A missing Invoice Response is neither acceptance nor rejection: customers are not obliged to send one (Peppol BIS Invoice Response 3.2), and responses reach OrdoGrid only in Mode : Envoi + réception (send and receive). And code AB, shown as Acceptée avec erreurs (accepted with errors), only means in Peppol that a readable invoice was received.
Through the public API
Branch on the error code, not on the message text.
| Code or symptom | Meaning | Action |
|---|---|---|
401 API_KEY_EXPIRED; badge Expired on API keys | The key passed its Expires on date | Create a new key with the same Permissions and Integration ID; Rotate keeps the old expiry date |
401 API_KEY_REVOKED or INVALID_API_KEY | Revoked or wrong key | Find out who revoked or rotated it (Rotate revokes the old key at once); if nobody did either on purpose, treat it as a security incident |
403 INSUFFICIENT_SCOPE | A permission is missing | Issue a key with that permission |
403 PEPPOL_APPROVAL_REQUIRED, 403 PEPPOL_LIMIT_REACHED | No Peppol authorisation, or monthly quota used up | As in the app; nothing was sent |
429 RATE_LIMITED | Too many requests for this key this minute | Wait for Retry-After; slow the queue |
| Timeout or lost response on a create | The invoice may exist | Look it up by external_id first |
409 EXTERNAL_OPERATION_IN_PROGRESS | Another worker is creating the same document | Wait more than two minutes (the worker lease), look up, retry identical content |
PEPPOL_TRANSMISSION_REJECTED | The access point refused the request | Fix the cause; a retry resends the same archived bytes |
PEPPOL_TRANSMISSION_UNCERTAIN; transmission_state sending or uncertain | May have reached the network | Hold; read the status; reconcile with OrdoGrid support |
PEPPOL_CLIENT_NOT_FOUND | Recipient not confirmed; nothing sent | Check with GET /api/v1/peppol/participants/{vat_number} |
PEPPOL_ARCHIVE_HASH_MISMATCH, XML_NOT_AVAILABLE | Archived evidence cannot be served as stored | Escalate; never present a regenerated file as the original |
Look up by external_id at GET /api/v1/invoices/lookup, GET /api/v1/credit-notes/lookup and, for payments and refunds, GET /api/v1/invoices/payments/lookup. Full contract: the API reference.
Set the severity
Severity decides who is involved, not how serious the cause sounds. A small bug that blocks every send is high; an outage touching one invoice due next month is low.
| Level | Typical situation | Who is involved |
|---|---|---|
| Low | One document; outcome known (Pas sur Peppol, plan limit, missing authorisation); deadline not at risk | Sender, fixed the same day |
| Medium | Several documents or one key customer; any uncertain outcome; or an invoicing deadline less than five working days away | Incident lead, finance owner informed, inventory the same day |
| High | A whole flow stopped; duplicates already reached customers; possible credential exposure; or many invoices at risk of missing the 15th | Lead, finance and integration owners, OrdoGrid support, customer owners; regular internal updates |
This scale is our suggestion for your own process, not an OrdoGrid support classification, and it implies no response time; your plan and contract terms apply.
Roles: who decides what
| Role | Decides or does | In a small business |
|---|---|---|
| Incident lead | Scope, timeline, pause and restart, closure | You |
| Finance owner | Amounts, VAT, credit notes, refunds, customer debt | You, with your accountant |
| Integration owner | Connector pause, lookups, safe replay, key replacement | Your developer, if any |
| Sender / operations | Outbox checks, manual queue, daily follow-up | You |
| Customer owner | Messages to customers and commitments made | You |
| OrdoGrid support (contact@ordogrid.com) | Confirms uncertain or delayed transmissions; investigates archive errors | The same |
OrdoGrid connects to Peppol through a certified access point and reconciles transmission outcomes with it. You have no direct relationship with that access point: ask OrdoGrid support.
One failed invoice: the small-business path
- Do not click Sauvegarder & Envoyer again. Screenshot the results with the time.
- Open Peppol, then the Outbox tab; find the row by Numéro and click Vérifier. Opening the row shows Statut (refresh), XML and PDF (what was sent).
- Act on the badge. Traité: done. Créé, En file, En attente, Nouvelle tentative: wait. Erreur: fix the cause, then retry once from Factures (invoices) with the globe icon (tooltip Envoyer à Peppol); if the retry is refused because the earlier outcome must be reconciled, stop. Pas sur Peppol: compare the VAT number on the invoice with the customer's and check its Peppol registration; if the customer confirms it cannot receive, email that same invoice.
- Still unresolved at the end of the next working day, or retry refused: email OrdoGrid support with the details under "What to send OrdoGrid support".
Sophie Lambert, a Namur web designer on the Free plan, sends F-2026-0057 (€1,000.00 + €210.00 VAT = €1,210.00) to Boulangerie Dubois SRL and gets Limite du plan gratuit atteinte. Nothing went out on Peppol, and no PDF either, because she had unticked Email in the send popover: nothing needs reconciling. She changes plan under Billing & Subscription and resends the same invoice with the globe icon (Envoyer à Peppol). An emailed PDF would not have been compliant, because her customer receives on Peppol.
The team path: contain, inventory, recover
Contain without destroying evidence
- Keep identities stable. Keep source transactions,
external_idvalues, the Integration ID and sanitised payloads as submitted. They survive key rotation; a new namespace orexternal_iddefeats duplicate protection. - Do not delete. OrdoGrid deletes only a draft that has no payment, payment link, Peppol transmission or linked or converted document and was not created through the API with an
external_id. Unless it held the highest number in its series (the next document then reuses it), its number leaves a gap you must be able to explain. - Credentials. Revoke a key (Revoke) only when it is demonstrably exposed, or to stop a runaway connector; then create a new key with the same Integration ID. An expired key or a missing permission is not a compromise.
- No secrets in tickets: no API key, no
Authorizationheader, no customer data beyond what the case needs.
Build the inventory
One row per affected source transaction: external_id and Integration ID; OrdoGrid invoice number, document_id and peppol_document_id; amount including VAT and currency; outcome (created, absent, unknown); last badge, status or transmission_state; next action; owner. Count business events, not requests: a replayed request is not new revenue.
Recover each document by its state
| What you found | Meaning | Do | Never |
|---|---|---|---|
| Lookup finds no document | Not created | Resubmit with the same external_id and identical content | Invent a new external_id |
| Invoice exists, never sent | Not transmitted | Send that invoice | Create a second one |
Erreur / rejected, retry accepted | Known not delivered | Fix the cause; retry the same document | Retry under a new number |
sending / uncertain, or retry refused | May have reached the network | Hold; reconcile with OrdoGrid support | Resend, email, replace |
Traité (status processed) | Delivered to the customer's provider | Nothing more on Peppol; follow up payment | Resend because the customer cannot find it |
| Delivered, then Rejetée or Sous question | Business dispute | Finance decides; credit note and new invoice only if the content is wrong | Treat it as a transport failure |
| Archive or hash error | Evidence problem | Preserve the error and references; escalate | Rebuild a file and call it the original |
OrdoGrid locks an invoice's financial content once a Peppol transmission has been prepared or a payment recorded, so a retry resends it exactly as prepared. Wrong content needs a credit note on Peppol and a new invoice.
Belgian rules that keep applying during an incident
What the law requires. Since 1 January 2026, with some exceptions, a business established in Belgium must issue structured invoices to its business customers established in Belgium and identified there for VAT, by default in Peppol BIS over Peppol. For those invoices the structured invoice is the only legal invoice; an emailed PDF does not meet the obligation (FPS B2B FAQ, Q11). An incident does not move the deadline: the 15th of the month after the chargeable event (Royal Decree no. 1, art. 4). When the recipient technically cannot receive, you still issue the invoice in another form, such as a PDF (art. 53 §2bis VAT Code, last paragraph, Law of 10 February 2026), and do not resend it on Peppol later (B2B FAQ, Q8). A credit note correcting a structured invoice also goes on Peppol.
What is not settled. That fallback covers a customer that cannot receive, not an outage on your side. For a supplier that is not ready, the FPS says the customer may in principle refuse an invoice issued another way but keeps its VAT deduction, and the supplier risks a fine (B2B FAQ, Q7). We found no FPS guidance on a temporary outage. The general tolerance covered only the first quarter of 2026 and ended on 31 March 2026 (confirmed by the FPS on 7 April 2026); a fine is now waived only exceptionally, after individual analysis (FPS Finance). Lacking the technical means to issue and receive costs €1,500 for a first infringement (penalties).
What we recommend. Most incidents last hours and the deadline is weeks away: wait for the structured channel. If an outage puts the 15th at risk, decide with your accountant whether to issue in another form, and keep evidence of the outage. One channel per invoice: on 8 September 2026 the Belgian Peppol service providers' forum recommended sending only on Peppol to recipients that receive there (a recommendation, not a ban).
What OrdoGrid does. It archives the exact XML and PDF before transmission, resends that archive on a retry, refuses a new attempt while an outcome is unresolved and never switches to email by itself. It has no test mode.
- Uncertain transmission
- A Peppol send for which OrdoGrid got no clear answer from its access point, for example after a timeout (
transmission_stateuncertain, errorPEPPOL_TRANSMISSION_UNCERTAIN). The document may have reached the network, so OrdoGrid blocks a new attempt until the outcome is reconciled.
Worked example: a batch interrupted at invoice 30 of 50
Brabant Facility Services SRL in Wavre invoices 50 maintenance contracts for September 2026 through its ERP connector (Integration ID erp) on Thursday 1 October 2026 from 08:00 Brussels time (UTC+2 until 25 October). Each contract has a stable external_id, such as contract-2026-09-0330.
| Contract type | Invoices | Net each | VAT 21% each | Total each | Batch total |
|---|---|---|---|---|---|
| Standard | 30 | €800.00 | €168.00 | €968.00 | €29,040.00 |
| Premium | 20 | €1,250.00 | €262.50 | €1,512.50 | €30,250.00 |
| All | 50 | €59,290.00 (net €49,000.00 + VAT €10,290.00) |
At request 30 the network between the ERP and OrdoGrid fails: 28 successful responses, 2 timeouts, 20 contracts never attempted.
- 08:20. The integration owner pauses the connector. Severity high while the connector flow is stopped; lowered to medium at 09:15 once it resumes, since only one outcome remains uncertain and the deadline of 15 October is two weeks away. The key works, so it is not rotated.
- 08:35. Lookups by
external_idfind both timed-out contracts as invoices F-2026-0329 and F-2026-0330, two Premium contracts. Recreating them would have billed €3,025.00 twice. - 08:40. F-2026-0329 is Traité. F-2026-0330 is
uncertain, and the connector's automatic retry at 08:17, just before the pause, had been refused withPEPPOL_TRANSMISSION_UNCERTAIN: the lead holds it and emails OrdoGrid support. - 09:15. The connector resumes the 20 unattempted contracts with their original
external_idvalues; OrdoGrid numbers them F-2026-0331 to F-2026-0350. - Friday 2 October. Support confirms that F-2026-0330 reached the network; the row shows Traité.
| Group | Invoices | Amount incl. VAT | Outcome | Action |
|---|---|---|---|---|
| Response received | 28 | €32,549.00 | Created and sent | Monitor until Traité |
| Response lost, delivered | 1 | €1,512.50 | F-2026-0329, Traité | No resend |
| Response lost, uncertain | 1 | €1,512.50 | F-2026-0330 | Held, then confirmed |
| Never attempted | 20 | €23,716.00 | Absent | Resumed with original IDs |
| Total | 50 | €59,290.00 | F-2026-0301 to F-2026-0350 | Closed 2 October |
The 28 are 18 Standard and 10 Premium (€17,424.00 + €15,125.00); the 20 are 12 Standard and 8 Premium (€11,616.00 + €12,100.00). Closure check: 50 contracts, 50 invoice numbers, €59,290.00 on both sides, 50 Traité, no duplicate.
Keep customers and colleagues informed
Separate what is proven from what is still being checked: a held queue is not lost revenue, and a delayed delivery is not a missing invoice. Each internal update states the impact (count and amount), what is proven, what is under investigation, the customer impact and the time and owner of the next decision. At 09:30 in the example: 50 invoices, €59,290.00; 28 sent, 1 delivered, 20 being resumed; 1 uncertain (€1,512.50) held; no duplicate sent; next decision at 11:00.
Write to a customer only when it is affected: a delay it will notice, a duplicate it may have received, a rejection to clarify.
Subject: Invoice F-2026-0330 – Peppol delivery being confirmed
Our invoice F-2026-0330 of 1 October 2026 (€1,512.50 incl. VAT, due 31 October 2026)
was sent to you on Peppol. We are checking whether it reached your Peppol provider.
We will not send it again by email or under another number. If it is not in your
system by 6 October, please ask your Peppol provider to look for this invoice number.
Share only the references the customer needs, never keys or other customers' data, and record who was told what and any commitment made.
Restart and close
- Counts. Every source event has exactly one OrdoGrid document.
- Amounts. Totals including VAT match by currency between the source system and OrdoGrid.
- Delivery. Every document is Traité, or has a named owner and a next action.
- Money. Use Record payment in Settlement only when money reaches your bank; a delivery incident changes no balance. See Month-end reconciliation.
- Controlled restart. Send a small real batch, check it in Outbox, then release the rest.
- Manual actions. List what was done by hand, such as an invoice emailed under the fallback, so automation does not repeat it.
- Closure record. Cause; impact window with times and timezone; affected count and amount; corrective action; evidence; one improvement action with an owner and a due date.
Close only when every affected transaction is accounted for or has a named residual-case owner; a restored service does not prove your backlog reconciled. Feed repeated causes into your integration reliability controls and the rollout acceptance pack.
What to send OrdoGrid support
Subject: Peppol incident – F-2026-0330 – outcome to confirm
Company and VAT number: …
Invoice: F-2026-0330 (document_id …, peppol_document_id …)
external_id and Integration ID: contract-2026-09-0330, erp
Sent: 1 October 2026, 06:14 UTC (08:14 CEST)
Last badge / transmission_state: Erreur / uncertain
Error code: PEPPOL_TRANSMISSION_UNCERTAIN (retry refused at 06:17 UTC)
Already done: connector paused; no resend, no email copy
Leave out API keys and request headers. From the app, a screenshot and the invoice number replace the technical identifiers.
Evidence to keep
- Screenshots of messages and badges, with date and time.
- The transmitted XML and PDF from each Outbox row, or a ZIP of selected rows.
- The inventory, with lookups,
transmission_statevalues and error codes. - Internal updates, customer messages and support exchanges.
- The closure record and its improvement action.
Keep invoices and credit notes for 7 years from 1 January of the year after issue (VAT Code art. 60, as amended by the Law of 18 December 2025); keeping the original XML is strongly recommended. OrdoGrid archives what it transmits with hashes but is not a legal archiving service: keep your own copy.
FAQ
Should I email PDFs while Peppol sending is failing?
Not to customers that receive on Peppol: for them the structured invoice is the legal invoice, and a copy risks a duplicate Peppol cannot detect. Wait for the structured channel; involve your accountant only if the 15th-of-month deadline is at risk.
Can I delete the failed invoice and start again?
No. Once a Peppol transmission exists, OrdoGrid will not delete the invoice and its number stays in your sequence. Retry it, hold it while the outcome is uncertain, or credit it if its content is wrong.
Who confirms whether an uncertain invoice reached the customer?
OrdoGrid support, which reconciles the outcome with its access point; you have no direct relationship with that access point. Send the invoice number, the time in UTC and the error code.
Our API key expired in the middle of a batch. Is rotating it enough?
No. Rotate keeps the old expiry date. Create a new key with the same permissions and Integration ID, then resume with the original external IDs.
The customer sent no Invoice Response. Is something wrong?
No. Invoice Responses are optional in standard Peppol BIS and reach OrdoGrid only when reception is active. Traité shows delivery; your bank statement shows payment.
Sources and references
- Peppol BIS Invoice Response 3.2: transport acknowledgements versus business responses
- FPS Finance, Peppol FAQ: participant lookup and delivery delays
- FPS Finance, e-invoicing FAQ: specific questions (Q4 duplicates, Q29 wrong recipient)
- FPS Finance, e-invoicing FAQ: general questions on the B2B obligation (Q7–Q8, Q11)
- Law of 10 February 2026, art. 4: invoice in another form when the recipient cannot receive (Belgian Official Journal, 20.02.2026)
- FPS Finance, end of the e-invoicing tolerance period (7 April 2026)