Why Is Form 3CD Showing a Tax Audit Comment on MSME Payments?

The Chartered Accountant sends the draft Form 3CD one week before the tax audit upload deadline. You scroll to Clause 22 and see it — “Amount inadmissible under Section 43B(h) of the Income-tax Act 1961 on account of dues payable to Micro and Small enterprises beyond the appointed day under Section 15 of the MSMED Act 2006: Rs 22,00,000”. Nobody flagged this exposure through the year. The tax audit report has to upload in seven days.

You have never seen a Clause 22 comment of this size before. The immediate question is not “what do we do next” — the CA has already told you the disallowance auto-adds to your return. The confusion is why the comment is on the report at all when the AP team was releasing payments on the usual cycle, and where else the comment flows to once the tax audit report goes on the e-filing portal.

Quick answer

Clause 22 of Form 3CD is the tax auditor’s mandatory disclosure — under Rule 6G of the Income-tax Rules 1962 — of amounts inadmissible under the MSMED Act 2006 and, since the CBDT amendment of 5 March 2024, also amounts inadmissible under Section 43B(h) of the Income-tax Act 1961. A Clause 22 comment means your MSME payables ageing at 31 March showed unpaid dues to Micro or Small enterprise vendors past the Section 15 appointed day (15 days without a written agreement, 45 days with one), and the auditor is legally required to disclose the aggregate figure in the audit report. It is a factual disclosure, not an opinion, and there is no auditor discretion to omit it once the underlying condition exists.

The Rs 22,00,000 figure will flow to three downstream places in the next 60 days — the income-tax return under Section 43B(h) as an auto add-back to profit (roughly Rs 5,53,740 in additional tax at the Section 115BAA concessional rate of 25.17 per cent), the statutory audit report as a potential qualification on the corresponding balance-sheet liability, and — for a company assessee — the internal financial controls opinion under Section 143(3)(i) of the Companies Act 2013.

What Clause 22 actually asks

Section 44AB of the Income-tax Act 1961 requires businesses above the tax audit threshold (Rs 1 crore turnover, or Rs 10 crore where cash flow is under 5 per cent, or Rs 75 lakh for professionals) to have accounts audited by a Chartered Accountant. Rule 6G of the Income-tax Rules 1962 prescribes the audit report in Form 3CA (for company assessees whose accounts are audited under the Companies Act) or Form 3CB (for other assessees), and the 44-clause statement of particulars in Form 3CD.

Clause 22 in the current Form 3CD utility asks the auditor to disclose two related amounts:

• Interest inadmissible under Section 23 of the MSMED Act 2006 — the compound interest at three times the RBI-notified bank rate that a buyer is liable to pay to an MSME vendor for a delayed payment under Section 16 of the MSMED Act, and which is non-deductible under Section 37 of the Income-tax Act by virtue of Section 23.
• Principal amount inadmissible under Section 43B(h) of the Income-tax Act — the unpaid Micro and Small enterprise dues sitting on the balance sheet at 31 March past the Section 15 appointed day, added to the Clause 22 disclosure by the CBDT Notification G.S.R. 155(E) dated 5 March 2024.

The auditor tests both figures against the MSME payables ageing register and the vendor-master Udyam classification tags. Where the reconciliation shows a positive figure, the disclosure is mandatory — the auditor has no discretion to omit or to negotiate.

Why the comment surfaced when nobody flagged it earlier

Five common patterns explain why a Clause 22 disclosure lands as a surprise on the draft tax audit report.

1. The vendor master had no MSME classification field

The most frequent cause. The AP ledger records every invoice and every payment but does not carry the vendor’s Udyam Registration Number, classification tier, principal activity code, or URN issue date. The AP team therefore has no runtime signal that a specific invoice belongs to a Micro or Small enterprise vendor subject to the Section 15 appointed day, and the payment cycle runs on the usual 60 or 90-day norm. The comment surfaces at audit fieldwork when the CA asks for the MSME payables list and the vendor-master gap becomes visible. See the companion TOFU article on how to verify a vendor’s MSME status for the four-filter verification pattern that the vendor master should carry.

2. The AP ageing report was not filtered on MSME status

Even where the vendor master carries the classification, the AP ageing bucket report typically shows past-30, past-60, past-90 columns based on the default 60-day payment norm. A Micro or Small enterprise invoice at 46 days past acceptance is already past the Section 15 appointed day, but sits inside the past-60 bucket that no one escalates. The exposure exists but is not surfaced by the report the AP team runs weekly.

3. A payment was released to the vendor’s parent PAN but not to the correct URN

A group vendor operates from three state units, each with its own GSTIN but one PAN, and a single URN issued at the head office. The payment lands at the PAN level but the AP ledger allocates it against a different GSTIN’s outstanding. The Section 43B(h) test — is this specific invoice paid within the appointed day — runs against the invoice-level payment allocation, not the aggregate vendor balance. Payments that clear at the parent level but do not allocate cleanly to specific invoices generate a residual past-appointed-day exposure at year-end.

4. A vendor registered on Udyam mid-year and the master was not updated

An ancillary supplier that was outside the MSME regime through the first three quarters registers on Udyam in December. The AP master still shows the vendor as Non-MSME. Invoices from January to March, sitting unpaid past the 15 or 45-day deadline, are in scope for Section 43B(h) but do not appear on the MSME exposure list. The auditor catches the classification drift during substantive testing and adds the vendor to the disclosure.

5. The March 31 payment run cleared bank on 1 April

A cheque cut on 30 March or a NEFT batch initiated on 31 March that credits the vendor on 1 April does not stop the appointed-day clock at year-end. The Section 43B(h) test looks at whether the payment has been actually released — the credit date at the vendor’s bank, not the debit initiation date at the buyer’s bank. A working-day-boundary case adds to the Clause 22 disclosure even when the AP team believes the exposure was cleared before year-end.

The three downstream places the comment flows to

This is where a Clause 22 comment stops being an isolated tax-audit line and becomes a multi-report event.

Downstream 1 — Income-tax return auto add-back under Section 43B(h)

The Rs 22,00,000 Clause 22 figure flows directly into the computation of income for the year as an add-back to profit. At the Section 115BAA concessional rate of 25.17 per cent (the rate most mid-market SMEs file under after cess and surcharge), the additional tax is approximately Rs 5,53,740 for the year — roughly Rs 5.5 lakh in current-year cash outflow. The disallowance reverses in the year of actual payment to the vendor, so if the outstanding is cleared in April, the deduction lands in the next financial year’s return. That is a full-year deferral of a Rs 5.5 lakh outflow rather than a permanent loss — but the current-year cash impact is real.

The Section 43B(h) MSME disallowance estimator tool is the fastest way to model this — plug in the AP ageing buckets and the applicable rate, and it produces the disclosure figure and the tax charge in seconds. The full Section 43B(h) TOFU walkthrough covers the underlying rule and the interaction with Section 16 MSMED Act interest.

Downstream 2 — Statutory audit qualification on the balance-sheet liability

For a company assessee, the statutory auditor sees the Clause 22 disclosure in the tax audit report and tests the same MSME payables balance for accuracy and completeness. Where the tax audit uncovered a classification gap in the vendor master, the statutory audit typically extends its own substantive testing — sample verification of the URN population, re-performance of the appointed-day calculation for a sample of past-45-day invoices, and confirmation of the disclosure narrative in the notes to accounts. The disclosure of dues to Micro, Small and Medium Enterprises in the notes to accounts (a Schedule III requirement) becomes a formal audit disclosure item, and any material understatement of the balance flows into the audit opinion.

Downstream 3 — Companies Act Section 143(3)(i) ICFR observation

The auditor of a company assessee is also required, under Section 143(3)(i) of the Companies Act 2013, to state whether the company has adequate internal financial controls with reference to financial statements and whether such controls are operating effectively. A Clause 22 comment on Section 43B(h) inadmissibility is direct evidence that the control over MSME payables ageing did not surface the exposure before year-end. For a listed company or one meeting the ICFR audit thresholds under the Companies (Accounts) Rules 2014, this typically translates into a formal ICFR audit observation on control design — and depending on the materiality, a modified opinion. That observation is separately disclosed to the audit committee, the board, and — for listed entities — via SEBI (LODR) disclosure. The tax audit line item becomes a governance line item.

Which downstream to worry about first

For a private limited company mid-market SME with no listing exposure, the largest immediate concern is downstream 1 — the current-year tax outflow. The Rs 5.5 lakh cash charge lands with the next advance tax instalment or the self-assessment payment at return filing, and needs to be in the tax provision immediately.

For a company approaching the ICFR audit threshold — turnover Rs 50 crore or paid-up capital Rs 25 crore — downstream 3 becomes the more serious governance issue. An ICFR audit qualification on a material control weakness is a directors’ report disclosure item under the Companies (Accounts) Rules 2014, and remediation is a formal board-tracked corrective action. See the statutory audit reconciliation checklist for India for the reconciliation-preparation discipline that the ICFR auditor tests against, and the Form 3CD reconciliation items under Section 44AB walkthrough for the full 44-clause auditor procedure. The statutory audit preparation kit bundles the reconciliation templates that support both the Clause 22 disclosure and the ICFR narrative.

Separately, Section 271B of the Income-tax Act 1961 imposes a penalty of 0.5 per cent of turnover (capped at Rs 1,50,000) for failure to get accounts audited or furnish the audit report by the due date. A Clause 22 dispute that delays the Form 3CD upload past the deadline can trigger Section 271B in addition to the underlying disallowance — the penalty is separate from the tax charge and separate from the ICFR consequence.

What to prepare before next year’s audit

Three items, built over roughly a quarter, move the finance team from a March-25 scramble to an audit-ready standing position.

• Quarterly Udyam URN re-verification — every URN-registered vendor in the AP master is refreshed against the Udyam portal’s public verification tool once a quarter. The classification tier and the principal activity code are updated in the vendor master. Vendors who have grown from Small to Medium fall out of scope; vendors who have registered mid-year enter scope. For a 400-vendor AP master with 60 URN-registered MSME suppliers, this takes an analyst about a working day per quarter.
• AP ageing bucket flag — every MSME invoice at booking time is stamped with its Section 15 appointed day (invoice acceptance date plus 15 days for no written agreement, or the agreed period capped at 45 days for a written-agreement vendor). The AP ageing bucket report carries an MSME filter and surfaces past-appointed-day invoices continuously across the year. The AP head sees the exposure daily, the payment prioritisation run releases these first, and the year-end scramble disappears.
• Monthly Section 43B(h) exposure projection — a monthly worksheet computes the running Clause 22 figure and the tax charge at the Section 115BAA rate. The CFO sees the exposure crystallising month by month, and the audit committee sees the trend at every quarterly review. When the tax auditor arrives at fieldwork, the disclosure is a reconciled figure that maps to the aged AP report and the URN verification log — a re-performance check rather than a full-population investigation.

For the sector-specific worked disallowance patterns where a single delayed payment cascades through multiple ancillary tiers, the chemical ancillary vendor 45-day cascade and steel ancillary vendor 45-day cascade reconciliation walk through the compounding disclosure across job-work and material-issue cycles with worked numbers.

When the manual tracking outgrows itself

For a controller managing under 30 URN-registered MSME vendors, a quarterly-refreshed spreadsheet-based classification register and a monthly ageing pull from the ERP is workable — an analyst holds it inside a normal monthly close. For a company running 200-plus URN-registered vendors across multiple state units, multiple GSTINs consolidating to a single URN at parent PAN level, and a payment run cadence that clears MSME invoices in the same weekly cycle as non-MSME invoices, the spreadsheet-based approach starts to leak — missed URN drift as a Small vendor grows into Medium, missed acceptance-date-versus-invoice-date reconciliation where the appointed day should run from goods receipt rather than invoice booking, and missed payment-boundary cases where a March 31 wire posts to the vendor’s bank on 1 April.

At that scale, moving the MSME payables ageing and the Clause 22 disclosure worksheet onto continuously refreshed detection — where Terra Insight’s reconciliation software for India treats the URN classification, the appointed-day calculation, and the running Section 43B(h) exposure as first-class outputs — is what keeps the tax audit fieldwork inside a re-performance-check discipline rather than a fresh-population investigation.

Go deeper

• What is Section 43B(h) MSME 45-day rule and does it apply to me? — the TOFU companion on the underlying disallowance rule
• How do I know if my vendor is MSME registered? — the four-filter URN verification pattern
• Statutory audit reconciliation checklist for India — the reconciliation-preparation discipline that anticipates Clause 22
• Form 3CD reconciliation items under Section 44AB — the full 44-clause auditor procedure walkthrough
• Section 43B(h) chemical ancillary vendor 45-day cascade
• Section 43B(h) steel ancillary vendor 45-day cascade reconciliation
• Section 43B(h) MSME disallowance estimator (tool)
• Statutory audit preparation kit (bundled templates)
• Reconciliation software for India — money page

Frequently Asked Questions

The tax auditor has put in a Clause 22 comment on MSME payments. What does that actually mean?

Clause 22 of Form 3CD is the tax auditor’s mandatory disclosure of amounts inadmissible under the MSMED Act 2006 and — following the CBDT amendment of 5 March 2024 — amounts inadmissible under Section 43B(h) of the Income-tax Act 1961. A Clause 22 comment means the auditor has tested your MSME payables ageing at 31 March, found unpaid amounts owed to Micro or Small enterprise vendors past the Section 15 appointed day (15 days without a written agreement, 45 days with one), and disclosed the aggregate figure in the tax audit report. The comment is not an auditor’s opinion or a matter for negotiation — Rule 6G of the Income-tax Rules requires it as a factual disclosure whenever the underlying condition exists. The consequence flows through three downstream places: the income-tax return computation adds the same figure back to profit under Section 43B(h), the statutory audit report may qualify on the corresponding balance-sheet liability accuracy, and for a company assessee the finding contributes to the Section 143(3)(i) opinion on internal financial controls.

Does the Clause 22 comment automatically become an income-tax addition, or can we argue it away?

It automatically becomes a disallowance in the computation of income. Section 43B(h) is a statutory disallowance — the amount disclosed in Clause 22 gets added back to profit before tax in the return of income, and the tax charge for the year increases by the corresponding rate multiplied by the disclosure. For a Rs 22,00,000 Clause 22 figure at the concessional Section 115BAA rate of 25.17 per cent, the current-year tax outflow rises by approximately Rs 5,53,740 — roughly Rs 5.5 lakh in additional tax. The Clause 22 figure and the ITR add-back figure must reconcile — the tax auditor’s disclosure is one of the specific numbers that the Centralised Processing Centre cross-checks under Section 143(1)(a) at return-processing time, and any mismatch surfaces as a prima-facie adjustment intimation. The disallowance reverses only in the year of actual payment to the vendor, so a Rs 22 lakh disallowance in the current year becomes a Rs 22 lakh additional deduction in the year the payment is released — but the cash-flow impact of the current-year tax remains real.

The auditor put Clause 22 in only because we did not have a vendor-master MSME field — is that our fault?

Yes, unfortunately, in the sense that the assessee is responsible for maintaining the records needed to compute the disclosure correctly. ICAI’s Guidance Note on Tax Audit under Section 44AB places the primary responsibility for the classification of vendors as Micro or Small enterprises on the assessee, not the auditor. Where the vendor master does not capture the URN, classification tier, principal activity code, and URN issue date, the auditor cannot rely on management representations alone and must either extend the substantive testing (typically by sample verification on the Udyam portal for a subset of the top vendors) or issue an emphasis-of-matter paragraph or qualification. The Clause 22 comment is a foreseeable outcome of a missing vendor-master field. The fix is not to argue with the auditor — the fix is to build the vendor-master field before the year-end so that next year’s disclosure computes cleanly and the auditor’s substantive testing shrinks to a re-performance check rather than a full-population verification.

We have no Micro or Small enterprise vendors — why is the auditor still asking for Clause 22 documentation?

Because a nil disclosure in Clause 22 is itself a disclosure that the auditor has to defend with evidence, not simply omit. To report “Nil” under Clause 22, the auditor has to be satisfied that either the vendor master has been classified against Udyam registration status and no Micro or Small enterprise vendor exists in the payables population, or the MSME payables ageing at year-end shows no invoice past the Section 15 appointed day. The evidence typically requested is the vendor-master MSME classification register, the URN verification log for at least a sample of the top payables, and the aged AP report at 31 March with an MSME filter. A blank Clause 22 without this documentation is a common cause of an auditor qualification even for companies with no material MSME exposure — the qualification then rests on the absence of a control rather than the existence of a disallowance.

What is the practical preparation we can do before next year’s audit to avoid the Clause 22 comment?

Three items build the audit-ready position over roughly a quarter. First, a quarterly Udyam URN re-verification cadence on every URN-registered vendor in the AP master, refreshing the classification tier and the principal activity code from the Udyam portal’s public verification tool — this closes the false-positive gap where a Small vendor has grown into Medium (out of scope), and the false-negative gap where a new vendor has registered mid-year. Second, an AP ageing bucket flag that computes the Section 15 appointed day for each MSME invoice at booking time (15 days from acceptance for no-written-agreement vendors, capped at 45 days with a written agreement) and surfaces past-appointed-day invoices continuously across the year rather than at March 31. Third, a monthly Section 43B(h) exposure projection at the current concessional tax rate — the CFO sees the exposure crystallising month by month, not only when the tax audit fieldwork begins. Together these three feed a Clause 22 disclosure worksheet that the auditor tests against the aged AP report and the Udyam verification log — a re-performance check rather than a full-population verification, and no Clause 22 qualification if the underlying payment run has cleared the exposure before year-end.

Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published Invalid Date

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024