fix(bank-reco): known-patterns.json — Mistral is an ANNUAL subscription, not monthly #56

Closed
opened 2026-07-11 18:19:48 +02:00 by arcodange · 0 comments
Owner

Small correction from the 2026-07-11 regularization (source: the actual invoice PDF MSTRL-API-814045-001, 2026-04-02, "Abonnement annuel - Le Chat Pro - Annual", 143,90 HT / 172,68 TTC).

.claude/skills/arcodange-bank-reco/known-patterns.json currently documents the MISTRAL.AI card debit as "Récurrent mensuel" — it is annual (next expected ~2027-04). This mis-set expectation cost investigation time ("where are the May/June Mistral debits?" — there are none).

While in there:

  • Anthropic (CLAUDE.AI SUBSCRIPTION) pattern: April was on the Qonto card, but the May/June receipts (#2344-8391, #2997-4837 in books@) have no Qonto debit — probably the personal card (fk_account=3, API-invisible). Document the pattern as "payment rail moved — personal-card lane, see #57".
  • Both AI subscriptions are now RECORDED supplier invoices (post-replay), so these patterns may graduate from "known bank-only gap" to "matched" — re-check what bank match reports after the prod replay and prune accordingly.

Acceptance: bank match --since 2026-01-01 after the prod replay shows no stale "intentional gap" annotations for entries that are now properly recorded.


Execution — Blocked by: the prod replay of the 2026-07-11 pack (the re-check depends on it; the annual-vs-monthly text fix itself can land anytime) · Blocks: none · Human gates: none.
Start: claude --worktree known-patterns-fix from the erp repo root; edit .claude/skills/arcodange-bank-reco/known-patterns.json, then (post-replay) run bank match --since 2026-01-01.
Done means: corrected patterns + post-replay match output posted here → PR merged with Closes #56.

Small correction from the 2026-07-11 regularization (source: the actual invoice PDF `MSTRL-API-814045-001`, 2026-04-02, "Abonnement annuel - Le Chat Pro - Annual", 143,90 HT / 172,68 TTC). `.claude/skills/arcodange-bank-reco/known-patterns.json` currently documents the MISTRAL.AI card debit as "Récurrent mensuel" — it is **annual** (next expected ~2027-04). This mis-set expectation cost investigation time ("where are the May/June Mistral debits?" — there are none). While in there: - Anthropic (CLAUDE.AI SUBSCRIPTION) pattern: April was on the Qonto card, but the **May/June receipts (#2344-8391, #2997-4837 in books@) have no Qonto debit** — probably the personal card (fk_account=3, API-invisible). Document the pattern as "payment rail moved — personal-card lane, see #57". - Both AI subscriptions are now RECORDED supplier invoices (post-replay), so these patterns may graduate from "known bank-only gap" to "matched" — re-check what `bank match` reports after the prod replay and prune accordingly. **Acceptance:** `bank match --since 2026-01-01` after the prod replay shows no stale "intentional gap" annotations for entries that are now properly recorded. --- **Execution** — Blocked by: the **prod replay** of the 2026-07-11 pack (the re-check depends on it; the annual-vs-monthly text fix itself can land anytime) · Blocks: none · Human gates: none. **Start:** `claude --worktree known-patterns-fix` from the erp repo root; edit `.claude/skills/arcodange-bank-reco/known-patterns.json`, then (post-replay) run `bank match --since 2026-01-01`. **Done means:** corrected patterns + post-replay match output posted here → PR merged with `Closes #56`.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: arcodange-org/erp#56