Playbook21 min read

Billing controls: prevent and detect invoicing and payment errors

Pre-issue checks, weekly reviews and correction rules for Belgian invoicing in OrdoGrid: mandatory details, numbering, duplicates, credit notes, refunds, evidence.

Updated
Content owner
Finance operations
For
Financial controllers · Accounts receivable and billing teams · Freelancers and small business owners · Accountants reviewing a client's invoicing

At a glance

Check company, customer, VAT treatment, number and amounts before an invoice is issued, because a Peppol send or a recorded payment locks its amounts. Afterwards, reconcile each invoice's Settlement panel with the bank, review numbering, duplicates and delivery, and correct only with credit notes and reversals that keep the original visible.

Before you begin

  • Owner or administrator access to the OrdoGrid company, or the Viewer role for review only
  • Bank statements for the period and the commercial source: quotes, orders, timesheets, contracts
  • Your accountant's position on VAT treatments, rounding cents and write-offs
  • For API integrations: the source system's external IDs and the API key's Integration ID

What you will achieve

  • A control routine sized to your invoice volume, with an owner and evidence for each check
  • Wrong company, customer, VAT treatment or amount stopped before the customer receives the invoice
  • A settlement review that ties OrdoGrid to the bank and to the VAT figures
  • Corrections that keep the original invoice, the credit note and every movement linked
On this page

A billing control is a check with an owner, a moment and evidence. In OrdoGrid, most errors are cheapest to stop before the first Peppol send or recorded payment: from then on the amounts are locked, and every correction needs a credit note or a reversal that stays visible. After issue, the controls are detective: reconcile each invoice's Settlement panel with the bank, review numbering, duplicates and delivery, and check that every correction points to the document it corrects.

This playbook is for controllers, accounts receivable teams, accountants and small businesses that want a short routine. The step-by-step guides are elsewhere: Correct, cancel or credit an issued invoice, Follow up an invoice and record a partial payment and, for the period close, month-end reconciliation.

What the law requires, what we recommend, what OrdoGrid does

TopicBelgian lawWe recommendOrdoGrid
Invoice contentMandatory full-invoice details under Royal Decree no. 1, art. 5 §1: date and number, both parties' name, address and VAT number, per rate the taxable amount and unit price excluding VAT, total VAT, exemption or reverse-charge wordingThe pre-issue check belowPrints what you enter; validates Peppol XML against EN 16931 and BIS Billing 3.0.21 before delivery; no legal check of an emailed PDF
DeadlineBy the 15th of the month after the chargeable event (art. 4)Monthly completeness checkNo alert
NumberingSequential, unique, "based on one or several series" (art. 5 §1 1°)Monthly gap reviewProposes the next number, refuses duplicates, no gap-free enforcement
CorrectionsRectifying document referring to the invoice (art. 12), in the same format as a structured original (VAT Code art. 53 §2bis)Credit note, then a new invoice where neededLocks amounts after a payment or Peppol send; credit notes start from an invoice
DuplicatesPeppol does not detect duplicates; spotting them is up to the user and the software (FPS Finance FAQ, Q4)One channel per customer; weekly reviewRefuses a duplicate number and a second Peppol send of a document
PaymentsBookkeeping evidence, not a required invoice detailRecord only money that has arrivedNo "paid" status without a recorded payment
Retention7 years from 1 January after the year of issueKeep your own copiesArchives the XML and PDF sent on Peppol; no retention guarantee

Size the routine to your volume

The law sets the invoicing rules, not how often you check them. This is our suggested starting point; adjust it with your accountant or auditor.

Invoices per monthBefore issueAfter issue
Fewer than 20Check every invoice yourselfMonthly: every invoice, payment and credit note against the bank
20 to 500Preparer checks; a second person checks non-standard VAT, credit notes and write-offsWeekly exceptions; monthly sample of about 10% of the rest
More than 500, or via an integrationChecks in the source system; human review of exceptionsDaily automated comparison of counts, totals and identities; weekly exceptions

The control register

Record for each control the risk, the moment, the owner, the evidence and the action on failure. A small team may combine roles; note who did both steps rather than claim an independence that does not exist.

ControlRiskWhenEvidence
Issuing companyWrong company of a group, wrong VAT numberEvery invoicePreview header
CustomerWrong customer, VAT number or addressNew customer, every changeLookup source, order or contract
VAT treatmentWrong rate or regime, missing wordingEvery non-standard invoiceReviewer's note with legal basis
AmountsDiffers from the agreementEvery invoiceQuote, order, timesheet
CompletenessSupply not invoiced by the 15thMonthlyDeliveries matched to invoices
NumberingGaps, duplicate numbers, jumpsMonthly, per seriesExplained number list
DuplicatesSame supply invoiced or sent twiceWeeklyReview by customer and amount
DeliveryPeppol send stuck or failedDaily or weeklyOutbox status, follow-up
SettlementUnrecorded money, money recorded that never came, refund owedWeekly or monthlyBank statement, Movement history
Corrections and write-offsNo reason or reference; refund unpaid; debt dropped without decisionMonthlyCredit note, reason, refund bank line, dated decision

OrdoGrid has no approval workflow: owners and administrators create and send documents and record payments directly. For separation of duties, give reviewers the Viewer role under Team: they can read documents but not create, send or record anything.

Before issuing: the pre-issue check

Run it before Save or Envoyer (Send). Articles refer to Royal Decree no. 1 unless stated otherwise.

  1. Issuing company. With several companies, the profile menu (Changer d'entreprise) decides who issues. In the preview header, name, address and TVA number must be the supplier's (art. 5 §1 2°). Companies and associations must also state their legal form, registered office, enterprise number, the RPM/RPR (register of legal entities) mention with the competent court and, where they have them, their email address and website (Companies and Associations Code, art. 2:20). Put what the header lacks, such as "RPM Liège, division Namur", in the field Mentions légales (pied de page des factures) on the Company profile page (titled Profil entreprise): OrdoGrid prints it in the footer of every invoice and credit note PDF, where you check it in the preview, and sends it in the Peppol invoice as the seller's additional legal information (BT-33).
  2. Customer. With Sélectionner un client, check name, full address and VAT number: all three are required on every full invoice to a VAT-registered customer (art. 5 §1 3°), not only under reverse charge. The client form shows the data source (Registre belge (BCE), the Crossroads Bank for Enterprises, or VIES (UE)). Numbers issued since September 2023 start with 1: BE1… is valid.
  3. Number and dates. Keep the number proposed in N° unless you have a documented reason. If the supply date or period differs from Date, state it (art. 5 §1 5°) in the line Description or in Notes: there is no separate field. Échéance (due date) is commercial, not a VAT requirement.
  4. Lines. Compare Quantité, Prix Unitaire, discounts and each line's TVA rate with the quote, order or timesheet. A full invoice shows, per rate, the taxable amount and the unit price excluding VAT (art. 5 §1 8°). With Prix unitaires TVAC (TVA incluse) ticked, the PDF shows VAT-inclusive unit prices and line totals only: the Peppol XML still carries net prices, but a PDF or paper invoice then lacks the unit price excluding VAT that art. 5 §1 8° requires, so use net prices whenever the PDF is the legal invoice. Expect a Rounding line (Arrondi) of a cent or two.
  5. VAT regime. In Options de TVA, OrdoGrid applies a regime by itself only when every line is already at 0% and the customer's location decides it: Export for a customer outside the EU, Autoliquidation for a business customer in another EU country. When a Standard invoice with every line at 0% is blocked, it suggests Régime cocontractant for a Belgian VAT-registered customer, together with its condition (works on immovable property for a customer that files periodic VAT returns), but never applies it by itself; it never suggests Régime de la franchise de taxe, which only a supplier under the small-business exemption may use. A suggestion is not a legal decision: have every non-standard regime confirmed and check the printed wording, the official mention on French and Dutch documents and a translation on English and German ones. See VAT regimes on Belgian invoices.
  6. References. If the customer requires a purchase order, N° bon de commande is mandatory. Peppol requires a buyer or order reference (rule PEPPOL-EN16931-R003); OrdoGrid uses the PO number, else the payment communication, else the invoice number. A final invoice must refer to earlier advance invoices and not charge their VAT again (art. 5 §1 11°).
  7. Channel. In Envoyer, for a customer on Peppol keep Envoi électronique via Peppol ticked and untick Email: OrdoGrid pre-ticks both when it can and sends them in parallel. If it shows Peppol — ignoré (Le client n'est pas enregistré sur le réseau Peppol), the invoice must still be issued, by email or on paper.
  8. Preview, then send. Check Aperçu du PDF, then click Sauvegarder & Envoyer (Save & Send). The list's globe button Envoyer à Peppol warns Action irréversible - Vérifiez le contenu avant d'envoyer: amounts lock once the send is prepared.

What OrdoGrid blocks, and what stays your job

In the app you see a message in your language, except those quoted in French below; integrations receive the code shown.

SituationOrdoGridYour control
Number already usedRefused on saveNone
Gaps or jumps in numberingNot detected: a deleted draft frees its number; the next proposal is the highest number + 1Monthly gap review
Standard regime with every line at 0%Blocked: Attention : Régime standard incompatible avec TVA à 0%None
Wrong regime, or suggestion accepted uncheckedNot detectedSecond-person review
Missing legal wording on a PDFNot detectedPre-issue step 5
Same invoice by email and on PeppolAllowedUntick Email
Second Peppol send of a delivered documentRefused: Déjà envoyé via PeppolNone
Editing amounts, VAT, customer or number after a payment or Peppol send, or on a saved credit noteRefused: DOCUMENT_FINANCIAL_CONTENTS_LOCKED or DOCUMENT_FINANCIAL_CONTENT_FROZENCredit note, never a recreated invoice
"Paid" status with no payment recordedRefused: PAYMENT_MOVEMENT_REQUIRED; choosing Payée opens Record paymentNone
Payment above OutstandingRefused: OVERPAYMENTFind where the excess belongs
Refund above Refund dueRefused: OVER_REFUNDCheck the credit note and bank debit
Credit notes above what remains creditableRefused: CREDIT_CAPACITY_EXCEEDEDReview earlier credits first
Reversing a movement twiceRefused: PAYMENT_ALREADY_REVERSEDCheck Movement history
Reversing a payment that was refundedRefused: PAYMENT_ALREADY_REFUNDEDReverse the mistaken refund first
Sending without approvalPossibleReview routine, Viewer role

Three states you must not confuse

QuestionWhereValuesDoes not prove
Where is the invoice in its life?Status in Invoices (page Factures)Brouillon, Envoyée, En retard (automatic from the start of the Échéance day), 1er rappel to Recouvrement, Abandonnée; Payée, Partiellement payée and Annulée derive from payments and creditsA reminder status sends nothing
Did the network deliver it?Peppol → OutboxTraité, En file, Nouvelle tentative, Erreur, Pas sur PeppolAcceptance or payment
Is it paid?Settlement panelUnpaid, Partially settled, Settled, Refund dueThat money moved: recording moves none

The customer's view arrives separately, as an Invoice Response shown on the invoice (AP accepted, RE rejected, UQ under query). Buyers are not obliged to send one.

Settlement lineAPI fieldControl rule
Invoice totaldocument_totalAmount payable as issued, rounding included: ties to receivables, not to net plus VAT
PrepaymentsprepaymentsAlready inside the next line
Payments (including prepayments)paymentsConfirmed money, net of reversals; never add prepayments again
CreditscreditsLinked credit notes, VAT included; not cash
OutstandingoutstandingTotal minus credits minus payments plus refunds, never below zero: the customer's open balance
Completed refundsrefundsEach matches a bank debit
Refund duerefund_dueZero, or on your refund list

The API settlement status is unpaid, partial, settled or refund_due. A classic spreadsheet error: a €40 deposit and an €81 balance on a €121 invoice show Payments €121; adding the deposit again gives €161 and a phantom overpayment.

Worked example 1: a VAT-inclusive invoice in the ledger

Papeterie Lemaire SRL in Namur sells from its VAT-inclusive price list to Bureau Delvaux SRL in Wavre. Invoice F-2026-0187 of 5 October 2026, sent on Peppol, has two lines at 21%: 6 binders and 6 notebooks at €11.50 each, VAT included.

FigureCalculationAmountTies to
Net per line6 × €11.50 ÷ 1.21 = €57.0248€57.02
Net total€57.02 × 2€114.04Revenue
VAT 21%€114.04 × 21% = €23.9484€23.95Output VAT at 21%
Legal total incl. VAT€114.04 + €23.95€137.99Peppol BT-112
Rounding€138.00 − €137.99+€0.01Peppol BT-114; account agreed with your accountant
Invoice total2 × €69.00€138.00Receivables

The control ties three figures, not one: output VAT to the VAT per rate, revenue to the net, receivables to Invoice total. Over a period, receivables minus net minus VAT must equal the sum of the rounding lines; any other difference is an exception. If Bureau Delvaux pays €137.99, Outstanding shows €0.01: agree once with your accountant how such cents are cleared, then apply that rule every time. See VAT-inclusive prices, discounts and rounding.

Worked example 2: mixed rates, a partial credit and a refund

Opleidingen Maes BV in Hasselt invoices Brouwerij De Kroon NV in Leuven on 2 October 2026, invoice F-2026-0214 on Peppol:

LineNetVATTotal
In-company workshop, 1 day€1,000.0021%: €210.00€1,210.00
20 printed course books at €10.00€200.006%: €12.00€212.00
Invoice F-2026-0214€1,200.00€222.00€1,422.00

De Kroon pays €1,422.00 on 12 October and returns the unused books on 14 October. Maes starts credit note NC-2026-0019 from the invoice with Note de crédit, keeps only the book line (€200.00 + 6% VAT €12.00 = €212.00) and sends it on Peppol, as the original was.

MomentPaymentsCreditsOutstandingCompleted refundsRefund dueHeader
12 October, paid€1,422.00€0.00€0.00€0.00€0.00Settled
14 October, credit note€1,422.00€212.00€0.00€0.00€212.00Refund due
16 October, refunded€1,422.00€212.00€0.00€212.00€0.00Settled

The control passes only when four things hold: Refund due is zero; a €212.00 bank debit of 16 October matches the Record refund entry; NC-2026-0019 refers to F-2026-0214, states the reason and, because returned goods are an art. 79 VAT Code case, carries "T.V.A. à reverser à l'Etat dans la mesure où elle a été initialement déduite" (Royal Decree no. 4, art. 4 §1; Dutch documents get the Dutch wording), which OrdoGrid adds automatically, on the PDF and in the Peppol XML, since the credit note credits Belgian VAT to a customer with a VAT number; and its €12.00 VAT is calculated at 6%, the rate of the credited book line, not 21%: in the VAT return for the period that includes 14 October (October or Q4 2026), your accountant reports €200.00 in grid 49 and €12.00 in grid 64, which are not split by rate. A Payée status proves none of this.

Correct the cause, never the history

What went wrongCorrectionIn OrdoGridDo not
Wrong price, rate, regime or customer on an issued invoiceCredit note referring to it, then a new invoice if neededNote de crédit, then Dupliquer or Nouvelle factureEdit it or reuse its number
Invoice sent to the wrong customerRecord it, credit it to that customer (FPS Finance FAQ, Q29), invoice the right oneFull credit note from the originalIgnore it
Same supply invoiced twiceCredit note for the duplicateNote de crédit on the duplicateHide or renumber it
Payment on the wrong invoice or for the wrong amountReversal, then the correct paymentReverse payment in Movement history, then Record paymentOffset it with a credit note
Refund recorded but never paidReversal of the refundReverse refundWait for it to "catch up"
Refunded payment to reverseRefund first, then paymentReverse refund, then Reverse paymentReverse the payment alone
Customer will not payNot a correction: reminders, collection, write-offAbandonnée after a documented decisionCredit a correct invoice
Written-off invoice paid after allReactivation, then the paymentSet the status to Brouillon and confirm Reactivate written-off invoiceRecord the money elsewhere

Reversals always cancel a whole movement: to change part of one, reverse it and record the right amount. A credit note's lines, amounts, customer and number lock at its first save, even as a draft, so remove unwanted lines before saving; afterwards only Notes and other non-financial fields can change, and it can never be deleted. An invoice sent only by email is not locked: Éditer ce document ? offers Éditer quand même (edit anyway), which regenerates the PDF, but the customer keeps the version it received under the same number, so treat it as issued. After a reactivation, set the invoice to Envoyée if a balance remains, so that the overdue check sees it. Writing off is only a label: it books nothing and changes no VAT; whether VAT on an uncollectible claim can be recovered is a question for your accountant.

Weekly and monthly reviews in OrdoGrid

  1. Numbering, monthly. In Invoices, set the month's date range and sort by Number. The series must continue from last month's last number; explain each gap (deleted draft, typed number) or jump in a note. Repeat in Credit Notes. A typo such as F-2026-0420 for F-2026-0042 makes OrdoGrid propose F-2026-0421 next: correct it while it is a draft. See Invoice numbering in Belgium.
  2. Drafts, weekly. Filter on Brouillon. A draft already holds its number. A draft printed or emailed outside OrdoGrid is issued but will never turn En retard: set it to Envoyée. Delete only drafts that never left the company.
  3. Completeness, before the 15th. Match last month's deliveries, timesheets and contract periods with the invoices issued (Royal Decree no. 1, art. 4).
  4. Delivery and responses, daily or weekly. In Peppol, tab Outbox, filter on Erreur and En file and use Vérifier. Delivery usually takes minutes to a couple of hours; FPS Finance advises contacting your provider after one working day, so contact OrdoGrid support. For Pas sur Peppol, send the invoice by email or post. After an RE or UQ response, stop reminders until the issue is resolved.
  5. Settlement against the bank. Rows in Invoices show Outstanding, and Refund due when you owe money. Match each bank receipt to a movement in Movement history with the same amount, date and reference, and each movement to a bank line. List separately: unmatched receipts, invoices with Refund due above zero, invoices showing Legacy payment evidence needs reconciliation., and non-euro invoices, reconciled in their own currency.
  6. Credit notes and write-offs, monthly. Each credit note names its invoice (Facture d'origine), states a reason in Notes, carries the Royal Decree no. 4 mention from worked example 2, which OrdoGrid adds, when it gives VAT back to a customer with a VAT number, used the original's channel and, if money went back, matches a Record refund entry. Each Abandonnée invoice has a dated decision known to your accountant.
  7. Duplicates, weekly. Sort Invoices by Client and look for equal amounts in the same period; check that no Peppol invoice was also emailed.
  8. Archive sample, quarterly. For three earlier invoices, one at least on Peppol, download the Original document from Settlement and the XML from Peppol → Outbox.

Keep the population and selection method with each result (date range, filters, sample), so that someone else can repeat the review and reach the same conclusion. Log each unexplained difference with owner, amount, currency, cause and due date, and keep it out of further automatic processing. Only the financial owner closes a difference in debt or cash. Recurring exceptions are a process problem to fix; hand what is still open to the controller at month-end.

API integrations: identity controls

  • Give each source transaction and payment one stable external_id, and each HTTP request an Idempotency-Key. Idempotency keys last 24 hours and belong to the API key that used them; external_id identities never expire.
  • An external_id is unique per company, integration and document type. The integration is the key's Integration ID (default default), which Rotate keeps. Give a hand-made replacement key the same Integration ID, or retries will no longer find earlier documents and can create duplicate invoices.
  • EXTERNAL_ID_REUSED means anything in the payload changed under the same external_id, even a description or email address. Decide which version is right; never bypass it with a new ID.
  • After a lost response, look the transaction up (GET /api/v1/invoices/lookup with its external_id) before retrying. After PEPPOL_TRANSMISSION_UNCERTAIN, check the delivery status before any resend.
  • Omit number so the company series assigns it. Send amounts with the currency's decimals: extra precision is refused (INVALID_AMOUNT_PRECISION), as are partial reversals (REVERSAL_AMOUNT_MISMATCH) and unsupported VAT treatments (UNKNOWN_VAT_TYPE, before numbering). GET /api/v1/me returns the key's company, integration_id and capabilities: currencies, payment methods, margin schemes.

Retry design: integration reliability; full contract: API reference.

Evidence to keep

  • Before issue: the commercial source and, for non-standard VAT, the reviewer's note and proof of the customer's status.
  • As issued: the Original document PDF and, for Peppol, the XML from Peppol → Outbox; FPS Finance strongly recommends keeping the original XML.
  • Delivery: the Outbox status and any customer response.
  • Settlement: bank statements, Movement history and the Current statement downloaded at each review.
  • Corrections: credit notes with reasons, the customer's agreement, refund bank lines, write-off decisions.
  • Reviews: population, filters, sample, result, reviewer, date, and the exception log.

Keep invoices and evidence for 7 years from 1 January of the year after issue (VAT Code art. 60, as amended by the Law of 18 December 2025), longer for documents tied to VAT revision on immovable property. OrdoGrid is not a legal archiving service and gives no retention guarantee: see Invoice archiving in Belgium.

FAQ

Can I correct an invoice after the customer has paid it?

Not by editing it. Once a payment is recorded or the invoice is prepared or sent on Peppol, OrdoGrid locks its amounts. Issue a credit note that refers to it (Royal Decree no. 1, art. 12) and, if needed, a new invoice with a new number.

The customer paid an invoice twice: what do I record?

The payment that settles the invoice; OrdoGrid refuses the second because it exceeds Outstanding. Ask whether the excess should cover another open invoice (record it there, with the customer's written confirmation) or be refunded. A bank refund of an unrecorded excess stays outside Settlement, so give the bank evidence to your accountant.

The customer paid the wrong invoice: how do I fix it?

Ask which invoice the money was meant for and record it there. If it is already recorded on the wrong one, use Reverse payment there, then record it on the right invoice with the bank's date and reference.

What do I do with a bank receipt I cannot match?

Record nothing yet. Put it on an unmatched list with date, amount, payer and reference, ask the payer, and hand it to your accountant at month-end if still open. Never apply it to the oldest open invoice by default.

Does OrdoGrid have an approval step before an invoice is sent?

No. Owners and administrators can send directly. Build the review into your routine: the PDF preview, a second person for non-standard VAT and credit notes, and the Viewer role for people who must see but not change anything.

Do credit notes need their own number series?

No. Belgian law allows one or several series and records credit notes in the same outgoing-invoice book (Royal Decree no. 1, art. 5 and 14). OrdoGrid uses a separate NC- series by default; what you control is that each series has no unexplained gaps.

Sources and references