Sage Intacct takes CSV, Excel, OFX, and QIF files, never a PDF. Upload your PDF statement here and download a CSV or Excel file with the date, description, and signed amount columns the import template expects. Start free, no credit card.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
Sage Intacct imports bank transactions through the Bank Transaction Assistant, which reads CSV, Excel, OFX, QIF, BAI2, and CAMT.053 files, and it will not read a PDF. The classic reconciliation import accepts a CSV or QIF built from a template with a posting date, a transaction type, and a signed amount. Convert the PDF to a clean CSV or Excel file first, then upload it under Cash Management for reconciliation.
The Bank Transaction Assistant is reliable. Most failed imports trace back to the shape of the file, or to a bank feed that never covered the period you need.
The import formats are CSV, Excel, OFX, QIF, BAI2, and CAMT.053. Your bank emails a PDF, so it has to be converted before Sage Intacct sees it.
The import fails on a header that is misspelled, capitalized differently, or has extra spacing. A converted file with stable, correct columns imports on the first try.
The classic template wants MM/DD/YYYY, and a blank row or stray whitespace triggers an Invalid date format error partway down the file.
You pick a three-column layout with a single signed amount or a four-column layout with separate money in and money out. Statements printing two columns have to be collapsed correctly, or withdrawals import positive.
Sage Intacct bank feeds run on Yodlee and start from a date you set once. Most banks provide only 30 to 90 days of history, so anything older comes off the statement PDF.
Yodlee limits connections to 20 accounts per institution, Chase supports only one connection, and a closed account has no live feed at all. Those cases are import-from-statement cases.
Upload the PDF and the converter reads the transaction table rather than the page layout, then writes a CSV or Excel file the Bank Transaction Assistant can take without hand editing.
Posting date, transaction type, description, and amount come out in the same positions every month, so the import maps cleanly each time.
Separate withdrawal and deposit columns are collapsed into a single signed amount, or split into money in and money out, whichever layout you import.
Dates are normalized across the whole file with no blank rows or whitespace, so you never hit the Invalid date format error mid-file.
Opening and closing balances come through with the transactions, so you can prove the statement ending balance on the reconciliation.
Convert a stack of monthly PDFs into one continuous list, which is how most Sage Intacct onboardings load opening bank history.
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 CSV or Excel.
Tip: Keep the same output columns every month.
In Cash Management, go to Transactions, add a bank transaction import file, and download the example template if you want to match it exactly.
Tip: Headers must match the template.
Select your converted file, choose the date order and amount layout, upload, then match the imported lines during bank reconciliation.
Tip: Check the statement ending balance.
Sage Intacct is a default cloud ERP for US mid-market companies, nonprofits, and SaaS finance teams, and the bank reconciliation is where a migration or a monthly close tends to stall, because the ledger needs history the feed cannot reach.
Load a client opening bank history during onboarding, when no feed exists yet and everything arrives as statement PDFs.
Catch up months of unreconciled bank lines for an account whose feed was never connected or dropped a period.
Reconcile restricted-fund and grant accounts at smaller banks the Yodlee feed does not cover.
Bring in a closed or legacy account against the authoritative PDF statement rather than a feed that may have missed items.
Last updated July 2026
The Bank Transaction Assistant, the current import path in Cash Management, reads CSV, Excel, OFX, QIF, BAI2, and CAMT.053 files. The older classic reconciliation import accepts a CSV or QIF built from a downloadable template. Neither path reads a PDF, so a statement that arrives as a PDF has to be converted to one of these formats first.
| Format | Imports into Sage Intacct | Notes |
|---|---|---|
| CSV | Yes | Three-column signed amount or four-column money in and out. |
| Excel (XLS, XLSX) | Yes | Only the first tab is processed. |
| OFX or QIF | Yes | Read directly by the Bank Transaction Assistant. |
| BAI2 or CAMT.053 | Yes | Bank-issued structured files, where your bank provides them. |
| No | Convert to CSV or Excel before importing. |
In Cash Management, open Transactions and add a bank transaction import file, then drag in your CSV, Excel, OFX, or QIF file. The Assistant offers an example template and an import guide during upload, and you tell it the date order and whether amounts are one signed column or split into money in and money out. On the classic path you open the bank reconciliation, choose the account, select Import, and upload a file matching the reconciliation transactions template. Either way the rows land as bank transactions you then match against Intacct entries.
The classic reconciliation template requires a posting date in MM/DD/YYYY, a transaction type of deposit or withdrawal, and a numeric non-zero amount, with negatives shown by a leading dash. Optional columns include document type, document number, payee, and description. The headers have to match the template exactly, down to capitalization and spacing, and a single blank row or stray space triggers an Invalid date format error. A converted file gives you clean headers, consistent dates, and no empty rows.
Because the import is unforgiving about shape, the value of converting straight from the PDF is consistency. Every statement comes out with the same columns in the same order and the same date format, so a file that imported last month imports again this month without hand editing.
A spreadsheet assembled by copying pages out of a PDF will import happily even when it is missing three rows. Nothing errors. The gap shows up at the end of the reconciliation, when the statement ending balance does not agree with the lines that loaded, and you spend an afternoon hunting a difference that was a page break. Converting from the PDF keeps every transaction and both balances.
The amount column is the other reliable trap. Statements that print withdrawals and deposits in two columns have to be collapsed into one signed value, and a manual paste usually leaves withdrawals positive, which inflates the balance and makes every later match wrong.
Yes, powered by Yodlee, with connectivity marketed to thousands of institutions. Two limits matter for reconciliation. The feed starts from a date you choose once, and most banks provide only 30 to 90 days of history, so it will not reach the start of your fiscal year. And Yodlee caps connections at 20 accounts per institution, with some banks supporting only a single connection, so busy or closed accounts fall back to the statement. Those are exactly the cases a converted file handles.
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 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 Xero 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.
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.
In Cash Management, open Transactions and add a bank transaction import file, then upload a CSV, Excel, OFX, or QIF file through the Bank Transaction Assistant. You set the date order and amount layout during upload, and the rows load as bank transactions you match during reconciliation. The classic path imports a CSV or QIF from the reconciliation screen instead.
No. Sage Intacct imports CSV, Excel, OFX, QIF, BAI2, and CAMT.053 files, and PDF is not supported on any import path. Convert the PDF into a CSV or Excel file with a posting date, a description, and a signed amount, then upload that through the Bank Transaction Assistant.
The Bank Transaction Assistant reads CSV, Excel, OFX, QIF, BAI2, and CAMT.053 files. CSV and Excel cover statements you convert yourself, while OFX, QIF, BAI2, and CAMT.053 cover structured files a bank issues directly. The exact list can vary by release, so check the import guide shown during upload.
The classic reconciliation template requires a posting date in MM/DD/YYYY, a transaction type of deposit or withdrawal, and a numeric amount with negatives shown by a leading dash. Payee and description are optional. Headers must match the template exactly, and blank rows or extra spaces cause an Invalid date format error.
Usually because a date is not in the expected order, or a blank row or trailing whitespace slipped into the file. The classic import wants MM/DD/YYYY. A converted file normalizes every date and removes empty rows, so the error does not appear partway down the statement.
The Yodlee feed starts from a date you set once, and most banks provide only 30 to 90 days of history. It will not reach the beginning of your fiscal year, will not cover a closed account, and is capped at 20 accounts per institution. Older or missing periods have to be imported from the statement instead.
Yes. The Bank Transaction Assistant reads XLS and XLSX files, though it processes only the first tab. The converter outputs both Excel and CSV, so you can review the data in Excel and import either format. Keep the columns in the layout the template expects.
Yes, they are separate products with different import screens. Sage Intacct is a cloud ERP using the Bank Transaction Assistant in Cash Management, while Sage 50 is a desktop product with its own import. Neither reads a PDF, so both need a converted CSV or a supported structured file.
The same import on Dynamics 365 Business Central.
The QuickBooks side of a migration.
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 |
