Skip to content
StatementClear
Start a free trial

Tide bank feed not working in Xero? Post the missing weeks as feed lines

Tide's Xero feed refreshes roughly every two hours until its 90-day open banking consent expires, and the stretch before anyone notices becomes a manual job. Reconnecting can create duplicate accounts to clean up. StatementClear posts the missing weeks into Xero as feed lines, deduped against what the feed already caught.

Tide's feed works until it quietly stops: open banking consent expires every 90 days, and the stretch between expiry and the day someone notices becomes a manual import job. Reconnection has its own mess - Xero's guidance notes a reactivated Tide connection can create duplicate accounts to clean up. StatementClear posts the missing weeks into Xero as live feed lines, deduped and balance-checked, so the gap closes without hand-building an import file and without double-posting what the feed already caught.

Start a free trial

14 days, no card. Connect Xero and post a real statement before you decide anything.

Where the native Tide feed falls short

Tide has a direct feed into Xero, set up from inside Tide and refreshing roughly every two hours. It runs on 90-day open banking consent and backfills a maximum of twelve months, so a missed renewal or an older account leaves gaps that still need filling by hand.

Tide's native feed has two structural limits worth knowing before you rely on it. Consent expires every 90 days under open banking rules, and a missed renewal stops the feed from the expiry date - the missing weeks then have to be spotted and filled by hand, and Xero's community threads suggest plenty of people find out late. Backfill is capped at twelve months, so an account older than that needs its early history brought in from statements. Only the Tide account owner can set up or renew the connection, a recurring headache for bookkeepers who are not the owner. StatementClear works from Tide's CSV or PDF statement exports instead: upload the missing period, map the columns once, and dedupe plus balance checks make sure the patch posts cleanly. Reconnection is where duplicates creep in: the overlap between the dead feed's last day and the new consent's first is easy to post twice, and a reactivated connection can create duplicate bank accounts in Xero that need deleting. StatementClear's dedupe checks every upload against what it has already posted, so covering a gap with a statement never double-counts 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.

  1. Step 1

    Connect Xero

    Link your org and pick the account that is missing transactions.

  2. Step 2

    Upload your Tide statement

    PDF, CSV or Excel - whatever you can export. Map the columns once and we remember the mapping.

  3. Step 3

    We check it first

    Duplicates are skipped, the running balance is verified, and sign errors are caught before anything posts.

  4. Step 4

    It lands as a feed

    Clean lines arrive in Xero through the Bank Feeds API, ready to reconcile.

Questions about Tide and Xero

Either way works. Some people use StatementClear to patch the gaps a lapsed 90-day consent leaves; others post their Tide statements monthly and skip the renewal cycle altogether. Both routes post live feed lines through Xero's Bank Feeds API, so reconciliation looks identical.

Yes. The native feed backfills twelve months at most, but Tide lets you download statements for older periods. Upload them in any order; dedupe stops overlaps posting twice and the balance checks flag a period that has gone missing.

No. Converters hand you back a file that you still have to import into Xero yourself, and it never becomes a feed. StatementClear posts your statement lines straight into Xero as a live bank feed - deduped, balance-checked, nothing left to import.

To your Xero org, and it is not sold to anyone. Files are encrypted in transit and at rest, and the statement lines go one place: the Xero bank account you choose, through Xero's Bank Feeds API.

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.

Guides for Tide in Xero

Related accounts

Stop importing Tide statements. Start feeding them.

Connect Xero, drop in a Tide statement, and watch the lines arrive as feed lines.

Start a free trial

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.