Paying TDS by cheque — the challan 281 walkthrough for Indian businesses (2026)

Every month, in accounts departments all over India, the same quiet arithmetic happens: totalling up tax that was never the company's to keep. ₹3,600 held back from a contractor's bill under 194C. Ten percent off the CA's fee under 194J. A slice of the office rent under 194I. A piece of every salary under 192.

That money is a deposit in transit. It belongs to the deductee and to the government, in that order, and it sits in your current account only until the deposit deadline early in the following month. Miss the deadline and interest starts — computed by software, per month or part of a month, with zero interest in the story behind the delay.

Which makes the paper version of this deposit a high-stakes little ritual. This is the walkthrough for it: challan ITNS 281, the bank counter, the cheque — who is still allowed to pay this way, which fields on the form actually break, and the one clock rule that decides whether your deposit was on time.

Challan 281 is not challan 280 — one digit, different universe

The income-tax counter runs on a small family of challan forms, and two of them get confused constantly. Challan ITNS 280 is for tax on your own income — advance tax, self-assessment, a demand. We've walked that form separately in the income-tax-by-cheque guide. Challan ITNS 281 is for tax you deducted from someone else — TDS (and its collection cousin, TCS). Same counter, same stamped counterfoil, entirely different legal posture: on a 280 you're a taxpayer; on a 281 you're a deductor, a middleman moving someone else's tax.

That difference shows up in the very first field. A 280 wants your PAN. A 281 wants your TAN — the ten-character Tax Deduction and Collection Account Number the business holds as a deductor. Not your PAN. Not the deductee's PAN either (that comes later, in the quarterly return, not on this challan).

Ask anyone who processes challan corrections what the most common 281 error is, and this is it. PAN in the TAN field. One wrong identifier and the deposit sails into the system attached to nothing your TDS return can find.

Who can still walk to the counter

Honest answer: fewer deductors every year, but not zero.

Electronic payment of TDS has been mandatory for larger deductors for a long time — companies, and businesses subject to tax audit, are the categories typically required to pay only through the electronic route. For them the counter is closed; the challan is generated and paid online, end of story. (The exact boundary of the mandate is the kind of thing to confirm on the portal, not in a blog post — see the fact-check note below.)

The counter survives for the rest: proprietors and small firms outside the audit net who still hold a TAN because they pay rent above the threshold, or run contractors, or cut a salary or two. For them, the e-filing portal's e-Pay Tax service offers a "Pay at Bank Counter" mode — generate the challan online against your TAN, print it, and carry it with a cheque to an authorised bank branch. It's the same shrinking-but-real population that keeps over-the-counter GST payment alive: businesses that run on cheques anyway and want the payment inside the same paper trail as everything else.

Two checks before you plan the branch trip. Your bank must be on the portal's authorised list and actually accept cheques at the counter for this — the list moves. And the printed challan carries a validity window; deposit inside it or the reference lapses and you start again.

The field map — what you write, and where it goes wrong

Challan 281 is one page. Every field on it has a well-worn failure mode.

Read that deductee-category row twice. A proprietorship that paid a private limited contractor ticks company deductees — the tick describes the person whose tax this is, not the person depositing it. It feels backwards. It isn't; you're the courier here, not the customer.

The clock — realised, not received

Now the rule this whole article exists for.

When you pay over the counter by cheque, the bank does not credit the government the moment the leaf crosses the counter. The challan is credited when the cheque is realised — when it clears and the money actually moves. The deposit date the system records rides on that realisation.

A TDS cheque handed over on the due date and realised the day after was, in the department's calendar, deposited late. The counter clerk's stamp proves you visited a branch. Only the clearing proves you paid.

So the operating discipline is a buffer. Clearing in India typically takes a working day or two once presented, more across a weekend or holiday — so a TDS cheque goes in three to four working days before the deadline, minimum. Same-bank cheques (drawn on the very bank receiving the challan) tend to realise faster, but "tend to" is not a compliance strategy. And remember what late means here: interest on a delayed deposit runs from when the tax was deducted, not from the due date — a one-day slip can price like a multi-week one. Annoying? Very. The rule is the rule.

Writing the cheque itself

The cheque attached to a challan 281 has to survive two inspections — the teller's, and clearing's. Four habits get it through:

The payee line follows the bank's printed instruction. Banks generally want the cheque drawn in their own favour for credit to the government account, and the challan or the counter will say exactly how. Copy the instruction. Don't improvise from folklore or from how the last bank wanted it.

The amount in words matches the figures to the rupee. A words/figures mismatch is a routine return reason, and a returned tax cheque is a deadline lost to penmanship. The cheque-filling guide covers the full discipline; for a tax cheque, treat it as scripture.

No corrections. CTS-era practice refuses cheques with overwriting in material fields, however neatly countersigned. Fumbled a word? Cancel the leaf, write a fresh one. Thirty seconds now versus a lapsed challan later.

The right hand signs it. A company or firm cheque pays only against the signature the bank holds on its mandate — the authorised-signatory rules apply with full force here, and a signatory who's travelling on deposit day is a problem you want discovered a week early. Drawn on cleared funds, always: a bounced TDS cheque means no deposit happened, interest still running, plus a return charge for the insult.

The counter run, start to finish

The actual visit is short if the paperwork is right. Log in to e-Pay Tax against your TAN, choose the pay-at-counter mode, and print the challan the portal issues — it carries a reference number and its validity window. Staple your cheque to it. Go to an authorised branch of the bank you selected — not any branch of any bank — inside the validity window and with your clearing buffer intact.

The teller takes the set, stamps the counterfoil or acknowledgment, and hands it back. That stamp is your proof of tender — hold onto it like it's currency, because until the cheque clears, it's the only evidence the deposit exists. (The mechanics at the counter are the same as depositing any cheque at a branch; the difference is what's riding on the date.)

Then the cheque clears, and the real receipt is born.

After the deposit — the CIN, and the reconcile that actually matters

Once the cheque is realised, the deposit acquires a CIN — the Challan Identification Number, three facts fused together: the BSR code of the receiving branch, the date of deposit, and the challan serial number. The CIN is the government's receipt. It is also, and this is the part that bites, the number your quarterly TDS return must quote for the deductees' credit to flow.

So the post-deposit routine is not optional. Within a few days of the expected clearing, verify the challan appears against your TAN on the portal, and check the CIN's amount and date against your TDS register. Do this before the quarterly return is filed, never during the filing scramble. A challan that cleared your bank but hasn't surfaced online is a follow-up you start immediately — counterfoil and bank statement in hand, first at the receiving branch, then through the department's channels.

Because here's what an unreconciled challan actually costs: the return quotes a CIN the system can't match, the deductees' tax credit doesn't reach their accounts, and a month later your contractor is on the phone asking why the tax you cut from his bill isn't showing against his PAN. You become the villain of someone else's tax filing. Avoidable, every time, with one ten-minute check.

The four errors that cause the most pain

Every challan-281 horror story is one of four:

Wrong TAN. The deposit exists but is attached to the wrong (or no) deductor. The heaviest fix — this is identity, not detail, and the correction runs through the department.

Wrong assessment year. The money sits one year off from where the return is looking. Common in April–May deposits, when the year has just rolled.

Wrong section code. Rent deposited as contractor payment. The totals still add up, the mapping doesn't.

Wrong deductee category. Company money in the non-company bucket or the reverse.

There is a correction mechanism — banks can fix certain fields within a short window after deposit, and beyond that the request goes through the department's correction channels. It works. It is also measured in weeks of follow-up, while the quarterly return's own deadline keeps approaching. The cheapest challan correction is the one you never need, which is why the field map above deserves sixty seconds of checking before the cheque leaves the office. (Correction procedure specifics change; treat this as general information, not tax advice — your CA has the current version.)

Why this still happens on paper

Strip away the compliance and one reason the TDS cheque survives is boring and good: the trail. A cheque number in the payment register, a stamped counterfoil, a clearing entry on the bank statement, a CIN — four documents agreeing with each other, which is exactly what you want in the file when a TDS question surfaces three years later. Businesses that run their vendor payments on cheques simply extend the same spine to the tax on those payments.

The weak link in that spine was never the concept. It's the handwriting — the mismatched words line, the corrected digit, the cheque nobody logged. Fix the handwriting and the paper route is, for the small deductor still allowed to use it, a perfectly respectable way to pay other people's tax.

The tax you deducted from someone else's money deserves a cleaner trail than your own. Cheqify prints the TDS cheque — and every vendor cheque the deduction came from — on 300+ Indian bank layouts with the amount in words auto-generated and each leaf tracked from issue to clearance, so the challan, the counterfoil and the register all tell one story. 100% free. Start at app.cheqify.app.