Bank branch audit: empanelment and the audit process.

What is a bank branch audit?

A bank branch audit is a statutory audit of an individual branch of a bank — most commonly a public sector bank — conducted by a Chartered Accountant firm empanelled for the purpose, as part of the bank's overall annual statutory audit. Unlike a company statutory audit, the branch auditor doesn't get to choose the client: appointment flows through the ICAI–RBI bank branch audit empanelment system, and the audit itself covers a narrower, more specialised scope centred on advances quality, income recognition and asset classification.

For most practicing CAs, bank branch audit work is seasonal — concentrated in the weeks after 31 March each year — and is often one of the first significant assurance engagements a young partner or qualified assistant leads independently.

The empanelment process, in plain language

Empanelment is renewed every year, not once. Broadly, the cycle runs like this:

Your category on the panel (broadly linked to firm constitution, number of full-time partners, and points earned from continuing professional experience including prior bank audit exposure) determines which class of branches — small, medium, or large — you're eligible for. The exact category definitions, point weightages and application dates change from year to year in ICAI's empanelment circular, so always verify the current criteria and dates on the ICAI empanelment portal and RBI's latest guidelines before you apply — don't rely on a previous cycle's numbers.

What a bank branch audit actually covers

The scope is narrower than a typical statutory audit but far deeper in specific areas — advances above all. A typical engagement covers:

NPA classification and provisioning is usually where the audit earns its fee. RBI's Income Recognition and Asset Classification (IRAC) norms fix classification largely by objective triggers — most importantly, how many days an account has been overdue — so the auditor's job is to independently test the branch's own classification against those triggers, not simply accept the branch's system output. Where classification is wrong, income recognised on that account and the provisioning held against it are both wrong, so a single missed NPA can flow through several numbers in the branch return at once.

The LFAR (Long Form Audit Report) is submitted in addition to the audit opinion on the branch financials. It is a structured, largely questionnaire-format report addressing credit appraisal quality, documentation gaps, fraud indicators and general control observations — a format RBI and the bank prescribe afresh each year, so use the current cycle's LFAR proforma rather than a prior year's.

Worked example: a single advance account

A branch has a cash-credit account with a sanctioned limit of ₹50,00,000. On the audit date, the outstanding balance is ₹48,00,000 and the account has been continuously overdue (interest not serviced) for more than the period that triggers sub-standard classification under IRAC norms — say, past the 90-day threshold. The branch's system still shows it as "standard."

• Reclassification: the auditor reclassifies the account from standard to sub-standard.
• Provisioning impact: a standard advance typically carries a small general provision (illustratively 0.40%, i.e. ₹19,200 on ₹48,00,000); a sub-standard advance requires a materially higher provision rate (illustratively 15% on the secured portion, i.e. ₹7,20,000 if fully secured) — a swing of roughly ₹7,00,800 in additional provisioning the auditor must report.
• Income reversal: any interest already recognised as income after the account became a non-performing asset must be reversed out of the branch's income for the period, not just adjusted going forward.

The provisioning percentages above are illustrative to show the mechanics only — always apply the exact IRAC provisioning rates and classification triggers current for the audit year, from RBI's master circular/directions in force at that date.

Practical notes for a practicing CA

• Plan the sample before the branch closes. The field-work window after 31 March is short; deciding your advances sample, LFAR document list and cash/fixed-asset verification approach in advance is what makes the timeline workable.
• Don't accept the branch's own NPA flagging at face value. Independently recompute days-past-due and check for restructuring, evergreening (fresh disbursement used to service old dues) and technical adhoc sanctions that mask an overdue account.
• Cross-check drawing power against the latest stock/book-debt statement — a stale statement inflating drawing power is one of the most common branch-audit findings.
• Read the current year's LFAR format carefully before starting field work — questions, thresholds and certificates requested do shift year to year.
• Rotation and cooling-off rules apply to branch auditor appointments; confirm your firm isn't within a cooling-off period for a particular bank before accepting an appointment.
• Document everything contemporaneously. Given the compressed timeline, working papers written up after the fact are where quality-review findings usually originate.

Frequently asked questions