Claude Marketplaces
SkillsMCP serversMarketplacesDigestTools
Submit

This week in Claude

Every Monday: Claude Code, Agent SDK, MCP, and the Anthropic platform moves worth your time.

Skills by category
Frontend DevelopmentBackend & APIsTesting & QASecurityDevOps & CI/CDGit & Pull RequestsDocumentationCode Review & QualityAI & Agent BuildingSkill Development
MCP servers by category
Sales & MarketingWeb & Browser AutomationDatabasesAI & LLM ToolsCloud & InfrastructureCommunication & MessagingDeveloper ToolsDesign & CreativeDocuments & KnowledgeSearch & Web Crawling
Marketplaces by category
AI Agents & OrchestrationLLM IntegrationDevelopment ToolsFrontend & UIBackend & APIsDatabasesTesting & Code QualityDevOps & CloudSecurity & ComplianceGit & Version Control
Claude Marketplaces

An independent directory of skills, plugins and MCP servers for Claude Code. Not affiliated with Anthropic.

Browse

  • Skills
  • MCP servers
  • Marketplaces
  • Weekly digest
  • Skill index
  • MCP index
  • Marketplace index

Site

  • About
  • Tools
  • Submit
  • Feedback
  • Privacy
  • llms.txt
  • Plugins reference

Maker

  • Snug
  • Agent Caffeine
  • knobs
  • Wax
  • Vectoys
  • mertduzgun.com
Crafted at
Skills
anthropics avatar

Reconciliation

anthropics/knowledge-work-pluginsOfficial

This walks you through the mechanics of financial reconciliations: GL to subledger, bank recs, and intercompany balances. It gives you the standard formats (like the two-sided bank rec layout), explains how to categorize reconciling items (timing differences vs. adjustments vs. investigate), and includes aging buckets for outstanding items. The escalation thresholds and trending guidance are actually useful if you're setting up a new process or documenting one. It's comprehensive enough that you could hand it to someone doing their first month-end close, but it won't tell you how to fix your specific ERP's interface failures or why your AR subledger is off by $47,283.

installs
3.5K
GitHub stars
33.3K
last updated
Aug 21, 2026
View on GitHubSave

Install

$ npx -y skills add anthropics/knowledge-work-plugins --skill reconciliation --agent claude-code

Installs into .claude/skills of the current project.

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:

  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 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

Aging Report Format

Item #DescriptionAmountDate OriginatedAge (Days)CategoryStatusOwner
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:

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.

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
SKILL.md on GitHub

Sponsors

SnugThe clipboard manager you and your agent can use, safelyAgent CaffeineClose your lid, come back to finished workWaxBlock anything with supervision, without erasing your iPhoneOpen StepsSponsoredFree and open-source skills that make AI coding agents easier to understand, verify, and control.

Details

Repository
github.com/anthropics/knowledge-work-plugins
First seen
Apr 16, 2026

More from anthropics/knowledge-work-plugins

All 198
  • Legal Response3.4K
  • Account Research3.4K
  • Risk Assessment3.4K
  • Competitive Brief3.3K
  • Draft Outreach3.3K
  • Performance Review3.3K
  • Compliance Check3.3K
  • Variance Analysis3.3K
  • Daily Briefing3.3K
  • Campaign Plan3.2K
  • Slack Search3.2K
  • Process Optimization3.2K
  • Audit Support3.2K
  • Brand Review3.2K
  • Roadmap Update3.1K
  • Runbook3.1K
  • Data Context Extractor3.1K
  • Sprint Planning3.1K
  • Status Report3.1K
  • Customer Research3.1K
  • Synthesize Research3K
  • Close Management3K
  • Forecast3K
  • Call Prep3K

Recommended

1juliusbrussee avatarcavemanjuliusbrussee/cavemanUltra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels594.9Kinstalls
2mattpocock avatargrill-memattpocock/skillsA relentless interview to sharpen a plan or design.1.4Minstalls
3shadcn avatarimproveshadcn/improveSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on s37.9Kinstalls
4obra avatarsystematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes309.2Kinstalls
5forrestchang avatarkarpathy-guidelinesforrestchang/andrej-karpathy-skillsBehavioral guidelines to reduce common LLM coding mistakes through explicit assumptions, simplicity, and verifiable success criteria.17.9Kinstalls
6vercel-labs avatarfind-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express int4.1Minstalls