Sign up Now and get 10 free credits.Sign up Now and get 10 free credits. Register new account
Business Central Import Bank Statement
Every way to import a bank statement into Dynamics 365 Business Central, and the most reliable one: the converter turns your PDF into a clean CSV that matches your Data Exchange Definition, so it imports on the Bank Acc. Reconciliation page without a format error. Free to try, online, no installation.
PDF (MAX. 10MB)
4.7/5
Business Central-Ready CSV
Business Central imports bank statements from a CSV mapped through a Data Exchange Definition. The converter turns your PDF into a clean CSV, one transaction per row, with the columns and consistent structure your Data Exchange Definition expects to map into the Bank Acc. Reconciliation Line.
Free & Online, No Install
This tool to prepare a bank statement for Business Central runs entirely online, free to try with no account and no card. There is nothing to install and it works the same on Windows, Mac, and Chromebook.
Clean CSV, Data Exchange Ready
Amounts come out clean with debit and credit handled correctly, dates in a consistent format, and only transaction rows, so the CSV imports on the Bank Account Reconciliation page without failing on structure.
PDF to a Business Central-ready file
How it works
Step 1: upload your PDF statement
Step 2: converted to a Business Central file
Step 3: import into Business Central
How Do You Import a Bank Statement into Business Central?
Business Central gives you three ways to bring in bank transactions: import a CSV file, connect your bank automatically through a service like Envestnet Yodlee, or key entries manually. In practice the CSV route is the most reliable, since the automatic feed is known to be patchy. To import, you set up a Data Exchange Definition that maps each column in your file to a field in the Bank Acc. Reconciliation Line table, attach that format to the bank account, then use Import Bank Statement on the Bank Account Reconciliation page. The catch: your bank hands you a PDF, and Business Central cannot read a PDF at all. So the first step is always to convert that PDF into a clean CSV. This converter does exactly that. It reads your PDF statement and returns a CSV, one transaction per row with consistent columns, ready for your Data Exchange Definition to map.
Upload any PDF bank or credit-card statement and the converter returns a clean CSV for Business Central. Amounts are written as clean numbers with debit and credit handled correctly, dates use a consistent format, and headers, the account line and balance subtotals are removed, which matters because a stray Closing Balance or header row imports as a bogus transaction line. Because everything happens online, there is nothing to install. You can prepare a bank statement for Business Central in seconds, free to try, whether your statement is one page or eighty, current or from prior years, typed or scanned.
Why Convert the PDF for the Business Central Import?
- Business Central cannot read a PDF, only CSVBusiness Central imports bank statements from a comma or semicolon delimited CSV, not PDF, which is just an image of your numbers. Its automatic bank feed through Yodlee is unreliable, so CSV is the recommended route. Since your bank gives you a PDF, this converter produces the clean CSV Business Central reads.
- Columns match your Data Exchange DefinitionBusiness Central maps each CSV column to a field in the Bank Acc. Reconciliation Line through a Data Exchange Definition. A messy export breaks that mapping. The converter outputs clean, consistent columns, Date, Description, Debit and Credit, so your Data Exchange Definition reads them the same way every time.
- Debit and credit handled the way BC expectsIn Business Central a debit often needs a Multiplier of -1 to import as a negative statement amount, or a Negative-Sign Identifier to flip the sign. The converter outputs clean debit and credit columns, so your Data Exchange Definition can apply the sign correctly and the amounts post the right way.
- No stray header or closing-balance rowsA common Business Central problem is a header or Closing Balance line importing as a fake transaction. The converter returns only real transaction rows, with headers, the account line and balance subtotals removed, so nothing bogus lands in the Bank Statement Lines pane.
- Free to try online, works with the format wizardBusiness Central's Bank Statement File Format wizard helps you define an import format from a clean sample file. The converter gives you exactly that: a consistent CSV you can point the wizard or your Data Exchange Definition at, free to try online, with no format to build from a messy export.
- Brings in old periods and scanned PDFsThe Business Central automatic feed does not reach old periods, and not every bank connects. The converter reads any date range with no limit, and scanned or photographed statements are handled with OCR, so you can load prior-year statements into Business Central for reconciliation, year-end close, or a data migration.
What This Tool for Business Central Bank Statement Import Does
1. Clean CSV for Bank Reconciliation
The converter produces a clean CSV for the Business Central Bank Account Reconciliation page, imported with Import Bank Statement. One transaction per row, so the rows land correctly in the Bank Statement Lines pane.
2. Mapped to Your Data Exchange Definition
Columns are clean and consistent, so your Data Exchange Definition maps each one to the Bank Acc. Reconciliation Line without adjustment, instead of forcing a raw bank export into the structure Business Central expects.
3. Debit and Credit With the Right Sign
Debit and credit come out in clean, separate columns, so your Data Exchange Definition can apply the Multiplier or Negative-Sign Identifier and post statement amounts with the correct sign, no manual fixing after import.
4. Only Transaction Rows, Nothing Bogus
Header rows, the account line, and Closing Balance or subtotal rows are removed, so Business Central does not import a fake transaction line, exactly the issue that trips up a raw bank CSV.
5. CSV, Comma or Semicolon
Download a clean CSV that fits the Business Central import, which accepts comma or semicolon delimited files. It carries clean Date, Description, Debit and Credit data, one transaction per row, ready to map.
Download a clean CSV that fits the Business Central import, which accepts comma or semicolon delimited files. It carries clean Date, Description, Debit and Credit data, one transaction per row, ready to map.
Three import methods compared
Business Central Bank Statement Import: Why the CSV and Its Mapping Decide Everything
Dynamics 365 Business Central gives you three ways to get bank transactions in: import a CSV, connect the bank automatically through Envestnet Yodlee, or type entries by hand. In practice the CSV route wins, because the automatic feed is widely reported as unreliable and manual entry defeats the purpose. But the CSV route has a setup that decides whether your import works on the first try: the Data Exchange Definition. This is where you map each column in your file, date, description, debit, credit, to a field in the Bank Acc. Reconciliation Line, and where you tell Business Central how to handle the amount sign, often a Multiplier of -1 on the debit column or a Negative-Sign Identifier so debits post as negative. Get the file right and the import is clean; feed it a messy export and columns misalign, debits post as positive, and a stray Closing Balance or header row imports as a fake transaction. On top of all this, your bank almost always gives you a PDF, and Business Central cannot read a PDF at all. A bank statement PDF is an image of your numbers, not structured data, so it has to be converted first. This page exists because the CSV and its mapping are where Business Central imports actually succeed or fail. When the converter turns your PDF into a clean CSV, one transaction per row, with debit and credit in separate columns, consistent dates, and only real transaction data, your Data Exchange Definition maps it cleanly and the statement loads on the Bank Account Reconciliation page ready to match. For finance teams and Business Central partners handling many statements, or bringing in historical periods for a go-live, that difference compounds. It is the gap between a file that imports in minutes and one you reshape by hand. The converter is engineered to produce the former, and it is free to try so you can verify the file on your own statement before importing.
Frequently Asked Questions
1. Is this tool for Business Central bank statement import free?
It is free to try: you can convert up to 6 statements with no account and no card to check the Business Central file for yourself. Create a free account and you get 10 free pages per month. Paid plans exist only if you need higher volume, and most one-off conversions cost nothing.
2. Can I import a PDF bank statement into Business Central?
No. Business Central imports a comma or semicolon delimited CSV, or SEPA CAMT, but not PDF. Since most banks provide only a PDF, you convert it first. This converter turns any bank's PDF into a clean CSV, ready for your Data Exchange Definition and the Bank Account Reconciliation page.
3. How do I import the CSV into Business Central?
Set up a Data Exchange Definition that maps your columns to the Bank Acc. Reconciliation Line and attach it to the bank account. Then open the Bank Account Reconciliation page, select the bank account, and choose Import Bank Statement to load the converted CSV into the Bank Statement Lines pane.
4. What is a Data Exchange Definition?
It is the Business Central setup that tells the system how to read your bank file: which column is the date, the description, the amount, and how to handle the sign. You map each column to a field in the Bank Acc. Reconciliation Line. The converter's clean, consistent columns make that mapping simple.
5. Why does my debit import as a positive amount?
Business Central needs a Multiplier of -1 on the debit column, or a Negative-Sign Identifier, to store debits as negative statement amounts. The converter keeps debit and credit in clean, separate columns, so your Data Exchange Definition can apply the sign and the amounts post correctly.
6. Does it convert scanned or old statements?
Yes. Scanned and photographed statements are read with OCR, and there is no date-range limit. Since the automatic feed does not reach old periods, this is how you import historical statements into Business Central for reconciliation, year-end, or a migration.
7. Does this replace the Yodlee bank feed?
It is a reliable alternative. The automatic feed through Envestnet Yodlee is known to be patchy and does not reach older periods. Converting your PDF to a clean CSV and importing it through the Bank Account Reconciliation page gives you a dependable route that works for any bank.
8. Which banks work, and is my Business Central data safe?
It detects layouts automatically across hundreds of bank and credit-card formats, so it works whatever your bank, including banks that do not connect to Business Central. Uploads are protected and removed after conversion, and no account is required to try it, so your data is not stored or shared.