Forensic invoice auditing.
The service. The deliverable. The forensic posture.
Section 1
What we audit.
We audit any vendor invoice that has a counterparty, a structured set of line items, and an underlying contractual basis we can verify against. That includes carrier and freight invoices, professional-services time-and-materials invoices, manufacturing raw-materials and indirect-cost invoices, hospitality service invoices, healthcare procurement invoices, and construction subcontractor invoices. We accept invoices in any format — PDF, image, scan, or photograph — and we extract them through a forensic-grade pipeline that captures every value with its geometric anchor on the page.
The contractual basis is the rulebook. Contracts. SOWs. Amendments. Purchase orders. Rate cards. Policy documents. Email approvals where they constitute a binding term. The audit verifies the invoice against this rulebook line by line.
We do not audit invoices in isolation against vague industry norms. Every finding requires a citable basis — a clause, a rate, a contracted term, an arithmetic identity. Without that basis, the finding does not ship.
Section 2
How we audit.
Two passes run in parallel for every invoice. An interpretive pass — large language models read the relevant contract clauses and propose discrepancies. A deterministic pass — purpose-built engines recompute every number, check every arithmetic identity, validate every total against the sum of its parts, cross-validate against the contracted rates and policy thresholds.
The two passes converge. The deterministic engines decide. Findings that survive both passes ship. Findings that fail deterministic verification are dropped, even if the interpretive pass proposed them. Findings the deterministic engines catch independently are added, even if the interpretive pass missed them.
The result is reproducible by design. The same invoice through the same pipeline produces the same findings. The audit hash printed in every report is the SHA-256 of the immutable snapshot — the auditor’s chain-of-custody mark.
Section 3
What you receive.
Per-invoice PDF report.
One PDF for every audited invoice. Contents: letterhead with audit reference; single-word verdict (Approved, Needs Review, Disputed) in the brand accent colour; executive summary in plain English; source document panel with every finding highlighted on the original invoice page; findings table ranked by severity with the principal finding bolded; calculation appendix that prints the math beneath every numerical claim; recommended next step; footer with audit hash, report version, and confidentiality notice.
Engagement summary PDF.
For multi-invoice engagements, one combined PDF containing a cover page, an aggregate dashboard of finding categories, a per-invoice index, and the detailed findings of every invoice inline.
Dispute-ready email body.
The recommended-next-step section of each disputed report contains a polished business letter built deterministically from the structured findings. Forward it to the vendor as-is, or use it as the basis for your team's outbound message.
Ready to engage.
Tell us about the invoices. We will scope the engagement and quote the fee.
Related
Vendor risk benchmarking
Anonymised cross-tenant insight on vendor error rates and overbilling frequency, drawn from audited invoice populations rather than survey data. Scoped per engagement.
Contract verification
Structural and clause-level review of vendor contracts before signing. Flag the terms that read favourable but cost-leak in execution.
Payment terms compliance
Continuous validation that vendor invoices honour the negotiated payment terms — discount windows, late-fee clauses, currency conversion rules.