Insights & updates from our experts
Service Instance and SLA Added to Time Entry Exports
Yet another improvement has been made to the time entry export feature. This feature is primarily used by managed service providers (MSPs) to integrate their Xurrent environment with their billing system.
A time entry export file already included the service, as well as the customer of the service, for each time entry. Now the following columns have been added to the time entry export files to make it easier for MSPs to relate their invoices to the SLAs they have established with their customers:
- Service Level Agreement ID
- Service Level Agreement
- Service Instance ID
- Service Instance

Because requests are the only assignments related to specific service instances and SLAs, the new columns only contain a value for time entries that were generated after someone filled out the Time spent field of a request.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)

.webp)












