If you run finance or operations at a 50- to 300-person Indian company, you already know the drill. It's the last week of the month, and somewhere between the payroll run and the GST filing deadline, someone on your team is downloading PDFs from Slack, Zoom, Notion, Figma, AWS, and eleven other vendor portals, cross-referencing card statements, and trying to figure out why the Razorpay charges don't match the invoice amounts. This is not a technology problem. It's a procurement design problem.
The core issue is simple: 30 separate SaaS invoices from 30 different billing systems will cost your finance team more in time, ITC losses, and missed renewals than the tools themselves are worth to manage individually. Most growing Indian companies don't realize how much that fragmentation costs until they sit down and count it.
shadow IT SaaS audit means in practice — the GST mechanics, the reconciliation math, the pricing leverage you're likely leaving behind, and how to audit what you're spending before you consolidate anything. Real numbers throughout, mostly from what we see with 80+ customers across Indian mid-market companies.
The Real Cost of 30 Separate SaaS Invoices
Let's start with the time cost, because it's the most underestimated. A finance associate at a 120-person company spending 4 to 6 hours per month chasing, downloading, and coding individual vendor PDFs is burning roughly 60 to 72 hours per year on pure SaaS admin. At a fully-loaded cost of ₹600 per hour, that's ₹36,000 to ₹43,000 in staff cost, doing work that produces zero business value.
The GST leakage is worse. Most overseas SaaS vendors issue invoices in USD with no HSN code, no Indian GSTIN, and sometimes the wrong legal entity name. Each of those gaps is grounds for an ITC denial during a scrutiny assessment. 18% GST on ₹5 lakh of annual SaaS spend is ₹90,000 in input tax credit you're entitled to — and most finance teams we talk to are recovering less than half of it because their invoices don't meet the documentary requirements.
SaaS price increases in India Indian credit cards typically carry a 1% to 3.5% foreign exchange conversion charge plus any card network markup. On a ₹30 lakh annual SaaS portfolio, that's ₹30,000 to ₹1 lakh in charges that don't show up as SaaS cost anywhere — they're buried in bank fee line items.
And then there's the audit risk. When 8 different cards across 5 departments are paying for SaaS tools with no central procurement record, your auditor's first question in a GST audit is going to be uncomfortable. The absence of a clean ledger isn't just an inconvenience — it's a compliance exposure.
Key takeaway: The hidden cost of fragmented SaaS invoicing — ITC denials, FX markups, and staff hours — typically exceeds ₹1 lakh annually for a 100-person company, before counting a single duplicate subscription.
What GST-Clean SaaS Invoicing Actually Means
GST on SaaS India, so it's worth being precise. Under the OIDAR (Online Information and Database Access or Retrieval) rules, foreign SaaS vendors selling to Indian businesses are required to charge and remit 18% GST. Most of them do. But charging GST and issuing a GST-compliant invoice are two different things.
A valid tax invoice for ITC purposes under Indian GST rules must carry: your company's legal name as the billing entity, your GSTIN, the vendor's GSTIN (or the intermediary's, if applicable), the HSN/SAC code for the service, and the invoice number in a format that satisfies Rule 46 of the CGST Rules. A generic PDF receipt from Slack's Singapore entity with your email address as the billing detail will not satisfy these requirements.
When an Indian intermediary — a licensed reseller or procurement platform — bills you instead of the overseas vendor, the invoice is issued under Indian GST law by a registered entity. The ITC claim becomes straightforward. The document has everything a scrutiny assessment needs.
Most Indian SMBs are paying 18% GST on their SaaS subscriptions and then failing to claim it back — not because they're ineligible, but because the vendor's PDF doesn't meet the documentary standard a GST officer will accept.
The practical implication: routing SaaS purchases through an Indian procurement intermediary with a proper consolidated invoice isn't just about convenience. It's about recovering tax credit you've already paid and are legally entitled to claim.
Run a free SaaS spend audit — find every hidden subscription
How Reconciliation Breaks Down Across Teams
Shadow IT is real, and it's more widespread than most ops heads want to admit. In a 100-person company, our discovery data consistently shows that 30% to 40% of active SaaS subscriptions were signed up by individuals, not by IT or finance. Someone on the marketing team signed up for a design tool on their personal card. A developer spun up an AWS sub-account. A sales manager bought a prospecting tool during a trial and never cancelled it.
The result is a ledger that's structurally incomplete. The AP team's view of SaaS spend is whatever hits the company Amex and the two Razorpay accounts they know about. The actual spend picture includes personal cards that get expensed irregularly, sometimes months late, sometimes never.
Here's a real scenario that illustrates the problem. A 120-person B2B software company we onboarded had 43 active SaaS tools across 9 credit cards. Their internal estimate of SaaS spend was ₹14 lakh per year. The actual figure, after a full discovery, was ₹22.6 lakh per year. The gap — ₹8.6 lakh — was entirely in tools that either hadn't been expensed, had been expensed to the wrong cost center, or were being paid by employees who'd long since forgotten they signed up. Cleaning that up took two weeks and freed up ₹3.1 lakh in annualized spend from tools nobody was actively using.
Watch out: If your month-end close involves manually cross-referencing SaaS invoices against card statements from more than 2 payment sources, you're already operating with an incomplete ledger. The subscriptions you don't know about are the ones that will surface in a GST audit.
Consolidated Billing and the Pricing Leverage You Are Leaving Behind
This is the part of the conversation that tends to get CFOs' attention quickly. When you buy SaaS seat-by-seat, vendor-by-vendor, you're a small customer in each vendor's account book, even if your aggregate SaaS spend is substantial. When a procurement partner consolidates volume across their customer base and negotiates at the vendor level, the pricing dynamics change entirely.
The discounts we've negotiated with anchor vendors (Microsoft, Google, AWS, Slack, Zoho, among others) run between 10% and 35% depending on the product and volume tier. These are not coupon codes or promotional rates that disappear at renewal. They're partner-tier pricing that holds year over year, because they're tied to the intermediary's committed volume, not a one-time deal.
Annual versus monthly billing is another lever that consolidation makes easier to pull. When you're managing 30 tools individually, switching 15 of them from monthly to annual billing requires 15 separate admin decisions, 15 separate payment authorizations, and trusting that each tool will actually be useful for the full year. When those tools flow through a single procurement entity, the decision is made once and the savings are immediate — typically 15% to 20% on tools that offer annual discounts.
To make this concrete: a 200-seat company paying for Microsoft 365 Business Standard (roughly ₹1,260 per seat per month at retail), Google Workspace Business Starter (roughly ₹150 per seat per month at retail), and Slack Pro (roughly ₹750 per seat per month at retail) is spending approximately ₹51.6 lakh per year across those three tools alone. A 20% blended discount from consolidated procurement returns ₹10.3 lakh annually — without changing what anyone uses or how they work.
You can explore what discounted pricing looks like for your specific stack in our marketplace, where we list India-first vendor pricing across 100+ tools.
Key takeaway: Consolidated procurement isn't about squeezing vendors — it's about matching the buying power your aggregate spend already justifies, which individual seat purchases will never achieve.
The Mechanics of Centralizing SaaS Procurement
Here's how the actual process works, without the hand-waving about "digital transformation."
Step 1 is discovery. Connect your company's work inboxes (Gmail or Outlook), major card statements, and HR onboarding records. The goal is surfacing everything being paid for, not just what IT already knows about. This takes 30 minutes, not 3 weeks.
Step 2 is triage. Categorize what you find into business-critical (can't operate without it), actively used but not critical, and unused or underused. You need actual utilization data for this, not self-reported usage from team leads. Login frequency, active seat counts, and feature engagement tell a different story than "we definitely use it."
Step 3 is routing renewals through a single entity. Tools that pass the triage move to consolidated billing under one GSTIN. Unused tools get cancelled before renewal, not after. This step alone typically eliminates 15% to 25% of the SaaS budget.
Step 4 is governance. New SaaS purchases go through an approval workflow before a card gets charged. The workflow doesn't need to be complicated — a Slack message that routes to a finance approver is fine — but it needs to exist. Shadow IT doesn't survive a functioning approval process.
For companies without a dedicated IT lead (which is most companies in the 50 to 200 headcount range), the AI CIO handles the ongoing monitoring: renewal alerts, utilization drops, new shadow-IT flags, and license reclamation when someone leaves the company.
Talk to our team — see your SaaS savings in a 15-minute call
What One Invoice Actually Contains (and Why Finance Teams Love It)
A consolidated SaaS invoice from an Indian procurement intermediary is a fundamentally different document from a vendor PDF. It contains a line-item breakdown per vendor, per team, and per cost center — all on a single GST-compliant invoice issued under Indian law. One document, one GSTIN, one ITC claim, one journal entry.
Renewal dates, billing cycles, and license counts are on the same document. Your auditor gets a clean record. Your AP team doesn't need to log into 30 vendor portals to download PDFs that may or may not have the right billing details.
For companies running Tally ERP or Zoho Books, a well-structured consolidated invoice maps directly into your existing chart of accounts without manual data entry. The invoice format can be aligned to your cost center structure so each line item hits the right GL code automatically.
Action: Ask your current SaaS vendors to issue a test invoice to your company GSTIN and check whether it includes an HSN/SAC code and a valid invoice number under Rule 46. If more than 3 of them can't produce a compliant document, you're already losing ITC you've paid for.
The time saving is consistent across the customers we work with. Finance teams report a 60% to 70% reduction in SaaS-related reconciliation hours after moving to a consolidated billing model. For a company where SaaS admin was consuming 5 hours of a finance associate's month, that's getting 3 to 3.5 hours back every month — time that goes toward analysis, not admin.
Common Objections from CFOs (and the Honest Answers)
"We'll lose our direct vendor relationships." In practice, the relationship with the vendor's account manager usually continues. The procurement intermediary handles billing and renewals; your team still interacts with the vendor's support and customer success teams directly. For enterprise contracts with custom SLAs, the intermediary works alongside the vendor relationship, not instead of it.
"What stops the intermediary from marking up prices?" This is a fair question and worth asking directly. Look for pass-through pricing with a transparent service fee, not a hidden margin baked into the "discounted" price. At Easexpense, we show customers the vendor's base price and our fee separately. If a vendor quotes 20% off, you see 20% off — not 20% off minus an undisclosed intermediary cut.
"Migration sounds painful." For most tools, migration happens at renewal, not mid-contract. The actual effort required to move 20 tools is roughly 2 to 4 hours of admin work spread over the next billing cycle, not a project that requires IT involvement. The perceived complexity is almost always larger than the real effort.
"We're too small for this to matter." Here's a break-even calculation worth running. A 60-person company with 20 active SaaS tools at an average of ₹8,000 per tool per month is spending ₹19.2 lakh per year. A 15% combined saving from discounts, ITC recovery, and eliminating unused licenses returns ₹2.88 lakh in year one. That exceeds any reasonable management cost for a consolidation service.
Running a SaaS Spend Audit Before You Consolidate
Consolidating your SaaS billing without auditing first is a mistake. You don't want to lock in a year of billing for tools that half your team stopped using three months ago. The audit comes first, always.
The fastest way to do this is connecting your company's work inbox to an automated discovery tool. In about 30 seconds, it reads invoice-pattern emails and surfaces every recurring subscription — vendor name, monthly amount, renewal date, and which email address (read: which employee) signed up. No self-reporting required, no IT ticket needed.
What you get is a working inventory: the tools you knew about, the ones you forgot, and the ones you definitely didn't authorize. From there, the triage process from Step 2 above is straightforward because you're working from actual data, not memory and spreadsheets.
You can run this right now for your company at our free SaaS spend audit. It takes 30 seconds to connect an inbox, and the output is a full subscription inventory with spend and renewal data. Most finance teams find at least 3 to 5 tools in the first run that either shouldn't exist or haven't been expensed correctly.
Key takeaway: Audit before you consolidate — you're cleaning the house before you renovate, and the inventory you get will shape every procurement decision that follows.
When Consolidation Makes Sense (and When It Does Not)
The sweet spot for consolidated SaaS billing is a company with 15 or more active SaaS tools, at least 50 employees, and at least one person spending 3 or more hours per month on SaaS admin. If all three are true, the economics are clear.
There are situations where consolidation adds less value. A single-product startup under 20 people with 4 or 5 tools and direct vendor relationships with favorable pricing doesn't need an intermediary layer. The overhead isn't justified by the savings at that scale.
But if any of the following are true, consolidation is probably overdue: you've had a missed or surprise renewal in the last 12 months; ITC claims have been rejected or left unclaimed on SaaS invoices; someone in leadership has complained about shadow IT; or your finance team can't produce a complete SaaS inventory on demand. Those are the signs that the fragmentation has already started costing you, and the cost is compounding each renewal cycle you wait.
See how your current stack compares against benchmarks for your company size on our pricing page, or browse tools and their discounted India pricing in the marketplace.
Frequently asked questions
Can I claim GST input tax credit on SaaS subscriptions bought from foreign vendors?
It depends on how the invoice is structured. Foreign SaaS vendors selling to Indian businesses under the OIDAR (Online Information and Database Access or Retrieval) rules must charge 18% GST and register for GST in India. If the invoice carries a valid GSTIN, your company's legal name, and the correct HSN/SAC code, you can claim ITC. The problem is that most overseas vendor PDFs fail at least one of these requirements — they show your email address instead of your legal entity name, or they omit the HSN code, or they're issued from a non-registered foreign entity. Routing purchases through an Indian intermediary that issues a compliant tax invoice under its own GSTIN is the most reliable way to resolve this without chasing each vendor individually.
How does consolidated SaaS billing work for a company with multiple GST registrations across states?
When a company has branch GST registrations in multiple states, each invoice ideally maps to the GSTIN of the consuming entity — meaning the Delhi branch's SaaS tools should be invoiced to the Delhi GSTIN, not the head office registration in Bengaluru. A good procurement intermediary handles this by issuing separate GST-compliant invoices per registered entity rather than a single catch-all document, which keeps ITC claims clean at each GSTIN level and avoids cross-state credit complications. This is particularly important for companies with manufacturing or warehouse operations across states, where GST officers will scrutinize input credits tied to the registered place of supply. If you have 3 or more state registrations, make sure your intermediary can issue state-wise invoicing before you consolidate.
What is the typical saving when you consolidate SaaS purchasing through a single vendor?
In our experience with 80+ customers, direct discounts from consolidated vendor partnerships run between 10% and 35% depending on the tool and the volume tier. Add the recovered ITC on previously non-compliant invoices (typically 18% of the spend that was being written off), the reduced finance team hours (valued at ₹30,000 to ₹60,000 per year for most companies), and the savings from eliminating unused licenses discovered during the initial audit. Total first-year savings regularly land between 20% and 40% of prior SaaS spend. The ITC recovery alone often pays for the first year of any management fee within the first quarter.
How do I find out which SaaS tools my company is currently paying for?
The fastest method is connecting your company's work inbox to an automated discovery tool that reads invoice-pattern emails and recurring payment notifications. This surfaces every active subscription — the vendor name, the monthly cost, the renewal date, and the email address that signed up — without requiring employees to self-report, which they notoriously underreport. The Easexpense free SaaS spend audit does exactly this in about 30 seconds at easexpense.com/saas-spend-audit. Most finance teams find tools in the first run that haven't been expensed in months, which means the actual SaaS spend is higher than whatever number is in the budget model.
Does centralizing SaaS procurement mean we lose control over which tools individual teams use?
No, but it does mean new purchases go through an approval layer before a card gets charged. Most ops and IT leads find this is a feature rather than a constraint — teams still request the tools they need, and the right tools still get approved quickly. The difference is that finance sees the request, the cost, and the renewal date before it becomes a line on an unknown credit card statement three months later. Teams that felt they "lost control" in a badly designed approval process were typically working with overly bureaucratic sign-off chains, not with consolidation itself. A well-designed approval workflow for a 100-person company can process a new tool request in under 24 hours.
What happens to existing vendor contracts when we move to consolidated SaaS billing?
Most SaaS contracts are seat-based and billing is managed at the account level, which means they transfer at renewal without requiring a new contract or any renegotiation. The procurement intermediary takes over the billing relationship at the next renewal cycle, and you continue using the software without any interruption to access, data, or support. For tools with annual contracts that are mid-cycle, the intermediary typically manages the transition at the next billing date and holds the current pricing until then. In practice, the migration effort for 20 tools spread over 2 to 3 billing cycles is 2 to 4 hours of admin work — not a project that requires IT involvement or system changes.
Is consolidated SaaS billing only relevant for large companies, or do smaller teams benefit too?
The break-even point is lower than most finance teams expect. A 60-person company paying for 20 SaaS tools at an average of ₹8,000 per tool per month is spending roughly ₹19.2 lakh annually on software subscriptions. A 15% combined saving from vendor discounts, ITC recovery on previously non-compliant invoices, and eliminating unused licenses returns ₹2.88 lakh per year — well above any reasonable management overhead cost. At 50 employees, the recurring pain of fragmented invoicing is already real even if the absolute rupee savings look modest at first. The finance team hours alone justify the change before counting a single rupee of pricing discount.