Sage 50 bank statement import: OFX, QFX or CSV?
The reason this question has so many conflicting answers is that Sage 50 has two different import routes, and they accept different formats. Which one you have depends on your version, your region and your service plan — so an answer that is right for one Sage 50 user is wrong for the next.
🔒 Make the file Sage wants — drop in a CSV, Excel
or PDF statement and get .OFX, .QFX or a clean CSV back. Free, runs
in your browser, nothing uploaded.
The two routes, in Sage's own words
| Route | Formats Sage names | Also needed |
|---|---|---|
| Account Reconciliation Tasks → Account Reconciliation → Import |
lets you import a file in standard OFX or QuickBooks® QFX format |
— |
| Bank Services upload Banking → Match Bank Transactions → Upload to Bank Services |
You can use CSV or OFX. |
a service plan that includes Bank Services |
OFX is the only format both routes accept. If you do not know which route your copy has, or you are writing instructions for someone else, OFX is the answer that cannot be wrong.
What to generate, for each route
- Account Reconciliation → OFX. Convert your
statement and pick .OFX. This is the plain, non-Intuit variant — no institution
codes to get wrong, unlike a
.QBO. - Account Reconciliation → QFX also works per the quote above, and we write that too. There is no advantage over OFX here; QFX exists for Quicken.
- Bank Services → CSV or OFX. Sage does not publish a column template for the CSV route (see below), so OFX again avoids the guesswork. If you do want CSV, the Spreadsheet CSV output gives every column as read.
Three things the popular answers get wrong
“Sage 50 supports OFX, QIF and CSV.” QIF appears on neither of Sage's two pages. It is repeated widely, and it may well be true of some other Sage product or an older release, but we could not find it in Sage's documentation for these routes and so we do not assert it. If your Sage 50 does offer a QIF import, that is better evidence than this page.
“Use the Sage 50 CSV import template.” For bank statements there is not one to find. Sage's Bank Services page names CSV as acceptable but publishes no required columns, no date format and no encoding — so anyone handing you a definitive Sage bank-statement CSV template is describing their own guess, not Sage's spec. That is the main reason to prefer OFX, which does specify its fields.
“It is the same as QuickBooks.” It is not. A
.QBO carries Intuit's FID and INTU.BID fields and is
checked against Intuit's institution directory; neither Sage route asks for them.
The format comparison covers the difference, and
the FID lookup is only relevant if you are going to QuickBooks.
What we have not verified
Stated plainly, because the whole point of this page is the formats:
- Sage Accounting / Sage Business Cloud is a different product and is not covered here. Its help URL for importing a statement returned a 404 when we checked, so we have no quotable source for it.
- Sage 50 UK (“Sage 50 Accounts”) may differ from the North American product quoted above. The two quotes come from Sage's US and Canadian help.
- We have not run an import into Sage 50 ourselves. The formats above are Sage's statements about its own software, which is a different thing from a test. Tell us what happened if you try one — especially if it is refused.
The date trap, which applies to every route
If you go the CSV way, the date column is where imports quietly go wrong: a UK statement
reading 01/04/2026 means 1 April, and software expecting US order reads it as
4 January. OFX avoids this entirely because its dates are YYYYMMDD with no
ordering to infer. Our converter shows you the parsed dates before you download, and
the long version of that trap is written up
for QuickBooks but the cause is identical anywhere.
Sources
- Import a Bank Statement — Sage 50 US help, the Account Reconciliation wizard. Source of the OFX/QFX quote.
- Upload a Bank Statement to Bank Services — Sage 50 Canada 2023 help. Source of the
You can use CSV or OFX.
quote and the service-plan requirement.