What a Payment Reference Carries
The reference field survives the journey or it does not, and when it does not the money arrives anonymous.
Still yours, and statedTaken, never statedUnit changes; scale restarts
Four steps from instruction to arrival. One step carries no figure: the hatching marks where the money leaves and is not drawn to scale, because there is no figure to draw. Nothing here adds them up, since an amount you cannot see is not an amount you can subtract. One line, two facts, and a gap where the rest of the journey was.
The reference is free text the payer types, and whether it reaches you intact depends on how many systems the payment passed through and what each of them does with free text.
The evidence question in “What a Payment Reference Carries” calls for records that can be reconciled rather than one unexplained total. For teams exploring productivity software for business, see the product in its original context can supply time and project context, provided corrections remain visible and the payment provider or bank remains authoritative for settlement and currency data.
When it does not survive, money arrives with no indication of what it is for, which is a different problem from money not arriving.
As a separate reference point for “What a Payment Reference Carries”, see European Bank for Reconstruction and Development. Confirm broad guidance against current provider disclosures and qualified financial or tax advice where needed.
What the field is for
Telling you which invoice, which month or which piece of work a payment covers. Nothing in the banking system requires it or checks it.
It exists because people need it, and it is treated accordingly by the machinery.
That is worth understanding before blaming anybody. The field is carried as a courtesy by systems designed to move value, not information about it.
Why it gets damaged
Length limits differ between systems, character sets differ, and some institutions prepend their own text. A reference passing through three systems can lose its end, its punctuation or all of it.
Nobody is doing anything wrong. Each system is applying its own format to a field that was never standardised.
How long is safe
Short. Twelve to sixteen characters survives almost everywhere. Thirty-five is the limit in several schemes and is frequently truncated earlier in practice.
A reference that still identifies the payment after being cut at sixteen characters is a reference that works.
Test it once by looking at what arrived on a real payment, rather than by trusting a published limit.
What to ask the payer to put in it
An invoice number and nothing else, or a short code plus a month. Not your name, which is already elsewhere, and not a sentence.
Give them the exact string you want, once, in writing. People type what they are given.
Put it on the invoice as well, labelled as the payment reference. A finance clerk copying from an invoice will copy whatever is beside that label.
Avoiding characters that break
What survives, roughly in order:
- Letters and digits, everywhere.
- Hyphens, almost everywhere.
- Spaces, usually, though they may be collapsed.
- Slashes, ampersands and accented characters, unpredictably.
- Anything outside the basic set, rarely.
Design the reference so that it contains nothing but letters and digits and you remove a class of problem entirely.
When nothing arrives in the field
The credit shows the sender's name and a bank's transaction identifier and nothing else. You know who paid and not what for.
Where a payer sends one payment a month this is tolerable. Where they send several, it is a reconciliation problem with no solution at your end.
Structured references
Some countries and schemes have a formal reference format with a check digit, designed exactly for this. Where both ends support it, it survives reliably and can be matched automatically.
Worth asking about if your corridor has one. Most people have never heard of it and it solves the problem completely.
Asking the payer what they sent
Where a reference arrives damaged, the payer's confirmation shows what they typed. Comparing the two tells you whether the problem is at their end or in the chain.
If they typed it correctly, nothing you do will fix it and the answer is to shorten it.
Matching without a reference
By amount and date, which works while amounts differ and fails the moment two are the same.
Where you are reduced to this, ask the payer for a remittance advice each month. It is a separate document and it is the proper fix.
Your own naming
Keep invoice numbers short, sequential and free of punctuation, for exactly the reasons above.
An invoice number designed to survive a payment reference is a small act of foresight that pays for itself for years.
When the reference is the evidence
For tax, for a dispute, or for proving which invoice was settled, the reference on the credit is the link between a payment and an obligation.
A payment with no reference is harder to attach to anything later, which matters more than it seems at the time.
What the field cannot do
Travel with meaning it was never given. A payer who writes nothing, or writes their own internal code, produces a credit you cannot interpret, and no amount of asking your bank will recover it.
Everything about the reference is decided before the payment leaves. That makes it one of the few things in this whole collection that is fixed entirely by a conversation at the start, and one of the few where the payer bears no cost at all for doing it properly.
It also costs them nothing, which makes it the easiest request in this entire collection and the one most reliably forgotten.