Dynamics 365 Finance reconciles from camt.053, BAI2, and MT940 files, never a PDF, and there is no native US bank feed. Upload your PDF statement here and download a clean Excel or CSV with the date, description, and signed amount columns you need to reconcile the account. Start free, no credit card.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
Dynamics 365 Finance and Operations reads electronic bank statements in ISO 20022 camt.053, BAI2, and MT940 for Advanced bank reconciliation, and it will not read a PDF. It does not read a plain Excel or CSV natively either, so a spreadsheet only imports through a custom Electronic Reporting format. Convert the PDF to a clean Excel or CSV first, then reconcile it by hand on basic bank reconciliation, feed a custom import your team built, or check the data before you load a period the bank feed never covered.
Advanced bank reconciliation is powerful, but it only accepts a few structured file formats and has no built-in feed for US banks. Most of the friction is about getting a usable file for the account and period you actually need to reconcile.
Advanced bank reconciliation imports ISO 20022 camt.053, BAI2, and MT940 through Electronic Reporting. Your bank emails a PDF, which is on none of those paths, so it has to be converted first.
Unlike some ERPs, D365 Finance does not read a plain Excel or CSV out of the box. A spreadsheet only comes in through a custom Electronic Reporting format your team builds and maintains.
Finance and Operations has no built-in bank feed. Statement intake is file based, so every camt.053 or BAI2 file is downloaded from the bank portal, and third-party connectors cover only some institutions.
Microsoft notes that banks often diverge from the standard layout, so the Electronic Reporting mapping or transformation has to be adjusted per bank, and a mismatch makes the import fail.
If an account is on basic bank reconciliation rather than Advanced, there is no file import at all. You clear each transaction by hand against the statement, which is slow off a PDF.
Opening bank history from before a Finance and Operations go live, and closed or dormant accounts, rarely arrives as an electronic file. Those periods come off the statement PDF.
Upload the PDF and the converter reads the transaction table rather than the page layout, then writes a clean Excel or CSV you can reconcile against, feed to a custom import, or audit before loading.
Date, description, and amount come out in the same positions every month, so a custom Electronic Reporting format or a manual reconciliation sheet maps the same way each time.
Debits and credits are collapsed into a single signed amount so it is unambiguous which lines cleared as money in and which as money out.
Dates are normalized across the whole file, so a multi-page statement does not break the mapping partway down.
Convert a stack of monthly PDFs into one continuous list, which is how most go lives load opening bank history for reconciliation.
Opening and closing balances carry through so the reconciled period ties out against what D365 Finance expects.
256-bit encryption in transit and you can delete your uploaded files whenever you want.
No software to install and no credit card to start.
Upload your PDF statement above and download the result as Excel or CSV.
Tip: Concatenate months for a full go-live load.
Clear the lines against your bank transactions on basic reconciliation, or feed the file to the custom Electronic Reporting format your team built for Advanced reconciliation.
Tip: Confirm the account and signs before loading.
Run your matching rule set to auto-match statement lines against D365 Finance bank transactions, then finalize the reconciliation.
Tip: Review any lines the rules could not match.
Dynamics 365 Finance and Operations runs the finance function at large, multi-entity US organizations, where bank reconciliation spans many accounts and banks, and the electronic file rarely covers every account or period.
Load a client opening bank history during a go live, when no file or feed exists yet and everything arrives as statement PDFs.
Reconcile an account whose bank cannot deliver camt.053 or BAI2, or clear a period on basic reconciliation without keying every row.
Bring in operating, payroll, and closed accounts at banks the third-party connectors do not cover.
Pull statement data into Excel to tie out balances and test the reconciliation independently of the ERP.
Last updated July 2026
Advanced bank reconciliation in Dynamics 365 Finance and Operations imports three electronic statement formats through Electronic Reporting: ISO 20022 camt.053, BAI2, and MT940. Those ship as prebuilt Electronic Reporting configurations you assign to the bank account. A plain CSV or Excel is not read natively, and neither is a PDF. To bring a spreadsheet in, a team builds a custom Electronic Reporting format, which is why clean, stable columns matter.
| Format | Imports into D365 Finance? | Notes |
|---|---|---|
| ISO 20022 camt.053 | Yes | Built-in Electronic Reporting format for Advanced bank reconciliation. |
| BAI2 | Yes | Built-in format; common for US banks. |
| MT940 | Yes | Built-in SWIFT statement format. |
| CSV or Excel | Only via custom format | Needs a custom Electronic Reporting configuration; not native. |
| No | Convert to Excel or CSV, then reconcile or map it. |
Enable Advanced bank reconciliation on the bank account, assign a statement format such as the camt.053, BAI2, or MT940 Electronic Reporting configuration, then import the file on the Bank statements page and run your reconciliation matching rules. If the account is on basic bank reconciliation instead, there is no file import: you open the reconciliation worksheet and clear each bank transaction by hand against the statement. Converting the PDF to a clean Excel sheet makes that manual clearing far faster than reading a scanned document line by line.
Not out of the box. Finance and Operations reads camt.053, BAI2, and MT940 for Advanced bank reconciliation, and a plain CSV or Excel is not one of those formats. Teams that want to import a spreadsheet build a custom Electronic Reporting format that maps the columns to the reconciliation model. A converted file with a single signed amount column and stable headers is what makes that custom format reliable month after month. When there is no custom format, the same clean spreadsheet is what you reconcile against manually.
Advanced bank reconciliation imports an electronic statement file and auto-matches its lines against D365 Finance bank transactions using reconciliation matching rules, so most of the work is machine matched. Basic bank reconciliation has no file import: an accountant marks each transaction as cleared by hand against the statement and enters the ending balance. Only Advanced reconciliation ingests a file, so accounts left on basic reconciliation are exactly where a clean, converted statement saves the most keying.
No native one. Finance and Operations does not include a built-in bank feed the way Business Central does with its Yodlee service. Statement intake is file based, so you download camt.053, BAI2, or MT940 files from each bank and import them. Third-party connectors on AppSource can automate some of that, but coverage varies by bank, and historical or closed-account data still tends to arrive as a statement rather than a feed.
Because there is no feed to backfill and the electronic file usually starts at the connection date, pre-go-live history comes off the statement. Convert each monthly PDF, concatenate them into one file, and use it to reconcile the opening periods in order, either through your custom import or by clearing lines manually. The guide to reconciling multiple bank accounts covers doing this across several accounts, and transaction categorization cleans up descriptions before they hit the ledger.
They are separate products with separate mechanics. Finance and Operations, the enterprise ERP covered here, reconciles from camt.053, BAI2, and MT940 through Electronic Reporting with no native feed. Business Central, the small and midsize product, uses bank export and import setup with data exchange definitions and includes a native Yodlee bank feed for US and Canada. If you run Business Central instead, use the Business Central bank statement converter. Teams on other platforms have matching guides for the SAP bank statement converter, the NetSuite bank statement converter, and the Acumatica bank statement converter. Starting from a PDF? Use the bank statement converter.
A reconciled bank account is only half the close, because every vendor payment line has an invoice behind it that still has to be read and coded. Finance teams handling real volume do that by automating accounts payable rather than keying invoices one at a time.
Enable Advanced bank reconciliation on the bank account, assign a camt.053, BAI2, or MT940 statement format through Electronic Reporting, then import the file on the Bank statements page and run your matching rules. On basic reconciliation there is no import, so you clear each transaction by hand against the statement, which a converted Excel sheet makes much faster.
No. Advanced bank reconciliation reads ISO 20022 camt.053, BAI2, and MT940 files, and PDF is not supported on any path. Convert the PDF to Excel or CSV first, then reconcile against it or feed it to a custom import your team built.
Not natively. A plain CSV or Excel is not one of the built-in statement formats, so it only imports through a custom Electronic Reporting format that maps your columns to the reconciliation model. A converted file with stable headers and a single signed amount column is what makes that custom format reliable, and the same clean sheet is what you reconcile against manually when there is no custom format.
Advanced bank reconciliation imports an electronic statement file and auto-matches its lines against D365 Finance transactions using matching rules. Basic bank reconciliation has no file import, so an accountant clears each transaction by hand against the statement. Only Advanced reconciliation ingests a file.
No native feed. Statement intake is file based, so you download camt.053, BAI2, or MT940 files from the bank and import them. Third-party connectors on AppSource can automate some of that, but coverage varies by bank and historical data usually still arrives as a statement.
Because there is no feed to backfill before the connection date, older history comes from the statement. Convert the monthly PDFs, concatenate them into one file, and reconcile the opening periods in order through your custom import or by clearing lines manually.
The most common cause is a format mismatch: the statement format on the bank account has to match the file, and banks often deviate from the standard layout, so the Electronic Reporting mapping needs adjusting. Check the job history execution log to see where parsing broke, and confirm you selected the right camt.053, BAI2, or MT940 configuration.
No. They are separate products. Finance and Operations reconciles from camt.053, BAI2, and MT940 through Electronic Reporting with no native feed, while Business Central uses data exchange definitions and includes a native Yodlee bank feed for US and Canada. Use the matching converter page for whichever product you run.
The Business Central side of the Dynamics family.
Prepare statements for SAP instead.
The same import on Acumatica.
From the same family of tools
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
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
billed as
$888 yearly
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
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
