...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
IN PROGRESS
Workbench Release Notes
| Expand | ||
|---|---|---|
| ||
Scheduled Release - 29 July 2024 |
...
Upcoming Functionality & News
Workbench API Licence
The use of the Workbench API will now require a licence. An API User licence will enable you to access all the Workbench functionality available through our API.
Contract Progress Claim Process - upcoming changes you need to know
We will be making changes to improve the Claiming process on Contract Claims, and users will soon be able to:
Capture This Claim Claimed Values.
Capture this Claim Certified Values.
Available from August 2024 as a beta feature.
...
New Features
GST-registered clients/suppliers
We have improved the way Companies (suppliers & clients) are flagged as GST registered in Workbench (Use GST flag) when syncing from the Financial Systems.
1- On creation of new companies (synced from the financial system using its API), the Use GST flag on the company will be set to true only if the template company has it set to true.
...
New companies, the Use GST flag on the company would be set to true only if the template company has it set to true, and the GST Number was populated in the financial system. However, this was only set on create (i.e. the first time this company is synced or created from the financial system; updates to the financial company thereafter would not update this field in Workbench).
...
Feature Revisions
Purchase Requisitions
GST and GST type can now be enabled on Purchase Requisition lines via Grid Management, hidden by default. This is to keep consistency with Purchase Orders, for those who have GST enabled for POs.
Internal Comments from a Purchase Requisition can now flow to a Purchase Order’s new field Internal Comments.
Subcontracts
Approved Subcontract Retention Balance Statement in Retention Reporting:
The Retention balance used across the application includes any subcontract claim, but there are cases where clients are creating a full retention release and leaving it unapproved, ready to be used in the future (even 1 year ahead). In this case, the subcontract is not included in the report, because the retention release is included as if it has been approved, making the retention balance $0.
We have made a change to the logic of the Retention Balance Statement so it is populated when there is
A new column has been to display the Approved Retention Balance, in addition to the existing Retention Balance value on the Retention Reporting tab on Retention Management:
a balance of approved retentions different to $0, as opposed to a retention balance different to $0 (including ALL existing subcontract claims regardless of their status)
Quotes
Enhancements:
Quote Selling value in the Main tab is now locked when there are Costs Sheets. It will reflect the Selling Value of all Cost sheets. This is to avoid having a user approve a value in the Main tab that does not match the sum of the Selling value of the Cost Sheets. If there are no Cost Sheets, then this field can be edited.
Service Log
Improvements to the invoicing process have been made for Service Logs with a Quoted charge type:
The default invoice value will come from the Log’s Expected Value, if no value is specified in it, it will come from the Job’s Job Value (in Job maintenance).
The Billing statuses:
Part Billed: when there are invoices and the $ value is less than the quoted Job’s Value (value in Job Maintenance).
Billed: invoice/s same or greater than the quoted Job’s Value (value in Job Maintenance).
Month End
Minor enhancements:
AR invoice - email template:
The 'Report - JobInvoice' email template now has $InvoiceValue token formatted with thousand(s) commas & a new token $InvoiceValueOnly with no currency code.Timesheets - Log and job code:
When selecting a Logno first in a timesheet line, this will auto-populate the Job Code with the Job from the Service Log
People Scheduler - sorting by name:
The default sorting order for the employees in the People Scheduler is now by first name. It was previously sorted by EmployeeID which was not very useful.
...
Upvise
...
Integration
Financial integration via API - import inactive status for companies
To avoid users selecting inactive suppliers or clients, we have enhanced the integration with the financial systems (via API), so that when a company is made inactive (or archived) in the financial system, this change also syncs to Workbench, and the Company is flagged as Inactive.
MYOB Advanced
PO number on exported AP invoices:
When exporting an AP Invoice, the AP invoice comments will have the PO number on the first AP Invoice line. If there are multiple different PO numbers on the different AP invoice lines, then to avoid confusion the PO number will not be populated in the AP Invoice comment when exporting to MYOB.
Fixes & Technical changes
| Expand | ||
|---|---|---|
| ||
Dockets & DaysheetsTimesheetsBillingUpvise |
...
Things we are busy working on...
💻 New series of webinars started in July. Visit our new Events page on our website for our August Webinar.
...