Sanctions normalization is not sanctions screening

Where does the normalizer stop?

Normalization restructures official list data. Screening compares a customer or transaction using matching, escalation and decision rules.

OFAC format guidance concerns source data. Its compliance framework discusses program components beyond that preparation step.

The normalizer does not identify your customer, investigate a possible match or decide whether a transaction may proceed.

Worked example. An added alias is not a customer match

Fictional example. Two snapshots contain the same official source identifier. The later record adds an alias.

The change report records that addition against the identifier. It does not mean a customer with a similar name is the listed party.

A screening team needs the customer’s identifying facts, relevant list coverage and a matching procedure. It must investigate any potential match.

A zero-change report means no detected change between those inputs. It does not mean “no sanctions risk” or prove either input is current.

Review program, ownership and transaction facts separately. An unchanged list can still contain relevant restrictions.

What normalization does

It parses a supported official schema, preserves identifiers and provenance, standardizes fields and records changes between source versions.

What screening adds

Screening needs subject data, name and identifier matching, thresholds, aliases, false-positive handling, escalation and a decision process.

Keep the boundary visible

Label a normalized file as source preparation. Do not state that a person is clear, matched or sanctioned unless an authorized screening and decision process supports that conclusion.

Working checklist and fictional samples

Use this checklist as an operating aid, not an exhaustive legal assessment. Inspect the samples before entering your own facts.

• Label the output normalized source data, not a cleared customer file.
• Include official source, list family, retrieval time and digest.
• Preserve identifiers, aliases and source relationships.
• Disclose rejected data and unresolved transformation warnings.
• Identify the earlier snapshot and change-report method.
• Name the owner of the separate screening and escalation process.

• Fictional US sanctions change report PDF. Inspect provenance and changes. The sample is not a current sanctions list.