How to track SaaS spend across multiple brands and entities
If you operate more than one brand, your SaaS spend is probably split across cards, emails, and entities you cannot see at once. Here is a structured way to bring it together.
Tracking SaaS spend gets exponentially harder the moment you add a second brand. Subscriptions get bought on whichever credit card was nearest, signed up under whichever email a teammate happened to be logged into, and assigned — implicitly — to whichever entity people remember at month-end. The result is a number on the P&L that nobody fully trusts.
The four-axis problem
Multi-brand SaaS spend is not a list. It is a four-axis problem: every subscription has an owning entity, an owning brand, a payment method, and an account email. Most tools track only one or two of those axes well. To allocate spend cleanly you need all four resolved at once, for every line item.
Step 1: pull every subscription into one place
Start with a single inventory. Pull subscriptions from accounting exports, vendor portals, and finance statements. Do not worry about cleanliness yet — duplicates are useful signal because they often reveal the same tool being paid for twice across brands.
Step 2: attach each subscription to its four axes
For every subscription, resolve the four axes explicitly:
- Entity: which legal company is the contracting party?
- Brand: which product or business unit benefits from the spend?
- Payment method: which card, bank, or invoice line actually pays?
- Identity: which email or login is the account registered under?
When all four are filled in, allocation becomes deterministic. When even one is missing, you have an orphan — a subscription that will create reconciliation work every month until it is resolved.
Step 3: detect orphans and ghost spend
Orphans fall into a few common shapes. Subscriptions paid by a personal card that should be on a corporate one. Tools registered under a former teammate's email. Accounts assigned to a brand that no longer exists. Each one is recoverable, but only if your inventory makes them visible.
Step 4: keep the graph in sync
An allocation map that is correct today drifts tomorrow. The teams that maintain clean attribution treat their subscription graph as a living system: every new tool gets added with its four axes resolved up front, every card change rolls through to every subscription it backs, and every entity change triggers a review. The work goes from a quarterly cleanup project to a small, continuous habit.