Bank statement and payment reconciliation automation: Swedbank, SEB, Luminor, Revolut, Paysera

What is bank reconciliation and why does it eat up time?

Bank reconciliation means linking every bank transaction to an accounting entry: an incoming transfer is matched to a sales invoice, an outgoing payment to a supplier invoice, a bank fee to an expense account. At the end of the month, the bank balance must match the balance in your books.

Importing the statement itself is easy today. What eats up time are the exceptions: the customer wrote "for goods" in the reference, paid three invoices with one transfer, paid 2 cents short, the owner paid from a personal account, and money from the online store arrives as a Paysera or Stripe payout that bundles a hundred orders. These exceptions are exactly what is worth automating.

How to get bank statements from Swedbank, SEB, Luminor, Revolut and Paysera automatically

Most Lithuanian banks let you download a statement in the ISO 20022 camt.053 XML format, which almost all accounting software can import. But you have to download the file by hand every time. The automatic options:

An important point: if your accounting software is already a bank "operator", connecting through it is usually the cheapest option. For example, Rivile ERP (a widely used Lithuanian accounting system) has a direct bank connection through a licensed open banking provider, while Rivile GAMA needs a separate Rivile API key for open banking import, and you can only pull entries no older than 3 months directly. The permissions a bank grants are valid for a limited time, so they have to be renewed periodically; this is one of the most common "why did it stop working" cases.

123

1. 1 Pricelist: contract and monthly fees
2. 2 Get an automatic account statement: the statement arrives automatically
3. 3 Statements for other banks' accounts (SEB, Luminor, Citadele and more) in the same channel

How does automatic payment-to-invoice matching work?

Well-designed reconciliation goes from the strictest rules to the loosest. Each transaction is checked in order until a match is found:

1. Structured reference. A payment code or invoice number in the structured field (camt.053 RmtInf/Strd) or the EndToEndId.
2. Invoice number in the reference. Searched for by your series pattern, e.g. "SF-2026-" followed by digits, and the amount is compared.
3. Company code and amount. The payer's code from the statement plus the only unpaid invoice for that amount.
4. IBAN and amount. The payer's account, already linked to the customer before.
5. Several invoices. The payment amount equals the total of several unpaid invoices from that customer.
6. Partial payment and rounding. An allowed tolerance (e.g. up to €0.05) or a partial match.
7. Bank fees, interest, payments to VMI (the Lithuanian tax authority). Recognized by the transaction code (e.g. CHRG, INTR) and the recipient.

Whatever is left after these rules goes to AI or a person. So that the rules catch more next time, the system remembers a new IBAN or name variant on the customer record.

Where AI helps: unmatched payments

A language model handles well the cases where rules break: "pmt for inv. 1234 and 1240", "UAB Medis ir Ko per contract No. 7", "advance". A practical approach:

• The AI receives the transaction and the list of unpaid invoices of that customer (or customers with similar names), not your whole ledger.
• It returns a structured answer: which invoices, what amount for each, a confidence score, an explanation.
• High-confidence suggestions are presented to the accountant for one-click approval; low-confidence ones are left for manual work.
• The AI never changes amounts or creates entries on its own without approval.

AI is also useful at the end of the month: to compile a list of "who hasn't paid and how late they are" and to prepare reminder texts for customers. How AI is used in other accounting tasks is covered in AI in accounting.

How to reconcile Paysera or Stripe payouts with online store orders

For online stores, the biggest headache is not individual transfers but bundled payouts. The payment provider transfers one amount to your bank account for dozens or hundreds of orders, minus its fees. Your bank statement shows one line, while your books have a hundred invoices.

The automated solution works in three steps:

1. The payout breakdown is fetched from the payment system (API or reports): which orders, which amounts, which fees.
2. Each order is linked to an invoice in your accounting by order number.
3. The bank line is split: order amounts are matched to invoices, fees go to expenses, and the difference (refunds, disputes) is flagged for review.

The same principle works for card terminal (POS) payouts. SEB Baltic Gateway, for example, also provides card reader reports, which can serve as the breakdown source. From a security point of view, reconciliation needs only read access: the automation tool does not need payment initiation rights.

Accounting software feature or a custom n8n workflow?

My advice: first make full use of what your software and bank already offer. Build a custom workflow only on top of what is left. On choosing between n8n and Make, see n8n or Make for a small business.

What an automated reconciliation workflow looks like: 7 steps

An example: a service company issues invoices in an invoicing app, keeps its books in Rivile and banks with SEB and Paysera:

1. Every morning, n8n fetches yesterday's transactions from SEB (via Baltic Gateway or camt.053) and the Paysera API.
2. Transactions are normalized into one format, and duplicates are dropped by the bank transaction ID.
3. Unpaid invoices are pulled from the invoicing app.
4. Rules match the clear cases; the invoices are marked as paid.
5. The remaining transactions go to AI, which suggests matches with an explanation.
6. The accountant receives one summary (by email or Slack): what was matched, what to approve, what is left.
7. Reminders are sent automatically for overdue invoices, and approved payments are passed to accounting.

This workflow runs alongside your accounting software and does not replace it. If you issue invoices in your online store, it is worth automating the transfer of orders as well; see Rivile integration with an online store.

How much does bank reconciliation automation cost?

Example (an illustration, not a client case): if an accountant spends 6 hours a month reconciling 300 transactions, and automation matches most of them and leaves a few dozen to approve, a few hours a month are saved. Whether it pays off depends on your hourly rate and number of transactions; send me those two numbers and I will email you a more precise estimate. Prices for other parts of accounting automation: invoice automation cost 2026; the service: process automation; solutions for accounting: automation for accounting; all prices: pricing.

Frequently asked questions

Sources and related articles

• Swedbank Gateway, SEB Baltic Gateway (in Lithuanian), Rivile GAMA: direct bank connection (in Lithuanian)
• Automatic i.SAF submission (Lithuanian VAT invoice register)
• SABIS e-invoices 2026 (Lithuanian public sector e-invoicing)
• Invoice automation with B1 (Site.pro), Rivile and Xero
• Xero integration and automation