--- sourceDocument: Australia Asset Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-asset-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Asset Management ft:clusterId : - itam bundleId : - itam workflow : - Technology --- # Managing software spend in the Software Asset Workspace # Managing software spend in the Software Asset Workspace {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Managing software spend in the Software Asset Workspace The Software Spend Detection feature, accessible in the Software Asset Workspace under License operations, enables ServiceNow customers to import financial transactions, review labeled transactions, and monitor software spending across their organization. This feature was moved from the Core UI starting with the Brazil release, consolidating spend detection activities into a unified workspace. The previous Software Spend Detection Overview dashboard has been deprecated, and all existing imports and spend transactions remain available within the Software Asset Workspace. Show full answer Show less ## Key Features * **Transaction imports:** This submodule provides a detailed record of every import job, including status, results, and error tracking. Customers can monitor each import's outcome, identify errors, and review transactions created by specific imports. Import details include uploaded files and transaction lists, with an Errors tab showing issues for failed rows. * **All transactions:** This consolidated list displays every spend transaction imported or manually created, showing source data alongside AI or user-assigned labeling such as publisher, product, and software indicators. Visual distinctions highlight the origin of labeling to facilitate transaction review and correction. * **Transaction labeling states:** Transactions progress through defined states---New, Labeled, Partially labeled, Manually labeled, and Unlabeled---indicating their classification and matching status. This helps users understand the transaction lifecycle and identify unmanaged software spend where purchases are not yet tracked in the Software Asset Management Content Library. ## Practical Application ServiceNow customers can use the Software Asset Workspace to effectively manage software spend by importing financial data, validating and correcting labeled transactions, and tracking software purchases that may require attention. The ability to distinguish managed versus unmanaged software spend enables better compliance and cost control. To initiate spend tracking, customers can import transactions or manually create spend transactions as needed, utilizing AI-powered classification to streamline the process. The Software Spend Detection feature is available in the Software Asset Workspace under License operations. Use Software Spend Detection in the Software Asset Workspace to import financial transactions, review labeled transactions, and track software spending across your organization. Important: Starting with the Brazil release, the Software Spend Detection feature is no longer available in the Core UI. Existing imports and spend transactions that were created using the Core UI are preserved and available in the Software Asset Workspace. The Software Spend Detection Overview dashboard is also deprecated. The Software Asset Workspace provides a unified experience for managing your software spend detection activities. Under License operations, the Software spend detection section contains two submodules that support the end-to-end spend detection workflow.{#spend-detection-sam-workspace__spend-detection-sam-workspace-para-1} Transaction imports : Record of every import job with its status and results. All transactions : Consolidated list of every spend transaction in the system, regardless of import source or state. ## Transaction imports {#spend-detection-sam-workspace__transaction-imports} The Transaction imports list shows every import record created in Software Spend Detection. Each row shows the import name, its status, and the row counts for inserts, errors, updates, skipped rows, and ignored rows.{#spend-detection-sam-workspace__spend-detection-sam-workspace-para-6} Use this list to monitor the outcome of an import, identify imports that completed with errors, and locate the transactions created by a specific import. Select any record to open the import and review its details, including the file that was uploaded and the transactions the import created.{#spend-detection-sam-workspace__spend-detection-sam-workspace-para-7} Selecting an import from the list opens its record with a Transactions tab showing every transaction created by that import. If an import contains rows that failed to process, an Errors tab also appears with the source row number, error message, and the original values from the file. To start a spend transaction import, see [Import financial transactions](https://www.servicenow.com/docs/2vtR3dCqoYhbrJifo3HT5g "Import a Microsoft Excel spreadsheet of financial transaction data in the Software Asset Workspace to start managing software spending.").{#spend-detection-sam-workspace__spend-detection-sam-workspace-para-8} Figure 1. Transaction imports list ## All transactions {#spend-detection-sam-workspace__all-transactions} The All transactions list shows every spend transaction that has been imported or manually created in the Software Asset Workspace. Use this list to review the state of each transaction, verify how it was labeled, and identify transactions that require correction.{#spend-detection-sam-workspace__spend-detection-sam-workspace-para-3} Each row shows the transaction details from your source data along with the values assigned during labeling, such as the publisher, product, software indicator, and labeling method. Values assigned by AI, machine learning, or a user are visually distinct, so you can quickly identify which transactions need review.{#spend-detection-sam-workspace__spend-detection-sam-workspace-para-4} The following two fields on the transaction record help you identify software purchases that aren't yet tracked in your Software Asset Management Content Library: * Is software: Indicates whether the transaction represents a software purchase. * Is managed: Indicates whether the software is already tracked in your Software Asset Management Content Library with an active software model. {#spend-detection-sam-workspace__ul_szf_tpl_pkc} Transactions where Is software is true and Is managed is false represent unmanaged software spend. The State field indicates where each transaction is in the labeling process. {#spend-detection-sam-workspace__table_tzf_tpl_pkc__entry__2} | Value | Description | |-|-| | New | Default state assigned when a transaction is imported or manually created. | | Labeled | The transaction is classified as a software purchase, and both the publisher and product are matched to existing records. | | Partially labeled | The transaction is classified as a software purchase, and the publisher is matched, but the product isn't. | | Manually labeled | A user manually set or updated the Is software, Publisher, or Product fields on the transaction. | | Unlabeled | The labeling process couldn't classify or normalize the transaction after the maximum retry attempts. | [Table 1. State field values] {#spend-detection-sam-workspace__table_tzf_tpl_pkc} For details on how each state is assigned, see [AI-powered software spend detection](https://www.servicenow.com/docs/3GNIOacBdNWzckiHediN6g "AI-powered spend detection identifies software purchases in imported spend transactions and normalizes the derived raw publisher and raw product to existing publisher and product records in Software Asset Management Content Library. This automation improves spend reporting accuracy and reduces manual classification effort."). To manually create a spend transaction, see [Create a spend transaction manually](https://www.servicenow.com/docs/9YzCvYSUYwex8KlqlCpf6Q "Create spend transactions for one-off software purchases or spend records that are not captured in your accounts payable import file. This allows you to track all software spending in one location.").{#spend-detection-sam-workspace__spend-detection-sam-workspace-para-5} Figure 2. All transactions list **Related concepts** * [AI-powered software spend detection](https://www.servicenow.com/docs/3GNIOacBdNWzckiHediN6g "AI-powered spend detection identifies software purchases in imported spend transactions and normalizes the derived raw publisher and raw product to existing publisher and product records in Software Asset Management Content Library. This automation improves spend reporting accuracy and reduces manual classification effort.") **Related tasks** * [Import financial transactions](https://www.servicenow.com/docs/2vtR3dCqoYhbrJifo3HT5g "Import a Microsoft Excel spreadsheet of financial transaction data in the Software Asset Workspace to start managing software spending.") * [Create a spend transaction manually](https://www.servicenow.com/docs/9YzCvYSUYwex8KlqlCpf6Q "Create spend transactions for one-off software purchases or spend records that are not captured in your accounts payable import file. This allows you to track all software spending in one location.")