Structured remittance information: make payment references useful to automated reconciliation

Structured remittance information carries payment-reference data in defined fields so the recipient can match cash to invoices without interpreting free text. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What structured remittance information means in practice

Structured remittance information carries payment-reference data in defined fields so the recipient can match cash to invoices without interpreting free text. The commercial effect often appears before accounting catches up, so treasury should identify the exact event that changes the position.

The benefit appears only when the payer creates accurate structured data, intermediaries preserve it and the recipient's system actually consumes the fields. A practical procedure should say exactly who checks the condition, when it is tested and where the supporting record is retained.

How structured remittance information works from start to finish

The operating file should contain invoice number, creditor reference, remittance field used, character limits, message standard, bank mapping, intermediary treatment and ERP matching logic. Bringing those facts together prevents legal, treasury and accounting teams from reaching different conclusions about the same event.

Operational ownership should follow the transaction through to its final state. The person who initiates an action does not need to perform every later step, but the business must know who owns unresolved exceptions.

The data and evidence that matter

Evidence also needs a retention location that survives staff turnover. A material structured remittance information decision should be understandable from the treasury or finance record without depending on a private mailbox or one employee's memory.

An effective record should also make the exception path visible. If the normal rule cannot be met, the team should capture who approved the deviation, how long it applies and what evidence will close it. For structured remittance information, that distinction prevents a temporary workaround from becoming an undocumented permanent practice. For structured remittance information, the specific checkpoint is this: Define reference standards with accounts payable and receivables teams, validate them before transmission and monitor unmatched receipts after implementation.

Where the process can fail

A company can invest in ISO 20022 connectivity but still send 'INV PAYMENT' in free text, losing most of the reconciliation benefit. The financial exposure can grow quickly when the issue is discovered close to settlement, drawdown or payment day.

Deadline pressure can also weaken controls. If the process depends on an emergency override every month, the underlying timetable is wrong and should be redesigned rather than normalising exceptions.

Worked example: test the mechanics

A customer pays £96,420 covering 14 invoices. A free-text line lists only the first few invoice numbers before truncation. Structured remittance can carry references in a machine-readable form, allowing the recipient to allocate the receipt without a manual spreadsheet if both banks and systems preserve the data.

This example is a method rather than a universal rule. The business should replace every illustrative figure with its own contractual terms, bank data and dates, then test the result before assuming that cash or authority is available.

Governance and controls for structured remittance information

Define reference standards with accounts payable and receivables teams, validate them before transmission and monitor unmatched receipts after implementation. A reviewer should be able to see the rule, the data used and the final status in one case file without rebuilding the chronology from emails.

Monitoring should focus on unresolved items and ageing. For structured remittance information, management gains more from seeing exceptions that are approaching a deadline than from a report showing only how many transactions completed successfully.

Senior review is most valuable where judgement remains. Automated controls can check limits and formats, but unusual legal, liquidity or counterparty issues still need an accountable person to decide whether the business should proceed.

Decision records should separate three layers: what the governing document or payment scheme allows, what the bank or counterparty operationally supports, and what internal policy permits. Those layers can produce different answers, and structured remittance information is safest when the difference is explicit before the transaction proceeds. In this workflow, the supporting record should cover invoice number, creditor reference, remittance field used, character limits, message standard, bank mapping, intermediary treatment and ERP matching logic.

The review should use invoice number, creditor reference, remittance field used, character limits, message standard, bank mapping, intermediary treatment and ERP matching logic and should identify which item would force the team to pause, obtain consent or change the planned date. A useful challenge question is whether the transaction would still be safe if a company can invest in ISO 20022 connectivity but still send 'INV PAYMENT' in free text, losing most of the reconciliation benefit. Where that answer is uncertain, define reference standards with accounts payable and receivables teams, validate them before transmission and monitor unmatched receipts after implementation. This makes the control decision-focused: staff know what evidence is sufficient, what is still unresolved and which person can accept an exception.