Back to Details

plan-payroll

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Run the payroll-confidence pipeline by chaining two skills. The owner approves at each handoff — never send a reminder or commit a forecast without explicit confirmation.
Parse arguments:
  • --horizon
    (default 
    30
    ) — forecast window in days (30, 60, or 90)
  • --payroll-date
    (optional) — the date payroll runs; defaults to next Friday
通过串联两个skill运行工资发放信心流水线。企业主在每个交接环节都需要审批——未经明确确认，绝不发送催款提醒或确定预测结果。
解析参数：
  • --horizon
    （默认值
    30
    ）——预测周期（天数，可选30、60或90）
  • --payroll-date
    （可选）——发薪日期；默认值为下周五

Step 1 — Cash forecast (cash-flow-snapshot)

步骤1 — 现金流预测（cash-flow-snapshot）

Trigger the 
cash-flow-snapshot
skill workflow:
  1. Pull AR, AP, and historical cash timing from QuickBooks, PayPal, Stripe, or Square (whichever are connected). Fall back to CSV upload if no connector is live.
  2. Layer in known fixed costs (rent, payroll, recurring vendor charges).
  3. Produce a 30/60/90-day forecast (use the requested 
    --horizon
    ) with percentage-variance confidence bands.
  4. Flag named risks — e.g., "payroll on May 15 lands $4,200 below your fixed-cost floor at the median forecast."
  5. Deliver chat summary + downloadable XLSX.
  6. Present to the owner. Wait for explicit "okay, see what we can collect" before Step 2.
If the forecast shows payroll is comfortably covered, ask the owner whether they still want to chase overdue invoices or stop here.
触发
cash-flow-snapshot
skill工作流：
  1. 从QuickBooks、PayPal、Stripe或Square（已连接的平台）提取应收账款（AR）、应付账款（AP）及历史现金流时序数据。若没有可用连接器，则退化为CSV上传模式。
  2. 加入已知固定成本（房租、工资、定期供应商费用）。
  3. 根据指定的
    --horizon
    生成30/60/90天预测报告，包含百分比方差置信区间。
  4. 标记明确风险——例如：“按中位数预测，5月15日的工资发放将比固定成本下限低4200美元。”
  5. 生成聊天摘要及可下载的XLSX文件。
  6. 提交给企业主。在进入步骤2前，需等待明确的“好的，看看我们能收回哪些款项”的确认。
如果预测显示工资发放资金充足，询问企业主是否仍要追讨逾期发票或就此终止流程。

Step 2 — Overdue collection (invoice-chase)

步骤2 — 逾期款项催收（invoice-chase）

After Step 1 approval, trigger the 
invoice-chase
skill workflow:
  1. Pull overdue invoices from QuickBooks and PayPal.
  2. Rank by amount × days-late × customer payment history.
  3. For each, draft a reminder matched to tone (gentle for good customers, firm for repeat late payers).
  4. PayPal-issued invoices queue as PayPal-send drafts; non-PayPal invoices queue as Mail drafts.
  5. Present the ranked list with drafted reminders. Show the projected cash impact if a top-N subset gets paid within the horizon — does that close the payroll gap from Step 1?
  6. Wait for explicit "send these" per reminder (or batch approval) before pushing.
获得步骤1的批准后，触发
invoice-chase
skill工作流：
  1. 从QuickBooks和PayPal提取逾期发票。
  2. 按金额×逾期天数×客户付款历史进行排序。
  3. 为每张发票匹配对应语气的催款草稿（对优质客户用温和语气，对多次逾期的付款方用强硬语气）。
  4. PayPal开具的发票将生成PayPal发送草稿；非PayPal发票则生成邮件草稿。
  5. 展示排序后的发票列表及对应的催款草稿。显示若前N个发票在预测周期内回款，预计能带来的现金流影响——是否能填补步骤1中发现的工资资金缺口？
  6. 在发送前，需等待针对每张催款草稿的明确“发送”指令（或批量批准）。

Approval gates (must hold)

审批闸门（必须遵守）

  • Never send a reminder without owner approval — drafts only until "send" is given.
  • Never commit a forecast as authoritative without owner sign-off.
  • If a connector is unreachable (QuickBooks, PayPal, Mail), stop, report which connector failed, and ask whether to retry, fall back to CSV, or abort.
  • 未经企业主批准，绝不发送催款提醒——仅生成草稿，直到收到“发送”指令。
  • 未经企业主签字确认，绝不将预测结果作为权威结论。
  • 若连接器无法访问（QuickBooks、PayPal、邮件），立即停止流程，报告故障的连接器，并询问是否重试、退化为CSV模式或终止流程。

Output

输出

End the run with a one-paragraph recap: forecast verdict (covered / gap / risk), reminders sent and to whom, projected new cash position if reminders convert.
流程结束时生成一段总结：预测结论（资金充足/存在缺口/有风险）、已发送的催款提醒及接收方、若催款提醒得到回款后的预计新现金流状况。