Software Spend Detection in SAM Pro

[Maniteja_2003]

Every SAM program eventually hits the same wall. Discovery covers what's installed. Entitlements cover what's been licensed and purchased through procurement. But between the two, there's still a gap: software bought through expense reports, credit cards, or one-off procurement requests that never generates a license record at all. Software Spend Detection exists to close exactly that gap.

What is Software Spend Detection?

Software Spend Detection is a capability within ServiceNow SAM Pro that takes your organization's financial transaction data — purchases recorded in accounts payable/procurement systems, or expenses submitted through expense reports and credit card feeds — and automatically identifies which of those transactions are software purchases, and for which publisher and product.

In newer releases, this is powered by ServiceNow Otto for Software Asset Management (SAM). When the Otto for SAM app is installed, two AI skills handle the work: a classification skill that reads the vendor name, description, and GL account to determine whether a transaction is software (and extracts the publisher/product if so), and a normalization skill that matches that extraction to existing records in your Software Asset Management Content Library. A scheduled job then labels every transaction with a State — New, Labeled, Partially labeled, Unlabeled, or Manually labeled — giving you a fully auditable trail of how each transaction was classified.

Key Insights

• Total Software Spend – Get a complete view of software spending from both Accounts Payable (AP) and employee expenses. This also helps identify software purchases that may not normally be visible to the IT team.
  Total Detected Spend = AP Spend + Expense Spend.
   
• Unmanaged Spend and Products/Publishers – Identify software that has been detected through spending data but does not yet have a Software Model in the system. Unmanaged spend is already part of the total software spend; it is not an additional spend.
   
• Overlapping Software – Find different software products that are being used for the same or similar purpose across different teams. This makes it easier to identify duplicate tools and areas where software can be consolidated.
   
• Spend Trends Over Time – View software spending month by month to identify increases, decreases, or unusual spending patterns.
   
• Spend by Publisher and Product – See how much is being spent on each publisher and software product. This information can help identify opportunities for software consolidation and vendor negotiations.
   
• Spend by Cost Center, Department, and Location – View software spending based on cost center, department, and location. These values are taken directly from the finance data, so they reflect the values used by the finance team. If needed, they can also be linked to records in the platform.

Why it matters

Together, these insights turn "we spend X on software" into something actionable: where to consolidate, where spend doesn't match policy, and where unmanaged software needs a formal entitlement before it becomes an audit or renewal surprise. If you have SAM Pro, Spend Detection is one of the fastest ways to show tangible ROI from that investment — and it's often sitting there unused.

Thanks,
Maniteja.