Blog Image

goAML FFR and PNMR Reports in the UAE: What Compliance Teams Should Do

What are FFR and PNMR reports?

The Funds Freeze Report (FFR) and Partial Name Match Report (PNMR) are goAML report types connected with targeted financial sanctions screening. They are different from an STR or SAR, which concerns suspicion of criminal activity. An FFR or PNMR documents action taken after a screening result involving a sanctions list, in line with the applicable rules and the entity’s procedures.

The UAEFIU report-type guidance describes an FFR for a confirmed name match to the UAE Local Terrorist List or UN Consolidated List where freezing measures have been taken. It describes a PNMR where a partial name match is identified and suspension measures have been taken. The guidance states that FIs, DNFBPs, and VASPs should submit these reports through goAML within five days from taking the relevant measures. Always confirm the latest FIU instructions and the requirements of your supervisory authority before applying a deadline to a particular case.

How a screening result should be handled

A similar name is not automatically a confirmed match, but an alert should not be dismissed without review. Escalate it and compare relevant identifiers such as date of birth, nationality, address, and corporate details. For a confirmed match, follow the applicable sanctions directions and document any required freeze and report. For a partial match, investigate and take any required suspension measure while it is reviewed. Record the evidence, action, timing, and approver.

FFR versus PNMR

The simplest distinction is the match status and action described by the report type:

  • FFR: A confirmed match to a relevant sanctions list and a freezing measure taken.
  • PNMR: A partial name match to a relevant sanctions list and a suspension measure taken while it is assessed.

Do not select a report solely because the customer’s name resembles a listed name. The compliance officer should use the current UAEFIU guidance and internal procedure to establish which report is required. If the facts do not match the FFR or PNMR criteria, another action or report type may be relevant. If a separate suspicion exists, assess whether an STR or SAR is also required; sanctions reporting and suspicious activity reporting serve different purposes.

Information to collect for the review

Keep the list and screening date, identifiers compared, match rationale, relevant customer or transaction context, and steps taken to confirm or rule out the match. Record the freeze or suspension, timing, affected assets or transaction, approver, and FIU correspondence. Use the current report form for its exact field requirements.

A practical reporting workflow

1. Escalate the alert promptly

Route potential sanctions matches to the designated compliance officer or MLRO. Staff should know that a screening alert requires review and should not be cleared without following the organisation’s documented procedure.

2. Compare identifying information

Review the exact name, aliases, date of birth, nationality, address, corporate identifiers, and other available data against the list entry and the customer file. Document what matched and what did not. If information is missing, seek it through approved internal processes.

3. Apply the relevant measure

Follow the applicable sanctions direction and internal procedure for a confirmed or partial match. Record when the organisation acted and which funds, assets, or transactions were affected. Do not tell a customer that a suspicious report has been or may be filed; follow the organisation’s confidentiality and non-disclosure controls.

4. Choose the correct report type

Use the FIU’s current goAML guide to determine whether the case calls for an FFR or PNMR. These report types are tied to different match conditions and actions. Do not use an STR as a substitute for sanctions reporting or vice versa.

5. Submit and retain the record

Complete the report using verified information, submit it within the timeframe specified by current guidance, and save the reference number and supporting documents in a restricted-access case file. Assign a responsible person to monitor portal messages and any FIU request for more information.

Common mistakes to avoid

Common failures include treating every alert as confirmed, clearing a partial match without recorded analysis, missing the action date, using the wrong report type, and not monitoring FIU messages. A procedure should define screening frequency, escalation, approval authority, implementation of measures, and report filing. Train staff on spelling variations and ownership links.

Governance and staff readiness

A written sanctions procedure should show which screening lists are used, how often customers and counterparties are screened, who can clear a false positive, and who can approve a freeze or suspension. Keep a time-stamped record of the alert, the match analysis, the decision, and the filing. Ensure authorised staff can access the current goAML guidance and that another trained employee can act if the primary MLRO is unavailable.

The organisation should also test its process. A short tabletop exercise can check whether staff know whom to notify, how to preserve relevant records, and who monitors the FIU portal after a filing. Update the procedure when the regulator’s guidance, sanctions exposure, product range, or customer profile changes. Keep a training record showing which roles attended, what version of the procedure they reviewed, and how new staff learn the escalation route. This makes it easier to identify gaps during an internal review. Where responsibilities are shared across branches, define which office owns each escalation and report.

FAQs

When is an FFR used?

The UAEFIU guidance describes it for a confirmed name match to a relevant sanctions list where a freezing measure has been taken.

When is a PNMR used?

The guidance describes it for a partial name match where suspension measures have been taken.

Are FFR and PNMR the same as an STR?

No. They relate to sanctions-list matching and measures taken. STRs and SARs address suspicion of criminal activity.

What is the reporting timeframe?

The UAEFIU report-type guidance states five days from taking the relevant measure. Check for later FIU or supervisory updates before filing.

Should the business file an STR as well?

If there is a separate basis for suspicion, assess that reporting obligation separately. An FFR or PNMR does not automatically replace an STR or SAR.