Hi,
It appears that BC is detecting multiple statements within the file you're trying to import. This warning typically appears when the file contains more than one logical statement block, which BC expects to be handled separately.
Let’s break down what’s happening and how to proceed:
1. Why the warning appears
BC’s Bank Account Reconciliation expects one statement per import session. If your file includes multiple statement headers, date ranges, or account identifiers, the system flags it to prevent mismatched reconciliation.
- This is common with consolidated bank files from multi-account setups or batch exports
- The system doesn’t automatically split or route these statements , it expects one statement per reconciliation record
2. How to handle multi-statement files
You have two options:
Option A: Pre-process the file externally
- Use Excel or a script to split the file into separate statement files
- Import each file individually into its corresponding Bank Account Reconciliation record
Option B: Customize the Data Exchange Definition
- Go to Data Exchange Definitions and review the import format
- Add logic to detect statement boundaries (e.g., based on date, account number, or tags)
- Use a custom processing codeunit to route each statement to the correct reconciliation record
This approach requires development effort but can automate multi-statement handling.
3. Assign the correct import format to the bank account
- Navigate to the Bank Account Card
- Set the Bank Statement Import Format to your customized format
- Then go to Bank Account Reconciliation and use Import Bank Statement
Helpful references:
Import and reconcile bank statements – Microsoft Learn
Create a bank statement import format – Valentin Castravet
Using bank statement imports – Fenwick Software
If you find this helpful, feel free to mark this as the suggested or verified answer.
Cheers
Jeffrey
