Skip to content

[Due for payment 2026-08-05] [$250] Reorder onboarding steps: feature selection before accounting integration #89594

Closed

Description

@MelvinBot

Problem

During onboarding, some "manage my team" users select None in the Accounting integration step, then later toggle Accounting back on in the feature selection step (since it shows as disabled after choosing None). The current step order (Accounting first, then feature selection) leads to confusion because None logically reads as "none of these options, but I still use accounting."

Proposed Changes

  1. Switch the order of onboarding steps: Show the feature selection step first, then the accounting integration list. This makes the flow go from broader functionality to more granular, reducing confusion.
  2. If the user keeps Accounting enabled in feature selection, show the accounting integration options where:
    • Remove the None option
    • Make Other a free text input

Rationale

Users are selecting None instead of Other, then re-enabling accounting in the next step. Reordering the steps and cleaning up the options should reduce this friction.

Slack thread: https://expensify.slack.com/archives/C07HPDRELLD/p1776855884573059

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022054850490363431325
  • Upwork Job ID: 2054850490363431325
  • Last Price Increase: 2026-05-14
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. dylanexpensify commented on May 5, 2026

    @dylanexpensify
    Contributor

    @MelvinBot propose how you'd implement this.

  2. MelvinBot commented on May 5, 2026

    @MelvinBot
    ContributorAuthor

    Proposal

    What is the root cause of that problem?

    The onboarding step order for "manage my team" users is defined in getOnboardingStepCounter.ts:42 as EMPLOYEES → ACCOUNTING → INTERESTED_FEATURES. This puts accounting integration selection before feature selection, so users see "None" and pick it (thinking "none of these"), then later re-enable Accounting in the feature toggle step. The same order also appears for VSB/SMB qualifier flows at line 55-56.

    What changes do you think we should make in order to solve the problem?

    1. Swap step order in getOnboardingStepCounter.ts:

    • Change MANAGE_TEAM to [EMPLOYEES, INTERESTED_FEATURES, ACCOUNTING]
    • Apply the same swap to the VSB and SMB qualifier flows on lines 55-56

    2. Update hardcoded navigation in the continue handlers:

    3. Conditionally show the Accounting step: If the user disables Accounting in feature selection, skip the Accounting step entirely.

    4. Remove the "None" option from BaseOnboardingAccounting.tsx:149-162 — delete the noneAccountingOption object and remove it from the returned array at line 179.

    5. Convert "Other" to a free text input: Replace the static "Other" option at BaseOnboardingAccounting.tsx:164-177 with a selectable option that, when selected, reveals a TextInput for the user to type their accounting tool name. Store the typed value (instead of the string 'other') via setOnboardingUserReportedIntegration.

    What alternative solutions did you explore? (Optional)

    An alternative is to keep the step order the same but just remove "None" — however, this doesn't address the broader UX confusion of asking for a specific integration before asking whether the user even wants accounting enabled. Swapping the order makes the flow logically progressive (broad feature selection → specific integration) and naturally eliminates the need for "None."


    Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

  3. melvin-bot commented on May 8, 2026

    @melvin-bot

    @dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  4. dylanexpensify commented on May 12, 2026

    @dylanexpensify
    Contributor

    Moving forward this week!

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 14, 2026
  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 14, 2026
  7. melvin-bot commented on May 14, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)

  8. 51 remaining items

  9. melvin-bot commented on Aug 4, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  10. melvin-bot commented on Aug 4, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2054850490363431325/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. mallenexpensify commented on Aug 7, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @nabi-ebrahimi paid $250 via Upwork
    Contributor+: @parasharrajat due $250 via NewDot

    @nabi-ebrahimi can you please accept the job below? Please reply here and tag me once you have.
    If you're not sent an offer in Upwork when you're assigned to an issue, please tag me. If an Upwork job exists, please submit a proposal.
    https://www.upwork.com/jobs/~022085551964297837554

    ^ Test case created. Thx

  12. nabi-ebrahimi commented on Aug 10, 2026

    @nabi-ebrahimi

    @mallenexpensify, Accepted the offer. thanks.

  13. mallenexpensify commented on Aug 10, 2026

    @mallenexpensify
    Contributor

    @nabi-ebrahimi paid, summary updated above. Thx.

  14. m-natarajan commented on Aug 13, 2026

    @m-natarajan

    @parasharrajat This is regarding the Regression test proposal
    Just to confirm, Features modal displayed before accounting modal for all the number of employees option. Hope its expected.

  15. parasharrajat commented on Aug 14, 2026

    @parasharrajat
    Member

    yes it is fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributorImprovementItem broken or needs improvement.Task

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions