Trade compliance · Add-on

Check every document before the bank does

The compliance add-on reads each shipping document against the letter of credit, the deal and the destination country, and reports what does not match, with the rule it relied on.

  • Reads the letter of credit (MT700)
  • Cites the rule for every finding
  • Sold separately, safe to remove
comet · complianceCompliance findings

How it works

From a presentation to a clear set of findings

The engine reads, checks and reports, and a person publishes before anything blocks.

  1. 01

    Read the credit

    The letter of credit is parsed directly from SWIFT MT700, with fields 46A and 47A compiled into rules.

  2. 02

    Check the documents

    Each shipping document is checked against the credit, the deal and the destination country’s requirements.

  3. 03

    Screen the parties

    Every party, bank and vessel is screened against the EU, UN and OFAC lists.

  4. 04

    Report the findings

    Each finding cites the rule, the law and the page. Nothing blocks a trade until a person publishes it.

Everything at a glance

What the compliance engine checks

The documentary credit, the rulebooks and the sanctions lists.

Letter-of-credit parsing

SWIFT MT700 read directly, with fields 46A and 47A compiled into checkable rules.

UCP 600 and ISBP 821

Documentary-credit rules applied across the presentation, alongside Incoterms 2020 and URC 522.

Per-country corpus

A researched, per-country requirements corpus, where the source is quoted and a person reviews before a rule can block.

Denied-party screening

Every party, bank and vessel screened against the EU consolidated list, UN Security Council and the OFAC SDN list of roughly 77,000 entries.

Reproducible findings

A model extracts and Python judges, so each finding cites the rule, the law and the page it came from.

Nothing blocks until published

An unreadable document is treated as clean, an un-evaluable rule as inconclusive, and only a published rule can hold a trade.

A look at the compliance engine

A checked presentation and a single finding with its citation.

comet · complianceFindings
comet · ruleRule citation

Frequently asked questions

Is the compliance engine part of the core platform?

No. It is a separate add-on, licensed on its own, and it is provably safe to uninstall — nothing else in the system depends on it.

What does it read?

It parses the letter of credit from SWIFT MT700 and checks the shipping documents against it, against the deal, and against the destination country’s requirements.

Can it block a trade automatically?

No. Every finding cites its rule and law, and a person reviews and publishes before any rule can hold a trade. An un-evaluable rule is inconclusive, never a pass.

How large is the sanctions screening?

Parties, banks and vessels are screened against the EU consolidated list, the UN Security Council list and the OFAC SDN list of roughly 77,000 entries.

See Comet on your own trades

Book a walkthrough and we will run it against your deal flow, from the first inquiry to the accounting entry.