How to use TradeGuard

TradeGuard is a public, rule-based review-support workspace. It helps an authorised reviewer organise information and identify potential risk indicators; it does not make a final compliance decision.

Public guide

1. Choose the right workspace

• TBML Check: use for a trade-level review involving goods, HS Code, price, parties, routes, payments and documents.
• Transaction Monitoring: use for emerging behavioural patterns such as unusual velocity, value shifts, new counterparties, rapid funds flow, corridor changes or channel changes.

2. TBML Check workflow

1. Enter the HS Code, origin and destination country.
2. Add price, quantity, unit, parties, route, document and payment information where available.
3. Select only the red-flag indicators supported by the available evidence.
4. Review the score, data completeness, data integrity, evidence requirements and suggested next step.
5. Use Copy summary, Print / Save PDF or Download TXT to retain the indicative review note.

3. Transaction Monitoring workflow

1. Select the monitoring period: 7, 30, 90, 180 or 365 days.
2. Choose the customer segment, profession and appropriate baseline window.
3. Enter the expected and observed transaction count/value where reliable baseline information exists.
4. Select only supported patterns and provide details for flow, counterparty, route or channel changes.
5. Review the configured score, evidence-supported score, unverified contribution, risk type and required human review.

4. PDF review

• Use fictional, synthetic or anonymised PDFs only.
• Full-statement mode can pre-fill available context. Transaction-history-only mode is suitable when names, account numbers and bank details have been removed; context can be entered manually.
• Up to five PDF files may be selected together. Each file can be up to 10 MB, with a combined limit of 40 MB.
• PDF text is extracted locally in the browser and is not sent to a TradeGuard server.
• The public build extracts selectable text. Scanned/image-only PDFs may not produce usable text because OCR is not included in this public build.

5. How to interpret the output

• Risk signal: the configured prioritisation score; it is not a probability or legal conclusion.
• Evidence-supported: the portion supported by the details supplied in the review.
• Unverified: selected patterns that still require supporting evidence.
• Risk type / typology lens: the broad review category, such as valuation, counterparty, funds-flow, geographic, channel, document or customer-profile risk. Any typology mapping is indicative and is not a FATF determination or proof of wrongdoing.
• Human review required: the responsible officer must validate evidence and determine the appropriate next action.

6. Document Assessment workflow

1. Open Document Assessment and choose KYC/AOF, trade, loan/credit, financial statement or collateral/security review.
2. Select up to five local PDF or image files and confirm that they are fictional or anonymised.
3. The browser extracts selectable text and uses OCR for scanned pages or images when needed.
4. Review the document-quality, completeness and inconsistency flags against the original documents.
5. Use Copy summary, Print / Save PDF or Download TXT to retain the indicative note.

7. Current scope and roadmap

The public build does not perform live sanctions or PEP screening, core-banking integration, saved-case management or server-side audit logging. The new Document Assessment workspace provides browser-local selectable-text extraction and optional OCR-assisted checks for document completeness and inconsistency; it remains an indicative review aid.

Further institutional modules may extend the public document workspace with governed OCR language packs, structured document taxonomies, field-level reconciliation, approved data processing, access controls and human review.

Institutional document-controls roadmap

1. 0–3 months — refinement and prototype governance: define document taxonomies, OCR/PDF extraction, confidence scoring, PII handling and retention controls.
2. 3–6 months — controlled pilot: test KYC/AOF and loan/credit-document checks with reviewer workflows, false-positive testing and exception handling.
3. 6–12 months — institutional readiness: add access controls, audit logging, model/rule governance, retention controls and a scoped pilot with approved institutions.

Timing is indicative only and depends on approved data governance, security review, representative documents and institutional or regulatory approval. OCR is best-effort and optional in this public build; verify every result against the original document.

8. Privacy and safe use

Do not upload real bank statements, customer records, identity documents, LC files, payment messages or confidential trade documents to this public demo. Read the Privacy and PDF handling page before testing.