Conga Billing October '23 Release Notes

In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the Billing October '23 release. For documentation updates, see What's New in Billing Documentation.

This documentation may describe optional features for which you have not purchased a license; therefore, your solution or implementation may differ from what is described here. Contact your Customer Success Manager (CSM) or Account Executive (AE) to discuss your specific features and licensing.

Packages 

The following packages and dependencies are required to upgrade to this release and use its new features. These are the minimum required versions; later versions are also supported. Prerequisites for each feature can be found in its documentation. Packages marked (New) are new for this release.

You can register your org for the Conga Upgrade Program. Conga Upgrade Program is an automated tool that upgrades packages available in your Salesforce org (Production or Sandbox) to the latest versions. In addition, it also ensures all the Conga-published managed packages are on the latest versions for your registered orgs. For more information, see Registering for Conga Upgrade Program.

For more information on installing Conga-managed packages, refer to Installing Conga Billing. For more information on upgrading Conga-managed packages, refer to Upgrading Conga Billing.

System Requirements and Supported Platforms

For requirements and recommendations to consider before installing the Conga product suite, see System Requirements and Supported Platforms Matrix.

Upgrade Note

Before you upgrade the Conga Billing Package, you must update the help text in the Billing Plan object's Billing Start Date and Billing End Date fields.

For more information, see Upgrading Conga Billing.

New Features

The following features are new to Conga Billing in this release.

Generating Summary Lines on an Invoice

Conga Billing now supports creating summary lines for invoices that are in a draft or approved status.

Once the basic configuration is done per Configuration Required to Generate Summary Lines for an Invoice, you should be able to generate the summary lines for a given invoice during the Invoice creation. You can also use an API to create the summary lines.

Based on your customer request, you can also re-generate the summary for a given Invoice through Invoice UI or using the API.

For more information, see Creating an Invoice Summary Line and Configuration Required to Generate Summary Lines for an Invoice.

The feature can also be used for ad hoc invoices, where you can generate invoice line summaries for such invoices. For more information, see Invoice Line Summary for Ad Hoc Invoices.

Splitting a Billing Schedule

Conga Billing enables you to split a billing schedule into two or more billing schedules by percentage, date, or amount. When a billing schedule is split, billing will supersede the original schedule and create new schedules with a Pending Billing status. The newly created schedules will reference the original schedule, and the sum of the fee amount will be the same as the original. You cannot further split these billing schedules. For more information, see Splitting a Billing Schedule.

Draft Usage Rating

Conga Billing now enables you to draft rate the usage inputs before you actually rate them. The draft usage rating enables you to see the forecasted billable amount for the submitted usage inputs. The usage inputs remain in the Loaded status even after the records are draft-rated, and the draft amount is updated in the (Draft) Rated Amount field. You can draft rate a single usage input record from the Usage Input Detail page and multiple records by using the list view, by running a batch job, or by calling an API. For more information, see Working with Draft Usage Rating.

Enhancements

The following enhancement is new to Conga Billing in this release.

API to Change the Status of Billing Schedules

The status change of a billing schedule after invoicing must be communicated to and understood by Conga Billing. The engine then implements a batch job to calculate the Remaining Billable Amount (RBA) and update it accordingly.

Invoicing done through the Invoice Run framework solves this purpose. But invoicing done through other means like manually or through any other automated interface, does not communicate the status change to the batch job and hence the RBA is not calculated and updated properly. To solve this problem, an API is required so that the status change of the billing schedules can be understood by Conga Billing and RBA can be updated properly.

 For more information, see Changing the Status of Billing Schedule by Calling an API and Changing the Status of Billing Schedules.

Data Model Changes

The following objects and fields are introduced to or changed in the system or data model in this release.

Fixed Issues

The following table lists the known issue fixed from the previous release.

Known Issues

There are no known issues in this release.

DOC ID: BILOCT23RN20231004