Mattsson
1af977950b
* 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>
48 lines
2.0 KiB
SQL
48 lines
2.0 KiB
SQL
-- AI provenance on journal entries.
|
|
--
|
|
-- Adds two columns to journal_entries so that entries posted via the AI
|
|
-- agent flow carry a BFL-defensible audit trail: who created this entry,
|
|
-- and which AI proposal did the user approve to produce it?
|
|
--
|
|
-- `created_via` is informational — it describes the *method* of creation,
|
|
-- not the business event. The existing `source_type` column still describes
|
|
-- the business event (bank_transaction, invoice_created, supplier_invoice_
|
|
-- registered, etc.). An AI-proposed booking for a bank transaction will
|
|
-- have source_type='bank_transaction' AND created_via='ai_proposed'.
|
|
--
|
|
-- The existing immutability trigger (migration 017) prevents changes to
|
|
-- posted entries. These new columns are set while the entry is still in
|
|
-- draft status and frozen at commit — consistent with how the trigger
|
|
-- already treats other fields.
|
|
|
|
ALTER TABLE public.journal_entries
|
|
ADD COLUMN IF NOT EXISTS created_via text NOT NULL DEFAULT 'manual';
|
|
|
|
ALTER TABLE public.journal_entries
|
|
ALTER COLUMN created_via SET DEFAULT 'manual';
|
|
|
|
-- Re-apply NOT NULL for environments where the column was added out-of-band
|
|
UPDATE public.journal_entries SET created_via = 'manual' WHERE created_via IS NULL;
|
|
|
|
ALTER TABLE public.journal_entries
|
|
ALTER COLUMN created_via SET NOT NULL;
|
|
|
|
ALTER TABLE public.journal_entries
|
|
DROP CONSTRAINT IF EXISTS journal_entries_created_via_check;
|
|
|
|
ALTER TABLE public.journal_entries
|
|
ADD CONSTRAINT journal_entries_created_via_check
|
|
CHECK (created_via IN ('manual', 'ai_proposed', 'imported', 'system'));
|
|
|
|
-- Nullable FK — only AI-proposed entries link back to a proposal
|
|
ALTER TABLE public.journal_entries
|
|
ADD COLUMN IF NOT EXISTS source_proposal_id uuid
|
|
REFERENCES public.ai_proposals(id) ON DELETE SET NULL;
|
|
|
|
-- Audit lookup: "show me all AI-proposed entries from last month"
|
|
CREATE INDEX IF NOT EXISTS idx_journal_entries_created_via_ai
|
|
ON public.journal_entries (company_id, created_at DESC)
|
|
WHERE created_via = 'ai_proposed';
|
|
|
|
NOTIFY pgrst, 'reload schema';
|