Sanctions screening for money services businesses

On this page

Define the business activity and responsibilities

Money services businesses can perform different activities and operate under different requirements. Establish the actual business, jurisdictions, agent relationships, and obligations before mapping the control. FinCEN’s MSB materials are a starting point, not a substitute for an applicability assessment.

Sanctions screening compares submitted identities with selected sources. It is not the same as transaction-pattern monitoring, customer verification, or filing a required report.

Identify the people and organizations your process covers

Map customers, business counterparties, and any additional parties your policy requires the team to identify. Keep the party’s role and stable internal reference with the subject. Avoid using one person’s search as an unexplained proxy for a legal entity.

Collect only useful, lawfully available identity details. Preserve partial dates and the provenance of identifiers rather than inventing missing values to satisfy a field.

Design the time-sensitive exception path

Specify when a completed check is required and who handles a candidate or unavailable source. A transaction deadline does not turn an incomplete check into a no-match result.

Keep your system’s screening state separate from the transaction state. A completed no-match result may still leave other checks outstanding, while a possible identity match requires an assigned review rather than a blanket finding of wrongdoing.

Retain review evidence across handoffs

Synthetic example: an invented customer has a potential name match with no reliable source birth date. The first reviewer records that the date comparison is unavailable, not contradictory, and assigns the additional investigation. A second reviewer can then continue from the actual evidence.

Preserve the source record, reasoning, required approvals, and separate business action. Determine how evidence moves between the principal business, an agent, and other relevant teams without assuming another party’s check is complete or accessible.

Budget for portfolio monitoring

Choose continuing subjects for monitoring according to policy and keep their identity information current. Scheduled and qualified source-triggered rescreens use the same production allowance as interactive screens. Define the operational response to a usage cap or failed monitoring run.

Monitoring a customer’s name does not analyze the customer’s transaction behavior. Maintain those responsibilities and evidence separately within the broader AML and sanctions program.

Test the workflow under pressure

See the MSB solution and fintech API guide for the integration and team handoffs.

Test a candidate during a time-sensitive transaction workflow.
Test unavailable required coverage and a transport timeout.
Verify a retry uses the same operation key and unchanged payload.
Exercise reviewer absence and principal-agent evidence handoffs.
Prove monitoring failures remain visible until addressed.