Account Reconciliation
Legal and finance skill, available on Zeplik
Account Reconciliation is a ready-to-run legal and finance skill on Zeplik. Compares GL balances to subledgers, bank statements, or third-party data and categorizes differences. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured table you can keep and reuse: Reconciliation table -- GL vs source balances, categorized reconciling items, right-aligned amounts, net-difference total (see artifact-templates/table.md).
The Account Reconciliation skill loads automatically when your request matches it, or you can invoke it directly by typing /reconciliation in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Account Reconciliation skill can do
- Compare GL control balances to subledger detail to find variances
- Build bank reconciliations with outstanding checks and deposits in transit
- Reconcile intercompany balances between entity pairs for consolidation
- Categorize and age reconciling items to flag items needing escalation
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Account Reconciliation skill works
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.00
Intercompany 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
Zeplik output presentation
Present the final deliverable as a single polished artifact: clear headings, tables where the content is tabular, fenced code where it is code. Lead with the deliverable itself; keep process commentary to a single short line. If the skill produced multiple files or sections, end with a compact list of them with one-line purposes.
How to use the Account Reconciliation skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Account Reconciliation skill right away.
Describe your legal and finance task
Ask in plain language, or type /reconciliation to invoke the skill directly. Zeplik recognizes the Account Reconciliation skill and applies its method.
Review and refine the result
Zeplik returns a structured table you can edit, download, and reuse. Ask follow-ups to refine it.
Source and credit
- Author
- Anthropic
- License
- Apache-2.0
Adapted from the open-source anthropics/knowledge-work-plugins project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Account Reconciliation skill?
- Account Reconciliation is a ready-to-run legal and finance skill on Zeplik. Compares GL balances to subledgers, bank statements, or third-party data and categorizes differences. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured table you can keep and reuse: Reconciliation table -- GL vs source balances, categorized reconciling items, right-aligned amounts, net-difference total (see artifact-templates/table.md).
- How do I use Account Reconciliation on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /reconciliation in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Account Reconciliation skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Account Reconciliation skill runs on your preferred model for the task.
- Where does the Account Reconciliation skill come from?
- The Account Reconciliation skill is adapted from the open-source anthropics/knowledge-work-plugins project (Apache-2.0) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Account Reconciliation skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related legal and finance skills
- Audit SupportUse when the user is preparing for an internal or external audit -- "get ready for the auditors", "build testing workpapers", "select audit samples", "classify this control deficiency". SOX 404 control testing methodology and documentation standards. Not for running a SOX testing cycle (use sox-testing).
- Cash Flow SnapshotUse when the user asks about cash flow or runway -- "forecast my cash flow", "will I make payroll", "how long is my runway", "cash crunch coming". Builds a 30/60/90-day cash forecast with confidence bands and named risk flags from books data or CSV, plus a downloadable XLSX.
- Cash-Flow Heads UpA forward-looking 30/60-day cash outlook flagging the tightest week and two things to act on. Not for reconciling and closing the books (use close-month or month-end-prep).
- Compliance CheckUse when the user asks whether a feature, campaign, or initiative is compliant -- "compliance check this launch", "does this touch GDPR or personal data", "what approvals do we need before shipping". Surfaces applicable regulations, required approvals, jurisdictional requirements, and risk areas.
- Contract ReviewUse when the user asks to review a contract -- "review this MSA", "redline this vendor agreement", "what's risky in this contract". Clause-by-clause analysis against a negotiation playbook with redlines, business impact, and fallback positions. Not for quick NDA screening (use triage-nda).
- Employment Contract DrafterUse when drafting employment paperwork -- 'write an employment agreement for a new hire', 'draft an employee handbook policy', 'do we need at-will language'. Agreements, handbook policies, IP and non-compete clauses. Not for offer letters (use draft-offer) or reviewing third-party contracts (use review-contract).
More on Zeplik
Try Account Reconciliation on Zeplik
Every model, one chat. Bring the Account Reconciliation skill into your next conversation and let the assistant do the work.