Finance · Accounting

Bank reconciliation, down to a short list of exceptions.

Statements from your banks and Wise matched line by line to your accounting ledger. What doesn't match comes to a person with a proposed fix.

Book a free strategy call

How do you automate bank reconciliation with AI?

Export the statements from your bank and Wise accounts. The workflow matches each movement to your accounting ledger by amount and date, converts foreign currency at the ECB reference rate and lists what's left: missing payments, duplicates, payments booked on the wrong account. Each exception comes with a proposed fix, and a person approves it before anything changes in the books. It already runs in production.

Who approves
Your finance lead or your accountant
You own
The workflow, agent logic, integrations, evals and logs

When the statements and the books stop agreeing

The expensive part is the payment booked on the wrong account in March that surfaces at year-end closing, when nobody remembers what it was.

  • “The year-end balances don't match, and nobody knows which payment ended up on the wrong account.”
  • “We tick lines in a spreadsheet every month and the accountant still finds surprises when the year closes.”
  • “Half our suppliers are paid from Wise in dollars or pounds, and the euro amounts never come out the same twice.”

From statement to approved fixes in six steps

  1. 1

    Statements in

    Statement exports (CSV) from each bank and Wise account, per currency. Read-only: the workflow never logs into your bank.

  2. 2

    Match by amount and date

    Each movement is matched to a payment or receipt in your ledger. Counterpart and reference break the ties.

  3. 3

    Convert currency

    Movements in USD, GBP or other currencies are converted to euro at the ECB reference rate for that day.

  4. 4

    List the exceptions

    Movements with no match, payments recorded twice, payments booked on the wrong account, invoices marked paid with no movement behind them.

  5. 5

    Propose the fix

    For each exception, a proposed correction: move the payment to the right account, record a missing payment, flag a missing invoice. A person approves or rejects each one.

  6. 6

    Check the balances

    Statement balance and ledger balance per account, side by side, with the open items that explain any difference.

What the AI can touch, who approves, what gets logged

Each solution runs with the narrowest access that does the job. Drafts stay drafts until a person sends them.

It can

  • Read the statement exports you provide
  • Read invoices, payments and accounts in your accounting software
  • Propose matches and corrections as a list to review
  • Apply a correction after a person approves it, through a user with limited permissions

It can't

  • Log into your bank or move money
  • Delete invoices or ledger entries
  • Approve its own corrections
  • Send anything to your accountant, your suppliers or the tax authority
Who approves
The person who answers for the books: your finance or admin lead, or your accountant. They see each proposed fix with the movement and the ledger entry behind it.
What's logged
Every proposed match and correction, with the statement line, the ledger entry before and after, the rate used, and who approved it and when.

In production today, and what it changed

It runs in production on real bank and Wise statements, against a real accounting ledger. The matching rules, the exception list and the approval step have been tested on months of movements, so your project starts from working pieces and only the edges change.

Measured on your data, before and after

What we measure, before and after: Hours per month on reconciliation, and exceptions still open at closing.

What you provide, what we set up, how long it takes

You provide

  • Statement exports from each bank and Wise account, or read-only access to them
  • A user in your accounting software with the permissions the job needs
  • The rules your accountant already applies: accounts, recurring suppliers, tolerances
  • One person who answers for the reconciliation

We set up

  • The connection to your accounting software through its API
  • Matching rules for your accounts and currencies
  • The exception list and the approval step, in the tool your team already uses
  • The log and the before/after measure

Embed time

The first run is on a month you have already closed, so the result can be checked against your accountant's work.

What we adapt to your company

The matching logic stays the same. The edges change with your company.

  • More banks, card accounts and payment platforms alongside Wise
  • Your accounting software, through its API
  • Tolerances for bank fees and rounding
  • How often it runs: weekly, monthly or at closing
  • Where exceptions land: email, your project tool or a shared sheet

Case study · Automation · ERP · Integrations

Automating Operations with Custom ERP and Payment Integrations

Administrative workload down about 60% at a consultancy, after a custom ERP automated invoicing and recurring invoice reconciliation.

administrative workload (approximate)
−60%
recurring invoice reconciliation, previously hours of manual checks
Automated
“We have had the privilege of working with this team across multiple projects, and it has always been a truly rewarding experience. They bring a clear vision, strategic thinking, and a collaborative spirit that makes every engagement successful.”
Tech consultancy
Full story

Questions before you start

No. It works on the statement exports you provide, or on read-only access if your bank offers it. It can't move money, and it changes your books only after a person approves each correction.

It connects to your accounting software through its API. For yours, we check the API on the first call: what it lets us read and what it lets us change. If a step can't be automated safely, it stays manual and goes on the exception list.

They're converted to euro at the ECB reference rate for the date of the movement, and the rate is logged next to the match. Differences from bank fees or rounding go on the exception list unless they fall within the tolerance your accountant sets.

The person you name as owner approves every correction before it reaches the books, and the log shows what was proposed, what was approved and by whom. A wrong match that nobody approved changes nothing.

No. Your accountant gets cleaner books and a list of open items with the evidence attached. The accountant can also be the person who approves the fixes.

Hours per month spent on reconciliation and exceptions still open at closing, before and after, on your own accounts.

Bring last month's bank statement.

On a strategy call we look at your banks, your accounting software and where the balances drift. If the solution doesn't fit, we'll tell you on the call.

Let's talk