GST e-Invoice Portal Maintenance: Checks for Auto-Pulled Data

Direct verdict

If your business already pulls e-invoice data automatically, keep that pull. Do not replace it with manual downloads. Use the GSTN e-invoice portal and its API as the source, and treat manual downloads as the way to fill gaps when a pull fails. The GSTN e-invoice portal and manual downloads are the same system seen through two routes, so the real choice is how much of the checking a person does by hand.

The maintenance has closed, so the job now is verification. Nothing in the advisory says IRN generation stopped. The risk sits in the downstream pulls, the GSTR-1 auto-population and the JSON files, which is where a silent gap can go unnoticed.

What the maintenance window covered

GSTN issued its advisory on 28 October 2026. It described a scheduled infrastructure upgrade on the e-invoice portal at einvoice.gst.gov.in. The window started at 9:00 AM IST on 31 October 2026 and ended at 1:00 PM IST on 1 November 2026. Trade press reports describe the advisory as using the wording that the affected services would be temporarily unavailable, and that they were expected to resume once the work was done.

Three functions were named. The first was retrieval and processing of e-invoice data from the Invoice Registration Portals. The second was auto-population of e-invoice data into GSTR-1. The third was e-invoice JSON downloads, through both the portal and the APIs. Jurishour reads the advisory as not suspending e-invoice generation or IRN generation at the IRPs. That reading matters for your checks: an invoice issued during the window may have an IRN, but your system may not have fetched it.

The advisory did not give a reason beyond the upgrade, and it did not say how many invoices or taxpayers were affected. Do not assume the window was harmless for your business until your own logs show it.

Checks to run now

1. Confirm the scheduled pulls ran. Open the log of your automated pulls and list every run between 9:00 AM IST on 31 October and 1:00 PM IST on 1 November. Any run in that window that returned an error, an empty file or a partial count needs a rerun. Also check that the first run after 1:00 PM IST on 1 November completed normally.
2. Match GSTR-1 against your register. Download the auto-populated details from the GSTR-1 dashboard, using the Excel option the portal provides. Compare the invoice count, the taxable value and the IRN for each invoice against your sales register for the period. Note that the portal's Excel file reflects what was reported to the IRP, so later edits in GSTR-1 will not appear in it.
3. Rerun missed JSON downloads. Build a list of IRNs issued in the window and check each one has a stored JSON file. The portal's download history shows only the last five files downloaded, so do not rely on it to find older gaps. Use your own IRN list as the reference.

Auto-population depends on the document date, not the date the invoice reached the IRP. A late-reported invoice can therefore land in an earlier month's GSTR-1. GSTZen's FAQ on auto-population also notes that auto-population stops once GSTR-1 for that period has been filed, and invoices reported after that do not populate anywhere. Check your filing calendar against the list of gaps before you file.

How the two routes compare

The table compares the automated route through the GSTN e-invoice portal and its APIs with manual portal downloads of e-invoice data and JSON files. Pricing is taken from GSTN's own notices where they exist. No tier names are published for the government portal itself.

The table shows that the cost of the portal is low and the cost of the work around it is where the money goes. A business that pulls data well during a normal month can still lose track of a three-day window if nobody owns the checks.

Who each route suits

Manual downloads suit a business with a small number of e-invoices each month, a single person who knows the portal, and no ERP that generates invoices. The work is slow but simple, and it is easy to see what has been done.

The automated route suits a business with an ERP, a steady stream of invoices or several billing systems. The GSTN ecosystem page describes third-party applications connecting to the GST system through secure APIs, which is the route most ERP and billing vendors use. A business with many invoices a day cannot check each one by hand in a reasonable time, so the automated route is the only practical option at that scale.

Neither route removes the need for a person. The portal does not tell you which invoice you forgot to fetch. Someone has to look at the list of gaps and decide.

Total cost of ownership beyond the sticker price

Set-up. The government portal charges nothing for IRN generation under the 2023 notice, but the cost of connecting it does not disappear. An API route needs a developer or ERP partner, a sandbox test, and a cutover plan. The NIC API developer sandbox at einv-apisandbox.nic.in is the official testing environment for integration, according to a 2026 GSTN advisory reported by Jurishour.

Breakage. API changes carry real cost. From 1 August 2026, GSTN made the Ship-to GSTIN mandatory in the e-invoice and e-way bill APIs where ship-to details are provided and an e-way bill is needed. Trade press has warned that integrations not updated before cutover can see invoices rejected at generation. Budget for an update each time GSTN changes a schema.

Maintenance. Someone has to own the integration. That person watches advisories, tests changes and checks the pull log each month. If that person leaves, the integration drifts.

Vendor lock-in. A GSP API is an interface licensed through GSTN that lets business software send and receive GST data without logging in to the portal. Moving between GSPs means new onboarding, new credentials and a fresh test cycle. Keep your own copies of every JSON file and IRN list, so that a change of provider does not cut you off from your history.

Manual time. Each window like 31 October costs staff time to check, rerun and reconcile. That cost is real even when the portal fee is zero.

The custom-built alternative, and when it wins

A custom build means your own software, or an AI worker, sitting between your ERP and the portal or a GSP. It takes the pull schedule, the matching and the exception list out of people's heads and puts them in a system with a log. It wins when you run several ERPs or billing tools, when you issue many invoices each day, or when auditors and your own finance team want a written trail of every pull.

An AI worker for this problem would connect to the pull route you already use, either the GSP API or the portal's downloads, and to your ERP's invoice list. It would run the pulls on schedule. When a pull fails during a window, it would queue the failed request, retry it on a set schedule, record each attempt and mark the IRNs still missing. At the end of the window it would compare the GSTR-1 export with your register and list every mismatch. A person then decides what to do. The worker cannot fix the portal, cannot change an invoice and cannot file a return. A person still checks each gap, decides on any amendment and approves the GSTR-1 before filing.

A custom build loses when you have a few dozen invoices a month, one person who owns the process and an ERP that already handles the pulls. In that case the cost of building and maintaining the worker is larger than the cost of a careful monthly check.

Migration notes

If you are moving from manual downloads to an automated route, start with a copy of your current IRN list and the JSON files you already hold. Keep both in a location you control, because the portal's own history is short.

Test the new route in a sandbox before the cutover. Run both routes side by side for one full GSTR-1 cycle, and compare the output. Keep the manual download as the fallback until the automated route has completed at least one full cycle without a gap.

Check the ship-to fields in your invoice data against the current schema before each cutover. Schema changes are the most common reason an integration that worked last month fails this month.

This explains the rule in general terms; it is not legal or tax advice for your case.