Use caseReconciliation
Every break explained and closed.
Agents compare ledger, bank and processor records, investigate every break, and close it with the evidence attached.
How it works
From an unmatched line to a closed break.
- 01
Comes in
Each day the agent lines up the ledger against bank statements and processor settlement files and opens a case for every break.
/compare└ settlement 12 Nov · 1,207 lines› 1,204 matched› 3 breaks · £1,318.40✦ 3 cases opened - 02
Worked across teams
It works out why each line does not match, asks the processor or bank for what is missing, and brings in finance when an entry needs posting.
/investigate› STL-5528 · fee not booked› STL-5531 · arrives T+1› STL-5540 · refund duplicated‖ journal entry · awaiting finance - 03
Closed with evidence
Each break is closed with the explanation, the matching record and the approval attached, ready for month-end review.
/close✓ fee journal posted✓ T+1 line matched 13 Nov✓ duplicate refund recovered✓ 1,207 of 1,207 explained
Systems
Works across your ledgers, banks and processors.
Agents read the records on every side of a match and post nothing without the approvals you set.
- SAP
- Oracle
- Xero
- QuickBooks
- Core banking ledger
- Bank statements
- Stripe
- Adyen
- Visa
- Mastercard
- Snowflake
- Google Sheets
- Slack
- Jira
Security and governance
for every agent action.
Agents act only within the permissions you set, pause for approval on high-risk steps and log every action with its evidence. No AI training on your data.
Read moreScoped permissions
Decide which systems, actions and limits each agent can use. Nothing happens outside that scope.
Human approval
Set approval points for high-risk steps. Agents pause and route the decision to the right person.
Full audit trail
Every action is logged with what was done, why, and the evidence behind it, ready for audit.
Certified security
SOC 2 Type II, GDPR and PCI DSS. AES-256 encryption at rest and TLS in transit.
More use cases