Back to Blog

How to Reconcile Bank Payments with AI: Step-by-Step Guide

Henri Jung, Co-founder at Superkind
Henri Jung

Co-founder at Superkind

A precision balance scale with the orange Superkind mascot sitting in one pan

To reconcile bank payments with AI means to hand the tedious matching of incoming transactions to open invoices to a digital colleague that does it in your accounting system and asks before it posts anything. It is a Friday afternoon, the bank export is open in one window, the list of open invoices in another, and you are scrolling up and down looking for the payment that matches invoice 4071. A customer paid two invoices in one transfer, another paid the wrong amount, and three payments have references nobody recognises. This is the job that eats an afternoon every week - and it is exactly the kind of work an AI employee can take off your desk.

This guide shows you, step by step, how to reconcile bank payments with Superkind: what you need, the exact messages you send, what happens in which system, and what you check before anything is booked.

Key takeaways

Reconciling payments means matching each incoming bank transaction to the right open invoice and clearing it - the AI does the matching, you approve the result.

Superkind works in your tools - DATEV, Lexware Office, SAP Business One, Excel or Google Sheets - and asks before it posts anything.

Set it up once and reconciliation runs as a weekly routine, pinging you only when a payment needs a decision.

What Reconciling Bank Payments with AI Means

Reconciling bank payments is the process of matching incoming transactions on your bank statement to the open invoices in your books, marking each paid invoice as settled, and resolving anything that does not line up. Doing it with AI means an AI employee performs the matching across both sources, proposes how to clear each item, and flags the exceptions - while a person approves every entry that touches the accounts.

  • The two sources - your bank transactions (what actually arrived) and your open invoices (what you expected to arrive). Reconciliation connects the two.
  • The clean matches - a payment whose amount and reference clearly belong to one open invoice. These are the bulk of the work and the easiest to automate.
  • The exceptions - partial payments, batch transfers covering several invoices, bank fees, and payments with no matching invoice. These need judgement, which is why approval matters.
  • The goal - books that match the bank, no invoice marked paid by mistake, and no customer chased for money they already sent.

How Superkind Does It

Superkind is the AI employee for your team. You write to it in Outlook, Microsoft Teams or Slack like a colleague, and it does the task in your tools and asks you before anything goes out. For reconciliation, that means it reads your bank transactions and your open invoices, matches them in DATEV, Lexware Office, SAP Business One or a spreadsheet, and waits for your approval before it clears a single entry.

  1. 1

    You write the task

    In Teams, Slack or Outlook you ask Superkind to reconcile the day’s bank transactions with your open invoices. No new app to open - you write where you already work.

  2. 2

    Superkind matches in your system

    It reads the bank transactions and the list of open invoices in DATEV, Lexware Office, SAP Business One or your spreadsheet, matches each payment using amount, reference and sender, and applies your rules and company knowledge.

  3. 3

    It asks for your approval

    Superkind shows the proposed matches and the flagged mismatches. Clearing invoices is a sensitive action, so it posts nothing until you click Approve.

  4. 4

    It runs as a routine

    Explain it once and the match runs on your schedule - every morning or every Friday - so you only step in when a payment needs a decision.

TeamsLena to Superkind

Reconcile today’s bank transactions in DATEV with the open invoices and flag any mismatches for my review.

Send Superkind your first reconciliation

Start for free in Outlook, Teams or Slack.

Two dark metal puzzle pieces fitted together with an orange seam

What You Need Before You Start

Reconciliation is only as good as the data behind it. Before you send the first task, make sure these are in place.

Your reconciliation checklist

  • Access to your bank transactions - a connected business account or a regular statement export (CSV, MT940 or camt)
  • Your accounting system with the current list of open invoices (DATEV, Lexware Office, SAP Business One, or a spreadsheet)
  • Superkind connected to both, running in Outlook, Teams or Slack
  • Clear matching rules - which reference to trust, how to treat fees, what counts as a partial payment
  • A named person who approves the cleared entries before they are posted
  • A place for the exceptions - who decides where an unexplained payment belongs

Step by Step with Superkind

Here is the full flow, from the first message to a clean set of books. Every step is something you can do this week.

Step 1: Connect Superkind to your bank and accounting system

Give Superkind access to your bank transactions and your accounting tool. It reads the incoming payments on one side and the open invoices on the other. Tell it your matching rules - for example, which reference field to trust and how to treat bank fees - so it works the way your team already does.

TeamsLena to Superkind

Use the Commerzbank account and our open invoices in Lexware Office. Match on invoice number first, then amount and sender. Treat anything under 2 euros as a bank fee.

What you check: that Superkind is reading the right account and the right invoice list.

Step 2: Start the reconciliation

Ask Superkind to reconcile a defined period - today, this week, or since the last run. It compares every incoming payment against the open invoices and prepares the matches. It does this in your system; nothing is posted yet.

SlackLena to Superkind

Reconcile the bank transactions since Monday with our open invoices and show me the matches before you post anything.

What Superkind does: reads the bank transactions and open invoices in DATEV or Lexware Office, matches on amount, reference and sender, and drafts the clearings.

Step 3: Review the matches and the flagged mismatches

Superkind comes back with a short result: how many transactions it checked, how many it matched cleanly, and how many need your eyes. The clean matches are ready to clear. The mismatches - wrong amounts, duplicate references, payments it could not place - are flagged for you.

TeamsSuperkind to Lena

22 transactions checked. 18 matched to open invoices. 4 need your review: 2 partial payments, 1 batch transfer, 1 payment with no matching invoice.

What you check: the flagged items. The 18 clean matches you can approve as a batch.

Step 4: Clear the exceptions

Partial payments, batch transfers and unknown references are where reconciliation really happens. Ask Superkind to propose a split for a batch transfer, leave the rest of a partial payment open, or research a mystery reference against your customer list before you decide.

TeamsLena to Superkind

The 1,480 euro from Berger covers invoices 4071 and 4072. Split it across both and leave invoice 4069 open - they only paid half.

What you check: that each split and each open balance is right before you approve.

Step 5: Approve and document the open items

You approve the matches, Superkind posts the clearings to your accounting system, and it lists every payment it could not match as an unexplained item. Nothing is forced into a match to make the totals tie out - the open points stay visible until someone decides what they are.

SlackLena to Superkind

Approved. Post the matches and send me the list of unexplained payments so I can clear them with the team tomorrow.

What Superkind does: posts the approved clearings in DATEV or Lexware Office and hands you a clean list of open items.

Set It Up as a Routine

The point of explaining it once is that you never explain it again. Turn the task into a standing routine and reconciliation stops being a Friday chore.

  • Pick a rhythm - daily keeps the exceptions small, weekly suits lower volumes. Little and often beats a monthly marathon.
  • Set the rule - “Every morning at 8, reconcile yesterday’s bank transactions with our open invoices and post me the mismatches in Teams.”
  • Keep approval in the loop - the routine prepares the matches; a person still approves before anything is cleared.
  • Let the knowledge build - every correction you make teaches Superkind how your customers pay, so next week’s match is sharper. This company knowledge stays even when people leave.

When it gets more complex

If your reconciliation grows beyond a simple match - many accounts, payment providers like PayPal or Stripe, a dashboard your team wants to see - you do not start over. You can build a custom solution or an app with its own interface on the Superkind platform, on top of everything Superkind already knows about your invoices and customers.

Other Ways to Reconcile Payments

AI is one way to reconcile payments, not the only one. Here is an honest comparison of the common approaches.

ApproachEffortError riskSuited for
By handHigh every weekHigh - typos, missed itemsA handful of invoices a month
Excel or macrosMedium, fragileMedium - breaks on edge casesSteady, simple payment patterns
RPA / rule botsHigh to build, low to runFails on anything unexpectedVery standardised, high volume
SuperkindLow - you write a messageLow - matches checked, you approveReal-world payments with exceptions

Manual reconciliation works while volumes are tiny, but effort and error rate climb as you grow, which is why most teams move to an automated method. Rule-based bots are fast but brittle: they handle the clean 80 percent and stall on the partial payments and odd references that actually need attention. An AI employee reads the context, handles the exceptions, and still asks before it posts.

Common Mistakes to Avoid

  • Forcing a match to make it balance - posting an adjusting entry just to tie the numbers out hides the real cause. Leave it open until you know what the payment is.
  • Skipping the small amounts - a two-euro fee or a rounding difference looks harmless, but unreconciled small items pile up and distort the account. Match every line.
  • Trusting the bank import blindly - check payments against the source invoice. Errors can come from the payer or the bank, not just your books.
  • Mishandling partial payments and batch transfers - clearing a whole invoice on a partial payment, or one invoice on a batch transfer, leaves your receivables wrong. Split the amount properly.
  • Letting one person do everything - the person who records payments should not be the only one who approves the reconciliation. Keep a second pair of eyes on the clearings.

6 Tips for Cleaner Reconciliation

1. Reconcile little and often

A short daily or weekly run beats a monthly marathon. Small batches mean small problems, and you catch a missing payment while the customer still remembers the transfer.

2. Fix the reference at the source

Most mismatches start with a vague payment reference. Put a clear invoice number on every invoice you send, and more payments match on the first pass.

3. Write your rules down once

Tell Superkind how you treat fees, partial payments and foreign currency once. Codified rules reconcile the same way every time and survive staff changes.

4. Keep the exceptions visible

Do not let unexplained payments disappear into a suspense account and stay there. Review the open list every week so it never grows into a quarter-end surprise.

5. Watch the payment providers

PayPal, Stripe and Klarna pay out net of fees and on a delay, so the amount on your bank rarely matches the invoice exactly. Set a rule for how the fee and timing are handled.

6. Keep the audit trail intact

Every match should link back to a bank transaction and an invoice, with your approval on record. That keeps the books traceable for the tax office and makes the year-end close far less painful.

Conclusion

Reconciling bank payments is repetitive, detail-heavy work that still needs a human eye for the exceptions - the perfect fit for an AI employee that does the matching and asks before it posts. With Superkind you write one message in Teams, Slack or Outlook, review the matches and the flagged items, approve, and the clearings land in DATEV or Lexware Office. Set it up as a weekly routine and the Friday afternoon of scrolling two spreadsheets is gone.

Send Superkind your first reconciliation this week: connect your bank and your accounting system, ask it to match the open invoices, and see how many it clears before you approve.

Frequently Asked Questions

It means letting an AI employee match each incoming bank transaction to the right open invoice, mark paid invoices as settled, and flag anything that does not line up. You still decide: Superkind proposes the matches and asks for your approval before it posts anything to your accounting system.

Superkind works in the accounting tools you already use, including DATEV, Lexware Office (lexoffice), SAP Business One, and spreadsheets in Excel or Google Sheets. It reads the bank transactions and the list of open invoices, matches them, and writes the cleared entries back once you approve.

No. Reconciling is a sensitive action, so Superkind always asks first. It shows you the proposed matches and the flagged mismatches, and only posts the cleared items after you click Approve. You stay in control of every entry that touches your books.

Superkind recognises when a payment covers several invoices (a batch transfer) or only part of one (a partial payment). It proposes how to split the amount across the open invoices, leaves the rest open, and flags it for your review so nothing is cleared by accident.

Little and often beats a monthly marathon. Reconciling weekly, or even daily, keeps errors small and catches problems early. Once you set it up as a routine, Superkind runs the match on your schedule and only pings you when something needs a decision.

The work stays auditable. Every match Superkind proposes is tied to a bank transaction and an invoice, and your approval is logged, which supports the GoBD principle that a qualified third party must be able to follow each booking. Superkind is hosted in Europe, is GDPR compliant, and does not train models on your data.

Superkind lists every bank transaction it could not match to an open invoice as an unexplained payment. You see the amount, the sender, and the reference, decide what it belongs to, and tell Superkind where to book it. Nothing gets forced into a match to make the numbers tie out.

Related Articles

Henri Jung, Co-founder at Superkind
Henri Jung

Co-founder of Superkind, the AI employee teams write to in Outlook, Teams and Slack. Henri helps companies, from small teams to the Mittelstand, hand their routine work to AI - without new tools, consultants or an in-house AI team.

Send Superkind your first task.

Start for free in Outlook, Teams or Slack. Or let us show you in 30 minutes how it runs in your systems.