Release 2025.11
Nov. 27, 2025
This release represents a significant step forward for Maki: from a completely redesigned invoicing experience to a powerful and flexible integration with Exact Online. Teams work faster thanks to automated ticket handling, smart synchronization, and immediately organized activities. Analysts also gain greater capabilities with expanded Power BI datasets. The release also includes strengthened security, resolved bottlenecks, and technical upgrades that prepare Maki for the next phase.
What’s in the release?
GUI – Design Invoices + InvoiceLines
The entire design of the invoice and invoice line pages has been redesigned based on Maki UI guidelines. In addition to a more modern look, the screens are now more functionally consistent with the rest of the platform. Users can access a clear detail screen that brings together all relevant invoice information, and existing filtering capabilities are optimally integrated into the new design
Automatically close ‘Resolved’ tickets
A new management setting has been added that allows tenant admins to control after how much time tickets with Resolved status are automatically closed. This eliminates the need for manual closing. In addition, a default message can be set that is automatically posted as a comment when a ticket is closed by this process. This increases efficiency and keeps ticket overviews current and clear, without additional management effort.
On/off switch for financial coupling
Tenant Admins can now easily choose whether their organization is linked to a financial package, such as Exact Online. When activating Exact, an integration is automatically created, after which additional settings become available. When deactivating, the existing link including configurations will be checked and securely removed. This allows an organization to flexibly switch between having or not having financial integration, depending on their business operations.
Setting billing preference by relationship
Maki now offers extensive capabilities to tailor billing behavior at both the organizational level and by individual relationship. This allows users to control how time entries and projects are grouped on invoices-from a single collective invoice to fully segmented invoices by project or ticket. Relationships adopt organizational settings by default, but these are easily fine-tuned on a per-relationship basis. This gives finance teams maximum control over invoice composition to customers.
Article link for time recording category
With an active connection to Exact Online, time registration categories can now be linked to article codes from the financial package. Users can set a default article for the organization as well as different articles per category and per invoice line. The list of available items is retrieved from Exact and cached locally, allowing users to select quickly without performance loss. This ensures accurate processing of hours in financial administrations.
Ability to configure financial linkage
Administrators can now manage the Exact connection settings themselves, including authentication settings and the selection of default article codes. They can also specify which article code to use per time recording category. This makes the financial integration fully manageable and accurately aligned with the customer’s Exact environment.
Synchronization of relationships with Exact
Relationships can now be automatically synchronized with Exact, with Maki leading all customer data. Once a relationship gets Account status in Maki, it is created in Exact and Exact links its own relationship number back to Maki. Address information is automatically included. In addition, buttons have been added to manually force synchronization at the integration or relationship level. This keeps customer data in both systems fully in sync.
Organize new or changed activity directly chronologically
Activities in the communication feed are now automatically placed in the correct place based on date and time, both when created and when modified. This eliminates the need for the user to refresh the page to see the correct chronological order. This increases the reliability of the feed and makes communication information instantly clear and logically ordered.
Security against brute force attacks on MFA.
The security level of the MFA procedure has been further tightened. User accounts are automatically blocked after five failed MFA attempts, with a clear notification about the block. The counter is reset after successful login or if the blocking period is over. This effectively prevents brute-force abuse and maintains account security for all users.
New field for billing email address on relation card
A separate field has been added for a relation’s billing email address so that this email address is separate from the notification address. This prevents errors when synchronizing with Exact Online and makes it clear which address is used for invoices. The field is only editable for users with a new permission and is supported in import/export. Also, the correct address is automatically used in financial linking.
Adding Companies table to Power BI dataset
The Power BI dataset has been expanded to include a new table for relationships with a link to time entries, projects, tickets and tasks. This allows analysts to easily segment reports by company or customer. This makes dashboards more powerful and analyses more interpretable.
Year, quarter, month and week fields in dataset
Additional time dimensions have been added to several date fields, such as year, quarter, month and week. These fields make it easier to perform time series analysis, identify trends or do SLA evaluations by period. This significantly enriches the Power BI dataset and speeds up analysis work.
Include total duration in invoice specification
In addition to the total amount, the invoice specification now also shows the total duration of the hours charged. This makes it immediately clear to customers how the invoice is structured and increases the transparency of the services provided.
Resolved bugs
Show eye icon on billable time entries
For billable time records, the eye icon was not automatically displayed, causing ambiguity about the visibility of these records. This has been fixed: all new and existing billable time records now automatically show the familiar visibility icon. This visibility can no longer be adjusted manually, so that users always get an unambiguous indication.
Correct display of icons on employee page
On the employee page, the icons for lock/unlock and MFA did not always reflect the actual status. Also, multiple tooltips appeared, which caused confusion. The logic behind status display and tooltip has been completely corrected: icons now always show the current status, and one consistent tooltip clearly shows which action will be performed.
Active menu selection in module ‘Time’ is not displayed properly
When users navigated to other pages within the Time module (such as Time per day or Approve), the All time menu item remained visually active. The menu selection error has been fixed: the menu item belonging to the opened page is now immediately highlighted correctly, making navigation more intuitive.
Profile page employee gives white screen
A specific employee was unable to open her profile page due to an error that resulted in a full page crash (white screen). This error was traced to incorrect data processing within the profile component. The page now always loads correctly, allowing employees to reliably view and edit their own data again.
Searching contacts without case sensitivity
The search function within contacts was case-insensitive, so the same name could return different results depending on the capital letters used. The search logic has been modified so that first and last names are now no longer searched case-insensitive. As a result, any variation of a name will yield desired results.
Filter ‘MFA’ in employees does not work
The MFA filter in the employee view always returned an empty result when used, regardless of the filter value. The filter logic has been restored, so administrators can now quickly find employees with or without an activated MFA.
Treatment group service partner-child sometimes not selectable after ticket creation
Immediately after creating a new ticket, some treatment groups of service partner-child organizations could not be selected. This was due to not immediately updating available groups in the dropdown. This has been corrected: after creation, all groups become immediately available in the list, allowing tickets to be assigned without delay.
Filter by relationship + status ‘New’ does not show old projects
Combinations of filters by relationship and status New sometimes showed no projects even though they met the criteria. This mainly concerned older projects with an end date in the past. The error in the filter logic has been fixed, so that all projects that meet both filters are now correctly visible in the overview.
Maintenance
.NET 10 testing and migration
The application was tested and migrated to .NET 10, including compatibility checks and validation of critical functionality.
Server updates (November 2025)
Extensive updates have been made to .NET hosting bundles, RabbitMQ, Erlang and Elasticsearch. This keeps the platform secure, stable and ready for upcoming enhancements.
Back-end & Front-end updates (November 2025)
Various maintenance work was performed on both front and backend, including dependency updates and performance optimizations.