Files
accounted/supabase/migrations/20260423140000_ai_requests.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

78 lines
3.0 KiB
SQL

-- ai_requests: structured asks from the AI agent to the user.
--
-- When the AI agent cannot produce a proposal because something is missing or
-- ambiguous (blurry receipt, no candidate transactions, uncertain VAT), it
-- creates an ai_requests row instead of an ai_proposals row. The UI renders
-- these as actionable cards with typed forms.
--
-- One open request per (subject, request_type) enforced by a partial unique
-- index so the orchestrator can safely re-issue on retries without creating
-- duplicates.
CREATE TABLE IF NOT EXISTS public.ai_requests (
id uuid PRIMARY KEY DEFAULT uuid_generate_v4(),
company_id uuid NOT NULL REFERENCES public.companies(id) ON DELETE CASCADE,
-- What the request is about
subject_type text NOT NULL
CHECK (subject_type IN ('inbox_item')),
subject_id uuid NOT NULL,
-- What the AI is asking for
request_type text NOT NULL
CHECK (request_type IN (
'reupload_document',
'pick_transaction',
'specify_vat',
'clarify_business_private',
'needs_manual'
)),
message text NOT NULL,
required_fields jsonb,
options jsonb,
-- Lifecycle
status text NOT NULL DEFAULT 'open'
CHECK (status IN ('open', 'resolved', 'dismissed')),
response_json jsonb,
resolved_at timestamptz,
resolved_by_user_id uuid REFERENCES auth.users(id) ON DELETE SET NULL,
-- Provenance
model text,
prompt_version text,
created_at timestamptz NOT NULL DEFAULT now(),
updated_at timestamptz NOT NULL DEFAULT now()
);
-- Only one open request per (subject, request_type) at a time
CREATE UNIQUE INDEX IF NOT EXISTS idx_ai_requests_one_open_per_subject_type
ON public.ai_requests (subject_type, subject_id, request_type)
WHERE status = 'open';
-- Lookup by company
CREATE INDEX IF NOT EXISTS idx_ai_requests_company_status
ON public.ai_requests (company_id, status);
-- Lookup by subject (for cascading when the inbox item is processed)
CREATE INDEX IF NOT EXISTS idx_ai_requests_subject
ON public.ai_requests (subject_type, subject_id);
-- RLS: company-scoped using user_company_ids()
ALTER TABLE public.ai_requests ENABLE ROW LEVEL SECURITY;
CREATE POLICY "ai_requests_select" ON public.ai_requests
FOR SELECT USING (company_id IN (SELECT public.user_company_ids()));
CREATE POLICY "ai_requests_insert" ON public.ai_requests
FOR INSERT WITH CHECK (company_id IN (SELECT public.user_company_ids()));
CREATE POLICY "ai_requests_update" ON public.ai_requests
FOR UPDATE USING (company_id IN (SELECT public.user_company_ids()));
-- updated_at trigger
CREATE TRIGGER ai_requests_updated_at
BEFORE UPDATE ON public.ai_requests
FOR EACH ROW EXECUTE FUNCTION public.update_updated_at_column();
NOTIFY pgrst, 'reload schema';