ITR-6 AY 2026–27 Audit Reconciliation: Prevent Duplicate Add-Backs and Answer Section 143(1)(a) Variances

Online income tax return preparation with laptop

A mismatch is a risk to investigate, not an automatic second tax charge

An expense reported under one section in Form 3CD and another field in ITR-6 can produce a validation variance or a proposed processing adjustment. It does not invariably mean the expense has been deducted twice, disallowed twice or generated a demand. The key question is whether the correct tax effect is already included once in the returned income and whether the chosen field is accurate. This article sets out a transaction-level reconciliation and response file for FY 2025–26 / AY 2026–27 under the Income-tax Act, 1961, checked on 27 October 2026. Income-tax Act, 1961: sections 139(5), 143(1)(a), 154 and 249.

Reconcile three actual artefacts, not three draft spreadsheets

Use the submitted and accepted tax audit report with its acknowledgement, the final tax computation, and the actual filed ITR-6 JSON/preview with acknowledgement. A late spreadsheet correction is not evidence that the filed return contains it. Add a fourth record after processing: the section 143(1) intimation and its adjustment comparison. Identify the PAN, AY, version, filing section and timestamps in the working. A changed tax audit report also needs its legally valid filing history; do not silently substitute a draft report for the one the Department received.

Give every adjustment a transaction identifier and one final tax effect

For each line record ledger/invoice, expense population, original AY, booked amount, legal section, actual audit clause, whether the audit amount is gross disclosure or inadmissible amount, computation effect, OI subrow, BP destination and evidence. Maintain separate current additions, current deductions and disclosure-only lines. Reconcile subtotals by legal section, then the full profit-to-taxable-income bridge. A cost described in two audit disclosures is not automatically two costs. Where provisions overlap, analyse the legal result and identify the same underlying population before combining amounts.

Use specific mappings to expose hidden duplicates

For example, Form 3CD 21(b)(ii) resident withholding adjustments map through OI 8A(b)/8Aj to BP A16. A matching amount also manually entered in A24 can double the returned addition even when the specific OI field is correct. Section 43B current additions map from OI 11i to A18; releases of prior disallowances from OI 10i to A31. MSMED interest uses OI 17/A19, while current clause (h) supplier-principal disallowance uses OI 11h/A18. Book depreciation uses A11 and tax depreciation A12, supported by the audit clause 18 working. These mappings are controls for one tax effect, not a command to add every source field independently. AY validation Category D item 23 and Annexure 1.

Separate a disclosed transaction from an indicated disallowance

Form 3CD clause 23 reports specified-person payments; the gross payment is not automatically excessive or unreasonable under section 40A(2). Clause 34 withholding information is not itself the final section 40(a) expense addition. Club-payment disclosures also require their own deductibility analysis. In contrast, a report field expressly identifying an inadmissible amount requires a clear return treatment or a supported explanation of disagreement. Document whether the company accepts the audit conclusion, has already reflected it elsewhere, or takes a different legally supported position. Do not alter the auditor’s filed opinion in the return workpaper or invent a missing clause. Official Form 3CD disclosure fields.

Understand what section 143(1)(a) authorises

Section 143(1)(a)(iv) covers expenditure disallowance or income increase indicated in the audit report but not taken into account in the return computation. Other listed processing powers include arithmetical errors and certain incorrect claims apparent from the return. The provision requires communication of a proposed adjustment and consideration of the taxpayer’s response; where no response is received within thirty days of issue, the statute provides for making the adjustment. This does not make every disclosure an addition or decide every disputed legal issue against the taxpayer. A proposed variance is different from the final section 143(1) intimation and any payable amount it determines. Income-tax Act, 1961: sections 139(5), 143(1)(a), 154 and 249.

Answer each proposed variance with an evidence bridge

Download and authenticate the communication, confirm the AY and actual response deadline, and compare the reported audit field with the filed return field. In the portal’s e-Proceedings service, open the prima facie adjustment, review each variance and provide an Agree/Disagree response as appropriate. Where disagreeing because the effect is already taken, identify the exact filed OI/BP row, amount, computation page and transaction IDs, and explain why an additional increase would duplicate it. Provide the evidence/explanation facilities available for that communication. Complete declaration and submission for all variances and preserve the transaction ID and response copy; saving an individual draft response is not final submission. Official e-Proceedings response manual.

Use the correction route that matches the stage and error

Before filing, correct the computation and generated return, then rerun validation. After filing, a valid revised return under section 139(5) may correct a discoverable omission/wrong statement within its AY-specific statutory period and before assessment completion, where applicable; it does not replace a pending notice response. For this AY the Finance Act, 2026 amended revision period extends to the end of the assessment year, 31 March 2027, subject to earlier assessment completion; check applicable fee/utility rules when using that route. A section 139(9) defective-return notice is a different proceeding requiring its own response. After an intimation/order, section 154 rectification addresses a mistake apparent from the record; it is not an unrestricted fresh deduction or a substitute for resolving a debatable legal claim through the appropriate remedy. Income-tax Act, 1961: sections 139(5), 143(1)(a), 154 and 249.

Do not let a rectification request hide an appeal deadline

The official rectification service supports reprocessing and data-correction categories according to the case, and the offline route uses the applicable utility-generated JSON/XML. Under section 154(7), the general amendment limit is four years from the end of the financial year of the order sought to be amended, subject to statutory exceptions. That long limit does not extend a separate appeal deadline. Where an appeal is appropriate, section 249 generally prescribes thirty days from the relevant service/communication event, with the statutory provisions on admission and condonation; check the precise order and route promptly. Merely filing a rectification request or grievance does not by itself settle, pay or stay a demand. Official rectification filing manual. The current rectification FAQ restricts fresh or changed loss/MAT-credit claims in its Return Data Correction category. If that limitation affects the required correction, establish the appropriate statutory and jurisdictional route rather than forcing the change into an unsupported portal request.

Close both the tax balance and the loss/credit records

A wrong addition can increase current tax, reduce a refund or reduce a carried loss without producing immediate tax. Compare the processed normal income, MAT, MAT credit, losses, tax payments and interest with the filed return. A supported mismatch explanation should not promise that processing will necessarily accept it; preserve the order and follow the available remedy if needed. Where the error originates in the audit report, coordinate with the auditor and test the legal basis and procedure for any report revision rather than assuming it may always be replaced. Retain the final reconciliation, submitted responses and subsequent orders as the next year’s opening evidence.

Applicable primary references

Income-tax Act, 1961: sections 139(5), 143(1)(a), 154 and 249 AY 2026–27 ITR-6: OI, BP and tax/loss schedules AY validation Category D item 23 and Annexure 1 Official Form 3CD disclosure fields Official e-Proceedings response manual Official rectification filing manual Official rectification FAQs

Six worked illustrations

All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules. Tax figures show the computation stage; the final net payable or refund is rounded under section 288B to the nearest ₹10 after all applicable adjustments.

Illustrative example 1: The company itself adds one expense twice

Starting profit is ₹20,00,000. One supported ₹3,00,000 disallowance should produce ₹23,00,000 before other adjustments. If the same amount enters BP A16 and A24, the result becomes ₹26,00,000. At an assumed applicable normal 25% plus 4% cess, with MAT below normal tax and no credits, the unnecessary ₹3,00,000 creates ₹78,000 extra tax. This error exists before any CPC adjustment.

Illustrative example 2: Wrong field, correct total, proposed extra addition

A ₹6,00,000 section 40(a)(ia) effect is already included at A24 instead of its correct OI 8A(b)/BP A16 route. Starting profit ₹50,00,000 plus the single effect gives ₹56,00,000. Correcting the location alone does not change that total. A further proposed ₹6,00,000 increase would produce ₹62,00,000; at the assumed 26% composite normal rate, the additional model tax would be ₹1,56,000. The response should prove the existing effect and explain the classification; a wrong field alone does not prove tax was underpaid.

Illustrative example 3: Gross related-party disclosure is not the addition

Clause 23 reports ₹25,00,000 of payments. Assume a supported section 40A(2) analysis identifies only ₹1,50,000 as excessive. The correct model add-back is ₹1,50,000, not ₹25,00,000. A gross-disclosure import would overstate the addition by ₹23,50,000; the working must retain the basis for the remaining ₹23,50,000 rather than merely asserting a mismatch.

Illustrative example 4: Similar supplier labels, distinct adjustments

Assume the legally inadmissible micro-enterprise principal is ₹10,00,000 and separately booked statutory MSMED interest ₹20,000. Proper current adjustments total ₹10,20,000, split between BP A18 and A19. These are not duplicate amounts merely because they refer to the same supplier. Conversely, adding the ₹10,00,000 principal again at A19 would create a duplicate principal effect and omit correct classification of the separate interest.

Illustrative example 5: One payment-year allowance imported twice

An opening section 43B disallowance pool is ₹8,00,000. Of it, ₹5,00,000 is actually paid and eligible for allowance in FY 2025–26; ₹3,00,000 remains unrelieved. With starting profit ₹40,00,000 and no new book deduction, the correct single deduction gives ₹35,00,000. If a manual deduction at A32 duplicates the same release already at OI 10i/BP A31, the result becomes ₹30,00,000: ₹5,00,000 understated. At the assumed normal 26% composite rate, the model tax shortfall is ₹1,30,000, subject to the stated absence of MAT/credits.

Illustrative example 6: Duplicate disallowance can harm a loss without a demand

A company’s starting ordinary business loss is ₹5,00,000. One valid ₹2,40,000 addition leaves a loss of ₹2,60,000 before other adjustments. Duplicating the same addition leaves only ₹20,000 loss. Assume no other taxable income or MAT liability; immediate income tax remains nil in both models. Yet the reported loss is understated by ₹2,40,000, so the reconciliation matters even without an immediate demand.

Ten-step verification table

Step	Action	Evidence
1	Freeze the filed evidence set	Accepted 3CD, tax computation and submitted ITR acknowledgements.
2	Assign adjustment IDs	Ledger/invoice and original-year identifiers.
3	Classify audit figures	Gross disclosure, indicated addition or allowable deduction.
4	Trace legal provision and book treatment	Eligibility memo and proof the expense affected the starting result.
5	Match exact OI/BP paths	AY form and Annexure 1 crosswalk.
6	Search duplicate destinations	Specific row versus A23/A24/A32 and import/manual entries.
7	Reconcile the complete bridge	Section subtotals and closing income/loss/credit workings.
8	Review any proposed variance	Communication, issue date, deadline and exact reported field.
9	Submit supported responses or corrections	Appropriate route, final transaction ID and evidence copy.
10	Verify processed consequences	Intimation/order, demand/refund and next-year opening records.

Sixteen practitioner FAQs

1. Will a wrong-section mismatch always cause a demand?

No. Examine whether income is already correct, the actual proposed adjustment, MAT, credits and payments; outcomes can differ.

2. Can a duplicate arise even without processing by CPC?

Yes. Manual and imported entries can add the same expense twice inside the company’s filed computation.

3. Is an OI amount and its linked BP amount a duplicate by themselves?

No. The OI-to-BP flow is the intended single effect; a second independent entry elsewhere can duplicate it.

4. Why examine the filed JSON instead of the current spreadsheet?

Processing uses the filed data, which may differ from a later-edited working or a software preview never submitted.

5. Does every clause 23 payment imply section 40A(2) excess?

No. The gross related-party disclosure needs a separate excessive/unreasonable-payment analysis.

6. Should every clause 34 TDS figure be added under section 40?

No. Determine the affected expense, applicable provision, timing and relief; withholding information is not automatically the addition.

7. Can one supplier have both A18 and A19 adjustments?

Yes, for distinct section 43B(h) principal and MSMED statutory interest; use separate amounts and legal tests.

8. What statutory processing provision covers missed audit-report effects?

Section 143(1)(a)(iv) concerns indicated expenditure disallowance or income increase not taken into account in the return.

9. Is a proposed adjustment already the final demand?

No. It provides a response opportunity before the final processing result; read the actual communication and stage.

10. How long does section 143(1)(a) provide before no-response processing?

The statute refers to thirty days from issue of the proposed-adjustment intimation; monitor the actual communication and submit promptly.

11. What best supports an already-added explanation?

The filed row, exact amount, transaction ID, computation bridge and audit extract showing the same tax effect has already been included.

12. Is saving Agree or Disagree on one line enough?

Complete every applicable variance, declaration and final submission; preserve the response transaction ID and copy.

13. Can a revised return replace responding to a pending notice?

Do not assume so. Meet the notice response requirement and independently test whether a revised return is valid and appropriate.

14. When is section 154 rectification relevant?

For a mistake apparent from the record in the relevant intimation/order, using the supported category; not every disputed tax position is rectifiable.

15. Does a rectification application extend the appeal period or stay recovery?

Do not assume either. Assess appeal timing and demand-management remedies separately under the applicable law.

16. Can a loss company ignore an addition because current tax is nil?

No. It may reduce the carry-forward loss or another opening balance even where immediate tax or demand does not arise.

Conclusion

Reconcile Form 3CD, the tax computation and filed ITR-6 by transaction, prevent duplicate tax effects, and distinguish proposed adjustments from final demands.