What’s new

Global e-Invoicing

e-Invoicing compliance Timeline

Know More →

Global e-Invoicing

UAE e-Invoicing: The Complete Guide to Compliance and Future Readiness

Read More →

Cygnet Vendor Postbox

Types of Vendor Verification and When to Use Them

Read More →

Cygnet Vendor Postbox

Safeguard Your Business with Vendor Validation before Onboarding

Read More →

Cygnet BridgeFlow

Modernizing Dealer/Distributor & Customer Onboarding with BridgeFlow

Read More →

Cygnet BridgeFlow

Accelerate Vendor Onboarding with BridgeFlow

Read More →

Cygnet Bills

GST Filing 360°: GST, E-Invoicing, E-Way Bills & Annual Returns Made Simple

Read More →

Cygnet Bills

Why Manual Tax Determination Fails for High-Volume, Multi-Country Transactions

Read More →

Cygnet IRP

GST Filing 360°: GST, E-Invoicing, E-Way Bills & Annual Returns Made Simple

Read More →

Cygnet IRP

Key Features of an Invoice Management System Every Business Should Know

Read More →

Cygnature

Automating the Shipping Bill & Bill of Entry Invoice Operations for a Leading Construction Company

Read More →

Cygnature

From Manual to Massive: How Enterprises Are Automating Invoice Signing at Scale

Know More →

What’s new

Data Analytics & AI

AI-Powered Voice Assistant for Smarter Search Experiences

Explore More →

Data Analytics & AI

Cygnet.One’s GenAI Ideation Workshop

Know More →

Digital Engineering

Our Journey to CMMI Level 5 Appraisal for Development and Service Model

Read More →

Digital Engineering

Extend your team with vetted talent for cloud, data, and product work

Explore More →

Quality Engineering

Enterprise Application Testing Services: What to Expect

Read More →

Quality Engineering

Future-Proof Your Enterprise with AI-First Quality Engineering

Read More →

Cloud Engineering

Cloud Modernization Enabled HDFC to Cut Storage Costs & Recovery Time

Know More →

Cloud Engineering

Cloud-Native Scalability & Release Agility for a Leading AMC

Know More →

Managed IT Services

AWS workload optimization & cost management for sustainable growth

Know More →

Managed IT Services

Cloud Cost Optimization Strategies for 2026: Best Practices to Follow

Read More →

Amazon Web Services

Cygnet.One’s GenAI Ideation Workshop

Explore More →

Amazon Web Services

Practical Approaches to Migration with AWS: A Cygnet.One Guide

Know More →

Cygnet TaxAssurance

Tax Governance Frameworks for Enterprises

Read More →

Cygnet TaxAssurance

Cygnet Launches TaxAssurance: A Step Towards Certainty in Tax Management

Read More →

Cygnet TaxAssurance

10 Generative AI Use Cases Driving Enterprise Value

Read More →

Cygnet TaxAssurance

Navigating the Generative AI Landscape

Read More →

Cygnet TaxAssurance

Truly Rise with SAP: The Business Integrators Guide

Read More →

Cygnet TaxAssurance

Mastering SAP S/4HANA Migration: Essential Pre-Migration Strategies and Preparation

Read More →

GST Guide

GST Mismatch Reason Codes: Building an Exception-Management Workflow

Explore GST mismatch reason codes for GSTR-2B, GSTR-1 and GSTR-3B reconciliation, exception ownership, automation, resolution, and audit tracking.
By Kesha Shah November 18, 2026 7 minutes read

A month-end review meeting. Someone puts up a sheet with 3,200 mismatched lines. The comments column says things like “supplier issue”, “check”, “timing?” and “wrong GSTIN maybe”. Two people read the same comment two ways. Nobody can say how many of those lines put credit at risk, and next month the same suppliers are back on the list.

Finding a GST mismatch is the easy part. Tools do it in minutes. The problem here is that each one is described in free text, and thus there is nothing that can be quantified or tracked back to its root cause. That’s where a reason code comes into play. The reason code is a short, standardized label on each exception indicating the reason for the exception. When all lines are tagged with reason codes, the list becomes a workflow. This post covers how to set that up, and it works as one of your core GST compliance controls.

Data Sources for GST Mismatch Reason Codes

A code only makes sense if you know which two datasets disagreed, so tag every GST reconciliation mismatch with the comparison it came from. Establishing consistent IMS-driven reconciliation controls can also help finance teams maintain accuracy when comparing information across multiple records and identifying discrepancies. The usual comparisons include:

  • Purchase register against GSTR-2B. This is where a GSTR-2B mismatch comes up.
  • Sales register against GSTR-1 and e-invoice data.
  • GSTR-1 against GSTR-3B, the classic GSTR-1 3B mismatch on output liability.
  • Credit available in GSTR-2B against credit claimed in GSTR-3B.
  • GST ledgers in the books against what has been filed in the return.

When there are multiple registrations, include GSTIN and period in every entry, and time-stamp every data extract. A mismatch that you cannot replicate next week cannot be justified either.

Matching Keys Across Data Sources

Select the keys once and commit them to writing. In purchases, use supplier GSTIN, invoice number, invoice date and document type. In sales, use IRN for e-invoiced documents and invoice number and date for everything else. Taxable value and tax by head can be compared only after matching the keys. An invoice-level GST reconciliation approach helps finance teams identify discrepancies at the individual document level rather than relying solely on aggregated differences. Normalize invoice numbers first (prefixes, slashes, zeroes) because these can generate more mismatches than one might expect.

Exact matches, partial matches and timing differences

Exact matches need no code. Partial matches and timing differences are where codes start paying for themselves. A partial match has the key right and the values off, or a near-identical key. Make the time discrepancy brief: if it still exists when the next period arrives, it gets moved to another code with another owner. Otherwise “time” is the dumping ground for all the discrepancies.

Data-quality checks before matching begins

Check the raw data before you match it. Look for invalid GSTIN formats, duplicate invoice numbers, missing dates, wrong document types and cancelled documents still in the register. Failures here get their own codes with the data source team as owner, so they are not blamed on suppliers.

Mismatch Classification and Ownership

Keep the list of code short. A dozen or so is simpler to use than forty, because with forty people choose whatever comes first. Each code needs one meaning, one default owner, one default action and one priority. The codes below are examples to adapt, not a standard.

CodeMeaningDefault ownerPriority
SUP-NRPurchase invoice in books, not in GSTR-2BAccounts payableHigh: affects credit
VAL-DIFFValue or tax differs on a matched invoiceAccounts payableHigh: affects credit
TIM-01Same document, different periodGST teamMedium, with expiry
OUT-NRSale in books, missing or different in GSTR-1 or e-invoice dataBilling / sales opsHigh: affects liability
LIAB-3BGSTR-1 and GSTR-3B liability differTax teamHigh: affects liability
MST-ERRWrong GSTIN, state code or document type in master dataMaster data teamMedium
DQ-DUPDuplicate or cancelled document in the registerSource system ownerLow to medium

For priority, put the codes that touch credit claimed or tax payable in the open return first, then sort by value and age. Owners should be named people with a due date tied to the return calendar, not a team mailbox.

Exception Resolution Workflow

  1. Detect the exception when the matching run finishes.
  2. Assign a code. where the pattern is clear GST automation can do this automatically where the pattern is clear, and a person does the rest of the job.
  3. Route them to the default owner with a due date.
  4. Owner takes the action like correcting the entry, following up with the supplier, mark a timing item, or referring a judgement call to the tax head.
  5. A second person verifies the fix before the item closes
  6. Close the item with root cause tags to be able to identify the suppliers, units or processes which are repeatedly producing GST reconciliation discrepancy.

Two rules hold this together. Uncoded items should be zero before the filing review starts. And Close the item with root cause tags to be able to identify the suppliers, units or processes which are repeatedly producing GST reconciliation discrepancy.

Automating Reconciliation

Reason codes are easy to design and hard to run by hand across many GSTINs. Automation helps with the repetitive work: scheduled data pulls, normalising and matching, applying coding rules, assigning owners, sending reminders and producing ageing views by code, owner and GSTIN. It also makes supplier follow-up lists much quicker to produce. Businesses can use GST compliance software to streamline these activities, maintain visibility into reconciliation exceptions and support more consistent GST compliance processes.

Judgment must remain within your team. The question of whether you should go after a supplier, accept the difference, or take advice regarding a questionable account cannot be resolved through a policy statement. Good tooling hands your team clean, coded exceptions so their time goes there.

Audit and Filing Evidence

In respect of each GSTIN and period, retain the date-time-stamped data extracts, the exception log with codes, owners, resolution dates and resolution details, the history of modifications of the list of codes and matching logic, approvals, supplier communication regarding material invoices and a summary linking the reconciliation process to the return filing. Retain such documentation for the period mandated by law and ascertain the same from your legal advisor. In case of an audit request or inquiry related to any invoice, the response must be one click away.

Conclusion

A GST mismatch should not become a recurring month-end headache. When every exception has a clear reason code, an assigned owner and a defined resolution path, finance teams can move beyond simply identifying discrepancies to understanding why they happen. Over time, this makes reconciliation more predictable, reduces repeated supplier follow-ups and helps protect eligible ITC and tax reporting accuracy. The real value of a reason-code-based workflow is not just closing the current month’s exceptions. It is ensuring the same issues do not keep appearing in the next filing cycle.

FAQ's

Invoices that have not been reported by suppliers or have been reported late, data entry errors in invoice numbers or dates, incorrect GSTIN numbers, discrepancies in amounts or tax rates, document-type errors and period-mismatched differences

Group mismatched items according to the cause and ownership of the mismatch, not the reports to which they pertain. Begin with supplier mismatches, value mismatches, timing mismatches, outward reporting mismatches, liability mismatches, master data errors, and data quality problems. Only add a coding for those mismatches which require a different ownership and/or action.

Any mismatch which affects the credit taken or taxes due on the open return such as missing purchase invoices, value mismatches and outward reporting mismatches.

Assign by cause. Supplier gaps go to accounts payable, billing errors to sales operations, master data errors to the master data owner. Each item gets one named person and a due date linked to the return calendar.

Exceptions by code, credit at risk by code, ageing by owner, repeat suppliers, the share auto-coded, the share cleared before filing and uncoded items. Falling repeat counts show you are fixing causes.

Author
Kesha Shah Linkedin
Kesha Shah
General Manager - Products Marketing

Kesha Kumar leads the global products marketing team at Cygnet.One, where she turns the complexity of tax and finance transformation into stories that resonate with the people who matter most. She’s the strategic force behind the brand’s presence across India, the GCC, Southeast Asia, and Europe, translating dense subjects like e-Invoicing mandates, digital engineering, and enterprise AI into narratives that inform and drive action. With expertise spanning tax and finance transformation, quality, enterprise applications, and data and AI, Kesha blends sharp strategic thinking with a marketer’s instinct for what truly connects. At Cygnet.One, she does more than build campaigns and content; she shapes the conversations that help enterprises navigate compliance with clarity and confidence, propelling the brand to the forefront of the industry along the way.