The audit pipeline a 10–100 person consultancy actually needs.

The same SaaS or consulting vendor appears as two distinct vendor IDs because one was opened under the previous engagement's AP setup and a fresh one is opened under the new project's cost centre. PODetect's vendor-master dictionary matches on remit-to, tax ID, and bank fingerprint, pauses the duplicate the day it lands, and surfaces the canonical master record on the morning digest so the second vendor is never the one your controller approves.

Consultancy billings go out against client-issued POs — project codes, retainer top-ups, change orders. A scope drift, a quantity short, or an amount that no longer matches the PO the client signed is caught before the line posts: the audit pauses the billing, the morning digest lists the PO, the rule, the client, and the drift. The reviewer resolves it in under a minute and the engagement keeps its margin intact — not a 30-day clawback.

The same SaaS vendor team bought twice over the project's lifetime, under two engagement codes, both billed monthly. The duplicate guard collapses them into a single vendor record and frees the second monthly seat before the next renewal cycle. On thin consultancy margins, a recurring double-charge is months of unbilled headroom gone — and the rule that closes it is the same one that runs against a duplicate lab invoice on the clinics page.

The same five-rule audit — PO match, vendor drift, duplicate pay, split-allocation, sales-tax anomalies — fires per line at ingest. Approve the morning digest and the clean posts go through; a busy reviewer resolves the flagged lines in a single quiet review. There is no new audit pass to schedule and no spreadsheet to hand to a junior at quarter-end — the trail is what the audit writes by default.