The errors that undermine an input credit reconciliation are rarely arithmetic. They are structural: comparing the wrong documents, pooling populations that must stay separate, searching too narrow a period, and collapsing categories that carry different conclusions. Most of them produce a reconciliation that appears to balance, which is why they survive review and surface later as a demand the client was not expecting.
Errors in what is being compared
- 01Reconciling against GSTR-2A instead of GSTR-2B2A is dynamic and keeps changing as suppliers file and amend. A reconciliation against it gives a different answer each time it is run, so the working paper cannot be reperformed, which is the whole basis on which documentation is expected to stand. Use 2B, which is static once generated, and record the download date.
- 02Pooling a multi-state client's registrationsEach registration has its own GSTR-2B and its own credit ledger. Pooling the registers and the statements produces a reconciliation that can balance overall while concealing credit taken in a state where it was not available. Reconcile each GSTIN separately and never net across them.
- 03Comparing the register to the returns instead of to the booksThree things need to agree: the purchase register, the credit recorded in the books, and the credit claimed in GSTR-3B. Checking the register against the returns and skipping the ledger leaves the possibility that the accounts show something different from both.
- 04Reconciling a register that was never agreed to the ledgerIf the register does not total to the purchases in the general ledger, the reconciliation is between a statement and a spreadsheet. Agree the population before matching anything.
Errors in the population
- 01Leaving reverse-charge supplies in the register sideThey are not reported by the supplier in a way that puts them in 2B, so every one appears as an unmatched line. In a client with significant reverse-charge purchases this can be most of the difference report, and it buries the items that matter.
- 02Leaving credit and debit notes in with invoicesThey reduce credit rather than create it. Matching them against invoices produces noise on both sides. Reconcile them as their own population.
- 03Stopping at the March statementCredit relating to the year under audit routinely appears in the 2B of April, May or later, because the supplier filed late. Searching only within the year reports these as supplier non-filing, which is the single most consequential miscategorisation in this working paper: it turns a timing difference into a potential loss of credit.
- 04Ignoring the effect of actions in the Invoice Management SystemRecords rejected by the client do not carry credit into 2B even though the supplier filed them, and records on which no action was taken flow through as deemed accepted. A reconciliation that treats 2B as purely a product of supplier behaviour will misread both.
Errors in the conclusion
- 01Treating availability as eligibilityAn invoice appearing in 2B means the supplier reported it. It says nothing about whether credit on that supply is permitted. Credit blocked under section 17(5) appears in 2B like any other credit, and a reconciliation that matches it and moves on has confirmed exactly the wrong thing.
- 02Netting differences across categoriesA timing difference in one direction and an ineligible credit in the other produce a small net figure and two unreported problems. Quantify each category separately and conclude on each separately.
- 03Missing the conditions that 2B cannot showRule 37 requires reversal where the supplier has not been paid within 180 days of the invoice date, and that is invisible in any comparison of the register to 2B. It requires an ageing of unpaid purchase invoices, which is a different procedure entirely and is regularly omitted.
- 04Accepting an unexplained residue as a balancing figureThe residue is the number the conclusion actually turns on. Describing it as immaterial without investigating it is an assertion, not a conclusion. Investigate individually and state what remains.
Regulatory requirement
Section 16(4) of the CGST Act sets the outer limit for taking credit for a financial year as the earlier of 30 November following the end of that year or the date of filing the annual return. Rule 37A requires reversal where the supplier has not furnished the relevant GSTR-3B by 30 September following the year of availment, with reversal by 30 November. A reconciliation completed after these dates can identify a problem but not preserve the remedy. Verify the current provisions before advising.
How each mistake shows up on review
| What a reviewer sees | Likely cause | Question to ask |
|---|---|---|
| A reconciliation that balances to the rupee | A balancing figure has been inserted, or categories have been netted | What is in the residue line, item by item? |
| Hundreds of unmatched lines with small values | Reference normalisation was not done, or reverse charge was left in | How many of these are format differences on the same invoice? |
| A large supplier non-filing figure | Only the period's own statement was searched | Were the following months searched, and what was found? |
| One reconciliation for a client with four registrations | Pooling | Which state does each credit belong to? |
| No mention of blocked credits anywhere | Eligibility was never tested, only availability | What procedure addressed section 17(5)? |
| No 180-day ageing in the file | Rule 37 not considered | Which unpaid invoices are past 180 days, and what was reversed? |
| A conclusion saying the credit has been reconciled | The conclusion restates the procedure | What did the reconciliation show, and what is at risk? |
A short self-check before the paper goes for review
- Each registration reconciled separately, with nothing netted across them.
- 2B statements identified by period and download date, and retained in the file.
- The six expected-difference categories removed and quantified, not silently deleted.
- The following months searched for late-filed invoices, and the search evidenced.
- Every unmatched line assigned to exactly one category.
- Eligibility tested against section 17(5) by reference to the nature of the supply.
- The 180-day condition tested from an ageing, not from the reconciliation.
- Credit at risk quantified by category, with the recoverable and non-recoverable portions separated.
- The result agreed to the credit claimed in the returns actually filed.
- A conclusion that states what was found, written by a named person.
How we think about this
Almost every error above is a process failure rather than a knowledge failure. The team knew that 2B is static and that reverse charge does not appear; the reconciliation was just built by hand, differently each time. That is the argument for running the deterministic part the same way on every engagement, and reserving human attention for the residue and the conclusion.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- GST & GSTR-2BGSTR-2B reconciliation: a practical guide for auditorsWhat GSTR-2B is, how the Invoice Management System changed it, the statutory conditions that govern input credit, and how to run and conclude the reconciliation.
- GST & GSTR-2BInvestigating ITC mismatches during auditA decision path for an ITC mismatch: available, eligible, still claimable. What the client can do about each outcome, and how to quantify credit at risk.
- GST & GSTR-2BGSTR-2B reconciliation: the difference categoriesWhat GSTR-2B is, how it differs from 2A, and the six categories every reconciliation difference falls into — with what each one usually means and what it implies for the audit file.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.