Records matched across systems every morning, from the ledger to the bank file, and anything that does not line up sent to a person with the evidence attached, before the close and not after it.
See also Industries and Method
Scoping writes down how your team reconciles today: which ledgers, bank files and statements are compared, what counts as a match, and which differences a person always reviews. The system works from those rules, inside your own systems. Nothing is migrated, nothing is replaced.
Example request
Reconcile yesterday's settlements against the bank file and the general ledger. Match on reference, amount and date, allow for the usual one-day lag, and send anything over our threshold to the finance team.
Decide which differences the system may clear on its own and which always go to a person. Set thresholds, owners and escalation paths by account, entity or counterparty, and change them as the business changes, with every change approved and logged.
Example request
Clear timing differences under our threshold automatically, but send every unmatched payment above it to the controller. Never write anything off without a person, and note the reason for every match the system makes.
Every morning the reconciliation is ready before the team starts, with each match and each open item traced to its record. Month-end close starts from a clean position, open items are aged and assigned, and the audit trail is ready before the auditor asks.
Example request
Show me last week's open items. What were the five most common reasons a payment did not match? Which accounts need a new rule?
Tell us how this process runs today and we will scope it with you.
