Back to Details

close-month

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Run the month-end close workflow. Reconcile, flag gaps, narrate the P&L, and export the close packet for the owner's records (and their accountant).
Parse arguments:
  • --month
    (default: previous calendar month) — 
    YYYY-MM
    format
  • --save-to
    (default 
    files
    ) — 
    files
    (Google Drive / OneDrive), 
    desktop
    (local), or 
    both
运行月末结账工作流。完成账目核对、标记差异、撰写损益表（P&L）说明，并导出结账数据包供企业主存档（及其会计师使用）。
解析参数：
  • --month
    （默认值：上一自然月）——格式为
    YYYY-MM
  • --save-to
    （默认值：
    files
    ）——可选值包括
    files
    （Google Drive / OneDrive）、
    desktop
    （本地）或
    both
    （两者皆存）

Step 1 — Reconcile

步骤1 — 账目核对

Trigger the 
month-end-prep
skill workflow:
  1. Pull all QuickBooks transactions for the target month.
  2. Pull settlements from each connected payment processor (PayPal, Stripe, Square) for the same month.
  3. Match QB entries to processor settlements by amount + date (±2 days).
  4. Surface three gap categories:
    • Unmatched processor settlements — money came in via PayPal/Stripe/Square but never landed in QB
    • Unmatched QB deposits — QB shows income with no processor record (cash? wire? misclassified?)
    • Variance lines — matched but amount differs (fees, refunds split)
触发
month-end-prep
技能工作流：
  1. 提取目标月份的所有QuickBooks交易记录。
  2. 提取同一月份内所有已关联支付处理器（PayPal、Stripe、Square）的结算记录。
  3. 按金额+日期（±2天）匹配QB记录与处理器结算记录。
  4. 呈现三类差异：
    • 未匹配的处理器结算记录——资金通过PayPal/Stripe/Square到账，但未录入QB
    • 未匹配的QB存款记录——QB显示有收入，但无对应处理器记录（现金？电汇？分类错误？）
    • 金额差异项——记录已匹配，但金额存在差异（手续费、退款拆分等）

Step 2 — Flag suspicious entries

步骤2 — 标记可疑记录

Surface in the same report:
  • Uncategorized transactions — QB entries with no category
  • Suspicious duplicates — same amount, same vendor, within 3 days
  • Missing receipts — QB entries above $75 with no attachment
For each, recommend an action: categorize as X, delete duplicate, attach receipt from inbox.
Wait for owner to triage flagged items before generating the narrative. Do not auto-categorize or auto-delete.
在同一报告中呈现：
  • 未分类交易——QB中未分配类别的记录
  • 可疑重复项——金额相同、供应商相同且时间间隔在3天内的记录
  • 缺失收据——金额超过75美元且未附收据的QB记录
针对每一项给出操作建议：归类为X、删除重复项、从收件箱上传收据。 在生成说明前，需等待企业主处理标记项。不得自动归类或自动删除。

Step 3 — P&L narrative

步骤3 — 损益表（P&L）说明

After triage, generate a plain-English P&L narrative:
{Month YYYY} closed at ${revenue} revenue ({+/-}{X}% vs prior month).
Top driver: {category/customer}. Biggest swing: {category} {direction} ${amount}
because {reason inferred from transactions}.

Margin: {X}% ({+/-}Y pts vs prior). {Cost-side commentary}.

Three notable items:
1. ...
2. ...
3. ...
Numbers come from QB; the why comes from cross-referencing top transactions, vendor names, and prior-month deltas.
处理完标记项后，生成通俗易懂的损益表说明：
{Month YYYY} closed at ${revenue} revenue ({+/-}{X}% vs prior month).
Top driver: {category/customer}. Biggest swing: {category} {direction} ${amount}
because {reason inferred from transactions}.

Margin: {X}% ({+/-}Y pts vs prior). {Cost-side commentary}.

Three notable items:
1. ...
2. ...
3. ...
数据来源于QB；变动原因则通过交叉对比重点交易、供应商名称及上月差异得出。

Step 4 — Export the close packet

步骤4 — 导出结账数据包

Generate two files:
  1. close-packet-{YYYY-MM}.xlsx
     — multi-tab workbook: 
    • Reconciliation
      — QB ↔ processor match table with gap rows highlighted
    • Flagged
      — uncategorized / duplicates / missing receipts
    • P&L
      — formatted income statement with prior-month delta column
    • Trial Balance
      — accounts + ending balances
  2. close-packet-{YYYY-MM}.pdf
     — one-page summary: P&L narrative + top-line numbers + gap count
Save both to the chosen 
--save-to
location. Filename format: 
close-packet-2026-04.xlsx
etc.
生成两类文件：
  1. close-packet-{YYYY-MM}.xlsx
    ——多标签工作簿： 
    • Reconciliation
      ——QB与处理器匹配表，高亮显示差异行
    • Flagged
      ——未分类/重复项/缺失收据记录
    • P&L
      ——带上月差异列的格式化损益表
    • Trial Balance
      ——账户及期末余额
  2. close-packet-{YYYY-MM}.pdf
    ——单页摘要：损益表说明+关键数据+差异数量
将两类文件保存至指定的
--save-to
路径。文件名格式示例：
close-packet-2026-04.xlsx
等。

Connector failures

连接器故障处理

If QuickBooks is unreachable, stop — reconciliation requires QB as the source of truth. If a payment processor (PayPal, Stripe, Square) is unreachable, run reconciliation against the available processors and note "PayPal not connected — PayPal settlements skipped from reconciliation" (or whichever is missing). If all processors are missing, run QB-only analysis and flag it.
若无法连接QuickBooks，需终止流程——账目核对需以QB为基准数据源。若某一支付处理器（PayPal、Stripe、Square）无法连接，则基于可用处理器完成核对，并标注“PayPal未连接——核对过程跳过PayPal结算记录”（或对应缺失的处理器）。若所有处理器均无法连接，则仅运行QB分析并标记该情况。

Approval gates

审批规则

  • Never auto-fix flagged items. Always show the gap, recommend an action, wait for the owner.
  • Never delete duplicates without explicit confirmation. Show both records side-by-side.
  • Saving the packet is auto — it goes to the owner's own drive.
  • 不得自动修复标记项。始终显示差异，给出操作建议，等待企业主处理。
  • 未经明确确认不得删除重复项。需并排展示两条记录。
  • 数据包保存为自动执行——直接保存至企业主的云端存储。

Output

输出结果

End the run with a one-paragraph recap: revenue, margin, gap count remaining (if any), file paths to the saved packet. If gaps were not all resolved, list them so the owner can revisit.
流程结束时生成一段总结：收入、利润率、剩余差异数量（如有）、已保存数据包的文件路径。若差异未全部解决，需列出这些差异供企业主后续处理。