Stand-alone Transactions in SaaS Metric Reporting

The Stand-alone Transaction use case tracks the impact of isolated transactions on your SaaS metrics, including new sales, upsells, downsells, churn, and renewals. A stand-alone transaction is defined by unique start and end dates on the transaction header and does not maintain revision history.

Source Records

Stand-alone transactions can originate from:

  • Sales Orders

  • Invoices

  • Cash Sales

Impact Categories and Subcategories

Impact Category

Impact Subcategory

Situation/Trigger

Notes

New

New Contract

New transaction/item

Upsell

Price Increase

Increase in amount (not quantity) on renewal transaction

Upsell

Quantity Increase

Increase in quantity on renewal or coterminous transaction

Upsell

Quantity Increase

Simultaneous price and quantity increase on renewal transaction

Upsell

Add-on

New line item added on renewal transaction or different coterminous sales order with same customer, different item

Downsell

Quantity Decrease

Partial quantity removed by Return Authorization, Credit Memo, or Cash Refund

Downsell

Quantity Decrease

Decrease in quantity on renewal transaction

Downsell

Price Decrease

Decrease in amount (not quantity) on renewal transaction

Downsell

Item Removal

Item removal on renewal transaction

Updates churn event on original analytical impact

Downsell

Item Removal

Full line removed by Return Authorization, Credit Memo, or Cash Refund

Churn

Contract Churn

No renewal transaction

No Impact

Renewal

Analytical impact linked to renewal transaction’s analytical impact

N/A

N/A

Increase or decrease to original line’s quantity/amount (no revision history on stand-alone transactions)

Updates monthly impact amount without generating upsell/downsells on standalone transactions

Related Topics

General Notices