If you deduct tax at source on payments other than salary, you owe each deductee a TDS certificate for every quarter. For the July–September quarter, Form 16A is usually due on 15 November, which is 15 days after the quarterly TDS statement is due on 31 October. Here is who issues it, how to produce it and how to fix mismatches. Please check the portal for any extension or renumbering before you rely on a date.
What Form 16A is and who must issue it
Form 16A is the TDS certificate for payments such as contractor fees, professional fees, rent, commission and interest. It is different from Form 16, which covers salary and is issued once a year. A Form 16A shows the deductor's and deductee's PAN, the amount paid, the tax deducted and the challan details of the deposit.
As the deductor, you must issue it to every deductee whose tax you deducted in the quarter. It is generated from the TRACES portal after your quarterly TDS statement is filed and processed, and it carries a unique certificate number you can quote in queries.
The Q2 timeline in plain words
- 7 October, 7 November and 7 December: TDS deducted in the previous month is normally deposited by the 7th. If you need a refresher, read our guide to depositing TDS by the 7th.
- 31 October: the usual due date for the quarterly TDS statement (the 26Q form for non-salary payments to residents) for July–September. Our article on the TDS Q2 returns covers what happens if it was missed.
- 15 November: the usual last date for issuing Form 16A for that quarter.
Dates and form numbering can change by notification. If the portal shows the certificate under a new form name, it is the same certificate, so follow what TRACES displays.
How to download Form 16A from TRACES
- Log in to TRACES with your TAN as the deductor.
- Check that the quarterly statement shows as processed and that the challans are matched. Certificates are available only for matched deductions.
- Request the Form 16A download for the quarter, choosing the deductee-wise or bulk option.
- Digitally sign the files and send each deductee their own certificate.
If the statement shows defaults, such as a PAN error or a challan that was not matched, the certificate for that deductee may not be generated until you correct the statement. That is why a clean statement matters before 15 November.
What a delay can cost
The law has historically attached a penalty of ₹100 per day of delay in issuing a TDS certificate, running until it is issued. The specific section numbers and provisions can change, so confirm the current provision with your CA. Whatever the penalty, a late or wrong certificate also leaves your vendor unable to claim credit with confidence, which is what causes the phone calls.
How deductees should match it with Form 26AS and AIS
If you are the deductee, compare each Form 16A with your Form 26AS and your Annual Information Statement (AIS) on the income tax portal. Check three things:
- The deductor's TAN and your PAN are correct.
- The amount credited and the tax deducted match the certificate.
- The credit appears in the quarter in which the payment was made.
Claim TDS credit in your return only for the amount that appears against your PAN. If a certificate shows more than 26AS does, ask the deductor to correct it before you file.
Fixing a mismatch as the deductor
Most mismatches come from a handful of causes. A wrong PAN is the commonest, followed by a challan allocated to the wrong deductee, a deduction booked in the wrong quarter and a short deduction or short deposit noticed later. The usual fix is a correction statement filed on TRACES, after which the certificate can be downloaded again. Keep the original challan counterfoil and the vendor ledger ready while you do this.
Keeping your books ready for Form 16A
Form 16A is easy to produce when your books already record TDS deduction by vendor. In Aicountly Smart Books, the TDS section has Computation, Exceptions, Outstanding and Register tabs. The Exceptions tab sorts problems into data defects, non-deduction, short deduction, excess deduction, short collection and short deposit. A separate Challan reconciliation page lets you record a challan and allocate TDS deductions to it. The TDS Deduction Register can be exported as a CSV, so you can check it against the TRACES statement before you issue certificates.
A quick checklist before you issue certificates
- List every vendor you deducted tax from between July and September, with the section and rate used.
- Match the total deducted per vendor with the figure in the filed 26Q statement.
- Confirm each challan was deposited and shows as matched against the right deductee.
- Verify each vendor's PAN, because a wrong or inoperative PAN is the commonest reason a certificate cannot be generated.
- Keep a note of who received a certificate and on which date, so you can answer follow-up queries quickly.
Doing this once a quarter, rather than in a rush on the last day, usually saves several corrections later.
Key takeaways
- Form 16A is the quarterly TDS certificate for non-salary payments, and the usual date for Q2 is 15 November.
- It is generated on TRACES after the quarterly statement is filed and the challans match.
- Deductees should check it against Form 26AS and AIS before claiming credit.
- Fix mismatches through a correction statement, not by editing the certificate.
- Confirm dates and form numbering on the official portal, and ask your CA about specific cases.
Aicountly Smart Books, the accounting app from Aicountly, can help you keep deductions, challans and vendor-wise TDS in one place. See Aicountly Smart Books if you want your TDS records ready before the next quarter. This article is general guidance, not tax advice.
