NatWest Statement to Excel Converter

Separate paid in and paid out columns, type codes and a running balance make manual re-keying slow and error-prone — one wrong figure breaks the reconciliation.

FlowParse reads the whole statement at once, signs amounts correctly, and validates the balance, turning the job into a 30-second conversion.

NatWest uses the standard UK grid: Date, Type, Description, Paid in, Paid out and Balance, as one continuous table rather than a set of named blocks.

Direction is carried by which of the two money columns a figure occupies, not by a sign on the number, and on most rows one of the two is empty. That is the single most important thing to preserve during extraction — merge the columns and every amount survives while direction does not, producing a file of entirely plausible numbers and a reconciliation out by exactly twice the affected total.

The Balance column gives a per-row anchor, which makes the row-to-row check available: each balance minus the previous one should equal that row's signed amount, pinning a misread figure to an exact row. The Type column carries a short code for the payment method, and it is worth keeping as its own field because it distinguishes transactions the description alone cannot separate.

FlowParse merges Paid in and Paid out into one signed amount, keeps the Type code distinct, excludes the Balance column from the transaction list, and runs both the row chain and the document-level check against the opening and closing balances NatWest printed.

Log in to Online Banking at onlinebanking.natwest.com and select Statements & transactions from the main menu. NatWest's own guidance describes downloading recent or historic statements going back up to seven years, with a PDF version shown in Online Banking as soon as a statement has been issued, which you can save and print.

Seven years is generous by international standards, and it depends on the account still being open. Once an account closes the self-service route goes with it at every bank, so if you are switching, closing a business account or winding a company up, download the full history before the closure completes rather than afterwards.

Verified against NatWest's own support-centre pages on accessing bank statements online, August 2026. Confirm the current path before relying on it — banks reorganise their apps without notice, and one of NatWest's older how-to URLs already redirects to a fallback page.

NatWest makes a point on its own support pages that is worth repeating, because it changes how you should treat the file: a downloaded PDF statement can serve as proof of identity, address or income.

That is a different job from bookkeeping, and it explains why the PDF matters even once you have converted it to a spreadsheet. A lender, a landlord or a compliance check will accept the bank's own document; they will not accept a spreadsheet you produced from it, however accurate. The two artefacts are not interchangeable, and only one of them can be reissued by the bank.

So keep both, deliberately. The converted data is what you work with — filter it, categorise it, reconcile against it. The PDF is the evidence behind it, and it is what you hand over when somebody official asks. If the two ever disagree, the statement is what settles the question, which is precisely the reason for keeping the original unmodified rather than only the convenient derivative.

This also affects how you store a year. Filing only exported spreadsheets and deleting the source PDFs feels tidy and quietly removes your ability to evidence anything. Keep the documents, organised by account and period, and treat the spreadsheets as working files derived from them.

Four failures, each leaving output that looks entirely reasonable.

Paid in and Paid out merged into one column. Direction disappears, payments read as receipts, and the arithmetic misses by exactly twice their value.

The Type code folded into the description. Nothing looks broken and categorisation downstream gets quietly worse, because the most stable signal about what a transaction was has been buried in a text field that banks reformat without notice.

The Balance column imported as an amount. A position treated as a movement, inflating the file by the size of a balance — usually large enough to be noticed, which makes it one of the more forgiving errors here.

Rows lost at a page break. Column headings repeat at the top of each page, and where they are not recognised as repeated furniture either they enter the data or the genuine first rows of the page are dropped with them. The row-to-row balance chain cannot see this, because it closes over the gap and remains perfectly continuous; the document-level check is what catches it.

Once a year of NatWest transactions is in a spreadsheet, one review pays for the whole exercise: listing everything that recurs.

Recurring outflows are where money quietly leaks. Subscriptions nobody cancelled, services renewed automatically, insurance that rolled over at a worse rate, a standing order to a supplier you stopped using. None of it shows up as a problem in any individual month, because each amount is small and each looks exactly like it did last time. It shows up when twelve months are in one place and sorted.

The Type code is what makes the review quick, which is the practical reason for keeping it as its own column rather than folding it into the description. Filter to the payment types used for recurring instructions and you have the candidate list in seconds, rather than reading a year of descriptions looking for repetition.

The distinction between the two main recurring types matters when you act on the list. A standing order is an instruction you gave your bank, for a fixed amount, and you can change or cancel it yourself. A direct debit is an authority you gave the recipient to collect varying amounts, so cancelling it without telling them leaves an obligation unpaid and usually a failed payment. The type tells you which conversation you need to have.

Take a full twelve months rather than a sample. Annual charges — insurance, licences, professional subscriptions, domain renewals — appear exactly once, and a three-month extract misses every one of them. That is also why this review is worth doing from converted statements rather than from memory: the statements contain the things you have forgotten, which is precisely the point.

One caution on acting from the list: a payment that stops appearing is as interesting as one that keeps appearing. A direct debit that quietly failed, a standing order that lapsed when card details changed, a supplier who stopped collecting — each leaves a gap in the pattern rather than an entry, and gaps are invisible when you read a year looking for what is there. Sorting by counterparty and checking that each recurring item appears the number of times it should is the version of this review that catches both.