Version 3.05.31.45

January 26, 2026

 

Dear maestro* clients,

 

We proudly present the main developments that were added to maestro* and maestro*MOBILE in this update.

Happy reading,

 

The Maestro Technical Writing team

 

maestro*

Projects

201994

Time Management

213514, 214498, US-67998, US-67999, US-68004, US-68113

Invoicing

210168

Purchasing

210988

Equipment

205512

Service Management

208999

Maintenance

US-67357

Interfaces

US-67215

 

 

Projects Module

 

Project Management

 

maestro* > Projects > Maintenance > Projects > Project Management

 

201994

Modification made to the Project and Activity columns of the Selection of activities to add to contract window, available via the Apply Subcontracts icon, so that these columns support the full length of project and activity codes, i.e. up to 20 characters.

 

Time Management Module

 

Record of Employment

 

maestro* > Time Management > Payroll > Layoff > Record of Employment

 

213514

Modification made to consider in “insurable hours” the vacation paid in hours with Revenue types of bonuses for which the Affects Employm. Insurance (for Hours) box is checked, and to update the cumulative insurable hours in the employee’s file accordingly.

 

Define Hourly Rates and Social Benefits Management

 

maestro* > Time Mangement > Maintenance > Payroll > Define Hourly Rates

maestro* > Time Management > Maintenance > Payroll > Social Benefits Management

 

214498

Modification made to update hourly rates and social benefits in maestro*, from the CCQ website, for trades greater than or equal to 600, with the Occupation skill.

CCQ Employer's Monthly Report

 

maestro* > Time Management > Payroll > Reports > CCQ Employer's Monthly Report

 

US-67998

Modification made to the display of the number of weeks worked.

US-67999

Modiification made so that various contributions and social benefits are calculated based on total worked hours.

US-68004

Modification made to allow the report to be produced for more than one committee simultaneously.

US-68113

Modification made to the display of the CCQ union contribution.

 

Invoicing Module

 

Invoice Preparation

 

maestro* > Invoicing > Contractual Billing > Processing > Invoice Preparation

 

210168

Cost Plus Invoicing

Modification made to display the unit cost price of each transaction with the same precision (i.e., the same number of decimal places) as the project cost transaction. The unit selling price will be calculated based on this unit price.

Purchasing Module

 

Batch Disbursement and Project Disbursements

 

maestro* > Purchasing > Purchasing > Payment > Batch Disbursement

maestro* > Purchasing > Purchasing > Payment > Project Disbursements

 

210988

Modification made to take into account the Discount Calc. method defined in the supplier file when calculating the discount to be applied.

 

Equipment Module

 

Tool Allocation

 

maestro* > Equipment > Small Tools > Processing > Tool Allocation

 

205512

Modification made to the return-to-inventory of tools assigned to suppliers.

 

Service Management Module

 

Call Dispatch

 

maestro* > Service Management > Service Management > Dispatch > Call Dispatch

 

208999

Modification made to eliminate the error message when the call grid is in SQL mode for a regular user.

 

Maintenance Module

 

Analyze Transactions

 

maestro* > Maintenance > General Maintenance > Analyze GL > Analyze Transactions

 

US-67357

Modification made to eliminate the error message obtained when exporting to Excel.

Interfaces

 

XML Interface

 

US-67215

Modification made to the CreatePurchaseOrderInvoicing XML function to consider the values present in the tax tags in the XML file structure, even if a receipt of goods "Counter" is present.

When creating an invoice for a stock order from catalogue using the XML interface, it was possible to specify one or more receipts of goods "Counter" numbers, which made it unnecessary to fill in all the fields in the breakdown grid.

However, the interface did not take into account any changes that users wanted to make to taxes; the tax-related tags were completely ignored.

The objective of this development is therefore to take tax tags into account when they are present, even if the receipt of goods "Counter" is present in the XML structure.