Contents

October 2026

Caroline Buckland Updated by Caroline Buckland

Financials October Release

Release Notes

This document contains details of new and amended functionality included in the software update deployed on 12th October. We've rolled out the following enhancements this month.

 ·       Accounts Receivable User Data

·       Validation on Duplicate Location codes

·       Non mandatory VAT codes on Customers

·       Portals – new setting to define GL account when using Item codes

·       GL Journal screen change

·       AFX Updates

External References for Accounts Receivable Transactions

Details of the change

We have now delivered the final part of the extended data fields for Accounts Receivable Transactions.  Follow the link the below to learn how to set this new feature up.

Details

Enhanced User Data for Sales Invoices

We've introduced a new capability that allows user data created for Sales Invoices to be seamlessly extended to Accounts Receivable (AR). As a result, the data will now be automatically passed through from the Sales Invoice to AR.

We recommend configuring SI Extended User Data and AR Extended User Data in the same manner for both transactions and items. This unified approach ensures that data is accurately and efficiently transferred between the two systems.

Current Limitations

Please note that these extended user data fields are not currently accessible via APIs or Jasper reports.

April 2026 - Help | Financials

Duplicate locations – Purchasing

Details of the change

We've introduced a new feature that enables postcode and address line one validation for location codes. This enhancement allows you to configure a setting that displays a warning or error message when a user tries to create a new location with a postcode and address line one that already exists. This improvement helps maintain data integrity and prevents duplicate location codes being created.

To make the most of this feature, you can adjust the setting according to your needs, choosing between a warning or an error message, depending on your organisation's requirements.

Setup

Select Change Company/Role button

Enter your company code in the window and then select F4 on the keyboard.

Select the Edit>Amend action.

Select from the drop-down menu to this set as a warning, or error for any duplicates entered.

When setting up new Location codes with the same Postcode and address line one, the following message are displayed.  

Non mandatory VAT codes on Customers

Details of the change

We've introduced an update to our Accounts Receivable feature, providing greater control over VAT code entry during data entry. This new functionality allows you to configure a setting against a specific customer, ensuring that users are prompted to manually enter a VAT code rather than the default code associated with that customer.

This change was applied to Suppliers in the September Release.

For more details select the link September 2026 - Help | Financials

Exclusions

Any system generated transactions that require a tax code (e.g. AR generated interest charges) will continue to use a default tax code as the user has no interaction with these transactions.

Additional changes will be required to the API’s and reporting for the new customer and supplier control changes for the new indicator to control data entry defaulting of tax codes.

Tax code entry is then a mandatory entry when creating documents.

Portals – new setting to define GL account when using Item a default item

Details of the change

The GL account can be cleared and then automatically re-defaulted on the Requisition and Order Basket screens when the Item code is updated. This functionality can be controlled through configurable system settings on the Administration tool.

Here's how it works:

When the Setting is Off

  • The GL account will not be cleared when the Item code is changed.

When the Setting is On

  • Entering an Item Code: If you enter an Item code for the first time, the GL account will be cleared.
  • Removing an Item Code: If you remove an Item code that was previously entered, the GL account will not be cleared.
  • Changing the Item Code: If you change the Item code, the GL account will be cleared.
  • Not Changing the Item Code: If you don't change the Item code, the GL account will not be cleared.

This behaviour applies to both the Orders and Requisitions screens.

Setup

A new toggle control has been added:

Administration → Purchasing → Reset GL Account on Item Change

Journal Data Entry

Current Version

New Version – expected total fields added

AFX Updates

  • Improved accessibility in the Supplier List – Drawer treeview by ensuring the aria-labelled by attribute references a valid, unique ID that exists in the DOM and provides the intended accessible name (EFIVE-39554).
  • Enhanced the Supplier List – Drawer treeview structure by ensuring that only valid tree child roles, such as treeitem and group, are used within the tree hierarchy (EFIVE-39555).
  • Improved accessibility of the Supplier List – Drawer menu search by updating the label or ARIA attribute to reference a valid, unique ID in the DOM and correctly associate the label with the search control (EFIVE-39557).
  • Fixed an issue where the Due Date was not populating on the Invoice Header after validation in AFX, ensuring the expected due-date information is displayed correctly (EFIVE-40631).
  • Fixed an issue with the Calculator function incorrectly rounding off values in lines, ensuring calculated values retain the expected precision (EFIVE-40756).

 

Was this article useful?

September 2026

Contact