How-to · Marg ERP & e-invoicing

Marg ERP can upload an e-invoice in one click. Not when the GSP credentials and the portal's own e-invoice switch are two different gates

The short answer

Marg ERP's "Invalid Login Credentials" error means the GSP username and password saved in Marg's e-Invoice Settings don't match an active API user registered "Through GSP" on the government e-invoice portal — per Marg's own support page, the fix is to re-register that API user and re-enter the exact same credentials in Marg. A related but different error, "e-Invoice options are not enable for this GSTN," means the GSTIN itself was never separately activated for e-invoicing via Registration > e-Invoice Enablement on the portal — GSP credentials alone don't fix that one.

Marg ERP's own support pages document a working e-invoicing setup — GSP registration on the government portal, a settings screen inside Marg, a one-click "Generate eInvoice" upload. What they also document, across four separate answers, is that "Invalid Login Credentials" and a GSTIN never activated for e-invoicing are two different failures with two different fixes — and that the e-way bill isn't something you type an existing number for; it's a separate checkbox and a separate details screen on the same upload step that generates one.

What Rule 48(4) actually requires, before you touch Marg

e-Invoicing is a reporting mechanism under Rule 48(4) of the CGST Rules, not a Marg feature. The rule itself fixes no threshold — it delegates the coverage test to a notification. Under Notification 13/2020-Central Tax dated 21 March 2020, as amended — by Notification 10/2023-CT w.e.f. 1 August 2023 for the ₹5 crore figure below — a registered person, other than a government department, a local authority, an SEZ unit, and insurers, banks/NBFCs, goods transport agencies, passenger transport suppliers and multiplex-cinema suppliers covered by Rule 54(2)-(4A), whose aggregate turnover in any preceding financial year from 2017-18 onwards exceeds ₹5 crore must report B2B invoices and exports (incl. credit/debit notes) through the portal, as of 30 October 2026. Marg's own support pages state the same figure in simpler terms — "E-invoicing is mandatory for all the taxpayers having aggregate turnover above Rs 5 crore in any of the previous years from 2017-18 onwards" — but don't repeat the exclusions list, so treat the fuller version above, not Marg's summary, as the governing one. Crossing ₹5 crore once keeps a GSTIN in the regime permanently; it is not a current-year test and doesn't switch off if turnover later falls back below the line. "IRP" — Invoice Registration Portal — is GSTN's own vocabulary for the notified system, not a term Rule 48(4) itself uses. The consequence of a missed or invalid registration sits in the neighbouring rule: under Rule 48(5), an invoice issued any other way "shall not be treated as an invoice" at all — which is why a buyer's ITC claim on it fails under Section 16(2)(a), long before anyone reaches a reconciliation screen.

Coming 1 January 2027, not yet in force: Notification 04/2026-CT dated 26 October 2026 — implementing the 57th GST Council's 8 October 2026 recommendation — adds two more categories to the same mandate (aggregate turnover exceeding ₹5 crore in any preceding financial year): reverse-charge supplies received from an unregistered supplier, and import of services. The ₹5 crore test and every exclusion above stay the same; only the scope of what must be reported grows. These are your own inward supplies, so you — the recipient — would be the one reporting them, not your supplier. Reverse-charge purchases from a registered supplier aren't added by this notification. GSTN's 16 October 2026 advisory has opened the new supply types on IRP sandboxes only, with no production rollout date announced as of 30 October 2026, and Marg's support pages don't yet document them.

GSP registration happens on the government portal, not inside Marg

Per Marg's own support pages, Marg has "collaborated with Pinnacle Finserve Advisors Pvt. Ltd." to offer e-invoice generation at no extra cost — on an undated Marg support page, Marg states "the users don't have to pay any charges for the installation, Portal, or GSP" when registering through that named partner. As with other ERPs, the GSP ID itself is created on the government e-invoice portal, not inside Marg, and the credentials you set there are then pasted into Marg's own settings screen as API credentials — separate from any portal login you may already hold. Per Marg's documented flow:

  1. Visit einvoice1.gst.gov.in and log in (or complete Registration > e-Invoice Enablement first if the GSTIN hasn't been enabled for e-invoicing before — see the next section).
  2. From the Dashboard, click API Registration > Create API User.
  3. When asked "Do you wish to Register your GSTIN for API Interface," select Through GSP.
  4. In Select your GSP, choose Pinnacle Finserve Advisors Pvt. Ltd. — the provider Marg's support pages name for this integration.
  5. Create a Username and Password, re-enter the password, and submit. Verify the OTP sent to the registered mobile number.

That username and password then go into Marg itself, under GST > GSTR Settings > E Invoice Settings, alongside the GSP selection. Marg's docs don't state any invoice-volume or turnover figure for who can register this way. A claim some sources repeat — that invoice volume above 25,000 a month, or turnover above ₹100 crore or ₹10 crore, gates direct API/GSP access — has no primary GSTN or NIC source behind it, as of 30 October 2026 (GSTN's News & Updates feed checked item by item). Marg's own documentation describes GSP registration as a registration process, and states no qualifying figure.

"Invalid Login Credentials" — the actual cause, per Marg's support page

Marg's support page on this exact error is direct about the cause: "This issue appears when user has mentioned wrong Id Password of E Invoice in the Software." It is a credential-mismatch error, not a Marg bug and not a government-portal outage. The documented fix is to redo the GSP registration cleanly and re-enter the resulting credentials:

StepWhereWhat you're doing
1. Re-create the API usereinvoice1.gst.gov.in > API Registration > Create API UserSelect Through GSP, choose Pinnacle Finserve Advisors Pvt. Ltd., set a fresh Username and Password, verify the OTP
2. Open E Invoice Settings in MargGST > GSTR Settings > E Invoice SettingsOpen the settings window for editing
3. Match the GSP fieldSelect Your GSPSet it to the same provider used at registration (Marg's docs show "MyGST Cafe" as the Pinnacle-branded option in this dropdown)
4. Re-enter credentialseInvoice Login Username & PasswordType the exact username and password created in Step 1 — not your government e-invoice portal login, which is a separate credential entirely

Per Marg's page, completing that sequence is what stops the alert appearing "at the time of uploading E Invoice." The distinction worth holding onto: your e-invoice portal login (used to browse the dashboard) and the API user created "Through GSP" are two different accounts. Marg's page specifies that what belongs in those fields is "the Api Id and Password of the E invoice" — the credentials created under API Registration, not the portal login. It doesn't name "typed the portal login" as a specific cause, but its fix names the API credentials specifically.

A different error that looks similar: e-invoicing never enabled on the GSTIN itself

Marg's support pages separately document a different failure at the same upload step: "Error from IRP e-Invoice options are not enable for this GSTN." Its documented cause is not a credential mismatch — it's that "the user has not activated e-Invoice from the e-Invoice portal" at all. This is the step that can make the upload option in Marg look broken even after GSP registration is done correctly: if the GSTIN isn't already enabled for e-invoicing — GSTN's 16 June 2023 advisory auto-enabled taxpayers at ₹5 crore-plus turnover, so this mainly catches a GSTIN that was never auto-enabled — Registration > e-Invoice Enablement on einvoice1.gst.gov.in needs completing. Marg's own fix page for this error puts enablement first, ahead of the GSP/API registration steps described above.

Two different gates, two different fixes. "Invalid Login Credentials" is a credential mismatch between Marg's saved settings and an active GSP-registered API user. "e-Invoice options are not enable for this GSTN" is the GSTIN itself never having completed e-Invoice Enablement on the portal. Re-registering a GSP account fixes the first; it only fixes the second if enablement happens to get done in the same pass. If the "Generate eInvoice" screen in Marg won't upload anything and no settings have changed recently, check which of the two errors actually appears before assuming either fix applies.

Changing your GSP in Marg

Marg's support pages document this as a three-part process, named for a specific migration (from Master India Pvt. Ltd. to Pinnacle Finserve Pvt. Ltd.) but structurally the same regardless of which two providers are involved:

  1. Deactivate the current GSP. On einvoice1.gst.gov.in, go to User Credentials > Freeze API User, verify by OTP, select the existing user ID in the dropdown, and click Freeze.
  2. Re-register through the new GSP. Go to User Credentials > Create API User, verify by OTP, select Through GSP, choose the new provider, and set a new, unique username and password — Marg's page is explicit that the previous credentials cannot be reused at re-registration.
  3. Update Marg itself. In Marg, go to GST > GST Settings > e-invoice settings, change Select your GSP to the new provider, and enter the new username and password created in Step 2.

Marg's page orders it freeze-first, then re-register, then update Marg's own settings.

Marg's own pages don't agree with each other on small details here — the GSP dropdown option is labelled "MyGST Cafe" on one support page and "Pinnacle Finserve Advisors Pvt. Ltd." (or just "Pinnacle") on others, and the settings menu path appears as both "GSTR Settings" and "GST Settings" depending on which page and release you're reading. Match whichever your own screen actually shows.

Generating the e-invoice, and generating the e-way bill alongside it

Once GSP registration, e-invoice enablement, Marg's own E Invoice Settings, and — from 15 June 2024, per Marg's documentation — E-Invoice Service activation in Marg Wallet are all in place, the working screen is GST > Generate eInvoice. Set a date range and a status filter (Pending / Uploaded / Cancelled / All), select an invoice, and click Generate eInvoice. Per Marg's documentation, the e-way bill isn't entered as an existing number — it's generated together with the e-invoice via a checkbox and a linked details screen on this same upload step:

  • Tick the e-Way Bill checkbox if the e-way bill should go up together with the e-invoice.
  • Click e-Way Details to open the e-way-specific fields.
  • Marg's page states it is mandatory to fill in Current Date and Transporter Doc. No. / Vehicle No. here.
  • Save, then click Generate eInvoice to upload. A successful upload returns an Acknowledgement No. and Date, with the option to print the e-invoice.

For volume, Marg's bulk flow works the same screen with a Check for Errors step before Generate Bulk eInvoice, returning a per-bill acknowledgement number plus a total-filed/total-failed count — worth reading in full before assuming a bulk run succeeded.

Why a quiet GSP failure is a buyer's problem, not just a filing inconvenience

An invoice that never clears the GSP-to-IRP round trip — because of a stale credential, an un-enabled GSTIN, or a bulk run with unread errors — doesn't just fail to print a QR code. It never gets a valid IRN, so under Rule 48(5) it "shall not be treated as an invoice" at all, and it never auto-populates into the supplier's GSTR-1. If nobody keys it into GSTR-1 by hand, it never reaches the buyer's GSTR-2B, and the buyer's ordinary vendor-credit claim fails under Section 16(2)(aa) read with Rule 36(4). If the supplier does key it into GSTR-1 manually, it can still appear in the buyer's 2B — but Rule 48(5) means it still isn't a valid invoice, so the credit is exposed under Section 16(2)(a) instead. Either way it's real, blocked or at-risk credit on someone else's return, with nothing in the buyer's own books to explain why. Catching that gap — a supplier whose invoices keep landing without a matching, valid entry in your 2B — before it becomes a missed ITC claim is exactly the kind of continuous, invoice-by-invoice check that's painful to do by hand across a purchase register with any real vendor count.

Video walkthrough by Success 0 Km — embedded with credit; the guide above is our own.

This guide is written from Marg ERP's own support pages, not from the video.

How Recoup fits

Recoup doesn't register GSPs or generate IRNs — that's Marg and the GSP layer's job, and getting the setup above right is table stakes for that to work at all. What Recoup does is sit on the other side of the same chain: it reconciles your purchase register against what actually lands in your GSTR-2B, and checks that vendor invoices carry a valid IRN before you book the credit on them — naming the specific supplier and invoice behind a credit that never arrived, including the ones stuck because a vendor's own Marg, or any other, e-invoicing setup quietly failed.

An invoice stuck in Marg's Pending list on the supplier's side shows up as missing credit on the buyer's side.

Recoup reconciles your purchase register against GSTR-2B continuously and names the exact supplier and invoice behind credit that never arrived.

Book a demo →

Related guides