How do you run GSTR-2B reconciliation for 20 to 50 clients without chaos?

The arithmetic of a practice is unforgiving. GSTR-2B for a monthly filer is generated on the 14th and GSTR-3B is due on the 20th, so every client shares the same six days. What breaks a practice in those days is rarely the matching itself. It is the client whose register arrives on the 17th, the supplier chased twice by two different juniors, and the return filed before anyone told the owner that ₹1,10,000 of credit was on hold. This post is the operating system we would set up: what to do before the 14th, a calendar for the six days, the tracker, and how to triage.

This page is one part of our GSTR-2B reconciliation guide, which shows how the whole process fits together.

The dates your whole practice runs on

Keep these on the wall. Each row is from the GSTN user guides checked on 30 September 2026, shown for the September 2026 tax period.

For quarterly clients, how and when their own GSTR-2B is produced is a separate question from the dates above; check the current GSTN advisory rather than assuming the monthly pattern. If a date in this table falls on a day the portal treats differently, or an extension is notified, the portal notification wins over this page.

Before the 14th: intake decides how the week goes

The 14th should start with a file to download, not a phone call to make. Fix an internal cut-off, for example the 10th, by which every client sends the purchase register for the period. Ask for it in the shape the tool reads, so nobody retypes anything.

• Export, do not re-key. Ask for the register as exported from Tally, Busy, Marg, Zoho or the client's own sheet. Per-ERP export steps are in the guides for Tally Prime, Busy, Marg and Zoho Books. Send the link to the client once instead of explaining it monthly.
• Insist on the fields that match. Supplier GSTIN, supplier name, invoice number, invoice date, tax amount and total invoice value are required by the mapping step of the tool; taxable value is optional. A register without supplier GSTINs cannot be matched, whatever the software.
• Name files the same way every month. GSTIN_MMYYYY_register.xlsx and GSTIN_MMYYYY_2B.xlsx take ten seconds to type and save an hour of hunting on the 19th.
• Decide who acts on IMS. IMS actions are taken on the client's own GSTIN. Agree in writing which invoices you may accept on the client's behalf and which need the client to confirm receipt of goods.

The calendar for 14th to 20th, written for a practice

The day-by-day reconciliation routine for a single business is in the 14th-to-20th plan. This is the practice version: the same six days, organised by batch.

1. 14th, batch one. Download the 2B for each GSTIN (the steps are in how to download GSTR-2B and the step-by-step download guide). Load 2B and register into the tool and export the CSV for each client. Fill the tracker's rupee columns straight from the report.
2. 15th, rank and chase. Sort by ITC at risk (next section). Send the standard supplier messages for the top clients first. Ask the remaining clients only for what you cannot resolve yourself.
3. 16th and 17th, decisions. Collect client answers on invoices that show as IMS Pending or as in 2B but not in books. Chase suppliers a second time on the 17th with the list of who has replied.
4. 18th, recompute. Where a client's IMS action changed, recompute GSTR-2B before filing GSTR-3B (GSTN IMS FAQ; steps in recompute guide), download again and re-match. Only these clients need a second pass.
5. 19th, sign-off. Send each client a one-line statement: ITC being claimed, ITC on hold and why. File nothing for a client who has not seen it.
6. 20th, file. Monthly clients are filed by the 20th; quarterly clients follow their 22nd or 24th date.

The client-wise tracker

One sheet, one row per GSTIN, columns that answer “where is this client right now?” without opening anything. A layout you can copy:

The “ITC at risk” and “IMS Pending” figures come straight from the two totals at the top of the tool's report (at risk is bucket C plus bucket E; IMS Pending is bucket E). The tool works on one client at a time and exports a CSV per client, so the tracker is a sheet you maintain, not something the tool builds. Add one extra column in October and November: unclaimed invoices of FY 2025-26, because the Section 16(4) limit is 30 November following the end of the financial year, or the date of the annual return, whichever is earlier. See the Section 16(4) guide for the full rule.

Triage: spend hours where the rupees are

A practice with thirty clients does not have thirty equal problems. Rank by ITC at risk on the 15th and work from the top. The split below is an illustrative month, not a statistic from anywhere; your own numbers will differ.

Four clients out of thirty carry about 58% of the rupees (4,10,000 of 7,10,500). If the first pass takes 15 minutes per client, which is a planning assumption to replace with your own timing, the thirty first passes take seven and a half hours and fit inside the 14th and 15th for two people. The rest of the week is for the top tier.

Two rules make the tiers useful. First, IMS Pending outranks other at-risk credit of the same size, because the fix is in the client's hands and can be done before the 18th; the IMS Pending guide explains why. Second, when a client's problem is a supplier who has not filed, decide on the 15th whether the credit will be claimed this month or held, so the client does not learn about it on the 20th. The supplier route is in the guide on suppliers who have not filed, and the payment-hold policy for such vendors is in the vendor payment-hold SOP.

Standard messages: write them once

Two messages carry most of the traffic. Keep them in a shared file, fill the brackets, and always send them in the client's name.

One habit worth adopting: keep an internal list of suppliers who miss reporting across several clients, but never put one client's name, invoice or amount into a message for another client's supplier. The confidentiality side of running many clients is covered in the CA practice guide.

Rules that stop the avoidable mistakes

• Never file from a stale 2B. If the client changed any IMS action after your first download, the return needs the recomputed 2B. Write the download date and time into the file name.
• Keep the hold list with a reason. Every invoice you decline to claim gets a line: supplier, invoice, amount, reason, date reviewed. It is your answer if a client asks in December why credit was not taken.
• Do not let a claim exceed 2B to please a client. The system compares the two figures and issues a DRC-01C intimation when the gap crosses a limit; the reply is your work and the interest is at 18% a year if the credit was wrongly availed and utilised. The DRC-01C guide has the reply process.
• Separate the clients with several GSTINs. Each GSTIN has its own 2B; do not merge them into one file. The multi-GSTIN guide covers branch transfers.

Related guides

• GSTR-2B reconciliation guide: the complete guide to ITC matching
• GSTR-2B reconciliation for multiple GSTINs: several GSTINs and one consolidated result
• GSTR-2B reconciliation with purchase register: matching your register with GSTR-2B invoice by invoice
• How accountants can automate GSTR-2B reconciliation
• GSTR-2B reconciliation checklist: monthly process for accountants
• GSTR-2B vendor wise reconciliation guide
• GSTR-2B reconciliation for large businesses
• How to use a GSTR-2B reconciliation tool

Last checked: 30 September 2026. Sources: GSTN GSTR-1 user guide, GSTN return view guide, GSTN GSTR-3B user guide, GSTN GSTR-1A FAQ, GSTN IMS FAQ, CBIC Circular 237/31/2024-GST, GSTN DRC-01C advisory, Notification 13/2017-CT.