Skip to main content

Finance manual card tracking: Apple Card and X1 Card

Date: 2026-10-04. Stakeholder-approved addition, executed by the finance agent (maverick-muse-finance-001). The Apple Card and X1 Card are not linked to Plaid, so the dashboard could not see their obligations; both are now tracked in the bill registry as manual, email-sourced bills. Commits on jknash/dashboard: registry d95f5ee, generator c94d863, tests 503898a, snapshot f620eed; Cloudflare deployment 9132874b, verified from outside (landing 200, finance behind the Access 302, production and preview).

How manual bills work (generator extension)​

Three small, tested additions to scripts/build_finance_snapshot.py (35 tests green: 31 existing + 4 new):

  • once schedule type — {"type": "once", "date": "YYYY-MM-DD"} generates exactly one occurrence. It exists so a single evidenced cycle can be tracked without inventing a standing due day or minimum.
  • manual: true (+ source: "email") registry flags — the matcher skips manual bills unconditionally: no bank transaction may ever mark one paid. A manual occurrence leaves the unpaid state only when its registry entry is updated from new email evidence.
  • Snapshot markers — manual appears on bill-history entries, upcoming-bills entries, and pay-cycle allocations, so every consumer can see these figures are email-sourced, not bank-verified.

Maintenance contract, recorded in each registry entry's notes: each email sweep replaces the entry's once date/amount from the latest statement or due email for that card, and marks an occurrence paid only from email evidence (e.g. a payment confirmation). Nothing recurs automatically, and balances are context in the notes, never occurrences.

What was added (evidence, not inference)​

  • Apple Card (apple-card-manual): one occurrence, $220.00 due 2026-09-30, status overdue. Amount from the Apple Card Support notice of 2026-10-02 ($220.00 past-due balance due immediately, account 2 days past due); date from Apple's "payment is due today" email of 2026-09-30. A statement-ready email was also seen 2026-10-01.
  • X1 Card (x1-card-manual): one occurrence, $107.00 due 2026-10-07, status upcoming. From the X1 notice of 2026-10-03: a payment of $107 or more due by Oct 7. The $3,697.84 balance (nearly at limit) is recorded in the notes as context only.

No standing schedule, due day, or minimum beyond these single occurrences is asserted for either card.

Effect on the headline numbers​

The snapshot was regenerated from a fresh Plaid pull (2026-10-04 evening; the earlier pull's retained inputs had been lost with a /tmp cleanup). Generated against the same fresh inputs with and without the new registry entries, the cards' isolated effect is exact:

  • Safe-to-spend: $1,370.55 → $1,043.55 (−$327.00)
  • Unpaid allocations: $339.68 → $666.68 (+$327.00)
  • 90-day forecast trough: $2,790.58 → $2,463.58 on 2026-10-14 (−$327.00)

Separately, the fresh pull itself moved the picture versus the afternoon snapshot: Chase checking available fell $5,309.83 → $3,040.23 because pending debits grew by $2,269.60 — the $2,000 Zelle (matched, status pending, dated 2026-10-04) plus new Oct 4 pending spend (Instacart $207.51, Liven $49.98, 7 Brew $12.11). Pending total $2,727.61 reconciles exactly with the current-minus-available gap.

Published by Muse · 2026-10-04.