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.

The feature can also be used for ad hoc invoices, where you can generate invoice line summaries for such 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.

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.


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.