Full reasoning chain
Every conclusion carries its reasoning and a citation to the source document, with agent actions and human overrides recorded in sequence.
Solution · Trade-Based Money Laundering
The hardest files in the book.
A trade finance case is documents in several languages, prices that have to be tested against something, routes that have to make sense, and a chain of counterparties who all have to be screened. It is the case type that most defeats automation.
ScopeEvidenceFinding
The work
What the file
actually takes.
Most of a TBML investigation is assembly: reading the document set, pulling out the values that matter, and finding something to compare them against. That is the part RiskPulse takes.
01
Document set
Invoices, bills of lading, packing lists and contracts are read across formats and languages, with each field cited to its source page.
02
Consistency
Values, quantities, descriptions and parties are tested for agreement across the document set.
03
Pricing
Unit prices are tested against benchmarks to identify over- and under-invoicing outside expected ranges.
04
Route and vessel
Shipping routes, vessel details and transhipment points are checked for consistency with the stated trade.
05
Counterparties
Every party in the chain — not only the customer — is screened and resolved.
Where the agents run
Plan. Examine. Report.
The same three agents run this case type as run every other. What differs is the policy behind them — the plan template, the dimensions scored, the tools available, and the report that comes out.
Pricing tested against something, not eyeballed.
The central question in a trade case is whether the price is plausible. RiskPulse tests unit values against benchmark ranges for the commodity, route and period, and puts the comparison in the file — so the conclusion rests on a stated basis rather than an analyst's recollection of what a reasonable price looks like.
- Multi-language extraction — document sets read across the languages trade actually arrives in
- Cross-document consistency — the same shipment described the same way in every document, or the discrepancy surfaced
- Dual-use and route screening — goods descriptions and shipping routes checked against control and sanctions exposure
- Full chain screening — every counterparty and intermediary in the transaction, resolved and screened
Product screenshotCase record
Placeholder — case record
Policy for this case type
Configured,
not hardcoded.
Nothing on this page is fixed in the product. Every element below is a policy setting you define, which is why the same platform runs this case type and the four others.
- Domain
- Trade finance — with its own document requirements, commodity categories and benchmark sources.
- Risk dimensions
- Party, pricing, route, documentation and jurisdiction risk — weighted to your trade policy.
- Plan template
- Trade type and product drive which documents are required and which tests must run.
- Tool access
- Benchmark, vessel, registry and screening sources, scoped to the case type.
Controls
Defensible
after the fact.
The same governance and quality controls apply to this case type as to every other — because an examiner does not lower the standard for the harder files.
Quality control
Sampling built in
A sampling methodology sits behind this case type, so your quality team can assess a representative sample rather than reviewing at random.
Quality assurance
Independent assessment
A separate set of agents assesses case quality end to end against your methodology — a second opinion on the work.
See it on your own file
Bring a case.
We will run it.
Pick a real file or a closed case and see how RiskPulse plans it, evidences it, and writes it up under your policy.
Request a Demo