Preventing Avoidable GST Demands: Monthly Reconciliation, Proper Records and a Reasoned Defence from ASMT-10 to Adjudication
Summary: This article, authored by S. Prasad, GST Practitioner, Mysuru, explains how taxpayers can prevent avoidable GST demands through regular reconciliation, proper documentation, timely payment verification and effective responses to departmental notices. It emphasises that successful filing of GST returns does not automatically establish correct tax compliance, making monthly reconciliation of books of account, GSTR-1, GSTR-1A, GSTR-3B, GSTR-2A and GSTR-2B essential for identifying discrepancies before they result in tax demands. The article examines common issues involving outward-supply mismatches, excess or ineligible input tax credit, delayed tax payments, interest liability under Section 50, annual reconciliation through GSTR-9 and GSTR-9C, and the importance of maintaining payment evidence through DRC-03 and DRC-03A. It also explains the distinct purposes of scrutiny notices in ASMT-10, pre-notice intimations in DRC-01A, show-cause notices accompanied by DRC-01, and system-generated discrepancy communications in DRC-01B and DRC-01C. Particular attention is given to preparing issue-wise replies supported by invoices, reconciliations, ledger entries, payment acknowledgements and statutory provisions. The article further discusses jurisdictional objections under Section 6(2)(b), the Supreme Court’s decision in Armour Security (India) Ltd. v. Commissioner, CGST concerning overlapping GST proceedings, limitation under Sections 73, 74 and 74A, and the requirements of personal hearing and reasoned adjudication under Section 75. Through practical illustrations and a monthly compliance control sheet, it highlights the importance of identifying genuine unpaid liabilities, avoiding duplicate demands, documenting portal-related difficulties and preserving evidence for future proceedings. The article concludes that taxpayers should reconcile discrepancies promptly and maintain traceable records, while tax authorities must examine explanations, recognise earlier payments, verify jurisdiction and limitation, and provide reasoned findings before confirming GST demands.
- Introduction: The dispute often begins long before the notice
- 1. Do not treat successful filing as proof of correct compliance
- 2. GSTR-1 versus GSTR-3B: Check the filed figures every month
- Illustration 1: An unnoticed short-payment
- Correct before filing, where the facility permits
- 3. A later payment may resolve principal tax without eliminating interest
- Illustration 2: Liability paid in a subsequent month
- 4. GSTR-2A versus GSTR-2B: First identify what the difference actually represents
- A practical period-wise approach
- Illustration 3: A supplier reports the invoice late
- Historical mismatch certificates are not a universal cure
- 5. GSTR-9 and GSTR-9C: Relevant evidence, but not an automatic cure
- Illustration 4: A difference already dealt with during annual reconciliation
- 6. Preserve the payment trail: DRC-03 and DRC-03A perform different functions
- The payment file should contain more than a challan
- 7. ASMT-10, DRC-01A and DRC-01 are not interchangeable
- Responding to ASMT-10
- Responding to DRC-01A
- Responding to the SCN and DRC-01
- 8. Deal promptly with DRC-01B and DRC-01C
- 9. Enforcement issues the notice; an audit officer passes the order: What must be checked?
- The Supreme Court’s guidance in Armour Security
- Illustration 5: An overlapping demand
- Illustration 6: A different adjudicating officer
- 10. A strong reply gives the officer a verifiable route to the answer
- An illustrative factual submission
- 11. Identify the correct demand provision and test limitation separately
- 12. Portal problems: Record the defect while it is happening
- 13. What the final adjudication order must address
- 14. A monthly control sheet every taxpayer should maintain
- 15. What the department should improve
- Conclusion: Close the month before closing the file
Introduction: The dispute often begins long before the notice
A GST notice received today may concern a return filed three or four years earlier. By then, the accountant may have changed, the supporting reconciliation may be missing, and the taxpayer may remember only that “the return was filed and the tax was paid.”
That recollection is not enough to answer a demand.
The practical safeguard is reconciliation—not merely at the end of the financial year, but every month, followed by preservation of the returns, workings and proof of discharge of liability.
A taxpayer cannot prevent every lawful scrutiny, audit or investigation. What can be reduced is the number of avoidable discrepancies, the accumulation of genuine unpaid liabilities, and the difficulty of defending a transaction years later.
The department, equally, must distinguish a numerical difference from an actual tax shortfall. A difference deserves examination; it does not dispense with examination. Where adjudication is undertaken, section 75 requires consideration through a fair hearing and an order setting out the relevant facts and the basis of the decision.
This article examines both sides of that responsibility: what taxpayers should do before a notice arrives, and what officers should examine before confirming a demand.
1. Do not treat successful filing as proof of correct compliance
There are three separate questions in every tax period:
- Were the transactions correctly recorded in the books?
- Were they correctly reported in the applicable GST statements and returns?
- Was the resulting liability actually discharged?
A filing acknowledgement answers only part of this enquiry. Likewise, a bank challan should not be treated as the complete record of settlement. The GST portal’s payment procedure separately involves the availability of cash or eligible credit, payment against the liability, and filing of the relevant form. The supporting ledger entries and filing acknowledgement therefore matter alongside the challan.
The monthly compliance file should show the connection:
Books of account → GSTR-1/GSTR-1A → GSTR-3B → cash/credit ledger debit → filed acknowledgement.
Where additional payment is made through DRC-03, that payment must form a further identifiable link in the same chain.
2. GSTR-1 versus GSTR-3B: Check the filed figures every month
The GST portal provides for auto-population of outward-supply figures from GSTR-1/GSTR-1A into relevant tables of GSTR-3B. Nevertheless, the taxpayer must verify the actual figures appearing in the return before filing and preserve the filed version afterwards. Auto-population is a facility; it is not an independent assurance that the underlying classification and tax treatment are correct.
The comparison should not stop at turnover. It should cover:
- Taxable value and the corresponding tax;
- IGST, CGST, SGST and cess separately;
- Credit notes and debit notes;
- Amendments relating to earlier periods;
- Zero-rated, exempt, nil-rated and non-GST supplies;
- Advances and adjustments, wherever applicable;
- Transactions requiring separate treatment, including reverse-charge liabilities.
A difference should be entered in an exception register with its reason, supporting documents, proposed action and eventual closure.
Illustration 1: An unnoticed short-payment
Assume the following figures for a month:
| Particulars | Amount |
|---|---|
| Taxable outward supplies correctly reported in GSTR-1 | ₹50,00,000 |
| GST payable at 18% | ₹9,00,000 |
| Liability reported and discharged through GSTR-3B | ₹8,10,000 |
| Apparent shortfall | ₹90,000 |
The taxpayer must first determine whether ₹90,000 is genuinely unpaid or whether the comparison has overlooked an amendment, adjustment or separate payment.
If it is genuinely unpaid, waiting for departmental detection serves no useful purpose. The appropriate correction/payment route and applicable interest should be examined promptly.
If it was already paid separately, the monthly file should identify the DRC-03 ARN, period, tax head, amount and ledger debit. Otherwise, the same ₹90,000 may appear years later as an unexplained difference.
This is particularly important because section 75(12), with its Explanation, includes within “self-assessed tax” the tax payable on outward supplies reported under section 37 but not included in the return under section 39. Such differences therefore cannot safely be left unattended on the assumption that a conventional adjudication notice must always precede recovery.
Correct before filing, where the facility permits
GSTR-1A provides an opportunity, within its prescribed window, to make relevant additions or amendments after GSTR-1 and before GSTR-3B for that tax period. The applicable portal functionality and the particular tables concerned must be checked before filing; taxpayers should not assume that every auto-populated field remains editable.
The sensible practice is straightforward:
Compare first. Correct through the permitted mechanism. File only after reviewing the resulting GSTR-3B.
3. A later payment may resolve principal tax without eliminating interest
Annual reconciliation may establish that the tax was ultimately paid. That does not necessarily establish that it was paid on time.
Illustration 2: Liability paid in a subsequent month
Suppose ₹1,00,000 relating to April was omitted from April’s GSTR-3B but was discharged in a later return.
The reconciliation should identify:
- The original transaction and tax period;
- The return in which liability was omitted;
- The subsequent return or DRC-03 through which payment was made;
- The actual date of discharge;
- The interest treatment and its legal basis.
The taxpayer can then contest a second demand for the same principal amount while separately addressing any legally payable interest for the delay. Section 75(9) recognises that interest on tax short-paid or unpaid remains payable even where it is not specified in the order determining the tax liability.
For ITC disputes, however, the analysis is different. Section 50(3), read with rule 88B (3), concerns ITC wrongly availed and utilised. Interest should not be calculated merely by identifying an entry of wrongly availed credit without examining utilisation under the applicable rule.
4. GSTR-2A versus GSTR-2B: First identify what the difference actually represents
A comparison between GSTR-2A and GSTR-2B is useful for locating supplier-reporting and timing differences. But the tax enquiry is not simply whether those two statements match.
The relevant questions are:
- What credit was taken in GSTR-3B?
- Which invoices support it?
- When did the supplier report those invoices?
- What conditions governed entitlement during that period?
- Was the credit reversed, reclaimed or duplicated?
- Were goods or services actually received?
Historical ITC disputes require period-specific treatment. The law and reconciliation arrangements applicable to the initial GST years cannot be applied indiscriminately to later years. Circular No. 183/15/2022-GST dated 27 December 2022 addresses specified GSTR-3B versus GSTR-2A differences for FY 2017-18 and FY 2018-19. Circular No. 193/05/2023-GST dated 17 July 2023 addresses the period from 1 April 2019 to 31 December 2021, subject to the applicable rule 36(4) restrictions. From 1 January 2022, the supplier-reporting and communication requirement under section 16(2) (aa) materially changes the enquiry.
A practical period-wise approach
| Period | Principal reconciliation approach |
|---|---|
| FY 2017-18 and FY 2018-19 | Examine the specified situations and verification procedure under Circular No. 183 |
| 1 April 2019 to 31 December 2021 | Examine Circular No. 193 together with the rule 36(4) restrictions applicable to the relevant period |
| From 1 January 2022 | Examine supplier reporting and communication in GSTR-2B, along with the other applicable ITC conditions |
The historical restrictions included different percentage limits at different times; a single percentage should not be applied to the entire period.
Illustration 3: A supplier reports the invoice late
A purchaser receives an invoice carrying ₹18,000 GST. The invoice is absent from the relevant GSTR-2B because the supplier reports it later.
The purchaser should record the invoice as an unresolved item, follow up with the supplier and track the statement in which it subsequently appears. Credit must be taken only when the applicable statutory conditions are satisfied.
The later appearance should also be marked against the original invoice. Otherwise, the same invoice may be claimed twice—once through a manual entry and again when it appears in a subsequent statement.
The reconciliation should therefore operate invoice by invoice, not merely through monthly totals.
Historical mismatch certificates are not a universal cure
Under Circular No. 183, the prescribed verification includes a CA/CMA certificate where the supplier-wise difference for the financial year exceeds ₹5 lakh, and a supplier certificate within the specified lower-value category. These requirements operate within the circular’s scope and conditions; they are not a general substitute for GSTR-2B requirements in every later year.
5. GSTR-9 and GSTR-9C: Relevant evidence, but not an automatic cure
Two extreme positions should be avoided.
The first is the taxpayer’s assumption that disclosure in GSTR-9 automatically settles every earlier error.
The second is the officer’s assumption that annual-return disclosures and reconciliation statements need not be examined because the proposed demand arose from monthly-return comparisons.
Neither approach is sound.
The GST portal expressly recognises that additional liability not reported earlier in GSTR-3B may be declared in GSTR-9 and must be paid through the applicable DRC-03 mechanism. Merely entering the amount in the annual return does not establish payment.
GSTR-9C, where applicable, should provide the reconciliation between the financial statements and GST disclosures, with intelligible reasons for differences. The current framework treats it as a self-certified reconciliation statement; the historical CA/CMA-certified regime should not be confused with the present position.
Illustration 4: A difference already dealt with during annual reconciliation
Assume:
| Particulars | Amount |
|---|---|
| Tax liability according to the relevant outward-supply reconciliation | ₹24,00,000 |
| Liability discharged through GSTR-3B | ₹23,40,000 |
| Additional tax paid through DRC-03 during annual reconciliation | ₹60,000 |
If a later notice demands ₹60,000 solely by comparing GSTR-1 with GSTR-3B, the taxpayer should produce:
- The monthly and annual reconciliation;
- The relevant GSTR-9 disclosures;
- The applicable GSTR-9C explanation;
- The filed DRC-03 and ARN;
- The ledger debit and payment particulars;
- A separate explanation of interest, where applicable.
The proper question is whether the earlier ₹60,000 payment relates to the very liability now proposed. If it does, the principal cannot sensibly be examined as though that payment never occurred. The order must deal with the relevant facts and explain its conclusion.
Annual disclosure does not necessarily revise the original monthly return or remove a statutory default. Its significance lies in what it proves when read with the transaction records and payment evidence.
6. Preserve the payment trail: DRC-03 and DRC-03A perform different functions
The correct forms are GST DRC-03 and GST DRC-03A.
DRC-03 is used to intimate payments under the applicable circumstances. The portal manual provides categories including annual return, reconciliation statement, scrutiny, investigation/enforcement and payment connected with a show-cause notice.
DRC-03A serves a different purpose: it enables an eligible payment already made through DRC-03 to be adjusted against the corresponding outstanding demand. It is not a fresh payment or a fresh transfer of ITC. The official advisory requires the DRC-03 ARN and the relevant demand-order particulars, following which the corresponding liability-ledger entries are updated.
The payment file should contain more than a challan
Preserve:
- Filed DRC-03 and its ARN;
- The selected cause of payment;
- Financial year, tax period and statutory provision;
- Tax-head-wise allocation;
- Cash-ledger and eligible credit-ledger debits;
- Interest and penalty particulars, separately;
- The accompanying explanation and calculation;
- Relevant acknowledgement or conclusion communication;
- DRC-03A and the updated liability ledger, where adjustment is applicable.
The portal manual permits use of eligible credit for applicable liabilities but specifies cash payment for interest and penalty. Taxpayers should not assume that every liability or every payment category can be discharged through ITC.
A useful control is a “payment mapping register” linking every additional payment to the particular discrepancy, notice or demand. This prevents both forgotten payments and accidental double adjustment.
7. ASMT-10, DRC-01A and DRC-01 are not interchangeable
A taxpayer must identify the stage of the proceeding before preparing a reply.
| Communication | Nature and appropriate response |
|---|---|
| ASMT-10 | Scrutiny communication identifying discrepancies; respond through ASMT-11 with explanations and supporting records |
| ASMT-12 | Communication accepting the explanation in the scrutiny process |
| DRC-01A | Pre-notice intimation of the officer’s ascertainment; make the appropriate submission in Part B |
| SCN accompanied by DRC-01 | Formal demand proposal and its electronic summary; submit the substantive defence through DRC-06 |
| Adjudication order accompanied by DRC-07 | Decision and electronic summary; compare the detailed findings with the notice, reply, hearing record and payment evidence |
The scrutiny forms operate under the scrutiny framework, while rule 142 governs the relevant demand-and-recovery forms.
These are not compulsory steps in one unbroken sequence in every case. Under the current wording of rule 142(1A), the proper officer “may” communicate the ascertainment through DRC-01A. Absence of DRC-01A should therefore not automatically be presented as fatal without examining the rule applicable at the relevant time.
Responding to ASMT-10
The reply should answer each discrepancy in the same sequence as the notice.
For each item, provide:
- The figure stated by the officer;
- The figure according to the taxpayer;
- The reason for the difference;
- The tax consequence, if any;
- The supporting annexure;
- The action or relief requested.
Where the explanation is accepted, obtain and preserve ASMT-12. Do not treat a telephone conversation or silence as a documented closure.
Responding to DRC-01A
Separate the proposed amount into:
- Liability admitted;
- Liability already discharged;
- Liability disputed on facts;
- Liability disputed on law.
If an admitted amount is paid, identify precisely what that payment covers. Do not leave the accompanying explanation so broad that payment of one item appears to admit the entire proposal.
Responding to the SCN and DRC-01
DRC-01 is the summary accompanying the show-cause notice. The substantive notice, allegations, calculations and relied-upon material must be examined; the summary should not be treated as an adequate substitute for a properly particularised notice. The prescribed electronic reply is DRC-06.
An earlier ASMT-11 or DRC-01A reply should be expressly incorporated and, where necessary, reattached. A taxpayer should not assume that the adjudicating officer will reconstruct the defence from earlier correspondence.
8. Deal promptly with DRC-01B and DRC-01C
Two system-driven communications also deserve attention:
- DRC-01B concerns specified GSTR-1/IFF versus GSTR-3B liability differences under rule 88C.
- DRC-01C concerns specified GSTR-2B versus GSTR-3B ITC differences under rule 88D.
The framework requires payment and reporting of the relevant particulars, or an explanation through the prescribed Part B response, within seven days. These communications should not be handled as though they carry the same response period as an ordinary scrutiny notice.
The taxpayer should maintain an active portal-review arrangement. Responsibility for checking notices must be assigned to a named person, rather than left between the proprietor, accountant and consultant.
9. Enforcement issues the notice; an audit officer passes the order: What must be checked?
This issue requires care. Different officer designations do not, by themselves, establish a violation of section 6(2)(b).
Three questions must be kept separate:
- Does the adjudicating officer possess the required statutory assignment and jurisdiction?
- Is the officer acting on a validly assigned or transferred proceeding?
- Has another tax administration independently initiated proceedings on the same subject matter?
Section 6(2)(b) addresses overlapping proceedings between the Central and State/Union Territory tax administrations. A change of officer or wing within the same administration is not automatically a breach of that provision. The proper-officer assignment, applicable notifications, monetary competence and any transfer order must be examined independently.
The Supreme Court’s guidance in Armour Security
In M/s Armour Security (India) Ltd. v. Commissioner, CGST, Delhi East Commissionerate & Anr., 2025 INSC 982, decided on 14 August 2025, the Supreme Court distinguished investigatory steps from formal adjudicatory proceedings. Summons, search and evidence-gathering do not, merely by themselves, constitute initiation of proceedings for the statutory bar. The Court also examined the need to identify the same liability or contravention and the same or overlapping demand, rather than relying merely on an overlapping financial year.
Illustration 5: An overlapping demand
Suppose the State authority has issued an SCN alleging ₹8 lakh of excess ITC on a specified set of invoices. The Central authority subsequently issues another SCN seeking the same ₹8 lakh on the same invoices and facts.
That calls for a specific section 6(2)(b) objection supported by both notices and an invoice-wise comparison.
By contrast, a second proceeding concerning an independent outward-supply suppression issue is not necessarily barred merely because it concerns the same financial year. The subject matter must be compared, not just the period.
Illustration 6: A different adjudicating officer
An enforcement officer issues the SCN, and an officer posted in an audit wing later adjudicates it.
The taxpayer should seek or verify the instrument assigning adjudication, the officer’s competence and the procedural record. If there is no lawful assignment, raise that defect precisely. If the case has been validly assigned to a competent adjudicating officer, the officer’s earlier posting or wing description alone does not establish invalidity.
A jurisdiction objection should identify the missing legal authority—not merely express discomfort with the departmental arrangement.
10. A strong reply gives the officer a verifiable route to the answer
A useful reply structure is:
- Notice particulars and applicable statutory provision;
- Brief facts and the taxpayer’s business;
- Preliminary objections, including jurisdiction and limitation where supported;
- Issue-wise factual reconciliation;
- Legal submissions appropriate to the relevant period;
- Details of amounts already paid;
- Separate interest and penalty submissions;
- Request for relied-upon documents, where not supplied;
- Express request for personal hearing;
- Precise relief sought.
The annexures should be indexed and cross-referenced. A large collection of documents without a reconciliation may be no more useful than a reconciliation without documents.
An illustrative factual submission
“The proposed difference of ₹3,60,000 comprises ₹2,40,000 discharged through DRC-03 dated _, ₹90,000 arising from the amendments identified in Annexure B, and ₹30,000 requiring separate examination. The payment ARN, relevant ledger debit and tax-head-wise reconciliation are enclosed. The proposed principal demand may therefore be reconsidered after giving effect to these records. Interest, if legally payable, may be determined on the correct amount and for the correct period.”
This is more effective than the unsupported statement, “All taxes have been paid.”
11. Identify the correct demand provision and test limitation separately
For determination relating to periods up to FY 2023-24, the relevant sections 73/74 framework must be examined. Section 74A applies to determination pertaining to FY 2024-25 onwards. It provides its own notice and adjudication timelines, including the 42-month notice period specified in subsection (2).
The fact that a notice arrives after three or four years does not, by itself, establish that it is time-barred.
A limitation working should identify:
- The financial year;
- The applicable statutory provision;
- The relevant annual-return due date;
- Notice and order deadlines;
- Applicable extensions or exclusions;
- Actual service and order dates.
Section 75 contains provisions concerning exclusions and consequences where adjudication is not completed within the applicable statutory period. Limitation should therefore be calculated, not asserted in a standard paragraph.
12. Portal problems: Record the defect while it is happening
Taxpayers may encounter incorrect population, unavailable functions or unresolved helpdesk complaints. A statement made years later that “the portal was not working” is much harder to evaluate than a contemporaneous record.
Maintain a technical-issue file containing:
- Date and time of the problem;
- GSTIN and affected return period;
- Screenshot and error message;
- Relevant return downloads;
- Helpdesk ticket and follow-up correspondence;
- The correct underlying transaction data;
- Written intimation to the jurisdictional officer where appropriate;
- Subsequent correction or payment particulars.
A helpdesk ticket should not be treated as permission to ignore a notice, omit a return or leave tax unpaid. Where the problem prevents filing a reply, document the attempt, seek time promptly and communicate the substantive response through an appropriate alternative channel, while continuing efforts to complete the prescribed portal filing.
The departmental enquiry should then distinguish an established technical defect from an unsupported allegation. Neither the taxpayer nor the officer benefits when a genuine portal issue is left undocumented.
13. What the final adjudication order must address
A reasoned order should deal with the material defence, particularly:
- Reconciliation of books with returns;
- Relevant GSTR-9 and GSTR-9C disclosures;
- Subsequent-period adjustments;
- Earlier DRC-03 payments;
- Applicable historical ITC circulars;
- Interest computation;
- The factual basis for penalty;
- Jurisdiction and limitation objections;
- Any alleged overlapping proceeding.
Section 75(4) provides for a hearing where requested in writing or where an adverse decision is contemplated. Section 75(6) requires relevant facts and the basis of decision to be stated. Section 75(7) prohibits confirmation beyond the amount or grounds specified in the notice.
A reply does not become “unsatisfactory” merely because the officer disagrees with it. The order must explain why the material explanation fails.
Equally, taxpayers should not rely on procedural objections alone where a factual reconciliation is available. A sound defence ordinarily answers both questions: whether the proceeding is legally valid and whether the alleged liability actually exists.
14. A monthly control sheet every taxpayer should maintain
The following is a practical internal-control format:
| Control | Evidence to retain |
|---|---|
| Books versus GSTR-1 | Sales-register reconciliation and exception list |
| GSTR-1/GSTR-1A versus GSTR-3B | Tax-head-wise comparison and amendment trail |
| Purchase register versus GSTR-2B | Invoice-wise matched, missing, disputed and deferred items |
| GSTR-2A versus GSTR-2B | Explanation of relevant timing/reporting differences |
| ITC availed, reversed and reclaimed | Credit movement register |
| Liability discharged | Filed GSTR-3B and ledger debits |
| Additional payments | DRC-03, ARN, workings and payment mapping |
| Adjustment against demand | DRC-03A and updated liability ledger, where applicable |
| Portal difficulties | Screenshots, tickets and written follow-up |
| Notices and replies | Complete communication, annexures and filing acknowledgement |
For quarterly filers, adapt this control to the applicable filing cycle while keeping transaction and payment records current.
Keep downloaded electronic copies as well as an organised printed file where useful. The objective is not to accumulate paper. It is to preserve a readable, traceable record of what was reported, what was paid and why a difference exists.
15. What the department should improve
A fair compliance system should reduce repetitive disputes, not merely generate more comparisons.
As a matter of sound administration, the following improvements deserve priority:
- Match proposed demands with identifiable earlier payments before confirmation.
- Examine annual-return and reconciliation disclosures placed on record.
- Specify the transactions, periods and tax heads behind a discrepancy.
- Avoid separate proceedings seeking the same liability.
- Ensure that assignment and transfer of adjudication are transparent.
- Provide workable routes for documented portal failures.
- Give meaningful reasons for rejecting reconciliations and supporting documents.
These are practical measures for better administration, supported by the statutory requirements for reasoned adjudication and the Supreme Court’s treatment of overlapping jurisdiction.
Conclusion: Close the month before closing the file
The most useful time to resolve a GST mismatch is the month in which it arises.
A difference left unexplained today may become a demand several years later. By then, the dispute may involve not only principal tax but also interest, penalty, lost records and jurisdictional complications.
Taxpayers should therefore verify the filed GSTR-1/GSTR-1A and GSTR-3B, reconcile purchase records with the relevant ITC statements, identify unresolved items, and preserve the actual payment trail. Annual reconciliation should complete that work, not begin it.
The department has a corresponding duty: examine the explanation, recognise the payment, identify the actual unpaid liability and give reasons before confirming a demand.
The central discipline is simple: every material difference must have an explanation, every explanation must have evidence, and every payment must be traceable to the liability it discharges.






