User Interface medium complexity mobile
0
Dependencies
0
Dependents
3
Entities
0
Integrations

Description

Mobile form that lets peer mentors and coordinators log a travel expense after an activity. Presents fixed expense-type choices to prevent illegal combinations and pre-fills the linked activity, date, and route where possible.

Feature: Travel Expense Registration

expense-form

Sources & reasoning

Section 2.1 and the priority matrix mark travel expense registration as SHOULD HAVE in Phase 2 (Core Product) for HLF and Blindeforbundet, with explicit requirements for fixed expense types. Phase 5 roadmap also lists 'Reiserefusjonshåndtering' under Core Product.

  • Begge organisasjoner har behov for registrering av kilometergodtgjørelse, bompenger, parkering og kollektivt. ... Faste valg for utleggstype - ikke fritekst - for å hindre feilkombinasjon (f.eks. både km og bussbillett).
  • Reiserefusjon / utleggsregistrering | - | - | ✓ | ✓ | ✓ | SHOULD HAVE | 2

Responsibilities

  • Render fixed expense-type selector (mileage, tolls, parking, public transport)
  • Pre-fill activity, date, and route fields from the linked activity context
  • Validate input client-side before submission to the Expense Service
  • Display submission status and approval outcome to the user
  • Block illegal expense-type combinations on the same leg

Interfaces

openForActivity(activityId): void
submitExpense(payload): SubmissionResult
selectExpenseType(type): void

Related Data Entities (3)

Data entities managed by this component