Engineering Analysis: A Practical Guide to Software Payment Withholding

Engineering Analysis does not mean that all cross-border software payments are outside India’s withholding tax net. It means that payments for the end use or distribution of software under an EULA or distribution agreement may not constitute royalty under an applicable tax treaty. Whether withholding applies still depends on the contract, the rights granted, the vendor’s tax residence, treaty availability, the presence of a permanent establishment, and whether the payment includes taxable services.

What Did Engineering Analysis Decide?

In March 2021, the Supreme Court decided a batch of close to ninety appeals in Engineering Analysis Centre of Excellence. For anyone who had spent the previous decade arguing whether a shrink-wrapped licence was a royalty, it felt like the end of a very long argument.

The Court drew a line between two things that tax officers had been treating as one: a copyright, and a copyrighted article. When an Indian distributor or end user pays for software under a licence that only allows it to use the program, and not to reproduce, adapt or commercially exploit the code, nothing in the nature of copyright passes to the payer. So the payment is not a royalty under the treaty. It is business income of the foreign vendor, taxable in India only if the vendor has a permanent establishment here.

The Court also held that the wider domestic definition, expanded by the 2012 amendment, could not be read into the narrower treaty definition. Where a treaty applies, the treaty wins.

Why Software Payments May Still Attract Withholding Tax?

In practice, many finance teams took away only the headline and not the reasoning. Here is what I keep running into when I review remittance registers:

• Payments to vendors in countries with which India has no treaty. The domestic definition applies to them, and it is wide. Engineering Analysis does not help here.
• Invoices that bundle a licence with implementation, customization, training or annual support. The licence component may be outside royalty, but the services component has to be tested separately, often as fees for technical services.
• Contracts that grant rights to modify source code, sub-licence, or reproduce copies for distribution. That is exactly the situation the Court said was different.
• Treaty claims made without a valid TRC or Form 10F on file. The best legal position in the world will not survive a missing document.

How to Assess Software, SaaS, and Cloud Contracts

When reviewing a software, SaaS, API, cloud infrastructure, or data-subscription arrangement, consider:

• Whether the arrangement transfers any right over the software itself.
• Whether the customer merely accesses a hosted service.
• Whether the vendor grants rights to reproduce, modify, sub-license, or distribute the software.
• Whether the payment includes implementation, integration, customization, training, or support services.
• Whether any services are performed from India or involve a dependent agent in India.
• Whether the vendor has a tax residency certificate and other treaty documentation.
• Whether the payment should be allocated between licence, services, and other components.

The ruling was written in a world of CDs and installed licences. Today most of what companies buy is SaaS, API access, cloud infrastructure and data subscriptions. The principle still applies, but the facts have to be read again. Is there any right granted over the software itself, or is the customer simply accessing a service? Is anything customized for the Indian entity? Is there a human element in delivery?

The assessment is straightforward in principle, but it must be performed contract by contract rather than by applying a blanket vendor category.

Documentation Required for Treaty Claims

A treaty-based position should be supported by contemporaneous documentation. At a minimum, organizations should retain the executed contract, invoice, tax residency certificate, Form 10F where applicable, beneficial ownership information, withholding tax analysis, and evidence of the commercial substance of the arrangement.

Where a payment includes both non-taxable and taxable components, organizations should maintain a clear allocation methodology and be able to explain how each component was characterized.

Practical Steps for Finance and Tax Teams

Finance and tax teams should review cross-border software arrangements periodically rather than relying on a generic vendor classification.

• Identify all recurring software, SaaS, cloud, API, and data-subscription vendors.
• Review the contractual rights granted, service components, and payment structure.
• Confirm the vendor’s country of tax residence and treaty availability.
• Assess permanent establishment and service-related withholding exposure.
• Obtain and validate treaty documentation before remitting payments.
• Document the tax analysis, allocation methodology, and approval process.
• Review positions periodically as contracts, delivery models, and regulations change.

Frequently Asked Questions

Does Engineering Analysis apply to all software payments?

No. Engineering Analysis applies to payments for the end use or distribution of software under an EULA or distribution agreement where the applicable treaty definition of royalty is engaged. Other payments may still be taxable or subject to withholding depending on the contract, services, vendor residence, treaty availability, and permanent establishment position.

Is TDS required on SaaS payments in India?

It depends on the facts. A SaaS payment may be treated as a service rather than a royalty where the customer merely accesses a hosted application and no copyright is transferred. However, withholding may still apply if the payment includes taxable technical services, the vendor has a permanent establishment in India, or no applicable treaty reduces or eliminates the tax liability.

Is a tax residency certificate mandatory for treaty benefits?

A valid Tax Residency Certificate is generally essential to support a treaty claim. Depending on the applicable requirements, Form 10F, PAN, and other beneficial ownership information may also be required.

Can a software invoice be split between licence and services?

Yes, but the split must reflect the actual commercial arrangement and be supported by the contract, invoice, and delivery evidence. A generic allocation without substance may not withstand scrutiny.

What should finance teams retain for software remittances?

Finance teams should retain the contract, invoice, TRC, Form 10F where applicable, withholding analysis, payment records, beneficial ownership information, and evidence supporting any allocation between software and services.