Pre-Registration GST Supplies & Later GSTR-1 Reporting: Where Compliance Ends and Risk Begins

By CA Surekha Ahuja

Can pre-registration supplies be reported in a later GSTR-1? Understand the legal position on GSTR-1 amendment, DRC-03, Reverse Charge, Section 9(5), retrospective registration, ITC visibility, and the safest GST compliance strategy.

A common GST dispute today arises where a supplier crosses the GST registration threshold earlier but obtains registration later with effect from a subsequent date. The issue becomes commercially sensitive where services are supplied through aggregators, digital platforms, or corporate customers that reimburse GST only if Input Tax Credit (ITC) appears in their GST records.

This creates a conflict between:

• actual tax liability,
• outward supply reporting,
• reimbursement recovery,
• and recipient-side ITC visibility.

The practical question usually becomes:

“Can earlier or pre-registration supplies be reported in a later GSTR-1 merely to create ITC visibility?”

Commercially convenient — yes. Legally safe — not always.

Because GST law distinguishes between:

• correcting a reporting mistake, and
• changing the actual period of supply itself.

That distinction is the foundation of the entire issue.

The Real Issue Is the Time of Supply

The controversy is fundamentally not just about amendment of returns. It is primarily a “time of supply” issue.

If services were actually rendered earlier, GST liability ordinarily belongs to that earlier period itself.

A later registration date does not automatically convert earlier supplies into later-period supplies. Similarly, GSTR-1 amendment is generally intended for correcting reporting mistakes — not reconstructing transaction history merely to generate ITC visibility.

GST follows the real transaction timeline, not later compliance convenience.

Legal Foundation Behind the Issue

Provision	Core Principle
Section 22	Liability begins once threshold is crossed
Section 13	GST follows time of supply
Section 37	GSTR-1 is period-specific outward reporting

Accordingly, delay in obtaining registration does not automatically remove earlier GST exposure.

Why the Problem Becomes Commercially Difficult

The issue usually develops like this:

Practical Event	Commercial Consequence
Threshold crossed earlier	GST liability technically starts
Registration obtained later	Earlier supplies remain outside return chain
Customer/platform seeks ITC visibility	Reimbursement becomes conditional
Supplier wants GST recovery	Pressure arises for later reporting

This is where taxpayers begin considering:

• later-period reporting,
• invoice re-dating,
• fresh invoicing,
• or amendment-based ITC visibility creation.

However, each approach carries different levels of compliance risk.

What GSTR-1 Amendment Can Actually Do

GSTR-1 amendment is generally intended for correcting genuine reporting errors such as:

• incorrect GSTIN,
• invoice number errors,
• taxable value mismatch,
• duplicate reporting,
• omitted invoices,
• wrong tax rate,
• and place of supply mistakes.

These are reporting corrections.

What GSTR-1 Amendment Cannot Ordinarily Do

The amendment facility is not ordinarily intended for:

• changing the actual time of supply,
• converting historical supplies into current-period supplies,
• or creating artificial ITC visibility.

Once actual transaction chronology is altered merely to fit a later return cycle, the issue may move beyond correction into possible misreporting.

GST law permits correction of mistakes — not artificial reconstruction of transaction history.

The Most Overlooked Question: Who Was Actually Liable to Pay GST?

One of the biggest practical mistakes in such disputes is that taxpayers immediately focus on:

• GSTR-1 amendment,
• ITC visibility,
• or reimbursement recovery,

without first examining a far more important issue:

“Who was legally liable to pay GST in the first place?”

This analysis is extremely important because in some cases:

• the supplier may not have been liable at all,
• the recipient may have been liable under Reverse Charge,
• or the platform itself may have been liable under Section 9(5).

Therefore, before attempting amendment or later-period reporting, the original liability structure itself should first be examined carefully.

Can Reverse Charge Help?

Ordinarily, no — if the original transaction was taxable under Forward Charge.

Reverse Charge Mechanism (RCM) cannot generally be used merely because:

• registration was delayed,
• outward reporting was missed,
• or recipient-side ITC visibility is absent.

RCM applies only where:

• the law specifically notifies the transaction,
• the nature of service falls within notified categories,
• or the charging mechanism itself shifts liability.

Accordingly:

A transaction originally taxable under Forward Charge cannot ordinarily be converted into Reverse Charge merely to solve a later compliance issue.

Situations Where Reverse Charge or Section 9(5) May Matter

Situation	Possible Effect
Service already covered under RCM	Recipient itself may be liable
Import of services	GST may arise under RCM
Specific notified services	Liability may shift from supplier
ECO transactions under Section 9(5)	ECO itself may become deemed supplier

Why Section 9(5) Requires Careful Examination

In platform-based business models, Section 9(5) can materially alter the entire liability framework.

Under Section 9(5) of the CGST Act, certain notified services supplied through an Electronic Commerce Operator (ECO) become taxable in the hands of the ECO itself.

In such cases:

Position	Consequence
ECO treated as deemed supplier	ECO becomes liable to pay GST
Actual service provider	Liability may reduce or shift
Reporting structure	Entire compliance analysis changes

This becomes highly relevant in sectors involving:

• aggregators,
• app-based platforms,
• transport facilitation,
• accommodation services,
• and notified digital ecosystems.

Therefore, before adopting any amendment strategy, taxpayers should first examine whether:

• Reverse Charge applies,
• Section 9(5) shifts liability to the ECO,
• or supplier-side GST liability existed at all.

Because in many cases:

The real issue is not “how to amend the return,” but “who was legally liable to pay GST originally.”

Why Re-Dating Supplies Is Risky

Reporting earlier supplies in a later GSTR-1 may appear commercially convenient because tax ultimately gets paid.

However, GST law also focuses on:

• correct tax period disclosure,
• invoice chronology,
• matching architecture,
• and integrity of ITC flow.

Accordingly, later-period reporting may create:

Risk	Exposure
Wrong tax period reporting	Scrutiny
Artificial ITC visibility	Recipient dispute
Invoice mismatch	Audit objection
Misreporting allegation	Litigation exposure
Delayed payment	Interest liability

Time Limit for GSTR-1 Amendment

GSTR-1 amendment is time-bound.

Practically:

• corrections must be made within the statutory amendment window,
• delayed amendments may become unavailable,
• and expired periods cannot ordinarily be reopened indefinitely.

The amendment mechanism is therefore a correction facility — not an unrestricted historical editing tool.

GSTR-1 Amendment vs GSTR-1A

Particulars	GSTR-1 Amendment	GSTR-1A
Purpose	Correct filed data	Reconcile/alignment interface
Nature	Amendment mechanism	Adjustment/review workflow

In simple terms:

• GSTR-1 amendment corrects already filed outward supply data.
• GSTR-1A operates more as a reconciliation or alignment interface depending upon the GST framework.

Which Errors Are Usually Correctable?

Error Type	Usually Correctable
GSTIN error	Yes
Invoice number	Yes
Taxable value	Yes
Tax rate	Yes
Place of supply	Yes
Omitted invoice	Yes
Duplicate invoice	Yes

However, changing the actual supply period itself remains significantly more sensitive.

What Happens After Saving an Amended GSTR-1?

Stage	Effect
Amendment saved	Draft created
Not yet filed	No legal effect
Filed successfully	Outward data updated
System processed	GST chain updated

Saving is procedural. Filing creates legal and system effect.

The Safest Compliance Strategy

The most defensible route is usually transparent tax regularisation.Step 1 — Determine Actual Exposure

Prepare:

• invoice-wise reconciliation,
• threshold analysis,
• and period-wise liability mapping.

Step 2 — Determine Correct Liability Mechanism

Before payment, first examine:

• whether Forward Charge applied,
• whether Reverse Charge applied,
• whether Section 9(5) shifted liability to the ECO,
• and whether supplier-side GST liability actually existed.

This step is often ignored but is legally critical.

Step 3 — Regularise the Tax Liability

Where supplier-side liability genuinely exists, discharge:

• GST liability,
• applicable interest,
• and related dues.

Step 4 — Use DRC-03 Where Required

DRC-03 helps establish:

• voluntary payment,
• documentary evidence,
• and reconciliation trail.

However:

DRC-03 proves payment — it does not automatically create GSTR-2B visibility.

Step 5 — Explore Retrospective Registration Separately

Where facts genuinely support earlier liability, retrospective registration may sometimes help.

However, it remains:

• discretionary,
• fact-dependent,
• and officer-driven.

It should therefore be treated as supportive relief and not a guaranteed cure.

Commercial Reality: Reimbursement vs ITC

Platforms may commercially insist:

“No ITC visibility, no reimbursement.”

However, commercial reimbursement conditions do not automatically justify incorrect GST reporting.

A safer approach is often:

Alternative	Practical Benefit
DRC-03 challan	Proof of payment
Invoice reconciliation	Transaction clarity
Payment trail	Commercial support
Written reimbursement request	Documentary protection

Many reimbursement disputes can still be commercially resolved through strong documentary support even where automated ITC visibility does not arise.

What Should Generally Be Avoided

Approach	Why Risky
Re-dating invoices	Incorrect chronology
Showing old supplies as current supplies	Wrong tax period
Artificial ITC creation	High litigation exposure
Delaying tax payment	Interest and scrutiny risk

Practical Compliance Matrix

Compliance Option	Legal Strength	Risk Level
Proper tax payment with reconciliation	Strong	Low
DRC-03 regularisation	Strong	Low
Retrospective registration request	Moderate	Moderate
Later-period re-reporting	Weak	High
Artificial ITC creation strategy	Weak	Very High

FAQs on GSTR-1 Amendment & Pre-Registration Supplies

Can GSTR-1 be amended after filing?

Yes. Certain reporting mistakes can be corrected through amendment within statutory timelines.

Can amendment change the actual period of supply?

Ordinarily, no. Amendment is intended for correcting reporting errors, not changing transaction chronology.

Is DRC-03 enough for recipient ITC?

No. DRC-03 proves tax payment but does not automatically generate ITC visibility in GSTR-2B.

Can retrospective registration solve old GST issues?

Sometimes, depending on facts and departmental approval. However, it is not automatic.

Can pre-registration supplies be shown in later GSTR-1?

Ordinarily, not merely to create ITC visibility. Earlier supplies generally remain linked to the actual period in which they were made.

Final Conclusion

The safest GST strategy is usually the most transparent one:

• preserve the true time of supply,
• regularise liability properly,
• avoid artificial re-dating,
• maintain documentary reconciliation,
• and resolve reimbursement commercially through proof of payment rather than distorted reporting.

Before adopting any amendment-based strategy, taxpayers should first examine:

• whether Reverse Charge applies,
• whether Section 9(5) shifts liability to the ECO,
• whether retrospective registration is feasible,
• and whether reimbursement can be resolved without artificial ITC creation.

GSTR-1 amendment is fundamentally a correction mechanism for genuine reporting mistakes. It is not ordinarily intended to convert pre-registration supplies into later-period outward supplies merely to facilitate ITC flow.

In GST compliance, factual chronology still remains the strongest defence.

Section 140B vs Sections 234A, 234B & 234C- Whether CPC Can Continue Levy of Interest After Full Pre-Payment in ITR-U Cases

By CA Surekha Ahuja

A Legal and Interpretational Analysis of Updated Returns, Compensatory Interest and CPC Processing-Based Demands

“Compensatory interest survives only so long as Revenue remains deprived of the tax. Once the tax already stands discharged, the law must examine whether continued interest remains compensatory or becomes an unintended extension of levy.”

The levy of interest under Sections 234A, 234B and 234C in Updated Return (ITR-U) cases has emerged as one of the most important interpretational controversies under the Income-tax Act.

A recurring issue is now being witnessed across multiple ITR-U cases:

• Updated Return filed voluntarily under Section 139(8A),
• Entire tax, interest and additional tax paid before filing,
• No refund claimed,
• Yet CPC recomputes Section 234B interest till processing under Section 143(1), thereby generating fresh demands.

The dispute is not merely computational.

It concerns:

• the true scope of compensatory interest,
• interplay between Sections 140B and 234B,
• the effect of mandatory pre-payment under ITR-U,
• and whether automated processing can enlarge liability after complete discharge already stands made.

Statutory Structure of ITR-U

Section 139(8A) read with Section 140B

Unlike ordinary returns, an Updated Return cannot be furnished unless the assessee first pays:

• tax,
• interest,
• fee,
• and additional income-tax under Section 140B.

Thus, ITR-U operates as a mandatory pre-paid compliance framework.

Particulars	Ordinary Return	ITR-U
Filing without payment possible	Yes	No
Mandatory pre-payment	No	Yes
Additional tax payable	No	Yes
Refund claim allowed	Yes	No

Therefore:

By statutory design itself, Revenue already receives the taxes before the Updated Return legally comes into existence.

This distinction materially affects interpretation of Sections 234A, 234B and 234C.

II. Nature of Interest under Sections 234A, 234B & 234C

Judicial principles consistently recognise these provisions as substantially compensatory in nature.

Provision	Compensatory Basis
Section 234A	Delay in furnishing return
Section 234B	Shortfall in advance tax
Section 234C	Deferment of advance tax instalments

Thus, the underlying rationale remains:

Interest compensates Revenue for delayed receipt of taxes.

This principle becomes central in ITR-U cases where taxes already stand discharged before filing.

III. Section 234A — Filing-Centric Levy

Section 234A levies interest from:

From	To
Due date under Section 139(1)	Date of furnishing return

Accordingly:

Section 234A ordinarily terminates on furnishing of return and does not extend till processing under Section 143(1).

IV. Section 234C — Instalment-Specific Levy

Section 234C applies for deferment of advance tax instalments and operates within fixed statutory periods.

Characteristic	Position
Instalment linked	Yes
Processing linked	No
Fixed duration	Yes

Thus:

Section 234C ordinarily exhausts itself within the prescribed instalment framework itself.

V. Section 234B — The Core Controversy

Statutory Position

Section 234B broadly contemplates levy of interest:

From 1st April of the Assessment Year till determination under Section 143(1) or regular assessment.

This expression forms the basis of CPC’s computation mechanism.

VI. CPC’s Computational Interpretation

The CPC system generally follows a mechanical processing approach:

CPC Approach	Result
234B computed till processing/intimation	Yes
Processing date treated as terminal point	Yes
Independent contextual analysis of Section 140B	Generally absent

Consequently, demands arise even where:

• taxes stood fully paid before filing,
• additional tax already stood discharged,
• and no actual revenue deprivation survived thereafter.

VII. The Real Legal Question

The controversy is not whether Section 234B applies.

The real issue is:

Whether compensatory interest under Section 234B can continue on liabilities already discharged before filing ITR-U merely because CPC processed the return subsequently.

This distinction is critical.

VIII. Why the Taxpayer’s Interpretation Gains Strength

Section 140B Fundamentally Alters the Context

Under ordinary returns:

• taxes may remain unpaid till assessment.

Under ITR-U:

• taxes must mandatorily be paid before filing itself.

Thus:

By the time Updated Return is furnished, Revenue already possesses the taxes.

This substantially weakens the continuing compensatory basis for post-filing levy.

Additional Tax under Section 140B Already Protects Revenue

The Updated Return mechanism itself imposes additional income-tax:

Timing of Filing	Additional Tax
Earlier period	25%
Later period	50%

Thus, the statute already incorporates:

• revenue protection,
• delayed disclosure consequences,
• and additional compensatory burden.

Accordingly:

Mechanical continuation of Section 234B even after complete discharge may create overlapping compensatory consequences beyond the legislative scheme.

Compensatory Levy Cannot Ignore Actual Receipt of Revenue

The jurisprudential basis of interest provisions rests upon deprivation of taxes.

Situation	Compensatory Justification
Tax unpaid	Strong
Revenue deprived of funds	Strong
Taxes already discharged before filing	Substantially diluted

Therefore, the taxpayer’s strongest argument becomes:

Once taxes stood fully discharged before furnishing Updated Return, continuation of compensatory interest merely due to later CPC processing may amount to over-extension of levy beyond the period of actual revenue deprivation.

IX. Harmonious Construction of Sections 140B and 234B

A settled principle of interpretation requires statutory provisions to be read harmoniously and not in isolation.

Therefore:

• Section 234B cannot be interpreted divorced from Section 140B,
• particularly where Section 140B mandates complete prior discharge before filing itself.

A purely literal interpretation may therefore produce unintended and excessive consequences.

X. Revenue’s Technical Counter-Argument

Revenue may legitimately contend that:

Section 234B itself expressly refers to determination under Section 143(1).

Therefore, CPC’s computation is not entirely unsupported by statutory language.

This is precisely why simplistic assertions that CPC’s action is “clearly illegal” are technically unsafe.

XI. The Most Sustainable Professional Position

The stronger and more balanced legal position therefore is:

The controversy is highly debatable and requires harmonious construction of Sections 140B and 234B in light of the compensatory character of interest provisions and the mandatory pre-payment framework governing ITR-U.

This becomes a more persuasive and litigation-sustainable interpretation.

XII. Cases Where Taxpayer’s Position Becomes Particularly Strong

Situation	Strength
Entire tax paid before filing	Very Strong
Interest already discharged	Very Strong
Additional tax under Section 140B paid	Very Strong
No refund claimed	Strong
Demand arises solely due to delayed processing	Very Strong
No challan or credit mismatch exists	Very Strong

XIII. Cases Where CPC Demand May Still Sustain

Defect	Consequence
Challan mismatch	Credit denial
Wrong AY tagging	Non-adjustment
Incorrect minor head	Payment mismatch
Partial payment before filing	Genuine continuation possible
Incorrect self-computation	Sustainable adjustment

Thus:

Not every CPC demand in ITR-U cases is necessarily unsustainable.

XIV. Practical Resolution Framework

Step	Action
1	Reconcile challans, AIS/26AS and interest computation
2	File rectification under Section 154
3	Escalate before Jurisdictional AO
4	File grievance and seek stay of demand
5	Consider writ remedy in exceptional cases

Suggested Legal Submission

“The assessee had fully discharged tax, interest and additional income-tax liability under Section 140B prior to furnishing Updated Return under Section 139(8A). Accordingly, continuation of interest under Section 234B on liabilities already discharged before filing merely due to subsequent processing under Section 143(1) results in a debatable and potentially excessive extension of compensatory levy beyond the period of actual revenue deprivation and therefore requires harmonious construction of Sections 140B and 234B.”

Final Closure

The controversy surrounding Section 234B in ITR-U cases is far deeper than a routine computational dispute.

It raises important questions concerning:

• the scope of compensatory interest,
• interaction between Sections 140B and 234B,
• limits of automated processing,
• and fairness within a mandatory pre-payment framework.

A purely algorithmic extension of interest till CPC processing may not fully account for the statutory architecture of Section 140B where:

• taxes are compulsorily paid before filing,
• additional tax already protects Revenue,
• and Government already possesses the funds before processing occurs.

At the same time, the statutory reference in Section 234B to determination under Section 143(1) prevents simplistic conclusions.

Accordingly, the most professionally sustainable view remains:

The issue is legally arguable, interpretationally substantial and fit for rectification, administrative reconsideration and judicial examination where liabilities already stood fully discharged prior to furnishing Updated Return under Section 139(8A).

Section 194-IA in Joint Property Purchase: ITAT Delhi Rules No TDS if Individual Share is Below ₹50 Lakhs

 By CA Surekha Ahuja

Joint Property Purchase: No TDS if Individual Share is Below ₹50 Lakhs

Harvindra Singh vs ACIT CPC-TDS – 186 taxmann.com 176 (Delhi ITAT)

A significant clarification has been laid down by the Delhi ITAT on one of the most litigated TDS issues in property transactions — whether the ₹50 lakh threshold under Section 194-IA applies per property or per buyer in joint purchases.

In a taxpayer-favourable ruling in Harvindra Singh vs. ACIT CPC-TDS, the Tribunal has held that the threshold must be tested with reference to each individual transferee’s share, where ownership and consideration are clearly identifiable.

This ruling has direct relevance under both:

• Income Tax Act, 1961 (Section 194-IA)
• Income Tax Act, 2025 (Section 393 – TDS on immovable property framework)

Core Legal Issue

Whether TDS under Section 194-IA is triggered:

• on aggregate property value, or
• on individual buyer’s share in joint ownership

Delhi ITAT’s Final Ruling

The Tribunal held:

The ₹50 lakh threshold under Section 194-IA must be applied buyer-wise, not property-wise, where shares are clearly defined in a joint purchase transaction.

Accordingly:

• If individual share < ₹50 lakhs, no TDS is required
• CPC cannot mechanically aggregate total consideration for default creation

Facts in Brief

Particulars	Amount
Total Property Value	₹55,00,000
Co-buyers	3
Individual Share	₹18,33,333 approx.
TDS Deducted	Nil

Despite clear ownership apportionment, CPC-TDS raised demand under Section 200A, which was deleted by ITAT.

Mathematical Position (Ownership Test)

$\text{Individual Share} = \frac{\text{Total Property Value}}{\text{Number of Buyers}}$

$\frac{₹55,00,000}{3} = ₹18,33,333$

Since:

$₹18,33,333 < ₹50,00,000$

Result:

No TDS liability arises under Section 194-IA.

Comparative Legal Position

A. Income Tax Act, 1961 – Section 194-IA

• TDS @ 1% on transfer of immovable property
• Threshold: ₹50 lakhs consideration
• Dispute: Whether threshold applies per transaction or per transferee
• ITAT ruling clarifies: Per transferee basis applies where shares are identifiable

B. Income Tax Act, 2025 – Section 393 (New Framework)

Under the new law:

• Section 393 replaces Section 194-IA framework
• Digital integration with property registries increases automation
• CPC-style validations become more data-driven and system-based

However, the legal principle remains unchanged:

Threshold applicability must still be determined on individual transferee consideration, not mere aggregate property value.

Key Comparative Insight (Old vs New Act)

Aspect	1961 Act (Section 194-IA)	2025 Act (Section 393)
Threshold test	₹50 lakhs property consideration	Substantially retained
Basis of application	Disputed (property vs buyer)	Must remain transferee-based
Compliance system	TRACES / CPC	AI + registry-linked system
Risk area	Manual aggregation errors	Automated mismatch detection
Judicial safeguard	ITAT interpretation	Still fully applicable

Key Findings of ITAT

The Tribunal emphasized:

• Threshold cannot be applied mechanically on aggregate value
• Identifiable ownership shares govern tax deduction liability
• CPC processing under Section 200A cannot override substantive law
• Identical transactions must not result in unequal tax treatment

Practical Impact of the Ruling

1. Major Relief for Joint Property Transactions

Applies to:

• husband-wife purchases
• HUF acquisitions
• family investments
• co-investor arrangements
• NRI joint property holdings

2. Protection Against CPC-TDS Demands

Helps in challenging:

• automated Section 200A intimations
• interest under Section 201(1A)
• TRACES mismatch defaults
• incorrect aggregation-based demands

3. Strong Substance Over Form Principle

The ruling reinforces:

Tax law applies on real economic ownership, not mechanical aggregation.

Compliance Takeaways (Very Important)

To safely rely on this ruling:

Ensure:

• ownership ratio is clearly stated in sale deed
• payment contribution matches share
• bank trail supports allocation

Maintain documentation:

• share computation sheet
• legal note on non-deduction
• sale deed extract
• ITAT ruling reference

Tax Audit Relevance

• Clause 34 of Form 3CD is the primary reporting clause for TDS compliance
• Auditors must document:
  • whether TDS was applicable
  • basis of non-deduction (if any)
  • share-wise computation
  • legal reliance including judicial precedents

Clause 19 has only indirect or minimal relevance in this context.

Conclusion

The ruling in Harvindra Singh vs. ACIT CPC-TDS is a landmark clarification on Section 194-IA, now strengthened in relevance under both tax regimes.

It conclusively establishes:

The ₹50 lakh threshold applies to the individual transferee’s share, not the aggregate property value in joint purchases.

This judgment not only resolves a long-standing CPC-TDS controversy but also sets a clear compliance direction for the evolving digital tax administration framework under the Income Tax Act, 2025.

TDS on Foreign Software Distribution Payments — Royalty or Not

 By CA Surekha Ahuja

Downloading Software from Foreign Vendor for Resale — Whether Payment Constitutes Royalty and Whether TDS Under Section 195 Applies

The taxation of cross-border software payments has been one of the most aggressively litigated international tax issues in India. The controversy primarily revolved around whether payments made by Indian distributors/resellers to foreign software suppliers for downloadable or off-the-shelf software constitute “royalty” under Section 9(1)(vi) of the Income-tax Act, 1961 and the applicable DTAAs.

The issue attained final judicial clarity through the landmark Supreme Court ruling in Engineering Analysis Centre of Excellence Pvt. Ltd. v. CIT, which fundamentally settled the distinction between:

• transfer of copyright rights; and
• sale/use of a copyrighted article.

That distinction now forms the backbone of software taxation jurisprudence in India.

Core Legal Issue

Whether payment made by an Indian entity to a foreign vendor for downloading software and thereafter reselling the same to Indian customers constitutes:

payment for copyright, or

payment for a copyrighted product?

The answer determines:

• taxability in India;
• characterisation as royalty;
• applicability of Section 195 TDS;
• consequential exposure under Section 40(a)(i).

The Foundational Legal Principle — Copyright vs Copyrighted Article

The Supreme Court recognised the most crucial distinction in software taxation:

Every software contains copyright,

but every software payment is not royalty.

Royalty arises only when rights in the copyright itself are transferred.

Mere use, resale, or distribution of a copyrighted product does not amount to use of copyright.

This distinction is both commercially and legally decisive.

What Constitutes Copyright Rights?

Copyright rights generally include:

• right to reproduce software;
• right to modify source code;
• right to commercially exploit IP;
• right to create derivative works;
• right to independently distribute or sub-license;
• right to adapt or alter software.

Transfer of such rights may result in royalty.

What Is a Copyrighted Article?

A copyrighted article merely refers to:

• a software copy;
• downloadable software package;
• standard licensed software;
• shrink-wrapped or electronically supplied software.

The purchaser merely obtains limited rights to use or resell the software subject to restrictions.

The underlying intellectual property continues to belong to the foreign supplier.

Thus:

the customer uses the product, but does not acquire the copyright embedded in it.

Supreme Court Decision — Engineering Analysis

In Engineering Analysis Centre of Excellence Pvt. Ltd. v. CIT, the Supreme Court examined:

• distributor arrangements;
• reseller structures;
• downloadable software;
• OEM transactions;
• EULAs and licence agreements.

The Court categorically held:

consideration for mere resale/use of software without transfer of copyright rights is not royalty.

The Court further clarified that:

• limited licence rights;
• installation permissions;
• restricted resale rights;
• end-user access permissions,

do not amount to transfer of copyright.

What is transferred is merely a copyrighted article.

Important Analytical Principle Emerging from the Judgment

The judgment shifted the analysis from terminology to substance.

Mere nomenclature such as:

• “licence fee”,
• “software licence”,
• “user licence”,

does not automatically create royalty.

Courts examine:

the real legal rights transferred,

and not merely the labels used in agreements.

Why Ordinary Software Resale Transactions Are Not Royalty

In a standard software distribution arrangement:

• foreign vendor retains copyright ownership;
• reseller gets only restricted distribution rights;
• source code is not transferred;
• software cannot be modified;
• reseller cannot commercially exploit IP independently;
• no derivative rights are granted.

Therefore:

distributor never steps into the shoes of a copyright owner.

The distributor merely facilitates movement of licensed software copies.

Hence:
payment remains consideration for copyrighted products and not for use of copyright itself.

Download Mechanism Is Legally Irrelevant

The Supreme Court effectively rejected the argument that electronically downloaded software automatically becomes royalty.

Whether software is supplied through:

• physical media;
• electronic download;
• cloud delivery;
• activation keys,

the decisive factor remains:

whether copyright rights are transferred.

The mode of delivery does not alter tax characterisation.

Interplay with Section 195

Section 195 applies only where payment is “chargeable to tax” in India.

The Supreme Court in GE India Technology Centre Pvt. Ltd. v. CIT held:

withholding obligation cannot exceed actual taxability.

Thus, where:

• payment is not royalty; and
• foreign supplier has no Permanent Establishment in India,

the income itself may not be taxable in India.

Consequently:

no TDS obligation under Section 195 survives.

DTAA Protection — A Critical Dimension

Most Indian DTAAs define royalty far more narrowly than domestic law.

The Supreme Court made an extremely important observation:

unilateral domestic amendments cannot automatically expand treaty taxation rights retrospectively.

This became highly significant because retrospective amendments introduced through Finance Act 2012 attempted to widen royalty scope for software payments.

However, treaty protection continued to prevail.

The judgment thereby reinforced an important international tax principle:
DTAAs cannot be indirectly rewritten through retrospective domestic amendments.

Alignment with International Tax Principles

The Supreme Court substantially aligned Indian jurisprudence with internationally accepted OECD principles distinguishing:

• copyright rights;
  from
• copyrighted articles.

This brought significant certainty to global software commerce and cross-border technology transactions.

Situations Where Royalty Exposure May Still Arise

Engineering Analysis does not provide blanket exemption to every software transaction.

Royalty exposure may still arise where agreements grant:

• source code ownership/access;
• unrestricted reproduction rights;
• modification rights;
• rights to create derivative works;
• independent commercial exploitation rights;
• unrestricted sub-licensing powers.

In such cases:

payment may represent consideration for transfer or use of copyright itself.

Accordingly:

• royalty provisions may apply;
• TDS under Section 195 may become mandatory.

Practical Drafting Significance

Post Engineering Analysis, contractual architecture has become extremely important.

Agreements should clearly establish:

• copyright retained by foreign supplier;
• limited user/distribution rights only;
• no transfer of IP ownership;
• no unrestricted reproduction rights;
• no modification or derivative rights.

Many software agreements unintentionally weaken the non-royalty position by granting excessive hosting, API integration, modification, or sub-licensing rights.

Therefore:

tax characterization ultimately depends upon the precise legal rights and commercial powers actually transferred.

Emerging Area — SaaS and Cloud Models

While Engineering Analysis substantially settled traditional software distribution taxation, evolving:

• SaaS models;
• cloud infrastructure arrangements;
• AI licensing frameworks;
• platform access structures,

may still generate future litigation depending upon the degree of control, access, and IP rights granted.

Thus, characterisation analysis continues to remain transaction-specific.

Practical Conclusion

The law now stands substantially settled that:

downloading software from a foreign vendor and reselling the same ordinarily does not constitute royalty where copyright itself is not transferred.

Where:

• foreign supplier retains IP ownership;
• Indian reseller merely receives limited distribution/use rights;
• no proprietary copyright rights are parted with,

the payment ordinarily:

• is not royalty;
• is not chargeable to tax in India as royalty;
• does not attract Section 195 withholding;
• should not trigger disallowance under Section 40(a)(i).

The decisive test is not the existence of embedded intellectual property within software, but:

whether the payer acquires copyright rights,

or merely deals in a copyrighted product.

That distinction now forms the settled foundation of Indian software taxation jurisprudence.

Key Judicial Authorities

• Engineering Analysis Centre of Excellence Pvt. Ltd. v. CIT
• GE India Technology Centre Pvt. Ltd. v. CIT