skills.rest
sammyTI
sammyTICOMMUNITY
Explore all skills by this author →
GitHub

break-trace

Trace GL and subledger entries to identify reconciliation discrepancy sources.

Updated May 3, 2026
Search Tags:#root cause#audit trail#reconciliation#subledger#financial discrepancy#GL
One-click install
npx skills add https://github.com/sammyTI/dotcompany-template --skill break-trace-sammyti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-trace
Source: https://github.com/sammyTI/dotcompany-template/tree/main/plugins/vertical-plugins/fund-admin/skills/break-trace
Command: npx skills add https://github.com/sammyTI/dotcompany-template --skill break-trace-sammyti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps identify the underlying source of reconciliation discrepancies in financial data by tracing and analyzing differences between GL and subledger entries.

Core Features & Use Cases

  • Source Investigation: Locate the originating transaction or posting from a reported break row in the general ledger system.
  • Difference Analysis: Compare key attributes such as posting date, FX rate, account mapping, and amount signs to determine causes of the break.
  • Use Case: Finance teams can employ this Skill to quickly identify whether timing, FX rates, or data mapping caused a reconciliation discrepancy, streamlining resolution.

Quick Start

Provide the break row information including key identifiers, GL values, subledger values, and likely cause, to diagnose the root reason for the break.

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 between my GL and subledger?▼

To identify the root cause of a reconciliation break, compare key attributes like posting dates, FX rates, and account mappings between GL and subledger entries to pinpoint the exact source of the financial discrepancy.

Why do my subledger and general ledger entries show a financial discrepancy?▼

Subledger and general ledger entries show a financial discrepancy due to data mismatches such as timing issues in posting dates, differences in FX rates applied, or incorrect account mapping during transaction posting.

What information do I need to provide to diagnose a reconciliation discrepancy?▼

To diagnose a reconciliation discrepancy, provide the break row information including key identifiers, GL values, subledger values, and the likely cause to analyze the difference and determine the underlying reason.

What is the best way to trace an audit trail break to its originating transaction?▼

The best way to trace an audit trail break is to analyze the break row information to locate the originating transaction or posting from the reported discrepancy in the general ledger system.

Can I use this to identify if an FX rate difference caused a financial break?▼

Yes, you can identify if an FX rate difference caused a financial break by comparing key attributes between the GL and subledger entries to determine if the data mismatch stems from applied exchange rates.

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
ViviennaMAOViviennaMAO
26

gl-recon

Reconcile general ledger and subledger data with Python.

Community
Advanced
iTzFaisaliTzFaisal

break-trace

Trace a break row to its GL entry and subledger transaction, then output a root-cause JSON.

Community
Intermediate