Import Bank Statements into Sage Accounting (CSV Rules)

TL;DR: Sage Accounting imports bank statements from CSV, OFX and QIF files (and, in some regions, more formats). For CSV, Sage's UK help specifies two templates: Date, Description, Amount (payments out negative) or Date, Description, Money in, Money out, with slash-separated dates, no blank descriptions and numbers only in amount columns. Import from the bank account's Actions menu, pick the date format, review, confirm, then process and reconcile as you would a bank feed.

Sage Accounting (the cloud product for small businesses) is common in the UK, Ireland and Canada, and it handles statement imports well, as long as the file follows its rules. Those rules are stricter than some other tools', which is actually helpful: when you know them, imports are predictable.

This guide is based on Sage's own help articles at the time of writing, mainly the UK and Ireland versions. Sage's regional editions differ (the Canadian help, for example, lists additional file types), so if something doesn't match your screen, check Sage's knowledge base for your region. If you use Sage 50 or another desktop Sage product, the import process is different; this article is about Sage Accounting.

When to import instead of using a bank feed

Sage's help describes statement imports as useful when your bank doesn't have a bank feed, when the feed isn't working, or when you have historical transactions not included in your feed. That covers most situations we see: a new Sage user bringing in last year, a bank feed outage, or a client who only has PDFs.

Things Sage won't import

Two limits from Sage's UK help worth knowing up front:

• No foreign currency bank statement imports. If you hold a foreign currency account, imports aren't supported for it in that edition; check your region's help.
• Nothing before your Accounts Start Date. If you need history earlier than that date, talk to whoever manages the Sage company before changing it.

Sage's Canadian help also notes that file imports apply to chequing, credit card and savings accounts, not to cash in hand, loan or other account types.

Choosing a file format

Format	What Sage says	When we use it
OFX (or ASO)	Industry standard; upload without editing. Only the first account in the file is imported.	A bank's own download, as-is
QIF	Supported; you confirm the date order on upload	When it's all the bank offers
CSV	Supported with specific headers and rules	Converted PDFs, edited or combined data

Sage recommends OFX where the bank offers it. We agree for bank downloads. For PDF statements, a CSV built to Sage's template is the practical route.

Sage's CSV templates

Sage's UK help gives two acceptable layouts.

Three columns:

Date,Description,Amount
04/03/2026,DD BRITISH GAS,-45.00
05/03/2026,FASTER PAYMENT CLIENT LTD,1250.00

Rules: columns labelled Date, Description and Amount, in that order. Both payments in and out in the Amount column, with payments out negative.

Four columns:

Date,Description,Money in,Money out
04/03/2026,DD BRITISH GAS,,45.00
05/03/2026,FASTER PAYMENT CLIENT LTD,1250.00,

Rules: columns labelled Date, Description, Money in, Money out, in that order. Payments in in Money in, payments out in Money out.

Rules for both:

• Dates separated by slashes (for example 04/01/2021).
• Description must contain text; it can't be blank.
• Description text must be on one line (no line breaks inside the field).
• Amount columns contain numbers only.

Sage also offers a downloadable template on the import page. Using it is the quickest way to get headers exactly right.

Which template should you choose? If your source already has separate money in and money out columns, as many UK statements do, the four-column template avoids a conversion step. If you're combining data or using a converter's signed output, the three-column template is simpler. Both import the same way.

Building a Sage-ready CSV from PDF statements

1. Convert the PDFs. SheetStatement's bank statement to CSV converter extracts all transactions and checks the balance.
2. Verify: opening balance + sum of amounts = closing balance. Our balance checker does this.
3. Shape to one of Sage's templates. Use exactly the header names above.
4. Fix descriptions: fill any blanks (for example with the transaction type) and remove line breaks: =SUBSTITUTE(SUBSTITUTE([@Description],CHAR(10)," "),CHAR(13)," ").
5. Format dates with slashes, consistently: =TEXT([@Date],"dd/mm/yyyy") for UK and Irish setups.
6. Clean amounts: no currency symbols, no thousands separators.
7. Save as CSV and check it in a text editor.

Importing step by step

From Sage's UK help, in outline:

1. Go to Banking and find the bank account.
2. Select Actions, then Import statement.
3. Browse to or drag in the file, then choose to review transactions.
4. Select the date format used in your file and continue.
5. Review the transactions for errors.
6. Confirm import.

Sage remembers your choices for the next import and offers options to change import settings or import without review. We'd keep the review step until you've done a few months without problems.

After import, you process the transactions like a bank feed: match, create, apply bank rules. Sage's help notes that bank rules still apply to imported transactions.

OFX and QIF in practice

If your bank offers OFX, it's usually the smoothest option for Sage: no editing, no column rules. One detail from Sage's help matters: only the first account in an OFX file is imported. Some banks let you export several accounts into one OFX file; if you do that, only the first will come in. Export one account per file.

QIF files work too, but Sage asks you to confirm the date order (day/month/year, month/day/year or year/month/day). Open the file in a text editor, find a transaction date, and note its order before uploading. A QIF file from a US-based bank or app will often be month first, which is easy to get wrong in a UK company.

If an OFX or QIF file won't import, try downloading it again, since partial downloads happen. If it still fails, fall back to a CSV built to Sage's template.

Checking the result

After confirming the import, before processing anything:

1. Compare the number of imported transactions with the number in your file.
2. Check the first and last transaction dates.
3. Spot-check one payment in and one payment out for the right direction.
4. Compare the account's statement balance in Sage (if shown) with the bank statement.

If anything is off, it's much easier to deal with now than after you've processed and reconciled the transactions.

Avoiding duplicates with a bank feed

Sage's guidance is sensible: note the last transaction imported from your bank feed, and choose a date range for the file that starts the day after. Also note the statement end balance, which you'll need for reconciliation.

We'd add: keep a short log for each account with the date ranges you've imported, and import one statement period per file.

Reconciling

Once the transactions are processed, reconcile the account against the statement's end balance. If it doesn't agree:

• Check for overlap with the bank feed.
• Check the opening balance as of your Accounts Start Date.
• Check the file was complete (the verification step).
• Look for transactions processed twice (once matched, once created).

Our guide to finding reconciliation discrepancies works for Sage as for any software.

Getting the opening position right

Before importing any history, make sure the bank account in Sage starts from the right place. When a Sage company is set up, it has an Accounts Start Date and opening balances for each bank account as at that date. Imports can only bring in transactions after the start date, and reconciliations build on the opening balance.

Check two things:

1. The opening balance for the bank account equals the statement balance at the end of the day before the Accounts Start Date (or whatever your accountant used, if there were uncleared items at that point).
2. Uncleared items at the start date, such as cheques written but not yet cleared, are recorded the way your accountant intended. These affect the first reconciliation.

If either is wrong, every reconciliation afterward will be off by the same amount, which is frustrating to diagnose later. Ten minutes of checking now prevents it.

Using bank rules with imports

Sage's help points out that bank rules still apply to imported transactions. That's worth setting up before a large import:

1. Look at the first statement and list the recurring payees and payers: rent, utilities, software, payroll provider, regular customers.
2. Create a bank rule for each, matching on a distinctive part of the description, with the ledger account and VAT treatment your accountant uses.
3. Import, and let the rules do the bulk of the work.

Rules are only as good as the descriptions they match, which is another reason not to leave descriptions blank or replace them with generic text. If you have to fill a blank description, use something meaningful such as "Bank charge" or "Card refund" rather than "-".

VAT and imported transactions

For VAT-registered businesses, each transaction you create from an imported line needs the right VAT treatment. Bank rules can set a default, but check anything unusual. The bank statement shows the gross amount; whether and how VAT applies depends on the supplier, the item and your VAT scheme, so ask your accountant if you're unsure. This is the most common area where catch-up imports need professional review before a VAT return goes in.

Importing a year of history

For a new Sage company where you want a full year of transactions:

1. Confirm the Accounts Start Date and opening balances.
2. Convert all statements for the period and verify each one.
3. Import month by month, oldest first.
4. Process and reconcile each month before importing the next.
5. Connect the bank feed only after you've decided where imports stop and the feed begins.

Doing it in this order keeps each step checkable. Our catch-up bookkeeping guide covers the wider process, including tagging transfers and batching questions for the business owner.

Credit cards

Sage supports imports into credit card accounts. With the three-column template, think about direction: for the card, spending is money going out, so it should be negative; payments to the card are money in. If your card export has purchases as positive numbers, flip them. Check a known purchase and payment after importing. Our credit card statement converter produces consistent card files.

A worked example

A bookkeeper takes on a Sage client whose bank feed was disconnected for two months.

1. She notes the last transaction the feed brought in: 2 April. The feed was reconnected and resumed from 6 June.
2. She downloads the April and May PDF statements and the start of the June statement, and converts them.
3. She trims the data to 3 April through 5 June.
4. She shapes it to the three-column template, fills two blank descriptions with "Bank charge" (they were fee lines with no text), formats dates as dd/mm/yyyy, and saves.
5. In Sage, she imports via Actions > Import statement, chooses the day/month/year date format, and reviews. All rows show the right dates and amounts.
6. She processes the transactions with the client's existing bank rules, which handle most of them.
7. She reconciles April and May to the statements. Both agree.

The two blank descriptions would have stopped the import; Sage requires text in that column. Catching them before upload saved a round trip.

Common errors

Sage has its own help articles for import errors, including a "file not imported" error. In our experience, the causes are usually:

• Header names or order don't match the template. Use the exact labels.
• Blank descriptions. Fill them.
• Multi-line descriptions. Remove line breaks.
• Dates without slashes (for example 2026-03-04 or 04.03.2026). Reformat with slashes.
• Text in amount columns (currency symbols, commas, spaces). Clean them.
• Mixed date formats in one file.
• Dates before the Accounts Start Date.
• Foreign currency account. Not supported for imports in the UK edition.

Our take

Sage Accounting's import rules are specific, and that's a good thing: follow the template exactly and imports work. Use OFX for bank downloads, a template-perfect CSV for converted PDFs, respect the start date, avoid feed overlap, and reconcile each month after importing.

Troubleshooting Sage imports

"File not imported." Start with the template: exact header names in the exact order. Then look for blank descriptions, line breaks within descriptions, dates without slashes, and text in amount columns. Fixing one of these and trying again usually works.

Dates land in the wrong month. The date format you choose during import applies to the whole file. A UK file imported as month/day/year moves early-month dates and rejects others. Re-import with day/month/year after deleting the wrong lines.

Some lines are missing after import. Check whether they're dated before your Accounts Start Date; Sage won't import those. If they matter, discuss the start date with your accountant.

Duplicates with the bank feed. Compare the last feed transaction with the first imported transaction. Delete the duplicated lines before processing them.

Card imports with the wrong direction. On the three-column template, purchases should be negative. If they came in as money in, flip the signs and import again.

A second worked example: a new Sage company with history

A café moves to Sage Accounting in April with an Accounts Start Date of January 1. The accountant enters opening balances as at that date. The bookkeeper converts January to March statements, shapes each to the four-column template (the bank's statements already have money in and money out columns), fills three blank descriptions with "Card fee", and imports one month at a time, choosing day/month/year. After setting bank rules for the main suppliers, she processes and reconciles each month, then connects the bank feed from April 1.

Mini checklist

1. Template headers exact, in order.
2. Dates with slashes, in one format.
3. Descriptions filled and on one line.
4. Amounts numeric only.
5. No dates before the Accounts Start Date.
6. No overlap with the bank feed.

FAQ

What file formats can Sage Accounting import for bank statements?

Sage's UK help lists CSV, OFX (or ASO) and QIF. Some regional editions support additional formats; check Sage's help for your region.

What CSV format does Sage Accounting require?

Either Date, Description, Amount (payments out negative) or Date, Description, Money in, Money out, in that order, with slash-separated dates, non-blank single-line descriptions and numbers only in amount columns.

Why does Sage say my file wasn't imported?

Common causes are header names or order not matching the template, blank or multi-line descriptions, dates without slashes, text in amount columns, or dates before your Accounts Start Date.

Can I import a PDF bank statement into Sage?

Sage needs a file such as CSV, OFX or QIF. Convert the PDF to a Sage-format CSV first, then import it.

How do I avoid duplicates with my bank feed?

Note the last transaction your feed imported, and import only transactions from the following day, as Sage recommends. Keep a log of imported periods.

Can I import foreign currency statements into Sage Accounting?

According to Sage's UK help, foreign currency bank statement imports aren't supported. Check the help for your region and product.