Transaction Manager: Transaction-level system fields

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    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 Transaction Manager: Transaction-level system fields

    The Transaction Manager provides essential fields that give insights into transactions, including quote numbers and associated account information. These fields are divided into two categories: transaction-level (header-level) fields and transaction line-level fields.

    Show full answer Show less

    Key Features

    Transaction-level fields offer general transaction details, while line-level fields focus on specific product information. Key system-provided header-level fields include:

    • txn.id: Unique ID of the transaction (auto-generated).
    • txn.account.id: ID of the account for the transaction (user-modifiable).
    • txn.opportunity.id: ID of the opportunity associated with the transaction (user-modifiable).
    • txn.pricebook.id: Pricebook entry for selected products (user-modifiable).
    • txn.pricing.currencyCode: Currency of the chosen products (user-modifiable).
    • txn.created: Timestamp of transaction creation (auto-generated).
    • txn.modified: Timestamp of the last modification (auto-generated).
    • txn.externalId: Unique identifier for external references (user-modifiable).
    • txn.stage: Current status of the transaction (auto-generated).
    • txn.persona: User persona of the requester (auto-generated).

    Key Outcomes

    By utilizing these transaction-level fields, ServiceNow customers can efficiently manage transaction information, ensuring that all essential details are captured and accessible for processing and reporting. This structure enhances data management and supports better decision-making within the organization.

    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.

    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.

    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.
    • Default value: The initial value assigned to the system field, specifying what can be set as the default during configuration.
    Table 1. System-provided header-level fields
    Variable name Description Modifiable by Default value
    txn.id UUID or unique ID of the transaction System

    <Generated>

    Auto-generated by the system upon creation
    txn.account.id ID of the account which was used while creating a new transaction User

    <Empty>

    Expected to be passed in on create
    txn.opportunity.id ID of the opportunity through which the transaction is created User

    <Empty>

    Expected to be passed in on create
    txn.pricebook.id Pricebook entry associated with the products chosen by user User

    <Empty>

    A blank value is interpreted as the default pricebook
    txn.pricing.currencyCode Currency associated with the products chosen by the user User

    <Empty>

    A blank value equals base currency for the tenant
    txn.created Timestamp of when the transaction was created System

    <Generated>

    Auto-generated by the system upon creation
    txn.createdBy Name of the user who created the transaction System

    <Generated>

    Auto-generated by the system upon creation
    txn.modified Timestamp of the last modification on a transaction System

    <Generated>

    Auto-generated by the system upon update
    txn.modifiedBy Name of the user who performed the last modification on the transaction System

    <Generated>

    Auto-generated by the system upon update
    txn.externalId Unique identifier used to reference a transaction in external connections/integrations User

    <Empty>

    Expected to be passed in on create
    txn.stage Stage or status of a transaction System

    <Generated>

    Auto-generated by the system; depends on configuration
    txn.persona Persona of the user who performed the request System

    <Generated>

    Auto-generated by the system; depends on configuration