Form 60 & 61: Tips for Indian Finance

Form 60 & 61: Tips for Indian Finance

Form 60 is a written declaration submitted by a person without a Permanent Account Number (PAN) before completing any specified high-value transaction listed under Rule 114B of the Income Tax Rules, 1962. Form 61 is the half-yearly return that the receiving institution then files on the Income Tax Reporting Portal, consolidating every Form 60 collected during that six-month window. For FY 2026-27, with Annual Information Statements (AIS), Statement of Financial Transactions (SFT) filings, and PAN-Aadhaar integration all operating at full depth, Form 60 and Form 61 are live audit triggers — not administrative paperwork.

Why Form 60 Exists: The Rule 114B Backbone

Rule 114B of the Income Tax Rules, 1962 specifies a list of transactions in which every person — individual, HUF, company, or firm — must quote their PAN at the time the transaction occurs. The rationale is straightforward: the tax department needs a way to track high-value movement of money even when it flows through unregistered or low-income channels.

When a person enters into one of these transactions without a PAN — because their income is below the taxable limit, or because they have genuinely never applied — they submit Form 60 in lieu of a PAN. Form 60 acts as a surrogate identifier: it captures the person's name, address, Aadhaar number (or enrolment ID), the nature of the transaction, the amount, and a declaration that their income either does not exist or has not exceeded the basic exemption limit.

The institution receiving Form 60 does not process it and move on. It retains the original, digitises it, and six months later bundles all such declarations into Form 61 for the Income Tax Department. Every Form 60 you collect creates a data point that will eventually surface in AIS — even if the declarant never acquires a PAN.

Which Transactions Require a PAN or Form 60?

The categories below are the most common under Rule 114B as applicable for FY 2026-27. If CBDT has issued a specific amendment notification for AY 2027-28, use the revised threshold.

Banking and deposits:

• Opening any bank account other than a Basic Savings Bank Deposit (BSBD) account
• Cash deposit of Rs. 50,000 or more in a single day into any bank account — savings, current, cash credit, or fixed deposit
• Aggregate cash deposits of Rs. 2,50,000 or more in a financial year in a savings bank account

Investments:

• Purchase of mutual fund units for Rs. 50,000 or more in a single transaction
• Purchase of shares from a company for Rs. 1,00,000 or more, or debentures/bonds for Rs. 50,000 or more
• Purchase of Reserve Bank of India bonds for Rs. 50,000 or more

Property and vehicles:

• Sale or purchase of immovable property valued at Rs. 10 lakh or more
• Sale or purchase of any motor vehicle (other than a two-wheeler), regardless of price

Insurance and payments:

• Payment of life insurance premium exceeding Rs. 50,000 in a financial year to any insurer
• Payment of Rs. 50,000 or more in cash for hotel or restaurant bills
• Cash payment of Rs. 25,000 or more toward foreign travel — airfares, package tours, or foreign currency purchase

Demand drafts and pay orders:

• Purchase of bank drafts, pay orders, or banker's cheques for Rs. 50,000 or more in cash in a single day

Other high-value cash transactions:

• Sale or purchase of goods or services for Rs. 2,00,000 or more per transaction in cash (not otherwise covered above)

Any institution facilitating one of these transactions must collect either a valid PAN card or a duly filled Form 60. There is no third option.

How to Fill Form 60 Correctly: Step-by-Step

Form 60 has three functional parts. Work through each at the counter while the declarant is present — corrections after the fact create far more paperwork than doing it right the first time.

Part A — Personal identification:

1. Full name as per Aadhaar or an officially valid document (OVD)
2. Date of birth (or date of incorporation for non-individual entities)
3. Father's or mother's name (for individuals)
4. Complete address with district, state, and PIN code
5. Mobile number or email, if available

Part B — Transaction details:

1. Nature of transaction — select the applicable Rule 114B category
2. Exact amount of transaction in rupees
3. Date of transaction
4. Name and address of the counterparty (the bank branch, dealer, or registrar)

Part C — Aadhaar and income declaration:

1. Declarant's statement that they do not hold a PAN
2. Estimated annual income and whether it exceeds the basic exemption limit for FY 2026-27
3. Aadhaar number — mandatory where Aadhaar has been allotted. If Aadhaar has been applied for but not yet received, enter the 14-digit Aadhaar Enrolment ID in the format XXXX/XXXXX/XXXXX
4. If the declarant has neither Aadhaar nor an Enrolment ID, attach a copy of one OVD: passport, voter identity card, driving licence, or NREGA job card

Verification: Signed (or thumb-impressed in the presence of a responsible official) by the declarant. The institution's authorised signatory counter-signs where the format requires it.

Training tip for front-desk staff: Audit Part C specifically every time. A Form 60 without an Aadhaar number (or Enrolment ID) and without any OVD attached is incomplete. The Reporting Portal will flag it as a deficiency when Form 61 is filed, which then requires a correction filing — avoidable effort that compounds across hundreds of declarations.

Worked Example: Opening a Fixed Deposit Without PAN

Facts: Rajamma Devi, age 64, a retired agricultural labourer from Warangal, approaches a district co-operative bank to open a fixed deposit of Rs. 80,000. She draws a monthly state government welfare pension of Rs. 1,50,000 per year — well below the basic exemption limit for FY 2026-27. She has an Aadhaar card but has never applied for a PAN.

At the counter:

1. The bank officer confirms no PAN exists.
2. Rajamma fills Part A (name, address, date of birth), Part B (time deposit of Rs. 80,000, date, bank branch details), and Part C (Aadhaar number, income declaration).
3. She signs the declaration. The officer keeps the original and hands her a photocopy.
4. The officer assigns a serial number from the branch's Form 60 register and opens the fixed deposit.
5. The bank digitises the declaration within 48 hours.

Six months later: This transaction falls in the April–September 2026 half-year. By 31 October 2026, the bank consolidates Rajamma's Form 60 along with every other declaration collected in that period and uploads Form 61 to the Reporting Portal.

Rajamma's Rs. 80,000 deposit now sits in the tax department's database, linked to her Aadhaar. If she applies for a PAN next year and acquires one, AIS will reflect this deposit automatically. Her income is below the taxable limit, so there is no tax consequence — but the data trail is clean and complete, protecting both her and the bank.

What Is Form 61 and Who Must File It?

Form 61 is the half-yearly return filed by reporting entities to submit all Form 60 declarations collected during a period. Entities required to file include:

• Banking companies, co-operative banks, and post offices accepting deposits
• Registrars or sub-registrars under the Registration Act (property transactions)
• Dealers in motor vehicles
• Mutual funds
• Companies issuing shares, debentures, or bonds
• Insurance companies
• Hotels and restaurants accepting cash payments above thresholds
• Authorised dealers in foreign exchange

Each such entity must register on the Reporting Portal and obtain an ITDREIN (Income Tax Department Reporting Entity Identification Number) — a 16-character alphanumeric code that tags every Form 61 submission. ITDREIN registration is a one-time activity; once obtained, it is reused for all subsequent filings.

Filing Form 61 on the Reporting Portal: Step-by-Step

The Reporting Portal is accessible at report.insight.gov.in. The following steps apply to the April–September 2026 half-year filing.

Step 1 — Register your ITDREIN (one-time) Log in to the Income Tax e-filing portal at incometax.gov.in using the entity's PAN credentials. Navigate to "Pending Actions → Reporting Portal" and register as a reporting entity under the relevant SFT/Form 61 category. The system generates your ITDREIN immediately.

Step 2 — Prepare your data file Consolidate all Form 60 declarations received between April 1 and September 30, 2026. For each declaration you need: declarant name and address, Aadhaar number or Enrolment ID, nature and amount of transaction, date, and your register serial number. Most core banking systems and dealer management software can export this in the NSDL-prescribed XML schema for Form 61. If yours cannot, the Reporting Portal provides an offline utility to prepare and validate the XML manually.

Step 3 — Validate before uploading Use the Reporting Portal's offline validation tool to run your XML through a format check before submitting. This catches Aadhaar format errors, missing mandatory fields, and schema mismatches — problems that are far easier to fix before submission than after.

Step 4 — Upload and submit Log in at report.insight.gov.in with your ITDREIN credentials. Select "Form 61 — Statement of Form 60 Declarations." Upload the validated XML. The portal generates an acknowledgment number immediately. Record this number in your compliance register — it is your primary evidence of timely filing.

Step 5 — Monitor and respond to deficiency notices The portal processes uploads and may issue deficiency notices for incomplete or inconsistent data. You have a defined correction window to file a revised Form 61. Address every deficiency promptly and retain the revised acknowledgment number as well.

Due dates — FY 2026-27:

Nil returns: If your entity collected zero Form 60 declarations in a half-year, file a nil Form 61 anyway. It takes under ten minutes and prevents the department from assuming you simply failed to file.

Worked Example: Penalty Calculation for a Late Form 61

Facts: A motor vehicle dealer in Nagpur collected 14 Form 60 declarations during April–September 2026. Form 61 was due on 31 October 2026. Due to a staff handover, the accounts team missed the deadline and eventually filed on 10 January 2027 — a delay of 71 days.

The Assessing Officer issued a notice on 20 November 2026 directing the dealer to file within 15 days, i.e., by 5 December 2026. The dealer did not comply by that date.

Penalty calculation under Section 271FA:

• Period 1 (before notice deadline): 1 November to 5 December 2026 = 35 days × Rs. 500 = Rs. 17,500
• Period 2 (post-notice-deadline): 6 December 2026 to 10 January 2027 = 36 days × Rs. 1,000 = Rs. 36,000
• Total penalty: Rs. 53,500

Now suppose two of those 14 Form 60 declarations contained incorrect Aadhaar numbers (a data-entry transposition). Each inaccurate statement attracts Rs. 50,000 under Section 271FAA — an additional Rs. 1,00,000.

Total exposure for a 71-day delay and two data errors: Rs. 1,53,500.

This dealer's entire back-office oversight failure was preventable with a calendar reminder and a one-hour XML validation step.

Penalties Under Section 271FA and Section 271FAA

Section 271FA — Late or non-filing:

• Rs. 500 per day from the due date until the date of actual filing
• Escalates to Rs. 1,000 per day once the window given in the AO's notice expires without compliance

Section 271FAA — Inaccurate information in Form 61:

• Rs. 50,000 flat for each statement containing inaccurate particulars — not per incorrect record, but per inaccurate statement filed

Reasonable cause defence under Section 273B: Penalties under both sections can be waived if you prove reasonable cause. Examples the department has accepted include:

• Documented technical downtime on the Reporting Portal (retain screenshots and NSDL helpdesk ticket numbers)
• Genuine uncertainty about whether an unusual transaction type falls under Rule 114B, corrected promptly once clarified
• First-time minor format errors cured through a timely revised filing with full supporting documentation

What does not constitute reasonable cause:

• Claiming unawareness of the compliance obligation
• Staff turnover without documented knowledge transfer
• Simultaneous involvement in an unrelated audit or litigation

Common Mistakes and Pitfalls to Avoid

Conflating Form 60 with KYC

Form 60 satisfies the Income Tax Act's PAN-quoting requirement under Rule 114B. It does not replace Know Your Customer (KYC) obligations under the Prevention of Money Laundering Act, 2002 (PMLA) and RBI Master Directions on KYC. Both frameworks must be satisfied independently. A bank that accepts Form 60 in lieu of KYC documentation is exposed on two fronts simultaneously.

Leaving the Aadhaar field blank

Many legacy Form 60 templates in circulation pre-date the mandatory Aadhaar amendment. If the declarant holds an Aadhaar number, it is mandatory on the form. Submitting Form 61 with blank Aadhaar fields for declarants who do possess Aadhaar generates deficiency notices and potential penalty exposure under Section 271FAA.

No running serial-number register

Without a numbered register at each branch or outlet, you cannot reconcile how many Form 60 declarations you received against what you report in Form 61. Gaps will surface when your Form 61 data is cross-matched against SFT submissions for the same period.

Filing Form 61 without offline validation

Uploading directly without running the offline utility first risks portal-level rejection of the entire batch — eating into your filing window and potentially pushing you past the due date.

Skipping the nil return

An entity that collected no Form 60 declarations and therefore did not file Form 61 may receive a deficiency notice from the Insight system. A nil filing closes the loop in under ten minutes.

Allowing transactions to proceed without Form 60

Some branch staff, to reduce paperwork at busy counters, permit Rule 114B transactions to proceed when the customer has no PAN and has not filled Form 60. This exposes the institution — not just the customer — to penalty under Section 271FA as a reporting entity that failed in its collection obligation.

Integration with AIS, SFT and the Broader Tax Ecosystem

Form 60 data submitted through Form 61 is ingested into the Annual Information Statement (AIS) accessible to the declarant and the department alike through the Insight platform. The implications are significant:

1. A transaction reported via Form 60/61 is visible to the tax department even without a PAN attached to it at the time.
2. When the declarant later acquires a PAN — or when the department links their Aadhaar to a PAN through de-duplication — the historical transaction resurfaces in AIS and the taxpayer must reconcile it in their return for that year or subsequent years.
3. For reporting entities, Form 61 data is cross-matched against the Statement of Financial Transactions (SFT) filed for the same period. If your SFT reports 60 cash deposits above Rs. 50,000 but your Form 61 shows only 18 Form 60 declarations, the Insight system will flag a gap. The remaining 42 transactions should all have corresponding PAN records — be ready to demonstrate this linkage.

Practical reconciliation check before filing: Before you upload Form 61, run a report from your core banking system or dealer management software: list every transaction in the half-year that met any Rule 114B threshold, separate those where a valid PAN was collected, and the remainder should exactly equal your Form 60 count. Any discrepancy means either a Form 60 is missing from your register or a PAN-linked transaction was miscategorised.

For CA advisors serving individual clients: If you have a client who once filed a Form 60 declaration (say, when opening an account at a time they had no PAN), check their AIS/TIS at incometax.gov.in under the AIS tab to see whether those historical transactions now appear and whether they have been auto-mapped to the client's current PAN. Unreconciled entries in AIS can generate system-triggered scrutiny notices.

Encouraging Form 60 Declarants to Apply for a PAN

Any individual who files Form 60 repeatedly — especially for transactions like vehicle purchases or property registrations — is building a growing trail in the tax department's database. The department uses this information to profile likely taxpayers, and repeated Form 60 filings without an eventual PAN application can attract enquiry letters under Section 133(6).

PAN application through Protean (formerly NSDL) or UTIITSL takes fewer than 15 working days under normal circumstances and costs under Rs. 200 for Indian applicants. Some co-operative banks and CSC centres now assist with PAN application at the time Form 60 is collected.

For reporting entities, reducing the stock of Form 60 filers over time is a tangible efficiency gain — every declarant who gets a PAN in Year 1 is one fewer Form 60 to collect, digitise, and report in Years 2, 3, and beyond. Consider making a one-page PAN application guide available at every Form 60 collection point.

Key Takeaways

• Form 60 is filed by a person without PAN at the time of a Rule 114B transaction; it must capture Aadhaar where allotted — verify this at collection, not at filing time.
• Form 61 is the half-yearly return of all collected Form 60 declarations, filed by reporting entities at report.insight.gov.in using an ITDREIN.
• FY 2026-27 due dates: 31 October 2026 for the April–September half-year; 30 April 2027 for the October–March half-year.
• Penalty exposure is compounding: Section 271FA runs at Rs. 500–Rs. 1,000 per day; Section 271FAA adds Rs. 50,000 per inaccurate statement — a 71-day delay with two bad records can cost over Rs. 1.5 lakh.
• Form 60 ≠ KYC: Both regimes must be satisfied independently; conflating them is one of the most common and most costly audit triggers.
• Nil returns close the compliance loop: File even when no Form 60 was collected to prevent system-generated deficiency notices.
• AIS is the long memory: Every Form 60 trail the department holds will eventually be linked to a PAN or Aadhaar — clean records protect both the institution and the declarant.