finance/accounting/reconciliation/SKILL.md
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.
npx skillsauth add harsh040506/claude-code-unified-skill-plugin-library reconciliationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Compare the general ledger control account balance to the detailed subledger balance.
Common accounts:
Process:
Common causes of differences:
Compare the GL cash balance to the bank statement balance.
Process:
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
Reconcile balances between related entities to ensure they net to zero on consolidation.
Process:
Common causes of differences:
Items that exist because of normal processing timing and will clear without action:
Expected resolution: These items should clear within the normal processing cycle (typically 1-5 business days). No adjusting entry needed.
Items that require a journal entry to correct:
Action: Prepare adjusting journal entry to correct the GL or subledger.
Items that cannot be immediately explained:
Action: Investigate root cause, document findings, escalate if unresolved.
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 |
| Item # | Description | Amount | Date Originated | Age (Days) | Category | Status | Owner | |--------|-------------|--------|-----------------|------------|----------|--------|-------| | 1 | [Detail] | $X,XXX | [Date] | XX | [Type] | [Status] | [Name] |
Track reconciling item totals over time to identify growing balances:
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.
testing
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.
tools
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.
testing
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".
development
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.