Transaction Manager: Transaction-level system fields

  • Release version: Zurich
  • Updated November 10, 2025
  • 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

    This document explains the transaction-level (header-level) system fields available in ServiceNow’s Transaction Manager, particularly for the Zurich release. These fields provide general information about transactions, such as quote numbers, opportunity details, and account information. They complement line-level fields that pertain to specific products within transaction lines.

    Show full answer Show less

    Transaction-level fields are critical for managing transaction metadata and support integration, tracking, and configuration of transactions within the platform.

    Key Features

    • Two Field Levels:
      • Transaction-Level Fields: General transaction information (header-level).
      • Transaction Line-Level Fields: Product-specific details (covered separately).
    • System-Provided Fields: Default header-level fields are predefined by the system with names prefixed by txn.. Custom fields by administrators use the prefix txn.custom.
    • Modifiability: Some fields are system-generated and cannot be edited by users or administrators, ensuring data integrity (e.g., transaction ID, creation timestamps). Others can be modified by authorized users or via determination rules (e.g., account ID, opportunity ID, external ID).

    Key Fields and Their Practical Use

    • txn.id: Unique transaction identifier, auto-generated by the system.
    • txn.account.id: Account ID linked to the transaction, user-set on creation.
    • txn.opportunity.id: Opportunity ID associated with the transaction, user-set on creation.
    • txn.pricebook.id: Pricebook entry for the transaction’s products; blank defaults to tenant’s default pricebook.
    • txn.pricing.currencyCode: Currency code for product pricing; blank defaults to tenant base currency.
    • txn.created, txn.createdBy: Timestamps and creator user info, system-generated for audit and tracking.
    • txn.modified, txn.modifiedBy: Last modification details, system-generated for change tracking.
    • txn.externalId: Used for external integrations to uniquely reference transactions; expected to be provided at creation.
    • txn.stage: Transaction status/stage, system-generated based on configuration.
    • txn.persona: User persona performing the request, system-generated based on configuration.

    Practical Implications for ServiceNow Customers

    Understanding and utilizing these transaction-level fields allows administrators and users to effectively manage transaction metadata, support integrations, and maintain accurate transaction records. The distinction between system-generated and user-modifiable fields helps ensure that critical transaction identifiers and audit information remain consistent, while allowing flexibility where necessary (e.g., linking accounts, opportunities, and external references).

    When configuring Transaction Manager, customers can rely on these fields for automation, reporting, and integration workflows, ensuring transactions are properly tracked and associated with relevant business entities.

    Learn about the Transaction Manager fields that provide general information about the 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: 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 Default value
    txn.id uuid or unique ID of the transaction System

    <Generated>

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

    <Empty>

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

    <Empty>

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

    <Empty>

    blank will be interpreted as the default pricebook
    txn.pricing.currencyCode The currency associated with the products chosen by user User

    <Empty>

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

    <Generated>

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

    <Generated>

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

    <Generated>

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

    <Generated>

    Auto-generated by System upon update of a transaction record.
    txn.externalId Unique identifier which is used to reference a transaction in external connections/integrations User

    <Empty>

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

    <Generated>

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

    <Generated>

    Auto generated by system; depends on configuration