How to import a bank statement into Sage 50 (U.S., UK and Canadian editions)

"Sage 50" is three different programs: the U.S. edition, Sage 50 Accounts in the UK, and the Canadian edition. Each imports bank statements through a different screen, takes different files, and does a different thing with them. This guide covers all three: which file each takes, the steps, why the U.S. import doesn't add anything to your books (and the CSV import that does), what to do with a PDF, and how to check the result against the statement.

1. Which Sage 50 you have, and what it imports

Search results and forum answers mix the editions up, and the menus don't carry over. Find your row first.

The rest of the guide takes each edition in turn. If you use Sage's cloud product (Sage Accounting) rather than a Sage 50 desktop edition, the import is under Banking and is closer to the UK screen; the sample OFX guide lists it.

2. Sage 50 U.S.: import an OFX or QFX statement

From Sage's knowledgebase article How do I import a bank statement? and the Sage 50 help page Import a Bank Statement:

1. Download the statement from your bank as an .OFX or .QFX file. Sage says to import bank statements one month at a time.
2. In Sage 50, select Tasks, then Account Reconciliation.
3. In Account to Reconcile, select the account, then enter the correct Statement Date.
4. Click Import, then Manually select a statement.
5. Click Browse, select the file, click Open, then Import.
6. Fill in the Select Account or Enter Account window that appears, and click OK. Sage 50 shows a summary of the statement's contents when the import works.

Three limits from the same pages decide whether this route is for you:

• It doesn't create transactions. In Sage's words, "Importing bank statements will not generate transactions in Sage." The import brings in the bank's debits and credits, plus interest and service charge items, so you can clear the transactions you've already entered. To add transactions, see section 4.
• Not in Pro Accounting. The article says the feature "is not available in Pro Accounting for Sage 50—U.S. Edition". On Pro, clear transactions by hand in Account Reconciliation.
• OFX or QFX only. Sage's help names "standard OFX or QuickBooks® QFX format". A CSV from your bank can't go in this way.

An OFX statement is a text file with the account, one entry per transaction and the closing balance. These lines are from the OFX Utilly writes for the sample statement:

<BANKACCTFROM><BANKID>999999999<ACCTID>0427<ACCTTYPE>CHECKING</BANKACCTFROM>
<STMTTRN><TRNTYPE>DEBIT<DTPOSTED>20260901120000<TRNAMT>-6420.18<FITID>20260901E26D1A27070800<NAME>ACH DEBIT GUSTO PAYROLL 0912<MEMO>ACH DEBIT GUSTO PAYROLL 0912</STMTTRN>
<LEDGERBAL><BALAMT>13440.52<DTASOF>20260930</LEDGERBAL>

Every tag is explained in sample OFX file.

3. Sage 50 U.S.: match and reconcile the imported lines

After the import, Sage 50 tries to match each bank line to a transaction already in the account. From Sage's help on manual matching and reconciling:

• Lines it matches are listed as autocleared.
• Lines it can't match appear as a new bank record. Select one, right-click and choose Manual Match. The window lists Sage 50 transactions with the same dollar amount; pick one, or click Skip this record.
• Enter the Statement Ending Balance from the statement. The Imported Interest and Imported Charges fields show amounts that came in with the statement; check them, and delete any duplicates in their window.
• Clear everything on the statement. As you do, Sage updates Outstanding Checks, Deposits in Transit and the Unreconciled Difference, which should end at 0.00.

If the bank corrects a statement, you can import it again as long as it's in the current period and none of its lines have been matched and cleared; the new lines replace the old. Lines already cleared are kept, so unclear them first (right-click, Clear), then import the corrected file, Sage's help says. Otherwise you can end up with duplicate bank records.

4. Sage 50 U.S.: create the transactions from a CSV

When the transactions aren't in Sage 50 yet, for example months you're catching up, the statement import has nothing to match. Sage's article points instead to its data import, File → Select Import/Export, which reads a comma-separated CSV and creates records. For bank lines, the General Journal template is the simplest. Customer receipts and vendor payments have their own templates (under Accounts Receivable and Accounts Payable) if you track who paid whom.

The General Journal fields you can import, from Sage's knowledgebase:

Each bank line becomes a two-line entry: the bank account on one side and the expense or income account on the other. These rows are the first two transactions of the sample statement, with made-up account numbers (10200 checking, 72000 payroll, 40000 sales). Use your own chart of accounts:

Date,Reference,Number of Distributions,G/L Account,Description,Amount,Recur Number,Recur Frequency
09/01/26,BANK0901-1,2,72000,ACH DEBIT GUSTO PAYROLL 0912,6420.18,0,0
09/01/26,BANK0901-1,2,10200,ACH DEBIT GUSTO PAYROLL 0912,-6420.18,0,0
09/01/26,BANK0901-2,2,10200,STRIPE TRANSFER ST-K2M8Q4,3184.27,0,0
09/01/26,BANK0901-2,2,40000,STRIPE TRANSFER ST-K2M8Q4,-3184.27,0,0

Money out of the bank is a credit (negative) to 10200; money in is a debit (positive). To import, from Sage's Import Data into Sage 50 help:

1. Back up the company. Choose File → Select Import/Export, then General Ledger and the General Journal template, and click Import.
2. On the Fields tab, tick Show for exactly the fields in your file, in the same order; use Move to reorder. "The import will fail if the fields in the file you are importing do not exactly match the order and number of the fields".
3. On the Options tab, select the file and tick First Row Contains Headings if it has a header row, then click OK. If a line is wrong, Sage reports the problem and its line number.

Sage's own tip is to export one existing entry first, with Include Headings ticked, to see the exact fields and order your version uses. Its Warn if Duplicate Reference option only covers Payments, Payroll and Receipts, so a General Journal file imported twice goes in twice. Keep one file per statement and note which ones you've imported. The lines from the bank statement are in the CSV Utilly writes (PDF statement to CSV); adding the account numbers is up to you.

5. Sage 50 U.S.: Sage Bank Feeds

Sage's import article sends users of version 2018.1 and later with a service plan to Bank Feeds. Its knowledgebase describes the setup: in Account Reconciliation, pick the account, then Bank Feeds → Connect to Bank Feed, sign in to your bank and choose a start date. Two points from that article matter here:

• "Bank Feeds is for U.S. banks only," and like the file import, "it doesn't create transactions within the system". If a downloaded line can't be matched, right-click the new bank record and choose Manual Match, or Create New to enter the transaction.
• The start date defaults to 90 days back and can't go back more than two years, and your bank may allow less. Don't pick a period you've already reconciled. Older months come from files: one OFX per monthly statement, as in section 2.

6. Sage 50 Accounts (UK)

In Sage 50 Accounts v30.1 and above, Sage's article Import bank transactions with Bank Feeds says you can import a statement file whether or not the account has an automatic feed:

1. Go to the Bank Feeds module. For an account without a feed, click Get started, then Import statement. For an account with a feed, open it, select Import, then Continue.
2. Select Continue on the welcome window, then Select a file from your device and open the file.
3. Click Review transactions. If asked, choose the date order your file uses.
4. Check the lines. If money in shows as money out, click Switch transaction types and Sage reprocesses the file.
5. Click Confirm import. The lines appear on the To be matched tab, ready to match with your Sage transactions.

The file types listed are .CSV, .BAI, .XML, .TXT, .OFX, .ASO, .QBO, .QFX, .QIF and .XLS. For a CSV, Sage's bank file format article (written for Sage Accounting's import) gives two layouts: Date, Description, Amount, with payments out negative, or Date, Description, Money in, Money out, in that order, dates separated by slashes and no blank descriptions. For OFX it says you can upload the file without editing, and only the first bank account in a file is imported. A file in the three-column layout looks like this (the sample statement's QuickBooks-style CSV, which uses U.S. month/day dates, so pick that order when asked):

Date,Description,Amount
09/01/2026,ACH DEBIT GUSTO PAYROLL 0912,-6420.18
09/01/2026,STRIPE TRANSFER ST-K2M8Q4,3184.27
09/02/2026,CHECK 2041,-1850.00

Utilly's statement reader has been built and tested on U.S. bank PDFs, so try the free preview on one UK statement before converting a year of them. If your bank exports CSV, CSV to OFX turns it into a file with no date-order question.

7. Sage 50 Canadian edition

The Canadian edition has two file routes, from Sage's Canadian help and knowledgebase:

• Import Online Statements (OFX). First set linked accounts for bank charges and income under Setup → Settings → General (Accounts) → Linked Accounts. Then choose File → Import/Export → Import Online Statements (or Import Online Statements in the Account Reconciliation window), follow the wizard and click Finish. Sage matches lines with the same dates and amounts, and the Match Transactions window opens for the rest: tick the matches and create transactions for the others. Sage's tip: rename each downloaded file, or the next download overwrites it.
• Upload to Bank Services (CSV or OFX). This needs a service plan that includes Bank Services. Go to Banking → Match Bank Transactions → Upload to Bank Services, pick a new or existing bank account, choose CSV or OFX, select the file and its date format (Year, month, day for an OFX), upload it, confirm each line as money in or money out, click Import transactions, then Get Transactions in the Match Transactions window. Sage's article says to use this route if you want bank rules.

8. When all you have is a PDF

None of the file lists above includes PDF. Sage's U.S. article says that if your bank only provides PDF statements, "there are third party software that can convert .PDF to .OFX or .QFX that can import into Sage via the Import button", and that Sage doesn't help troubleshoot those files. Many banks keep statement PDFs online longer than they let you download activity files, so older months for a catch-up often exist only as PDFs.

That's what Utilly's PDF to OFX converter does: it reads the statement, checks that the opening balance plus every transaction equals the closing balance, and writes an OFX file, plus a CSV of the same lines for a General Journal file or Sage 50 Accounts. Each statement becomes one file, which suits Sage's one-month-at-a-time rule. For a business years behind, catch-up bookkeeping from bank statements covers the order of work.

9. Check the import against the statement

Whichever edition you use, compare what came in with the statement before you reconcile. For the sample:

When the difference won't go to zero, finding bank reconciliation discrepancies shows how to find the line, and the free bank statement balance checker confirms the statement itself adds up.

10. Common problems

11. Convert your own statement

Utilly reads a bank or credit card statement PDF, checks every transaction against the opening and closing balances, and writes an OFX file for Sage 50's statement import plus a CSV of the same lines. PDF statements get a free preview; CSV, Excel and OFX files convert free up to 100 rows. Files are read in memory and not stored.

Utilly isn't affiliated with Sage. Menu names change between versions; the steps above are from Sage's help and knowledgebase, checked November 10, 2026, and weren't run in a live Sage 50 company. Sources: Sage 50 U.S., How do I import a bank statement? (OFX/QFX, one month at a time, not in Pro, no transactions created, PDF converters), Import a Bank Statement, Manually Match an Imported Bank Record, Reconcile an Account, Import a Corrected Bank Statement, Why does my OFX file fail to import?, Import Data into Sage 50, General Journal fields for Import/Export, How to reconcile my account using Bank Feeds; Sage 50 Accounts (UK), Import bank transactions with Bank Feeds, Supported file formats for bank statement imports; Sage 50 Canadian edition, Import a Bank Statement, Upload a Bank Statement to Bank Services, How to import a list of transactions using Bank Feeds. The sample statement is fictional.

FAQ

Related guides

• Free sample OFX file (bank and credit card), explained
• How to open an OFX, QFX or QIF file (Excel, Quicken, text)
• Catch-up bookkeeping: getting 12 months of bank statements into QuickBooks or Xero and reconciled
• How to find a bank reconciliation discrepancy: 7 causes and a 15-minute method
• Free sample bank statement files: PDF, CSV, QBO, IIF, QIF and Xero CSV
• Free sample bank statement PDF (fictional, with known totals)

Related tools

• Bank reconciliation checker: compare a bank statement to your books and list missing, duplicate and mismatched transactions.
• Receipt to CSV: turn PDF or photo receipts and invoices into CSV, Excel, or QuickBooks and Xero bill imports.