Convert Monzo Statements to Excel

It would be easy for a page like this to pretend otherwise, so let us be plain: Monzo exports your transactions itself, and where that export covers what you need it is the better route. Data from the bank has never been through a reading of a page.

The steps, from Monzo's own help: tap Home in the app's menu bar, tap the three dots underneath your card, tap Bank statements, choose the date range you'd like, and choose the format you'd like — PDF, CSV or QIF. A CSV opens directly in Excel or Sheets, and QIF imports into a number of accounting packages.

So when is a converter the right tool for a Monzo customer at all? Three situations, and none of them is a criticism of the export. When somebody sends you a Monzo PDF — if you are an accountant, a bookkeeper or a lender, what arrives is the statement, not access to the app that produced it, and you cannot re-export from an account you do not hold. When the account is closed, because every self-service export depends on being able to log in. And when the PDF is the artefact that matters: Monzo's help notes that "All of our bank statements are original documents. So you shouldn't need to get them stamped or signed for your mortgage or visa application."

Verified against Monzo's own help pages, August 2026.

A Monzo statement lists each transaction with a date, the merchant name, a spending category, the amount and a running balance. The category is the distinctive part: Monzo assigns one at the point of spending, which is genuinely useful and worth preserving as its own column rather than folding into the description.

It is worth being clear about what that category is and is not. It is Monzo's classification of the merchant, not an accounting treatment. It will tell you a transaction was at a supermarket; it cannot tell you whether that was a business cost, a personal one, or something reimbursable. The mechanical half is done; the judgement half is not, and no bank-side category will ever supply it.

The running balance is the other column that earns its keep, because it makes the row-to-row check possible: each balance minus the previous one should equal that row's amount. Monzo has also added a running balance to business CSV exports, which is exactly the field that lets an export verify itself rather than being taken on trust. That distinction matters generally — a CSV with a balance column can be checked; a bare list of transactions cannot. If you are choosing between export formats and one carries the balance, take that one.

For Monzo Business there is a further option that removes the remembering: Monzo can create a folder in your Google Drive or Microsoft OneDrive and export the previous month's bank statement on the first of each month, in PDF, CSV or QIF, with the ability to export older statements too.

That is a small feature with a disproportionate effect, because the commonest cause of a missing statement is nobody downloading it at the time. An automatic monthly export means the archive builds itself, and the year-end scramble becomes a check rather than a collection exercise.

Two things still need doing by hand. First, confirm the exports are actually arriving — an automation nobody checks is a backup nobody has tested, and the month it silently stops is the month you find out. Second, run the continuity test across the series: each statement's closing balance should equal the next one's opening balance. An automated export can miss a month just as a human can, and the balances are what prove it did not.

Monzo PDFs are cleanly typeset, which removes some of the difficulty other banks present and leaves a specific set of failures — all of them quiet.

The category folded into the description: a separate field with real value, and collapsing it into text means filtering and rules can no longer use it. The running balance imported as an amount: a position treated as a movement, inflating the file by the size of a balance.

Pot transfers read as external spending is the one worth watching. Money moved into a savings pot has not left your control — it is an internal transfer between your own balances. Treated as an expense it overstates costs, and the corresponding movement back overstates income, while profit stays untouched. That is precisely why the error survives a review that only looks at the bottom line.

And rows lost at a page break on a long statement, where repeated headers either enter the data or take the genuine first rows of a page with them. The row-to-row balance chain closes over that gap and stays perfectly continuous, so it is the document-level check — opening plus every transaction against the printed closing balance — that catches it.

For a year end, a mortgage application or a bookkeeping catch-up, two checks matter and they answer different questions. Within each statement, the opening balance plus every transaction should equal the printed closing balance — that proves the document is whole, with nothing lost at a page break and no balance figure imported as a movement. Between statements, each closing balance should equal the next statement's opening balance, exactly, through the whole period — that proves the series is unbroken.

The second one is the check almost nobody runs, and it is the one that catches the failure you cannot see. A folder can hold twelve internally perfect statements and still be missing a month entirely, because every surviving document reconciles on its own terms and the gap is invisible from either side of it.

There is a wrinkle specific to app-first banks. Because Monzo lets you choose an arbitrary date range rather than only issuing fixed monthly statements, a year is often assembled from ranges somebody picked by hand — and hand-picked ranges are exactly where consecutive periods overlap by a day or leave one uncovered. An overlap counts those transactions twice, inflating both income and costs while the closing balance still looks plausible; a gap loses them silently. Generate statements on consistent period boundaries rather than ad hoc, and run the continuity check across the set afterwards.

Keep personal and business accounts as separate series. Each is its own balance chain, and money moving between two accounts you hold is an internal transfer rather than income or expenditure. Booked as trading it inflates turnover and costs by the same amount while leaving profit untouched — which is exactly why that error survives a review that only checks the bottom line.

And save each statement when the period ends rather than when someone asks for it. Access to an app-first bank depends entirely on being able to log in: there is no branch to walk into and no paper archive arriving in the post, so closing the account removes the route completely. Whatever you saved while it was open is the whole of the record, and that is a much easier thing to arrange in advance than to fix afterwards. The same reasoning applies to anyone holding a Monzo statement on someone else's behalf: an accountant receives the document, never the login, so the PDF is the only thing that can be worked from.