LogiSense Billing 10.8.x.x Release Notes

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.

10.8.0.0 Release Notes #

Change Highlights #

Billing and Invoicing Enhancements: #

• Improved performance when voiding an invoice
• Modified invoice item rounding to use carryforward calculations. Sub-cent values will now be factored in to the invoice item calculations as they round, ensuring the sum of the invoice items will always equal the invoice total
• Modified the Bill Run History screen ‘Invoice’ step to display the number of invoice items in the total/queued/processed fields instead of the number of total/queued/processed messages
• Modified the Bill Run History screen ‘Term’ step to display the number of accounts in the total/queued/processed fields instead of the number of total/queued/processed messages
• Modified the Bill Groups screen to show account Display Names in the account list and allow accounts in the list to be filtered by Name, Display Name, accounts excluded from the bill group and accounts included in the bill group

Tax Enhancements: #

• Added a new Missing Jurisdiction Code screen to the Operations menu that returns all of the Account Tax Contacts per Bill Group that do not have a pCode set on them. The ability to configure the pCode refresh schedule is also available on this screen
• Added the ability to refresh the Tax Jurisdiction Code on the Contact screen without the need to modify the contact address
• Added a new automated service for systems integrated with AvaTax AFC. This service will analyze all Account Tax Contacts where the pCode address has not been updated in the last three months and call out to Avalara using the address to determine if the pCode value has changed. If it has, the pCode will be updated
• Added core support for importing tax rates into the system

Owner Enhancements: #

• Added a setting for Absolute Session Timeout, allowing for a maximum amount of time an application user can use the system before being required to authenticate

Usage & Rating Enhancements: #

• Mediation, rating and rerating performance, resiliency and logging improvements
• New usage calculation types for aggregate rates
  • Previously LogiSense Billing would sum together all usage daily totals to apply the rate, but now the following options are also supported:
    • Max: only charge the highest daily usage total in the period
    • Last: only charge the last daily usage total for the period
    • Mean: average out the daily usage totals in the period and apply the rate based on that value
    • Median: find the median value of the daily usage totals in the period and apply the rate based on that value
    • Continuous: sum together the daily aggregate values and apply the previous day’s usage total for any dates that do not have usage
• Usage Rerates screen
  • Added an operational screen to show the results for historical rerates run in the system, and details on scheduled and in progress rerates

Bulk Export Service #

• Added a bulk export service focused on delivering high volume custom queries as csv reports in a timely fashion
• Export files can be run on demand, via a schedule, or automatically as part of billing as an invoice attachment. Invoice attachment exports are only supported for Offline and Export deliveries
• Export files can be generated on the LogiSense Billing S3 file storage or delivered automatically to a customer configured S3 or SFTP directory
• Export files can be configured with custom naming per export, and per file, using tokens to generate the file name

Other Enhancements and Fixes #

• Many AdminPortal and API validation fixes and improvements
• Fixed multiple AdminPortal UI Issues
• Fixed multiple Customer Portal UI issues
• Error handling fixes and improvements
• Improved search performance
• Added a user settings screen for the logged in user, allowing them to manage a limited set of their own user settings, like names, email, and locale
• Fixed permission issues relating to displaying screen links shown on the left hand side menu and granted access to the account search and overview screens if the user has access to other account screens
• Fixed a permissions issue which resulted in an error when attempting to access the custom fields screen
• Added an option for the Customer Portal to change the default Account hierarchy view to Parent/Child instead of Invoicer. Portal users can now view and interact with any account in their account’s hierarchy when this setting is enabled
• Added a notice page that will indicate when scheduled maintenance is occurring in the Admin and Customer Portals
• Added support for sending emails using a Google G-Suite login, bypassing the need for a dedicated SMTP server for sending emails out of LogiSense Billing
• Renamed the SMTP Settings screen to Email Settings
• Replaced the email editor in the UI, allowing for enhanced email templates supporting markup, hyperlinks, and HTML images to be embedded in the template
• Account price plan tiered usage rate tiers can now be customized per price plan along with the rate per tier
• Removed the References tab from the Service Transitions screen
• Modified the Credits and Payments screens to show the invoice name on the Disbursement tab instead of the Invoice ID
• Added a ‘Created By’ field to the Payments and Transactions screens to indicate which user added the payment or transaction
• Added support for account contracts to start on the 29th-31st of a month provided the contract has no commitments configured
• Fixed an issue that could prevent a contract from being canceled when it was configured with a renewal type of ‘New Contract’ and no commitments existed on the contract
• Fixed an issue that could cause a product code to be removed from an account-package after modifying the account-package’s effective date
• Fixed an issue were the calendar UI displayed the incorrect number of days in a month
• Fixed an issue where it wasn’t possible to clear a future cancelation date set on a usage bucket attached to an account-service
• Fixed an issue where accounts would display ‘AUD’ instead of a dollar symbol when configured to use Australian currency
• Fixed an issue where a recurring credit could be created for a reversed transaction, improperly crediting an account
• Added references to related Bill Runs, Payments, and Account Packages to the Order screen
• Fixed an issue where a new account-package could not be added to an existing order when the order was in draft status
• Fixed an issue where a share plan bucket would not be created properly after a usage only billing activation service was activated
• Fixed an issue that could cause duplicate charges to be applied for flat charges configured on usage bucket tiers
• Fixed an issue that was causing no rerate entry to be created when a share plan add-on was cancelled
• Fixed an issue that was causing no rerate entry to be created when the effective date of an account-package within a share plan was changed
• Modified usage rate tiers to be sorted by threshold values to prevent the appearance of overlapping thresholds
• Fixed an issue that prevented a usage rate from being created when the associated rate group was configured for pass through rating
• Fixed an issue that could cause rating to fail when attempting to rate overage charges using an overage rate plan configured on a usage bucket
• Fixed usage rate tier calculation for bracketed tiered pricing so that tier breakpoints are now exclusive rather than inclusive to prevent the possibility of incorrectly billing tiered usage
• Fixed a billing issue where the bill run delivery step would not start if incomplete report fulfillment records existed on cancelled accounts
• Fixed an issue where a bill run could fail when attempting to bill an account-package with a custom address configured on it
• Fixed a billing issue that could cause accounts to be repeatedly queued for payment processing in environments with a large number of accounts (40k+)
• Fixed a billing issue where two aggregate invoices with a balance equaling zero dollars could still result in automatic payment collection occurring
• Fixed an issue in Adyen integrated environments where importing payment method data for an existing payment method failed to update credit card expiry dates and payment method identifiers
• Fixed an issue where changing the invoice prefix would not reset invoice numbering to follow the number configured in the ‘Start’ field
• Fixed an issue where the invoice name was not displayed properly on account screens after a bill run failure occurred in some scenarios
• Fixed an issue where an incorrect total could be calculated on an invoice after voiding an invoice that contained a one-time credit or one-time transaction
• Fixed an issue that could cause bill runs to partially fail when attempting to deliver a high volume of invoices
• Real Time Taxation through AvaTax AFC has been removed
• Fixed an issue in AvaTax integrated environments where creating a manual credit would proceed without error when a tax jurisdiction code was missing from the account
• Added the ability to reprocess a failed Data Import file from the UI and API
• Added the ability to export expiring JSONAPILog data before it is purged from the system
• Removed legacy IP blacklist and whitelist functionality
• Clicking on a record in the Usage Identifier History screen will now take the user to the related Account and Account Package directly
• Added support for webhooks sent out of the system to use OAuth authentication using the form-url-encoded standard. Previously only the json standard was supported
• Fixed an issue where attempting to edit a Transfer Location would fail with an Update Failed error message
• Fixed an issue that prevented an existing event subscription email template from being updated
• Fixed an intermittent caching issue that could cause incorrect values to be returned when looking up custom field values across multiple webservers
• Fixed an issue that could cause login failures in SSO integrated environments
• Fixed an issue where no search results would be returned when using operators to query certain columns
• Fixed an issue with Advanced Filters that could cause the column filter list to be unpopulated
• Fixed an issue that prevented Advanced Filters from being configured on the Notes screen

API Changes #

• Deprecated APIs:
  • Account/Service/UsageIdentifier?prefix (Get)
  • Account/Service/UsageIdentifier/Paged?prefix (Get)
  • usage/billingtype (Get, Post, Put, Delete)
  • usage/billingtype/type (Get)
• Updated APIs:
  • Added support to set the effective start date of the initial Rate Plan on Account Packages, Package Services, and Package Frequencies
  • v10/AuthorizationServer/Api/V10/Access/Login (Post): AuthenticateResponse DTO Added: [JsonPropertyCreated(PropertyName = “.sessionExpires”, Since =APIVersion.V10)] DateTime? SessionExpires { get; set; }
  • v10/AuthorizationServer/Api/V10/ServiceAccess/Login (Post): AuthenticateResponse DTO Added: [JsonPropertyCreated(PropertyName = “.sessionExpires”, Since =APIVersion.V10)] DateTime? SessionExpires { get; set; }
  • v10/AuthorizationServer/Api/V10/CustomerPortal/Access/Login (Post): AuthenticateResponse DTO Added: [JsonPropertyCreated(PropertyName = “.sessionExpires”, Since =APIVersion.V10)] DateTime? SessionExpires { get; set; }
  • v10/BillGroup (Get, Post, Put, Patch, Delete): BillGroupDTO Removed: AdvanceInvoiceDays, InvoiceCloseThresholdAmount, UsageBillingTypeId and UsageBillingTypeName
  • v10/Internal/Account (Post, Patch): In AddressDTO and TaxAddressDTO, added FetchTaxJurisdicationAsync to support for retrieving a pCode from AvaTax asynchronously
  • v10/Internal/Account/Package (Post, Patch): In AddressDTO and TaxAddressDTO, added FetchTaxJurisdicationAsync
  • v10/Internal/Account/Package/FromCatalog/Metadata (Post, Patch): In AddressDTO and TaxAddressDTO, added FetchTaxJurisdicationAsync
  • v10/Internal/Account/id/Contact (Post, Patch): In AddressDTO and TaxAddressDTO, added FetchTaxJurisdicationAsync
  • v10/Internal/Order/id (Post, Patch): In AddressDTO and TaxAddressDTO, added FetchTaxJurisdicationAsync
  • v10/EventSubscription/Webhook (Post, Put, Patch, Get): EventSubscriptionWebhookDetailDTO has WebhookConfigurationSubsetDTO WebhookFormatTypeId { get; set; }
  • v10/Rerate (Post, Patch): Added int CreatedByUserId
  • v10/RerateSchedule (Get): Removed Property: ScheduledStart
  • v10/RerateSchedule/Paged (Get): Removed Property: ScheduledStart
  • v10/RerateSchedule/[id] (Get): Removed Property: ScheduledStart
  • v10/Usage/Rate/Group (Get, Post, Put, Patch, Delete): UsageRateGroupDTO AggregationTypeId { get; set; } AggregationTypeName { get; set; }
• New APIs:
  • JsonApi/ApiVersion/Latest (Get)
  • v10/BillRun/History/{id}/Recovery (Post): allows a bill run in a failed state to be retried. Note: this API does not retry running the subscription or usage billing stages of the bill run
  • v10/DataImport/Usage/{apifeedname} (Post)
  • V10/DataImport/Usage/Download?FileKey=”[Path and File Name]” (Get): allows you to check if a usage file has been uploaded successfully
  • v10/DataImport/Usage/History/{id}/Reprocess (Post)
  • v10/Invoice/Item/TaxSummary (Get)
  • v10/Invoice/Item/{invoiceItemId}/TaxSummary (Get)
  • v10/Order/{orderId}/Status (Get)
  • v10/Order/{orderId}/PackageTracking/Paged (Get)
  • v10/RerateScheduleTracking/ByRerateSchedule/{id} (Get):
  • v10/RerateScheduleTracking/ByRerateSchedule/{id}/Paged (Get)
  • v10/Rerate/Pending (Get)
  • v10/RerateSchedule (Get)
  • v10/Rerate/Now (Post)
  • v10/Schedule/DataExport (Get, Post)
  • v10/Schedule/DataExport/{id} (Put)
  • v10/Schedule/Rerate (Get, Put, Post)
  • v10/SMTP/Setting/SMTPAuth (Post)
  • v10/SMTP/Setting/SMTPAuth/{id} (Put, Get)
  • v10/SMTP/Setting/GoogleJWT (Post)
  • v10/SMTP/Setting/GoogleJWT/{id} (Put, Get)

For additional API documentation please see the API Reference documentation on logisense.com.

10.8.0.1 Release Notes #

• Added enhancements to support revenue modeling reporting for recurring charges, non-recurring charges, tiered and non-tiered usage charges
• Fixed an issue that could cause a billing exception to occur even though there was no billing error when billing an account-package with the ‘Charge Recurring Only if Usage’ feature enabled
• Fixed a validation issue that prevented Contacts from being saved when configured using an ‘address with country only’ format
• Fixed an issue where negative invoice balances were not distributed correctly after voiding an invoice and re-billing an account
• Fixed an issue where voiding an invoice that contained a manual tax inclusive charge could generate a manual transaction with an incorrect amount
• Fixed a validation issue that could prevent a transaction with a negative value from being reversed
• Fixed an issue where a credit on a child account could be displayed with the incorrect currency symbol when the parent and child accounts used different currencies
• Fixed an issue where changing a credit from manual disbursement to automatic disbursement would display the undisbursed amount without taxes included
• Fixed a billing issue introduced in version 10.7.3.4 where payment execution used a date-time value to determine when to run payments instead of a date value, which could cause the payment step to be missed when executing a bill run
• Fixed an issue that could prevent currency exchange settings from being updated
• Fixed an issue where disbursement could occur when deleting a payment
• Fixed a tax rounding issue where a partial reversal of a transaction could result in the account balance being off by 0.01

10.8.1.0 Release Notes #

Change Highlights #

Product Catalog Enhancements: #

• Price Change Scheduling
  • Added the ability to schedule future price changes on packages in the Product Catalog
  • If price changes are scheduled they can also be seen at an account level. Account-services will display a new ‘Price Changes’ button on the Pricing tab which will indicate the details of the upcoming price change
  • If account price plans or direct price overrides are applied to an account-package then those prices take precedence, regardless of any price changes configured in the catalog
• Money Contract Commitments:
  • Added The ability to use Money as a usage commitment option. This option will calculate the post bucketing usage amounts (before taxes) from all applicable usage classes and account-services in order to determine if the money commitment is met on the contract
  • Money contract commitments can be configured on invoicer and sub accounts
  • Invoicer contracts can be configured to include sub account usage

Billing and Invoicing Enhancements: #

• Invoice Discounts
  • Added the ability to setup Invoice level discounts for accounts on the Accounts / Settings screen
  • Discounts can be based on the Invoice total or the count/spend of specific account-packages or account-services
  • Tiered discounts and sequential discounts can be configured

Owner Enhancements: #

• Financial Periods
  • Added a new Financial Period section on the Owner screen allowing financial periods to be defined and managed
  • Financial Periods can be imported
  • Financial Periods are optional, no system behavior changes will occur if they are not configured

Account Enhancements: #

• Added the ability to search for accounts using billing contact data
• Added a ‘Forget Account’ option on the Account / Settings screen which allows GDPR data to be purged for canceled accounts
• Added the ability to reverse unbilled transactions, credits, and recorded payments (previously these items could only be deleted)

Tax Enhancements: #

• Adyen Integration Enhancements:
  • Default Merchant Account:
    • A new ‘Default Merchant Account’ option is configurable on the Account / Settings screen in Adyen integrated environments
    • When Collecting payments during billing the default Merchant Account will be used instead of determining the account based on the billing contact country value
  • Chargebacks:
    • Added support for chargebacks through the Adyen payment gateway
    • Added support for Adyen chargeback_failed webhook events. When LogiSense Billing receives a chargeback callback from Adyen for a payment in the system, a payment refund will occur, reducing the payment amount

Usage & Rating Enhancements #

• Account-Service Rate Plans:
  • Added the ability to configure rate plans on account-services
• Aggregate Rates at the Invoicer level:
  • Aggregate rates can now be configured on rate groups to pool at the Invoicer level instead of by service
  • When enabled all applicable usage data under the Invoicer account hierarchy will be analyzed to generate a usage charge on the Invoicer account

Other Enhancements and Fixes #

• Billing resiliency improvements
• Addressed many AdminPortal and API validation issues
• Error handling fixes and improvements
• Fixed many UI Issues
• Modified modals to remove blur and reduce shading to allow users to read text in the background behind them
• Modified the Bill Run History screen Render and Contract steps to display progress based on the total number of accounts in each status
• Modified the Bill Run History screen to ask for confirmation when attempting to Stop or Retry a bill run
• Modified the Credits screen to allow Details, Dates, Posting dates, Period End and Period Start date values to be modified on un-invoiced credits
• Modified contact phone numbers to allow non-numeric characters
• Modified the AdminPortal to enable the auto-disbursement option by default when creating credits and payments
• Modified child accounts that use a different currency from their parent account to display converted currency amounts when viewing unbilled transactions
• Fixed a billing issue where accounts would continue to be processed if the Bill Run was canceled in the middle of the billing stage
• Fixed an issue which could cause incorrect date/time values to be set on account-service status last updated dates
• Fixed an issue on the Transaction screen that could cause an update failed error to occur when attempting to modify the Detail field
• Fixed an issue that could prevent one time credits from being reversed or deleted on the Transactions screen
• Fixed an issue that could prevent non-recurring charges from being reversed
• Fixed an issue where it wasn’t possible to delete a newly created unbilled tax adjustment transaction
• Fixed an issue where backdated cancelation of an account-package could result in an incorrect account balance in scenarios where the package applied transition charges
• Fixed an issue where an invoice item with a discount could not be reversed if the related account-package has been canceled
• Fixed an issue that prevented a billing contact with an American or Canadian address from being updated to use another country, if that country did not support states
• Fixed an issue when adding a tax inclusive service to a package frequency that could result in the tax inclusive option being re-enabled after the user had disabled it
• Fixed a rounding issue that in some scenarios could cause tax inclusive invoice items to have incorrect amounts
• Fixed an issue where tax exemptions configured on services were not being applied when adding credits
• Fixed an issue that could cause unexpected unbilled charges on sales order invoices
• Modified the Account Search Search View to indicate which fields are being used as search terms
• Fixed account search permission issues
• Fixed an issue where a price plan could not be added if its Start Date matched a previous price plan’s End Date
• Modified the Invoices screen to include a ‘Do Not Deliver’ checkbox which will indicate if the Invoice has been set not to be delivered and allow that value to be modified
• Modified invoices to set their due dates to Today when an invoice is created with a negative balance
• Modified invoice void logic to set the voided invoice Due Date and the voided transactions posting dates to ‘Today’. Previously the dates were taken from the original invoice
• Fixed an issue where re-rendering an invoice set the invoice Date and invoice Due dates to the date the invoice was re-rendered instead of the original invoice dates
• Fixed an issue where transition charges for services changed from a billable status to a canceled status would not be applied after an invoice was voided and rebilled
• Fixed an issue that could cause invoice balances to be incorrect when calculating payment disbursements in some scenarios
• Modified Date fields on invoice templates to support forward slashes
• Fixed an issue that resulted in the ‘Last Modified Date’ failing to update when saving an invoice or credit note template
• Fixed an issue which caused tax summary token data not to render on credit notes
• Fixed an issue where canceling prorated buckets could result in incorrect bucketing values
• Fixed a rare issue that could cause usage records to fail to be mediated or go into exception
• Fixed an issue that could cause usage not to be bucketed by an account share plan if there was a billing activation service configured
• Improved status messaging in AvaTax integrated environments to indicate whether taxation is pending or has not occurred
• Modified AvaTax integration to address exceptions that can occur when attempting to retrieve Canadian addresses
• Modified the Payments screen to display check numbers when the payment type is Cash
• Modified Adyen integration to send level 2 and level 3 credit card data when making payments
• Modified Adyen integration to reject payments made with an unknown or unsupported Card Type and log a validation message stating the card type was not supported
• Fixed an issue where payments collected during dunning were not set to disbursed automatically
• Fixed an issue that caused payments collected by a sales order bill run not to be disbursed
• Fixed an issue in Adyen integrated environments that could cause duplicate payments or duplicate refunds to occur in certain scenarios when multiple webhooks were setup in the same environment
• Fixed an issue in Adyen integrated environments where Klarna payment methods could not be added if the ‘Name’ value wasn’t populated
• Fixed an issue that could result in a ‘Payments redacted’ error when attempting to make ACH payments through a Spreedly gateway
• Fixed a webhook issue that resulted in the sourceCallbackPayload field being empty when making a payment webhook request
• Fixed a webhook issue where payment status update events could fail to populate payment data in the generated webhook
• Modified events to trigger only when an entity is updated and the state of the entity matches the criteria defined in the event filter
• Fixed an issue where a custom field column that started with a number value could cause account search failures when searching for accounts using the Account By Extensions option
• Fixed an issue that could cause Month to Date report values to be inaccurate in rare scenarios
• Added the ability to export or purge login history data from the system
• Added a new daily data archive option, ‘Usage Delta Export’, which exports rated and mediated data
• Modified the Billing Delta Export job to include AccountPriceBookRegion and ServicePriceBookSetting items
• Fixed an issue with the Billing Delta Export data archive job which could cause no notification or logging to occur when data archive items were skipped due to an error
• Fixed an issue where reports were not delivered to an external transfer location if the reports were configured to be delivered by event subscription
• Adjusted SSO integration to ensure user group changes in the identity portal result in corresponding role updates for the user in LogiSense Billing
• Modified the JSON API log to set the stored DateTime value for requests to the request start time (previously the request end time was logged)
• Fixed an issue that generated an unexpected API error when attempting to filter the JSON API logs by ID
• Fixed an issue that could result in usage identifiers and account service IDs failing to match in different tables in the database

API Changes #

• API Enhancements:
  • Fixed a caching issue in multi web server environments where several APIs could return a 404 not found error when requesting a resource by ID
  • Fixed an issue with API filters where the ‘notStartsWith’ operator was not working
  • Fixed several issues that could prevent data from being imported by API
• Deprecated APIs:
  • v10/Invoice/Item (Post)
• Updated APIs:
  • v10/Account/<id> (Get, Patch, Delete): In AccountDetailDTO added AccountInvoiceDiscount
  • v10/Package/Service/Price/Plan (Get, Post, Patch, Delete): PackageServicePricePlanDTO
    Added: PricePlanTypeId, Effective, PriceChangeTrackingId, PriceChangeCriteriaId, Created, Updated.Removed: GeneralLedgerId, ServiceTaxCategoryId, IsTaxInclusive
  • v10/PriceChangeTracking (Get): PriceChangeTrackingDTO
  • v10/Usage/Rate/Group (Get, Post, Patch, Delete): Added IsAggregatedByInvoicer
  • v10/Package/Frequency/{packageFrequencyId}/PriceBook/{priceBookId}/Currency/{currencyid/code}/Pricing (Get): Retrieve all of the PackageFrequency objects
  • v10/Account/Package/FromCatalog (Post): Added UsageRatePlanName to AccountPackageFromCatalogServiceAttributeDTO
  • Package/Frequency/{id}/Basic/Detail (Get): PackageDetailBasicDTO
  • Package/Frequency/{id}/PriceBook/{id}/Pricing (Get): PackageServicePricePlanDTO
  • DataImport/Usage/Feed/{{FeedName}}/Search (Post): added to ViewImportBatchInfoDTOpublic string FileName { get; set; }
  • v10/Invoice/Item (Get, Put, Patch): InvoiceItemDTO Added UsageValue and UsageUnit readonly fields
  • v10/EventSubscription/Webhook (Post, Put, Patch, Delete, Get): Added WebhookFormatTypeName support to EventSubscriptionWebhookDTO
• New APIs:
  • v10/Invoice/DiscountCalculationType (Get)
  • v10/Invoice/DiscountType (Get)
  • v10/PriceChange (Get, Post, Put, Patch, Delete)
  • v10/PriceChangeType (Get)
  • v10/PriceChangeStatusType (Get)
  • v10/PriceChangeCriteriaPriceType (Get)
  • v10/Account/Forget (Post)
  • v10/Account/ByBillingContact/Search (Post)
  • v10/PricePlanType (Get)
  • v10/PriceChange/{id}/Process (Post)
  • v10/PriceChange/{id}/Approve (Post)
  • v10/PriceChange/{id}/Rollback (Post)
  • v10/PriceChange/{id}/Pricing/Paged/Detail (Get)
  • v10/WebhookFormatType (Get)

For additional API documentation please see the API Reference documentation on logisense.com.

10.8.1.1 Release Notes #

Change Highlights #

Amount and Invoice Precision Changes: #

• Modified invoice amount precisions to adhere to the invoice currency precision. All invoice amounts will now round to the currency precision, this includes charges, credits, payments, manual transactions, reversals, taxes, tax adjustments, disbursements and invoice/account balances.
• Rounding occurs when invoicing, manual charges such as credits and taxes can still be entered with full precision
• If manual transactions are added on a sub-account that uses a different currency then the invoicer account the transaction will be converted to the invoicer’s currency

Dunning improvements #

• Performance improvements
• Added more conditions which allow accounts to be excluded from dunning and skipped
• Improved account and invoice balance reconciliation process to validate that items are in the proper state before dunning and ensure unbilled or unrecognized credits and payments are accounted for before applying dunning rules
• Pending payments, unbilled reversals, and unbilled tax adjustment credits are now factored in to the overdue balance calculation. Accounts with overdue invoices balances that would be offset by pending amounts are no longer subject to dunning. The Collect Payment dunning option also factors in these amounts when calculating the amount to collect using the payment method
• Payment Collection through Dunning will now attempt to collect a single payment from the account for all overdue invoices instead of one payment per invoice, lowering collection fees
• Negative invoice balances are now factored in when an invoice with an overdue balance exists, offsetting the balance
• Fixed issues with when dunning actions execute in relation to other dunning actions

Other Enhancements and Fixes #

• Modified account-package cancellation logic to apply full period charges if that option is configured and cancelation of the account-package occurs due to a package contract expiring
• Fixed an issue with the account search which caused deleted contact points to be returned in search results
• Fixed an issue where a service charge could be applied after a service was canceled if the service’s last billed date exactly matched the service’s effective cancel date
• Fixed an issue where reversing a partial transaction could result in a credit amount of one cent being displayed
• Fixed an issue that could cause an account-package’s cancelation date to be cleared after voiding an invoice
• Fixed a rare rounding issue that could cause invoice items to display incorrect values
• Fixed an issue where the Maximum charges per period value set on Transitions was not honored when an account-package was added with a product code specified
• Fixed an issue that prevented an account price plan from being deleted if it contained usage rate tier overrides
• Fixed an issue were updates to usage rate tier overrides on account price plans could result in incorrect amount values
• Fixed an issue where a price book region would remain configured on an account after a user removed it
• Fixed an issue that could cause invoices to be delivered by email multiple times
• Fixed an issue that could cause usage charges not to be listed as invoice items when billing usage related to rate groups aggregated at the invoicer level and configured for progressive tiering. Note: this would not lead to incorrect billing, the total amount of usage billed would still be accurate
• Fixed an issue which caused the usage rates screen to fail to refresh after modifying the usage rate group
• Fixed an issue that could cause a continuous aggregated usage charge to be split between two invoices when billing back dated usage
• Fixed an issue that could cause usage billing to fail when pass through rating was enabled
• Fixed a customer portal issue where the products page failed to load data when an account-package was configured with a custom tax address
• Modified Adyen integrated environments to create pending reversed payments for Capture_Failed events in order to avoid the possibility of overcollection. Users can then move pending reversals to Captured or Rejected by reviewing payment details in the Adyen portal
• Modified Adyen integration to ensure payments cannot be imported with a posting date that is within a closed fiscal period
• Fixed an issue in Adyen integrated environments were the invoice balance due could be incorrect in some scenarios after a payment was rejected and then captured after a retry
• Added ID event tokens which are returned by webhooks and emails:
  • Account Package Id
  • Account Service Id
  • Account Contact Id
  • Payment Id
  • Data Import History Id
• Added the ability to group by a string datatype in embedded report data
• Added invoicer aggregates to the revenue modeling MTD reports
• Added bucket aggregates to revenue modeling reports
• Fixed an issue that could cause an overflow exception when attempting to generate reports
• Fixed an issue that could cause the usage delta export to fail when exported usage had duplicate usage dates
• Modified the InvoiceItem table to store InvoiceItem.UsageValue in base units to prevent a loss of precision in certain scenarios
• Fixed an issue where the Event Service would fail with an exception when processing an event message if the request that triggered the event included a custom field and a value

API Changes #

• API Enhancements:
  • ViewPackageServicePricePlan (Get): fixed an issue which caused the response to return default date time values for the ‘updated’ and ‘created’ fields
• Updated APIs:
  • v10/EmailTemplate/Type (Get): made API public
  • v10/EmailTemplate/Type/{id} (Get): made API public
  • v10/EmailTemplate/Type/Paged (Get): made API public

For additional API documentation please see the API Reference documentation on logisense.com.

10.8.1.1 Build 137 Additions #

• Fixed an issue that caused account-services to observe the tax inclusive configuration set on services instead of the tax inclusive configuration set on package-services
• Fixed an issue that caused the reverse and refund options to be disabled when a payment amount was a thousand dollars or more
• Fixed an issue that caused amounts on accounts to be displayed with commas
• Fixed an issue on the Transactions screen where an incorrect currency, amount or amount precision could be displayed when viewing reversal taxes related to a child account
• Fixed an issue in Adyen integrated environments that could cause an incorrect precision to be displayed in the Amount field when making a payment

10.8.1.2 Release Notes #

Change Highlights #

Payment Enhancements: #

• Added new payment tokens for webhook templates to track when payments are recorded on an account (payments recorded in the LogiSense Billing application)
  • isManual: a Boolean value that defaults to true if the payment was created by a LogiSense user
  • TransactionType: the name of the Transaction Type of the payment
  • createdByUserName: the username of the user who created the payment
• Modified payment related events and added payment transaction types to make working with payment related events simpler:
  • Events Removed:
    • ‘Payment Processed’: This can be now be tracked using the ‘Payment Updated’ or ‘Payment Status Updated’ events
  • Events Added:
    • ‘Payment Created’: New event that fires whenever a payment is created
    • ‘Payment Updated’: New event that fires when a payment entity changes
  • Events Modified:
    • Modified to fire when a payment status is updated and not for any payment entity change
• Added the ability to reverse a processed payment in LogiSense Billing only, without updating the payment record with the payment provider
• Added a Payment Transaction Type field to the Payment screen to indicate the type of transaction that occurred (e.g. was the payment only recorded in LogiSense Billing or was it processed through a payment gateway)

Other Enhancements and Fixes #

• Minor UI fixes
• Billing resiliency improvements
• Widened the quick account search box, removed the Usage Identifier search, and removed the search filter dropdown in order to provide more area to display long account names in the search results. Usage identifiers can now be searched for by loading the account and accessing the Account Search screen
• Increased the size of the account balance pillboxes on the Account Overview screen to prevent large values from overflowing the box
• Modified invoice and credit note templates to support a currency precision value of 0
• Fixed an issue that caused amounts on accounts to be displayed with commas
• Modified the Transactions screen so that the ‘Apply Tax Now’ checkbox is enabled by default
• Fixed an issue that could cause an unexpected API error response when executing an account search
• Fixed an issue on the Transactions screen where an incorrect currency, amount or amount precision could be displayed when viewing reversal taxes related to a child account
• Fixed an issue that could prevent the ability to issue a refund after performing a partial refund
• Fixed an issue when reversing recurring credits that in rare scenarios could cause an incorrect invoice balance and account balance
• Fixed an issue that could cause an incorrect rate to be used when applying account price plan pricing
• Fixed an issue where a pricebook region would still be listed on several account screens after it was removed on the Account Settings screen
• Fixed an issue that caused early contract termination charges not be applied after voiding and rebilling an invoice
• Fixed an invoice generation issue that caused the currency symbol not be displayed when invoice tokens were used within a hierarchy
• Fixed an issue that caused the currency symbol not to be rendered when using the invoice token invoice.invoiceLineItems.invoiceLineItem.price in some scenarios
• Modified usage configuration to allow usage rates to be setup with the same location groups and rate groups provided that the usage class is not the same and dynamic usage classes are not enabled
• Fixed an issue that could cause usage bucket flat charges configured on share plans not to be applied to an invoice when cancelled share plans exist
• Fixed an issue where usage buckets configured with multiple usage tiers and set to share usage across account-packages did not bucket usage beyond the first tier
• Fixed an issue that could cause billing to fail to bill usage in some scenarios when using invoicer level aggregation
• Fixed an issue that could cause a ‘given key not present in the dictionary’ error when billing discounted items
• Fixed an issue that could cause an incorrect price to be set on an invoice item for non-aggregated usage
• Fixed an issue that caused an error when attempting to reverse a tax inclusive recurring credit
• Fixed an issue in AvaTax integrated environments that could cause taxation to fail when multiple refund items related to a single transaction existed and no tax was applicable to the single transaction
• Fixed an issue in AvaTax integrated environments that caused manual transactions with a quantity value to be charged an incorrect tax amount when the transaction was reversed
• Fixed an issue in Adyen integrated environments where importing payments would fail when multiple Adyen payment gateways were configured in LogiSense Billing
• Fixed an issue in Adyen integrated environments that could cause an incorrect precision to be displayed in the Amount field when making a payment
• Fixed an issue that caused month to date data on reports to show prorated values for services configured for full period billing
• Added payment error webhook tokens for the payment updated and payment status updated events
• Modified data export logic to prevent invoice data from being exported if the invoice contains no rows

API Changes #

• API Enhancements:
  • Account/{id}/Detail (Get): fixed an issue that caused an incorrect Contract Address Updated Date to be returned
  • v9/Package/Frequency/{Id}: Fixed an error that would occur when attempting to pass in the serviceTaxCategoryName
  • v9/PaymentMethod/Import/Sync: added a uniqueness check when updating a payment method to allow requests to be made when a payment method token already exists on an account. Note: this may cause the payment method name to change for an existing payment method name in order to enforce uniqueness. This automatic renaming will only occur if a payment method name wasn’t supplied in the request
  • Adjusted API Idempotency response error handling to return an expected API response instead of a 503 error code when a redis update fails
• Updated APIs:
  • v6-v10/Udr/Feed (Get): made public
  • v6-v10/Udr/Feed/[id] (Get): made public
  • v6-v10/Udr/Feed/Paged (Get): made public
  • v10/DataExport (Get): made public
  • v10/DataExport/Paged (Get): made public
  • v10/DataExport/[id] (Get): made public
  • v10/DataExport/{id}/TriggerExport (Post): public bool TransferEmptyExport { get; set; }
  • v10/Payment (Get): added “paymentTransactionTypeId” and “paymentTransactionTypeName”
  • v10/Payment/Reverse/Vendor (Post): added “isInternalRefundOnly” flag
  • v10/Schedule/DataExport (Post): public bool TransferEmptyExport { get; set; }, made public
• New APIs:
  • v10/payment/TransactionType (Get)
  • v10/Tax/Rate/CalculationType (Get)
  • v10/Tax/Rate/CalculationType/{id} (Get)
  • v10/Tax/Rate/CalculationType/Paged (Get)

For additional API documentation please see the API Reference documentation on logisense.com.

10.8.1.3 Release Notes #

Enhancements and Fixes #

• Billing performance and resiliency improvements
• Improved invoice void performance
• Improved performance loading the Usage Rate Groups screen
• Data import performance improvements
• Modified the customer portal login page to load the Large Logo and customer portal Title from the owner configuration settings
• Added the ability to hide the Products and Usage screens in the customer portal
• Added the ability to filter account-packages by AccountPackageStatusType on the Advanced Filter modal
• Modified billing to allow an account already being billed to be billed again in parallel if the initial bill run has reached the delivery stage
• Added a new email token invoice.documentIdentifier which allows a hyperlink to an invoice guid to be included in emails of type ‘Invoice’
• Fixed an issue that caused an incorrect amount to be displayed for tax inclusive credits with a quantity value greater than one
• Fixed an issue where adding a credit would fail in some scenarios when working with a currency configured with more than two decimal places of precision
• Fixed an issue where adding multiple credits or transactions at approximately the same time could result in the credits/transactions not being applied to the account balance
• Fixed an issue where an unexpected API error could occur when attempting to partially reverse a transaction amount with three decimals of precision
• Fixed an issue which prevented a package frequency from being modified if a service attached to the package was configured to be tax inclusive
• Fixed an issue with post paid packages where an extra period could be billed in certain scenarios
• Fixed an issue that could cause a failure to apply early contract termination fees
• Fixed an issue that prevented usage aggregated at the invoicer level from being counted when calculating contract usage commitments
• Fixed an issue where a scheduled bill run could fail to start in rare scenarios
• Fixed an issue where billing could fail during the dunning process if an account had both positive and negative balance invoices and invoicing was also performed on the same bill run
• Fixed an issue that could cause billing to fail and invoice tax summary data to be missing from invoices for some accounts during billing in some scenarios
• Fixed a billing issue where the updated date was not getting set on invoice items when updating the posting date during a retried a bill run
• Fixed an issue where charges for subsequent billing periods were not applied when billing continuous aggregated usage
• Addressed an issue which reduced rating performance when utilizing rate plans configured at the account-service level
• Fixed a ‘given key not present in the dictionary’ error that could occur in some scenarios when billing usage
• Fixed an issue where aggregated usage on a child account rolled up to a parent account could fail to be included when billing usage
• Fixed an issue that could cause usage aggregated at the invoicer level not to be billed
• Fixed an issue where rerating could become stuck when a date/time conversion exception occurred
• Fixed a rating exception that could occur when multiple usage identifiers existed with the same name but different casing
• Fixed an issue that caused a data import failure when a usage identifier name contained a single quote character
• Fixed an issue in Adyen integrated environments where a payment collected during billing was only disbursed to the newly created invoice to which it was attached, instead of older outstanding invoices
• Fixed a webhook issue in Adyen integrated environments where credit card details were not updated when receiving both realtimeAccountUpdaterStatus and recurring payment method details (recurringDetailReference) in the same authorized callback
• Fixed an issue in AvaTax integrated environments where in rare scenarios duplicate invoice items could be generated resulting in taxation failures during invoicing
• Fixed several issues with the revenue modelling report
• Fixed an issue which could prevent the ability to make payments in the customer portal after billing an account

API Changes #

• API Enhancements and Fixes:
  • Fixed an issue where adding an account-package by API and then cancelling it before the account-package’s next bill date could cause the account-package’s start date to be later than its end date
  • Fixed a validation issue that allowed any invoice to be voided by API instead of restricting the void action to only the most recent invoice
• Updated APIs:
  • v10/Account/Package (Post, Put, Patch): In AccountPackageDTO added AccountPackageStatusTypeId { get; set; } and AccountPackageStatusTypeName { get; set; }

For additional API documentation please see the API Reference documentation on logisense.com.

10.8.2.0 Release Notes #

Enhancements and Fixes #

• Added a rate group condition that allows a rate group to be used only if a UDR originating or terminating identifier is found within a particular location group
• Fixed an issue where account-service discounts did not apply within the initial prorated period of an account-package configured for full period billing in some scenarios
• Fixed an issue which permitted duplicate GeoTree locations to be created within a location group
• Fixed an issue in AvaTax integrated environments where tax reversals on negative amount invoice items did not occur after voiding an invoice
• Fixed an issue where contribution overrides on share plans were not calculated properly when an account-service in the plan was configured with both data and event buckets

API Changes #

• Updated APIs:
  • v10/Account/PricePlan/{id}/Detail (Get):
    • In AccountPackageServicePricePlanDTO added int ServiceCategoryId { get; set; } and string ServiceCategoryName { get; set; }
  • Usage/Rate/Group/{id}/Detail (Get):
    • Changes in UsageRateGroupDetailDTO
      • Added ListResultsDTO<UsageRateGroupConditionDTO> RateGroupConditions{ get; set; }
      • Removed ListResultsDTO<UsageRateGroupFilterDTO> RateGroupFilters { get; set; }
    • Added new DTO class UsageRateGroupConditionDTO
      • int UsageRateGroupId { get; set; }
      • string UsageRateGroupName { get; set; }
      • int ConditionFieldTypeId { get; set; }
      • string ConditionFieldTypeName { get; set; }
      • string Value { get; set; }
      • int OperatorTypeId { get; set; }
      • string OperatorTypeName { get; set; }
  • Usage/Rate/Group (Post, Put, Patch, Delete):
    • Changes in UsageRateGroupDetailDTO
      • Added ListResultsDTO<UsageRateGroupConditionDTO> RateGroupConditions{ get; set; }
      • Removed ListResultsDTO<UsageRateGroupFilterDTO> RateGroupFilters { get; set; }
    • Added new DTO class UsageRateGroupConditionDTO
      • int UsageRateGroupId { get; set; }
      • string UsageRateGroupName { get; set; }
      • int ConditionFieldTypeId { get; set; }
      • string ConditionFieldTypeName { get; set; }
      • string Value { get; set; }
      • int OperatorTypeId { get; set; }
      • string OperatorTypeName { get; set; }
  • Usage/Class (Get, Post, Put, Patch): added int UsageClassResolverTypeId { get; set; }
  • Usage/Class (Get, Post, Patch):
    • Added UsageClassDetailDTO Details { get; set; }
    • Details: UsageClassLocationGroupResolverSettingDTO UsageClassLocationGroupResolverSettings { get; set; }
  • Owner (Get, Post, Patch): added bool UsageClassResolverIsActive { get; set; }
• New APIs:
  • Account/PricePlan/{accountPricePlanId}/CustomizeLocationGroup (Post)
  • AccountPricePlan/PackageServicePricePlan/[id]/LocationGroupOverrides (Post)
  • Account/PricePlan/PackageServicePricePlan/{packageServicePricePlanId}/LocationGroupOverride/Search (Post)
  • AccountPricePlan/PackageServicePricePlan/{packageServicePricePlanId}/LocationGroup/{geoTreeLocationGroupId} (Get, Patch)
  • AccountPricePlan/PackageServicePricePlan/[id]/LocationGroupOverrides (Patch)
  • Usage/Rate/Group/ConditionFieldType (Get)

For additional API documentation please see the API Reference documentation on logisense.com.

10.8.2.1 Release Notes #

Enhancements and Fixes #

• Zone based rating:
  • Added an ‘Enable Usage Class Resolver’ setting on owners. When this setting is enabled it will be possible to configure classes in the system to resolve to a different usage class based upon the relationship of the UDR Originating and Terminating Identifiers within the GeoTree Location Groups. The resolved class will then be used to calculate the rate to apply
• Location Groups can now be customized at the Account Price Plan Package level
• Fixed an issue that could cause pooling and non-pooling buckets to be treated as a single shared bucket

10.8.3.0 Release Notes #

Release Date: July 11, 2025

Change Highlights #

• Added the ability to customize account share plan participation and contributions by product code
• Modified formatting when importing data from CSV files into LogiSense Billing
  • Parsing rules follow iaw https://www.ietf.org/rfc/rfc4180.txt
  • Exceptions include:
    • Line breaks within fields (even when enclosed with double-quotes) are not supported
    • CSV files with leading/trailing whitespace are not supported
    • Recommended: Fields containing double quotes should be enclosed in double-quotes

Enhancements and Fixes #

• Improved performance loading account price plan data
• Improved performance loading data on the Account Packages screen
• Modified contact addresses to support up to 255 characters
• Added two new fields to UsageRated: ‘Originating_GeoTreeLocationGroupID’ and ‘Originating_GeoTreeLocationID’. These values track the originating identifier’s location group and location based on the location data that was used during rate selection
• Fixed an issue with the search feature which caused custom field values to be indexed only up to 30 characters, which could result in a failure to return relevant accounts in search results
• Fixed an issue that could cause an unexpected API response error when attempting to load account data
• Fixed an issue that could cause an invoice to fail to be voided properly in rare scenarios
• Fixed an issue that could cause usage billing to fail in some scenarios when billing usage aggregated at the invoicer level
• Fixed an issue where billing could fail during invoice rendering in some scenarios when attempting to bill usage aggregated at the invoicer level
• Fixed an issue that could halt usage billing processing and return a usage exception in some scenarios while billing usage related to multiple tiered rate overrides in a single rate plan configured on an account price plan
• Fixed issues where voiding an invoice with tens of thousands of invoice items or thousands of recurring charges could cause the void operation to fail in error
• Fixed an issue that prevented a price tier threshold from being re-added if it was deleted
• Fixed an issue that could prevent tier deletion and rate overrides from being saved when modifying account price plans
• Fixed an issue with account price plans that prevented usage rate plan overrides from being configured when the account price plan was created by API
• Fixed a validation issue that permitted the same product code to be configured on multiple package frequencies in an account price plan
• Fixed an issue where rating could fail to find a rate group when the rate group was configured with conditions set on the usage class, usage class type and UDR identifier type
• Fixed a caching issue that could result in stale data being displayed for location groups, rate plans and rate groups in some scenarios
• Fixed a rating performance issue introduced in version 10.8.2.1 that impacted systems configured to use zone based rating
• Fixed an issue where modifying the Rater value of a Class resulted in an error when attempting to save the change
• Fixed an issue when importing non-usage based data that could cause the import process to stall without error when importing data that contained double quotes which were not properly escaped
• Fixed an issue that could cause the revenue modelling report to fail to run

API Changes #

• Updated APIs:
  • v10/Account/SharePlan (Get): Added to AccountSharePlanDTO
    • int SharePlanTypeId { get; set; }
    • string SharePlanTypeName { get; set; }
    • int SellingServiceId { get; set; }
    • string SellingServiceName { get; set; }
    • int SharePlanUsageFrequency { get; set; }
    • int SharePlanUsageFrequencyTypeId { get; set; }
    • string SharePlanUsageFrequencyTypeName { get; set; }
    • DateTime LastBilled { get; set; }
    • DateTime LastUsageBilled { get; set; }
    • int PriceBookId { get; set; }
    • string PriceBookName { get; set; }
  • Owner (Get, Post, Patch): Added to OwnerDTO
    • bool AccountSharePlanProductCodeCustomizationIsActive { get; set; }
  • Account/SharePlan/Participation (Get): Added to AccountSharePlanParticipationDTO
    • int AccountProductCodeId { get; set; }
    • string AccountProductCodeName { get; set; }
  • Account/SharePlan/{id}/Detail (Get, Post, Patch, Delete): Added to AccountSharePlanParticipationDTO
    • int AccountProductCodeId { get; set; }
    • string AccountProductCodeName { get; set; }
• New APIs:
  • v10/Account/SharePlan/{id}/AddOn (Get, Patch)
  • v10/Account/SharePlan/{id}/ProductCode (Post)
  • v10/Account/SharePlan/{id}/ProductCode/{productCode} (Get, Patch, Delete)
  • v10/Account/SharePlan/{id}/AttachedProductCode (Get)
  • v10/Account/SharePlan/{id}/AvailableFor/ProductCode (Get)

For additional API documentation please see the API Reference documentation on logisense.com.

10.8.3.1 Release Notes #

Release Date: July 30, 2025

• Modified several Service drop downs fields on account screens to be wider or wrap long service names across two lines
• Modified the invoice item price to reflect the usage rate used by billing for account-service usage charges instead of displaying the default base price
• Improved error handling when data import issues occur
• Improved rating service exception handling in scenarios that can cause duplicate records to be created
• Modified product code names to support entirely numeric values as well as the . and ~ characters
• Modified share plan validation rules to permit participation and contribution levels to be set to zero when creating a share plan bucket
• Fixed an issue where a discount might not be applied to the correct period when an account-package was configured for full period billing and the account-package’s start date and the discount’s start date were different
• Fixed an issue where splitting a share plan into separate pools using a product code could result in an unlimited participation limit
• Fixed an issue where canceling an account-package would not trigger rerating when the account-package had no usage elements but was contributing to a share plan
• Fixed an Okta SSO integration issue that would cause a group of users not to be linked to any role groups in LogiSense Billing after unlinking, deleting and relinking a group in the Okta portal
• Fixed an issue where canceling an account-package with a backdated date could cause invalid data in revenue modeling reports in some scenarios
• Fixed an issue that allowed account price plan rate overrides to be configured by API even when no rate plan was configured within the service details of a package frequency
• Fixed an issue with the Usage/Class/{id} API which prevented updates from being made using the Put method
• Fixed an issue where creating an account-package using the Account/Package/FromCatalog API could fail in error when using a product code configured with a discount in some scenarios

10.8.3.2 Release Notes #

Release Date: Aug 21, 2025

• Rating and rerating performance improvements
• Event Service improvements to reduce memory consumption
• Improved performance activating share plans that share at the package level by having the event service bulk load daily thresholds
• Removed the validation that prevented a contributing amount in a share plan being set to zero
• Added validation to ensure that when adding or updating a package in a price plan that the rate plan set on the package matches the catalog package rate plan
• Modified billing to ignore unbilled usage from a previously billed period if the usage is being billed using a high watermark calculation. Usage in this scenario will be marked as billed but will not be charged
• Fixed an issue that could cause an unexpected API response error to appear when searching for an account share plan
• Fixed an issue where billing could get stuck at the invoice rendering step in some scenarios if an invoice generated by a sales order was voided
• Fixed an issue that could cause usage billing to be skipped for the incorrect invoicer accounts in scenarios where billing is filtering out non-related records when collecting invoicer aggregate records
• Fixed an issue that could cause a database timeout to occur when billing usage
• Fixed an issue where the data export service would not observe the command timeout configured

10.8.3.3 Release Notes #

Release Date: Sept 25, 2025

• Rerating resiliency and performance improvements
• Improved performance voiding invoices
• Fixed an issue that could prevent custom fields from being deleted in some scenarios
• Fixed an issue that prevented account price plan usage rate overrides from being configured in the AdminPortal
• Fixed an issue where E911 / Telecom Relay taxes were being capped at the sub account level instead of the invoicer level
• Fixed an issue where usage billing charges for non-tiered rates were incorrect when rerating usage related to a rate override on an account price plan

10.8.3.4 Release Notes #

Release Date: Sept 30, 2025

• Rating performance improvements
• Fixed an issue with product code level discounts failing to discount charges for the first month when the discount was configured to prorate
• Fixed an issue where incorrect charges for tiered progressive counts were generated when account-packages with different product codes were billed

10.8.3.5 Release Notes #

Release Date: Oct 2, 2025

• Fixed a permissions issue that prevented users from being able to access the Edit Location Configuration options under the product code section of the account Price Plan screen
• Fixed an issue where additional monthly recurring charges could be applied for past billing periods when billing account-packages configured with the ‘Charge Recurring Only if Usage’ option

10.8.3.5 Build 7 Additions #

Release Date: Oct 16, 2025

• Fixed an issue that caused manual charges/credits to be re-applied after voiding an invoice that contained charges for more than a thousand account-packages
• Fixed an issue that caused a usage billing exception in scenarios where a share plan selling package was cancelled, billing was executed, the generated invoice was voided and billing was executed again
• Fixed an issue where voiding an invoice that included more than a thousand account-packages spread across multiple sub-accounts could cause the void operation to fail to fully complete

10.8.3.6 Release Notes #

Release Date: Nov 26, 2025

• Rerating performance and resiliency improvements
• Modified billing to permit a bill run to start even if accounts being billed have pending rerates scheduled, provided the bill run isn’t configured to bill subscription or usage charges
• Modified rounding behavior to perform carryforward rounding on taxes applied to invoice items for tax exclusive invoice items only. Rounding will observe the precision set on the invoicer account’s currency. Tax inclusive invoice items and their taxes will not have carryforward rounding applied to them. This change will align tax amounts in tax vendor portals to the sum of invoice item taxes in LogiSense Billing
• Fixed an issue where an unexpected API error response would occur when trying to configure advanced filters on the Account Share Plans screen
• Fixed an issue where account-services did not have their usage next bill dates rolled back after voiding an invoice in scenarios where billing had only applied recurring charges or only applied usage charges
• Fixed a rerating issue that allowed rerating to be executed when an account was already scheduled to be rerated
• Fixed a rerating issue where the rerate start date could be set incorrectly when multiple rerates of different accounts were all rerated using a single rerate schedule

10.8.4.0 Release Notes #

Release Date: Aug 27, 2025

Change Highlights #

• Adyen Integration Enhancements:
  • Chargebacks will now bet set to captured status instead of pending refund, provided the total refund and chargeback amount is less than or equal to the original amount. Captured chargebacks will immediately be applied to the account balance
  • Chargebacks for direct debit payment methods will automatically disable the payment method to prevent subsequent payment collection attempts
  • A ‘Deactivation Reason’ field has been added to the Account / Settings / Payment Method screen. This field can be populated by a user or populated with a deactivation reason provided by Adyen
  • Modified Adyen integration so that pending payments will no longer be attached to an invoice when they are generated during a bill run. Captured payments will still be attached to invoices, pending payments will be attached to the next invoice once they are moved to a captured state

Enhancements and Fixes #

• Added a new bill run status called ‘Scheduled Pending Void’. This status will be displayed when a bill run detects an account to be billed that is currently executing a void operation. When the void operation is complete the bill run schedule will resume
• Added a ‘Do Not Email If Invoice contains only $0 charges’ setting to the Invoice Delivery screen. When enabled invoices will not be emailed if the invoice contains only $0 charges on it
• Modified the currency precision on invoices to observe the system currency precision instead of the locale precision. Precision overrides on the invoice template itself will still take precedence
• Modified the PaymentType event token for emails and webhooks to return the proper payment type of the payment (check, cash, adyen visa)
• A new PaymentBaseType event token has been added for emails and webhooks that use the payment token context. This token will return the base type of the payment (cash, credit card, direct debit, wallet)
• Added Idempotency config options to control caching behavior
• Report generation performance improvements
• Improved performance loading share plan data in the product catalog
• Improved performance loading share plan data when viewing account-service information
• Fixed an issue with account share plans where the Edit Tiered Charges UI would fail to display tiers and amounts in some scenarios
• Fixed an issue with account share plans where changes made in the Edit Tiered Charges UI could not be saved in some scenarios
• Fixed an issue that prevented payment disbursement if an undisbursed payment existed and it had a rejected refund against it
• Fixed an issue where an account-service could be incorrectly charged if the account-service’s status was modified within an already billed period
• Fixed an issue where searching for an exact match of a custom field value on an account-package would fail if the custom field value exceeded 800 characters
• Fixed an issue that could cause the detail value of an invoice item to be incorrect for discount charges
• Fixed an issue where a bill run could stall when attempting to bill cancelled accounts
• Fixed an issue that could cause payments to be collected for invoices that are not yet due
• Fixed an issue where postpaid account-packages with backdated cancellation dates might not be billed during a bill run in some scenarios
• Fixed an issue where the data export service would not observe the command timeout configured
• Fixed a report generation issue where reports where being truncated using the default max report size value instead of the user configured maximum

API Changes #

• Updated APIs:
  • v10/Invoice (Get): Added to: InvoiceDTO – EmailDeliverySkipped { get; set; }
  • v10/Invoice/Delivery (Get, Post, Patch): Added to: InvoiceDeliveryDTO – DoNotEmailZeroChargeInvoice { get; set; }
  • v10/PaymentMethod (Get, Post, Put): Added to: PaymentMethodDTO – DeactivationReasonTypeName { get; set; }
  • v10/Json API / Log (Get): Fixed an issue where an error would occur when attempting to look up entries using a valid requestTrackingId
  • v10/Payment/Method/Import/Sync (Post): Changed the response to return a 500-series error instead of the current 400-series response when a communications error occurs with Adyen
  • v10/Usage/Bucket/Base (Patch): Modified patch operation to support updating a usage bucket name and usage bucket class in a single call
  • v10/Usage/Bucket/SharePlan (Post): Fixed an issue that would cause an incorrect error message to appear if the payload contained errors
• New APIs:
  • v10/Account/{id}/PriceBookRegion (Get)

10.8.5.0 Release Notes #

Release Date: Jan 19, 2026

Change Highlights #

• New Percentage Off of Base Price Tiered Pricing Option:
  • This pricing option takes the base price per price book and currency and allows tiers to be setup offering a percentage discount of the base price
  • Supported with both bracketed and progressive tiers
  • Bracketed thresholds and percentages can be customized on account price plans
  • Bracketed and progressive thresholds and percentages can be customized at the account-package level as well
  • Added invoice tokens permit the discount and percentage to be displayed on invoices
• Catalog and Pricing Enhancements:
  • Added the ability to change the Tier Type or Counting Rule for package frequencies that are in use as of a scheduled date using the Price Change API
  • Modifying a counting rule will now trigger a recount when a counting rule is created or changed. If a counting rule or its service/package mappings are changed then the count will be recalculated across all affected accounts
  • Existing account-packages will continue to observe any price overrides set when tier type or counting rule changes are made with the Price Change API
  • Moved the Counting Rule from the top section of the Package Frequency screen and replaced it with a ‘Default Counting Rule’. The default will be used for new Services or Statuses
  • Tier Types, Tier Pricing and Counting Rules are now visible and applicable per Service and Status for each price book and currency

Enhancements and Fixes #

• Billing performance and resiliency improvements
• Improved performance loading report history data on report screens
• Reduced memory consumption when generating PDFs
• Added the ability to resize the left hand side list on heavily used account and setup screens
• Account-contract cancellation is now scheduled in advance or backdated, both through the AdminPortal or by API. Account-contracts can no longer be set to cancelled by the user, the system handles cancellation when the scheduled date is reached
• Added support for EPS and Bancontact card payments in Adyen integrated environments
• Added support for Bancontact mobile payments in Adyen integrated environments
• Added support for five new Adyen wallet payment methods: Dana, GoPay, GCash, Kakao Pay, MoMo
• Modified callback handling in Adyen integrated environments to process ‘Transaction Recaptured’ events
• Expanded webhook handling in Adyen integrated environments to support processing callbacks for payments imported into LogiSense Billing
• Modified Adyen integration to no longer set a payment to rejected or create a payment transaction error if an API call to Adyen times out. Instead payments will remain in a pending state until a response from Adyen indicates if they are captured or rejected
• Added support for Stripe credit card payments in Spreedly integrated environments
• Modified Invoices screen to enable the ability to deliver invoices that are in a ‘delivery failed’ state
• Modified rating to trigger a rerate scheduled back to the earliest unbilled usage date when a usage rate override value is changed within an account price plan
• Modified billing delta export to exclude un-invoiced manual transactions, credits and any related tax records
• Modified the report generator to limit failed retries to ten attempts. After the tenth failure an error will be logged and a failure notification will be sent
• Added text to the cancellation date fields related to account-packages and account-services to explain that the cancellation dates are exclusive, and charges will not be generated for the cancellation day
• Fixed an issue where changing the price for one particular service status within an account-package could result in incorrect price being set for that service status
• Fixed an issue where an unexpected API error response could occur when attempting to filter against an ID value
• Fixed an issue on the Account Packages screen where the Usage identifiers filter could not be used without refreshing the screen
• Fixed an issue that allowed account-service status changes to be backdated for more than one period after billing had already occurred
• Fixed several issues that prevented or allowed read only users to access screens, buttons and filters
• Fixed an issue on the Credits screen where a newly created credit would not be displayed in some scenarios
• Fixed an issue that could prevent a sales order from being completed and billed, returning the error ‘Nullable object must have a value’
• Fixed an issue that could prevent a sales order from being completed and billed, returning the error ‘The number of ‘accountPackage’ ‘attributes’ provided must equal the ‘accountPackage’ ‘quantity’
• Fixed an issue where a parent account could display a manual credit amount from a sub-account without currency conversion being applied
• Fixed an issue where tax exemptions setup on an invoicer account did to get applied to sub-accounts when the sub-account was configured with its own address
• Fixed an issue where an invoicer account’s tax exemption settings could override exceptions set on a sub-account
• Fixed an issue where voiding an invoice that contained a credit reversal would result in an account balance that did not factor in the reversal credit amount
• Fixed an issue where custom invoice fonts were not being rendered properly on invoices
• Fixed a contract termination issue where the percentage of remaining commitments charge could be calculated incorrectly
• Fixed an issue with cancelled account contracts where the commitments were still being evaluating after contract cancellation
• Fixed an issue where a contract’s start date could be modified after a period under commitment was billed
• Fixed an issue where the percentage of remaining commitments penalty was not charged when terminating a contract early
• Fixed an issue with contracts where the Termination Date and Comments fields were not displayed when the termination date exceeded the current date
• Fixed an issue where account-package cancellation would fail in error when more than two thousand share plan services are setup in the system
• Fixed an issue where tiered charges set to be deleted were not being deleted after saving changes to tiered charges on an account price plan
• Fixed an issue that prevented a price override from being created on a price plan in the AdminPortal after a pricing change was made
• Fixed an issue with account price plans that could prevent pricing updates from being applied
• Fixed an issue where using the Forget Account feature caused address information to be erased for other accounts that were configured using the same price book region
• Fixed an issue which could cause pricing not to be displayed on the Edit Package Frequency screen when two or more currencies were configured on a package and the default currency was not in USD
• Fixed an issue that did not allow tiered pricing to be saved on a package frequency when the first tier was configured with a zero dollar price
• Fixed an issue that could prevent service details from being added on an existing package frequency using a standard or custom price book
• Fixed an issue that could cause taxes not to be applied when usage charges configured to aggregate at the invoicer level were calculated
• Fixed issues with cloning rate groups where rates and aggregated configuration settings were not being copied to the cloned group
• Fixed an issue on the Payment Gateways screen which prevented unassigned countries from being displayed when filtering merchant accounts
• Fixed an issue where disbursements were not being removed after manually changing the status of a pending refund to ‘Captured’
• Fixed an issue when setting up an Adyen payment gateway where an incorrect AuthUserId would be automatically set, requiring the callback user id to be manually re-selected in the list before the gateway configuration could be saved
• Fixed an issue in Adyen integrated environments where a captured payment could be switched to rejected and still be disbursed
• Fixed an issue with deleting rating exceptions in the AdminPortal which could cause inaccurate exception totals
• Fixed an issue that could cause out of scope date range errors during rating leading to rating failures and usage exceptions
• Fixed an issue where revenue modeling data would display recurring revenue after the cancellation period of an account-package
• Fixed an issue with the report generator which could cause the bill run delivery step to become stalled
• Fixed an issue that prevented webhook requests from being sent for the Invoice Posted and Invoice Delivered events
• Fixed a data export issue that could cause attachments not to be included on delivered emails
• Fixed an issue where custom field changes were not being shown in the audit log until subsequent custom field changes were made

API Changes #

• Updated APIs:
  • v10/AccountSharePlan/[id]/AddOn (Get, Post, Patch): Added support to retrieve, update and add the new percentage based tier charge type
  • v10/Account/Package (Get, Post, Patch): Added support to retrieve, update and add the new percentage based tier charge type
  • v10/Invoice/Item (Get): Added support to retrieve the percentage discount value of the new percentage based tier charge type
  • v10/Invoice/Item/TaxSummary (Get): Added support to retrieve the percentage discount value of the new percentage based tier charge type
  • v10/Invoice (Get): Added support to retrieve the percentage discount value of the new percentage based tier charge type
  • v10/Account/Package/FromCatalog (Post): If the new TierChargeTypeId is not provided in the request, the catalog value will be is used
  • v10/Package/Frequency (Post): Added support to add the new percentage based tier charge type
  • v10/Package/Frequency/[id]/Pricebook/[id]/Currency/[id]/Pricing (Get): Added support to retrieve the new percentage based tier charge type and added counting rule configuration as it is no longer set on the package-frequency
  • v10/Account/PricePlan (Post, Patch): Added support to retrieve the new percentage based tier charge type and added counting rule configuration as it is no longer set on the package-frequency
  • v10/Account/PricePlan/[id]/PackageServicePricePlan/[id]/Pricing (Get): Added support to retrieve the new percentage based tier charge type and added counting rule configuration as it is no longer set on the package-frequency
  • v10/PackageFrequency/[id] (Get, Post, Patch): Added DefaultCountingRule settings on package-frequencies for backward compatibility. If DefaultCountingRule values are set on the package-frequency then those values will be copied over to the new counting rule configuration location under PackageServiceTieredPricing
  • v10/Package/[id]/Detail (Get): Added DefaultCountingRule settings on package-frequencies for backward compatibility. If DefaultCountingRule values are set on the package-frequency then those values will be copied over to the new counting rule configuration location under PackageServiceTieredPricing
  • v10/PriceChange (Get, Post, Patch): The Tier Type or Counting Rule of a package-frequency can now be changed as of a specified date, even when the package-frequency is already in use (account-packages exist). Note: switching package-frequencies to progressive pricing is not supported at this time
• New APIs:
  • v10/Account/Contract/{ID}/EarlyTermination (Put, Delete): Put allows an EarlyTermination date to be set with the options to add an EarlyTerminationComment and or a Termination_AccountContractStatusTypeID. Delete clears the EarlyTermination date and EarlyTerminationComment fields on the AccountContract
  • v10/DataExport/History/{id} (Get): Returns data export history details for the specified ID
  • v10/DataExport/History/Paged (Get): Returns data export history details in a paged list
  • v10/DataExport/History/[dataExportHistoryID]/Download (Get): Takes a dataExportHistoryID representing a specific generated export file and returns data for the file from the DataExportHistory table, including the AWS S3 location. DataExport/Trigger returns the DataExportHistoryID so that should be used when fetching the download. The user (API or integration) can then use the returned S3 link to download the file and save it in the required location
  • v10/BillRun/History/[id]/DataExport (Get): Takes a dataExportHistoryID representing a specific generated export file and returns data for the file from the DataExportHistory table, including the AWS S3 location. DataExport/Trigger returns the DataExportHistoryID so that should be used when fetching the download. The user (API or integration) can then use the returned S3 link to download the file and save it in the required location
  • v10/TierChargeType (Get): Allows the charge types configured on pricing tiers to be retrieved (‘Fixed Amount’ or ‘Percentage Off of Base Price’). As of 10.8.5.0 a new percentage based tier type has been introduced which allows a base price to be defined along with percentage discounts per each tier
  • v10/Account/SimulatePackageBilling (Post): Simulates billing charges that would be created on an account if a limited number of account-packages were cancelled or added (maximum of ten). The API response will contain the invoice items that would be created for the account-packages in the next bill run as well as the total amount
  • v10/PaymentGateway (Get): Retrieve all of the PaymentGateway objects
  • v10/PaymentGateway/Paged (Get): Retrieve all of the PaymentGateway objects in a paged fashion
  • v10/PaymentGateway/[id] (Get): Retrieve an instance of the PaymentGateway object by its ID
  • v10/PaymentGateway/[id]/Detail (Get): Retrieve deep detail of the PaymentGateway object by its ID
  • v10/Adyen/MerchantAccount/PaymentGateway/[paymentGatewayId] (Get): Retrieve all of the AdyenMerchantAccount objects
  • v10/Adyen/MerchantAccount/PaymentGateway/{paymentGatewayId}/Sync (Post): Create a new instance of the AdyenMerchantAccount object
• API Enhancements and Fixes:
  • Account/Contract/[id] (Patch): Fixed an issue where it was possible to update an account-contract to Cancelled status (billing handles this task when evaluating contract cancellation dates)
  • Account/Package/FromCatalog (Post): fixed an issue that allowed the same usage identifiers to be added to multiple account-services
  • Package/Service/PricePlan/[id] (Patch): fixed an issue where attempting to update a service tax category ID would fail and return the error ‘Object Reference not set to an instance of an object’
  • PaymentMethod (Put): fixed an issue where the request would fail if deactivationReasonTypeName was passed as an update request filter
  • PriceChange/[id]/Pricing/Paged/Detail (Get): fixed an issue which caused duplicate items to be returned in the response
  • PriceChange/[id]/Pricing/Paged/Detail (Get): fixed incorrect response provided when no matches were found

10.8.5.2 Release Notes #

Release Date: April 14, 2026

EN-33160
Improved Adyen payment update handling so completed payments are no longer incorrectly changed to a rejected status when delayed gateway responses are received. This resolves a case where late payment updates could overwrite the correct final payment result.

EN-33231
Fixed an issue that could prevent users from updating a usage identifier on a service, even when the change should have been allowed. This resolves validation errors that were blocking legitimate service updates.

EN-33332
Resolved an issue where some payment error events were not always processed correctly, improving reliability of downstream payment-related notifications and actions. This ensures payment error records are handled more consistently during higher-volume processing.

EN-33392
Fixed a tax handling issue so manually created and reversed transactions in the same month now update Avalara correctly. This resolves cases where tax commitments were not being properly cleared after a reversal.

EN-33493
Added support for automatically creating reversal payment transactions when conflicting payment status updates are received, improving payment accuracy and reducing manual correction work. This resolves situations where payment records could otherwise be left out of sync with the gateway outcome.

EN-33529
Fixed an issue that could prevent the system from creating an Adyen payment method through the Payment Session API. This resolves failures during payment setup that could interrupt the payment method creation process.

EN-33570
Added support for a missing payment transaction type needed for gateway reconciliation scenarios. This resolves a gap that prevented certain reconciliation-related payment activity from being recorded correctly.

EN-33571
Improved handling of a specific Adyen authorization response so manually captured payments are no longer disrupted by that callback scenario. This resolves an edge case where a later gateway message could interfere with an already completed payment flow.

EN-33622
Fixed an issue where some gateway reconciliation payments could be created without a transaction ID, improving payment traceability and consistency. This resolves missing reference information needed to properly track and audit those payments.

10.8.5.3 Release Notes #

Release Date: Aug 18, 2026

EN-30162
Added support for associating an imported Adyen payment with an existing active account payment method. This allows payment receipts to include details such as the card type and last four digits while ensuring the payment method belongs to the account and matches the payment type reported by Adyen.

LB-180
Added created and updated timestamps to payment and credit invoice disbursements, improving aged balance reporting and invoice payment tracking. Disbursements now use soft deletion so deleted records are retained for auditing while being excluded from account and invoice balance calculations.

10.8.6.0 Release Notes #

Release Date: May 6, 2026

Release Highlights #

EN-28933, EN-30375
High Watermark Rates – Changes in Bucketing/Entitlements to Apply only to the Chargeable Usage Value based on a high watermark evaluation. This update ensures that peak usage pricing is calculated only on billable activity, helping prevent overcharges and improving confidence in invoice accuracy.

Fair and Consistent Peak Usage Calculations Across Subaccounts. This change ensures peak usage pricing is applied fairly across subaccounts while still providing an accurate total at the master account level.

EN-31715, EN-31714, EN-31716, EN-31717
Improved Tiered Usage Pricing Calculations. This enhancement improves how usage is grouped into pricing tiers so customers are charged correctly as their consumption increases. Accurate Handling of Custom Tiered Pricing Agreements. This update ensures that custom pricing agreements are honored accurately when calculating tiered usage charges.

EN-32931
Greater Transparency in Tiered Usage Reporting. This feature provides clearer invoice reporting by showing how usage was calculated within each pricing tier, making charges easier to understand.

EN-32941
Stronger Safeguards to Prevent Incorrect Usage Charges. This update adds safeguards to prevent incorrect charges by flagging usage that does not meet pricing rules for review before billing.

EN-29478
Greater Flexibility in Customer-Specific Usage Pricing. This feature allows greater flexibility in how usage pricing is defined for specific customers, making it easier to match billing to contract terms.

EN-31970
Automatic Recalculation When Pricing Dates Change. This enhancement automatically updates charges when pricing dates change, helping ensure invoices always reflect the correct timeframe.

Fixed In This Release #

EN-33078
Resolved Account Package Import Issue. This update corrects an issue that prevented certain account packages from being imported successfully, improving setup reliability.

EN-32218
Improved Billing Error Handling. This update strengthens system validation to prevent billing interruptions when key billing dates are missing.

EN-31428
Resolved Usage Bucket API Creation Error. This fix ensures newly created usage buckets can be referenced immediately without triggering validation errors.

EN-32919
Improved Validation When Updating Usage Tiers via API. This fix prevents incorrect validation errors when modifying usage unit settings.

EN-32620
Resolved Bill Run Scheduling Delay. This fix corrects an issue that could cause bill runs to remain pending due to unscheduled rerating events.

EN-32086
Improved Search Filtering in Rate Setup Screen. This fix ensures search results display correctly across all pages, improving usability.

EN-32350
Improved API Error Messaging for Subaccount Updates. This update provides clearer validation responses when updating subaccount details.

EN-32030
Resolved Early Termination Penalty Handling After Contract Closure. This fix ensures penalties cannot be modified after a contract is cancelled or expired.

EN-32825
Improved Share Plan Date Protection After Cancellation. This update prevents changes to share plan dates once a related package has been cancelled.

EN-32160
Improved Bill Group Page Performance. This update reduces page load times by optimizing background data calls.

EN-32994
Improved Month-to-Date Reporting Accuracy. This update ensures non-billable data is excluded from reporting totals.

EN-32032
Enhanced Flexibility for Usage Commitments. This fix restores the ability to configure commitments across different usage unit types.

EN-32776
Improved Audit Logging for Account Hierarchy Changes. This update ensures parent account changes are properly captured and displayed.

EN-32154
Improved Tiered Usage Billing Performance. This enhancement optimizes system indexing to improve performance during tiered billing operations.

EN-32821
Resolved Share Plan Cancellation Alignment Issue. This fix ensures related services and plans are properly cancelled together to prevent billing failures.

EN-32833
Improved Invoice Item Count Accuracy. This fix ensures flat bucket charges are correctly accounted for during invoice processing.

EN-33203
Improved Read-Only Field Behavior in Usage Buckets. This update ensures read-only settings cannot be modified in the interface.

EN-33213
Improved Visual Feedback in Service Type Setup. This fix resolves a display issue to ensure screen highlights update correctly after saving.

EN-30321
Corrected Aggregate Usage Charge Calculations. This update resolves inconsistencies in how maximum aggregate rates are applied across related accounts.

EN-32741
Corrected Contract Termination Penalty Calculation. This update ensures remaining commitment penalties are applied accurately after termination.

EN-32953
Improved Tiered Pricing Update Validation. This fix ensures pricing thresholds can be updated without triggering duplicate key errors.

EN-30317
Corrected Usage and Charge Totals After Void and Rerate. This fix resolves discrepancies that could occur after adjustments and rebilling.

For information on any API Changes please see the change log in the Developer Documentation.

10.8.6.1 Release Notes #

Release Date: June 10, 2026

Release Highlights #

EN-32608, EN-33441

Reduced Unnecessary Rerating for Account Package and Share Plan Changes. This release improves rerate decision logic for account package additions and cancellations. Share plan overage checks now compare bucket consumption against bucket size instead of relying on last-tier remaining values, which avoids false positives in participation-limit scenarios. The rerating flow also avoids rerates caused by zero-value flat charges and clears account-scoped rating and usage caches when the same account is rerated more than once in a session.

EN-33456

Invoice Adjustment Hook. 10.8.6.1 adds a reusable invoice-stage adjustment hook that can create invoice adjustment items after invoice item batching and before invoice-level tax and finalization. The platform owns persistence, currency conversion, rounding, tax participation, and idempotency handling for these adjustment items, with guardrails in place to prevent unexpectedly large adjustment batches.

Fixed In This Release #

Billing, Invoicing, and Rendering

EN-33219, EN-34054

Improved Bill Run Completion and Usage Billing Performance. Billing and rendering workflows were updated to reduce timeout and stuck-step risk for large bill runs. Usage billing account-service selection now prefilters candidate account services before checking dirty usage consistency records, improving query plans for large accounts. Rendering pagination was also updated to avoid redundant count queries and to terminate based on actual page size.

EN-32803

Protected Catalog Pricing When Updating Account Product Code MRC. Updating MRC pricing for an account product code now creates or updates account-level pricing when no package service recurring price override exists, instead of modifying catalog-level recurring pricing.

Rerating, Usage, and Messaging

EN-33780, EN-33795

Improved Usage Pipeline and Messaging Resilience. Usage processing now recovers more cleanly when high-volume jobs encounter interruptions or temporary slowdowns. This reduces the chance of follow-on processing errors and helps keep rating and rerating work moving reliably.

Account Packages, Share Plans, and Search

EN-34056

Stronger Account Package Cancellation Validation. Account package cancellation updates now validate the full effective range for duplicate usage identifier conflicts. This prevents cancellation removal in cases where a usage identifier has already been reassigned to another account package service.

EN-32517

Faster Account Share Plan Filter Searches. Account share plan search dropdown filtering was updated to use startsWith matching instead of contains matching. This narrows large account package searches and improves response time when adding advanced filter conditions.