Bank transaction reconciliation explained: check incoming payments faster

Bank transaction reconciliation answers a simple but important question: which payment in your business account belongs to which unpaid invoice? When you check this regularly, you can see sooner who has paid, which amounts are still outstanding and which cases need investigation. Reconciliation does not replace bookkeeping or advice from a tax adviser. It creates a traceable link between the bank transaction, the invoice and its payment status.

The original draft mixed up bank transaction reconciliation, invoice retention and e-invoicing. These are different topics. An e-invoice does not make an incoming payment unambiguous. Conversely, a matching transfer does not prove that the invoice, the underlying supply and the tax treatment are correct in every respect.

In short: clear payments can be matched automatically. Partial payments, amount differences, missing invoice numbers and multiple possible matches belong in a review queue, not in an automatic “paid” posting.

What does bank transaction reconciliation mean?

Bank transaction reconciliation compares movements in a bank account with the company’s records and open transactions. For outgoing invoices, the main task is payment matching: an incoming payment is linked to a particular invoice and the outstanding amount is updated.

In accounting, reconciliation may have a wider meaning. It can verify that the balance and every posting in the bank ledger agree with the bank statement. That broader check includes expenses, fees, refunds, direct debits and transfers between accounts. The Motorica workflow described here focuses on incoming bank transactions and unpaid invoices.

Three tasks that should remain separate

• Payment matching: Which payment belongs to which invoice? The result is a documented link between the bank transaction and the invoice.
• Accounts-receivable review: Is an invoice fully paid, partly paid, overdue or unresolved? This provides the basis for a payment reminder and, if necessary, a formal payment demand.
• Accounting bank reconciliation: Do the bank balance, all ledger postings and the supporting documents agree completely? This is broader than checking incoming payments.

Automation can simplify the first task, but it does not necessarily complete the other two. Exceptions must therefore remain visible and be reviewed regularly.

Which data should be compared?

A reliable match uses several signals:

• booking date and value date of the bank transaction;
• amount received and currency;
• remittance information or transfer reference;
• invoice number found in the transfer text;
• payer or account-holder name;
• invoice total, due date and outstanding balance;
• partial payments, credit notes or refunds already allocated.

An identical amount alone is weak evidence when several unpaid invoices have the same value. An invoice number alone is not enough when the amount differs. The strongest match combines a unique invoice number, the correct amount and a plausible counterparty.

The reconciliation workflow step by step

1. Issue an identifiable invoice: Use a unique invoice number and give the customer a clear transfer reference.
2. Connect the business account or provide transactions: Motorica can connect a business account through BANKSapi’s PSD2-based service and import account movements.
3. Retrieve incoming payments: The application imports bank transactions for the selected period.
4. Compare unpaid invoices: Invoice number, amount and open items are compared with the payments received.
5. Process clear matches: When the invoice number is recognised and the amount agrees, the invoice can be marked as paid automatically.
6. Review uncertain cases: Amount differences, missing numbers or several possible invoices go to the review queue.
7. Document the decision: Confirm or reject a suggestion only after checking the invoice, payment and any remaining balance.
8. Follow up open items: If money is still outstanding, the next step may be a question to the customer, a payment reminder or a formal collection process.

When is automatic allocation appropriate?

Automatic payment matching is most reliable when the transfer reference contains a unique invoice number and the payment amount equals the invoice amount. Motorica can process this kind of clear match automatically.

Without an invoice number, an identical amount can be a clue but not conclusive evidence. If only one open invoice has that amount, Motorica presents it for review. If several invoices share the same value, the match is ambiguous. The system should not guess.

Automation therefore does not mean posting every transaction without control. Good automation completes clear cases and isolates uncertain cases visibly.

Review cases: partial, combined and differing payments

Real payments often do not match one invoice exactly:

• Partial payment: The customer pays only part of the total. Keep the remaining balance open and document the amount received.
• Combined payment: One transfer settles several invoices. Allocate the payment across all of them instead of marking only one as paid.
• Overpayment: The amount exceeds the invoice. Check whether it covers another invoice, is an advance, is an error or must be refunded.
• Discount or fees: The amount is lower because an agreed cash discount was used or bank charges were deducted. Verify whether the difference is justified and posted correctly.
• Credit note or set-off: A receivable was offset against a credit or counterclaim. Preserve a clear documentary trail.
• Wrong transfer reference: The payment may belong to another invoice or another customer.
• Chargeback or refund: A payment recognised earlier may later be reversed. The status must not remain “paid” without review.

For partial payments and amount differences, use Motorica’s review queue and establish the remaining balance before confirming an invoice as fully paid.

How to resolve an uncertain match

Open the invoice and the proposed bank transaction. Compare invoice number, amount, payer, booking date and transfer reference. Then check whether another payment, credit note or correction has already been allocated.

If the match is clear, confirm it and add a short note when useful. If it is wrong, reject the suggestion. If the case remains uncertain, do not change the invoice status prematurely. Ask the customer or clarify the posting with your bookkeeper or tax adviser.

An amount difference must not be treated as full payment merely because the invoice number appears in the transfer text.

How often should you reconcile?

German law does not prescribe a blanket weekly procedure called “bank reconciliation”. The right frequency depends on transaction volume, payment terms and the cost of reacting late.

A practical routine is:

• daily or several times a week: with many incoming payments, tight cash planning or active debt collection;
• weekly: a workable open-item routine for many self-employed people and small businesses;
• at month end: reconcile the complete bank account, postings, accounting documents or receipts, fees, refunds and unresolved transactions;
• before VAT filings, an income surplus statement, year-end work or handover to the tax adviser: investigate all open and unclear cases.

The important point is not a rigid interval. It is that unexplained transactions do not remain unresolved indefinitely.

Documentation, GoBD and retention

Section 146 of the German Fiscal Code requires relevant postings and records to be individual, complete, correct, timely and orderly. Changes must not hide the original content. In practical terms, the bank transaction, invoice, allocation, correction and later changes must remain traceable.

Retention depends on the type of document. Under section 147 of the Fiscal Code, books and certain records are generally retained for ten years, accounting documents or receipts for eight years, and other tax-relevant records generally for six years. Invoices are generally retained for eight years under section 14b of the German VAT Act. A period can run longer in special cases, for example while documents remain relevant to a tax period that is still open.

Whether a bank statement is an accounting document or another tax-relevant record in a particular case depends on its function in the accounting process. Keep not only the visible payment status but also the supporting evidence and continued access to, or exports of, the bank data.

What e-invoices do and do not solve

An e-invoice contains structured invoice data. This can make the invoice number, amount, supplier and tax details easier to process automatically. It does not confirm that the customer has paid. Payment occurs in the bank account or through another payment provider.

A sound process links the e-invoice and bank transaction with a clear reference. Keep the original structured data set of an e-invoice. A PDF rendering alone does not replace that structured original when the structured file is the invoice.

Security and access to the business account

Motorica connects business accounts through BANKSapi using a PSD2-based account-information service. The bank may require strong customer authentication or renewed consent. If authorisation expires or the connection is disconnected, synchronisation stops; transactions and matches already imported remain available.

Review which accounts are connected, who may see bank data and allocations, and whether former staff still have access. Grant only the rights needed for the task. Reading account information is not the same as initiating a payment.

How reconciliation works in Motorica

Motorica compares positive bank transactions with unpaid invoices. If it recognises an invoice number and the amount agrees, it can update the payment status automatically. A differing amount creates a review case. Without an invoice number, a possible same-amount match is only proposed for review; several open invoices with the same amount remain ambiguous.

The Review area shows the invoice number, expected amount, actual payment amount, booking date, transfer reference and customer. You can confirm the suggestion as paid or reject it. Reconciliation history also records which runs occurred and how many transactions were imported, matched automatically or held for review.

The limitation is deliberate: Motorica matches clear incoming payments, but it does not independently decide the commercial meaning of uncertain partial payments, set-offs or disputed cases.

Checklist for a clean reconciliation

• Have you included every relevant business account and the correct period?
• Does every outgoing invoice have a unique invoice number?
• Do invoice number, amount, payer and transfer reference agree?
• Have you checked whether the amount is already matched elsewhere?
• Are partial payments recorded with the remaining balance still open?
• Are combined payments distributed across every affected invoice?
• Have overpayments, discounts, fees, credit notes and refunds been resolved?
• Were incorrect proposals rejected rather than merely ignored?
• Do the invoice, bank transaction and decision remain traceably linked?
• Are unpaid or overdue invoices marked for the next action?
• Are account access and user permissions current?
• Are bank data and records available for the applicable retention period?

Common errors and the better approach

• Searching by amount only: Identical amounts occur frequently. Compare invoice number, payer and reference together.
• Treating a partial payment as full payment: The remaining debt disappears from the open list. Record the partial payment and outstanding balance separately.
• Assigning a combined payment to one invoice: Other invoices remain incorrectly unpaid. Allocate the amount transparently.
• Equating an incoming payment with correct bookkeeping: The invoice, supply, tax treatment or evidence can still be wrong. Treat reconciliation as one part of the complete process.
• Leaving uncertain matches untouched for months: Open items and cash information become unreliable. Use a fixed review routine with clear responsibility.
• Overwriting invoices or transaction records: The audit trail is lost. Add traceable corrections while preserving originals.
• Using an e-invoice as proof of payment: It proves billing information, not receipt of money. Match the bank transaction separately.

Frequently asked questions

Is bank transaction reconciliation required by law?

There is no general rule that requires every self-employed person to perform a weekly process with this name. Required postings and records must nevertheless be complete, correct, timely and orderly. Regular reconciliation is a practical control that supports these requirements and a reliable open-item list.

When may an invoice be marked as paid automatically?

Only when the match is sufficiently clear. In Motorica, a recognised invoice number together with a matching amount can be processed automatically. Partial payments, differences, missing numbers and multiple candidates require manual review.

What should I do with a partial payment?

Allocate the amount received to the invoice, keep the remaining balance open and document any agreement or customer query. Do not mark the invoice fully paid until the balance has been paid, validly waived, offset or corrected.

Is a bank statement enough as evidence?

A bank statement proves the bank movement, not necessarily the entire business transaction. Depending on the case, you also need an invoice, contract, credit note, receipt or other records. The evidence required depends on what actually occurred.

What is the difference between bank and payment reconciliation?

Payment reconciliation focuses on assigning individual payments to invoices. Bank reconciliation can be broader and verify that all bank movements and the bank balance agree with the accounting records. Motorica’s workflow focuses on payment matching for unpaid invoices.

Can software complete the entire reconciliation?

Software can automate clear matches and sort exceptions. Partial payments, combined transfers, chargebacks, set-offs and disputed cases still require a human decision. If the tax treatment is unclear, involve a qualified tax adviser.

Conclusion

Good reconciliation does not try to turn as many transactions green as possible. It separates reliable matches from genuine review cases. A unique invoice number and matching amount enable fast allocation. Partial payments, differences and ambiguous transactions remain visible until resolved.

This makes unpaid invoices more reliable, payment reminders more targeted and bookkeeping easier to follow. Reconciliation is a control within the wider invoicing and accounting process, not a substitute for it.

Next step

Connect your business account, review suggested matches and resolve exceptions before confirming invoices as fully paid.

Start payment reconciliation in Motorica

Sources and date

Information checked on 26 September 2026.

• Section 146 of the German Fiscal Code – record-keeping rules
• Section 147 of the German Fiscal Code – retention of records
• Section 14b of the German VAT Act – invoice retention
• German Ministry of Finance – second GoBD amendment of 14 July 2025
• BaFin – PSD2 and account-information services

This article provides general information and does not replace legal or tax advice. Ask a qualified tax adviser about unresolved postings, special tax cases or doubts about the correct treatment.