The New AI Employee
How-to

Bank Reconciliation Automation: How Matching Suggestions Work

Bank reconciliation automation explained: each bank line gets a suggested match with the reason shown, you confirm, and unclear lines stay open.

The New AI Employee6 min read
Two columns, bank statement lines and invoice cards, joined by thin lines proposing matches, with a few lines left unconnected beside question marks.
Short answer

Bank reconciliation automation reads your bank lines and suggests a match for each one: an invoice, a bill or a known regular payment, with the reason shown. You confirm the suggestions. Lines with no clear match stay open instead of being forced.

Why does reconciliation fall behind?

Reconciliation falls behind because every bank line needs a small decision, and the decisions pile up. Bank reconciliation automation prepares those decisions, so you only confirm them.

On paper it's simple: every line on the bank statement should match something in the books. An invoice paid, a bill settled, a fee, a transfer. In real life, a customer pays three invoices at once, or half of one. References are missing. Fees come off the amount. A supplier refunds an overpayment months later. Each line takes a few minutes of searching, and nobody has those minutes at month end.

Picture a small catering firm. Customers pay by transfer, some with the invoice number and some with only a name. By month end forty lines are unmatched. Then the list of unpaid invoices is wrong, customers get reminders for invoices they've paid, and the accountant asks questions nobody can answer fast.

This table shows why lines resist matching, and what a suggestion can do.

Why the line is hardExampleWhat a suggestion can do
One payment, several invoicesA customer pays three invoices in one transferPropose the set of open invoices that adds up to the amount
Part paymentA customer pays half an invoicePropose the invoice and show the amount still open
Missing or wrong referenceThe transfer shows only the customer's namePropose by payer and amount, with lower confidence shown
Bank fees taken offThe amount received is slightly shortPropose the invoice and a separate fee line
Regular paymentRent, a subscription, a loan repaymentPropose the known rule for that payee
Nothing fitsAn unknown transfer in or outLeave it open for you, with no forced match

How are matching suggestions made?

Each bank line is compared with open invoices, open bills and known regular payments, and the best candidate is proposed with the reason shown.

The comparison uses what's on the line and what's in your books: the amount, the date, the payer or payee name, and any reference. A suggestion is only as good as its reason, so each one says why it was made. Same amount and same invoice number in the reference. Or same payer and an amount equal to two open invoices.

It also uses your confirmations. When you confirm that a certain payer always settles a certain kind of invoice, or that a monthly charge always goes to the same account, that becomes a rule, and the next line of that kind comes with a clearer reason.

This is built to order on the same engine as our supplier bills AI employee, which runs today. Here's how one bank line moves through.

  1. The bank lines for the period are read from your bank feed or statement export.
  2. For each line, the AI employee looks for open invoices, open bills and known regular payments that fit the amount, date and party.
  3. It ranks the candidates and keeps only those with a clear reason.
  4. It writes a suggestion beside the line: the proposed match, the reason, and any difference such as a fee.
  5. Lines with no clear candidate are marked open, with a note on what was searched.
  6. You go through the list, confirm the good suggestions and handle the open lines.
  7. Every suggestion and every confirmation goes in the log.

Why confirm instead of forcing a match?

You confirm each suggestion. Nothing is forced, and a line that doesn't clearly match stays open instead of being pushed onto the nearest invoice.

Forcing a match is the quiet failure of careless bank reconciliation automation. The balance looks right, but one customer's payment now sits against another customer's invoice. The first gets a reminder for an invoice they paid. The second looks paid when they aren't. Nobody notices until someone complains.

That's why ours only makes suggestions. Every step starts with your approval, and later you choose which ones go automatic. It doesn't post entries, doesn't move money and doesn't decide. You confirm each match in your accounting software, or reject it and pick another.

Confirming is faster than it sounds. With the reason written beside each suggestion, most can be confirmed at a glance, and your attention goes to the few that need it.

Interactive

Your reconciliation backlog: a suggested weekly routine

Tick each line that's true of your books today. The result suggests a weekly routine for keeping bank lines matched.

What do you do with unmatched lines?

Unmatched lines become a short, named list for you to work through, each with a note on what was searched and why nothing fitted.

Most fall into a handful of kinds, and each has a usual next step. When a customer payment can't be placed, the right move is often to ask the customer which invoices it covers. That request can be a draft email, ready in the thread. That's where reconciliation meets accounts receivable automation.

Here are typical unmatched lines and the usual next step.

  • A customer payment with no reference: ask the customer which invoices it covers.
  • A supplier payment that matches no bill: check whether the bill ever arrived and was entered.
  • A transfer between your own accounts: confirm it and record it as a transfer.
  • An unknown charge: check with the bank or the card holder before coding it.
  • A refund or credit: link it to the credit note, or ask the sender for one.
  • Anything to do with tax payments or refunds: ask your adviser how to record it.

How do you keep it current?

Reconciliation stays current when you do it weekly, in a short session, on suggestions already prepared.

A backlog is mostly a timing problem. A week's lines are easy to remember. A quarter's aren't. When suggestions are ready each week, the review takes a short fixed slot in your calendar, and the open lines are fresh enough to settle with one email.

The weekly slot works best with the same person each time and a short written list of rules: which payers are known, which charges repeat, which accounts are your own. The AI employee does the searching. You spend the slot on decisions.

Keeping current also helps the rest of the books. When payments are matched promptly, the list of unpaid invoices is right, so reminders go only to customers who really owe. Drafting those reminders is a separate job, also built to order: a draft for each overdue invoice, ready the day it falls due. That's the heart of what people want from credit control software.

Together these make a simple accounting workflow automation: bills entered as drafts, bank lines matched by suggestion, reminders drafted from a correct list, and every step on record.

What do you need to start?

To start you need access to your bank lines, your accounting software, and someone who'll review the suggestions each week.

The bank lines can come from the feed your accounting software already receives, or from a statement export. The accounting software holds the open invoices and bills. The regular payments are listed once: rent, subscriptions, loan repayments, payroll transfers, each with the payee and the usual amount.

If there's a backlog, decide first how far back to go. Sometimes the right answer is to clear the old lines with your accountant and start fresh from a clean date, so the weekly routine isn't buried under history.

Agree what counts as close enough, too. A suggestion with a small difference, like a bank fee, may be fine to confirm with a fee line. A bigger gap should stay open. Write that down with your accountant and the matching stays consistent week to week.

Our AI employees are rented monthly and run on our servers against your own bank feed and accounting software. One command stops any of them, and nothing starts without your yes. The checklist below suggests a weekly routine for your own backlog.

Questions

Can bank reconciliation be fully automated?

Matching can be suggested automatically, but ours doesn't confirm by itself. You confirm each suggestion, and lines with no clear match stay open.

What happens to a payment that matches no invoice?

It stays open, with a note on what was searched. You decide, often after asking the customer which invoices it covers.

How often should bank reconciliation be done?

Weekly works well for most businesses. The lines are fresh, the session is short, and the list of unpaid invoices stays correct.

Is your bank matching running today?

It's built to order. The supplier bills AI employee it builds on runs today for clients.

Does it move money or post entries?

No. It prepares suggestions. You confirm matches in your accounting software, and it can't move money.

Tell us your workflow. We will build it around you.

Write to hello@thenewaiemployee.com with how many bank lines you reconcile each month and how long it takes. We'll tell you plainly whether matching suggestions help.

Talk to us Related service: Bank and receivables

Keep reading

Write to us

Tell us which hours you want back.

Three lines are enough: what you do, what takes your time, how many hours a week it costs. Write to hello@thenewaiemployee.com.

Offices in Sheridan (Wyoming), Panama City, London, Bucharest and Milan.