Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计通过

account-reconciliation账户对账

Agent Skill

account-reconciliation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

544

周安装

22

GitHub Stars

56

下载量

171
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:account-reconciliation(账户对账)
来源仓库:https://github.com/vm0-ai/vm0-skills
仓库路径:skills/account-reconciliation
安装命令:
npx skills add https://github.com/vm0-ai/vm0-skills --skill account-reconciliation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/vm0-ai/vm0-skills --skill account-reconciliation

简介

account-reconciliation 用于核对总账与明细账目一致性,保障财务数据准确可靠。

  • 适用于贸易应收应付、固定资产、库存及预提负债等科目的定期对账工作。
  • 通过提取总账余额与子账明细,比对总额并排查差异原因,支持财务合规与审计需求。
  • 使用前请确认数据来源权限与接口稳定性,避免因批量查询影响系统性能。
  • 需根据企业实际科目设置调整核对模板,确保覆盖所有关键控制点。

SKILL.md

Reconciliation Categories

General Ledger vs. Subledger

Verify that each control account in the GL agrees with the sum of its underlying detail ledger.

Accounts typically reconciled this way:

  • Trade receivables (GL control vs. AR aging schedule)
  • Trade payables (GL control vs. AP aging schedule)
  • Property, plant & equipment (GL control vs. asset register)
  • Inventory (GL control vs. stock valuation report)
  • Prepaid assets (GL control vs. amortization schedule)
  • Accrued liabilities (GL control vs. accrual supporting schedules)

Workflow:

  1. Extract the GL control account balance at the period cut-off
  2. Generate the subledger detail or trial balance as of the identical date
  3. Match the two totals — under real-time posting they should be identical
  4. Research any gap (manual GL postings, pending interface batches, failed data transfers, reclassifications without subledger mirror)

Typical root causes of discrepancy:

  • Journal entries booked directly to the control account without a subledger transaction
  • Subledger batches queued but not yet transmitted to the GL
  • Lag between batch processing windows
  • GL reclassifications with no subledger counterpart
  • Integration failures or rejected interface records

Cash / Bank Reconciliation

Align the book cash balance with the financial institution's reported position.

Workflow:

  1. Obtain the institution's closing statement balance
  2. Pull the corresponding GL cash account balance at the same date
  3. List checks written but not yet presented for payment
  4. List deposits recorded in the books but not yet credited by the bank
  5. Identify bank-initiated entries (fees, interest, returned items) absent from the GL
  6. Derive an adjusted balance on each side; the two must agree

Presentation template:

Institution statement balance:          $XX,XXX
  Plus: Deposits not yet credited        $X,XXX
  Less: Unpresented checks             ($X,XXX)
  Plus/Less: Institution errors          $X,XXX
Adjusted institution balance:           $XX,XXX

Book (GL) balance:                      $XX,XXX
  Plus: Interest & credits unrecorded    $X,XXX
  Less: Fees & charges unrecorded      ($X,XXX)
  Plus/Less: Book errors                 $X,XXX
Adjusted book balance:                  $XX,XXX

Remaining variance:                     $0.00

Intercompany Reconciliation

Confirm that receivables and payables between affiliated entities offset to zero for consolidation purposes.

Workflow:

  1. Collect intercompany receivable and payable balances for every entity pair
  2. Match Entity A's claim on Entity B against Entity B's corresponding obligation to Entity A
  3. Investigate and resolve discrepancies
  4. Verify that both sides have captured every intra-group transaction
  5. Validate that consolidation elimination entries will net these balances cleanly

Typical root causes of discrepancy:

  • One entity recorded the transaction while the other has not yet done so
  • Entities applied different foreign exchange rates on the same transaction
  • Amounts classified as intercompany by one party but as third-party by the other
  • Contested charges or unapplied cash receipts
  • Differing period-end cut-off conventions across subsidiaries

Classifying Open Reconciling Items

Class 1 — Timing Lags

Items arising from normal processing sequences that will self-clear without intervention:

  • Checks issued and booked but awaiting bank presentment
  • Deposits journalized but pending bank value-date credit
  • Transactions posted in one system awaiting batch interface to the other
  • Items sitting in an approval queue prior to final posting

Expected outcome: Resolution within the standard processing window (generally 1-5 business days). No corrective entry required.

Class 2 — Corrective Action Needed

Items that demand a journal entry or other ledger adjustment:

  • Bank-originated charges not yet reflected on the books (service fees, wire costs, NSF penalties)
  • Interest income or expense recognized by the institution but absent from the GL
  • Posting mistakes — wrong dollar amount, wrong account, or duplicate recording
  • Transactions present in one system with no counterpart in the other
  • Properly recorded amounts sitting in an incorrect GL account

Expected outcome: Prepare and post a correcting entry during the current or next available period.

Class 3 — Investigation Required

Items lacking a clear explanation:

  • Variances with no identifiable source
  • Amounts in dispute between internal parties or with external counterparties
  • Stale items that have exceeded their expected clearance window
  • Persistent differences of the same type reappearing period after period

Expected outcome: Perform root-cause analysis, document findings, and escalate when resolution is not straightforward.

Aging and Monitoring of Open Items

Track every unresolved reconciling item by age to surface those requiring management attention:

Age BandClassificationRequired Response
0-30 daysCurrentRoutine monitoring — within normal processing window
31-60 daysMaturingActive follow-up — determine why the item has not cleared
61-90 daysPast dueSupervisor notification with documented investigation
Over 90 daysStaleManagement escalation — evaluate write-off or forced adjustment

Item-Level Tracking Register

SeqDescriptionAmountOrigination DateDays OpenClassResolution StatusAssigned To
1[Detail]$X,XXX[Date]XX[Type][Status][Name]

Trend Monitoring

Evaluate the reconciling-item population across periods to detect deterioration:

  • Compare the aggregate dollar value of open items to the prior period
  • Flag when total open items exceed the account's materiality benchmark
  • Flag when the count of open items grows for two or more consecutive periods
  • Investigate chronic items that appear in every reconciliation (signal of a systemic process gap)

Escalation Governance

Establish triggers proportional to organizational risk appetite:

ConditionIllustrative ThresholdEscalation Path
Single-item dollar valueAbove $10,000Supervisor review
Single-item dollar valueAbove $50,000Controller review
Aggregate open itemsAbove $100,000Controller review
Item ageOver 60 daysSupervisor follow-up
Item ageOver 90 daysController / senior management review
Unresolved net differenceAny amountPeriod cannot close — must resolve or formally document
Worsening trendThree or more consecutive periodsInitiate process-improvement project

*Calibrate thresholds to match the entity's materiality level and control environment.*

Operating Principles

  1. Cadence discipline: Finish every reconciliation within the close calendar window (commonly T+3 to T+5 after period end)
  2. Coverage: Reconcile every balance sheet account on a defined cycle — monthly for material balances, quarterly for immaterial ones
  3. Audit trail: Each reconciliation must identify the preparer, reviewer, completion date, and a narrative for every open item
  4. Separation of duties: The reconciler should not be the person who initiates or approves transactions in the same account
  5. Closure rigor: Carry open items forward only with active follow-up; never allow perpetual rollover without investigation
  6. Systemic fixes: When the same reconciling item type recurs, address the upstream process rather than repeatedly clearing symptoms
  7. Uniform format: Employ standardized templates and naming conventions across all accounts and business units
  8. Record keeping: Retain completed reconciliations and all supporting evidence in accordance with the organization's document-retention policy

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.31%
按下载量换算60

Claude

29.63%
按下载量换算51

Cursor

19.73%
按下载量换算34

Gemini CLI

8.99%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills