Specs
Recon Daily specs
Setup notes and briefing numbers for Recon Daily.
Reconciliation fields that matter daily
The Recon Daily specs page gives a more exact structure for documenting reconciliation rules. It is meant for teams defining files, references, timing windows, and exception handling in a way others can actually follow.
Start the Recon Daily spec with the source file name, statement date, and the exact reference fields your team can trust. Set out whether matching happens on bank reference, merchant reference, amount, or a combination, because Instant EFT and PayShap entries do not always land with the same wording. Add the cut-off used for that day so late settlements are separated from true exceptions.
Include the evidence point used before a line is cleared, such as a bank statement row, gateway export, or core system receipt number. Some teams also note the manual checks required after load-shedding or a branch connectivity drop, especially where proof was captured on a phone and loaded later. A good spec states where unmatched items are parked and who may release them for follow-up.
Outputs expected from the spec
The finished note should show the file layout, field definitions, timing window, and exception codes in one place. Finance, operations, and support must be able to read the same page and reach the same conclusion about a disputed payment. Where a rule changes by rail, spell that out instead of hiding it under one generic reconciliation step.
Link Recon Daily specs to the matching process note and any exception register before adding new rules. Record the current import screen, sample statement rows, and the naming used in your ledger so the spec mirrors live work rather than theory. Describe how your team reconciles today, for example in a spreadsheet or the accounting system's bank feed.
- Reference hierarchy for difficult matches
- Late settlement handling after cut-off
- Sample CSV and statement mapping notes
South African conditions in the rules
South African bank feeds do not present every payment rail in the same shape, so the spec should note where wording differs across statements and gateway exports. Teams working from Johannesburg head office, Durban operations desks, or Cape Town finance hubs often need one rule for central processing and another for branch-captured references. DebiCheck returns, PayShap aliases, and Instant EFT proof screenshots should each have their own treatment in the exception table.
Power cuts and connectivity gaps affect when files are pulled and when unmatched lines can be reviewed with confidence. On high-volume days, a warehouse dispatch deadline may force a temporary holding bucket until settlement is visible on the bank side. Write those operating conditions into the note so staff are not guessing whether a payment is missing or merely delayed.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Briefing details before drafting
Send the current recon sheet, sample bank entries, and two or three exceptions that caused trouble this month. It also helps to note the ledger fields available, the settlement times you work to, and whether any references are edited by staff before import.
Capture the rule changes on the day they are tested, while the mismatch is still easy to trace back to source data. Pair the note with the operating note used by the team and the evidence pack kept for audit or sign-off.
What our Real-Time Payments customers say
Verified Google reviews