Income-tax Act, 2025 – Section 85: Dempo Override, GST Exposure & Industrial Unit Sale Risks

 By CA Surekha Ahuja

Executive Summary: A Structural Shift, Not a Routine Amendment

The Income-tax Act, 2025 (effective April 1, 2026) introduces Section 85 (in place of Section 54EC), materially changing the capital gains exemption framework.

• The trigger shifts from “transfer of a long-term capital asset” to “long-term capital gains arising”
• This change effectively neutralizes the position flowing from V.S. Dempo & Co. Pvt. Ltd. v. CIT, where long-term holding enabled LTCG treatment even for depreciable assets
• Under the new regime, depreciable assets (plant & machinery) continue to be governed by Clause 75 (successor to Section 50) and are taxed as short-term capital gains

Practical Consequence

• Higher tax incidence in mixed-asset industrial transfers
• Removal of bond-based exemption for depreciable components
• Parallel exposure under Section 85 of the CGST Act (joint liability)

This represents a shift from asset-based eligibility to gain-character determination.

Legislative Mechanics: The “Two-Word Shift”

Parameter	Earlier Framework (Section 54EC)	Revised Framework (Section 85)
Trigger condition	Transfer of long-term capital asset	Long-term capital gains arise
Position post-Dempo	LTCG possible even for depreciables	Not relevant under new trigger
Governing principle	Holding period of asset	Character of gain (Clause 75)
Relief availability	₹50 lakh bond exemption	Not available for depreciables

Interpretation:
The amendment does not expressly overrule Dempo; however, by modifying the statutory trigger, it changes the outcome prospectively without disturbing the judicial precedent.

Industrial Unit Sale: Comparative Tax Position

Illustration: ₹5 crore industrial unit
(₹3 crore land + ₹2 crore machinery; holding period: 5 years)

Position under Earlier Framework

• Land → LTCG (approx. ₹60 lakh tax post indexation)
• Machinery → LTCG benefit through bonds (approx. ₹40 lakh tax)
  Total tax outflow: ~₹1 crore

Position under Section 85

• Land → LTCG (approx. ₹60 lakh)
• Machinery → STCG taxable at applicable slab rates (approx. ₹60 lakh)
  Total tax outflow: ~₹1.2 crore

Corporate Structure Considerations

Where the transfer is undertaken through a company:

• Corporate tax (~25%)
• MAT implications (where applicable)
• Taxation at distribution stage

This may lead to a higher effective tax burden depending on structure and profit distribution strategy.

GST Section 85: Joint and Several Liability Risk

Under Section 85 of the CGST Act:

Upon transfer of business, the transferor and transferee are jointly and severally liable for pre-transfer GST dues.

Key Implications

• Liability includes tax, interest, and penalties
• Exposure may arise subsequently upon audit or investigation
• Contractual protections (indemnities) do not override statutory liability

Indicative Risk Areas and Controls

Risk Area	Exposure	Suggested Control
Absence of GST reconciliation	Undetected liabilities	Two-year audit review
ITC mismatches	Credit denial/blockage	ITC mapping and validation
Partial business transfers	Allocation disputes	Asset-level documentation
Non-amendment of registration	Continuing liability	Timely GST updates

Section 50C: Industrial Property Considerations

Section 50C continues to apply subject to:

• Safe harbour for variation within prescribed limits
• Non-applicability in case of stock-in-trade
• Relief in specific cases such as SEZ/STP allocations (subject to conditions)
• Valuation challenge through registered valuer reports

Practical Insight:
Proper segregation between land and depreciable assets is critical to mitigate unintended tax consequences.

Tax Regime Considerations (FY 2026–27)

Parameter	New Regime	Old Regime
STCG	Slab rates (higher basic exemption)	Slab rates
LTCG	12.5% (without indexation)	20% (with indexation)
Deductions	Limited	Available

Approach:
The choice should be based on asset composition, deduction availability, and overall tax position, rather than a uniform preference.

Transition Timeline

• Up to March 31, 2026 → Existing provisions continue
• From April 1, 2026 → Section 85 becomes applicable
• FY 2026–27 → First year of application
• Return filing for FY 2026–27 → Due July 2027

Illustrative Exposure Matrix

Unit Type	Earlier Tax Position	Revised Position	GST Exposure	Overall Impact
Land only	Comparable	Comparable	Low	Neutral
Mixed assets	Moderate	Higher	Medium	Increased
Plant-heavy units	Higher	Significantly higher	High	Substantial
Slump sale	Variable	Higher	Elevated	Material

Planning Considerations

Pre-April 2026

• Evaluate timing of proposed transfer
• Undertake GST reconciliation
• Obtain valuation bifurcation (land vs plant)

Post-April 2026

• Consider asset segregation strategies
• Evaluate restructuring or reinvestment options
• Align transaction structuring with combined tax and GST exposure

Conclusion

Section 85 represents a recalibration of capital gains taxation:

• Restricts exemption benefits for depreciable assets
• Elevates the importance of transaction structuring
• Introduces concurrent GST exposure requiring parallel diligence

For industrial and MSME transactions, integrated tax and GST planning at the structuring stage is now essential.

A combined income-tax and GST review prior to any business transfer is critical to manage exposure and optimise outcomes.

MSME Form 1 Compliance Due 30.04.2026

Legal & Practical Guidance Note - High-Risk Compliance, Tax Exposure & Governance Control

MSME Form 1 is a statutory disclosure return under the Companies Act, 2013, requiring companies to report MSME (Micro and Small) dues outstanding beyond 45 days. It is not merely a procedural filing—it is a payment discipline and compliance transparency mechanism that directly interacts with MSMED Act obligations and Income-tax disallowance under Section 43B(h).

For the half-year ended 31 March 2026 (due 30 April 2026), companies must ensure invoice-level accuracy and MSME vendor validation, as this disclosure is increasingly used for regulatory and tax cross-verification.

Is MSME Form 1 Mandatory?

Yes — it is mandatory, but only for covered entities.

MSME Form 1 is compulsorily required under Section 405 of the Companies Act, 2013 when:

• The company has transactions with Udyam-registered Micro or Small enterprises, and
• Any payment is:
  • outstanding beyond 45 days from acceptance, OR
  • unpaid as on reporting date

Key clarification:

• It is not a universal filing for all companies
• It is trigger-based reporting, not optional disclosure

 If MSME dues exist beyond 45 days, filing becomes statutorily mandatory

Legal Framework (Core Risk Linkage)

• Section 405, Companies Act, 2013 → Mandatory information return to MCA
• Section 15, MSMED Act, 2006 → Payment within 45 days
• Section 43B(h), Income-tax Act, 1961 → Expense disallowance for delayed MSME payments

Core principle:

A delayed MSME payment is simultaneously:

• a MCA disclosure item,
• a statutory interest liability, and
• a tax deduction risk

Due Date

Period	Cut-off	Due
Apr–Sep	30 Sep	31 Oct
Oct–Mar	31 Mar	30 Apr

Current cycle: Half-year ended 31.03.2026 → Due 30.04.2026

What Must Be Reported

• MSME vendor details (Micro/Small only)
• Invoice-wise outstanding position
• Payments beyond 45 days
• Unpaid balances as on reporting date
• MSMED interest liability
• Reason for delay

Why This Compliance Is High Risk (Even If No Immediate Penalty)

Even where no immediate penalty is imposed at filing stage, MSME Form 1 remains critical because:

• It is a statutory obligation under Section 405
• It is used for MCA risk profiling and scrutiny selection
• It directly impacts Section 43B(h) tax disallowance
• It can trigger audit and governance observations

Legal reality:

• Liability arises on non-compliance itself, not on detection
• Enforcement may be delayed, but default is automatic once breached

Key Risk Areas

• Wrongly applying contract credit terms instead of 45-day rule
• Missing MSME tagging in accounting system
• Ignoring opening MSME balances
• Non-reconciliation with books/GST
• Missing Udyam validation

Tax Impact (Critical)

If MSME payment exceeds 45 days:

• Expense becomes disallowable in the same year under Section 43B(h)
• Even if paid before year-end

 Direct impact on taxable income and cash flow planning

MSMED Interest Exposure

• Interest: 3× RBI bank rate
• Applies automatically on delay
• Mandatory disclosure in MSME Form 1

MSME Form 1 due on 30.04.2026 is mandatory wherever MSME overdue exposure exists beyond 45 days.

It is not a routine filing—it is a statutory audit of your MSME payment discipline with direct tax consequences.

The real compliance test is not filing MSME Form 1 on time,
but ensuring no MSME invoice silently crosses the 45-day legal threshold in the first place.

Cash Donations in Temples & Trusts: No Change in Limits, But Strict Scrutiny under Income-tax Act, 2025

 Same Limits. Stronger Enforcement.

By CA Surekha Ahuja

Cash continues to flow through temples, gurudwaras and charitable institutions—via donation boxes, pranami and langar contributions.

But under the current tax framework, cash is no longer informal—it is a monitored compliance area.

Compliance today depends on system design, not intent.

No Change in Limits

• ₹2,000 per cash donation
• ₹2,00,000 per person per day (receipts)
• ₹10,000 per person per day (payments)

There is no change in thresholds under the Income-tax Act, 2025.

However, enforcement has strengthened through:

• data analytics
• system-based validation
• AI-driven scrutiny

The law remains the same. Enforcement does not.

Three Non-Negotiable Triggers

• High-value cash donations must be avoided
• Aggregation per donor must be controlled
• Cash payments must remain minimal

These are not limits to track—they are limits to build your system around.

What Well-Managed Institutions Do

• Donation boxes handle only small offerings
• Larger contributions are routed through banking channels
• Cash payments are restricted and documented

They do not eliminate cash—they discipline it.

Minimum Compliance System

• Accept only small-value cash
• Shift higher donations to non-cash immediately
• Segregate funds (donation / pranami / langar / project)
• Record and deposit donation box collections properly
• Restrict cash payments to petty expenses only

Professional Recommendations

• Treat thresholds as hard operational caps
• Build controls at the point of transaction
• Avoid idle cash—deposit and utilise timely
• Maintain consistent documentation
• Conduct periodic internal reviews

Red Flags

• Large cash donations
• High or frequent cash payments
• Absence of donation box records
• Mixing of funds
• Unexplained cash balances

Conclusion

The shift is clear:

From recording transactions → to controlling transactions

Thresholds didn’t change. Surveillance did.
If your system allows a breach, your compliance is already at risk.

 

Form No. 121 (FY 2026–27) Guide with Procedure, Penalties, AIS Reconciliation & Zero-Risk Compliance Strategy

 By CA Surekha Ahuja

Replacing Forms 15G and 15H under the Income-tax Act, 2025

Introduction: From Declaration to Data-Driven Tax Compliance

With effect from 1 April 2026, Form No. 121 replaces Forms 15G and 15H. This change marks a decisive shift from a declaration-based system to a data-driven, traceable compliance framework.

Each declaration is now:

• Tagged with a Unique Identification Number (UIN)
• Reported by the payer against its TAN
• Linked to the taxpayer’s PAN
• Reflected in system-based reporting such as TDS statements and AIS

The objective is clear: eliminate mismatches between income reporting, TDS data, and tax returns at a PAN–TAN level.

Legal Framework and Objective

Form No. 121 is prescribed under:

• Section 393(6) of the Income-tax Act, 2025
• Rule 211 of the Income-tax Rules, 2026

It enables eligible persons to declare that their estimated total income results in nil tax liability, allowing the payer not to deduct tax at source on specified payments.

Core Principle: Nil Tax Liability

The declaration is valid only where:

• Total income is properly estimated
• Deductions and rebates are considered
• Correct tax regime is applied
• Final tax liability is nil

This makes Form 121 a computation-based declaration, not a threshold-based formality.

Eligibility Position

Category	Eligibility
Resident Individuals	Eligible where tax liability is nil
Senior Citizens	Eligible where tax liability is nil
Hindu Undivided Family	Eligible where tax liability is nil
Firms / LLPs	Not eligible
Companies	Not eligible
Non-residents	Not eligible

Income Covered

The declaration applies to a wide range of incomes:

• Interest income
• Dividend income
• Mutual fund income
• Rental income
• Insurance commission
• Life insurance proceeds
• Provident fund withdrawals and pension receipts
• Other specified payments

Procedure and Mode of Filing

By the Taxpayer (Declarant)

Form No. 121 is not directly filed on the income-tax portal by the taxpayer.

It is furnished as a declaration to the payer:

• Before the scheduled transaction date
• Separately for each payer
• For each financial year

Modes:

• Physical submission, or
• Electronic submission (if enabled by payer)

By the Deductor (Payer)

The payer is responsible for system integration:

• Digitization of declaration (if physical)
• Generation of UIN
• Filing of Part B electronically on the portal
• Reporting in Quarterly TDS Statement (Form 140)

UIN and PAN–TAN Level Tracking

Each declaration is tracked through a 26-character UIN:

Component	Description
Sequence Number	D + 9 digits
Tax Year	Example: 202627
TAN	Payer’s TAN

This creates a three-way linkage:

• PAN of taxpayer
• TAN of deductor
• UIN of declaration

AIS, TDS and ITR Reconciliation: Government’s Core Objective

The introduction of Form 121 is closely aligned with the Government’s broader objective of data consistency and mismatch elimination.

How the System Works

• Declarations (Form 121) are reported by the payer
• Transactions are captured in TDS returns (Form 140)
• Data flows into the taxpayer’s Annual Information Statement (AIS)
• Taxpayer files Income-tax Return (ITR)

Mismatch Scenarios Targeted

Scenario	System Risk
Income received without TDS but not declared in ITR	High mismatch trigger
Form 121 filed but income later taxable	Red flag in AIS vs ITR
Multiple declarations across payers without consistency	Data inconsistency
Incorrect PAN / UIN reporting	Reconciliation failure

Compliance Impact

• Increased automated scrutiny selection
• System-generated notices and alerts
• Higher audit visibility at PAN level

Form 121 is therefore not just a TDS tool—it is part of a data reconciliation ecosystem.

Consequences, Defaults and Penalties

Non-Filing of Form 121

• TDS is deducted
• Cash flow is impacted
• Refund only through return filing

Delayed Filing

• Not valid for that transaction
• TDS already deducted cannot be reversed

Incorrect Declaration (Tax Liability Not Nil)

• Tax becomes payable
• Interest liability arises
• Penalty for under-reporting or misreporting may apply
• In serious cases, prosecution provisions may be invoked

Non-Furnishing of PAN

• Declaration becomes invalid
• TDS at higher rate

Payer-Level Defaults

Default	Consequence
Failure to generate UIN	Reporting breakdown
Non-filing of Part B	Penalty exposure
Non-reporting in TDS return	AIS mismatch risk
Delay in compliance	Late fees

Caution Points for Taxpayers

• Compute total income from all sources before filing
• Do not rely only on exemption limits
• Ensure filing before transaction date
• Submit separate declarations for each payer
• Monitor income during the year
• Inform payer if tax position changes

Caution Points for Deductors

• Do not rely on incomplete declarations
• Ensure PAN validation
• Maintain UIN-wise control register
• File Part B within prescribed timelines
• Reconcile with TDS returns
• Maintain audit documentation

Dynamic Situations: Mid-Year Changes

If income increases during the year and tax becomes payable:

• Taxpayer should inform the payer
• TDS should be applied on subsequent payments

Failure to act may result in:

• Interest liability
• Penalty exposure
• Increased scrutiny risk

Practical Risk Matrix

Situation	Risk Level	Impact
Correct declaration	Low	Smooth compliance
Non-filing	Medium	Cash flow impact
Late filing	Medium	TDS unavoidable
Incorrect estimation	High	Tax + interest + penalty
False declaration	Very High	Penalty and prosecution risk

Professional Compliance Approach

For Taxpayers

• Estimate income carefully
• Compute tax accurately
• File only where tax liability is nil
• Maintain supporting working

For Deductors

• Maintain UIN records
• Ensure timely reporting
• Align Form 121 with TDS returns
• Maintain audit trail

Strategic Perspective

Form No. 121 represents a transition from:

Declaration-based compliance to PAN–TAN integrated data verification

This ensures:

• Reduced mismatches in AIS and ITR
• Improved tax transparency
• Stronger compliance monitoring

Conclusion

Form No. 121 is a powerful compliance mechanism, but it operates within a data-driven tax environment.

Correct usage ensures:

• No TDS deduction
• Efficient cash flow
• Clean tax reporting

Incorrect usage may result in:

• Tax liability
• Interest and penalties
• System-triggered scrutiny

Before furnishing Form No. 121, it is essential to confirm:

The estimated total income has been properly computed and results in nil tax liability, and that such position will remain consistent with reporting in AIS and ITR.

 

Airbnb Hosts India: Complete Compliance & Taxation Guide for FY 2026–27

 By CA Surekha Ahuja

GST | Income Tax Act 2025 | Rules 2026 | TDS/TCS | NIDHI | State Licensing | Zero-Default Framework

Hosting through Airbnb has evolved into a fully regulated, system-reported economic activity in India.

With the integration of:

• Income Tax Act 2025
• Income Tax Rules 2026
• Central Goods and Services Tax Act 2017

every transaction is now:

• Digitally recorded
• Automatically reported
• Cross-verified across tax and regulatory systems

This guide is structured as a practical compliance note, combining statutory provisions with real-world scenarios to ensure a zero-default approach for Airbnb hosts in India.

Core Tax & Compliance Position

Particulars	Unregistered Host	Registered Host
GST	Not required (<₹20L)	Mandatory (≥₹20L)
TCS	Not applicable	1% (GST)
TDS	0.1%*	0.1%
ITR Form	ITR-1 / ITR-2	ITR-3 / ITR-4
Income Head	House Property	Business/Profession

*5% if PAN not furnished

Turnover = Gross Airbnb receipts (including reimbursements) − refunds/cancellations

Transaction Flow – Practical Understanding

Example: ₹1,00,000 Booking

Particulars	Unregistered	Registered
Gross Booking	₹1,00,000	₹1,00,000
GST	Collected by Airbnb	Collected by Airbnb
TCS	Nil	₹1,000
TDS (0.1%)	₹100	₹100
Net Payout	₹99,900	₹98,900

Key Principle: Income must be reported on a gross basis, not net payout.

Role of the E-Commerce Operator

Airbnb acts as an E-Commerce Operator (ECO) and:

• Collects GST from guests
• Deducts TCS (if GST registered)
• Deducts TDS under income tax law
• Reports transactions to AIS and GST systems

Host responsibility = reconciliation and correct reporting

Income Tax Framework (FY 2026–27)

Under Income Tax Act 2025:

• TDS @ 0.1% on gross receipts credited
• TDS @ 5% where PAN not furnished

₹5 Lakh Threshold – Legal Interpretation

Condition	TDS Applicability
Individual/HUF + PAN + ≤ ₹5L receipts	Not deducted
Any condition not satisfied	TDS applicable

Reasoning:
This is a limited exemption provision, not a trigger threshold.

AIS-Based Compliance

Under Income Tax Rules 2026:

• Airbnb income is reflected in AIS
• ITRs are pre-filled
• Mismatches are system-flagged

AIS reconciliation is essential for compliance integrity

Income Classification: House Property vs Business

Decision Matrix

Indicator	Likely Classification
Passive renting	House Property
Multiple listings / frequent turnover	Business
Additional services (food/cleaning)	Business

Comparative Impact

Factor	House Property	Business
Deduction	30% standard	Actual expenses
Depreciation	Not allowed	Allowed
Audit	Rare	Possible

GST vs Income Tax vs Licensing – Integrated View

Aspect	GST	Income Tax	State Licensing
Trigger	₹20L turnover	Any income	Mandatory
Authority	GST Department	Income Tax Dept	Tourism/Local Authority
Basis	Turnover	Income/Profit	Property usage
Risk	Penalty + interest	Notice/scrutiny	Shutdown/delisting

GST Framework

Under Central Goods and Services Tax Act 2017:

• Registration required above ₹20 lakh
• Airbnb collects GST from customers
• TCS applies for registered hosts

 Filing obligations continue even where tax is offset through TCS

Government Homestay Ecosystem

Promoted by:

• Ministry of Tourism India
• NIDHI Portal

Policy Objective

• Monetisation of vacant residential capacity
• Formalisation of homestay sector
• Integration with tourism and compliance systems

NIDHI Portal – Functional Role

Requirement	Details
Registration	Centralised tourism database
Capacity	Max 6 rooms / 12 beds
Facilities	Clean rooms, water, electricity
Safety	Fire compliance
Validity	3 years

Optional but enhances credibility and visibility

State Licensing Requirements

Example: Uttar Pradesh

• Mandatory tourism registration
• Police verification
• Fire safety compliance
• CCTV and operational conditions

 Non-compliance may lead to:

• Business closure
• Platform delisting
• Regulatory action

Other States

• Delhi → Police NOC (foreign guests)
• Karnataka / Himachal / Rajasthan → Tourism registration
• All states → Fire NOC + FSSAI (if food services provided)

Practical Scenarios (High-Risk Areas)

Scenario	Correct Treatment
Co-hosting	Separate taxation
Partial personal use	Apportionment
Long-term stays (>1 month)	Possible GST variation
Multi-location hosting	Aggregate turnover applies
NRI host	FEMA + TDS implications

Compliance Timeline

Timeline	Action
Monthly (by 5th)	AIS & GSTR-2B reconciliation
Monthly (20/22)	GST filing
Quarterly	TDS verification (Form 16A)
Annual	ITR filing and e-verification

Penalty & Risk Matrix

Default	Consequence
AIS mismatch	Notice/scrutiny
GST delay	₹50/day + interest
PAN not linked	5% TDS
No state license	Shutdown risk
Incorrect classification	Reassessment

Documentation Checklist

• Airbnb statements
• Bank statements
• GST returns
• License/NOC approvals
• Fire/FSSAI compliance records

FAQs with Reasoning

Do I need GST below ₹20 lakh?
No, but turnover must be monitored for threshold crossing.

Why is TDS deducted even for small hosts?
To ensure transaction-level reporting under Income Tax Act 2025.

Why is AIS critical?
It reflects system-reported income—mismatch leads to notices.

How to determine income head?
Based on nature and scale of activity, not intention.

Is NIDHI registration mandatory?
No, but beneficial for visibility and compliance alignment.

Is state registration avoidable?
No—this governs legality of operations.

Zero-Default Compliance Checklist

✔ PAN linked with platform
✔ Airbnb income matches AIS
✔ GST threshold monitored
✔ State licensing completed
✔ Records maintained (minimum 6–7 years)

The primary compliance risk today is not tax liability, but mismatch between platform-reported data and filed returns.

Final Conclusion

Airbnb income in FY 2026–27 is:

• Digitally recorded
• System-reported
• Cross-verified

Compliance is no longer about disclosure—it is about accuracy and alignment.

A structured and compliant approach enables:

• Sustainable income generation
• Efficient tax planning
• Elimination of regulatory risk

 

TDS Compliance Guide (Updated 2026): Section 194-IA Property Transactions with March–April Split Payments

By CA Surekha Ahuja

Introduction

Section 194-IA of the Income-tax Act, 1961 mandates deduction of TDS at 1% on transfer of immovable property (other than agricultural land) where consideration exceeds ₹50 lakh. The obligation arises at the earlier of payment or credit to the seller.

A major procedural transition becomes effective from 1 April 2026, shifting from the traditional Form 26QB system to the integrated Form 141 regime. This creates a critical compliance sensitivity for split payment property transactions spanning March and April 2026, where dual reporting systems apply within the same transaction lifecycle.

Legal Framework and Transition from Form 26QB to Form 141

Particulars	Form 26QB (Up to 31 Mar 2026)	Form 141 (From 1 Apr 2026)
Structure	Challan-cum-statement	Unified pay + file system
Filing model	Separate payment and filing	Single integrated workflow
Trigger	Payment/credit date	Payment/credit date
Portal	e-Pay Tax → 26QB	e-Pay Tax → 141
Certificate	Challan acknowledgement	Form 132 (TRACES)
Scope	Property only	Property + rent + lease
Computation	Manual/system assisted	Fully auto-calculated

The decisive factor is the date of payment or credit, irrespective of agreement, registration, or possession.

Split Payment Rules for March–April 2026 Transactions

Payment Date	Applicable Form	Compliance Treatment	Consolidation
Up to 31 March 2026	Form 26QB	Legacy reporting	Not permitted
On/after 1 April 2026	Form 141	New regime reporting	Not permitted

Even if the transaction is a single sale deed, segregation is mandatory and non-negotiable.

Due Date Framework for Transitional Transactions

Transaction Period	Form	Due Date
March 2026 payments	Form 26QB	30 April 2026
April 2026 onwards	Form 141	30/31 May 2026

Timely compliance is critical as delays attract both interest and statutory fees.

Form 26QB Compliance Process (March 2026 Transactions)

• Login to Income Tax portal using PAN
• Navigate to e-Pay Tax → Form 26QB
• Enter buyer, seller, and property details
• System computes 1% TDS automatically
• Make payment and generate challan-cum-statement
• Preserve challan as primary compliance proof

This regime functions as a standalone challan-based compliance system without separate return filing.

Form 141 Compliance Process (From April 2026)

Step	Compliance Action
Login	Income Tax portal (PAN-based)
Selection	e-Pay Tax → Form 141
Schedule	Select Schedule B (Sec 194-IA)
Data entry	Buyer/seller/property details
Validation	System PAN + data verification
Computation	Auto 1% TDS calculation
Filing	Unified pay + submit
Output	Acknowledgment + TRACES linkage

Form 141 eliminates manual duplication by integrating payment + reporting + validation in a single workflow.

Key Compliance Risk Areas

Risk Area	Impact	Prevention
PAN mismatch	Rejection or demand notice	Validate PAN before payment
Mixing March & April payments	Invalid compliance structure	Strict segregation by date
Wrong form selection	Defective filing	Confirm cut-off date
NRI misclassification	Under-deduction risk	Apply Section 195 review
Missing fields	Filing failure	Pre-check compliance checklist

Rectification and Revision Mechanism

Form 141 does not allow direct editing after submission. Corrections must be made through:

• Revised return linked to original acknowledgment, or
• Jurisdictional Assessing Officer with supporting documentation

System updates reflect in downstream TRACES records post correction.

Penalty and Interest Framework

Default Type	Provision	Consequence
Late filing	Section 234E	₹200/day (subject to TDS cap)
Late deposit	Section 201(1A)	1.5% per month
Non/short deduction	Section 201(1A)	1% + 1.5% per month
Late reporting	Section 234H	Up to ₹5,000

Non-compliance escalates quickly into interest-heavy exposure, making timely filing essential.

Form 132 Certificate (TRACES) Process

Stage	Details
Generation	After Form 141 processing
Timeline	5–7 days typically
Portal	TRACES download section
Input	Acknowledgment + seller PAN
Output	ZIP file certificate
Password	Seller DOB (DDMMYYYY)

Form 132 acts as the final compliance validation document for seller credit.

End-to-End Compliance Flow (March–April 2026)

Stage	March Transactions	April Transactions
System	Form 26QB	Form 141
Filing deadline	30 April 2026	30/31 May 2026
Output	Challan	TRACES Form 132
Compliance nature	Legacy system	Unified system

Audit-Ready Compliance Checklist

• Sale agreement and payment trail maintained
• PAN validated before transaction execution
• Strict segregation of March and April payments
• Correct form selection as per cut-off date
• Timely filing within statutory due dates
• TRACES certificate downloaded and preserved
• Records retained for minimum 7 years

Conclusion

The transition from Form 26QB to Form 141 marks a significant evolution in India’s property TDS compliance framework, moving towards a unified, technology-driven reporting system.

However, the March–April 2026 overlap creates a high-sensitivity compliance window, where even minor errors in date classification can lead to interest, penalties, and defective filings.

A disciplined, date-driven compliance approach ensures fully audit-proof reporting under Section 194-IA, eliminating litigation risk and ensuring seamless seller credit under the evolving TDS ecosystem.