Import a Bank Statement Into Sage 100 Reconciliation

Why Sage 100 won't import your PDF

Sage 100, the mid-market ERP formerly known as MAS 90 and 200, reconciles bank accounts from a statement file, and it reads a range of them, OFX, QFX, QIF, CSV, and BAI among others, but not a PDF. A statement PDF is a printed page, not the structured bank data Sage 100 compares against your books. So a statement your bank sends as a PDF cannot go into Account Reconciliation as is. Converting it to an OFX or CSV produces the file Sage 100's import accepts, so the bank's record of the month can be matched against what the ERP already has recorded.

Account Reconciliation: select the account and import

The import lives in the reconciliation task. Go to Tasks, then Account Reconciliation, select the account to reconcile, and enter the correct statement date. Click Import, choose to manually select a statement, then Browse to the file you converted and open it. Sage 100 reads the transactions from the file and lays them alongside the account for matching. Because a converted statement comes out clean and consistently dated, it imports without the date-order and formatting snags that trip up a raw bank download.

Reconciliation only, not new transactions

This is the part that surprises people coming from a personal finance app: importing a bank statement into Sage 100 does not create transactions. The statement is used purely to reconcile, its lines are matched against entries the ERP already holds from general ledger, accounts payable, and accounts receivable postings. So the converted file is the bank's side of the reconciliation, the independent record you tick your books against, rather than a source of new entries. That distinction is why the conversion needs to be accurate: a misread amount would show as a false discrepancy during matching.

Which format to convert to

Sage 100 accepts several bank formats, and the structured ones behave best. An OFX or QFX file carries clean, dated transactions the import reads directly, and QIF works similarly, while CSV and BAI are also supported for banks that export those. If a converted OFX ever fails to import, the cause is usually a formatting or date-order issue in the file, which is exactly what a clean conversion avoids by writing a consistent date format. Converting your statement to OFX gives Sage 100 the least troublesome file to reconcile from.

Accuracy and privacy

Because the imported statement drives a reconciliation, every figure needs to be right, and each transaction is reviewable in the converter before export so a misread does not surface as a phantom discrepancy. The output is a clean OFX or CSV in the shape Account Reconciliation expects. Since the statement holds real company account activity, the file is processed to build it and then deleted automatically, with nothing retained on a server afterward, which keeps entity bank data out of a third-party tool once the reconciliation file is in Sage 100.

Frequently Asked Questions