Playbook · Treasury & close

The rec that's done
before breakfast.

Bank reconciliation is the quiet reason the close starts from behind: whatever wasn't tied out during the month becomes week-one archaeology. This play makes reconciliation a daily non-event instead of a month-end project.

Systems: SAP · Oracle · your banking portals Runs: every morning, before start of day Pilot-ready
Today

Downloaded, pasted, eyeballed, parked.

Most teams run some version of the same morning: download the bank file, paste it next to the ledger in a spreadsheet, match what matches, and park what doesn't in a growing "to investigate" tab. The clean lines are mindless work; the odd ones — timing differences, bank fees, duplicated payments, unreferenced receipts — each need a small investigation nobody has time for mid-month.

So the odd ones wait. And at month-end, the accumulated tail of unmatched lines lands on the close's critical path, in the same week as everything else. Half of finance teams take more than a week to close, and 94% of them are living in a spreadsheet somewhere inside it — this spreadsheet is usually one of them.

With an agent on the process

Yesterday's activity, tied out by 7am.

1

Pulls the bank feed before start of day

Every morning the agent collects yesterday's statements across your accounts and lines them up against the ledger — no downloads, no pasting.

2

Clears the clean matches

References, amounts, dates and agreed tolerances, applied the same way every time. The mindless 80% is matched and posted before anyone logs in.

3

Buckets the odd ones by cause

Timing difference, bank fee, duplicate, missing reference — each unmatched line arrives pre-investigated, with the likely explanation and a suggested entry attached.

4

Posts what you approve, chases what's missing

Approved entries go into the ledger under the agent's scoped credentials. Items needing someone else's input get chased automatically until they're resolved.

5

Hands the close a finished rec

By month-end there is no tail. The reconciliation summary rolls straight into the close checklist, with every entry traceable to its evidence.

Month-end project → daily non-eventthe close starts reconciled instead of starting from behind
Governance

The guardrails are the product.

Scoped permissions

Read the feeds, match within tolerances, post approved entries. No payments, no transfers, no exceptions to its own rules.

Confidence gate

Anything below the threshold your team set is a suggestion, not an action. The agent proposes; your accountant disposes.

Human review queue

The bucketed exceptions arrive with evidence attached, in the tool your team already uses. A queue you clear in minutes, not a tab you dread.

Full audit trail

Every match, every posting, every approval reconstructable end to end — the trail your auditor asks for is generated as a by-product.

Measurement

The numbers this play moves.

▼ down

Time spent waiting

Unmatched lines stop queueing for month-end; the close's critical path gets shorter.

Measured as CTE · Cycle Time Efficiency
▼ down

Work done by hand

The download-paste-match morning ritual becomes governed system actions.

Measured as DWR · Digital Work Ratio
▼ down

Cost per line reconciled

Your accountants review suggestions instead of building matches from scratch.

Measured as CTS · Cost to Serve
▼ down

Rework

Tolerances and rules applied identically every day — no more end-of-month corrections of mid-month shortcuts.

Measured as FTR · First Time Right

Baselined in week one from your own event logs, re-measured in week six. The methodology is our Portfolio Process Mining framework.

Run this play as your pilot.

One agent on your daily rec, live in six weeks, for one fixed fee — with the before-and-after measured in your own data.

Book a pilot scoping call Back to the playbook