Payments - Introduction / Learning brief
Misc Payment Concepts
Your notes
In simple terms / 01
What this means in plain language
Provides a compact glossary of foundational terms such as SWIFT, SEPA, ISO 20022, payment infrastructures, and related standards.
Payment terminology becomes manageable when each term is tied to a layer. A scheme defines common rules. A network transports messages. A clearing mechanism exchanges instructions and may calculate obligations. Settlement completes the financial obligation between participants. ISO 20022 provides a structured business-message standard, while SWIFT and SEPA describe different kinds of industry arrangements. Accounts, identifiers, controls, and reporting connect the layers. Instead of memorizing isolated definitions, draw one payment and label where each concept acts, who owns it, and what evidence shows that the step completed.
Complete lesson / 02
Understand the full idea, step by step
Some of the most consequential words in payments are the small ones. A date that is not the date you think. A deadline that quietly re-routes your afternoon. A reference that either survives the journey or ruins the reconciliation. This brief collects five such concepts — small, sharp, and used every single day on an operations desk.
Booking date vs value date
Two dates ride on every entry, and they answer different questions. The booking date says when the bank wrote the entry into the account. The value date says from when the money counts — the date used to calculate interest and, often, availability. Usually they match. When they differ, the value date is the one the money cares about: an entry booked Monday with Friday's value date earns (or costs) interest as if it had happened on Friday.
Cut-off time
The last moment a bank or scheme accepts an instruction for today's processing. Miss it and the payment is not lost — but its path changes. Depending on the rail and the bank's rules it may be queued for the next window, re-dated to the next business day, re-routed to a faster rail (possibly at a different price), sent for repair, or rejected back to the sender. "It missed cut-off, so it arrives tomorrow" is a guess, not a rule — the actual outcome depends on what the bank's processing does next.
Back-valuation
The repair tool for a wrong date. If a payment that should have carried Friday's value date is only processed on Monday — say, because a bank delayed it — the bank can post it on Monday with Friday's value date. The customer's interest position is then exactly as if the payment had been on time. That is Maya's first puzzle solved: Friday's date on Monday's entry usually means someone put a delayed payment right.
End-to-end reference
The reference the payer assigns for the payee — "INV-2214", "RENT-JULY" — meant to travel unchanged through every bank and system in the chain, so the payee can match money to the reason for it. It is distinct from the technical references each bank and system adds for its own tracking. When a system truncates or drops the end-to-end reference, the money still arrives, but the story does not: Arjun's missing reference is exactly this failure, and reconciliation is its victim.
Finality (and the cool-off before it)
Before a payment executes, there is often a window in which it is merely a stored instruction — a future-dated transfer can usually be cancelled, because nothing has happened yet. Finality is the legal moment that window closes: once a payment settles, it is unconditional and irrevocable. After that, getting money back is a request, not a command — a recall or return that the other side may grant or refuse. Riya's hour-old payment has almost certainly passed that line.
COMMON CONFUSION
“A payment can always be cancelled if you act quickly enough.”
It depends entirely on where the payment is in its lifecycle. An instruction not yet executed can usually be cancelled. One that has settled is final: the sender's bank can only ask the beneficiary's side to return the money, and on many rails — especially instant ones — the executed state arrives within seconds of pressing send. Speed of regret does not reopen a settled payment.
REMEMBER IT
Five small words, one line each: booking says when the entry was written; value says when the money counts; the cut-off decides which day; back-valuation repairs the day; the reference ties the story together — and finality ends it.
FOR NOW, REMEMBER
- Booking date records the entry; value date drives interest and availability — and they can legitimately differ.
- Missing a cut-off has several possible outcomes — queue, re-date, re-route, repair, reject — never assume "tomorrow" without checking.
- Back-valuation posts a delayed payment with the value date it should have had, making the customer whole on interest.
- The end-to-end reference exists for the payee's reconciliation and must survive the chain unchanged; technical references belong to the banks.
- Cancellation only exists before execution; after settlement, finality means recovery is a request to the other side.
TRY IT YOURSELF
A corporate account shows a credit **booked Monday 14 July** with **value date Friday 11 July**. The bank had held the payment over the weekend for a processing fault of its own. What is the best reading?
Each of these small concepts marks a point on one journey — instructed, executed, settled, posted. The payment lifecycle topic assembles that journey end to end, so every date, deadline, and reference has a place on the map.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Classify each term as a rule, message, network, process, or account concept.
- 02
Similar payment words can describe different layers.
- 03
A labeled end-to-end flow makes definitions practical.
Practical use cases / 04
Where you would use this
A new joiner builds a glossary linked to the bank's actual payment architecture.
A business analyst resolves a requirement that incorrectly treats messaging and settlement as the same event.
A trainer asks learners to label scheme, network, clearing, and account steps on one transfer.
Worked example / 05
Put the idea into a real situation
Take a cross-border instruction sent in a standard message. ISO 20022 may define the structure, a network may carry it, a bank's payment engine may validate and route it, and correspondent or infrastructure accounts may support settlement. Customer reporting then communicates the result. These pieces cooperate but are not interchangeable. The example is deliberately generic so learners can replace each layer with the actual scheme, message, provider, and account arrangement used in their organization.
Evidence & review / 07
Evidence & review
General account-to-account payment concepts; exact cut-off outcomes, cancellation windows, and value-dating rules vary by bank, scheme, and jurisdiction
What this brief simplifies: Treats each concept generically rather than under one scheme's rulebook; omits jurisdiction-specific value-dating regulation and scheme-specific recall procedures.
Sources for this brief2
- Market practiceMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements · Settlement finality and value-date terminology
Terminology has evolved since this edition; newer CPMI publications refine some definitions.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.