Skip to content
StatementStudio
Convert a statement
Free during beta · No sign-up

Bank statement to Sage CSV

A Sage-ready CSV — Date, Description, Money in, Money out — the four-column template Sage’s bank-transaction import reads, kept lossless from your reviewed debit and credit values.

Choose a bank-statement PDFDownload a sample Sage CSV

The sample is a synthetic statement — no real bank, person, or account — and the excerpt shown is taken from that exact file, byte for byte.

Sample Sage CSVstatementstudio-sample-sage.csv · synthetic data
Date,Description,Money in,Money out01/05/2026,BACS SALARY ACME LTD MAY PAY,3250.00,02/05/2026,CARD PURCHASE TESCO STORES 4381,,46.8203/05/2026,ATM WITHDRAWAL HIGH STREET CASH MACHINE REF 778221,,80.0004/05/2026,DIRECT DEBIT CITY ENERGY,,124.40

The first lines of the sample file — money in and money out in separate columns, only one side populated per row.

What you download

Sage's four-column template, kept lossless.

Sage's import also accepts a 3-column signed layout, but the four-column form maps directly onto the debit and credit values you reviewed — no sign convention to second-guess.

Date
Slash-separated dates — dd/mm/yyyy, or mm/dd/yyyy when the statement itself is US-formatted. Sage asks you to confirm the date order during import.
Description
Always present and always a single line — multi-line source text is flattened, and a row with a blank description is never written (Sage requires one). Formula-safe, like every CSV we export.
Money in · Money out
The credit magnitude goes in Money in, the debit magnitude in Money out — exactly one side per row, never a negative number, and never a fabricated 0.00 in the empty side.
Deliberately absent
No currency or balance columns — Sage’s template doesn’t read them. The generic CSV keeps the full documented column set if you want it beside your books.
Reviewed, then exported

Convert a bank statement for Sage — after the checking is done.

Rows are extracted beside their source pages and checked against the statement's balances first. Here is one reviewed row — a debit — landing in the Money out column:

DateDescriptionAmountSource page
4 May 2026DIRECT DEBIT CITY ENERGY(£124.40)1
04/05/2026,DIRECT DEBIT CITY ENERGY,,124.40
Step through the review on sample dataHow the whole flow works
What this file is — and isn’t

A file you import yourself — not a live bank feed.

You download the CSV and import it from within Sage. There is no live feed and no link between StatementStudio and your Sage account — Sage shows its own import preview before transactions are created.

Importing into Sage

  1. Download your reviewed Sage CSV.
  2. In Sage, open the bank-transaction import for the relevant account.
  3. Select the CSV file — Sage reads the four columns (Date, Description, Money in, Money out) directly.
  4. Confirm the date order Sage asks for, since the dates are slash-separated.
  5. Review the import preview before confirming.

Sage documents the template and flow in its Import bank transactions guide.

Stated limits

When this export refuses to generate.

Designed boundaries, not bugs — the export refuses rather than writing a row Sage would reject or misread.

A blank description
Sage requires a description on every row. If any included row’s reviewed description is blank, the export refuses to generate until it’s filled in during review.
More than one currency
The Sage CSV format has no currency column, so a mixed-currency statement can’t be represented — the export refuses rather than importing unlabelled amounts.
Missing dates or amounts
Every row needs a date and a signed amount. If a reviewed row lacks either, this export stays unavailable until the row is resolved in review.

Review your transactions before importing, and check the import preview in your accounting software.

Other formats

Sage also imports OFX and QIF.

OFX
A single statement file with the currency and closing balance stated inside. Bank statement to OFX
QIF
The older text format — Sage’s QIF import asks you to confirm the date order. Bank statement to QIF
Everything else
The bank statement converter lists every output, including Excel with the validation summary.
Questions

About the Sage CSV output

What columns does the Sage CSV have?

Date, Description, Money in, Money out — four columns, matching Sage’s bank-transaction import template.

What if a row has no description?

Every exported row carries a non-blank, single-line description; multi-line source text is flattened to one line. If an included row has a blank description, the export refuses to generate rather than writing a row Sage would reject.

What date format does it use?

Slash-separated dates. Sage asks you to confirm the date order during import, and its import preview shows exactly how the dates were read.

Can I use OFX or QIF instead?

Yes — Sage also imports OFX and QIF files, generated from the same reviewed rows.

Do you support mixed-currency statements?

No — the Sage CSV format has no currency column, so a mixed-currency statement can’t be exported this way.

Free during beta

Convert a bank statement to Sage CSV — and check it first.

Choose a bank-statement PDFSee a sample conversion