Skip to content

[Due for payment 2025-03-05] [Due for payment 2025-02-18] [HOLD for payment 2025-02-04] Tweaks to the Create Expense Flow  #52981

Description

@trjExpensify

Coming from here.

Background: We're experimenting with an A/B test of a combined "Create expense" flow to see if we improve the decision juncture between "Submit expense" and "Track expense" out the gate. We've seen in Fullstory that submitters are still getting wrong-footed on this page choosing the "Just track it (don't submit it!)" option row. All the while, the workspace settings actually determine whether an expense created is submitted on creation, or if it’s added to a draft report to be submitted later, either manually or automatically with scheduled submit.

Problem: When submitters choose the "Just track it (don't submit it!)" on this page, they end up creating non-reimbursable expenses in the selfDM, which leads to confusion and having no recourse to getting paid back.

Solution: Let's make a couple of tweaks to the Create expense flow, as follows:

Participant selector screen

  • Title it "Choose recipient"
  • Remove the "Just track it (don't submit it)" option row
  • Add a section for "Workspaces" at the top (if you're a member of a workspace). Your primary workspace should be in the top position. That should be followed by a section for "Personal", which has your selfDM. Then followed by the existing "Recents" (if you have any that aren't already above in workspaces/selfDM) and "Contacts" sections.

Confirmation page screen

  • Title it "Confirm details"
  • Update the confirmation button to read: "Create $amount expense"

image

CC: @danielrvidal @JmillsExpensify @Expensify/design

New addition from @dubielzyk-expensify to add as a follow-up

In the participant selector, switch out the second line of each workspace row (which currently reads Workspace) to be the displayName of the approver ("submitsTo") instead. Use the primaryLogin as a fallback if no displayName is set.

image
Issue OwnerCurrent Issue Owner: @trjExpensify

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionNewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Done
Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions