--- sourceDocument: Australia Sales and Order Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management Release : - australia ft:locale : - de-DE ft:publication_title : - Australia Sales and Order Management ft:clusterId : - omgmt bundleId : - omgmt workflow : - Customer and Industry --- # Transaction Manager: Transaction-level system fields # Transaction Manager: Transaction-level system fields {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer Learn about the Transaction Manager fields that provide information about a transaction, such as the quote number and account information. The fields available in Transaction Manager are categorized into two levels in the user interface (UI): * Transaction-level fields: Also known as header-level fields, these fields provide general information about the transaction, such as the quote number, opportunity details, and account information. * Transaction line-level fields: Also referred to as line-level fields, these fields capture specific information about the products associated with the transaction lines, including price, product details, and order information. For more information about line-level fields, see [Transaction Manager: Line-level system fields](https://servicenow-prod.fluidtopics.net/lDAk96fd5WjSG4U0i3JmBg "Learn about the Transaction Manager fields that provide information about a product, including price, product details, and order information."). {#transaction-manager-transaction-header-level-system-fields__ul_v5v_qs4_ghc} ## System-provided fields in Transaction Manager {#transaction-manager-transaction-header-level-system-fields__System-Provided-Fields-in-Transaction-Manager} By default, Transaction Manager offers a set of system-provided fields that assist administrators in transaction processing. This article focuses on transaction-level (header-level) fields that are predefined by the system. * System-generated fields at the header level use the prefix "txn" followed by the actual field name. * Custom header-level fields created by administrators are prefixed with "txn.custom" followed by the desired field name. {#transaction-manager-transaction-header-level-system-fields__ul_mv1_4s4_ghc} ## List of system-provided header-level fields {#transaction-manager-transaction-header-level-system-fields__List-of-System-Provided-Header-Level-Fields} The following table outlines the system-provided fields at the transaction level. * Variable name: The system-defined name of the field as configured in the environment. * Description: A brief overview of the purpose and use case of the system field. * Modifiable by: Indicates who can edit the field configurations: * System: The values of system-modifiable fields can only be set by the application. End-users cannot edit these fields. Administrators cannot determine the values of these fields via rules. * User: Any authorized end user with the appropriate permissions can update the field value. Determination rule actions can also modify the field value. {#transaction-manager-transaction-header-level-system-fields__ul_yv1_4s4_ghc} * Default value: The initial value assigned to the system field, specifying what can be set as the default during configuration. {#transaction-manager-transaction-header-level-system-fields__ul_xv1_4s4_ghc} {#transaction-manager-transaction-header-level-system-fields__table_sv1_4s4_ghc__entry__4} | Variable name | Description | Modifiable by | Default value | |-|-|-|-| | txn.id | UUID or unique ID of the transaction | System | \ Auto-generated by the system upon creation | | txn.account.id | ID of the account which was used while creating a new transaction | User | \ Expected to be passed in on create | | txn.opportunity.id | ID of the opportunity through which the transaction is created | User | \ Expected to be passed in on create | | txn.pricebook.id | Pricebook entry associated with the products chosen by user | User | \ A blank value is interpreted as the default pricebook | | txn.pricing.currencyCode | Currency associated with the products chosen by the user | User | \ A blank value equals base currency for the tenant | | txn.created | Timestamp of when the transaction was created | System | \ Auto-generated by the system upon creation | | txn.createdBy | Name of the user who created the transaction | System | \ Auto-generated by the system upon creation | | txn.modified | Timestamp of the last modification on a transaction | System | \ Auto-generated by the system upon update | | txn.modifiedBy | Name of the user who performed the last modification on the transaction | System | \ Auto-generated by the system upon update | | txn.externalId | Unique identifier used to reference a transaction in external connections/integrations | User | \ Expected to be passed in on create | | txn.stage | Stage or status of a transaction | System | \ Auto-generated by the system; depends on configuration | | txn.persona | Persona of the user who performed the request | System | \ Auto-generated by the system; depends on configuration | [Tabelle : 1. System-provided header-level fields] {#transaction-manager-transaction-header-level-system-fields__table_sv1_4s4_ghc} **Zugehörige Konzepte** * [Transaction Manager: Fields](https://servicenow-prod.fluidtopics.net/jDHG6hVPWzx1DlUczF6qkA "Understand the five major field type options: text, number, Boolean, picklist, and date/time. Learn how to create new fields using the Admin UI.") * [Transaction Manager: Line-level system fields](https://servicenow-prod.fluidtopics.net/lDAk96fd5WjSG4U0i3JmBg "Learn about the Transaction Manager fields that provide information about a product, including price, product details, and order information.") * [Transaction Manager: Date and time fields](https://servicenow-prod.fluidtopics.net/_KajLqIVy_pbw~QKwX92GA "Learn about Transaction Manager fields for times and dates.")