What’s New in AutoCount Accounting Version 2.2.31.44

This release introduces a range of enhancements focused on improving email management, eInvoicing flexibility, and system usability. Key updates include per-user and per-database SMTP settings, improvements to the Server Mailing List, greater flexibility in maintaining Tax Entity information for submitted e-Invoices, support for the latest LHDN BRN requirements, and the addition of Brunei Dollar (BND) as a Home Currency option.

Important: This version of AutoCount Accounting will upgrade your Database Version to 2.2.96.

Summary of Key Enhancements

  • Support to cache SMTP From Name and From Email by each Database and each User ID
  • Add “From Email” column in the Server Mailing List
  • Enhance Server Mailing List with a Summary Footer
  • Support to allow editing Tax Entity fields even if already submitted e-Invoice transactions
  • Add new Brunei Currency (BND) as a Home Currency selection
  • Several other usability and reporting improvements

1. Support to Cache SMTP From Name and From Email by Each Database and Each User ID

The system now caches the SMTP From Name and From Email for each database and User ID. This enhancement eliminates the need to repeatedly re-enter the sender information when working with multiple account books on the same PC, ensuring each database retains its own SMTP settings.

Example:

  • Two account books are opened on the same PC.
Manage Account Book window showing two account books opened on the same PC
  • Account Book A uses From Name: Autocount Dummy and From Email: 123@gmail.com.
Mail Setting window for Account Book A showing From Name Autocount Dummy and From Email 123@gmail.com
  • Account Book B uses From Name: Brunei and From Email: example@gmail.com.
Mail Setting window for Account Book B showing From Name Brunei and From Email example@gmail.com

The system remembers the From Name and From Email for each account book/database independently, so users do not need to re-enter this information every time they switch to a different account book if the email used is different.

2. Add “From Email” Column in the Server Mailing List

A new From Email column has been added to the Server Mailing List to display the sender email address for each email record, allowing users to quickly identify which email account was used to send the email. Click here to learn how to configure Gmail SMTP for sending email.

Server Mailing List showing the new From Email column

3. Enhance Server Mailing List with Summary Footer

A new Summary Footer has been added to the Server Mailing List to display the total number of emails based on the selected filter and date range. This enhancement enables users to quickly view the total without having to manually count the email records.

Server Mailing List with summary footer showing total record count

4. Support to Allow Editing Tax Entity Fields Even If Already Submitted e-Invoice Transactions

The system now allows users to edit Tax Entity information even if the tax entity has already been used to submit e-Invoice transactions. This enhancement provides greater flexibility when maintaining Tax Entity records and eliminates the need to use the Merge TIN function for certain updates.

Example:

  • A submitted e-Invoice exists under an AutoCount TIN.
View Invoice screen showing an approved e-Invoice with Valid status
  • Users can still edit the Tax Entity information without affecting the existing submitted e-Invoice transaction.
Tax Entity Maintenance edit screen with a note that TIN is not allowed to be directly edited

Note: The TIN field itself is still not allowed to be directly edited.

5. Add New Brunei Currency (BND) as Home Currency Selection

The Brunei Dollar (BND) has been added as a new Home Currency option under the “Others” selection when creating a new Account Book. This enhancement provides greater flexibility for businesses in Malaysia that need to maintain BND as their base currency.

Create Account Book Wizard showing BND as an available Home Currency option

6. Other Enhancements

Some other key highlights of this version that do not require further explanation:

  • Amend all sales reports to display business date instead of created date for POS transactions — Updated all sales reports to display the Business Date instead of the Created Date for POS transactions. This change has no impact on users, as it simply improves consistency in the reporting function.
  • Add “Our Invoice No.” column at A/R Credit Note grid — Added an “Our Invoice No.” column to the A/R Credit Note grid, allowing users to easily view and identify the related invoice number.
  • Enhance DocNo to support up to 50 characters — Increased the maximum length of Document Number (DocNo) to 50 characters, providing greater flexibility for longer document numbering formats and matching the LHDN e-Invoice accepted character range.
  • Extend Sales Exemption No. field at transaction detail level to 300 characters — Increased the maximum length of the Sales Exemption No. field at the transaction detail level to 300 characters, allowing longer exemption reference numbers and matching the LHDN e-Invoice accepted character range.
  • Enhance Purchase Request to support Unit Price, Currency Code, Total Amount, and Reference Attachments — Enhanced the Purchase Request module to support Unit Price, Currency Code, Total Amount, and Reference Attachments, providing more comprehensive purchasing information and supporting documents during the request process.
  • Enhance auto-detect and assign issue date for e-Invoice submission — Improved the e-Invoice submission process by automatically detecting and assigning the appropriate Issue Date, reducing manual intervention and ensuring more accurate submissions.
  • Remove phone validation at transaction level — Removed phone field validation at the transaction level, allowing users to save transactions even when the phone number does not meet the previous validation rules.
  • [SG] Enhance InvoiceNow to handle empty Item Description — Enhanced InvoiceNow (Singapore) to support transactions with an empty Item Description, improving compatibility with different business scenarios and reducing submission failures.

Leave a Comment