Generating e-way bills from TallyPrime. The GSP API step, and the errors that block it

TallyPrime can generate an e-way bill directly, in real time, without you ever opening the government portal separately. The one-time setup behind that is where almost everyone gets stuck — not because it's complicated, but because it quietly asks for two different sets of credentials and most guidance treats them as one.

The credential most guides skip a step on

TallyPrime supports two ways of getting an e-way bill: generate the details, export them, and upload the file to the government portal yourself — or let TallyPrime talk to the e-way bill system directly and get the e-way bill number back in the same screen. The second one is what people mean by "API" or "GSP" setup, and it needs more than logging into the e-way bill portal once.

Per TallyPrime's own one-time setup guidance, there are two distinct credential sets, created in two different places on the e-way bill portal:

• Your e-Way Bill portal login — created the normal way, under Registration > e-Way Bill Registration, verified by an OTP to your registered mobile number, with a username and password you choose. This is what you'd use if you logged into the portal in a browser.
• A separate API user profile — created under Registration > For GSP, where you select a GST Suvidha Provider from a list and set a different username and password specifically for that API channel. For TallyPrime's direct integration, under GSP Name select Tally (India) Private Limited IPL (Tally's other pages refer to the same GSP in prose as "Tally (India) Pvt Ltd").

Tally's own documentation is explicit about why this trips people up: "The API user credential is different from your e-Way Bill credential." Typing your ordinary portal password into TallyPrime's e-way bill login screen is the single most common reason the "one-time setup" doesn't feel finished the first time — it isn't the same password, even though nothing on either screen says so loudly.

The one-time setup, step by step

Generating an e-way bill online, once setup is done

With both credential sets in place, TallyPrime's online generation flow runs inside the sales voucher itself:

1. Create the GST sales voucher as usual — party, ledgers, items.
2. Set "Provide GST/e-Way Bill details" to Yes, and complete the Consignor, Consignee and Transport Details on the Statutory Details screen.
3. Press Ctrl+A to save and generate the e-way bill; confirm on the prompt that follows.
4. An e-Way Bill Login screen appears — this is where the API credentials from Step 2 above go, not your ordinary portal login.
5. Press Enter. TallyPrime exchanges the voucher's details with the e-way bill system directly.
6. On success, the e-Way Bill No. and Validity Date are written back into the Statutory Details screen; Page Down shows the generated e-way bill with its QR code — nothing to separately download or upload.

That's the entire value of doing the one-time setup correctly: everything after Step 2 above is one voucher, one confirmation, no separate portal visit.

Video walkthrough by Accounting Solutions — embedded with credit; the guide above is our own.

The errors that actually block registration

Four failures account for most of the trouble at this step. Here's what TallyPrime's own troubleshooting guidance says about each — and, where it says nothing, that's stated honestly rather than guessed at.

"Invalid credentials" after an e-Way Bill portal password change

Because the API user profile and your ordinary portal login are separate accounts (see above), changing your portal password does not touch your API credentials — and vice versa. Tally's FAQ page lists the checklist for "TallyPrime shows that the e-Way Bill credentials are invalid":

• Confirm the credentials you're entering were registered with Tally (India) Pvt Ltd selected as GSP — not a different provider, and not your ordinary portal login.
• Confirm the credentials match the GSTIN you're generating the e-way bill for.
• Confirm you're pointed at the live e-way bill portal, not the sandbox/test environment.
• Type the username and password in manually rather than pasting, to rule out a stray special character.

If none of that resolves it and you've genuinely lost the API password, Tally's FAQ page is specific that there is no direct reset: you have to log into the e-way bill portal, go to User Management, Freeze User on the existing API user profile, and create a new one under Registration > For GSP again. A forgotten API password is a re-registration, not a "forgot password" link.

"Error occurred while registration of API"

Tally's documentation doesn't name this error string. What its FAQ does address is the registration-type choice itself — it asks "During the registration, should I select GSP or API?" as its own dedicated question, and answers "During the registration process on the e-Way Bill portal, select For GSP." If registration errors out, that's the first thing to re-check: that you're on the For GSP screen and that Tally (India) Private Limited IPL is the GSP selected — not a generic "API" option elsewhere on the portal.

OTP never arrives during registration

A related, separately-documented cause: the portal sends its OTP to the mobile number registered against your GSTIN on the GST portal, not a number typed fresh into the e-way bill form. Update it on the GST portal first.

"GSP account showing inactive"

Tally's own e-way bill documentation doesn't describe an "inactive GSP account" state — we could not find an official explanation of that specific message, so we won't invent one. What is independently sourceable, and can produce a similar-looking block, is a completely different mechanism worth ruling out first, covered next — because it isn't a Tally or GSP problem at all.

The one cause that has nothing to do with your GSP setup

Rule 138E of the CGST Rules (inserted by Notification 74/2018-Central Tax, in force 21 November 2019; scope narrowed to the defaulter's outward movements by Notification 15/2021-Central Tax; position as of 24 August 2026) blocks a registered person from furnishing Part A of an e-way bill for their own outward movements if they've defaulted on filing — and the counts differ by limb: the return under section 39 (GSTR-3B in the ordinary case) for two consecutive tax periods, GSTR-1 for any two months or quarters, CMP-08 for two consecutive quarters under composition, or registration under suspension. It applies from the portal side, on your GSTIN's filing status, regardless of how correctly TallyPrime's API credentials are configured. Perfectly working GSP credentials cannot generate a Part A the portal has blocked for filing defaults — checking recent GSTR-1/3B filing status is worth doing before spending more time on the API screen.

What actually triggers an e-way bill in the first place

Worth being precise about, since a wrong assumption here causes its own generation failures. Rule 138(1) of the CGST Rules requires an e-way bill for movement of goods of consignment value exceeding fifty thousand rupees — the CGST Rules' figure, which governs inter-State movement. Explanation 2 to the rule defines that value as the section-15 value declared on the invoice, bill of supply or delivery challan, including CGST/SGST/IGST and cess, not the taxable value alone. It also isn't only a sales trigger: the same rule covers movement "for reasons other than supply" (branch transfers, job-work despatches) and inward movement from an unregistered person. Intra-state movement can carry a different threshold, set independently by each state — check your own state's notification rather than assuming ₹50,000 applies uniformly within it.

An e-way bill failure is often the first symptom, not the problem itself

A voucher that fails at the e-way bill screen — wrong buyer GSTIN, a consignment value that doesn't match what the invoice actually says, a stale party address — is almost never a TallyPrime or GSP problem underneath. It's TallyPrime correctly reporting a value in your sales register that was already wrong before you tried to generate anything against it. The e-way bill step just happens to be the first place in the filing chain that actually validates the data against a live external system, so it's often the first place the error surfaces — not the first place it was created.

Catching a stale GSTIN, a mismatched consignment value or an outdated party master at the point it's entered, across a purchase and sales register with any real volume, is exactly the kind of continuous checking that is painful to do manually — by the time an e-way bill generation fails, the same bad data has usually already been sitting in the register for weeks, waiting to also break your GSTR-1 export or your GSTR-2B match.

Where this connects to e-invoicing, and to what GSTN nearly changed

Two things worth knowing before you consider this setup "done":

• If you're also above the e-invoicing threshold under Rule 48(4), that's a third, separate registration with the Invoice Registration Portal — its own registration, though Tally's setup page notes the one shortcut in the other direction: if you already hold e-Invoice API credentials, you can use them to generate e-way bills without creating a separate GSP profile.
• GSTN had proposed making a Ship-to GSTIN field mandatory on exactly this API layer (Standalone Generate EWB and related e-way bill APIs) from 1 August 2026. GSTN's Advisory No. 668 dated 29 July 2026 ("Advisory on Keeping on Hold the Proposed e-Way Bill Enhancements") kept implementation on hold until further notice and withdrew the advisories of 9 and 17 June 2026 and the FAQs of 2 July 2026. No replacement date has been announced as of 24 August 2026. Note that TallyPrime's own help page has not caught up — it still describes the 1 August 2026 mandate as effective; go by Advisory 668, not that page. Nothing in the setup above needs to change for it.

How Recoup fits in

Recoup doesn't generate e-way bills — that's TallyPrime and the GSP layer's job, and the setup above is what makes that work correctly. What Recoup does is sit upstream of it: it continuously reconciles your ITC against GSTR-2B and flags register-level errors — the same class of stale GSTIN, mismatched value or bad master data that also causes an e-way bill to fail — before they reach a filing screen, not after. Fixing the register once, upstream, is cheaper than chasing the same bad data across three different failure points.

Related guides