How a payment picks its rail

A rail is a clearing scheme your organisation can send money on. Most markets offer more than one, and they differ in speed, cost, and how much they will carry.

You do not choose the scheme. You say how fast the payment needs to be, and the system picks the first rail that can carry it.

The Raised Under column on the Direct Credits tab is not about the rail. It says who raised the payment — see who raised a direct credit.

The ladder

Your organisation configures its rails in order, fastest first. A payment tries each one in turn and takes the first that fits.

flowchart TD
    A["Payment raised"] --> B{"Instant rail fits?"}
    B -- "Yes" --> C["Sent in seconds"]
    B -- "No: too large, or<br/>not fast enough to need it" --> D{"Same-day rail fits?"}
    D -- "Yes" --> E["Cleared today"]
    D -- "No" --> F["Next-day batch"]

Four things decide whether a rail fits.

Test What it asks
Addressing Can this rail reach the beneficiary — by account number, or by proxy?
Amount Is the payment within the rail’s limit?
Service level Does this rail serve the speed the payment asked for?
Cut-off Has the rail closed for today?

The first three decide which rail carries the payment. The fourth decides when it settles — see Cut-off times below.

Service levels

A payment declares what it needs of the clearing system. There are three.

Service level What it means
Non-urgent Ordinary. Cheapest rail that can carry it.
Urgent Send it now, and pay for the speed.
Same-day value The money must be with the beneficiary today.

These are the standard ISO 20022 service levels, so a service level means the same thing here as it does on the wire. See the standards register row for ISO 20022 — ExternalServiceLevel1Code.

A payment that says nothing is non-urgent. That matters: a rail that serves only urgent payments charges an urgent fee, and a payment nobody marked urgent should never quietly pay it.

Why a fast rail does not take everything

A rail declares which service levels it serves. A rail that names none serves them all.

Suppose your organisation adds a same-day rail above its next-day batch. If the new rail named no service levels, every ordinary payment would take it, because it is higher in the order and always fits. Every interest payout, every account closure, on a paid rail nobody asked for.

Naming the levels a rail serves is what prevents that.

The payment asks for The rail it takes
Non-urgent The next-day batch
Same-day value The same-day rail
Urgent The same-day rail

An urgent payment over the fast rail’s limit still falls through to the batch. A limit is a test of fit, not a refusal — the payment goes out, more slowly.

Cut-off times

A rail closes at a time each day. A payment approved after it stays on the same rail and settles one business day later. It is not moved to another scheme.

That is what a cut-off means in banking, and it is why the date you are quoted can move when the payment is approved.

Take a rail that closes at 16:00 and normally settles the next business day:

Approved at Settles
15:30 Next business day
16:30 The business day after that

The cut-off is read in the rail’s own market. A rail that closes at 16:00 in Johannesburg closes at 16:00 there, whatever time it is where you are sitting.

When the date changes

The date you see when a payment is captured is provisional. It becomes firm at approval, because approval is when the rail is really chosen.

A revised date is always later than the one first quoted, never earlier. Someone told the money arrives tomorrow, who is paid in seconds, is pleasantly surprised. Someone told it arrives today, who waits a day, has been misled.

Every revision is recorded with who approved the payment and when, so you can always see why a date moved.

An account operation’s payout

An account operation, such as paying out an account’s balance, is dated before its fee is known. The fee depends on the rail, and the amount paid depends on the fee. So the operation’s payout is dated on the slowest rail its speed allows.

Take a same-day rail capped at R50,000, above a next-day rail:

Payout Run on Dated
R20,000 balance Tuesday Wednesday

If the payout then clears on the same-day rail, the customer is paid a day sooner than the date shows. The date is never earlier than the money moves.

Which speed a payment asks for

The speed comes from what the payment is for, not from who raises it.

Your organisation sets a service level against each purpose it pays for — an interest payout, a maturity, a disbursement. Every payment for that purpose asks for that speed, without anyone deciding it payment by payment.

A payout on an account type takes its speed from that account type. You choose it on the account type’s Payment Speed panel — see Setting a payout’s speed. A payout is dated on the rail its speed picks, so an urgent payout can be dated today while a standard one is dated tomorrow.

Bank default and Standard

A payout set to Bank default asks for your organisation’s default speed. A payout set to Standard always asks for an ordinary payment.

Your default Bank default payout Standard payout
Standard Ordinary payment Ordinary payment
Urgent Urgent payment Ordinary payment

Payouts that post the same transaction type share one speed. Changing one changes them all.

A purpose can also be marked so that its speed cannot be overridden. That is a policy your organisation sets, and the system enforces it when the payment is raised — not by hiding a control.

Real-time clearing

Some markets offer a real-time credit scheme that clears against an ordinary account number, settling in seconds rather than overnight.

This sits between an instant proxy payment, which is capped and needs the beneficiary’s proxy, and the next-day batch, which carries anything. It gives you a third tier: fast, addressed the ordinary way, and available for any amount your organisation permits.

Two things are worth knowing about it.

South Africa’s scheme is Real Time Clearing. See the standards register row for BankservAfrica Real Time Clearing (RTC), South Africa.

What your organisation configures

Rail settings are staged in Studio and take effect when the staged changes are published, so a change is reviewed before it moves any money. The change is recorded, with who published it.

From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.