Rails
Settlement Window
Settlement window is the period after a payer sends money but before the receiving bank reflects it as fully posted. On South African rails, that gap can sit between authorisation, interbank clearing, and the final account update. Teams need plain notes here because a customer may have proof of payment while operations still cannot release stock, access, or service.
Bank-side lag after send
Settlement Window explains the gap between a payment being sent, cleared, and reflected on the bank side. It is written for South African teams that need cleaner handovers when customers ask why money moved but the status still looks unfinished.
A useful handover note should state which rail was used, what status the payer can see, and what the receiving side still lacks. PayShap, Instant EFT, card-to-bank flows, and DebiCheck collections do not move through the same checkpoints, so the settlement window changes with the method. In South Africa, staff often need wording that fits phone calls, counter queries, and order desks without slipping into bank jargon.
Capture the amount, beneficiary reference, payer name, and timestamp before anyone starts chasing the bank. Those four items usually decide whether the issue is a delayed bank reflection, a mismatched reference, or a payment sent on the wrong rail. A short internal note next to the order saves a lot of repeated checking later in the day.
Settlement stages your team will see
Sent, cleared, and available need to stay separate, because those words often get treated as if they mean the same thing. Finance may see one status, support may hear another from the customer, and fulfilment only wants to know whether goods can move. Clear wording reduces bad handovers between checkout, recon, and dispatch.
Link settlement-window to the exact customer message, then compare the bank-side status with the reference on your own system before you escalate.
- Sent time recorded against the order
- Beneficiary reference checked character by character
- Counter script for payment status queries
SA payment timing conditions
Settlement windows are shaped by how South African banks post incoming funds, especially outside peak business handling periods. A payment can leave the customer account quickly while the receiver still waits for bank-side reflection, treasury visibility, or a successful automated match. That matters in places such as Johannesburg fulfilment hubs, Durban service desks, and Cape Town booking teams where release decisions happen throughout the day.
Branch traffic changes the wording people need at the counter. Load-shedding affects when staff can verify a transfer and save proof, while courier cut-offs limit how long dispatch can wait for bank reflection. A walk-in payment query needs plain banking language, not terms lifted from scheme manuals.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
What to capture in handover
When briefing a settlement window issue, include the rail used, the payer proof, and the exact status your bank portal still shows. Add the operational consequence as well, such as dispatch hold, booking delay, or failed auto-allocation. Specific detail beats a vague note that money has not reflected yet.
When a proof request or release check comes in, file the settlement note with the order record while the references are still visible. Pair it with a process note and a resource sheet when finance or ops needs a checked handover.
What our Real-Time Payments customers say
Verified Google reviews