To import a bank statement into Sage 50, open Tasks, then Account Reconciliation, pick the bank account and click Import to load an OFX or QFX file. Sage 50 matches the lines to transactions you have entered. A CSV goes in another way, through a field template under File, then Select Import/Export, with columns in a fixed order.
Which Sage 50 import route suits your bank statement file?
Sage 50 has two routes for bank data, and the file you hold decides which one you use. An OFX or QFX file goes into Account Reconciliation as a statement. A CSV goes through the general import templates, where each row becomes a transaction. This post follows the US Sage 50 help; other countries' editions lay things out differently.
The two routes do different jobs, which is the part people miss. The statement import does not create your books. It brings in the bank's records so Sage 50 can tick off transactions you already entered. The template import does create entries, so it is the one that can double your figures if you run it twice.
| Point | Statement import (OFX or QFX) | Template import (CSV) |
|---|---|---|
| Where it starts | Tasks, Account Reconciliation, Import | File, Select Import/Export |
| What each line becomes | A bank record to match and clear | A new transaction in a journal |
| Column mapping | None; the file carries its own tags | You set the fields and their order |
| Main risk | Unmatched records left to clear by hand | Duplicate entries from a repeated import |
If your bank offers a download for Quicken or Microsoft Money, take that and use the statement import. Choose CSV when the bank has nothing else, or when the transactions are not in Sage 50 yet and you want them there.
If you use the cloud product called Sage Accounting rather than the desktop Sage 50, the steps are different again. Importing a bank statement into Sage Accounting covers that product.
Importing an OFX or QFX statement through Sage 50 Account Reconciliation
The Sage 50 statement import sits inside Account Reconciliation. Sage's help article on importing a bank statement into Sage 50 says the Import Statement wizard reads a file in standard OFX or QuickBooks QFX format, and works even when your bank does not send statements to Sage 50 directly.
The steps, following that article:
- Download the statement from your bank in OFX or QFX format for one statement period.
- In Sage 50, open the Tasks menu and choose Account Reconciliation.
- In Account to Reconcile, pick the bank account. Type a question mark to see the list.
- Click Import. The Import Statement window opens.
- Use Browse to select the file, so its path shows in Statement Location.
- Click Import. Depending on the bank, Sage 50 shows a Select Account or an Enter Account window. Fill it in and click OK.
- Read the summary of the statement's contents that Sage 50 shows after a successful import.
The article says the import brings in every debit and credit in the file, plus interest and service charge items. Those last two are the lines most often missing from your own entries, because nobody writes a check for a bank fee.
After the first import, Sage 50 remembers the bank account it came from and shows a Change Account button. Use it if the next file belongs to a different account. Leaving the old account selected is an easy way to send a savings statement into checking.
Setting up a Sage 50 CSV import template and its field order
A CSV goes into Sage 50 through a field template that you set to match the file column by column. Sage's help on importing data into Sage 50 says the import fails if the fields shown in the template do not match the order and number of columns in your file.
The setup, in the order that article gives it:
- Open File, then Select Import/Export.
- Choose the program area, such as General Ledger or Accounts Payable, then the template within it.
- Click Import. The template opens on its Fields tab.
- Tick Show for each field your file contains, and only those.
- Use Move to put the fields in the same order as the columns in your file.
- On the Options tab, point to your CSV and tick First Row Contains Headings if the file has a header row.
- Save the template under a new name so you can reuse it, then click OK.
A worked field-order example
The example below shows a bank CSV and the field order the template needs. Field names and values are illustrations; use the names your template actually lists.
| Column in your CSV | Example value | Template field to tick, in this position |
|---|---|---|
| 1 | 03/14/2026 | Date |
| 2 | DEP-0314 | Reference |
| 3 | Deposit, Lakeside Design | Description |
| 4 | 10200 | GL account (the bank account's ID) |
| 5 | 1250.00 | Amount |
If the bank's CSV has a sixth column, such as a running balance, either delete it from the file or tick a field for it. An untracked extra column shifts every value after it, which is how a balance ends up in an amount field.
Order matters in a second way. The same help article warns that some data must exist before other data can be imported; you cannot import receipts before the customers and accounts they refer to. Import the chart of accounts and lists first if the company file is new.
The same fixed-order discipline applies when you load other spreadsheets into desktop accounting software. Importing invoices into QuickBooks Desktop from Excel shows it for sales invoices.
How does Sage 50 match imported bank records to existing transactions?
After a statement import, Sage 50 tries to match each bank record to a transaction you already entered. Sage's article on manually matching an imported bank record says matched lines appear as autocleared in Account Reconciliation, and lines it cannot match appear as new bank records you must deal with before reconciling.
To clear a new bank record:
- In Account Reconciliation, select the first new bank record.
- Right-click and choose Manual Match.
- The Manual Matching window lists Sage 50 transactions with the same dollar amount. Select the one that fits.
- If nothing fits, click Skip this record, then OK/Next for the next one.
A new bank record with no match usually means one of two things. The transaction is missing from your books, such as a bank fee, so enter it and come back. Or the amounts differ by a few cents, so the right transaction never appears in the list. Look up the transaction by date and fix its amount.
The same article warns that an automatic match can be wrong. Two checks for the same amount in one month are the classic case. Select the line, use Clear to undo the match, then Manual Match to pair it correctly.
Checking a Sage 50 bank import against the paper statement
A Sage 50 bank import is complete when the account reconciles to the statement's closing balance with nothing left over. Enter the statement date and the statement ending balance in Account Reconciliation, as the reconciliation window asks, and the difference should come to zero once every record is matched or cleared.
Work through this checklist with the statement beside you:
- The statement date matches the last day of the bank's statement period.
- The ending balance is copied from the statement, not from the bank's website on a later day.
- Every new bank record is matched, entered, or deliberately skipped with a note.
- Interest and service charges from the file now exist as transactions.
- After a CSV template import, the count of new journal lines equals the count of rows in the file.
If the difference is not zero, compare totals rather than lines first. Add up the deposits on the statement and the deposits Sage 50 cleared. The side that disagrees tells you where to look.
Bookkeepers who also keep a client on QuickBooks will recognise this routine. Importing bank transactions into QuickBooks Solopreneur shows the lighter version of the same check in that product.
Corrected bank statements and duplicate records in Sage 50
A corrected statement is the edge case that causes duplicates in the Sage 50 statement import. Sage's import article warns that importing a statement again after the bank corrects it can result in duplicate bank records, and points to a separate procedure for importing a corrected statement.
The manual-matching article gives the key step in that procedure: the bank records from the first import must be cleared, using the same Clear command that removes a match, before the corrected file goes in. Otherwise the corrected lines arrive next to the originals, and Sage 50 shows two records for the same deposit.
Two habits keep this rare:
- Wait for the statement to close. Import a statement once the period has ended, not a mid-month activity file that the bank may still change.
- Keep one file per period. Name each download with the account and the month, and import each one once.
The CSV route has its own version of this mistake. Running the same template import twice creates every transaction twice. The import help mentions a Warn if Duplicate Reference option on the Options tab that warns about repeated check or receipt numbers, but only for payments, payroll and receipts, so do not rely on it for every template.
If the statements you need exist only as PDFs and the books are in QuickBooks Online or Xero, SimpleBankConvert is being built to turn those PDFs into an import-ready CSV or QBO file. Accounts are not open yet, and the homepage explains what it is being built to do.