Acumatica Bank Statement Converter: Import Bank Statements into Acumatica as Excel or CSV

Last updated July 2026

What file formats does Acumatica accept for bank statement import?

The Import Bank Transactions screen in Cash Management reads OFX, QBO, QFX, and Excel files directly, using a statement reader service. Bank feeds handle BAI2 and BTRS files, plus American Express GL1025 files, through the feed mechanism. A plain CSV is not read by the standard importer, so it comes in through an import scenario that maps your columns. PDF is not on any of these paths.

How do I import bank transactions in Acumatica?

Open the Import Bank Transactions screen in Cash Management, select the cash account, and upload your file. For an OFX, QBO, QFX, or Excel file the statement reader loads the rows directly. For a CSV you run an import scenario that maps your columns onto the transaction fields. Review the loaded rows and save, then move to Process Bank Transactions to auto-match them against Acumatica payments, invoices, and receipts before reconciling.

Can Acumatica import a CSV bank statement?

Yes, but not on the standard importer. A CSV comes in through an import scenario, where you map each column to a field and add the values the file does not carry, such as whether a row is a receipt or a disbursement. That is why a converted CSV with a single signed amount column and stable headers is worth the small setup: the scenario you build once keeps working every month. If you would rather skip the scenario entirely, convert to Excel instead, which the Import Bank Transactions screen reads on its own.

Why the account identifier has to match

Acumatica maps an imported statement to a cash account by matching the bank account identifier in the file to the External Ref. Number on the cash account. If they do not match, the rows import but do not attach to the account, and the reconciliation has nothing to work with. A converted file lets you confirm the account number is present and correct before you upload.

Does Acumatica have bank feeds for US banks?

Yes. Acumatica bank feeds connect to more than 14,000 institutions through Plaid and MX, on a schedule you set, with machine matching against your Acumatica documents. Two limits matter. The feed pulls incrementally from the last imported date and does not backfill history before the connection, so the start of your fiscal year is not covered. And MX supports only US and Canada institutions, some banks deliver a file to an SFTP folder instead, and feeds can quietly stop after a Plaid reauthorization. Those gaps are import-from-statement cases.

Loading opening bank history during an Acumatica go live

Most implementations go live partway through a year, so the bank account starts empty while the business has months of activity behind it. Convert each monthly PDF, concatenate them into one file, import once per cash account, then reconcile forward. The guide to reconciling bank statements covers doing this across several accounts, and transaction categorization cleans up descriptions before they hit the ledger. If you support clients on other platforms there are matching guides for the NetSuite bank statement converter, the Business Central bank statement converter, and the SAP bank statement converter. Coming off QuickBooks? The QuickBooks bank statement converter handles the other side of that migration. Starting from a PDF? Use the bank statement converter.

The documents around the bank line

A reconciled bank account is only half the picture, because every payment line has a document behind it. Vendor invoices still have to be read and coded, which teams handling real volume do by automating accounts payable rather than typing them one at a time.