GSTR-1 vs GSTR-3B: Sales Reporting and Tax-Payment Reconciliation
GSTR-1 reports outward-supply invoice details; GSTR-3B is the summary return used to declare liability, ITC and pay tax.
Use the GSTR-9 and GSTR-9C Applicability Checker to apply these points to your figures or facts.
Filing one does not replace the other, and differences must be reconciled tax-period and financial-year wise.
Legal or Computational Framework
Governing rule
Current-law status: reviewed 5 Aug 2026, still current - GSTR-1 data feeds recipients and portal auto-population, while GSTR-3B determines self-assessed payment. Amendments may be made through permitted return mechanisms, but tax shortfall requires payment with applicable interest. This GST mechanics is separate from and unaffected by the Income-tax Act 1961-to-2025 transition (AY 2026–27 income-tax returns still fall under the 1961 Act; the 2025 Act governs income from 1 April 2026) - the two timelines should not be conflated.
For the connected rule, example or next step, see GSTR-1 Amendment Workflow for Wrong Invoice Reporting.
Correct workflow
The reconciliation only works top-down: start from the invoice register (the source of truth), not from GSTR-3B backwards. Forcing GSTR-3B to match GSTR-1 by adjusting the summary return - without first tracing WHY the two differ at the invoice level - is how genuine timing differences get mistaken for tax shortfalls, or real shortfalls get missed entirely.
Step-by-step method
- Reconcile invoice register to GSTR-1.
- map tax liability to GSTR-3B.
- compare taxable value and tax by rate and place.
- identify timing, amendment and credit-note differences.
- pay shortfall and document corrections.
- Reconcile the conclusion with official statements and supporting documents.
Worked example
GSTR-1 shows taxable sales ₹50 lakh and GST ₹9 lakh, while GSTR-3B reports ₹48 lakh and ₹8.64 lakh. The ₹36,000 tax difference needs transaction-level explanation and, if underpaid, payment with interest.
The example is an audit trail, not a substitute for the user's facts. Change one input—residence, payment date, tax year, asset, return form, GST status, employer category or supporting document—and the result can change.
Edge cases
- Advances can affect services differently from goods: record the factual and legal conclusion in the working paper.
- Credit notes have reporting and time-limit rules: record the factual and legal conclusion in the working paper.
- E-invoice data can auto-populate but still needs review: record the factual and legal conclusion in the working paper.
- Same-period correction mechanisms can alter workflow: record the factual and legal conclusion in the working paper.
- Annual return does not automatically amend returns: record the factual and legal conclusion in the working paper.
What Generic Pages Miss
- Forcing identical turnover without timing analysis.
- Ignoring rate-wise mismatch.
- Using GSTR-1 as proof tax was paid.
- Forgetting debit or credit notes.
- Netting exports and domestic supplies.
For the connected rule, example or next step, see GST Turnover vs Income-Tax Turnover: Reconciliation for Businesses.
Generic pages often confuse gross income with net receipt, TDS with final tax, GST turnover with income-tax turnover or a portal value with legal eligibility. Finin2min should show why an amount is accepted, deferred, reversed, rejected or carried forward.
Practical Documentation Checklist
- Invoice register
- GSTR-1/1A/IFF
- GSTR-3B
- E-invoice/IRN data
- Credit/debit-note register
- Tax and interest working
See the broader GST & Indirect Tax knowledge hub for related rules and calculators on this topic.
Finin2min Summary
Treat a GSTR-1-vs-GSTR-3B gap as a control exception to investigate before deciding it is an error - timing differences (an invoice dated in one period but reported in another), credit notes, and e-invoice/IRP mapping issues routinely produce a mismatch that closes once the source documents are traced, with no actual tax shortfall.
Finin2min rule: classify the legal event, calculate from source records and show every adjustment.
GSTR-1 vs GSTR-3B — mismatch decision table
Do not force equality without explaining timing. A difference is a control exception to investigate, not automatically an error. Reconcile invoice-level data first and classify the reason before changing a return or paying tax.
| Mismatch | Likely bucket | Action |
|---|---|---|
| GSTR-1 liability higher than GSTR-3B | Possible under-payment, timing or amendment mismatch | Trace invoice/note level; if tax was short-paid, discharge tax and applicable interest through the permitted route. |
| GSTR-3B liability higher than GSTR-1 | Possible advance/timing/manual reporting difference | Do not automatically reduce 3B; identify the source record and the permitted correction mechanism. |
| E-invoice exists but GSTR-1 differs | IRP/GSTR-1 mapping or amendment issue | Reconcile IRN data, document type, cancellation/amendment and return period. |
| Credit note is in one return but not the other | Timing / statutory time-limit issue | Check the credit-note eligibility and reporting period before netting liability. |
Portal control: GSTR-3B contains auto-populated values from returns/statements, but auto-population is not evidence that the underlying legal classification is correct. Preserve the invoice register, GSTR-1/IFF, GSTR-3B, IRP data and adjustment working.
Frequently Asked Questions
Source and review trail
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.
- Primary category
- GST & Indirect Tax
- Official starting point
- www.indiacode.gov.in
Page source links
Primary sources & related provisions
Statutory provisions referenced in this guide: