What should compliance teams ask first in an AML transaction monitoring RFP?

What procurement teams should ask before features

Ask for evidence of governance before asking for feature breadth. In an aml transaction monitoring RFP, the first filter is whether the vendor can show a defensible control trail for how scenarios change, how tuning decisions are approved, how reviewers act on alerts, and how dispositions are retained for audit and investigation use.

A platform can look strong on detection and still be weak where it matters most: explainability of change, operational accountability, and repeatable decision records. That is why the first question is not “what can it detect?”, but “can you prove how the system was governed when the model, rules, and review outcomes changed?”

A useful RFP prompt is to ask the vendor to walk through one complete alert lifecycle, from scenario creation or tuning through review, escalation, closure, and retention. The answer should show who can change what, who approves it, what evidence is produced, and how the platform preserves context for later challenge by auditors, compliance QA, or law enforcement.

What good governance evidence looks like in practice

Good evidence is specific, time bound, and attributable. The vendor should be able to demonstrate change logs for rule sets, tuning history for model or scenario adjustments, reviewer decision history, disposition rationales, and any exception handling that affects alert outcomes. If those records are fragmented, mutable, or hard to export, governance will be difficult even when detection coverage is broad.

Compliance teams should also look for separation between configuration activity and casework. The people tuning thresholds, approving changes, and resolving alerts should leave a clear trace, because auditors often want to know not only what the system did, but why a particular operating choice was made and whether it was reviewed under the right authority.

FATF Recommendations remain the clearest external reference point for expecting risk-based controls, customer due diligence, and defensible monitoring practices, so an RFP should test whether the vendor’s governance artefacts support those obligations in daily operations.

Which vendor answers deserve follow-up questions

Be cautious if the vendor answers only with detection metrics, UI screenshots, or a list of machine-learning features. Those answers may describe capability, but they do not prove operational control. The stronger response is the one that shows how the platform is operated under oversight, how changes are approved, and how investigators can reconstruct a decision after the fact.

Ask follow-up questions when the vendor cannot describe versioning, approval workflow, reviewer accountability, or retention of disposition rationale. Those gaps often surface later as audit findings, weak model governance, or an inability to defend why certain alerts were closed, escalated, or suppressed. In AML, that is a governance failure, not just a product limitation.

FinCEN is the right public authority to anchor expectations around suspicious activity reporting and monitoring discipline in the U.S., while EBA AML/CFT Guidance is useful for EU-oriented programmes that need to evidence robust governance, control ownership, and ongoing oversight.

Practitioner Guidance

What to prioritise: Start with the control trail, not the alert engine. If the vendor cannot demonstrate how changes are authorized, recorded, and reviewed, the product is not ready for a compliance-led RFP even if the detection story sounds strong.

What to verify: Request sample evidence for one recent rule change, one tuning decision, and one alert disposition. You want to see timestamps, approvers, rationale, version history, and exportable records that can survive an audit or investigator challenge.

Decision rule: If the platform can produce consistent governance artefacts for changes and case decisions, it deserves a deeper functional evaluation. If it cannot, treat that as a high-risk procurement issue and do not let feature demonstrations distract from it.

Practitioner takeaway: In AML monitoring, explainability of operations is as important as detection quality, because a system that cannot defend its own decisions will struggle to support compliance outcomes when scrutiny arrives.

Related resources from NHI Mgmt Group

• How should teams evaluate AML transaction monitoring vendors in an RFP?
• How should compliance teams structure transaction monitoring training for mixed-experience AML and fraud staff?
• How should compliance teams reduce fragmentation across KYC, AML screening, transaction monitoring, fraud, and case management tools?
• How should compliance teams structure AML oversight when suspicious activity reporting, customer due diligence, and transaction monitoring all sit in the same function?