Clause 44 of Form 3CD is easy to underestimate because it looks like a single GST-linked table. In practice, it is a data-classification exercise: the tax-audit working papers need a defensible bridge from the entity’s total expenditure to expenditure with GST-registered suppliers and expenditure with unregistered suppliers. The Income Tax Department’s current tax-audit reporting summary, updated for the Finance Act, 2026, continues to describe Clause 44 as requiring details of total expenditure incurred during the year, split between entities registered under GST and entities not registered under GST.
This article explains how to approach that exercise without turning Clause 44 into a mechanical copy of the purchase register. The objective is to build a reconciled, reviewable working paper that can support the figure ultimately reported in Form 3CD.
What exactly does Clause 44 ask for?
The prescribed table was introduced into Form 3CD through the Income-tax (Eighth Amendment) Rules, 2018 notification. It asks for the total amount of expenditure incurred during the year and then divides the GST-registered portion into three buckets: expenditure relating to exempt goods or services, expenditure relating to entities under the composition scheme, and expenditure relating to other registered entities. It also asks for the total amount relating to registered entities and the expenditure relating to entities not registered under GST.
The Income Tax e-Filing portal’s Form 3CB-3CD page confirms that Form 3CD contains the prescribed particulars for a tax audit under section 44AB and that the form is filed through the portal using the applicable utility process.
Why a purchase-register total is not enough
A purchase register may contain only inventory and service purchases captured through a procurement process. Clause 44, however, is framed around expenditure incurred during the year. That makes the starting population important. A finance team should first define which ledgers and transaction classes make up the expenditure universe, then document how each class is treated for Clause 44.
The practical risk is inconsistency. For example, one branch may classify a vendor from its GSTIN master while another branch may rely on whether GST was charged on the invoice. Those are not the same test. A registered supplier can make an exempt supply, and a composition supplier is also registered. The working paper therefore needs both the supplier’s GST status and the nature of the transaction.
A practical five-step workflow
1. Build the expenditure universe from the general ledger
Start with the trial balance and identify all expense and purchase ledgers that could feed the Clause 44 population. Do not begin by downloading GSTR-2B and treating it as the entire universe. GSTR-2B is useful for GST reconciliation, but the tax-audit table is driven by expenditure in the books.
Create a control total from the ledger extract and retain a mapping of ledger groups included, excluded or separately reviewed. The key review question is simple: can another reviewer reproduce the population from the books?
2. Create a clean vendor master
For each supplier, capture a stable identifier such as vendor code, legal name and GSTIN where available. Then classify the supplier as registered or unregistered for the relevant period. Where a supplier has multiple GST registrations, preserve the GSTIN used for the transaction rather than collapsing everything only at PAN level.
Do not infer registration merely from tax being charged. Exempt supplies from registered persons and supplies from composition taxpayers are separate categories in the prescribed Clause 44 table.
3. Classify the registered-supplier spend into the three prescribed buckets
- Exempt goods or services: registered supplier, but the relevant supply falls in the exempt bucket for the reporting classification.
- Composition scheme: expenditure relating to an entity falling under the GST composition scheme.
- Other registered entities: the balance of expenditure relating to registered entities that does not fall into the first two buckets.
Build the classification at a level that can be traced back to invoices or ledger entries. A vendor-level default may be efficient, but transaction-level exceptions should be possible where the same supplier has different kinds of supplies.
4. Reconcile the table, not just the GST data
Your working paper should show how the total expenditure population connects to the registered and unregistered buckets. It should also show how the three registered sub-buckets add to the total registered amount. If there are differences because the team has adopted a particular treatment for items that do not fit a normal supplier-spend model, document the nature of those differences and the basis used.
Use GST data as a cross-check rather than as a substitute for the books. Large mismatches between the books, vendor master and GST data should be investigated for causes such as missing GSTINs, duplicate vendor codes, year-end accruals, reversals, imports, branch postings or supplier-status changes.
5. Retain evidence for review and sign-off
The final file should contain the source ledger extract, vendor-status logic, exception list, reconciliation, management explanations for unresolved items and the final Clause 44 summary. ICAI’s Guidance Note on Tax Audit under section 44AB, Revised 2026 is the current professional reference point for members conducting tax audits and should be checked for engagement-specific reporting considerations.
Worked illustration
Assume the ledger-based expenditure population identified for Clause 44 is Rs. 12 crore. After vendor and transaction classification, Rs. 8.6 crore relates to registered suppliers and Rs. 3.1 crore relates to unregistered suppliers. A further Rs. 0.3 crore remains in an exception file because the vendor status or treatment is not yet supported.
Do not force the Rs. 0.3 crore into a bucket merely to make the table balance. Resolve the exceptions first. Suppose the review shows Rs. 0.2 crore belongs to other registered entities and Rs. 0.1 crore to unregistered entities. The final classification then becomes Rs. 8.8 crore registered and Rs. 3.2 crore unregistered, which reconciles to the Rs. 12 crore control total. Within the Rs. 8.8 crore registered amount, the team should separately identify the exempt, composition and other-registered components.
Common mistakes in Clause 44 working papers
- Using only GSTR-2B as the starting population and missing book expenditure outside that dataset.
- Treating every invoice without GST as an unregistered-supplier transaction.
- Classifying suppliers only once for the entire year without considering changes in registration status or transaction-specific exceptions.
- Ignoring branch or location-level vendor masters and then double-counting or omitting expenditure during consolidation.
- Reporting a final number without preserving the ledger-to-table reconciliation and exception-resolution evidence.
- Allowing the registered sub-buckets to be populated independently without a control that ties them back to the total registered amount.
Year-end checklist for the tax auditor and finance team
- Freeze the ledger population and record the extraction date.
- Document which ledgers make up the Clause 44 expenditure universe.
- Validate GSTIN and registration status for material vendors and exceptions.
- Separate exempt, composition and other registered expenditure.
- Identify unregistered-supplier expenditure independently.
- Reconcile the registered and unregistered totals to the expenditure control total.
- Investigate material differences with GST data and preserve explanations.
- Review unusual year-end accruals, reversals and manual journals.
- Retain an exception log and evidence of how each material exception was closed.
- Perform a final technical check against the current Form 3CD utility and the latest ICAI tax-audit guidance before filing.
Practical takeaway
Clause 44 is best handled as a controlled data-reconciliation exercise, not a last-minute GST report. Start from the books, classify suppliers and transactions using documented rules, reconcile every bucket to a control total and retain the evidence behind exceptions. A clean working paper makes the final Form 3CD number easier to review, defend and reproduce in the next audit cycle.
