Philippines supplier sanctions-screening handoff: preserve the match evidence for qualified review

Prepare an identity record before screening

A supplier named “North Star Trading” appears in a screening result, but the name alone cannot show whether it is the listed party. Start with the approved onboarding sources: legal name, aliases, entity type, registration number, jurisdiction, addresses, ownership information available under the client’s procedure, bank beneficiary where permitted, and service scope. Record the source and retrieval date for each field.

Do not collect nationality, personal identifiers, or ownership data beyond the client’s lawful and approved need. A Philippines-based procurement administrator may normalize the record, run an authorized tool, preserve results, and assemble a review packet. They may not decide that a supplier is sanctioned, clear a possible match, interpret sanctions law, block property, reject the supplier, or notify authorities.

Those actions stay with the client’s compliance and legal owners. The US Treasury’s Office of Foreign Assets Control provides official list-search tools and guidance, but an automated result is not a legal conclusion and screening requirements depend on the organization and transaction.

Record the search so another reviewer can reproduce it

The screening record should include tool and dataset, search time and timezone, list version or update time where available, fields submitted, matching threshold, transliteration settings, filters, result identifiers, and unaltered result output. Preserve a protected copy or durable reference according to policy. If the tool searches only a name while the client expects address or identifier comparison, flag the limitation.

Do not manipulate spelling until a result disappears. Run approved aliases and transliterations as separate attributable searches. A “no match” result means the configured search returned none at that time; it does not prove the supplier or every owner is clear.

Likewise, a high score does not prove identity. Screening vendors can rank similarities differently. The handoff should let the qualified reviewer see which facts agree, which conflict, which are missing, and what source supports each comparison without repeating the search from memory.

Build a possible-match comparison without making the decision

Use a side-by-side table for name and aliases, entity or person type, jurisdiction, address, date or registration identifiers, ownership connections, list program, and source confidence. Mark exact agreement, material conflict, partial information, and unavailable evidence. Do not use a single mismatch as automatic clearance unless the client’s qualified procedure says it is dispositive.

A supplier can share a common name with a listed party, while an alias can differ substantially. Separate factual comparison from inference. “Addresses differ” is a fact when both sources are current; “therefore false positive” is a decision.

Record commercial urgency and pending transactions, but never let a payment deadline lower the evidentiary standard. Place affected onboarding, purchase, access, or payment activity in the client’s prescribed hold state. The administrator communicates only approved status language and does not accuse the supplier or disclose sensitive screening logic.

Route the result through named decision states

Define states such as prepared, screened, no result under stated configuration, possible match, awaiting evidence, under qualified review, cleared by owner, rejected by owner, blocked or restricted under owner instruction, and rescreen required. Every transition names the actor, time, evidence, and permitted next action. An email saying “looks fine” is not enough if the procedure requires a case decision.

The compliance owner may request a registration extract, ownership confirmation, or another source through an approved channel. The administrator tracks that request without deciding what evidence is legally sufficient. OFAC’s Sanctions List Search and its guidance on search results explain that users must assess potential matches; the client’s advisers determine the correct response.

If instructions conflict, keep the supplier and affected transaction on hold and escalate. Do not delete the first result after later clearance because the history explains why work paused and what the reviewer considered.

Rescreen when relevant facts change

Approval is time-bound to the identity, ownership, lists, and transaction context reviewed. Define rescreen triggers: list updates under client policy, legal-name or ownership change, new jurisdiction, bank-beneficiary change, long inactivity, contract renewal, unusual transaction, or scheduled periodic review. Reconcile active suppliers to the screening register and investigate missing or stale records.

Sample cleared possible matches to confirm the comparison and decision evidence remain linked. Test the process with a common name, transliterated alias, changed address, incomplete registration, corporate parent, and supplier whose bank beneficiary differs. Measure preparation completeness, review aging, unsupported releases, stale screening, and downstream holds left active after a decision.

Do not rank administrators by quick clearances. The useful outcome is a reproducible packet that allows qualified owners to decide while the offshore role manages evidence, follow-up, and system state without taking compliance authority.

Control screening-tool and list changes

Screening results can change when a vendor updates its matching algorithm, a list source changes format, thresholds move, or the client enables another dataset. Record configuration ownership and require a change notice that identifies effective time, affected populations, test cases, and rollback. Before release, compare known clear, known possible-match, alias, common-name, and incomplete-record examples under old and new settings.

Do not use real restricted cases in a broad test environment. If a configuration change creates a large new queue, preserve prior results and prioritize through the qualified owner’s rule rather than lowering the threshold to reduce volume. Reconcile users and permissions after the change.

The administrator may execute an approved rescreen and report result movement, but cannot declare the new configuration legally sufficient. Keep list-update time distinct from the time a supplier was rescreened. When a historical result cannot be reproduced because the tool or data changed, document that limitation and retain the original output.

This gives reviewers a defensible history instead of a dashboard that silently applies today’s logic to yesterday’s decision. Record the test approver too.