StatementClear

The transactions your Xero feed never delivered.

Expired consent, an outage, a backfill cap, or an account that was never eligible. Same result - transactions that exist only on a statement. StatementClear posts them into Xero as live feed lines, deduped and balance-checked. Not another CSV import.

Lines post through Xero's official Bank Feeds API.

A feed is not the same thing as a complete ledger.

Open banking consent expires every 90 days and has to be renewed on every account. Aggregators go down for weeks. Backfill stops at twelve months. And some accounts - foreign banks, corporate cards, FX balances, lending and invoice-finance platforms - were never eligible for a feed in the first place.

Every one of those ends the same way: a stretch of transactions the feed will never deliver, and a reconnect that runs forward without filling it in. So somebody logs in, exports, reformats, uploads a CSV and hopes the balance matches. Do it across a dozen client orgs and it eats a day you will never get back.

Statement in. Feed out. Three steps.

  1. Step 1

    Connect Xero.

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

  2. Step 2

    Drop in your statement.

    PDF, CSV or Excel. Map the columns once - we remember it next time. We dedupe, check the balance and catch sign errors before anything posts.

  3. Step 3

    It's a feed now.

    Clean lines land in Xero, ready to reconcile. Re-upload overlapping statements any time; we skip the duplicates.

Xero's own import is free. Here's where it stops.

Xero will take a CSV, OFX, QIF or QBO file at no cost, and for a one-off catch-up that is the right tool. It stops being the right tool the moment it repeats.

  • No duplicate detection.

    Import an overlapping period and Xero makes a second copy of every line in the overlap. Nothing warns you, and unpicking it afterwards is manual.

  • No balance check.

    Xero imports whatever the file contains. If the export was truncated or a page was lost in conversion, the import succeeds and the account is quietly wrong.

  • No PDF, no Excel.

    The import takes CSV, OFX, QIF and QBO only. PDF and Excel are what most banks and platforms actually hand you, so there is a conversion step before you start.

  • It's a period, not a connection.

    Every month is a fresh export, a fresh reformat and a fresh import, on every account, for as long as the account exists.

StatementClear does the same job through the Bank Feeds API instead. Overlaps are deduplicated against what is already in the account, the running balance is checked against the statement before anything posts, and PDF and Excel go in as they are. What Xero's manual import accepts, and the four limits that matter.

Xero can already import a CSV. Here is what that costs you.

For one account, once, the manual import is fine. The problems start when it repeats, and when the period you are importing overlaps something the feed already delivered.

Xero's manual import

Free, and the right tool for a one-off

  • No duplicate detection. Import a period that overlaps and every transaction in the overlap lands twice.
  • No balance check. A truncated export imports cleanly and leaves the account quietly wrong.
  • CSV, OFX, QIF and QBO only. Not the PDF or Excel your bank actually gives you.
  • Imports a period, not a connection. Next month is the same job again.

Statement converters

A file, not a feed

  • Turn the PDF into a CSV and hand it back to you.
  • You still run Xero's manual import afterwards, with every limit above.
  • No knowledge of what is already in the Xero account.

StatementClear

A feed

  • Posts through Xero's official Bank Feeds API, so the lines arrive as feed lines.
  • Deduped against what is already in the account, which is what makes re-posting an overlapping period safe.
  • Running balance verified against the statement before anything reaches the ledger.
  • PDF, CSV and Excel. Columns mapped once per account and remembered.

Almost no one can do this. The Bank Feeds API is partner-only, and we're in.

Built for the people who reconcile.

Bookkeepers and accountants

Consent expires on a rolling 90-day cycle across every client org, and some accounts never had a feed at all. One tool for both, with column mappings saved per client.

Businesses with awkward accounts

A feed that lapsed mid-quarter, a backfill that stopped at twelve months, or an account Xero never covered: foreign banks, cards, FX balances, lending and invoice-finance platforms.

Get your accounts connected.

Start with your email, then tell us which accounts are missing transactions and how your org is set up.

Then a few quick questions so we know which accounts to prioritise.

We'll only email you about StatementClear, and you can opt out any time. See our Privacy Policy.

Questions, answered.

A real feed. Lines post into Xero through the official Bank Feeds API and arrive ready to reconcile, not as a manual import.

Any of them. If you can export a statement as PDF, CSV or Excel, we can feed it. We're not limited to supported banks.

Yes. We never ask for your bank login - you only upload statements you already have. They travel over encrypted connections, are stored encrypted at rest with per-account isolation, and lines reach Xero through the official Bank Feeds API. We never sell your data. The full detail is in our Privacy Policy and Security pages.

A monthly subscription per Xero org, with a plan for practices managing several.

PDF, CSV and Excel. Columns are mapped once per account and remembered, so every upload after the first is just the file. Xero's own manual import accepts none of those without conversion.

Guides to Xero feeds and statement imports

All guides or browse every bank and platform.

Get your statements feeding themselves.