GST, e-Invoice and e-Way Bill for Aerospace Dispatch in India

The three documents behind every compliant dispatch

When an aerospace component leaves a shop floor in Bengaluru bound for a prime, a public sector unit or an export gateway, three GST artefacts have to line up before the truck moves. The first is the tax invoice itself. The second is the e-invoice, more precisely the Invoice Reference Number, or IRN, that the government portal returns after the invoice is reported. The third is the e-way bill, which authorises the physical movement of the goods above the prescribed value.

These are not three copies of the same thing. They are three distinct compliance events that must be internally consistent. If the invoice says one HSN code and quantity, the IRN must reflect it, and the e-way bill must match both, along with the transporter and vehicle details. A mismatch is not a cosmetic problem. It invites detention of goods in transit, denial of input tax credit to your customer, and a stack of reconciliation work no one wants.

For aerospace and defence suppliers the stakes are higher than for ordinary manufacturing, because the parts are high value, the customers are exacting, and the movements often cross into special zones or job-work loops. Getting the paperwork right on the first pass is a service-level commitment to your customer, not merely a tax formality. Firms that standardise this on an aerospace and defence ERP software platform simply make fewer of these errors, because the three documents are generated from one shared record.

e-Invoicing and the IRN explained

e-Invoicing does not mean generating an invoice in a PDF and emailing it. It means reporting the invoice in a defined schema to the Invoice Registration Portal, which validates it and returns a unique Invoice Reference Number together with a signed QR code. Only after that reporting is the invoice legally valid for a business that falls within the e-invoicing turnover threshold. The QR code and IRN then travel with the document.

The mechanics matter for dispatch teams. The IRN is generated per invoice, and once generated it cannot simply be edited; a wrong invoice has to be cancelled within the permitted window and reissued. That places a premium on getting the data right before reporting, not after. The fields that most often trip up aerospace suppliers are the HSN code, the unit of measure, the place of supply and the treatment flag for special supplies such as those to a special economic zone.

Because the IRN process is unforgiving of after-the-fact edits, the discipline that pays off is validating the invoice data at source. When part masters carry the correct HSN and unit of measure, and when customer masters carry the correct place of supply and special-zone status, the IRN comes back clean the first time. The official portal at gst.gov.in remains the authoritative reference for schema and thresholds, and it is worth confirming current turnover thresholds there rather than relying on memory. Our dedicated page on aerospace GST, e-invoice and e-way bill automation walks through the field-level setup in detail.

The e-way bill: authorising the movement

The e-way bill is the document that legitimises the physical transport of goods whose consignment value exceeds the prescribed limit. It captures who is sending, who is receiving, what is moving, its value, and crucially the transporter and vehicle. It carries its own validity period keyed to the distance to be covered, and it must be updated if the vehicle changes mid-journey.

Two features of the e-way bill regularly catch aerospace dispatch teams. First, the value threshold and the state-level rules around it mean not every movement needs a bill, but high-value aero parts almost always cross it, so treat the bill as the default. Second, the e-way bill and the e-invoice can be generated together, with the e-invoice system able to pass details through so the e-way bill is not keyed a second time. Doing them together, from the same data, is the single biggest error-reduction move available.

Where movements are complex, for example a part travelling to a job-worker and back, or a consignment routed through a hub, the e-way bill discipline compounds. Each leg is its own authorised movement with its own validity. A system that understands the leg structure, rather than treating every dispatch as a simple A to B, prevents the classic failure of an expired bill on a part that sat longer than expected at an intermediate step. Suppliers running an aerospace ERP in Peenya or similar location deployment typically model these legs explicitly.

HSN classification for aerospace parts

Everything downstream depends on classifying the goods correctly under the Harmonised System of Nomenclature. The HSN code determines the applicable rate, informs the documentation and, when wrong, is one of the first things a scrutiny picks up. Aerospace parts sit across several chapters depending on what they are, which makes casual classification risky.

The table below is an orientation aid, not a ruling. Classification depends on the specific article, its material and its function, and the authoritative position is always the tariff and the notes that govern it. Treat this as a prompt to classify deliberately rather than as a substitute for that work.

The practical discipline is to fix HSN at the part master level, decided once by someone competent, and then let every invoice inherit it. That removes the temptation for a dispatch clerk to guess under time pressure. When HSN lives in the master data of an aerospace and defence ERP in Bangalore deployment, the code is consistent across every dispatch and every return, which is exactly what a clean audit needs.

SEZ supplies and zero-rating

A significant share of India's aerospace ecosystem sits inside special economic zones, including parts of the cluster around Devanahalli. Supplies to a unit or developer in a special economic zone are treated as zero-rated supplies, which means the supply can be made without payment of tax under a bond or letter of undertaking, or with payment of tax followed by a refund. The commercial benefit is real, but it is conditional.

The conditions are where suppliers slip. Zero-rating for an SEZ supply depends on the goods being for authorised operations, on the correct endorsement by the specified officer, and on the invoice and e-way bill carrying the right flags so the transaction is reported as an SEZ supply rather than an ordinary one. Get the flag wrong on the e-invoice and you have reported a taxable supply that you intended to be zero-rated, which then needs correction.

• Customer master accuracy: the receiving unit correctly marked as an SEZ unit or developer so every document inherits the right treatment.
• LUT or bond tracking: a valid letter of undertaking or bond in force so supplies can move without tax payment where that route is chosen.
• Endorsement capture: the specified officer's endorsement retained against the transaction as evidence for any refund claim.
• Consistent flagging: the SEZ treatment reflected identically on the invoice, the IRN and the e-way bill.

Because zero-rating hinges on these details being right and consistent, it is a prime example of where automation removes risk. When the customer master carries the SEZ status, every document downstream inherits the correct treatment automatically, and the letter of undertaking validity can be tracked so it never lapses unnoticed. Suppliers near the aerospace park often align this with a aerospace ERP in Devanahalli rollout so SEZ handling is native to the system.

Job-work and ITC-04 in aerospace supply chains

Aerospace manufacturing is a job-work-intensive business. A part may leave your premises for heat treatment, then for a special process such as plating or non-destructive testing, then return for final machining, all before it is a finished good. Under GST, sending goods to a job-worker and receiving them back is governed by specific provisions, and the movement is reported in the ITC-04 return.

The core idea is that inputs or capital goods sent for job-work can move without being treated as a supply, provided they return within the prescribed period, or are supplied directly from the job-worker's premises where permitted. If they do not return in time, the original despatch can be deemed a supply, with tax consequences. ITC-04 is the mechanism through which this movement is declared, capturing goods sent and goods received back within the period.

For aerospace suppliers running multiple parallel job-work loops, the tracking burden is significant. Each challan under which goods went out has to be reconciled against the goods that came back, within the clock, across many vendors. This is a natural fit for automation: the system that issues the delivery challan can hold the return clock, flag ageing job-work, and assemble the ITC-04 data without manual collation. Our aerospace procurement software overview describes how outbound job-work and inbound receipts are tied together so nothing ages silently.

How ERP automates the dispatch compliance chain

The recurring theme across e-invoicing, e-way bills, HSN, SEZ handling and job-work is that each is a data problem with a hard consistency requirement. That is exactly the class of problem an enterprise system solves well. Elite Tech Corporation implements configured Zoho platforms with custom AWS components rather than selling a fixed defence product, which means the GST logic is fitted to how your dispatch desk actually works instead of forcing your process to fit a rigid tool.

In a well configured deployment, a single dispatch event drives the whole chain:

• One source of truth: HSN, unit of measure, place of supply and SEZ status live in master data, so the invoice is right before it is reported.
• Automated IRN: the invoice is reported to the portal and the IRN and QR code return without re-keying.
• Linked e-way bill: the e-way bill is generated from the same data, with transporter and vehicle details, and its validity is tracked.
• SEZ and export treatment: zero-rating flags, letter of undertaking validity and endorsements are handled by rule, not by memory.
• Job-work control: outbound challans, return clocks and ITC-04 data are maintained continuously.
• Reconciliation and reporting: the data needed for returns is assembled from live transactions rather than rebuilt each period.

The result is faster dispatch with fewer detentions, cleaner input tax credit for your customers, and a dramatically lighter compliance load at return time. Because the same platform also handles production and traceability, GST compliance stops being a separate silo and becomes a by-product of running the business correctly. Firms adopting this often begin with our aerospace ERP implementation services to map their exact dispatch and job-work flows before go-live.

A practical readiness checklist

Before treating dispatch compliance as solved, it is worth pressure-testing the basics. The failures that cause detained trucks and blocked credits are almost always mundane data gaps rather than exotic legal questions. A short readiness review usually surfaces them quickly.

Ask whether every part has a fixed, competent HSN classification in the master rather than a value guessed at dispatch. Ask whether every customer master correctly reflects place of supply and, where relevant, SEZ status. Ask whether the letter of undertaking is current and whose job it is to renew it. Ask whether outbound job-work challans are reconciled against returns on a clock rather than at year end. Ask whether the e-invoice and e-way bill are generated together from one dataset or keyed twice by hand.

Where the answers reveal manual steps and duplicated keying, those are precisely the points where a configured system removes both effort and risk. Defence PSU suppliers in particular, who dispatch to demanding customers under tight documentation expectations, benefit from tightening this early, which our ERP for defence PSU suppliers overview addresses directly. When you are ready to map your own flows, the fastest path is simply to talk to Elite Tech Corporation.

Conclusion

GST compliance for aerospace dispatch is not one obligation but a chain of interlocking ones: the invoice, the IRN, the e-way bill, the HSN behind them, the special treatment for SEZ supplies, and the parallel discipline of job-work reporting. Each link is simple in isolation and fails in combination, usually because the same data was keyed more than once and drifted. The suppliers who dispatch fastest and get scrutinised least are the ones who fixed their master data, generated their documents from a single source, and let the system hold the clocks that humans forget. That is a solvable problem, and solving it turns compliance from a recurring fire drill into a quiet, reliable by-product of good operations.