Supply to SEZ under GST creates several data-validation requirements for Indian billing and ERP software. A system must identify the SEZ recipient, validate authorised operations, record the correct tax treatment and maintain refund evidence.
For developers building invoicing platforms, accounting software or enterprise resource planning (ERP) systems, these requirements should be part of the transaction workflow rather than manual checks performed after filing.
This tutorial explores a practical way to model SEZ GST compliance using TypeScript.
1. Understand the GST rules before writing code
Two provisions are particularly important.
Section 7(5)(b) of the IGST Act, 2017
A supply to or by an SEZ developer or unit is treated as an interstate supply. This applies even when the supplier and recipient are located in the same state.
Section 16(1)(b) of the IGST Act
A supply to an SEZ developer or unit qualifies as zero-rated when it is made for authorised operations.
These are separate checks:
- Interstate classification identifies the nature of the transaction.
- Authorised operations determine whether the SEZ supply qualifies for zero-rated treatment.
A billing application should not combine these two conditions into one boolean field.
Official reference: IGST Act – Section 16.
2. Design the SEZ recipient data model
Start by separating recipient information from transaction information.
A basic TypeScript model could look like this:
type RecipientKind = | "sez_unit" | "sez_developer" | "regular_business"; type VerificationStatus = | "pending" | "verified" | "rejected"; interface SEZRecipient { recipientId: string; gstin: string; legalName: string; recipientKind: RecipientKind; approvalReference?: string; verificationStatus: VerificationStatus; } interface SEZSupply { invoiceId: string; recipientId: string; supplyValuePaise: number; authorisedOperationsStatus: VerificationStatus; supplyDescription: string; invoiceDate: string; } This structure separates three concepts:
- Who receives the supply?
- Has the recipient's relevant SEZ information been verified?
- Is there supporting evidence that the supply relates to authorised operations?
Keeping these fields separate makes the application easier to audit.
3. Build an authorised-operations validation workflow
One important software-design mistake is marking every SEZ invoice as zero-rated automatically.
Instead, use an explicit validation stage.
interface ValidationResult { interstateSupply: boolean; zeroRatedCandidate: boolean; requiresReview: boolean; reasons: string[]; } function validateSEZSupply( recipient: SEZRecipient, supply: SEZSupply ): ValidationResult { const reasons: string[] = []; const isSEZ = recipient.recipientKind === "sez_unit" || recipient.recipientKind === "sez_developer"; if (!isSEZ) { reasons.push("Recipient is not classified as an SEZ entity."); } if (recipient.verificationStatus !== "verified") { reasons.push("SEZ recipient verification is incomplete."); } if (supply.authorisedOperationsStatus !== "verified") { reasons.push("Authorised operations evidence needs review."); } const zeroRatedCandidate = isSEZ && recipient.verificationStatus === "verified" && supply.authorisedOperationsStatus === "verified"; return { interstateSupply: isSEZ, zeroRatedCandidate, requiresReview: !zeroRatedCandidate, reasons }; } This is an illustrative application-level validation, not a legal eligibility engine.
The final tax treatment should be approved through the applicable legal checks and documentation.
4. Model LUT and IGST refund routes separately
Developers should avoid hardcoding the assumption that all SEZ suppliers can choose any refund route.
The current Section 16 framework distinguishes:
LUT route – Section 16(3)
The registered supplier can make qualifying zero-rated supplies without payment of IGST under a Bond or Letter of Undertaking and claim a refund of eligible unutilised ITC.
IGST-payment route – Section 16(4)
The Government can notify the eligible classes of persons and goods or services for payment of IGST and refund of the tax paid.
Notification No. 05/2023-Integrated Tax dated 26 October 2023 covers eligible suppliers making supplies to SEZ developers or units for authorised operations, subject to specified exclusions.
The Finance (No. 2) Act, 2024 amended the refund provisions with effect from 1 November 2024.
A software system should maintain versioned tax configurations rather than permanently embedding notification conditions in application code.
Example:
type RefundRoute = | "lut_without_igst" | "igst_paid"; interface RefundConfiguration { route: RefundRoute; effectiveFrom: string; effectiveTo?: string; legallyReviewed: boolean; eligibilityReference: string; } The application's refund-route selection should depend on a current, legally reviewed configuration.
5. Design an invoice and document checklist
An SEZ invoice is not just a monetary record. The associated supporting documentation matters during refund processing.
A practical document-management module should track:
| Document | Purpose |
|---|---|
| GST registration | Verify supplier and recipient |
| SEZ approval | Establish SEZ status |
| Purchase order | Record the commercial transaction |
| Tax invoice | Support outward supply reporting |
| LUT acknowledgement | Support the LUT route |
| Delivery documents | Support goods movement |
| SEZ endorsement | Support receipt for authorised operations |
| ITC reconciliation | Support refund calculations |
Rule 89 of the CGST Rules prescribes evidence requirements for refund claims involving SEZ supplies.
For goods, the application should track evidence of admission into the SEZ. For services, it should track evidence of receipt for authorised operations.
The prescribed endorsement from the SEZ's specified officer should be stored against the relevant invoice or refund record.
Useful implementation features include:
- Document upload and version history.
- Invoice-to-purchase-order mapping.
- Evidence status tracking.
- Missing-document alerts.
- Refund application audit logs.
6. Build a reconciliation process
Before a refund application is prepared, software should compare:
- Outward supply invoice records.
- GST return reporting.
- Eligible ITC records.
- LUT and tax-payment details.
- SEZ endorsement records.
- Refund application values.
A mismatch should create a review task rather than an automatic adjustment.
For example, an invoice with a missing SEZ endorsement could be marked as:
PENDING_SEZ_EVIDENCE
This is better than allowing the refund workflow to proceed without the prescribed documentation.
7. Suggested application workflow
A useful architecture looks like this:
Create Recipient | v Verify SEZ Status | v Create Supply Invoice | v Check Authorised Operations | v Legal Eligibility Review | v Select Permitted Refund Route | v Collect Documents | v Reconcile GST Records | v Prepare Refund Application | v Compliance Review Each stage should have a timestamp, responsible user and supporting-document reference.
This provides a reliable audit trail when a refund application needs investigation.
8. Common software-design mistakes
Developers should avoid:
- Automatically assigning zero-rated status to every SEZ recipient.
- Combining interstate classification with zero-rated eligibility.
- Hardcoding old GST notification conditions.
- Allowing refund-route selection without checking current eligibility.
- Storing invoices without supporting endorsements.
- Modifying historical tax records without an audit trail.
- Treating a pending document as verified evidence.
A tax configuration layer with effective dates makes the application easier to update when government notifications change.
Conclusion
Supply to SEZ under GST requires more than generating an invoice with the correct tax classification.
Billing and ERP systems should separately manage SEZ recipient verification, authorised operations, refund-route eligibility, supporting documents and ITC reconciliation.
A well-designed workflow can reduce manual errors and help businesses maintain reliable GST records.
Further reading: Supply to SEZ Under GST – Detailed Guide by Delhi Tax Solutions.
AI disclosure: This article was prepared with AI assistance and checked against the cited statutory references. The publishing author should independently verify the legal interpretation and add relevant professional or implementation experience before publication.
Disclaimer: This is a software-design and general GST information guide, not personalised legal or tax advice.
