In this guide 6 sections
Confirm applicability with your CA first. Then clean the item and party masters, set up portal credentials, fix the numbering series, send test invoices and build a queue that holds invoices during downtime. Run old and new in parallel. Allow several weeks for it.
Confirm applicability and the start date in writing
The government notifies the turnover threshold for e-invoicing, and it has changed more than once since the scheme began, so memory and a vendor’s sales call are poor sources. Ask your CA which turnover figure counts, which financial year it is measured on and the date from which you must comply.
Write the answer down. It sets your deadline, and every later step in this plan is scheduled backwards from that date, so an error here moves everything.
Also ask which registrations are affected. A business with several GSTINs may find that only one of them crosses the line, or that one crosses earlier than the rest.
Clean the masters before any invoice goes to the portal
The portal is strict. Item masters with a blank HSN code, a unit of measure that is free text, or a duplicated product under two names will each cause a rejection. Party masters fail on a mistyped GSTIN, a missing pin code or a state that contradicts the GSTIN’s first two digits and is rejected at upload.
Export both masters to a spreadsheet. Sort by HSN, then by unit, then by GSTIN state code, fix the odd entries, merge duplicates, mark inactive records and check every GSTIN against its checksum. Load the corrected file back.
This work is dull. It still decides whether go-live is calm or becomes a fortnight of rejected invoices, credit notes and apologies to customers waiting on their goods.
- HSN or SAC present on every active item
- Unit of measure picked from a fixed list
- GSTIN checksum valid on every registered party
- Pin code and state agree with the GSTIN
- Duplicate parties merged
Credentials, numbering series and test invoices
Register on the e-invoice portal, create API credentials for your billing software, and name one person who holds them and one deputy who can renew them. Credentials live in one controlled vault, never on a sticky note, in a shared spreadsheet or in a personal email inbox where a leaver could still read them.
Check your document series. Each series must stay unique within a financial year, respect the permitted length and character set, and never repeat a number, even after a cancelled invoice. Splitting series by branch or document type suits e-invoicing well, provided each prefix has one owner and is never reused by another branch.
Send test invoices from the sandbox: a plain sale, a credit note, an invoice with several tax rates, a branch delivery and one deliberately wrong GSTIN. Read the error the wrong one returns.
Plan for portal downtime and failed calls
Sometimes the portal is slow or down. The billing screen must not freeze. A queue holds the invoice in a pending state, retries on a schedule and shows the clerk a clear status, so billing carries on.
Agree what dispatch does when an IRN has not arrived, because some businesses hold the vehicle at the gate while others follow a documented fallback approved by the CA. Decide it long before go-live.
Log every request and response. The clerk should see the portal’s message in plain words beside the failed invoice, with the time of the attempt and the number of retries so far.
Run in parallel, then cut over
For one to two weeks, raise invoices the old way and also push the same invoices through the new set-up in test. Compare tax amounts, totals and numbering line by line, and chase every difference back to the master record, the tax rate or the series that caused it. Differences show up fast.
Set a go-live date away from month-end. Name one person to watch the queue on day one and another to phone the accountant when a rejection looks like a tax question rather than a data error. After the first week, review rejections by reason and fix the causes in the masters rather than invoice by invoice, because the same blank HSN will return.
E-invoicing go-live tracker
One sheet, one row per task. Columns hold owner, due date, status and the evidence that proves the task is done, such as a screenshot or a test invoice number. Rows run in order: CA confirmation, master cleanup counts, portal registration, credential holder, series list, test cases passed, downtime fallback agreed, parallel run results and cutover sign-off.
Open a blank worksheet to printQuestions owners ask
How early should we start?
Start well before the notified date. Master cleanup and the parallel run take longer than most owners expect, and month-end pressure leaves little room for fixing a rejected batch of invoices.
Can we use the free portal tool instead of integrated software?
For very low volumes, perhaps. Typing each invoice twice, once in the books and once on the portal, invites mismatches, so beyond a handful a day send directly from the billing system.
What if our turnover is close to the limit but not over it?
Ask your CA how the limit is measured and when it applies to each registration, then start the master cleanup now rather than after the notice. Cleaning masters pays off regardless. The same item and party data also feeds your returns and your e-way bills, so none of the cleaning is wasted even if the threshold reaches you later.