Home › Circulars › RBI/2011-12/407

Lead Bank Responsibility for New District Panchsheel Nagar

Current · Source: Reserve Bank of India · RBI/2011-12/407 · issued 22 Feb 2012 · ~1 min read
Quick answerRBI assigns Syndicate Bank as lead bank for the newly formed Panchsheel Nagar district in Uttar Pradesh, effective September 28, 2011. The district, carved from Ghaziabad, includes Hapur, Garh Mukteshwar, and Dhaulana tehsils. No other district lead bank changes.
The rule, in the simplest words
How it plays out — a real example

The officer at Syndicate Bank's Hapur branch works with the farmer to understand his needs and creates a plan to help him get a loan. The officer then reports the loan application to the district's lead bank office, using the district working code 313, as required by RBI rules. A branch operations officer in Hapur helps a local farmer get a loan to buy new farming equipment.

What changed

The Government of Uttar Pradesh created Panchsheel Nagar district on September 28, 2011, with headquarters at Hapur, from parts of Ghaziabad district. RBI has now assigned Syndicate Bank as the lead bank for this new district. The district has been given working code 313 for reporting purposes.

What it means for you

Syndicate Bank must now coordinate banking development and credit planning in Panchsheel Nagar, including preparing district credit plans and monitoring priority sector lending. Other banks operating in the district will need to align with Syndicate Bank's lead bank role. This assignment does not affect lead bank responsibilities in any other Uttar Pradesh district.

What you must do

Who it affects

Syndicate Bank (lead bank for Panchsheel Nagar), All banks operating in Panchsheel Nagar district, Banks previously covering Ghaziabad district (now reduced in area), Uttar Pradesh state-level bankers' committee

❓ Common questions

Regulatory timeline

Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).

What is the effective date of this lead bank assignment?

The new district was formed on September 28, 2011, and the lead bank assignment is effective from the date of this circular, February 22, 2012.

Which tehsils are included in Panchsheel Nagar?

The district comprises three tehsils: Hapur, Garh Mukteshwar, and Dhaulana.

Does this change affect lead bank responsibilities in other Uttar Pradesh districts?

No, there is no change in lead bank responsibilities for any other district in the state.

📜 Read the original circular — full text as issued by RBI
RBI/2011-12/407 RPCD.CO.LBS. BC.No. 8377 /02.08.01/2011-12 February 22, 2012 The Chairmen/CMD All Lead Banks Dear Sir/Madam, Formation of new district – Panchsheel Nagar in the State of Uttar Pradesh Assignment of Lead Bank responsibility The Government of Uttar Pradesh vide their Gazette Notifications No. 2877/1-5-2011-153/2-11-R-5 & 2878/1-5-2011-153/2011-R-5 dated September 28, 2011 has advised about the constitution of a new district viz. Panchsheel Nagar with effect from September 28, 2011. The new district with its headquarter at Hapur has been carved out from the existing Ghaziabad and comprises of three Tehsils viz. Hapur, Garh Mukteshwar & Dhaulana. 2. It has been decided to assign the lead bank responsibility of the new district Panchsheel Nagar to Syndicate Bank. There is no change in the lead bank responsibilities of other districts in the State. 3. The newly formed district Panchsheel Nagar has been allotted District working code "313" for the purpose of reporting. Yours faithfully, (Deepali Pant Joshi) Chief General Manager-in-Charge
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2011-12/407 · issued 22 Feb 2012. The plain-English explanation above is BankPulse’s own independent summary.
🧰 Tools — save, print, templates & related
Most relevant forSenior Management / BoardBusiness Head / Vertical HeadBranch Manager — Private Bank / SFBBranch Operations (Accounts / FD / CASA)Compliance TeamData Science / Analytics
🛠 Banker’s toolkit — checklists & reply templates →
Related circulars · Financial Inclusion & Priority Sector
Small Account Rules for Co-operative Banks – RBI Circular 2011RRB CRR Hiked to 9% from Aug 30, 2008CRR Hiked for RRBs by 50 bps in Two StagesRRBs: PMLA Compliance – CTR, STR, and KYC Software MandateRRB CRR Hiked to 8.25% from May 24, 2008
Browse all departments →
Who does what — compliance checklist
💻 IT / Systems
  • Banks should update internal systems to reflect the new district boundaries and lead bank arrangements.
📜 Compliance
  • Syndicate Bank should immediately establish lead bank office in Hapur and initiate district credit plan preparation.
  • All banks in Panchsheel Nagar must report data using district working code 313.
  • Syndicate Bank to convene first District Consultative Committee meeting at the earliest.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template

Example: if you are a Compliance officer at a bank this circular applies to (Syndicate Bank (lead bank for Panchsheel Nagar), All banks operating in Panchsheel Nagar district, Banks previously covering Ghaziabad district (now reduced in area), Uttar Pradesh state-level bankers' committee), your first concrete step on “Lead Bank Responsibility for New District Panchsheel Nagar” is: “Syndicate Bank should immediately establish lead bank office in Hapur and initiate district credit plan preparation.” (RBI issued this 22 Feb 2012).

  1. Circular: RBI/2011-12/407 -- Lead Bank Responsibility for New District Panchsheel Nagar
  2. Issued: 22 Feb 2012
  3. Action required: Syndicate Bank should immediately establish lead bank office in Hapur and initiate district credit plan preparation.
  4. Action required: All banks in Panchsheel Nagar must report data using district working code 313.
  5. Action required: Banks should update internal systems to reflect the new district boundaries and lead bank arrangements.
  6. Action required: Syndicate Bank to convene first District Consultative Committee meeting at the earliest.
  7. Owner: ____________ Target date: ____________
  8. Board/committee approval needed? Y / N
  9. Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.

💬 Banker Discussion

Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.

Loading comments…
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly).
Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=7020&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
—