Compliance in Banks and Corporate Governance

Compliance Function in Banks

Read at your own pace. Use chapter practice to check your understanding.

Chapters and chapter contents
100%
Practise this chapter ↓

Last updated · By the Clerk2Officer editorial team · Report a correction

1. Why compliance is a banking function

A bank converts promises into financial services: a deposit must remain accessible under agreed conditions, a loan must follow its sanctioned terms, and customer information must be handled within applicable requirements. Compliance connects those daily promises to the laws, regulations, supervisory directions and conduct standards governing the institution. A profitable transaction can still create serious compliance exposure if its design, sale, execution or reporting breaches an applicable obligation. Conversely, an honest mistake needs investigation and correction without automatically being labelled fraud.

Consider an original branch example. A product brochure correctly explains an account charge, but the software applies that charge to an exempt customer category. The brochure is evidence of intended design; the transactions reveal failed implementation. The branch should stop or contain the continuing error through authorised action, identify affected customers, preserve records, escalate the problem and arrange appropriate remediation. Compliance helps interpret the obligation and challenge the response. Operations owns execution, technology fixes the rule, and independent assurance later checks whether the remedy worked. This division of labour is the central idea of the chapter: everyone must comply, while a dedicated function provides oversight, advice, testing and escalation.

2. Compliance risk and related risks

Compliance risk concerns adverse consequences of failing to observe applicable obligations. These consequences can include supervisory action, legal sanctions, financial loss and damage to confidence. It overlaps with operational, legal and reputational risk, but the labels answer different questions. Operational risk examines failures of people, processes, systems and external events. Legal risk concerns rights, enforceability and legal outcomes. Reputation describes how customers and other stakeholders perceive the bank. Compliance asks whether the institution identified and met the requirements governing its conduct. A single event may need all these perspectives without being counted repeatedly as several independent losses.

Suppose a lending platform omits a mandatory disclosure because a software field was removed. The system change is an operational cause; the omitted obligation is a compliance failure; complaints and proceedings create legal and reputational consequences. An analyst should identify the underlying event, affected population, duration, obligation and control weakness before assigning categories. Do not infer that an absence of penalties proves an absence of risk. A breach may remain undiscovered or unpenalised while customers continue to suffer. Equally, the existence of a complaint is a signal to investigate, not proof that the bank violated a requirement. Good analysis separates allegation, evidence, conclusion and corrective action in the issue record.

3. Establish the applicable rulebook

Before applying a rule, identify the regulated entity, activity, jurisdiction and relevant date. A commercial bank, a small finance bank and an NBFC may operate similar customer journeys but fall under different directions. A bank distributing insurance also needs to consider requirements relevant to that activity. Group membership does not erase the separate obligations of each legal entity. A useful obligation register records the source, provision, effective date, applicability reasoning, responsible owner, required control, evidence and review frequency. It also records exclusions and interpretation questions, so a convenient assumption does not silently become institutional policy.

The current-practice reference for this chapter is RBI's Commercial Banks: Compliance Function Directions issued on 31 July 2026. Its defined commercial-bank scope excludes small finance banks, payments banks and local area banks; learners must not extend every prescription automatically to those categories. The IIBF syllabus has a separate examination cutoff convention. For examinations from March to August, the published convention refers to developments up to the preceding December end; for September to February, it refers to June end. Consequently, July 2026 material is labelled a current-practice update here rather than silently treated as examinable for every sitting. Read the applicable examination notice alongside this lesson. A current operational obligation and a syllabus cutoff can legitimately refer to different dates.

4. Policy, procedure and programme

A compliance policy states the institution's position: the authority of the function, expected conduct, responsibilities, independence, escalation arrangements and oversight. A procedure translates that position into repeatable steps for a particular task. A programme organises the planned work across the institution: risk assessment, monitoring, testing, regulatory change, training, reporting and follow-up. Confusing these levels produces familiar weaknesses. Each level needs ownership and an update mechanism.

For example, the policy may require timely escalation of material breaches. The procedure explains who records an incident, what information is mandatory, which channel is used, and what happens if the primary recipient is unavailable. The programme tests a sample of incidents, checks whether escalation worked, analyses recurring causes and reports improvements. A practical review asks four questions: does the document identify an obligation; can staff follow it; does the system support it; and can the bank demonstrate that it operated? Include version numbers and effective dates on operational instructions. When a procedure changes, retire obsolete copies and assess whether older transactions need correction. Merely emailing the new version does not establish implementation or understanding.

Turn obligations into evidenceClockwise: identify requirements, assign implementation, test actual operation, and report and verify remedies. Circulation alone is not implementation.Turn obligations into evidenceIdentifySource, scope and dateImplementOwner, procedure, systemRemediateReport, correct, verifyTestActual outcomes and gaps→↓←
Clockwise: identify requirements, assign implementation, test actual operation, and report and verify remedies. Circulation alone is not implementation.

5. Principles that make the function effective

Independence means the function can reach and communicate an unfavourable conclusion without being controlled by the business whose conduct it examines. Competence means staff understand both the requirements and the activities to which they apply. Authority means they can obtain records, question assumptions and escalate concerns. Resources mean adequate people, information and systems. Accountability means business owners remain responsible for compliant execution. These principles reinforce one another: a nominally independent team with no access to transaction data cannot provide meaningful challenge, and a well-resourced team whose appraisal depends on sales may hesitate to report failures.

Use a simple counterfactual test. If a product is commercially successful but has a material disclosure defect, can compliance insist on investigation and appropriate restriction without obtaining permission from the sales head? Can it report disagreement through a protected route? Can it explain the defect in operational terms and evaluate the proposed remedy? Independence does not mean isolation or habitual obstruction. Early advice can help teams build compliant products more efficiently than late rejection. However, collaboration should not turn the compliance team into the owner of revenue targets or the substitute operator of every control. The Basel Committee's compliance principles offer a useful conceptual background; Indian entity-specific directions determine the applicable local requirements.

6. Board and senior-management oversight

The Board establishes expectations and oversees whether the institution has an effective compliance framework. Senior management implements the framework, assigns resources, addresses failures and ensures that business decisions reflect applicable obligations. These are different responsibilities. A Board need not verify every customer file, but it should receive information sufficient to challenge systemic weaknesses and unresolved material breaches. Management cannot discharge its responsibility by stating that a compliance department exists. Reports should make visible the severity, age, recurrence and customer impact of issues, together with responsible owners and realistic corrective milestones.

Under the cited 2026 commercial-bank directions, the compliance policy is reviewed annually, and the Board or Audit Committee reviews the function quarterly with a detailed annual review. The lesson is not to memorise a meeting count without understanding the work. A committee pack containing only the number of circulars circulated gives little assurance. A better pack identifies important regulatory changes, significant testing results, overdue remediation, repeated failures and capacity constraints. Minutes should capture decisions and challenge, not merely that a presentation was noted. An item can be administratively marked complete while its underlying weakness persists; oversight should therefore ask what evidence supports closure and whether later testing confirms that the fix continues to operate.

7. Structure from head office to branches

A bank needs an enterprise view of obligations and a practical route to the people executing them. Head-office compliance coordinates interpretation, risk assessment, monitoring standards and reporting. Business and support departments implement controls in their own processes. Field compliance arrangements connect local activity to central oversight. Branch staff should know where to seek clarification and how to report a problem, including one involving their own manager. Organisational charts are useful only when supported by working information flows, defined authority and enough time for designated officials to perform their responsibilities.

Imagine a recurring account-opening exception across twelve branches. If each branch sends a separate informal email, central compliance may see isolated mistakes rather than a shared process defect. A common issue taxonomy and central register reveal that the same onboarding instruction was misunderstood everywhere. The remedy then includes a revised instruction, system validation, targeted training and review of affected accounts. Local managers still own correction of their records. Central compliance monitors the pattern and challenges completion evidence. Internal audit later assesses the framework independently. A small institution can adopt proportionate arrangements, but proportionality does not mean that inconvenient obligations disappear or that the same person may perform conflicting duties without scrutiny.

8. Chief Compliance Officer: stature and appointment

The CCO leads the function and requires sufficient stature to challenge senior colleagues. Appointment should be supported by a documented assessment of integrity, experience, knowledge and ability to exercise independent judgement. A prestigious title alone does not establish these qualities. The selection record should explain why the candidate can understand the bank's activities, interpret requirements, manage a capable team and communicate difficult findings. Succession planning matters because a prolonged vacancy or abrupt loss of expertise can weaken oversight precisely when the institution is changing products or systems.

The cited commercial-bank directions include a minimum three-year fixed tenure and prescribe experience and seniority conditions. Their age condition is not a simple universal ban on appointments after 55: the text contains a qualification concerning continuous association with compliance before that age. Read that qualification before answering a rule-based question. The experience prescription includes fifteen years overall in banking or financial services and at least five years in specified control-related fields. These bank-specific requirements must not be copied automatically into the NBFC chapter. Appointment and premature changes also involve prescribed RBI intimation and internal governance steps. Prior intimation to a supervisor and prior approval by the Board are different concepts; replacing one phrase with the other changes the requirement.

9. Reporting lines and conflicts of interest

Reporting arrangements should allow the CCO to raise an issue even when senior business management disagrees. Direct access to the Board or its Audit Committee provides an important safeguard. Where the CCO reports to the chief executive, protected interaction with the oversight body helps prevent material matters from being filtered. Independence also depends on appraisal, remuneration, information access and committee roles. A reporting arrow on an organisation chart cannot neutralise a financial incentive to suppress bad news or a practice of denying access to relevant records.

Consider two proposed assignments. Asking the CCO to advise a product committee about disclosure obligations is consistent with challenge. Making the CCO jointly responsible for achieving the product's sales target creates a conflict, because the person would assess compliance in activity for which they are commercially rewarded. Similarly, operational sanction responsibility can conflict with independent oversight of the sanction process. The 2026 directions restrict conflicting dual roles and treat participation in conflicting committees as advisory where permitted. Some compatible responsibilities may be possible, but compatibility must be evaluated rather than assumed from convenience. A sound conflict assessment identifies the decisions involved, incentives, reporting route and safeguards. It should be revisited when the business or role changes, not filed once and forgotten.

10. Regulatory change as an operating process

Regulatory change management begins with identifying an authoritative publication and determining whether it applies. It then moves through interpretation, impact assessment, allocation, implementation, testing and closure. The due date must be distinguished from the date on which someone forwarded the circular. Equally, a change may require amendments to customer communications, software, contracts, training and reports, rather than a single policy update. The change record should identify these dependencies and the evidence required from each owner.

Suppose a new disclosure requirement applies to a particular channel. Compliance interprets the requirement with legal input where needed. Product management changes the customer journey; technology updates the screen and stored record; operations revises exception handling; training reaches frontline staff. Testing checks real examples, including failed transactions and alternative language screens. The accountable owner signs off supported by evidence, and compliance challenges whether coverage is complete. A dashboard should distinguish not applicable, assessed, implementation in progress, testing failed and verified complete. Treating every item as either open or closed conceals important differences. If interpretation remains uncertain, record the question and obtain clarification through the appropriate route instead of converting uncertainty into an undocumented exemption.

11. New products and compliance testing

New products can change the bank's obligations even when the underlying financial instrument looks familiar. A new distribution channel may introduce different consent, disclosure, outsourcing, recordkeeping or customer-support risks. Compliance review should occur before launch, when changes are still practical. It should examine who the customer is, what is promised, how the transaction is processed, which parties handle data and money, how exceptions are resolved and what evidence will remain. A product approval paper should document unresolved conditions and the person authorised to determine whether launch can proceed.

The cited bank directions require intensive monitoring of new products during their first six months. This is not a reason to stop monitoring on the next day; later monitoring should reflect continuing risk. An original testing plan might examine the first cohort of customers, failed journeys, unusual overrides and complaints, then compare results across branches and channels. Compliance testing asks whether specified requirements and controls operated. It differs from merely checking whether staff completed a training module. A useful test states its objective, population, selection method, evidence, exception definition and limitations. If an exception appears, investigate its cause and possible wider reach.

12. Reporting, remediation and sustainable closure

A useful issue report states the requirement, observed condition, evidence, affected population, consequence and proposed response. Avoid vague statements such as documentation needs improvement. Instead describe which document or control was missing, in how many tested cases, over what period, and why it matters. Separate confirmed findings from matters still under investigation. Escalation should reflect severity and urgency; a material ongoing customer-impact issue should not wait for the next routine reporting cycle simply because the standard spreadsheet is submitted monthly.

Remediation has several layers. Immediate containment limits further harm. Correction addresses affected transactions or customers. Root-cause action changes the process, system, incentives or capability that produced the failure. Verification checks that the action actually works. Sustainable closure requires all relevant layers, not merely an owner's statement that staff have been advised. Suppose twenty customers received an incorrect charge. Reversing those charges corrects known cases, but the bank must also identify the full affected population and fix the charging logic. Later testing should confirm correct treatment. If a deadline is missed, the issue remains visible with reasons and escalation. Internal approval of a delay does not itself extend a statutory deadline or remove a reporting obligation.

13. Technology, data and useful measures

A compliance workflow can connect requirements, controls, tests, incidents and actions. Its value comes from reliable definitions and evidence, not from the number of coloured charts. Access should follow role and need, while changes to findings and closure decisions should leave an audit trail. Sensitive customer or whistleblower information should not be displayed indiscriminately on management dashboards. The system should help the bank see its actual position, including overdue and disputed items, rather than reward teams for making the screen look green.

The interactive exercise uses an illustrative weighted completion measure. If high-priority actions carry weight three and routine actions weight one, completing eight of ten high-priority actions and fifteen of twenty routine actions gives weighted completion of (8 × 3 + 15) / (10 × 3 + 20), or 78%. The unweighted figure is 23 / 30, approximately 76.67%. Neither number proves compliance or permits the remaining actions to be ignored. A single unresolved critical obligation may outweigh a favourable average. The weights are teaching assumptions, not RBI risk weights. Use the calculation to understand denominator choice and reporting distortion, then review severity, age, evidence and customer impact separately before drawing any management conclusion.

Weighted completion needs contextHigh-priority: 8 × 3 = 24 completed weight from 30. Routine: 15 from 20. Total 39/50 = 78%; remaining critical obligations still matter.Weighted completion needs contextIllustrative action weights24High complete30High total15Routine done20Routine total
High-priority: 8 × 3 = 24 completed weight from 30. Routine: 15 from 20. Total 39/50 = 78%; remaining critical obligations still matter.

14. Integrated branch case

Riverview Bank launches an original illustrative deposit package through branches and an app. Two months later, complaints indicate that some eligible customers were charged an account fee. The product team says the brochure was approved and asks compliance to close the matter because the total amount is small. A good response begins by identifying the actual eligibility rule and comparing it with transaction logic. The complaint count is not the affected population. The review should include both channels, relevant dates, reversals already made and cases where customers did not complain.

Operations arranges authorised containment and customer correction; technology fixes and tests the rule; the product owner updates guidance if necessary. Compliance challenges scope, monitors remediation and escalates material concerns. Internal audit does not become the developer of the replacement control merely because it may later review the response. Closure evidence includes population reconciliation, verified corrections, tested logic and follow-up results. If management disputes materiality, the record should show both the financial amount and the nature of the obligation and customer impact. A small monetary total does not automatically make a systematic conduct failure immaterial. The case demonstrates how policy, programme, testing, reporting and governance operate together rather than as separate examination definitions.

15. Revision and decision discipline

For revision, reconstruct the compliance cycle without looking at the headings: identify obligations, allocate responsibility, design controls, implement, monitor, test, report and verify corrective action. Then explain why business ownership, compliance oversight and independent audit must remain distinguishable. Ask whether a proposed measure describes activity, outcome or assurance. Circulars circulated and training attendance are activities; fewer repeat defects and timely verified corrections are more informative outcomes; independent testing provides evidence about reliability. No single measure captures the whole framework.

In an examination case, first identify the entity and the date of the rule. Next locate the actual failure: interpretation, design, execution, evidence, escalation or closure. Choose the response that addresses that failure while preserving independence and accountability. Avoid answers that transfer every responsibility to the CCO, equate profit with compliance, treat a dashboard score as approval or close issues solely on verbal assurances. For numerical questions, write the numerator, denominator and weights before calculating. Finally, distinguish the original educational examples in this chapter from binding requirements. The reference register records the retrieved source versions, and the current-practice boxes identify later developments. This disciplined approach supports both accurate exam reasoning and better decisions in a real branch or control function.

Open the interactive chapter exercise and offline practice

LEARN THROUGH EXPLANATIONS

Chapter practice

This practice is separate from timed mock tests. Answers and explanations appear after you choose an option.

Your reading progress

Sign in to save your progress across devices.

Browse published timed tests for this paper