
Reconciliation
Run structured GL-to-subledger, bank, or intercompany reconciliations and categorize reconciling items before period close.
Overview
Reconciliation is an agent skill for the Operate phase that guides GL-to-subledger, bank, and intercompany account reconciliations and reconciling-item analysis.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill reconciliationWhat is this skill?
- GL-to-subledger methodology for AR, AP, fixed assets, inventory, prepaids, and accruals
- Bank reconciliation process from statement import through outstanding checks and deposits in transit
- Intercompany pairing rules and reconciling-item categorization with escalation guidance
- Explicit disclaimer that output requires qualified financial professional review
- Covers six common GL-to-subledger control account patterns listed in the skill body
Adoption & trust: 1.7k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your period-end GL control account does not match the bank, subledger, or intercompany schedule and you need a consistent investigation workflow.
Who is it for?
Indie SaaS founders or small teams closing books who want agent-assisted rec checklists tied to specific accounts and periods.
Skip if: Builders seeking tax advice, automated payment signing, or product engineering tasks unrelated to ledger tie-out.
When should I use this skill?
Performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
What do I get? / Deliverables
You get a documented reconciliation approach with categorized variances, aging notes, and escalation triggers ready for a qualified reviewer’s sign-off.
- Reconciliation workpaper outline with variance explanations
- Categorized reconciling items with aging and escalation notes
Recommended Skills
Journey fit
Reconciliation is recurring close and control work after you are operating a business with real ledgers and bank feeds. Iterate subphase covers ongoing accounting hygiene—matching balances, aging exceptions, and escalation—not greenfield product build.
How it compares
Methodology skill for finance close workflows—not a live bank API integration or crypto wallet connector.
Common Questions / FAQ
Who is reconciliation for?
Solo builders and small finance leads who perform bank, GL-to-subledger, or intercompany reconciliations and want structured agent assistance before professional review.
When should I use reconciliation?
During operate iterate at month or quarter end when comparing GL balances to AR/AP aging, bank statements, or intercompany schedules for a named account and period.
Is reconciliation safe to install?
It does not move money by itself, but it may process sensitive financial exports—review the Security Audits panel on this page and restrict ledger data in agent sessions.
SKILL.md
READMESKILL.md - Reconciliation
# Reconciliation **Important**: This skill assists with reconciliation workflows but does not provide financial advice. All reconciliations should be reviewed by qualified financial professionals before sign-off. Methodology and best practices for account reconciliation, including GL-to-subledger, bank reconciliations, and intercompany. Covers reconciling item categorization, aging analysis, and escalation. ## Reconciliation Types ### GL to Subledger Reconciliation Compare the general ledger control account balance to the detailed subledger balance. **Common accounts:** - Accounts receivable (GL control vs AR subledger aging) - Accounts payable (GL control vs AP subledger aging) - Fixed assets (GL control vs fixed asset register) - Inventory (GL control vs inventory valuation report) - Prepaid expenses (GL control vs prepaid amortization schedule) - Accrued liabilities (GL control vs accrual detail schedules) **Process:** 1. Pull GL balance for the control account as of period end 2. Pull subledger trial balance or detail report as of the same date 3. Compare totals — they should match if posting is real-time 4. Investigate any differences (timing of posting, manual entries not reflected, interface errors) **Common causes of differences:** - Manual journal entries posted to the control account but not reflected in the subledger - Subledger transactions not yet interfaced to the GL - Timing differences in batch posting - Reclassification entries in the GL without subledger adjustment - System interface errors or failed postings ### Bank Reconciliation Compare the GL cash balance to the bank statement balance. **Process:** 1. Obtain the bank statement balance as of period end 2. Pull the GL cash account balance as of the same date 3. Identify outstanding checks (issued but not cleared at the bank) 4. Identify deposits in transit (recorded in GL but not yet credited by bank) 5. Identify bank charges, interest, or adjustments not yet recorded in GL 6. Reconcile both sides to an adjusted balance **Standard format:** ``` Balance per bank statement: $XX,XXX Add: Deposits in transit $X,XXX Less: Outstanding checks ($X,XXX) Add/Less: Bank errors $X,XXX Adjusted bank balance: $XX,XXX Balance per general ledger: $XX,XXX Add: Interest/credits not recorded $X,XXX Less: Bank fees not recorded ($X,XXX) Add/Less: GL errors $X,XXX Adjusted GL balance: $XX,XXX Difference: $0.00 ``` ### Intercompany Reconciliation Reconcile balances between related entities to ensure they net to zero on consolidation. **Process:** 1. Pull intercompany receivable/payable balances for each entity pair 2. Compare Entity A's receivable from Entity B to Entity B's payable to Entity A 3. Identify and resolve differences 4. Confirm all intercompany transactions have been recorded on both sides 5. Verify elimination entries are correct for consolidation **Common causes of differences:** - Transactions recorded by one entity but not the other (timing) - Different FX rates used by each entity - Misclassification (intercompany vs third-party) - Disputed amounts or unapplied payments - Different period-end cut-off practices across entities ## Reconciling Item Categorization ### Category 1: Timing Differences Items that exist because of normal processing timing and will clear without action: - **Outstanding checks:** Checks issued and recorded in GL, pending bank clearance - **Deposits in transit:** Deposits made and recorded in GL, pending bank credit - **In-transit transactions:** Items posted in one system but