ServiceNow Software Asset Management Professional for Insurance
SAM Professional is the ServiceNow software asset management application that tracks which software is in use, how many licences have been bought and whether usage stays within the licence terms. For an insurer it is the tool that keeps a mixed estate of legacy, cloud and finance software reconciled before a vendor audit begins.
How Insurance Organisations Use SAM Professional
Licence reconciliation in an insurer has to cover a mixed estate: legacy mainframe systems running the core book, cloud applications for claims and customer service, analytics tools and the enterprise finance suite, each counted on a different licence basis. The sections below cover compliance and audit readiness, policyholder data protection, cost optimisation and negotiation, then the routine: matching entitlements to what is installed before an audit starts, deciding what to track at product level, a reconciliation procedure an auditor can follow, building the evidence pack before a renewal, and when a managed reconciliation returns less than it costs.
Insurance systems store confidential customer data and proprietary pricing and underwriting information. Software licensing and usage must be controlled to meet data protection requirements and ensure only authorised systems access sensitive data.
Licensing Compliance for Insurance Systems
Insurance organisations operate diverse software portfolios: legacy mainframe systems running core insurance business, modern cloud applications for customer service and claims, business intelligence tools for analytics, and enterprise applications for finance and operations. Each category of software has different licensing models and compliance requirements.
SAM Professional tracks which software is in use, how many licenses have been purchased, and whether usage is within license limits. Compliance teams use this data to confirm license compliance during audits.
Audit Readiness and Evidence Collection
Insurance regulators require evidence of software licensing compliance and approval processes for technology changes. SAM Professional maintains audit trails showing what software is in use, who approved its use, and what compliance controls are in place. When auditors request evidence, the system can quickly generate reports showing compliance status.
Software inventory reports grouped by business function (underwriting, claims, customer service) help auditors understand what technology supports each business process.
Policyholder Data Protection and Access Control
Software that accesses policyholder data must be configured with appropriate access controls and usage policies. SAM Professional can be integrated with security tools to ensure only approved software can access sensitive data systems. Software inventory linked to data classifications helps identify which systems handle which sensitivity levels of data.
Cost Optimisation and License Negotiation
SAM Professional identifies underutilised software that could be decommissioned or renegotiated. Insurance organisations often negotiate volume licenses or subscription terms; SAM data showing actual usage supports negotiations with vendors.
License renewal decisions can be informed by usage data. Software with low usage across the organisation can be targeted for renewal discussion or replacement with lower-cost alternatives.
Technical Aspects Specific to Insurance
Insurance organisations may need specialized integration with underwriting systems that have unique licensing terms, claims systems with high-volume transaction licenses, and data warehouse systems with complex user-based or consumption-based licensing. SAM Professional configuration should reflect these specialized licensing models.
Regulatory Compliance Specifics
Depending on the jurisdiction, insurance regulators require software to meet specific security and audit standards. Compliance teams must confirm that software meets regulatory requirements. Compliance teams should verify specific regulatory requirements for the organisation’s geographic and product scope.
Oblytech’s SAM Professional for Insurance Services
We help insurance organisations design SAM programs that address regulatory compliance and audit readiness. Implementation includes software inventory tailored to insurance business functions, licensing model configuration for insurance-specific applications, and integration with compliance and audit workflows. Consulting addresses how to maintain compliance as the technology portfolio evolves.
Technology Cost Optimisation
SAM data enables cost optimisation by identifying underutilised licenses, opportunities to consolidate vendors, or negotiate volume agreements. Cost savings can be reinvested in strategic technology initiatives.
Compliance Evidence and Audit Trails
Insurance regulators require evidence of software licensing compliance. SAM Professional provides audit trails showing when licenses were purchased, when software was deployed, and what compliance checks were performed. This documentation becomes evidence during regulatory reviews and helps the organisation demonstrate responsible licensing practices.
Integration With Risk and Compliance Modules
SAM Professional integrates with Risk Management and Compliance Management modules. Licensing violations are documented as compliance findings. Risk assessments can consider software licensing risks: unlicensed software creates legal and financial risk that should be managed.
Vendor License Negotiations
Insurance organisations often negotiate volume licenses with software vendors based on usage data. SAM Professional provides accurate usage data supporting negotiations. Data showing actual usage patterns helps secure better licensing terms and pricing when renewing contracts with vendors.
Matching entitlements to what is installed before an audit starts
A license audit is a reconciliation. The publisher compares what the organization bought, in the form the contract recorded it, with what is running, and the gap becomes the finding. The reconciliation is often easier when entitlements are held as structured records rather than as attached documents. Before anything else, agree which entitlement records are the source of truth, which purchases feed them and who signs off a change. An entitlement recorded late on a Friday by someone who was not in the procurement meeting is a common source of false gaps.
| License metric | What the evidence must show | Common trap |
|---|
| Per named user | Each assigned user and the date of assignment | Shared accounts that look like many users |
|---|
| Per device or per processor core | The device list and core count at the relevant date | Virtual machines moved between hosts without records |
|---|
| Per instance or environment | Which environments are production and which are non-production | Non-production copies counted as production |
|---|
| Consumption or usage based | Usage logs and the contractual definition of the unit | Usage data with no matching unit definition |
|---|
| Bundled subscription | Which bundle covers which product | A product sold inside a bundle counted as a separate purchase |
|---|
Deciding what to track at product level
Tracking every installed file can produce noise. Track the products whose license terms the contract actually cares about, and group the rest under broad categories. A practical test is whether the product’s installation or use can create a payable obligation. If it can, it belongs in the reconciliation. If it cannot, it belongs in the general inventory. The SAM Professional module supports both views, so the choice is about where the reconciliation effort goes rather than about what the tool can record.
A reconciliation procedure an auditor can follow
- Freeze the entitlement set for the period and record the date it was frozen.
- Export the installed inventory for the same date from the discovery source.
- Normalize publisher and product names, so that one product does not appear under three spellings.
- Match each installation to an entitlement, using the metric the contract specifies.
- List unmatched installations and unused entitlements separately.
- Record a disposition for each gap, whether remove, purchase or contest, with its owner and the evidence used.
- Keep the workpapers with the reconciliation date, so they can be produced without rebuilding them under pressure.
Where the reconciliation tends to break down
A common failure is a mismatch in names and editions, which creates many small gaps that are not real. The second is discovery coverage: a server the discovery tool cannot reach will not appear, and the absence looks like compliance. The third is treating a purchase as an entitlement before the contract is signed. Each of these makes the number look better or worse than the truth, and an auditor will test all three. The software license optimization guidance covers the usage side of the same problem.
Building the evidence pack before a renewal
A renewal is often the cheapest moment to correct the records, because the vendor and the insurer are already negotiating. Before the meeting, assemble a short pack: the entitlement list with its source documents, the reconciliation result with the date it was taken, the list of unused entitlements with the owner’s view on each, and the usage figures for the metric the contract uses. Keep the pack to what the negotiator needs. A pack that runs to many pages is often unread, and the one page the negotiator needed may be buried in it.
When a managed reconciliation returns less than it costs
A limited portfolio with a few contracts, all tracked in a register the finance team reviews, may not justify a managed reconciliation. If the organization has no reliable entitlement records and no one who owns them, fix the records first. Automating a reconciliation over unreliable inputs can produce an authoritative-looking report that is wrong, and a wrong report can carry more risk than no report.
Questions the license and finance teams ask
How often should the reconciliation run?
Often enough that a gap is found while the contract is still open for negotiation. Many teams run a full reconciliation before each renewal and a lighter check each quarter, with the cadence agreed by the contract owner.
Does a usage report count as evidence on its own?
It is evidence of usage, not of entitlement. Keep the usage report beside the contract clause that defines the unit of measure, or the report answers a question that nobody asked.
Who should own the entitlement records?
The contract owner, not the person who installs the software. Separating those roles keeps the records honest, because the installer has an interest in the environment looking tidy.
What happens to software bought on a business unit’s own card?
It has to enter the entitlement records like any other purchase.
Review roles are set out in the governance model for SAM Professional.
Frequently asked questions
How should SAM Professional handle software with unique licensing models?
Create custom license type records in SAM for each unique licensing model. Assign rules to track usage against license terms. Validate compliance for each license type separately.
Should Insurance SAM Professional track software used by customers?
Only if the insurance organisation provides software to customers as part of their service. Customer-used software is managed separately from company-operated software.
How often should Insurance SAM Professional be audited?
Audit before regulatory compliance reviews. Audit before major changes to the software portfolio. Many organisations audit quarterly to ensure ongoing compliance.
Related guides
Planning, running or fixing a ServiceNow programme? Tell us where you are and we will suggest a sensible next step.
Contact us