Free tools Windows power users keep installed
One-click scans. No signup required.
A GST input-tax-credit (ITC) mismatch communication is not automatically a demand to repay every rupee that differs between GSTR-2B and GSTR-3B. First identify whether you received an automated Form GST DRC-01C intimation or a statutory show-cause notice, then reconcile the figures invoice by invoice, classify the cause, and respond through the route and deadline stated on the actual communication.
Start by identifying exactly what you received
The phrase “GST notice” covers different processes. The heading, form number, issuing authority, tax period, allegations, requested action and deadline on your communication determine what you must do.
As an Amazon Associate I earn from qualifying purchases.
Form GST DRC-01C: automated ITC mismatch intimation
GST portal guidance describes Form GST DRC-01C as an automated intimation about a difference between input tax credit available in GSTR-2B and credit claimed in GSTR-3B or GSTR-3BQ. The response is filed in Part B of the form. It is a compliance response to the portal comparison, not the same document as a statutory adjudication notice.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteSection 73 show-cause notice
A show-cause notice under section 73 of the Central Goods and Services Tax Act is a separate statutory step for specified non-fraud cases, including credit alleged to have been wrongly availed or utilised. It normally sets out the period, tax, interest and proposed action and gives a deadline for a detailed reply. Treat each allegation separately and address the statutory basis, not just the arithmetic difference.
#1 Best Overall
Make an identification record
Before analysing the numbers, download the communication and its attachments from the official GST portal. Record:
- form number and document reference or identifier, if shown;
- issuing authority and the date of issue;
- tax period or periods covered;
- amounts and tax heads in dispute;
- the stated basis for the comparison or allegation; and
- the exact response deadline and filing channel.
Keep the portal download, delivery details and any system-generated acknowledgement together. If an email or letter does not match the notice history on the portal, verify it before sharing records or making payment.
What the GSTR-2B versus GSTR-3B difference actually means
GSTR-2B is a system-generated statement of inward supplies and related credit information reported by suppliers and other specified sources. GSTR-3B is the return in which the recipient self-assesses and reports its tax liability and ITC. A total difference can therefore have several explanations; it is not proof that every unmatched invoice is ineligible.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteGSTN’s guidance instructs taxpayers to reconcile GSTR-2B with their books and warns that the statement’s “not available” summary covers only specified situations. Other statutory restrictions can apply even when the system does not flag an invoice. Eligibility remains a self-assessment under the CGST Act, including the conditions in section 16.
| Question | GSTR-2B | GSTR-3B |
|---|---|---|
| What it is | A system statement of credit information received from supplier filings and specified records. | The taxpayer’s return reporting outward tax, eligible ITC, reversals and payment. |
| Whose data drives it | Supplier or other counterparty reporting, including later amendments. | The recipient’s books, self-assessment and return workings. |
| What a difference can show | Timing, amendment, document-data or reporting differences, as well as possible eligibility concerns. | Credit claimed, reversed, reclaimed or otherwise reported by the recipient. |
| Does it decide legal eligibility by itself? | No. It is an important data source, but legal conditions still have to be tested. | No. A claim in the return must satisfy the Act and applicable rules. |
Build the records before you draft a reply
Download a separate copy of the GSTR-2B statement used for every period in the communication. Do not rely on a later regenerated view if supplier amendments have changed the data. Gather the corresponding GSTR-3B returns, purchase register, invoice and debit-note files, credit notes, supplier correspondence, receipt or service evidence, payment and accounting records, and any earlier reversal or reclaim calculation.
Organise the evidence by tax period and keep the original file names or a document index. A reviewer should be able to move from a row in your reconciliation to the invoice, accounting entry, receipt evidence and return table without guessing.
Reconcile at invoice level
Start with a working paper rather than a narrative explanation. Use one row for each invoice, debit note or credit note and include at least these columns:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- supplier GSTIN and legal name;
- document number and document date;
- taxable value and each applicable tax head (IGST, CGST, SGST or UTGST, and cess where relevant);
- the period in which the document appears in GSTR-2B;
- the period and table in which ITC was claimed in GSTR-3B;
- amendment, credit-note or debit-note references;
- book entry, receipt or service-completion reference;
- eligibility result and reason for any reversal; and
- proposed action and the evidence supporting it.
Match the GSTIN, document number and date, taxable value and tax amount. Then check whether the same document appears twice, whether a supplier amendment changed an earlier value, and whether a credit or debit note has been netted in a different period.
Check these common causes one by one
- Supplier filing or amendment timing: the supplier may have filed GSTR-1, amended a document or reported it after the statement used for your return.
- Tax-period differences: an invoice can be booked or claimed in one period while appearing in a later GSTR-2B.
- Credit and debit notes: the note may reduce or increase the eligible amount in a period different from the original invoice.
- Wrong GSTIN or place-of-supply data: a typographical error can send the document to another registration or change the tax head.
- Duplicate records: the purchase register, import data or a supplier amendment may have been loaded twice.
- Reverse-charge treatment: reverse-charge ITC is accounted for through its own process. GSTN’s April–June 2024 functionality compilation states that reverse-charge ITC in table 4A(3) was excluded from the DRC-01C comparison.
- Blocked or otherwise ineligible credit: a document can appear in GSTR-2B and still fail a legal condition or fall within a blocked-credit category.
- Reversal and reclaim: a credit reversed in an earlier return and reclaimed after conditions were met can create a timing difference if the working paper does not show both entries.
GSTN guidance also notes that information declared or amended through GSTR-1A becomes available to a recipient in the next tax period’s GSTR-2B. That timing can explain a difference without eliminating the need to test the underlying invoice and the section 16 conditions.
Classify every difference and quantify the action
After matching, assign each row one outcome. Do not answer an aggregate alert with an aggregate assertion when the underlying items have different causes.
| Classification | What it means | Typical response treatment |
|---|---|---|
| Eligible and supported | The document is genuine, supported by records and satisfies the applicable ITC conditions; the difference is explained by timing, amendment or another data issue. | List the document, explain the period difference and attach or retain the supporting reconciliation. |
| Supplier follow-up required | The document or amendment is missing, incorrect or reported under the wrong registration. | Request correction from the supplier, track the expected filing period and avoid claiming unsupported credit. |
| Correct in a later period | The accounting and portal records will align only after a valid later filing or amendment. | State the period and event that will resolve the item; do not describe a future correction as already completed. |
| Reverse, repay or correct | The claim is duplicated, unsupported, blocked or otherwise not eligible, or the amount was claimed in error. | Calculate the tax-head amount, interest or other amount required by the communication and preserve payment or return evidence. |
| Legal position needs explanation | The facts are documented but eligibility depends on interpreting a statutory condition or an allegation in a show-cause notice. | Set out the facts, provision relied on, computation and evidence; obtain qualified Indian GST review when the amount or issue is material. |
Reconcile totals after classification. The sum of eligible, timing, supplier-action and correction buckets should explain the portal difference, with separate treatment for each tax head. If it does not, investigate unmatched rows before filing.
How to respond to a DRC-01C intimation
The GST portal manual identifies a specific workflow and says the Part B response is mandatory. According to that manual, failure to respond prevents filing GSTR-1 or an Invoice Furnishing Facility (IFF) statement for the subsequent tax period.
- Sign in to the official GST portal using the registration concerned.
- Open Services > Returns > Return Compliance.
- Open the ITC Mismatch tile and select the relevant DRC-01C intimation.
- Review the period, comparison figures, tax heads and available response status against your downloaded records.
- Prepare the invoice-level reconciliation and determine the amount, if any, that must be paid or corrected.
- In Part B, enter payment details where an amount is accepted, provide an explanation where the difference is supported, or provide both when the facts require partial correction and partial explanation.
- Upload or reference the supporting workings in the format the current portal permits, verify the declaration and authorised signatory details, and submit using the prescribed electronic verification method.
- Download the acknowledgement and the filed Part B response. Confirm that the portal status changed from pending and store the acknowledgement with the working paper.
The portal manual does not establish one universal response period for every case in the material available here. Use the deadline printed on your own intimation and allow time for an authorised signatory, payment and portal errors. If the deadline is close, submit a factually complete response through the prescribed route rather than waiting for a perfect narrative.
How to answer a section 73 show-cause notice
A statutory notice requires a more formal answer than a DRC-01C Part B entry. Read every paragraph and build a reply that follows the notice’s numbering.
- Map the allegations: create a table with the notice paragraph, tax period, invoice or return table, disputed tax, interest and any penalty or other amount.
- Separate facts from law: state which documents were received, booked, reported, reversed or paid, then identify the legal condition the notice says was not met.
- Answer each item: explain timing and data errors with the reconciliation; contest an incorrect factual premise with source records; and accept only the amount that your review supports.
- Show the computation: reconcile tax heads and periods, explain any interest calculation and identify payments already made.
- Attach an indexed evidence set: include returns, statements, invoices, notes, receipt or service proof, ledger extracts, supplier correspondence and payment records that directly support the answer.
- Request the appropriate outcome: state which proposed amount should be dropped, which amount has been corrected or paid, and any hearing or procedural request available under the notice.
- File and preserve proof: use the channel and deadline stated in the notice, retain the submission acknowledgement and keep the final signed reply with the period file.
Section 73 concerns specified non-fraud cases, but the applicable limitation, procedure and amounts depend on the period, notice and law in force. A significant demand, a disputed statutory eligibility condition or a formal adjudication is a sensible point for review by a qualified Indian GST professional.
How to write the explanation so it can be checked
Use a short opening that identifies the registration, notice number, periods and the response being filed. Follow it with a reconciliation table rather than several pages of unstructured prose. For each category, state:
- the number of documents and tax amount;
- why GSTR-2B and GSTR-3B differ;
- the legal and accounting treatment applied;
- the supporting document index; and
- the exact correction, payment or future-period action, if any.
Do not claim that a supplier will amend a return until the amendment has actually appeared. Do not call an invoice eligible solely because it appears in GSTR-2B, and do not call it ineligible solely because it is absent from the statement without checking the period, reporting route and statutory conditions.
Decision guide: which route fits the problem?
| Situation | Communication | Immediate focus | Exposure or consequence |
|---|---|---|---|
| Aggregate difference flagged by the portal, with no adjudicated allegation | DRC-01C | Invoice-level reconciliation, then Part B explanation, payment, or both. | Part B is mandatory according to the portal manual; non-response blocks the subsequent period’s GSTR-1/IFF filing. |
| Alleged wrongly availed or utilised ITC with statutory reasoning and proposed demand | Section 73 show-cause notice | Paragraph-by-paragraph factual and legal reply with evidence and computation. | Proceeding, interest and other consequences depend on the notice, period and applicable law. |
| Difference caused by supplier amendment or delayed reporting | Either, depending on what was issued | Document the original and amended data, period movement and supplier follow-up. | Do not treat a pending future amendment as present proof; monitor the next statement and return. |
| Duplicate, blocked or unsupported credit | Either, depending on what was issued | Isolate the amount by tax head, reverse or pay where required and retain evidence. | Corrected amount and any applicable interest must match the communication and return records. |
Common mistakes and how to avoid them
- Using the wrong response path: a DRC-01C Part B entry is not a substitute for a full reply to a section 73 notice.
- Replying only with a total: an unexplained total does not show which invoices are eligible, delayed, duplicated or reversed.
- Assuming the portal is the law: GSTR-2B is a data statement; section 16 conditions and other restrictions still require self-assessment.
- Ignoring amendments and notes: compare original and amended document values and link every credit or debit note to its invoice.
- Mixing tax periods: preserve the statement for the period used when the return was filed and show any later-period appearance separately.
- Forgetting reverse-charge treatment: check the relevant return tables and the DRC-01C comparison scope; the 2024 GSTN functionality compilation states that table 4A(3) reverse-charge ITC was excluded from that comparison.
- Missing the filing consequence: a pending DRC-01C response can prevent the next GSTR-1 or IFF filing.
- Leaving no audit trail: save the submitted response, acknowledgement, payment challan or return reference, reconciliation version and supporting documents.
- Waiting until the final day: portal outages, electronic verification issues or an unavailable authorised signatory can consume the response window.
What the available guidance does not establish
The portal material describes the DRC-01C trigger as a “pre-defined limit,” but the numeric threshold is not stated in the official manual material considered here. Do not rely on an internet figure as a universal current threshold. The sources also do not establish one deadline that applies to every DRC-01C intimation or every show-cause notice; the communication itself controls.
No reliable official statistic establishes how often these notices are issued or how often taxpayers succeed with a particular response. Treat anecdotal percentages and success claims cautiously.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →When professional review is worthwhile
Consider qualified Indian GST advice when the disputed amount is significant, the records support a complex statutory eligibility position, several registrations or periods are involved, a section 73 notice has been issued, or the deadline leaves little time to test the legal analysis. Professional review should supplement—not replace—the invoice-level working paper and source records.
Record-retention checklist
- the original DRC-01C or show-cause notice and every attachment;
- portal history, delivery details and final acknowledgement;
- the period-specific GSTR-2B files and filed GSTR-3B returns;
- purchase register, invoices, debit notes, credit notes and amendments;
- goods-receipt or service evidence, payment records and ledger extracts;
- supplier requests, replies and evidence of later corrections;
- reversal, reclaim and interest workings; and
- payment challans, return references and the final signed response.
Keep the set together by registration and tax period so that a later officer, auditor or adviser can reproduce the figures used in the response.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
