Skip to main content
Home › Indian Laws › Banking Regulation Act, 1949 › Section 29A
Banking Regulation Act, 1949 · Section guide

Section 29A: Power in respect of associate enterprises

Reviewed by CA Nikhil Gupta · Last reviewed 18 September 2026

Section 29A — Power in respect of associate enterprises. Extends RBI information/inspection reach to associate enterprises of a banking company where necessary for consolidated. Supervision; the bank and associate should maintain records that allow RBI to trace group exposures and transactions.

Official statute linkedProvision-specific anatomyPractical case + evidence file
Official text: DFS consolidated Act

Statutory structure and provision map

This map is a provision-specific explanation, not a substitute for the exact statutory text.

Core statutory rule

Extends RBI information/inspection reach to associate enterprises of a banking company where necessary for consolidated supervision.

Condition / limitation

the bank and associate should maintain records that allow RBI to trace group exposures and transactions.

Source and effective-date control

Apply the wording of Section 29A that was in force on the event date; use the official Act and any applicable commencement/amending instrument linked on this page.

Professional application

Explain associate-enterprise information/inspection powers, scope and confidentiality; define the covered entities.

Evidence / working-paper checklist

  • Section 29A evidence: general-ledger / treasury reconciliation.
  • Section 29A evidence: return or financial statement submitted to RBI/Registrar.
  • Section 29A evidence: auditor sign-off or working papers where relevant.
  • Section 29A evidence: filing acknowledgement and calculation of the statutory reference date.

Retain the event date and source version with the file so the conclusion remains reproducible after later amendments.

Common mistakes to avoid

  • For Section 29A, avoid using a legacy Friday/fortnight reference after the statutory date changed.
  • For Section 29A, avoid submitting a return without a ledger reconciliation.
  • For Section 29A, avoid assuming an extension exists without a written statutory/RBI basis.

Current-law source control

Source control: Section 29A is anchored to the official DFS consolidated text; later changes require separate Gazette verification.

Dated matters: verify any later Gazette, RBI direction or binding judgment affecting Section 29A on the event date.

Professional reading note

Professional reading note — Section 29A should be applied as a sequence, not as an isolated heading. Start with the factual trigger

for power in respect of associate enterprises, then test the operative proposition: Extends RBI information/inspection reach to associate enterprises of a banking

company where necessary for consolidated supervision. Next confirm the limiting or interaction point: the bank and associate should maintain records that allow

RBI to trace group exposures and transactions. The working file should be capable of showing why the section applies to the relevant

bank or person, which statutory version governs the event date, and which documentary record proves the conclusion. Useful evidence on this page

includes Section 29A evidence: general-ledger / treasury reconciliation and Section 29A evidence: return or financial statement submitted to RBI/Registrar. Read the provision

in sequence with Section 28 — Power to publish information and Section 29 — Accounts and balance-sheet. This method keeps the legal

answer tied to the provision itself while allowing RBI directions, rules and later instruments to be layered on only where their own

scope actually applies.

Disclaimer

This Finin2min page is an educational and professional reference. Banking regulation is fact-, entity- and date-sensitive. Verify the current Act, Gazette amendments and commencement notifications, applicable RBI Rules/directions and the transaction record before acting or filing.