Billing UIUX: Support for Custom Plans, Plan Templates, Billing Preferences, and Usage Management

This release expands the Billing UI/UX, introducing comprehensive capabilities for managing custom plans, plan templates, billing preferences, and usage inputs — enabling sales, finance, and billing teams to configure and control billing operations directly within the interface.

Sales representatives can now create, edit, and delete Milestone or Term-Based custom plans directly from the order/Quote/Cart interface, using either predefined templates or direct entry forms, streamlining plan setup during the sales process. The new Manage Custom Plans interface provides a grid view for reviewing, creating and bulk-deleting custom plans, while the Custom Plan Details page centralizes all plan configuration and audit information in a single view, supporting flexible billing and revenue recognition needs.

Finance administrators have control over Custom Plan Templates, with the ability to create, edit, clone, activate, or inactivate templates from both list and detail views. The template creation UI supports configuration of plan type, computation method, installment structure, and payment terms, with built-in validations to ensure accuracy before saving. The Plan Template detail view allows administrators to manage templates directly, while other users can review template data in a read-only format; bulk actions and export options in the list view further streamline template management at scale.

The new Billing Preferences module gives administrators a list view and detail interface to create, edit, activate, inactivate, or delete billing preferences. To maintain compliance, only one active preference can be set as default at a time, and mass update or delete actions are restricted. Billing analysts have read-only access to preferences, ensuring appropriate separation between configuration and usage.

Usage management is enhanced with a centralized Usage Inputs list view supporting both single and mass entry of usage data. Billing analysts can create single or multiple entries, edit or delete usage inputs, and access detailed views for verification and rating.

Finally, the Forecast Billing feature is now accessible from any cart or transaction header, providing a consistent forecasting experience across proposals, agreements, and orders. The UI dynamically adapts to the transaction context, ensuring accurate forecasting and billing operations.

For more information, see Custom Plans, Custom Plan Template, Preferences, Usage Inputs, and Forecast Billing.

Credit Memo Application to Invoices

The Invoice Creation Request API now supports automatic application of approved credit memos to eligible invoices for the same Bill To account. Credit memos are applied using either the Oldest Invoices First or Most Recent Invoices First method, depending on the scenario, to reduce invoice balances in the correct order. This automation eliminates manual intervention and ensures that credit memos are fully or partially consumed as appropriate, with balances and statuses updated atomically.

Finance analysts can continue to manually apply one or more approved credit memos to an approved invoice using the API endpoint:

POST /api/invoicing/v1/creditmemos/apply-to-invoices

The API enforces validation rules, including status checks, unapplied balances, and duplicate detection, and updates payment statuses, audit logs, and related accounts receivable transaction records on both the invoice and credit memo. All changes are committed atomically to maintain data integrity.

These enhancements support accurate financial adjustments and reconciliation, and provide foundational capabilities for document generation, tax integration, and payment integration within invoice management.

For more information, see Use Case: Create an Invoice Creation Request, Use Case: Apply Credit Memos to Invoices, and Developer Hub.

Consumption Billing: Enhanced Usage Input Rating, Cloning, and Billing Header Updates

This release enhances the Usage Input Rating and Estimate APIs so that tier-level percentage-based Discount and Markup adjustments are applied directly to the Net Unit Price defined in the billing header, replacing the earlier List Price Override method at the unit tier level. The updated calculation logic supports Discrete, Range, and Cumulative Range dimension values.

A new Clone Usage Inputs API lets users duplicate one or more usage input records in a single operation, generating new records with unique IDs in either Loaded or Draft status. The API copies all standard fields except auto-number fields, Description, and Rated Amount, and returns detailed error information for any records that cannot be cloned.

This release also introduces several enhancements to improve usage-based billing accuracy. A new Offset picklist value has been added to the Type field on usage inputs, enabling negative currency values for Rated Amount and linking them to the appropriate Billing Schedule Record (BSR) to support mid-period amendments or cancellations. The Billing Header now includes a TCV (Usage) field, which aggregates Rated Amounts across all BSRs when the Price Type is Usage and automatically recalculates related fields such as Total Bill Including Adjustments.

For more information, see Use Case: Rate Usage when Unit Price is not Available at the Tier Level and Use Case: Consumption-based Billing Workflow

Billing API Enhancements

The Generate Billing and Milestone Completion APIs now calculate the Actual Fee Amount on Billing Schedule Details using the Amount from custom plan line items when there is exactly one transaction line. If the Amount is not specified or multiple transaction lines exist, the APIs default to using the Percent value. The Draft Rating API now exclusively uses the Quantity field for all computations, removing the Draft Quantity field from both request and response payloads.

The Edit Custom Plans API allows editing of milestone-based custom plans and their plan line items after Billing Header and Billing Schedule Records are created, without requiring an Asset-Based Ordering (ABO) transaction. Update installments—including fields such as Expected Date, Payment Term, Percent, Amount, Comments, and Description fields — provided the plan type is Milestone, the Billing Header is Active, and at least one installment remains open. Editing is also supported for custom plans created from the Agreement header or cart path before activation, including both percentage-based and amount-based variants, with validations on plan type, calculation method, and agreement activation status.

The Edit API supports editing custom plans created from a custom plan template before proposal acceptance. Update the Template ID, Billing Amount Criterion, LineItemIDs, and Description fields. The API automatically updates plan line items from the template when applicable and applies the corresponding edit logic and validations when switching between template-based and manual plans.

The Delete API supports removal of custom plans created from the Agreement context, including cascading deletion of dependent installment records. Deletion is restricted if the quote is accepted, the cart is finalized, the order is activated, or billing has been generated for the custom plan, and clear error messages are returned for unauthorized or invalid requests.

Sales representatives and agreement processing specialists can create milestone-based and term-based custom plans for one or more Agreement Line Items directly from the Agreement header during new sales. The API supports both payload-defined and template-driven plans, accommodating percentage-based and amount-based schedules across multiple Agreement Line Items. Only eligible Agreement Line Items without existing custom plans are processed. The API also enables creation of custom plans—both Milestone and Term Based— directly from the Proposal header, supporting plan creation using eligible templates and linking custom plans to selected line items and the Proposal.

The custom-plans/search API allows filtering custom plans by Agreement ID and Agreement Line Item ID, enabling retrieval of plans associated with specific agreements and their line items. The response includes plan header fields and installment details, and returns an empty result set when no matching plans exist.

The system updates the Milestone Expected Date logic for custom plans with Plan Type = Milestone by requiring that, from the second installment onward, each expected date must be the same as or later than the previous milestone’s expected date. This validation applies to both API and UI, regardless of whether Periods Needed is on or off, and removes the restriction that expected dates must fall within the period start and end dates.

For more information, see Developer Hub and Use Case: Custom Plan Workflow on Agreement.