How to Import Bank Statements into Sage Accounting, Sage 50 and Sage Intacct

Sage is one of the most widely used accounting brands, especially in the United Kingdom, Ireland, South Africa, Canada and parts of Europe, and with Sage Intacct among mid-sized organisations in North America. Like other accounting systems, Sage products work best with bank feeds, but file imports remain essential for history, for banks without a feed, for broken connections and for clients who hand over PDF statements.

This guide explains how statement imports work across the main Sage products, how to prepare a file that imports cleanly, how to convert PDF statements into a Sage-ready file, and how to troubleshoot. Because Sage products differ, the steps below describe the general process; check Sage's help centre for the exact menu labels in your product and region.

Know which Sage product you use

"Sage" covers several distinct products, and the import process depends on which one you have:

Product	Typical users	Import approach
Sage Accounting (cloud, formerly Sage Business Cloud Accounting)	Small businesses, sole traders, accountants	Upload a statement file from the bank account screen, then reconcile
Sage 50 (desktop, UK and other regions)	Small and medium businesses	Bank feeds module or statement import, then bank reconciliation
Sage 50 (US edition)	Small businesses in North America	Account reconciliation tools with downloaded bank files
Sage Intacct	Mid-sized organisations	Bank transaction import using templates or feeds, then matching rules
Sage 200 and other mid-market products	Larger businesses	Cash book and bank reconciliation modules, often with partner tools

If you are unsure which product you use, look at the login page or the "About" screen. The rest of this guide notes where the products differ. Accountants who support several Sage products should keep a short note per client recording the product, edition and import method, because the differences catch people out when switching between clients.

Which file formats Sage accepts

Format	Typical support	Notes
CSV	Widely supported	Most flexible; columns must be mapped or match a template
OFX	Commonly supported	Structured, with unique transaction IDs
QIF	Supported in some products	Older format without unique IDs
QBO / QFX	Sometimes accepted as OFX variants	Test with your product
Excel	Usually needs saving as CSV
PDF	Not supported	Convert first

When your bank offers OFX downloads, use them for duplicate protection. When you need control or the source is a PDF, use CSV. Our guide to QBO, OFX, QIF and CSV compares the formats in detail.

Preparing a CSV for Sage

Sage products expect a simple table. The exact columns vary by product, and some provide a downloadable template, which is always the safest starting point. A layout that works in most cases:

Date	Reference	Description	Amount
02/03/2026	BGC	Payroll - Northwind Ltd	4250.00
04/03/2026	SO	Rent - Elm Street Props	-1850.00
07/03/2026	POS	Office supplies	-86.47

Some products prefer separate columns for money in and money out (often labelled Receipts and Payments, or Paid In and Paid Out). Either works as long as you map them correctly.

Rules that prevent most import errors:

• One header row only, then transactions. Remove opening balance lines, subtotals, page headers and blank rows.
• Consistent date format. UK and Irish users typically use DD/MM/YYYY. Choose the matching option during import.
• Signed amounts or separate columns, never "CR" or "DR" text in the amount field.
• No currency symbols or thousands separators.
• Reference column populated where possible. Sage uses references in reconciliation and reports; bank codes such as BGC, DD, SO or cheque numbers are useful. Our bank statement abbreviations reference explains them.
• Plain CSV encoding (UTF-8 or the encoding Sage specifies), especially if descriptions contain accented characters.

Our converter's Sage export produces this layout from PDF, scanned or photographed statements, with your choice of date format.

Importing into Sage Accounting (cloud)

The general process:

1. Open Banking and select the bank account.
2. Choose the option to import or upload a statement file.
3. Select your CSV, OFX or QIF file.
4. For CSV files, map the columns to Sage's fields (date, reference, description, amount or in/out), choose the date format and confirm the header row.
5. Review the preview, then import.
6. Go to the bank reconciliation or bank transactions screen to match imported lines to existing transactions (invoices, bills, transfers) or create new transactions for items such as bank charges.
7. Reconcile to the statement's closing balance and date.

Importing into Sage 50 (desktop)

In Sage 50 desktop editions, statement imports are typically handled through the bank feeds or e-banking area for the relevant bank account. The process usually involves selecting the bank record, choosing to import a statement file (often OFX, QIF or CSV, depending on edition and region), matching imported transactions to existing entries or creating new ones, and then completing the bank reconciliation.

Always take a backup before importing into a desktop company file. If the import option is not visible, check your edition, region and version, and whether the bank feeds module is enabled.

Importing into Sage Intacct

Sage Intacct supports bank transaction imports, typically using a defined CSV template, as well as automated bank feeds. Imported bank transactions are then matched to records using matching rules in the reconciliation process. Intacct implementations are often configured by partners, so check with your administrator which template and matching rules your organisation uses before importing.

Converting PDF statements for Sage

When the source is a PDF, which is common for catch-up work, client records and older periods, convert before importing:

1. Upload the statement to a converter that understands statement layouts, such as our bank statement to Sage tool.
2. Check the balance proof. The extracted transactions must reproduce the statement's opening and closing balances, and printed running balances where they exist. This proves no rows were dropped or misread.
3. Correct flagged rows in the review table.
4. Export a Sage-style CSV with your date format, or OFX if your product accepts it.
5. Import one statement period at a time and reconcile each.

Avoid generic PDF-to-CSV tools that copy the page layout. They often produce merged cells, headers mixed with transactions and amounts stored as text, all of which Sage will reject or misread. For background on conversion methods, see how to convert a bank statement PDF to Excel.

Setting opening balances correctly

When you start using Sage, or start importing history for an account, the opening balance is the anchor for every reconciliation that follows.

• Choose a start date at the beginning of a statement period, ideally the start of the financial year.
• Use the statement balance from the end of the previous day as the bank account's opening balance in Sage.
• Account for uncleared items at the start date. If cheques or deposits were in transit, your accountant may prefer to enter them individually so they clear in the first reconciliation, rather than folding them into a single balance.
• Never import an opening balance row as a transaction. Remove "balance brought forward" lines from converted CSVs before import.

If the opening balance is wrong, every subsequent reconciliation will be out by the same amount, and the cause can be hard to spot months later.

Foreign currency bank accounts

Where your Sage product supports foreign currency bank accounts, import each account's transactions in that account's own currency. Do not convert amounts before import; Sage applies exchange rates according to its settings. If a statement shows both a foreign amount and a converted amount on the same line, make sure the exported amount is the one that moved through the account. Mixing currencies within one file produces balances that can never reconcile.

Making Tax Digital and digital records (UK)

UK businesses within Making Tax Digital for VAT must keep certain records digitally and file returns using compatible software. Importing bank transactions from files into Sage is a normal way of maintaining those digital records, alongside feeds. The important points are to keep the records complete, to avoid manual retyping where a digital transfer is possible, and to keep the source statements as evidence. If you are unsure how the rules apply to your process, check HMRC guidance or ask your accountant.

Bank feeds vs imports in Sage

Feeds and imports complement each other:

Situation	Use
Day-to-day transactions at a supported bank	Bank feed
History before the feed started	File import
Gaps when a feed disconnected	File import for the missing dates
Banks without feed support, including some foreign banks	File import
Closed accounts	File import from PDF statements
Client records supplied as PDFs	Convert, then import

Record which periods came from feeds and which from files for each account. That simple log prevents duplicates and helps anyone reviewing the books later.

Avoiding duplicates

• Know the feed boundary. If a bank feed is connected, import only periods before it started or gaps it missed.
• Never import the same file twice. OFX files carry unique transaction IDs that help Sage detect repeats; CSV files do not.
• Use exact statement periods so files do not overlap at month ends.
• Delete or ignore duplicates promptly in the bank transactions or reconciliation screen, before they are matched.

Checklist before every Sage import

Run through this short list before you upload a file. It takes a minute and prevents most of the problems in the troubleshooting table.

1. The file covers exactly one statement period, with no overlap with the previous import or the bank feed.
2. The transactions reproduce the statement's opening and closing balances.
3. There is one header row and no subtotals, blank rows or balance lines.
4. Dates use one format throughout, and you know which format to select in Sage.
5. Amounts are numeric, with payments negative or in a separate column.
6. The reference column carries cheque numbers or bank codes where the statement provides them.
7. You have a current backup (for desktop products).
8. The import is logged with the account, period, file name and date.

What happens to the original statements

Importing data does not replace the source documents. Keep the PDF statements with the client or company records for the retention period that applies, which in the UK is commonly six years for limited companies and longer than many people expect for the self-employed. Our guide to how long to keep bank statements explains the periods by country. Store the converted CSVs alongside the PDFs so you can show exactly what was imported.

Troubleshooting

Problem	Likely cause	Fix
Import rejected	Extra header rows, blank lines, or text in amount columns	Clean the file to one header row and numeric amounts
Dates wrong	Day and month swapped	Choose the correct date format, or normalise dates before import
All lines treated as receipts	Amounts all positive with a single amount column	Make payments negative, or use separate in/out columns
Accented characters garbled	Wrong encoding	Save as UTF-8 or the encoding Sage specifies
Imported balance differs from the statement	Missing or duplicate lines, or wrong opening balance in Sage	Compare totals and line counts; check the bank account's opening balance
Option to import not visible	Product, edition or permissions	Check your Sage product and user rights; consult Sage help

Reconciling after import

Imported statement lines are only the raw material. Reconciliation is where they become accounting records. Work through the lines, match them to invoices, bills and transfers, create transactions for bank charges, interest and other bank-only items, and finish by reconciling to the statement's closing balance. Our guide to reconciling a bank statement explains the logic, and the month-end close checklist shows where it fits in the monthly routine.

Tips for accountants with Sage clients

• Standardise the CSV layout across clients so staff learn one mapping.
• Collect PDF statements monthly even when feeds work; they are your fallback and your evidence.
• Keep an import log per client and account listing which periods were imported by file and which came through feeds.
• Use bank rules where your Sage product supports them, and review them periodically.
• Lock or close periods after reconciliation where the product allows, to protect reconciled history.

Our accountants and bookkeepers pages describe batch conversion workflows for multiple clients.

Worked example: importing three months for a new client

A UK bookkeeper takes on a sole trader using Sage Accounting whose bank feed was connected only from April. The client sends PDF statements for January to March.

1. The bookkeeper checks the bank account's opening balance in Sage against the 1 January statement. It matches.
2. The three PDFs are converted to Sage CSV with DD/MM/YYYY dates. Each reconciles to its printed closing balance.
3. Each file is imported in order. The first import requires column mapping; Sage remembers it for the next two.
4. Imported lines are matched to sales invoices already raised, with new transactions created for bank charges and a handful of supplier payments not yet recorded.
5. Each month is reconciled to the statement's closing balance before the next file is imported.
6. The March closing balance in Sage equals the opening balance of the April feed, so the boundary is clean and nothing is duplicated.

Frequently asked questions

Can Sage import PDF bank statements?

No. Sage products import transactions from files such as CSV, OFX and, in some products, QIF. Convert PDF statements to one of those formats first, and verify the result against the statement's balances.

What CSV format does Sage Accounting need?

Typically a header row and columns for date, reference, description and either a single signed amount or separate money in and money out columns. Use the template provided by your Sage product if one is available, and choose the correct date format during import.

Is OFX better than CSV for Sage?

OFX is more structured and includes unique transaction IDs, which reduces the risk of duplicates. CSV gives more control and is the fallback when OFX is not available or when converting from PDFs.

How do I import bank statements into Sage 50?

The process depends on your edition and region, but generally involves using the bank feeds or e-banking area for the bank account to import an OFX, QIF or CSV file, then matching transactions and completing the bank reconciliation. Back up the company file first.

Why are my imported Sage transactions dated wrongly?

The date format chosen during import probably does not match the file. A US-format file (MM/DD/YYYY) imported as UK format (DD/MM/YYYY) swaps day and month for dates up to the 12th. Re-import with the correct setting.

Can I import credit card statements into Sage?

Yes, into a credit card or liability bank account, using the same file formats. Pay attention to signs: purchases increase the balance owed and payments reduce it. Our article on bank vs credit card statements explains the logic.

Summary

Every Sage product can bring in bank transactions from files, although the menus differ. Prepare a clean CSV or use OFX, import one statement period at a time, and reconcile each one. If your statements are PDFs, convert them with balance checks so every import starts from complete data. QuickBooks and Xero users can follow our guides to importing into QuickBooks and importing into Xero.