Insights & updates from our experts
It recently became possible for directory administrators to go to the âBillable Usersâ section of the Settings console in their directory account to download not just the billable users registered in the directory account, but also the billable users whose person records are registered in the any of the directory accountâs support domains. This makes it easier to get a complete overview of the Xurrent usage within the enterprise and to charge back billable users to the different enterprise functions that use Xurrent to manager their services.
This week, the âBillable Usersâ section has improved even further. When administrators open this section of the Settings console, they are now greeted with a graph that presents the number of consumed user-months over time.

Checking the Group by account box, turns the graph into a stacked bar chart that presents the Xurrent user-month consumption by account. This graph is also available â without the checkbox â in support domain accounts and standard accounts to allow the administrators of such accounts to easily track their billable users over time.
The same graph can be found by every auditor and administrator in the âReportsâ section of the Analytics console. That makes it possible to place this graph on a dashboard. In the âReportsâ section, the graph is called âConsumed User-Monthsâ, where 1 user-month is considered consumed when a person who is registered in the account had access to Xurrent as an auditor, specialist, designer and/or administrator at any point during a given month. When the âConsumed User-Monthsâ report is opened in a support domain account or a standard account, only the billable users whose person record is registered in that account are included in the report.
This improvement should give customers improved visibility of their Xurrent user-month consumption over time.

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

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)














