Turn a PDF or scanned bank statement into a clean CSV that Dynamics 365 Business Central can import on the Bank Acc. Reconciliation page.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
Dynamics 365 Business Central imports bank statements as delimited files, not as PDFs. On the Bank Acc. Reconciliation page you choose the Import Bank Statement action and pick a comma or semicolon delimited file, and if your bank's layout is not supported out of the box you define it once with the Set up a bank statement file format assisted setup. The other routes in are SEPA CAMT XML and the Envestnet Yodlee bank feed, which is available online only and only for banks in the United States and Canada. Since a PDF statement fits none of those, converting it to CSV first is the practical step, and the column order is then handled by a data exchange definition.
Business Central is happy to import a bank statement, as long as it arrives as structured, delimited data with a format definition behind it. Most finance teams have neither.
The Import Bank Statement action expects a file or stream from the bank in a defined layout. A PDF from online banking, and certainly a scan of a posted statement, is not something any data exchange definition can parse.
The Envestnet Yodlee bank feed only runs on Business Central online, and Microsoft supports it only for banks in the United States and Canada. On-premises deployments need a co-brand account and custom code, so plenty of teams never get a feed at all.
Microsoft notes that in the North American versions the Bank Rec. Worksheet page suits checks and deposits but does not let you import bank statement files. Teams land on that page, find no import action, and assume the feature is missing.
Column order, date format and how negative amounts are marked all vary by institution. Without a matching data exchange definition the import either fails or loads amounts with the wrong sign.
Banks typically serve around 90 days of downloadable transactions while statements go back years, so any catch-up, migration or audit request runs past what the download screen or the feed can return.
Keying a statement in by hand is where transposed amounts come from, and they surface later as a reconciliation that will not balance and a difference nobody can trace to a specific line.
One gap to bridge: you have a PDF, and Business Central wants delimited rows it can map to fields.
Export CSV with one row per transaction and consistent date, description and amount columns, which is what a data exchange definition needs in order to map reliably.
Image-only PDFs, scanned pages and photographed statements are read the same way as text PDFs, which matters for the older periods that exist only on paper.
Up to 50 statements per upload, each up to 50MB, with an option to merge one account's monthly PDFs into a single continuous file before extraction.
Each conversion is checked against the statement balances, so a misread amount is flagged before the file reaches your reconciliation rather than during it.
Debits and credits keep their sign, so you can map a single amount column rather than leaning on the Negative-Sign Identifier to flip values during import.
Community banks and credit unions that offer no feed and no structured export still produce statements, and those convert like any other.
Convert the statement, define the layout once, then import against the bank account.
Upload the PDF or scanned statement here and export CSV, keeping one row per transaction with date, description and amount columns.
Tip: Convert a whole year in one batch if you are loading history rather than a single month.
Run the Set up a bank statement file format assisted setup to describe the delimited layout and attach the format to the bank account, so later imports need no extra work.
Tip: The underlying settings live on the Data Exchange Definition and Data Exchange Mapping pages if you need to adjust them.
Search for Bank Account Reconciliation, choose New, select the bank account, then enter the Statement Date and the Statement Ending Balance from the printed statement.
Tip: In North American versions, the Bank Rec. Worksheet page cannot import files. Use the Bank Acc. Reconciliation page instead.
Choose Import Bank Statement, open the CSV, and the transactions fill the Bank Statement Lines pane. Then use Match Automatically or Match Manually before posting.
Tip: Run the Test Report before posting to check the reconciliation adds up.
Usually finance teams dealing with accounts or periods the bank feed does not reach.
A reconciliation cannot wait for a feed that is down or an account that was never linked, and the statement is always available.
A new implementation needs prior-period history loaded so opening balances reconcile, and that history lives in statements rather than in a 90 day window.
The Yodlee feed is not supported on-premises without a co-brand account and custom code, so file import is the standard route for those installations.
Auditors ask for periods that predate the current feed, and converted statements produce a dataset that ties directly back to the source documents.
Business Central imports bank statements as comma or semicolon delimited files, as SEPA CAMT XML, or as a stream from the Envestnet Yodlee bank feed. There is no PDF route. If your bank delivers a layout that is not supported out of the box, the Set up a bank statement file format assisted setup lets you define flat file, comma-separated or semicolon-separated formats and attach them to a bank account.
| Route in | Supported | What to know |
|---|---|---|
| CSV, comma or semicolon delimited | Yes | The usual manual route. Needs a data exchange definition describing the columns, created once per bank layout. |
| Flat text file | Yes | Handled by the same assisted setup as delimited files when the bank sends fixed-width or plain text. |
| SEPA CAMT XML | Yes | Built in, with its own field mapping. Common in Europe, rare on US accounts. |
| Envestnet Yodlee bank feed | Online only | Supported for banks in the United States and Canada. Not supported on-premises without a co-brand account and custom code. |
| OFX or QFX | Not out of the box | Unlike NetSuite, Business Central has no built-in OFX parser. Export CSV for Business Central instead. |
| PDF statement | No | Not an input to any import route. Convert it to CSV first. |
Search for Bank Account Reconciliation and choose the related link, then select New. Pick the account in the Bank Account No. field, enter the Statement Date and the Statement Ending Balance from the printed statement, then choose the Import Bank Statement action and open your file. The transactions appear in the Bank Statement Lines pane, ready to be matched against the bank account ledger entries in the pane beside it.
From there, Match Automatically compares text on the statement lines against the ledger entries, with a Transaction Date Tolerance in days that widens the search around each posting date. Anything it cannot resolve you match by hand with Match Manually. Before posting, the Test Report gives you a preview of whether the reconciliation actually balances, which is a cheaper way to find a problem than posting and reversing.
This one catches out a lot of US users, and it is not a bug. Microsoft documents that the North American versions offer a Bank Rec. Worksheet page which is better suited to checks and deposits but does not let you import bank statement files. If that is the page you are on, the import action is genuinely absent.
The switch between the two is the Bank Recon. with Auto. Match field on the General Ledger Setup page. Clearing it gives you the worksheet, and leaving it on gives you the Bank Acc. Reconciliation page where Import Bank Statement lives. The same toggle governs whether you can undo a posted bank reconciliation, since the Undo action is not available for bank statements posted from a reconciliation worksheet.
A data exchange definition has two halves. The Data Exchange Definition page describes how lines and columns in the file are laid out, and the Data Exchange Mapping page connects those columns to fields in Business Central. Setting it up takes a few minutes for a given bank layout, and once the format is attached to the bank account every later import for that account just works.
The field worth knowing about is the Negative-Sign Identifier. Some banks export files that cannot hold a minus sign and instead mark withdrawals with a separate indicator, and this setting names the value that means negative so the amounts are reversed during import. If your statement already exports debits as negative numbers, as the CSV from this converter does, you can leave it alone and map a single amount column.
Date format is the other place imports go wrong quietly rather than loudly. Confirm that what the definition expects matches what is actually in the file, because a mismatch that still parses will place transactions in the wrong period and only show up when the statement date filter hides half of them.
This is the usual reason teams convert statements rather than waiting on a connection. Bank download screens serve roughly the last 90 days, and the Yodlee feed is designed to keep a linked account current rather than to backfill years, with the Automatic Bank Statement Import Setup asking for a Number of Days Included that Microsoft suggests keeping at seven or more. None of that helps when a new implementation needs two years of history so opening balances reconcile.
Statements are the complete record, so convert them as a batch. Up to 50 documents go into one upload, and when they all belong to the same account you can merge them first, so twelve monthly PDFs come back as one continuous file for the year. The bulk bank statement converter page covers how batching and merging behave in more detail.
Worth knowing if you work across both, or are choosing between them. NetSuite ships parsers for OFX, QFX, CSV, BAI2 and CAMT.053, so a converted OFX file imports without any column mapping at all. Business Central has no OFX parser out of the box, and instead gives you a flexible definition layer that can be taught almost any delimited layout once you invest the setup time.
Neither approach is better in the abstract. NetSuite gets you moving faster on a one-off import, and Business Central handles an odd bank export more gracefully once the definition exists. What it means in practice is that the format you export depends on the destination: CSV for Business Central, and OFX for NetSuite, which the NetSuite bank statement import page covers in full.
Business Central imports comma or semicolon delimited files, flat text files, SEPA CAMT XML, and streams from the Envestnet Yodlee bank feed. PDF is not supported by any route. For a statement you downloaded as a PDF, convert it to CSV and define the layout with the Set up a bank statement file format assisted setup.
Search for Bank Account Reconciliation, choose New, select the bank account, then enter the Statement Date and Statement Ending Balance. Choose the Import Bank Statement action and open your file. The transactions fill the Bank Statement Lines pane, where you match them against bank account ledger entries before posting.
No. Every import route expects structured data, either a delimited file, a flat file, CAMT XML or a bank feed stream, and a PDF is none of those. Converting the PDF to CSV first is the practical way in, and scanned or photographed statements convert the same way as text PDFs.
Not out of the box. Business Central has no built-in OFX parser, which is a difference from NetSuite, where OFX and QFX are handled by default parsers. For Business Central, export CSV and map the columns with a data exchange definition rather than trying to use an OFX file.
You are most likely on the Bank Rec. Worksheet page, which the North American versions offer for checks and deposits and which does not allow importing statement files. The Bank Recon. with Auto. Match field on the General Ledger Setup page switches between that worksheet and the Bank Acc. Reconciliation page where the import action lives.
The Envestnet Yodlee Bank Feeds service runs on Business Central online only and Microsoft supports it for banks in the United States and Canada. It is not supported on-premises unless you obtain a co-brand account from Envestnet and add code to integrate with the Yodlee API, so file import is the normal route for those deployments.
It specifies the value used in a data file to identify negative amounts, for files that cannot contain negative signs, and the identified amounts are reversed to negative during import. If your CSV already carries debits as negative numbers you do not need it, and can map a single signed amount column instead.
Use the Set up a bank statement file format assisted setup to describe a flat file or delimited layout and attach it to a bank account. The detailed settings live on the Data Exchange Definition page, which describes the lines and columns, and the Data Exchange Mapping page, which connects those columns to Business Central fields.
Convert them as a batch first. Up to 50 statements go into a single upload here, and when they all belong to one account you can merge them before extraction so a year of monthly PDFs becomes one continuous file. In Business Central you still reconcile period by period, entering the statement date and ending balance for each.
The file most likely marks withdrawals with an indicator rather than a minus sign, and the Negative-Sign Identifier in the data exchange definition has not been set to that value. Either set it, or export a CSV that already carries debits as negative numbers and map one amount column.
The NetSuite route, where OFX and QFX are read by default parsers.
PDF statement to a clean CSV, column and format notes.
Convert up to 50 statements in one batch, with merging.
The Sage Intacct route, where the assistant reads OFX.
Turn a PDF statement into an OFX file for software that reads it.
Conversion workflow for client and volume bookkeeping work.
Get started converting bank statements to OFX.
USD
per month
per month
$288 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
per month
$888 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
per month
$ charged today
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
