Form 16 for Employers: A Payroll Team's Issuance Guide

Form 16 for employers is one of those payroll obligations that looks simple and turns into a three-week fire drill if the groundwork was not laid months earlier. It is a single certificate, usually two or three pages, that tells an employee how much salary you paid them in a financial year and how much tax you deducted and deposited against their PAN. Behind that short document sits a year of monthly TDS computations, four quarterly returns, a set of challans, and a government portal that will happily reject your file over a mismatch of a single rupee.

For HR and payroll teams at Indian SMBs, Form 16 issuance is the moment everything you did during the year becomes visible to employees. If investment declarations were collected late, if a new joiner's previous employer income was never captured, if a challan was tagged to the wrong quarter, the certificate is where it surfaces — usually as a message that begins "my Form 16 doesn't match my payslips." Getting it right is less about tax expertise and more about operational discipline: clean master data, reconciled returns, and a predictable calendar.

This guide walks through the whole process from a payroll operations point of view: what Part A and Part B contain and where each comes from, how Form 24Q feeds the certificate, the end-to-end issuance workflow, the errors that cause the most rework, how corrections and revised certificates work, what to do about mid-year joiners, how the old versus new tax regime election shows up in the document, and how to run the cycle from an HRMS instead of a folder of spreadsheets. Tax rules change every year, so treat this as an operating framework — always confirm current rates, form versions and due dates on the official income-tax portal or with your tax advisor.

What Form 16 Actually Is

Form 16 is a salary TDS certificate. It is the statutory proof an employer gives an employee that tax was deducted at source from salary income and deposited with the government against that employee's PAN.

Two things follow from that, and both matter operationally.

First, it is a certificate of tax deducted, not a payslip summary. It reports the salary accounted for under the head "Salaries" and the tax you actually deducted and deposited. If you deducted nothing, the obligation to issue the certificate may not strictly arise — though many employers issue a salary statement anyway because employees need it for loans and visas.

Second, it is a derived document. You do not write it from scratch. Part A is produced by TRACES from the quarterly TDS returns you filed. Part B is produced from your annual salary computation, and current practice requires employers to generate it through TRACES as well. The certificate is only as accurate as the returns behind it.

Form 16 versus Form 16A versus Form 12BB

These get confused constantly, especially where one person handles both vendor and payroll TDS.

• Form 16 — annual certificate for TDS on salary, issued once per financial year per employee.
• Form 16A — quarterly certificate for TDS on non-salary payments such as contractor, professional fee or rent payments. Different form, different return, different rhythm.
• Form 12BB — an employee-to-employer declaration of proposed investments, rent and other deductions. It is an input to your computation, not an output.
• Form 12B — a statement an employee gives a new employer about salary and TDS from a previous employer in the same year.

A useful mental model: Form 12BB and Form 12B flow into payroll; Form 16 flows out of it.

Who has to issue it

Any employer who deducts TDS on salary must issue Form 16 to that employee, regardless of company size, and for the period of employment even if the employee left mid-year. The obligation attaches to the deductor holding the TAN, not to whoever runs payroll for them.

If you have multiple TANs — separate registrations by state or business unit — the certificate is issued per TAN. An employee transferred between TANs mid-year receives one certificate from each.

Part A and Part B of Form 16 for Employers

The certificate has two parts from two different sources answering two different questions. Part A answers "was the tax actually deposited?" Part B answers "how was the tax computed?"

What Part A contains

Part A is the government-authenticated portion. You generate it by logging into TRACES with deductor credentials, selecting the financial year and quarter range, and requesting the file once your returns have been processed. It typically carries the deductor's and employee's details, the TAN and both PANs, the assessment year and period of employment, a quarter-wise summary of salary paid and tax deducted, the challan details behind each deposit, and a TRACES-generated certificate number with a verification watermark.

The critical point: you cannot edit Part A. The figures are whatever your filed Form 24Q says. If Part A is wrong, the fix is a correction return, not an edit to the PDF.

What Part B contains

Part B is the annexure showing the computation, where an employee can trace the arithmetic from gross salary down to tax payable. It typically includes:

• Gross salary split into salary, perquisites, and profits in lieu of salary
• Allowances exempt to the extent claimed and supported
• Deductions from salary such as standard deduction and professional tax
• Other income the employee asked you to consider
• Chapter deductions — provident fund, insurance, housing loan principal, pension contributions and the rest
• Taxable income, tax on total income, rebate, surcharge, cess, relief and net tax payable
• Tax deducted by the employer and the balance payable or refundable

Part B also carries the declaration signed by the responsible person, with designation, date and place.

Part A versus Part B at a glance

Why you should never hand-build Part A

When TRACES is slow, it is tempting to produce a lookalike certificate from payroll so employees stop asking. Resist it. A document without the TRACES verification number and watermark is not the statutory certificate, and employees who file using it may find their claimed TDS does not match departmental records. If you need an interim document, send a clearly labelled annual salary and TDS statement and say the formal Form 16 follows.

How Form 24Q Feeds Form 16 Issuance

Form 24Q is the quarterly TDS return for salary. Everything in the certificate traces back to it, which is why teams who treat 24Q as background compliance end up with a painful June.

The quarterly rhythm

Each quarter you file a 24Q covering salary paid and tax deducted in those three months, with the challans used to deposit that tax. The return has two annexures, and the difference between them is the single most useful thing to understand about Form 16 issuance.

Annexure I is filed every quarter. It is the deductee-wise breakdown: per employee, the amount paid, tax deducted, date of deduction, and the challan it was deposited under. Annexure I builds Part A.

Annexure II is filed with the fourth quarter only. It is the annual salary detail per employee: gross salary, exemptions, deductions, taxable income, tax computed, regime opted for, relief claimed. Annexure II builds Part B.

The practical consequence: the quality of your Q4 return determines the quality of every Part B you issue. A wrong deduction figure in Annexure II produces the same wrong figure in Part B, and no amount of re-downloading changes it.

Challans, deposits and matching

TDS deducted in a month is deposited by challan by the monthly due date. When you file, you map each deductee row to a challan and to an amount within it. The department matches your claimed details against its record of receipts. Where they match, credit flows to the employee's annual tax statement and into Part A. Where they do not — wrong BSR code, deposit date, assessment year, or section code — the row sits unmatched and the credit never appears.

A few habits prevent most of this:

• Reconcile the bank or payment portal challan file against your own deposit register the same week you pay, not in June
• Check the assessment year on every challan before paying; an AY error is among the most tedious to correct
• Keep mapped deductee amounts within the challan total, since overclaiming causes rejection
• Store challan receipts in the same folder structure every quarter so retrieval is trivial in correction season

Validating before you file

Validation utilities catch structural errors — a missing field, an invalid PAN format, an impossible date — but not a semantically wrong number. A salary figure off by a lakh validates perfectly and produces a perfectly wrong Form 16. Your internal review matters more than the validation step. Before filing Q4, reconcile at a minimum:

• Total gross salary in Annexure II against the payroll register for the year
• Total TDS in Annexure II against total TDS across the four Annexure I filings
• Total TDS in Annexure I filings against total challans deposited
• Headcount in Annexure II against everyone who received salary during the year, including leavers

If those four tie out, most Form 16 problems disappear before they start.

The End-to-End Form 16 Issuance Workflow

Here is the sequence a payroll team should follow. The timing below describes the shape of the year rather than exact deadlines — confirm current statutory dates each year, since they do shift.

1. Close the payroll year. Run the final March cycle, post all arrears, bonuses, settlements and reimbursements belonging to the year, and freeze the payroll register. Nothing moves after this without documented approval.

1. Complete proof verification. Every declared investment and exemption must have supporting proof on file. Anything unsupported is removed from the computation and the resulting tax recovered through payroll — before the year closes, not after.

1. Run the final tax computation. Recompute each employee's annual tax on actuals: salary paid, verified deductions, previous employer income where declared, other income where requested, and the applicable regime. Compare against tax already deducted and settle the difference in the final run.

1. Deposit the final month's TDS. Check TAN, assessment year and section code on the challan, and reconcile the deposit the same day.

1. Prepare and reconcile Q4 including Annexure II. Build the annexure from the final computation, run the four reconciliations above, and have a second person review a sample of unusual cases: leavers, previous employer income, relief claims, regime changes.

1. File the Q4 return by the due date. Keep the acknowledgement, the validated file and the challan status file together.

1. Check the return status on TRACES. Returns are not available for certificate generation immediately. Confirm the statement has been processed and check for defaults — short deduction, short payment, late payment interest, PAN errors. Resolve defaults before generating anything.

1. Request Part A files. Log in as deductor, request Part A for the year, wait for processing, and download. You will need the conversion utility and your account's password convention.

1. Request and generate Part B for the same period, then download and convert it the same way.

1. Merge, sign and quality-check. Combine both parts per employee, apply the digital signature, and sample-check certificates against the payroll register before distribution.

1. Distribute. Publish through employee self-service where possible, with email as fallback, and record the issue date per employee.

1. Archive. Store signed certificates, returns, challans, proofs and computation sheets together for the required retention period.

The parallel leaver workflow

Employees who left mid-year create a second track that is easy to forget until they email you in July.

1. Complete the full-and-final settlement and record it in the correct quarter.
2. Include the leaver in that quarter's Annexure I and in Annexure II for the period employed.
3. Generate their certificate in the normal June cycle alongside everyone else.
4. Send it to the personal email on file, since the work address is deactivated.
5. Keep a documented channel — an alumni mailbox or request form — so ex-employees can reach payroll directly.

Leaver certificates generate a disproportionate share of queries simply because nobody told the employee when to expect the document. One line in the exit letter removes most of them.

The Payroll Year-End Calendar

A workable issuance calendar starts long before the year ends. The table below describes the shape of a typical cycle; verify every statutory date for the current year rather than relying on any published table.

Building backwards from the issuance date

The most common planning mistake is treating the issuance deadline as the start of the work. It is the end. Work backwards: distribution needs signing and quality checks before it; those need TRACES requests, which take time to process and take longer at peak load; those need a filed and processed Q4 return; that needs a reconciled Annexure II; and that needs a closed payroll and completed proof verification.

For an SMB with a couple of hundred employees, this chain realistically needs six to eight weeks of calendar time with slack built in. Planning for two weeks is how teams issue certificates late.

Digital Signatures and Distribution

Signing the certificate

Form 16 can be issued with a digital signature, and for any employer beyond a handful of staff this is the only sensible approach. Practical points:

• The signature should belong to the person authorised to act for the deductor, typically whoever is named on TDS filings
• Keep the signing certificate valid; an expired certificate in early June is a genuinely bad week
• Apply the signature after merging Part A and Part B, so employees receive one signed document rather than two signed halves
• Confirm the signature renders as valid in a standard PDF reader before bulk distribution, since a signature showing as unknown triggers a wave of queries

If you sign manually instead, record the signatory's name, designation and date on each certificate.

Distribution and password practice

Certificates carry PAN, salary and address data, so treat distribution like payslips.

• Prefer self-service download inside the HRMS over email attachments; it gives you an audit trail
• If you email, password-protect the file using a documented convention employees already know, and never send the password in the same email
• For leavers, verify the personal email captured at exit before sending
• Log the date and channel of issuance per employee as evidence in any later dispute

What to publish alongside the certificate

A certificate on its own generates questions; a certificate with a short covering note generates far fewer. Include the period and assessment year covered, a one-line statement of the regime applied, a prompt to cross-check TDS against their own annual tax statement on the income-tax portal, the channel and cut-off for raising discrepancies, and a clear statement that payroll cannot advise on personal tax filing.

Employees Who Joined Mid-Year

This is the largest source of complexity in a growing SMB, because hiring is continuous while tax computation is annual.

The core problem

Tax on salary is computed on total salary income for the year across all employers, but each employer only knows what it paid. If two employers each compute tax on only their own portion, both apply the basic exemption and the lower slabs to their slice, and the employee ends up with a liability at filing time that nobody deducted.

The law anticipates this. The employee can furnish details of previous employment salary and TDS to the new employer, who then computes tax on the combined figure and deducts accordingly. The mechanism is a declaration from the employee — commonly Form 12B — supported by the previous employer's Form 16 or salary statement.

What the employer should do

1. Ask at onboarding, not in January. Make previous employer income a standard joining field for anyone joining after the year starts. Capture gross salary, exemptions, deductions, professional tax and TDS deducted.
2. Ask for supporting documents. The signed declaration is the legal basis; a previous Form 16 or a final payslip with year-to-date figures is the practical verification.
3. Ask which regime the previous employer applied. If it differs from what they want here, flag it early — the computation and eventual filing get complicated.
4. Fold the figures into the computation. Once accepted, previous employer income joins the annual computation and previous TDS counts as tax already deducted for the year.
5. Report it correctly in Annexure II. The annexure has fields for previous employer salary and tax deducted. Filling these is what makes the employee's Part B reconcile.
6. Document a refusal. Employees may decline to share previous employer details. Record it in writing, compute on your portion only, and let the employee settle the difference at filing.

How many certificates will the employee receive

One from each employer who deducted TDS from their salary during the year. Someone who worked at two companies gets two certificates, each covering its own period. The employee aggregates the salary figures and claims the total TDS when filing. Neither employer merges them. Your responsibility ends at issuing an accurate certificate for the period you employed them.

The transfer-between-TANs case deserves attention because employees find it genuinely confusing. If your group restructures or opens a new registration mid-year, brief employees in advance that two certificates are normal.

Old Versus New Tax Regime in the Certificate

The two-regime system has made the computation harder to explain to employees and the election harder to administer.

The operational reality

Under current rules one regime is the default, and an employee wanting the other must positively elect it. You compute monthly TDS on the regime the employee is on, and the annual computation in Annexure II — and therefore Part B — reflects that same regime. Three consequences:

• The certificate reflects the regime you applied, not the one the employee eventually files under. An employee may file under the other regime subject to eligibility. The certificate is still correct; it certifies what you deducted.
• Deduction fields look very different across regimes. Under the concessional regime most familiar deductions are unavailable, so those lines show nil. Employees who have seen an old-regime certificate read this as an error.
• The election must be captured, dated and retained. If an employee later claims you applied the wrong regime, the declaration on file is your evidence.

Running the election cleanly

1. Open the election window at the start of the year, before the first payroll run.
2. Give employees a comparison tool or worked example, framed as information rather than advice.
3. Set a default for non-responders matching the statutory default, and communicate it clearly.
4. Lock the election for TDS purposes after the cut-off, and document your policy on mid-year changes.
5. Record the date, channel and confirmation for every election.
6. Reflect the elected regime in the annual annexure so Part B computes on the right basis.

Communicating regime effects

The most common complaint is "my Form 16 doesn't show my investments." Pre-empt it in the covering note: certificates computed under the concessional regime show nil or minimal figures against most deduction fields because those deductions do not apply; the regime applied is stated in the certificate; employees may still have a choice at filing, subject to eligibility, and should consult a tax professional; and payroll cannot change the regime retrospectively for a closed year, because the certificate follows the filed return. State that last point firmly and early — it is the request payroll receives most often in June and most often has to refuse.

Common Form 16 Issuance Errors and How to Prevent Them

The three checks that catch most problems

If you only have time for a short review, do these:

1. Headcount check. Certificates generated should equal the number of people who received taxable salary during the year — including leavers, including someone who joined in March.
2. Totals check. Gross salary across all Part B documents should reconcile to your annual payroll register, and total TDS to total challans deposited.
3. Outlier check. Pull the ten highest and lowest tax figures and the ten largest variances between tax computed and tax deducted, and review those manually. Errors concentrate in unusual cases.

Corrections and Revised Certificates

Something will be wrong. The question is how quickly you can fix it.

Triage before you correct

Not every complaint needs a correction statement.

• Data is genuinely wrong — salary, deduction, TDS or PAN is incorrect. This needs a correction.
• Data is right but the employee disputes the tax treatment — a computation discussion, not automatically a correction.
• The employee wanted a different regime. Generally not correctable after the year has closed and the return is filed.
• The file will not open or the signature looks odd. A distribution issue, resolved by reissuing the same document.

The correction workflow

1. Log the issue with the employee ID, the disputed field, and the evidence provided.
2. Verify against source — payroll register, challan record, proof file, declaration. Never treat the certificate itself as evidence of what is right.
3. Decide whether the filed return is wrong. If the return is right and the certificate reflects it, there is nothing to correct.
4. Prepare a correction statement for the affected quarter. Salary or deduction errors mean correcting the Q4 annexure; challan or deduction-detail errors mean correcting the relevant Annexure I.
5. File and wait for processing. Corrected data must be processed before a revised certificate can be generated.
6. Regenerate, sign and reissue, clearly marked as a revised certificate.
7. Tell the employee what changed — particularly if they have already filed using the earlier version, in which case they should consult their tax advisor.
8. Record the root cause and fix the process that produced it.

Batch corrections into a small number of statements rather than one per employee, set a communicated cut-off for raising discrepancies, and be honest about timelines: a correction requires a return to be filed and processed, and that is not a same-day turnaround.

Handling Employee Queries

Form 16 season generates more inbound questions than any payroll event except salary revisions, and most of them are the same ten questions.

Publish a one-page explainer alongside the certificates covering what the document is, how to read the main sections, why deduction lines may show nil, how to cross-check against their own annual tax statement, what payroll can and cannot do, and how to raise a discrepancy. This single document typically removes the majority of tickets.

Then draw the advice line clearly. Payroll can explain what a figure represents and where it came from, and can correct a factual error in the underlying data. Payroll cannot advise which regime an employee should file under, whether a particular investment is deductible in their circumstances, or how to complete their return. Employees with tax questions should consult a qualified professional. Put this in the covering note; it protects your team and sets a reasonable expectation.

Finally, route everything through a single intake — a form or dedicated mailbox — rather than direct messages to individual payroll staff. Categorise each query as reissue, explanation, or correction. Reissues and explanations should close within a day or two; corrections follow the longer statutory path and need realistic timelines from the start.

Running Form 16 Issuance from an HRMS

Everything above can be done with spreadsheets, a TRACES login and patience. SMBs move to an integrated system not because the manual route is impossible, but because it is fragile: it depends on one person remembering the sequence, and it breaks the year they are on leave in June.

What integration actually changes

• Single source of salary data. Payroll, attendance, reimbursements and settlements feed one register, so the annual annexure is built from data rather than reassembled from exports.
• Declarations and proofs in the same system. Regime elections, investment declarations and proof documents arrive through self-service; approvals flow straight into the computation instead of living in an inbox.
• Automatic recomputation. When a proof is rejected or an arrear posted, the annual projection updates and remaining months' TDS adjusts.
• Return-ready outputs. The system produces quarterly return files including the annual annexure, with internal reconciliations already run.
• Bulk certificate handling. Downloaded files are converted, merged per employee, digitally signed and published to self-service in one operation, with an issuance log.
• Audit trail. Every declaration, approval, computation change and document issue is timestamped and attributable.

What an HRMS does not do

Be realistic about the boundary, because vendors are not always precise here. It does not file your return without review — someone still checks the numbers. It does not remove the TRACES dependency, since both parts originate there and portal downtime is still downtime. It does not fix bad inputs: a wrong PAN entered at onboarding is a wrong PAN in the return. And it does not make tax decisions. Regime policy, exemption treatment and unusual allowances remain your calls, taken with your advisor.

What to look for when evaluating

• Support for multiple TANs and entities if your group has them
• Declaration and proof verification workflows with configurable windows and reminders
• Regime election capture with dated records and a configurable default
• Previous employer income fields on the joining workflow, feeding the computation automatically
• Full-year population handling so leavers are never dropped from the annexure
• Reconciliation reports tying the annexure to the payroll register and to challans
• Bulk merge, digital signature and self-service publishing
• A retained archive that ex-employees can still access

A pre-season readiness checklist

Run this in the final quarter of the financial year, before the crunch:

• PAN verified and name-matched for every active and exited employee
• Regime election on file and dated for everyone
• Previous employer details captured for every current-year joiner, or a documented refusal
• Proof verification complete with unsupported claims reversed
• All four quarters filed and acknowledged, with no open defaults for the year
• Challan register reconciled to the payroll register
• TRACES credentials working and the authorised person's details current
• Digital signature certificate valid well past the issuance date
• Personal email addresses on file for all leavers
• Employee communication drafted and scheduled
• A named owner and a named backup for the process

Teams that clear this list in February have an uneventful June. Teams that start it in May do not.

Frequently Asked Questions

Is an employer required to issue Form 16 if no tax was deducted?

The obligation to issue a salary TDS certificate arises where tax has actually been deducted from salary. Where none was deducted, many employers still issue an annual salary statement because employees need it for loans, visas and record-keeping, even though it is not the statutory certificate. Confirm the current position with your tax advisor if your policy is to issue nothing.

Can we generate Form 16 before filing the Q4 return?

No. Both parts are generated through TRACES from returns you have filed, and Part B depends specifically on the annual salary annexure submitted with the fourth-quarter return. Until that return is filed and processed, there is no data for the portal to generate certificates from.

What happens if Form 16 is issued late?

Late issuance can attract a penalty calculated on a per-day basis, and repeated lateness is the kind of thing that surfaces in an audit. More immediately, employees cannot complete their own filing without it. Confirm the current penalty amount and any cap with your advisor, and plan the calendar backwards from the issuance date.

An employee's Form 16 does not match their annual tax statement. What now?

Compare both against your own records first: payroll register, challans filed, and the deductee rows in the relevant quarter's return. A mismatch usually means a challan did not match, a PAN was wrong, or a deductee row was omitted. If the underlying return is wrong, file a correction statement for that quarter and regenerate the certificate once it is processed.

Do we issue separate certificates if an employee moved between our group entities mid-year?

If the entities have different TANs, yes — each issues a certificate for the period of employment under it. Employees often read this as an error, so explain it in advance. The receiving entity should treat the earlier period as previous employment income so the annual computation is correct.

Can we change an employee's tax regime after the year has closed?

Generally no, as far as the certificate is concerned. It reflects the computation reported in your filed return, which reflects the regime applied during the year. Employees may still have options when filing their own return, subject to eligibility rules, and should discuss that with a tax professional rather than with payroll.

How long should we keep Form 16 records and supporting files?

Keep signed certificates, filed returns, challans, computation sheets, declarations and proof documents together for the retention period required by tax law and by your auditors, which is measured in years rather than months. Keeping the full set for the same period as your other statutory records is simpler than tracking a separate rule per document type. Confirm the applicable period with your advisor.

Conclusion

Form 16 issuance is not a June task. It is the visible end of a year-long process that starts with a PAN captured correctly at onboarding, runs through twelve months of accurate deductions and deposits, passes through four quarterly returns, and only then becomes a certificate. Teams that treat it that way issue clean certificates on time with a handful of queries. Teams that treat it as a June task spend June filing corrections.

The operating principles are straightforward. Collect regime elections and previous employer details before the first payroll run. Reconcile challans monthly rather than annually. Enforce the proof verification cut-off. Reconcile the Q4 annexure to the payroll register before filing. Clear defaults before requesting certificates. Build the calendar backwards from the issuance date with slack for portal delays. Communicate to employees before they have to ask. And verify every rate, form version and deadline against the official income-tax portal or with your tax advisor each year, because the details do change.

If your team runs this from spreadsheets and shared inboxes, the work is doable but the process is fragile. CozyHR handles payroll, TDS computation, investment declarations and proof verification, quarterly return preparation and Form 16 generation in one place, with the reconciliations and audit trail built into the workflow rather than bolted on in June. If that would take some pressure off your next year-end, it is worth a look — and if your current process already works, keep it and use the checklists above to stress-test it before the season starts.