Convert NatWest Statements to Xero

Be clear on that last point, because tools in this space love to blur it. A NatWest bank feed keeps a connected account topped up and only reaches back roughly 90 days. A file import is for everything beyond that — last year's months, a closed account, a catch-up backlog, a client onto Xero who only ever sends PDFs. That's where converting the statement does the real work.

Reading a NatWest statement before you convert it

NatWest doesn't print a statement the way Xero wants to receive one, so it pays to know your starting shape. Transactions run down the page with a Date, a transaction Type, a Description, then Paid in and Paid out as two separate money columns, and the running Balance on the right. Dates print as DD MMM; you'll normalise them to DD/MM/YYYY for Xero so they sort and import without flipping month and day.

The Type column is NatWest's own shorthand, and it's worth being able to read because it carries straight through into your Xero descriptions:

• BAC — a Bankers' Automated Clearing payment
• D/D — Direct Debit
• S/O — Standing Order
• POS — a card payment at a till
• TFR — a transfer between accounts
• CHG — a bank charge
• BGC — a Bank Giro Credit

Keep those codes in the Description rather than flattening every line to "payment". A row that just reads "£82.40" tells you nothing weeks later; "D/D — British Gas" tells you everything when you're matching in Xero. One quirk specific to this bank: the layout is shared across NatWest Group, so RBS and Ulster Bank statements read the same way and convert on the same logic — mixed books, one format.

Convert the NatWest PDF to a Xero-ready CSV

Here's the path that holds up, start to finish:

1. Upload the NatWest PDF to Export Bank Statement. A text export from Online Banking reads cleanly; an older scanned or photographed statement is an image, so it goes through OCR first.
2. Let it extract every line — Date, Type and Description, Paid in, Paid out and the running Balance for each transaction.
3. Check the reconciliation result. The tool recomputes the running Balance from opening to closing. If the figures agree you get a clear tick; if a line was misread or dropped, the statement is flagged before you download anything.
4. Download the CSV in Xero's native bank-import layout, ready for Import a Statement.

Map NatWest columns to what Xero imports

When you open Import a Statement, Xero asks you to map the columns in your file. It works with Date, Amount, Payee and Description, plus an optional Reference. NatWest's Paid in / Paid out split maps across like this:

Two things trip people up on NatWest files. First, the date format: Xero reads dates the way you tell it to on the import screen, so a January date read as December is a quiet, year-end-only kind of error. Match the format to the file. Second, signed amount versus separate debit and credit: Xero takes either one Amount column where Paid out is negative and Paid in is positive, or two columns for debit and credit. NatWest prints them separately, so your CSV can keep that split or fold it into one signed Amount — both import fine. The single mistake to avoid is mapping a Paid out figure as a positive amount, which inflates your balance. Map it once and Xero remembers the layout for that account next time.

Why the running-balance check is the step that matters

Pulling the transactions out of a NatWest PDF is the easy half. Knowing you pulled out *all* of them is the half that protects your numbers — and it's the part most converters quietly leave to you. A tool can hand back a tidy-looking CSV that's missing one Direct Debit off the foot of page four, and a clean file that's wrong is worse than an obvious mess, because you'll trust it and import it.

This is where NatWest's running Balance earns its keep. It's a built-in checksum: opening Balance, plus everything Paid in, minus everything Paid out, has to land on the closing Balance, and the running figure has to tie line by line. If a misread "£2,150.00" should have read "£2,750.00", the totals stop matching and the gap surfaces at the convert stage — not three weeks later when you're chasing a £600 hole through a reconciled month in Xero.

Export Bank Statement converts the NatWest PDF — scanned and photographed copies included, via OCR — into a clean CSV or Excel file, then runs that running-balance check for you. It recomputes the totals against the printed closing Balance and flags any statement that doesn't reconcile, so a dropped or misread line shows up before it reaches Xero. Most converters don't do this. On a busy NatWest business account we once watched a clean-looking file fail the check on a single payroll payment clipped from a batch; the flag turned an afternoon of hunting into a one-minute fix.

It writes the file in Xero's native bank-import layout, so the columns arrive shaped the way Import a Statement expects. Just hold the honest line on what it is: convert, then import. It doesn't push transactions into Xero through a certified bank-feed API, and it isn't a bookkeeping service — you stay in charge of what gets imported. For loading several past months at once, the historical-import approach covers ordering and overlaps; if you're unsure whether Xero takes a PDF at all, the answer is in can Xero import PDF bank statements.

Import the CSV and reconcile in Xero

Open your NatWest account in Xero, choose Import a Statement, upload the CSV, confirm the column mapping and the date format, then import. The transactions arrive as statement lines, exactly the way a feed would deliver them — ready to match against your bills, invoices and existing entries.

Reconciling before you import is what keeps this tidy. If the CSV already balances opening to closing, you're matching a full set of lines, not hunting a phantom that never crossed a page break. NatWest business statements are where that bites hardest: a busy month runs to dozens of pages, the closing Balance of one page becomes the opening Balance of the next, and a line lost at a break throws off everything below it. Treat the whole document as one statement and check it end to end.