August 31, 2025

We are pleased to announce the VOGSY updates for August 2025. This release focuses on significant performance enhancements in reporting, expanded resource management capabilities, and new datasets for advanced analytics and custom reporting.

Optimized Time Entry Reporting

Report generation and refresh speeds for Time Entry reports have been significantly improved. New filtering options are now available, allowing for more granular data selection and faster performance.

New Employee Skills Matrix Report

A comprehensive skills matrix report has been added to provide a clear overview of employee skills and proficiency levels, enhancing resource planning. The data from this report is also available as a BigQuery dataset for advanced analytics.

Track overtime

The Overtime feature is now available! This feature allows for robust tracking, management, and reporting of employee overtime. For setup and usage details, please refer to the updated User Guide: Overtime tracking, management, and reporting.

Introducing the New Back Office

We are excited to launch our new Back Office, now accessible via an extra option in the main menu. As previously announced, this new experience features a completely modernized UX while offering the same back-office features. You can read more about this update here. To ensure a smooth transition, the classic version will be available alongside the new one until October 1st, 2025, after which the new back office will become the standard

New Task Export Report

A new back-office report is now available to export task data directly to Google Sheets or Microsoft Excel. This allows for flexible, custom analysis and provides stakeholders with detailed insights into task management.

New BigQuery Dataset: Project Invoices

To further enhance custom reporting, a new BigQuery dataset containing all project invoice data is now available. This allows for in-depth financial analysis and the creation of custom dashboards using your BI tooling.

Bug Fixes

Invoice XML Data: An issue was resolved where invoice XML files did not use the correct organization name when an alternative invoice address was specified. The XML output now correctly reflects the customer name, ensuring data consistency.