Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A mid-tier Indian electronics manufacturing services (EMS) beneficiary — at the Rs 500 crore-plus annual revenue scale that sits comfortably above the CBIC Notification 10/2023 dated 10-May-2023 e-invoicing threshold of Rs 5 crore aggregate turnover in any preceding financial year from 2017-18 onwards, effective 01-August-2023 — must reconcile a per-invoice IRN generation log via GSP integration against the ERP outward supplies register, an IRN failure log covering the 30-day IRN generation window (per GSTN Advisory dated 05-November-2024 for Rs 10 crore-plus taxpayers) and the 24-hour cancellation window applicable to all taxpayers, a credit note IRN linkage register that binds each Section 34 CGST credit note IRN back to the original invoice IRN through the mandatory reference field in the FORM GST INV-01 credit note schema, and the GSTN-auto-populated FORM GSTR-1 outward supplies return filed by the 11th of the month succeeding the tax period under Section 37 CGST. Missing any hop can render the affected invoice invalid under Rule 48(5) of the CGST Rules 2017, expose the recipient's input tax credit claim to denial under Section 16(2)(a) read with Rule 36(4), and attract penalty exposure to the supplier under Section 122(1) (Rs 10,000 or the tax evaded, whichever is higher) and Section 122(3)(e) (up to Rs 25,000 for failure to issue an invoice in accordance with the Act or rules). At the mid-tier EMS scale of 15,000 to 20,000 monthly B2B invoices to a mixed customer base of consumer electronics OEMs and IT hardware OEMs, the per-invoice reconciliation cannot be run manually and requires a purpose-built reconciliation surface.
Build a per-invoice IRN status log keyed to the ERP outward supplies register, capturing invoice date, invoice number, GSP submission timestamp, IRP response timestamp, IRN, QR code payload, IRN age from invoice date (30-day tracker), and cancellation window countdown (24-hour tracker) per invoice. Bind the credit note IRN linkage register to the original invoice IRN through the credit-note reference field. Run a three-way tie-out between the ERP outward supplies register (source of truth), the IRP-issued IRN log (invoices that carry a valid IRN), and the GSTN-auto-populated FORM GSTR-1 (what GSTN believes the supplier reported) each month before the 11th-day filing deadline under Section 37 CGST. Track IRN generation failures (portal downtime rejections, schema validation rejections for missing mandatory fields, IRP rejection for post-30-day submission attempts) with a retry-and-escalation register. Track cancellation window overruns with a Section 34 credit-note-plus-fresh-invoice remediation pathway. Compute the Section 122 penalty exposure quantification per invalid invoice for the audit trail. Bind the entire IRN reconciliation surface to the monthly GSTR-1 file and to the recipient's downstream GSTR-2B match risk on high-volume OEM customer accounts.
Per-invoice IRN status log with invoice date, invoice number, ERP outward supplies register row reference, GSP submission timestamp, IRP response timestamp, IRN (64 characters), QR code payload, IRN age from invoice date (30-day tracker), cancellation window countdown (24-hour tracker), and status flag (IRN generated / IRN pending / IRN failed / IRN cancelled / IRN cancellation window elapsed); GSP selection register (ClearTax / Cygnet / Perennial / IRIS or other approved provider) with the API endpoint reference and the token refresh cadence; ERP outward supplies register with the invoice JSON payload schema mapping to FORM GST INV-01 mandatory fields (supplier GSTIN, recipient GSTIN, invoice number, invoice date, line item HSN, quantity, taxable value, IGST or CGST-plus-SGST rate and amount, place of supply, buyer name and address); IRN generation failure register with failure reason categorisation (portal downtime, schema validation, post-30-day rejection, GSP token expiry, network error); IRN cancellation register with the 24-hour cancellation window elapsed flag and the Section 34 CGST credit-note-plus-fresh-invoice remediation pathway; credit note IRN linkage register with the mandatory original invoice IRN reference field; GSTN-auto-populated FORM GSTR-1 register with the three-way tie-out to the ERP outward supplies register and the IRP-issued IRN log; Section 122 penalty exposure quantification schedule with invalid invoice count and taxable value impact; monthly GSTR-1 review checklist bound to the 11th-day filing deadline under Section 37 CGST; recipient GSTR-2B match risk register for high-volume OEM customer accounts.
A monthly e-invoicing reconciliation pack: the per-invoice IRN status log with the 30-day generation window tracker and the 24-hour cancellation window tracker; the IRN generation failure register with categorised failure reasons and retry-or-escalation status; the credit note IRN linkage register with the one-to-many mapping from original invoice IRN to downstream credit note IRNs; the three-way tie-out between the ERP outward supplies register, the IRP-issued IRN log, and the GSTN-auto-populated FORM GSTR-1; the Section 122 CGST penalty exposure quantification for any invalid invoices in the period; the monthly GSTR-1 review checklist bound to the 11th-day filing deadline under Section 37 CGST; the recipient GSTR-2B match risk register for high-volume OEM customer accounts flagged for supplier-side outreach; and the audit trail linking each IRN, credit note IRN and GSTR-1 line back to the ERP outward supplies register row for period-end statutory audit substantiation.
A mid-tier Indian electronics manufacturing services (EMS) beneficiary at the scale of an entity running consumer electronics component and industrial electronics assembly operations across a two-plant footprint in Faridabad Haryana and Ghaziabad Uttar Pradesh — with an FY 2026-27 annual EMS output of approximately Rs 850 crore, well above the CBIC Notification 10/2023 dated 10-May-2023 e-invoicing threshold of Rs 5 crore aggregate turnover in any preceding financial year from 2017-18 onwards effective 01-August-2023 — closes its monthly outward supplies return under the GSTN e-invoicing regime with four reconciliation surfaces simultaneously in view: a per-invoice Invoice Reference Number (IRN) status log across roughly 15,000 to 20,000 monthly B2B invoices, an IRN failure log covering the 30-day generation window and the 24-hour cancellation window, a credit note IRN linkage register that binds each Section 34 CGST credit note back to its original invoice, and the GSTN-auto-populated FORM GSTR-1 outward supplies return filed by the 11th of the month succeeding the tax period. This is e-invoicing electronics manufacturer Rs 5 crore IRN reconciliation at operating scale for a mid-tier EMS running high monthly invoice volumes, and the discipline that keeps the ERP outward supplies register, the IRP-issued IRN log, the credit note linkage register and the GSTR-1 auto-population simultaneously clean is what separates a supplier whose downstream OEM customers receive fully ITC-valid invoices from one that spends the following month unwinding Section 16(2) denial notices raised against its OEM customers.
The reconciliation in one paragraph
An EMS beneficiary at the Rs 500 crore-plus annual revenue scale runs a four-surface reconciliation cascade each month. Surface one is the per-invoice IRN status log keyed to the ERP outward supplies register — invoice date, invoice number, GSP submission timestamp, IRP response timestamp, the 64-character IRN, the QR code payload, an IRN age tracker against the 30-day generation window (per GSTN Advisory dated 05-November-2024 for taxpayers at Rs 10 crore-plus aggregate annual turnover), and a cancellation countdown against the 24-hour cancellation window applicable to all taxpayers. Surface two is the IRN failure log — categorised by failure reason (portal downtime, schema validation rejection for missing mandatory fields, IRP rejection for post-30-day submission attempts, GSP token expiry, network error) with a retry-or-escalation state per failure. Surface three is the credit note IRN linkage register — every Section 34 CGST credit note issued against an original e-invoice must itself carry its own IRN and must reference the original invoice’s IRN in the mandatory reference field of the FORM GST INV-01 credit note schema, so that GSTN can bind the credit note back to the original invoice for downstream GSTR-1 and recipient GSTR-2B auto-population. Surface four is the three-way tie-out between the ERP outward supplies register (the source-of-truth), the IRP-issued IRN log (the invoices that carry a valid IRN), and the GSTN-auto-populated FORM GSTR-1 (what GSTN believes the supplier reported), reviewed and corrected before the monthly Section 37 CGST filing deadline of the 11th day of the month succeeding the tax period (the 13th day for QRMP quarterly filers). Terra Insight’s electronics manufacturing cluster hub situates the e-invoicing discipline within the broader PLI Semiconductor, PLI LSEM, PLI IT Hardware, PLI White Goods and RoDTEP surface that a mid-tier EMS runs in parallel.
What the scenario looks like in India — the illustrative persona
Consider a mid-tier Indian EMS entity in the mould of Elin Electronics — a Faridabad-Haryana-headquartered contract manufacturer with production plants at Faridabad Haryana and Ghaziabad Uttar Pradesh, running an FY 2026-27 annual EMS output of approximately Rs 850 crore across a customer base that includes consumer electronics OEMs (small kitchen appliance brands, personal care appliance brands, LED lighting brands) and IT hardware OEMs (server components, storage components, mid-tier industrial electronics). The two-plant footprint operates on two distinct state GSTINs (Haryana GSTIN 06XXXXXXXXX and Uttar Pradesh GSTIN 09XXXXXXXXX) with cross-plant work-in-progress movement handled under Section 143 CGST job-work challan with Rule 45 tracking and Form ITC-04 quarterly filing. The monthly B2B invoice output across the two plants ranges from approximately 15,000 to 20,000 invoices — a volume that comfortably exceeds the Rs 5 crore aggregate turnover threshold set by CBIC Notification 10/2023 effective 01-August-2023 and that mandates 100 percent e-invoicing on B2B outward supplies. The scale also puts the entity above the Rs 10 crore aggregate annual turnover threshold at which the GSTN Advisory dated 05-November-2024’s 30-day IRN generation window applies with hard IRP rejection on post-30-day submission attempts.
The persona is illustrative — the exact plant footprint, product mix, monthly invoice volume, customer base, and GSP selection for any specific EMS entity are commercial and operational choices governed by that entity’s own decisions, and the numbers below are illustrative of the reconciliation surface, not a claim about any specific real EMS entity’s exact operating position. The point of the persona is the operating cadence of the monthly IRN log, the IRN failure log, the credit note IRN linkage register, and the GSTR-1 review — a cadence that transfers cleanly from Elin-scale operations to any similar mid-tier EMS at the Rs 500 crore-plus annual revenue scale.
The IRN generation infrastructure for the entity is a GSP-integrated flow. The ERP (typically SAP FI, Oracle Fusion, Microsoft Dynamics 365, or an industry-specific ERP configured for EMS with a plant-and-cost-centre structure) generates the tax invoice with all mandatory fields per the FORM GST INV-01 schema, composes the invoice JSON payload, and posts it to the GSP’s e-invoicing API endpoint over a secure channel. Common approved GSPs in the e-invoicing space include ClearTax (Defmacro Software), Cygnet Infotech, Perennial Systems, and IRIS Business Services — the specific GSP selection for any given taxpayer is a commercial and technical fit decision based on API throughput, SLA on IRP round-trip latency, error-handling maturity, and integration cost against the taxpayer’s ERP stack. The GSP relays the payload to the Invoice Registration Portal (IRP), which validates the payload against the schema, generates the 64-character IRN, generates the QR code payload, and returns both back to the GSP for embedding on the customer-copy PDF, seller-copy PDF, and transporter copy where applicable.
The regulatory overlay — Notification 10/2023, Rule 48(4), Section 34, Section 37, Section 122
Six regulatory anchors govern the e-invoicing claim and reconciliation chain, and each maps to a specific control surface.
CBIC Notification No 10/2023 — Central Tax dated 10-May-2023 reduced the e-invoicing threshold under Rule 48(4) of the CGST Rules 2017 to Rs 5 crore aggregate turnover in any preceding financial year from 2017-18 onwards, with effect from 01-August-2023. Prior thresholds were phased downward from Rs 500 crore (from 01-October-2020), Rs 100 crore (from 01-January-2021), Rs 50 crore (from 01-April-2021), Rs 20 crore (from 01-April-2022) and Rs 10 crore (from 01-October-2022) to the current Rs 5 crore floor. Any registered person crossing this threshold — including mid-tier and larger Indian electronics manufacturers, mobile handset EMS providers, IT hardware EMS providers, appliance component manufacturers, and semiconductor packaging beneficiaries — must generate an IRN for every B2B tax invoice, credit note and debit note before or at the time of issuing the tax invoice to the recipient. Specified persons — SEZ units, banking, insurance, NBFC, goods transport agency, passenger transport and multiplex cinema — remain excluded per Notification 13/2020 as amended, and this exclusion is why Foxconn’s Sriperumbudur SEZ operation is treated distinctly from a DTA-based EMS entity for e-invoicing purposes (the SEZ exclusion is a separate treatment head, not a threshold-based exemption).
Rule 48(4) and Rule 48(5) of the CGST Rules 2017 are the second anchor. Rule 48(4) prescribes that the qualifying registered person shall prepare a tax invoice by including the particulars contained in FORM GST INV-01 after obtaining an IRN by uploading the information contained therein on the Invoice Registration Portal. Rule 48(5) then prescribes that every invoice issued in any other manner shall not be treated as an invoice. The consequence is legal and immediate — a supplier document that carries a tax-invoice header but does not carry the IRN and QR code is not a valid tax invoice for the recipient’s ITC purposes under Section 16(2)(a) read with Rule 36(4), and the recipient’s ITC claim on that supplier document is exposed to denial in the recipient’s next assessment cycle.
The 30-day IRN generation window and the 24-hour IRN cancellation window are the third anchor. Per the GSTN Advisory dated 05-November-2024, taxpayers with aggregate annual turnover of Rs 10 crore and above must generate the IRN within 30 days from the invoice date. Attempts to generate IRN after the 30-day window will be rejected by the IRP. For taxpayers below the Rs 10 crore threshold, no time limit is currently prescribed, though contemporaneous generation remains the good-practice discipline. The IRN cancellation window is 24 hours from IRN generation for all taxpayers — during this window, the supplier can cancel the IRN on the IRP and re-generate a fresh IRN against a corrected invoice. Post-24-hour correction requires issuing a Section 34 CGST credit note with its own IRN and a fresh tax invoice with a fresh IRN.
Section 34 CGST is the fourth anchor. Where the tax invoice’s taxable value or tax charged exceeds the value or tax actually payable, or where goods are returned or found deficient, the supplier issues a credit note; where the taxable value or tax charged is lower, the supplier issues a debit note. Under the e-invoicing regime, each credit note and debit note issued against an e-invoice must itself be uploaded to the IRP and carry its own IRN, and must reference the original e-invoice IRN in the mandatory reference field of the FORM GST INV-01 credit note schema. For a mid-tier EMS handling B2B returns from an OEM customer (defective components returned under the OEM’s incoming quality control, quantity adjustments per the OEM’s inspection report, price adjustments per a subsequent purchase order revision), the credit note IRN linkage register maintains the one-to-many mapping between the original invoice IRN and each downstream credit note IRN issued against it.
Section 37 CGST is the fifth anchor. The outward supplies return in FORM GSTR-1 is filed by the 11th day of the month succeeding the tax period (or by the 13th day for the QRMP quarterly filer). Where the supplier has generated e-invoices for the tax period, GSTN auto-populates the supplier’s GSTR-1 from the IRP data. The supplier reviews the auto-populated GSTR-1, adds any non-e-invoice supplies (B2C supplies not falling under the e-invoicing mandate, exports and SEZ supplies with the correct treatment, nil-rated and exempt supplies), corrects any drop-outs, and files by the deadline. The three-way tie-out that must happen before filing is between the ERP outward supplies register (source of truth), the IRP-issued IRN log (invoices that carry a valid IRN), and the GSTN-auto-populated GSTR-1 (what GSTN believes the supplier reported). The reconciliation playbook monthly close pillar situates this three-way tie-out within the entity’s monthly close cadence, ensuring that the GSTR-1 filing lands cleanly in the correct period.
Section 122 CGST is the sixth anchor. Section 122(1) prescribes a penalty of Rs 10,000 or the amount of tax evaded, whichever is higher, on a taxable person who supplies goods or services without issue of any invoice or issues an incorrect or false invoice. Section 122(3)(e) prescribes a penalty of up to Rs 25,000 for a person who fails to issue an invoice in accordance with the provisions of the Act or the rules made thereunder. In the e-invoicing context, failure to generate an IRN within the applicable generation window renders the invoice invalid under Rule 48(5) and attracts penalty exposure under Section 122(3)(e) to the supplier, with parallel input tax credit denial exposure to the recipient under Section 16(2)(a) read with Rule 36(4).
A worked example — a mid-tier EMS across a monthly IRN cycle
Illustrative — the following figures represent the operating pattern of a mid-tier EMS entity in the mould of Elin Electronics running a two-plant footprint at Faridabad Haryana and Ghaziabad Uttar Pradesh, FY 2026-27 annual EMS output of approximately Rs 850 crore, and monthly B2B invoice output of approximately 15,000 to 20,000 invoices across the two state GSTINs. The exact plant footprint, product mix, monthly invoice volume, customer base, and GSP selection for any specific real EMS entity are commercial and operational choices governed by that entity’s own decisions, and the numbers below are illustrative of the reconciliation surface, not a claim about any specific real EMS entity’s exact operating position.
Consider the entity’s July FY 2026-27 monthly outward supplies close. The two-plant ERP outward supplies register shows approximately 18,400 B2B tax invoices raised in July across the Haryana and Uttar Pradesh GSTINs, with an aggregate taxable value of approximately Rs 72 crore for the month and an aggregate GST charged (IGST plus CGST plus SGST as applicable per place of supply) of approximately Rs 13 crore at the blended output rate (predominantly 18 percent per HSN 8471, HSN 8517, HSN 8525, HSN 8536, HSN 8542, HSN 8544 and other applicable Chapter 84 and Chapter 85 headings for the entity’s product mix). The GSP-integrated IRN generation flow closes the round-trip on approximately 18,340 invoices within the invoice-raise cycle (99.7 percent first-attempt success rate), with the residual 60 invoices caught by the IRN failure log for various failure-reason categories.
| IRN failure category | Count (illustrative) | Reconciliation output |
|---|---|---|
| Portal downtime rejection | 22 | Retry queue with exponential back-off; re-submit within 30-day window |
| Schema validation rejection (missing recipient GSTIN, wrong HSN, wrong place of supply) | 18 | ERP data-correction workflow; re-submit within 30-day window |
| GSP token expiry (mid-batch API session lapse) | 12 | Token refresh; retry batch |
| Network error (transient) | 6 | Retry queue |
| Wrong invoice number format (duplicate detection) | 2 | Invoice number correction; re-submit with fresh number |
| Total failures | 60 | All resolved within 30-day generation window |
The credit note IRN linkage register for the July cycle shows approximately 240 credit notes issued against original July invoices and approximately 180 credit notes issued against earlier-month invoices (June, May, April) for delayed OEM incoming quality control rejections, quantity adjustments, and price adjustments per subsequent purchase order revisions. Each credit note carries its own IRN and references the original invoice IRN in the mandatory reference field of the FORM GST INV-01 credit note schema.
Post the monthly IRN cycle close, the entity runs the three-way tie-out for GSTR-1 filing by 11-August:
| Reconciliation surface | Value (Rs cr, illustrative) | Reconciliation output |
|---|---|---|
| ERP outward supplies register — Haryana GSTIN | 44.0 | Source of truth |
| ERP outward supplies register — Uttar Pradesh GSTIN | 28.0 | Source of truth |
| Total ERP register | 72.0 | Aggregate month |
| IRP-issued IRN log — invoices with valid IRN | 71.8 | 60 rejections resolved and re-submitted |
| GSTN-auto-populated GSTR-1 draft | 71.7 | Small drop-out reconciled |
| Post-review GSTR-1 filed | 72.0 | Aligned with ERP after manual add-back of the drop-out and non-e-invoice supplies |
The Section 122 penalty exposure quantification for the month is nil because all 60 IRN failures were resolved and re-submitted within the 30-day generation window and no invoice fell into Rule 48(5) invalidity. The recipient GSTR-2B match risk register flags the drop-out invoice for supplier-side outreach to the affected OEM customer to confirm that the invoice has been auto-populated on the OEM’s GSTR-2B for the same tax period.
Common reconciliation breakages
Five breakages recur across mid-tier EMS monthly IRN cycles, and each maps to a specific control failure.
-
IRN generation window overrun. For taxpayers at Rs 10 crore-plus aggregate annual turnover, the GSTN Advisory dated 05-November-2024’s 30-day IRN generation window is a hard IRP-side rejection edge — an invoice raised on the 1st of the month for which IRN is not generated by the 30th falls into Rule 48(5) invalidity and attracts Section 122(3)(e) penalty exposure. The failure mode is typically a delayed IRN cycle for month-end and month-start invoices caught in a portal-downtime window that persists across the 30-day cutoff for an old invoice. The reconciliation discipline is a per-invoice IRN age tracker with an alert-and-escalation trigger at Day 20 and a mandatory-close-out trigger at Day 25, well before the Day 30 hard cutoff.
-
24-hour cancellation window elapsed for a post-issuance correction request. Where the supplier discovers an error on an issued invoice (wrong recipient GSTIN, wrong HSN, wrong place of supply, wrong taxable value) more than 24 hours after IRN generation, the IRP-side cancellation route is closed. The correction pathway is a Section 34 CGST credit note with its own IRN reversing the original invoice, and a fresh tax invoice with a fresh IRN for the corrected supply. Failure to follow the credit-note-plus-fresh-invoice pathway (for example, informally cancelling the original invoice on the ERP without a corresponding IRP credit note) creates a permanent mismatch between the ERP outward supplies register and the IRP IRN log, and a downstream mismatch on the recipient’s GSTR-2B.
-
Credit note IRN missing the original invoice IRN reference field. Every Section 34 credit note IRN must reference the original invoice IRN in the mandatory reference field of the FORM GST INV-01 credit note schema. A credit note IRN generated without the original invoice IRN reference is technically valid at the IRP but cannot be bound back to the original invoice for the downstream GSTR-1 and recipient GSTR-2B auto-population. The reconciliation surface is a credit note IRN linkage register that maintains the one-to-many mapping and flags any credit note IRN missing the reference field for immediate remediation.
-
ERP-to-IRP-to-GSTR-1 three-way tie-out drop-outs. Where an invoice generated in the ERP fails to obtain an IRN (falling into the IRN failure log) and the failure is not resolved before the GSTR-1 filing deadline, the invoice does not appear in the GSTN-auto-populated GSTR-1 for the tax period, creating a drop-out. Where the drop-out is not manually reconciled before filing, the GSTR-1 filed for the period is under-stated against the ERP outward supplies register, and the recipient’s GSTR-2B for the period is under-populated against the invoices the recipient has received. The reconciliation discipline is the mandatory three-way tie-out between the ERP register, the IRP IRN log, and the GSTN-auto-populated GSTR-1, run before the 11th-day filing deadline under Section 37 CGST.
-
GSP token expiry and mid-batch API session lapse causing partial-batch IRN generation. In a high-volume EMS environment running 15,000 to 20,000 monthly invoices, batch submissions to the GSP e-invoicing API can lapse partway through if the GSP authentication token expires mid-batch. The failure mode is a partial batch with some IRNs issued and others held in a pending state — the reconciliation risk is that the pending state is not automatically re-driven and the residual invoices sit in an IRN-not-generated state past the 30-day window. The reconciliation discipline is a per-batch reconciliation between the ERP submission list and the GSP-returned IRN list, with an automatic re-drive of any pending or failed entries. The reconciliation failure-mode analysis for India methodology treats this batch-integrity failure as a documented control test, and the 57 human errors and the detection envelope trust asset situates the specific error class within the broader taxonomy of process failures.
How a reconciliation platform handles this
A purpose-built electronics reconciliation platform ingests the ERP outward supplies register from the SAP FI, Oracle Fusion, Microsoft Dynamics 365, or industry-specific EMS ERP, the GSP-returned IRN log with invoice-to-IRN one-to-one mapping and the QR code payload, the IRN failure log with categorised failure reasons and retry-or-escalation state, the credit note IRN linkage register with the mandatory original invoice IRN reference field validation, and the GSTN-auto-populated FORM GSTR-1 draft — and produces a monthly e-invoicing reconciliation pack that closes the loop from the ERP invoice row to the GSTR-1 filed line. The platform runs the per-invoice IRN age tracker against the 30-day generation window with alert-and-escalation thresholds well before the hard IRP cutoff, the 24-hour cancellation window countdown for any correction request raised, the credit note IRN linkage register validation, the ERP-to-IRP-to-GSTR-1 three-way tie-out with drop-out identification and manual add-back workflow, the Section 122 penalty exposure quantification for any invalid invoices in the period, and the recipient GSTR-2B match risk register for high-volume OEM customer accounts flagged for supplier-side outreach — all bound to the entity’s monthly close cadence and the Section 37 CGST 11th-day filing deadline. Match rate improvement from 51 to 88 percent on the ERP-to-IRP-to-GSTR-1 three-way tie-out and the credit note IRN linkage register, combined with an ISO 27001:2022 posture, AWS Mumbai residency, and DPDP Act 2023 aligned data handling, is what makes the platform an infrastructure investment for a mid-tier EMS running 15,000 to 20,000 monthly B2B invoices rather than a spreadsheet substitute. The commercial pillar for the sub-cluster is Electronics reconciliation software India; the sister GST-native cluster is GST reconciliation software; the broader authority is reconciliation software India.
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ CBIC Notification No 10/2023 — Central Tax dated 10-May-2023 (e-invoicing threshold reduction to Rs 5 crore) — In exercise of the powers conferred by sub-rule (4) of Rule 48 of the Central Goods and Services Tax Rules 2017, the Central Board of Indirect Taxes and Customs, on the recommendations of the GST Council, made a further amendment to Notification No 13/2020 — Central Tax dated 21-March-2020. With effect from 01-August-2023, the aggregate turnover threshold for e-invoicing applicability was reduced to Rs 5 crore in any preceding financial year from 2017-18 onwards. Prior thresholds were phased downward from Rs 500 crore (from 01-October-2020), Rs 100 crore (from 01-January-2021), Rs 50 crore (from 01-April-2021), Rs 20 crore (from 01-April-2022) and Rs 10 crore (from 01-October-2022) to the current Rs 5 crore floor. Registered persons whose aggregate turnover in any financial year from 2017-18 onwards exceeds the Rs 5 crore threshold must generate an Invoice Reference Number (IRN) for every B2B invoice, credit note and debit note by uploading the invoice JSON payload to the Invoice Registration Portal (IRP) before or at the time of issuing the tax invoice to the recipient. Specified persons — SEZ units, insurance companies, banking companies, financial institutions, non-banking financial companies, goods transport agencies transporting goods by road in a goods carriage, passenger transport service suppliers and suppliers of admission to exhibition of cinematograph films in multiplex screens — remain excluded from the e-invoicing mandate under Notification 13/2020 as amended.
- ▸ Rule 48(4) and Rule 48(5) of the Central Goods and Services Tax Rules 2017 (mandatory e-invoicing) — Rule 48(4) prescribes that a registered person, other than those referred to in Rule 54(2), 54(3), 54(4) and 54(4A) and those excluded by notification, whose aggregate turnover in a financial year exceeds the notified threshold shall prepare a tax invoice by including such particulars contained in FORM GST INV-01 after obtaining an Invoice Reference Number by uploading the information contained therein on the Common Goods and Services Tax Electronic Portal. Rule 48(5) further prescribes that every invoice issued by such a person in any other manner shall not be treated as an invoice. The consequence is that the IRN and the QR code embedded on the tax invoice are the legal proof of the invoice's validity — a supplier document that carries a tax-invoice header but does not carry the IRN and QR code is not a valid tax invoice for the recipient's input tax credit purposes and can attract input tax credit denial to the recipient under Section 16(2)(a) read with Rule 36(4).
- ▸ Section 122 of the Central Goods and Services Tax Act 2017 (penalty for failure to comply with e-invoicing) — Section 122(1) prescribes a penalty of Rs 10,000 or the amount of tax evaded, whichever is higher, on a taxable person who supplies any goods or services or both without issue of any invoice or issues an incorrect or false invoice with regard to any such supply. Section 122(3)(e) prescribes a penalty of up to Rs 25,000 for a person who fails to issue an invoice in accordance with the provisions of the Act or the rules made thereunder. In the e-invoicing context, failure to generate an IRN within the required window (currently 30 days from the invoice date for taxpayers with aggregate turnover of Rs 10 crore and above per GSTN Advisory dated 05-November-2024, and previously 7 days from the invoice date for the Rs 100 crore-plus category — the specific window applicable to a given taxpayer must be verified against the current GSTN Advisory in force) renders the invoice invalid under Rule 48(5) and can attract penalty exposure under Section 122(3)(e) to the supplier and input tax credit denial exposure to the recipient under Section 16(2)(a) read with Rule 36(4). The IRN cancellation window on the IRP is 24 hours from IRN generation — post-24-hour correction requires issuing a credit note under Section 34 CGST with its own IRN and a fresh tax invoice with a fresh IRN.
- ▸ Section 34, Section 37, and Section 16 of the Central Goods and Services Tax Act 2017 (credit notes, GSTR-1, input tax credit) — Section 34 prescribes the credit note and debit note mechanism — where the tax invoice's taxable value or tax charged exceeds the value or tax actually payable, or where the goods are returned or found deficient, the supplier issues a credit note; where the taxable value or tax charged is lower, the supplier issues a debit note. Under the e-invoicing regime, each credit note and debit note issued against an e-invoice must itself be uploaded to the IRP and carry its own IRN, and must reference the original e-invoice IRN for downstream traceability. Section 37 prescribes the outward supplies return in FORM GSTR-1, filed by the 11th day of the month succeeding the tax period (or by the 13th day for the QRMP quarterly filer). Where the supplier has generated e-invoices for the tax period, the GSTR-1 is auto-populated by GSTN from the IRP data — the supplier reviews the auto-populated GSTR-1, adds any non-e-invoice supplies (B2C, exports without payment of tax where applicable), corrects any drop-outs, and files. Section 16(2) prescribes the input tax credit conditions for the recipient — including that the recipient must be in possession of a tax invoice or debit note issued by a registered supplier and that the tax charged in respect of the supply has been actually paid to the government.
- ▸ GSTN Advisory dated 05-November-2024 (30-day IRN generation window for Rs 10 crore-plus taxpayers) — Per the GSTN Advisory dated 05-November-2024, taxpayers with aggregate annual turnover of Rs 10 crore and above are required to generate the Invoice Reference Number (IRN) for their invoices, credit notes and debit notes within 30 days from the date of invoice, credit note or debit note. Attempts to generate IRN after the 30-day window will be rejected by the IRP. For taxpayers below the Rs 10 crore aggregate annual turnover threshold, no time limit is currently prescribed for IRN generation, though the good-practice discipline remains contemporaneous generation. The IRN cancellation window remains 24 hours from IRN generation for all taxpayers. Post-24-hour correction requires a Section 34 credit note with its own IRN. The Invoice Registration Portal is accessible either directly via the GST portal or via a GST Suvidha Provider (GSP) API integration into the taxpayer's Enterprise Resource Planning system for high-volume invoice cycles.
- ▸ GST Suvidha Provider (GSP) framework — GSTN circular on GSP appointment — The GST Suvidha Provider (GSP) framework was established by GSTN to enable third-party service providers to integrate with the GSTN infrastructure via secure APIs, allowing high-volume taxpayers to file GST returns, upload e-invoices, and generate e-way bills from within their own Enterprise Resource Planning systems. Approved GSPs must meet the technical and security standards prescribed by GSTN and are periodically re-evaluated. Common GSP names in the e-invoicing space include ClearTax (Defmacro Software), Cygnet Infotech, Perennial Systems, IRIS Business Services and other approved providers — the specific GSP selection for any given taxpayer is a commercial and technical fit decision. Under the GSP-integrated e-invoicing flow, the taxpayer's ERP generates the invoice JSON per the FORM GST INV-01 schema, the GSP relays the payload to the IRP, and the IRP returns the IRN and QR code payload for embedding on the customer-copy PDF.