Reconciliation
AnthropicOfficialPublished by Anthropic
- Skill
- Guidelines
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured framework for performing account reconciliations, including GL-to-subledger, bank, and intercompany reconciliations. It outlines standard processes for identifying, categorizing, and resolving discrepancies, while establishing best practices for aging analysis, escalation thresholds, and documentation to ensure financial integrity during period-end closes.
What it does
- Defines standard procedures for GL-to-subledger, bank, and intercompany reconciliations.
- Provides a framework for categorizing reconciling items into timing differences, necessary adjustments, or items requiring investigation.
- Offers templates for bank reconciliation formats and aging reports.
- Establishes best practices for segregation of duties, timeliness, and root cause analysis.
- Suggests escalation thresholds based on item amount, age, and materiality.
- Includes guidance on tracking trends in reconciling items to identify systemic process issues.
When to use it
- During month-end or period-end financial closing processes.
- When investigating discrepancies between general ledger balances and subledgers or bank statements.
- When establishing or auditing internal financial control procedures.
- When managing intercompany balances to ensure accurate consolidation.
- When training staff on standardized reconciliation workflows.
Advantages
- Promotes consistency and standardization across financial reporting processes.
- Helps identify and resolve stale or recurring reconciling items through structured aging analysis.
- Provides clear escalation paths to manage financial risk and materiality.
- Encourages proactive root cause analysis rather than just clearing balances.
- Supports audit readiness through standardized documentation requirements.
Usage examples
- “What is the standard process for a bank reconciliation?”
- The agent provides a step-by-step guide including obtaining balances, identifying outstanding checks and deposits in transit, and a standard reconciliation format to reach an adjusted balance.
- “How should I categorize an unexplained difference in my accounts?”
- The agent explains the three categories (Timing, Adjustments, Investigation) and advises that unexplained differences fall under 'Requires Investigation' and must be documented and escalated.
- “What are the best practices for intercompany reconciliation?”
- The agent outlines a 5-step process focusing on comparing receivable/payable balances, resolving timing differences, verifying FX rates, and confirming elimination entries.
- “When should I escalate a reconciling item?”
- The agent provides a table of escalation triggers based on item amount, age, and total unreconciled differences, suggesting specific thresholds for supervisor or controller review.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/anthropics/reconciliation/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip reconciliation.zip -d .agents/skills
Documentation by Anthropic
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
Files
- ATTRIBUTION.mdAdded by AutoGineer920 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md8.0 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · finance/skills/reconciliation · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from finance/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download reconciliation.zip