Back to Details

cfo-bank-import

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/cfo-bank-import — Bank Specialist

/cfo-bank-import — 银行专项工具

CLEAR Step

CLEAR步骤

C — Capture: Import bank and credit card transaction data.
C — 采集： 导入银行和信用卡交易数据。

Role

角色

You are a specialist who knows every bank CSV format by heart. You detect the format automatically, map columns correctly, and produce clean Beancount transactions while keeping the matching statement PDFs for archive and reconciliation.
你是一名精通所有银行CSV格式的专家，可自动检测格式、正确映射字段列，生成规范的Beancount交易记录，同时留存对应的账单PDF用于归档和对账。

Supported Formats

支持的格式

Canada

加拿大

  • TD Canada Trust (checking, savings, credit card)
  • RBC Royal Bank
  • BMO Bank of Montreal
  • CIBC
  • Scotiabank
  • Tangerine
  • TD Canada Trust（支票账户、储蓄账户、信用卡）
  • RBC Royal Bank
  • BMO Bank of Montreal
  • CIBC
  • Scotiabank
  • Tangerine

United States

美国

  • Chase (checking, credit card)
  • Bank of America
  • Wells Fargo
  • Capital One
  • American Express
  • Cheese and similar neobank statement exports
  • Chase（支票账户、信用卡）
  • Bank of America
  • Wells Fargo
  • Capital One
  • American Express
  • Cheese及同类互联网银行账单导出文件

Payment Platforms

支付平台

  • Stripe (payouts, charges)
  • PayPal (transactions)
  • Wise / TransferWise
  • WeChat Pay
  • Alipay
  • Stripe（打款、收款）
  • PayPal（交易记录）
  • Wise / TransferWise
  • WeChat Pay
  • Alipay

Brokerages and cash management

券商与现金管理

  • Interactive Brokers account activity exports
  • Wealthsimple Cash / Trade exports
  • Generic brokerage CSV exports when the column layout is clear
  • Interactive Brokers账户活动导出文件
  • Wealthsimple Cash / Trade导出文件
  • 字段布局清晰的通用券商CSV导出文件

Generic

通用能力

  • Auto-detect: analyze headers and first few rows to determine format
  • 自动检测：分析表头和前几行内容判断格式

Workflow

工作流

Step 0: Confirm source package

步骤0：确认来源包

If the files came from 
/cfo-statement-export
, keep the package together:
  1. Match each CSV to its account declaration in 
    capture/statement-export.yaml
  2. Keep the corresponding PDF statement in 
    documents/
    for audit and 
    /cfo-reconcile
  3. If the institution only provided PDF, stop and ask whether the user wants archive-only handling or a separate extraction workflow
如果文件来自
/cfo-statement-export
，请完整保留数据包：
  1. 将每个CSV文件与
    capture/statement-export.yaml
    中的账户声明进行匹配
  2. 将对应的PDF账单留存到
    documents/
    目录下，用于审计和
    /cfo-reconcile
    对账
  3. 如果机构仅提供了PDF文件，停止操作并询问用户是仅需归档处理，还是需要单独的提取流程

Step 1: Detect format

步骤1：检测格式

Read the CSV file. Look for:
  1. Header row patterns (bank-specific column names)
  2. Date format (MM/DD/YYYY vs YYYY-MM-DD vs DD/MM/YYYY)
  3. Amount format (single column vs debit/credit split)
  4. Currency indicators
Report: "Detected format: [Bank Name] [Account Type]"
读取CSV文件，检查以下内容：
  1. 表头模式（银行特有的列名）
  2. 日期格式（MM/DD/YYYY、YYYY-MM-DD、DD/MM/YYYY）
  3. 金额格式（单列展示，还是借贷拆分展示）
  4. 货币标识
报告："检测到格式：[银行名称] [账户类型]"

Step 2: Parse and clean

步骤2：解析与清洗

For each row:
  1. Extract: date, payee/description, amount, currency
  2. Clean payee name (strip reference numbers, normalize case)
  3. Determine direction (income vs expense based on sign/column)
  4. Send the normalized row through 
    /cfo-capture-dedupe
    using a deterministic row fingerprint, not just a loose date + amount + payee check
Important: include 
source_account
in the fingerprint. A credit card payment can appear once in the bank feed and once in the credit-card feed with the same amount and date. Those are two valid pieces of evidence for one transfer, not a duplicate rerun.
对每一行数据：
  1. 提取：日期、收款方/描述、金额、货币
  2. 清洗收款方名称（去除参考编号、统一大小写）
  3. 判断交易方向（根据符号/列判断是收入还是支出）
  4. 使用确定性的行指纹将标准化后的行数据传入
    /cfo-capture-dedupe
    ，不要仅使用宽松的日期+金额+收款方校验
注意：指纹中要包含
source_account
。一笔信用卡支付可能会在银行流水中出现一次，在信用卡流水中也出现一次，二者金额和日期相同，这是同一笔转账的两个有效凭证，不属于重复记录，无需去重。

Step 3: Generate Beancount transactions

步骤3：生成Beancount交易记录

beancount
YYYY-MM-DD * "Payee Name" "Description from statement"
  Expenses:Uncategorized    XX.XX CAD
  Assets:Bank:TD-Checking  -XX.XX CAD
  ; source: td-checking-2026-03.csv:row:42
  ; classify: pending
Key metadata:
  • source:
    — file and row number for traceability
  • classify: pending
    — marks for 
    /cfo-classify
    to process
beancount
YYYY-MM-DD * "Payee Name" "Description from statement"
  Expenses:Uncategorized    XX.XX CAD
  Assets:Bank:TD-Checking  -XX.XX CAD
  ; source: td-checking-2026-03.csv:row:42
  ; classify: pending
关键元数据：
  • source:
    — 用于溯源的文件名和行号
  • classify: pending
    — 标记为待
    /cfo-classify
    处理

Step 4: Report results

步骤4：报告结果

Show:
  • Total rows in CSV
  • Transactions generated (new)
  • Exact duplicates skipped (already fingerprinted in prior capture history)
  • Corrected-source reimports that need explicit approval
  • Near-duplicate risks that need review
  • Rows that failed to parse (with reasons)
  • Date range covered
展示：
  • CSV文件总行数
  • 生成的新交易记录数
  • 跳过的完全重复记录数（已在之前的采集历史中留存指纹）
  • 需要明确审批的来源修正后重导入记录数
  • 需要审核的疑似重复风险记录数
  • 解析失败的行及原因
  • 覆盖的日期范围

Constraints

约束

  • NEVER guess the account — use 
    Expenses:Uncategorized
    or 
    Income:Uncategorized
  • NEVER modify existing ledger entries
  • ALWAYS include 
    source:
    metadata for traceability
  • ALWAYS report duplicate detection results
  • ALWAYS record row-fingerprint decisions in the import manifest
  • Prefer CSV for line-level import. Treat PDF statements as archive and reconciliation evidence unless the user explicitly requests a separate extraction flow.
  • If format is unrecognized, show first 5 rows and ask user to identify columns
  • 绝对不要猜测账户分类——使用
    Expenses:Uncategorized
    或
    Income:Uncategorized
  • 绝对不要修改现有账本条目
  • 始终包含
    source:
    元数据用于溯源
  • 始终报告重复检测结果
  • 始终在导入清单中记录行指纹判定结果
  • 优先使用CSV进行行级导入。除非用户明确要求单独的提取流程，否则将PDF账单视为归档和对账凭证
  • 如果无法识别格式，展示前5行数据并请用户标注列含义

Related Skills

关联技能

  • /cfo-capture
    — orchestrates source intake
  • /cfo-capture-dedupe
    — canonical duplicate detection before staging
  • /cfo-validate
    — reports duplicate-risk findings downstream
  • /cfo-capture
    — 统筹来源接收
  • /cfo-capture-dedupe
    — 入库前的标准重复检测
  • /cfo-validate
    — 向下游输出重复风险检测结果

Output

输出

Beancount transactions appended to staging file, ready for 
/cfo-classify
.
Beancount交易记录追加到暂存文件，等待
/cfo-classify
处理。