Signals
Cut Off Habits
A short payment note on cut-off habits that reduce confusion between payment made, payment cleared, and payment reflected.
Cut-off mistakes do not look dramatic, but they create avoidable friction. A payment sent after the bank's processing window, a PayShap request left too late, or a same-day expectation carried into the evening can all derail handover. Cut Off Habits is our note on the payment deadlines teams should keep in view.
The habits around payment cut-off times matter just as much as the payment rail itself. Teams often need to explain why a transfer can be sent today, clear later, and only reflect after that.
Three clocks behind one payment
- Bank processing window recorded
- Time sent captured from the payer side
- Reference copied exactly from the transaction
- Method stated as Instant EFT, PayShap, or DebiCheck
Use this note next to the payment-method pages, not instead of them. Cut-off habits explain timing and interpretation, while the rail pages explain how Instant EFT, PayShap, or DebiCheck work in the first place. That split helps finance, ops, and support speak about the same payment without mixing statuses.
How Cut Off Habits affect a DebiCheck collections week
Cut Off Habits explains the deadlines that change how a payment should be read by finance, ops, and support. It focuses on the common mix-up between payment made, payment cleared, and payment reflected.
Cut-off problems usually start with one missing detail, such as the bank's last processing window for the day or the time a proof was actually generated. In Johannesburg, Durban, and Cape Town, the same customer phrase of payment made can still mean three different things inside a team.
Capture the first visible proof while the payment is still being discussed. A screenshot taken later can miss the exact send time, the reference, or whether the status was pending at that moment. That matters when someone expects same-day release and the bank has moved into the next processing period.
Useful habits after 3 pm
Teams need language that separates sent, cleared, and reflected without adding extra bank jargon. The point is not to make every payment sound complicated. The point is to stop teams from treating one status as if it were the next one.
Read Cut Off Habits with the matching entries in Rails, Playbooks, and Signals when a payment issue crosses teams. Before stock, access, or service is released, compare the bank-side status to the exact reference on hand. Our contact form takes attachments, so include a current screenshot of the payment step in question.
- Timing notes tied to actual bank windows
- First proof saved before status changes
SA cut-off pressure points
South African payment teams often work across more than one clock at once: customer expectation, bank processing, and internal handover. PayShap may be faster for many use cases, but not every query on a desk is a PayShap query. Instant EFT and DebiCheck still bring their own timing checks, especially where settlement expectations and mandate understanding differ across departments.
Load-shedding can interrupt the moment a proof is saved or reviewed. Courier collections can force a dispatch decision before a late-day payment has moved far enough to be treated as cleared. At a branch counter or on WhatsApp, that distinction needs plain wording that does not overstate what the bank has finished doing.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Notes for DebiCheck collection days
A short payment note on cut-off habits that reduce confusion between payment made, payment cleared, and payment reflected.
File this note with the order record while the payment trail is still easy to trace. Add the proof of payment, bank status, and internal handover note so finance can see why the transaction was treated as made, cleared, or only reflected.