Shadow IT: find software nobody approved
Shadow IT is software that a team bought and uses without IT or purchasing knowing about it. Paid shadow IT leaves a trace in the books, so the most direct way to find it is to list every software supplier on the invoices and card statements of the last twelve months and compare that list with the applications you manage. Each supplier without an entry is a find. For each one you name an owner, record the contract and its notice date, and decide whether to adopt the tool, merge it with one you already have, or end it.
Shadow IT is software a team bought and uses without IT or purchasing knowing. You find the paid part of it in the books: every subscription sends an invoice or appears on a card statement. List the software suppliers of the last twelve months, compare them with the applications you manage, and every name without an entry is a find.
Why it is worth finding
A tool nobody manages has no owner for three questions. Who holds a seat and still needs it? When does the contract renew, and by when must notice be given? What company data is in it, and who can still sign in after leaving? There is a cost side as well: a tool booked by one team often does the job of one the company already pays for, as described in finding overlapping SaaS tools.
The cause is rarely bad intent. Booking a subscription with a card takes minutes, an approval may take weeks, and the team has work to do.
Where shadow IT leaves a trace
| Source | What it shows | What it misses |
|---|---|---|
| Supplier invoices | Supplier, product, amount, billing period | Free plans, tools paid privately |
| Company card statements | Small monthly charges, often in a foreign currency | The product behind a payment processor's name |
| Expense claims | Tools one person booked and claimed back | Anything not claimed |
| Sign-in records of the identity provider | Applications people open with their company account | Tools with their own password |
| A question to team leads | What is really in use, and why | What people have forgotten |
Scanning devices, browsers or network traffic is another method, with questions of its own about what an employer may observe. It is not covered here. The method below works with documents the company already has.
Step 1: have an inventory to compare against
You can only find what is missing from a list if there is a list. If none exists, start with the applications IT administers and the contracts purchasing knows. What to record per application is covered in SaaS licence management basics.
Step 2: list the software suppliers on invoices
Take the invoices of the last twelve months and keep the suppliers whose lines are software: subscriptions, licences, hosted services. Add up what each one billed. Twelve months matter, because annual plans appear only once a year. If invoices are not yet sorted by category, that is the first job: see spend analysis basics.
Step 3: compare names, carefully
Match each supplier against the inventory. Names differ: the invoice says the legal name of the company, the inventory says the product. A supplier whose name begins with the product name is the same thing. Resellers and marketplaces need a second look, because one supplier name can hide several products. Read the line items of those invoices.
Step 4: add cards and expense claims
Repeat the comparison with company card statements and expense claims. This is where the small subscriptions are: one seat, booked monthly, by one person. Each is small. Together they are the part of software spend that nobody has looked at.
Step 5: ask before you judge
For every find, ask the person or team behind the order three things: what the tool is used for, who uses it, and whether a managed tool could do the same. The answer decides the next step.
- Adopt. The tool is needed. It gets an owner, an entry in the inventory, its contract and its notice date.
- Merge. A managed tool does the same. The team moves, and the subscription ends at its next date.
- End. Nobody uses it any more. Cancel it before it renews.
What goes wrong
- Treating finds as offences. People stop answering questions, and the next tool is paid privately, where no invoice shows it.
- Looking at one month. Annual subscriptions and quarterly bills are missed.
- Matching by exact name. The same vendor then appears as a find although it has been managed for years.
- Stopping at the list. A find without an owner and a notice date is the same gap as before, with a row in a spreadsheet.
- Counting a saving too early. The spend with an unmanaged supplier is not a saving. Whether anything can be saved is known after the questions in step 5.
A worked example
The figures are invented and round. A company manages 30 applications. Its invoices of the last twelve months show software lines from 36 suppliers. After matching names, 6 suppliers have no application behind them, with 1,200.00, 900.00, 600.00, 600.00, 400.00 and 300.00 billed. Together that is 4,000.00 a year that nobody watches. After asking, three tools are adopted, two are merged into tools the company already has, and one is cancelled. The 4,000.00 is spend, not a saving. What the merged and cancelled tools cost becomes a saving on the date their subscriptions end.
How Cureman does it
Cureman finds unapproved software from invoices and from the applications an organisation manages. It does not scan devices, browsers or networks. Where invoice audit and licence optimisation are both booked, it takes the suppliers on the invoices of the last twelve months whose lines are mostly software and compares them with the application inventory, treating a supplier whose name begins with an application's name as that application. Suppliers with no application behind them are listed in one finding, each with the software spend the invoices show. The finding states no saving, because nobody has quoted one. Its next step is manual: add the supplier as an application, enter the contract from the invoice, and connect it where a connector exists. Connectors only read. From then on seats, plans and activity are read from the vendor's own data, and the renewal is on the list. Software that never appears on an invoice, such as a free plan, is not found this way. The modules are described on the pages about licence optimisation and invoice audit and spend analysis.
Questions and answers
What is shadow IT?
- Software or cloud services that a team uses for work without IT or purchasing having approved or recorded them. Typical cases are a subscription booked on a company card, a tool expensed by one person, or a free plan that later became a paid one. The term describes a gap in the inventory, not misconduct.
How do I find software that departments bought themselves?
- Start with the money. List every supplier that sent a software invoice or appears with a software charge on a card statement in the last twelve months, and compare the names with your application inventory. A supplier with no application behind it is a find. Then ask the person who ordered it what it is used for.
Can shadow IT be found from invoices alone?
- Only the part that is paid for and billed to the company. Free plans, trials and tools paid privately leave no invoice. For those you need other sources, such as the sign-in records of your identity provider or a question to the teams. Invoices are still the best first source, because they also show what the tool costs.
Should unapproved software be forbidden?
- A general ban rarely holds, because teams book tools when the approved ones do not fit their work. A short approval path works better, with one place to ask, an answer within days and a clear owner per tool. What matters is that every paid tool is in the inventory with its contract and its notice date.