How to Import Bank Transactions into Sage 50

Which file formats Sage 50 accepts

Both Sage 50 product lines, Sage 50 US (Sage 50 Accounting) and Sage 50 UK (Sage 50 Accounts), can bring in a downloaded bank statement, and both list OFX and QFX among their supported file types. OFX is structured financial data: each transaction already carries a date, an amount, a description and a unique ID, so Sage matches it against your bank account without you mapping columns by hand. QFX is Intuit's flavour of the same standard and imports the same way.

You can often import a CSV too, but Sage is strict about its layout, which is exactly why converting first saves time. If your bank gives you a CSV or Excel download, drop it into the converter, choose OFX (or QFX), and you get a clean, import-ready file in seconds. Everything runs in your browser, the statement is never uploaded anywhere.

Step 1: Convert your bank CSV or Excel file to OFX

1. Log in to online banking and download your transactions as CSV or Excel (XLSX/XLS). Export the data download, not a printed PDF statement.
2. Open QBO Maker and drop the file into the tool.
3. Map the columns once, typically Date, Description, and Amount (or separate Debit/Credit columns). The preview shows the parsed rows so you can confirm money out is negative before you export.
4. Choose OFX as the output format and download. If your Sage build prefers it, pick QFX instead, the import steps are the same.

The conversion happens client-side, so there is no upload step or file-size queue. Free handles a single statement with unlimited transactions; Pro adds batch multi-file conversion and saved per-bank templates if you import for several accounts each month, see pricing.

Step 2: Import the file into Sage 50

Exact menu wording differs by version and region, so treat these as the general path rather than a fixed click trail:

1. Open the Bank accounts (or Banking / Bank Feeds) area of Sage 50 and select the specific account the statement belongs to.
2. Look for the option to import or upload a statement, often found under the bank feeds / online-banking controls or a feed-rules menu for that account.
3. Browse to your converted .OFX (or .QFX) file and select it.
4. Confirm the account the file maps to, then review the incoming transactions. Sage reads the dates, amounts and descriptions straight from the file, so there is no column-mapping screen as there is with a raw CSV.
5. Match or post the transactions, then reconcile the account as usual.

In Sage 50 US the import sits under the bank account's online-banking / Account Reconciliation tools; in Sage 50 UK it lives within the Bank Feeds module via the Import statement button on the account. If you can't find an OFX import on your edition, check that bank feeds are set up for that account, that is what unlocks statement file import.

Getting dates right before you import

Wrong-month transactions are the single most common import headache, and it is almost always a date-order mismatch in the source CSV. A bank might export 03/04/2026 meaning 4 March (UK, DD/MM/YYYY) or 3 April (US, MM/DD/YYYY), and that order can be misread from a bare CSV.

• Set the date format in the converter to match how your bank wrote the file, then preview to confirm the parsed dates land in the right month.
• OFX removes the ambiguity entirely. The format stores each date as an unambiguous timestamp, so once it is converted, regional date order is no longer a guessing game.
• Watch the date-order prompt on import. Some Sage editions ask you to confirm the date order of the file as you import it; converting to OFX means the file already carries unambiguous dates, so there is nothing to second-guess.

Avoiding duplicate transactions

Re-importing an overlapping period is the usual cause of duplicates. A few habits keep your bank account clean:

• Convert only the new statement period. If you imported through 31 May last month, start the next export on 1 June rather than re-pulling May.
• Lean on the unique IDs in OFX. Each transaction in an OFX file gets a unique ID (FITID), which helps reconciliation software recognise lines it has already seen, an advantage a plain CSV cannot offer.
• Reconcile before the next import. Matching and clearing transactions first makes any accidental duplicate obvious in the next batch.

For a deeper walkthrough of the principle, see avoiding duplicate transactions, the same logic applies in Sage.

OFX vs CSV for Sage 50

• OFX (or QFX), structured, no column mapping, unambiguous dates, and unique IDs that help with duplicate detection. Best for clean, repeatable monthly imports into a bank account.
• CSV, possible on some editions, but you own the formatting: correct columns, regional date order, and a single signed amount column. Workable for a one-off if your export already matches Sage's expected layout.

For most bookkeepers doing monthly bank reconciliations, converting once and importing OFX is faster and far less fiddly. You can sanity-check a generated file on our validator before importing. Convert your statement now and bring a clean file into Sage 50.

Frequently asked questions

Related