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:

• Data imports: Work was done to improve data imports on Root. Imports that fail or stall part-way through can be retried from the dashboard and continue from where they stopped. Imports can also be set up to run automatically, from receiving the data through to producing the bank file, without manual steps.
• Product module enhancements: Several additions were made for product module builders:
  • The cancellation reasons available for a policy can be defined in the product module.
  • Product modules can define the document labels available when uploading a policy document.
  • A new lifecycle hook runs when an alteration package is created on a policy, for example to expire a pending alteration that is never applied. Read the docs.
  • A new API endpoint returns reference data from a product module, such as rate tables and benefit lists.
• Documents on Dashboard: We're busy developing a new feature that will allow clients to build, publish and manage their own documents on Root. Documents can be built from templates with merge fields, generated for policies, claims and other records, and attached to communications. This feature is still in development and testing.
• Invoicing: We're busy developing invoicing for policies on Root. It will allow clients to create and manage invoices on policies, send invoice communications to policyholders, and bring their invoice history across when moving to Root. This feature is still in development and testing. Read the docs.
• Insights dashboards: We're continuing to develop Insights dashboards, including dashboards built from saved queries and standard dashboards maintained by Root.
• Scheduled queries on working days: We're continuing to develop support for monthly scheduled queries to move off weekends and public holidays to the nearest working day, with an optional cut-off day.Platform Enhancements

• Performance Enhancements

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

  • API reference documentation: 56 more API endpoints were documented in the API reference. Read the docs.
  • Faster dashboard for multi-organisation users: Work was done to improve dashboard responsiveness for users in many organisations, particularly when completing quotes and opening policies.
  • Faster custom data exports: Template-based data exports were optimised, which is expected to cut run times on large books. Output files are unchanged. Read the docs.
  • Reliable delivery of large scheduled query results: Improvements were made so that very large scheduled query results are delivered reliably and exactly once.
  • Quote document versioning: An application's quote documents are versioned so every generation is kept, and a refresh is skipped when nothing has changed.
  • Product module resilience: Internal safeguards were introduced so a missing shared dependency no longer takes a whole product module down.
  • Application search by number: The applications list search matches partial application numbers, for applications created from this release onwards.

• Billing Enhancements

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

  • Collection modules: Work was done to extend collection modules, including support for payment partners that exchange files instead of API calls. The platform handles sending files, receiving partner replies and settling the payments, with safeguards so each file is only sent once. Module authors also get clearer logs to troubleshoot their own modules. Read the docs: Collection modules and File batching.
  • Payment methods and billing configuration: Updates were made to give more control over payment methods:
    • Organisations collecting through more than one account can assign a specific billing configuration to a payment method, or clear it. Read the docs: Assign and Clear payment methods.
    • Payment methods can be found and corrected by external reference, and listed by the collection module. Read the docs: Search, Update and List.
    • A policy's payments can be filtered by external reference. Read the docs.
  • Debit order payment method reliability: Adding a debit order payment method completes within a fixed time. An identical retry within 60 seconds returns the original payment method instead of creating a duplicate and charging a second verification fee. Read the docs.
  • Lapse rule timing: The missed billing periods lapse and not-taken-up rules support an optional number of days after the last missed billing date, so a policy can end sooner. Read the docs.
  • Proof of payment: Marking a payment as successful accepts an optional proof of payment (PDF, JPG or PNG). Any files attached to a payment are listed on its details. Read the docs.
  • Continued work on the policy ledger: Ongoing improvements include new memo entry types that show on a policy's ledger but are never invoiced.

Bug fixes

We’ve addressed key issues to improve system reliability:

• Module data links: Resolved an issue where links pointing back into the dashboard showed the full web address after their label.

• Archive attachments permission: Fixed an issue where an API key with only the archive attachments permission couldn't archive attachments on applications, claims and complaints.

• Billing bug fixes:

  • Resolved an issue where scheduled update requests (once-off premiums, billing day, start date and expiry) were actioned a day late for organisations ahead of UTC.
  • Fixed DebiCheck batches so that one payment without an authorised mandate no longer blocks the rest. A replacement mandate also takes over only once the bank approves it.
  • Fixed an issue where one invalid line in a DebiCheck mandate response file stopped the rest of the file from being applied.

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.