TDS Return Filing Checklist: Build It or Buy It?

Filing a TDS return is not one task. It is a chain: collect a valid PAN, pick the right section, deduct at the right rate, deposit by the 7th, tag the challan in TRACES, reconcile against 26AS, then generate and upload the validation file before the quarterly deadline. Break one link and the return is either rejected, or accepted with a fee attached. This checklist is for the finance or ops lead who owns that chain end to end.

What a TDS return filing checklist actually covers

A TDS return filing checklist is the ordered set of steps between a payment and a filed statement — deduction, deposit, challan tagging, reconciliation and validation — not just the quarterly form. Three records have to agree: what you deducted, what you paid to the government, and what you reported. Most rejections we see are not missed deadlines; they are challan mismatches, where the amount tagged to deductee rows does not match the challan. The form changes with the payment type — 24Q for salary, 26Q for resident non-salary, 27Q for non-residents, 27EQ for TCS — but the checklist underneath is the same.

The monthly checklist: five things before the 7th

The monthly part of a TDS return filing checklist is five recurring checks, and most of them are due before the 7th of the following month. Do them monthly; repairing them at quarter end costs more.

• Confirm PAN before the bill is booked. A missing or invalid PAN pushes the rate to 20% under section 206AA, and you cannot recover that from the vendor later.
• Pick the section deliberately. 194C for contracts, 194J for professional fees, 194I for rent, 194H for commission, 194Q for goods above ₹50 lakh in a year.
• Deduct on the earlier of the ledger credit or the payment date. The liability starts there, not when you pay the vendor.
• Deposit by the 7th of the following month; March deductions are due by 30 April.
• Tag the challan to deductee rows in TRACES that same month, not in the last week of the quarter.

If invoices and ledger entries already carry section and rate as fields, steps one and two stop being manual lookups — that is usually where the bill needs GST and TDS tagging built into the billing flow rather than bolted on as a spreadsheet column.

Quarterly filing: deadlines, forms and the FVU step

The quarterly return needs four things: a validated deduction file, correct challan-to-deductee mapping, the right form, and an FVU file generated and uploaded before the due date. For the current financial year the deadlines are 31 July, 31 October, 31 January and 31 May. Validate the file through the FVU utility and keep the receipt — it is your proof of filing. Form 16 for salary is due by 15 June; Form 16A for non-salary is downloadable within 15 days of filing. Nil returns are still returns: file them, because one missing quarter blocks the whole year. A correction statement costs the same fee as an original, so reconcile before you file, not after.

Build versus buy: where the honest line sits

Build if your deduction logic is genuinely unusual or you have a high, stable number of deductees; buy if the pain is data collection, PAN validation and challan mapping. A spreadsheet plus TRACES genuinely works below roughly 150 deductees a quarter, in our experience. A custom tool that reads your ERP ledger, validates PANs, applies section-wise rates and outputs a return-ready file typically takes 4-8 weeks to build, and it needs an owner every time the Budget moves a rate or threshold. Bought software costs a fraction of that, but its ceiling is real: group structures and unusual sections tend to end up back in a spreadsheet anyway. The honest test is where the hours go. Chasing vendors for PANs? Buy. Mapping your own ERP's quirks? Build. Price both sides the same way — build cost plus maintenance against a subscription — and treat something like our published pricing as one benchmark for the buy side.

A worked example: 40 contractor invoices and one bad PAN

A quarter's worth of small process gaps can cost more than the software that prevents them, and the arithmetic is easy to run. Say a Gurgaon services company pays 40 contractors ₹50,000 each in July — ₹20,00,000 of contract payments under section 194C. If those contractors are companies or firms, TDS at 2% is ₹40,000; if they are individuals or HUFs, 1% is ₹20,000. Now suppose one is a company with an invalid PAN. That single invoice attracts 20% under section 206AA — ₹10,000 instead of ₹1,000 — and the contractor will argue about it. Suppose the ₹40,000 was deducted on 25 July but deposited on 20 August: interest at 1.5% per month or part of it, roughly ₹600. File the Q2 return 20 days late and section 234E adds ₹200 per day, ₹4,000, capped at the TDS amount. None of that is a filing error; all of it is an upstream process error.

Where to start

Run one quarter end to end on a whiteboard before deciding anything: list every step, mark who does it, and time it. Whichever side of the line your hours fall on decides build versus buy. Most teams we meet at Maysan Labs find the fix is less about return software and more about the invoice and ledger data feeding it — automate that first and the filing gets simpler on its own.