Structured communication (OGM/VCS): matching payments to invoices
UnsplashEvery self-employed person knows the scene: a transfer arrives on the business account with "invoice" or "payment June" as its only message, and you have to guess which of three open invoices it pays. Multiply that by fifty clients and reconciling the bank becomes a monthly chore. Belgium has had a simple answer for a long time: the structured communication, called OGM in Dutch and VCS in French.
This article explains what it is, how it is built, and how to use it so that payments link themselves to the right invoice.
UnsplashWhat a structured communication is
A structured communication is a 12-digit payment reference that you print on your invoice. The client copies it into the "structured communication" field of the transfer, instead of typing a free message. When the money arrives, the reference comes back with it, unchanged.
- OGM stands for overschrijving met gestructureerde mededeling.
- VCS stands for virement avec communication structurée.
Both names describe the same Belgian standard, maintained by Febelfin, the federation of the Belgian financial sector. The banks in Belgium support it for SEPA credit transfers, SEPA instant transfers and SEPA direct debits.
How the 12 digits are built
The format is always the same: three blocks of 3, 4 and 5 digits, between plus signs.
+++123/4567/89002+++
| Part | Digits | Role |
|---|---|---|
| Base number | First 10 digits | Your own reference, often derived from the invoice number or client number |
| Check digits | Last 2 digits | Remainder of the base number divided by 97, or 97 if the remainder is 0 |
In the example above, the base number is 1234567890. Divided by 97, it leaves a remainder of 2, so the check digits are 02. The check digits can never be 00: when the division leaves nothing, the check becomes 97.
That check is what lets a banking app refuse a mistyped reference. If one digit is wrong, the remainder no longer matches and the transfer form flags it before the money leaves.
Why it matters for payment matching
Without a structured reference, matching a payment means comparing amounts, names and dates by hand. That works for ten invoices a month. It breaks down when:
- two clients pay the same amount on the same day,
- a client pays several invoices in one transfer,
- the payer is not the client itself (an accountant, a parent company, a spouse),
- the message field says only "invoice".
With a structured communication, the reference arrives as data, not as text. An invoicing or bookkeeping tool can read it from the bank statement and mark the right invoice as paid.
UnsplashPutting it on the invoice correctly
A structured communication only helps if the client actually uses it. A few practical points:
- Show it clearly near the amount and the IBAN, in its +++ form, so it is easy to copy.
- Add one line of instruction: "Please use this structured communication when paying."
- Include it in the payment QR code if your invoices have one, so a phone banking app fills it in automatically. Febelfin has published Belgian guidelines for that QR code. [TO VERIFY: the date and content of the current Febelfin guidelines for the payment QR code on invoices.]
- Carry it in the Peppol invoice too. A structured electronic invoice has a field for the payment reference, so the client's software can prepare the transfer with it.
When the client does not use it
Some clients will still type a free message, or pay two invoices at once. The structured communication reduces manual work, it does not remove it.
- For a combined payment, match it against the open invoices of that client whose total equals the amount.
- For a partial payment, record the amount received and keep the remaining balance open on the invoice.
- For a payment with no reference, look at payer name and amount, then confirm with the client if needed.
A short reminder in your next invoice or e-mail ("one transfer per invoice, with the structured communication") usually fixes the habit.
Structured communication and the RF reference
You may also see a reference starting with RF followed by two check digits and up to 21 characters. That is the international creditor reference (ISO 11649), usable across the SEPA area. It also uses a modulo 97 check, but on a different formula.
For Belgian clients, the OGM/VCS is the familiar choice, and Belgian banking apps offer a field for it. For clients abroad, the RF reference is often easier for their bank to handle.
| OGM/VCS | RF reference | |
|---|---|---|
| Scope | Belgian standard | International (ISO 11649) |
| Format | 12 digits, +++xxx/xxxx/xxxxx+++ | RF + 2 check digits + up to 21 characters |
| Check | Modulo 97 on 10 digits | Modulo 97, IBAN-style |
| Best for | Belgian clients | Clients in other SEPA countries |
Let the software generate it
The check digits are easy to compute but easy to get wrong by hand. The safest approach is to let your invoicing tool create a structured communication for every invoice, print it on the PDF, put it in the Peppol data and use it to mark the invoice as paid when the transfer comes in.
Shark-it, the invoicing app by TRUE DATA, tracks payments on every invoice, finds a client from its VAT number, and sends and receives invoices through Peppol in every pack, on the web, iPhone and Android. You can try it at shark-it.be.