Skip to main content
Promotional banner ad for the Penetration Testing Report Kit
Making KYC Escalation Hold Up Against Revenue PressureCompliance Program Governance
5 min readFor KYC Analysts

Making KYC Escalation Hold Up Against Revenue Pressure

Scope

This guide covers one operational question for KYC analysts: when a business sponsor wants to accept, retain, or expand a high-risk customer relationship, what makes your concern consequential rather than decorative?

The prompt is a reported case. Journalists examining more than 15 million leaked internal Deutsche Bank documents claim the bank overrode compliance concerns to increase business with Russian oligarchs. The problems are said to span over two decades and to cast doubt on the bank's assurances that it improved AML and compliance procedures after earlier regulatory fines. These are claims from a media investigation. Treat them as a stress test for your own process, not as established fact.

This guide does not cover sanctions screening mechanics or transaction monitoring tuning.

Key Concepts and Definitions

Override. A decision to proceed with a relationship, product, or limit increase despite an unresolved compliance concern. Overrides are not inherently wrong. Unrecorded or unowned overrides are.

Decision rights. Who can approve, who can veto, and who can only advise. If a concern is "noted" but nobody must act on it, you don't have decision rights; you have commentary.

Customer Risk Rating. The output of your risk model. It only matters if a change in rating changes what the business is allowed to do.

Ongoing Due Diligence. Scrutiny of the relationship and its transactions after onboarding, including reassessment when the relationship grows or changes in nature.

Periodic Review. The scheduled re-examination of the Customer Risk Profile. Triggers between reviews matter as much as the calendar.

Escalation to MLRO. The defined path by which an unresolved concern reaches the person with authority to act on it.

Requirements Breakdown

You won't find a single rule that says "compliance must be able to stop revenue." The obligation is assembled from several places.

  • Risk-based approach. FATF Recommendations (Recommendation 1) expects enhanced measures where risk is higher. Enhanced measures that never change a decision aren't enhanced.
  • Senior management approval. FATF Recommendation 12 expects senior management approval to establish or continue relationships with politically exposed persons. Apply the same logic to any high-risk tier even where the rule doesn't strictly require it.
  • Ongoing due diligence. Recommendation 10 requires ongoing due diligence and scrutiny of transactions throughout the relationship, so that activity stays consistent with what you know about the customer.
  • Governance expectations. Supervisors generally expect an independent compliance function with sufficient authority and direct access to the board. Check the exact wording in your own jurisdiction's rules and guidance rather than relying on this summary.

The practical reading: the law asks whether your controls work, not whether your policy exists.

Implementation Guidance

1. Define which decisions need independent approval

Put these behind a compliance sign-off the business cannot grant itself:

  • Onboarding of customers in your highest Customer Risk Rating tier
  • Retention after a negative adverse-media or source-of-wealth finding
  • Material expansion of products, limits, or jurisdictions for a high-risk customer
  • Any exit reversal, where a relationship flagged for closure is reinstated

2. Retain evidence when a sponsor pushes back

When a business sponsor challenges or seeks to override a concern, keep a single reviewable file containing:

  • The original concern, stated specifically (what was found, what is unexplained)
  • The sponsor's challenge, in their own words, and the date
  • Any new information offered, and whether it was independently verified
  • The decision, the named decision-maker, and their written rationale
  • Conditions attached (enhanced monitoring, limits, review date)
  • Whether the disagreement was resolved or escalated, and to whom

If the sponsor's argument is commercial ("this client is strategically important"), record it as such. Commercial value is not a mitigant of money laundering risk, and your file should make that distinction visible.

3. Build a disagreement path with a defined end

Unresolved disagreements need a ladder with deadlines: analyst, KYC lead, head of compliance, MLRO, then the board risk committee or equivalent. The key design point is that the default outcome of an unresolved escalation is no expansion, not proceed. Silence must never approve.

4. Reassess when the relationship grows

Don't treat onboarding as a one-time gate. Set event triggers for a fresh look:

  • Sharp growth in volumes or balances against the original expected activity
  • New products, booking centers, or counterparties
  • A new adverse finding on the customer or connected parties
  • A change in ownership or control

A relationship that has doubled in size may warrant reassessment, but growth alone does not establish that its risk has changed.

5. Test whether remediation changed behavior

Revised policies are evidence of intent. Behavior shows up in outcomes. Ask your second line or internal audit to sample and report on:

  • Override rate for high-risk customers, and trend over time
  • Time-to-decision when compliance and the business disagree
  • Cases where concerns were raised and the relationship still expanded, with the documented rationale
  • Exits initiated by compliance versus exits initiated by the business
  • Whether the same sponsors repeatedly generate overrides

A remediation program where override patterns never move has changed the paperwork, not the decisions.

Common Pitfalls

  • Advisory-only compliance. Concerns are logged, but no one is obliged to respond.
  • Rationale by reference. "Approved per relationship manager" is not a rationale.
  • Onboarding-only scrutiny. Strong initial assessment, then growth with no reassessment.
  • Remediation measured by deliverables. Counting policies updated and training completed instead of decisions changed.
  • Normalized overrides. When overrides are routine, they stop being visible as exceptions.
  • Analyst isolation. A junior analyst raising a concern alone, without a protected route above the sponsor's reporting line.

Quick Reference Table

Question What good looks like Red flag
Who can override a compliance concern? A named senior role, in writing, with compliance concurrence Business line can self-approve
What is recorded? Concern, challenge, decision-maker, rationale, conditions Verbal agreement, no file
What if the disagreement is unresolved? Escalates by deadline; default is no expansion Proceeds while pending
When is the customer reassessed? Periodic Review plus event triggers tied to growth Calendar only
How is remediation tested? Outcome sampling of overrides, exits, expansions Policy and training counts only
Who sees override trends? MLRO and board risk committee, regularly Visible only to the originating team

Closing Check

Pick one high-risk relationship that grew over the last year. Pull the file. Can you see what concern was raised, who challenged it, who decided, and why? If you can't reconstruct that in minutes, that may indicate a record-management issue.

a promotional banner asking how ready are you for PCI DSS 4.0? With a call-to-action to get the checklist now.

You Might Also Like