FATF's next assessment of the Philippines is expected in 2027, under a methodology that scores whether AML controls actually work, not whether a policy manual says they should. BSP-regulated institutions aren't assessed individually, but the evidence examiners gather from them is what BSP and AMLC will draw on. “Having a policy” and “being ready” are no longer the same claim.
What is a FATF mutual evaluation, and why is one due in 2027?
A mutual evaluation is FATF's periodic assessment of a country's AML/CFT system. It runs against the Financial Action Task Force's 40 Recommendations, and separately, against how effectively that system operates in practice. FATF's president and BSP Governor Eli Remolona have both stated the Philippines' next assessment falls in 2027. It follows the country's exit from the FATF grey list on 21 February 2025, a result we've covered in detail elsewhere. Grey-list exit closed one chapter. The 2027 evaluation opens the next one, on different terms.
Why does effectiveness matter more than paperwork under the 5th-round methodology?
Because that is the explicit design of the current assessment framework. FATF's own methodology guidance states plainly: “sound laws, regulations and procedures are important, but what is even more important is that they are put to use and deliver results.” It adds a second point: “it is up to the country to demonstrate that it is taking effective action.” The 5th round scores a country against 11 Immediate Outcomes, a measure of whether the system works. That effectiveness score carries more weight than technical compliance with the Recommendations themselves. A supervised institution whose program exists mostly as a binder satisfies the older, narrower test. It does not satisfy this one.
Source: FATF, The 2022 and 2013 Methodologies for Assessing Technical Compliance and Effectiveness of AML/CFT/CPF Systems.
Does FATF actually examine individual institutions, or only BSP and AMLC?
Only the country is rated. FATF assessors evaluate the Philippines as a jurisdiction, working with BSP, AMLC, and other competent authorities. Mutual evaluation on-site visits typically include meetings with private-sector reporting entities as one input among several. Your institution will not receive a FATF grade. But the evidence BSP and AMLC bring to that assessment, filing timeliness, case documentation, screening records, comes from supervised institutions' own operations. BSP's own supervisory posture has already shifted toward testing whether a compliance program produces auditable outcomes, not just documents one. That shift is ahead of, and independent of, the 2027 date.
What should an institution be able to show, right now, rather than describe?
A few concrete things separate a program that can produce evidence from one that can only describe itself. First, a record of when suspicion was established on a filed STR, not just the filing date itself. Those two dates are legally distinct, and often conflated. Second, a case file that consolidates an alert, its investigation, and its disposition in one place an examiner can follow, instead of three disconnected tickets. Third, a screening program that can show when a customer was actually checked against an updated list, not only that a policy requires periodic checks. None of this is new guidance invented for 2027. It is the same standard BSP examiners already apply. And it is the same standard that breaks down inside institutions that have never had to produce the underlying record, the exact gap the five-day-versus-next-day filing confusion exposes.
How does this connect to filing timeliness specifically?
Timeliness is one input, not the whole picture. This piece isn't the place to re-walk the STR-versus-CTR deadline mechanics; two other pieces on this site cover that ground directly. What matters for evaluation readiness is narrower. Can the institution produce, on request, the timestamp of when suspicion was determined against the timestamp of when the STR was filed, for a sample of cases? That's a different question from asserting the next-working-day rule is followed. A monitoring system that logs both moments as part of the same case record answers it by default. A system that only logs the filing date does not. The gap stays invisible until someone actually asks for it.
What's the discrepancy between 2026 and 2027 about?
AMLC's own 2024 Annual Regulatory Plan referenced a “scheduled Mutual Evaluation in 2026.” FATF's president and BSP's governor have both since stated 2027. We have not independently reconciled that discrepancy against the FATF and APG's own assessment calendar. Institutions should treat 2027 as the widely stated figure, and confirm the exact onsite window with their Compliance Advisory Lead as the schedule firms up. Neither date implies a return to grey-list status. Grey-list exit and mutual evaluation are separate processes, and this article does not suggest otherwise.
Where does this map in your AML program?
This is a Case Management problem first. An examiner-followable audit trail across alert, investigation, and disposition is what turns “we have a process” into evidence a process ran. It is a Regulatory Reporting problem second, since filing-timeliness records are one of the concrete data points BSP and AMLC will have on hand. Fyscal ARCX's Case Management module keeps every alert, screening result, and investigation tied to one customer or case record, with the underlying timestamps preserved. The record an examiner would ask for already exists, instead of needing reconstruction after the fact. For a broader view of an auditable compliance data architecture beyond case files specifically, see our regulatory reporting playbook for mid-size fintechs. For why a point-in-time check is the wrong model generally, see continuous KYC: from checkpoint to real-time risk decision.