Receipt Photo Upload

Receipt documentation is a compliance requirement for expense reimbursement above defined thresholds; HLF sets this at 100 kr. Without digital capture, peer mentors retain paper receipts and submit them separately, creating friction, loss risk, and processing delays for coordinators who must reconcile paper with digital records. Integrating receipt capture into the same registration flow removes the paper step entirely and creates an immutable audit trail directly linked to the specific expense item. For Bufdir grant compliance and internal accounting audits, receipts digitally attached to expense records eliminate a manual reconciliation step. The result is faster approval cycles, fewer missing-receipt follow-ups from coordinators, and lower administrative cost per claim. Offline queuing ensures peer mentors in low-connectivity areas are not disadvantaged by the requirement.

Uses Flutter's image_picker package for camera and gallery access, with platform-level permission handling following the pattern established by CalendarPermissionHandler and SpeechPermissionHandler. Images are compressed to a configurable maximum resolution before upload to limit storage cost and transmission time. ReceiptStorageClient requests a presigned upload URL from the backend, writes the image directly to object storage, then stores the resulting object key in the expense_receipts table. In offline mode the compressed image is stored as a local file path reference in Drift and queued in the mutation outbox alongside the parent expense record. On reconnect the outbox processor uploads the image first, receives the object key, then persists the expense_receipts row. The backend enforces the receipt requirement server-side by checking whether a receipt record exists for above-threshold items before allowing approval, providing defense in depth independent of client flow.