...
In this article:
10.4.0 Release Notes
Change Highlights
...
Rating performance improvements
Manual Transactions can now be added with an amount up to 11 digits of decimal precision. Amounts will still be rounded to 2 decimal places on the Invoice
Fixed an issue where usage could go unbilled if an account-package was cancelled after the first usage billing period and billing was executed after the cancellation but before the second billing period
Modified logic to create an invoice item when any amount of usage is billed regardless of the value (e.g. when the usage is fully bucketed). Previously these usage charges were set as no charge invoice items and excluded from the invoice
Fixed an issue where an invoice would fail to generate if an account contained tax reversal transactions and the system was setup to use the local LogiSense tax vendor
For customers using AvaTax for Communications, manual transactions recorded against a Service with a Service Tax Category based on Lines can support a quantity of up to 500,000. All other transactions are still limited to a quantity of 10,000
Fixed an AvaTax integration issue where incorrect taxes were applied when a credit or negative transaction was added with a quantity value greater than one
Modified AvaTax integration to removed the '-' from the list of special characters that are padded by default when making a GeoTree lookup as this was causing an incorrect tax jurisdiction code to be assigned
Fixed an issue where rating would fail to find a rate group when rate group conditions existed and those conditions referenced a custom mediation field with a name that began with a lower case character
Fixed a mediation issue where in rare cases the mediation process would fail when highly concurrent operations were executing
Fixed an issue that could database connections to be become blocked in some scenarios
Fixed issues that could cause data loss when archiving data to an S3 bucket
File Importer performance and resiliency improvements
10.4.2-Patch.2 Release Notes
Fixed an issue that could cause the MessageCollector service to fail to collect queued messages until the service was restarted
Fixed an issue where usage records marked for deletion would not be deleted in some scenarios
Modified AvaTax integration to send the amount value as the total price for all lines (price * quantity) when service tax categories are utilized
Fixed an issue where UniquenessIdentifiers were not stored with the correct value when mediated usage data was archived
10.4.2-Patch.3 Release Notes
Fixed an issue where transition charges were billed using the ServiceID rather than the Charge_ServiceID