skills.rest
Timmy6942025
Timmy6942025COMMUNITY
Explore all skills by this author →
GitHub

break-trace

Trace reconciliation breaks by comparing GL and subledger transaction attributes.

3|Updated May 30, 2026
Search Tags:#root cause analysis#financial reconciliation#GL reconciliation#subledger comparison#break tracing
One-click install
npx skills add https://github.com/Timmy6942025/open-financial-agents --skill break-trace-timmy6942025
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-trace
Source: https://github.com/Timmy6942025/open-financial-agents/tree/main/src/agent-skills/gl-reconciler/skills/break-trace
Command: npx skills add https://github.com/Timmy6942025/open-financial-agents --skill break-trace-timmy6942025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps in diagnosing and resolving reconciliation breaks in financial records by tracing their root cause back to the originating transaction.

Core Features & Use Cases

  • Root Cause Analysis: Trace the source transaction for reconciliation breaks and compare it against subledger information.
  • Attribute Diffing: Compare GL and subledger side attributes such as dates, FX rates, and account mappings.
  • Output Reporting: Generate a structured output with key details like key, root cause, owner, expected clear date, and action required.

Quick Start

Utilize the 'break-trace' skill by providing a single break row for analysis.

Frequently Asked Questions about break-trace

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

FAQPage Schema
How do I trace the root cause of a financial reconciliation break?▼

To trace the root cause of a financial reconciliation break, compare General Ledger and subledger transaction attributes. This analysis identifies originating source transactions and generates a detailed report on the issue and required resolution steps.

What is GL and subledger attribute diffing in financial reconciliation?▼

GL and subledger attribute diffing compares transaction attributes like dates, FX rates, and account mappings between the General Ledger and subledger. This comparison highlights specific mismatches causing reconciliation breaks for further investigation.

How do I resolve General Ledger reconciliation breaks with subledger data?▼

Resolve General Ledger reconciliation breaks by analyzing a single break row against subledger information. This traces originating source transactions and produces a structured output detailing the root cause, owner, and expected clear date.

Can I use break tracing for daily financial reconciliation diagnostics?▼

Yes, you can use break tracing for financial reconciliation diagnostics by providing a single break row for analysis. The process compares GL and subledger attributes to identify transaction mismatches and output resolution actions.

What details are included in a financial reconciliation break report?▼

A financial reconciliation break report includes key details such as the break key, root cause, owner, expected clear date, and required action. This structured output directly results from tracing GL and subledger transaction mismatches.

Related Skills

Explore More Finance & Accounting Skills→
Duzhenyang111Duzhenyang111

gl-recon

Reconcile general ledger and subledger accounts and generate break reports.

Community
Advanced
Duzhenyang111Duzhenyang111

break-trace

Compare GL and subledger data to diagnose reconciliation breaks.

Community
Advanced
nvmohinaninvmohinani

break-trace

Trace GL postings to source transactions and generate root-cause statements.

Community
Advanced
EvolutionAPIEvolutionAPI
520

fin-reconciliation

Reconcile GL balances with subledger and bank data to identify mismatches.

Official
Advanced