coreyhaines31/makerskills / skills/company-cfo
company-cfo
VerifiedMonthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.8 KB |
| references/categorization.md | markdown | 4.1 KB |
| references/company-config-template.md | markdown | 4.8 KB |
| references/eom-cash-methodology.md | markdown | 5.2 KB |
| references/report-template.md | markdown | 5.2 KB |
| references/scenario-projector.md | markdown | 6.7 KB |
| references/traps.md | markdown | 6.5 KB |
references/traps.md
View on GitHub# CFO workflow traps
Universal categorization + reconciliation traps that recur across CFO workflows. Check each every monthly run.
## Cash-vs-credit double-count
If your bank shows a monthly "credit card autopay" outflow AND the credit card account shows individual charges, counting both double-counts every SaaS bill.
**Fix**: Filter to cash accounts only when computing outflows. Treat the credit card as a debt account (individual charges are visible on the CC statement, but the CC autopay from checking is what actually leaves cash).
Alternative: treat the CC individual charges as your source of truth and exclude the autopay from cash outflow analysis. Both work — pick one and lock it.
## Internal transfers
Transfers between your own accounts (Checking ↔ Savings, brokerage ↔ checking, subsidiary ↔ parent) net to zero within the company but appear as separate transactions.
**Fix**: Filter out `kind=internalTransfer` (or equivalent) OR match by account-pair-and-timestamp OR sum only OUTGOING transactions to accounts you don't own.
Common gotcha: sweep accounts (auto-move idle cash to savings for yield) generate internal transfers daily. Include them in the exclusion filter.
## Currency mismatches
Contractor payment tools often return `destination_amount` in the worker's payout currency (JPY, EUR, GBP, INR, etc.) — not USD.
**Fix**: Always use `source_amount` (or equivalent — different tools name it differently) for base-currency cost analysis.
Common tools + right field:
- **Plane**: `funding.amount` (USD funding) vs `destination_amount` (worker's local currency) → use `funding.amount`
- **Deel**: `source_amount` vs `destination_amount` → use `source_amount`
- **Gusto** (US-only): USD everywhere, no ambiguity
- **Wise Business**: check the API docs — the naming varies by endpoint
## Distribution count mismatch
If N partners should get a monthly distribution and only N-1 appear in the bank data, flag the missing partner.
**Common causes**:
- One partner is deferring their draw to preserve cash
- One partner's ACH bounced or was rejected (rare, but worth catching)
- Distribution was routed to a different account than usual (e.g., moving from personal checking to an LLC-owned brokerage)
- The payroll platform processed the distribution as a W-2 payment instead of an owner draw (common when there's a comp-structure change mid-month)
**Fix**: Ask leadership to confirm — don't guess. The report should note which N-1 distributions occurred + flag the missing one.
## Held deductions residual
Total payroll debits in the bank rarely EXACTLY match payroll-tool API totals — there's usually a small residual ($100-$2K) from held deductions:
- Retirement contributions held for the 401k custodian
- Benefits held for insurance carriers
- Tax withholdings held for quarterly payment
- Garnishments (rare but real)
- Corrections + adjustments applied later
**Fix**: Allow ~$1K-$2K residual as normal. Flag anything bigger — that's usually a missed transaction or a categorization bug.
## Cash-basis vs accrual lag (expense management)
Expense management tools (Ramp / Brex / Divvy) show WHEN expenses were submitted / approved. Bank shows WHEN reimbursement was PAID OUT.
These can lag 1-4 weeks. Reconciliation between expense-mgmt total and bank total will always show a delta.
**Fix**: Use **bank** as the source of truth for cash-basis reporting (matches what actually left the account). Use expense-mgmt for spend-by-category reporting (matches spend by category). Note the two in the report — they're different lenses on different questions.
## Payment processor lag
Payment processors (Stripe, etc.) charge customers on day X but payout to your bank on day X+2 or later. Monthly Stripe payout cadence lands the whole month's revenue at EOM.
**Fix**: For MRR + revenue reporting, use processor API (charges) as source of truth. For cash-in-bank reporting, use bank inflows. They will not match — that's expected — but they should be reconcilable via known payout schedules.
## Missing revenue sources (invisible in primary processor)
If you bill through multiple platforms (Stripe + Paddle, Stripe + direct invoicing, Stripe + a marketplace's payment intermediary), the primary processor's MRR is an undercount.
**Fix**: Add all revenue sources to the methodology in your config doc. Query each independently. Reconcile against bank inflows.
Common example: SaaS with a primary Stripe subscription AND a "Mallow-style" secondary invoicing platform. Stripe MRR shows $80K; total revenue from all sources is $95K. Reporting Stripe MRR only understates cash generation.
## Software baseline drift
The monthly SaaS bill (dominated by autopay from corporate cards) shifts as tools are added / removed. Model the current baseline, not last year's — a stale baseline creates optimistic cash projections.
**Fix**: Every quarter, review the actual last-3-month software autopay average. Update `baselineMrr` and `OPEX_DEFAULTS` in the projector to match. Don't project with a lower software baseline "to be conservative" — the projection is inaccurate.
## Categorization drift mid-year
Changing how a category is defined mid-year makes trends unreadable. If June's "software" category includes AI subscriptions but May's didn't, month-over-month software growth is noise.
**Fix**: Lock categories at the start of the fiscal year. If a new expense type appears that doesn't fit, add a new category at year-end + document in the memory note. See `categorization.md`.
## Partner comp-structure changes
If a partner's W-2 salary decreases by $X and their monthly distribution increases by $X, total comp is unchanged. But the "team" (payroll) line drops and the "distributions" line rises — this WILL show up as a trend break in your monthly charts.
**Fix**: Note comp-structure changes in the "why" paragraph. Don't read the team-line drop as a real cost decrease.
## The cash floor applies to the LOW, not the EOM HIGH
EOM cash is the cycle HIGH (Stripe payout just landed). Most of the month you're at the intramonth LOW.
**Fix**: Weekly cash pulse (weekly mode of this skill) monitors the low. Cash floor checks apply to the low. See `eom-cash-methodology.md` for the intramonth-low formulas by payout cadence.
## Add your own
Every CFO workflow discovers company-specific traps over time. Document them in your config doc in `${COMPANY_CFO_ROOT}` under a "Traps documented for this company" section. This file is the universal starter; your company's config doc is where the specific muscle memory lives.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |