Bank statement processing in SAP Business One – how to set it up and use it correctly

Bank statement processing in SAP Business One with digital bank statements

Bank files can be imported electronically and used as a basis for incoming and outgoing payments.
The function is activated once under Administration → System Initialization → Company Details → Accounting Basics.
Main bank accounts, general ledger accounts, internal and external bank codes, and reconciliation criteria must be set up in advance.
Imported bank statement lines initially appear as parked documents and are checked before posting.
Up to three search rounds can assign open items based on criteria such as invoice number, amount, or customer number.
Bank statements must be imported and processed in chronological order.
camt.053 is the current ISO 20022 standard; the continued availability of MT940 depends on the individual bank.

The Bank statement processing in SAP Business One It reduces manual effort in banking: bank files are imported electronically, transactions are recognized based on predefined rules and compared with open items.

This guide shows, how to set up the function and use it in daily business. You will learn which formats are supported, how booking suggestions are generated, and how to avoid typical errors.

What does bank statement processing accomplish?

Without bank statement processing, incoming and outgoing payments must be entered manually and individually reconciled with invoices. This is time-consuming and increases the risk of errors when dealing with a large number of transactions.

With bank statement processing, the bank file is read directly into SAP Business One. The system evaluates the transactions based on defined bank codes and matching criteria and generates a report. System-supported booking suggestions.

Without bank statement processing	With bank statement processing
Manual reconciliation of each payment	Automatic detection based on defined criteria
Error-prone manual booking	System-generated booking proposal
No consistent bank reconciliation	Internal and external voting integrated
High workload with many receipts	Batch processing of entire bank statements

Setting up bank statement processing – but doing it right

We configure house bank accounts, bank codes and matching criteria so that bank statements can be processed reliably.

Request a free initial consultation

Supported formats: MT940, camt.053 and Multicash

The bank statement format used depends on the individual bank and its connection. For new institutions, this should generally be the case today. camt.053 based on ISO 20022 to be given preference.

format	standard	Classification	Recommendation
MT940	SWIFT	Older format, still available depending on the bank	Clarify existing usage and switching with your bank.
camt.053	ISO 20022 (XML)	Current standard with structured transaction data	For new and reconfigured connections, prefer
Multicash	Proprietary, SWIFT-based	Especially used with older bank connections	Only use if the existing connection requires it.

MT940 will be gradually replaced

The ISO 20022 coexistence phase ended in November 2025. However, it is unclear whether and for how long MT940 will continue to be provided. depends on the respective bank. Clarify the available formats directly with your bank and plan the switch to camt.053 in good time.

camt.053 provides structured information such as intended use, reference numbers, and counterparty data. This information can be used by automatic assignment to open items improve.

Setting up bank statement processing – step by step

The setup is a one-time process. If individual points are omitted or entered incorrectly, the import may fail or generate unsuitable booking suggestions.

Step	Proceed
1. Activate function	Under Administration → System Initialization → Company Details → Accounting Basics, activate bank statement processing.
2. Configure your main bank account	Under Administration → Setup → Banking → Main Bank Accounts, enter the bank account, import format, general ledger account and interim general ledger account.
3. Define internal bank codes	Create transaction types such as customer payment, supplier payment, fee or direct debit with the desired booking logic.
4. Assign external bank codes	Assign the codes from the bank file to the internal bank codes. Missing assignments will prevent automatic recognition.
5. Define matching criteria	Define up to three search rounds, for example first invoice number, then amount, and then customer number.
6. Book opening balance	Record the current account balance when using the device for the first time, so that subsequent balance comparisons are correct.
7. Reconcile the account assignment	Clarify the allocation of general ledger and interim accounts for fees, interest and unassignable items with your tax advisor before going live.

Import bank statement and edit booking proposal

The daily process starts under Banking → Bank Statements and External Reconciliations → Bank Statement Processing. The processing then proceeds as follows: five consecutive steps.

Step	Proceed
1. Select your main bank account	Select the desired bank account from the list.
2. Import bank file	Read the MT940 or camt.053 file. The lines will initially appear as parked documents.
3. Show booking suggestion	Open a bank statement line by double-clicking. SAP Business One displays the suggestion based on the defined rules.
4. Review proposal	Check business partner, document, and amount. Manually add any missing allocations or post to a clearing account.
5. Book and vote	The booking process executes the journal entry and reconciliation; the associated open item is cleared.

Maintain chronological order

Bank statements must in the correct chronological order They are imported and processed. This prevents conflicting balances in SAP Business One.

Internal and external coordination

When posting from bank statement processing, two levels of reconciliation are taken into account. Internal voting connects transactions within SAP Business One. external voting reconciles system entries with actual bank statements.

Voting method	What is being compared?	Example
Internal vote	Business partner accounts and general ledger accounts within the system	An incoming payment settles an outstanding outgoing invoice.
External voting	System transactions and actual bank statement lines	A booked payment is linked to the corresponding bank line.

Reset vote

An incorrect vote can be reset via Banking → Internal Voting or External Voting. The original booking remains valid.; only the link is broken and the open item becomes visible again.

Typical transaction scenarios

The internal bank codes determine which booking logic is applied. SAP Business One can therefore handle different payment situations.

scenario	Booking logic
Customer payment	Book incoming payment, settle outstanding outgoing invoice and reconcile internally.
Supplier payment	Book the outgoing payment and balance the creditor account.
Bank fees or interest	Direct posting to a general ledger account without business partner assignment
collective payment	Assigning one payment to multiple open invoices
Advance payment	Book to a down payment account and reconcile manually later.
Unattributable payment	Book to a transit or interim account and allocate later.
chargeback	Cancel payment and restore the original open item.

Process e-invoices in XML format with SAP Business One

Process e-invoices directly in SAP Business One

From structured incoming invoices to subsequent payments: Learn how SAP Business One processes XRechnungen and ZUGFeRD files and integrates them into end-to-end accounting processes.

More about e-invoicing

Common mistakes and how to avoid them

Error pattern	Caused	Solution
File is not recognized	Incorrect import format or non-compliant bank file	Check the format in your bank account and the bank's file.
Rows are not assigned	External bank codes are missing or incorrectly linked	Add assignments under External Bank Codes
False business partner	The matching criteria are too unspecific.	Refine search rounds and use unambiguous references
Chronology error	Extracts were imported in the wrong order.	Correct the import and import the extracts chronologically.
The balance is incorrect.	Opening balance is missing or incorrect	Check the balance and coordinate the correction with your tax advisor.

Frequently Asked Questions

Does bank statement processing need to be activated in SAP Business One first?

Yes. The function is activated under Administration → System Initialization → Company Details → Accounting Basics. Only then will the corresponding menu item be available in the banking section.

Which format should be used today – MT940 or camt.053?

camt.053 is the current ISO 20022 standard. and should be preferred for new connections. Whether MT940 will continue to be offered depends on the bank. camt.053 provides more structured data for automatic matching.

What happens to payments that cannot be allocated?

The transaction can initially be posted to a transit or interim account. Once the correct document is identified, the allocation is carried out via internal reconciliation.

Can a faulty vote be reversed?

Yes. Internal and external votes can be reset in the respective voting modules. The original booking remains; the open item becomes visible again.

Any remaining questions regarding bank statement processing?

Whether it's bank code assignment, matching criteria or switching to camt.053: We help you to set up bank statement processing cleanly and to fix errors in a targeted manner.