GST E-Invoice for Agricultural Commodities: Complete Compliance Guide

Whether a given agricultural-commodity trade falls under GST e-invoice depends on two separate questions: (1) is the commodity itself taxable under GST? and (2) is the supplier's aggregate turnover above the e-invoice turnover threshold? Confusing these two is the most common compliance error we see in agri-trade.

Many unprocessed agricultural products are GST-exempt; processed and branded agri products are usually taxable. And e-invoice applies to B2B supplies by registered persons above the turnover threshold (Rs 5 crore under the current framework, with the threshold having been progressively lowered over time). Both conditions must be satisfied before e-invoice is mandatory for a transaction.

Schedule II and the GST exemption notification exempt raw, unprocessed agricultural produce — paddy, wheat, raw vegetables and fruits, raw cereals and pulses sold un-branded, unbranded whole spices, raw oilseeds, raw cotton, fresh milk — from GST. A sale of raw paddy from a farmer or trader to a miller is typically exempt.

The line is processing and branding. Branded and packaged rice, packaged atta/flour, edible oils, branded spices, ghee, sugar, tea, and processed foods are taxable (most at 5% or 12%, some at 18%). The moment an agricultural product is processed, packaged, or branded, it usually leaves the exemption and the GST chain — including e-invoice, where applicable — begins.

GST e-invoice is not a separate invoice the government issues. It is a reporting mechanism: the supplier's accounting/ERP system generates the invoice JSON, pushes it to the Invoice Registration Portal (IRP), the IRP validates it against the GSTN, and returns an Invoice Reference Number (IRN) plus a QR code. The IRN must be printed on the invoice; without it the invoice is not legally valid for an e-invoice-applicable transaction.

IRN generation must happen before the invoice is issued to the buyer. For a typical B2B agri-supply — say, branded packaged rice from a processor to a distributor — the processor's ERP calls the IRP API, gets the IRN, then issues the invoice. The buyer uses this IRN-tagged invoice for their input tax credit (ITC) claim.

E-invoice applies to registered persons whose aggregate turnover in any of the previous financial years exceeds the notified threshold (Rs 5 crore currently, lowered progressively from the original Rs 500 crore). A small commodity trader below the threshold need not generate IRNs even on taxable B2B supplies; a large processor above the threshold must.

Timing matters: IRN must be obtained at the time of invoice creation, with a 24-hour / 30-day window for reporting depending on the turnover band (the 30-day window applies to taxpayers above Rs 100 crore from the relevant date). Late reporting invalidates the invoice for the buyer's ITC, which is why the IRN call is built into invoice creation, not done as an afterthought.

Three rules make this manageable. First, classify every SKU in your catalogue against the GST exemption list up front — not at invoice time. The raw-vs-processed line is the dominant compliance decision and should be settled once, in your item master.

Second, build the IRN call into the invoicing workflow, not as a manual post-step. Direct API integration with an IRP (there are several IRPs: NIC, and others) returns the IRN at invoice creation. Mandi Sathi-style procurement systems integrate this so buyers get ITC-valid invoices automatically.

Third, keep the turnover threshold monitored. A growing agri-trading firm that crosses the threshold mid-year becomes e-invoice-liable from the notified date — being unprepared creates a wave of invalid invoices that affect the buyer's ITC and relationships. Confirm threshold, exemption classification, and IRP integration with your CA/GST counsel; this guide is an operational overview, not legal advice.