Questions? We have answers.

October 2026 Release notes: Release 2

  • Updated

What’s new in MindBridge

This release introduces new ways to explore analysis results with AI, extends the Subledger workflow to support interim and year-end testing, and improves Data Table configuration and account mapping.

Functional capabilities


MindBridge MCP

MindBridge Model Context Protocol (MCP) connects a supported AI assistant to your MindBridge environment. Users can ask questions about completed analyses, explore risk scores and control points, and retrieve relevant transactions without manually exporting results.

MCP supports existing Audit and Enterprise engagements and provides read-only access within each user’s existing MindBridge permissions. Tenant Admins control who can connect and can revoke access at any time.

For more information about connecting an assistant and managing access, see MindBridge MCP: Overview and access management.

For more information about MCP, connecting an assistant, and managing access, visit the MindBridge Developer Portal.


Subledger interim analysis and rollforward sampling

Subledger now supports interim analysis and rollforward sampling, extending the existing General Ledger interim workflow to Subledger. Users can create an interim analysis, later convert it to a year-end analysis using full-year data, and retain access to interim results and sampling information.

Following the year-end analysis, users can limit the Data Table and sampling population to transactions after the interim end date. This reduces manual filtering and helps avoid selecting transactions from periods already covered by interim testing.

Interim analysis must be enabled for the applicable Subledger analysis template and library. This update does not include an Interim Rollforward Check report.

For more information about interim analysis and rollforward sampling, see Run an interim Subledger analysis and roll forward to year-end.


Saved Data Table configuration

Users can now save their Data Table column selection, order, and widths across sessions and browsers. Save for me stores a personal configuration, while Save for everyone allows an App Admin to set a shared configuration for an analysis.

Users can load their saved or shared layout, and exports reflect the configuration currently applied to the Data Table. Reset to default restores the standard configuration.

For more information about saving and applying Data Table configurations, see Save and manage Data Table configurations.


LLM account mapping improvements

The account mapping workflow now offers a clearer choice between reviewing LLM-generated suggestions and mapping accounts manually. Users can clear selected mappings or reset all LLM-generated mappings to continue manually, while retaining mappings they have manually added or edited.

A confirmation message and progress indicator provide feedback during a full reset. The Next button also remains visible when working with long account lists or smaller screens.

For more information about mapping your accounts, see Map accounts using LLM suggestions.

Was this article helpful?