Software spend transaction fields
Software spend transaction form fields and their descriptions.
Software spend transaction form
|
Field |
Description |
|---|---|
|
Overview section | |
|
Description |
Short description of the transaction. |
|
State |
Current state of the transaction. This field is defaulted to New. |
|
Vendor name |
Name of the vendor associated with the transaction. |
|
Is software |
Indicates that the transaction is a software purchase. |
|
Publisher |
Publisher of the software product associated with the transaction. |
|
Product |
Software product associated with the transaction. |
|
GL account |
General ledger account associated with the transaction. |
|
Amount |
Transaction amount and currency. |
|
Is managed |
Indicates whether a software model exists for the detected product. If no software model exists, the transaction is treated as unmanaged spend. |
|
Type |
Type of the transaction. The values include: - Expense
This field is automatically set to Expense. |
|
Transaction date |
Date of the transaction in YYYY-MM-DD format. |
|
Type detail |
Additional detail about the transaction type. |
|
Source |
System that the transaction data originated from. |
|
More details section | |
|
Imported cost center |
Cost center value as received from the source import file. |
|
Cost center |
Cost center associated with the transaction. |
|
Imported department |
Department value as received from the source import file. |
|
Department |
Department associated with the transaction. |
|
Imported location |
Location value as received from the source import file. |
|
Location |
Location associated with the transaction. |
|
Employee ID |
Identifier of the employee associated with the transaction. |
|
External ID |
Identifier of the transaction in the source system. |
|
Employee name |
Name of the employee associated with the transaction. |
|
Upload |
Transaction import that the software spend transaction is associated with. |
|
Employee email |
Email address of the employee associated with the transaction. |
|
Exclude from content service |
Option to exclude the transaction from being shared with the Software Asset Management Content Library team. |
|
Activity section | |
|
Work notes |
Notes about the transaction that are visible to all users within your organization. |
Related topics
--- title: Software spend transaction fields description: Software spend transaction form fields and their descriptions. locale: en-us canonical_url: https://www.servicenow.com/docs/r/australia/it-asset-management/software-asset-management/software-spend-transaction-fields.html release: australia product: Software Asset Management classification: software-asset-management topic_type: reference last_updated: "2026-09-17" reading_time_minutes: 1 keywords: [software spend detection, software asset management software spend detection, software spend transaction fields] breadcrumb: [Software Asset Management references, Software Asset Management, IT Asset Management, Asset Management] --- # Software spend transaction fields Software spend transaction form fields and their descriptions. ## Software spend transaction form <table><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td colspan="2"> Overview section </td></tr><tr><td> Description </td><td> Short description of the transaction. </td></tr><tr><td> State </td><td> Current state of the transaction. This field is defaulted to New. </td></tr><tr><td> Vendor name </td><td> Name of the vendor associated with the transaction. </td></tr><tr><td> Is software </td><td> Indicates that the transaction is a software purchase. </td></tr><tr><td> Publisher </td><td> Publisher of the software product associated with the transaction. </td></tr><tr><td> Product </td><td> Software product associated with the transaction. </td></tr><tr><td> GL account </td><td> General ledger account associated with the transaction. </td></tr><tr><td> Amount </td><td> Transaction amount and currency. </td></tr><tr><td> Is managed </td><td> Indicates whether a software model exists for the detected product. If no software model exists, the transaction is treated as unmanaged spend. </td></tr><tr><td> Type </td><td> Type of the transaction. The values include: - Expense - Accounts payable This field is automatically set to Expense. </td></tr><tr><td> Transaction date </td><td> Date of the transaction in YYYY-MM-DD format. </td></tr><tr><td> Type detail </td><td> Additional detail about the transaction type. </td></tr><tr><td> Source </td><td> System that the transaction data originated from. </td></tr><tr><td colspan="2"> More details section </td></tr><tr><td> Imported cost center </td><td> Cost center value as received from the source import file. </td></tr><tr><td> Cost center </td><td> Cost center associated with the transaction. </td></tr><tr><td> Imported department </td><td> Department value as received from the source import file. </td></tr><tr><td> Department </td><td> Department associated with the transaction. </td></tr><tr><td> Imported location </td><td> Location value as received from the source import file. </td></tr><tr><td> Location </td><td> Location associated with the transaction. </td></tr><tr><td> Employee ID </td><td> Identifier of the employee associated with the transaction. </td></tr><tr><td> External ID </td><td> Identifier of the transaction in the source system. </td></tr><tr><td> Employee name </td><td> Name of the employee associated with the transaction. </td></tr><tr><td> Upload </td><td> Transaction import that the software spend transaction is associated with. </td></tr><tr><td> Employee email </td><td> Email address of the employee associated with the transaction. </td></tr><tr><td> Exclude from content service </td><td> Option to exclude the transaction from being shared with the Software Asset Management Content Library team. </td></tr><tr><td colspan="2"> Activity section </td></tr><tr><td> Work notes </td><td> Notes about the transaction that are visible to all users within your organization. </td></tr></tbody> </table>**Parent Topic:**[Software Asset Management references](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/references.md) **Related topics** [Create a spend transaction manually](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/manually-update-transactions.md)
| title | Software spend transaction fields |
| description | Software spend transaction form fields and their descriptions. |
| locale | en-us |
| canonical_url | https://www.servicenow.com/docs/r/australia/it-asset-management/software-asset-management/software-spend-transaction-fields.html |
| release | australia |
| product | Software Asset Management |
| classification | software-asset-management |
| topic_type | reference |
| last_updated | 2026-09-17 |
| reading_time_minutes | 1 |
| keywords | software spend detectionsoftware asset management software spend detectionsoftware spend transaction fields |
| breadcrumb | Software Asset Management referencesSoftware Asset ManagementIT Asset ManagementAsset Management |