B2B workflow sample
TrustField B2B Payment Evidence Review
Run a synthetic case, inspect the tasks, forms, decisions and evidence, then download the generated workflow as a file your engineering team can review before anything goes live.
Try the sample case
Synthetic data only — editable in your browser. Nothing is uploaded or filed. Editable summaries only — no real upload. Do not enter real bank details, account numbers, or confidential customer information.
TrustField B2B Payment Evidence Review
Eight-stage reusable engine: intake → document collection → three-way matching → beneficiary / third-party → source-of-funds sufficiency → sanctions / trade-control referral → CRO decision → optional STR handoff. TrustField may perform document intake, extraction, case creation, matching, validation, exception routing, drafting, human approval, and evidence pack assembly. It does not hold funds, initiate, authorize, or transmit payment, settle, or make the final regulatory decision.
Source-linked matching
Three-way and beneficiary maps keep page/clause citations and confidence — not a payment rail.
Human-controlled stages
Eight explicit stages prepare the file; the compliance officer records Approve / Return / Escalate / STR / Reject.
Upstream of CRO → FINTRAC
Open STR assessment hands off to the live CRO → FINTRAC sample. This workflow does not replace filing judgment.
Synthetic case
Edit browser-local summaries, apply, then walk the eight stages. No files leave this browser.
AI-ASSISTED · HUMAN-APPROVED
Cascade Imports Ltd. → Nordic Equipment BV
B2B payment evidence review · USD 150,000 requested · 8 stages
Workflow stage 1 of 8
B2B payment request enters evidence review
Synthetic invoice, agreement, delivery, bank instructions, and one SoF evidence item become one review case. Nothing is uploaded or filed.
Synthetic document pack
1. Payment Request
USD 150,000 to Asia Treasury Services Ltd.
2. Commercial Invoice
INV-88421 · Nordic Equipment BV · USD 150,000
3. Purchase Order / Agreement
PO- Cascade/NE-17 · Milestone 50% at signing / 50% after shipment
4. Bill of Lading / Proof of Delivery
Not provided in sample pack
5. Beneficiary Bank Instructions
Asia Treasury Services Ltd. · USD correspondent instructions
6. Source-of-funds evidence (Bank Statement)
Operating revenue claimed · statement covers operating account only
Evidence kernel
Shared on every stage- Source document
- Payment Request
- Page / clause
- p.1 · request header
- Extracted value
- USD 150,000 · B2B-PER-2026-0412
- Confidence
- 0.96
- Rule / result
- Case opened for evidence review only
- Exception
- —
- Owner
- —
- Human decision
- Pending human gate
- Rationale
- —
- Timestamp
- 2026-07-23T15:40:00Z
- Version
- evidence-pack-v2-eight-stage
- Final evidence
- Draft — awaiting CRO decision
Workflow output
Sample · review requiredCase opened for evidence review only — no payment initiation, authorization, transmission, or settlement.
Probable manual path today
Payment request → scattered PDFs → spreadsheet match → email exceptions → undocumented CO decision
Configured TrustField workflow
Intake → document collection → three-way matching → beneficiary map → SoF sufficiency → sanctions referral → CRO decision → optional STR handoff
Agent Execution Assurance
Your engineers review the workflow before it goes live
The agent builds the workflow and hands you the specification as a file. Your engineering and compliance teams read it, mark it up, and sign it off. Nothing touches a production system, a customer record, or a regulator until they do.
Step 1
The agent generates it
Stages, field mappings, validation rules, decision gates, and evidence events are produced from your scenario.
Step 2
You take the file
Download the full specification as JSON. It is inert: reading it, storing it, and diffing it changes nothing.
Step 3
Your team approves it
Your named reviewer records a decision in the signoff block and returns the file. Only then does TrustField configure it.
Who is reviewing it?
Optional. The download works without any of this.
Fill this in and the file is made out to your organization, with your reviewer named in the signoff block, so it arrives ready to circulate internally.
Status in the file: inactive. It cannot activate itself.
What your reviewers should check
- – Every source system listed, and whether the stated role for each is correct
- – Field mappings against your own field names and formats
- – Validation rules against your internal policy, not just the regulatory minimum
- – Whether each human decision gate sits with the role that actually holds that authority
- – Whether the evidence events satisfy your retention and audit requirements
- – Whether the boundaries match what your compliance function expects of an automated system
The file states what the system does and what it will not do, including that it does not make the filing decision and does not submit to a regulator without an authorized officer of your organization.
Choose one launch path. You do not pay CAD 4,900 plus CAD 8,500. Workflow Confirmation is optional.
Optional — if scope is unclear
Confirm the scope
CAD 900
No production deployment.
Fully credited toward a qualifying Controlled Launch within 30 days.
Choose one launch path
TrustField performs the implementation. You confirm data, roles, decisions, and access.
Recommended
Controlled Launch
CAD 4,900 total
One working workflow using CSV, secure file, structured form, manual intake, or another simple data source.
60 days Launch Care included.
Connected Launch
Connect to your live systems
From CAD 8,500 total
The working workflow plus one live API, webhook, database, SFTP, or application integration, automated case creation, retry/recovery, and status synchronization.
After go-live
Both production launch paths include 60 days of Launch Care. Continued hosting, monitoring, and support are optional afterward under Managed Care from CAD 750/month.
Already launched with TrustField? Live integration is quoted as incremental scope. Reusable workflow work is reflected in the SOW.
Boundaries
Public workflow sample by TrustField. LLM-assisted extraction with source-linked evidence, confidence thresholds, and deterministic workflow gates — not “fully deterministic AI.” This sample does not auto-file, move money, authenticate documents, clear sanctions, prove source-of-funds legitimacy, or replace regulatory judgment. Reporting entities remain responsible for final decisions.