Structured payment communication (OGM) for Belgian invoices
What Belgian structured payment references (+++/+++/+++) are, when to put them on invoices, and how they close the reconciliation loop with Peppol structured invoices.
Updated
- Belgium
One job: link the payment to the invoice
Peppol delivers a structured invoice. A Belgian structured payment communication (OGM / communication structurée / gestructureerde mededeling) links the bank transfer back to that invoice. Without it, you can book the receivable automatically and still match cash by hand.
Visible form: +++123/4567/89012+++. Twelve digits, modulo-97 check, carried in SEPA remittance data so banks and accounting tools can match without reading free text.
- Structured payment communication (OGM)
Belgian twelve-digit payment reference with modulo-97 check digits, shown as +++123/4567/89012+++, used to match bank transfers to open invoices.
When to use it
| Situation | Use OGM? | Why |
|---|---|---|
| Domestic B2B invoice paid by Belgian bank transfer | Yes | Highest automatic match rate |
| Payment reminders / dunning for the same invoice | Yes (same reference) | Keeps one key across follow-ups |
| Partial payments expected | Yes, still | Identifies the invoice; amount needs exception handling |
| Foreign payer / free-text remittance culture | Optional | Format may not be entered or validated abroad |
| Direct debit / card / cash | Usually no | Different payment rails |
OGM does not replace the legal invoice number. Numbering stays continuous for VAT and audit; OGM is a payment-layer key next to IBAN/BIC.
Format (enough to operate)
| Segment | Digits | Role |
|---|---|---|
| Block 1 | 3 | Payload |
| Block 2 | 4 | Payload |
| Block 3 | 5 | Payload + 2 check digits |
First ten digits encode your reference (often derived from invoice number). Last two are modulo 97 (use 97 when remainder is 0). Generate in software; never invent check digits by hand.
Peppol invoice + OGM = closed order-to-cash
| Layer | Mechanism | What it automates |
|---|---|---|
| Invoice exchange | Peppol / UBL | Booking the bill (AP/AR) |
| Payment reference | OGM on the invoice | Matching the bank receipt to that bill |
| Bank feed | CODA / camt.053 | Importing movements with remittance fields |
Practical setup:
- Generate one OGM per open invoice when you finalize.
- Put it in structured payment means / remittance fields and on the human payment block.
- Instruct the customer to copy it exactly.
- Configure bank import to prefer structured remittance over free text.
| Without OGM | With OGM |
|---|---|
| Match by amount + name guesswork | Match by exact reference |
| Same-amount invoices collide | Each invoice stays unique |
| Peppol books AR; treasury still manual | Peppol books AR; bank clears AR |
OGM proves identity of the payment instruction, not that the amount is correct. Grouped remittances and credit notes still need exception rules. For document roles, see invoice, credit note, and quote. For the e-invoicing mandate context, see Belgian structured e-invoicing obligation (2026).