Every quarter, the same pattern repeats in CA firms across India. Challans are paid on time, the deductee list looks complete, and then the statement bounces at validation or comes back from TRACES with a short-deduction default a few weeks later. Most of these problems are not about tax law at all. They come from gaps in the process. AskSolique, which helps Indian CA practices with tds return filing research and wider income tax work, sees the same handful of avoidable errors again and again.

This checklist walks through what a firm should verify before, during and after a quarterly TDS statement goes out, so that the return is filed once and stays filed.

1. Know Which Statement and Which Deadline Applies

The first step sounds basic, yet it is where junior staff most often slip. Each deductor files a separate quarterly statement for each type of payment:

• Form 24Q for TDS on salary
• Form 26Q for TDS on non-salary payments to residents (contractors, professional fees, rent, interest and so on)
• Form 27Q for payments to non-residents
• Form 27EQ for tax collected at source

Under the long-standing schedule, the statements for the April–June, July–September and October–December quarters fall due by the last day of the month after the quarter ends (31 July, 31 October and 31 January), and the January–March statement by 31 May. With the Income Tax Act 2025 now in force from April 2026, several section and form references are being remapped, so always confirm the current reference and due date against the latest CBDT notification before you quote it to a client.

A simple master calendar, one row per client and one column per form and quarter, removes most of the “we forgot the 27Q” surprises.

2. Reconcile Challans Before You Prepare the Statement

Most rejected or defaulted statements trace back to challan mismatches. Before anyone opens the return preparation utility, reconcile three things for the quarter:

1. Books of account — every payment that attracted TDS, with the section, rate and amount deducted.
2. Challans paid — the BSR code, challan serial number, date of deposit and amount, matched against the OLTAS status on the portal.
3. Deductee details — PAN, name and the section code for each deductee.

If the total deducted in the books does not equal the total of challans tagged to the statement, stop and fix it first. A short payment or a challan mapped to the wrong quarter will create a demand on the deductor's TRACES account later, and fixing it then takes far longer than fixing it now.

Invalid or missing PANs deserve special attention. A deductee without a valid PAN attracts a higher rate of deduction, and a typo in a valid PAN means the deductee never sees the credit in their Form 26AS. Run a PAN verification on the deductee master every quarter rather than once a year.

3. Prepare, Validate and File Without Shortcuts

Once the data is clean, preparation is mostly mechanical:

• Prepare the statement in the current version of the Return Preparation Utility (RPU). Older versions are a common cause of validation failure.
• Validate the file using the latest File Validation Utility (FVU). Read the error file line by line instead of guessing.
• Upload the validated file through the income tax e-filing portal, or through a TIN facilitation centre if the client prefers.
• Download and store the provisional receipt with the token number. You will need it for any later correction.

Late filing is expensive. A fee is charged for every day of delay until the statement is filed, capped at the amount of TDS, and a separate penalty can apply where a statement is filed very late or with incorrect information. Clients rarely remember that the fee applies even when the tax itself was deposited on time, so it is worth saying so in your quarterly reminder.

4. Handle Corrections Through TRACES the Right Way

No firm files every statement perfectly. When a correction is needed (a wrong PAN, a challan tagged to the wrong deductee, a missed entry), the safe sequence is:

1. Log in to TRACES and request the consolidated file for the original statement, using the token number and challan details.
2. Import the consolidated file into the RPU and make only the required changes.
3. Validate the correction statement with the FVU and upload it.
4. Recheck the TRACES statement status and the justification report once processing is complete.

The most frequent mistake here is preparing a correction from the firm's own working file instead of the consolidated file. The department's records are the base; the correction has to start from them. If a demand has already been raised, it often makes sense to read the intimation the same way you would read any other notice. The approach in our earlier note on the income tax demand notice under section 143(1) applies here too: identify the exact mismatch before you draft anything.

5. Fit TDS Into the Wider Compliance Calendar

TDS does not sit on its own. The same accounts team is usually handling advance tax, GST returns and the year-end annual filings at the same time. October is a good example: the quarter-two TDS statements fall due in the same weeks that firms are planning ahead for the annual GST return. Keeping the GSTR-9 due date on the same master calendar as the quarterly TDS deadlines lets a manager see the crunch weeks early and assign people before the deadline, not after it.

A shared calendar also makes reconciliations easier. Vendor payments that attract TDS under 26Q usually also appear in GST input credit records, so mismatches spotted in one place often point to errors in the other.

6. Use Technology Where It Actually Saves Time

Software will not make judgement calls for you, but it can take the slow, repetitive parts off your team's desk: checking the correct section and rate for an unusual payment, pulling the latest circular, or comparing the old and new section references under the 2025 Act. Firms that adopt AI built for chartered accountants typically use it for research and first drafts, and keep review, sign-off and client communication with the partner.

If you are weighing whether such a tool fits your practice, our earlier piece on what CA firms should compare before choosing an AI tax research tool sets out the questions to ask. And when a TDS default turns into a full scrutiny case, the steps in preparing a defensible response to an income tax scrutiny notice are a good next read.

Quick Quarter-End Checklist

• Confirm which statements (24Q, 26Q, 27Q, 27EQ) each client must file this quarter
• Reconcile books, challans and OLTAS status before preparation
• Verify every deductee PAN
• Use the latest RPU and FVU versions
• File before the due date and store the provisional receipt
• Correct only from the TRACES consolidated file
• Review the justification report after processing

A firm that runs this list every quarter will see fewer defaults, fewer late fees and far fewer anxious client calls.

This note is published by AskSolique, the AI tax research platform for CA firms in India. For a walkthrough of how it supports TDS, income tax and GST work in your practice, please contact us.

Getting a GST notice in your registered email or on the portal is rarely a pleasant surprise, but it doesn't have to be a crisis either. Most notices — whether they relate to a mismatch between GSTR-1 and GSTR-3B, a delayed filing, or a scrutiny query — follow a predictable structure, and so should your response. Understanding the right gst notice reply format before you sit down to draft one saves time, avoids unnecessary back-and-forth with the department, and reduces the risk of the reply being rejected on a technicality rather than on the merits of your case.

Why the Format Matters as Much as the Content

Tax officers process a high volume of replies, and a submission that is hard to follow, missing required references, or structured inconsistently is more likely to draw a follow-up query — even when the underlying facts are perfectly defensible. A well-formatted reply signals that the taxpayer has understood the notice correctly and is responding to the actual point raised, not a generic template pasted in without review.

This matters more under GST than it did under the earlier indirect tax regime, simply because so much of the process — from notice issuance to reply submission — now happens through the GST portal itself, where structure and reference numbers are checked systematically before a human even reads the content.

The Core Structure Every Reply Should Follow

Regardless of which section or notice type you're responding to, a competent GST reply generally follows the same skeleton:

1. Reference details — notice number, date of issue, GSTIN, and the specific section or rule under which it was issued
2. Brief recap of the notice — a short, neutral restatement of what the department has alleged or queried, showing you've read it correctly
3. Point-by-point response — addressing each allegation or query separately rather than as one combined paragraph, with supporting figures or reconciliations attached as annexures
4. Legal or factual basis — the specific provision, circular, or documentary evidence that supports your position
5. Prayer/conclusion — a clear closing statement on what you are asking the department to do (drop the proceedings, accept the reconciliation, etc.)

Skipping the point-by-point breakdown is one of the most common mistakes businesses make. A single dense paragraph trying to cover multiple allegations at once is harder to evaluate and easier to misread, both of which work against you.

Common Notice Types and What They Need

A demand notice under mismatch of ITC claimed versus GSTR-2B needs a reconciliation statement as the centerpiece of the reply — dates, invoice numbers, and the specific discrepancy explained line by line. A late-filing notice usually needs less narrative and more documentary proof of the actual filing date along with any reasonable cause for delay. A scrutiny notice under Section 61, by contrast, often requires the widest response, since it can touch multiple aspects of a return in a single notice.

Businesses that keep a standard internal checklist and a structured template library for each notice type tend to respond faster and more consistently than those drafting each reply from scratch, particularly when the same category of notice recurs across GST periods or between related entities.

Where Delays and Errors Usually Creep In

Two things account for most avoidable problems in GST reply drafting. First, teams underestimate how much time reconciliation work takes relative to writing the reply itself — by the time the numbers are sorted out, the response window is uncomfortably tight. Second, replies get drafted by whoever is available rather than whoever has handled that specific notice type before, which shows up as generic language that doesn't map cleanly onto the department's actual query.

Having access to a maintained, well-structured template library for the common GST and income tax notice categories helps address both problems — it shortens the drafting time and keeps the response format consistent with what has worked in similar cases before, rather than starting from a blank page under deadline pressure.

A Few Practical Checks Before Submission

Before filing a GST notice reply, it's worth running through a short internal checklist: confirm the reply is filed against the correct reference number and within the stipulated timeframe, verify every factual claim is backed by an attached document rather than asserted alone, make sure figures in the reply tie back exactly to the figures in GSTR filings for the relevant period, and have a second person — ideally someone not involved in drafting — read the reply purely for clarity before it goes out.

None of these checks are complicated individually, but skipping them under time pressure is exactly how avoidable follow-up notices happen. A reply that is accurate but poorly organized can generate almost as much friction as one that is factually weak.

Getting the Process Right, Not Just the Reply

The businesses that handle GST notices with the least friction aren't necessarily the ones with zero discrepancies — discrepancies happen even in well-run compliance functions. They're the ones with a repeatable process: a consistent format, a clear internal owner for each notice category, and templates that don't have to be rebuilt every time a similar notice arrives.

If your team is looking to tighten up how GST and income tax notice responses get drafted and reviewed, AskSolique can walk you through what a more structured approach looks like in practice.