skills.rest
executiveusa
executiveusaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

break-trace

Trace reconciliation breaks to originating GL postings and subledger transactions.

1|Updated May 16, 2026
Search Tags:#root cause analysis#audit trail#reconciliation#account mapping#fund administration#fx mismatch#journal tracing
One-click install
npx skills add https://github.com/executiveusa/Cheggie-trade-V2 --skill break-trace-executiveusa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-trace
Source: https://github.com/executiveusa/Cheggie-trade-V2/tree/main/core/financial-skills/plugins/vertical-plugins/fund-admin/skills/break-trace
Command: npx skills add https://github.com/executiveusa/Cheggie-trade-V2 --skill break-trace-executiveusa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconciliation breaks are often hard to explain because the mismatch could originate from timing, FX rates, account mapping, or duplicate postings; this Skill traces a break back to the originating GL and subledger source so you can state the exact reason.

Core Features & Use Cases

  • GL-to-source tracing: Pull the GL journal entry or posting that produced the specific GL line (entry id, posting date, source system, batch id, preparer).
  • Subledger-to-source tracing: Pull the matching trade/settlement transaction (trade id, trade/settle dates, counterparty, source feed, FX rate used).
  • Attribute diff root-cause: Compare key attributes (posting/settle dates, FX rate/date, account mapping, quantity sign, amount sign) and convert the observed difference into a one-sentence cause statement.

Use case: After gl-recon classifies a break row, use break-trace to determine whether the break is caused by timing differences, an FX rate mismatch, a mapping error to the wrong account, or a duplicate post in the subledger.

Quick Start

Use the break-trace skill to trace a specific reconciliation break row back to its GL and subledger sources, then return a one-sentence root-cause statement and recommended next action.

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 a reconciliation break?▼

Root cause analysis for a reconciliation break involves tracing the break row to its originating GL posting and matching subledger transaction, diffing attributes like posting dates and FX rates, and emitting a structured cause statement.

Why does my GL reconciliation have an FX rate mismatch?▼

An FX rate mismatch in GL reconciliation happens when the FX rate or date in the GL posting differs from the subledger transaction. Diffing these specific attributes reveals the discrepancy.

How do I trace a GL journal entry to a subledger transaction for fund administration?▼

To trace a GL journal entry to a subledger transaction for fund administration, fetch source data from internal GL and subledger systems, then compare trade and settlement dates against the applied FX rate.

Can I identify duplicate postings and account mapping errors in an audit trail?▼

Yes, identify duplicate postings and account mapping errors in an audit trail by diffing posting attributes and account mappings between the GL source and subledger transactions to pinpoint the exact anomaly.

What is the best way to resolve timing discrepancies in reconciliation breaks?▼

Resolve timing discrepancies in reconciliation breaks by tracing the break to its GL and subledger sources, comparing posting and settle dates, and outputting an expected clear date with a recommended action.

Do I need classified break rows before tracing reconciliation breaks?▼

Yes, classified break rows from a GL reconciliation process are required before tracing reconciliation breaks, because this Skill applies after classification to root-cause the break by tracing it to its sources.

Related Skills

Explore More Finance & Accounting Skills→
nvmohinaninvmohinani

break-trace

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

Community
Advanced
krzemienskikrzemienski
2

root-cause-tracing

Trace execution errors backward through call chains to identify root causes.

Community
Advanced
rpoole-devrpoole-dev

break-trace

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

Community
Intermediate
r9412460971-cloudr9412460971-cloud
31

break-trace

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

Community
Intermediate