Payment Run Reconciliation Agent
Reconciles each supplier payment run sent to the banks against bank confirmations and returns.
- Industry
- Procure AI
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Investigator
- Approver
- Accounts Payable Lead
- Code
- FIN-17
It reconciles every supplier payment run the company sends to banks for its own and its clients' AP ledgers, file by file and bank by bank across several cutoffs a day, against what the banks confirmed, debited and returned. It explains each variance as cutoff timing, a bank fee, a rejected or returned payment, a partial debit or a duplicate, proposes the entries, and completes the run once every variance is explained or approved. **The problem it solves:** Why a bank's confirmed or debited amount for a payment run differs from the file total in the ledger: which payments fell either side of the cutoff, what the bank charged, which payments were rejected or returned and why, and how long each variance has been open.
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 purchasing and accounts payable modules: the payment files sent per ledger with their payments, the banks' confirmations, debits, rejects and returns for the value date, and runs left unreconciled earlier..
- 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 Accounts Payable Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ERP's purchasing and accounts payable modules: it posts the approved entries, marks each run reconciled, credits returned payments back to the client's funds and reopens their invoices for AP. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The payment operations manual: each bank's file cutoffs and value-dating rules, payment file formats, fee schedules per client funding account, reject and return reason codes, the rule that a returned payment is never re-sent without corrected and verified supplier details, the variance tolerances and the escalation path.
Reads from
the ERP's purchasing and accounts payable modules: the payment files sent per ledger with their payments, the banks' confirmations, debits, rejects and returns for the value date, and runs left unreconciled earlier.
Acts in
the ERP's purchasing and accounts payable modules: it posts the approved entries, marks each run reconciled, credits returned payments back to the client's funds and reopens their invoices for AP.
Hands back
A list with one entry per bank and file, each with bank_name, ledger, run_label, sent_at, cutoff_at, currency, file_total, bank_confirmed, difference, payments_matched, reconciled (true or false), variances (a list, each with amount, variance_class (cutoff_timing, bank_fee, rejected, returned, partial_debit, duplicate, missing_confirmation or unknown), supplier (or null), reason_code (or null), evidence and hours_open), adjusting_entries (a list, each with account, amount and description) and unexplained_amount.
Asks a person when
A fee is 100 or more or off schedule, a variance is a duplicate, partial debit or unknown, a returned payment is unresolved after 3 days, a confirmation is missing, or a run is unreconciled for more than 24 hours.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Variance tolerance per run (USD) | 0 | Client payment runs reconcile to the cent; a difference above this must be explained. |
| Cutoff grace (minutes) | 15 | A file sent within this of a bank's cutoff may be valued that day or the next, with the reason given. |
| Post bank fees without approval below (USD) | 100 | A bank fee that matches the schedule and is under this posts straight away. |
| Resolve a returned payment within (days) | 3 | A returned supplier payment should be corrected, verified and re-queued by AP within this long. |
| Escalate an unreconciled run after (hours) | 24 | A run still unreconciled this long after its value date is escalated. |
| Expected runs per bank per day | 2 | A bank confirming fewer runs on a payment day is flagged as a missing confirmation. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Reconcile each bank, ledger and file separately; never net one client's run against another's or against the company's own.
- A run is reconciled only when the difference is within 0; otherwise every variance is explained.
- Value a file by its send time against the bank's cutoff; one within 15 minutes may go either side, with the reason stated.
- Class every variance as cutoff timing, bank fee, rejected payment, returned payment, partial debit, duplicate, missing confirmation or unknown, with evidence.
- A returned or rejected payment goes back to the client's funds and to AP with its reason code; it is never re-sent until the supplier's details are corrected and verified, and an unresolved return after 3 days is escalated.
- A bank fee that matches the schedule and is under 100 posts without approval; one that does not match is a variance against the bank agreement.
- A bank with fewer than 2 confirmations on a payment day has a missing confirmation, and a run unreconciled for more than 24 hours goes to the Accounts Payable Lead.
See the Payment Run 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.