Skip to content
StatementClear
Start a free trial

Mercury bank feed for Xero: import Mercury statements as a live feed

Mercury's native Xero feed syncs a live USD account forward and backfills twelve months at most. Checking, savings, treasury and the IO card each produce their own statements, and older history is a manual job. StatementClear posts those statements into Xero as live bank feed lines instead.

Mercury's own Xero feed covers the easy case: one live USD account, syncing forward. Real setups are rarely that tidy - checking, savings and treasury each produce their own statements, and the IO card runs its own cycle. Whatever the native feed does not sync is a manual import every month, not a one-off. StatementClear closes that gap: upload the Mercury statements you have and they post into Xero as a live bank feed, deduped and balance-checked, ready to reconcile.

Start a free trial

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

Where the native Mercury feed falls short

Mercury offers a native Xero feed, connected from inside Mercury and free to use, so if you only need a daily USD feed going forward, use it. The limits sit at the edges: the first sync backfills twelve months at most, older history is a manual job, and connecting on top of previously imported statements leaves duplicates to clear by hand.

Mercury is USD only, but one company rarely means one account: checking, savings and treasury sit separately, each with its own statements, and the IO credit card produces statements of its own. The native feed's first sync reaches back twelve months at most, so older history - common when a startup gets its books built properly for the first time - has to come from the monthly PDF statements or a CSV export. On the Xero side, the receiving bank account must be USD, so a UK or Australian org needs multi-currency enabled before anything can post. StatementClear takes those PDF and CSV exports, maps the columns once per account, and posts each account's history into Xero as feed lines, with dedupe and balance checks run before anything lands.

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

For everything the native feed cannot reach. The first sync backfills at most twelve months, so older history - a catch-up year, a late-connected account - still has to come from statements. StatementClear posts those statement lines into Xero as live feed lines through Xero's Bank Feeds API, so the history reconciles exactly like the feed does.

Yes. Mercury accounts are USD, so your Xero org needs a USD bank account to receive the lines, which on most plans means multi-currency enabled. Once that account exists, upload your Mercury statements and StatementClear posts them as a feed, the same as any other account.

A real feed. StatementClear posts lines through Xero's Bank Feeds API, so they land in Xero the way native feed lines do: ready to reconcile, deduped, with sign and balance checks run first. Converters give you another file to import by hand; this leaves nothing to import.

Yes. Each Mercury account maps to its own Xero bank account and its own feed, so checking, savings, treasury and the IO card reconcile separately rather than being flattened into one line. Upload each statement and the mapping is remembered.

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 Mercury statements. Start feeding them.

Connect Xero, drop in a Mercury 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.