The ninety percent is easy. We built for the rest.
Exact-match reconciliation is table stakes and every tool claims it. The cases below are what actually cost you the week.
Start free trialThis is the review screen, running.
Eight transactions off the feed, each already coded with the account Cy chose and how sure it was. Recording them is one action, and the result below is the product's own — not a caption we wrote.
Seeded figures, disconnected from any database. Nothing here can be posted.
Where the queue actually goes to nought.
This is the same workspace as folio 01, further down the line. The interesting column is the last one: the product tells you how confident it is, and stops when it is not.
- 01
The backlog from folio 01, cleared
Two thousand three hundred lines is not a queue anybody works through by hand. Ninety-six per cent of them follow a pattern, and patterns are the one thing software is genuinely better at than people.
- 02
One payout, twelve invoices, net of fees
A processor settles the week as a single figure. Cy decomposes it back to the invoices it covers, posts the fee to its own nominal, and leaves nothing floating.
- 03
It shows you how sure it is
Sixty-one per cent means two plausible candidates and no honest way to choose. So it stops and asks, with the evidence already attached, instead of picking one quietly.
Matched means posted
There is no staging area. A matched line is a journal entry, which is why the unreconciled figure can sit at nought rather than at 'nearly'.
Corrections stick
Overrule a match once and the correction becomes the rule for that counterparty. It is learning your ledger, not an average of everybody else's.
Nothing posts to a closed period
Late arrivals against a closed month are held and flagged rather than quietly backdated into figures you have already signed off.
Figures shown are from a demonstration workspace. Counterparty names are obscured.
The cases a rules engine gives up on.
Exact-match reconciliation handles the easy ninety percent, and every accounting tool claims it. These five are what actually eat the week — and the reason most teams still reconcile by hand.
- 01
The batched payout
One deposit of £48,209.14 settles forty-seven invoices, net of processor fees and a refund issued the week before.
What resolving it takesSplit the deposit across every invoice it covers, post the fee to its own nominal and net the refund — without anyone opening forty-seven records to do it.
- 02
The part-payment
A customer pays £8,000 against a £12,500 invoice and sends no remittance advice with it.
What resolving it takesAllocate against the oldest open balance, leave the invoice correctly part-settled, and keep the debtor ageing honest instead of closing it to make the screen tidy.
- 03
The crossed reference
A supplier quotes their own invoice number on the payment. Yours appears nowhere on it, and never has.
What resolving it takesMatch on amount, date proximity and that supplier's history rather than the reference — then remember the habit, so it is never a question again.
- 04
The FX leg
Money leaves on Tuesday at one rate and arrives on Thursday at another. Neither figure agrees with the invoice.
What resolving it takesRecognise both legs as a single movement and post the difference as realised FX against the right nominal, not as an unexplained variance for someone to chase.
- 05
The honest duplicate
The same invoice is entered twice, nine days apart, under two different references by two different people.
What resolving it takesFlag it on amount, supplier and line detail before it is paid — which is the only point at which finding it is worth anything.
Every one of these is a real pattern from customer ledgers, anonymised. They are the cases the engine was built around, because the easy ninety percent was never what cost you the week.
The same close, minus the week.
Not a faster version of the same work — most of the work stops being yours. What is left is the part that actually needs an accountant.
Hover a block to see what that stage involves
Figures are the median reported by WAW Profi customers across their first two month-ends, self-reported at onboarding and again at ninety days. Closes vary enormously by entity count, transaction volume and how clean the opening balances are — treat this as a shape, not a promise.
Your next month-end could be the last hard one.
Connect your accounts, let WAW Profi backfill the history, and see your first automated close before the trial is out.