What happens when you email
us your invoices.
A long-form walk-through of a LEGERIS engagement — from the moment your invoices land in our intake to the moment you receive the forensic report. Three acts: Ingest. Verify. Deliver.
ACT I
Ingest.
The invoices arrive. We make them legible.
A client engagement starts with an email. Invoices land in our intake — PDFs, scans, image-only documents. Some are clean digital exports. Some are photographs of fax-machine outputs. We treat both the same way: every page gets routed through a forensic-grade extraction layer that pulls the header, the line items, the totals, the dates, and the supporting metadata into a structured schema.
What separates this stage from a generic OCR tool is the geometry. We do not just read the text — we capture where on the page each field lives. Bounding boxes. Page anchors. Field provenance. Every value carries a visible coordinate so that later, when a finding cites “the rate on line 6, total column,” that citation is a real anchor pointing at a real position on a real document.
The intake stage also classifies. Each document is tagged by shape — a full invoice page, a header-only fragment, a body-only fragment, a summary page from a larger document. The classification matters because audit logic differs by shape. A partial document does not get treated as a full one. Missing fields do not get treated as zero values. The forensic posture starts here.
ACT II
Verify.
Every line cross-checked against contractual truth.
With the document structured and the contract ingested into our knowledge base, the audit proper begins. The hybrid intelligence engine runs two passes simultaneously. One pass is interpretive — language models read the relevant clauses, extract the negotiated terms, and propose potential discrepancies between the invoice and the contract. The other pass is deterministic — purpose-built engines recompute every number, check every arithmetic identity, validate every total against the sum of its parts.
The two passes converge. The language-model pass proposes; the deterministic engines decide. A finding is not surfaced because the model thinks something looks off. A finding is surfaced because the deterministic engine has the math, the contract reference, and the visible evidence in alignment. Anything the model proposes that fails deterministic verification is dropped. Anything the deterministic engine catches independently is added. The result is a set of findings that survives both interpretive and arithmetic scrutiny.
Each surviving finding carries its evidence as it travels through the pipeline. The exact line. The exact value. The exact contract clause. The exact calculation. By the time the finding reaches the report, nothing about it is opaque. The auditor reviewing it sees the proof. The vendor reading the dispute letter sees the proof. There is no black box in the chain between invoice and finding.
ACT III
Deliver.
A forensic report. Ready to forward to the vendor.
The audit completes. The findings are assembled into a deliverable — a PDF report formatted to the standard a Big4 audit firm would produce. A letterhead. A verdict. An executive summary in plain English. The source document with every finding-anchor highlighted as a coloured overlay on the original invoice page. A findings table that ranks each issue by severity. A calculation appendix that shows every numerical claim with the math beneath it. A recommended next step. A footer with the audit hash for non-repudiation.
Every per-invoice report can be forwarded to the vendor as-is. The disputed-email body, embedded in the report, is rendered deterministically from the structured findings — it is not generated by a language model. It says what the findings prove, with the math beside the claims, signed by the LEGERIS forensic team on behalf of the client organisation. The vendor receiving it sees a report that reads like it came from a lawyer’s office, because that is the register the brand commits to.
For multi-invoice engagements, the per-invoice reports compose into an engagement summary — a cover page, an aggregate dashboard, a per-invoice index, the detailed findings of every invoice inline. One PDF that captures the entire engagement. The client receives both: the per-invoice reports for individual disputes and the engagement summary for the partner-facing rollup.
That is what a LEGERIS audit looks like.
The same forensic posture, on every invoice we audit. Predictable. Reproducible. Defensible.
Engagement-based pricing. Reply within 24 hours.