跳到正文
cccskills
免费在 GitHub 公开

accounts-receivable-follow-up

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md2.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Accounts receivable follow-up

Use this to prepare a receivables review and message drafts. The owner approves all customer contact.

Verify before calling an invoice overdue

For each open invoice, collect the invoice record, customer, currency, issued date, due date, original amount, credits, payments, open balance, last contact, dispute status, and account owner. Check payment records through the stated cutoff time. If the due date or balance cannot be proved, mark the item status unconfirmed rather than overdue.

Calculate days past due from the supplied due date and cutoff date. Keep part-payments, credits, disputes, and promised payment dates visible.

Prioritise the queue

Group items as:

  • due soon;
  • past due with no known dispute;
  • disputed or blocked;
  • promised payment not yet due;
  • status unconfirmed.

Within each group, sort by age and open balance, then note any named customer or contract rule that changes the handling. Do not invent a credit policy.

Draft the follow-up

Each draft should state the invoice number, issue and due dates, open balance, currency, and the requested next step. Keep the tone calm. Ask whether payment has been made or whether a record is missing. For a dispute, acknowledge the stated issue and route it to the owner; do not argue the contract.

Prepare a contact log row with draft stage, evidence cutoff, owner, approval state, and next review date. Drafts must not claim a late fee, service stop, collection action, or legal consequence unless an approved policy and owner instruction support it.

Safety rules

Never send a message, call a customer, apply a fee, stop service, change an invoice, or threaten collection. Never expose another customer's data. Route disputes, hardship, insolvency, legal threats, sanctions, and material customer risk to the finance owner or counsel.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

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.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Write ad variants that each test one idea, within platform limits and supported claims.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

查看 Significant-Gravitas 的全部技能

报告此技能的问题