2025.6 Release Notes

Schedule

For an explanation of the zones, refer to Where am I hosted?

Zone	Date	From (UTC)	To (UTC)	Duration
Limited Release and UK Limited Release	November 26, 2025	01:00	05:00	4 hrs
America East 1, 2 & 3	December 4, 2025	01:00	06:00	5 hrs
America West 1, 2, 3 & 4	December 10, 2025	01:00	06:00	5 hrs
UK, UK 2, UK 3, EU 1 (English), and German	December 10, 2025	20:00	01:00	5 hrs
Australia 1, 2 & New Zealand	December 11, 2025	15:00	17:00	2 hrs
Spanish	December 10, 2025	01:00	03:00	2 hrs

IMPORTANT  All dates are subject to change. For up-to-date information on scheduled releases, refer to the Kaseya Status Page.

New Features

Strengthening password policy for enhanced security

As part of our ongoing commitment to security and compliance, we are updating our password policy to address vulnerabilities identified during recent penetration testing. The previous policy allowed passwords as short as seven characters and enforced certain complexity requirements.

IMPORTANT  All users must ensure their passwords comply with the minimum complexity requirements. Passwords that do not meet these requirements must be updated to align with the new security standards.

What’s changing?

• Minimum Password Length Increased: The minimum required password length will be raised from seven to 12 characters.

• Complexity Requirements Maintained:

  • Exclude spaces and single quotes (').

  • Include at least one special character.

  • Contain characters from at least two of the following groups: uppercase letters, lowercase letters, numbers.

  • Be different from your previous 5 passwords.

Why this matters?

• Improved Security: Longer passwords are significantly harder to crack, reducing the risk of unauthorized access.

• Compliance: Aligns with OWASP and industry best practices for password security.

• Reduced Predictability: We are reviewing positional restrictions on special characters to avoid predictable password patterns.

What will be required of users?

• New Passwords: When creating a new account or changing your password, you must now use a password that is at least 12 characters long and meets the complexity requirements.

Centralized license management

The new centralized license management UI for Autotask is a major enhancement that merges the resource and license management pages into a single, unified experience. This update introduces a modernized interface for managing all license types—including Resource, and Co-managed users—directly from one page. It also supports the new Contractual Minimum Quantity (CMQ) licensing model, replacing the previous High Watermark Pricing approach. Refer to CMQ faqs for more information.

Why is this helpful?

Benefit/Impact	Description
Unified Management	Manage all licensed users (Resource, Co-managed, and API) from a single, streamlined page—no more switching between multiple admin screens.
Flexible Licensing	The new CMQ model allows you to flexibly add users above your contractual minimum as your business grows, with clear visibility into overages for billing.
Improved Visibility	Instantly see how many licenses of each type are in use, with real-time tiles and a detailed table.
Simplified Navigation	All previous admin links for user and license management now redirect to this new page, ensuring a consistent and efficient workflow.
No Forced Deactivation	If you exceed your contractual minimum, users are not automatically deactivated. Overage is tracked and reported for billing, giving you more control and flexibility.

e-Invoicing support for the European Union (EU)

Autotask is adding e-invoicing support to comply with the EU’s VAT in the Digital Age (ViDA) directive, ensuring structured, machine-readable invoices that meet regulatory standards while improving compliance, efficiency, and cross-border transparency.

IMPORTANT  Enable e-invoicing only when Autotask is the authoritative invoicing system. If your environment uses an integrated financial platform for invoice management, delegate e-invoice generation to that system to maintain data integrity. Do not activate e-invoicing if invoice numbers are modified or reassigned outside Autotask after initial creation, as this can introduce discrepancies between systems.

What does the new e-invoicing feature mean?

If your organization operates in the EU, you may soon be required by law to submit invoices electronically in a standardized format.

The new e-invoicing feature in Autotask helps you comply with these evolving government mandates (such as the EU’s VAT in the Digital Age/ViDA directive) without needing to manage separate systems or manual processes.

Once enabled, Autotask can automatically generate and submit e-invoices for your customers who require them.

Benefit/Impact	Description
Regulatory Compliance	Meet EU and local government e-invoicing mandates easily.
Automation	Reduce manual invoice handling and errors.
Customer-Specific Controls	Enable e-invoicing only where needed.
Status Visibility	Track e-invoice delivery and acceptance in real time.
Future-Proofing	Be ready for upcoming legal requirements in your country or region.

Supported countries and mandate start dates

Country	Mandate Start Date	Notes
Belgium	2026-01-01
Germany	2026-01-01 2027-01-01	2026: Companies with annual income above €800,000 and as required by receiving party. All others by 2027-01-01.
Estonia	2026-01-01
Romania	2026-01-01	MSP must register with local VAT agency; Legal ID required.
Spain	2026-01-01 2026-09-01	Special B2G requirements (not in initial release); Verifactu submission required from 2026-01-01.
Poland	2026-02-01
France	2026-09-01
Slovenia	2027-01-01
Latvia	2028-01-01
Rest of EU	By 2030	No mandated start date yet, but all must comply by 2030.

e-Invoicing commonly asked questions

1. Which countries are included in Autotask’s e-invoicing support?

   • All EU countries are included, with support prioritized by each country’s legal mandate start date. The first wave includes Belgium, Germany, Estonia, Romania, Spain, Poland, France, Slovenia, and Latvia. All EU countries must be compliant by 2030.

2. What if my country does not have a mandated start date yet?

   • If your country is in the EU but does not have a mandated start date, you can request to have e-invoicing enabled. All EU countries will eventually be required to comply by 2030.

3. Are non-EU countries supported?

   • No, the initial release only supports EU countries. Support for other regions may be considered in the future.

4. What are the minimum requirements for an e-invoice?

   • Tax/VAT ID (with country code) for both sender and receiver.

   • Legal ID (if required by local regulations).

   • Destination country (from billing address).

   • Fallback (contact) email address.

   • Government invoice flag (if required).

   • Sender and receiver details.

5. What happens if an invoice submission fails?

   • If the invoice is missing required information, the Routing Agent will reject it. You must correct the data and resubmit via the Invoice History page. If the Routing Network submission fails, the invoice will be sent via fallback email automatically.

6. How is data processed and where is it stored?

   • Autotask uses a Routing Agent based in the Netherlands, with data centers located within the EU. Data and architecture reviews are ongoing to ensure compliance.

7. What are the country-specific requirements?

   • Germany: E-invoicing required for companies with annual income above €800,000 and as required by the receiver; all others by 2027-01-01.

   • Spain: Special B2G requirements (not in initial release); Verifactu submission required from 2026-01-01.

   • Romania: MSP must register with the local VAT agency; Legal ID must be stored in Autotask.

   • Italy, Poland, Estonia, France: The Routing Agent manages registration and submission to the VAT agency.

8. Can I disable e-invoicing for some organizations?

   • Yes, e-invoicing can be enabled or disabled per CRM organization. Bulk updates are supported via CRM Export/Import.

9. What is the fallback if network submission fails?

   • Invoices will be sent via email from the Routing Agent. This fallback cannot be disabled, as it is a regulatory requirement.

10. What is not supported in the initial release?

    • Invoice grouping (Roll Up) via templates (must be disabled for e-invoicing). To ensure that the invoices are submitted correctly, all groupings (rollups) must be disabled on the invoice templates to ensure accurate and consistent invoice reporting. E-invoices need to show all taxable items for accurate tax reporting.

    • Spanish B2G routing (planned for a future release).

    • Voiding (credit) invoices and email-only options (planned for future releases).

List of improvements and fixes in this release

Type	Summary
Fix	Fixed the storage of Message-ID values for In-Reply-To headers so that email replies are correctly threaded into ticket notes.
Fix	Resolved the error (STDE) that occurred when running the Resource Utilization report in Standard Reports.
Fix	Fixed the 404 error when searching global notes with queries exceeding the character limit.
Fix	Standardized the ticketWebhook payload so that it is consistent between update and create actions.
Fix	Fixed the "Access Denied" error when using the "Renew Contract" option in widgets.
Fix	Fixed the SQL transaction error when editing security level permissions as users.
Fix	Fixed workflow rules so that approval requests created via API now trigger them as expected.
Fix	Ensured that modifying regular time entries updates the "lastModifiedDateTime" value via the UI.
Fix	Fixed the dynamic range filter so tickets with due dates at the end of the quarter (on the 31st) are shown.
Fix	Corrected the display of task time entries using non-billable work type in LiveMobile (Android) and LiveMobile (iOS).
Fix	Fixed the date/time variable in ticket notification templates to display the correct value for the Adelaide time zone.
Fix	Fixed the context menu so "View Timesheet" navigates to the correct timesheet, not always the current one.
Fix	Resolved the STDE error when viewing milestone details in Approve & Post for certain users.
Fix	Fixed the issue where the PDF pop-up did not close and the PDF did not open after generating a purchase order PDF.
Fix	Fixed permissions so co-managed users cannot see ticket numbers/titles they should not access.
Fix	Fixed the feedback script so the window can be closed and is properly grayed out.
Fix	Fixed the contact picker/type ahead so additional contacts can be added even if the Contact field is not visible.
Fix	Fixed the Company Insight so it displays correctly when a company is assigned via a ticket form template.
Fix	Fixed the Error 500 when using multiple filter fields in LiveReports dropdown menus.
Fix	Fixed the Account Widget so alert columns display data when drilling in.
Fix	Fixed the opportunity owner selection so Save/Save & Close works with a single click.
Fix	Fixed the browser settings check to report the correct Windows/Browser version.
Fix	Fixed the time zone display for the Dispatch Calendar for (UTC+10:00) Canberra, Melbourne, Sydney.
Fix	Fixed system daily alerts so they do not show inactive Expense Approvers when the Expense feature is deactivated.
Fix	Fixed the STDE error when accessing tasks in LiveMobile with certain security level/task category settings.
Fix	Fixed the address format so changing the default does not add a blank line in address fields.
Fix	Fixed the API so "isSupportedWebhookField" is correctly set for ticket fields.
Fix	Fixed the display of currency symbols for cost/price in Subscription widgets.
Fix	Fixed timesheets so Task Work Hours display correctly when the resource is changed after time entry creation.