Your GSTR-2B does not match your books. The reason is usually simpler than you think.

Every month your CA reconcile GSTR-2B against the books. GSTR-2B shows what your suppliers filed in their GSTR-1. Your books show what you posted. The two should match. When they do not, someone spends hours tracing which invoice is missing, which GSTIN is wrong, or which total does not add up.

Many mismatches trace back to the original entry. A GSTIN that does not match any registered taxpayer. A tax amount that does not equal the taxable value times the rate. A duplicate invoice number. These errors are small at entry time and large at filing time. By the time your CA finds them, fixing them means amending returns and paying interest.

Reconciliation is not the problem. It is the symptom. The problem is that dirty data reached Tally in the first place.

What GSTR-2B actually is

GSTR-2B is an auto-drafted statement. It shows the input tax credit available to you based on what your suppliers have filed. You do not fill it in. Your suppliers do, through their GSTR-1. Your job is to make sure what they filed matches what you booked.

When a supplier files GSTR-1 with an invoice that mentions your GSTIN, that invoice appears in your GSTR-2B. The amount of ITC you can claim is based on what appears there. If a supplier filed an invoice for ₹50,000, your GSTR-2B shows ₹50,000 in available ITC from that supplier. If you booked ₹55,000 in your books for the same invoice, there is a ₹5,000 mismatch. That mismatch needs to be resolved before you file GSTR-3B.

The three statements that must reconcile:

If books and 2B differ, the gap may be a bad voucher, a supplier who has not filed, or timing. Do not assume it is always your typing. Check. Clean entry still removes the gaps you caused.

The seven-step reconciliation checklist

Reconciliation is a monthly ritual. Here is the checklist. Each step has a specific job, and skipping any one of them leaves a gap that shows up at filing time.

Step 1: Download GSTR-2B. From the GST portal, download the auto-drafted statement for the month. This is the statement that shows what your suppliers have filed. It is not editable. It is what it is.

Step 2: Compare totals. Total ITC in 2B versus total ITC in your books. The difference is the problem to solve. If the difference is zero, you are done. If it is not, proceed to step 3.

Step 3: Match invoice by invoice. For each invoice in your books, find it in 2B. This is the tedious part. It takes time. But it is the only way to find the specific invoices that cause the mismatch.

Step 4: Check missing invoices. Invoices in your books but not in 2B. These are the ones where you booked the entry but the supplier has not filed GSTR-1. Check the GSTIN. Check the supplier's filing status. If the GSTIN is wrong, the invoice will never appear in 2B because the supplier filed under a different GSTIN.

Step 5: Check extra invoices. Invoices in 2B but not in your books. These are suppliers who filed but you did not book. This happens when an invoice is received but not processed, or when the invoice number does not match what you have on file.

Step 6: Resolve mismatches. Wrong GSTIN, wrong amount, missing invoice. Contact the supplier or correct the entry. This is where the time goes. Every mismatch needs to be traced to its source and fixed.

Step 7: File with confidence. Once 2B and books match, file GSTR-3B with the reconciled ITC. The filing is easy. The reconciliation is hard. But if you validate at entry, the reconciliation becomes a formality.

Why reconciliation takes so long

The time in reconciliation is not in the filing. It is in the tracing. Every mismatch needs to be investigated. Was the GSTIN wrong? Was the amount wrong? Was the invoice not filed by the supplier? Each question leads to another question, and each answer takes time.

Mismatches and typical causes (not a measured ranking):

Some causes are entry-time (wrong GSTIN, wrong amount, duplicate). Some are the supplier’s filing. Some are timing. A checklist that pretends every 2B gap is a clerk error creates fake work.

Prevention is cheaper than reconciliation

Every one of those seven steps exists because an error slipped through at entry time. A GSTIN that does not match. A tax amount that does not add up. A duplicate invoice. If you catch those errors before they reach Tally, the monthly reconciliation takes minutes, not hours.

EntryLedger validates GSTINs, HSNs, and arithmetic at the point of entry. Wrong numbers are blocked before they reach the books. That is the difference between reconciliation as a formality and reconciliation as a fire drill.

Your console shows straight-through on your own paper. That rate is the share of invoices that pass all checks and export automatically. The rest go to review, where a person confirms or corrects them. Either way, the data that reaches Tally is clean, and the monthly reconciliation reflects that.

What 2B cannot fix

If the supplier never filed GSTR-1, no amount of GSTIN checksum on your side will make the invoice appear in 2B. That is a vendor problem. Chase the vendor. Do not blame the clerk. Since IMS, the missing line has a new middle step: pending, rejected, or accepted by the supplier. Validation at entry still helps: you know your books are not inventing GSTINs, so when 2B is short you are looking at non-filing, not a typo you introduced.

If you booked an invoice that is not a GST invoice (no GSTIN, not a tax invoice), it should never have been in the ITC bucket. A gate that refuses auto-export without seller and buyer GSTIN keeps those out of the claim. That is Section 16 hygiene, not a 2B feature.

Timing mismatches are real too. You booked in March. They filed in April. 2B will catch up next month. Do not “fix” that by changing your voucher. Note it and wait. A checklist that does not distinguish timing from data error creates fake work.

EntryLedger does not replace your 2B tool. Clear and the GST portal own that view. We make the books you compare against less dirty. If you skip entry validation, you will keep paying for recon as a sport. If you do entry validation, recon becomes matching two lists that mostly already agree.