GSTR 2B/3B Reconciliation Report

GSTR 2B/3B Reconciliation Report

GSTR 2B/3B Reconciliation Report - User Guide

âš ī¸
Eligibility Check: This report is exclusively available for societies registered under the GST Act. If your society is “Unregistered” (URP), this module will remain inactive.

1. Introduction 📊

The GSTR 2B/3B Reconciliation Report is a high-level tax audit tool. It automates the complex task of matching the society’s internal purchase records with the data uploaded by vendors on the GST portal (GSTR-2B) and the final returns filed by the society (GSTR-3B).

â„šī¸

Purpose of this Report:

  • Claim Full ITC: Ensure that for every GST paid to a vendor, the society has claimed the corresponding Input Tax Credit (ITC).
  • Identify Missing Bills: Spot cases where a vendor has taken payment but hasn’t uploaded the bill to the government portal.
  • Accuracy Check: Reconcile differences in Bill Dates, Tax Amounts, and Invoice Numbers between society books and portal data.
  • Avoid Penalties: Maintain a “Clean” tax profile by ensuring no over-claimed or mismatched credits.

2. Reconciliation Analysis 🚀

The module focuses on three primary reconciliation workflows:

A. GSTR-2B Reconciliation (Shown in 2B)

  • Purpose: Compares society books with the portal’s GSTR-2B statement (auto-generated for every month).
  • Analysis: Identifies if a vendor has filed their GSTR-1. If a bill appears in your books but NOT in 2B, you cannot legally claim ITC.

B. GSTR-3B Reconciliation (Availed in 3B)

  • Purpose: Matches your books with what the society finally filed in the GSTR-3B return.
  • Analysis: Ensures that the ITC recorded during bill entry matches the final figures submitted for tax payment.

C. Unreconciled / Variance Analysis

  • Purpose: The “Action Area” of the report. It highlights only the rows where a mismatch exists.
  • Common Variances:
    • Book Only: Bill is entered in ERP but not found on the portal.
    • Portal Only: Bill appears on the portal but hasn’t been entered in the society ERP.
    • Amount Mismatch: GST numbers match but basic amounts or tax values differ.

3. Data Visibility & Scanning Options 🔍

Users can choose the “Source Filter” for how the system should scan and match documents:

Scan Based On Logic Applied
Bill Date Matches documents based on the invoice date printed on the vendor bill.
2B Date Analysis based on the month/period the vendor uploaded the bill to the portal.
3B Date Analysis based on the month the society claimed the credit in their return.

4. The Upload & Sync Process 🔄

Unlike standard reports, the GSTR Reco module requires an external data feed:

  1. Download: Obtain your GSTR-2B JSON/Excel file from the GST portal.
  2. Upload: Navigate to the Upload section within the module.
  3. Process: The system parses the portal file and matches it against your internal Purchase Bills.
  4. Analyze: Use the Download button to view the reconciliation results in Excel.

5. Using the Report Interface đŸ› ī¸

Selection Filters

  • Select Option: Choose between All (comprehensive view) or Unreconciled (only exceptions).
  • Report Type: Choose 2B Reco or 3B Reco (active when ‘Unreconciled’ is selected).
  • Date Range: Typically aligned with a monthly or quarterly tax filing period.

Generation Mode

  • Download (Excel): Produces a multi-sheet Excel file highlighting matches and mismatches with color-coded status indicators (Reconciled / Missing / Mismatch).

6. Best Practices / Tips 💡

  • Monthly Reconciliation: Perform this task on the 14th of every month (after GSTR-2B is generated) to ensure your monthly GSTR-3B filing is 100% accurate.
  • Follow Up with Vendors: If a high-value bill appears as “Unreconciled,” send an automated email to the vendor asking them to update their GST returns immediately.
  • Check Bill Numbers: Often, mismatches occur due to prefixes (e.g., INV/01 vs 01). Ensure your purchase entry matches the vendor’s portal entry for better auto-matching results.
  • ITC Safeguard: Never claim ITC for a “Book Only” row until the vendor uploads the data and it appears in your 2B statement.