Reimbursement Overview
Feature Detail
Description
The Reimbursement Overview gives organization admins an aggregated, filterable view of all expense claims - pending, approved, rejected, and paid. Summary statistics show total claimed, total approved, pending liability, and average time-to-decision. The overview supports financial planning, Bufdir reporting, and pre-export reconciliation for organizations integrating with external accounting systems such as Xledger (Blindeforbundet) and Dynamics (HLF).
Sources & reasoning
HLF and Blindeforbundet both require accounting system integration, which needs a consolidated financial view as prerequisite for reconciliation before export. The Bufdir one-click export requirement also depends on clean aggregated expense data. The Fase 2 roadmap confirms full reimbursement handling as v1.0, and an overview is the natural admin surface that feeds both accounting exports and Bufdir report generation.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Organization admins at HLF and Blindeforbundet need a consolidated view of reimbursement liability and throughput to plan budgets, meet reporting deadlines, and reconcile with accounting systems before export. Without an overview, admins must query individual claims or use spreadsheets - reintroducing the manual aggregation the platform eliminates. The overview also surfaces anomalies: duplicate submissions, unusually high mileage, or spikes in pending volume. For Bufdir-funded organizations, the financial data feeds directly into grant reporting and audit responses, reducing the effort of compliance reporting.
The overview page is server-rendered, querying expenses joined with expense_approvals, users, and expense_types grouped by status and period. Stat cards show total claimed, approved, pending, and mean decision time. A filterable data table lists individual claims with CSV export respecting active filters. For organizations with accounting integration enabled, an Export to Accounting button triggers the Accounting API Adapter. Data is strictly scoped to the admin's organization; global admins require an explicit support-access grant before seeing any org data, consistent with the tenant isolation model.
Components (43)
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.