Marg ERP can reconcile GSTR-2B on its own. One setting hides two menus away, under a name that has nothing to do with reconciliation
Reconciling GSTR-2B in Marg ERP needs two things done before the reconciliation screen itself works — API access enabled on the GST portal, and a GSP selected under Marg's GST > GSTR Settings > E Invoice Settings (Marg's own walkthrough uses Pinnacle Finserv). Only then does GST > GSTR 2A-2B Reconciliation download and colour-code invoices against your GSTR-2B, which is itself a draft that can still change before you file GSTR-3B.
Marg's own help-centre pages document a real, working GSTR-2B reconciliation flow — a JSON pull from the GST portal, four colour-coded match statuses, invoice-level detail. What they don't flag clearly is that the documented setup routes through a screen labelled E Invoice Settings, and puts it before the reconciliation steps — for a feature that isn't e-invoicing.
What Marg's own help centre documents, and what it doesn't
Marg ERP publishes two near-identical FAQ pages on its help portal, care.margcompusoft.com — one for GSTR-2A reconciliation and one for GSTR-2B reconciliation. Both walk through a genuinely usable feature: pull a JSON statement from the GST portal, match it invoice-by-invoice against what's in Marg, and colour-code the result. What neither page frames clearly is that the walkthrough routes through a screen called E Invoice Settings — a GSP selection, inside a guide that has nothing else to do with e-invoicing — and documents it before the reconciliation steps, not after. Marg doesn't say what breaks if you skip it; it's simply documented as the order to follow.
Step 1 — enable API access on the GST portal
Per Marg's own FAQ, before anything happens inside the software: log in at www.gst.gov.in, click My Profile (top right), select Manage API Access from the Quick Links tab, choose Yes for "Enable API Request," and pick a Duration — 6 hours or 30 days. That duration is the window an OTP stays valid for once you start pulling JSON files into Marg: on a 6-hour setting, the first download of each window needs an OTP and every download after that, for 6 hours, doesn't; on a 30-day setting the same applies across those 30 days. Whichever you pick expires and asks for a fresh OTP again once the window closes — it isn't a one-time enable.
Step 2 — the two Marg settings the reconciliation walkthrough documents first
Marg's documented setup happens across two separate visits to the same menu, GST > GSTR Settings:
| Screen | Field | What you enter |
|---|---|---|
| GST > GSTR Settings | GSTR User Name | The same username registered on the GST portal — click Okay to save. |
| GST > GSTR Settings > E Invoice Settings > Edit | Select your GSP | Marg's own walkthrough selects Pinnacle Finserv, then clicks Save. |
Skip either row in the table above and Marg's own support portal names exactly what happens: an "API Access is not enabled" alert if the GST-portal side (Step 1) was never done or has lapsed — the fix is to re-run Manage API Access and revisit GSTR Settings — and a Download option that stays greyed out if the GSTR User Name field was left blank, which Marg's support page traces to that one missing entry rather than a GSP or portal problem.
Step 3 — running the reconciliation
With both settings in place, go to GST > GSTR 2A-2B Reconciliation and click GSTR-2B (the same menu also holds the separate GSTR-2A screen). Select the period — from which month to which — and click Show; click a specific month to open it. A pop-up offers two ways to load the data: Manual, if you already have the JSON file saved, or Download, which pulls it straight from the GST portal if the machine has internet access. The first Download of the OTP window prompts for the OTP you'd have received per Step 1's Duration setting; after verifying it, Marg confirms the JSON download for that month and loads it. Two things can leave a month with nothing to download: if you are on QRMP you get no GSTR-2B for the first two months of a quarter — it's quarterly for you — and 2B won't generate for any period until the previous period's GSTR-3B is filed (GSTN advisory, 16 Nov 2024 — this is portal behaviour, not Rule 60 itself, which on its face says GSTR-2B is made available for every month; position as of 16 September 2026). Filing the arrear 3B doesn't back-fill the statement automatically either — you generate it on demand with "Compute GSTR-2B" on the IMS dashboard, then re-run Marg's Download.
Once loaded, Marg shows the invoice-level totals — total entries, taxable amount, CGST, SGST, IGST, CESS and total tax — colour-coded into four statuses, per Marg's own documentation:
| Colour | Status | What it means, per Marg's own FAQ |
|---|---|---|
| Green | Matched | The invoice agrees between the GST portal data and what's recorded in Marg. |
| Red | Mismatched | "The invoice value on the GST Portal is different and the value in the invoice created in Marg Software is different." |
| Purple | Not uploaded | "Those invoices are not been uploaded on the GST Portal" — present in Marg, absent from the portal statement. |
| Blue | Absent in Marg | "Those invoices are not been created in Marg Software" — present on the portal statement, no matching Marg entry. |
Double-clicking any status, or clicking Detailed, lists the underlying invoices — customer name, invoice number, invoice date, GSTIN and invoice value — with taxable amount, tax rate and tax shown twice: once as "Auto Populated" (what the seller uploaded in their GSTR-1) and once as "Marg GSTR2 Data" (what you recorded). A Summary view breaks the same counts down by invoice type (B2B, or debit/credit notes) and by status. Marg also lets you set a tolerance before a value difference counts as a mismatch at all: entering an amount under Mismatch Amount and ticking Ignore Invoice Amount tells the software to treat a difference within that figure as a match rather than a red row; a separate Ignore Dates checkbox does the same for date differences. Set either tolerance wide and you'll see fewer red rows — which is exactly why it's worth knowing the setting exists before assuming a clean-looking screen means nothing is actually off.
One documented downstream effect is worth flagging on its own: Marg's FAQ notes that GSTR-3B can pull its ITC figures either from these reconciled entries — "only matched entries will be shown" — or, if you skip reconciliation, straight from your accounting books instead. Filing 3B off your books without ever running this screen means Marg has no way to know whether what you're claiming actually sits in your GSTR-2B — the exact gap that a Rule 88D (DRC-01C) intimation exists to catch once the two diverge past a threshold GSTN does not publish.
What a "not uploaded" row is, and what it usually isn't
It's tempting to read a purple, "not uploaded" invoice as proof a supplier simply hasn't filed. Sometimes that's exactly it — and if so, Section 16(2)(aa) of the CGST Act means the credit genuinely isn't available yet, because it hasn't been communicated to you the way the law requires (the mechanics run through Rule 36(4), which ties the condition specifically to appearing in GSTR-2B, not GSTR-2A). But two other, entirely benign explanations produce the identical purple row. A supplier on the QRMP quarterly scheme files GSTR-1 only for the quarter — but can still push B2B invoices for the first two months into your GSTR-2B through the optional Invoice Furnishing Facility under Rule 59(2), up to the 13th of the following month and capped at ₹50 lakh cumulative per month; IFF details are one of the limbs GSTR-2B is built from under Rule 60(7). So a "not uploaded" invoice from a QRMP vendor in month one or two may be a filing-cycle timing gap rather than a missing filing — but only because the IFF is optional and that vendor didn't use it for that invoice. It is not something you can assume from the vendor's scheme alone. And GSTR-2B itself isn't a fixed file: GSTN drafts it on the 14th of the following month and keeps it open to change through Invoice Management System (IMS) actions, right up until you file GSTR-3B for that period — untouched records are deemed accepted by default. A JSON you downloaded into Marg on the 15th is a snapshot of that draft, not a guarantee of what the statement looks like by the time you file. Marg's own reconciliation FAQ, whose walkthrough still screenshots October 2022 data and whose footer is copyright-dated 2023, predates IMS and doesn't mention it at all — worth keeping in mind if you're reading the purple bucket as a finished answer rather than a moment-in-time snapshot (position as of 16 September 2026).
Why GSTR-2B, not GSTR-2A, is the screen that decides your credit
Marg documents both reconciliation screens with near-identical mechanics, the substantive difference being which GST-portal statement they pull. That parity in the tool can obscure a real difference in the law. Under Section 16(2)(aa), read with Rule 36(4)(b) of the CGST Rules, an ordinary vendor credit is only yours to claim once it's communicated to you in GSTR-2B under Rule 60(7) — GSTR-2A carries no such condition; it's a running, constantly-revising record useful for spotting a slow filer, not the reference for what you can claim this period. (Rule 36(4) also doesn't reach imports on a bill of entry, ISD credit, or reverse-charge self-invoices — those follow their own rules regardless of what either screen shows.) A green row on Marg's GSTR-2A screen and a green row on its GSTR-2B screen for the same invoice are not the same fact, and reconciling only the 2A screen because it's the one your team is used to checking is a genuine risk worth correcting.
What the colour buckets don't tell you
Marg's four statuses and the Detailed drill-down are further than plenty of accounting packages this size document at all — you get a named customer, invoice number, GSTIN and two side-by-side value sets for every entry. What none of it does is tell you why a specific vendor invoice is sitting in mismatched or absent, or how long it's been sitting there. A purple row could be a genuinely unfiled supplier, a QRMP timing gap, or an IMS action taken after your last download — Marg's screen shows you the same colour for all three, and nothing in its documented flow opens a follow-up against the specific GSTIN behind that row or ages how many reconciliation cycles it's survived unresolved. Working that out, invoice by invoice, across a purchase register with any real number of vendors, every month, is painful to do by hand at scale — which is exactly the gap a stuck row sitting unresolved in Marg, month after month, actually points at.
Video walkthrough by MARG ERP — embedded with credit; the guide above is our own.
Where Recoup fits in
Recoup doesn't replace Marg's reconciliation screen — it sits on top of the same underlying question. It continuously reconciles your purchase register against GSTR-2B, names the specific supplier and invoice behind every stuck credit it finds, and tracks how long each one has stayed unresolved, instead of leaving a coloured row to be noticed on the next monthly pass.
A red or purple row in Marg tells you something's off. It doesn't tell you which vendor to call.
Recoup reconciles your books against GSTR-2B continuously and names the specific supplier and invoice behind every mismatch it surfaces — so a stuck credit doesn't wait for the next monthly reconciliation cycle to be noticed.
Book a demo →Related guides
GST reconciliation: the 2026 guide for finance teams
Marg's colour-coded match screen is one implementation of a bigger exercise — the four reconciliations that actually decide your credit.
GSTR-2A/2B reconciliation in BUSY
The same GST-portal-JSON-download pattern, worked through for a different accounting package — and a different undocumented gap.
Supplier hasn't filed GSTR-1? Recover the blocked ITC
What a purple "not uploaded" row in Marg actually means, and why it isn't a Rule 37A reversal.
Input Tax Credit: eligibility, reversals & the 30-Nov clock
A matched, green row in Marg and an eligible credit under Section 16 are two different tests.
GSTR-2B
Why GSTR-2B, not GSTR-2A, is the statement that actually decides what you can claim.