A later bank remittance does not necessarily postpone deduction
For an ordinary chargeable non-resident commercial payment governed by the credit-or-payment rule, compare the actual credit event with payment and use the earlier event. Under section 393(11), crediting the relevant income or sum to a suspense account or another account name is deemed credit to the payee. A year-end provision cannot be treated as outside TDS merely because it has not reached the named vendor ledger.
Framework for tax year 2026–27
Checked on 24 October 2026 against Income-tax Act, 2025, section 393(2), its notes and section 393(11). Section 393(2)(b) establishes the general earlier-of-credit-or-payment timing for the non-resident table. The table and notes contain exceptions: for example, its specified interest payable by Government, a public sector bank or a public financial institution is addressed by a payment-time rule. Read the applicable entry and notes before using a generic worksheet.
This article concerns identifiable, established chargeable commercial obligations to non-residents, assuming a separately validated deduction rate. It does not decide whether an unallocated estimate, contingent liability, capital transaction or disputed amount is income chargeable to the recipient. It also does not prescribe a treaty rate, tax-deposit due date or remittance form merely from the accounting date.
Build an event ledger, not a remittance-only list
For each obligation, record the service or contractual basis, recipient, chargeability conclusion, applicable provision, effective rate, first relevant credit, payments, subsequent invoice and adjustments. Keep evidence of the actual accounting event. Backdating a journal or treating an invoice date as a universal substitute for credit is not a reliable control.
A payment before the invoice or expense booking may itself trigger the payment limb where the sum is chargeable under the selected provision. Conversely, a later invoice and remittance may only settle an obligation already captured at an earlier credit. Link those events so the tax base is neither missed initially nor counted again at settlement.
Suspense and provision reviews need a factual conclusion
A label such as provision, accrued expense or suspense does not settle the legal result. Identify whose income or sum has actually been credited and whether the chargeability and deduction conditions apply. Where the payee or obligation is genuinely uncertain, retain a reasoned current-law assessment rather than writing “no invoice, no TDS” across the entire ledger.
If a provision changes, distinguish an additional newly recognised chargeable sum from a reclassification of the same original amount. For reversals, disputes or over-deductions, determine the permitted correction route separately; do not assume that a commercial reversal automatically refunds tax already paid. Preserve the original event and the reason for every subsequent change.
Rate, currency and accounting reconciliations remain separate
The illustrations stipulate an effective flat rate of 10% solely to demonstrate event allocation. That is not a rate recommendation for any treaty, service class or recipient. They assume the payer deducts from a gross amount and has not promised an additional net-of-tax amount; tax-bearing contracts need a separate gross-up analysis.
The event worksheet should feed the separately applicable deduction, payment, statement and remittance process. For foreign-currency obligations, establish the required tax-conversion basis independently of the financial-statement closing rate. An exchange difference or a journal migration does not automatically mean the same underlying income must be taxed a second time.
Worked illustrations
These illustrations use fictional facts and expressly stated assumptions. Amounts are Indian rupees unless a different currency or unit is specified. They are independent examples, not findings about any actual client.
Illustrative example 1: Credit before payment
An established gross chargeable obligation of ₹600,000 is credited on 31 October 2026 and paid on 20 November. Under the assumed general rule, 31 October is earlier. At the stipulated 10%, deduction is ₹60,000; waiting until the bank-payment event would miss the identified trigger.
Illustrative example 2: Payment before credit
Assume a ₹300,000 payment on 10 October is itself a chargeable sum under the selected provision, with credit booked on 25 October. The earlier event is 10 October, and the stipulated 10% deduction is ₹30,000. This assumption does not declare every deposit or advance taxable.
Illustrative example 3: Suspense is not a different recipient
An established ₹450,000 chargeable amount for an identified non-resident is credited to suspense on 31 March 2027 and transferred to the vendor account on 15 April. Section 393(11) requires consideration of the 31 March credit. At the assumed 10%, tax is ₹45,000; the transfer is a linked reclassification, not another ₹450,000 of income.
Illustrative example 4: An increase is different from a reclassification
A chargeable ₹800,000 provision has already been subjected to ₹80,000 deduction at the assumed 10%. A later supported invoice establishes total gross consideration of ₹850,000. The additional gross amount is ₹50,000 and its assumed additional deduction ₹5,000. Keep the total ₹85,000 deduction reconciliation rather than duplicating tax on the original ₹800,000.
Illustrative example 5: Split payment dates do not duplicate an earlier full credit
A ₹1,000,000 gross obligation is first credited on 30 September, with later gross settlements of ₹400,000 and ₹600,000. At the stipulated 10%, the credit-event deduction is ₹100,000. The two settlements total the same ₹1,000,000; they are not a further ₹1,000,000 tax base.
Illustrative example 6: Reconcile the population across the closing date
Assume two independently chargeable credits on 31 March of ₹200,000 and ₹350,000, while a distinct ₹150,000 chargeable obligation first arises and is credited on 2 April. At the stipulated 10%, the March credit population is ₹550,000 with ₹55,000 deduction; the April population is ₹150,000 with ₹15,000. Classify by actual events and applicable law, not by one combined payment batch.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Identify the actual non-resident and obligation | Contract, recipient and service evidence. |
| 2 | Determine chargeability before timing | Current-law and treaty memorandum. |
| 3 | Select the correct section 393 entry and notes | Provision and exception review. |
| 4 | Approve the effective deduction rate | Rate and tax-bearing-clause analysis. |
| 5 | Locate the first relevant accounting credit | Journal, suspense and vendor-ledger trail. |
| 6 | Compare payment and credit events | Dated bank and accounting records. |
| 7 | Review unidentified or disputed provisions individually | Reasoned factual and legal assessment. |
| 8 | Link invoices, adjustments and settlements | Unique obligation reference and event ledger. |
| 9 | Reconcile currency and tax bases without duplication | Conversion evidence and deduction working. |
| 10 | Complete the separate payment and reporting obligations | Applicable due-date, statement and remittance records. |
Sixteen practitioner FAQs
1. Does remittance always determine the deduction date?
No. A relevant earlier credit can trigger the general rule.
2. Can a payment before expense booking matter?
Yes, where it is a chargeable sum governed by the payment limb.
3. Does a suspense-account label avoid deemed credit?
No. Section 393(11) addresses credit to accounts under any name.
4. Does every estimate automatically create TDS?
This article does not make that claim. Establish the actual obligation, payee, chargeability and applicable conditions.
5. Is an absent invoice a universal exemption?
No. Review the underlying credit and legal facts.
6. Do all non-resident table entries follow an identical timing rule?
Read their notes and exceptions, including the specified payment-time interest case.
7. Are the example percentages treaty rates?
No. They are stipulated effective rates for event-reconciliation practice.
8. Does the article cover net-of-tax gross-up?
No. Its examples assume deduction from a gross amount; analyse a payer-borne tax promise separately.
9. Is transferring suspense to a vendor necessarily new income?
Not if it merely reclassifies the same identified obligation. Preserve the linkage.
10. What if an invoice increases the established consideration?
Identify the incremental sum and analyse its own relevant event rather than duplicating the original base.
11. Can a reversal automatically recover previously deposited tax?
No. Determine the applicable correction or recovery process separately.
12. Can one payment settle several timing populations?
Yes. Allocate it back to the actual obligations and their events.
13. Does the closing exchange rate necessarily determine the TDS conversion?
No. Establish the applicable tax-conversion requirement independently.
14. Does this working set tax-deposit deadlines?
No. Apply the separate payment and reporting rules after identifying the deduction event.
15. Which legislation is used for the stated period?
The Income-tax Act, 2025, as applicable to tax year 2026–27, with the relevant current rules.
16. What is the strongest closing control?
Reconcile each obligation from first credit or chargeable payment through deduction, later invoice, settlement and any correction.
Conclusion
Determine chargeability and the applicable timing rule before reviewing the accounting event. A linked event ledger should capture the first trigger and prevent duplicate bases at later settlement.