Insights & updates from our experts
In recent enhancements, it has become possible to relate invoices to projects, and after that to changes, contracts, service level agreements and first line support agreements. Soon, it will also be possible to link an invoice to configuration items (CIs). As it will be possible to link several CIs to one invoice, the ‘Subject’ column on the ‘Invoices’ view, that shows the name of the record an invoice belongs to, is now substituted by the ‘Service’ column, showing the service the records that are linked to the invoices are related to.

For contracts and FLSAs, that are not related to a service, the ‘Service’ column in the ‘Invoice’ view is empty. Note that invoices still contain the same information, so imports and exports of invoices still function the same way they did before.

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)











