UK
A NatWest statement gets into QuickBooks in three moves: turn the PDF into a CSV with a Date, a Description and an Amount, prove the file still reconciles against NatWest's printed running Balance, then upload it under Transactions > Bank transactions. QuickBooks won't read the PDF itself — it accepts CSV, Excel, QBO and OFX — so the file you build before the upload is where everything is won or lost. And to be plain about it: this is a file you upload by hand, not a live bank feed piping data in over an API.
That last point matters more than people expect. A bank feed keeps a connected NatWest account topped up with recent activity. A file import is for everything a feed leaves behind — last year's months, a closed account, a catch-up backlog, a client who only ever emails PDFs. Statements stuck in a PDF belong to the file route, every time.
Read the NatWest layout before you touch QuickBooks
NatWest doesn't lay a statement out the way QuickBooks wants to receive it, so it helps to know the shape you're starting from. 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 on the page; for QuickBooks you'll normalise them to DD/MM/YYYY so they sort and import cleanly.
The Type column is pure NatWest shorthand, and it's worth being able to read it because it carries straight through into your QuickBooks descriptions. BAC is a Bankers' Automated Clearing payment, D/D a Direct Debit, S/O a Standing Order, POS a card payment at a till, TFR a transfer, CHG a charge and BGC a Bank Giro Credit. Keep those codes in the Description rather than flattening every line to "payment" — they're what makes a transaction recognisable months later when you're categorising in QuickBooks.
One more thing about NatWest: the format is shared across NatWest Group, so RBS and Ulster Bank statements read the same way and convert on the same logic. If your books mix those accounts, you're working with one layout, not three.
Convert a NatWest statement to QuickBooks step by step
Work through these in order. Each one assumes the previous step came out clean.
- Gather your NatWest PDFs in date order, no gaps. Pull them from Online Banking (Statements & transactions) or the app, where you can reach up to seven years back. A skipped month means a missing opening balance, and the import after the gap starts from the wrong figure.
- Convert each PDF to a spreadsheet. Lift the transactions into CSV or Excel. A text PDF straight from Online Banking reads cleanly; an older scanned or photographed statement is an image, so it needs OCR to read the figures off the page.
- Check the file reconciles. Take the opening Balance, add every Paid in, subtract every Paid out, and confirm you land on the printed closing Balance — and that the running Balance ties line by line. The first row where your recomputed total stops matching NatWest's Balance is the exact line where something was dropped or misread.
- Reshape the columns for QuickBooks. Cut it down to Date, Description, Amount. Either fold Paid in and Paid out into one signed Amount column (Paid out negative, Paid in positive), or keep them as separate debit and credit columns. Strip the £ sign and any thousands commas, and set dates to a format QuickBooks accepts — it asks you which during import.
- Upload it. In QuickBooks Online, open Transactions > Bank transactions, select the NatWest account, choose Upload from file, map your columns when prompted, and import. The lines drop into the For Review tab, ready to categorise and match.
Map NatWest columns to the QuickBooks 3-column CSV
QuickBooks Online's manual import wants three things per transaction: a Date, a Description and an Amount. You can hand it the Amount in either of two shapes. Simplest is a single signed column — Paid out as a negative, Paid in as a positive. The alternative splits them into a separate debit column and credit column. Both import fine; choose one and hold it steady across the whole file.
NatWest column | What QuickBooks needs | How to handle it |
|---|---|---|
Date | Date | Keep it; normalise DD MMM to DD/MM/YYYY, confirm the format on import |
Type + Description | Description | Keep the type code (D/D, BAC, S/O, POS) with the text so the line stays recognisable |
Paid out | Amount (negative) or Debit | Negative in the signed column, or its own debit column |
Paid in | Amount (positive) or Credit | Positive in the signed column, or its own credit column |
Balance (running balance) | — not imported | Use it to check the conversion, then drop the column |
QuickBooks rejects a handful of things outright, so clear them before uploading: currency symbols, thousands separators inside numbers, blank rows and merged header cells. A Description that's empty on the odd row is tolerated; an empty Amount is not.
The running-balance check is the step almost everyone skips
Converting the NatWest PDF is the easy half. Knowing the converted file is *complete* is the hard half — and it's the part most tools quietly leave to you. A converter can hand back a neat-looking CSV that's missing one Direct Debit off the bottom of page four, and a tidy file that's wrong is worse than an obvious mess, because you'll trust it and import it.
This is where NatWest's own running Balance does real work. It's a built-in checksum: opening Balance, plus everything Paid in, minus everything Paid out, has to equal the closing Balance on the last line. If a misread "£2,150.00" should have read "£2,750.00", the totals stop tying and the gap shows up straight away — not a fortnight later when you're chasing a £600 hole through your QuickBooks accounts.
Export Bank Statement converts the NatWest PDF — including scanned and photographed copies, via OCR — into clean CSV or Excel, 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 surfaces before it reaches QuickBooks. We once watched a clean-looking import fail this check on a single payroll payment clipped from a batch on a busy NatWest business account; the flag turned an afternoon of hunting into a one-minute fix.
It writes the file in QuickBooks' native bank-import CSV format, so the columns arrive shaped the way QuickBooks expects. Just be clear on what it is: convert, then upload. It doesn't push transactions into QuickBooks through a live bank-feed API, and it isn't a bookkeeping service — you stay in charge of what gets imported and how it's reconciled. For the QuickBooks side in detail, the import PDF statements into QuickBooks guide and the QuickBooks CSV import format walkthrough go field by field, and the NatWest statement guide covers the conversion end. You can also browse the wider US accounting guides.
Business statements, batches and page breaks
NatWest business current accounts are where the check earns its place. A busy month can run to dozens of pages, and the closing Balance of one page becomes the opening Balance of the next — so a transaction lost at a page break throws off everything below it. Payroll runs and supplier batches post together too, and a clipped batch breaks the running Balance like any other gap. Treating the whole document as one statement and reconciling end to end is what catches those, whether it's a single page or fifty.
Frequently asked questions
Can QuickBooks import a NatWest PDF statement directly?keyboard_arrow_down
No. QuickBooks Online imports CSV, Excel (.xlsx), QBO and OFX files, not PDFs. A NatWest PDF has to be converted to a CSV first, then uploaded under Transactions > Bank transactions. The Receipts feature reads a single receipt or bill, but it won't take a full NatWest statement's transaction history.
How do I map NatWest Paid in and Paid out to QuickBooks?keyboard_arrow_down
QuickBooks needs one Amount per line. Either combine Paid out and Paid in into a single signed Amount column — Paid out negative, Paid in positive — or keep them as separate debit and credit columns. Leave the NatWest running Balance out; QuickBooks doesn't import it, though you should use it to check your conversion first.
Will the QuickBooks bank feed import my old NatWest statements?keyboard_arrow_down
No. A NatWest bank feed keeps a connected account current and only reaches back a few months. Older NatWest history has to be imported manually as a CSV, which is exactly why converting the PDF matters for catch-up work and migrations.
Does this work for RBS and Ulster Bank statements too?keyboard_arrow_down
Yes. NatWest, RBS and Ulster Bank share the same NatWest Group statement layout — the same Paid in / Paid out / Balance columns and type codes — so the same conversion, reconciliation and QuickBooks mapping apply.
How do I know the converted NatWest file is complete before uploading?keyboard_arrow_down
Check that it reconciles: opening Balance plus Paid in, minus Paid out, should equal the printed closing Balance, with the running Balance matching line by line. A converter that recomputes the running Balance and flags any statement that doesn't reconcile catches a dropped transaction up front, before it skews your QuickBooks books.
Try it on your own statement
Clean Excel/CSV, with every transaction checked to balance.