A banking integration retrieves account transactions and links them to company documents. It goes beyond marking an order paid. Establish whether payment is confirmed, which contract it belongs to and how to handle a payment reference that cannot identify the order automatically.
Distinguish statements from payment initiation
Retrieving statements and submitting payment instructions are different scenarios with different permissions. Incoming payment reconciliation generally starts with reading transactions. Do not grant payment creation capabilities when they are outside the agreed scope.
Check the specific bank’s official API or module, eligibility for company accounts and current terms. For example, Privat24 for Business documents balance and transaction integration. This does not mean every bank has identical fields, limits and access rules.
Match transactions using reliable identifiers
Retain each transaction’s bank identifier, account, amount, currency, date and required counterparty details. Reimporting the same period must not create another payment. Import history supports reconciliation as well as technical diagnostics.
An invoice number in the payment reference helps but is not always sufficient. Check the payer, currency and outstanding amount. If matching produces several candidates, send the record for manual confirmation rather than attaching it to the first customer found.
Plan partial payments and exceptions
For example, a customer may pay advances against several invoices in one transfer. The system should support the agreed allocation and show unallocated amounts. Bank fees, refunds and payments from another legal entity also need explicit rules.
Do not confuse receiving a notification with final accounting recognition. Retain statuses and check the bank’s documentation for possible transaction updates. The responsible accountant confirms posting rules; the manager sees the settlement status they need.
Protect access and verify completeness
Store credentials on the server outside public files. Logs must not reveal keys or unnecessary banking details. Agree access revocation, secret rotation and ownership of integration recovery. An employee’s departure must not leave an unknown banking credential active.
Test reimports, missed periods, bank outages and manual matching corrections. After launch, reconcile transaction counts and amounts against the statement. An absence of error messages does not prove every receipt reached accounting.
Sources and further reading
