Indian withholding on software payments — how much of this can I do myself?
Some of it, yes — and we will say so on the call if that is the honest answer. The parts that are worth paying for are the ones where a missed election, a missed deadline or an unverified threshold costs more than the fee: the distinction turns on what rights the payment buys — use of a copy, or use of the copyright.
What if I have already filed and got it wrong?
That is a common starting point. We re-derive the position, identify whether an amendment or a disclosure route is the right vehicle, and tell you which one preserves the relief that is still available. The order matters more than the speed.
How long will it take?
It depends on the documents rather than on us. Once the pack is complete most filings turn around inside a fortnight; anything that needs a certificate from a tax authority runs on that authority's timetable, which we tell you at the start rather than at the end.
Do we have to withhold Indian tax on a software licence payment?
It depends on what the payment buys. Where the fee gives your Indian customer the right to use a copy of the program, the payment looks like the purchase of a copyrighted article. Where it gives them the right to exploit the copyright itself, to reproduce, adapt or sub-licence the code commercially, it looks like a royalty and withholding follows. The question has been litigated in India for two decades, so the answer is not obvious from the invoice. The payer carries the liability for getting it wrong, which is why the position is written down before the remittance rather than after a query arrives.
Is a shrink-wrapped software sale a royalty under Indian tax law?
The medium is not the test. A disc, a download and a key delivered with a purchase order can all sit on either side of the line, because what matters is the bundle of rights the customer acquires. A licence permitting installation and internal use is a different thing from a licence permitting reproduction for sale. India has taken both positions in litigation over many years, and the reasoning turns on the licence terms rather than on how the software reached the buyer. We read the agreement, identify the rights actually granted, and record the conclusion in a file the payer can produce if the deduction is questioned.
Why did our Indian customer deduct tax from our software invoice?
Because the payer, not the recipient, decides whether the remittance is a royalty, and the payer bears the consequences of deciding wrongly. Faced with an unsettled question, many Indian finance teams deduct as a precaution and leave the supplier to argue about it afterwards. That is a rational choice for them and an expensive one for you, since the deducted amount sits with the Indian revenue until it is either credited against a liability or reclaimed. The practical fix is to give the customer a documented position before the invoice is raised, so the deduction decision is made on analysis rather than on caution.
Does a tax treaty change whether software payments are royalties?
It can. Treaty royalty definitions are not identical to each other or to domestic law, and the wording of the particular article decides whether a payment for the use of a program falls inside it. That means the same contract can produce a different answer for a supplier in one country than for a supplier in another. The analysis therefore runs in two stages: what the domestic rule says, and what the applicable treaty says, with the treaty position available only if the supplier can evidence entitlement to it. Both stages go in the file, because the payer may have to show its working.
What happens if we withhold nothing and the department disagrees?
The exposure lands on the payer. A determination that a remittance was a royalty and that no tax was deducted puts the payer in the position of having to fund tax it never withheld, alongside whatever consequences attach to the failure itself. That is why the decision is treated as a filing position rather than an administrative step: the contract is read, the rights granted are identified, the treaty is checked, and the conclusion is documented with the reasoning that supports it. A position that was written down before the payment is a very different thing to explain than one reconstructed afterwards.
Are cloud subscriptions and software support payments treated the same way?
Not automatically. A subscription giving access to a hosted service, a maintenance fee buying updates and helpdesk time, and a licence to reproduce code are three different bargains, and they can attract three different characterisations. Contracts often bundle them into one price, which is where difficulties begin, because an undifferentiated invoice invites the payer to treat the whole amount on the most cautious basis. Where the commercial arrangement genuinely has separate elements, the agreement and the invoice should say so. We look at what each element buys and set out the treatment element by element.
Do I need to report a foreign business I own?
Almost certainly, and on more than one form. Canada requires reporting of foreign affiliates on the T1134; the United States has a family of returns keyed to the entity type and your level of control, and several carry penalties that apply whether or not any tax is owed. These are information returns, so the obligation follows the ownership rather than the profit. See T1134.
Is my foreign pension taxable?
Usually in at least one country, and which one depends on the treaty article covering pensions — some give the taxing right to the country paying it, others to where you live, and several treat government service pensions differently again. Withholding at source is common and often reducible by treaty, with an elective return recovering an over-deduction. See the pensions article.
