Why does Xero say I have no valid accounts when connecting NatWest Bankline?

It is a permissions error rather than a feed fault. Bankline needs a user role carrying third-party provider privileges before Xero can see the accounts, and assigning it is an administrator action inside Bankline. Until that happens, the account can still be kept current from statements.

How much NatWest history can I get into Xero?

The feed offers up to twelve months when you first connect it. Older periods come from statements, which NatWest provides for well beyond that. Upload them in any order - dedupe stops overlaps posting twice and the balance checks flag a missing period.

Will reconnecting my NatWest feed fill in the weeks it missed?

No. A renewed consent delivers from the day it is renewed onwards. The gap in between is the part people forget, and it is why an account still will not reconcile after a successful reconnect. That period is what StatementClear posts.

Is this a real bank feed or another CSV import?

A real feed. The lines post through Xero's official Bank Feeds API and land ready to reconcile, next to whatever the native NatWest feed brings in. There is nothing left to import by hand.

NatWest bank feed for Xero: post the periods the feed did not deliver

NatWest's Xero feed covers business current, savings, card and foreign currency accounts, imports twice a day and shares twelve months of history at setup. Bankline accounts fail with a no-valid-accounts error until a role with third-party provider privileges is assigned. StatementClear posts NatWest statements into Xero as feed lines to cover what the feed misses.

Most NatWest feed problems are not outages, they are permissions. Bankline users hit an error saying there are no valid accounts, which reads like a broken feed and is actually a user role that has not been granted third-party provider privileges - and the person who can grant it is often not the person setting up the feed. Behind that sit the ordinary limits: consent expires every 90 days, backfill stops at twelve months, and a reconnect runs forward without filling in what it missed. StatementClear posts NatWest statements into Xero as live feed lines, deduped against what the feed already delivered.

Join the waitlist

Where the native NatWest feed falls short

NatWest has a direct Xero feed covering business current, savings, credit card and foreign currency accounts. It imports twice a day on a 90-day open banking consent and shares up to twelve months of history when you first connect. Bankline is where it gets complicated: the connection fails with a no-valid-accounts error until somebody assigns a user role carrying third-party provider privileges.

The NatWest feed itself is unremarkable in a good way - business current, savings, credit card and foreign currency accounts, importing twice a day, twelve months of history offered at setup. What catches people is Bankline. Connecting a Bankline account to Xero fails with an error saying you have no valid accounts unless a user role carrying third-party provider privileges has been assigned inside Bankline, and that is an administrator action at the bank rather than anything Xero can fix. In a practice this is the worst kind of blocker: the bookkeeper hits the error, the client's Bankline administrator has to act, and the account stays unfed for however long that takes. The rest is the standard open banking shape. Consent lapses every 90 days and the feed stops on the expiry date rather than on the day it is noticed. Backfill is capped at twelve months, so anything older comes from statements regardless. A reconnection delivers from the day it is made and does not recover the stretch in between. StatementClear closes all of those the same way: upload the NatWest statement as PDF, CSV or Excel, map the columns once and they are remembered, and every line is checked against what has already posted before anything reaches Xero - so an account that has been waiting a fortnight on a Bankline permission catches up without double-posting the edges.

The manual way, every month

Log in and export a statement (and hope the format didn't change)
Reformat columns, dates and signs until Xero's importer accepts it
Upload the CSV into the right account and pray nothing doubled up
Eyeball the balance, fix what broke, repeat next month

And after all that, it still isn't a feed - it's a one-off import you'll redo next month.

The StatementClear way: a real feed

Upload the statement and it posts into Xero as a live bank feed through Xero's Bank Feeds API - deduped, balance-checked and ready to reconcile. Not another file to import. Converters hand you a CSV; this arrives in Xero the way a bank feed does.

Step 1
Connect Xero
Link your org and pick the account that has no feed.
Step 2
Upload your NatWest statement
PDF, CSV or Excel - whatever you can export. Map the columns once and we remember the mapping.
Step 3
We check it first
Duplicates are skipped, the running balance is verified, and sign errors are caught before anything posts.
Step 4
It lands as a feed
Clean lines arrive in Xero through the Bank Feeds API, ready to reconcile.

Questions about NatWest and Xero

Related accounts

Stop importing NatWest statements. Start feeding them.

Tell us how your NatWest setup is structured and we'll get you connected.