break-trace

Diagnose root causes of financial reconciliation breaks across GL and subledger systems.

Updated May 10, 2026
One-click install
npx skills add https://github.com/rpoole-dev/comps-site --skill break-trace-rpoole-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: break-trace
Source: https://github.com/rpoole-dev/comps-site/tree/main/financial-services-main/plugins/vertical-plugins/fund-admin/skills/break-trace
Command: npx skills add https://github.com/rpoole-dev/comps-site --skill break-trace-rpoole-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies the root causes of reconciliation breaks in financial data, streamlining the audit process by tracing transactions back to their origins.

Core Features & Use Cases

  • Root Cause Analysis: Follow the audit trail from break rows back to the originating entry, comparing GL and subledger information.
  • Cause Statement Generation: Formulate concise, single-sentence root cause statements following a structured format.
  • Output: Returns detailed diagnostics for each traced break, including expected clear date and action to take.
  • Use Case: After the gl-recon classifies a reconciliation break, use this Skill to diagnose the root cause and provide necessary guidance.

Quick Start

Execute the 'break-trace' Skill to analyze the break and produce a root cause statement for the identified issue.

Frequently Asked Questions about break-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of financial reconciliation breaks between GL and subledger systems?

Root cause analysis for reconciliation breaks traces audit trails from break rows back to originating entries, comparing GL and subledger data to identify attribute discrepancies. It formulates concise cause statements and outputs diagnostics including expected clear dates and necessary actions.

What is the best way to generate audit trail diagnostics for reconciliation breaks?

Generating audit trail diagnostics requires tracing break rows back to originating entries across GL and subledgers. This process compares transaction attributes, formulates single-sentence cause statements, and outputs detailed diagnostics with expected clear dates and actions to take.

Do I need classified break data before diagnosing root causes in financial data?

Diagnosing root causes requires classified break data within financial reconciliation workflows. You trace audit trails from classified break rows back to originating entries, comparing GL and subledger attributes to output cause statements, expected clear dates, and corrective actions.

How does root cause analysis compare attributes for discrepancies in financial reconciliation?

Root cause analysis compares attributes for discrepancies by analyzing journal entries, postings, and transactions across GL and subledger systems. It identifies mismatches, follows audit trails from break rows to originating entries, and formulates structured single-sentence cause statements.

What output should I expect when tracing reconciliation breaks back to their originating entries?

Tracing reconciliation breaks back to originating entries outputs detailed diagnostics for each traced break. These diagnostics include a concise single-sentence root cause statement, the expected clear date, and the specific action to take to resolve the discrepancy.