- Industry
- Retail
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Investigator
- Approver
- Finance Controller
- Code
- FIN-07
It matches bank activity to the ledger, including store cash deposits, card settlements, online payment provider payouts and vendor payments, and explains each unmatched item, such as a store's cash banked late, a cash-in-transit shortfall or a payout net of fees. It proposes the adjusting entries and flags possible cash loss to loss prevention. **The problem it solves:** Why each bank or ledger item did not match, and whether it is timing, fees, cash loss or error.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ERP's cash management: the bank statement lines, ledger cash entries, store banked cash from the point-of-sale system and payment provider payout reports for the period..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Finance Controller with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ERP's cash management: it records the matches and posts the approved adjusting entries. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The reconciliation procedures: the bank accounts and their purposes, the cash-in-transit collection schedule by store, card and payment provider settlement timings and fees, the matching rules and the cash variance policy.
Reads from
the ERP's cash management: the bank statement lines, ledger cash entries, store banked cash from the point-of-sale system and payment provider payout reports for the period.
Acts in
the ERP's cash management: it records the matches and posts the approved adjusting entries.
Hands back
An object with matched_count, unmatched (a list of date, amount, description, likely_cause, evidence and proposed_entry or null), cash_shortfalls (a list of store, date and amount) and closing_difference.
Asks a person when
An adjustment writes off an amount, or a cash shortfall is flagged to loss prevention.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Amount tolerance for a match (USD) | 1 | Bank and ledger amounts within this match. |
| Date window for a match (days) | 3 | Items within this many days match. |
| Store cash variance that goes to loss prevention (USD) | 100 | A store's cash deposit short by more than this is flagged to loss prevention. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Match on amount within 1 and date within 3 days, then on reference.
- Explain each unmatched item by weighing timing, fees, cash-in-transit, duplicates and error, and say what evidence supports the cause.
- A store cash deposit short by more than 100 against the till's banked cash goes to loss prevention.
- Propose adjusting entries only for explained items; leave unexplained items open with the next step.
- Never clear an item by writing it off without approval.
See the Bank Reconciliation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.