Long Form Audit Report in Bank Statutory Audit: CAAP Guide

For candidates preparing for the Certified Accounting and Audit Professional exam, the Long Form Audit Report is one of the most practical — and most tested — deliverables a bank statutory auditor produces. Unlike the main audit opinion, the LFAR is a detailed, clause-by-clause commentary telling bank management exactly where controls, documentation and asset quality fall short. Its structure matters for both the exam and real branch audit assignments.

📋 What Is the Long Form Audit Report and Why It Matters

The Long Form Audit Report is a structured questionnaire-style report that a bank's statutory auditor submits in addition to the main audit report on the financial statements. While the main report expresses an opinion on whether the financial statements give a true and fair view, the LFAR goes several layers deeper — commenting specifically on internal controls, credit appraisal, documentation of advances, cash management, deposit operations, and compliance with statutory requirements at the branch or bank level.

The format traces back to guidance developed jointly by the banking regulator's audit expectations and the accounting profession's own standard-setting body, and is the accepted template statutory auditors of Indian banks follow every year.

💡 Exam Tip: Remember the LFAR is a supplementary report, not a substitute for the main audit report — questions often test this distinction directly.

Because the LFAR is addressed to management and the board rather than published with the annual accounts, it functions as a confidential diagnostic tool, flagging weaknesses that may not justify qualifying the main opinion but still warrant corrective action and follow-up in the next audit cycle.

🏦 LFAR Format: Branch-Level vs Head Office-Level Reporting

The LFAR exercise operates at two distinct levels, and candidates frequently confuse the two. The branch-level LFAR is prepared by the statutory branch auditor for each branch (or a representative sample, depending on the bank's audit coverage policy) and covers matters entirely within that branch's operations. The Head Office (bank-level) LFAR, by contrast, is prepared by the central statutory auditors and covers matters that cannot be assessed at any single branch.

A branch auditor is not expected to comment on bank-wide capital adequacy or investment portfolio management in the branch LFAR; those items belong to the central auditors' bank-level report. Exam questions often test whether a candidate can slot a given observation into the right level.

⚠️ Common Mistake: Students often assume every branch gets its own LFAR every year — coverage is usually risk-based and follows the bank's own branch audit selection policy.

🔍 Key Clauses Auditors Must Cover in the Branch LFAR

The branch LFAR proforma is organised into broad heads, and a CAAP candidate should be comfortable naming each one. It typically opens with general questions on the branch's accounting system, computerisation, and whether the branch maintains proper books in accordance with the bank's own manual of instructions.

The advances section is usually the most detailed part of the report, asking the auditor to comment on credit appraisal, sanction terms, documentation completeness, security valuation, and classification under the income recognition framework. Cash, deposits and borrowings each get their own questions covering physical verification, interest computation and reconciliation.

Beyond the transactional heads, the branch LFAR covers contingent liabilities such as guarantees and letters of credit outstanding at the branch, and a residual "other items" clause for anything material that does not fit elsewhere — unusual suspense entries, old inter-branch outstandings, or lapses management should know about.

Auditors are expected to answer each clause specifically, with a descriptive comment wherever a deficiency exists, rather than a blanket satisfactory remark that adds no diagnostic value.

⚠️ Common LFAR Reporting Gaps and Their Audit Implications

In practice — and in exam scenarios — several recurring gaps show up in branch LFAR responses. The most frequent is superficial commentary: ticking "satisfactory" against a clause without describing the test performed, which defeats the report's purpose and can attract criticism in the audit firm's own peer review process.

A second common gap is failing to cross-reference LFAR observations with the main audit report. If a branch has documentation deficiencies in advances that affect classification, that fact should be consistent between the LFAR clause and any qualification in the main report — an inconsistency between the two is a red flag reviewers look for.

• Not commenting separately on each contingent liability category (guarantees, LCs, forward contracts) with meaningful exposure.
• Treating the LFAR as an end-of-fieldwork formality rather than building observations into it throughout the audit.
• Not following up on the prior year's LFAR observations to check whether management actually remediated them.

Because the LFAR often surfaces the control weaknesses behind larger asset-quality problems, generic responses can mask issues that later show up as unexpected slippage or supervisory findings.

📆 LFAR Timelines, Submission Process, and RBI/ICAI Guidance

The LFAR is prepared alongside the statutory audit and submitted together with the main audit report, following the timetable the bank communicates to its branch and central auditors. Rather than a fixed universal day-count, auditors should follow the specific submission schedule the appointing bank prescribes for that financial year, since banks coordinate these deadlines to close their year-end accounts on time.

The guidance note shaping the current LFAR proforma is maintained by the accounting profession's standard-setting body and is periodically revised to reflect RBI's evolving supervisory priorities — for instance, added emphasis on cyber-related controls or digital lending exposures gets folded into the questionnaire over time. Auditors should always use the version current for the year under audit, not an outdated template.

📌 Remember: The LFAR is a management-facing report — it is not published with the bank's annual financial statements, but its findings can feed directly into supervisory review.

Once submitted, LFAR observations are typically compiled centrally and placed before the audit committee, giving management a structured view of control gaps across branches.

🧠 Practice MCQs: Long Form Audit Report

Want chapter-wise mock tests with 100+ MCQs? Start practising free →

❓ Frequently Asked Questions

Ready to master LFAR clauses for the CAAP exam?

Mapping what belongs in the branch LFAR versus the Head Office LFAR is one of the highest-yield preparation steps for this subject. Pair this guide with Introduction to Audit for the foundational framework, Risk Based Internal Audit Procedures to see how internal audit findings connect to LFAR clauses, and Audit Aspect of Inter Office Transactions for the reconciliation items behind the "other items" clause. Branch auditors verifying forex contingent liabilities should also review FEMA provisions for bankers.

For related reading, see our guides on the joint audit of bank branches, the going concern assumption in bank audit, and consolidated financial statements of banks. Browse more CAAP topics on the tag hub, and check supervisory guidance directly from the Reserve Bank of India and the auditing-standards guidance from the Institute of Chartered Accountants of India.