GSTR-1 vs GSTR-3B Reconciliation Failure Modes: What DRC-01B Is Really Telling You

A DRC-01B intimation is not a compliance nuisance. It is the CBIC’s automated reading of a reconciliation function that failed. Every DRC-01B ever served on a bona fide Indian enterprise reads exactly the same on the common portal — the tax payable in GSTR-1 for a tax period exceeds the tax paid through GSTR-3B for the same period, by more than the Rule 88C threshold, and the registered person has seven days to either pay the differential through DRC-03 with interest under Section 50, or reply in Part B of DRC-01B explaining the difference. The controller’s team reads it as a portal alert. The controller reads it as a Severity-8 event on the reconciliation process design severity scale — the same tier as a CARO 2020 reportable observation, and a full statutory tier below the Section 39(9) amendment window lockout that would follow if the underlying difference is not repaired by 30 November of the following financial year.

This article catalogues the twelve failure modes across the twelve-class reconciliation process design taxonomy that produce every DRC-01B intimation on a well-run finance function. It walks the Section 39(9) amendment window and the Section 34 credit-note deadline as the two clocks the reconciliation must age every open exception against. And it closes on the point at which the monthly GSTR-1 versus GSTR-3B reconciliation stops being viable as a spreadsheet walk and requires a continuously-refreshed detection layer to survive the year-end GSTR-9C three-way reconciliation without a qualification.

Function definition — what a GSTR-1 versus GSTR-3B reconciliation is

The GSTR-1 versus GSTR-3B reconciliation is a monthly, GSTIN-level, tax-head-split match between two of the three self-filed returns every registered person under the CGST Act 2017 files each month. GSTR-1 — filed by the 11th of the month following the tax period for monthly filers, or through the Invoice Furnishing Facility for QRMP-scheme quarterly filers — is the statement of outward supplies. Every B2B invoice appears in Table 4; every B2C(Large) inter-state invoice above two lakh fifty thousand rupees appears in Table 5; every export appears in Table 6A; every SEZ supply appears in Table 6B; every deemed export appears in Table 6C; every credit or debit note appears in Table 9B; every amendment appears in Table 9A (amended B2B), Table 9B (amended credit/debit notes to registered recipients), or Table 9C (amended export invoices).

GSTR-3B — filed by the 20th of the same month for monthly filers — is the summary return where the aggregate outward tax liability is declared in Table 3.1, ITC is availed in Table 4, and the net tax payable is settled in Table 6.1. Table 3.1(a) is outward taxable supplies (other than zero-rated, nil-rated, or exempt); Table 3.1(b) is outward taxable supplies (zero-rated); Table 3.1(c) is other outward supplies (nil-rated and exempt); Table 3.1(d) is inward supplies liable to reverse charge; Table 3.1(e) is non-GST outward supplies. Table 6.2 populates the TDS and TCS credit received by the supplier — TDS at two percent under Section 51 from government-deductor customers (one percent CGST plus one percent SGST for intra-state supplies, or two percent IGST for inter-state supplies), and TCS at one percent under Section 52 from e-commerce operator platforms.

The reconciliation function’s job is to confirm that every taxable outward supply declared in GSTR-1 for a tax period appears in the corresponding GSTR-3B liability tables at the correct tax-head split, that every credit note in GSTR-1 reduces the GSTR-3B liability for the same period, and that Table 6.2 TDS/TCS credits reconcile to the GSTR-7A and GSTR-8A returns filed by every deductor and operator. The output is a defensible GSTR-3B liability figure that will not trigger a Rule 88C DRC-01B intimation, and a GSTR-1 declaration that will not surface as a three-way mismatch in the annual GSTR-9C reconciliation statement.

Why a mismatch generates a DRC-01B — the Rule 88C mechanics

Rule 88C, inserted into the CGST Rules by Notification 26/2022-Central Tax, defines the DRC-01B intimation trigger with three parameters. First, the tax payable in GSTR-1 for a tax period must exceed the tax paid through GSTR-3B for the same tax period. Second, the excess must cross both an absolute rupee threshold and a percentage threshold specified by the GST Council. Third, the intimation is auto-generated in Part A of Form GST DRC-01B on the common portal, and the registered person has seven days to reply.

Two responses are permitted. The first is payment of the differential through Form GST DRC-03 with interest at eighteen percent per annum under Section 50(1) from the date on which the tax became payable. The second is a reply in Part B of DRC-01B explaining the reason for the difference — a timing mismatch that will self-correct in the next return, a credit note reported after the source period, an amendment filed via Table 9A/9B/9C that reduced the current-period liability, or a genuine calculation error being repaired via a Section 39(9) amendment in the current-period GSTR-3B. If neither response lands within the window, recovery proceedings under Section 79 may follow, and the differential exposure hardens into a Section 73 assessment order (non-fraudulent, with penalty capped at ten percent of the tax involved or ten thousand rupees whichever is higher) or, if the CBIC establishes suppression or wilful misstatement, a Section 74 assessment (fraud, penalty up to one hundred percent of the tax involved). See the DRC-01B reconciliation reply guide for the response mechanics.

The DRC-01B intimation itself is a Severity-8 anchor on the reconciliation process design severity scale — CBIC has read the enterprise’s own filings and formed a view that the enterprise is short of its declared liability. The underlying failure mode carries its own Severity rating, which may be higher than 8 if the reconciliation exception cannot be repaired within the Section 39(9) window.

The twin clocks — Section 39(9) and Section 34

Every GSTR-1 versus GSTR-3B failure mode has to be aged against two statutory clocks.

Section 39(9) — the amendment window. A registered person who discovers an omission or incorrect particular in a filed GSTR-3B — outside of any scrutiny, audit, inspection, or enforcement activity — is permitted to rectify the error in the return for the month or quarter in which the omission is noticed, subject to payment of interest. No such rectification is permitted after the 30th day of November following the end of the financial year to which the details pertain, or the actual date of furnishing of the annual return, whichever is earlier. Every open GSTR-1 versus GSTR-3B exception on an FY 2025-26 invoice must therefore be either paid or amended by 30 November 2026 or the earlier GSTR-9 filing date. This is a Severity-10 anchor on the reconciliation process design severity scale — the same tier as a Section 16(4) input-tax-credit permanent loss on the input side.

Section 34 — the credit note window. A credit note issued by a supplier for a reduction in taxable value, a return of goods, or a deficiency in supply must be declared in the return for the month in which the credit note is issued, but not later than the 30th day of November following the end of the financial year in which the original supply was made, or the date of furnishing of the annual return, whichever is earlier. A credit note reported within this window reduces outward tax liability in GSTR-3B Table 3.1(a) matching the GSTR-1 credit note declaration; a credit note reported after this window cannot be adjusted, and the enterprise continues to bear the GST liability on the original invoice value while the customer takes the commercial credit.

Both clocks run on the same 30 November calendar day. A reconciliation function that walks every open exception through the days-to-30-November countdown against both clocks — and against the earlier annual return filing date if the enterprise files GSTR-9 before 30 November — is producing the aging discipline the reconciliation process design framework demands.

The framework — twelve failure classes, six causes, Severity-first Action Priority

The reconciliation process design framework Terra Insight applies across every stream uses three intersecting taxonomies to name what can go wrong on the GSTR-1 versus GSTR-3B stream.

Twelve failure classes. Data extraction / Classification / Completeness / Matching / Timing / Partner / Precision / Policy / Aging / Cutoff / Evidence / Portal. On this stream, Timing (period slip between GSTR-1 and GSTR-3B), Classification (LUT-versus-with-payment, IGST-versus-CGST-SGST, B2B-versus-B2C), Policy (Section 34 credit note timing, Section 51 TDS treatment), Completeness (e-invoice IRN generated but invoice omitted from GSTR-1), and Aging (unrepaired exceptions surviving into the Section 39(9) window) carry the highest concentration of High Action Priority failure modes.

Six causes — the 6P taxonomy. Every failure traces to People (a preparer or reviewer action), Policy (a rule the enterprise has or lacks), Process (a step in the reconciliation walk), Portal (a behaviour or gap on the GST portal or ICEGATE), Period (a cross-tax-period timing issue — dominant on this stream), or Partner (a customer or deductor action — uncommon on a self-reconciliation stream, but material for Table 6.2 TDS credit and B2B-to-B2C misclassification by a supplier’s counterparty).

Severity-first Action Priority. The framework does not multiply Severity by Occurrence by Detection into a Risk Priority Number, because a Severity-10 row with Low Occurrence and Low Detection can still cause a Section 39(9) permanent lockout on amendment and must be a High Action Priority. Severity is the dominant axis. A Severity-10 row is always High Action Priority regardless of Occurrence or Detection. A Severity-8 or 9 row is High if Occurrence is Medium or higher, or if Detection is Low. Below Severity 6, the rating rarely exceeds Medium unless the failure clusters into a systemic pattern.

The twelve failure modes

Each row carries the failure mode name, the class from the twelve-class taxonomy, the 6P cause, the effect with the specific Indian statute triggered, and Severity/Occurrence/Detection ratings on a 1-to-10 scale with Action Priority derived on a Severity-first basis.

The failure mode descriptions and their prevention and detection controls follow.

Failure mode 1 — Invoice reported in GSTR-1 in one month, GSTR-3B liability in another

Class. Timing. 6P cause. Period. Effect. The supplier reported an invoice in GSTR-1 for tax period X — the invoice date and the tax-period-of-reporting align on the outward-supply statement. In GSTR-3B for the same period X, the corresponding tax liability was not declared because the accounts team booked the liability in period Y based on the invoice-recognition rule the ERP applies. The Rule 88C mismatch surfaces on period X and the DRC-01B intimation follows within days of the GSTR-3B filing. Period Y will show an equal-and-opposite mismatch — GSTR-3B liability without a matching GSTR-1 declaration — which triggers a follow-on notice sequence. Section 50 interest accrues from the date the tax was payable on the original invoice date to the date of eventual settlement. Severity 8 — DRC-01B intimation tier. Occurrence 8 — the single most common failure on this stream in a monthly close where the ERP invoice-date logic and the GSTR-1 filing logic run on different cutoffs. Detection 5 — visible on a pre-filing GSTR-1 versus GSTR-3B comparison if the walk is set up. Prevention control. ERP-level enforcement that the GSTR-1 tax-period-of-reporting matches the GSTR-3B liability period for every invoice; a written cutoff calendar aligning the invoice-book close to the GSTR-1 filing date; a Section 39(9) amendment plan for any exception surfacing after the fact. Detection control. A pre-filing GSTR-1 versus GSTR-3B match at the tax-head split level, run between the GSTR-1 filing date (11th) and the GSTR-3B filing date (20th), so any period-slip is caught before the return lands.

Failure mode 2 — Export invoice classified as LUT in one return, with-payment in another

Class. Classification. 6P cause. Policy. Effect. The supplier is registered under a Letter of Undertaking and typically exports without payment of IGST. The GSTR-1 Table 6A declaration correctly shows the LUT classification with zero IGST. In GSTR-3B, the same invoice value flows into Table 3.1(b) — zero-rated outward supplies — but the IGST amount is populated because the accounts team, working from the ERP tax code that defaults to with-payment for export lines, did not override the tax field to zero. The reconciliation fails at the tax-amount line — the invoice value matches, but the tax head does not. Rule 88C compares the tax payable side. In addition, if the enterprise attempts an automatic refund claim on the shipping bill data flowing from ICEGATE, the refund route is corrupted because the GSTR-1 declaration says LUT (no tax paid, no refund) while the GSTR-3B says with-payment (tax paid, refund claimable). Severity 8 — DRC-01B exposure plus refund-claim disruption. Occurrence 6. Detection 6 — visible on the pre-filing tax-head match. Prevention control. An export classification master keyed to the shipping bill and the LUT/with-payment declaration, gating the ERP tax code at PO-and-invoice creation. Detection control. A pre-filing GSTR-1 Table 6A versus GSTR-3B Table 3.1(b) match with zero-tax-versus-tax-paid validation.

Failure mode 3 — Credit note issued but not reported within the Section 34 window

Class. Timing. 6P cause. Policy / Period. Effect. A commercial credit note is issued to a customer against an FY 2025-26 supply — a rate revision, a quantity dispute, a quality claim, or a rebate against volume commitments. The customer takes the credit against the receivable. The finance team, treating the credit note as a book adjustment, does not push it through GSTR-1 Table 9B (for credit notes to registered recipients) in the same or a subsequent tax period, and does not reduce the outward liability in GSTR-3B Table 3.1(a). By 30 November 2026, the Section 34 window has closed. The credit note cannot be reported in any GSTR-1 or GSTR-3B for FY 2025-26 or subsequent years. The enterprise has borne the commercial cost of the credit but continues to owe the government the GST on the original invoice value. Severity 10 — permanent inability to reduce outward liability. Occurrence 5 — moderate, concentrated on year-end rebates and quality-claim reversals booked in April or May of the following FY. Detection 5 — visible on the credit note register versus GSTR-1 walk if the register is maintained. Prevention control. A credit note register that captures every commercial credit note the moment it is issued, with the mandatory GSTR-1 tax period tagged to it. Detection control. A monthly credit note register versus GSTR-1 Table 9B walk, with a days-to-30-November countdown per open row from May of the following FY onward.

Failure mode 4 — Amendment filed after the Section 39(9) window

Class. Timing. 6P cause. Period. Effect. A reconciliation exception surfaced in October 2026 on an FY 2025-26 invoice — a wrong tax-head split, a missed credit note, an export mis-classification. The correct repair path is an amendment through GSTR-1 Table 9A (for B2B invoice corrections), Table 9B (for credit/debit note corrections to registered recipients), or Table 9C (for export invoice corrections), together with a Section 39(9) rectification in the current-period GSTR-3B. If the amendment is filed on 5 December 2026 — after the 30 November deadline — the CBIC portal will accept the filing but the amendment carries no effect on the FY 2025-26 liability. The DRC-01B differential from the original period hardens into a Section 73 assessment order (or Section 74 if suppression is alleged), and the enterprise’s only remaining path is a payment through DRC-03. Severity 10 — permanent lockout. Occurrence 4 — infrequent but reliably clusters in December of the following FY when the year-end close reveals exceptions that were not tracked against the November calendar. Detection 5. Prevention control. A quarterly reconciliation exception review starting from July of the following FY, with mandatory days-to-30-November aging on every open exception. Detection control. An amendment queue with a hard cutoff at 15 November of the following FY — every open exception must have an amendment filing plan by that date, with escalation to the CFO for any exception without a plan.

Failure mode 5 — Section 51 TDS credit mis-treated in Table 6.2

Class. Classification. 6P cause. Policy / People. Effect. A government-deductor customer — a state government department, a PSU, or a specified agency — deducts TDS at two percent on a supply contract exceeding two lakh fifty thousand rupees under Section 51 of the CGST Act. The deduction is reflected in the supplier’s electronic cash ledger via GSTR-7A and auto-populates in Table 6.2 of GSTR-3B as TDS/TCS credit received. The supplier’s finance team, working from the customer’s payment advice, sometimes double-claims the credit — once through the auto-populated Table 6.2 flow, and once through a manual adjustment on the belief that the auto-populated amount is a portal glitch. Alternatively, the credit is missed entirely when the supplier’s own reconciliation stops at the customer-payment-received event without walking through to the government portal. Severity 7 — cash-ledger over-credit or under-credit exposure. Occurrence 6 — moderate. Detection 5. Prevention control. A written policy that Table 6.2 is the sole source of Section 51 TDS credit — no manual adjustments permitted. Detection control. A monthly walk of Table 6.2 auto-population against the customer-side payment advice and the corresponding GSTR-7A entries.

Failure mode 6 — Place of supply misclassified between IGST and CGST+SGST

Class. Classification. 6P cause. Policy / People. Effect. A supply to a customer in a different state should attract IGST under Section 5 of the IGST Act, but the supplier’s team classifies it as an intra-state supply under Section 9 of the CGST Act, charging CGST plus SGST. The GSTR-1 declaration and the GSTR-3B liability both reflect the wrong tax-head split. When the customer’s own reconciliation flags the discrepancy — the customer needs IGST to claim ITC in their state, not CGST+SGST from a state where they are not registered — the supplier must file an amendment through Table 9A. If the amendment is filed within the Section 39(9) window, the tax-head split is corrected without additional liability (the total tax paid remains the same). Outside the window, the CGST+SGST becomes a wrong-head payment and the correct IGST is a fresh liability with interest under Section 50. Severity 8. Occurrence 6. Detection 4 — the classification is invisible until the customer flags the mismatch or the GSTR-1 amendment queue is walked. Prevention control. A place-of-supply master keyed to the customer’s state and validated against the shipping address at PO creation. Detection control. A monthly place-of-supply exception report on every B2B invoice, with cross-state supplies flagged for IGST review.

Failure mode 7 — Advance received in one month with invoice raised in another

Class. Timing. 6P cause. Cutoff. Effect. A customer advance is received in March 2026 against a supply that will be invoiced in April 2026. Under the CGST Act framework as amended, advances against supply of services attract GST at the time of receipt (Section 13(2)), while advances against supply of goods are exempt from GST on receipt with the tax point at invoice date (post-Notification 66/2017-Central Tax). If the advance is against services and the finance team fails to declare the tax in GSTR-1 Table 11 (advances received) for March 2026 and in GSTR-3B Table 3.1(a) for the same period, a Rule 88C differential surfaces in April when the invoice is raised and the corresponding liability is declared in GSTR-3B against nothing in GSTR-1 for April (the advance already covered the invoice). Severity 6. Occurrence 7. Detection 5. Prevention control. An advance register keyed to the supply-of-services versus supply-of-goods distinction, with the applicable GST-on-advance rule tagged. Detection control. A monthly Table 11 GSTR-1 walk against the advance register.

Failure mode 8 — RCM inward reported in Table 3.1(d) but ITC never availed

Class. Completeness. 6P cause. Process. Effect. A reverse-charge inward supply — legal services from an advocate, sponsorship services, goods transport agency service — is correctly declared in Table 3.1(d) of GSTR-3B with tax paid through the electronic cash ledger. The corresponding ITC is claimable in Table 4(A) of the same GSTR-3B, but the finance team, working from a Table 3.1(d) checklist without a paired Table 4(A) entry, misses the availment. The GST is paid, but the offsetting ITC is not taken. Severity 7 — effective tax cost with no compensating credit. Occurrence 6. Detection 6. Prevention control. A paired-entry template where every Table 3.1(d) RCM entry auto-generates the corresponding Table 4(A) availment row for review. Detection control. A monthly Table 3.1(d)-to-Table 4(A) walk.

Failure mode 9 — E-invoice IRN generated but invoice omitted from GSTR-1

Class. Completeness. 6P cause. Process / Portal. Effect. For every enterprise whose aggregate turnover in any preceding financial year from FY 2017-18 onwards has exceeded five crore rupees, e-invoicing is mandatory. Every B2B invoice must be reported to the Invoice Registration Portal (IRP) at issue time, an Invoice Reference Number (IRN) is generated, and the invoice data is transmitted to the GST portal to auto-populate GSTR-1. Where the auto-population does not fire — because of an IRN-generation cutoff crossing, an IRP-to-portal integration lag, or a manual invoice cancellation not synced — the invoice can be reported to the IRP and still be missing from GSTR-1 for the period. The GSTR-3B liability is booked from the ERP-side sales register, so the tax is declared and paid, but GSTR-1 shows a lower outward supply value. On its own this produces a reverse-direction mismatch (GSTR-3B higher than GSTR-1) which does not trigger Rule 88C, but the recipient of the invoice does not see it in their GSTR-2B and loses ITC, and the GSTR-9C three-way reconciliation surfaces the mismatch at year-end. Section 122(1) penalty exposure applies to the recipient’s ITC denial. Severity 9 — recipient’s Section 16(4) permanent-loss exposure attaches. Occurrence 5. Detection 5. Prevention control. A daily IRN log versus GSTR-1 pending-list walk. Detection control. A monthly e-invoice audit — every IRN generated in the period must appear in GSTR-1 for the period or the immediately following period. See the IMS reconciliation guide for the mirror-side IMS action layer that catches this failure on the recipient’s side.

Failure mode 10 — B2B invoice mis-reported as B2C in GSTR-1

Class. Classification. 6P cause. People. Effect. A B2B invoice for supply to a registered recipient — with the recipient’s GSTIN captured on the tax invoice and communicated to the ERP — is reported in GSTR-1 as a B2C supply because the recipient GSTIN field was blank on the GSTR-1 line item or the sales register did not tag the transaction as B2B. Table 4 (B2B) of GSTR-1 shows a lower value than the sales register; Table 7 (B2C others) shows a higher value. The recipient does not receive the ITC through their GSTR-2B — because a B2C declaration by the supplier does not populate the recipient’s GSTR-2B — and the recipient loses the credit permanently under Section 16(4) if not repaired by the amendment window. From the supplier’s perspective the GSTR-1 versus GSTR-3B reconciliation may match at the aggregate level (total outward supply is the same), so Rule 88C does not fire, but the failure surfaces later as a customer escalation or as a GSTR-9C recipient reconciliation exception. Severity 9 — recipient permanent-loss exposure attaches. Occurrence 6. Detection 5. Prevention control. An ERP validation gate that requires a recipient GSTIN on every B2B tax invoice and blocks B2C classification for any customer flagged as GST-registered in the customer master. Detection control. A monthly B2B versus B2C classification audit against the customer master.

Failure mode 11 — Ineligible ITC under Section 17(5) not reversed in Table 4(B)

Class. Policy. 6P cause. Policy. Effect. The enterprise availed ITC in Table 4(A) on inputs that fall within the Section 17(5) blocked-credit list — motor vehicle repair not used for the specified taxable outward supplies, outdoor catering, works contract on immovable property. The correct treatment is a reversal in Table 4(B), leaving the net ITC in Table 4(C) at the eligible amount. When the reversal is missed, the excess ITC availed produces a Rule 88D DRC-01C intimation on the ITC side (mirroring the DRC-01B on the liability side), and a Section 74 recovery risk if the ITC was utilised to discharge outward tax liability. Severity 8. Occurrence 6. Detection 5. Prevention control. A Section 17(5) blocked-credit master keyed to HSN/SAC and payment description. Detection control. A monthly Table 4(B) walk against the Section 17(5) master.

Failure mode 12 — Reconciliation not run at all before GSTR-3B filing

Class. Aging. 6P cause. Process. Effect. The finance team files GSTR-1 on the 11th of the month, files GSTR-3B on the 20th, and never runs a comparison between the two. When Rule 88C thresholds are crossed, the DRC-01B intimation lands on the portal within days of the GSTR-3B filing. The seven-day reply window opens with no pre-existing reconciliation working paper to draw from, and the reply must be constructed from scratch under time pressure. The pre-filing opportunity to repair the mismatch through a Section 39(9) rectification in the current GSTR-3B — which would have avoided the DRC-01B altogether — is lost. Severity 8. Occurrence 7. Detection 9 — detection is trivially high because the failure is the absence of a control. Prevention control. A written monthly close SOP that requires a GSTR-1 versus GSTR-3B walk between the 11th and the 20th of every month, with sign-off before the GSTR-3B filing. Detection control. The reconciliation itself — running it is the control.

The Section 39(9) amendment discipline — Table 9A, Table 9B, Table 9C

Every failure mode above that is discovered after GSTR-3B filing but before the Section 39(9) window closes on 30 November of the following FY has three amendment paths in GSTR-1.

Table 9A — amended B2B invoices. For any B2B invoice previously reported in Table 4 that requires correction to invoice value, tax amount, tax-head split (IGST vs CGST+SGST), place of supply, or recipient GSTIN. The amendment is filed in the GSTR-1 for the tax period in which the correction is noticed. Revenue-neutral amendments (tax-head correction with the same total tax) do not attract additional liability; revenue-impact amendments (invoice value increase) attract additional tax with interest under Section 50 from the original invoice date.

Table 9B — amended credit and debit notes to registered recipients. For any CDNR previously reported that requires correction to value or tax amount. The Section 34 credit-note deadline still governs the timing — an amended credit note cannot extend the effective reduction beyond 30 November of the following FY on the original supply’s financial year.

Table 9C — amended export invoices. For any export invoice previously reported in Table 6A that requires correction to invoice value, LUT-versus-with-payment classification, IGST amount, or shipping bill data.

Every amendment path also requires a corresponding Section 39(9) rectification in the current GSTR-3B to reflect the tax-liability adjustment. The two amendments — GSTR-1 amendment table plus GSTR-3B rectification — must land in the same tax period to close the loop and prevent a residual Rule 88C mismatch.

The reconciliation process design framework’s discipline is that every open exception is aged against the 30 November cutoff from July of the following FY onward, escalated to the CFO at 15 November, and closed to zero by 30 November. The reconciliation control plan template documents the control layer for this discipline.

The Table 6.2 TDS/TCS credit reconciliation

Table 6.2 of GSTR-3B is the least-walked table in the monthly close, and it is the source of a distinct class of reconciliation exception. The table auto-populates from GSTR-7A (filed by every government deductor under Section 51) and GSTR-8A (filed by every e-commerce operator under Section 52), and the credit lands in the supplier’s electronic cash ledger — usable to discharge tax liability but not usable as ITC.

The reconciliation surface has three requirements. First, the Table 6.2 auto-populated amount must match the supplier’s own record of Section 51 TDS deducted by every government-deductor customer, sourced from the customer’s payment advice. Second, the auto-populated amount must match the deductor’s own GSTR-7A filing — a delay or mismatch in the deductor’s filing produces an under-credit that must be followed up. Third, the credit consumed to discharge tax liability must be recorded correctly so that the cash ledger balance is not double-counted.

Failure to run this walk produces a working-capital drag (unavailed cash-ledger credit) or a compliance exposure (over-claimed credit against a deductor’s non-filing).

When manual reconciliation outgrows itself

The GSTR-1 versus GSTR-3B reconciliation is one of the reconciliation streams a well-run manual finance function can sustain for longer than the GSTR-2B stream, because both inputs are self-generated returns rather than portal-sourced counterparty data. A mid-market enterprise with a single GSTIN, a monthly filing cadence, fewer than 500 outward invoices per month, and no cross-border complexity can run the reconciliation as a spreadsheet walk between the 11th and the 20th of every month — a Table-3.1-and-Table-6.2 comparison, a Table 9A/9B/9C amendment queue, and a Section 34 credit note register — reviewed by the tax manager, signed off by the controller.

The reconciliation stops being viable as a spreadsheet walk at three inflection points. The first is multi-GSTIN complexity — an enterprise with more than three GSTINs runs three separate GSTR-1-versus-GSTR-3B walks, and the reviewer capacity required to walk each in parallel exceeds what a single tax manager can sustain during the 11th-to-20th window. The second is the annual reconciliation compression — the Section 39(9) 30 November deadline, the Section 34 credit-note deadline, and the Section 16(4) ITC time bar all fall on the same day, and the September-October-November window compresses every open exception across every reconciliation stream into the same review capacity. The third is the DRC-01B response window — a seven-day reply window on a Rule 88C intimation cannot be reliably met when the reconciliation has to be rebuilt from scratch because no working paper existed before the intimation landed.

Above these inflection points, the GSTR-1 versus GSTR-3B reconciliation must become a continuously-refreshed detection layer — populated automatically from the ERP sales register, the IRP e-invoice log, the GSTR-1 filing, the GSTR-3B filing, and the GSTR-7A/GSTR-8A downloads — with a Rule 88C mismatch simulator running before every GSTR-3B filing, an amendment queue with days-to-30-November aging, and a Section 34 credit note register linked to the customer master. This is the point at which GST reconciliation software becomes the layer that carries the discipline, and reconciliation software India is the broader authority for every other stream’s reconciliation on the same cadence.

Cross-cluster bridges and where to read next

The pillar for the entire cluster is the reconciliation process design pillar. For the input-side twin of this article, read the GSTR-2B ITC reconciliation failure modes analysis where the Rule 88D DRC-01C intimation and the Section 16(4) permanent loss anchor the ITC-side discipline. For the receivable-side TDS twin, read the TDS reconciliation failure modes against Form 26AS and Form 168 analysis. For the sibling failure-mode analyses being shipped alongside this one, read the invoice-to-bank reconciliation failure modes analysis and the anchored Severity, Occurrence, Detection scale for Indian reconciliation method article. For the ops-layer counterpart on the monthly close, read the reconciliation playbook — monthly close pillar; the GSTR-1 versus GSTR-3B runbook that pairs with this failure-mode analysis is a forward addition to the Playbook cluster. For the DRC-01B response mechanics, read the DRC-01B reconciliation reply guide; for the DRC-01C ITC-side counterpart, read the DRC-01C ITC mismatch reply guide. The annual accumulation surface is documented in the GSTR-9C three-way mismatch reconciliation walkthrough. The commercial pillar for the GSTR-1 versus GSTR-3B surface is GST reconciliation software; the broader authority sits at reconciliation software India; and the statutory-audit anchor is documented in the statutory audit reconciliation checklist.

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 4 August 2026

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