Starling Bank Statement to CSV: Use the App First

You need Starling transactions in a spreadsheet — for a Self Assessment return, a set of year-end accounts, a mortgage application, or a bookkeeper who wants the year in one file.

Here is the honest version, up front: unlike most banks, Starling gives you a proper CSV export in the app, over any date range you choose, back to when the account was opened. If you can open the Starling app, that export is better than anything a PDF converter will produce, because it comes from the bank's own data rather than being reconstructed from ink on a page. This guide covers that route first, then the narrower cases where a PDF is genuinely all you have.

Quick answer

There are two ways to get Starling transactions into CSV:

1. Starling's own in-app export. Statements can be downloaded as CSV, PDF or large print PDF for any custom date range, going back to account opening, and each can be taken as a standard or a certified statement. It is a plain CSV you can open in any spreadsheet. This is the right answer for almost everyone.
2. Convert the PDF statement. Relevant when the app is not available to you: a certified PDF statement you were issued, a statement someone else sent you, or an account you can no longer log in to. Upload it to a converter such as BankStatementKit, which reads the transactions out and balance-checks the result against the statement's own printed totals.

Rule of thumb: if you can open the Starling app, use the app. The PDF route exists for when you cannot.

Convert a Starling PDF you were sent

Option 1: Starling's built-in CSV export

If the account is yours and the app is on your phone, this takes about thirty seconds.

1. Open the Starling app and tap the menu icon in the top right.
2. Select Statements.
3. Choose Statement history.
4. Pick the date range you want — Starling supports custom start and end dates, back to when the account was opened.
5. Choose your format — CSV, PDF or large print PDF — then choose standard or certified. Certification is offered on CSV as well as PDF.

Where the built-in export stops

The export is good, and there are still situations it cannot reach:

• It needs your app and your account. A statement a tenant, client, borrower or ex-partner sent you is a PDF that arrived by email, and no export screen exists for it.
• A closed account has no app. Once the account is closed and the app access is gone, whatever PDFs you saved are the record.
• A certified statement is a document you were given. Lenders, letting agents and visa applications frequently insist on one. Starling lets you certify a CSV as well as a PDF, but what usually lands in your inbox from a third party is the PDF.
• Accountants receive PDFs. In practice a bookkeeper is often handed the PDF, not the CSV, because that is what the client downloaded first.

None of those are failures of Starling's export. They are simply cases where the CSV was never in your hands to begin with.

Option 2: Convert the Starling PDF statement to CSV

1. Find the statement PDF — a certified or standard statement from the app, or one someone emailed you.
2. Upload it. The file is processed in memory and never stored. If it happens to be password-protected, supply the password at upload.
3. The transactions are read into seven standard columns: Date, Narration, Reference, Value Date, Debit, Credit, Balance. Outgoing amounts land in Debit and incoming in Credit, whatever sign convention the PDF uses.
4. Check the verification label, then download the CSV.

Uploads are limited to 20MB or 50 pages. Scanned statements — a PDF that is really a photograph or a scan of a printed statement — fall back to OCR automatically. More on the layout on the Starling statement converter page.

Convert a Starling statement PDF

Why Starling PDFs trip up generic converters

One amount column, not two. Where most British high-street statements print separate in and out columns, a Starling statement carries a single amount per row with the direction expressed by its sign. That inverts the usual failure mode: instead of losing the sign by merging two columns, a converter loses it by dropping a leading minus that PDF text extraction sometimes renders as a separate glyph, or as a character that is not the hyphen it looks like. Every outgoing payment then reads as income, and a whole year quietly doubles.

Counterparty and reference are distinct fields. A Starling transaction has a counterparty — the person, merchant or business — and separately a reference, note or category. When those print in adjacent positions on the page, a converter that reads a row as one run of text welds them into a single string, and you lose the ability to filter or match on the counterparty afterwards. They have to be kept apart as printed.

App-native design does not mean simple pages. The statement is generated for display quality, which means proportional spacing, and rows whose text length varies a lot. A long counterparty name plus a reference can push an entry onto a second printed line, and a converter treating each line as a transaction produces phantom rows carrying no amount at all.

Prove the CSV matches the statement

Whichever route you take, check the result — and this matters more for the PDF route, because a reconstructed table can be wrong in ways that look plausible.

1. The running balance chain. Each row prints a balance. For every row, the previous balance plus the signed amount must equal the printed figure. One dropped or duplicated transaction breaks the chain at exactly the row where it went wrong, and one flipped sign breaks it at that row and stays broken for the rest of the statement — which is why sign errors are so easy to spot this way and so hard to spot by eye.
2. The printed opening and closing balances. The statement states where the period starts and ends. Opening balance plus total credits minus total debits must equal the closing balance.

BankStatementKit runs both on every conversion and labels the result VERIFIED, DISCREPANCY or FAILED, with a discrepancy pointing at the row where the numbers stop reconciling. If you exported the CSV from the app instead, run the same two checks against the PDF anyway — it takes a minute in a spreadsheet and it is the only way to know the file is complete.

FAQ

The bottom line

Starling is one of the few UK banks where the native export is the right answer for most people, and we would rather say so than pretend otherwise. Open the app, pick your dates, take the CSV. Come back to the PDF route when the app is not yours to open — a certified statement, a client's file, a closed account — and when you do, insist on a conversion you can prove, because a single signed amount column is unforgiving about sign errors.