* fix(tic): call /enrichment before /collect to avoid session-consume bug TIC support confirmed (2026-04-24) that reading session status via /poll or /collect after the BankID session reaches `complete` marks the session as "consumed" server-side, after which /api/v1/enrichment refuses the sessionId with `error: "Session not completed"` (returned as HTTP 200, not 400). Today's flow inside POST /api/extensions/ext/tic/bankid/complete called collectBankIdResult and then requestEnrichment — exactly the order that triggers the bug. Login still succeeded (collect itself returns OK), but enrichment failed 100% of the time, leaving extension_data.bankid_enrichment empty and /select-company's CompanyRoles picker blank. Reorder so /enrichment runs first, then /collect. Per TIC, the consume flag only blocks subsequent /enrichment calls — collect after enrichment is harmless. Refactor the existing fetchAndStoreEnrichment helper into fetchEnrichmentSafely (pure fetch, returns EnrichmentData | null) and storeEnrichment (pure DB upsert), so the data can be captured before the collect/user-creation logic and persisted afterward. Enrichment stays non-blocking: any /enrichment failure still logs a warning and lets login proceed, exactly as today. Adds a regression test asserting requestEnrichment is invoked before collectBankIdResult (via mock.invocationCallOrder) plus tests for both failure modes — enrichment throwing and TIC returning the production "Session not completed" body shape. Ref: TIC session 90f7da27-84b2-4f09-afc4-47239eef57c1. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(tic): drop redundant void _omit — _ prefix already silences lint Per PR review: @typescript-eslint/no-unused-vars ignores `_`-prefixed identifiers by default, so the void expression is dead weight. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
gnubok
Open-source Swedish accounting software for sole traders (enskild firma) and limited companies (aktiebolag).
What is gnubok?
gnubok implements double-entry bookkeeping compliant with Swedish accounting law (Bokforingslagen). It supports the BAS 2026 chart of accounts, handles VAT declarations (momsdeklaration), SIE import/export, and enforces 7-year document retention. Built for sole traders and limited companies operating in Sweden.
Features
- Double-entry bookkeeping -- BAS 2026 chart of accounts, draft/commit workflow, sequential voucher numbering
- Invoicing -- Create, send, and track invoices with mixed VAT rates and PDF generation
- Bank reconciliation -- PSD2 bank connection via Enable Banking, 4-pass automatic matching
- VAT declaration -- SKV 4700 form mapping, per-rate breakdown, EU/export handling
- Tax reports -- NE-bilaga, INK2, SRU export for Skatteverket
- Supplier invoices -- Registration, payment tracking, input VAT deduction
- Document archive -- SHA-256 integrity, 7-year retention enforcement, full archive ZIP export
- SIE import/export -- Standard Swedish accounting interchange format
- Extension system -- Opt-in plugins for AI categorization, receipt OCR, email, calendar, and more
Self-Hosting
git clone https://github.com/erp-mafia/gnubok.git
cd gnubok
./setup.sh # Prompts for Supabase credentials, generates .env
docker compose up -d
You need a Supabase project and must apply the database migrations before first use. See SELF-HOSTING.md for the full step-by-step guide, including Supabase setup, auth configuration, optional features (AI, email, push notifications), and troubleshooting.
Development Setup
Prerequisites: Node.js 20+, a Supabase project.
npm install
npm run dev # Start dev server (auto-generates extension registry)
npm test # Run tests
npm run build # Production build
npm run lint # ESLint
Tech Stack
- Framework: Next.js 16 (App Router), React 19, TypeScript (strict)
- Database: Supabase (PostgreSQL + Row Level Security + email/password auth + TOTP MFA)
- Styling: Tailwind CSS 4 + shadcn/ui
- Integrations: Enable Banking (PSD2), Anthropic SDK, LangChain, OpenAI, Resend, JSZip
Documentation
- SELF-HOSTING.md -- Full self-hosting guide (Docker, Supabase setup, migrations, optional features)
- CLAUDE.md -- Architecture, bookkeeping engine, database conventions, extension system
- CONTRIBUTING.md -- Development workflow, code style, pull request process
- SECURITY.md -- Vulnerability reporting policy
Contributing
Contributions are welcome. See CONTRIBUTING.md for the full guide.
All commits require a DCO sign-off (git commit -s).
License
AGPL-3.0-or-later with an extension exception: third-party extensions that interact solely through the documented Extension API may be licensed under any terms, including proprietary. See LICENSE for details and NOTICE for third-party attributions.