February '24 Release Notes

In these release notes, you can find packages, requirements, features, enhancements, fixed issues, and known issues for the Billing February '24 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. 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.

Adding Manual Lines to System-Generated Invoices

Conga Billing now enables you to add manual lines to invoices generated by the Invoice Run and Ad hoc Invoices functionality to accommodate unique business requirements, like billing additional costs or miscellaneous charges to the customers. You can manually add invoice lines to a system-generated invoice that is in draft status. To use this feature, set Add Manual Lines To An Invoice to True.

You can also add new lines, edit or delete existing lines of an invoice by calling the BillingService.manageAdHocLines API.

For more information, see Adding Lines Manually to System-Generated Invoices.

Ability to Amend Usage Assets

If an amendment of the usage products is initiated, modification to the asset does not trigger the generation of negative billing schedules and unrating of the usage inputs (that have been rated previously) until there is an impact on the fee amount associated with the billing schedules. If the amendment does not impact the fee amount, the system does not create negative billing schedules.

For more information, see Amending Usage Assets.

Enhancements

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

Wallet Balance Based on Invoicing of its Billing Schedules

In previous releases, the wallet balance was updated as soon as the billing schedules of the Wallet Asset Line Item (WALI) were created, making all the balances available for instant consumption. With this release, you can now get the wallet balance only when the billing schedules of the WALI are invoiced (using Conga's Invoice Run or API). With this new feature, you control how much balance must be consumed from the wallet during a specific period. To use this feature, set the Wallet's Balance based on its Invoicing to True. For more information, see the Updating Wallet Balances section of Real-Time Wallet Updates and Wallets.

This enhancement includes the following functionalities:

Credit and Rebill from an Invoice Linked to a  WALI

You can now initiate credit and rebill operations from an invoice associated with a WALI.  If the Wallet’s Balance Based on its Invoicing setting is True, initiating credit and rebill operations triggers a validates the wallet's available balance. If there is sufficient balance available in the wallet, the credit and rebill operation is allowed, else it is rejected, and the UI displays an error message.

For more information, see Credit and Rebill from Wallet Asset Line Item section of Credit and Rebill.

Terminating a WALI

Conga Billing does not allow partial or mid-term termination of a WALI. Full-term termination of WALI is allowed subject to certain conditions.

For more information, see Wallets.

API to Create Credit Memos for Invoices Linked to WALI

You can create a credit memo for an invoice with invoice lines referencing a wallet asset line item (WALI) using an API. The API validates the total fee amount of the invoice lines with respect to the available balance of the wallet. If the validation passes, it executes the request, creates a Related A/R Transaction on the invoice, and updates the WALI balance in the Available Balance (Wallet) field.

For more information, see Creating Credit Memo for Invoices Referring to WALI by Using an API section of Direct Credit Memo From Invoice.

Payment Term to Accommodate Additional Offset

The payment term is now extended to accommodate additional offset. Two new fields, Offset 2 Type and Offset 2 Value, are introduced on the Payment Term object. The newly introduced fields allow you to set the required invoice due date in combination with the existing "Start" and "Offset" fields.

For more information, see Payment Term.

API to Change the Status of Billing Schedules of WALI

You can now call an API to change the status of the billing schedule from pending billing to invoiced or from invoiced to pending billing. This is a generic feature which is now supported for WALI. Each time the status of a billing schedule changes, the wallet balance gets updated. For the status change of a billing schedule from invoiced to pending billing, the API validates the fee amount of the billing schedules against the wallet available balance and processes the request after the validation passes. If you pass multiple billing schedule IDs the processing  happens in the order of the IDs sent to the API.

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

Data Model Changes

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

Fixed Issues

There are no issues fixed in this release.

Known Issues

There are no known issues in this release.

DOC ID: BILFEB24RN20240207