All articles
SaaS discoveryShadow IT· 11 min read

How to Find Every SaaS Subscription Your Company Is Paying For

Learn how to uncover shadow SaaS, duplicate tools, unused subscriptions, and upcoming renewals across cards, email, Drive, and Slack — and why the answer isn't in any single system.

Written by ClearSpendPosted July 13, 2026

Editorial illustration for the article

Most companies don’t have a purchasing problem. They have a scattered data problem.

The proof that a subscription exists is never in one place. The charge is on a corporate card. The invoice is in an employee’s inbox. The contract is a PDF in someone’s Drive folder. The people actually using the tool are talking about it in a Slack channel that Finance has never opened. Each system holds one fragment of the truth, and no fragment is enough on its own.

That’s why the standard advice — “review your general ledger” — finds maybe half of what you’re paying for. The ledger shows you charges. It doesn’t show you owners, contract terms, renewal deadlines, or whether anyone still logs in. And increasingly, it doesn’t even show you the vendor.

The scale of the problem isn’t theoretical. BetterCloud’s 2025 research found that organizations used an average of 106 SaaS applications. Zylo’s 2025 SaaS Management Index reported that lines of business controlled 70% of SaaS spend, while IT accounted for only 26.1%. When purchasing is decentralized but the evidence is scattered across four different systems, unknown subscriptions aren’t a failure of discipline. They’re the expected outcome.

Here’s how to actually find them.

Why your ledger can’t tell you what you’re buying

Open your card statement and look for these:

PADDLE.NET* MARKETPLACE
FS *SOMECOMPANY
DRI*TECHVENDOR

None of those are the software you bought. Paddle, FastSpring, and Digital River are merchants of record — payment infrastructure that thousands of software vendors sell through. The descriptor names the processor, not the product. Your team could be paying for three different tools through Paddle and your ledger would show three nearly identical lines.

Even when the vendor name does appear, the descriptor tells you nothing about which plan, how many seats, whether it auto-renews, or who owns it. A charge is a fact without context. Discovery means reattaching the context.

A subscription goes invisible whenever the fragments get separated:

  • The purchase was made on a corporate card outside Procurement.
  • The invoice went to the employee who signed up, not to Accounts Payable.
  • The contract lives in a personal Drive folder, disconnected from any inventory.
  • The team uses and discusses the tool in Slack, but IT never sees the activity.
  • The original owner changed roles or left — and the tool kept renewing.
  • A free trial converted automatically and nobody noticed the first charge.
  • Two departments bought separate accounts for tools that solve the same problem.

Every one of these is a normal, well-intentioned action. The invisibility comes from the scattering, not from anyone doing anything wrong.

The four places the evidence lives

1. Corporate cards and financial records

Card and transaction data is your foundation: it’s the only source that proves money actually changed hands. If you’re doing this manually:

  1. Export 13 months of transactions (13, not 12, so annual renewals appear at least once).
  2. Sort by merchant descriptor and flag anything that recurs at a regular interval.
  3. Separately flag every charge from a merchant-of-record processor (Paddle, FastSpring, Digital River, Gumroad) — each one needs a matching invoice or email to identify the real vendor.
  4. Pull employee reimbursements and repeat the process. Reimbursed software is where shadow SaaS hides best, because it never touches a company card at all.

For every recurring charge, you’ll eventually need: the application and plan, the cost and billing frequency, the purchasing department, a named business owner, the renewal date, and the invoice. The card data alone gives you at most two of those seven.

2. Gmail and shared inboxes

Every subscription generates an email trail: receipts, trial confirmations, renewal notices, payment failures, seat invitations. Email is usually the only place where the vendor’s real name, the plan, and the price appear together.

If you’re searching manually, these Gmail operators do most of the work:

subject:(invoice OR receipt) newer_than:1y
"your subscription" OR "renewal notice" newer_than:1y
"trial ending" OR "trial expires"
"payment successful" OR "payment failed"
from:(billing OR invoices OR receipts OR noreply) "subscription"

Run these against Accounts Payable inboxes first, then against the inboxes of anyone with purchasing authority. The goal is not to read employee communication — it’s to find billing signals that connect a mystery charge to a real vendor and a real owner.

This is also where you’ll decode the merchant-of-record charges from step one: a PADDLE.NET* line on the card almost always has a matching Paddle receipt in someone’s inbox naming the actual product.

3. Google Drive and contract storage

Drive holds the documents that answer questions no charge or receipt can:

  • Is the agreement monthly or annual?
  • Does it auto-renew, and how much cancellation notice does it require?
  • How many seats or usage units were purchased?
  • Which legal entity signed?

Search Drive for order forms, MSAs, DPAs, and anything titled with a vendor name plus “agreement,” “order,” or “quote.” The cancellation notice period matters more than almost anything else you’ll find: a 60-day notice requirement on an annual contract means your real decision deadline is two months before the renewal date on your calendar.

4. Slack and collaboration activity

Financial data tells you a tool is paid for. Slack tells you whether it’s alive. The signals worth looking for:

  • A dedicated channel for the tool (#figma, #datadog-alerts) with recent activity — strong evidence of operational use.
  • App integrations posting into channels (alerts, deploy notifications, form submissions) — the tool is wired into workflows, not just paid for.
  • Invitation and onboarding messages (“I added you to our Notion workspace”) — these identify the actual admin, who is often not the person whose card is charged.
  • Total silence about a vendor that’s been billing for a year — a candidate for the “does anyone actually use this?” question.

This matters most when the buyer, the administrator, and the daily users are three different people — which, at 106 applications, they usually are.

Turn the fragments into one record

Finding subscriptions is only the first step. Each application needs a single consolidated record:

FieldWhy it matters
Vendor and applicationEstablishes what the company is actually buying
Cost and billing cycleShows the financial commitment
Business ownerCreates accountability
Department or cost centerEnables allocation and reporting
Renewal dateCreates time to review or negotiate
Cancellation notice periodPrevents missed decision windows
Paid seats or usage tierEstablishes purchased capacity
Recent usageShows whether the tool is delivering value
Contract and invoiceSupports reconciliation and negotiation
Overlapping toolsReveals consolidation opportunities

The FinOps Foundation recommends exactly this: build a comprehensive SaaS inventory from financial records, identity logs, and security tools, then connect applications to owners, contracts, renewal dates, usage, and cost allocation. It also notes that decentralized purchasing and corporate-card spend require organization-level visibility rather than isolated department records (FinOps for SaaS).

Here’s the honest catch with doing all of this manually: the four searches above will take a finance team days the first time, and the result starts going stale immediately. Every new card charge, every trial conversion, every departing employee reopens the gap between the inventory and reality. A spreadsheet is a snapshot of a moving target.

What complete visibility changes

Visibility is not primarily about cutting software. It changes the timing and quality of decisions.

With a complete inventory, Finance forecasts renewals instead of reacting to charges. IT investigates shadow software and closes accounts after offboarding. Procurement walks into negotiations with accurate usage and seat data. Business leaders compare overlapping tools before approving a third one that does the same job.

How ClearSpend automates this

ClearSpend was built around the scattered-data premise directly: it connects to Gmail, Google Drive, and Google Workspace, plus company-card data, and reassembles the fragments automatically. When a charge appears, ClearSpend looks for the matching invoice or receipt across your inbox and Drive and attaches it to the subscription record — price, owner, renewal date, and the supporting document, together in one place.

And when it can’t find a match, it doesn’t guess. The charge becomes a flagged subscription that’s surfaced to you for review — which is exactly what you want from a finance tool: the unknowns made visible, not silently filed.

Because ClearSpend is AI-native, the parsing handles the messy documents that break rule-based tools — mixed currencies, inconsistent invoice formats, dates that need real interpretation. And through its MCP integration, your subscription data isn’t locked in another dashboard: you can query it directly from the AI tools your team already works in, asking “what renews in the next 60 days?” the same way you’d ask a colleague.

Then there’s the last-mile problem: a renewal notice is exactly the kind of email that gets buried. So ClearSpend delivers renewal alerts to both email and Slack, with enough lead time to review, cancel, downgrade, or renegotiate before the charge lands.

The goal is not to restrict useful software. It’s to make every subscription visible enough to manage deliberately.

A simple place to begin

Three questions:

  1. Can we produce one current list of every SaaS subscription we pay for?
  2. Does every application have a named owner and a renewal date?
  3. Can we tell whether paid capacity is still being used?

If any answer is no, the company doesn’t yet have reliable SaaS visibility — and the fix is following the evidence, not sending another survey.

Once discovery is in place, the next step is a structured review. Use the SaaS spend audit checklist to evaluate ownership, usage, duplication, contracts, and renewal exposure.

Find out what your company is actually paying for.

Start for Free or See a Live Demo.

FAQs

What is SaaS discovery?

SaaS discovery is the process of identifying every software subscription an organization uses or pays for, including approved applications and shadow SaaS purchased outside normal IT or Procurement workflows.

Why are card transactions not enough to track SaaS?

Card data confirms a charge, but often can’t identify the vendor (merchant-of-record processors like Paddle and FastSpring appear instead of the product name), and never shows the owner, contract terms, renewal deadline, seat count, or actual usage. Reliable tracking combines financial data with invoices, contracts, email, and operational signals.

What is shadow SaaS?

Shadow SaaS is software adopted or purchased outside the organization’s standard approval and visibility processes. It may still provide value, but it creates financial, security, and operational risk when nobody can see or govern it centrally.

Sources