/process-expenses
Section titled “/process-expenses”What it does: Extracts structured fields (dates, charges vs. balance, HST, line items) from a vendor bill PDF, with a deterministic reconciliation self-check. v0/v1 = extraction only — no QBO posting.
Where the code lives: ~/ai-config/claude/commands/process-expenses.md (Claude Code slash command; deploys to ~/.claude/commands/ via deploy.sh).
Vendor rules: Core/Accounting/Config/vendors/<vendor>.yaml — accounts, tax codes, exception triggers. First vendor: rogers.yaml (not wikilink-resolvable, YAML file — see Config/vendors/rogers.yaml). Dollar amounts always come from the bill PDF, never from vendor config or Expenses.md.
Usage: /process-expenses <pdf-or-folder> [--from <date>] [--to <date>]
When you actually need it (clarified 2026-08-09): this is the occasional Accounting tool, not part of the routine cycle. /hst-assistance does not call it — they read different inputs (Statements/ vs Bills/) and there is no call path between them. Reach for it when:
- a recurring bill’s rate changes — read the new bill, then record the new split as a
steady_state_periodinConfig/vendors/rogers.yaml. Due next for the wireless +$5 effective 2026-07-15 that the Jun-16-2026 Rogers bill announced - a new bill-type vendor appears and its fields need extracting
- a bill month is flagged TBD in the
/hst-assistanceartifact and needs its figures read from source
Text extraction is pdftext (pdfplumber), not MarkItDown — see AGENTS.md “Document extraction — pick by job”.
See Accounting-Dept-Start Phase 1 for the 3-layer design (extract / vendor-rules / post) and the FY26 Rogers reconciliation this tool produced.