What's new in BillingCenter for Qusar

BillingCenter now supports rebind transactions, which modify a bound policy submission without canceling or rewriting the submission. It also supports a final issuance transaction for policies at issuance. This feature helps you maintain billing integrity through every pre-issuance policy change.

Eligible policy-level changes include premium, payment plan, effective and expiration dates, producer (with commissions retroactive to the effective date), commissions, pricing, underwriting company, and currency for multicurrency policies. You cannot modify account-level and other restricted fields, such as billing level, billing method, alternate billing account, and billing contact.

Unlike standard policy change transactions, BillingCenter settles rebind/final issuance premium changes by fully offsetting the prior charges and adding the new charges, preserving a complete accounting audit trail and producing a clean, refactored invoice schedule that reflects the new dates. Final issuance transactions offer delta-charge processing, meaning that a single net-difference charge is sent.

For a short demo of the rebind transaction, watch this video:

Enhanced Funds Tracking now supports migrated transactions, enabling insurers to adopt the feature on existing books of business. A new callback lets you flag transaction bundles that were created before Enhanced Funds Tracking was migration-aware.

This release also strengthens fund slice and disbursement handling. Improvements include more reliable logic for selecting default unapplied fund slices, preventing scenarios that could create a negative fund slice, and a fix that preserves an overridden disbursement payment instrument instead of resetting it based on default values. Additionally, the feature has been validated at scale through large-volume performance testing across list bill and high-volume producer scenarios.

New endpoints

The following endpoints have been added to Cloud API. If you are doing a core update, you might want to add these endpoints to the appropriate role.yaml files to provide authorization to users and services as needed.

Billing API

• GET /accounts/{accountId}/enhanced-funds-sources
• GET /accounts/{accountId}/policies/{policyId}/policy-periods/{policyPeriodId}/trouble-tickets
• GET /accounts/{accountId}/policies/{policyId}/trouble-tickets
• GET /accounts/{accountId}/t-accounts
• GET /accounts/{accountId}/trouble-tickets
• GET /disbursements/{disbursementId}/funds-slice-allocations
• GET /disbursements/{disbursementId}/funds-slice-allocations/{fundsSliceAllocationId}
• GET /enhanced-funds-sources/{enhancedFundsSourceId}
• GET /enhanced-funds-use-event-groupings/{enhancedFundsUseEventGroupingId}
• GET /enhanced-funds-use-event-groupings/{enhancedFundsUseEventGroupingId}/enhanced-funds-use-events
• GET /producers/{producerId}/enhanced-funds-sources
• GET /producers/{producerId}/t-accounts
• GET /producers/{producerId}/trouble-tickets
• POST /search/disbursements
• POST /search/trouble-tickets
• GET /suspense-payments/{suspensePaymentId}/t-accounts
• GET /t-accounts/{tAccountId}
• GET /t-accounts/{tAccountId}/unapplied-fund-slices
• GET /t-accounts/{tAccountId}/unapplied-fund-slices/{unappliedFundSliceId}
• GET /t-accounts/{tAccountId}/unapplied-fund-slices/{unappliedFundSliceId}/enhanced-funds-use-events
• GET /t-accounts/{tAccountId}/unapplied-fund-slices/{unappliedFundSliceId}/enhanced-funds-use-events/{enhancedFundsUseEventId}
• POST /trouble-tickets
• GET /trouble-tickets/{troubleTicketId}
• PATCH /trouble-tickets/{troubleTicketId}
• POST /trouble-tickets/{troubleTicketId}/assign
• POST /trouble-tickets/{troubleTicketId}/close
• GET /trouble-tickets/{troubleTicketId}/holds
• GET /trouble-tickets/{troubleTicketId}/holds/{holdId}
• GET /trouble-tickets/{troubleTicketId}/holds/{holdId}/hold-type-entries
• POST /trouble-tickets/{troubleTicketId}/holds/{holdId}/hold-type-entries
• GET /trouble-tickets/{troubleTicketId}/holds/{holdId}/hold-type-entries/{holdTypeEntryId}
• PATCH /trouble-tickets/{troubleTicketId}/holds/{holdId}/hold-type-entries/{holdTypeEntryId}
• DELETE /trouble-tickets/{troubleTicketId}/holds/{holdId}/hold-type-entries/{holdTypeEntryId}
• GET /trouble-tickets/{troubleTicketId}/join-entities
• POST /trouble-tickets/{troubleTicketId}/join-entities
• GET /trouble-tickets/{troubleTicketId}/join-entities/{troubleTicketJoinEntityId}
• DELETE /trouble-tickets/{troubleTicketId}/join-entities/{troubleTicketJoinEntityId}
• GET /trouble-tickets/{troubleTicketId}/notes
• POST /trouble-tickets/{troubleTicketId}/notes

Common API

• POST /activities
• POST /search/activities

Support for enhanced funds tracking

This release of BillingCenter Cloud API exposes key entities in the data model of the Enhanced Funds Tracking feature. This includes T-accounts, unapplied funds, enhanced funds sources, unapplied fund slices, funds slice allocations, and funds use events. These endpoints provide full coverage of enhanced funds tracking functionality through the Billing API, so you can track where every bit of money flows in and out of BillingCenter.

Trouble tickets

You can now create and manage trouble tickets through the Billing API. This includes setting holds on trouble tickets and using join entities to associate trouble tickets with the relevant account, policy period, producer, or transaction.

Create and search activities

You can now create and search for activities using the Common API.