Within these release notes you will find descriptions of new features, enhancements and API changes in the LogiSense Billing application. The content below details changes in major release versions, point release versions and hotfixes. If you have any questions about the information provided below please do not hesitate to contact your LogiSense support representative.
In this article:
10.8.0.0 Release Notes
Change Highlights
...
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 a 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
...
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/Package/Frequency/{id}/Basic/Detail (Get)
v10/Package/Frequency/{id}/PriceBook/{id}/Pricing (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