How a payment declares what it is
Service level, local instrument, category purpose, purpose, and priority — the fields that tell everyone what kind of payment this is, and the 4-letter codes they carry.
IN ONE LINE
Analogy: a parcel does not just carry an address — it carries labels.
'Fragile', 'This way up', a customs code saying what is inside, a service sticker saying 'next-day' or 'economy'.
Anyone handling the parcel reads the labels and treats it accordingly, without opening it.
An ISO 20022 payment works the same way.
Alongside the amount and the parties, it carries small coded labels that say what kind of payment this is and how to handle it: which scheme it runs under, whether it is instant, what it is for, and how urgent it is.
Each label is a short code — usually four letters — from an agreed list, so a bank on the other side of the world reads 'SALA' or 'SEPA' and knows exactly what is meant.
WHAT IT ACTUALLY IS
Four elements do most of this labelling, and it helps to keep them apart.
Service level (SvcLvl) names the rulebook the payment runs under — for a euro retail payment that is the code SEPA.
Local instrument (LclInstrm) narrows that to a variant, such as INST for SEPA Instant.
Category purpose (CtgyPurp) tells the banks in the chain what kind of payment this is — SALA for salary, SUPP for a supplier — so they can apply special handling.
Purpose (Purp) states the reason for the payment for the creditor's benefit, carried unchanged from debtor to beneficiary.
On top of these, instruction priority (InstrPrty) is a coarse urgent/normal flag.
The useful mental model: service level and local instrument say 'how it is carried', category purpose says 'what kind, for the banks', and purpose says 'why, for the customer'.
HOW IT WORKS
Two confusions cause most mistakes.
First, category purpose versus purpose: they draw on overlapping 4-letter code lists (both can say SALA), but category purpose is read by the banks to route or prioritise, while purpose is informational for the creditor.
Putting the reason only in one of them, or assuming a bank acts on the customer-facing purpose, misfires.
Second, charge bearer: the ChrgBr element decides who pays the banks' fees — DEBT (debtor pays all, the beneficiary gets the full amount), CRED (creditor pays all), SHAR (each side pays its own), or SLEV (follow the service level, which the SEPA schemes require).
These map to the MT103's OUR / BEN / SHA.
Reading a payment well means reading these labels together: the service level sets the rules, the purpose codes set the intent, and the charge bearer sets who pays for the trip.
THE WORDS
- External code set
- A published list of allowed values for an ISO 20022 field, maintained separately from the message schema so codes can change without reissuing the schema.
READ FIRST
CONNECTED TO
SOURCES
- ISO 20022 External code sets — ISO 20022 Registration Authority
- ISO 20022 Catalogue of messages — ISO 20022 Registration Authority
- 2025 SEPA Credit Transfer rulebook — European Payments Council
- Payments Signal editorial teaching models — Payments Signal
Derived from How a payment declares what it is. Every claim on this card is sourced on that page.