Welcome to Zuora Product Documentation

Explore our rich library of product information

Credit memo reversal in Billing - Revenue integration

This document explains the process and limitations of credit memo reversal in Zuora Billing and its integration with Zuora Revenue, including the generation of debit memo transactions and their impact on revenue recognition.

If you have the Reverse Credit Memo user permission in Zuora Billing, you can reverse posted credit memos. When credit memo reversal happens in Zuora Billing, a debit memo transaction is generated by Zuora Billing. After this debit memo transaction is synced to Zuora Revenue, it will be treated as a new type of debit memo source called AdhocFromCreditMemo.

Limitations

Zuora Revenue currently supports the common use cases of credit memo reversal in Zuora Billing with the following limitations:

  • After the debit memo is generated for credit memo reversal, any deletion, unposting, or cancellation of the debit memo cannot be consumed in Zuora Revenue. It means the reversal entry will not be created in Zuora Revenue.

  • The debit memo transaction does not have any reference back to the reversed credit memo. Instead, it references back to the original sales order (SO) line for the charge. The SO reference for both regular and discount charges consists of the original ID of the rate plan charge (RatePlanCharge.OriginalId) followed by the rate plan charge segment (RatePlanCharge.segment).

  • The new Zuora Billing standard field CreditMemo.Reversed cannot be consumed in Zuora Revenue.

Use cases

Case 1

In this use case, the following actions occur in sequence in Zuora Billing.

  1. On the first day, a termed subscription is created with a recurring charge (C-00196777) of $100 from 09/01/2021 till 09/31/2021. A sales order (SO) transaction will be consumed in Zuora Revenue.
  2. On the same day, a bill run is created as of 10/01/2021. This will get an invoice transaction being consumed in Zuora Revenue.
  3. On the second day, the subscription is canceled with the effective date of 09/16/2021. The original SO line is updated with the new term.
  4. On the same day, a bill run is created to auto-generate a credit memo for the duration from 09/16/2021 till 09/30/2021. A CM-C transaction will be consumed in Zuora Revenue.
  5. On the third day, a credit memo reversal occurs to the generated credit memo. The system auto-generates a debit memo for the duration from 09/16/2021 till 09/30/2021. The debit memo transaction will be consumed as an invoice line in Zuora Revenue with reference to the rate plan charge ID and rate plan charge segment of the original SO line.

After billing data is synced, these actions will get the following transaction lines being consumed in Zuora Revenue.

ActionSubscription #Subscription VersionCharge #Charge Original IdCharge SegmentTransaction TypeSO Line IdStart DateEnd DateSO AmountInvoice #INV Line IdInvoice Amount
Create subscriptionA-S000997561C-00196777abc1231SOabc123.19/1/219/30/21100
Bill runA-S000997561C-00196777abc1231INVabc123.19/1/219/30/21INV00016050112233100
Cancel subscriptionA-S000997562C-00196777abc1231SOabc123.19/1/219/15/2150
Bill runA-S000997562C-00196777abc1231CM-Cabc123.19/16/219/30/21CM00000602223123-50
Credit memo reversalA-S000997562C-00196777abc1231INVabc123.19/16/219/30/21DM0000001934534550

Case 2

In this use case, the following actions occur in sequence in Zuora Billing. Different from the first use case, a discount charge is created together with the regular charge. This results in two SO lines being consumed in Zuora Revenue. The subsequent bill runs, subscription cancelation, and credit memo reversal will have an impact on both SO lines.

  1. On the first day, a termed subscription is created with a recurring charge (C-00196780) of $100 and a discount percentage charge (C-00196781) of 10% from 09/01/2021 till 09/31/2021. These two charges will be consumed as two SO lines in Zuora Revenue.
  2. On the same day, a bill run is created as of 10/01/2021. Two invoice lines are consumed in Zuora Revenue for the original two SO lines.
  3. On the second day, the subscription is canceled with the effective date of 09/16/2021. The original two SO lines are updated for the new term in Zuora Revenue.
  4. On the same day, a bill run is created to auto-generate a credit memo for the duration from 09/16/2021 till 09/30/2021. Two CM-C lines are consumed in Zuora Revenue with reference to the original SO lines.
  5. On the third day, a credit memo reversal occurs to the generated credit memo. The system auto-generates a debit memo for the duration from 09/16/2021 till 09/30/2021. Two debit memo lines are consumed in Zuora Revenue with reference to the rate plan charge ID and rate plan charge segment of the original SO line.

After billing data is synced, these actions will get the following transaction lines being consumed in Zuora Revenue.

ActionSubscription #Subscription VersionCharge #Charge Original IdCharge SegmentTransaction TypeSO Line IdStart DateEnd DateSO AmountInvoice #INV Line IdInvoice Amount
Create subscriptionA-S000997581C-00196780abc12341SOabc1234.19/1/219/30/21100
Create subscriptionA-S000997581C-00196781abc12351SOabc1234.1.abc1235.19/1/219/30/21-10
Bill runA-S000997581C-00196780abc12341INVabc1234.19/1/219/30/21INV000160513213100
Bill runA-S000997581C-00196781abc12351INVabc1234.1.abc1235.19/1/219/30/21INV000160513214-10
Cancel subscriptionA-S000997582C-00196780abc12341SOabc1234.19/1/219/15/2150
Cancel subscriptionA-S000997582C-00196781abc12351SOabc1234.1.abc1235.19/1/219/15/21-5
Bill runA-S000997582C-00196780abc12341CM-Cabc1234.19/16/219/30/21CM00000603223124-50
Bill runA-S000997582C-00196781abc12351CM-Cabc1234.1.abc1235.19/16/219/30/21CM000006032231255
Credit memo reversalA-S000997582C-00196780abc12341INVabc1234.19/16/219/30/21DM000000203234150
Credit memo reversalA-S000997582C-00196781abc12351INVabc1235.19/16/219/30/21DM0000002032342-5