Auto-Approval Rules
Feature Detail
Description
Auto-Approval Rules lets organization admins configure threshold-based rules that automatically approve expense claims meeting defined criteria - for example, claims under 50 kilometres with no receipts, or any claim below a monetary ceiling per expense type. Rules are stored per organization and evaluated on submission; matching claims are approved immediately without entering the manual queue. Admins can create, edit, and disable rules at any time, with the new configuration taking effect for all subsequent submissions.
Sources & reasoning
HLF explicitly defines the auto-approval boundary as 50 km / no receipts and the Fase 2 roadmap calls for 'terskelbasert godkjenning' (threshold-based approval). This feature is the admin-side configuration surface for that logic, enabling each organization to tune rules without engineering involvement and without branching the product per tenant.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
HLF's workshop data shows most peer mentor claims are straightforward travel under 50 km with no receipts. Requiring sign-off on every such claim adds overhead that delays payment and discourages legitimate submissions. Configurable auto-approval rules eliminate this friction while preserving manual oversight for higher-value claims. Different organizations can tune thresholds without code changes, supporting the multi-tenant architecture directly. Reduced review volume lowers coordinator burden and shortens reimbursement cycle time, improving volunteer satisfaction across all organizations on the platform.
Rules are stored in an approval_rules table with columns organization_id, expense_type_id (nullable for catch-all), max_distance_km, max_amount_nok, require_receipt_above_nok, and enabled. On submission, the API evaluates the claim against the organization's active rules ordered by specificity. If a rule matches, the claim status is set to auto_approved and an expense_approvals row is written with approver_type = system. The Admin Web Portal exposes a rules configuration page with numeric inputs per threshold dimension and a live preview showing how many recent claims would match the current settings.
Components (46)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.