bookkeeping-automation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

When this skill is activated, always start your first response with the 🧢 emoji.

激活本Skill后，首次回复请务必以🧢表情开头。

Bookkeeping Automation

簿记自动化

Bookkeeping is the systematic recording and organizing of all financial transactions for a business. Done well, it produces a reliable single source of truth for every dollar in and out, enabling confident decision-making, clean audits, and accurate tax filings. Automation shifts the work from data entry to exception handling - the machine reconciles the routine, the human resolves the unusual.

This skill covers the design and automation of core bookkeeping workflows: chart of accounts architecture, bank and credit card reconciliation, accounts payable and receivable pipelines, month-end close checklists, recurring journal entries, and expense management. It applies equally to spreadsheet-based setups, QuickBooks, Xero, NetSuite, and custom-built finance tooling.

簿记是对企业所有财务交易进行系统化记录和整理的工作。做好簿记工作，能为每一笔资金的流入和流出提供可靠的单一事实来源，助力做出有依据的决策、顺利通过审计并准确完成纳税申报。自动化将工作重心从数据录入转移到异常处理——机器处理常规事务，人工解决特殊情况。

本Skill涵盖核心簿记工作流的设计与自动化：会计科目表架构、银行及信用卡对账、应付账款（AP）与应收账款（AR）流程、月末结账清单、重复日记账分录以及费用管理。它同样适用于基于电子表格的设置、QuickBooks、Xero、NetSuite以及定制化财务工具。

When to use this skill

何时使用本Skill

Trigger this skill when the user:

Asks how to design or restructure a chart of accounts
Needs to automate or streamline bank reconciliation
Wants to build or improve an accounts payable (AP) workflow
Wants to build or improve an accounts receivable (AR) and collections process
Asks about month-end or year-end close procedures
Needs to create or automate recurring journal entries or accruals
Wants to implement an expense management and reimbursement system
Asks about the difference between accrual and cash basis accounting

Do NOT trigger this skill for:

Tax strategy, tax planning, or tax filing preparation (use a tax-specialist skill)
Financial modeling, forecasting, or FP&A (bookkeeping records history; FP&A projects forward)

当用户有以下需求时，触发本Skill：

询问如何设计或重组会计科目表
需要自动化或优化银行对账流程
想要构建或改进应付账款（AP）工作流
想要构建或改进应收账款（AR）及收款流程
询问月末或年末结账流程
需要创建或自动化重复日记账分录或应计项目
想要实施费用管理与报销系统
询问权责发生制与收付实现制的区别

请勿在以下场景触发本Skill：

税务策略、税务规划或纳税申报准备（请使用税务专业Skill）
财务建模、预测或财务规划与分析（FP&A）（簿记记录历史数据；FP&A侧重未来预测）

Key principles

核心原则

Double-entry is non-negotiable - Every transaction touches at least two accounts: a debit and a credit of equal value. This self-balancing property is what makes accounting auditable. Never design a system that records only one side.
Classify at the source - The cheapest time to categorize a transaction is when it first enters the system. Reclassifying entries later is expensive and error-prone. Design intake workflows (AP approval, expense submission, bank feed rules) to capture the correct account, department, and project code upfront.
Reconciliation is the heartbeat - Reconcile bank and credit card accounts at minimum monthly, ideally weekly. Unreconciled books drift from reality. Reconciliation is what transforms a transaction log into trustworthy financials.
Separate duties - The person who approves a payment should not be the same person who processes it. The person who records a journal entry should not be the only person who reviews it. Segregation of duties prevents both fraud and honest error.
Automate the routine, review the exception - Use bank feed rules, recurring transaction templates, and scheduled journal entries for predictable items. Reserve human attention for variance investigation, approval workflows, and anything over a materiality threshold.

复式记账不可或缺 - 每一笔交易至少涉及两个科目：金额相等的借方和贷方。这种自平衡特性是会计可审计性的基础。绝不要设计只记录单边的系统。
源头分类 - 对交易进行分类的最佳时机是它首次进入系统时。后续重新分类成本高且容易出错。设计录入工作流（AP审批、费用提交、银行流水规则）时，应提前捕获正确的科目、部门和项目代码。
对账是核心 - 银行及信用卡账户至少每月对账一次，理想状态为每周一次。未对账的账簿会与实际情况脱节。对账是将交易日志转化为可信财务数据的关键步骤。
职责分离 - 批准付款的人员不应同时负责处理付款。记录日记账分录的人员不应是唯一审核该分录的人。职责分离既能防止欺诈，也能避免无心之失。
自动化常规事务，审核异常情况 - 对可预测事项使用银行流水规则、重复交易模板和定时日记账分录。将人工精力集中在差异调查、审批工作流以及超过重要性阈值的事项上。

Core concepts

核心概念

Double-entry bookkeeping

复式记账法

Every financial event is recorded as a pair of equal and opposite entries. Debits increase asset and expense accounts; credits increase liability, equity, and revenue accounts. The fundamental equation always holds:

Assets = Liabilities + Equity

A simple example - paying a $500 vendor invoice:

Debit:  Accounts Payable   $500   (reduce liability)
Credit: Cash/Bank           $500   (reduce asset)

每一项财务事件都被记录为一对金额相等、方向相反的分录。借方增加资产和费用科目；贷方增加负债、所有者权益和收入科目。基本会计等式始终成立：

Assets = Liabilities + Equity

简单示例 - 支付500美元供应商发票：

Debit:  Accounts Payable   $500   (减少负债)
Credit: Cash/Bank           $500   (减少资产)

Chart of accounts structure

会计科目表结构

The chart of accounts (COA) is the master list of every account used to classify transactions. A well-structured COA uses a numeric scheme that groups by type:

Range	Type	Examples
1000-1999	Assets	Cash, AR, Inventory, Fixed Assets
2000-2999	Liabilities	AP, Credit Cards, Loans, Deferred Rev
3000-3999	Equity	Common Stock, Retained Earnings
4000-4999	Revenue	Product Sales, Service Revenue
5000-5999	Cost of Goods Sold	Direct Labor, Materials, Fulfillment
6000-6999	Operating Expenses	Payroll, Rent, Software, Marketing
7000-7999	Other Income/Expense	Interest Income, Gain/Loss on Sale

Keep the COA as flat as possible. Sub-accounts add granularity but also complexity. Add a new account only when reporting genuinely requires it - not speculatively.

会计科目表（COA）是用于分类交易的所有科目的主列表。结构合理的会计科目表采用数字编码方案，按类型分组：

编码范围	科目类型	示例
1000-1999	资产类	现金、AR、存货、固定资产
2000-2999	负债类	AP、信用卡、贷款、递延收入
3000-3999	所有者权益类	普通股、留存收益
4000-4999	收入类	产品销售收入、服务收入
5000-5999	销货成本类	直接人工、材料、履约成本
6000-6999	营业费用类	薪资、租金、软件、营销费用
7000-7999	其他收入/费用类	利息收入、出售损益

会计科目表应尽量扁平化。子科目虽能增加粒度，但也会提升复杂度。仅当报告确实需要时才添加新科目——不要凭猜测添加。

Accrual vs. cash basis

权责发生制 vs 收付实现制

Dimension	Cash Basis	Accrual Basis
Revenue recorded	When cash is received	When earned (invoice sent or service done)
Expense recorded	When cash is paid	When incurred (bill received or work done)
Accuracy	Simpler, matches bank	More accurate picture of financial health
Required for	Small businesses, sole traders	Companies >$25M revenue (US GAAP), audit
Key accounts	No AR, no AP	AR, AP, accrued liabilities, prepaid

Most growing businesses should use accrual. Cash basis can mask real obligations (e.g., a large unpaid bill not showing up as an expense yet).

维度	收付实现制	权责发生制
收入确认时间	收到现金时	赚取收入时（开具发票或完成服务）
费用确认时间	支付现金时	产生费用时（收到账单或完成工作）
准确性	更简单，与银行流水一致	更准确反映财务状况
适用场景	小型企业、个体经营者	年收入超过2500万美元的公司（美国GAAP）、审计要求
核心科目	无AR、无AP	AR、AP、应计负债、预付费用

大多数成长型企业应采用权责发生制。收付实现制可能掩盖真实债务（例如，大额未付账单尚未计入费用）。

Reconciliation

对账

Reconciliation is the process of comparing two sets of records to ensure they agree. Types:

Bank reconciliation - Match the general ledger cash account to the bank statement. Identify timing differences (outstanding checks, deposits-in-transit) and errors.
Credit card reconciliation - Match the credit card GL account to the card statement.
AR aging reconciliation - Ensure the AR subledger total matches the AR control account.
AP aging reconciliation - Ensure the AP subledger total matches the AP control account.
Balance sheet reconciliation - Every BS account should have a schedule supporting its balance (e.g., fixed asset roll-forward, prepaid amortization schedule).

对账是比较两组记录以确保一致的过程。类型包括：

银行对账 - 将总分类账（GL）现金科目与银行对账单进行匹配。识别时间差异（未兑现支票、在途存款）和错误。
信用卡对账 - 将总分类账（GL）信用卡科目与信用卡对账单进行匹配。
应收账款账龄对账 - 确保AR明细分类账总额与AR控制科目一致。
应付账款账龄对账 - 确保AP明细分类账总额与AP控制科目一致。
资产负债表对账 - 每个资产负债表科目都应有支持其余额的明细表（例如，固定资产滚动表、预付费用摊销表）。

Common tasks

常见任务

Design a chart of accounts

设计会计科目表

Start with the standard numeric ranges above. Reserve gaps (e.g., 1100-1199 for cash, 1200-1299 for AR) so related accounts cluster together.
Map every real transaction type to an account. If a transaction cannot be mapped, add an account - but never use a catch-all "Miscellaneous" account for regular activity.

Define a naming convention and enforce it:

[Type] - [Detail]

, e.g.,

6200 - Software Subscriptions

6210 - Software Subscriptions - Engineering

Create departments or classes at the reporting layer, not by multiplying accounts. Use one
```
6100 - Payroll
```
account with a department tag, not separate payroll accounts per team.
Review quarterly: retire unused accounts, merge near-duplicates, add only what reporting genuinely requires.

从上述标准数字编码范围开始。预留间隔（例如，1100-1199用于现金科目，1200-1299用于AR），使相关科目集中在一起。
将每一种实际交易类型映射到一个科目。如果某笔交易无法映射，则添加一个新科目——但绝不要将常规交易归入“其他费用”这类万能科目。

定义命名规则并强制执行：

[科目类型] - [明细]

，例如

6200 - 软件订阅费

、

6210 - 软件订阅费 - 工程部

。

在报告层面设置部门或类别，而非通过增加科目数量实现。使用一个
```
6100 - 薪资
```
科目并添加部门标签，而非为每个团队设置单独的薪资科目。
每季度审核：停用未使用的科目，合并近似重复的科目，仅添加报告确实需要的科目。

Automate bank reconciliation

自动化银行对账

Manual process baseline:

1. Export bank statement (CSV or OFX)
2. Import into accounting system or spreadsheet
3. Match each bank line to a GL entry by date, amount, and description
4. Flag unmatched items on either side
5. Investigate and resolve exceptions
6. Sign off when difference = 0

Automation levers:

Bank feed rules - In QuickBooks/Xero, create rules that auto-categorize recurring transactions by payee name or description pattern (e.g., "STRIPE" -> Revenue).
Fuzzy matching scripts - For custom setups, match bank lines to GL entries by amount tolerance and date window (±1 day, ±$0.01).
Auto-import OFX/CSV - Schedule a daily import so the feed is never more than 24 hours stale.
Exception queues - Surface only the unmatched items for human review. The matched 90% should require zero human time.

Key reconciliation formula:

Bank Statement Ending Balance
+ Deposits in Transit
- Outstanding Checks
+/- Bank Errors
= Adjusted Bank Balance

GL Cash Balance
+/- GL Errors / Unrecorded Items
= Adjusted Book Balance

Adjusted Bank Balance must equal Adjusted Book Balance

手动流程基准：

1. 导出银行对账单（CSV或OFX格式）
2. 导入会计系统或电子表格
3. 按日期、金额和描述将每笔银行流水与GL分录匹配
4. 标记双方的未匹配项
5. 调查并解决异常
6. 当差异为0时签字确认

自动化手段：

银行流水规则 - 在QuickBooks/Xero中，创建规则，根据付款方名称或描述模式自动分类重复交易（例如，“STRIPE” -> 收入）。
模糊匹配脚本 - 对于自定义系统，通过金额容差和日期窗口（±1天，±0.01美元）将银行流水与GL分录匹配。
自动导入OFX/CSV - 安排每日导入，确保流水数据的延迟不超过24小时。
异常队列 - 仅向人工展示未匹配项。已匹配的90%事务无需人工干预。

对账核心公式：

银行对账单期末余额
+ 在途存款
- 未兑现支票
± 银行错误
= 调整后银行余额

GL现金科目余额
± GL错误/未记录项
= 调整后账簿余额

调整后银行余额必须等于调整后账簿余额

Manage AP workflow

管理应付账款（AP）工作流

A clean AP process has five stages with clear owners:

Receive - Vendor sends invoice. Route to a single AP email inbox or portal. Capture: vendor, amount, due date, PO number (if applicable).
Code - AP team assigns GL account, department/class, and project. Verify against purchase order or contract if over approval threshold.
Approve - Require digital approval from budget owner. Use a materiality ladder: e.g., <$500 AP auto-approves, $500-$5K requires manager, >$5K requires CFO.
Pay - Batch payments on a schedule (e.g., Tuesday/Thursday). Record the payment in the GL on the date the funds leave. Use ACH over checks where possible.
Reconcile - Confirm paid invoices clear in AP aging. Reconcile AP subledger to control account at month-end.

Automation targets:

Auto-extract invoice data with OCR (e.g., Dext, Hubdoc, AWS Textract)
Duplicate invoice detection by vendor + amount + date proximity
Auto-match invoices to purchase orders (3-way match: PO, receipt, invoice)
Scheduled payment runs with pre-built approval email workflows

规范的AP流程包含五个阶段，且每个阶段都有明确负责人：

接收 - 供应商发送发票。将发票发送至统一的AP邮箱或门户。捕获信息：供应商、金额、到期日、采购订单编号（如有）。
编码 - AP团队分配GL科目、部门/类别和项目。若超过审批阈值，需对照采购订单或合同进行验证。
审批 - 需由预算负责人进行数字审批。采用分级审批机制：例如，<500美元由AP自动审批，500-5000美元需经理审批，>5000美元需CFO审批。
支付 - 按计划批量付款（例如，周二/周四）。在资金划出当日将付款记录至GL。尽可能使用ACH转账而非支票。
对账 - 确认已付款发票从AP账龄表中清除。月末将AP明细分类账与控制科目进行对账。

自动化目标：

使用OCR自动提取发票数据（例如Dext、Hubdoc、AWS Textract）
通过供应商+金额+日期 proximity检测重复发票
自动将发票与采购订单匹配（三方匹配：采购订单、收货单、发票）
预构建审批邮件工作流的定时付款运行

Manage AR and collections

管理应收账款（AR）与收款

AR management is revenue already earned but not yet collected. Aging matters:

Age Bucket	Action
0-30 days	Standard - no action unless terms exceeded
31-60 days	Automated reminder email
61-90 days	Personal outreach from AR team
91-120 days	Escalate to account manager or leadership
120+ days	Consider write-off or collections agency

Automation targets:

Auto-generate and send invoices from billing system on trigger (usage, milestone, date)
Automated dunning sequence: email at net+1, net+7, net+14, net+30 overdue
Payment portal link in every invoice email (Stripe, PayPal, ACH direct)
Weekly AR aging report auto-emailed to finance and sales leadership
Auto-apply cash receipts to oldest open invoices (FIFO matching)

Month-end AR tasks:

Reconcile AR subledger total to GL control account
Review aging for bad debt candidates
Post allowance for doubtful accounts entry if needed

AR管理针对已赚取但尚未收回的收入。账龄至关重要：

账龄区间	行动
0-30天	常规处理 - 未逾期则无需操作
31-60天	自动发送提醒邮件
61-90天	AR团队进行个性化跟进
91-120天	升级至客户经理或领导层处理
120天以上	考虑核销或委托收款机构

自动化目标：

触发后从计费系统自动生成并发送发票（按使用量、里程碑、日期）
自动催款序列：逾期1天、7天、14天、30天时发送邮件
每封发票邮件中包含付款门户链接（Stripe、PayPal、直接ACH）
每周自动向财务和销售领导层发送AR账龄报告
自动将现金收款应用于最早的未结发票（先进先出匹配）

月末AR任务：

核对AR明细分类账总额与GL控制科目一致
审核账龄表以识别坏账候选
如有需要，计提坏账准备分录

Streamline month-end close

优化月末结账

See

references/month-end-checklist.md

for the full detailed checklist.

High-level close sequence:

Week 1 of close:
  [ ] Lock prior-period transactions (prevent backdated entries)
  [ ] Complete bank and credit card reconciliations
  [ ] Reconcile AR and AP subledgers to control accounts
  [ ] Process payroll journal entries

Week 2 of close:
  [ ] Post depreciation and amortization entries
  [ ] Post accruals (uninvoiced expenses, deferred revenue adjustments)
  [ ] Post prepaid amortization
  [ ] Reconcile intercompany accounts (if applicable)

Final close steps:
  [ ] Review trial balance for anomalies
  [ ] Tie revenue to billing system
  [ ] Run flux analysis (month-over-month variance review)
  [ ] CFO/Controller sign-off
  [ ] Lock period in accounting system
  [ ] Distribute financial package

Target a 5 business day close. Every day over 5 is a process failure worth investigating.

完整的详细清单请参阅

references/month-end-checklist.md

。

高层级结账流程：

结账第1周：
  [ ] 锁定前期交易（防止回溯录入）
  [ ] 完成银行和信用卡对账
  [ ] 核对AR和AP明细分类账与控制科目一致
  [ ] 处理薪资日记账分录

结账第2周：
  [ ] 计提折旧和摊销分录
  [ ] 计提应计项目（未开票费用、递延收入调整）
  [ ] 计提预付费用摊销
  [ ] 核对公司间账户（如适用）

最终结账步骤：
  [ ] 审核试算平衡表中的异常
  [ ] 将收入与计费系统核对
  [ ] 执行波动分析（月度差异回顾）
  [ ] CFO/财务总监签字确认
  [ ] 在会计系统中锁定期间
  [ ] 分发财务报告包

目标是5个工作日完成结账。超过5天的每一天都意味着流程存在需要排查的问题。

Automate recurring journal entries

自动化重复日记账分录

Recurring entries are predictable in amount or calculation method. Automate them with templates that post on a schedule:

Entry Type	Frequency	Calculation
Depreciation	Monthly	Asset cost / useful life months
Prepaid amortization	Monthly	Prepaid balance / remaining months
Accrued payroll	Monthly	Days worked but unpaid at period-end
Deferred revenue release	Monthly	Contract value / contract months
Interest accrual	Monthly	Outstanding loan balance * (rate / 12)

Template structure for any recurring JE:

Entry name:    [Descriptive name - no abbreviations]
Debit account: [Account number and name]
Credit account:[Account number and name]
Amount method: [Fixed / Formula / % of balance]
Frequency:     [Monthly / Quarterly / Annual]
Auto-reverse:  [Yes for accruals / No for amortization]
Memo:          [Period: {month} {year} - {description}]

Set accruals to auto-reverse on the first day of the next period. This prevents the accrual from permanently inflating the expense balance when the actual invoice arrives.

重复分录的金额或计算方法具有可预测性。使用模板按计划自动过账：

分录类型	频率	计算方式
折旧	月度	资产成本 / 使用年限月数
预付费用摊销	月度	预付余额 / 剩余月数
应计薪资	月度	期末已工作但未支付的天数对应的薪资
递延收入释放	月度	合同金额 / 合同期限月数
应计利息	月度	未偿还贷款余额 * (利率 / 12)

任何重复日记账分录的模板结构：

分录名称:    [描述性名称 - 请勿缩写]
借方科目: [科目编号及名称]
贷方科目:[科目编号及名称]
金额计算方式: [固定值 / 公式 / 余额百分比]
频率:     [月度 / 季度 / 年度]
自动冲销:  [应计项目选是 / 摊销选否]
备注:          [期间: {月份} {年份} - {描述}]

将应计项目设置为在下一期间的第一天自动冲销。这样可以防止当实际发票到达时，应计项目永久虚增费用余额。

Implement expense management

实施费用管理

A clean expense process prevents both fraud and friction:

Policy first - Publish a clear expense policy: what's reimbursable, per-diems, receipt thresholds, approval chains. No policy means no enforcement.
Capture at point of purchase - Employees photograph receipts immediately (Expensify, Ramp, Brex). Never rely on paper receipts surviving a month.
Code on submission - Employee selects category and project. Finance reviews, not re-enters.
Approval workflow - Manager approves via email or app before finance processes.
Sync to GL - Connect expense tool to accounting system. Entries post automatically with correct account, department, and project coding.
Reimburse on schedule - Process reimbursements on a fixed weekly cadence. Unpredictable reimbursement is a major employee satisfaction issue.

For company card programs:

Issue cards with individual spend limits and MCC (merchant category code) restrictions
Require receipt + memo within 48 hours of transaction
Auto-lock cards with outstanding unreconciled transactions over 30 days

规范的费用流程可同时防止欺诈和减少摩擦：

先定政策 - 发布清晰的费用政策：可报销项目、每日津贴、收据阈值、审批链。无政策则无法执行。
购买时捕获信息 - 员工应立即拍摄收据（使用Expensify、Ramp、Brex）。绝不要依赖纸质收据留存一个月。
提交时编码 - 员工选择类别和项目。财务仅审核，不重新录入。
审批工作流 - 经理通过邮件或应用审批后，财务再处理。
同步至GL - 将费用工具与会计系统连接。分录自动过账，且带有正确的科目、部门和项目编码。
按计划报销 - 固定每周处理报销。报销时间不可预测会严重影响员工满意度。

对于公司卡计划：

为员工发放带有个人消费限额和商户类别码（MCC）限制的卡片
要求交易后48小时内提交收据+备注
对超过30天未对账的未结交易自动锁定卡片

Anti-patterns / common mistakes

反模式 / 常见错误

Mistake	Why it's wrong	What to do instead
Using a single "Miscellaneous Expense" account for anything unusual	Makes financials unauditable; hides real spend patterns	Create the right account. If it recurs twice, it deserves its own account
Recording expenses on cash basis while using accrual for revenue	Produces misleading P&L - expenses are understated relative to the revenue they generated	Pick accrual or cash consistently and apply it to both sides
Reconciling only at year-end	Errors compound over 12 months; finding a $50K discrepancy in December is a crisis	Reconcile bank accounts monthly at minimum, AR/AP weekly
Letting AP aging grow unchecked	Late payments damage vendor relationships and can trigger supply disruptions	Review AP aging weekly; pay on agreed terms, not whenever
Auto-posting all bank feed transactions without review	Bank feed rules misfire; creates a false sense of reconciliation while errors accumulate	Review and approve bank feed matches before they post, or review exceptions daily
Not using auto-reversing entries for accruals	Accrual posts in Month 1; actual invoice also posts in Month 2; expense is double-counted	Always set accruals to auto-reverse on the first day of the following period

错误	危害	正确做法
将所有异常交易归入单一“其他费用”科目	导致财务数据无法审计；隐藏真实支出模式	创建对应的科目。若某类交易出现两次，就值得拥有独立科目
收入采用权责发生制而费用采用收付实现制	生成误导性的利润表——费用相对于所产生的收入被低估	统一选择权责发生制或收付实现制，并应用于所有交易
仅在年末对账	错误会在12个月内累积；12月发现5万美元差异会引发危机	银行账户至少每月对账一次，AR/AP每周对账
放任AP账龄无限增长	逾期付款会损害供应商关系，并可能引发供应中断	每周审核AP账龄表；按约定条款付款，而非随意付款
自动过账所有银行流水交易而不审核	银行流水规则可能失效；在错误累积的同时产生已对账的错觉	过账前审核并确认银行流水匹配，或每日审核异常项
应计项目不使用自动冲销分录	应计项目在第1个月过账；实际发票在第2个月过账；费用被重复计算	务必将应计项目设置为在下一期间的第一天自动冲销

References

参考资料

For detailed content on specific topics, read the relevant file from

references/

```
references/month-end-checklist.md
```
- Step-by-step month-end close checklist with task owners, timing, and sign-off requirements

Only load a references file if the current task requires deep detail on that topic.

如需特定主题的详细内容，请阅读

references/

中的相关文件：

```
references/month-end-checklist.md
```
- 分步式月末结账清单，包含任务负责人、时间安排和签字确认要求

仅当当前任务需要该主题的详细内容时，才加载参考资料文件。