Banking and trade finance · Specified
The decision: Advance or hold
A receivables financing request against a schedule of eleven invoices with the shipping documents behind them. Receivables financing rests entirely on documents nobody forensically examines, and the failures are large and public.
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 same supplier, the same buyer, the same invoice numbers and the same amounts, submitted against a facility with a different financier four days earlier. Either the receivable has been assigned twice or one submission is in error.
The benign explanation: A withdrawn or declined earlier request being resubmitted elsewhere is ordinary and legitimate, and a duplicate index cannot see whether the first was cancelled.
The receivables schedule totals more than the sum of the eleven invoices attached. The difference corresponds closely to two invoices referenced in the schedule but not present in the bundle.
The benign explanation: Documents go missing from a submission constantly, and a schedule prepared before the pack was assembled will routinely reference items that were dropped.
The document’s last modification timestamp postdates the issue date printed on its face by three weeks, and the quantity field sits in a content stream added after the original.
The benign explanation: Corrections and amendments to shipping documents are routine and are frequently made by editing the original rather than reissuing it.
A double-assignment indication, a reconciliation gap and a post-dated amendment, each anchored twice. The advance is not refused by the platform. It is held for a person with the three specific questions to put to the borrower.
The duplicate-financing finding is only available to an examination that spans institutions. Inside one lender’s own book, the second submission is invisible by construction.
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]