Reconciliation is a filing problem

Every accounting tool we have used treats reconciliation as a matching exercise. Here is a bank line for £17.99. Which category does it belong to? Pick one from the dropdown, write a description, move on.

That framing is why reconciliation is miserable. The hard part was never choosing the category. The hard part is that the invoice explaining the charge is somewhere in an inbox, and finding it costs more than the explanation is worth. So people skip it. They guess the category from the bank descriptor, they leave the VAT on a default, and at year end their accountant asks for the paperwork behind forty transactions nobody can produce.

We built Filite the other way round. The document comes first. Once the invoice is filed and read, the bank line is not a question any more.

The document arrives before the bank line does

Almost always, the invoice reaches you days before the payment leaves your account. IONOS emails a receipt when they charge the card. Google Ads sends the monthly invoice. The lease renewal turns up as a PDF from the agent. That is a queue of documents nobody is processing, sitting in an inbox, aging.

Give suppliers your Filite address, or forward things when they arrive, or connect Gmail and let Filite read the supplier mail already sitting there. Whichever route it takes, the email and its attachments are captured as they arrived. We keep the original, not a thumbnail of a crumpled photo, because in three years the original is the thing HMRC or your accountant will ask for.

Filite reads what it captured. Vendor, date, total and VAT treatment come off the document itself, and the whole thing becomes searchable in seconds. Not searchable by the fields somebody remembered to type, but by supplier, month, amount, or the half-remembered detail that is usually all you have to go on.

Then the bank feed explains itself

When the £17.99 shows up in your FreeAgent bank feed, the invoice explaining it is already filed and already read. Filite matches the two, attaches the PDF to the transaction, books the VAT the way the document says it should be booked, and flags the whole thing for your review.

Reverse charge is the case that makes this worth doing. A Google Ads invoice is not a 20% UK purchase, and treating it like one is the sort of quiet, repeated mistake that costs a lot to unpick later. When the VAT treatment is read off the invoice rather than inferred from a bank descriptor, it comes out right.

Nothing posts without you. Filite explains, marks it for review, and waits. Your part is reading three or four items and clicking approve, which takes about two minutes. That is the job now.

We are live on FreeAgent today, with Xero next.

The archive is worth more than the reconciliation

Here is the part we did not expect when we started. Once every invoice, receipt, contract and statement is filed and readable, the reconciliation stops being the point. The archive becomes the thing you use.

Filite runs on docstore.ai, which speaks MCP, the open protocol AI tools use to reach real data. Connect Claude, or Claude Code, or any MCP client, and your assistant is reading actual documents and actual ledger entries rather than guessing. Where is the March IONOS invoice. What did we spend on hosting last quarter. Is the laptop still under warranty. When does the office lease break clause fall.

Your agent can also keep notes in that same archive, so the rules you work out together about how your books are handled stay put instead of being re-explained every session.

None of that works if the paperwork is scattered across an inbox, a Dropbox folder and a shoebox. It works because the filing happened first.

Reconciliation was never the goal. It is just the first thing you get for free once your documents are somewhere they can be found.