CSV Format

Import Bank Statement to Sage 50 — Free PDF to Sage CSV

Sage cannot read a PDF bank statement. Sage Accounting and Sage 50 Accounts import transactions from CSV, and both are strict about the shape of that file — the wrong column order, a wrapped description or a comma inside an amount will fail the whole import with an error that names no row. Drop your PDF below and we build the file Sage documents: Date, Description, Money in, Money out, with slash-separated dates and plain numbers. Pick the date order your Sage region uses before you download.

Bank-grade security - Files processed securely and deleted immediately
Trouble converting a file? Tell us — we fix issues fast. Report it

Not the file you need?

CSV keeps getting refused?
QIF has a fixed structure, so it sidesteps the column list entirely
Already have a CSV?
If Sage is rejecting it, convert that file to QIF instead
Using Sage 50 US?
That version imports OFX, not CSV — convert to OFX instead
Sage 50 US, OFX refused?
Its wizard also accepts QuickBooks QFX

Why Use Our Import Bank Statement to Sage Tool?

Built to the column list Sage publishes

Date, Description, Money in, Money out — in that order, with nothing extra. Sage fails an import on a renamed column and on an added one, so the statement's own Type and Balance columns are left out on purpose rather than passed through.

The formatting rules are applied, not just documented

Descriptions that the bank wrapped over two printed lines are joined back into one. Amounts are written 4097.16, never 4,097.16. Dates use slashes. Each of those is a documented reason Sage refuses a file, and each is handled before you download.

Your statement is read in the browser, not uploaded to us

The conversion runs on your machine. Bank statements are the most sensitive document a practice handles, and the safest place for one is the computer it is already on.

How to import a bank statement to Sage in three steps

1

Download the PDF from your bank

Log in and export the statement as a PDF. Plenty of banks, building societies and credit unions still offer no other download — which is usually what brings people to this page.

2

Upload the PDF

Add the statement above — drag it in, or pick it from your files. Every page is read, so a twelve-page statement arrives as one continuous list. A locked PDF is fine if you have the password.

3

Pick the date order and download

Choose DD/MM/YYYY for UK Sage or MM/DD/YYYY for US, then download the .csv. The preview above the button shows the exact four columns the file contains.

Which file does your Sage actually take?

Sage is several products, and they do not accept the same files — two of them share the name Sage 50 and behave in opposite ways. Getting this wrong is why correct instructions lead people to a menu that will not open their statement. Below the formats, how many columns each product expects.

Sage productCSV (this page)ExcelOFXQIFQFXQBO
Sage AccountingUK · CA · ZA · AUformerly Sage Business Cloud — still called Sage online or Sage OneYesYesYesYesNoNo
Sage Accounting StartUKYesYesYesYesNoNo
Sage 50 AccountsUK · IEYesYesYesYesYesYes
Sage 200 ProfessionalUKYesYesYesYesYesYes
Sage Sole TraderUKYesYesYesYesYesYes
Sage IntacctUSYesYesYesYesNoNo
Sage 50USformerly PeachtreeNoNoYesNoYesNo
Sage 50CAformerly Simply Accounting — via Bank ServicesYesNoYesNoNot stated by SageNot stated by Sage

Every ✓ and ✕ above is taken from Sage's own documentation, checked September 2026. A dash means Sage publishes nothing either way — we would rather show the gap than guess at it.

Using Sage 50 in the US? Its reconciliation wizard reads OFX and QuickBooks QFX only — a CSV will not be offered to you at all. In Canada, the opposite: Sage 50 Canadian Edition takes a CSV through Bank Services, so the file this page builds is the one you want.

On Sage 50 in the US? Convert to one of these instead

Every other Sage in the table takes the CSV from this page — if you are on one of those, you are in the right place already. Same statement, same conversion, different file.

OFXPDF to OFXThe standard the wizard expectsQFXPDF to QFXQuicken's variant, also accepted

Sage Accounting · Accounting Start

Headers published

Sage names them and fixes the order: Date, Description, Amount for three columns, or Date, Description, Money in, Money out for four.

Date,Description,Money in,Money out

Sage Intacct

You pick the shape

Match it to your file at upload — one amount column carrying both signs, or two columns splitting money in from money out.

Date,Description,Amount

Sage 50 Accounts · Sage 200 · Sole Trader

Template inside the product

These keep the header list in the app rather than the manual, so open the example file on your import screen and check the download against it.

Why getting a statement into Sage is harder than it looks

Sage has no PDF import at all

There is no menu item for it in Sage Accounting or Sage 50 Accounts. The banking screen takes CSV, OFX, QIF and spreadsheet files, and a PDF is simply not on the list — so the format every bank gives you is the one format Sage will not read.

Copy and paste destroys the columns

The first thing most people try is selecting the transactions in the PDF and pasting them into a spreadsheet. What arrives is one long column, or dates fused onto payee names, because a PDF stores placed text rather than a table. Rebuilding the columns by hand takes longer than typing the statement out.

The error message does not say which row

Sage reports that the file does not match the required format, and stops. It does not name the line, the column or the character that broke it, so finding the problem means opening the CSV in a text editor and reading it by eye.

Re-keying is where the real cost is

Faced with a rejected file, most people give up and type the month in by hand. An eighty-transaction statement is an afternoon, and it is an afternoon that introduces the transposition errors a reconciliation then has to find.

The five reasons Sage refuses a bank statement CSV

Sage reports only that the file does not match the required format — never which row, column or character. Here are the five causes behind almost every rejection: red is what Sage refuses, green is what this page writes instead.

Column list

A column Sage does not recognise

Sage allows a set of named extra columns, but the statement's own Type and Balance are not among them — one column it cannot place fails the whole file.

Sage refusesDate,Description,Type,Money In (£),Money Out (£),Balance (£)

We writeDate,Description,Money in,Money out

Dates

A date the bank printed its own way

Sage needs slashes in your region's order, and one wrong row fails the whole file.

Sage refuses01 Apr 26

We write01/04/2026

Amounts

A thousands separator inside an amount

Anything over £999.99 arrives grouped, and the comma quietly forces the field to be quoted too.

Sage refuses"4,097.16"

We write4097.16

Descriptions

A description that runs onto a second line

Sage requires one line. Banks wrap a payee across two — name first, reference underneath.

Sage refusesEARLY YEARS ALLIAN 0000000015217984/1

We writeEARLY YEARS ALLIAN 0000000015217984/1

Encoding

A pound sign that arrives as £

A file that does not declare its encoding gets guessed at, and £, € and accented names come through wrong.

Sage refusesMoney In (£)

We writeMoney in

Want to see the layout first?

Download a seven-row sample in the exact format Sage expects — correct headers, slash dates, plain amounts, single-line descriptions. Open it, compare it to the file Sage rejected, or use it as a template to paste into.

Download the sample CSV

Who converts bank statements for Sage

UK practices on Sage

Clients send whatever their bank hands them, and for smaller banks and building societies that is a PDF and nothing else. Convert each month to a Sage-shaped CSV and import it against the right client bank account.

Bookkeepers catching up

A late client means six or twelve statements to post before anything reconciles. Each PDF becomes a CSV in the same layout, so the import step is identical every time instead of a fresh repair job per file.

Charities and small societies

Treasurers usually have a PDF from the bank and no feed at all. This turns the statement into the four columns Sage asks for, without anyone typing a payee name twice.

Gaps your bank feed misses

Feeds start the day you connect them and most banks only backfill 90 days. Older periods still have to arrive as a file, and a PDF statement is usually the only record left.

Accounts the feed dropped

Re-authentication failures leave gaps that nobody notices until the reconciliation does not balance. Convert the PDF for the missing weeks and import just those transactions.

Closing or switching banks

Once an account closes, online access usually goes with it. Convert the final statements while you can still download them, so the history lands in Sage rather than a folder of PDFs.

Frequently Asked Questions — Import Bank Statement to Sage

QCan you import bank statements into Sage 50?

Yes, but not as a PDF. You can import bank transactions into Sage 50 from CSV, OFX, QIF and spreadsheet files through the banking screen, so a PDF statement has to be converted first. This page turns the PDF into the CSV layout Sage documents, which you then import in the usual way.

QHow do I import bank statements into Sage Accounting?

Open the bank account in Sage, choose to import a statement, then upload the CSV and confirm the date order when prompted. Sage reads the four columns, shows you the transactions it found, and posts them once you approve. The file this page produces is already in that layout. Sage renamed this product from Sage Business Cloud Accounting, and plenty of people still call it Sage online or Sage One, so a guide on how to import bank statements into Sage online is describing this same screen under an older name.

QDoes Sage accept PDF bank statements directly?

No. No current Sage product reads a PDF bank statement. Sage Accounting and Sage 50 Accounts both need a file with the transactions in columns — CSV is the usual answer, and OFX or QIF work too if your bank offers them. The PDF has to be converted before Sage sees it, and that is all this page does: convert PDF to CSV for Sage, in the layout its import screen expects.

QWhat columns does Sage need in a bank statement CSV?

Sage documents two layouts. The three-column file is Date, Description, Amount in that order. The four-column file is Date, Description, Money in, Money out. This page writes the four-column version, which suits UK statements because banks print money in and money out as separate columns already.

QWhy does Sage say my CSV file is not in the required format?

The Sage bank statement import checks the shape of the file before it reads a single row, and almost always one of five things is wrong: a column it cannot place, a date without slashes, a thousands separator inside an amount, a description that runs onto a second line, or a character encoding Sage misreads. Any one of them fails the whole file, and the message does not say which. All five are handled before you download here.

QWhat date format does Sage need?

Slash-separated, and in your region's order — DD/MM/YYYY for UK Sage, MM/DD/YYYY for US. A single row in the wrong order fails the import rather than just that line. The toggle on this page sets the order for every row at once, and it starts on the order your browser region suggests.

QWhy did a pound sign turn into £ in my file?

That is a character encoding mismatch. The file is written in UTF-8, where a pound sign is two bytes, and a spreadsheet that assumes an older Windows encoding shows those two bytes as two characters. The file this page produces declares its encoding, so £, € and accented payee names arrive intact.

QMy description is split over two lines. Why does that matter?

Because Sage requires the description to fit on one line, and bank statements routinely wrap a payee across two printed lines — the name on the first, the reference on the second. A faithful conversion keeps that break, and Sage reads it as the end of the row. Here the two lines are joined with a space before the file is written.

QCan I import bank statements into Sage for free?

Yes. Converting the statement on this page is free to start and needs no signup, and Sage does not charge for importing a file — the banking import is part of Sage Accounting and Sage 50 Accounts. The only paid alternative would be a bank feed, which your Sage subscription may already include.

QWhich Sage products does this work with?

The CSV suits Sage Accounting, Sage Accounting Start, Sage 50 Accounts, Sage 200, Sage Sole Trader and Sage Intacct, all of which take a CSV statement on their banking screen. Sage 50 is the name to watch, because it covers two unrelated programs: the US edition reads OFX and QuickBooks QFX only, so use the PDF to OFX converter linked above the FAQ, while the Canadian edition does accept a CSV through Bank Services.

QCan I import a CSV bank statement into Sage 50?

Yes, and you do not need to convert it — Sage 50 Accounts in the UK takes a CSV statement, as do Sage Accounting, Sage 200 and Sage Intacct. Sage 50 in the US is the one that does not. What usually goes wrong is shape rather than format: Sage checks the column list, the date order and the number formatting before it reads a single row, so a CSV straight from your bank is often refused. If that is your situation, the five causes above are what to compare it against. This page is for the other case, a PDF, which no Sage product reads at all.

QCan I import bank transactions into Sage Intacct?

Yes. Sage Intacct reads CSV, QIF, XLS, XLSX and OFX through its Bank Transaction Assistant, and you pick a three-column or four-column file type at upload so it matches the shape of your file. The CSV this page builds is the four-column shape — Date, Description, Money in, Money out. Intacct is normally on MM/DD/YYYY, so set the date toggle to month-first before you download.

QCan I import bank transactions into Sage from Excel?

Yes — Sage Accounting, Sage 50 Accounts, Sage 200 and Sage Intacct all take XLS and XLSX alongside CSV, so an Excel statement does not need converting either. Two things catch people out: Sage reads only the first tab of the workbook, and it still expects its own column list, so a file with a cover sheet or the bank's extra columns fails exactly the way a bad CSV does. A PDF is the one file Sage cannot read, and that is what this page converts.

QDoes this work with a multi-account statement?

It converts every transaction, but Sage imports one bank account at a time and has no account column in its layout, so the file cannot carry an account label. If your PDF covers several accounts, split the downloaded CSV by account before importing, or convert each account's statement separately.

QWill Sage still match the transactions to rules and suppliers?

Yes. Transactions that arrive by import go through the same matching as transactions from a bank feed, so bank rules, supplier matching and existing reconciliations behave normally. The description carries the payee text from the statement, which is what the matching reads.

QWhat is the best way to get bank statements into Sage?

A live bank feed, if your bank and Sage plan support one — it needs no files at all. Where a feed is unavailable, covers too short a period, or has dropped, converting the PDF is the practical route. Dedicated statement-conversion services run from roughly £20 a month upwards, and outsourced data entry costs more again; this page is free to start, which is worth trying before either.

Other Conversion Formats

PDF to QBO Converter

Convert to QBO

Import Bank Statement to Xero

Convert to CSV

Import Bank Statement to MYOB

Convert to QIF

CSV to QBO Converter

Convert to QBO

CSV to OFX Converter

Convert to OFX

CSV to QFX Converter

Convert to QFX

Get a file Sage takes on the first attempt

Sage will not read your PDF, and a file that is nearly right fails the same way as one that is completely wrong. Drop the statement in and take away a CSV built to the column list Sage publishes. Free to start, no signup.