‹ 首页

ar-aging

@wellapp-ai · 收录于 5 天前 · 上游提交 1 个月前

Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace. Use when the user asks who owes them money, an AR aging report, overdue invoices, days sales outstanding (DSO), or which customers to chase.

适合你,如果你需要追踪客户欠款并管理应收账款

/ 通过 npx 安装 校验哈希
npx oh-my-skill add wellapp-ai/well/ar-aging
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- wellapp-ai/well/ar-aging
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify wellapp-ai/well/ar-aging
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
340GitHub stars
~470上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 782601c · 表述以原文为准
它做什么

当你询问应收账款相关问题时,Claude 会从 Well 工作区获取发票与交易数据,生成一份账龄报告。报告按到期日分段(当前、1-30天等)列出未付金额,并标出已确认未支付的逾期发票。同时会提供每个客户的付款习惯和应收账款周转天数(DSO)。

什么时候触发

当用户问谁欠款、要应收账款报告、查逾期发票、算DSO,或问哪些客户需要追款时触发。

装好后可以这样说
生成应收账款账龄报告。
包含客户付款习惯。
显示DSO及计算周期。
技能原文 SKILL.md作者撰写 · MIT · 782601c

Accounts-receivable aging from Well

Collections is judgment, not nagging. The point of an aging report is to chase the right customers — firmly where their payment history warrants it, gently where it doesn't — and to never chase an invoice that was already paid, disputed, or credited. Verify status before recommending any chase.

Build it
  1. Discover the schema first (see well:querying-well-data).
  2. Open receivables — issued invoices filtered on the payment-status / outstanding field the schema exposes (don't infer "unpaid" by subtracting sums if a status field exists). Pull due date, outstanding amount, and the customer (companies).
  3. Confirm what's actually settled — cross-check against transactions / invoice_transactions so a payment already received but not yet reflected in status isn't counted as overdue. This is the well:reconciliation sibling skill — reuse it.
  4. Bucket by age from the due date: Current (not yet due), 1–30, 31–60, 61–90, 90+ days overdue. Total per bucket and per customer.
  5. Per-customer behavior — where history exists, note each customer's typical days-to-pay so the user can prioritise (a chronic late-payer ≠ a first-time slip).
Rules
  • Verify status before chasing. Exclude paid / disputed / credited invoices from "to chase" — chasing a settled invoice is the fastest way to lose trust.
  • Sort the chase list by amount × overdue age, but annotate each with the customer's payment tier.
  • Don't sum across currencies without converting (exchange_rates).
  • Report DSO (days sales outstanding) only with the window it's computed over.
Present it

An aging table (buckets × totals), a top "to chase" list (verified-open only, with each customer's payment behavior), DSO with its window, and the total outstanding — in the workspace currency.

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。