Break Trace is a specialized skill designed to assist financial operations teams in diagnosing reconciliation breaks by tracing them back to their source transactions. After a break has been classified by the general ledger reconciliation process, this skill enables users to pull detailed information from both the general ledger (GL) and the subledger. By following a structured trace path, users can identify discrepancies between the two sides and understand the underlying causes of the breaks.

The skill operates through a series of defined steps. First, it retrieves the relevant GL side data using the internal GL MCP, which includes essential details such as the journal entry, posting date, source system, and preparer information. Next, it accesses the corresponding subledger transaction data, providing insights into trade details, counterparty information, and the foreign exchange rates applied. By comparing these attributes, users can pinpoint the specific differences that led to the reconciliation break.

Once the differences are identified, Break Trace generates a concise root-cause statement that summarizes the issue in a clear format. This statement follows a specific structure, enabling teams to quickly grasp what went wrong and why. For instance, it might indicate timing issues, mapping discrepancies, or duplicate postings. The output is structured in a JSON format, providing a clear and actionable summary for further processing by the appropriate teams.

This skill is particularly valuable for financial analysts, accountants, and operations teams who deal with complex reconciliations and need a reliable method to trace and diagnose issues efficiently. By automating the root-cause analysis process, Break Trace saves time and reduces the potential for errors in manual investigations.