What Is KYC Remediation? Triggers, Scope and Workflow

KYC remediation brings existing customer files up to standard after a failure. What triggers it, how to scope it, and what regulators check.
Alexandre Berkovic

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.

What KYC Remediation Is, and What It Is Not

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.

ActivityWhat it examinesWhy it happensHow it ends
KYC remediationExisting customer filesA known deficiency in those filesPopulation closed and validated
KYC refreshOne customer file at a timeA review date or a change in the customerOngoing as part of normal operations
AML lookbackHistorical transactionsSuspicious activity may have been missedLate SARs and a report
Perpetual KYCCustomer data as it changesAn operating model choiceDoes not end

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.

What Triggers a Remediation

Matters requiring attention

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.

Audit findings, acquisitions and policy changes

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.

Scoping the Population

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.

  1. Tie the population to the failure. If the root cause was one onboarding channel between two dates, start there and test whether the problem extends further.
  2. Extract from source systems and reconcile the counts to the core banking record before any review begins.
  3. Run an attribute-level gap analysis, so a file missing one field is not handled like a file with no due diligence.
  4. Segment by risk, using current customer risk ratings while recognizing that those ratings may themselves be built on the bad data.
  5. Document exclusions such as closed accounts, entities outside the legal entity customer definition, and pre-May 2018 ownership records.
  6. Obtain sign-off from the BSA officer and, where an order applies, from the regulator.

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.

The Remediation Workflow

Each file moves through the same sequence, with a recorded outcome at every step.

  1. Freeze the standard and write a file-level test: every attribute, the acceptable evidence, and the pass condition.
  2. Pre-populate from what the institution already holds across its systems, and from public sources where policy permits.
  3. Contact the customer only for true gaps, using scripts reviewed by compliance.
  4. Review the completed file and reassess the customer risk profile.
  5. Escalate unusual activity to the investigations team.
  6. Apply quality control before closing the file.
  7. Exit non-responsive customers under a written, time-bound policy.
  8. Report progress and exceptions to the governance body.

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.

Staffing and Evidence

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.

What Regulators Look At

Closure rates alone do not satisfy an examiner. The two OCC orders describe quality in specific terms that translate well into a test plan.

  • Analysis in the file. TD's order calls for documented critical analysis of significant information, including disparities, risk indicators and well-supported conclusions.
  • Decision quality. Lake Shore's order requires independent, risk-based QA and QC of periodic reviews of high-risk customers, with a focus on decision quality.
  • Issue tracking. Lake Shore's order requires a system showing the remediation needed, its due date, specific reasons for any delay, and the person responsible.
  • Validated fixes. TD's order expects the audit program to review and validate corrective action promptly.

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.

How to Stop Needing Another One

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.

Where Sphinx Fits

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.

Frequently Asked Questions

What is the difference between KYC remediation and a KYC refresh?

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.

Do banks have to collect beneficial ownership for customers onboarded before May 2018?

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.

What happens if a customer does not respond during KYC remediation?

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.

Can suspicious activity found during remediation start the SAR clock?

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.