Saltar al contenido
Marketplace

reconciliation

de anthropics

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.

Resumen

SKILL.mdLeída en 8444efc

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

Archivos 1 archivo

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

npx skills add anthropics/knowledge-work-plugins --skill reconciliation

Más de anthropics

  • frontend-designanthropicsOficialGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.958 k instalaciones en skills.sh8
  • skill-creatoranthropicsOficialCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.398.8 k instalaciones en skills.sh0
  • pptxanthropicsOficialUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.231.2 k instalaciones en skills.sh0
  • pdfanthropicsOficialUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.206.2 k instalaciones en skills.sh0
  • docxanthropicsOficialUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.197.1 k instalaciones en skills.sh0
Todas las skills de anthropics