DTAA Between India and the USA: How Service Exporters Avoid Being Taxed Twice

The DTAA between India and the USA is a tax treaty that ensures the same income is not taxed in full by both countries.

Signed in 1989, it decides which country may tax a given type of income and caps the rate the other may charge.

For an Indian company exporting software or services to US clients, one point matters most. Your service fee is treated as business profits, and business profits are taxable in the US only if you have a permanent establishment there.

Most Indian firms billing from India do not, so that income is taxable in India alone.

The catch is documentation. Without the right treaty forms, a US client must withhold up to 30% of your invoice, and you are left recovering it later.

Three things carry this whole guide, so here they are up front:

• No US office, no US tax: clean service income under Article 7 carries a 0% US rate when you have no permanent establishment there.
• The 30% is a default, not the treaty rate: it applies only while your paperwork is missing.
• Fix it at source: a Form W-8BEN-E, and often a Tax Residency Certificate, applied before invoicing beats claiming a credit afterwards.

This guide is for Indian IT and IT-enabled services (ITeS) exporters. If your business runs on cross-border payments for service exporters, the treaty is the piece that decides what the US may keep.

It walks through what the treaty does, the rates that apply, the documents that reduce US tax, and two worked examples in rupees and dollars.

A DTAA, or Double Taxation Avoidance Agreement, is a bilateral treaty that splits taxing rights between two countries. It decides who may tax each type of income, and at what maximum rate.

India and the United States signed their treaty on 12 September 1989. It has applied to withholding taxes since 1 January 1991.

The treaty sits on top of each country's own tax law. Where the treaty rate is lower than the local rate, you claim the treaty rate; where domestic law is already lower, that applies instead.

It covers residents of either country. An Indian private limited company, LLP or proprietor that is tax-resident in India can claim its benefits on US-source income, as long as it can prove Indian residence.

This is the same mechanism behind double taxation relief in general, applied to one corridor.

Most guides on this treaty are written for non-resident Indians with US shares and property. A services exporter needs a different part of the treaty.

The export of services vs export of goods distinction matters here, because your income is a fee for services rather than a sale of goods, and the treaty taxes the two differently.

Your fee for delivering software, design, consulting or back-office work is business profits under Article 7.

The rule is short: business profits are taxable in the US only if you run them through a permanent establishment (PE), such as a US office, branch or dependent agent.

Most Indian ITeS firms billing from India have no US PE. No PE means no US tax on that income, and the client should not be withholding federal tax on it at all.

A quick example. A Pune development studio builds a web app for a New York client and invoices US$40,000. It has no US office or agent.

Under Article 7 that fee is taxable in India only, so the correct US withholding is zero.

Article 12 covers royalties and fees for included services (FIS), and it is where services exporters trip up.

If your work "makes available" technical knowledge, skill or a process that the client can then apply on its own, the fee can be recharacterised as FIS.

FIS is not tax-free. It carries a treaty-capped rate instead of the business-profits treatment, though the cap is still far below the 30% default.

The "make available" test is the dividing line. Two short scenarios show it:

• Routine delivery (business profits): you build and hand over a feature, then move on. The client cannot independently reproduce your skill. This stays under Article 7 at 0%.
• Knowledge transfer (FIS): you train the client's team to run a proprietary process, or hand over a reusable method they can apply alone. This can be FIS, taxed at the treaty cap.

Match the description on your invoice and contract to what you actually deliver. Calling a plain service a "royalty," or the reverse, changes the rate you owe.

The value of the treaty is the gap between the flat 30% the US withholds by default and the capped rate you can claim. As of August 2026 the headline caps are:

Read these as ceilings, not a bill you automatically owe. For a clean services engagement under Article 7, the correct treaty position is zero US tax.

The table also shows why classification matters in money terms. Moving a fee from "service" to "royalty" shifts it from 0% to a 10 to 15% cap.

Rules on the reverse flow, where an Indian business pays a US vendor, sit under TDS on foreign payments and Section 195.

When a US company pays a foreign vendor, its default duty is to withhold 30% and send it to the IRS. That default drops only when the vendor certifies a lower treaty rate.

The certificate is Form W-8BEN-E for a company, or W-8BEN for an individual. Filing an accurate Form W-8BEN-E tells the client your treaty residence and the article you claim, so it applies the reduced rate at source.

Larger US clients often want more before they release a gross payment:

• Form W-8BEN-E, certifying your treaty claim and confirming no US PE.
• A Tax Residency Certificate (TRC), proving you are tax-resident in India for the year.
• A No Permanent Establishment (No-PE) declaration, confirming you have no fixed base in the US.
• Sometimes Form 10F, when your TRC lacks the particulars the payer needs.

Hand these over before the first invoice and a compliant client applies the treaty rate straight away. Miss them and you recover the money the slow way.

Your Indian software company bills a US client US$50,000 for a project. The client had no W-8BEN-E on file, so it withheld the default 30% and paid you the balance.

That US$35,000 also arrives after any bank charges for foreign remittance, which a bank wire adds on top of the tax already lost.

Under Article 7 that income was taxable only in India, so the US$15,000 should not have been withheld. You have two routes to recover it.

The first is to correct future invoices: once your treaty documents are with the client, it applies the reduced rate and pays you gross.

The second is a foreign tax credit (FTC) for the amount already withheld. The US$15,000 of US tax is set off against the Indian tax on the same income, so you are not taxed twice.

The credit flows in from your reporting of the foreign remittance in the ITR.

The FTC prevents the double hit, but it is slower and ties up cash. The rule practitioners repeat is simple: fix the documents first, use the credit only as a backstop.

Take the same US$50,000 invoice, but this time your W-8BEN-E and TRC are on file before you bill. Here is the difference, converted at an illustrative US$1 = ₹87.

The tax outcome is the same either way, because the FTC eventually neutralises the US$15,000. The difference is timing.

Getting the paperwork right keeps roughly ₹13 lakh of working capital in your business now, instead of parked with the IRS until your Indian return is assessed.

For most ITeS firms the bulk of receipts are dollars, so how you receive money from USA to India shapes the effective rate on every one of them.

To take the US tax as a credit and to prove your treaty residence, keep this pack current each financial year:

• Tax Residency Certificate (TRC): an Indian resident applies to their Assessing Officer in Form 10FA, and the TRC is issued in Form 10FB. It is valid for one financial year, so you renew it annually.
• Form 10F: filed electronically on the income-tax portal to supply residence particulars a foreign TRC may not carry. Read the detail on Form 10F before you file.
• Form 67: the statement that lets you claim the foreign tax credit. It must be filed on or before your income-tax return due date, so a late Form 67 can cost you the credit.
• Schedule FSI and Schedule TR in your ITR, where you report the foreign income and the foreign tax paid.

None of this disturbs your export workflow. Your export of services under GST treatment, purpose codes and remittance documentation carry on as normal.

• Treating the 30% as final. It is a default for missing paperwork, not the treaty rate. Most services income under Article 7 carries no US tax at all.
• Filing Form 67 late. The credit is tied to the return due date. Miss it and the FTC can be denied even though the tax was genuinely paid.
• Letting the TRC lapse. A TRC covers one financial year. An expired certificate mid-project can pause a client's ability to apply the treaty rate.
• Assuming W-8BEN-E alone is enough. For larger payers you also need the TRC, and often a No-PE declaration, before they release a gross payment.
• Misreading royalty vs service. Calling reusable IP a "service," or a plain service a "royalty," changes the rate. Match the description to what you actually deliver.

The treaty decides what you owe. Getting the money into India cleanly is a separate job, and it is where a purpose-built cross-border setup helps.

Receiving US payments into dedicated receiving accounts settles them at a transparent USD to INR rate.

An eFIRA is issued automatically as the money lands, so your remittance proof for tax and GST is generated at the moment of receipt rather than chased afterwards.

Xflow holds final Payment Aggregator - Cross Border (PA-CB) authorisation from the Reserve Bank of India (RBI) for both exports and imports, as of February 2026. Receipts settle to your Indian bank account the next business day.

This guide is general information, not tax advice. Treaty positions turn on the facts of each engagement, so confirm your classification and filings with a qualified chartered accountant.