Overview of Booking Transactions

Booking transactions for subscriptions

When a subscription is created or amended, booking transactions are generated on the segment level if one of the following conditions is met:

• The new segment is a discount, and the new segment's quantity is not the same as the previous segment.
• The new segment is not a discount, and the new segment's Extended List Price (ELP) value is not the same as 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 Charge Contract Value (CCV) of the new segment is not the same as the previous segment.
• When a charge is created, a new segment is created and a booking transaction is generated for the new segment.
• When a charge is updated, a new segment is created and a booking transaction is generated for the segment.
• When an owner transfer occurs to a subscription and the subscription owner gets changed, all the segments that belong to the new version subscription generate booking transactions.
• If the current segment is a discount charge and the applied to charge segment is changed, a booking transaction is generated for the discount line.

There are more than 50 fields in the Booking Transaction object. For more information, see Booking Transaction object fields and Data Query.

Booking transactions for order line items

When an order line item is created or updated, booking transactions are generated if one of the following conditions is met:

• An order line item has the TriggerAsFulfillmentOccurs billing rule:
  • Setting the itemState field to Completedirectly when creating the order line item
  • Or, transitioning the itemState field from Executing to Complete
  • Or, transitioning itemState field from Booked to Complete
• An order line item has the TriggerWithoutFulfillment billing rule:
  • Setting the itemState field to Booked, SentToBilling, or Complete when creating the order line item
  • Or, transitioning itemState field from Executing to Booked, SentToBilling, or Complete

Limitations

The booking transactions are not generated for the following conditions:

• Fixed-amount discount charges
• Draft subscriptions
• Deleting a subscription (including deleting an order or deleting an amendment). The deleting operations are not recommended. For more information, see Required configurations and best practices for using Order to Revenue.
• When the billing rule “Enable credit back for removing or canceling one time charges?” is set to No, a one-time charge segment is canceled or removed (which makes its start date = end date) after it has been billed.
• For any subscription that has an account-level discount charge, the subscription does not generate any booking transaction.