23 Sept 2026 · ECOMCA Team
GSTR-2B Reconciliation Tools Compared: Excel vs Tally vs Outsourced
A D2C brand buying from 40 vendors across 3 states will generate somewhere between 300 and 600 purchase invoices a month. Every one of those has to show up correctly in GSTR-2B before the input tax credit against it is safe to claim. Miss that check even once, and the ITC claimed in the GSTR-3B return can be reversed later with interest. The question most finance teams eventually ask is not whether to reconcile GSTR-2B, but how — by hand in Excel, inside Tally, or by handing it to someone else on a retainer.
This post lays out what each option actually costs in time, error risk and scale, using a working example a founder can adapt to their own numbers.
Key takeaways
- GSTR-2B is a static, auto-generated statement reflecting supplier-filed invoices, made available to a taxpayer on GSTN typically around the 14th of the month following the tax period.
- Under clause (aa) of sub-section (2) of Section 16 of the CGST Act, 2017, input tax credit can be claimed only to the extent the invoice is reflected in the recipient's GSTR-2B, subject to the other conditions of Section 16 being met.
- Manual Excel reconciliation works up to roughly 100-150 invoices a month per GSTIN before error rates and time cost start rising sharply.
- Tally (or any accounting software with a GST reconciliation module) automates the matching logic but still needs a person to chase vendors for missing or wrongly reported invoices.
- Outsourced or retainer-based reconciliation scales across multiple GSTINs and states without a proportional rise in internal headcount, which is the main reason larger multi-channel sellers move to it.
What GSTR-2B actually contains, and why the reconciliation matters
GSTR-2B pulls together the invoices, debit notes and other documents that a taxpayer's suppliers have reported in their own outward supply returns (GSTR-1, GSTR-5, GSTR-6) up to the cut-off date for that period. Because it is static - it does not change once generated for a period, unlike the older GSTR-2A which kept updating - it gives a fixed base to reconcile against the purchase register for that month.
The gap between what a business has actually purchased and what shows up in GSTR-2B usually comes from three sources: the vendor hasn't filed their GSTR-1 yet, the vendor filed it with the wrong GSTIN or a wrong invoice number, or the vendor classified the supply under the wrong rate. On the GST rate side, this has mattered more since 22 September 2025, when the GST Council's rate rationalisation took effect and the 12% and 28% slabs were withdrawn in favour of a 0% / 5% / 18% / 40% structure. A vendor still invoicing at an old rate, or misreporting the new one, will throw up a mismatch that a reconciliation exercise should catch before the ITC is claimed.
Whatever method is used, the exercise is the same: match purchase register lines to GSTR-2B lines on GSTIN, invoice number, invoice date, taxable value and tax amount, then flag and chase what doesn't match.
Manual Excel reconciliation
This is where almost every small seller starts, and for good reason - it costs nothing beyond the time spent, and a competent accountant can build a working VLOOKUP or Power Query-based match sheet in an afternoon. It is also the method behind most of the searches for a "gstr 2b reconciliation tool free download" - sellers looking for a ready-made template rather than building one from scratch.
The limitation is not the logic, it is the volume. Once a business crosses two or three GSTINs, or a vendor base large enough that invoice numbers start repeating or getting entered with trailing spaces and inconsistent formats, Excel-based matching produces a lot of false mismatches that then need manual eyeballing. A finance manager doing this alongside marketplace payout reconciliation, monthly closing and GSTR-1/3B filing tends to push GSTR-2B matching to whatever week is left, which is exactly when errors creep in.
Excel also has no memory. Every month starts from a blank sheet unless someone maintains a running vendor master and history separately, and that maintenance itself is unpaid work that rarely gets budgeted for.
Tally and accounting-software-based reconciliation
Tally Prime and similar accounting platforms with a GST reconciliation module import the GSTR-2B JSON or Excel download directly from the GST portal and match it against the purchase vouchers already recorded in the books. This removes the manual matching step and the formatting inconsistencies that plague spreadsheets, because both sides are structured data.
What Tally does not remove is the follow-up. If a vendor hasn't filed, or filed with an error, the software will correctly flag the mismatch, but someone still has to write to the vendor, get the correction made in their next GSTR-1, and re-check the next month's GSTR-2B to confirm it landed. For a seller with a stable, small vendor base this is manageable inside the existing accounts team. For a seller onboarding new suppliers every quarter, expanding to new states, or dealing with a large number of small vendors who are themselves inconsistent filers, the follow-up volume becomes a job in itself, separate from the software.
There is also a practical ceiling on multi-GSTIN consolidation. Each GSTIN reconciles separately in the software; combining the picture across states into one dashboard for the finance head or the board still needs manual work outside Tally unless a separate MIS layer is built on top.
Outsourced or retainer-based reconciliation
This is where a firm or a dedicated team runs the reconciliation as a standing monthly process: pulling GSTR-2B for every GSTIN the business holds, matching it against the purchase register, chasing vendors on a template that has already been refined over many clients, and reporting back a clean mismatch list with an ageing view — which invoices have been outstanding for one month, two months, three.
The advantage over Excel and Tally is not that the underlying matching logic is different. It is the same logic. The advantage is that it does not depend on one person's bandwidth inside the business, and it scales horizontally: adding a fourth GSTIN or a hundred more vendors is a matter of the retainer team absorbing more volume, not the founder hiring another person in-house and training them on the process. For a business running multiple GSTINs across marketplace and D2C channels — a fairly common structure for sellers operating on Amazon, Flipkart and their own Shopify store simultaneously — this consolidation across states into one monthly view is usually the deciding factor.
The trade-off is cost. A retainer is a recurring cash outflow rather than a one-time software purchase or an internal person's existing salary. Whether that cost is justified depends entirely on volume and on what the founder's own time is worth spent elsewhere.
Comparing the three methods
| Factor | Manual Excel | Tally / accounting software | Outsourced / retainer |
|---|---|---|---|
| Upfront cost | Nil to low | Software licence cost | Recurring monthly fee |
| Time cost per month (150-300 invoices, single GSTIN) | High, rises sharply with volume | Moderate, matching is automated but follow-up is manual | Low for the internal team; absorbed by the service provider |
| Error rate at scale | Rises with invoice count and formatting inconsistency | Lower, structured data matching | Lowest, process is repeated across many clients and refined |
| Multi-GSTIN consolidation | Manual, separate sheet per GSTIN | Separate per GSTIN inside the software | Consolidated reporting typically included |
| Vendor follow-up | Done by whoever built the sheet | Done by internal accounts team | Done by the retainer team as part of the service |
| Best suited to | Very small sellers, under roughly 100 invoices/month, single GSTIN | Established in-house finance team with stable vendor base | Multi-channel or multi-state sellers, growing vendor count, limited internal bandwidth |
Table: comparative view of GSTR-2B reconciliation approaches. Time and error figures are illustrative, based on typical ecommerce vendor volumes as on 23 September 2026, and will vary by business.
A worked example
Consider a seller with ₹8 crore annual turnover, registered in 3 states, buying from 45 active vendors, generating around 220 purchase invoices a month combined. In Excel, matching this volume reliably, including chasing 15-20 mismatches a month across 3 vendor-facing emails and follow-ups, realistically takes a finance person 10-14 hours a month once formatting cleanup and re-checks are counted. In Tally, the matching itself drops to 2-3 hours, but the follow-up on 15-20 flagged mismatches, plus consolidating 3 separate GSTIN reports into one view for the founder, still takes 6-8 hours. Under a retainer arrangement, the internal time cost drops to reviewing a summary report, typically under an hour a month, with the matching, follow-up and consolidation done outside.
Whether that time saving is worth the retainer fee depends on what the finance person's hour is otherwise spent on — closing the books, managing marketplace payout reconciliation, or handling GST notices, all of which tend to matter more as the business grows.
What to actually do
A seller under roughly 100 invoices a month on a single GSTIN can reasonably continue with a well-built Excel template, provided someone owns the vendor master and actually runs it every month rather than deferring it. A seller with an established Tally setup and a stable vendor base should use the software's own reconciliation module rather than exporting data back into Excel, since that removes a layer of manual error. A seller running multiple GSTINs, onboarding vendors frequently, or finding that GSTR-2B mismatches are getting flagged in departmental notices should treat monthly reconciliation as a process that needs to run reliably regardless of who is available internally that week, which is the case a retainer model is built to solve.
Where this is unsettled
There is no dispute in law about the requirement itself — Section 16(2)(aa) of the CGST Act, 2017 is settled and has been in force since 1 January 2022. What remains a matter of practice rather than law is how far back a business should go chasing old mismatches once a vendor's non-filing is discovered late; different practitioners take different views on whether to reverse and reclaim ITC immediately on discovery or wait for the vendor's correction in a later GSTR-1, and departmental officers have not been fully consistent on this point across jurisdictions.
Frequently asked questions
Is there a free GSTR-2B reconciliation tool available? The GST portal itself provides a downloadable GSTR-2B in Excel and JSON format, and several free templates exist for matching it against a purchase register. These work adequately at low invoice volumes but need manual upkeep of the vendor master and do not scale well once invoice count or GSTIN count rises.
How often should GSTR-2B reconciliation be done? Monthly, aligned with the GSTR-3B filing cycle, since ITC eligibility for a period is generally assessed against the GSTR-2B available for that period. Waiting till year-end to reconcile makes vendor follow-up far harder, since old invoices are less likely to get corrected in the supplier's returns.
What happens if ITC is claimed but the invoice never appears in GSTR-2B? Under Section 16(2)(aa) of the CGST Act, 2017, credit not reflected in GSTR-2B is not eligible to be claimed, and if claimed, it is liable to be reversed along with applicable interest once identified, whether by the taxpayer or by the department.
Does the reconciliation method matter for a GST audit or notice response? The department cares about the outcome — accurate ITC claimed on eligible invoices — not the method used to get there. A documented, monthly reconciliation trail, whichever tool produced it, is what supports a response to a mismatch notice.
Can Tally alone handle reconciliation across multiple GSTINs? Tally reconciles GSTR-2B against purchase vouchers per GSTIN. Consolidating multiple GSTINs into a single view for management reporting needs either a manual layer on top or a separate MIS process, since the software does not merge GSTINs automatically.
This post is for general information and does not constitute professional advice. It reflects the position of law as on 23 September 2026 and may not account for subsequent amendments, notifications or judicial developments. Tax and regulatory outcomes depend on the specific facts of each case. Readers should obtain advice appropriate to their own circumstances before acting on anything stated here.