Jakob WennbergandClaude Opus 4.7
7cbd791c5b
* chore: translate TIC enrichment errors into actionable hints Adds self-diagnosing log output for known TIC failure shapes: - 'Session not completed' → tenant doesn't have enrichment enabled (the BankID consent-to-enrich dialog only fires when SPAR/CompanyRoles are configured on the tenant; without it, TIC rejects enrichment requests with this misleadingly-worded error) - 'not enabled' variants → explicit tenant disable - 'too old' → >30min between auth and enrichment request No behaviour change — purely diagnostic. Saves a future developer from re-discovering that "Session not completed" means "contact support@tic.io" rather than "retry the session." Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix: stop requesting disabled 'SPAR' enrichment type Root cause of the 'Session not completed' failures: TIC renamed 'SPAR' to 'Address' and our tenant has Address *disabled* (only CompanyRoles is on — verified via GET /api/v1/enrichment/types). Requesting an unknown or disabled type causes TIC to reject the whole enrichment with a misleading 'Session not completed' error rather than ignoring the unknown type or returning PartiallyCompleted. - Enrichment request now asks only for ['CompanyRoles'], which is what the /select-company picker actually needs. This is enough to stop the 'Session not completed' errors and make the picker work in prod. - If Address is enabled on TIC later, add it to the array (and wire up the address pre-fill paths in WelcomeOnboarding + createCompanyFromTicRole — both already look for a `.spar` field that TIC may have renamed). - Updated the diagnostic hint for 'Session not completed' to lead with the type-mismatch cause and point at the /enrichment/types curl for verification, since that's the first thing to check. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: clean up stale SPAR references in tic extension (PR review) Greptile P2 nits — all cosmetic, no runtime impact: - fetchAndStoreEnrichment JSDoc updated from "SPAR + CompanyRoles" to just CompanyRoles, with a note about where to add Address back if/when it's enabled on the tenant. - hasSpar log field removed from the 'enrichment data shape' snapshot. enrichmentData.spar was permanently undefined after the SPAR → nothing swap; logging a constantly-false field would have misled a future developer chasing missing address data. - Inline comment on the signup-path call to fetchAndStoreEnrichment now matches the login-path comment (CompanyRoles, not SPAR + CompanyRoles). 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.