
Until recently a firm paying its own partners had no deduction to make. Remuneration and interest went to the partners, the limits under section 40(b) decided how much of it the firm could claim, and that was the whole of the question.
From 1 April 2025 there is a second question. Section 194T requires a firm to deduct tax on salary, remuneration, commission, bonus or interest paid to a partner, at ten per cent, once the total for the year to that partner goes past a modest limit.
The limit is low enough that it catches almost every partnership and LLP with working partners, and the way the provision is worded catches entries where no money moved at all.
What the provision says
The obligation falls on any person being a firm responsible for paying any sum in the nature of salary, remuneration, commission, bonus or interest to a partner.
The rate is ten per cent.
There is no deduction where the sum, or the aggregate of such sums credited or paid or likely to be credited or paid to that partner, does not exceed Rs 20,000 for the financial year.
Three features of that wording do the damage, and each one is worth reading twice.
It is an aggregate, so a firm cannot look at a single payment and conclude it is below the limit. Everything to that partner across the year is added together.
It includes amounts "likely to be" credited or paid, which means the test is not satisfied by waiting to see. If the year's total is going to pass the limit, the deduction attaches from the point that becomes apparent.
It covers interest as well as remuneration, so a firm that pays no remuneration at all and only credits interest on capital is still inside it.
Important
The limit is for the financial year, per partner, across every category named. A firm with four working partners is making this test four times, not once.
The year end journal is the trap
This is the part that will produce the most defaults, and it is entirely invisible from a bank statement.
The provision reaches a sum credited to the partner's account, including the capital account. Under the Income-tax Act, 2025 the Table in section 393(3) says it in exactly those terms at serial number 7.
So the ordinary year end entry, where the firm works out remuneration and interest and credits both to the partners' capital accounts without paying anything out, is a credit that triggers the deduction. No money left the firm. No bank line exists. The obligation attaches anyway.
This is also why the usual way of finding missed deductions, by looking at payments, does not find this one. A firm that pays its partners irregularly through the year and squares it all up in March will see the whole thing happen in one journal, in the last month, often after the quarter's return has been prepared.
Pro tip
Put the partner remuneration and interest working into March, not into the following September. The figures are knowable from the book profit as soon as the year closes, and the deduction has to be made when the credit is passed, not when somebody computes it.
Two different tests on the same entry
What makes this genuinely confusing in practice is that a partner payment now faces two unrelated tests, both of which apply to the same figure, and neither of which answers the other.
How much is allowed is section 40(b), and it is unchanged. Remuneration to working partners is allowed up to ninety per cent of the first Rs 6,00,000 of book profit or Rs 3,00,000, whichever is more, and sixty per cent of the balance. Interest to a partner authorised by the deed is allowed up to twelve per cent simple interest, and the excess is not allowed.
Whether tax must be deducted is section 194T, and it does not care about those limits at all. It applies to the sum credited or paid, not to the deductible part of it.
So a firm can credit a partner more remuneration than section 40(b) allows, be disallowed the excess, and still owe a deduction on the whole amount credited. The two tests look at the same entry and are answering different questions.
Under the Income-tax Act, 2025 the allowance limits move to section 35(e)(iii)(A) and the deduction to the section 393(3) Table, so a practice running both years is quoting four provisions for what is conceptually two rules.
What it means for the quarterly return
A deduction under this provision has to reach the non-salary quarterly statement like any other, under its own section code, with the partner as the deductee.
Two practical notes.
The partner is a deductee with a PAN, and that PAN has to be right, because the credit will show in the partner's own tax credit statement and they will be relying on it when they file. A partner's remuneration is their business income, so the credit matters to them personally in a way a vendor's might not.
And the deduction has to be deposited on the ordinary timetable, counted from the credit rather than from any later payment. A credit passed on 31 March carries the March deposit date, which is the one date in the TDS calendar that is not the seventh of the following month.
If you are selecting software for this, it is worth asking directly whether it can write this section code on the statement at all. Not every tool that produces TDS returns covers the full code list, and a single line that cannot be written stops the whole statement rather than just that line. The forms and codes all changed number for 2026-27 as well.
Conclusion
A firm paying its partners is now a deductor, at ten per cent, above a limit small enough that it rarely saves anybody.
The risk is not the rate or the limit. It is that the provision reaches a credit to a capital account, so the entry that triggers it is a year end journal rather than a payment, and nothing in the bank statement will ever show it.
Finding deductions nobody made covers the general check, and the TDS workspace is here.
Turn bank statements into Tally vouchers on your own PC
Greenote reads 100+ Indian banks and posts clean vouchers straight into Tally, from your own PC. The statement is not uploaded, and nothing is typed by hand.
Free trial: 7 days or 5 statements, no card. Works with Tally Prime & ERP 9.


