db8983ba9e
* feat(arcim-migration): Briox provider with SIE-over-API import - Briox auth via account ID + application token (no app-level credentials); both tokens rotate on refresh and are persisted - New sie-fetcher pulls the general ledger as SIE through the provider API for Fortnox, Briox and Bjorn Lunden - Wizard stops on a failed SIE import and surfaces the real errors instead of proceeding to the misleading migrate-guard message - PROVIDER_SIE_ONLY_FORTNOX renamed to PROVIDER_SIE_NOT_SUPPORTED; new PROVIDER_TOKEN_INVALID for rejected provider credentials Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(bookkeeping): per-line accruals (periodisering) on invoices and supplier invoices Defer revenue/costs per invoice line to 29xx/17xx interim accounts with automatic monthly dissolution (nightly cron + catch-up at registration), schedule cancellation on credit, year-end auto-detect exclusion for already-scheduled invoices, invoice-inbox service-period extraction for prefill, and an MCP tool to list schedules. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(bokslut): iXBRL arsredovisning generation and Bolagsverket digital filing Generate the annual report as iXBRL from a generated taxonomy registry (K2 element lists, taxonomy:generate/check scripts + CI guard), expose it via the fiscal-period API, and add the bolagsverket extension for digital submission to eget utrymme with webhook-driven status tracking (submissions table + pg tests, lifecycle events, year-end wizard UI). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * test(mcp): raise origin-guard test timeout to 20s The dynamic import pulls in the full server module; the parse alone flirts with the 5s default under full-suite parallel load. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Add new scripts and documentation for K2 AB taxonomy generation and validation - Introduced `generate-taxonomy-registry.ts` to automate the generation of the iXBRL taxonomy concept registry from official element lists and tuple models. - Added `validate-ixbrl.mjs` for validating generated iXBRL reports against the official taxonomy package using Arelle. - Included new documentation files: - `k2-ab-arsredovisning-elementlista-2024-09-12_rev20250312_sv.xlsx` - `tuple-innehallsmodell-arsredovisning-k2-2024-09-12.xlsx` - `taxonomi-paket-2024-09-12_rev20250312.zip` * Add tests for bookkeeping accruals dissolution and supplier invoices - Implement tests for the POST /api/bookkeeping/accruals/[id]/dissolve route, covering success and error scenarios. - Add tests for the DELETE /api/supplier-invoices/[id] route, including authentication checks and validation of invoice deletion conditions. - Introduce tests for the Arcim migration provider client, ensuring token handling and error classification. - Create tests for the Bolagsverket extension, validating submission role enforcement and environment settings. - Add Zod schemas for Bolagsverket response payloads to ensure proper validation. - Implement tests for MCP server's list accrual schedules, confirming registration and scope mapping. - Add consistency tests for IXBRL document generation, ensuring duplicate facts and XML escaping are handled correctly. - Introduce typed domain errors for accrual schedules to improve error handling in the service. - Add tests for resolving consent with Briox token refresh concurrency, ensuring proper token management and error handling. * fix(tests): update payload size guard comments to reflect recent changes in tool descriptions and ceiling adjustments * fix(gitattributes): mark generated JSON files in bokslut taxonomy as linguist-generated * feat(migrations): add backfill for invoices.journal_entry_id and fallback for next_voucher_number user_id * feat(bokslut): enhance compliance and financial processing features with new submission details and security measures --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
102 lines
3.9 KiB
TypeScript
102 lines
3.9 KiB
TypeScript
import { describe, expect, it } from 'vitest'
|
|
import { getPool } from '@/tests/pg/setup'
|
|
import {
|
|
insertBalancedLines,
|
|
insertDraftJournalEntry,
|
|
seedCompany,
|
|
} from '@/tests/pg/fixtures'
|
|
|
|
describe('engine.pg — triggers & RPCs that mocks cannot catch', () => {
|
|
it('rejects INSERT into journal_entries when the fiscal period is closed', async () => {
|
|
const { userId, companyId, fiscalPeriodId } = await seedCompany({ isClosed: true })
|
|
|
|
await expect(
|
|
insertDraftJournalEntry({ userId, companyId, fiscalPeriodId }),
|
|
).rejects.toThrow(/locked\/closed fiscal period/i)
|
|
})
|
|
|
|
it('commit_journal_entry assigns sequential voucher numbers under concurrency', async () => {
|
|
const { userId, companyId, fiscalPeriodId } = await seedCompany()
|
|
|
|
const entryA = await insertDraftJournalEntry({ userId, companyId, fiscalPeriodId })
|
|
const entryB = await insertDraftJournalEntry({ userId, companyId, fiscalPeriodId })
|
|
await insertBalancedLines(entryA)
|
|
await insertBalancedLines(entryB)
|
|
|
|
// Two dedicated clients so the row-level lock on voucher_sequences is
|
|
// actually exercised — not just a single connection serialising calls.
|
|
const clientA = await getPool().connect()
|
|
const clientB = await getPool().connect()
|
|
try {
|
|
const [resA, resB] = await Promise.all([
|
|
clientA.query<{ voucher_number: number }>(
|
|
`SELECT voucher_number FROM public.commit_journal_entry($1::uuid, $2::uuid)`,
|
|
[companyId, entryA],
|
|
),
|
|
clientB.query<{ voucher_number: number }>(
|
|
`SELECT voucher_number FROM public.commit_journal_entry($1::uuid, $2::uuid)`,
|
|
[companyId, entryB],
|
|
),
|
|
])
|
|
const numbers = [resA.rows[0]!.voucher_number, resB.rows[0]!.voucher_number].sort(
|
|
(a, b) => a - b,
|
|
)
|
|
expect(numbers).toEqual([1, 2])
|
|
} finally {
|
|
clientA.release()
|
|
clientB.release()
|
|
}
|
|
})
|
|
|
|
it('rejects UPDATE to a posted journal entry (committed immutability)', async () => {
|
|
const { userId, companyId, fiscalPeriodId } = await seedCompany()
|
|
|
|
// Bypass commit_journal_entry by inserting directly as 'posted'. The
|
|
// immutability trigger fires on UPDATE, not INSERT, so this is legal
|
|
// setup on the superuser connection.
|
|
const entryId = await insertDraftJournalEntry({
|
|
userId,
|
|
companyId,
|
|
fiscalPeriodId,
|
|
status: 'posted',
|
|
voucherNumber: 1,
|
|
})
|
|
|
|
await expect(
|
|
getPool().query(
|
|
`UPDATE public.journal_entries SET description = 'tampered' WHERE id = $1`,
|
|
[entryId],
|
|
),
|
|
).rejects.toThrow(/Cannot modify a posted journal entry/i)
|
|
})
|
|
|
|
it('next_voucher_number falls back to the company owner when auth.uid() is NULL', async () => {
|
|
// The superuser pg connection has no Supabase JWT, so auth.uid() IS NULL —
|
|
// exactly the service-role shape (repair scripts, cron) that used to fail
|
|
// the voucher_sequences user_id NOT NULL check before ON CONFLICT could
|
|
// arbitrate (commit_journal_entry got the fallback in 20260421170500;
|
|
// next_voucher_number — the storno/correction path — did not until
|
|
// 20260623130000).
|
|
const { userId, companyId, fiscalPeriodId } = await seedCompany()
|
|
|
|
const first = await getPool().query<{ n: number }>(
|
|
`SELECT public.next_voucher_number($1::uuid, $2::uuid) AS n`,
|
|
[companyId, fiscalPeriodId],
|
|
)
|
|
const second = await getPool().query<{ n: number }>(
|
|
`SELECT public.next_voucher_number($1::uuid, $2::uuid) AS n`,
|
|
[companyId, fiscalPeriodId],
|
|
)
|
|
expect(first.rows[0]!.n).toBe(1)
|
|
expect(second.rows[0]!.n).toBe(2)
|
|
|
|
// Attribution on the sequence row falls back to companies.created_by.
|
|
const seq = await getPool().query<{ user_id: string }>(
|
|
`SELECT user_id FROM public.voucher_sequences
|
|
WHERE company_id = $1::uuid AND fiscal_period_id = $2::uuid AND voucher_series = 'A'`,
|
|
[companyId, fiscalPeriodId],
|
|
)
|
|
expect(seq.rows[0]!.user_id).toBe(userId)
|
|
})
|
|
})
|