reconciliation
Skill5 starsChanged 9 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.
10 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- microsoft/MicroHacktheir own version, first seen Nov 8, 2026
- microsoft/cat-agent-skillsedited, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- anthropics/knowledge-work-pluginsedited, 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 · 3
- anthropics/knowledge-work-plugins★ 35k99% same
- microsoft/cat-agent-skills★ 10123% same
- miptah21/skills★ 299% same
Wrote their own version · 7
- microsoft/MicroHack★ 220same name
- google-gemini/gemini-managed-agents-templates★ 99same name
- alebgl77/claude-inc★ 21same name
- 1398281322-a11y/java-backend-guardrails★ 2same name
- nisarth/claude-skills-store★ 1same 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 repository103 other files it gives its agents.
- ab-test-setupSkill
- analytics-trackingSkill
- apple-notesSkill
- apple-remindersSkill
- audit-supportSkill
- blogwatcherSkill
- camsnapSkill
- canned-responsesSkill
- canvas-designSkill
- canvasSkill
- close-managementSkill
- coding-agentSkill
- company-valuesSkill
- competitive-ads-extractorSkill
- competitive-analysisSkill
- competitor-alternativesSkill
- complianceSkill
- content-strategySkill
- contract-reviewSkill
- copy-editingSkill
- copywritingSkill
- deep-researchSkill
- email-sequenceSkill
- feature-specSkill
- file-organizerSkill
- finance-reconcileSkill
- financial-statementsSkill
- find-communitySkill
- first-customersSkill
- form-croSkill
- free-tool-strategySkill
- gifgrepSkill
- goose-adventure-gameSkill
- himalayaSkill
- image-optimizerSkill
- imsgSkill
- instagram-marketingSkill
- journal-entry-prepSkill
- launch-strategySkill
- legal-risk-assessmentSkill
- local-placesSkill
- marketing-ideasSkill
- marketing-psychologySkill
- mcporterSkill
- meeting-briefingSkill
- metrics-trackingSkill
- minimalist-reviewSkill
- model-usageSkill
- mvpSkill
- nano-banana-proSkill
- nano-pdfSkill
- nda-triageSkill
- notionSkill
- onboarding-croSkill
- openai-image-genSkill
- openai-whisper-apiSkill
- openai-whisperSkill
- openhueSkill
- oracleSkill
- ordercliSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
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 78
Verify elimination entries are correct for consolidation
- Distinctive: line 169
Documentation: Every reconciliation should include preparer, reviewer, date, and clear explanation of all reconciling items
- Distinctive: line 173
Standardization: Use consistent templates and procedures across all accounts
“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
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:
- Pull GL balance for the control account as of period end
- Pull subledger trial balance or detail report as of the same date
- Compare totals — they should match if posting is real-time
- 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:
- Obtain the bank statement balance as of period end
- Pull the GL cash account balance as of the same date
- Identify outstanding checks (issued but not cleared at the bank)
- Identify deposits in transit (recorded in GL but not yet credited by bank)
- Identify bank charges, interest, or adjustments not yet recorded in GL
- 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.00Intercompany Reconciliation
Reconcile balances between related entities to ensure they net to zero on consolidation.
Process:
- Pull intercompany receivable/payable balances for each entity pair
- Compare Entity A's receivable from Entity B to Entity B's payable to Entity A
- Identify and resolve differences
- Confirm all intercompany transactions have been recorded on both sides
- 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
- Timeliness: Complete reconciliations within the close calendar deadline (typically T+3 to T+5 business days after period end)
- Completeness: Reconcile all balance sheet accounts on a defined frequency (monthly for material accounts, quarterly for immaterial)
- Documentation: Every reconciliation should include preparer, reviewer, date, and clear explanation of all reconciling items
- Segregation: The person who reconciles should not be the same person who processes transactions in that account
- Follow-through: Track open items to resolution — do not just carry items forward indefinitely
- Root cause analysis: For recurring reconciling items, investigate and fix the underlying process issue
- Standardization: Use consistent templates and procedures across all accounts
- Retention: Maintain reconciliations and supporting detail per your organization's document retention policy
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.

