* feat(salary): one-click AGI submission with filing state machine and success feedback The AGI panel required users to know that "Ladda ner AGI-fil" was the generate step, then click submit, signing link, and kvittens manually. A nollkorning filing stalled on "AGI-XML saknas" pointing at a UI path that does not exist. - New primary button "Lamna in till Skatteverket" chains the existing endpoints client-side: generate XML if missing, POST underlag, poll kontrollresultat, create signing link, open Mina Sidor in a tab opened synchronously at click (popup-blocker safe). Inline stepper shows each step; the four old buttons become collapsed advanced/recovery actions, auto-expanded in stale-draft and rejected states. XML download stays visible and free for manual filing. - deriveAgiFilingState() + useAgiSubmission() lift the per-period submission record to the run page: the progress rail and salary hero now render the real state machine (generated, underlag inskickat, vantar pa BankID-signatur, inlamnad med kvittensnummer) instead of telling users to "lamna in" an already-submitted declaration. - Success card with kvittensnummer and signature metadata once signed, plus a toast when a poll flips the state while the page is open. - AGI kvittens cron every 15 min instead of every 2 h so filings signed on another device get stamped and emailed promptly. - Advanced submit also auto-generates, and the stale "Lon -> AGI -> Generera" error text now points at the real buttons. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(enable-banking): instant OAuth callback feedback and dead-attempt cleanup The bank redirect landed on a blank page for the several seconds the callback spent exchanging the PSD2 session and mirroring accounts, and every failed connect attempt left a status='error' row that rendered forever as an "Atgard kravs" card next to a successful retry, showing duplicate connections to the same bank. - Stream a branded "Slutfor bankanslutningen" progress page from the callback: the shell flushes before the session exchange starts and a script/meta redirect follows when the work completes, with a 30s slow-work escape hatch. Fast outcomes (denial, bad params, unknown state) keep their plain redirects. - Delete never-activated connection rows (no session_id, no accounts_data) on denial or exchange failure, and sweep leftovers for the same bank on the next connect. Established connections keep their "Atgard krävs" card via the accounts_data guard; FKs are ON DELETE SET NULL so deletion has no dependents. - Show "Banken ar ansluten: hamtar dina konton" while the settings panel loads after the callback instead of an anonymous spinner. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(invoices): reject re-send of issued invoices and gate bookkeeping on the sent flip A direct POST to /api/invoices/[id]/send against an already-issued invoice re-emailed the customer and posted a second revenue verifikat (createInvoiceJournalEntry has no dedup), overwriting journal_entry_id and orphaning the first entry. Only the UI hid the button; the v1 route and the MCP commit executor already rejected non-drafts. - Non-draft invoices now return 409 INVOICE_ALREADY_SENT. - The draft to sent status flip is an optimistic lock (status guard plus row-count check); journal entry, accrual schedules, PDF archival and the invoice.sent event only run for the request that won the flip. - On a flip failure the journal entry is deferred: the row stays draft and a retry re-runs the pipeline, ending with exactly one verifikat. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(invoices): payment links, failure visibility and sandbox guard for recurring auto-send - sendInvoiceFromSchedule now auto-creates an online payment link via applyPaymentLinkToInvoice before rendering and passes the payment link QR to the PDF: parity with the dashboard and v1 send routes, which recurring invoices silently lacked. - The recurring cron persists last_run_warning both when a claimed run throws (hourly retries stay visible on the schedule) and when a stale schedule is rolled forward, so a deterministic failure can no longer skip a month silently. - Auto-send is blocked for sandbox companies at the email chokepoint (freeze-and-retain: the invoice is still generated as a draft), covering both the cron and the run-now route with one guard. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(salary): close the Fortnox payroll API gaps (phases 1-4) Payroll now runs end-to-end through the open API, including onboarding a client from another payroll system, with every write staged for approval. - v1: per-employee payslips (list/detail/PDF), payslip line writes, run roster attach/remove, absence ranges (per-day storage), jamkning fields, cutover opening balances (single + atomic bulk PUT), vacation balance + vacation-year-close. PUT added to the wrapper's idempotency/ test-key set (test keys could otherwise write through PUT). - MCP: 10 new tools (get_employee/get_payslip/list_absence/ get_vacation_balance reads + staged update_payslip_line, register_absence, create_employee, update_employee, set_employee_opening_balances, close_vacation_year), executors, risk tiers, op-type CHECK expansions. create_employee encrypts personnummer at staging: pending_operations never holds plaintext. - Scope-map audit retrofit: 11 formerly unmapped tools now scoped; BREAKING for keys that relied on the 4 default-allow writes. - Cutover: employee_opening_balances (derived lock trigger, self-unlocks on run correction), engine YTD/karens/liability integration, Ingaende saldon section in the employee editor. - Arbetsschema-lite: employees.hours_per_week/workdays_per_week drive the hourly/daily divisors; legacy 173/21 preserved exactly at defaults so existing pay math is byte-identical. - Vacation ledger + semesterberedning/arsavslut: recomputed per-year day balances (synced on book/correct, non-fatal), year-close with the min-20 floor, 5-year sparade-dagar expiry to forced payout, and a 2920/2940 drift adjustment via the bookkeeping engine; Semester dashboard card with preview-then-confirm dialog. - Fix: Zod 4 defaults leak through .partial(), which made every sparse employee PATCH fail validation and reset defaulted columns. Migrations 20260713100000/101000/110000/121000/122000 (applied to staging with version rows; prod via merge). vacation_ledger renamed from 20260713120000 to avoid colliding with vat_declaration_totals_rpc. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * perf: cut dashboard page-load latency (region, round trips, caching, VAT RPC) The dominant cost was infrastructure: Vercel functions ran in iad1 (Washington D.C.) while Supabase (DB + auth) lives in eu-north-1 (Stockholm), so every request paid 4-5 transatlantic round trips of auth + company resolution before doing any real work (measured 530-1900ms for single-query GETs in prod logs). Pin functions to arn1 and cut the redundant work on top: - vercel.json: functions to arn1, same city as the database - getActiveCompanyId: preference + first-membership queries run in parallel; the fallback result doubles as validation in the common single-company case (one round trip instead of two sequential) - withRouteContext: Server-Timing header and authMs/companyMs/handlerMs in the op-completed log, so latency is attributable per phase - dashboard layout: nav badge counts off the critical path; DashboardNav loads them client-side via the new use-worklist-badges SWR hook with debounced realtime revalidation - swr (new dependency, approved): global provider; useCompanySettings shares one cache entry across consumers and renders from cache on back-navigation instead of re-showing skeletons - /pending: realtime refetch debounced; bulk operations previously fired 4 requests per row-change event - VAT declaration: new get_vat_declaration_totals RPC returns per-account totals, settlement-shape detection (#984) and source_type counts in ONE round trip instead of paging every entry+line through PostgREST. Account lists stay TS-side parameters so ACCOUNT_RUTA remains the single source of truth. Shape-exclusion coverage moved to tests/pg/vat-declaration-totals-rpc.pg.test.ts; DDL already applied to staging. - bundle: CommandPalette lazy-mounts on first Ctrl/Cmd+K, AgentChat dynamic-imports the markdown parser, @vercel/speed-insights (new dependency, approved) added for real-user timings The /salary fetch-waterfall fix from the same effort already landed inside 2084a756. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(invoices): settle öre-rounded payments from the mark-paid flow An invoice with öresavrundning shows a rounded "Att betala" on the PDF; the customer pays that amount (up to 50 öre off the stored öre total) and the invoice-page mark-paid flow rejected it with MATCH_AMOUNT_EXCEEDS_REMAINING: a dead end, while the bank-transaction match flow already absorbed the residual to 3740. - PaymentBookingDialog now proposes the rounded bank leg plus the 3740 residual line (credit when rounded up, debit when rounded down), resolved via getDisplayTotal from the per-invoice override and company_settings.ore_rounding. - settleInvoicePayment and the v1 mark-paid route absorb the sub-krona residual, gated by planInvoicePaymentForLines: absorption applies ONLY when the caller lines carry the exact residual on 3740; otherwise the strict plan applies (sub-krona partials stay partial, no-3740 overshoots keep the 400), so the GL can never diverge from the AR sub-ledger. - planInvoicePayment absorb-band boundary tightened to >= 1 kr: an exactly-1-kr overshoot used to slip past both the guard and the absorb branch and silently over-record paid_amount (pre-existing on the bank-match path). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(security): resolve all 7 PR compliance findings - ASVS V3.3: per-request CSP nonce on the enable-banking finalize page (mirrors the mcp-oauth consent page); inline scripts are nonce-bound - ASVS V16: decouple callback finalize work from the response stream (eager promise + next/server after()) so a client disconnect cannot drop session persistence or the consent_granted audit emit - ISO 27001 A.8.15: failed audit-event emits log through the structured logger with a stable message for log-based alerting - ASVS V2.3: recurring-invoice cron and run-now routes resolve isSandboxCompany themselves and pass an explicit suppressAutoSend flag (defence in depth around the email chokepoint, freeze-and-retain kept) - ISO 27001 A.8.11: stagePendingOperation rejects plaintext personnummer-bearing keys in params/preview_data (key-based guard; EF org numbers make value-matching unsafe) - ASVS V4.5: employee PATCH body is truly sparse; cleared number fields are omitted instead of resetting DB values to hardcoded fallbacks - ASVS V8.2.1: route-level tests pin the v1 cross-company deny (404 by convention, not 403) on the payslip PDF endpoint Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat: implement vacation-year basis change validation and error handling - Added tests to block vacation-year basis changes when open balances exist. - Implemented error handling for open-balances guard query failures in the settings route. - Enhanced absence route to reject reversed date ranges with a validation error. - Updated absence handling to use atomic upserts instead of delete+insert for better performance and reliability. - Refactored salary calculation logic to correctly handle age-based avgifter rates according to Skatteverket's rules. - Improved error messaging for vacation year closure adjustments. - Adjusted employee opening balances handling to preserve audit information during upserts. * feat(settings): add validation to block vacation-year basis change with open balances feat(absence): reject reversed date ranges in absence queries fix(absence): update absence handling to use atomic upserts instead of delete+insert fix(employee): improve validation for jamkning dates in employee updates fix(opening-balances): ensure created_by field is preserved during upserts test(absence): enhance tests for absence range and date validations test(calculation): add tests for age-based avgifter rates and edge cases test(semesterberedning): validate vacation year closure adjustments and error handling test(employee-opening-balances): update tests to reflect changes in salary_run_employees schema * fix(migrations): implement NOT VALID constraints for pending_operations and add validation migration --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
312 lines
11 KiB
TypeScript
312 lines
11 KiB
TypeScript
import type { SupabaseClient } from '@supabase/supabase-js'
|
|
import {
|
|
createInvoicePaymentJournalEntry,
|
|
createInvoiceCashEntry,
|
|
} from '@/lib/bookkeeping/invoice-entries'
|
|
import { createJournalEntry, findFiscalPeriod } from '@/lib/bookkeeping/engine'
|
|
import { resolveInvoicePaymentSourceType } from '@/lib/bookkeeping/propose-payment-lines'
|
|
import { isBookkeepingError } from '@/lib/bookkeeping/errors'
|
|
import { cancelOrphanedPaymentEntry } from '@/lib/bookkeeping/cancel-orphaned-entry'
|
|
import { planInvoicePaymentForLines } from '@/lib/invoices/apply-invoice-payment'
|
|
import { eventBus } from '@/lib/events'
|
|
import type { CreateJournalEntryInput, Customer, EntityType, Invoice } from '@/types'
|
|
|
|
/**
|
|
* The core "apply a payment to an invoice" operation, extracted from the
|
|
* mark-paid route so the Stripe payment sync (and any future automated payment
|
|
* channel) shares the exact same booking, status transition, orphan handling
|
|
* and event emission as the manual flow:
|
|
*
|
|
* 1. planInvoicePayment: ledger math + overpayment guard
|
|
* 2. journal entry: custom lines | cash entry (kontantmetoden, unbooked) |
|
|
* payment entry (clears 1510), fail-closed for real invoices
|
|
* 3. CAS-guarded invoice status update; a lost race or failed update cancels
|
|
* the just-posted voucher so GL and sub-ledger never diverge
|
|
* 4. invoice.paid event (best-effort)
|
|
*
|
|
* `settlementAccountNumber` routes the debit side: default 1930 (bank), 1686
|
|
* for PSP-balance settlements (Stripe) where the money reaches the bank only
|
|
* with the later payout.
|
|
*
|
|
* The function performs the write path only. Caller-owned concerns stay in
|
|
* the callers: fetching the invoice, payable-status guards, request parsing,
|
|
* the duplicate-payment guard (a UX advisory: the Stripe sync skips it
|
|
* because the payment event IS the authoritative payment), and mapping the
|
|
* result to a transport-specific response.
|
|
*/
|
|
|
|
export interface SettleCustomLine {
|
|
account_number: string
|
|
debit_amount: number
|
|
credit_amount: number
|
|
line_description?: string
|
|
}
|
|
|
|
/**
|
|
* Invoice shape at the settlement boundary. Callers typically join only the
|
|
* customer's name (`customer:customers(name)`), so the relation is modelled
|
|
* as exactly that: reading any other Customer field here would be undefined
|
|
* at runtime. A fully joined Customer still satisfies this structurally.
|
|
*/
|
|
export type InvoiceWithCustomerName = Omit<Invoice, 'customer'> & {
|
|
customer?: Pick<Customer, 'name'> | null
|
|
}
|
|
|
|
export interface SettleInvoicePaymentParams {
|
|
invoice: InvoiceWithCustomerName
|
|
/** Payment amount in the INVOICE currency (caller converts if needed). */
|
|
paymentAmountInInvoiceCurrency: number
|
|
/** Booking date (YYYY-MM-DD). */
|
|
paymentDate: string
|
|
accountingMethod: string
|
|
entityType: EntityType
|
|
/** FX difference in SEK (manual flow only). */
|
|
exchangeRateDifference?: number
|
|
/** Caller-supplied booking lines (manual dialog only); must balance. */
|
|
customLines?: SettleCustomLine[]
|
|
/** Debit-side account; default '1930'. Stripe settlements pass '1686'. */
|
|
settlementAccountNumber?: string
|
|
}
|
|
|
|
export type SettleInvoicePaymentResult =
|
|
| {
|
|
ok: true
|
|
newStatus: 'paid' | 'partially_paid'
|
|
newPaidAmount: number
|
|
newRemaining: number
|
|
journalEntryId: string | null
|
|
paidAt: string | null
|
|
}
|
|
| { ok: false; code: 'MATCH_AMOUNT_EXCEEDS_REMAINING'; details: Record<string, unknown> }
|
|
| { ok: false; code: 'INVOICE_PAID_LINES_UNBALANCED'; details: Record<string, unknown> }
|
|
| { ok: false; code: 'INVOICE_PAID_NO_FISCAL_PERIOD'; details: Record<string, unknown> }
|
|
| { ok: false; code: 'INVOICE_PAID_BOOK_FAILED'; details: Record<string, unknown> }
|
|
| { ok: false; code: 'INVOICE_PAID_RACE' }
|
|
| { ok: false; code: 'BOOKKEEPING_ERROR'; error: unknown }
|
|
| { ok: false; code: 'UPDATE_FAILED'; error: unknown }
|
|
|
|
export async function settleInvoicePayment(
|
|
supabase: SupabaseClient,
|
|
companyId: string,
|
|
userId: string,
|
|
params: SettleInvoicePaymentParams,
|
|
): Promise<SettleInvoicePaymentResult> {
|
|
const {
|
|
invoice,
|
|
paymentAmountInInvoiceCurrency,
|
|
paymentDate,
|
|
accountingMethod,
|
|
entityType,
|
|
exchangeRateDifference,
|
|
customLines,
|
|
settlementAccountNumber,
|
|
} = params
|
|
|
|
const now = new Date().toISOString()
|
|
|
|
// Drive the JE shape from the invoice's actual booking state, not from
|
|
// the current accounting_method setting. If the invoice was booked at
|
|
// send (Dr 1510 / Cr 30xx + VAT), the payment MUST clear 1510:
|
|
// otherwise the receivable orphans and 30xx + VAT double-count. Only
|
|
// when there is no prior JE (pure kontantmetoden) do we recognise
|
|
// revenue + VAT here.
|
|
const invoiceAlreadyBooked = !!(invoice as { journal_entry_id?: string | null })
|
|
.journal_entry_id
|
|
const useCashEntry = !invoiceAlreadyBooked && accountingMethod === 'cash'
|
|
|
|
// Ledger math + overpayment guard. Runs BEFORE any journal entry is
|
|
// created so a doomed overpayment never burns a voucher number.
|
|
// Custom-line SEK settlements absorb a sub-krona öresavrundning residual
|
|
// (customer paid the rounded "Att betala" from the PDF, up to 1 kr off the
|
|
// stored öre total) ONLY when the lines actually carry the residual on
|
|
// 3740, mirroring the bank-transaction match flow; lines that don't (e.g.
|
|
// a deliberate sub-krona partial) get the strict plan instead. The
|
|
// generated-entry paths (Stripe sync, no-body mark-paid) always pay the
|
|
// exact remaining, so absorption is a no-op there.
|
|
const payment = planInvoicePaymentForLines(
|
|
invoice,
|
|
paymentAmountInInvoiceCurrency,
|
|
customLines,
|
|
invoice.currency,
|
|
)
|
|
if (!payment.ok) {
|
|
return {
|
|
ok: false,
|
|
code: 'MATCH_AMOUNT_EXCEEDS_REMAINING',
|
|
details: payment.details as Record<string, unknown>,
|
|
}
|
|
}
|
|
const { newPaidAmount, newRemaining, newStatus } = payment.plan
|
|
|
|
const isRealInvoice = !invoice.document_type || invoice.document_type === 'invoice'
|
|
let journalEntryId: string | null = null
|
|
|
|
if (isRealInvoice) {
|
|
try {
|
|
if (customLines) {
|
|
const totalDebit = customLines.reduce((s, l) => s + l.debit_amount, 0)
|
|
const totalCredit = customLines.reduce((s, l) => s + l.credit_amount, 0)
|
|
if (Math.round((totalDebit - totalCredit) * 100) !== 0 || totalDebit <= 0) {
|
|
return {
|
|
ok: false,
|
|
code: 'INVOICE_PAID_LINES_UNBALANCED',
|
|
details: { totalDebit, totalCredit },
|
|
}
|
|
}
|
|
|
|
const fiscalPeriodId = await findFiscalPeriod(supabase, companyId, paymentDate)
|
|
if (!fiscalPeriodId) {
|
|
return {
|
|
ok: false,
|
|
code: 'INVOICE_PAID_NO_FISCAL_PERIOD',
|
|
details: { paymentDate },
|
|
}
|
|
}
|
|
const sourceType = resolveInvoicePaymentSourceType({
|
|
invoiceAlreadyBooked,
|
|
// Settings store a raw string; anything but 'cash' books as accrual,
|
|
// matching the useCashEntry check above.
|
|
accountingMethod: accountingMethod === 'cash' ? 'cash' : 'accrual',
|
|
})
|
|
const input: CreateJournalEntryInput = {
|
|
fiscal_period_id: fiscalPeriodId,
|
|
entry_date: paymentDate,
|
|
description: invoice.customer?.name
|
|
? `Inbetalning kundfaktura ${invoice.invoice_number}, ${invoice.customer.name}`
|
|
: `Inbetalning kundfaktura ${invoice.invoice_number}`,
|
|
source_type: sourceType,
|
|
source_id: invoice.id,
|
|
lines: customLines,
|
|
}
|
|
const journalEntry = await createJournalEntry(supabase, companyId, userId, input)
|
|
journalEntryId = journalEntry?.id ?? null
|
|
} else if (useCashEntry) {
|
|
// The entry helpers never read invoice.customer (the display name is
|
|
// passed explicitly), so the partial customer relation is safe here.
|
|
const journalEntry = await createInvoiceCashEntry(
|
|
supabase,
|
|
companyId,
|
|
userId,
|
|
invoice as Invoice,
|
|
paymentDate,
|
|
entityType,
|
|
invoice.customer?.name ?? undefined,
|
|
settlementAccountNumber,
|
|
)
|
|
journalEntryId = journalEntry?.id ?? null
|
|
} else {
|
|
const journalEntry = await createInvoicePaymentJournalEntry(
|
|
supabase,
|
|
companyId,
|
|
userId,
|
|
invoice as Invoice,
|
|
paymentDate,
|
|
exchangeRateDifference,
|
|
invoice.customer?.name ?? undefined,
|
|
undefined,
|
|
settlementAccountNumber,
|
|
)
|
|
journalEntryId = journalEntry?.id ?? null
|
|
}
|
|
} catch (err) {
|
|
if (isBookkeepingError(err)) {
|
|
return { ok: false, code: 'BOOKKEEPING_ERROR', error: err }
|
|
}
|
|
return {
|
|
ok: false,
|
|
code: 'INVOICE_PAID_BOOK_FAILED',
|
|
details: { reason: err instanceof Error ? err.message : 'unknown' },
|
|
}
|
|
}
|
|
|
|
// Fail closed: a real invoice must produce a payment voucher. If a helper
|
|
// returned null without throwing (e.g. a closed/locked fiscal period),
|
|
// refuse to mark the invoice paid: flipping status with no journal entry
|
|
// orphans the receivable and diverges the GL from the sub-ledger.
|
|
if (!journalEntryId) {
|
|
return {
|
|
ok: false,
|
|
code: 'INVOICE_PAID_BOOK_FAILED',
|
|
details: { reason: 'no_journal_entry_created' },
|
|
}
|
|
}
|
|
}
|
|
|
|
// CAS guard: only update if status is still in a payable state.
|
|
const { data: updateResult, error: updateError } = await supabase
|
|
.from('invoices')
|
|
.update({
|
|
status: newStatus,
|
|
paid_amount: newPaidAmount,
|
|
remaining_amount: newRemaining,
|
|
...(newStatus === 'paid' ? { paid_at: now } : {}),
|
|
})
|
|
.eq('id', invoice.id)
|
|
.eq('company_id', companyId)
|
|
.in('status', ['sent', 'overdue', 'partially_paid'])
|
|
.select('id')
|
|
|
|
if (updateError) {
|
|
// The payment voucher already posted but the invoice row did not flip to
|
|
// paid; cancel the orphan so the GL doesn't diverge from the sub-ledger.
|
|
if (journalEntryId) {
|
|
await cancelOrphanedPaymentEntry(
|
|
supabase,
|
|
companyId,
|
|
userId,
|
|
journalEntryId,
|
|
'Automatiskt makulerad: fakturauppdatering misslyckades efter bokförd betalning',
|
|
)
|
|
}
|
|
return { ok: false, code: 'UPDATE_FAILED', error: updateError }
|
|
}
|
|
|
|
if (!updateResult || updateResult.length === 0) {
|
|
// Status changed between read and write (concurrent settle): cancel the
|
|
// orphaned payment voucher; the trigger documents the voucher gap.
|
|
if (journalEntryId) {
|
|
await cancelOrphanedPaymentEntry(
|
|
supabase,
|
|
companyId,
|
|
userId,
|
|
journalEntryId,
|
|
'Automatiskt makulerad: dubblettbokning förhindrad av samtidighetsskydd',
|
|
)
|
|
}
|
|
return { ok: false, code: 'INVOICE_PAID_RACE' }
|
|
}
|
|
|
|
// Notify subscribers: invoice.paid fans out to registered webhooks and the
|
|
// Stripe extension's link-deactivation handler. Best-effort: the payment is
|
|
// already committed, so an emit failure must not fail the operation.
|
|
try {
|
|
await eventBus.emit({
|
|
type: 'invoice.paid',
|
|
payload: {
|
|
invoice: {
|
|
...invoice,
|
|
status: newStatus,
|
|
paid_amount: newPaidAmount,
|
|
remaining_amount: newRemaining,
|
|
paid_at: newStatus === 'paid' ? now : invoice.paid_at,
|
|
} as Invoice,
|
|
companyId,
|
|
userId,
|
|
paymentAmount: paymentAmountInInvoiceCurrency,
|
|
paymentDate,
|
|
},
|
|
})
|
|
} catch {
|
|
// Swallowed by design; the DB state is the source of truth.
|
|
}
|
|
|
|
return {
|
|
ok: true,
|
|
newStatus,
|
|
newPaidAmount,
|
|
newRemaining,
|
|
journalEntryId,
|
|
paidAt: newStatus === 'paid' ? now : null,
|
|
}
|
|
}
|