2025.2 Release notes
The 2025.2 release includes an Australian payroll compliance update and extends the multi-factor authentication (MFA) features introduced in 2024.3 to work for Greentree Browser.
We’ve also resolved issues identified in previous versions.
New features
Secure your Greentree Browser access with multi-factor authentication (MFA)
These days a password isn't enough to protect your online data. That's why we use multi-factor authentication (MFA) as a second layer of protection. It involves using something only you have access to: your mobile phone or tablet. This makes it harder for unauthorised people to access your Greentree Browser data.
Follow our MFA instructions to get started.
(Australia) Updated SGC threshold
For Australian payroll, we’ve updated the Super tab of the HR Module Control form to include the SGC threshold effective from 01/07/2025.

Other improvements
The inspector confirmation message now shows which data bucket you’re deleting or archiving records from. For example, in the screenshot below, records are being deleted from data bucket 2.
On the eDocs Status Maintenance form, teams are now listed separately from users. This makes it easier to give users the right eDocs access by simply selecting their team.
Platform updates
For Greentree Browser, this release includes a Sencha upgrade to version 7.7. This is mostly a behind-the-scenes change, but we’ve also refreshed the login screen to look the same as other Greentree login screens.
This release includes a JADE hotfix, which resolves JADE ODBC driver memory leak issues.
Resolved issues
Greentree Desktop
Issue IDs | Description |
---|---|
00014147 | A user called “User Tree Top” was appearing at the top of several forms, but wasn’t available on the User Maintenance form. We’ve updated User Tree Top so it will no longer be shown on forms. However, Greentree still uses User Tree Top as a template when you create a user with preferences set to None. By default, this user:
If you’re a value-added distributor (VAD) There has been a minor change to two plugin events that occur when users are created. When a new user is created from “None” the source user parameter to eventUserDuplicate and eventPostUserDuplicate will be null. |
00014145 | There was an issue with the propagation of email addresses from report parameter forms to the Add to Email Queue form for these reports:
|
00014171 | On the HR Employee Maintenance form, you couldn’t search by employee first names. |
00014209 | When opening ARCustomerMaint with Jade Painter, an error could occur: “'The requested property is not defined for this object class' (1011)”. |
00003581 | If a customer was inactive, the job code, job name and contact weren’t displayed on the JC AR Invoice Entry form. |
00014212 | We’ve removed the New Status button from the JC Status Maintenance form, as it was causing a 1310 error. Instead, you can use the Clear Form button, which works the same way as the New Status button. |
00014172 | An error could occur on the Prepare Stocktake and Stocktake Template forms: 14049 - "Invalid number of rows set for Table". |
00014088 | When changing ownership for a physical asset, Greentree was updating the child asset with all information from the parent asset. Now, Greentree only changes the new owner information on child assets. |
00014244 | On the Job Cost Module Control form, selecting the User masterfile audits checkbox could cause an error: “An error has occurred (1035) String too long.” This occurred if the name of a job cost report on the Reports tab exceeded 30 characters. |
00005189 | For DIM AR Customer Import, you can now choose any user defined field when selecting a system field. We’ve also added Assigned Team as a system field option. |
00014213 | You no longer need access to the AR Invoice Entry form to use the gtJCARInvoice FREE function. |
N/A | The new AR Auto Batch FREE functions now correctly display only mandatory fields in bold font. |
00009294 | On the Pay Entry form, replacing a GL line with a JC line could cause an error: “An error has occurred (1086) Class of object is invalid in this context.” |
00014157 | When using the XLSX format for Excel output, saved selections did not record a report’s output details where 'Save to Excel XLSX file' was used. When recalling the saved selection, both the Output report to and the Address fields were left empty. |
N/A | We’ve resolved minor visual layout problems. |
00014175 | We’ve improved the performance on the IN Prepare Stocktake/Enter Counts form, which was very slow to load when using a large inventory tree for stocktake. |
eDocs
Issue IDs | Description |
---|---|
00014703 | If you manually changed the selling rate on a purchase order with JC lines, then using eDocs to allocate the purchase order to an AP invoice reverted the selling rate to its original value. |
00013972 | Sometimes a PDF attached to an eDoc wouldn’t display. |