Form 24Q Filing: The Payroll Team's Quarterly Guide

Every payroll team in India lives on a four-beat drum. Salaries go out monthly, but the compliance record of what you withheld from those salaries is submitted four times a year, and that record is the quarterly TDS return known as Form 24Q. Form 24Q filing is the single process that converts twelve months of payroll arithmetic into a government-readable statement of TDS on salary, employee by employee, rupee by rupee, challan by challan.

Get it right and nobody notices. Get it wrong and the consequences arrive months later, in the form of portal defaults, employee complaints about missing tax credit, and a Form 16 that nobody trusts. This guide is written for the people who actually do the work: payroll managers, HR operations leads, finance associates and founders who signed up to build a company and somehow ended up owning a quarterly statutory return.

We will walk the full operating loop, from freezing payroll to issuing Form 16, including the reconciliation habits that prevent problems rather than chase them. One standing caveat before we begin: due dates, fee amounts, interest rates, threshold limits and utility versions change. Treat everything here as a description of mechanisms, not as a substitute for checking the current position on the income tax department's portals or with your tax advisor.

What Form 24Q Actually Is

Form 24Q is the quarterly statement a deductor files to report tax deducted at source from salary payments. It is filed under the salary TDS provisions of the Income-tax Act, and it is submitted for each quarter of the financial year against your TAN.

The form has two distinct personalities inside it. Annexure I is the transactional layer: for each quarter, it lists which challan you paid, and against that challan, which employees were deducted from and for how much. Annexure II is the analytical layer: it is the annual salary statement for each employee, and it is normally required only in the final quarter of the financial year.

That structure explains almost everything about how the year feels. Three quarters are mechanical and challan-driven. The fourth quarter is a full-year tax computation exercise wrapped in a filing deadline.

How Form 24Q Differs From Form 26Q and Form 27Q

Payroll teams often inherit a spreadsheet labelled "TDS returns" that mixes up the forms. Keeping them separate is the first act of hygiene.

Three practical implications follow. First, a retainer or consultant who invoices you is not an employee, so their deduction belongs in Form 26Q, not in your Form 24Q filing. Second, a director's sitting fee is typically a non-salary payment even though the person sits in your board meetings. Third, if you second an employee abroad or engage a non-resident individual outside an employment relationship, the reporting form and the withholding logic can both change, so take advice rather than assuming.

The most common structural error we see is a payroll team pushing a consultant's TDS into the salary return because "the payment ran through payroll." The form follows the nature of the payment, not the system that generated the payment.

How Form 24Q Connects to Form 16, Form 12BB and the Annual Statement

Think of four documents as one chain, each feeding the next.

Form 12BB is where the employee declares what they intend to claim: house rent, interest on housing loan, deductions under the relevant chapter, and so on, along with the evidence they will produce. It is an input to your computation, not a filing in itself.

Your monthly TDS computation uses those declarations, applies the regime the employee has chosen, and produces a monthly deduction. Those deductions are deposited by challan and reported in Annexure I each quarter.

Annexure II in the final quarter reports the full-year salary breakup and the final tax computation per employee. This is the data that ultimately underpins Form 16 Part B.

Form 16 Part A is not something you type. It is generated from TRACES, based on what your filed returns and challans say. That is why Form 16 Part A is effectively a receipt for the accuracy of your Form 24Q filing. If your quarterly returns are wrong, the Part A that TRACES produces will be wrong too, and you cannot fix it by editing a PDF.

The employee's tax credit statement, which they see when filing their own return, is likewise built from your filings. So the same underlying data reaches the tax authority, the employee's Form 16 Part A, and the employee's tax credit statement. One error propagates to all three.

The Quarterly Rhythm of Form 24Q Filing

Quarters One Through Three: The Mechanical Quarters

In the first three quarters, Form 24Q filing is essentially a challan-and-deductee exercise. You report the challans you deposited for that quarter's salary months, and you allocate each challan across the employees whose deduction it covers.

The main risks in these quarters are boring but expensive: a challan entered with the wrong assessment year, a deductee row with a PAN that does not exist, a total that does not tie to the challan, or a missing employee who joined mid-quarter.

There is no full-year computation in these quarters, which is precisely why teams get complacent and then discover in the fourth quarter that nine months of allocation errors need correcting.

The Final Quarter: The Annual Reckoning

The last quarter of the financial year carries Annexure II, the annual salary statement. For every employee who was on your rolls at any point during the year, you report the gross salary, the exempt components, the deductions claimed, the taxable income, the tax computed, relief claimed, and the tax deducted.

This is where the year's assumptions get audited by arithmetic. Proof submission has closed, declarations that went unsupported have been reversed, previous-employer salary has been folded in, and the last months' deductions have been trued up.

The final quarter also has a longer preparation window than the others in most years, and there is a reason for that: the volume of computation is genuinely larger. Use the window; do not treat it as a buffer for procrastination.

A Generic Quarterly Calendar

Do not memorise dates from a blog post, including this one. Verify the current due dates on the income tax portal each year, because they move, and because relief notifications occasionally extend them. What you can rely on is the pattern.

Note the asymmetry: monthly TDS deposit deadlines run on their own clock, generally shortly after the month in which deduction happened, with a special rule for the last month of the financial year. Deposit deadlines and return deadlines are different obligations with different consequences, and a team that meets one while missing the other still has a problem.

Prerequisites: What Must Be In Place Before You File

TAN and Deductor Details

You file against a TAN, not a PAN. If your company has multiple branches or business units with separate TANs, you file separate returns for each, and the employee's deduction must sit under the TAN that actually deposited the tax.

Deductor details in the return must match what the department has on record: name, category, address, contact details, and responsible person. A mismatch here is a nuisance that shows up as validation failure or as a correction requirement later.

If an employee transfers between two of your TANs mid-year, that is a design decision with real consequences. Decide the policy in advance, because the employee's tax credit will be split and their Form 16 handling changes.

Authorised Signatory, DSC and EVC

Someone real has to stand behind the return. That person is the responsible person for TDS purposes, and their name, designation, PAN and contact details go into the return.

For electronic submission through the reporting portal, you generally authenticate either with a digital signature certificate registered to the authorised signatory, or with an electronic verification code route. DSC is the more common choice for companies, especially where the signatory is a director or CFO who already holds a certificate for other filings.

Practical warnings that cost people quarters: DSC tokens expire, the driver software breaks after operating system updates, the signatory changes jobs and nobody updates the portal profile, and the person holding the token is on leave in the filing week. Keep a calendar reminder for certificate expiry and always have a documented backup signatory.

Portal Registrations

You will interact with more than one portal. At a minimum, you need the ability to prepare and validate the return file, submit it, and then retrieve outcomes.

TRACES is where post-filing life happens: statement status, justification reports for defaults, correction requests, consolidated files for revision, PAN verification utilities, and Form 16 Part A downloads. If your organisation is not registered on TRACES against your TAN, you are effectively filing blind.

Register early, keep the login with at least two people, and record the security answers somewhere your team can retrieve them. A locked TRACES account in the week before Form 16 issuance is a self-inflicted crisis.

PAN Quality of Employees

PAN is the hinge on which the entire tax credit mechanism swings. A structurally valid PAN that belongs to someone else is worse than a missing PAN, because the credit goes to a stranger and the error is harder to detect.

Run bulk PAN verification against the employee master before every quarter's Form 24Q filing, not just at onboarding. Check that the name associated with the PAN matches the employee's name in your records, allowing for the usual initials-and-surname variations but investigating genuine mismatches.

Where an employee has not furnished a valid PAN, a higher withholding rate applies and the consequences flow to both of you. Verify the current rate and treatment rather than relying on remembered figures, and document the communications you sent asking for the PAN.

The End-to-End Form 24Q Filing Process, Step by Step

This is the operating sequence. Each step has an owner, an output and a check.

1. Freeze payroll for the quarter. Lock the three months' payroll registers so that no retrospective edits creep in after you have deposited tax. If a correction is genuinely needed, process it as a current-month adjustment rather than reopening a closed month.

1. Compute and true up TDS on salary. Recompute the projected annual tax for each employee based on current declarations, regime selection, actual payouts to date and any proofs received. Confirm that the deduction actually made in each month equals what your computation says it should have been.

1. Deposit challans on time, month by month. Salary TDS is deposited monthly, not quarterly. Use the correct assessment year, the correct TAN, the correct section code for salary, and the correct nature of payment. Split the amount correctly between tax, surcharge, cess, interest and fee fields, because misallocation inside a challan causes matching problems later.

1. Collect CIN details for every challan. For each deposit, capture the BSR code of the bank branch, the date of deposit, the challan serial number and the amount. This tuple is what the system uses to match your return to the money. Save the challan receipt as a PDF in a quarter folder, named consistently.

1. Verify challan status before you prepare the return. Confirm each challan appears with the expected amount and assessment year in the challan status enquiry facility. A challan that has not landed correctly will cause an unmatched status and a default, no matter how clean your return is.

1. Prepare Annexure I, the deductee-wise details. For each challan, list every employee against whom that challan's tax was deducted, with PAN, name, amount paid or credited, date of payment, tax deducted, tax deposited and date of deduction. The sum of deductee rows against a challan must equal the challan amount available for allocation.

1. Handle non-deduction and lower-deduction cases explicitly. Where no tax was deducted for an employee in the quarter, or where a lower or nil deduction certificate applies, use the prescribed reason codes rather than silently omitting the employee. Silent omission is how employees fall off the annual statement.

1. Prepare Annexure II for the final quarter. Build the annual salary statement for each employee: gross salary and its components, exempt allowances, perquisites, profits in lieu, deductions claimed, previous-employer salary where furnished, taxable income, tax on total income, relief claimed, and total tax deducted for the year. This annexure must reconcile to the sum of the year's Annexure I entries for that employee.

1. Validate the file. Use the current return preparation and file validation utilities. The validation utility checks structural rules, PAN formats, date logic, control totals and challan-deductee consistency. Fix every error, and read the warnings rather than dismissing them, because warnings are frequently the early signal of a matching problem.

1. Generate the validated file and the control summary, then submit. Depending on your filing route, you either upload the validated file through the reporting portal with DSC or EVC authentication, or submit it through an authorised facilitation centre. Retain the acknowledgement, the token or provisional receipt number, and the exact file you submitted.

1. Track processing status and download the outcome. A few days after submission, check the statement status on TRACES. You are looking for the statement to be processed. If it is processed with defaults, download the justification report and work through it line by line.

1. Issue Form 16. After the final quarter's return is processed, download Form 16 Part A from TRACES for each employee and pair it with Part B. Distribute securely, and keep a distribution log with dates and delivery method.

A note on step 12: Part A must come from TRACES. It carries the authentication that ties it back to your filings. Manually prepared substitutes are not equivalent, and employees increasingly know the difference.

Government Versus Non-Government Deductors: Challan and Book Entry

Most private employers deposit tax by challan through a bank or online payment, and the resulting Challan Identification Number is what they quote in the return. If that is you, the rest of this section is background knowledge.

Government deductors frequently do not pay by challan at all. The tax is transferred by book adjustment within the government accounting system, and the credit is evidenced not by a CIN but by a Book Identification Number.

The BIN is produced from a separate statement filed by the accounts officer or drawing and disbursing officer for the government entity. It consists of a receipt number, a serial number and a date, and it plays exactly the same role in Form 24Q filing that the CIN plays for a private employer: it is the anchor to which deductee rows are attached.

The practical difference is dependency. A private employer controls its own challan and can fix a problem by paying again. A government deductor depends on someone else filing the upstream statement correctly and on time, so BIN unavailability becomes a common cause of delayed or defective returns. If you work in a government or quasi-government body, build a monthly follow-up habit with your accounts office rather than discovering the gap at quarter end.

If you are a private employer with a public-sector-style structure, or a body funded by government, confirm your category before filing. Choosing the wrong deductor category produces validation failures and, worse, a return that does not match how your tax actually reached the exchequer.

Data Hygiene: The Employee Master That Makes or Breaks Your Return

Most Form 24Q filing failures are not tax-technical. They are master-data failures wearing a tax costume.

PAN Validation and the Fields That Matter

Validate PAN in bulk before every quarter, not just at onboarding. Look for three failure classes: structurally invalid PAN, valid PAN that does not exist in the database, and valid PAN whose registered name does not resemble the employee's name.

The third class is the dangerous one. A transposed digit can still yield a valid PAN belonging to a real person, and your employee's credit disappears into their account. Escalate name mismatches with a request for a PAN copy, and check for duplicate PANs, which usually signal a rehire recorded as a new employee.

The fields that actually drive a clean return are narrower than everything your HRMS holds: PAN, full name as per PAN, date of joining, date of leaving, employment type, tax regime election, residential status, and whether previous-employer salary has been furnished. Concentrate your quality checks there.

Mid-Year Joiners and Leavers

A joiner's tax is computed on the salary they will receive from you for the remaining months, plus any previous-employer income they choose to declare. If they do not declare it, you compute on your salary alone and they settle the difference in their own return, which frequently produces an unpleasant surprise for them in July.

A leaver must still appear in the annual annexure for the year, with the salary you paid and the tax you deducted, even though they have left. Their Form 16 for that period is your obligation.

Full-and-final settlements are a chronic source of error. Notice pay recovery, leave encashment, gratuity treatment and unvested benefits all change the taxable figure, and the settlement often runs outside the regular payroll cycle. Make sure the settlement's TDS is deposited with the right month's challan and reported in the right quarter.

Previous-Employer Salary

When an employee furnishes previous-employer salary details in the prescribed manner, you are expected to consider them in your computation. When they do not, you compute on your own payments. Either way, record the decision.

In the annual annexure, previous-employer salary is reported distinctly from salary paid by you, and mixing the two distorts both the annexure and the resulting Form 16. Ask for the previous employer's Form 16 or the prescribed statement rather than a payslip screenshot, and set a cut-off date, because a declaration arriving in the last week of March cannot be absorbed into a deduction schedule that has already run.

Employees on Two Different Tax Regimes

Your workforce will be split across regimes, and the split shifts when employees revisit their choice. Your computation engine has to hold both logics: one with a wide set of exemptions and deductions, one with a broader base and different slabs.

Three rules keep this manageable. Capture the election explicitly with a timestamp rather than inferring it. Communicate a clear window in which it can be changed for withholding purposes. And remind employees that their withholding election and their final position in their own return are related but not identical, so they should take their own advice.

Because regime rules and default treatments have changed in recent years, confirm the current default and election mechanics before each financial year begins rather than carrying forward last year's configuration.

Perquisites, Arrears and Exempt Allowances

Perquisites are where payroll data and finance data have to meet: accommodation, motor car, concessional loans, employer contributions above prescribed limits, stock-based benefits and gifts all carry valuation rules. The usual failure is not a wrong valuation but a perquisite that finance knows about and payroll does not, discovered in March. Set a standing quarterly request to finance and to whoever administers your equity plan, and report perquisites in their own fields rather than bundling them into basic salary.

Where arrears relating to earlier years are paid, the employee may be entitled to relief that spreads the tax impact. Ask for the prescribed claim form and the year-wise working, keep the file, and do not grant relief on the strength of an email. If you are unsure whether a payment qualifies, take advice before the payout rather than after.

Exempt allowances must be reported as exemptions in the annual annexure, not quietly netted off gross salary. House rent allowance is the perennial issue: receipts without a landlord PAN where one is required, rent paid to a family member without evidence of a real arrangement, claims that continue after the employee has moved. Build the proof rules into the declaration workflow so incomplete claims never reach a reviewer, and when a claim is genuinely doubtful, disallow it at the withholding stage and let the employee claim it in their own return.

Non-Resident and Expat Edge Cases

Residential status changes the withholding analysis, and inbound or outbound assignees raise questions about which country taxes which portion of the compensation, whether a treaty applies, whether social security agreements matter, and whether tax equalisation changes the gross-up.

These cases are genuinely specialist. Flag travel and assignment data in the employee master so you identify them early, get written advice for each fact pattern, and confirm which return form applies, because salary paid to a non-resident may need different treatment and the reporting consequence follows from that determination.

The Salary TDS Reconciliation Playbook

Reconciliation is the difference between a payroll team that files and a payroll team that files with confidence. The discipline is simple: four independent records should tell the same story.

The Four Ledgers

Ledger one: the payroll register. What you computed and withheld, per employee, per month.

Ledger two: the challan record. What you actually deposited, per challan, with CIN or BIN details.

Ledger three: the return. What you reported in Annexure I, and in the final quarter, Annexure II.

Ledger four: the tax credit statement. What the system shows as credited to each employee, and what TRACES shows as matched at the challan level.

If ledgers one and two disagree, you have a deposit problem. If two and three disagree, you have an allocation problem. If three and four disagree, you have a matching or processing problem. Diagnosing in that order saves hours.

A Reconciliation Table Template

Run this at the end of every month and again before every Form 24Q filing. Keep it in one place, versioned, with the preparer and reviewer named.

Lines C, E and H should be zero every month. When they are not, the explanation goes in a note beside the number, not in someone's memory. Line K will rarely be zero because employees with nil deduction may be treated differently, but every difference should have a written reason.

Tracing Common Mismatches

The reconciliation habit that pays for itself: after each quarter's return is processed, pull the tax credit position for a random sample of ten employees and confirm it matches your payroll register. Ten employees takes twenty minutes and catches systemic errors before they become an annual mess.

Corrections and Revised Returns

What Corrections Actually Are

A correction statement does not replace your original return. It amends specific parts of it, referencing the original filing, and the amendments are layered on the existing record.

Conceptually, corrections fall into a few categories: updating deductor details such as address or responsible person; updating challan details where an amount, date or identification number was captured incorrectly; adding a challan that was omitted; updating deductee details by adding, removing or reallocating rows; correcting a PAN, which is treated as sensitive and has its own constraints; and correcting the annual salary annexure in the final quarter.

The correction utilities label these categories with codes. The usual route is to download a consolidated file of your filed data from TRACES, import it into the preparation utility, make the change, revalidate and submit. Some smaller corrections can be done through online correction facilities directly on the portal.

When to File a Correction

File a correction when the facts have changed or when an error affects an employee's tax credit or the department's record. Four triggers dominate: a default appearing in the statement status, an employee reporting missing credit, an omitted employee or challan surfacing in your own reconciliation, and a year-end discovery that an earlier quarter was misallocated.

Do not batch corrections indefinitely. An unresolved first-quarter error distorts the annual annexure, which distorts Form 16, which produces a wave of employee queries in the peak filing season. Note also that a correction is not resolved when submitted, only when the status clears.

How to Avoid Needing Corrections

Corrections are cheap in money and expensive in attention. The habits that reduce them are unglamorous.

• Verify challan status before, not after, preparing the return.
• Run PAN verification every quarter, not once at onboarding.
• Tie deductee totals to challan amounts before validation, not after rejection.
• Read validation warnings, not just errors.
• Reconcile monthly so that quarterly filing is confirmation rather than discovery.
• Keep a single source of truth for the tax regime election and declaration status.
• Get finance to confirm perquisites quarterly instead of annually.
• Freeze payroll properly, so that the register you reconciled is the register you filed.

When Things Go Wrong: Fees, Interest and Defaults

There are four broad exposure categories, and they behave differently. Verify the current amounts, rates and computation mechanics with the department or your advisor, because they are periodically revised and because the details matter more than the headline.

Late filing fee. A fee accrues for each day the return is late, running until it is actually filed, and it is generally subject to a cap linked to the tax amount in the statement. This fee is not discretionary the way a penalty is; it attaches to the delay itself, and in practice it has to be settled before the statement goes through cleanly.

Interest on late deduction. If tax should have been deducted in a particular month and was not, interest runs from the date deduction was due to the date it was actually made. This commonly arises when a perquisite or a bonus is discovered late.

Interest on late deposit. If tax was deducted on time but deposited late, interest runs from the date of deduction to the date of deposit. This rate is typically higher than the late-deduction rate, which tells you how the law views holding on to money you have already withheld.

Defaults raised on the portal. After processing, your statement may show short deduction, short payment, late payment interest, late deduction interest or late filing fee, and TRACES provides a justification report explaining line by line how each was computed. Separately, there are penalty provisions for prolonged non-filing and for furnishing incorrect information, with their own conditions. If you are in that territory, involve your tax advisor rather than self-diagnosing.

How to Respond to a Default Notice

Start by downloading the justification report and reading it against your own working papers. A large share of defaults turn out to be data artefacts rather than genuine shortfalls: an employee reported twice, a challan mapped to the wrong quarter, a deduction date typed as the payment date.

For genuine shortfalls, compute the amount owed including interest, deposit it with a challan referencing the correct assessment year and section, then file a correction statement mapping the new challan to the affected deductees. For artefacts, file the correction that fixes the data and monitor the status until the default clears.

Keep a short memo for each default explaining what happened and what changed, because the same question will be asked at audit. Respond within the timeline stated in the communication, and if you need more time, say so in writing rather than going silent.

Worked Example: A Sixty-Employee Company's Quarter

The numbers below are illustrative and invented for teaching purposes. They are not benchmarks, averages or anything you should copy into a model.

Meet Tanager Systems, a hypothetical sixty-person product company with a single TAN. Its second-quarter payroll looks like this.

Two employees joined in August, one resigned in September with a full-and-final settlement, and one employee's PAN failed verification in July.

Now the reconciliation the payroll manager runs before Form 24Q filing.

The difference between 63 employees on roll and 47 deductee rows is explained in a note: sixteen employees had no tax deducted in the quarter because their projected annual income after declared deductions fell below the taxable threshold, and they are handled per the company's documented policy on nil-deduction reporting.

The resigned employee's settlement was paid in September and its TDS of 84,000 is inside the September figure. The payroll manager checks specifically that the settlement's deduction date and the September challan date are consistent, because settlements processed off-cycle are the classic source of date mismatches.

The July PAN failure was resolved on 12 August when the employee produced a PAN card copy. Because the deduction for July had already been made at the higher no-PAN rate, the manager documents the sequence, reports the correct PAN in the return, and notes that the excess will adjust across the remaining months of the year through the annual computation.

Finally, the manager samples five employees, compares their year-to-date deduction in the payroll register against what the return will report, and signs the reconciliation. Total time: about three hours. Total corrections needed later: zero.

Contrast that with the alternative. A team that skips this reconciliation files a return where the September challan is entered with the previous assessment year, discovers the unmatched challan when a default notice arrives in December, spends a day understanding the justification report, files a correction, and answers eleven employee emails about missing credit. Three hours versus three days.

The Quarter-End Checklist

Print this, or better, turn it into tasks with owners and dates in whatever tracker your team uses.

Payroll and computation

1. All three months' payroll registers locked and signed off.
2. Off-cycle payments, bonuses and incentives included in the correct month.
3. Full-and-final settlements processed and their TDS identified.
4. Perquisite data received from finance and the equity administrator.
5. Arrears identified and relief claims documented where applicable.
6. Tax regime election confirmed and current for every employee.
7. Declaration and proof status reviewed; unsupported claims reversed per policy.
8. Previous-employer salary declarations recorded for joiners.
9. Lower or nil deduction certificates on file and applied correctly.
10. Projected annual tax recomputed and monthly deduction trued up.

Master data

1. Bulk PAN verification run for all active and separated employees.
2. Name-versus-PAN mismatches escalated and resolved or documented.
3. Duplicate PANs and duplicate employee records checked.
4. Dates of joining and leaving accurate for everyone who moved.
5. Residential status flags reviewed for anyone with international movement.

Challans

1. Every month's TDS deposited by the applicable deadline.
2. Correct assessment year, TAN, section code and nature of payment on every challan.
3. Tax, surcharge, cess, interest and fee correctly split within each challan.
4. Challan status verified as available and matching the deposited amount.
5. Challan receipts saved in the quarter folder with a consistent naming convention.

Return preparation

1. Deductee rows prepared for every employee with deduction in the quarter.
2. Nil-deduction and lower-deduction cases reported with the correct reason codes.
3. Deductee totals tied to challan amounts, challan by challan.
4. Annexure II prepared and reconciled for the final quarter only.
5. Return prepared using the current utility version.
6. Validation run, all errors cleared, all warnings read and dispositioned.
7. Control summary reviewed against the reconciliation table.

Filing and aftermath

1. Authorised signatory available; DSC valid or EVC route confirmed.
2. Return submitted and acknowledgement or token number saved.
3. Statement status checked after processing.
4. Justification report downloaded and worked if any default appears.
5. Sample of ten employees' tax credit verified against the payroll register.
6. Reconciliation file archived with preparer and reviewer names.

A Week-by-Week Close Plan

Deadlines shift, so this plan is expressed relative to the quarter end rather than in calendar dates. Adjust the compression for the final quarter, which needs more runway.

The last two weeks of the quarter. Chase the inputs that always arrive late: perquisite data from finance, equity events, settlement calculations for leavers, and outstanding PAN submissions. Send the reminder before you need the data, not when you need it.

Week one after quarter end. Close the third month's payroll and deposit its TDS by the applicable deadline. Run bulk PAN verification. Complete the monthly reconciliation for all three months and resolve every non-zero difference.

Week two after quarter end. Verify all three challans' status. Prepare the return in the utility. Tie deductee allocations to challans. For the final quarter, this is when the annual annexure build begins and it will take longer than you think.

Week three after quarter end. Validate, clear errors, review the control summary against your reconciliation table, and get the reviewer's sign-off. Confirm signatory availability and DSC validity. File. Save the acknowledgement.

Week four after quarter end. Check statement status. Work any defaults. Sample-check employee credits. Archive the quarter file. Write the two-line note on what went wrong this quarter so next quarter is easier.

That deliberate one-week buffer before the deadline is the single highest-return habit in this entire guide. Every team that files on the last day eventually files late, because eventually a token expires or a portal is slow.

Automation: What Payroll Software Should Do, and What You Still Check

Automation should remove the arithmetic and the transcription, not the judgement.

The judgement items are not a failure of automation. They are the reason a payroll professional is worth employing.

Common Mistakes in Form 24Q Filing

Treating quarterly filing as the first reconciliation. If the quarter-end is where you discover problems, you have already lost the time you needed to fix them.

Wrong assessment year on a challan. Easy to do, painful to unwind, and the most frequent cause of unmatched challans.

Omitting nil-deduction employees without a policy. Decide your treatment, document it, apply it consistently, and be able to explain it.

Reporting a consultant in the salary return. The form follows the nature of the payment.

Letting the annual annexure disagree with the year's quarterly returns. These two must reconcile per employee. If they do not, Form 16 will be wrong and TRACES will notice.

Editing Form 16 Part A. Part A is generated from filings. If it is wrong, the filing is wrong.

Ignoring warnings during validation. Errors block you; warnings are the ones that produce defaults three months later.

Single-person dependency on DSC and portal credentials. Every quarter-end crisis has a person on leave in it.

Waiting for perquisite data until March. Ask quarterly. Finance will not volunteer it.

Not documenting the reason for every variance. A variance without a written reason is an unexplained variance at audit, regardless of what you remember.

Assuming the regime default hasn't changed. Confirm the current position at the start of every financial year.

Filing a correction and never checking whether it processed. Submission is not resolution. Watch the status until the default clears.

How CozyHR Helps With Form 24Q Filing

CozyHR is built for Indian payroll teams, which means the quarterly TDS return is treated as a first-class workflow rather than an export you wrestle into shape.

TDS computation runs continuously across both tax regimes, with monthly true-up as declarations, proofs and actual payouts change, so the number you deduct in month nine already reflects what you know in month nine.

The declaration and proof workflow gives employees self-service capture with the evidence rules built in, and gives reviewers a queue rather than an inbox. Unsupported claims reverse on your policy schedule instead of being remembered by one person in March.

Challan tracking keeps the payable summary, the deposit record and the CIN details in one place, with reminders ahead of monthly deadlines and a running view of what has been deposited against what was computed.

Return-ready exports produce deductee-wise data mapped to the structure the preparation utility expects, with challan mapping already allocated and control totals visible before you validate. The annual salary annexure rolls up from the same data that produced your monthly deductions, so the two reconcile by construction rather than by effort.

Form 16 distribution closes the loop, pairing Part B generation with secure delivery and a distribution log, so the July question "did I get my Form 16" has an answer that takes ten seconds.

None of this removes your judgement on perquisites, relief claims or expat fact patterns. It removes the transcription, the chasing and the arithmetic, which is where the hours actually go.

Frequently Asked Questions

Is Form 24Q required if no tax was deducted in a quarter?

Practice varies and the position has evolved. Many deductors either file with nil-deduction reporting or lodge a declaration for non-filing on the portal, so that the silence is not read as non-compliance. Confirm the current requirement for your situation with your tax advisor, and document whichever route you take.

Can I file Form 24Q without an employee's PAN?

You can file, but the consequences are real: a higher withholding rate typically applies, the employee's credit does not flow through cleanly, and your return may attract a default. Verify the current rate and treatment, keep evidence of your requests to the employee, and correct the return once the PAN is furnished.

What is the difference between Annexure I and Annexure II?

Annexure I is the quarterly deductee-wise detail: which challan, which employee, how much, on what date. Annexure II is the annual salary statement per employee, filed in the final quarter, carrying the full-year computation that underpins Form 16 Part B. The two must reconcile per employee across the year.

How does Form 24Q filing affect Form 16?

Directly and completely. Form 16 Part A is generated from TRACES on the basis of your filed returns and matched challans, and Part B reflects the annual computation in the final quarter's annexure. If a challan is unmatched or an employee is misreported, Form 16 will show it, and you cannot fix it without fixing the return.

What should I do if a default appears after filing?

Download the justification report from TRACES and read it against your working papers to decide whether the default is a genuine shortfall or a data error. For shortfalls, deposit the amount with applicable interest and map the new challan to the affected deductees through a correction. For data errors, file the correction and monitor status until it clears.

Do government deductors file Form 24Q differently?

The form and annexures are the same, but the payment evidence differs. Government deductors typically quote a Book Identification Number arising from the accounts officer's upstream statement instead of a challan identification number. The practical implication is dependency, so build a monthly follow-up rhythm with your accounts office.

What is the fastest way to prevent salary TDS reconciliation problems?

Reconcile monthly rather than quarterly, across three sources: the payroll register, the challan record and the return data. Confirm that computed equals withheld equals deposited equals allocated every month, with a written explanation for any variance. Quarterly Form 24Q filing then becomes a short confirmation rather than an investigation.

Conclusion: Make the Quarter Boring

The best Form 24Q filing is the one nobody remembers. No last-minute challan hunts, no unmatched entries, no employees emailing in July about credit that never arrived, no justification report to decode in December.

Getting there is not about knowing more tax law than everyone else. It is about a small number of habits repeated reliably: clean PAN data, honest monthly reconciliation, challans verified before the return is prepared, an annual annexure that agrees with the quarters that preceded it, and a one-week buffer before every deadline.

And keep the standing caveat in view. Due dates move, fee and interest provisions get revised, regime rules change, and utility versions update. Verify the current position on the income tax department's portals and with your tax advisor at the start of every quarter rather than trusting last year's configuration or any single article, including this one.

If you would rather your team spent that time on people than on transcription, CozyHR handles the computation, the declaration and proof workflow, the challan tracking, the return-ready exports and the Form 16 distribution, and leaves you the judgement calls that actually need a human. Take a look at what a boring quarter feels like.