Settlement cycle: ↓ 55%
Weight certificates, quality certs and the contract terms are read together rather than chased one at a time, and the statement goes out while the paperwork is still current.
Confirmation, settlement, demurrage, quality claims – WIQ learns each process from your GAFTA and FOSFA terms, your CTRM, and your spreadsheets, then ships it as a production agent your desk runs.
What would you like to do?
A commodity and agriculture trading operation runs far more than the desk you see. Behind every trade sits confirmation, settlement, contract reconciliation, demurrage, and quality claims – and all of it threads through scattered terrain. The terms come from GAFTA and FOSFA contracts. The back-and-forth runs over email with counterparties, brokers, and inspectors. The work itself moves through tools in the browser, like a CTRM such as Agiblocks and the bank portals, and on the desktop, like Excel and Outlook, alongside a steady stream of SGS inspection PDFs.
Most of it is repetitive: matching a weight certificate to a contract, applying a moisture discount from the quality cert, reconciling a confirmation that's off by a rounding. The cases that need a person – a cargo rejected on spec, documents that don't line up with a letter of credit – are fewer, and that's where the desk's judgment earns its keep.
There are vertical agents built for this world, like ClearDox and ClearOpx, but they live inside the trade lifecycle and tend to cover one slice of it. None runs the whole of settlement alongside confirmations and claims, let alone the processes sitting over in finance or compliance.
For a week or two, WIQ quietly records how Priya and Tomáš actually run settlement – every action across Agiblocks, essDOCS / CargoDocs, Microsoft Excel, Veson IMOS and Microsoft Outlook, and the rest of the stack – with no tagging and no configuration. It learns the real sequence of steps, the handoffs between people, and the judgment calls they make along the way.
Open settlement queuePriya · Agiblocks59s
Open trade CG-SOY-2231 flagged ready-to-settlePriya · Agiblocks1m 26s
Download SGS quality and weight certificate SGS-CN-88213Priya · essDOCS / CargoDocs1m 38s
Calculate demurrage 1.8 days at $18,500/dayPriya · Veson IMOS1m 41s
Review protein shortfall on CG-WHT-2188Tomáš · Agiblocks1m 6s
Approve $4.20/MT protein allowanceTomáš · Agiblocks33s
Resume settlement for CG-WHT-2188Priya · Agiblocks53s+ 30 more events in this run
From dozens of real runs, WIQ writes a Blueprint – a precise, executable description of the process. It captures the steps in order, the tools and connectors each one needs, the points where work escalates to a person, and the guardrails the agent must never cross. Nobody writes it by hand; it’s derived entirely from how the work already happens.


Agiblocks (CTRM)Poll Agiblocks for ready-to-settle trades and open a case per trade.
Agiblocks (CTRM)Pull the bill of lading, weight cert, and SGS quality cert from CargoDocs and fetch the contract.
Compare loaded weight to contract quantity within the franchise allowance.
Read moisture, oil, protein, and FFA from the cert and apply the contract's premium / discount schedule.
Agiblocks (CTRM)Apply the pricing basis (futures + basis) and FX, and reconcile to the provisional value.
Veson IMOSRun laytime in Veson IMOS for demurrage or dispatch, and add freight per the Incoterm.
Combine quantity, quality, price, freight, and demurrage into a settlement statement.
Email the statement and resolve any differences within tolerance.
Agiblocks (CTRM)On the L/C document check and counterparty confirmation, post the invoice in S/4HANA (human-approved).
A person signs off before this step completes.
Prepare the payment instruction; the agent never releases funds – Treasury releases on value date.
A person signs off before this step completes.
Required tools and integrations.

Trade capture, position, settle trigger
Invoicing & GL postings

Electronic shipping & trade docs
Quality & weight certificates

Laytime & demurrage calculation
Counterparty reconciliation
Payment initiation (release is human)
What happens when automation can't or shouldn't proceed on its own.
Inspection results outside contract spec halt pricing and route to the trader / contract manager for an allowance, claim, or rejection.
If shipping documents don't match the L/C terms, escalate to trade finance before the bank rejects presentation.
If final figures don't agree with the counterparty and can't be resolved within SLA, route to the desk / credit / finance.
Hard limits the automation must not cross.
Never price a cargo with any quality parameter outside the contract's reject band – halt and escalate.
Never present documents under an L/C with an unresolved discrepancy.
Invoice posting always requires human approval.
The agent never releases funds – payment is routed to Treasury for release.
A Blueprint isn’t locked to WIQ. Deploy it as an agent to the platform your team already uses – Claude, Microsoft Copilot, OpenAI, or your own stack – and it runs there with the same steps, connectors, escalation paths, and guardrails intact.
A new trade is confirmed against the broker note and counterparty: economic terms matched, the contract issued under the right GAFTA / FOSFA form, and any discrepancy flagged before it reaches settlement.
A laytime statement becomes an agreed demurrage or dispatch claim: time facts reconciled against the charter party, the claim calculated and supported with documents, and the figure negotiated to settlement.
Weight certificates, quality certs and the contract terms are read together rather than chased one at a time, and the statement goes out while the paperwork is still current.
Laytime is worked out from the statement of facts as soon as it lands, so a claim is raised inside the window rather than after it, with the calculation attached for the counterparty to check.
WIQ is built for enterprises that take data privacy seriously. Everything runs within a security framework designed for regulated industries.
Allowlist and blocklist by app, domain, and time window. Nothing outside the policy is ever recorded.
Scope the tools each Agent can reach and the actions it can take. Set the approval gates and escalation paths before it runs.
Every run is checked against the approved blueprint. Deviations are flagged and exceptions route to the right person.
Run locally where the work happens or inside your own cloud. The work never has to leave your environment.
Schedule a discovery session with an AI architect.
Book a demo