Files
accounted/supabase/migrations/20260423140400_company_settings_ai_flow_toggle.sql
T
MattssonandClaude Opus 4.7 1af977950b Ai/full autonomous flow (#359)
* Refactor bookkeeping error handling and introduce new error classes

- Introduced new error classes for better error categorization:
  - JournalEntryNotBalancedError
  - FiscalPeriodNotFoundError
  - EntryDateOutsideFiscalPeriodError
  - JournalEntryNotFoundError
  - CannotReverseNonPostedError
  - CannotCorrectNonPostedError
  - EntryAlreadyReversedError
  - CurrencyRevaluationAlreadyExistsError
  - InvalidMappingResultError
  - BookkeepingDatabaseError

- Updated existing functions in engine.ts and transaction-entries.ts to throw specific errors instead of generic ones.
- Enhanced error response handling in get-error-message.ts to provide localized messages for new error types.
- Added unit tests for new error classes and error handling functions to ensure correctness and coverage.

* feat(ai): implement AI proposal application and persistence

- Add apply.ts to handle the application of AI proposals, including match and booking steps.
- Introduce persist.ts for inserting and managing AI requests and proposals, ensuring unique constraints.
- Create re-validate.ts for validating proposals before acceptance, checking for stale conditions.
- Define database migrations for ai_requests and ai_proposals tables, including constraints and indexes.
- Enhance journal_entries with AI provenance tracking, linking entries to AI proposals.
- Update categorization_templates to distinguish AI-corrected templates.
- Add company settings for toggling AI flow and managing backfill processes.
- Extend processing_history to include AI-related events for better tracking.

* feat: add uncategorized transactions API and UI for transaction selection

- Implemented a new API endpoint for fetching uncategorized transactions with pagination and filtering options.
- Created ChangeTransactionDialog component for selecting alternative transactions based on AI proposals.
- Developed ReceiptDetailDialog to display detailed information about receipts, including upload functionality.
- Added TransactionDetailDialog for viewing transaction details with links to the transaction list.
- Introduced receipt quality assessment logic to evaluate extracted receipt data.
- Implemented feature flagging for the AI bookkeeping agent to control availability in different environments.

* feat: add manual receipt extraction dialog and integrate AWS Textract for expense analysis

- Added ManualExtractDialog component for user input when AI fails to extract receipt data.
- Implemented ReceiptsList component to manage and display uploaded receipts, including upload and rescan functionalities.
- Introduced Textract integration for analyzing expenses, extracting fields like total, vendor, and date.
- Updated package.json to include @aws-sdk/client-textract dependency.

* fix(ai): handle livsmedel VAT transition (12% → 6%) in booking prompt and re-validate guard

Add date-aware guidance to BOOKING_SYSTEM_PROMPT for the temporary livsmedel
VAT cut (Prop. 2025/26:55, 2026-04-01 to 2027-12-31), with restaurang/servering
carve-out at 12%. Add a re-validate safety net that rejects clearly-stale rate
labels for grocery-chain merchants relative to the entry date.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 10:32:15 +02:00

42 lines
1.5 KiB
SQL

-- Per-company toggle for the AI agent flow.
--
-- `ai_flow_enabled` is the master switch. When true:
-- * newly-classified receipts generate AI proposals (via orchestrator);
-- * the auto-book path in lib/transactions/ingest.ts is disabled — every
-- uncategorized transaction becomes a review item instead of being
-- silently posted at >=0.8 mapping-rule confidence;
-- * the /agent-inbox page becomes available.
--
-- `ai_backfill_cancel_requested` is the kill switch for in-flight backfill
-- loops. The backfill endpoint kicks off a fire-and-forget iteration over
-- pending receipts; each iteration checks this flag between items so the
-- loop can be stopped without a separate job queue.
ALTER TABLE public.company_settings
ADD COLUMN IF NOT EXISTS ai_flow_enabled boolean NOT NULL DEFAULT false;
ALTER TABLE public.company_settings
ALTER COLUMN ai_flow_enabled SET DEFAULT false;
UPDATE public.company_settings
SET ai_flow_enabled = false
WHERE ai_flow_enabled IS NULL;
ALTER TABLE public.company_settings
ALTER COLUMN ai_flow_enabled SET NOT NULL;
ALTER TABLE public.company_settings
ADD COLUMN IF NOT EXISTS ai_backfill_cancel_requested boolean NOT NULL DEFAULT false;
ALTER TABLE public.company_settings
ALTER COLUMN ai_backfill_cancel_requested SET DEFAULT false;
UPDATE public.company_settings
SET ai_backfill_cancel_requested = false
WHERE ai_backfill_cancel_requested IS NULL;
ALTER TABLE public.company_settings
ALTER COLUMN ai_backfill_cancel_requested SET NOT NULL;
NOTIFY pgrst, 'reload schema';