Skip to content
Quillix docs
Home Support Open app → (opens in a new tab)

Reconcile 2A / 2B

Viewing as
Where Sidebar Compliance 2A / 2B Reconciliation

Checks the client's booked purchases against what their suppliers actually filed. Input credit is only safe if the supplier declared the invoice — and the two ways that goes wrong both cost real money.

GSTR-2A
Dynamic. Moves continuously as suppliers file.
GSTR-2B
Static. The monthly snapshot ITC claims are matched against.
First
Nothing on this screen is populated until you upload. Download the period's 2A or 2B Excel from the GST portal and bring that file in here — the comparison is built from it against the purchases and expenses already in the client's books.
  1. Download the 2A or 2B Excel for the period from the GST portal.
  2. Upload it here and set the book period you want compared — the From and To dates for the books side.
  3. Review the buckets that come back.
Note
Matching is done on supplier GSTIN, which is the only key that holds. Trade names drift constantly between the portal and the books, so a name-based match would be wrong more often than right.
SCREENSHOT · the upload step — the portal-file picker beside the From / To book-period dates
Only in 2A The supplier filed an invoice against the client, but it is not in the books. That is input credit sitting unclaimed.
Only in books The client booked and claimed the credit, but the supplier has not filed. If it stays that way, the department will come for it.

Only in 2A — credit you have not claimed

  1. Open the Only in 2A bucket and check each invoice against the client's paperwork.
  2. Where the bill is genuine, book it so the credit is claimed — Quillix offers to add missing 2A invoices to the books for you.
  3. Use select-all to take every invoice in the bucket at once, rather than ticking them one by one.
Note
This is usually the bucket with money in it. A bill that never reached you is invisible until the portal shows it.

Only in books — credit at risk

  1. Open the Only in books bucket.
  2. Chase the supplier to file, or reverse the credit if they will not.
Note
Purchases from unregistered suppliers are tracked separately and deliberately kept out of this bucket. They can never appear in 2A, so including them would flood the risk list with rows that are not risks.

Mismatched — in both, but not the same

The invoice exists on both sides, but the count or the amount differs beyond tolerance.

  1. Open the bucket and use the invoice-level detail to see which figure disagrees.
  2. Decide whether the books or the portal is right, and correct the one that is wrong.

Matched — nothing to do

Present on both sides, with amounts agreeing within tolerance. Use the matched count as your confidence measure — a high proportion matched means the client's ITC position is sound.

SCREENSHOT · reconciliation result — the Only in 2A, Only in books, Mismatched and Matched buckets with their counts
Should ITC be claimed from GSTR-2A or GSTR-2B?
GSTR-2B is the static monthly statement credit is claimed against; 2A is dynamic and updates whenever a supplier files, including for earlier periods. Quillix reads either, but 2B is the one that freezes.
What does ITC at risk mean?
Purchases recorded in the books that no supplier has reported. Until the supplier files, that input tax credit may not be available — and claiming it is a demand notice waiting to happen.
Why would a vendor never appear in 2A?
A vendor with no GSTIN can never appear in the client 2A. Quillix tracks those purchases separately rather than flagging them as missing, because their absence is expected rather than a risk.

Last updated