Screened on every validation

Screen against 330+ global watchlists — on every validation

OFAC sanctions carry strict liability. Transacting with a sanctioned party — even unknowingly — creates penalty exposure that can dwarf the value of the transaction. TIN Comply screens every vendor, payee, customer, and partner against more than 330 global sanctions and watchlists, returns the official list data from the publishing organization, and logs every result with a timestamp.

Runs automatically alongside IRS TIN matching. One call, complete result.

List / Sanctions Screening Results Matches Found
Sanctions matches require immediate review before proceeding Do not process payments or onboard this vendor until compliance review is complete.
Sanctioned Entity Person Of Interest Debarred Entity Export Controlled
Sanctions & asset freezes2
US OFAC Specially Designated Nationals (SDN) List
Ukraine War and Sanctions
Export & trade controls2
US Trade Consolidated Screening List (CSL)
Taiwan Strategic High-Tech Commodities Entity List
Debarment & exclusion1
US SAM Procurement Exclusions
Lists screened Review required
OFAC SDN + 330 more
Fuzzy matching & aliases
Threshold you control
Audit-ready results
Included

Part of every TIN Comply plan from $20/mo — not a separate purchase. See pricing

The structural problem

Screening can't be a separate step someone remembers to do

Most organizations screen at vendor onboarding and assume that covers it. Two things break that assumption.

First, sanctions lists update continuously — a vendor who was clear at onboarding can be designated six months later while still sitting active in your payment system. Second, onboarding screening is rarely consistent across a vendor population built up over years, so a meaningful share of active vendors may never have been screened at all.

TIN Comply embeds screening into the same call as IRS TIN matching. Every validation — at onboarding, on correction, in a bulk pre-filing pass — screens simultaneously. The result is a screening record for every vendor, not just the ones someone remembered to check.

Strict liability, in plain terms

OFAC sanctions don't require intent. A payment to a sanctioned entity creates exposure regardless of whether the payer knew — "we didn't realize" is not a defense.

Civil penalties under IEEPA can reach hundreds of thousands of dollars per violation, or twice the transaction value, with criminal exposure for willful violations. Documentation that screening was performed, and when, is the foundation of any enforcement response.

Penalty maximums are adjusted for inflation. Confirm current figures with OFAC before relying on a specific number.

What you're exposed to

Four ways unscreened counterparties become your problem

Regulatory violations

Intent is not a defense. A payment to a sanctioned entity creates exposure regardless of what the payer knew or intended.

Civil & criminal penalties

Civil penalties run into the hundreds of thousands per violation, with criminal exposure for willful conduct — and no annual cap.

Onboarding risk

A sanctioned vendor added to AP without screening may receive payments for months before anyone checks. Onboarding is the only point where it's cheaply preventable.

Hidden counterparties

Sanctioned parties use aliases, transliterations, and ownership structures built to avoid detection. Exact-match screening misses them by design.

Not all exposure is the same

The lists that matter depend on what you pay for

Sanctions screening is the part everyone recognises, but for most industries the list that actually stops a payment is somewhere else entirely.

Financial services

Every counterparty onboarded is OFAC exposure, and politically exposed persons bring enhanced due diligence obligations on top. Sanctions and asset freezes plus PEP lists are the two that carry the weight here.

Healthcare

Paying an excluded provider from a federally funded program creates liability whether or not you knew. HHS OIG exclusions, state Medicaid termination lists and state medical boards matter more here than OFAC does — and they expect screening every month, not once at onboarding.

Government contracting

Debarment travels down the chain. SAM procurement exclusions and the development bank debarment lists decide whether a subcontractor can be paid on a federally funded award at all.

Logistics & supply chain

Export and trade controls sit alongside sanctions: BIS Denied Persons, the UFLPA Entity List, CBP withhold release orders. Maritime operators also draw on port state control detention records, which are an operating history rather than a prohibition.

Gaming

State gaming boards publish the people barred from licensed establishments, typically for criminal convictions or conduct a regulator judged a threat to the integrity of gaming. Dealing with someone on one of those lists is a licensing problem before it is anything else.

Marketplaces & retail

Exposure arrives through sellers, suppliers and affiliates rather than through obvious financial relationships, and rarely under the name you are looking for. Fuzzy matching across aliases and transliterations is what finds it.

Every result says which list it came from, what kind of list that is, and what appearing on it means — so a hit on a company registry never reads like a hit on a sanctions list.

Screening workflow

From "who am I paying" to a documented answer

1

Select who to screen

Vendors, payees, customers, or partners — individually in the portal, in bulk from an uploaded file, or automatically via API on every onboarding or validation event.

2

Choose list scope

Run global screening across all lists, or narrow by region or list type. Industry-specific coverage — gaming, healthcare, financial services — is available for regulated workflows.

3

Screen with fuzzy matching

Screening covers known aliases, transliterations, and alternate names — catching the matches that exact-string screening misses.

4

Review potential matches

Results carry the list source and official list detail, with risk categories flagged, so compliance can triage quickly. Clear results — not a hit/no-hit binary.

5

Escalate on policy

Potential matches are flagged for review and escalation based on your internal policy, with the match percentage shown so the decision is evidence-based.

6

Log for audit

Every result is logged per record with a timestamp — list source, result detail, screening date — retained automatically. The enforcement-defense documentation exists before it's needed.

Coverage & control

Broad lists are table stakes. Control over them isn't.

330+ global lists

OFAC SDN and Consolidated, US Trade CSL, SAM Procurement Exclusions, FinCEN advisories, BIS Denied Persons and Entity List, EU Consolidated, UN Security Council, and national programs across Europe, Asia, Africa, the Americas, and Oceania — all in a single screening call.

A match threshold you set

Choose the minimum name-match percentage that flags a potential match — anywhere from 50% to 95% — and select exactly which lists apply to your company account. Deselecting a list excludes it from all future checks. False positives are a tuning problem, not a fixed vendor default.

Industry-specific coverage

Specialty lists for gaming, healthcare, insurance, and financial services — covering excluded providers, debarred parties, and regulated-industry watchlists alongside standard sanctions, including state gaming commissions and medical exclusion lists.

Included on every TIN validation

Screening runs automatically alongside every IRS TIN matching call — no separate workflow, no extra step, no additional fee, and no vendors that slip through because someone forgot to run it.

What a match actually gives you

Enough detail to clear it — or escalate it — without leaving the screen

A hit that just says "possible match" hands the work back to you. Every TIN Comply result carries the match percentage, the risk categories, the specific lists, and the identifying detail the publishing organization provides.

  • Match percentage per result See exactly how close the match is, so a 100% hit and a 72% near-miss get different treatment.
  • Risk categories Sanctioned Entity, Person of Interest, Debarred Entity, Export Controlled, Trade Risk — or Exempt, where that applies.
  • Every list that hit, named Not "a watchlist" — the specific publishing lists, so you know which regime applies.
  • Names, aliases, and identity detail Addresses, country, sector, registration and program identifiers where the list provides them — the detail that separates a real match from a name collision.
  • A timestamped record Written to your searchable history with the user who ran it — which is what makes it evidence rather than a screenshot.
Match detail 80% match
Debarred Entity
Address

1420 Harbor Point Rd
Wilmington, DE 19801

Country

United States

Sector

Entity / Corporation

Registration

1063775895

US SAM Procurement Exclusions
Health and Human Services Inspector General Exclusions
Official list data from the publishing organization Review required
FAQ

Questions compliance teams ask

What is OFAC screening?

Checking a person or business against sanctions lists maintained by the US Treasury's Office of Foreign Assets Control — most importantly the Specially Designated Nationals and Blocked Persons (SDN) list.

Because OFAC sanctions carry strict liability, a payment to a sanctioned party creates exposure whether or not you knew. That's why screening before payment is the only control that actually works.

Who is required to do OFAC screening?

All US persons and businesses — not just banks. Any organization that pays vendors, onboards suppliers, or transacts with international counterparties is subject. There's no small-business exemption and no materiality threshold below which it stops applying.

Is screening at onboarding enough?

No — for two separate reasons. Lists update continuously, so a vendor clear at onboarding can be designated later while still active in your payment system. And onboarding screening is rarely consistent across a vendor population built over years, so some active vendors may never have been screened at all.

Periodic re-screening of the full active population is what closes both gaps.

Why does exact-match screening miss sanctioned parties?

Because sanctioned parties use aliases, transliterated spellings, and alternate corporate names — often structured deliberately to avoid detection. Exact string matching misses all of it. Fuzzy matching and alias detection aren't a nicety here; they're the difference between screening and the appearance of screening.

How do I reduce false positives?

Tune the threshold to your risk appetite instead of accepting a vendor default. TIN Comply lets you set the minimum name-match percentage anywhere from 50% to 95%, and choose exactly which lists apply to your account.

Every result shows its own match percentage, so you can see where your line currently falls and move it deliberately rather than by guesswork.

What lists does TIN Comply screen against?

More than 330, spanning the US, Europe, Asia, Africa, the Americas, and Oceania. Coverage includes OFAC SDN and Consolidated, US Trade CSL, SAM Procurement Exclusions, FinCEN, BIS Denied Persons and Entity List, EU Consolidated, and UN Security Council — plus industry-specific lists for gaming, healthcare, insurance, and financial services.

What should I do when a screening returns a match?

Stop before the payment. Don't process payments or onboard the vendor until compliance review is complete. Review the list source and official detail — aliases, addresses, identifiers, program codes — then escalate per your internal policy.

Every result is logged with a timestamp, so the review itself becomes part of the record.

Screen against 330+ lists in minutes

Run screening through the portal, bulk files, or API — automatically alongside IRS TIN matching on every validation, with official list results and a timestamped audit trail on every record.

No separate workflow. No add-on fee.