Which Sage products does this work with?

Sage Business Cloud Accounting imports the CSV directly; Sage 50 takes the same column layout through its bank import routines.

How are debits and credits represented?

As one signed amount column — money out negative, money in positive — which is what Sage's mapping expects. The statement's original two-column layout was normalised and verified during conversion.

Will UK dates import correctly?

Yes — exports use ISO dates (YYYY-MM-DD), which Sage reads unambiguously regardless of regional settings.

Can I do a year of statements for a catch-up job?

Yes — batch-convert the year (each statement is independently balance-checked) and import month by month in date order.

Built for Sage workflows

Convert bank statements for Sage

Statement PDFs to Sage-ready CSV — unambiguous dates, signed amounts, verified before import.

✓ No sign-up to try · originals deleted the moment conversion finishes

✓ ISO dates — no day/month ambiguity in Sage

PDF

Drop your statements here

or browse files · PDFs up to 20 MB each

.csv.xlsx.ofx.qfx.json

New here?

Convert the statement

Drop the PDF — reconciled against the statement's own printed balances first.

Download the CSV

Date, description, signed amount, balance — clean columns, UTF-8.

Import in Banking

Open the account in Sage, choose the statement import, map three columns, confirm.

Business Cloud, Sage 50, and the import details that bite

Sage Business Cloud Accounting imports statement CSVs per bank account with a simple column mapping — date, description, amount — and Sage 50 takes the same layout through its bank record import routines. The export is built for both: one signed amount column (money out negative), full descriptions for Sage's matching, and a reference balance column the import can ignore.

The details that usually bite Sage imports are dates and signs. A DD/MM file read as MM/DD silently swaps months; split debit/credit columns import as all-positive noise. Both problems are gone before the file reaches Sage — dates export as ISO, signs are inferred from the statement's columns and verified against its running balance during conversion.

.csv

Recommended for Sage

Sage's bank import reads CSV with a quick column mapping. Our export removes Sage's two classic import headaches: ISO dates that can't be misread, and one signed amount column instead of split debits and credits.

Every export format, on every plan

.csv

CSV

Opens anywhere

.xlsx

Excel

Formatted workbook

.ofx

OFX

QuickBooks & Xero

.qfx

QFX

Quicken-ready

.json

JSON

For your own stack

Balanced before it reaches Sage

Every conversion is cross-checked against the statement's own opening and closing balances — mismatches are flagged for review, never imported silently.

Originals deleted immediately

Files are encrypted in transit and at rest, never used for training, and the uploaded PDF is deleted the moment processing finishes.

Converting for Sage — questions

Step-by-step guide & other software

The full import guide for Sage

Step-by-step, with the mapping details and gotchas

For QuickBooks For Xero For Quicken For FreeAgent For Wave