reconciliation
Skill1 starsChanged 7 months agoMITView on GitHub
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. Trigger with "reconcile", "bank rec", "account reconciliation", "reconciling items", or "GL to subledger".
10 other projects use a version of this.
Adopted by
Most recently taken up by
- felipealvarenga/fintech-skillstheir own version, first seen Nov 15, 2026
- microsoft/MicroHacktheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- 1398281322-a11y/java-backend-guardrailstheir own version, first seen Aug 31, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- anthropics/knowledge-work-plugins★ 36ksame name
- microsoft/MicroHack★ 223same name
- google-gemini/gemini-managed-agents-templates★ 99same name
- alebgl77/claude-inc★ 21same name
- felipealvarenga/fintech-skills★ 7same name
- insight68/Skills★ 5same name
- 1398281322-a11y/java-backend-guardrails★ 2same name
- miptah21/skills★ 2same name
- awesomeclaude666/ClaudeCodeProject★ 0same name
- IngAs8/ClaudeSkill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 148
Always start with the prior period reconciliation to carry forward uncleared items.
- Distinctive: line 153
Document the source of every reconciling item.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Account Reconciliation
Reconcile account balances by comparing the general ledger to supporting sources: bank statements, subledger reports, third-party confirmations, or intercompany counterparts. Identify, categorize, and resolve reconciling differences.
Workflow
Step 1: Identify the Reconciliation Parameters
Gather the required inputs:
- Account: GL account number, name, and balance.
- Source: What the GL is being reconciled to (bank statement, subledger, counterparty).
- Period end: The as-of date for the reconciliation.
- Currency: Functional currency and whether FX translation applies.
- Prior period: Last reconciled balance and any carryforward items.
Step 2: Obtain and Compare Balances
Pull the two data sources to compare:
GL Side:
- Ending GL balance per the trial balance.
- Detail of transactions posted during the period.
Source Side:
- Bank statement ending balance, subledger total, or counterparty confirmation.
- Detail of transactions from the source.
Calculate the initial difference: GL balance minus source balance.
Step 3: Identify Reconciling Items
Categorize all differences into standard types:
Timing Differences (self-resolving):
- Outstanding checks (issued but not yet cleared).
- Deposits in transit (recorded but not yet credited by bank).
- Invoices posted in GL but not yet received by counterparty.
- Month-end cutoff items that will clear in the next period.
Permanent Differences (require action):
- Bank fees or interest not yet recorded in GL.
- Errors in GL posting (wrong amount, wrong account, wrong period).
- Duplicate transactions.
- Missing transactions (in source but not in GL, or vice versa).
- Unauthorized or unrecognized transactions.
Prior Period Carryforward:
- Items from the prior reconciliation that have not yet cleared.
- Aged items requiring follow-up or write-off.
Step 4: Resolve and Escalate
For each permanent difference:
- Record: Post correcting journal entries for GL errors.
- Investigate: Research unrecognized items with supporting documentation.
- Escalate: Flag items above a materiality threshold or older than 60 days.
- Write-off: Propose write-off for immaterial aged items with approval.
Step 5: Document and Certify
Complete the reconciliation workpaper with sign-off.
Output Format
## Account Reconciliation
**Account**: [Number] - [Name]
**Period end**: [YYYY-MM-DD]
**Prepared by**: [Name] | **Date**: [YYYY-MM-DD]
**Reviewed by**: [Name] | **Date**: [YYYY-MM-DD]
### Balance Comparison
| Source | Amount |
|---------------------------------|---------------|
| GL ending balance | $1,245,678.90 |
| Bank / subledger / counterparty | $1,238,432.15 |
| **Difference** | **$7,246.75** |
### Reconciling Items
| # | Type | Description | Amount | Age | Status | Action Required |
|---|----------|--------------------------------|-------------|------|--------------|--------------------|
| 1 | Timing | Outstanding check #4521 | ($3,200.00) | 5d | Expected | Monitor |
| 2 | Timing | Deposit in transit 03/31 | $2,500.00 | 1d | Expected | Confirm clearance |
| 3 | Permanent| Bank fee - March | ($46.75) | 0d | Open | Post JE |
| 4 | Permanent| Duplicate payment to vendor | ($8,000.00) | 15d | Investigating| Contact vendor |
| 5 | Carryfw | Outstanding check #4102 (Feb) | ($500.00) | 35d | Stale | Void and reissue |
### Reconciled Balance
| Description | Amount |
|-------------------------------------------|---------------|
| GL ending balance | $1,245,678.90 |
| Less: outstanding checks | ($3,700.00) |
| Add: deposits in transit | $2,500.00 |
| Less: unrecorded bank fees | ($46.75) |
| **Adjusted GL balance** | **$1,244,432.15** |
| Bank / source balance | $1,238,432.15 |
| **Remaining unreconciled difference** | **$6,000.00** |
| Memo: duplicate payment under investigation| ($8,000.00) |
### Certification
- [ ] All reconciling items are supported with documentation
- [ ] Items older than 30 days have been investigated
- [ ] Correcting journal entries have been posted or queued
- [ ] Reconciliation is complete and balanced within toleranceExamples
User: "Reconcile our operating cash account for March 2026" Action: Compare the GL cash balance to the bank statement, identify timing differences and permanent items, and produce the reconciliation workpaper.
User: "We have a $50K intercompany difference between US and UK entities" Action: Break down the difference by transaction, identify timing and FX items, and recommend resolution steps.
User: "Show me all aged reconciling items over 60 days" Action: Pull carryforward items from prior reconciliations, flag anything over 60 days, and recommend disposition (investigate, write-off, or escalate).
Best Practices
- Reconcile monthly at minimum; high-risk accounts (cash, revenue) may require more frequent reconciliation.
- Always start with the prior period reconciliation to carry forward uncleared items.
- Set a materiality threshold; differences below the threshold can be noted but do not require investigation.
- Age all reconciling items and escalate anything unresolved beyond 60 days.
- For bank reconciliations, always review the outstanding check list for stale items (typically >90 days).
- Intercompany reconciliations should net to zero after eliminations; any difference indicates a booking error.
- Document the source of every reconciling item; a reconciliation without supporting detail is incomplete.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

