Specs
Exception Queue specs
Setup notes and briefing numbers for Exception Queue.
Review triggers and release proof
The Exception Queue specs set out what sends an item into review and what evidence is needed to release it. Helpful detail includes queue categories, responsible checks, escalation notes, and the audit record kept when a deposit is corrected or confirmed. That gives finance teams a disciplined method for handling outliers.
An Exception Queue item starts with a defined trigger, not a vague concern. Typical entries include an amount that differs from the bank statement, a deposit reference that does not match the remittance, a missing proof of deposit, or a card settlement that landed outside the expected cut-off for the rail used in South Africa. Each trigger should be named in the spec so finance, ops, and branch staff all classify the same issue in the same way.
Release evidence must be listed per exception type. For cash, that usually means the stamped deposit slip, cash-up sheet, bag number, and the branch or CIT handover record. For EFT and card items, the queue should require the payer proof, statement line, merchant batch total, or acquirer report before anyone marks the item corrected or confirmed.
Queue categories used in reconciliation
The spec works best when the queue is split into categories with clear ownership. Use separate buckets for unmatched cash, unmatched EFT, duplicate allocation, short banking, over banking, stale references, and disputed reversals. That structure helps a South African finance team route an item to the cashier, branch admin, debtor clerk, or bank liaison without reopening the same case three times.
Escalation notes should state when an item moves beyond first-line checks and what record must follow it. Include the amount, value date, account reference, deposit rail, and a brief reason for review, then attach the current evidence set through the contact form if additional context is needed. The audit entry should then capture who changed the allocation, what proof supported the change, and whether the original posting was reversed, corrected, or left in place.
- Cash short against stamped bank slip
- EFT reference missing customer identifier
- Correction log with user and date
Checks shaped by South African deposit rails
Specs should reflect the rail in use because cut-offs and proof differ across channels. ATM and branch cash deposits produce physical or image-based proof, card settlements rely on merchant batches and acquirer timing, and EFT receipts can be misleading until the statement line appears. A queue rule that ignores those differences creates noise instead of control.
Local operating conditions matter when setting review thresholds. Load shedding can delay batch uploads or proof retrieval, while weekend trading and mall branch hours affect when a deposit should reasonably appear. Teams working across Johannesburg, Durban, Cape Town, and outlying towns should note the expected banking day in the spec so late items are reviewed against the right timeline.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Minimum audit fields for each case
Each exception record should keep the same core fields from open to close. Capture the queue category, amount, value date, original reference, corrected reference where relevant, source documents checked, owner, escalation step, and final outcome. Short remarks are useful when they explain the exact mismatch rather than repeating the category name.
Close-out notes should show why the item left review and what changed in the books. If a deposit was reallocated, record the old account line and the new one. If nothing was amended, note that the evidence confirmed the original posting and retain the supporting files with the cash-up or remittance pack.