Corporate payables · Specified
The decision: Pay the invoice, or change the bank details
A routine payables run with one bank-detail change request attached. This is the fastest examination in the platform and the one with the shortest window: the money leaves on Thursday.
There is no production tenant and no paying customer. Every document, finding and verdict on this page is synthetic, written to show what the forensic core examines and what a cited verdict looks like. No accuracy or detection figure appears here, because no pilot has produced one under a methodology we would publish beside it. The rule set for this sector is specified, not encoded. The forensic findings below run on any document bundle today; the sector rules do not exist yet.
The bundle as it lands, before anybody has read it.
The forensic core runs on every document in the bundle regardless of sector. None of these questions changes when the industry changes.
Every finding carries at least two anchors drawn from at least two separate documents, and the benign explanation that would account for it. A pattern appearing once in one place is not reported at all.
The domain differs from the supplier’s established domain by one transposed character. Sender policy and signature checks both fail on the requesting message, and pass on all six prior messages in the same thread.
The benign explanation: A supplier genuinely migrating to a new domain will fail exactly these checks during the transition, which is why the finding is a referral and not a block.
Logo raster, margin geometry and the footer registration line all differ from the forty invoices this supplier has issued since 2021.
The benign explanation: Rebrands happen, and a finance team may produce correspondence on a template the invoicing system does not use.
The account name on the request resolves to no registered entity matching the supplier of record, its group, or any registered business name associated with either.
The benign explanation: Payments are legitimately directed to factoring companies, trustees and group treasury entities whose names look nothing like the supplier.
Three findings, each anchored twice, on a request that would otherwise have been actioned by a person under time pressure. The payment is not blocked by the platform. It is held for a call to a number already on file, which is the control that actually works.
This is the shortest path to value of any sector on this list, because the examination takes seconds, the bundle is small, and the loss it prevents is immediate and quantifiable.
The same four constraints apply in every sector, and they are enforced in code rather than in policy.
Nothing was declined, refused, held or approved by the platform. A person decides, on the record, with the reasoning in front of them.
Every sector
No risk number, no ranking, no composite figure. The only number attached to a person is how many independent documents corroborate a fact about them.
Nowhere in the product
Two anchors from two documents, or the finding is not reported. This is the largest source of false positives in the category and the platform refuses to generate them.
Enforced at registration
A detector referencing a protected attribute fails registration and the platform will not start. It is a structural guarantee rather than a policy.
Throws on load
Hand us two hundred closed files. Settled claims, funded loans, granted applications, paid invoices, onboarded accounts. We examine them and show you the documents that lied, against outcomes you already know. It is the only honest way to evaluate this category, and it is the same motion in every sector on this page.
Only insurance is built. Every other sector is specified rather than shipped: the forensic core runs on any bundle today, and no rule set outside insurance has been encoded. [email protected]