Goods and Services Tax and Indirect Tax Compliance

Introduction and context

Goods and Services Tax (GST) is a destination-based indirect tax imposed on the supply of goods and services. It replaced several central and state levies in India and introduced a technology-supported compliance model involving registration, tax invoices, input tax credit, returns, payment, reconciliation and audit trails. Tally.ERP 9 provides an accounting and reporting environment for recording GST transactions, but it does not replace the taxpayer’s legal responsibility to interpret the law, verify data or file accurate returns.

This chapter explains the conceptual and operational relationship between GST law and Tally.ERP 9. Menu names and statutory forms may differ by product release, country and government notification. Accordingly, users must verify current provisions, tax rates, thresholds, return formats and e-way requirements with the applicable tax authority.

Learning objectives

After studying this chapter, the learner should be able to:

1. Explain the structure and rationale of GST and distinguish intra-state, inter-state, import, export and reverse-charge transactions.
2. Configure GST registration, company details, ledgers, stock items, tax classifications and tax rates in Tally.ERP 9.
3. Record sales, purchases, advances, credit notes, debit notes and reverse-charge transactions.
4. Evaluate input tax credit, blocked credits, tax-period cut-off and documentation requirements.
5. Reconcile books with supplier data and portal-generated information.
6. Generate statutory reports and e-way-related information while recognising the limits of accounting software.
7. Design controls for compliance, governance, review and ethical reporting.

1. GST architecture and terminology

GST is generally collected through a dual model. Central GST (CGST) and State or Union Territory GST (SGST/UTGST) normally apply to an intra-state supply. Integrated GST (IGST) normally applies to an inter-state supply, imports and specified cross-border transactions. The classification depends primarily on the location of the supplier and the place of supply, not merely on the location of the customer’s billing address.

The principal accounting identity for a tax period can be expressed as:

This is a reporting identity, not permission to claim every tax amount recorded in the books. Output liability includes tax collected or otherwise payable; eligible ITC is restricted by statutory conditions, exclusions, reversals, utilisation rules and payment obligations. A negative result may represent a credit balance or refund position, subject to law.

Tax computation

For a taxable value V and an applicable GST rate r expressed as a decimal:

For an invoice where the taxable value is known and tax is charged separately, the total invoice value is:

For a tax-inclusive amount T:

These equations assume that the rate is uniform across the taxable components and that no discount, cess, exemption, rounding adjustment or special valuation rule changes the base. If a transaction contains multiple items or rates, each component must be calculated separately.

2. Place of supply and tax determination

The central professional judgement is determining the nature of supply. A typical decision process is:

1. Identify the supplier’s registered location and, where relevant, the place from which supply is made.
2. Identify the recipient’s status and location.
3. Determine the statutory place of supply, considering movement of goods, installation, services, exports, imports and special categories.
4. Compare supplier location with place of supply.
5. Select CGST plus SGST/UTGST or IGST.
6. Record the reason and supporting evidence.

For example, a registered supplier in Maharashtra selling goods delivered to a customer in Maharashtra will ordinarily record CGST and SGST. The same supplier delivering goods to Karnataka will ordinarily record IGST. A service transaction may produce a different result because statutory place-of-supply rules vary by service category.

A common error is selecting the tax type from the customer’s ledger alone. The delivery address, bill-to/ship-to structure, warehouse location, service performance and contractual terms may be decisive. Tally can automate tax calculation only after the legal classification has been correctly established.

3. GST configuration in Tally.ERP 9

Configuration should be performed in a controlled sequence. A reliable implementation separates master-data design from transaction entry.

3.1 Company-level settings

Enable GST for the relevant company and enter:

• State or Union Territory of registration;
• GSTIN and registration type;
• effective date of GST applicability;
• applicable tax-related features;
• invoice and voucher numbering preferences;
• e-invoice or e-way-related settings where supported by the licensed release and jurisdiction;
• correct financial year and books beginning date.

The registration type must reflect the taxpayer’s legal status, such as regular, composition or another permitted category. A composition taxpayer cannot be configured as though it were entitled to ordinary ITC and tax collection. Multiple registrations may require separate company structures, branches or ledgers, depending on reporting requirements.

3.2 Ledger design

Create separate ledgers for:

• taxable sales by relevant classification;
• exempt, nil-rated and non-GST supplies;
• purchases of goods and services;
• CGST, SGST/UTGST and IGST input and output accounts;
• reverse-charge tax payable;
• freight, discounts, advances and other valuation components;
• customers and suppliers with correct State and GSTIN information.

Ledger names should be consistent and searchable. A useful convention is to identify tax type and direction, for example “Input CGST—Goods” and “Output IGST—Services.” Excessive consolidation can obscure reconciliation; excessive fragmentation can make reporting difficult. The design should support statutory reporting, management analysis and audit review simultaneously.

3.3 Stock items and service masters

For goods, define units of measure, HSN/SAC classification, applicable rate, exemption status and, where needed, batch or serial details. For services, use service ledgers or service masters with SAC classification and correct rate. Rates must be maintained with effective dates where the software supports them; retrospective changes must not silently alter historical vouchers.

Classification is not merely a software field. HSN/SAC selection affects invoice disclosure, return reporting, analytics and sometimes rate determination. Where classification is uncertain, obtain documented professional or official guidance before mass transaction entry.

3.4 Tax hierarchy and voucher controls

Tax ledgers should be mapped to the appropriate tax type and jurisdiction. Voucher classes, invoice templates and narration standards should require relevant fields such as place of supply, GSTIN, HSN/SAC, quantity, taxable value, tax rate and tax amount. User permissions should prevent unauthorised alteration of masters after transactions have been posted.

4. Recording principal transaction types

Intra-state sale

A sale within the same State generally requires two components: CGST and SGST/UTGST. If taxable value is ₹100,000 and the total GST rate is 18%, the tax is ₹18,000, normally divided as CGST ₹9,000 and SGST ₹9,000 when the applicable split is equal.

The accounting effect is commonly:

• Debit customer: ₹118,000
• Credit sales: ₹100,000
• Credit output CGST: ₹9,000
• Credit output SGST: ₹9,000

The exact entry may vary according to inventory, invoice and accounting configuration.

Inter-state sale

An inter-state sale generally uses IGST. For the same taxable value and rate:

• Debit customer: ₹118,000
• Credit sales: ₹100,000
• Credit output IGST: ₹18,000

Purchase and input tax

A purchase invoice should be recorded only after checking supplier identity, invoice particulars, classification, rate, tax amount, receipt of goods or services and business purpose. Input ledgers should distinguish potentially eligible credit from blocked, exempt-related or otherwise ineligible tax where practical.

Credit and debit notes

A credit note may reduce taxable value or tax when legally permitted, for example for returns or post-sale discounts satisfying conditions. A debit note may increase consideration or tax. The original invoice reference, reason, date and reporting period must be retained. A note should not be used to conceal an error that requires correction through another statutory mechanism.

Advances and adjustments

Treatment of advances depends on the nature of supply and applicable rules. Tally users should not assume that an advance is always taxable or always outside the tax computation. Configure advance ledgers and adjustment procedures consistently, and reconcile advance balances to subsequent invoices.

Reverse charge

Under reverse charge, the recipient records tax payable even though the supplier may not charge GST in the normal manner. A compliant workflow is:

1. identify the transaction under the relevant reverse-charge provision;
2. record the expense or purchase and payable to the supplier;
3. calculate and record reverse-charge tax payable by tax type;
4. pay the liability through the permitted mechanism;
5. claim ITC only when all eligibility conditions are met;
6. report the transaction in the relevant returns and preserve evidence.

The accounting entry for reverse charge and the later ITC entry should be distinguishable. A frequent failure is claiming credit merely because a reverse-charge liability was calculated, without verifying payment and other conditions.

5. Input tax credit: legal logic and accounting control

ITC is a conditional statutory benefit. A practical eligibility framework asks whether:

• the recipient possesses a valid prescribed document;
• the supply has been received;
• the tax has been charged and appropriately reported by the supplier where required;
• the recipient has furnished the relevant return;
• the purchase is used in the course or furtherance of business;
• payment conditions and time limits are satisfied;
• the credit is not blocked or attributable to exempt or non-business use;
• reversals are made for cancellations, non-payment, credit notes or changes in use.

The distinction between book ITC and claimable ITC is essential. A purchase register may show ₹500,000 of tax, while only ₹455,000 is eligible after blocked credit, missing documents and proportionate reversal. Tally should support a reconciliation classification such as “eligible,” “pending,” “ineligible,” “reversal required” and “claimed.”

Credit utilisation is subject to statutory ordering and restrictions. Therefore, the simple net-liability identity does not by itself determine which credit can be set off against which output tax. The taxpayer must apply the current utilisation rules and maintain tax-type balances.

6. Reconciliation and statutory reporting

Reconciliation is a control process, not a one-time export. The purchase register should be compared with supplier-reported data or portal-generated statements for:

• GSTIN;
• invoice number and date;
• taxable value;
• tax type and amount;
• credit/debit notes;
• amendments;
• supply period;
• eligibility status.

A useful reconciliation classification is shown below.

Tally reports can provide purchase registers, sales registers, tax ledgers, exception reports and return summaries. However, the user must validate report periods, cancelled vouchers, back-dated entries, manual journals, opening balances and ledger classifications before uploading or transcribing statutory data.

A sound month-end close includes:

1. lock or review the period after authorised adjustments;
2. reconcile sales to invoices, inventory dispatches, receipts and general ledger totals;
3. reconcile purchases to goods received, supplier statements and portal data;
4. review reverse-charge, advances, credit notes and amendments;
5. test tax rates and place-of-supply exceptions;
6. identify negative balances, unusual rates and manual postings;
7. obtain preparer and reviewer sign-off;
8. archive reports, workings and source documents.

7. E-way-related information and movement controls

An e-way bill is generally associated with the movement of goods above prescribed conditions and thresholds. Its applicability depends on jurisdiction, transaction type, consignment value, transporter information, distance, exemptions and current notifications. It is not automatically required for every invoice and is not a substitute for a tax invoice.

Before generating e-way-related information, verify:

• document type and number;
• document date;
• supplier and recipient GSTIN or relevant unregistered-person details;
• dispatch and delivery addresses;
• HSN, quantity, unit and taxable value;
• tax rate and tax amount;
• transporter ID, vehicle number and transport mode;
• validity period and permitted extensions.

The accounting system may generate data or an interface file, but the taxpayer remains responsible for portal validation, authentication, corrections and retention. Differences between invoice data and e-way data create enforcement, reconciliation and audit risks.

8. Applied case: Meridian Components (illustrative)

Background

Meridian Components, a registered manufacturer in Gujarat, sells electrical components domestically. It purchases inputs from Gujarat and Maharashtra, contracts a security service subject to reverse charge under applicable rules, and maintains its books in Tally.ERP 9.

Problem

At month-end, the accounts team reports output GST of ₹720,000 and input GST of ₹610,000. However, the purchase register includes ₹40,000 of blocked credit, ₹25,000 relating to invoices absent from supplier data, and ₹15,000 of duplicate postings. A Maharashtra purchase was incorrectly recorded as CGST and SGST instead of IGST. The reverse-charge liability of ₹12,000 was calculated but not separately tracked for payment.

Analysis

The apparent credit cannot be accepted without classification. Eligible input tax before resolving the missing invoices is:

The ₹25,000 absent from supplier data is placed in a pending category rather than automatically claimed. The Maharashtra purchase must be corrected because supplier location and place of supply indicate an inter-state transaction. The reverse-charge amount must be recorded as tax payable and handled under the applicable payment and credit rules.

Approach and solution

The controller first freezes the period for unauthorised edits, exports voucher-level reports and corrects the tax classification through an authorised amendment. Separate ledgers are created for eligible, blocked and reverse-charge-related tax. The purchase reconciliation identifies the duplicate and requests corrected supplier reporting for the missing invoices. A reviewer then compares the revised return summary with sales, purchase, tax and bank records.

If the ₹25,000 missing amount is later validated and becomes eligible, the claim is considered in the legally permitted period; otherwise it remains excluded. The provisional net liability before the pending amount is:

This figure is an analytical result only. Actual payment may differ because of tax-type utilisation order, reverse-charge payment treatment, interest, late fees, amendments and other statutory requirements.

Outcome

Meridian’s corrected records distinguish output tax, eligible ITC, blocked ITC, pending documents and reverse-charge liability. The company produces a documented reconciliation file and reduces the risk of duplicate credit, incorrect tax-type reporting and unsupported claims.

Learning points

The case demonstrates that software accuracy depends on master-data accuracy, that portal matching does not prove legal eligibility, and that reconciliation must be linked to tax-type balances and source documents. It also illustrates why review controls are necessary even when automated tax calculation is enabled.

9. Governance, ethics and professional judgement

Indirect tax compliance is an area of professional ethics. Deliberately suppressing sales, creating fictitious purchase invoices, misclassifying inter-state transactions, claiming credit without receipt, manipulating dates or generating false movement documents may produce short-term accounting benefits but exposes the entity and professionals to tax, interest, penalty, audit and reputational consequences.

Governance should include segregation of duties: one person maintains masters, another records transactions, a reviewer approves tax adjustments and an authorised officer files returns. Access logs, voucher alteration reports, backup procedures and retention schedules should be documented. Reconciliation differences should be resolved transparently rather than force-posted to a suspense account.

AI-assisted coding, anomaly detection and document extraction may help identify duplicate invoices, unusual tax rates or missing GSTINs. Such tools can misread invoices, infer incorrect classifications or reproduce biased historical coding. Human review, source-document verification, explainable exception reports and protection of taxpayer data remain mandatory. Automation should strengthen—not displace—professional accountability.

10. Challenges and limitations

Several practical limitations affect Tally-based compliance:

• frequent statutory changes may outpace configuration updates;
• legacy data may contain incomplete GSTINs or incorrect State details;
• one business may have multiple registrations and complex stock transfers;
• portal statements may reflect timing differences and supplier amendments;
• tax-inclusive prices and discounts may create rounding differences;
• manual journals can bypass invoice-level controls;
• software reports cannot resolve legal ambiguity about place of supply or classification;
• migration from older releases may alter masters, voucher numbering or tax mappings.

Best practice is to maintain a change register, test configurations in a copy of the company, preserve pre- and post-adjustment reports, obtain current legal guidance and conduct periodic internal audits.

Best-practice implementation checklist

Before go-live, confirm registration and company State; map ledgers and tax types; validate HSN/SAC and rates; test intra-state, inter-state, exempt, reverse-charge, credit-note and export scenarios; configure invoice fields; restrict permissions; establish backup and retention procedures; and document reviewer responsibilities.

For each reporting period, reconcile books to portal data, investigate exceptions, review tax-type balances, validate e-way-related information, approve adjustments, calculate statutory dues and retain evidence of filing and payment. After filing, compare the filed data with the books and record subsequent amendments in a controlled manner.

Chapter Summary

GST compliance combines legal interpretation, accounting classification, technology configuration and evidence-based review. CGST with SGST/UTGST generally applies to intra-state supplies, while IGST generally applies to inter-state supplies and specified imports or exports. Correct determination depends on supplier location, place of supply and transaction facts. Tally.ERP 9 can calculate and report tax only when company settings, ledgers, classifications, rates and voucher data are correctly designed.

Input tax credit is conditional and must be distinguished from tax merely recorded in purchase books. Reverse-charge transactions require separate liability recognition and careful payment and credit treatment. Reconciliation should compare invoice-level data with supplier and portal information, classify exceptions and prevent unsupported or duplicate claims. E-way information requires accurate movement and document details but does not replace legal review. Strong compliance depends on segregation of duties, audit trails, current configuration, ethical conduct and human oversight of automation.

Key Terms

GST: A destination-based tax on the supply of goods and services.

CGST: Central component of GST generally charged on intra-state supplies.

SGST: State component of GST generally charged on intra-state supplies.

UTGST: Union Territory component of GST in applicable territories.

IGST: Integrated GST generally charged on inter-state supplies and specified imports.

Supply: A taxable transaction involving goods, services or both.

Place of supply: Statutory location used to determine tax jurisdiction.

Taxable value: Amount on which GST is calculated.

HSN: Harmonised classification code for goods.

SAC: Service classification code.

GSTIN: Goods and Services Tax Identification Number.

Input tax credit: Eligible credit of GST paid on business inputs.

Reverse charge: Mechanism under which the recipient pays specified GST.

Tax invoice: Prescribed document evidencing a taxable supply.

Credit note: Document reducing consideration or tax under permitted conditions.

Debit note: Document increasing consideration or tax under permitted conditions.

E-way bill: Electronic document associated with specified movement of goods.

Reconciliation: Comparison of accounting records with external or portal data.

Blocked credit: Tax credit restricted by statute or transaction conditions.

Tax period: Prescribed period for reporting, payment and reconciliation.

Review Questions

Short Answer Questions

1. Distinguish CGST, SGST/UTGST and IGST.
2. Why is place of supply important in GST accounting?
3. What is the difference between book ITC and eligible ITC?
4. State two controls required before generating e-way-related information.
5. Why should reverse-charge tax be tracked separately?

Long Answer Questions

1. Explain the architecture of GST and its implications for configuring Tally.ERP 9.
2. Describe a complete month-end GST reconciliation process.
3. Explain the accounting and compliance treatment of intra-state, inter-state and reverse-charge transactions.
4. Discuss master-data design, user permissions and audit trails as GST governance mechanisms.
5. Evaluate the benefits and limitations of using Tally.ERP 9 for statutory GST reporting.

Analytical / Application Questions

1. A supplier in Karnataka delivers goods to a registered customer in Tamil Nadu. Explain the tax classification, required master data and invoice checks before posting the transaction.
2. A purchase register contains tax of ₹300,000, including ₹20,000 blocked credit and ₹10,000 duplicate credit. Calculate the provisional eligible amount and explain the additional checks required.
3. A company’s portal data shows supplier-reported invoices that are absent from its books. Design a control procedure that prevents both omission of legitimate credit and unsupported claims.

Multiple Choice Questions with Answers

Question 1

Which tax is generally applicable to an inter-state supply of goods in India?

A. CGST only

B. SGST only

C. IGST

D. UTGST only

Correct Answer: C. IGST

Question 2

If the taxable value is ₹100,000 and the GST rate is 18%, what is the GST amount, assuming tax is charged separately?

A. ₹1,800

B. ₹18,000

C. ₹82,000

D. ₹118,000

Correct Answer: B. ₹18,000

Question 3

Which factor is most important in determining whether CGST plus SGST or IGST applies?

A. The customer’s credit limit

B. The invoice font

C. Supplier location and statutory place of supply

D. The payment method

Correct Answer: C. Supplier location and statutory place of supply

Question 4

Which statement best describes input tax credit?

A. All tax appearing on purchase invoices is automatically claimable

B. It is a conditional credit subject to legal eligibility requirements

C. It applies only to exempt supplies

D. It is unrelated to supplier reporting

Correct Answer: B. It is a conditional credit subject to legal eligibility requirements

Question 5

Under reverse charge, who generally discharges the specified GST liability?

A. The recipient

B. The transporter only

C. The bank

D. The software vendor

Correct Answer: A. The recipient

Question 6

A purchase register shows ₹610,000 input tax, including ₹40,000 blocked credit and ₹15,000 duplicate credit. What is the provisional eligible amount before other checks?

A. ₹555,000

B. ₹575,000

C. ₹595,000

D. ₹665,000

Correct Answer: A. ₹555,000

Question 7

Which reconciliation status indicates that a document appears in portal data but not in the books?

A. Books only

B. Portal only

C. Matched

D. Duplicate only

Correct Answer: B. Portal only

Question 8

What is the primary purpose of an HSN or SAC code in GST processing?

A. To classify goods or services for reporting and tax treatment

B. To identify the employee approving payment

C. To calculate bank interest

D. To replace the GSTIN

Correct Answer: A. To classify goods or services for reporting and tax treatment

Question 9

Which statement about an e-way bill is correct?

A. It replaces the tax invoice

B. It is required for every invoice without exception

C. Its applicability depends on current rules and movement conditions

D. It proves that ITC is legally eligible

Correct Answer: C. Its applicability depends on current rules and movement conditions

Question 10

Which control most directly reduces the risk of unauthorised GST master-data changes?

A. Removing all invoice numbers

B. User permissions and alteration audit trails

C. Using only cash transactions

D. Deleting old vouchers monthly

Correct Answer: B. User permissions and alteration audit trails