All seven builds Invoice exceptions
Ledger Solutions logo

It stops the invoice and attaches the reason.

Before

Someone opened every single invoice to find the few that were wrong.

Now

The clean ones post themselves. The rest stop, with the reason attached and the question for the client already written.

Open the system What a build like this costs
ClientLedger Solutions
Clean invoicespost themselves
The reststop, with the reason attached
Counted toposting, not payment release
Releases a paymentnever

Built for a practice that keeps the books for other companies. Invoices that are clean post themselves; the ones that are not stop, with the reason attached and the question for the client already drafted.

The exception queue is the product, not the extraction. Reading an invoice accurately is a solved problem. Knowing which ones a person must look at, and why, is the actual job — so the number published here is about what stops, not about what is read.

What was measured, and what it does not say.

Every figure carries its own limit. Of the eight firms we checked, not one states the method or the limits behind any number it advertises.

4 in 5 Invoices that now post with nobody watching, out of 200 to 600 a month. What it does not say: nobody has counted what got through when it should have stopped.
3 Duplicate invoices caught in the last year, the largest more than $1,000. Each one would have been paid twice. It also stops on totals that do not add up, on suppliers the practice has no record of, and on an invoice that adds up perfectly and is wrong on its face — a description that does not fit the supplier. That last one is the only catch the arithmetic cannot make.

Three things it will not do.

These are in the build because a wrong answer to any of them costs more than no answer at all.

Posting anything a person has not seen, where the rules say stop

An invoice held by a control stays held. Nothing downstream can release it, including the model that reads it.

Treating an accepted suggestion as automatic

A person accepting a suggested account code is a human decision and is recorded as one.

Releasing a payment

The published figure stops at posting. Payment release is a separate act by a person.

What the reading adds to the arithmetic

  • The controls are exact and read nothing: totals, duplicates, unknown vendors, account codes.
  • What they cannot see is an invoice that adds up perfectly and is still wrong on its face — a description that does not fit the supplier, a round-sum charge for something usually itemised, a month named that the period does not cover.
  • A model reads for those and can stop an invoice. It can never release one, and that is enforced in code.

What Ledger Solutions says.

Approved by Ledger Solutions for publication.

Before, someone opened every invoice. Now most of them post while nobody is watching, and the day goes on the ones that need a decision. Our juniors stopped doing the dullest work in the practice, which has done more for us than we expected. It has been changed twice since it went in — once because we asked, and once because they noticed something we hadn’t and rang us about it.