ElasticFlow
HubAll SkillsBy DepartmentBy RoleBy ToolBy MetricMCPsPublishers
Sito principaleAccediRegistrati
ElasticFlow

Trasforma il tuo business con l'automazione dei workflow basata sull'IA. Una piattaforma unica per tutte le tue esigenze enterprise.

Seguici

Piattaforma

  • Funzionalità
  • Vantaggi
  • Casi d'uso
  • Libreria di workflow

Casi d'uso

  • Vendite
  • Marketing
  • Finanza e Legale
  • Risorse Umane

Catalogo

  • Dipartimenti
  • Ruoli
  • Strumenti
  • Metriche
  • Piattaforme

Crescita

  • Programma di referral
  • Partner

Legale

  • Informativa sulla privacy
  • Termini di servizio
  • Cookie policy
  • Uso accettabile
  • Sicurezza
  • SLA

© 2026 ElasticFlow. Tutti i diritti riservati.

ElasticFlow
HubAll SkillsBy DepartmentBy RoleBy ToolBy MetricMCPsPublishers
Sito principaleAccediRegistrati
ElasticFlow

Trasforma il tuo business con l'automazione dei workflow basata sull'IA. Una piattaforma unica per tutte le tue esigenze enterprise.

Seguici

Piattaforma

  • Funzionalità
  • Vantaggi
  • Casi d'uso
  • Libreria di workflow

Casi d'uso

  • Vendite
  • Marketing
  • Finanza e Legale
  • Risorse Umane

Catalogo

  • Dipartimenti
  • Ruoli
  • Strumenti
  • Metriche
  • Piattaforme

Crescita

  • Programma di referral
  • Partner

Legale

  • Informativa sulla privacy
  • Termini di servizio
  • Cookie policy
  • Uso accettabile
  • Sicurezza
  • SLA

© 2026 ElasticFlow. Tutti i diritti riservati.

ElasticFlow
HubAll SkillsBy DepartmentBy RoleBy ToolBy MetricMCPsPublishers
Sito principaleAccediRegistrati
  1. Home
  2. Skill
  3. Reconciliation
Disponibile in:🇬🇧 English🇰🇷 한국어
Skill IAReconcile accountsFinance

Match finance balances and document what still needs review. — Claude Skill

Uno skill Claude per Claude Code di anthropics✓ — esegui /reconciliation in Claude·Aggiornato il 12 giu 2026·vmain@b8e8089

Compatibile conGChatGPTClaudeClaudeCCClaude CodeCDClaude DesktopXCodex / Codex CLICursorCursorGeminiGeminiHHermes (via Continue / Cline)OpenClawOpenClawWindsurfWindsurf

Compares GL, subledger, bank, and third-party balances, categorizes differences, ages open items, and prepares close review notes.

  • Compares general ledger balances to bank statements, subledgers, or third-party reports.
  • Categorizes differences as timing, adjustment required, or investigation required.
  • Ages open items so old or material exceptions do not drift from close to close.
  • Produces review-ready reconciliation notes for finance close sign-off.
TuOggi

A finance team manually compares balances and carries unresolved items forward with inconsistent categorization.

Con /reconciliation

Run /reconciliation to structure the comparison, categorize every item, age exceptions, and prepare review-ready documentation.

1 Define scope2 Compare balances3 Categorize items4 Age exceptions5 Document sign-off

Per chi

Finance Manager

Structure close reconciliations, categorize exceptions, age outstanding items, and document sign-off.

Vedi gli skill per questo ruolo

Cosa fa

Bank reconciliation

Match cash GL balances to bank statements and explain deposits, checks, fees, and interest.

GL to subledger

Compare control accounts to AR, AP, fixed asset, inventory, prepaid, or accrual detail.

Intercompany

Find differences between related entities before consolidation.

Come funziona

1

Choose the reconciliation type: bank, GL-to-subledger, intercompany, or third-party.

2

Provide the account, period, source balances, and supporting details.

3

Compare both sides, list reconciling items, and categorize each difference.

4

Prepare aging, escalation, journal entry needs, and close sign-off notes.

Opzioni di input

Account and period

Account name, GL account, entity, cutoff date, and close period.

Esempio

Example input
Account: Operating Cash - 1020.
Period: May close.

Bank statement balance: $248,920.
GL balance: $241,480.

Known items:
- Deposits in transit: $6,200.
- Outstanding checks: $1,950.
- Bank fee not recorded: $85.
- Interest income not recorded: $15.

Materiality threshold: $500.
Need: reviewer-ready reconciliation summary.
What the skill returns
How it reads the request
The skill compares the bank view and the accounting ledger view, then explains which differences are timing items and which need accounting entries.
Adjusted balance logic
Deposits in transit and outstanding checks explain normal timing differences. The bank fee and interest income need to be recorded in the GL.
Items to record
Prepare a journal entry for the $85 bank fee and $15 interest income because they are not yet reflected in the GL.
Review result
After known items are applied, no unexplained difference above the $500 threshold remains.
What a human must confirm
Reviewer should confirm support for deposits in transit and outstanding checks, then approve the two small GL adjustments.

Metriche migliorate

Unreconciled Difference
Lower close risk
Finance
Close Timeliness
+10-20%
Finance
Reconciliation Aging
-20-40%
Finance

Funziona con

Google Sheets
manuale

Prepare shared reconciliation schedules and exception trackers.

SQL
manuale

Query transaction detail, subledger extracts, and finance-system exports for reconciliation.

Excel
manuale

Prepare reconciliation workbooks, aging analysis, and review documentation.

General Ledger
manuale

Primary finance system for GL balances, control accounts, journals, and close reconciliation.

Vuoi usare Reconciliation?

Scegli come iniziare.

Esegui in Claude Code
Gratis. Open source.

Installa ed esegui questo skill localmente sul tuo computer.

1
Installa Claude Code

Apri un terminale sul tuo computer e incolla questo comando:

2
Installa lo skill

Questo scarica lo skill con tutti i suoi file sul tuo computer:

Aggiungi -g alla fine per renderlo disponibile in tutti i tuoi progetti.

3
Eseguilo

Avvia Claude Code, poi digita il comando:

poi
Vedi sorgente su GitHub
Usa su ElasticFlow
Funzionalità per team e collaborazione

Esegui gli skill dal tuo browser. Condividi risultati, gestisci gli accessi, collabora con il tuo team. Senza terminale.

Prova gratuita di 14 giorni. Annulla quando vuoi.

Vedi su GitHub

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

Documenti di riferimento


name: reconciliation description: 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. argument-hint: "<account> [period]"

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
ElasticFlow

Trasforma il tuo business con l'automazione dei workflow basata sull'IA. Una piattaforma unica per tutte le tue esigenze enterprise.

Seguici

Piattaforma

  • Funzionalità
  • Vantaggi
  • Casi d'uso
  • Libreria di workflow

Casi d'uso

  • Vendite
  • Marketing
  • Finanza e Legale
  • Risorse Umane

Catalogo

  • Dipartimenti
  • Ruoli
  • Strumenti
  • Metriche
  • Piattaforme

Crescita

  • Programma di referral
  • Partner

Legale

  • Informativa sulla privacy
  • Termini di servizio
  • Cookie policy
  • Uso accettabile
  • Sicurezza
  • SLA

© 2026 ElasticFlow. Tutti i diritti riservati.