Home › The output
The register.
Every invoice in the batch, its status, and anything found against it. This is what you keep working in, and it is the artefact you can hand to a bookkeeper.
| Invoice | Supplier | Date | Amount | Status | Finding |
|---|
Illustrative rows from a made-up batch. Yours would be your own invoices, named and dated.
A legacy .xls, an encrypted PDF, a scanned image or a phone photo is listed as unreadable with the reason given. We never estimate around a gap.
The other two files
The register is one of three things you receive.
The client report
Page one carries the number and the decisions. It also carries a section on what the review could not cover — scanned invoices, encrypted files, a table with no recognisable columns — because that section is part of the result, not a disclaimer bolted on.
The ninety-day plan
What to chase first, who owns each line, and what the same leaks would cost over the following twelve months if nothing changes. The annual figure is an annual figure, not a one-off, and we say so on the page.
What we do not send
The raw data file, and anything about how we work. If you want the underlying JSON for your own records, ask and we will send it. It is not the point of the exercise.
Honest limits
What a review cannot see.
Some things are simply not readable, and we would rather tell you than produce a confident number built on a file we could not open.
-
Scanned invoices
Listed as a scan, not as an empty file.
-
Encrypted PDFs
Listed as unreadable, with the reason.
-
Legacy .xls
Ask for a CSV or XLSX export instead.
-
A single invoice
Duplicates are visible. Gaps are not.
Send us a month and see your own.
The first look is free. You get this same page back with your invoices in it, and nothing is committed to by either of us.