Third country duty
European Union · TARIC measure
Duty expression and regulation reference are shown together.
Sample report
What a reviewer sees after a check.
The real report is generated from a selected CN/TARIC code, ISO 20022 payment message, country context, date, language, TARIC measures, sanctions signals, participant evidence, footnotes, and source links. This sample uses illustrative content so no customer data is exposed.
Sample compliance report
CN 8504 40 30 · EU trade and regulatory review
Illustrative report layout for a TARIC and sanctions review. No customer data is shown.
Classification path
Chapter 85 > Heading 8504 > CN 85044030
Measures
Duty, conditions, certificate notes, validity dates
Entity screening
Legal persons, natural persons, banks, vessels, and aircraft
Sources
TARIC, EUR-Lex, EU FSF, OFAC SDN/Non-SDN, UN, UK, CH, US CSL, Canada, Australia, Ukraine, Japan, LV FID, and GLEIF context
12
TARIC rows
3
Key signals
7 days
Report link TTL
Duty and conditions
Reviewers see the duty expression, regulation reference, condition text, and certificate notes together.
Source verification
The generated report keeps official source references visible instead of hiding them in raw data.
Workspace history
The check can be saved to organization history so another reviewer can follow the same evidence trail.
ISO 20022 payment report
Payment evidence is visible before anyone logs in.
The public sample now shows the payment report shape too: message version, XML validation, BIC/GLEIF enrichment, participant screening, warnings, and reviewer-ready outputs.
pain.001 and pacs.008 messages become saved payment cases, not temporary parsing results.
Participants are linked to BIC, LEI, name, country, warnings, and screening status.
The report separates integrity warnings, participant hits, close matches, and reviewer decisions.
ISO 20022 payment case
pain.001 / pacs.008 screening with evidence
The case keeps the raw XML, message version, payment chain, participant screening, BIC/GLEIF context, and report outputs together.
Message
pacs.008.001.12 · 2 transactions
Validation
XSD and integrity warnings recorded
Participants
Debtor, creditor, agents, BIC and LEI context
Reports
Case summary, ISO 20022 payment PDF, evidence HTML
4
participants
2
transactions
payment report
Payment chain evidence
1
Debtor
Nordic Components AS
LEI 5493001KJTIIGC8Y1R12
2
Debtor agent
EXAMPLEBANKXXX
BIC resolved · GLEIF checked
3
Creditor agent
TARGETBANKXXX
BIC resolved · sanctions screened
4
Creditor
Baltic Systems OÜ
Name screened · VoP signal
BIC waterfall
Local cache, GLEIF, configured resolver evidence
Review signal
Hits, close matches, warnings, and reviewer action
Report detail
The sample shows how evidence is grouped for a reviewer.
Report summary
Illustrative example
Goods code85044030
ScenarioEU trade and regulatory review
Country contextRU/BY sanctions check included
LanguageEnglish
StatusReview required if a matching restriction applies
The report is evidence support, not a final legal decision. Critical trade and regulatory decisions should be reviewed by qualified customs, legal, or trade compliance professionals and verified against official sources or competent authorities.
Measures and signals
Grouped for review, not scattered across raw rows.
Regulatory control / condition
European Union · TARIC condition
Certificates, footnotes, and validity dates are grouped under the measure.
Sanctions signal
RU/BY scenario · EUR-Lex legal source
Direct matches and group-level matches are separated for review.
Entity screening example
A report can show why a listed-name result needs review.
Entity screening is saved with the same evidence discipline as goods checks: query, type, threshold, list source, date, match score, aliases, and reviewer outcome.
Saved entity case
Illustrative content; no customer data.
SubjectExample Bank Group
Entity typeLegal person / bank
List sourceEU FSF, OFAC SDN/Non-SDN, UN SC, UK, CH, US CSL, CA, AU, UA, JP
Threshold75% fuzzy score
StatusReviewer required
Match evidence
Scores support review; they do not confirm identity by themselves.
Matched name and aliases
Top score 100% · legal person
The report keeps the searched name, matched listed name, aliases, transliterations, and source list visible for human review.
Source and dates
Listed date · regulation/source reference
Reviewer can see where the list record came from and whether the result should be verified against the official source.
Reviewer outcome
Accepted by user · timestamp
The case can be accepted or reopened, preserving who reviewed the result and when.
Hierarchy, selected code, and descriptions stay together.
Footnotes and certificates remain visible near the measure.
Reports keep source links so reviewers can verify the legal basis.