gl-recon

Reconcile general ledger entries to subledger records and output prioritized break reports.

31|4|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/r9412460971-cloud/OPC-skill --skill gl-recon-r9412460971-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gl-recon
Source: https://github.com/r9412460971-cloud/OPC-skill/tree/main/skills/gl-recon
Command: npx skills add https://github.com/r9412460971-cloud/OPC-skill --skill gl-recon-r9412460971-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual general ledger to subledger reconciliation is time-consuming, error-prone, and difficult to track unreconciled breaks across asset classes for daily operational runs or month-end financial closes.

Core Features & Use Cases

  • Automated Normalization: Aligns GL and subledger extracts to a common key and comparison columns with exact type coercion for accurate matching.
  • Structured Break Matching: Full-outer joins records into defined break buckets (matched, amount break, quantity break, timing break, GL-only, subledger-only) with configurable amount tolerance.
  • Root Cause Classification: Tags each break with a probable cause (timing, FX, mapping, duplicate/missing post, fee/accrual, data quality) to accelerate resolution.
  • Use Case: For fund operations and accounting teams, this skill eliminates manual cross-checking of thousands of transaction lines during NAV tie-outs or month-end closes, delivering a prioritized break report for quick resolution.

Quick Start

Use the gl-recon skill to reconcile the Q3 general ledger extract against the corresponding subledger extract for the fixed income portfolio and generate a break report sorted by material amount deltas.

Frequently Asked Questions about gl-recon

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

FAQPage Schema
How do I automate general ledger to subledger reconciliation for month-end close?

General ledger to subledger reconciliation is automated by normalizing extracts into common keys, full-outer joining records into break buckets, and outputting a prioritized report with root cause tags for fast sign-off.

What is the best way to classify unreconciled breaks during a NAV tie-out?

Unreconciled breaks are classified by matching records into defined buckets like amount, quantity, and timing breaks, then tagging each with probable root causes such as FX, mapping, or duplicate posts to accelerate resolution.

Can I reconcile GL entries at both the transaction and position level across asset classes?

Yes, GL reconciliation supports matching at both the transaction and position level across all asset classes for specified trade dates or accounting periods during daily operational runs.

How do I handle timing breaks and amount tolerances when reconciling fund operations extracts?

Timing breaks and amount tolerances are handled using configurable amount tolerance settings that full-outer join GL and subledger records into structured break buckets for operational reconciliation.

Does this reconciliation approach work for daily operational runs and month-end financial closes?

Yes, this reconciliation approach applies to both daily operational reconciliation runs and month-end financial close workflows, surfacing unreconciled breaks and generating summary metrics for accounting sign-off.

Why do I have GL-only and subledger-only breaks during account reconciliation?

GL-only and subledger-only breaks occur during account reconciliation when records fail to match across extracts, which are categorized into specific break buckets and tagged with probable data quality or missing post causes.