Back to Workflow & Productivity

Account Reconciliation

accountingfinancereconciliationledgercompliance
20.9k📄 Apache-2.0🕒 2026-06-16✓ OfficialSource ↗

Install this skill

npx skills add anthropics/knowledge-work-plugins

Works across Claude Code, Cursor, Codex, Copilot & Antigravity

The Reconciliation skill provides a structured framework for validating financial data consistency between disparate systems. It assists accounting and finance professionals by automating the comparison of General Ledger (GL) balances against subledgers, bank statements, and intercompany records. Instead of relying on manual spreadsheet tracking, this tool identifies discrepancies, flags timing differences, and categorizes adjustments. It standardizes the workflow for month-end close procedures, ensuring that outstanding items are tracked through aging analysis and properly escalated when necessary. By providing a repeatable process for identifying, classifying, and resolving variances—such as unrecorded interest, timing delays in deposits, or posting errors—this skill minimizes manual effort while maintaining audit-ready documentation. It creates a clear audit trail by distinguishing between items requiring immediate correction and those that resolve naturally through standard processing cycles.
By anthropics

What this skill does

  • Automatic matching of GL balances against subledger trial balances
  • Standardized bank reconciliation reporting for outstanding checks and deposits
  • Cross-entity intercompany balance verification and elimination tracking
  • Systematic categorization of reconciling items into timing, adjustment, and investigation buckets
  • Aging analysis for long-standing unreconciled transactions

When to use it

  • Performing standard monthly bank statement verification
  • Validating AR and AP subledgers against the general ledger control accounts
  • Resolving discrepancies between related corporate entity balance sheets
  • Investigating unidentified variance spikes in financial reports

When not to use it

  • Performing primary financial reporting or preparing tax filings
  • Validating transaction data that has not yet been exported to the source system
  • Acting as a final sign-off authority for audited financial statements

How to invoke it

Example prompts that trigger this skill:

  • Reconcile the cash GL account with the latest bank statement file.
  • Identify discrepancies between the Accounts Receivable subledger and GL control account.
  • Check intercompany balances between Entity A and Entity B for this period.
  • Categorize the outstanding items in this report into timing differences and required adjustments.
  • Generate an aging report for all unresolved reconciling items from last month.

Example workflow

  1. Export period-end GL trial balance and subledger data.
  2. Run the reconciliation skill to perform the initial aggregate comparison.
  3. Review generated category report for timing differences versus actionable errors.
  4. Apply required adjustments for missing fees or bank charges as identified.
  5. Flag aged items requiring human investigation and internal escalation.

Prerequisites

  • Access to period-end general ledger and subledger reports
  • Bank statement exports in CSV or machine-readable format

Pitfalls & limitations

  • !Does not replace professional judgment for complex dispute resolution
  • !Requires high-quality source data to prevent false positive variance alerts
  • !Cannot detect errors if both the GL and subledger contain identical incorrect entries

FAQ

Does this tool provide financial advice?
No, this skill provides a workflow framework and does not provide financial or accounting advice.
How do I handle items that do not match?
The skill classifies items into timing differences, adjustments, or investigations, allowing you to focus your efforts on the items that require manual intervention.
Is this safe for use with sensitive financial data?
The tool is clean and follows standard data handling practices, though users should always follow their company's specific security protocols regarding financial data privacy.

How it compares

Unlike a generic prompt, this skill embeds specialized accounting logic for categorizing variances, ensuring consistent treatment of timing differences versus genuine entry errors.

Source & trust

21k stars📄 Apache-2.0🕒 Updated 2026-06-16🛡 no risky patterns found✓ Official source

From the source: “# 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, b…”

View the full SKILL.md source

# 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 pending interface to the other
- **Pending approvals:** Transactions awaiting approval to post in one system

**Expected resolution:** These items should clear within the normal processing cycle (typically 1-5 business days). No adjusting entry needed.

### Category 2: Adjustments Required

Items that require a journal entry to correct:

- **Unrecorded bank charges:** Bank fees, wire charges, returned item fees
- **Unrecorded interest:** Interest income or expense from bank/lender
- **Recording errors:** Wrong amount, wrong account, duplicates
- **Missing entries:** Transactions in one system with no corresponding entry in the other
- **Classification errors:** Correctly recorded but in the wrong account

**Action:** Prepare adjusting journal entry to correct the GL or subledger.

### Category 3: Requires Investigation

Items that cannot be immediately explained:

- **Unidentified differences:** Variances with no obvious cause
- **Disputed items:** Amounts contested between parties
- **Aged outstanding items:** Items that have not cleared within expected timeframes
- **Recurring unexplained differences:** Same type of difference appearing each period

**Action:** Investigate root cause, document findings, escalate if unresolved.

## Aging Analysis for Outstanding Items

Track the age of reconciling items to identify stale items requiring escalation:

| Age Bucket | Status | Action |
|-----------|--------|--------|
| 0-30 days | Current | Monitor — within normal processing cycle |
| 31-60 days | Aging | Investigate — follow up on why item has not cleared |
| 61-90 days | Overdue | Escalate — notify supervisor, document investigation |
| 90+ days | Stale | Escalate to management — potential write-off or adjustment needed |

### Aging Report Format

| Item # | Description | Amount | Date Originated | Age (Days) | Category | Status | Owner |
|--------|-------------|--------|-----------------|------------|----------|--------|-------|
| 1      | [Detail]    | $X,XXX | [Date]          | XX         | [Type]   | [Status] | [Name] |

### Trending

Track reconciling item totals over time to identify growing balances:

- Compare total outstanding items to prior period
- Flag if total reconciling items exceed materiality threshold
- Flag if number of items is growing period over period
- Identify recurring items that appear every period (may indicate process issue)

## Escalation Thresholds

Define escalation triggers based on your organization's risk tolerance:

| Trigger | Threshold (Example) | Escalation |
|---------|---------------------|------------|
| Individual item amount | > $10,000 | Supervisor review |
| Individual item amount | > $50,000 | Controller review |
| Total reconciling items | > $100,000 | Controller review |
| Item age | > 60 days | Supervisor follow-up |
| Item age | > 90 days | Controller / management review |
| Unreconciled difference | Any amount | Cannot close — must resolve or document |
| Growing trend | 3+ consecutive periods | Process improvement investigation |

*Note: Set thresholds based on your organization's materiality level and risk appetite. The examples above are illustrative.*

## Reconciliation Best Practices

1. **Timeliness:** Complete reconciliations within the close calendar deadline (typically T+3 to T+5 business days after period end)
2. **Completeness:** Reconcile all balance sheet accounts on a defined frequency (monthly for material accounts, quarterly for immaterial)
3. **Documentation:** Every reconciliation should include preparer, reviewer, date, and clear explanation of all reconciling items
4. **Segregation:** The person who reconciles should not be the same person who processes transactions in that account
5. **Follow-through:** Track open items to resolution — do not just carry items forward indefinitely
6. **Root cause analysis:** For recurring reconciling items, investigate and fix the underlying process issue
7. **Standardization:** Use consistent templates and procedures across all accounts
8. **Retention:** Maintain reconciliations and supporting detail per your organization's document retention policy

Quoted from anthropics/knowledge-work-plugins for reference — see the original for the authoritative, latest version.

How to Use This Skill Unit

Option A: Project-Specific (Recommended)

  1. Click "Download" above
  2. In your project, create the directory: .agent/skills/reconciliation/
  3. Save the file as SKILL.md
  4. The agent will automatically discover the skill based on its description.

Option B: Global Installation (All Agents)

Save the file to these locations to make it available across all projects:

  • Claude Code: ~/.claude/skills/anthropics/knowledge-work-plugins/reconciliation/SKILL.md
  • Cursor: ~/.cursor/skills/anthropics/knowledge-work-plugins/reconciliation/SKILL.md
  • Antigravity: ~/.gemini/antigravity/skills/anthropics/knowledge-work-plugins/reconciliation/SKILL.md

🚀 Install with CLI:
npx skills add anthropics/knowledge-work-plugins

Read the Master Guide: Mastering Agent Skills

Recommended Rules

View more rules

Recommended Workflows

View more workflows

Recommended MCP Servers

View more MCP servers

Take It Further

Maximize your productivity with these powerful resources

📋

Define Your Standards

Set up coding standards to ensure this workflow produces consistent, high-quality results.

Browse Rules Library
📖

Master Workflows

Learn how to create custom workflows, use Turbo Mode, and build your automation library.

Complete Guide

How to use this Skill in Claude Code & Cursor

For Claude Code (CLI)

To use this skill in Claude Code, copy the rule content into your project's custom instructions or follow our Add-Skill CLI guide. This ensures Claude follows your standards during every code generation.

For Cursor & Windsurf

For Cursor or Windsurf, individual skills are best used in the "Rules for AI" section. This specific unit helps the agent avoid workflow & productivity issues, leading to cleaner, more efficient code.

Why the skill format matters: the standardized Agent Skills format lets your AI agent load detailed instructions only when they are relevant, keeping your prompt clean while improving results.

Source & attribution

This skill is categorized under Workflow & Productivity and is published by anthropics, maintained in anthropics/knowledge-work-plugins.

← Browse All Agent Skills
Sponsored AI assistant. Recommendations may be paid.