break-trace

Trace reconciliation breaks to originating source transactions with structured root-cause statements.

31|4|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/r9412460971-cloud/OPC-skill --skill break-trace-r9412460971-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: break-trace
Source: https://github.com/r9412460971-cloud/OPC-skill/tree/main/skills/break-trace
Command: npx skills add https://github.com/r9412460971-cloud/OPC-skill --skill break-trace-r9412460971-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a reconciliation break occurs between general ledger (GL) and subledger entries, manually tracing the root cause across systems is time-consuming, prone to human error, and delays break resolution. This Skill automates the diagnostic process to quickly identify the source of discrepancies.

Core Features & Use Cases

  • Cross-system trace: Pulls GL journal entries and matching subledger transactions via dedicated MCPs to align data from both sides.
  • Attribute diffing: Compares key attributes like posting dates, FX rates, account mappings, and amount signs to pinpoint the exact cause of the break.
  • Structured output: Generates standardized root-cause statements with clear owners, expected clear dates, and recommended actions for common break types including timing mismatches, FX discrepancies, mapping errors, and duplicate postings. Use Case: After the gl-recon skill classifies a break row, use this Skill to avoid hours of manual cross-system data lookup and get a clear, actionable root cause assessment.

Quick Start

Use the break-trace skill to root-cause the reconciliation break for key [your-break-key] that was classified by gl-recon.

Frequently Asked Questions about break-trace

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

FAQPage Schema
How do I root-cause reconciliation breaks between general ledger and subledger entries?

To root-cause reconciliation breaks between general ledger and subledger entries, you can automatically trace discrepancies across systems by pulling and diffing journal entries against subledger transactions to pinpoint exact causes.

What is the best way to identify the source of GL-recon timing mismatches and FX rate discrepancies?

Identifying GL-recon timing mismatches and FX rate discrepancies is done by comparing key attributes like posting dates, FX rates, and account mappings to generate standardized root-cause statements for each break.

Can I automatically generate assigned owners and expected clear dates for account mapping errors?

Yes, you can automatically generate assigned owners, expected clear dates, and recommended resolution actions for account mapping errors and duplicate postings through structured root-cause output.

Do I need pre-classified break rows from a reconciliation step before tracing discrepancies?

Yes, this tracing process applies to post-reconciliation audit workflows where break rows have been pre-classified by a prior reconciliation step, serving as the input for the diagnostic trace.

How does cross-system trace handle duplicate postings in finance operations?

Cross-system trace handles duplicate postings by pulling GL journal entries and matching subledger transactions via dedicated connections, then attribute diffing amount signs to pinpoint the exact duplicate.