'use client' import { useState } from 'react' import { useCashAccounts } from '@/lib/reference-data/hooks' import { useTranslations, useLocale } from 'next-intl' import { Dialog, DialogContent, DialogHeader, DialogTitle } from '@/components/ui/dialog' import { Button } from '@/components/ui/button' import { useToast } from '@/components/ui/use-toast' import { AlertTriangle, Loader2 } from 'lucide-react' import { formatCurrency, formatDate } from '@/lib/utils' import { getErrorMessage, type ErrorLocale } from '@/lib/errors/get-error-message' import { resolveAccount } from '@/lib/cash-accounts/resolve-account' import type { BookedDuplicateCandidate } from '@/lib/transactions/booking-duplicate-detection' /** The bank transaction being booked, as much as the caller knows about it. * Enables the "Matcha mot verifikatet" action for ledger-only candidates. */ export interface DuplicateMatchTransaction { id: string cash_account_id?: string | null currency?: string | null } /** * Soft warning shown when the booking-time duplicate guard fires * (TRANSACTION_BOOK_POSSIBLE_DUPLICATE): another already-booked transaction * shares this one's date + amount + bank account. Never a hard block: * genuinely repeated same-day payments (e.g. several identical Swish transfers) * are legitimate, so the user can review the existing verifikat or book anyway. * * Shared by the /transactions list (runCategorize) and the manual booking * dialog (JournalEntryForm → /api/transactions/[id]/book). The caller owns the * retry: "Bokför ändå" must re-issue the request with force=true bound to * `candidate.journal_entry_id` via `expected_duplicate_journal_entry_id`: it * is present on both candidate kinds (a sibling-transaction candidate and a * ledger-only voucher candidate, which has no transaction_id), and the server * re-detects it so a stale id can't wave the guard away. * * Ledger-only candidates (candidate.transaction_id === null: the voucher exists * but no bank transaction is linked to it, e.g. a verifikat from an SIE import * or an invoice marked paid) get "Matcha mot verifikatet" as the PRIMARY action * when the caller supplies `matchTransaction` + `onMatched`: it links the bank * line to the existing voucher via /api/reconciliation/bank/link (the same path * MatchVoucherDialog uses) instead of double-booking the affärshändelse. * "Bokför ändå" stays available but demoted. * * Sibling-transaction candidates (candidate.transaction_id set: the verifikat * is already linked to ANOTHER bank transaction) get the match action too: * manualLink (lib/reconciliation/bank-reconciliation.ts) explicitly allows a * second transaction on one voucher (split settlements), so hiding the action * dead-ended the user in "Bokför ändå". Their body copy asks "vill du matcha i * stället?" and, because that shape is very often a duplicate IMPORT of one * real movement (where matching would double-count the bank side), they * additionally get "Ignorera transaktionen" via /api/transactions/[id]/ignore * when the caller supplies `onIgnored`. */ export default function DuplicateBookingDialog({ candidate, processing = false, onBookAnyway, onCancel, matchTransaction, onMatched, onIgnored, }: { /** The already-booked sibling, or null to keep the dialog closed. */ candidate: BookedDuplicateCandidate | null processing?: boolean onBookAnyway: () => void onCancel: () => void /** The transaction being booked; required for the match action. */ matchTransaction?: DuplicateMatchTransaction | null /** Called after /api/reconciliation/bank/link succeeds. Mirrors * MatchVoucherDialog's onLinked signature: everything the refresh needs is * passed in, so a mid-request dialog close can't strand the update. The * caller owns the success toast and state refresh (and closes the dialog by * clearing `candidate`). */ onMatched?: (transactionId: string, journalEntryId: string, voucherLabel: string) => void /** Called after POST /api/transactions/[id]/ignore succeeds for a * sibling-transaction candidate (the row is likely a duplicate import). * The caller owns the refresh and closes the dialog by clearing * `candidate`. Omit to hide the ignore action. */ onIgnored?: (transactionId: string) => void }) { const t = useTranslations('transactions') const locale = useLocale() as ErrorLocale const { toast } = useToast() const [matching, setMatching] = useState(false) const [ignoring, setIgnoring] = useState(false) // A sibling-transaction candidate: the twin bank row is already booked, so // the target is either a duplicate import (ignore), the second leg of an // N:1 settlement (match), or a genuinely separate identical event (book). const isSiblingCandidate = candidate !== null && candidate.transaction_id !== null // Matching links THIS bank line to the existing voucher instead of minting a // second verifikat (one affärshändelse, one verifikat). Offered for both // candidate kinds: for ledger-only vouchers it is the right default, and for // sibling candidates manualLink explicitly permits N:1 links. const canMatch = candidate !== null && !!matchTransaction && !!onMatched const canIgnore = isSiblingCandidate && !!matchTransaction && !!onIgnored // Session-cached (lib/reference-data); an empty list resolves to 1930 and // the link route re-validates the account either way. const { cashAccounts } = useCashAccounts() async function handleMatch() { if (!candidate || !matchTransaction || !onMatched || matching) return setMatching(true) try { // Link on the exact 19xx account the candidate voucher was booked to // when the guard reported it: a legacy transaction without a // cash_account_id would otherwise resolve by currency and can pick a // different 19xx than the voucher's leg, dead-ending the link. Fall back // to resolving from the company's cash accounts, same as // MatchVoucherDialog: the link route validates the voucher has a leg on // this account and that the transaction belongs to it. let account = candidate.account_number ?? '1930' if (!candidate.account_number) { account = resolveAccount( cashAccounts, matchTransaction.cash_account_id ?? null, matchTransaction.currency ?? 'SEK', ).account } const res = await fetch('/api/reconciliation/bank/link', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ transaction_id: matchTransaction.id, journal_entry_id: candidate.journal_entry_id, account_number: account, }), }) const result = await res.json() if (!res.ok || result.error) { toast({ title: t('dialog_duplicate_match_failed'), description: getErrorMessage(result, { context: 'transaction', statusCode: res.status, locale }), variant: 'destructive', }) return } onMatched(matchTransaction.id, candidate.journal_entry_id, candidate.voucher_label) } catch { toast({ title: t('dialog_duplicate_match_failed'), description: getErrorMessage(null, { context: 'transaction', locale }), variant: 'destructive', }) } finally { setMatching(false) } } async function handleIgnore() { if (!candidate || !matchTransaction || !onIgnored || ignoring) return setIgnoring(true) try { const res = await fetch(`/api/transactions/${matchTransaction.id}/ignore`, { method: 'POST', }) const result = await res.json().catch(() => null) if (!res.ok || result?.error) { toast({ title: t('dialog_duplicate_ignore_failed'), description: getErrorMessage(result, { context: 'transaction', statusCode: res.status, locale }), variant: 'destructive', }) return } onIgnored(matchTransaction.id) } catch { toast({ title: t('dialog_duplicate_ignore_failed'), description: getErrorMessage(null, { context: 'transaction', locale }), variant: 'destructive', }) } finally { setIgnoring(false) } } const busy = processing || matching || ignoring return ( { if (!open) onCancel() }} > {t('dialog_duplicate_title')}
{/* Sibling candidates get the "vill du matcha i stället?" copy: the generic body's "en annan transaktion eller en befintlig verifikation" hedge reads as noise once the twin is known. The ignore hint renders only when the action itself does (callers without onIgnored, e.g. the manual booking form and the bulk dialog, must not have copy pointing at a button that is not there). */}

{isSiblingCandidate ? t('dialog_duplicate_body_sibling') : t('dialog_duplicate_body')} {canIgnore && <> {t('dialog_duplicate_ignore_hint')}}

{candidate && (
{candidate.voucher_label ? t('dialog_duplicate_voucher_label', { label: candidate.voucher_label }) : t('dialog_duplicate_voucher_generic')} {/* candidate.amount is ALWAYS SEK or null, never a foreign number (booking-duplicate-detection.ts): the explicit 'SEK' states that contract at the call site. When the sibling is foreign and carries no stored rate, amount is null and the honest figure is the sibling's own amount in its own currency, explicitly labelled. */} {candidate.amount != null ? formatCurrency(candidate.amount, 'SEK') : candidate.currency && candidate.amount_in_currency != null ? formatCurrency(candidate.amount_in_currency, candidate.currency) : t('dialog_duplicate_amount_unknown')}
{/* Verified FX sibling: the kr figure above is the sibling's own booked SEK value; show the foreign original beneath it so the user can recognise their EUR/USD line at a glance. */} {candidate.amount != null && candidate.currency && candidate.amount_in_currency != null && (
{formatCurrency(candidate.amount_in_currency, candidate.currency)}
)}
{formatDate(candidate.entry_date)}
{candidate.description && (
{candidate.description}
)} {/* Rateless foreign sibling: the amounts matched exactly in the shared currency, but no SEK value exists for it, so say that instead of printing an authoritative-looking kr figure. Gated on candidate.currency: the sentence names the currency, and interpolating an empty string renders broken Swedish ("samma belopp i , men..."). A null-currency candidate with a null amount already shows dialog_duplicate_amount_unknown. */} {candidate.amount == null && candidate.currency && (

{t('dialog_duplicate_sek_unavailable', { currency: candidate.currency })}

)} {/* Ledger-only candidate found for a bank line that has no SEK value: the kr figure above is the voucher leg's real amount, but it could not be compared against the transaction, so the match rests on date + account + direction alone. */} {candidate.amount != null && !candidate.amount_verified && (

{t('dialog_duplicate_amount_unverified')}

)}
)}
{candidate && ( )}
{canMatch ? ( <> {/* Sibling candidates only: when the row is a duplicate import of the already-booked twin, ignoring it is the correct resolution (matching would double-count the bank side, booking would double-count the ledger side). */} {canIgnore && ( )} ) : ( )}
) }