Reconciliation

Reconciliation is an official finance skill in Anthropic’s knowledge-work-plugins repository. This catalog entry covers the individual reconciliation directory rather than the complete Finance plugin. According to the provider, the skill supports workflows that compare general-ledger balances with subledgers, bank statements, or third-party data. It also helps organize reconciling items, perform aging analysis, and escalate unresolved differences. The skill is a text-based methodology for Claude, not standalone accounting software.

Purpose and Professional Scope

A reconciliation makes clear whether two related sources show the same result for the same reporting date. The skill recommends defining the account, period, cutoff date, currency, sign convention, and accountable owner before comparing anything. Relevant balances are then obtained from the general ledger and the detailed source, aligned to the same period, and compared. A difference is not automatically an error. It may result from timing, pending approvals, interface delays, reclassification, or a missing entry. The important control objective is to explain or evidence every difference and to escalate items that cannot be resolved responsibly.

Common Reconciliation Types

For a general-ledger-to-subledger reconciliation, a control account is compared with detailed accounts-receivable, accounts-payable, fixed-asset, inventory, or prepaid-expense information. A bank reconciliation compares the bank statement with the cash account in the general ledger. Outstanding checks, deposits in transit, bank fees, interest, and corrections are considered separately before an adjusted balance is determined. An intercompany reconciliation compares receivable and payable balances between related entities. Different cutoff practices, foreign-exchange rates, classifications, disputed amounts, and elimination entries are important investigation paths.

Reconciling Items and Aging

The skill supports a traceable classification of open items. Timing differences may clear during the normal processing cycle. Other items require an adjustment, including unrecorded bank charges, missing entries, duplicate postings, or incorrect account classification. Unidentified differences, disputed items, and unusually old open items require investigation and documented escalation. Aging analysis groups items by their origin date and clarifies which items should be monitored, followed up, or raised to an accountable manager. Recurring differences should not simply be carried forward; they should trigger root-cause analysis and a process improvement discussion. Good documentation also preserves the reports used, the reconciliation timestamp, and the decision for each open item so another reviewer can retrace the reasoning later.

Controls, Boundaries, and Security

According to the provider, every reconciliation should be reviewed by qualified finance professionals before sign-off. The skill does not replace accounting policy, an ERP, an audit, tax advice, or an authorized close approval. Results depend on complete source data, consistent periodization, correct account mapping, documented adjustments, and appropriate permissions. Confidential financial information should be handled only in approved systems with the least access required. A connected language model may transmit inputs and outputs to its model provider; a local skill file does not automatically mean local model processing. The source is licensed under Apache-2.0. Skill Road does not state concrete prices or quotas. Data Analysis and Office are relevant categories, while Claude Code, Codex, and Cursor indicate possible client contexts; actual access depends on configuration and connected systems.