skills.rest
nvmohinani
nvmohinaniCOMMUNITY
Explore all skills by this author →
GitHub

break-trace

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

Updated May 6, 2026
Search Tags:#reconciliation#data-integrity#audit-trail#gl#subledger#root-causes
One-click install
npx skills add https://github.com/nvmohinani/financial_services --skill break-trace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-trace
Source: https://github.com/nvmohinani/financial_services/tree/main/plugins/vertical-plugins/fund-admin/skills/break-trace
Command: npx skills add https://github.com/nvmohinani/financial_services --skill break-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root-cause reconciliation breaks by tracing to the originating GL posting and the matching subledger transaction to explain why a discrepancy occurred.

Core Features & Use Cases

  • Trace GL and subledger sides to identify the exact mismatch.
  • Generate a concise root-cause sentence suitable for audit tickets.
  • Integrate after GL reconciliation to complete the audit trail.

Quick Start

Trace the provided break to its GL posting and subledger transaction and produce a single-sentence root-cause explanation.

Frequently Asked Questions about break-trace

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

FAQPage Schema
How do I trace a reconciliation break from the GL posting to the source transaction?▼

A reconciliation break occurs when a GL posting does not match the source subledger transaction. Tracing the break involves comparing both sides to pinpoint the exact discrepancy, generating a root-cause sentence suitable for audit tickets and remediation planning.

What's the best way to identify the root cause of a GL reconciliation discrepancy?▼

You do not need specific external dependencies to identify reconciliation root causes, but you must have access to GL and subledger data sources. This access enables the tracing workflow to function and return a structured root-cause statement.

When do I need to trace a GL and subledger mismatch for an audit trail?▼

You need to trace a GL and subledger mismatch when completing an audit trail after GL reconciliation. Tracing to the originating posting explains why a discrepancy occurred and supports issue resolution and remediation planning across financial postings.

Can I generate an audit-ready root cause statement for a subledger reconciliation break?▼

Tracing a reconciliation break requires access to both GL and subledger data sources. Without this access, the workflow cannot compare both sides to identify the exact mismatch or produce the structured root-cause statement for remediation planning.

Related Skills

Explore More Finance & Accounting Skills→
mouseqiao85mouseqiao85
1

break-trace

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

Community
Intermediate
lm93129lm93129
2

report-drafting

Generate audit report drafts from audit results and misstatements per CSA 1501~1504.

Community
Advanced
ViviennaMAOViviennaMAO
26

break-trace

Compare GL and subledger data to trace reconciliation breaks to source transactions.

Community
Intermediate
lm93129lm93129
2

analytical-review

Analyze financial statements to identify anomalies and evaluate reasonableness.

Community
Intermediate