AML Policy: What to Include, Section by Section
What an AML policy must say section by section, how it differs from procedures, who approves it, and the exam findings a weak policy draws.
TL;DR: KYC remediation is a bounded project that brings existing customer files up to a defined standard after a failure has been found, usually through a consent order, a supervisory finding, an audit, an acquisition or a policy change. A 2023 OCC consent order gave Lake Shore Savings Bank 90 days to review all high-risk customer relationships and build a plan to correct every inaccuracy in its identification, ownership and due diligence records. The work succeeds when the file population is scoped in writing, each decision is evidenced, and the cause of the failure is fixed.
KYC remediation is the corrective review of existing customer records against a stated standard, carried out because those records are known or suspected to be deficient. It has a defined population, an end date and usually an external audience. Teams often use the term interchangeably with a KYC refresh, and the two differ in cause. A refresh is routine maintenance. Remediation responds to a problem.
A transaction AML lookback review can expose bad customer data, and a remediation can surface activity that needs investigating, so the two workstreams should share findings while keeping separate populations and tests.
The FFIEC BSA/AML Manual states that the ongoing monitoring element imposes no categorical requirement to update customer information on a continuous or periodic basis. The federal duty is risk-based and event-driven. A bank may still set review dates in its policy, and once written, those dates become a standard examiners and auditors can test the bank against.
Enforcement orders produce the least flexible remediations, because the regulator writes the terms. The OCC's 2023 consent order against Lake Shore Savings Bank cited deficiencies in customer identification, due diligence, enhanced due diligence and beneficial ownership. Article XIV required written plans to correct inaccuracies in those records for current and new customers, and required the BSA Officer to complete a review of all high-risk customer accounts and relationships within 90 days.
The OCC's 2024 consent order against TD Bank shows the same requirement at far greater scale. Article XII required an effective customer due diligence program within 120 days, unless the approved action plan set another date, including procedures for identifying and timely remediating missing or incomplete information and for enforcing timely consequences when customers fail to provide it. Article XV went further: consultants were to facilitate updating due diligence for moderate- and high-risk customers identified during the SAR lookback, and remediating known errors across the bank's entire customer base.
MRAs have been a common trigger, and the standard for issuing them has just changed at two agencies. A final rule from the OCC and FDIC, effective November 2, 2026, ties MRAs to practices that could reasonably be expected to materially harm an institution's financial condition or present a material risk of loss to the Deposit Insurance Fund, or to actual violations of banking or banking-related law. Violations that show a pattern or are systemic qualify. Concerns below that bar can be delivered as supervisory observations, which carry no requirement for corrective action.
A handful of stale files may now draw an observation. A systemic failure to collect beneficial ownership information is a violation of a BSA regulation, and systemic violations can still support an MRA. The rule covers OCC- and FDIC-supervised institutions only, so Federal Reserve-supervised banks and credit unions should not assume the same standard applies.
Independent testing is a required program element under 31 CFR 1020.210, and a failed sample is often the first sign of a population-level problem.
Acquisitions create a subtler gap. Under the CIP rule, an account acquired through a merger, purchase of assets or assumption of liabilities is excluded from the definition of account, so the acquirer does not have to re-run CIP merely because of the transaction. That exclusion leaves open whether inherited due diligence supports the acquirer's risk profiles and monitoring. Integration teams commonly map the target's files to their own standard and remediate the differences.
Policy changes are the trigger easiest to over-apply. A new risk methodology may justify re-rating the back book, yet a higher internal standard carries no automatic duty of retroactive collection. The FFIEC Manual confirms that banks need not conduct retroactive reviews to obtain beneficial ownership for legal entity customers that existed on May 11, 2018, although ongoing monitoring may require it for particular customers. The decision to apply a new standard forward only, or across the back book, should be made once and recorded with its reasoning.
A sound scope answers four questions in writing: which customers, which attributes, measured against which version of the standard, and why those boundaries are right.
Regulators can hold the pen on scope. In TD's order, the examiner-in-charge determined the lookback scope in writing and the OCC reserved the right to expand it. Lake Shore had to submit a list of the customers, accounts and alerts selected for its lookback, along with the selection method.
Each file moves through the same sequence, with a recorded outcome at every step.
Escalation starts a clock: under 31 CFR 1020.320, a SAR is due within 30 calendar days of initial detection of facts that may constitute a basis for filing, or 60 days if no suspect is identified. Reviewers also need clear rules on outreach, because the same section prohibits disclosing a SAR or anything that would reveal one. A customer contacted for updated documents must not learn why a file was prioritized.
Non-response deserves equal care. TD's order required timely consequences for customers who do not provide information. Those usually escalate from reminders to restrictions to closure, and they need legal and business approval before the first letter goes out.
Remediation staffing is a surge problem, usually met by pairing internal subject-matter leads with contract reviewers or a consultant. An order may take that choice away. OCC Bulletin 2013-33 lists severity, confidence in management, and the bank's own expertise and resources among the factors in requiring an independent consultant, and states that using one does not absolve management or the board.
Resourcing can be enforced directly. TD's order required the board to certify in writing that appropriate resources and staffing were allocated to remediation before paying dividends or repurchasing shares, and capped the bank's average total assets at the September 30, 2024 level until the order terminates.
Evidence should let a stranger re-perform the decision. Each file needs the standard version applied, the attributes tested, the source and date of each piece of evidence, the reviewer and approver, the discrepancy resolutions, and the resulting risk rating. At program level, TD's lookback report had to list the customers whose due diligence was updated or errors remediated, the methodologies used, and cases where the bank declined a consultant's SAR recommendation, with reasons.
Closure rates alone do not satisfy an examiner. The two OCC orders describe quality in specific terms that translate well into a test plan.
A remediation should plan for independent validation before declaring completion. A QA program sampling closed files gives the institution its own evidence before an examiner asks for it.
Remediations recur when the back book is cleaned and the intake that polluted it stays open. The final deliverable should be the control that prevents recurrence.
Start at onboarding, by rejecting incomplete files before they reach a reviewer. Then connect file maintenance to events. The FFIEC Manual lists relevant triggers, including unexplained changes in account activity, changes in ownership, red flags from monitoring, law enforcement inquiries, negative media and the length of time since information was gathered. An institution moving toward perpetual KYC builds on the same signals.
Three further controls close the remaining gaps: a file-health metric reported alongside alert volumes, an impact assessment before any change to the KYC standard, and an integration playbook for acquired portfolios.
Sphinx is an investigation layer inside the systems a compliance team already uses. For remediation, Sphinx's AI agents work through a defined population, pull the existing file and supporting data, test each attribute against the team's SOPs, and prepare a traceable recommendation with its sources recorded. Reviewers keep final approval on every disposition. Sphinx reports 94-98% agreement with analysts. Sphinx does not verify a person's face, connect to bank accounts, or score transactions, so identity verification stays with existing teams and tools.
A KYC refresh is routine maintenance of a customer file, driven by a review date or a change in the customer. KYC remediation is a bounded project to correct files known or suspected to be deficient. Remediation has a defined population and end date, and it often reports to a regulator.
Not retroactively as a blanket exercise. The FFIEC Manual says banks need not conduct retroactive reviews for legal entity customers that existed on May 11, 2018. Ongoing monitoring may still require collecting or updating that information for a particular customer.
The institution should follow a written, time-bound exit policy, which commonly moves from reminders to restrictions to closure. The OCC's 2024 order against TD Bank required procedures to enforce timely consequences when customers fail to provide required due diligence information.
Yes. Under 31 CFR 1020.320, a SAR is due within 30 calendar days of initial detection of facts that may constitute a basis for filing, or 60 days if no suspect is identified.