home

Billing for Salesforce

Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)Conga CopilotCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release
Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)Conga CopilotCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Contents

Show Page Sections

Billing for Salesforce

Amendment of Legacy Assets

Amending the Recurring Legacy Assets

The recurring legacy assets can be amended by using the "Change" on the CPQ Cart or explicitly calling the API to perform an amendment on the legacy asset.

Prerequisites

  • The object and fields required to support legacy billing for legacy asset line items are configured. For more information, see Understanding Billing Schedules and Use Case 3.
  • The following minimum criteria are met:
    • The Is Legacy for Billing checkbox is set to True.
    • The Price Type is not Usages.
    • The Billing Frequency is not One Time.
  • The Original Start Date, Start Date, End Date, First Billing Date, Remaining Billable Amount, TCV, Selling Term, and CPQ Pricing fields (Base Unit Price and Net Price) are captured accurately on the asset line record.

Key points to consider

  • The Change:Quantity and Change:Configuration functionalities are not supported for the amendment of recurring legacy assets. If you attempt to perform any of these functions, they tend to cancel the ongoing amendment process and create a new asset line item. This new asset line item is not treated as a legacy asset by the system and hence it goes out of the scope of this functionality.
  • You must populate the "First Billing Date" on the asset line record. Once populated, you should not change this date manually or through database updates for subsequent operations, else it’ll have serious data corruption and will impact the billing data integrity.
    • If the populated date for the change is equal to the "Start Date", or "First Billing Date", then no change is allowed on the CPQ cart.
    • If the populated date for the change is on or after the “First Billing Date”, then the change operation can be performed on the asset line.

  • The asset line item is billed in a recurring fashion in the legacy system.

    This implies that the asset has been billed consistently in the legacy period where the remaining billable amount is in accordance with the formula:

    remaining billable amount= (net unit price * quantity * billing term).

To amend recurring legacy products

Follow the following steps to amend a recurring legacy product:

  1. Bill a recurring legacy asset. For more information, see Recurring Billing for Legacy Assets.
  2. Navigate to the Installed Products page and click Change on the CPQ Cart or explicitly call the API to perform an amendment on the legacy asset.
    Warning: The Change:Quantity and Change:Configuration functionalities are not supported for the amendment of recurring legacy assets. If you attempt to perform any of these functions, they tend to cancel the ongoing amendment process and create a new asset line item. This new asset line item is not treated as a legacy asset by the system and hence it goes out of the scope of this functionality.

    At the time of initiating billing for the “Change” scenario, Conga Billing verifies if the populated date for the change is on or after the “First Billing Date” and if the validation is passed:

    • Conga Billing processes the request. It supersedes the previous billing schedules and creates new schedules in their place with an amount equivalent to the delta/refund. Otherwise, it throws an error on the Order page.
    • For all the invoiced billing schedules, it updates the Remaining Billable Amount on the asset line item.
      Warning:

      CPQ doesn’t stop you from amending an asset if the Change Start Date is in between the current “Start Date” and “First Billing Date.” However, Billing will not work for this scenario.

      Until there are out-of-the-box messages available on the CPQ cart, it’s strongly advised by Conga Billing to create self-constraint rules (or have this logic in your callbacks) on the cart to prevent such operations.

      This will ensure that the user is stopped at CPQ itself instead of discovering at the Order stage which is too late for that ALI.

User Guide
Billing

November 27, 2025