GST Master Data Checklist Before Filing Returns
- Review master records before preparing GSTR-1 and finalising GSTR-3B.
- Check newly created or modified party, GSTIN, item, tax, and ledger records.
- Table 12 of GSTR-1 and GSTR-1A now uses dropdown-based HSN reporting.
- Use 4-digit or 6-digit HSN codes based on turnover in the preceding financial year.
- Review only the goods and services affected by GST rate changes from 22 September 2025.
- Treat a cancelled or suspended GSTIN as a review trigger, not automatic proof that all earlier ITC is ineligible.
- Give billing teams responsibility for creating records and accounts teams responsibility for verifying them.
Incorrect reusable records can affect several invoices before the error is noticed. A wrong GSTIN, HSN code, state, tax rate, or ledger mapping may lead to incorrect return reporting, reconciliation differences, or later amendments.
This GST master data checklist is for accountants and billing teams preparing monthly or quarterly GST returns. It is also useful for businesses moving from spreadsheets, changing accounting software, or setting up GST records for the first time.
Experience the power of Expert Accounting
Join our guided walkthrough to see how BUSY can transform your business operations.
What Is GST Master Data?
GST master data is the reusable information stored in billing or accounting software and applied automatically when invoices, purchases, credit notes, and other transactions are recorded. It normally includes:
| Master | Information Stored |
|---|---|
| Party records | Customer or supplier name, GSTIN, address, state, and taxpayer type |
| Item or service records | Description, HSN or SAC, tax rate, unit, and cess |
| Tax records | CGST, SGST, UTGST, IGST, cess, and RCM configuration |
| Ledger records | Sales, purchases, output tax, input tax, reversals, and ineligible ITC |
| Transaction settings | Place of supply, invoice series, bill-to and ship-to treatment, and effective dates |
Master
Information Stored
Master
Information Stored
Master
Information Stored
Master
Information Stored
Master
Information Stored
These records support compliance, but they do not replace transaction-level checks. Place of supply, RCM, tax rate, and ITC eligibility may still depend on the facts of an individual transaction.
Reports to Keep Ready Before Starting
Begin with records created or modified during the return period. Newly added or changed records are more likely to contain setup errors than older records used regularly. Keep the following reports ready:
| Review Area | Reports or Records Required |
|---|---|
| New or modified masters | Parties, items, and services created or changed during the return period |
| Missing or invalid details | Records with blank or invalid GSTINs and HSN or SAC codes |
| Tax classification | Items grouped by GST rate and RCM transaction report |
| Duplicate records | Duplicate GSTIN or party report |
| Ledger review | Tax-ledger summary |
| Return validation | GSTR-1 exception or validation report and GSTR-2B reconciliation report |
Review Area
Reports or Records Required
Review Area
Reports or Records Required
Review Area
Reports or Records Required
Review Area
Reports or Records Required
Review Area
Reports or Records Required
Review Area
Reports or Records Required
These reports help narrow the review to records that are new, incomplete, inconsistent, or more likely to affect GST reporting.
Party Master Checklist
The party master contains the customer and supplier details used in invoices, purchase entries, ledgers, and GST reports. Review every party created or modified during the return period.
Identity and Registration Details
- Legal name is recorded correctly.
- Trade name is included where relevant.
- GSTIN belongs to the correct party.
- Separate state-wise GSTINs are maintained as separate party records.
Address and State Details
- Billing address is current.
- Shipping address is recorded separately where required.
- State and state code are correct.
- PIN code is complete.
Rule 46 of the CGST Rules requires the recipient’s name, address, and GSTIN or UIN on a tax invoice where the recipient is registered. It also requires place-of-supply details for inter-State supplies .
Check the Taxpayer Type
The taxpayer type selected in the party master affects how transactions are classified and reported. Common categories include regular, composition, SEZ unit, SEZ developer, UIN holder, and unregistered customer or supplier.
Make sure the category reflects the party’s actual GST registration. For example, a composition taxpayer should not be treated as a regular taxpayer, while an SEZ unit and an SEZ developer may require different transaction treatment depending on the supply.
Note: Deemed export is not a GST registration type. It is a treatment available for specified supplies when the required conditions are met. It should therefore be applied at the transaction level rather than selected as the party category.
Review Place of Supply Separately
The state entered in the party record is an important input, but it does not decide the tax type in every transaction. The place of supply may need a separate review where:
- The bill-to and ship-to locations are different.
- Goods are delivered to another state.
- Goods are installed or assembled at a separate location.
- The supply is made to an SEZ.
- The transaction is an export.
- A special place-of-supply rule applies to the service.
For example, a customer may be registered in Delhi but request delivery to its Haryana unit. The invoice should not automatically use the Delhi state details. The applicable tax must be determined from the actual transaction and the relevant place-of-supply rule.
Remove Duplicate Party Records
Duplicate party records usually arise when the same customer or supplier is created under different spellings. For example, “ABC Traders Pvt Ltd” and “ABC Traders Private Limited” may appear as separate records even though both carry the same GSTIN.
This does not directly change the data on the GST Portal, but it can split sales, purchases, balances, invoices, and reconciliation history across multiple records.
The most reliable way to identify duplicates is to search by GSTIN rather than by party name. Once identified, the duplicate record should be merged or deactivated without disturbing the transaction history.
GSTIN Master Review
The GSTIN master should confirm that the registration details stored in the accounting system belong to the correct customer or supplier. A basic review should cover:
| Field | What to Verify |
|---|---|
| GSTIN format | The GSTIN contains 15 characters and follows the correct structure |
| Legal entity | The GSTIN belongs to the intended business |
| State code | The first two digits match the registered state |
| Registration status | The GSTIN is active, cancelled, suspended, or otherwise updated |
| Registration date | Confirm that the registration was effective for the relevant supply period |
| Legal and trade names | The saved party details match the registration record |
| Taxpayer type | The party is correctly marked as regular, composition, SEZ, or another applicable category |
| Cancellation or suspension date | The effective date is reviewed before deciding the treatment of old invoices |
Field
What to Verify
Field
What to Verify
Field
What to Verify
Field
What to Verify
Field
What to Verify
Field
What to Verify
Field
What to Verify
Field
What to Verify
The GST Portal’s pre-login taxpayer search can display the registration status, legal name, trade name, taxpayer type, principal place of business, registration date, cancellation details, and recent filing information.
How Often Should GSTINs Be Verified?
GST law does not prescribe one fixed verification cycle for all suppliers. The frequency should depend on the value, activity, and compliance risk of the party. This is a business control rather than a statutory safe harbour.
| Party Type | Practical Review Frequency |
|---|---|
| Newly added supplier | Before relying on the first invoice for ITC |
| High-value or high-volume supplier | Monthly or quarterly |
| Supplier with repeated filing delays | Before a material ITC claim |
| Supplier used after a long gap | Before recording fresh purchases |
| Stable, low-value supplier | Through periodic sample checks |
Party Type
Practical Review Frequency
Party Type
Practical Review Frequency
Party Type
Practical Review Frequency
Party Type
Practical Review Frequency
Party Type
Practical Review Frequency
What If a GSTIN Is Cancelled or Suspended?
A current cancelled or suspended status should trigger a review, but it does not automatically make every earlier invoice invalid. Before deciding whether ITC must be reversed, review:
- The invoice date.
- The effective date of cancellation or suspension.
- Whether the cancellation was retrospective.
- Whether the registration was later restored.
- Whether the goods or services were received.
- Whether the invoice appears in GSTR-2B.
- Whether the conditions under Section 16 were met.
- Whether any order or dispute affects the relevant period.
Note that the current GSTIN status is only one part of the review. The treatment of an earlier invoice depends on the invoice period, effective registration status, receipt of supply, GSTR-2B reporting , and Section 16 conditions.
Where ITC is found to have been wrongly availed and utilised , interest under Section 50 (3) applies at the notified rate of 24% per annum. Rule 88B explains how the utilisation period is calculated.
Item Master Review for GST
The item or service master controls the HSN or SAC code , tax rate, unit, and classification used across invoices. Errors in this master can therefore repeat across several transactions.
HSN and SAC Validation
Review whether each record is correctly created as goods or services and whether the HSN or SAC code matches the actual supply. The following fields deserve attention:
| Field | Review Point |
|---|---|
| Goods or service type | The item is not incorrectly created under the wrong category |
| HSN or SAC code | The code is complete and not blank |
| Required digits | The correct 4-digit or 6-digit reporting level is used |
| Description | The tariff description reasonably matches the actual product or service |
| Consistency | Similar items are not using different codes without a valid reason |
| Supporting basis | High-value or disputed classifications have supporting documents |
Field
Review Point
Field
Review Point
Field
Review Point
Field
Review Point
Field
Review Point
Field
Review Point
Phase 3 of Table 12 reporting applies from the May 2025 return period. It introduced dropdown-based HSN selection and separate B2B and B2C reporting.
Four-Digit and Six-Digit HSN Requirements
| Aggregate Annual Turnover in the Preceding Financial Year | Table 12 Requirement |
|---|---|
| Up to ₹5 crore | 4-digit HSN |
| Above ₹5 crore | 6-digit HSN |
Aggregate Annual Turnover in the Preceding Financial Year
Table 12 Requirement
Aggregate Annual Turnover in the Preceding Financial Year
Table 12 Requirement
Invoice requirements and Table 12 reporting should not be treated as identical. For Table 12, the applicable HSN summary must be reported separately for B2B and B2C supplies under the current portal workflow.
Use the GST Portal Search Carefully
The GST Portal HSN search is useful for finding codes and related descriptions, but it is only a facilitation tool. A code appearing in the search does not automatically settle a disputed classification. For unusual, high-value, or disputed goods or services, review:
- Customs Tariff wording
- Product composition
- Product function and use
- Section and chapter notes
- Applicable GST rate notification
- Relevant circulars or rulings
Review the GST Rate and Effective Date
The item master should preserve both the correct rate and the date from which it applies. For items affected by the GST changes effective from 22 September 2025, compare:
| Review Area | What to Confirm |
|---|---|
| Old rate | Rate applicable before the change |
| Revised rate | Rate notified from the effective date |
| Classification | HSN or SAC entry covered by the notification |
| Conditions | Value, use, recipient, description, or other conditions |
| Cess | Whether compensation cess continues to apply |
| Returns and adjustments | Treatment of credit notes, debit notes, and sales returns |
| Historical invoices | Old transactions continue to retain the original applicable rate |
Review Area
What to Confirm
Review Area
What to Confirm
Review Area
What to Confirm
Review Area
What to Confirm
Review Area
What to Confirm
Review Area
What to Confirm
Review Area
What to Confirm
Note: The 56th GST Council recommendations moved the main structure towards 5% and 18%, with a special 40% rate for select supplies. However, the exact treatment must be checked against the relevant notification.
Do not update every item created before September 2025. Review and change only those classifications that were actually affected.
Check Unit and Quantity Settings
Incorrect unit settings can create differences between invoices, stock records, e-way bills, and return summaries. For goods, confirm that:
- The correct UQC is selected.
- Purchase and sales units are properly converted.
- Alternate units do not change taxable quantities.
- Decimal quantities follow one consistent method.
- Goods are not mistakenly created as services.
- Stock and invoice units match where required.
A wrong unit may not always prevent return filing, but it can make quantity and inventory reconciliation unreliable.
Tax and Ledger Master Review
Output Tax Ledgers
Separate ledger mapping should be maintained for:
| Ledger | Purpose |
|---|---|
| CGST | Central tax on intra-State supplies |
| SGST or UTGST | State or Union Territory tax on intra-State supplies |
| IGST | Tax on inter-State supplies |
| Compensation cess | Cess on specified goods |
| RCM liability | Tax payable under reverse charge |
| Tax corrections | Additional liability arising from rate or classification corrections |
Ledger
Purpose
Ledger
Purpose
Ledger
Purpose
Ledger
Purpose
Ledger
Purpose
Ledger
Purpose
The accounts team should review whether inter-State supplies are reaching the IGST ledger and intra-State supplies are reaching the CGST and SGST or UTGST ledgers, subject to the applicable place-of-supply rules.
Input Tax and Reversal Ledgers
Eligible credit should not be grouped with blocked, reversed, or disputed amounts. A clear ledger structure may include:
| Ledger Group | Examples |
|---|---|
| Eligible ITC | Input CGST, SGST or UTGST, and IGST |
| RCM credit | ITC relating to tax paid under reverse charge |
| Blocked ITC | Credit restricted under Section 17(5) |
| Temporary reversals | Credit that may be reclaimed later |
| Permanent reversals | Credit that cannot be reclaimed |
| Common-credit reversals | Personal use, non-business use, or exempt supplies |
| Prior-period corrections | Adjustments relating to earlier tax periods |
Ledger Group
Examples
Ledger Group
Examples
Ledger Group
Examples
Ledger Group
Examples
Ledger Group
Examples
Ledger Group
Examples
Ledger Group
Examples
Creating separate ledgers does not by itself decide legal eligibility. It acts as a control so that known blocked or reversed amounts are not mixed with the regular ITC claim.
Review RCM at Transaction Level
RCM should not be applied merely because a supplier is unregistered. For each RCM transaction, check the nature of supply, notification entry, supplier category, recipient category, rate, exemption, time of supply , and documentation requirements.
A transaction-level or supply-category review is safer than placing one blanket RCM flag on the entire supplier record.
When Each Master Should Be Reviewed
| Stage | Main Review |
|---|---|
| When adding a party | Name, GSTIN, state, taxpayer type, address, status, and duplicate search |
| When adding an item | Goods or service type, HSN or SAC, rate, unit, cess, and exemption |
| When a rate changes | Affected classifications, effective date, sample invoices, and historical-rate protection |
| Before GSTR-1 | New parties, invalid GSTINs, HSN summary, invoice series, rate, and place of supply |
| Before GSTR-3B | Output tax, RCM, ITC, reversals, blocked credit, and ledger mapping |
| Periodic review | Inactive records, duplicate parties, changed GSTIN status, and unused tax categories |
Stage
Main Review
Stage
Main Review
Stage
Main Review
Stage
Main Review
Stage
Main Review
Stage
Main Review
Who Should Own the Review?
| Role | Responsibility |
|---|---|
| Billing team | Collect details and create customer, supplier, and item records |
| Accounts team | Verify GSTIN, state, HSN, tax rate, and ledger mapping |
| Tax reviewer | Review RCM, place of supply, exemptions, and disputed classifications |
| System administrator | Restrict edit access and maintain change logs |
| Finance head | Approve material exceptions before filing |
Role
Responsibility
Role
Responsibility
Role
Responsibility
Role
Responsibility
Role
Responsibility
Where one employee handles both billing and accounts, generate a report of all masters created or modified during the month. Review this report separately before finalising the return.
Final Pre-Filing Review
Before filing, complete one consolidated review instead of repeating separate checklists across every section:
- Review all party and item masters created or modified during the period.
- Identify duplicate GSTINs.
- Validate new and high-value parties.
- Review cancelled or suspended registrations with their effective dates.
- Check unusual place-of-supply transactions.
- Identify blank or invalid HSN or SAC codes.
- Compare Table 12 data with the applicable HSN requirements.
- Review items affected by the September 2025 rate changes.
- Check RCM and ineligible ITC ledgers.
- Reconcile the output-tax ledgers with GSTR-1 and the proposed GSTR-3B .
This review does not replace GST return reconciliation . It confirms that the reusable records behind the transactions are accurate before the return is filed.
Common Errors and Corrective Action
| Error | Possible Effect | Action |
|---|---|---|
| Malformed GSTIN | Validation or upload error | Correct and validate the GSTIN |
| Correct format but wrong GSTIN | Invoice reported against the wrong recipient | Confirm the party and amend the transaction |
| Cancelled GSTIN | ITC or invoice-period risk | Review the effective date and Section 16 conditions |
| Blank or wrong HSN | Table 12 or classification issue | Correct the item record and affected transactions |
| Old tax rate | Overpayment, short payment, or customer dispute | Apply the correct rate from the effective date |
| Wrong party state | Incorrect tax type or place of supply | Review the actual transaction |
| Blanket RCM setting | RCM applied to non-covered purchases | Check the relevant notification conditions |
| Duplicate party | Split balances and reconciliation history | Merge or deactivate the duplicate record |
| Wrong unit | Incorrect stock or quantity reporting | Correct the unit and conversion factor |
| Blocked ITC in an eligible ledger | Overstated ITC claim | Reclassify and report the amount correctly |
Error
Possible Effect
Action
Error
Possible Effect
Action
Error
Possible Effect
Action
Error
Possible Effect
Action
Error
Possible Effect
Action
Error
Possible Effect
Action
Error
Possible Effect
Action
Error
Possible Effect
Action
Error
Possible Effect
Action
Error
Possible Effect
Action
Make the Review Easier with BUSY
Checking hundreds of customer, supplier, and item records manually can delay return preparation. BUSY allows users to validate single or multiple GSTINs and HSN codes online. It can also display GSTIN status and update available party details in the account record.
BUSY accounting software, trusted by 6 lakh+ businesses, helps connect billing, accounting, GST records, and return preparation in one system.
Software validation can reduce avoidable data-entry errors. However, classification, place of supply, RCM, and ITC eligibility must still be reviewed based on the applicable law and transaction facts.
Conclusion
Accurate records make GST return preparation faster and reduce the need for repeated corrections. The most effective process is to verify new or modified records when they are created and run a shorter exception review before every filing.
Billing teams should focus on entering complete information. Accounts and tax teams should verify the fields that affect GST reporting. This maker-checker process is more reliable than waiting for a portal error or reconciliation difference to expose a setup problem.