What Are Payment Cut-Off Times and Value Dates?

A cut-off time is the deadline by which a payment instruction must be submitted to be processed in a given cycle, and a value date is the date on which the payment takes effect. Together they explain one of the most common payment questions in South Africa: why a payment made today only reflects tomorrow — or, around a long weekend, several days later.

Cut-offs and value dates matter most for batch rails such as EFT credits and debit orders. Real-time rails like PayShap largely remove the problem, which is one of their main advantages.

What is a banking day?

A banking day (or business day) is a day on which the interbank clearing and settlement systems run normal processing cycles. In South Africa:

• Banking days are Mondays to Fridays that are not public holidays.
• Non-banking days are Saturdays, Sundays and South African public holidays.

Batch payments submitted on or for a non-banking day are not processed that day — they are handled according to the rail's date rules. Real-time rails such as PayShap operate every day of the year, including weekends and public holidays.

What is a submission cut-off time?

Each batch processing cycle has a submission deadline. Instructions received before the cut-off are included in that cycle; instructions received after it roll into the next cycle, which may be the next banking day.

Practical implications:

• An EFT credit sent before your bank's cut-off on a banking day typically reflects the same day or the next banking day; sent after the cut-off, add another banking day.
• Debit order collections must be submitted before the cut-off ahead of the action date. Kwik publishes its submission deadlines so collections are always delivered to the banks in time — see Action dates and processing cycles.
• DebiCheck adds an earlier step: the mandate must be authenticated before the collection can be submitted, so plan for both deadlines.

Exact cut-off times differ by bank, rail and provider, so always work from the published deadlines that apply to your setup rather than a general rule.

What is a value date?

The value date is the date a payment is treated as taking effect — the date interest, availability of funds and the action of a debit order are anchored to. It is not always the same as:

• Submission date — when the instruction was sent, which may be one or more days earlier.
• Statement date — when the entry appears on a statement, which can lag the value date.

For debit orders, the value date is the action date: the day the payer's account is debited, agreed in the mandate.

What happens when the action date falls on a weekend or public holiday?

Batch debits cannot be processed on non-banking days, so the date must be adjusted. The standard convention for debit orders is to collect on the previous business day when the agreed action date falls on a Saturday, Sunday or South African public holiday.

For example, if a monthly debit order runs on the 1st and the 1st is a Sunday, the collection is processed on the preceding Friday (assuming Friday is a banking day). Key points:

• The date adjustment rule should be disclosed in the mandate so payers are not surprised by an earlier debit — see Minimum mandate requirements.
• Adjustment can move a collection into the previous calendar month, which affects billing and reconciliation around month-end.
• Salary-date collections need particular care in months where the usual pay date shifts.

How do cut-offs differ across rails?

Related topics

• Back to the hub: How Payments Work
• Payment Statuses and References Explained
• What Is the Payment Lifecycle?
• EFT vs RTC vs PayShap vs RTGS