BUSY can reconcile GSTR-2A and GSTR-2B on its own. Two settings decide whether auto-download works at all

BUSY, from Busy Infotech, says it serves 6,00,000+ businesses, and its own FAQ pages document a genuinely usable reconciliation setup — GST Misc. Utilities, a JSON download, a red/blue match screen. Almost nothing outside BUSY's own docs explains it. This is that walkthrough, plus the step it skips over and the question it never answers.

What BUSY's own FAQ documents, and why almost nothing else does

BUSY, from Busy Infotech, says it serves 6,00,000+ businesses (busy.in), and it markets GSTR reconciliation as a built-in feature — matching purchase invoices against GSTR-2B, detecting value and tax mismatches, reconciling by party, GSTIN and invoice, and running a side-by-side GSTR-2A vs GSTR-2B comparison to spot delayed supplier filings (busy.in/accounting-software/gstr-reconciliation/). What that marketing page doesn't cover is how you actually turn it on; the clearest step-by-step lives in BUSY's own FAQ pages — primarily answerid-48415, with a near-identical walkthrough also documented under a QRMP-switching FAQ, answerid-29907 — and, as of September 2026, we couldn't find an independent walkthrough covering it in comparable depth outside BUSY's own docs.

Step 1 — GST portal access, before anything else works

Per BUSY's FAQ, two prerequisites have nothing to do with a GSTR download itself. First, on the GST portal: log in and navigate to the My Profile section, select Manage API access, and click Yes — per BUSY's FAQ, "Log in to the GST portal and navigate to the My profile section... select Manage API access. Click yes on it. Duration dropdown will be displayed." Second, inside BUSY: go to Administration > Configuration > Features/Options > GST/VAT and enter your GST portal username. Neither step appears on BUSY's GSTR-reconciliation product page — only in the FAQ's own numbered steps. The username specifically is needed for Auto Download: skip it, and Auto Download has no portal login to authenticate against. The FAQ ties the username to auto download and puts the API-access step inside the Auto Download procedure; it does not state that Manual mode requires either. Manual is described only as browsing to the file path, for months or quarters.

Step 2 — GST Misc. Utilities: downloading the returns

With GST selected as your tax type, the Transactions menu exposes GST Misc. Utilities — per BUSY, "GST Misc. Utilities option appears in Transactions menu only if you have selected the tax type as GST." Inside it sits Download GSTR JSON Data. BUSY's primary FAQ (answerid-48415) walks through this step naming three options: "Under Download GSTR JSON Data, following options appear: Download GSTR1 Data. Download GSTR 2A Data. Download GSTR 3B Data" — and demonstrates GSTR-1 throughout. A sibling BUSY FAQ on switching from QRMP to regular filing (answerid-29907) documents the identical screen naming a fourth option: "select Download GSTR1, GSTR2A, GSTR2B or GSTR3B as required" — so GSTR-2B download is corroborated in BUSY's own FAQ corpus, not just its marketing page, even though the primary walkthrough this article otherwise follows doesn't demonstrate pulling it. GSTR-4A is a different matter: it appears only in the Administration tab's general capability blurb quoted in Step 1, never as a named Download-screen option in either FAQ we could retrieve — treat GSTR-4A support as unconfirmed. Two saving modes are documented: Auto Download, where clicking Download against a month opens a Specify OTP window; per BUSY's FAQ the OTP "will be valid for the time period as selected while configuring API Access on GST Portal," so re-authentication frequency depends on the Duration you picked, not a fixed per-month prompt — and Manual, described only as browsing to a saved JSON file path.

Step 3 — Reconcile GSTR Data: blue matched, red mismatched

Once the data's downloaded, Reconcile GSTR Data takes a start and end month and opens a comparison window where, per BUSY's FAQ, "data of each party as appearing in BUSY and as available on GST Portal is shown in separate rows." The colour coding is the entire interface: rows in blue mean BUSY's books and the portal statement agree; rows in red mean they don't. BUSY's own documentation gives five examples of causes of a red row: invoice amount differences, invoice number differences, a party that "does not exist in BUSY" — the FAQ's own phrase, meaning the portal data shows a party your books have no matching master for — a different GSTIN mentioned in the party master (the FAQ's phrase is "Diffrent GSTN mention in party master"), and a negative value as might appear in a debit or credit note.

Reconciling against 2A tells you less than reconciling against 2B

BUSY's own FAQ pages document GSTR-1, GSTR-2A, GSTR-2B and GSTR-3B as downloadable, reconcilable data sets, and its product page pitches the 2A-vs-2B comparison as a way to spot "delayed supplier filings." That's a genuinely useful diagnostic. It's also easy to read a clean GSTR-2A match as the finish line, and it isn't one — which is exactly why running the 2B reconcile, not only the 2A one, is the step that actually matters here. Under Section 16(2)(aa) of the CGST Act, read with Rule 36(4)(b) of the CGST Rules, the credit that's actually yours to claim depends on the invoice being communicated to you in GSTR-2B under Rule 60(7) — not on whether it happens to appear in GSTR-2A. (Rule 36(4) only bites on documents required to be furnished under Section 37(1) — it doesn't gate IGST paid on imports against a bill of entry, ISD credit, or reverse-charge credit on a Section 31(3)(f) self-invoice, which follow their own eligibility rules.) GSTR-2A keeps changing as suppliers file late or amend their returns, which is exactly why it's useful for tracing a slow filer, and exactly why it was never meant to be the reference for what you can actually claim this period. A blue row on the GSTR-2A screen and a blue row on the GSTR-2B screen for the same invoice are not the same fact.

There's a second wrinkle worth knowing before you assume a "missing" row is a genuine mismatch, also as of 9 September 2026: businesses on the QRMP quarterly filing scheme don't get a GSTR-2B for the individual months of a quarter at all; they get a single GSTR-2B, issued for the quarter's last month — for the Oct–Dec quarter, the December period only (GSTN advisory, 16 November 2024) — and, like any GSTR-2B, generated on the 14th of the month after that period, i.e. 14 January (GSTN's IMS manual: the system "will automatically generate draft GSTR-2B on 14th of the subsequent period"). So an empty M1 or M2 GSTR-2B download for a quarterly filer is the portal's design, not a reconciliation failure or a reason to chase every vendor from that period individually — note this is a GSTR-2B behaviour only; GSTR-2A continues to be made available monthly for QRMP filers (GSTN QRMP Advisory Q25), which is what BUSY's FAQ walkthrough actually downloads — and even the quarter's own statement isn't there until after the quarter ends. Separately, and more likely for a monthly filer — this article's default reader — no GSTR-2B is generated for any period until the previous period's GSTR-3B has been filed: file the pending 3B, then use Compute GSTR-2B on the IMS dashboard (GSTN advisory, 16 November 2024).

What "correct the error if shows mismatch" actually means

BUSY's documented guidance on a red row stops at telling you to fix it — the FAQ doesn't set out a decision tree for which kind of mismatch gets which fix. In practice most red rows are one of five things, and each needs a different action: a typo in your own purchase voucher (fix the voucher); a GSTIN or vendor-master discrepancy on your side (fix the master); a negative value on a debit or credit note that doesn't match between BUSY and the portal (reconcile the note); a supplier who filed the invoice late or in a different tax period, visible by comparing the same invoice's GSTR-2A and GSTR-2B position; or a supplier who hasn't filed it at all, in which case there is no credit sitting anywhere yet to reconcile against — under Section 16(2)(aa) it simply hasn't been communicated to you. That last case isn't a BUSY problem to solve inside the reconciliation screen; it's a vendor-chasing problem, and the fix looks different again from a Rule 37A reversal.

Where BUSY's reconciliation stops, and the bottleneck actually starts

None of this is a knock on the tool — a red/blue match screen, driven by a real portal download, is more than most accounting packages this size document at all, and BUSY's product page separately advertises supplier return-filing-status visibility, IMS ITC tagging against GSTR-2A/2B, exception alerts and payment reminders. But none of that documented tooling is described as tied to a specific red reconciliation row: BUSY's documented workflow doesn't open a follow-up against the GSTIN behind a particular mismatch, or age how many months an unresolved red row has been sitting there. At one vendor, chasing a red row down to which of the five causes above it actually is takes a phone call and five minutes. Across a purchase register with a few hundred vendors, doing that every month, for every red row, and doing it consistently enough to catch the two or three that are quietly costing real credit, is painful to do by hand at any real volume — which is exactly the gap a red row sitting unresolved in BUSY, month after month, with nobody automatically chasing the vendor behind that specific row, actually points at.

A matched row still isn't the same as claimable credit

Even a clean GSTR-2B match in BUSY only tells you the invoice is sitting in the right statement today. Section 16(4) of the CGST Act separately cuts off any unclaimed credit after 30 November following the end of the financial year the invoice belongs to, or the filing of the annual return, whichever is earlier — so an invoice that reconciled cleanly in, say, April can still be lost if nobody actually claims it in a GSTR-3B before that date. A reconciliation screen that shows a matched, blue row has done its job. Whether that credit gets claimed in time is a separate discipline BUSY's own documentation doesn't cover at all.

Related guides