Skip to main content
GST Reconciliation · ITC Verification

GST Reconciliation Software for High-Volume Indian Businesses

Rule 36(4) ended provisional ITC in 2022. Today, every rupee of Input Tax Credit you claim in GSTR-3B must be supported by an entry in your GSTR-2B — auto-populated on the GST portal from your suppliers' GSTR-1 filings. Unreconciled ITC is not a timing difference — it is a tax liability, recoverable with interest at 18% per annum, and one of the most common forms of revenue leakage in Indian enterprise finance. Estimate your exposure with the free ITC Leakage Calculator. Manual reconciliation using spreadsheets fails at enterprise scale because it matches on a single field, produces an undifferentiated exception list, and leaves blocked credits, period mismatches, and supplier defaults unclassified. GSTR-1 and 3B outward filing reconciliation leads the TransactIG GST roadmap. GSTR-2B inward matching, the IMS workflow, and DRC-01B/01C tied ITC responses are on the roadmap — the sections below describe both the outward capability that is shipping and the inward capability that is planned.

Capability status

Live today: bank-to-books reconciliation with an evidence trail, and TDS reconciliation. Leading the roadmap: GSTR-1 and GSTR-3B outward filing reconciliation (sales-side, output tax, HSN turnover, payment ledger).
On the roadmap: GSTR-2B inward matching, the Invoice Management System (IMS) accept/reject/pending workflow, DRC-01B and DRC-01C tied ITC responses, Section 17(5) blocked-credit exclusion, and Section 52 TCS reconciliation against the electronic cash ledger. The sections below describe both surfaces — the inward-side content documents Indian GST regime mechanics and the planned TransactIG capability set, not a shipped feature. No specific rollout window for the inward capability is currently published.

Rule 36(4)
ITC restricted to GSTR-2B
6 mismatch types
On the roadmap
2–4 weeks
Outward-side implementation
GSTR-1 + 3B live
GSTR-2B on the roadmap

Why GST ITC Reconciliation Is Now Mandatory

When GST was introduced in 2017, businesses could claim provisional ITC on invoices not yet reflected in the government's system — up to 20% initially, later reduced to 10%, and then to 5% of GSTR-2B-eligible credit. This buffer was eliminated with effect from 1 January 2022. Since then, Rule 36(4) — as notified by the Central Board of Indirect Taxes and Customs (CBIC) — permits ITC claims only on invoices that appear in GSTR-2B. There is no provisional credit, no grace period, and no self-assessment latitude on the ITC amount beyond what the portal reflects.

GSTR-2B is generated monthly between the 12th and 14th of each month, capturing all supplier GSTR-1 filings up to the 11th. Any supplier who files their GSTR-1 after the 11th will not appear in the current month's GSTR-2B — they will appear in the following month's statement. For enterprises with large supplier bases, this creates a systematic lag: invoices received and recorded in the purchase register in month N will not generate ITC until month N+1 if the supplier is a late filer. Identifying and quantifying this lag before filing GSTR-3B is only possible through a structured reconciliation of the purchase register against GSTR-2B.

The consequences of not reconciling are cumulative. Each month's unresolved ITC mismatch carries forward to GSTR-3B as either an overclaim (ITC claimed without GSTR-2B support — triggers demand) or an underclaim (ITC available in GSTR-2B but not captured — forfeits working capital). By the time the GSTR-9 annual return is due, the cumulative difference between Table 8A (ITC as per GSTR-2A/2B) and Table 8C (ITC claimed in GSTR-3B) must be reconciled and, where unexplained, attracts scrutiny from the GST department. Businesses that have maintained a disciplined monthly reconciliation produce this reconciliation in hours; those that have not face a year-end reconstruction exercise spanning 12 months of purchase data. GSTR-9 auditors typically follow the guidance issued by the Institute of Chartered Accountants of India (ICAI) on annual return reconciliation working papers.

Beyond ITC verification, GST reconciliation also surfaces supplier compliance risk. A supplier who consistently fails to file GSTR-1 on time is creating a recurring ITC shortfall for every business they supply. Identifying these suppliers through reconciliation data allows procurement and finance teams to take commercial action — amending payment terms, requiring advance filing confirmation, or switching suppliers — rather than absorbing the ITC loss silently.

For a detailed walkthrough of the GSTR-2B download process and ITC matching methodology, see the GSTR-2B reconciliation guide. For the broader context of reconciliation infrastructure across Indian enterprise finance, see reconciliation software India.

The GSTR-2B Reconciliation Roadmap

The inward-side capability set on the roadmap — six planned functional modules covering the full scope of GST ITC verification, from supplier filing status to annual GSTR-9 reconciliation. Terra Insight's the GST roadmap leads with GSTR-1 and 3B outward-filing reconciliation; the inward modules below follow.

01

GSTR-2B vs purchase register matching at invoice level (on the roadmap)

The planned GSTR-2B reconciliation module — matching is being built — will ingest the GSTR-2B statement from the GST portal and the purchase register export from the ERP, and match at invoice level — not at period aggregate — using GSTIN, invoice number, invoice date, and tax value as matching signals. Entries that do not match exactly will go to an exception queue for review before classification. GSTR-1 and 3B outward-filing reconciliation leads the GST roadmap; the inward-side matching described here follows it.

02

Supplier GSTIN validation and GSTR-1 filing status check (on the roadmap)

The planned inward-side workflow will validate each supplier GSTIN in the purchase register against the GST portal to confirm the GSTIN is active and the supplier has filed their GSTR-1 for the relevant period. Invoices from non-filers would be immediately flagged as SUPPLIER_NOT_FILED rather than passed to the match engine, which prevents false positives. This validation loop is on the roadmap.

03

Section 17(5) blocked credit identification and exclusion (on the roadmap)

A configurable blocked credit ruleset — planned for the GSTR-2B reconciliation module on the roadmap — will cover all categories specified under Section 17(5): motor vehicles, personal consumption goods, food and beverages, outdoor catering, club and health centre memberships, and works contract services for immovable property. Invoices matching these categories would be excluded from ITC claims automatically and routed to the BLOCKED_CREDIT queue for documentation. This ruleset is forthcoming.

04

TCS (Section 52) and GST TDS (Section 51) classification (on the roadmap)

Marketplace sellers receive TCS deductions at 1% from e-commerce operators under Section 52. Government entity vendors face GST TDS at 2% on payments exceeding ₹2.5 lakh under Section 51. The planned GST-side TCS/TDS loop on the roadmap will process settlement sidecar files from marketplace operators and purchase order data from government clients to match TCS and TDS credits appearing in the GST cash ledger against expected amounts. The upstream marketplace-settlement reconciliation itself is a delivered TransactIG capability.

05

ITC carry-forward tracking across periods (on the roadmap)

When a PERIOD_MISMATCH means ITC must be claimed in a different month than the invoice date, the planned inward-side module will track the carry-forward balance across periods. This would ensure ITC is not double-claimed, not abandoned, and is claimed in the earliest eligible period — which is relevant for working capital planning and for the GSTR-9 annual reconciliation. Carry-forward tracking is on the roadmap alongside the broader GSTR-2B capability.

06

GSTR-9 annual reconciliation support (on the roadmap)

The GSTR-9 annual return requires reconciling cumulative ITC claimed in monthly GSTR-3B filings against the ITC available in GSTR-2A/2B across the full year. Differences must be declared in Table 8. The planned GSTR-9 reconciliation summary — generated from monthly match data by the inward-side module on the roadmap — would eliminate the need to reconstruct the full year's reconciliation from spreadsheets at year-end. This annual-summary output is forthcoming.

GST Mismatch Types: Classification and ITC Impact

The six-way classification below is the standard Indian GST-practice structure for GSTR-2B mismatches. On the roadmap, the planned inward-side module will assign a structured mismatch code to every unmatched entry so unmatched entries are not treated as a homogeneous pending list. Documented here as domain reference; the automated typing engine is forthcoming.

Mismatch Type Cause ITC Impact Resolution
SUPPLIER_NOT_FILED Supplier hasn't filed GSTR-1 No ITC claimable Follow up; reverse if unresolved by September
AMOUNT_MISMATCH Invoice amount differs between your records and GSTR-2B Partial ITC only Raise credit/debit note or debit supplier
GSTIN_MISMATCH Supplier used wrong GSTIN in their return ITC wrongly credited Supplier correction return required
PERIOD_MISMATCH Invoice in different GSTR-2B month than expected ITC in wrong period Claim in correct period; track carry-forward
BLOCKED_CREDIT Invoice is for blocked supply under Section 17(5) No ITC claimable Classify and exclude; do not reverse if already excluded
CANCELLED_INVOICE Supplier cancelled invoice post-GSTR-2B auto-population ITC must be reversed Reverse in next filing; add interest at 18%

Structured variance codes for GST inward exceptions are on the roadmap. TransactIG's live variance taxonomy today covers TDS, GSTR-1/3B outward, NACH, bank, and platform-settlement domains. See variance taxonomy for the full classification schema.

How the Planned GSTR-2B Reconciliation Would Work

Three steps from GSTR-2B download to a structured exception queue, before the 20th of each month — the planned inward-side workflow on the roadmap. Live GSTR-1 and 3B outward reconciliation ships today on the same underlying engine.

01

Download GSTR-2B (on the roadmap)

The planned inward-side module will ingest GSTR-2B data either through automated portal extract or manual JSON/Excel upload from the GST portal. Multi-GSTIN entities would upload once per registered entity. GSTR-2B data would be parsed, structured, and indexed by supplier GSTIN, invoice number, and tax period — ready for matching. This ingestion is forthcoming.

02

Match against purchase register from ERP (on the roadmap)

The purchase register would be exported from SAP, Oracle NetSuite, Tally Prime, Zoho Books, Busy Accounting, or Microsoft Dynamics using a pre-configured connector. The matching engine would match GSTR-2B entries to purchase register entries using GSTIN, invoice number, date, and tax value — with configurable tolerance on amounts for rounding differences. Blocked credit invoices would be identified and excluded before the match. This matching leg is planned.

03

Exception queue with mismatch classification (on the roadmap)

Every unmatched entry would receive a structured mismatch code: SUPPLIER_NOT_FILED, AMOUNT_MISMATCH, GSTIN_MISMATCH, PERIOD_MISMATCH, BLOCKED_CREDIT, or CANCELLED_INVOICE. The planned exception queue would show ITC impact per entry, recommended resolution action, and responsible party. Every resolution action would be logged with timestamp and user identity for audit. This queue is forthcoming; audit trails on the live outward-side reconciliation are already delivered.

GST Reconciliation by Industry

The complexity of GST ITC reconciliation varies by industry. Different sectors face different mismatch patterns, apportionment requirements, and TCS/TDS obligations.

Retail and E-commerce

Marketplace sellers operating on Amazon, Flipkart, or Meesho receive TCS deductions at 1% of net value under Section 52 on each settlement. Reconciling TCS credits in the GST cash ledger against settlement statements from multiple platforms, while simultaneously matching supplier invoices in GSTR-2B for inbound goods, creates a two-track reconciliation requirement that manual processes routinely conflate. The upstream marketplace-settlement leg is a delivered TransactIG capability today; the GST-side GSTR-2B and TCS-ledger loop that closes the second track is on the roadmap. See the full coverage for retail and e-commerce reconciliation .

IT Services — Export Invoices and LUT

IT services companies exporting services under a Letter of Undertaking (LUT) raise zero-rated invoices. While no GST is charged on export invoices, ITC on input services used to provide those exports is claimable as a refund under Rule 89. Reconciling input credit on domestic purchases against export turnover, and apportioning ITC between taxable and exempt supplies under Rule 42/43 for the refund application, are inward-side workflows on the roadmap alongside the broader GSTR-2B capability.

Manufacturing — Input Credit on Capital Goods

Capital goods GST credit is available across two years under Section 16 — 50% in the year of acquisition and 50% in the following year. Tracking capital goods ITC separately from revenue ITC, scheduling the second-year credit claim, and matching the asset register entry and GSTR-2B entry for capital invoices for the GSTR-9C audit reconciliation, are workflows on the roadmap alongside the inward-side capability.

Healthcare — Exempt Supplies and Partial ITC

Hospitals and diagnostic centres provide both exempt services (patient care) and taxable services (pharmacy, diagnostics for non-patients). Under Rule 42, ITC on common inputs must be apportioned between taxable and exempt activities. Applying the apportionment formula at the cost-centre level, identifying blocked credits on healthcare-specific expenditure, and preparing the Rule 42 working for GSTR-3B and GSTR-9 are inward-side workflows on the roadmap.

For marketplace sellers and aggregator platforms, see how platform settlement reconciliation handles the intersection of GST TCS, payout timing, and commission deductions in a single workflow.

Manual GST Reconciliation vs the Planned TransactIG GSTR-2B Module

The comparison below sets manual spreadsheet reconciliation against the inward-side capability set on the roadmap. It illustrates the difference the planned module is designed to make — structure of the output and reliability of the ITC position before each GSTR-3B filing — not a shipped feature today.

Dimension Manual / Spreadsheet TransactIG
Matching approach VLOOKUP on invoice number or GSTIN; single-field match only On the roadmap: matching on GSTIN, invoice number, date, and tax value. The 51% to 88% match rate figure is validated on bank-to-books matching, not on inward-GST
Mismatch classification Unmatched entries listed in a single "pending" tab with no classification On the roadmap: six structured mismatch types (SUPPLIER_NOT_FILED, AMOUNT_MISMATCH, GSTIN_MISMATCH, PERIOD_MISMATCH, BLOCKED_CREDIT, CANCELLED_INVOICE)
Blocked credit handling Manual line-by-line review against Section 17(5) list; prone to omission On the roadmap: configurable blocked credit ruleset applied before matching; automatic exclusion from ITC claims
ITC carry-forward tracking Tracked in a separate spreadsheet; reconciliation between months is manual On the roadmap: carry-forward balance tracked within the system across periods; included in the planned GSTR-9 summary
Audit trail Version history in spreadsheet only; no record of who approved each adjustment On the roadmap for the inward-side workflow: every match, override, and write-off logged with timestamp and user identity; exportable for GST audit. Audit trails ship with the outward-side reconciliation, which leads the roadmap; delivered

TransactIG is certified ISO 27001:2022. All reconciliation data is processed and stored in a cloud-only environment. The GST roadmap leads with GSTR-1 and 3B outward-filing reconciliation; GSTR-2B inward matching and the IMS workflow are on the roadmap. For the full delivered capability overview and ERP integration list, see the product page.

What is GST Reconciliation Software

GST reconciliation software is a purpose-built system that automates the comparison between the purchase register, GSTR-2B (auto-populated from the GST portal), and GSTR-3B (the monthly return) to ensure that every Input Tax Credit claimed is accurate, supported by a corresponding GSTR-2B entry, and compliant with Rule 36(4). This category of software ingests data from an ERP and the GST portal, matches invoices at the GSTIN, invoice number, date, and tax value level, and classifies every mismatch into a defined category — SUPPLIER_NOT_FILED, AMOUNT_MISMATCH, GSTIN_MISMATCH, PERIOD_MISMATCH, BLOCKED_CREDIT, or CANCELLED_INVOICE. In the TransactIG product surface, GST reconciliation is shipping today for the GSTR-1 and 3B outward side; the GSTR-2B inward reconciliation described above is on the roadmap.

Unlike manual VLOOKUP-based reconciliation, GST reconciliation software handles the full complexity of the Indian GST regime: multi-GSTIN entities where a single company may have 10 or more state-level registrations, reverse charge mechanism (RCM) transactions that must be self-assessed, Section 17(5) blocked credits that must be excluded before ITC is calculated, and credit notes that require reversal tracking across periods. The output is a structured exception queue — not a raw list of unmatched rows — with each item classified by mismatch type and linked to a resolution workflow.

For businesses processing 500 or more purchase invoices per month across multiple GSTINs, GST reconciliation software eliminates the 2 to 4 days per month that finance teams spend on manual GSTR-2B comparison and converts the reconciliation process from a monthly spreadsheet exercise into a systematic workflow with a documented audit trail.

Invoice Management System and GST Reconciliation

The Invoice Management System (IMS), live on the GST portal since October 2024, introduces an additional reconciliation layer between GSTR-1 (filed by your supplier) and GSTR-2B (auto-populated for your entity). Before IMS, every invoice filed by a supplier in their GSTR-1 automatically flowed into the recipient's GSTR-2B. IMS changes this by giving the recipient three choices for each inward invoice: Accept, Reject, or leave as Pending.

Accepted invoices flow into GSTR-2B and are available for ITC. Rejected invoices are excluded from GSTR-2B and flagged back to the supplier for correction. Pending invoices are subject to deemed acceptance — if no action is taken before the GSTR-2B generation date (typically the 14th of each month), they are treated as accepted and included in GSTR-2B automatically. This deemed acceptance mechanism means that incorrect invoices left unreviewed in IMS will generate ITC that may later need to be reversed with interest.

For GST reconciliation software, IMS creates a two-level reconciliation requirement. First, the purchase register must be reconciled against IMS action status — ensuring that every invoice your business intends to claim has been explicitly accepted, and every invoice that should be rejected (incorrect amounts, wrong GSTIN, duplicate filings) has been rejected before the deemed acceptance window closes. Second, the accepted invoices in IMS must be reconciled against the resulting GSTR-2B to confirm that the ITC available matches the ITC your business plans to claim in GSTR-3B.

For detailed coverage of IMS reconciliation workflows, see the IMS reconciliation guide and the IMS vs GSTR-2B comparison.

Benefits of Automated GST Reconciliation (Planned Outcomes)

The value of automated GST reconciliation — the four outcomes below — is what the inward-side module on the roadmap is designed to deliver. It is not limited to time savings: it protects working capital, prevents penalty exposure, and supports compliance readiness at every filing cycle. The outcomes are stated for the planned capability; the shipped GST reconciliation today covers the GSTR-1 and 3B outward-filing side.

ITC recovered and protected

Manual reconciliation routinely misses ITC that is available but not claimed — invoices appearing in GSTR-2B in a different period than expected, invoices with minor amount differences that are within tolerance, and credit notes that reduce rather than eliminate ITC. Automated reconciliation identifies every claimable rupee of ITC across periods and ensures Section 16(4) deadlines are tracked so that ITC is claimed before the time bar expires (30th November of the following financial year, or the date of filing the annual return, whichever is earlier).

Interest and penalty avoidance

ITC claimed without GSTR-2B support triggers interest at 18% per annum under Section 50 of the CGST Act. Where the department determines the claim was wilful, the rate increases to 24%. DRC-01C notices — issued when the GST system detects a difference between ITC claimed in GSTR-3B and ITC available in GSTR-2B — require a response within 7 days. Failure to respond within this window results in automatic liability confirmation. Automated reconciliation ensures that GSTR-3B is filed with only GSTR-2B-supported ITC, eliminating the primary trigger for DRC-01C notices.

GSTR-9C three-way mismatch prevention

The GSTR-9C annual reconciliation statement requires a three-way comparison between the audited financial statements, GSTR-9 annual return data, and the monthly GSTR-3B filings. Differences between these three sources must be declared and explained. Businesses that reconcile GST monthly using automated software carry forward zero cumulative reconciliation debt into the annual return — the GSTR-9C preparation reduces to a verification exercise rather than a 2-week reconstruction effort from 12 months of spreadsheets.

DRC-01C response readiness

The DRC-01C intimation notice is generated automatically by the GST portal when the system detects a difference between ITC claimed in GSTR-3B and ITC reflected in GSTR-2B for any tax period. The taxpayer must either pay the differential amount or explain the difference within 7 days. With automated reconciliation, every ITC claim in GSTR-3B is already supported by GSTR-2B data, and the reconciliation evidence is available immediately for DRC-01C response preparation — no retrospective reconstruction required.

Key Features to Evaluate in GST Reconciliation Software

When evaluating GST reconciliation software for your organisation, these are the functional capabilities that differentiate a purpose-built solution from a basic comparison tool. Each feature should be verified during vendor evaluation — including with TransactIG.

GSTR-2B auto-download and scheduled ingestion

The software should download GSTR-2B data from the GST portal automatically on a scheduled cycle — immediately after GSTR-2B is generated on the 14th of each month. Manual portal downloads create a bottleneck and delay the start of reconciliation. Verify whether the solution uses API access to the GST portal or requires manual CSV upload.

Multi-GSTIN support for group entities

Businesses operating across multiple states carry separate GSTINs for each registration. A reconciliation solution must handle 10, 20, or 50 GSTINs within a single dashboard — with consolidated reporting across all registrations and entity-level drill-down. Ask how many GSTINs the platform supports and whether pricing is per-GSTIN or per-entity.

Tolerance matching for amount variances

Invoice amounts in the purchase register and GSTR-2B frequently differ by small amounts due to rounding, tax calculation at line-item versus invoice level, or minor data entry differences. Configurable tolerance bands — such as ₹1 for rounding, 0.5% for tax computation differences — prevent these from appearing as false exceptions. Verify that tolerances are configurable per mismatch type, not a single global setting.

Supplier compliance scoring

A supplier who consistently files GSTR-1 late or files with errors creates recurring ITC risk. Supplier compliance scoring tracks each supplier's filing history, error rate, and correction frequency — giving procurement and finance teams a risk-based view of the supplier base. This is particularly relevant for large supplier bases (100+ active suppliers) where individual follow-up is not scalable.

ERP integration: Tally, SAP, Oracle, Zoho

The purchase register export from your ERP is the primary data source for GST reconciliation. Verify native support for your specific ERP — Tally Prime, SAP S/4HANA, Oracle NetSuite, Zoho Books, Busy Accounting, or Microsoft Dynamics. The integration should support scheduled exports, not manual file uploads, and should handle field mapping configuration without code changes.

RCM handling and credit note reconciliation

Reverse Charge Mechanism (RCM) transactions under Section 9(3) and 9(4) require the recipient to self-assess and pay GST, then claim ITC on the self-assessed amount. Credit notes issued by suppliers reduce ITC and must be tracked across periods. Both RCM and credit notes require specialised handling that basic comparison tools do not provide. Verify that the software identifies RCM liability, tracks self-assessment compliance, and reconciles credit notes against the original invoices across periods.

Frequently Asked Questions

What is GST reconciliation software?
GST reconciliation software is a tool that automatically matches the invoices appearing in your GSTR-2B (auto-populated from your suppliers' GSTR-1 filings on the GST portal) against the corresponding entries in your purchase register or ERP. The purpose is to verify that every Input Tax Credit (ITC) you intend to claim has a corresponding entry in GSTR-2B before you file your GSTR-3B return. Since Rule 36(4) came into effect in 2022, provisional ITC — the 5% buffer that previously allowed claims beyond GSTR-2B — has been eliminated entirely. Every rupee of ITC you claim must now be supported by a GSTR-2B entry. GST reconciliation software enforces this requirement at invoice level, identifies the type of mismatch for each unmatched entry, and gives your finance team a structured exception queue to resolve before the 20th of each month.
What is GSTR-2B reconciliation?
GSTR-2B is a read-only, auto-generated statement on the GST portal that is populated each month from your suppliers' GSTR-1 and GSTR-1A filings. It shows, for each of your GSTINs, which supplier invoices are available for ITC in that period. GSTR-2B reconciliation is the process of comparing this portal-generated statement against your own purchase register — verifying that each invoice you have recorded in your books also appears in GSTR-2B at the correct GSTIN, amount, and tax period. Under Rule 36(4), ITC can only be claimed on invoices reflected in GSTR-2B. If a supplier has not filed their GSTR-1, or filed it with errors, the invoice will not appear in your GSTR-2B and the corresponding ITC cannot be claimed — even if the physical invoice is in your possession and the payment has been made.
What happens if ITC is claimed without GSTR-2B support?
Claiming ITC not reflected in GSTR-2B is treated as an erroneous or excess ITC claim under the GST Act. When the GST department's system reconciles your GSTR-3B (where ITC is claimed) against the GSTR-2B available for your GSTIN, the unmatched portion will trigger a demand notice under Section 73 or Section 74. You will be required to reverse the ITC, pay the tax liability equivalent, and pay interest at 18% per annum on the amount from the date of the original filing. Where the department determines the claim was wilful, the interest rate increases to 24% per annum and penalty provisions apply. Unreconciled ITC also surfaces during the GSTR-9 annual return, where the cumulative difference between ITC claimed in GSTR-3B and ITC reflected in GSTR-2A/2B across the year must be declared and defended.
What is TransactIG live for on the GST side today, and what is on the roadmap?
GSTR-1 and GSTR-3B outward filing reconciliation — the sales and payment sides of the GST surface — leads the TransactIG GST roadmap, covering the GST return, including HSN-wise turnover, output tax, and payment ledger positions. GSTR-2B inward reconciliation, the Invoice Management System (IMS) workflow, DRC-01B and DRC-01C tied ITC responses, ITC mismatch typing, blocked-credit exclusion under Section 17(5), and TCS reconciliation against the electronic cash ledger are on the roadmap. The educational content on this page — Rule 36(4), the six-way GSTR-2B mismatch structure, Section 17(5), Section 52 TCS, DRC-01C mechanics — describes the Indian GST regime and the standard reconciliation exercise, not a delivered TransactIG capability. Where the page refers to what "TransactIG will match" or "the planned GSTR-2B module classifies", that language is deliberately future-tense: the inward-side capability set is planned, not shipped.
How would the six GSTR-2B mismatch types be classified once the inward capability ships?
The classification structure planned for the GSTR-2B reconciliation module on the roadmap follows the six categories that Indian GST practice already recognises. SUPPLIER_NOT_FILED: the supplier has not filed their GSTR-1 for the period, so the invoice does not appear in your GSTR-2B at all — no ITC is claimable until they file. AMOUNT_MISMATCH: the invoice amount or tax value in your purchase register differs from what the supplier reported in their GSTR-1 — only the amount in GSTR-2B is eligible for ITC. GSTIN_MISMATCH: the supplier quoted an incorrect GSTIN in their return, causing the ITC credit to appear against the wrong entity. PERIOD_MISMATCH: the invoice appears in a different month's GSTR-2B than expected, which means ITC must be claimed in that specific period and tracked across carry-forwards. BLOCKED_CREDIT: the invoice falls under Section 17(5) of the GST Act — vehicles, personal-use goods, food, club memberships, and other specified categories — and no ITC is available regardless of GSTR-2B appearance. CANCELLED_INVOICE: the supplier cancelled the invoice after GSTR-2B was auto-populated, requiring mandatory ITC reversal with interest. The classification is documented here as domain reference; the automated typing engine for it is on the roadmap.
How would TCS from e-commerce operators be handled once the inward capability ships?
Under Section 52 of the GST Act, e-commerce operators are required to collect Tax Collected at Source (TCS) at 1% of the net value of taxable supplies made through their platform. This amount is deducted from the settlement payout to the seller and deposited directly with the GST department, appearing as a credit in the seller's GST electronic cash ledger rather than as ITC in their electronic credit ledger. TCS reconciliation is on the roadmap alongside the broader GSTR-2B inward capability — the planned workflow will ingest the settlement sidecar files provided by each marketplace, aggregate them across platforms such as Amazon, Flipkart, and Meesho, and match them against the corresponding TCS credits reflected in the GST portal cash ledger. Today, marketplace-settlement reconciliation itself (payout timing, commission deductions, refunds) is a delivered TransactIG capability via the platform-settlement surface — see the payment-gateway and marketplace-settlement pages. What is forthcoming is the GST-side loop that closes the settlement TCS against the cash ledger credit.
How long does the live GST reconciliation implementation take, and what is the roadmap window for GSTR-2B?
Once the GSTR-1 and 3B outward-filing reconciliation ships (it leads the GST roadmap), implementation is 2 to 4 weeks with no code development required. The implementation process has three stages. In week one, your ERP connection is configured — TransactIG supports SAP, Oracle NetSuite, Tally Prime, Zoho Books, Busy Accounting, and Microsoft Dynamics — and the sales register and payment ledger fields are mapped to the reconciliation schema. In week two, GSTIN configuration is completed for all entities in your GST registration. In weeks three and four, a parallel run is conducted on the prior month's data to validate match rates and tune tolerance rules. After sign-off, the outward-side reconciliation is live for the current month's GSTR-1 and 3B cycle. The GSTR-2B inward-side capability is on the roadmap and would extend the same implementation pattern; no specific window is currently published for the inward-side rollout.
ISO 27001:2022 Certified · Cloud-only · No code development

Ship the GSTR-1 and 3B outward-filing reconciliation now; join the roadmap for GSTR-2B

The live GSTR-1 and 3B outward-filing reconciliation is shipping today on the same underlying engine that would carry the planned GSTR-2B inward matching, mismatch classification, and IMS workflow. Request a demo to see the live capability and discuss the inward-side roadmap.

Live-capability implementation in 2–4 weeks. Integrates with SAP, Oracle NetSuite, Tally Prime, Zoho Books, Busy Accounting, and Microsoft Dynamics.