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.
14 days, no card. Connect Xero and post a real statement before you decide anything.
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 is missing transactions.
- 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
Where this comes from
Everything above about what Xero's native feed covers, what its manual import accepts and how feed lines reach a bank account comes from Xero's own documentation. The relevant pages are below, so you can check the claim rather than take it.
- About bank feedsXero's own account of which feeds exist, how they connect and what they do not cover.
- Import a CSV bank statementThe manual import: the formats it accepts, and how it handles lines it has seen before.
- Bank Feeds API overviewThe interface StatementClear posts through, and the reason a fed line is not an imported one.
Related accounts
Stop importing FNB statements. Start feeding them.
Connect Xero, drop in a FNB statement, and watch the lines arrive as feed lines.
14 days, no card. Connect Xero and post a real statement before you decide anything.
Browse every bank and platform or read the Xero bank feed guides.