OFAC Screening for Money Transfer Counters: A Workflow
Industry Payment Guides

OFAC Screening at the Remittance Counter: Hits, Holds and Logs

OFAC screening for money transfer counters: clear common-name false positives, handle customer holds, and know when a transfer goes to compliance.

Businessman in a dark suit checking his wristwatch in front of rolled-up US dollar bills

Photo: Pixabay

On this page 6 sections
  1. OFAC Compliance for a Money Transmitter Reaches the Agent Counter
  2. OFAC Screening for Money Transfers Goes Beyond the Sender's Name
  3. Clearing an OFAC False Positive on a Remittance
  4. Blocked Transaction Reports, Rejections and Who Files Them
  5. What to Tell a Customer Whose Transfer Is on Hold
  6. Screening Logs That Hold up in an Exam or Bank Review

Key takeaways

  • An agent counter shares the compliance job even when the principal's platform runs the screening. Staff need one fixed rule: a held transfer is never released at the window.
  • Clear a name hit by comparing the list entry's published identifiers with the customer's ID and file, and log which ones you compared. Re-spelling a name to make an alert disappear is evasion.
  • Decide in writing who files with OFAC, which report applies and by what deadline before the first true match arrives. Don't work it out while a customer waits.
  • Counter staff should read the same neutral hold script every time. They should never name a list or mention a suspicious activity report.

Every money transfer that leaves your counter has to be checked against U.S. sanctions before it goes, and OFAC screening is how you do that for each money transfer. You run every party to the transfer, plus the destination, against the lists published by the Treasury Department's Office of Foreign Assets Control (OFAC). A near-miss gets cleared with a written reason. A true match stops and goes to your compliance officer, who handles it under OFAC's regulations.

Most of the hard calls happen at the window while a customer waits. That is where common-name hits get cleared or escalated, and where a badly worded hold can embarrass an innocent customer. What follows is general information, not legal advice. Confirm your program with a qualified compliance professional or counsel.

OFAC Compliance for a Money Transmitter Reaches the Agent Counter

An agent can't hand sanctions compliance entirely to the principal's software. Confirm with counsel exactly how the rules apply to your business, but plan on the basis that your business and the people working your window are covered, and that the size of the transfer doesn't change the answer. A small transfer to a listed person is not a smaller problem.

Don't build your program on the hope that an honest mistake will be excused. The defensible position is a written procedure that staff actually follow, plus records showing they followed it. "The clerk didn't notice" is not something you want to rely on.

Keep sanctions screening separate from your anti-money-laundering work. Your AML program, including how you decide whether activity is suspicious, runs on its own set of rules and reports. One transaction can raise both issues, and each gets handled on its own terms by whoever owns it. If your counter also cashes checks, see our guide to spotting fake payroll and altered checks.

How the work divides depends on how you operate:

  • Agents of a principal. If you send for a large network, the principal's platform usually screens each transfer in real time and returns a hold on a possible match. Your agent agreement decides who reviews alerts and who files with OFAC. Find the section on what counter staff may do without calling compliance, and train to it. Our comparison of agent commissions at Western Union, MoneyGram and Ria covers the commercial terms of those agreements. The compliance terms deserve the same attention.
  • Independent licensed transmitters. You own the whole program, from choosing the screening tool to filing reports, and you answer for it when examiners or bank partners review you.

Either way, staff need one rule memorized: a teller never releases a transfer the system has held.

OFAC Screening for Money Transfers Goes Beyond the Sender's Name

A program that screens only the sender leaves gaps. Good sanctions screening for an MSB checks every party and every data field that could tie a transfer to a sanctioned person or place.

People. Screen the sender and the receiver. Also screen anyone else with an interest in the money, such as a third party paying on the sender's behalf. Your ID and customer-information process feeds this step, and a thin receiver record makes an alert much harder to clear later.

Ownership. For business-to-business transfers, a company's name being absent from the lists doesn't settle the question, because a listed person can sit behind a company that isn't named. Ask your compliance officer how your procedure treats companies owned by listed persons, and ask your screening vendor how the tool accounts for ownership.

Places. Sanctions can reach destinations, not just named people, and what's restricted changes over time. Check OFAC's website for current program information instead of trusting a printout taped next to the terminal, and have your compliance officer spell out which destinations your procedure treats as off limits.

Free-text fields. Address lines and purpose-of-transfer notes can carry a sanctioned city or company name. Payout-location fields can too. A tool that reads only the name fields will miss them.

Timing. Screen at origination. If a transfer sits pending across a list update, screen it again before payout. For repeat senders whose profiles you keep, rescreen the stored base after each update rather than waiting for their next visit.

Clearing an OFAC False Positive on a Remittance

Many alerts turn out to be someone else. Common and transliterated names produce a steady stream of hits on people who aren't the listed person. Clearing an OFAC false positive on a remittance is a comparison exercise, and it should run the same way every time:

  1. Read the list entry, not just the name. Note which list it came from and every identifier published for it: dates of birth, nationality, addresses, document numbers and any aliases.
  2. Compare those identifiers with what you collected. Work from the customer's ID and file. One hard mismatch, like birth dates decades apart, usually counts for more than several soft similarities.
  3. Judge how strong the name match is. A full-name match with matching identifiers is a different situation from a shared surname paired with a similar first name.
  4. Escalate when you can't tell. If identifiers are missing on either side or the comparison is ambiguous, the transfer stays held and goes to your compliance officer or the principal's compliance team. They decide whether to contact OFAC.
  5. Write down the reason. "Cleared" by itself is not a reason.

Illustrative example. The customer, dates and list entry here are invented for this article. A sender presents a Texas driver's license as "Ramon Cruz," a man in his late thirties with a Houston address. The tool flags a fictional list entry, "Ramon Antonio Cruz," whose listed birth date would make him nearly three decades older. That entry also shows a foreign nationality and an address abroad.

The names overlap, but none of the identifiers do. The reviewer clears the alert and logs: "Customer DOB and listed DOB about three decades apart; U.S. license and Houston address vs. listed foreign address; no alias match. Cleared." Had the license shown the listed birth date, the transfer would have stayed held and gone to compliance.

Repeat customers with common names will hit again and again. Many tools let you mark a reviewed customer as cleared so later alerts are suppressed. That works only if the suppression is tied to the identifiers you checked rather than to the name. It also needs a fresh review whenever the list entry it matched changes.

One shortcut is off limits. Never re-spell a customer's name or swap in a different ID to make an alert go away. That isn't clearing a false positive. It is evading screening. If a customer offers to "just use my cousin's name," treat the offer as a red flag in its own right.

Blocked Transaction Reports, Rejections and Who Files Them

When an alert is a true match, or the destination is one your procedure treats as restricted, the counter's job ends and compliance takes over. OFAC's regulations govern what happens next: whether the transfer is blocked or rejected, what happens to the funds, which report goes to OFAC and how quickly it is due. Your compliance officer applies those rules to the specific facts. Nobody at the window should be making that call.

What you can do now is make sure your written procedure already answers the questions that come up in the first hour after a true match. If any of these is blank, fill it in with your compliance officer before the next alert:

Question your procedure must answerWho usually answers it
Who decides whether a match is confirmedCompliance officer, or the principal's compliance team for agents
Whether the transfer is blocked or rejected, and what happens to the fundsCompliance officer, applying OFAC's regulations
Who files the report with OFACThe principal in many agent networks; the transmitter itself if independent
The current filing deadline, in writingCompliance officer, confirmed against OFAC's reporting regulations
What facts the agent must send, and how fastAgent agreement or principal's procedures
Whether a suspicious activity review is also neededYour AML program, handled separately

The deadline row matters most. Reporting windows are short, and a late report creates a problem of its own. Get the current deadline from your compliance officer or the regulations themselves, write it into your procedures and train to it.

Agents should know who files the blocked transaction report or reject report before any alert happens. In many principal networks, the principal files and the agent supplies the facts quickly. Independent transmitters file for themselves. A blocked or rejected transfer may also call for a suspicious activity report, but that decision runs through your AML program, not your OFAC procedure.

What to Tell a Customer Whose Transfer Is on Hold

The customer at the window wants to know when the money will arrive. Counter staff have to stay calm and accurate without guessing. A workable script for a held transfer:

"Your transfer needs an additional review before it can be sent. We'll contact you as soon as it's complete. I can't give you a time estimate, but I have your phone number, and your receipt number is on this slip."

Then hold to a few rules:

  • Skip the why. Never say "sanctions list," "terrorist list" or "your name matched someone." A hold often turns out to be a false positive, and naming a list can humiliate an innocent customer.
  • No promises on timing. How long review takes depends on what compliance finds.
  • Never suggest a workaround. Proposing a different receiver or payout country, or breaking the amount into smaller transfers, can turn a held transfer into a violation.
  • Keep any SAR out of it. Follow your compliance officer's instructions on what may be disclosed, and never mention a suspicious activity report to a customer.

If the transfer is blocked, the formal notice to the customer comes from your compliance officer or principal. A teller should not improvise it, and compliance should handle any customer who disputes the outcome. Keep a printed copy of the hold script at every window, so a new hire working a Saturday rush says what your compliance officer would say.

Screening Logs That Hold up in an Exam or Bank Review

An examiner treats a program you can't prove as a program you don't have. For every alert, record:

  • Date and time, plus the list version or update date the tool used
  • Every party and field that was screened
  • Which list entry triggered the alert
  • Identifiers compared, with the result of each comparison
  • Reviewer's name and decision: cleared, escalated, blocked or rejected
  • Escalation notes and any contact with OFAC
  • Reference numbers and filing dates for any report to OFAC

Store your written OFAC policy alongside staff training records. If the program has been independently tested, file those results there too. Confirm with your compliance officer how long each type of record must be kept before you purge anything old.

These records matter beyond regulators. Sponsor banks and card processors look hard at money services businesses before approval and after it. A clean alert log and a written policy strengthen an application, and gaps in both come up often in our guide to why money transmitter merchant accounts get declined. The code you're boarded under shapes that scrutiny as well. Our explainer on how money transfer merchant category codes affect fees and risk reviews walks through it.

MannyPay offers high-risk merchant accounts and international payment processing. Approval for any business depends on underwriting. A MannyPay specialist responds to quote requests within one business day.

Start with this job this week: pull last month's alerts and check that every cleared one carries a written reason naming the identifiers compared. Any entry that says only "cleared" is the first gap an examiner will find. With that file in order, you can request a free quote and have your documentation ready if underwriting asks for it.

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading