Skip to main content

Overview of Booking Transactions

Zuora

Overview of Booking Transactions

The booking transaction object is available in the data source and data query. This object stores data and data changes in the Zuora Billing. It provides the systems downstream of Zuora Billing with consistent and traceable data for order or bookings data.

Booking transaction captures important changes and the delta values on Rate Plan Charge, Order Line Items, and similar objects when a subscription is created or modified.

When a new subscription is created, Booking Transaction record(s) is generated on the segment level if one of the following conditions is met:

  • The value of the new segment is not a Discount, and the new segment's quantity is not the same as that of the previous segment.
  • The value of the new segment is a Discount, and the new segment's ELP is not the same as that of the previous segment.
  • The new segment's effective start date is not the same as the previous segment.
  • The new segment's effective end date value is not the same as the previous segment.
  • The CCV value of the new segment is not the same as that of the previous segment.
  • Previous segment is a segment in the previous version subscription, and has the same chargeNumber and segmentNumber.
  • If a segment does not have a previous segment, it will generate a Booking Transaction.
  • The subscription owner of the new subscription is not the same as that of the previous subscription, all the segments belong to this new subscription.

There are more than 50 fields in the Booking Transaction object, including Subscription information (ID, Name, and so on), Product, Charge, Amendment Types, Accounting Codes, Currency, CCV-related stats, and so on. See Booking Transaction object fields and Data Query, for more information.

Limitations:

The Booking Transaction will not be generated for the following conditions:

  • Fixed-amount discount charge
  • Draft/pending subscriptions
  • Deleting a subscription (including deleting order/amendment)
  • For a one-time charge segment, If the Billing Rules “Enable credit back for removing or canceling one time charges?” is set to“No”, canceled or removed (which makes its startDate = endDate) after it has been billed or posted.
  • For Evergreen Subscription, If tenant Property “ENABLE_EVERGREEN_SUBSCRIPTION_CONTRACTUAL_VALUE” is false, the percentage discount charges is not eligible to be recorded as booking transaction.
  • Any subscription that has account-level discount charge, the subscription will not generate any record as Booking Transaction.

When an order line item is created or updated, Booking Transaction is generated if one of the following conditions is met:

  1. The orderLineItem has the rule of “TriggerAsFulfillmentOccurs”:
    • Setting the state to “Complete” directly when creating (or) transitioning from “Executing” to “Complete” (or) transitioning it from “Booked” to “Complete.”
  2. The orderLineItem has the rule of “TriggerWithoutFulfillment”:
    • Setting the state to “Booked,” “SentToBilling,” or “Complete” when creating (or) transitioning it from “Executing” to “Booked,” “SentToBilling,” or “Complete.”

Account level discount is not supported. In addition, fixed amount discounts will not be supported as part of the discount allocation.