Within these release notes you will find descriptions of new features, enhancements and API changes in the LogiSense Billing application. The content below details changes in major release versions, point release versions and hotfixes. If you have any questions about the information provided below please do not hesitate to contact your LogiSense support representative.
In this article:
In this article:
I
Billing performance and resiliency improvements
Payment Collection Bill Runs
Payments can now be collected using a bill run without the need to generate an invoice during the bill run
Only accounts setup to Auto-Pay will be applicable to payment collection bill runs
The Bill Run Collection Type of ‘Invoice Balance’ has been changed to to ‘Account Balance Due’ to support this feature. Payment collection using this setting will collect the balance of invoices which have a due date less than or equal to the current date
If the payment collection Bill Run Collection Type is set to ‘Account Balance’ then the full balance of the account is collected as a payment, regardless of the due dates set on the invoices on the account
Bill Runs Trigger Re-rating
Modified Bill Runs to initiate re-rating for accounts that require it to ensure re-rating is performed immediately and does not delay account billing
Ability to Change the Account Bill Day
Added the ability to change an account’s Bill Day and Usage Bill Day when the account has account packages added to it
Once the bill day is changed the current billing period will finish as is
A prorated charge will be applied to align the account to the new bill cycle
The prorated period will be handled as a full period when determining tiered pricing and usage bucketing
The new full billing period will start on the specified new bill day after the prorated period
Pending bill day changes are displayed on the Account / Settings / Billing tab
Pending bill day changes can be deleted or modified as needed
New Cancellation Charge options for Account Packages and Services
Prorate the transaction: apply charges for the cancellation period based on the amount of time within the period that the account-services were in a billable state
Charge full period: charge the full price of the account-services for the cancellation period, regardless of how many days in the period the services were in a billable state
No transaction: cancel the service and do not charge the service for this period ($0)
Waive Contract Penalties: When the account-package being cancelled contains a contract, this option will appear. When this setting is enabled contract early termination fees and remainder fees will not be applied
Added start and end dates to price plans to support time period specific pricing. The end date can be left unpopulated to provide an open ended price plan
Multiple price plans can be created on an account provided only one price plan is active at a time
Price plans can be future dated so the changes to prices can effectively be automated
Added a price plan setting that allows child accounts to inherit price plan pricing when enabled
Added a ‘Pricing inherited from’ detail at the bottom of the Account Package screen to indicate what price plan the account is currently using
Added an indicator beside the pricing source message on the Account Package screen to indicate when a Product Code is no longer valid
Added a new Pricing step to the order wizard where pricing is defined for the services within the order
The Personalize step in the wizard will no longer be used to set pricing but instead handle setting data overrides per service (e.g. Usage Identifier values, Custom Fields)
Service effective dates can now be configured in an order
Product Codes can be selected in an order if the code’s Account Price Plan is valid as of the package’s effective date
Minor order screen UI changes and validation improvements
x
Added a new event subscription screen under Setup / Extensibility / Event Subscriptions
This screen allows notifications to be sent to system users or account contacts when certain system events occur (e.g. notify an account billing contact that payment was successfully processed or notify a user configured in the LogiSense Billing application that a Bill Run has completed)
Event subscriptions can be sent via email (utilizing email templates in the system) or sent using webhooks
Money Buckets
Added the ability to configure money buckets which can allow multiple classes of usage to consume a specified amount of money (e.g. a $100 bucket that can be consumed by data, airtime and messaging usage)
A money bucket's value will always match the account’s currency
The price of the bucket (service charge) and amount of money in the bucket do not need to match. E.g. you can charge $100 for the bucket, but include $200 worth of usage in the bucket
Money buckets attached to a package can be shared so that all account-services in an account-package can draw from the bucket
Money Buckets can be configured with a rate plan
Money buckets can be configured in share plans
Add-on services can be configured with money buckets
Money Buckets cannot be prorated or set as a Billing Activation bucket
Aggregate Rates are not eligible to be used for Money Buckets
Bucket sizing/amounts are now defined on the Package Frequency for stand alone buckets and on the share plan for share plan buckets. Previously the bucket size/amounts were configured on the usage bucket
Rate Plans on Usage Buckets
Added the ability to configure rate plans directly on usage buckets
Rate plans can be configured on recurring buckets (with or without rollover) but not on non-recurring buckets
Bucket rate plans are not applicable to activation buckets or share plan add-on buckets
Bucket rate plans override rates set in price plans
Many AdminPortal and API validation improvements and fixes
Many AdminPortal and API error handling and error messaging improvements
Security enhancements
Data import and file mover resiliency improvements
v5 note / deprecated versions note
Deprecated APIs:
A
Updated APIs:
v
New APIs:
v
For additional API documentation please see the API Reference documentation on logisense.com.