One-click install
npx skills add https://github.com/executiveusa/Cheggie-trade-V2 --skill gl-recon-executiveusa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gl-recon
Source: https://github.com/executiveusa/Cheggie-trade-V2/tree/main/core/financial-skills/plugins/vertical-plugins/fund-admin/skills/gl-recon
Command: npx skills add https://github.com/executiveusa/Cheggie-trade-V2 --skill gl-recon-executiveusa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces time-consuming reconciliation effort by matching general ledger and subledger extracts and producing a clear report of where and why they don’t agree.

Core Features & Use Cases

  • Match and classify differences: Reconciles by the lowest shared key (e.g., security/account/trade date or journal line id) and categorizes breaks into matched, amount, quantity, timing, GL-only, or subledger-only.
  • Deterministic normalization: Coerces dates to ISO, amounts to two-decimal numerics, and identifiers to upper-stripped strings so comparisons are exact within defined tolerances.
  • Hypothesis-based cause tagging: Assigns a likely cause to each break (e.g., Timing, FX, Mapping, Duplicate/missing post, Fee/accrual, Data quality) to speed up resolution.
  • Use Case: Run daily or month-end recon for a specific entity, asset class, and trade date/period, then use the break report to drive sign-off and trace root causes.

Quick Start

Use the gl-recon skill to reconcile a GL extract and a subledger extract for the same entity, asset class, and trade date, then generate the break report and summary of match rates and likely causes.

Frequently Asked Questions about gl-recon

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

FAQPage Schema
How do I reconcile general ledger extracts to subledger data for month-end close?

General ledger reconciliation matches GL extracts to subledger extracts by the lowest shared key, categorizing breaks into matched, amount, quantity, timing, GL-only, or subledger-only buckets to produce a clear report of discrepancies.

What is the best way to classify GL reconciliation breaks by root cause?

GL reconciliation break classification applies hypothesis-based cause tagging to assign likely causes such as Timing, FX, Mapping, Duplicate or missing post, Fee or accrual, and Data quality to each break, speeding up resolution and sign-off.

Can I use this GL reconciliation process for daily trading workflows across multiple asset classes?

Yes, GL reconciliation applies to both daily and month-end workflows across asset classes, matching amounts, quantities, and timing that must agree across feeds for a specific entity and trade date or period.

Why do my GL and subledger amounts not match after normalization during reconciliation?

GL and subledger amounts may not match due to timing differences, FX delta analysis discrepancies, mapping errors, duplicate or missing posts, fee or accrual entries, or data quality issues identified during full-outer matching.

Does gl-recon require any specific data normalization before matching GL and subledger extracts?

Yes, gl-recon requires deterministic normalization that coerces dates to ISO format, amounts to two-decimal numerics, and identifiers to upper-stripped strings, ensuring comparisons are exact within defined tolerances.