%)` when `lines > 0`.
Total renders via `fmtUsd`. Created shows `created_at.slice(0, 10)` (date part).
- **B8.** "+ New batch" is a link to `?new=1` (`scroll={false}`), hidden while the form is
open. The inline panel has one required text field `name` (placeholder
"e.g. April 2026 PlusROI", autoFocus), a submit button "Create batch", and a Cancel link
back to `/tools/cc-expenses`.
- **B9.** Flash messages come from query params: `?error=` renders ``,
`?info=` renders `
` (same pattern on all three pages).
- **B10.** `createCcBatch(formData)`: requires trimmed `name` ("Batch name is required.");
inserts `{ org_id, name, created_by: eu?.real_user_id ?? null }`; on success revalidates
`/tools/cc-expenses` and redirects to `/tools/cc-expenses/`. Permission failure:
"Only an owner can create expense batches."
- **B11.** `deleteCcBatch(formData)`: deletes by `.eq('id', id)` — lines removed via FK
`ON DELETE CASCADE`; redirects to `/tools/cc-expenses?info=Batch+deleted.`. The only guard
is the `DeleteForm` browser confirm:
`Delete batch "" and all its lines? Cannot be undone.`
### Statement paste parsing (`lib/cc-expenses.ts` — pure, no I/O)
- **B12.** **Accepted line format** (tab-separated, greedy column slots, extra trailing tabs
ignored — `cols[5+]` never read):
```
{date}\t{description}\t{debit amount}\t{credit amount}\t{running balance}\t
```
Real example: `May 20, 2026\tFACEBK *N7VKLP9RX2\t$7.15\t\t$3,856.56\t`
(column 4 — credit — is usually empty).
- **B13.** `parseExpenseDate(raw)` → `YYYY-MM-DD | null`. Trim; empty → null. ISO passthrough
on `/^(\d{4})-(\d{2})-(\d{2})$/`. Long format on
`/^([A-Za-z]+)\.?\s+(\d{1,2}),?\s+(\d{4})$/` — month name case-insensitive against the
`MONTHS` map (full names + abbreviations: jan, feb, mar, apr, may, jun, jul, aug,
**sep/sept**, oct, nov, dec; optional trailing period, comma optional). Validation: day
1–31, year 1900–2999 — **no per-month day check** ("Feb 31" passes; see edge cases). Output
is zero-padded.
- **B14.** `parseCurrency(raw)` → `number | null`. Trim, strip a single **leading** `$`, strip
ALL commas; empty → null; `Number(...)`; non-finite → null; rounds to cents via
`Math.round(n * 100) / 100`. Sign quirk: `-5` → −5 survives; `$-5.00` → −5; `-$5.00` → null
(`$` isn't leading).
- **B15.** `parseCcLine(raw)` → `ParsedCcLine | null`
(`{ raw_line, expense_date, description, amount_usd, balance_usd }`). Blank/whitespace-only
→ null. Otherwise split on `\t`, trim every column; `cols[0]` → date, `cols[1]` →
description (empty → null), `cols[2]` → debit, `cols[3]` → credit, `cols[4]` → balance.
- **B16.** `amount_usd = debit ?? credit ?? null` — **debit wins if both set**; a credit is
used as an alternate amount with **no sign flip** (Phase-1 decision: both positive).
- **B17.** **Partial parses keep the row**: any non-blank line returns a `ParsedCcLine` even
if every field is null — the row is inserted and shown so the user can see what failed and
fix/delete it. `raw_line` always preserves the verbatim input for audit/re-parse.
- **B18.** `parseCcPaste(input)` splits on `/\r?\n/` (CRLF-safe), parses each line, drops
nulls (blank lines), preserves order.
### Paste ingestion + auto-assign — `appendCcLines(formData)` (`actions.ts`)
- **B19.** Detail page has a paste panel: textarea `paste` (6 rows, monospace) + hidden
`batch_id` + "Add lines" button. Instruction copy: "Tab-separated columns: Date ·
Description · Amount · (Credit) · Balance. Trailing tabs are tolerated. Pastes multiple
times — each paste appends." Placeholder shows two real example lines.
- **B20.** Guards, in order: missing `batch_id` → "Missing batch id."; blank paste → "Paste
some lines first."; zero parsed lines → "No usable lines found in the paste." Permission
failure: "Only an owner can add expense lines."
- **B21.** `line_index` continues from the batch's current max (read `line_index` order DESC
limit 1 maybeSingle; `startIdx = (max ?? -1) + 1`) — **appends preserve paste order across
multiple pastes**. No dedupe: re-pasting the same lines creates duplicates.
- **B22.** All org `cc_auto_rules` are loaded ONCE (select
`id, keyword, project_id, assignment_description, category`, ordered **`created_at` DESC**)
and each parsed line's description is matched in JS via `findAutoRuleMatch`.
- **B23.** `findAutoRuleMatch(description, rules)`: case-insensitive **substring**
(`String.includes`) of each rule's keyword against the description; **first match in list
order wins** — with the created_at-DESC ordering that means **the newest matching rule
wins**. Null/empty description never matches; blank keywords skipped. Returns the whole
rule.
- **B24.** Insert rows are
`{ batch_id, line_index: startIdx + i, raw_line, expense_date, description, amount_usd,
balance_usd, project_id: match?.project_id ?? null, assignment_description:
match?.assignment_description ?? null, category: match?.category ?? null, auto_assigned:
match != null }` — one bulk insert.
- **B25.** Success flash: `Added lines ( auto-assigned).` when k > 0, else
`Added lines.` — redirect back to the batch page with `?info=`.
### Line assignment — `updateCcLine` / `deleteCcLine`
- **B26.** Each line row has an inline form (per-row Save): `SearchableCombobox`
`project_id` (options = org projects **that have a client**, labeled
`` `${client.name} : ${p.name}` `` per ADR #042, sorted by label localeCompare; value =
`projects.id`; placeholder "search projects…"), text `assignment_description` (placeholder
"e.g. Google"), text `category` with a per-row `