The FNB feed is connected but stopped refreshing. What can I actually do?

The usual answer is wait, chase support, and import CSVs to keep month end on track. StatementClear replaces that third step with a feed: upload the statement for the missing period and the lines post into Xero through the Bank Feeds API, balance-checked against the statement. Post the gap period only, so you never have two sources writing the same days.

I run a practice and most of my clients bank with FNB. Does this scale?

That is the design case. Each client account is its own feed with its own saved column mapping, so after the first month the routine per client is download, upload, done. Dedupe and the running-balance check run on every upload.

Is this a real bank feed or another CSV import?

A real feed - lines arrive in Xero through Xero's Bank Feeds API, ready to reconcile, not as a manual import.

Is my banking data safe?

Statements are encrypted in transit and at rest, and we never sell your data. A statement is used for one job: posting feed lines into your Xero organisation.

FNB bank feed not working in Xero? Post the backlog as feed lines

FNB does have a Xero feed; keeping it running is the problem. South African practitioners have reported repeated interruptions across roughly two years, with stretches of weeks where client feeds would not connect or refresh. StatementClear posts the backlog into Xero as feed lines, deduped against whatever the feed later recovers.

Ask a South African bookkeeper about the FNB feed and you will hear about the gaps: weeks where feeds across a whole client base stop refreshing, and a backlog that grows until the feed decides to come back. StatementClear gives you a way to keep the books moving that does not depend on the feed's mood: upload the FNB statement and the lines post into Xero as a live bank feed, deduped and balance-checked.

Join the waitlist

Where the FNB Xero feed keeps falling over

FNB does have a Xero feed - the trouble is keeping it alive. South African practitioners have reported repeated interruptions across roughly two years, with stretches of weeks where client feeds would not connect or refresh, and as of mid-2026 Xero's fix was still listed as in development.

Feed interruptions hurt most in a practice, where one outage stalls every FNB client at once and the catch-up all lands in the same week. FNB's statement exports carry a running balance, which gives StatementClear something concrete to verify each upload against before anything posts. Dedupe runs against everything StatementClear has already posted, so overlapping uploads during a messy patch never double up - and if you are covering a dated gap while the native feed is down, post the gap period only, so two sources are never writing the same days.

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 FNB 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 FNB and Xero

Related accounts

Stop importing FNB statements. Start feeding them.

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