Jakob Wennberg
27ae59040e
* fix(transactions): retire stale invoice match pointers when an invoice settles potential_invoice_id / potential_supplier_invoice_id are write-once import suggestions: nothing revisited them once written. With recurring same-amount invoices, an earlier suggestion pointed transaction A at invoice X, X was then paid off by transaction B, and A kept pointing at a fully paid invoice. The match dialog computed its amount diff against that invoice's 0 kr remaining_amount and reported a bogus partial payment, and the dead pointer also blocked a fresh suggestion: both re-suggestion scans require the column to be NULL. Add one shared helper, clearSettledInvoiceSuggestions(), that nulls a settled invoice's own suggestion column on every other transaction of the same company, scoped by company_id and by that invoice id only, never widening to the confirmed invoice_id / supplier_invoice_id links. It is best effort by construction: every caller has already booked a payment verifikat, so a failed cleanup logs and returns instead of failing the settle. Wired into every path where an invoice reaches paid through a payment: the dashboard and v1 match-invoice / match-supplier-invoice routes, the dashboard and v1 mark-paid routes, settleInvoicePayment, the batch allocation route (per fully settled allocation), linkInvoiceToVoucher and linkSupplierInvoiceToVoucher, linkTransactionToJournalEntry, and the MCP staged-operation executors for mark_invoice_paid and match_transaction_invoice. Partial payments are deliberately left alone: a partially paid invoice is still matchable. The v1 supplier match route also clears its own row's hint, which it was missing next to its dashboard twin. Read-time revalidation stays as the backstop for the paths not wired up here. countSuggestedMatches now delegates to listSuggestedMatches, which already revalidates candidates, so the worklist badge can no longer claim a number the list refuses to render. A data-only backfill migration retires the pointers already stranded in the database. It touches no journal entry, verifikat or period-locked data, is idempotent, and its status lists mirror lib/invoices/matchable-statuses.ts. Fixes #1259 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * fix(transactions): wire the MCP batch allocation into the settled-pointer cleanup Review follow-up on the #1259 fix. commitMatchBatchAllocate calls the same match_batch_allocate RPC as the dashboard route, and gnubok_match_batch_allocate is a live staged MCP tool, so an agent settling a samlingsbetalning reproduced the issue exactly: the RPC nulls potential_invoice_id / potential_supplier_invoice_id only on the source transaction, leaving every other transaction of the company pointing at an invoice the batch just closed. The per-allocation loop moves into clearSettledBatchAllocationSuggestions() so the HTTP route and the MCP executor run the same code and cannot drift again, with a commit-path test pinning that only the fully settled allocation is retired. The enlarged badge scan is made safe. countSuggestedMatches now feeds up to 200 ids into listSuggestedMatches, past the 150 per .in() that countInboxDocuments already chunks for, so the candidate lookups are chunked at IN_CLAUSE_CHUNK too and their ids deduped. Both lookups now check .error: previously a 414, a 500 or an RLS change produced empty maps, an empty list and a zero badge with nothing logged. Every failure branch here logs companyId, matching the logAndZero convention. Also: restore the anchorSupplierInvoiceDocument doc comment above its own call in the dashboard supplier-invoice mark-paid route (the #1259 block had been inserted between them), and assert the transaction update payload in the v1 match-supplier-invoice test, which now covers the potential_supplier_invoice_id null that the route was missing next to its dashboard twin. Fixes #1259 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
39 lines
1.7 KiB
SQL
39 lines
1.7 KiB
SQL
-- Issue #1259: retire suggestion pointers left behind when the invoice was
|
|
-- settled by a different transaction.
|
|
--
|
|
-- potential_invoice_id / potential_supplier_invoice_id are write-once import
|
|
-- suggestions. Until now nothing revisited them, so a recurring invoice paid
|
|
-- off by transaction B left every other transaction pointing at a fully paid
|
|
-- invoice. The read paths already refuse to offer such a candidate, but the
|
|
-- non-NULL column blocks a FRESH suggestion (both re-suggestion scans require
|
|
-- it to be NULL), so the affected transactions can never be suggested again.
|
|
--
|
|
-- Data only, no DDL. The potential_* columns carry no accounting meaning: the
|
|
-- confirmed links live in invoice_id / supplier_invoice_id, which are
|
|
-- untouched here, as are all journal entries, verifikat and period locks.
|
|
-- Idempotent: re-running clears nothing extra.
|
|
--
|
|
-- The status lists below are byte-identical to
|
|
-- lib/invoices/matchable-statuses.ts (MATCHABLE_SUPPLIER_INVOICE_STATUSES /
|
|
-- MATCHABLE_INVOICE_STATUSES). Keep them in sync.
|
|
|
|
UPDATE public.transactions t
|
|
SET potential_supplier_invoice_id = NULL
|
|
WHERE t.potential_supplier_invoice_id IS NOT NULL
|
|
AND NOT EXISTS (
|
|
SELECT 1 FROM public.supplier_invoices si
|
|
WHERE si.id = t.potential_supplier_invoice_id
|
|
AND si.status IN ('registered', 'approved', 'overdue', 'partially_paid')
|
|
AND COALESCE(si.remaining_amount, 0) > 0
|
|
);
|
|
|
|
UPDATE public.transactions t
|
|
SET potential_invoice_id = NULL
|
|
WHERE t.potential_invoice_id IS NOT NULL
|
|
AND NOT EXISTS (
|
|
SELECT 1 FROM public.invoices i
|
|
WHERE i.id = t.potential_invoice_id
|
|
AND i.status IN ('sent', 'overdue', 'partially_paid')
|
|
AND COALESCE(i.remaining_amount, 0) > 0
|
|
);
|