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.