We’re committed to keeping you fully up to speed with all of the features, enhancements and fixes we ship at Root. Here are all of the updates and improvements we shipped over the last month 🛠️

Features

We’re working on new features to expand what you can do on Root:

• Add user group assignment when creating an application: You can now include a user group ID when creating an application using an API key, streamlining the setup process by assigning the application to a user group immediately.
• Improved policy details view on Dashboard: We’ve redesigned the UI for the policy details view on Dashboard to make product module data easier to read and navigate. Clients will soon be able to control which data appears and in what order by updating their product module code. This feature is planned for rollout in November. Read the docs.

Platform Enhancements

• Performance Enhancements

  We’ve introduced enhancements to improve stability, efficiency, and visibility across Root:

  • Refactor and clean up legacy claims views and schema: The deprecated claim details views v1 and v2 have been removed and replaced with a single, refactored version to simplify the codebase. An admin endpoint has also been introduced to allow updates to the legacy claim schema, ensuring continued support for configurations not accessible via the usual interface.
  • Improved OCR processing based on file length: We’re continuing to build and test a new AI-powered OCR feature that adapts its processing method based on file length to improve efficiency and reduce costs. This feature is not yet released to clients. If you’re interested in early access, please contact our product team to join the beta AI list.
  • Refactor get policy action to use named arguments: The get policy action has been refactored to use named rather than positional arguments, improving clarity and preparing the platform for future updates.
  • Updates for developer documentation platform migration: Backend updates have been completed to support an upcoming migration of our developer documentation platform.
  • Improved internal monitoring efficiency: We’ve made backend changes to streamline how system activity is monitored, reducing unnecessary data ingestion while maintaining visibility into platform health. These improvements help us operate more efficiently without compromising reliability.

• Billing Enhancements

  We’ve made several improvements to increase reliability, accuracy, and automation across Root’s billing processes.

  • Exclude arrears from lapse and NTU calculations: A new setting is being introduced to allow arrears payments to be excluded from lapse and NTU calculations. This will enable more accurate lifecycle tracking in cases where arrears should not impact lapse assessments.
  • Arrears payment linking: Arrears payments will be linked to their original failed premiums via a new field. UI updates will show these links clearly within policy and payment details, enhancing tracking and transparency.
  • Payment queries now use correct billing settings: Payment queries have been updated to use billing settings from current product modules, improving accuracy in payment processing and enhancing the assume-success logic.
  • Disable payment creation for specific external methods: A new billing setting allows you to disable payment creation for selected external payment methods. This gives finer control when managing multiple payment methods.
  • Optimise debit order payment processing: The debit order payment job has been optimised with larger batch processing, new indexing, and improved monitoring, resulting in smoother and more efficient operations.
  • Support for split arrears and premium DebiCheck collections: We’ve added functionality to support creating separate DebiCheck payment collections for arrears and premiums. This includes validation to ensure that each collection aligns with the rules of the associated mandate. The feature is this is currently only supported for external debit order collections, and is still in testing.
  • Enhancements to billing job performance and monitoring: We’ve made ongoing improvements to how billing runs and external payments are processed behind the scenes. These changes improve system reliability, streamline internal monitoring and alerts, and make it easier to support and investigate billing-related issues when they arise.

• Bug fixes

  We’ve addressed key issues to improve system reliability:

  • Incorrect blocking of payment methods: Fixed a bug where payment methods were blocked early due to failed payments across unrelated modules. Blocking now only occurs when thresholds are met within the correct module context.
  • Flush sandbox improvements: Addressed an issue where the flush sandbox feature would intermittently fail when flushing large organisations, resulting in partially flushed data.

If you have any suggestions or feedback, please share them with your Client Success Manager or submit them via the Root product roadmap to make sure we always know what’s top of mind for you.