Files
accounted/lib/providers/resolve-consent.ts
T
MattssonandClaude Fable 5 db8983ba9e Add/bokslut (#718)
* 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>
2026-06-12 16:35:30 +02:00

186 lines
6.7 KiB
TypeScript

import { createServiceClient } from '@/lib/supabase/server';
import type { TokenResponse } from './types';
import { getOAuthConfig } from './oauth-config';
import { refreshFortnoxToken } from './fortnox/oauth';
import { refreshVismaToken } from './visma/oauth';
import { refreshBrioxToken } from './briox/oauth';
import { refreshBjornLundenToken } from './bjornlunden/oauth';
import { createLogger } from '@/lib/logger';
const log = createLogger('providers/resolve-consent');
export interface ResolvedConsent {
consent: Record<string, unknown>;
accessToken: string;
providerCompanyId?: string;
}
export async function resolveConsent(companyId: string, consentId: string): Promise<ResolvedConsent> {
const supabase = createServiceClient();
// Load consent
const { data: consentRows } = await supabase
.from('provider_consents')
.select('*')
.eq('id', consentId)
.eq('company_id', companyId)
.limit(1);
if (!consentRows || consentRows.length === 0) {
throw { status: 404, message: 'Consent not found' };
}
const consent = consentRows[0]!;
// Accept status 0 (token submitted, migration pending) and 1 (fully accepted)
if (consent.status !== 0 && consent.status !== 1) {
throw { status: 403, message: 'Consent is not in a valid status' };
}
if (!consent.provider) {
throw { status: 400, message: 'Consent has no provider set — complete onboarding first' };
}
// Load tokens
const { data: tokenRows } = await supabase
.from('provider_consent_tokens')
.select('*')
.eq('consent_id', consentId)
.limit(1);
if (!tokenRows || tokenRows.length === 0) {
throw { status: 401, message: 'No tokens found for this consent — complete OAuth first' };
}
const tokens = tokenRows[0]!;
// Bokio: private API tokens that don't expire
if (consent.provider === 'bokio') {
return {
consent,
accessToken: tokens.access_token as string,
providerCompanyId: tokens.provider_company_id as string | undefined,
};
}
// Björn Lunden: client credentials — auto-refresh when expired
if (consent.provider === 'bjornlunden') {
if (tokens.token_expires_at && new Date(tokens.token_expires_at as string) < new Date()) {
const refreshed = await refreshBjornLundenToken();
const newExpiresAt = new Date(Date.now() + refreshed.expires_in * 1000).toISOString();
await supabase
.from('provider_consent_tokens')
.update({
access_token: refreshed.access_token,
token_expires_at: newExpiresAt,
})
.eq('consent_id', consentId);
return {
consent,
accessToken: refreshed.access_token,
providerCompanyId: tokens.provider_company_id as string | undefined,
};
}
return {
consent,
accessToken: tokens.access_token as string,
providerCompanyId: tokens.provider_company_id as string | undefined,
};
}
// Check expiry, auto-refresh if needed
if (tokens.token_expires_at && new Date(tokens.token_expires_at as string) < new Date()) {
if (!tokens.refresh_token) {
throw { status: 401, message: 'Access token expired and no refresh token available' };
}
let refreshed: TokenResponse;
if (consent.provider === 'fortnox') {
refreshed = await refreshFortnoxToken(getOAuthConfig('fortnox'), tokens.refresh_token as string);
} else if (consent.provider === 'briox') {
// Briox /tokenrefresh wants the (expired) access token alongside the
// refresh token; no app-level config involved. Both tokens rotate —
// the new refresh_token is persisted below.
refreshed = await refreshBrioxToken(tokens.refresh_token as string, tokens.access_token as string);
} else {
refreshed = await refreshVismaToken(getOAuthConfig(consent.provider as string), tokens.refresh_token as string);
}
const newExpiresAt = new Date(Date.now() + refreshed.expires_in * 1000).toISOString();
// Optimistic concurrency guard: providers like Briox and Fortnox rotate
// BOTH tokens on refresh, so two concurrent requests refreshing the same
// expired pair must not both persist — the second write would overwrite
// the pair the first request just stored with a possibly-dead one. Key
// the UPDATE on the token_expires_at we read above: if another request
// already rotated, zero rows match and we adopt the stored fresh tokens.
const { data: updatedRows, error: updateError } = await supabase
.from('provider_consent_tokens')
.update({
access_token: refreshed.access_token,
refresh_token: refreshed.refresh_token,
token_expires_at: newExpiresAt,
})
.eq('consent_id', consentId)
.eq('token_expires_at', tokens.token_expires_at as string)
.select('id');
if (updateError) {
// The provider has ALREADY rotated the tokens but we failed to persist
// the new pair — the stored pair is now dead and every later call on
// this consent will fail. Log loudly; the only recovery is to
// disconnect and re-enter the provider credentials.
log.error(
`Failed to persist rotated ${consent.provider} tokens for consent ${consentId} — ` +
'the stored credentials are now invalid and the consent will break',
{ reason: updateError.message },
);
throw {
status: 500,
message:
'Token refresh succeeded at the provider but the rotated tokens could not be saved. ' +
'The stored credentials are no longer valid — disconnect the provider and re-enter the credentials.',
};
}
if (!updatedRows || updatedRows.length === 0) {
// Lost the refresh race: a concurrent request already rotated and
// persisted a fresh pair. Use those tokens as-is — calling the provider
// refresh endpoint again here would invalidate the winner's pair.
const { data: freshRows } = await supabase
.from('provider_consent_tokens')
.select('*')
.eq('consent_id', consentId)
.limit(1);
const fresh = freshRows?.[0];
if (fresh?.access_token) {
return {
consent,
accessToken: fresh.access_token as string,
providerCompanyId: (fresh.provider_company_id ?? tokens.provider_company_id) as
| string
| undefined,
};
}
// Token row vanished mid-flight (disconnect?) — fall through to our own
// refreshed pair, which the provider still considers the latest one.
}
return {
consent,
accessToken: refreshed.access_token,
providerCompanyId: tokens.provider_company_id as string | undefined,
};
}
return {
consent,
accessToken: tokens.access_token as string,
providerCompanyId: tokens.provider_company_id as string | undefined,
};
}