If you're the person who owns finance or operations at a growing Indian company, you've probably been there: it's the last week of the quarter, your CA is reconciling GSTR-2B, and three SaaS invoices don't match. One vendor forgot to put your GSTIN on the invoice. Another used CGST and SGST on what should have been an interstate IGST charge. A third is a US-based tool your team signed up for six months ago and no one thought to self-invoice under RCM. The input tax credit for all three is now at risk.
The problem isn't malice. Most SaaS vendors auto-generate invoices from billing systems that were built for global markets, not Indian GST compliance. They'll happily send you a PDF that looks official, charges 18%, and still manages to be useless for ITC purposes because it's missing a SAC code or has the wrong place of supply. By the time you notice, the vendor's filing period has closed and you're filing a dispute instead of a return.
consolidated SaaS billingify when an invoice lands in your inbox, what to do when a vendor can't or won't comply, and how to build the whole thing into your procurement flow so quarter-end stops being a scramble.
Why SaaS Invoices Are a GST Compliance Minefield
SaaS invoices are uniquely messy because they sit at the intersection of two things that don't cooperate well: automated global billing and Indian tax law that demands specificity.
GST on SaaS subscriptionsomers in Germany, Brazil, and Bengaluru. It might say "Tax: 18%" and even deposit something that looks like GST, but if the vendor doesn't have an active Indian GSTIN, that charge isn't real GST. It won't appear in GSTR-2B. You can't claim it. And you now also owe 18% IGST yourself under the reverse charge mechanism.
A single non-compliant invoice can block the ITC claim for that entire vendor's spend for the period. For a company paying ₹8–10 lakh annually in SaaS subscriptions, that's a real cash cost, not an accounting technicality.
The most common failure modes we see across our customer base are: missing or incorrect GSTIN (either the vendor's or yours), absent SAC codes, wrong tax type (IGST vs. CGST/SGST), no place of supply stated, and for larger vendors, no IRN on invoices that legally require one. Every one of these is checkable in under 2 minutes if you know what you're looking for.
Watch out: If your company operates from multiple states and has multiple GSTINs, confirm at account setup with every vendor which GSTIN they're billing to. Changing it retroactively after invoices have been filed is painful for everyone.
The 12-Point GST Invoice Checklist for Every SaaS Vendor
SaaS renewal calendar template Indiarocurement coordinator run through it on every new vendor's first invoice and spot-check it on renewals.
- Supplier's legal name exactly as registered on the GST portal, not a brand name or trade name alone.
- Supplier's GSTIN, active and matching the entity that's actually issuing the invoice (more on this below).
- Supplier's registered address as it appears on the GST portal.
- Your company's GSTIN on the face of the invoice. Not optional. Not "available on request."
- Your company's legal name and billing address. This should match your GST registration, not just the delivery or billing contact email.
- Unique invoice number in the vendor's sequential series, plus the invoice date.
- SAC code for the specific service. Most SaaS falls under 998314 (IT infrastructure and network management) or 998315 (IT consulting and support). The code must be present and must match the nature of the service.
- Taxable value stated separately from tax.
- GST rate (18% for most SaaS) and the split: CGST + SGST for intrastate, IGST for interstate or imports. Both the rate and the rupee amount must appear.
- Place of supply stated explicitly. For B2B SaaS, this is your registered state, not the vendor's.
- IRN (Invoice Reference Number) and QR code, if the vendor's annual turnover exceeds ₹5 crore. No IRN means the invoice isn't legally valid for ITC.
- Total invoice value in INR (or the INR equivalent if billed in foreign currency, along with the exchange rate and date).
That's it. 12 fields. If all 12 are present and accurate, the invoice is usable. If any are missing, you have a compliance gap before you've even processed payment.
Run a free SaaS spend audit — find every hidden subscription
Key takeaway: A GST-compliant SaaS invoice isn't just a receipt; it's a legal document with 12 mandatory fields. Missing even one can invalidate your ITC claim for that period.
GSTIN Fields: Yours, Theirs, and Why Both Must Be Exact
The GSTIN field is where most errors cluster, because there are two of them and both have to be right.
The vendor's GSTIN must belong to the entity actually issuing the invoice. This matters more than it sounds. Several large SaaS vendors operate through separate billing subsidiaries. You might contract with "Vendor India Pvt Ltd" but receive invoices from "Vendor Billing Solutions Ltd." If those are different legal entities with different GSTINs, and the billing entity's GSTIN doesn't match what's registered on the portal, the invoice is non-compliant. Always verify the vendor's GSTIN at gstin.gov.in before the first payment. It takes 60 seconds.
Your GSTIN must appear on the invoice for the transaction to show up as a B2B supply in GSTR-2B. Without it, the vendor may file it as a B2C transaction. It won't appear in your GSTR-2B reconciliation, and ITC is not claimable. Provide your GSTIN at account setup, confirm it on the first invoice, and escalate immediately if it's wrong.
Mismatched GSTINs are the single most common reason ITC claims get rejected in GSTR-2B reconciliation — and almost always preventable at onboarding.
When a vendor's billing entity differs from their contracting entity, ask for written confirmation of which GSTIN will appear on invoices before signing. Some vendors can update their billing systems; others can't. Knowing upfront saves a dispute six months later.
Action: Before adding any new SaaS vendor to your accounts payable flow, verify their GSTIN on the GST portal and save a screenshot. File it with the vendor onboarding record.
Reverse Charge Mechanism: When You Owe the GST, Not the Vendor
This is the section most finance teams wish someone had explained to them before their first GST audit.
When you buy a service from a supplier outside India, the supplier can't charge Indian GST because they're not registered here. But the transaction is still taxable in India. The government's solution is the Reverse Charge Mechanism (RCM): you, the buyer, are responsible for calculating and depositing the tax.
In practice, this means: for every SaaS tool billed in USD, EUR, or any non-INR currency by an entity with no Indian GST registration, you must self-invoice, pay 18% IGST directly to the government in cash, and then claim that amount as ITC in the same return period. You can't offset RCM liability against your existing ITC balance; it must be paid in cash first.
The tools this affects include AWS billed from Luxembourg, Google Workspace billed from Singapore, Zoom, Loom, Notion, Figma, and dozens of others that don't maintain an Indian GST entity. Check the billing address on every vendor invoice. If it's outside India, ask whether they have an India GST registration. If they don't, RCM applies.
The most common mistake: paying the foreign invoice, assuming GST is someone else's problem, and discovering a liability during an audit two years later, when you also owe interest on the unpaid tax.
Key takeaway: Any SaaS subscription billed from outside India in foreign currency likely triggers RCM. You owe 18% IGST, must self-invoice, and must pay it in cash before claiming ITC.
ITC Eligibility: Not Every SaaS Invoice Qualifies
Assume nothing. Just because you have a compliant invoice doesn't mean ITC is automatically available.
The core rule is straightforward: ITC is available if the subscription is used for business purposes and the vendor is GST-registered. Where it gets complicated is Section 17(5) of the CGST Act, which blocks credits for certain categories. SaaS tools used primarily for employee welfare or personal benefit can be disallowed. If your company pays for a fitness app subscription for employees, that ITC is blocked. A project management tool used for client delivery? Fully eligible.
Timing is another issue. Even if an invoice is perfectly compliant, you can only claim ITC after it appears in your GSTR-2B. If your vendor filed their GSTR-1 late, or filed with errors, the invoice won't appear in your GSTR-2B for that month. You'll have to wait for it to show up and claim it in a subsequent period. This is why monthly reconciliation matters, not quarterly.
For tools that have mixed use, document the business-use justification at onboarding. If 70% of a tool's use is client-facing and 30% is internal admin, you can claim 70% of the ITC. But you need that calculation on record, ideally in writing, before a scrutiny notice arrives asking for it retroactively.
Our platform at Easexpense AI CIO tracks utilization and subscription metadata for exactly this reason: when an auditor asks "what was this tool used for?", you need an answer that isn't just "someone from finance signed up for it."
If you're managing more than 20 SaaS subscriptions and doing ITC reconciliation manually, that's where a structured audit makes sense. Book a 15-minute call and we'll show you how we handle this for customers across our base.
Action: At every new SaaS subscription onboarding, document in writing: (1) which team uses it, (2) what business function it serves, and (3) the percentage of business vs. personal use if mixed. File this with the vendor record.
E-Invoice (IRN) Requirements: Who Must Issue Them and What to Check
E-invoicing under GST is mandatory for vendors with aggregate annual turnover above ₹5 crore. That threshold was set in August 2023 and covers the vast majority of established SaaS vendors operating in India.
A valid e-invoice carries an IRN (Invoice Reference Number) generated by the Invoice Registration Portal (IRP) and a QR code that encodes the key invoice fields. Without these, an invoice from a vendor who crosses the threshold is legally invalid as a tax document. You cannot claim ITC on it, even if every other field is correct.
Verifying an IRN takes seconds. Go to einvoice1.gst.gov.in, enter the IRN, and the portal confirms whether it's genuine and the fields match. Make this a standard step for any vendor billing you more than ₹50,000 in a year.
The practical action here is simple: at the start of each financial year, confirm with each vendor whether their turnover crosses the e-invoice threshold. Small vendors (individual consultants, niche tool builders) may be below it. Large vendors (Zoho, Freshworks, local cloud providers) are almost certainly above it. Update your records accordingly.
Key takeaway: For any Indian SaaS vendor above ₹5 crore turnover, an invoice without an IRN is not a valid GST document. Verify the IRN on the IRP portal for high-value vendors every billing cycle.
Place of Supply Rules for Cloud and SaaS Transactions
Place of supply determines whether the invoice should carry IGST (for interstate transactions) or CGST and SGST (for intrastate). Get this wrong, and even a fully compliant invoice becomes unclaim-able.
For B2B SaaS, the rule is clean: place of supply is the registered address of the recipient, meaning your company, not the vendor's location. If your vendor is in Maharashtra and your company is registered in Karnataka, the supply is interstate and must carry IGST. If the vendor incorrectly applies CGST and SGST instead, that ITC is stuck. You'd need a credit note and a corrected invoice.
Intrastate transactions where IGST has been incorrectly charged present the same problem in reverse. The wrong tax type can't be used.
Multi-location companies face a specific complication. If procurement is centralized in Mumbai but the actual users are in Delhi and Hyderabad, confirm which GSTIN is on each invoice. Each state registration is a separate taxpayer in GST law. A consolidated invoice billed to the Mumbai GSTIN for users in Delhi may create place-of-supply issues depending on the nature of the service. Get clarity on this before the first billing cycle, not after.
Building the Checklist Into Your Procurement Workflow
A checklist that lives in a document nobody opens is not a compliance process. Here's how to make it operational.
At vendor onboarding: collect GSTIN, confirm e-invoice status, note the billing entity name, and record the SAC code they'll use. Don't wait for the first invoice to discover they bill from a different entity than the one you contracted with. This information should be in the vendor record before any payment is approved.
At invoice receipt: run a five-field spot check before releasing payment. GSTIN (both), IRN if applicable, place of supply, SAC code, and tax type split. This takes 3 minutes per invoice and prevents a quarter-end crisis.
Monthly: reconcile invoices received against GSTR-2B. Any invoice you have that doesn't appear in GSTR-2B is a signal your vendor filed late or filed incorrectly. Flag it immediately, not in three months.
Quarterly: review vendors with recurring compliance errors. Send a formal correction request to their account manager. Document when you raised it. If they can't fix it after two billing cycles, escalate internally about whether the vendor relationship is worth the compliance overhead.
For companies managing 25+ SaaS subscriptions, doing this manually is genuinely painful. A consolidated view of all your SaaS invoices, with compliance flags built in, makes the reconciliation step significantly faster. That's what our vendor catalog and spend management layer is designed to do: surface problems at the invoice level before they become return-period problems.
What to Do When a Vendor Cannot or Will Not Fix the Invoice
It happens. A vendor's billing system is inflexible, their India finance team is unresponsive, or their global product team doesn't understand Indian GST nuance. Here's the escalation path.
First, request a credit note and corrected invoice in writing. Email is fine. The date you raised the issue matters if there's ever a dispute about whether you took timely action.
If the vendor is foreign and not GST-registered in India, stop waiting for them to fix something they can't fix. Shift to the self-invoice RCM process. You control that paperwork, it's legal, and it gets your ITC moving.
For Indian vendors who are non-compliant, the escalation path is: account manager first, then their India billing or finance team, then your own CA for a compliance note documenting the issue and your attempts to resolve it. That note protects you if you're ever questioned about why you claimed ITC on an imperfect invoice while pursuing correction.
When the vendor is high-value and repeatedly non-compliant, treat it as a procurement risk, not just a tax nuisance. Non-compliance on a ₹10 lakh annual subscription is a ₹1.8 lakh ITC exposure every year. That's a number worth making a vendor conversation uncomfortable over.
One of the practical advantages of procuring SaaS through Easexpense is that our vendor relationships mean invoice compliance issues can often be resolved through the platform without you having to cold-escalate to a vendor's global billing team. It's one of the less obvious reasons customers stick with us.
Compliance issues with SaaS invoices are not your vendor's problem to care about as much as yours. Build the escalation path into your process before you need it.
Frequently asked questions
What GST rate applies to SaaS subscriptions in India?
Most SaaS and cloud software subscriptions attract 18% GST under Information Technology software services. This applies whether the vendor is Indian or foreign. For foreign vendors without a GST registration in India, the 18% doesn't disappear; instead, the buyer is required to account for 18% IGST under the reverse charge mechanism, self-invoice, and deposit the tax directly to the government. There are narrow categories of software services that may attract a different rate, but for standard SaaS subscriptions, 18% is the rate you should plan around.
Can I claim ITC on SaaS invoices if the vendor is registered outside my state?
Yes, you can, but the invoice must carry IGST rather than CGST and SGST. Under GST law, a B2B SaaS transaction where the vendor and the recipient are in different states is an interstate supply, and place of supply is the recipient's registered state. If the vendor incorrectly charges CGST and SGST on an invoice that should carry IGST, you cannot claim ITC on it. You'll need to request a credit note and a corrected invoice. This is one of the more common errors from vendors whose billing systems default to their own state tax type.
Is reverse charge mechanism applicable on all foreign SaaS tools like AWS or Zoom?
RCM applies when you purchase a service from a supplier located outside India for business use within India. AWS (billed from Luxembourg), Google Cloud (billed from Singapore), Zoom, Notion, Figma, Loom, and similar tools fall into this category when they don't issue an India GST-registered invoice. You must raise a self-invoice, pay 18% IGST in cash (not from your ITC ledger), and then claim that paid amount as ITC in the same return period. One important check: some of these vendors do have Indian GST entities. If they issue an invoice with a valid Indian GSTIN, RCM does not apply and they handle the GST themselves.
Which SaaS vendors in India are required to issue e-invoices?
Any GST-registered vendor with aggregate annual turnover exceeding ₹5 crore in any preceding financial year must generate invoices through the Invoice Registration Portal, producing an IRN and QR code. For the Indian SaaS market, this threshold covers most established vendors. If your vendor clears this threshold and sends you a PDF invoice without an IRN, it is not a valid tax document for ITC purposes. The safest practice is to ask each vendor at the start of every financial year whether their turnover crosses the threshold, and verify IRNs on high-value invoices via the NIC e-invoice portal.
What SAC code should appear on a SaaS invoice?
The most common SAC codes for SaaS and cloud services are 998314 (IT infrastructure and network management services) and 998315 (IT consulting and support services). Some vendors use 998313 for software implementation services or 997331 for licensing of intellectual property. What matters most is that a SAC code is present and reflects the actual nature of the service being billed. A missing SAC code is a compliance gap that can be raised in a GST audit, and it's worth confirming with new vendors upfront what code they'll use.
What happens if a SaaS invoice is missing my company's GSTIN?
Without your GSTIN on the invoice, your vendor may file it as a B2C transaction in their GSTR-1. That means it won't appear in your GSTR-2B, and you cannot claim ITC on it. The fix is prevention: provide your GSTIN at account setup with every vendor and verify it appears correctly on the first invoice before approving payment. If you discover it's missing after the vendor has already filed, request a credit note and amended invoice. Some billing systems allow amendments; others don't, which is why catching it at the first invoice is critical.
How do I reconcile SaaS invoices against GSTR-2B efficiently?
Download your GSTR-2B for the month and match each SaaS invoice by vendor GSTIN and invoice number. Any invoice you received but that doesn't appear in GSTR-2B means your vendor filed late or filed with errors; you cannot claim that ITC until the invoice shows up in a subsequent month's GSTR-2B. For companies managing 20 or more SaaS subscriptions, doing this manually in a spreadsheet is time-consuming and error-prone. A consolidated spend management tool that tracks all your SaaS invoices in one place, with vendor GSTIN records and billing dates, cuts the reconciliation effort significantly. The free spend audit at Easexpense is a practical starting point for understanding how many invoices you're actually dealing with.