New Features

The following features are new to Conga CLM on Conga Platform in this release.

Conga Billing Architecture on Conga Platform

Using the Conga Billing service you can bill the orders created by Conga CPQ and CLM, as well as the orders created from external systems (orders coming from ERP, or orders coming from customer CPQ, etc.). 

When the service is initiated, Billing creates three layers of data - Billing Header (BH), Billing Schedule Record (BSR), and Billing Schedule Details (BSD).

  • The Billing Header is more like a placeholder to store the customer, product, and pricing information. For the pricing information, a setting is available based on which it can be fetched either from the order line item or the asset line item (similar to how the pricing is derived from the asset line item on Salesforce).  
  • Billing schedule records are the layer where the actual billing schedules are created which you are going to invoice your customers. However, the pricing detail is not present here but it is derived from the next layer.
  • Billing schedule details have a single purpose to capture the fee amount (amount invoiceable to the customer + any adjustments you want to give to your customers + any delta fee coming because of an amendment or cancellation). The fee amount from BSD is rolled up to BSR.

The billing header and billing schedule records synchronize with each other at scheduled intervals.

Configure Billing Preference

Billing preference is used for subscription billing. It captures the organizational policies or customer preferences to generate the billing schedules properly. It contains settings so that the recurring billing schedules are generated properly and the fee amounts are computed correctly.

There can be only one default Billing Preference at a given time.  You can update, delete, or inactive the existing billing preferences. You can also fetch all or specific billing preferences per your need.

Billing One-Time Products

Conga Billing enables the implementation team to bill one-time order line items (OLI). When the one-time order line is initiated for billing, the API creates a single billing header, a billing schedule record, and a billing schedule detail regardless of the term of the order line item. (There will be three layers of data but the actual billing schedule that is invoiceable to the customer is in the billing schedule records and that contains only one schedule.)

Billing Recurring Products

For recurring order line items (OLI), the API creates a cascade of billing schedule records depending on the term and billing frequency of the order line item. When you call the Initiate Billing API for a recurring order line item with OrderLineItemIds and ReadyForBillingDate as the payload, it starts processing the OLI. It creates one billing header, a cascade of billing schedule records, and billing schedule details. The billing schedule records are created with a "Pending Billing" status. 

One-Time Billing for Recurring Products

This feature enables you for a one-time billing of a recurring order line item with or without proration. Billing makes it possible by using a setting.

New Proration Computation Method

Conga billing has introduced new methods of proration calculation for an order line item on the Conga Platform. Now you have the following options for the proration computation to choose from:

  • Pick From Billing Preference
  • Calendar Days of First Month
  • 30 Days
  • No Bill
  • Maximize A/R

Special Rounding Method

Conga Billing has introduced a special rounding method for the Actual Fee Amount on the billing schedule records and billing schedule details. Now you can round the currency to the nearest integer depending upon the method selected. You can choose from the following values:

  • Always Up
  • Always Down
  • Half Up
  • Half Down
  • Half Even
  • None

Rounding Schedule for Fee Amounts

This feature rounds the decimal balances arising from any proration to the very first billing schedule record. This method is used for a recurring order line item and is applicable for a new sale transaction. If the Fee Amount Rounding Schedule is set to First, billing rounds the decimal values in the fee amount to the first billing schedule record. If the Fee Amount Rounding Schedule is set to Last, billing rounds the decimal values in the fee amount to the last billing schedule record.