What's new in version 2501.0.0.0

Tax Management for Drink-IT  •  Release Note  •  4/23/2025  • 

Features

With the features added in this release of the Aptean Beverage Tax Management extension, Drink-IT Edition,

  • You can view the tax ledger entries that close during tax settlement without a financial transaction, as their total amount is zero. The Closed by Date and Closed by Document No. fields on the Tax Ledger Entries page display this information. The system updates these fields with the corresponding Posting Date and Document No. field values from the Calculate and Post Tax Settlement page when you execute the Post action.
  • The system restricts the modification of the Default Tax Classification and Excise Type fields on the Location Card page if the location has existing inventory.
  • On the Item Card page, the Excise Product Code field value can be manually updated automatically derived during the validation of the Tariff Group or Default Tax Classification fields. The Excise Product Code field value is carried forward to the document tax line, tax ledger entry, and customs document, following a defined priority order. The precedence for this value, from highest to lowest, is as follows:
    • Item
    • Tariff group
    • Default tax classification.

UI/UX changes

The following UI/UX changes have been made in this release.

  • The Closed by Date and Closed by Document No. fields have been added to the Tax Ledger Entries page.
  • The Excise Product Code field has been added to the Item Card page.

Resolved issues

The following issues have been resolved in this release.

IDDescription
247017The system fails to update the Default Tax Classification field value on the Item Card page after assigning the New Classification Code field value for the associated tax code of the item on the Update Item Tax & Tax Classification page.
247053The system fails to update the Item Tax Class. Code field value on the Document Tax Lines page associated to any sales, purchase, or transfer document or item journal when using the Update Item Tax Classification in Documents action. This issue occurs after assigning a new tax classification code in the Tax Classification Relation page for an item.