Import a Bank Statement Into Sage Intacct

Why Sage Intacct won't import your PDF

Sage Intacct handles bank activity in Cash Management, and it reads structured files, CSV, OFX, QIF, XLS, and XLSX, none of which is a PDF. A statement PDF is a printed page rather than a table of dated transactions, so Intacct has nothing to import or match against your books. When a bank feed is not set up for the account, or the bank is not one Intacct connects to, you are left with a document the system cannot use. Converting the statement to a CSV or OFX gives Intacct a file the Bank Transaction Assistant accepts, so the transactions come in ready to match rather than being keyed by hand.

The Bank Transaction Assistant file import

The current path is the Bank Transaction Assistant. Go to Cash Management, then All, then Transactions, and click the add control next to Bank transaction import files. Choose the bank or credit card account you are importing for, then drag and drop your converted file to upload it. Intacct reads the transactions and stages them for matching against the account. Because a converted statement comes out with clean, consistent columns, the upload goes through without the reshaping a malformed bank export can need, and the imported transactions stay in Intacct even after you reconcile.

Which format to convert to

Intacct accepts several formats, so the choice comes down to what carries the cleanest data. OFX, and its QFX variant, includes a unique identifier per transaction, which helps the matching engine and reduces duplicate risk. A CSV or Excel file is the most flexible when a bank only exports a spreadsheet, and QIF works as well, though it is the older option. Converting your statement straight to OFX gives Intacct the richest file, while CSV remains the practical fallback. Whichever you pick, the file needs the transactions laid out cleanly, which is exactly what a conversion produces from a PDF.

Rule-based matching and reconciliation

Intacct matches imported transactions automatically using the rules in the account's rule set, and the results appear on the Banking cloud tab for that account. To get clean matches, you build rules, add them to a rule set, and assign that set to the account, so an incoming payroll debit or a recurring vendor payment maps to the right entry every cycle. A converted statement feeds that engine the same activity a live feed would, which is what lets you reconcile a period the feed did not cover. The cleaner the imported data, the more the rules match on their own and the less you confirm by hand.

Feed vs file import, and privacy

A live bank feed is the smoother path for ongoing activity, so file import is the route for what it misses: an unconnected account, an unsupported bank, or a back period you need to reconcile. Note that Intacct's older classic import, under Reconciliation then Bank then Import, is being retired no earlier than May 2026, so the Bank Transaction Assistant is the path to use. Because these files hold real account activity, they are processed to build the CSV or OFX and then deleted automatically, with nothing retained on a server afterward, which keeps entity account data out of a third-party tool.

Frequently Asked Questions