Skill Tracer
Skills › Knowledge Work Plugins › reconciliation

reconciliation

skill · 175 lines · Apache-2.0 · finance/skills/reconciliation/SKILL.md

The facts

Its description

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

A person asks for help reconciling an account — a bank reconciliation, a GL-to-subledger rec, or an intercompany rec — or asks how to categorize, age, or escalate the differences that come out of one. The description names those exact tasks, so a request framed around any of them would pull this skill in.

Things a person might say (the model's guesses)

  • “Can you help me do the bank reconciliation for our operating account for last month?”
  • “Our AR subledger doesn't tie to the GL control account — walk me through reconciling it.”
  • “The intercompany balances between our US and UK entities don't net to zero. How do I work through the differences?”

A model's summary of when it is used.

A model's reading

What it takes when started

<account> [period]

What to type after its name when you start it.

From its settingsline 4

What it leads to

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

Licence

Apache-2.0, from finance/LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: reconciliation
3description: Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
4argument-hint: "<account> [period]"
5---
6
7# Reconciliation
8
9**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.
11Methodology and best practices for account reconciliation, including GL-to-subledger, bank reconciliations, and intercompany. Covers reconciling item categorization, aging analysis, and escalation.

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.

Raw lines 1 to 12
13## Reconciliation Types

Reconciliation Types

Raw lines 13 to 14
15### GL to Subledger Reconciliation
17Compare the general ledger control account balance to the detailed subledger balance.
19**Common accounts:**
20- Accounts receivable (GL control vs AR subledger aging)
21- Accounts payable (GL control vs AP subledger aging)
22- Fixed assets (GL control vs fixed asset register)
23- Inventory (GL control vs inventory valuation report)
24- Prepaid expenses (GL control vs prepaid amortization schedule)
25- Accrued liabilities (GL control vs accrual detail schedules)
27**Process:**
281. Pull GL balance for the control account as of period end
292. Pull subledger trial balance or detail report as of the same date
303. Compare totals — they should match if posting is real-time
314. Investigate any differences (timing of posting, manual entries not reflected, interface errors)
33**Common causes of differences:**
34- Manual journal entries posted to the control account but not reflected in the subledger
35- Subledger transactions not yet interfaced to the GL
36- Timing differences in batch posting
37- Reclassification entries in the GL without subledger adjustment
38- System interface errors or failed postings

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
Raw lines 15 to 39
40### Bank Reconciliation
42Compare the GL cash balance to the bank statement balance.
44**Process:**
451. Obtain the bank statement balance as of period end
462. Pull the GL cash account balance as of the same date
473. Identify outstanding checks (issued but not cleared at the bank)
484. Identify deposits in transit (recorded in GL but not yet credited by bank)
495. Identify bank charges, interest, or adjustments not yet recorded in GL
506. Reconcile both sides to an adjusted balance
52**Standard format:**
54```
55Balance per bank statement: $XX,XXX
56Add: Deposits in transit $X,XXX
57Less: Outstanding checks ($X,XXX)
58Add/Less: Bank errors $X,XXX
59Adjusted bank balance: $XX,XXX
61Balance per general ledger: $XX,XXX
62Add: Interest/credits not recorded $X,XXX
63Less: Bank fees not recorded ($X,XXX)
64Add/Less: GL errors $X,XXX
65Adjusted GL balance: $XX,XXX
67Difference: $0.00
68```

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
Raw lines 40 to 69
70### Intercompany Reconciliation
72Reconcile balances between related entities to ensure they net to zero on consolidation.
74**Process:**
751. Pull intercompany receivable/payable balances for each entity pair
762. Compare Entity A's receivable from Entity B to Entity B's payable to Entity A
773. Identify and resolve differences
784. Confirm all intercompany transactions have been recorded on both sides
795. Verify elimination entries are correct for consolidation
81**Common causes of differences:**
82- Transactions recorded by one entity but not the other (timing)
83- Different FX rates used by each entity
84- Misclassification (intercompany vs third-party)
85- Disputed amounts or unapplied payments
86- Different period-end cut-off practices across entities

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
Raw lines 70 to 87
88## Reconciling Item Categorization

Reconciling Item Categorization

Raw lines 88 to 89
90### Category 1: Timing Differences
92Items that exist because of normal processing timing and will clear without action:
94- **Outstanding checks:** Checks issued and recorded in GL, pending bank clearance
95- **Deposits in transit:** Deposits made and recorded in GL, pending bank credit
96- **In-transit transactions:** Items posted in one system but pending interface to the other
97- **Pending approvals:** Transactions awaiting approval to post in one system
99**Expected resolution:** These items should clear within the normal processing cycle (typically 1-5 business days). No adjusting entry needed.

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.

Raw lines 90 to 100
101### Category 2: Adjustments Required
103Items that require a journal entry to correct:
105- **Unrecorded bank charges:** Bank fees, wire charges, returned item fees
106- **Unrecorded interest:** Interest income or expense from bank/lender
107- **Recording errors:** Wrong amount, wrong account, duplicates
108- **Missing entries:** Transactions in one system with no corresponding entry in the other
109- **Classification errors:** Correctly recorded but in the wrong account

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.

Raw lines 101 to 112
Names a skill journal-entry :111
113### Category 3: Requires Investigation
115Items that cannot be immediately explained:
117- **Unidentified differences:** Variances with no obvious cause
118- **Disputed items:** Amounts contested between parties
119- **Aged outstanding items:** Items that have not cleared within expected timeframes
120- **Recurring unexplained differences:** Same type of difference appearing each period
122**Action:** Investigate root cause, document findings, escalate if unresolved.

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.

Raw lines 113 to 123
124## Aging Analysis for Outstanding Items
126Track the age of reconciling items to identify stale items requiring escalation:
128| Age Bucket | Status | Action |
129|-----------|--------|--------|
130| 0-30 days | Current | Monitor — within normal processing cycle |
131| 31-60 days | Aging | Investigate — follow up on why item has not cleared |
132| 61-90 days | Overdue | Escalate — notify supervisor, document investigation |
133| 90+ days | Stale | Escalate to management — potential write-off or adjustment needed |

Aging Analysis for Outstanding Items

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

Age BucketStatusAction
0-30 daysCurrentMonitor — within normal processing cycle
31-60 daysAgingInvestigate — follow up on why item has not cleared
61-90 daysOverdueEscalate — notify supervisor, document investigation
90+ daysStaleEscalate to management — potential write-off or adjustment needed
Raw lines 124 to 134
135### Aging Report Format
137| Item # | Description | Amount | Date Originated | Age (Days) | Category | Status | Owner |
138|--------|-------------|--------|-----------------|------------|----------|--------|-------|
139| 1 | [Detail] | $X,XXX | [Date] | XX | [Type] | [Status] | [Name] |

Aging Report Format

Item #DescriptionAmountDate OriginatedAge (Days)CategoryStatusOwner
1[Detail]$X,XXX[Date]XX[Type][Status][Name]
Raw lines 135 to 140
141### Trending
143Track reconciling item totals over time to identify growing balances:
145- Compare total outstanding items to prior period
146- Flag if total reconciling items exceed materiality threshold
147- Flag if number of items is growing period over period
148- Identify recurring items that appear every period (may indicate process issue)

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)
Raw lines 141 to 149
150## Escalation Thresholds
152Define escalation triggers based on your organization's risk tolerance:
154| Trigger | Threshold (Example) | Escalation |
155|---------|---------------------|------------|
156| Individual item amount | > $10,000 | Supervisor review |
157| Individual item amount | > $50,000 | Controller review |
158| Total reconciling items | > $100,000 | Controller review |
159| Item age | > 60 days | Supervisor follow-up |
160| Item age | > 90 days | Controller / management review |
161| Unreconciled difference | Any amount | Cannot close — must resolve or document |
162| Growing trend | 3+ consecutive periods | Process improvement investigation |
164*Note: Set thresholds based on your organization's materiality level and risk appetite. The examples above are illustrative.*

Escalation Thresholds

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

TriggerThreshold (Example)Escalation
Individual item amount> $10,000Supervisor review
Individual item amount> $50,000Controller review
Total reconciling items> $100,000Controller review
Item age> 60 daysSupervisor follow-up
Item age> 90 daysController / management review
Unreconciled differenceAny amountCannot close — must resolve or document
Growing trend3+ consecutive periodsProcess improvement investigation

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

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

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
Raw lines 166 to 175
Names a skill close-management :168

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.