It is usually October when the call comes. The audits are barely behind you, you have not slept properly in three weeks, and a client rings to say a notice has turned up under section 143(2). You open the file half-bracing for a fight, and what you actually find is almost embarrassing. The depreciation in the tax audit report sits about four lakh higher than the figure that finally went into the return. An asset got capitalised late, the audit picked it up, the return didn’t. No fraud, no clever planning. Just two numbers that were meant to be identical and weren’t.
That is the whole subject of this article, really. Not evasion, not aggressive positions, just the quiet gaps between two documents that should be telling the same story.
Because here is what has changed, and what a lot of people still haven’t fully absorbed. The 3CD and the ITR are no longer read by a tired officer flipping between two paper files. They are read by software, together, and not just against each other. They are read against the 26AS, the AIS, the TIS, the GST returns and the SFT data, all in one pass. The department does not have to suspect your client of anything. It only has to notice that two forms carrying the same PAN disagree. That’s it. That’s the trigger.
So most of my September is spent doing something deeply unglamorous: sitting with the 3CD open in one window and the ITR schedules in the other, and tying them together before anyone signs anything.
Treat them as two witnesses
I find it useful to think of the audit report and the return as two witnesses describing the same year. If their statements line up, nobody asks a second question. If they diverge, the assessing officer’s job is to find out why, and yours becomes the far less pleasant job of explaining a difference that had no business existing in the first place.
The reason these gaps happen is honestly more about workflow than skill. We do the audit on one day, key the return on another, often a different person handles each, and somewhere in that handoff a figure drifts. The fix is not some grand technique. It is the patience to reconcile before you sign rather than after the notice.
These are the points I check on every assignment, because in my experience these are the ones that actually generate trouble. I’ve dropped the clauses the recent amendments have made irrelevant and kept what is still live.
| 3CD Clause | What it captures | Where it has to agree in the ITR |
| 18 | Depreciation under the Act | Schedule BP, DPM, DOA. Opening WDV must tie to last year’s closing |
| 20(b) | Employee PF/ESI, 36(1)(va) | Part A-OI. The due-date test shows no mercy |
| 21 | Disallowances, 37 / 40(b) / 40A(3) / 14A | Part A-OI. Disclosed here, added back there |
| 22 | Interest disallowed on late MSME payments, 43B(h) | Part A-OI. New, and watched closely |
| 23 | Payments to related parties, 40A(2)(b) | Part A-BS / Schedule AL. Check against the related-party note |
| 26 | 43B items, paid and unpaid | Part A-OI, split by year of payment |
| 34 | TDS deducted, deposited, returns filed | Tie to 26AS and the TDS returns, not only the books |
| 40 | The key ratios | Trading / P&L. Turnover here must equal turnover there |
There is nothing exotic on that list. It is simply the difference between a file that closes quietly and one that asks for trouble.
If your checklist is more than a year old, it’s wrong
A quick but important detour. Form 3CD itself was rewritten. The Eighth Amendment Rules of 2025 reshaped it with effect from 1 April 2025, for audits of AY 2025-26 onward, and if you are still running an old working template you will report things that no longer exist.
The rows for 32AC, 32AD, 35AC and 35CCB are gone from clause 19, because those deductions are gone. Clause 22 has become a proper MSME disclosure: the amount payable to micro and small enterprises under section 15 of the MSMED Act, the interest that becomes inadmissible under 43B(h) when you pay them late, and a clean split between the timely payments and the delayed ones. I’ll say plainly what I expect here. This is the clause that is going to throw up the most adjustments over the next couple of cycles, because plenty of businesses pay their small vendors whenever it suits them and have never once had it surface in a tax document. Get the client’s MSME creditor ageing sorted out early. Do not leave it for the last week.
There’s also a new clause 36B for share buyback under 2(22)(f), and 44BBC has been slotted into clause 12 for the cruise-ship presumptive cases. Niche for most of us, but worth knowing they’re there.
One more thing, since it trips people up. The section numbers in this piece follow the 1961 Act, which is the framework these audits and returns sit under. The scrutiny-selection machinery for the current cycle, though, is now being run under the new Income-tax Act, 2025. Two regimes talking to each other for a season. Hold that distinction in your head and you won’t fumble it in a reply to the department.
Know how a case actually gets picked
It helps to understand the other side’s method, because there are two separate tracks and they behave very differently.
The first is compulsory manual selection, set out in the CBDT’s annual guidelines. For the present cycle the Board, through guidelines issued in June 2026 under section 536(2)(c) of the 2025 Act, has named six categories of returns filed during FY 2025-26 that go into complete scrutiny no matter what. Survey cases under 133A, search and seizure matters, exemption-claiming trusts whose registration was cancelled, cases carrying a recurring addition on the same issue from earlier years, and matters flagged by enforcement or intelligence agencies. If your client sits in one of these, the case is coming whatever the return looks like, and your job is simply to be ready for it rather than surprised by it.
The second track is the one most ordinary assessees should actually worry about, and it is CASS, the Computer Assisted Scrutiny Selection. This is the silent one. It doesn’t read your narrative or your good intentions. It reads your numbers against everybody else’s numbers and it lights up the moment two of them don’t agree.
What lights it up
From what I keep seeing, these are the things to internalise. Notice that not one of them needs any wrongdoing. Each is just a discrepancy a computer can spot on its own.
A refund that looks oversized for the profile of the assessee. A return showing fat loans, advances or investments perched on top of thin declared income, where the obvious question, where did the money come from, asks itself.
Then the mismatches, which are the broadest family by far. Income in the books or the ITR that doesn’t agree with the 26AS. Income that doesn’t agree with the GSTR. Income or transactions that don’t agree with the AIS or the TIS. Turnover in clause 40 of the audit report that doesn’t match the turnover in the return. Book profits in Form 29B that differ from the ITR. Every one of these is a plain sentence the system can read and a question it can raise.
Sharp year-on-year swings in turnover or margin with nothing on record to explain them, because the machine is built to flag discontinuity. The big SFT entries too, the heavy cash deposits or withdrawals the bank reports. I have been through more bank statements than I care to count where a completely legitimate business simply ran on cash, never imagining the totals would land in an SFT feed and put a flag on an honest return.
And the valuation gaps. Property bought or sold below the stamp-duty value, which pulls in 50C and 56(2)(x). Shares moved below fair value, same idea. Plus the simplest one of all, the one that still catches people out: sales or purchases sitting visibly in the GSTR, the 26AS or the AIS where no return has been filed at all. The data is there, the return isn’t, and the notice writes itself.
What I actually do before signing
So, the routine. It’s roughly four things, though honestly the order shifts depending on the client.
Turnover gets tied three ways: the books, clause 40, and the GST returns for the same period. They have to reconcile to the rupee, and where they genuinely can’t, I want the reason sitting in the working papers before I sign, not invented afterwards when someone asks.
I run the 26AS and the AIS against the books, for the client and not merely for the return, so that anything the department already knows about is part of our story too. A receipt the client honestly forgot is far, far better found by me in September than by an officer the following March.
The disallowance chain gets walked end to end. Clause 21, the PF and ESI dates under 20(b), the 43B position in clause 26, and now the MSME interest in clause 22, all flowing properly into the add-backs. A disclosure in the audit report that quietly vanishes in the return is a contradiction waiting to be picked up.
And then I just look at the deltas like an outsider would. Any odd jump in turnover, any collapse in margin, any large refund, any heavy borrowing against modest income. If a number would make me pause, I make sure the file already holds the answer.
That’s most of the craft of it. For an honest assessee, scrutiny is hardly ever about something done wrong. It is about something left unreconciled. Tie the two documents together before you sign, and a good number of these notices simply never get written.
******
Disclaimer: This article is for general professional reference and is not a substitute for legal or tax advice. Clause references reflect Form 3CD as amended with effect from 1 April 2025, and the scrutiny parameters reflect the CBDT compulsory-selection guidelines for the current cycle; both may change. Please verify the current provisions and judge each case on its own facts.

