Feeds from every account
Operating, payroll, savings, and card accounts via Plaid, Finicity, or direct bank connections, with statement import as a fallback where a bank has no feed.
Platform · financial core
A monthly reconciliation finds a break four weeks after it happened, when the person who would have recognised the transaction has forgotten it. Running continuously turns a close task into a daily thirty-second review, and it is the single cheapest close improvement available.
Connect a read-only feed and we will reconcile a month against your ledger, showing every break itemised.
What it does
Operating, payroll, savings, and card accounts via Plaid, Finicity, or direct bank connections, with statement import as a fallback where a bank has no feed.
Exact on amount and reference, split where one deposit covers several items, and fuzzy where a memo line needs interpreting. Only the first two post automatically.
Anything without a confident candidate is held with the reason stated. An unexplained wire waits for a person rather than being coded to a suspense account nobody revisits.
Reconciliation runs daily, so a break surfaces the day it happens when someone still remembers the transaction — rather than on day four of the close when nobody does.
Real balances across every account and entity, with committed outflows from approved payment runs and expected inflows from ageing.
Foreign-currency bank accounts revalued correctly, with realised and unrealised gain and loss posted to the right accounts rather than lumped together.
Most automated reconciliation tools are optimised for match rate, because match rate demos well. The way you raise it is to lower the confidence threshold, and the way that manifests is a suspense or ask-my-accountant account that accumulates transactions nobody ever resolves.
We find that balance in almost every QuickBooks file we convert, and it is frequently years old and several thousand dollars. It exists because at some point a system, or a person under time pressure, preferred a coded transaction to an open question.
So our matcher posts only exact and split matches. Fuzzy matches are proposed and wait. Anything without a candidate goes to an exception queue with the reason stated. The match rate is lower than it could be and the number of unresolved items at year end is near zero, which is the trade worth making.
The obvious benefit is that day one of the close is already done. The larger one is that breaks get investigated while they are still cheap. A deposit that does not match is a two-minute question on the day it lands and a forty-minute archaeology exercise five weeks later.
It also changes the cash position from a number someone assembles to a number that exists. For businesses managing to a covenant or a tight runway, knowing real cash across every account and entity without asking anyone is worth more than the reconciliation itself.
Bank reconciliation proves your cash accounts agree with your bank. The shadow ledger proves our entire computed trial balance agrees with your existing system. They are different assurances at different scopes, and the first is a component of the second.
Customers on Connect get both from day one, which is why a reconciliation engagement is usually where an erp.io relationship starts — it is cheap, it is read-only, and it produces evidence rather than a claim.
Some smaller institutions still have no usable feed. We support statement import with the same matching logic, and we will tell you during the assessment which of your accounts fall into that category rather than discovering it in week three.
Questions
One month, read-only, every break itemised to the transaction that caused it.