Background
The For you slot on Home currently surfaces report-level actions: Submit, Approve, Pay, and Export. These all operate on reports as the unit of work.
By customer request, we're adding a new expense-level action that highlights flagged expenses that fall outside the user's company expense policy. This gives employees a single, low-effort entry point to address policy-flagged expenses before they roll up into a report, rather than discovering them only at submission time or when a report is rejected.
We use Review rather than Fix because not every flagged expense is necessarily wrong — some just need additional context (e.g. a comment explaining an out-of-policy charge). Review is more accurate across all flag types and avoids implying employee fault.
Product and design details
- This row is titled
Review X expenses (e.g. Review 4 expenses).
- We use the exclamation icon and
Begin button – all in green.
- It appears in the
For you slot, always above Submit, Approve, Pay, or Export.
- This row applies to users with one or more expenses flagged by policy rules, on any workspace.
- The relevant flag types already exist in
OpenApp, such as:
- Missing category
- Missing tag
- Amount exceeds the per-category max defined in policy
- Attendees or description required
- And so on
OpenApp doesn't return report field violations, so they are out of scope.- We aggregate flagged expenses across all workspaces the user submits to. We do not break them down or filter them per workspace.
- Clicking
Begin in the Review row opens all policy-flagged expenses on Draft reports in the RHP on Home. Users can navigate through all expenses the carousel in the new expense headers being added in this issue.
- After all flagged expenses are addressed (either re-coded or commented to resolve the violation), the row is hidden.
- If the user has no policy-flagged expenses, the row does not appear.
Issue Owner
Current Issue Owner: @adamgrzybowski
Background
The
For youslot on Home currently surfaces report-level actions: Submit, Approve, Pay, and Export. These all operate on reports as the unit of work.By customer request, we're adding a new expense-level action that highlights flagged expenses that fall outside the user's company expense policy. This gives employees a single, low-effort entry point to address policy-flagged expenses before they roll up into a report, rather than discovering them only at submission time or when a report is rejected.
We use
Reviewrather thanFixbecause not every flagged expense is necessarily wrong — some just need additional context (e.g. a comment explaining an out-of-policy charge). Review is more accurate across all flag types and avoids implying employee fault.Product and design details
Review X expenses(e.g. Review 4 expenses).Beginbutton – all in green.For you slot, always above Submit, Approve, Pay, or Export.OpenApp, such as:OpenAppdoesn't return report field violations, so they are out of scope.Beginin theReviewrow opens all policy-flagged expenses onDraftreports in the RHP on Home. Users can navigate through all expenses the carousel in the new expense headers being added in this issue.Issue Owner
Current Issue Owner: @adamgrzybowski