reconciliation
The reconciliation skill assists with GL-to-subledger comparisons, bank reconciliations, and intercompany account matching. Use it when balancing control accounts against detailed subledgers, reconciling cash to bank statements, identifying outstanding checks or deposits in transit, and categorizing timing differences and discrepancies. The skill covers common reconciling item causes, aging analysis, and escalation protocols for account verification workflows.
git clone --depth 1 https://github.com/openyak/openyak /tmp/reconciliation && cp -r /tmp/reconciliation/backend/app/data/plugins/finance/skills/reconciliation ~/.claude/skills/reconciliationSKILL.md
# 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 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 - Iden
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full ASM JSON, flattened CSV for easy import, and exportable Python code for data engineers. Common triggers include converting instrument files, standardizing lab data, preparing data for upload to LIMS/ELN systems, or generating parser code for production pipelines.
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or public datasets from GEO/SRA. Triggers on nf-core, Nextflow, FASTQ analysis, variant calling, gene expression, differential expression, GEO reanalysis, GSE/GSM/SRR accessions, or samplesheet creation.
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
>
>