Revenue recognition transaction overrides Beta

Learn how to make manual corrections to your revenue recognition reports.

It’s possible for the information on a transaction to become inaccurate for revenue recognition purposes. This can happen for a number of reasons, such as human error or evolving terms of a sale. The transaction override feature allows you to make corrections, regardless of when the transaction was created.

Creating a transaction override

The transaction overrides section can be found at the bottom of the revenue recognition page.

Add transaction override modal

1 Enter ID of the transaction model to override

To get started, enter the id of the transaction to override. Overrides are supported on the following transaction models:

Transaction model Restrictions
Invoices Invoices that contain any of the following cannot be overridden:
  • Proration line item
  • Metered billing line item
  • Charges Charges that are associated with an invoice cannot be overridden. Instead, override the invoice itself.

    The id of a transaction can be found in the Dashboard or using the API. If the transaction occurred in a previous month, it can also be found in the following report downloads when formatted by invoice:

    • Invoice Statement
    • Debits and credits
    • Corrections

    2 Choose the override type

    The following override types are supported:

    Override Type Description
    Recognition period start and end dates The start date and end dates correspond to when the service was started and stopped. The revenue of this transaction will be recognized within this period. Start and end dates can have the same value, in which case revenue is recognized all at once. Read more about how transaction overrides work below.
    Transaction exclusion Excluding a transaction will remove all records of it from revenue recognition. This is only supported on invoices that are either voided or manually marked as paid, and have no applied customer balance.

    How transaction overrides work

    Transaction overrides can be created for transactions that occurred in past accounting periods and in the current accounting period. If the transaction occurred in a past accounting period, corrections are implemented prospectively at the end of the current accounting period. You can view these corrections in the current period’s reports after the period has closed.

    If the overridden transaction occurred in the current accounting period, the transaction is not reflected as a correction in the current period. Instead, it’s recognized using the new attributes from the override.

    Creating a transaction override does not alter the attributes of the transaction model being overridden.

    Changes to a transaction override can be made by deleting the override and creating a new one. Similar to creating an override, deleting an override that already impacted a past accounting period will be reflected prospectively beginning with the current period’s reports; whereas deleting an override created in the current accounting period will result in no changes to the reports.

    Was this page helpful?
    Questions? Contact us.
    Developer tutorials on YouTube.