Screening Matches

Holds the hits the screening engine raises when a member or counterparty resembles a watchlist entry (mfi.aml.screening.match), each with a similarity score and review status. Compliance staff adjudicate every match as a true hit or a false positive, building an auditable disposition trail. Unresolved matches block onboarding or transactions per policy.

Screening Matches
Screening Matches — live screen from the BridgeERP MFI Suite.

Workflow

  1. Open Screening Matches under Compliance.
  2. Filter by status to see undecided matches first.
  3. Open a match to compare the member against the watchlist entry.
  4. Disposition it as a confirmed hit or a documented false positive.
  5. Escalate confirmed hits to an STR and apply any account restriction.

Fields reference

Every field on this screen, drawn from the live data model.

FieldTypeRequiredDescription
Member
member_id
Link → mfi.memberYesMember
Watchlist Entry
watchlist_entry_id
Link → mfi.aml.watchlist.entryYesWatchlist Entry
Match Method
match_method
Choice: Exact National ID, Exact Name, Fuzzy Name, DOB Match, CompositeYesMatch Method
Has Message
has_message
Yes/NoHas Message
Name
name
TextName
Code
source_code
Choice: UN Sanctions, US OFAC SDN, CBK PEP List, EU Financial Sanctions, INTERPOL Notices, UK HMT Sanctions, Custom ListCode
List Type
list_type
Choice: Politically Exposed Person, Sanctions, Criminal, Terrorist, AML High RiskList Type
Match Score
match_score
DecimalMatch Score
State
state
Choice: Potential, Confirmed Match, False Positive, ClearedState
Reviewed By
reviewed_by_id
Link → res.usersReviewed By
Reviewed Date
reviewed_date
Date & timeReviewed Date
Notes
notes
Long textNotes
Company
company_id
Link → res.companyCompany

Actions & buttons

Buttons available on this screen and what they do:

  • Confirm Match
  • False Positive
  • Clear

Status lifecycle

Records on this screen move through these statuses:

Potential → Confirmed Match → False Positive → Cleared

Notes & rules

  • Each match carries a similarity score for prioritisation.
  • Confirmed hits feed directly into STR creation.
  • False-positive decisions are recorded with a justification.
  • Open matches can gate onboarding and transaction processing.

Technical model: mfi.aml.screening.match · Record: AML Screening Match

Was this page helpful?