skills.rest
mouseqiao85
mouseqiao85COMMUNITY
Explore all skills by this author →
GitHub

break-trace

Trace reconciliation breaks to root causes by comparing GL and subledger transaction attributes.

1|Updated Feb 1, 2026
Search Tags:#root cause analysis#financial analysis#reconciliation#transaction tracing#break diagnosis
One-click install
npx skills add https://github.com/mouseqiao85/AI-Plat --skill break-trace-mouseqiao85
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-trace
Source: https://github.com/mouseqiao85/AI-Plat/tree/main/agent/skills/break-trace
Command: npx skills add https://github.com/mouseqiao85/AI-Plat --skill break-trace-mouseqiao85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users diagnose reconciliation breaks by tracing them back to their source transactions, providing a clear explanation of the root cause.

Core Features & Use Cases

  • Root Cause Analysis: Identify the root cause of reconciliation breaks, such as timing differences, FX rate discrepancies, or mapping errors.
  • Transaction Tracing: Trace the break back to the originating entry on each side (GL and subledger).
  • Attribute Comparison: Compare attributes like posting dates, FX rates, and account mappings to find the differing attribute causing the break.
  • Root Cause Statement: Provide a clear, concise root cause statement.
  • Output: Return the key, root cause, owner, expected clear date, and action required.

Quick Start

Trace the root cause of a reconciliation break identified by 'break-id-12345'.

Frequently Asked Questions about break-trace

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

FAQPage Schema
How do I diagnose reconciliation breaks in financial systems?▼

To diagnose reconciliation breaks, you trace them back to source transactions by comparing GL and subledger attributes like posting dates, FX rates, and account mappings to identify the exact root cause.

What causes reconciliation breaks between GL and subledger data?▼

Reconciliation breaks are caused by differing transaction attributes between the GL and subledger, typically involving timing differences, FX rate discrepancies, or account mapping errors.

How do I trace a financial transaction to find its root cause?▼

Financial transaction tracing requires comparing attributes on originating entries across both sides of the ledger to isolate the differing field, which generates a clear root cause statement.

Do I need GL and subledger data to perform transaction tracing?▼

Yes, transaction tracing requires access to both GL and subledger data to successfully compare transaction attributes and identify the specific discrepancy causing the reconciliation break.

What output should I expect from a root cause analysis of a reconciliation break?▼

A root cause analysis of a reconciliation break outputs a statement identifying the issue, along with the key, root cause, owner, expected clear date, and the specific action required.

Related Skills

Explore More Finance & Accounting Skills→
nvmohinaninvmohinani

break-trace

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

Community
Advanced
r9412460971-cloudr9412460971-cloud
31

break-trace

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

Community
Intermediate
sammyTIsammyTI

break-trace

Trace GL and subledger entries to identify reconciliation discrepancy sources.

Community
Advanced
anthropicsanthropics
34.1k

break-trace

Trace source transactions to identify root causes of reconciliation breaks.

Official
Intermediate