Use Motorica for twelve months at 59 € instead of 100 € per month.Offer valid until 31 August 2026Secure offer
Motorica
Start now
Motorica matches bank transactions with unpaid invoices

Banking & payments

Bank transaction reconciliation: match payments to invoices and review exceptions

How incoming payments are compared with unpaid invoices, when a match is reliable and which cases need manual review.

Photo by Franck

Bank transaction reconciliation compares incoming bank transactions with unpaid invoices. Clear matches can be assigned automatically; partial payments, batch payments, identical amounts and unclear payment references stay visible for review.

Bank transactions are matched with unpaid invoices in Motorica

What bank transaction reconciliation means in Motorica

Motorica retrieves bank transactions through the configured connection and compares incoming payments with unpaid invoices. The goal is not to automate every transaction blindly, but to close clear matches quickly and keep exceptions easy to review.

  • Set up the bank connection once
  • Synchronise new transactions
  • Use unpaid invoices as the matching basis
  • Separate clear matches, unpaid invoices and exceptions
Invoice number, amount and customer details are checked for payment matching

How Motorica identifies the matching invoice

Payment matching can use the amount, invoice number, payment reference and bank counterparty. The more details match, the more reliable the result. If important information is missing, the payment remains open for manual review.

  • Amount matches the unpaid invoice
  • Invoice number appears in the payment reference
  • Name or bank counterparty matches the customer
  • Ambiguous matches are not treated as reliable
Clear and ambiguous payments are handled separately

Automation only applies to reliable matches

Good bank transaction reconciliation saves checking time without hiding risk. If two invoices have the same amount, the payment reference is empty, or the payer and customer do not clearly match, the case needs review. Motorica lets you assign those payments manually.

  • Clear: assign the payment to the invoice
  • Ambiguous: show possible invoices for selection
  • Not found: leave the payment unresolved
  • Document the manual match with the payment date
Partial payment and remaining unpaid invoice amount

Partial payments, batch payments and incorrect payment references

Not every incoming payment matches exactly one invoice. Partial payments, batch payments and different payers can require additional checks. These cases should not be assigned too quickly. Check the invoice connection, document the decision and review the remaining unpaid amount.

  • Treat partial payments as review cases
  • Check the remaining unpaid amount
  • Do not assign batch payments to one invoice too quickly
  • Review different payers and payment references manually
  • Track refunds or cancellations separately
Bank account, invoice and payment status are connected

Open items show where payment or review is still missing

The open-items overview separates paid, unpaid and overdue invoices. That reduces switching between invoicing software, bank statements and spreadsheets. Accurate payment terms and regularly synchronised bank data are essential.

  • See due date and unpaid amount
  • Store the payment date after matching
  • Prioritise overdue invoices
  • Keep disputed cases separate from genuine non-payers
Business owner checks an overdue invoice before sending a formal payment demand

From payment reminder to formal payment demand

Motorica carries unpaid receivables forward into payment reminders and formal payment demands. Before sending anything, the payment status should be up to date. Disputed, paused or uncollectable cases need deliberate handling. Reminder texts and document backgrounds can be adapted to your business.

  • Check payment again before sending a reminder
  • Keep payment reminders and formal payment demands separate
  • Document pauses, disputes or uncollectable cases
  • Keep the formal payment demand PDF and email history traceable

The payment workflow starts with a well-structured invoice

Bank transaction reconciliation works best when invoice number, amount, customer, due date and bank details are correct. The full workflow runs from quote to invoice, delivery, payment and, if necessary, payment reminder or formal payment demand.

  • Use clear quote and invoice data
  • Use a unique invoice number and payment terms
  • Ask customers to include the invoice number as the payment reference
  • Run bank transaction reconciliation regularly, not only at month end

Bank data needs clear access rights

Bank transactions contain sensitive business and personal data. Access should therefore be limited to users who need it for their role. The bank connection is used to retrieve and reconcile transactions; this page does not describe initiating transfers.

  • Restrict access by role and task
  • Check bank access and the connection regularly
  • Do not store access details in free text or documents
  • Review unknown transactions with the right business context

Payment data for UStVA, EÜR and your tax adviser

Payment date and invoice connection are especially important for income-surplus accounting (EÜR), VAT advance returns (UStVA) and unpaid receivables. Motorica can bring payments and accounting documents together in a structured way. Direct DATEV transfer of accounting documents and final EÜR submission are not fully available from this workflow.

  • Separate paid and unpaid invoices
  • Use the payment date as a review point for EÜR
  • Resolve unclear transactions before handing data to your tax adviser
  • Prepare collaboration with your tax adviser

Setup, supported banks and limits

Whether an account can be connected depends on the bank, account type and available interface, and is checked during setup. Automatic matching cannot reliably infer missing or contradictory payment information. Cash, payment service providers and complex batch settlements may need additional checks.

  • Check bank and account type in advance
  • Choose the first synchronisation period deliberately
  • Review older unpaid invoices before you start
  • Document unclear special cases manually

FAQ

Frequently asked questions about bank transaction reconciliation and payments

What is automatic bank transaction reconciliation?

Automatic bank transaction reconciliation compares bank transactions with unpaid invoices and assigns clear incoming payments. Unclear cases remain open for review.

How do I set up bank transaction reconciliation?

Connect a supported bank account, choose the synchronisation period and review the first matches. Older unpaid invoices should be checked before you start.

How does Motorica find the correct invoice?

Motorica can use the amount, invoice number in the payment reference and the bank counterparty. The exact match depends on the quality of the transaction data.

What happens with a partial payment?

Partial payments are review cases. Check the invoice connection and the remaining unpaid amount. This page does not promise fully automatic handling of partial payments.

What happens if the payment reference is wrong or empty?

Motorica can check other details such as amount and counterparty. If the match remains uncertain, it is not treated as a clear result and must be reviewed manually.

Can I match a payment manually?

Yes. If a payment is not found or has several possible matches, you can select the suitable invoice and document the payment date.

How do open items and payment reminders work?

Unpaid and overdue invoices remain visible. After checking the payment status again, you can create payment reminders or formal payment demands, pause a case or mark it as disputed.

Can I adapt reminder texts and documents?

Yes. Reminder texts and document backgrounds can be set up for your workflow. Wording with legal or tax implications should be reviewed by a qualified adviser.

Which banks does Motorica support?

Availability depends on the bank, account type and technical interface. The specific account should be checked during setup; this page does not promise support for every bank.

Can Motorica initiate bank transfers?

This page only describes retrieving and reconciling transactions. It does not describe initiating transfers as a feature.

Does bank transaction reconciliation help with EÜR, ELSTER and DATEV?

Yes. Clearly matched payment data helps with EÜR, UStVA and tax adviser workflows. It does not automatically make direct DATEV document transfer or final EÜR submission available.

Where are the limits of automatic bank transaction reconciliation?

Missing payment references, batch payments, identical amounts, cash payments and external payment service providers can require manual review. Reconciliation does not replace accounting or tax review.

Stop searching for unpaid invoices between your bank account and a spreadsheet

Connect invoices, incoming payments and reminders in Motorica, with clear review cases instead of hidden automation.