Loading
Where a threshold is crossed mid-year, deduction may be due on the cumulative amount rather than only this payment. Both are shown.
Rates depend on the payment type and on the recipient's status — whether a PAN has been furnished, whether a lower-deduction certificate applies — and they change. They are inputs here rather than a lookup. The obligation and the liability for getting it wrong sit with the payer, so verify the rate and the threshold before deducting.
Calculates deduction on this payment and on the year's cumulative total.
Every figure it produces is arithmetic on what you enter, and the working is shown line by line rather than summarised into a single number.
Replace the defaults with your own figures. They are examples chosen to make the shape obvious, not benchmarks — using them unchanged tells you about a company that is not yours.
The lines beneath the headline are the useful part: they show which input is driving the result, which is what makes the answer arguable in a good way.
Rates depend on the payment type and on the recipient's status — whether a PAN has been furnished, whether a lower-deduction certificate applies — and they change. They are inputs here rather than a lookup. The obligation and the liability for getting it wrong sit with the payer, so verify the rate and the threshold before deducting.
Where two readings of the same question exist, both are shown rather than one being chosen for you. That is deliberate — the difference between them is usually the thing worth discussing.
If a figure looks wrong, change the input you least believe and watch what moves. That is faster than checking the arithmetic.
No. The tool runs in the page, nothing is sent anywhere, and there is no follow-up.
No. They are examples chosen to make the shape clear. Use your own figures.
It is stated in the working shown beneath the result, so you can check it rather than trust it.
Half an hour on your own figures, and an honest answer about the parts Treepie does not improve.