Skip to content

[BT-125] Migrate Money Request (Part 6) #83853

Closed

Description

@mjasikowski

Description

Current State:

  • 5 routes for money request receipt, hold, and split expense
  • These routes use backTo parameter for return navigation

Implementation:

  • Replace getRoute(..., backTo) with createDynamicRoute()
  • Add source screens to entryScreens array
  • Remove backTo parameter from route definitions
  • Test forward/back navigation

Scope

Routes (5):

Route Constant Path
MONEY_REQUEST_RECEIPT_VIEW receipt-view/:transactionID
MONEY_REQUEST_HOLD_REASON :action/:iouType/hold/:transactionID/:reportID
SPLIT_EXPENSE create/split-expense/overview/:reportID/:transactionID
SPLIT_EXPENSE_SEARCH create/split-expense/overview/:reportID/:transactionID/search
SPLIT_EXPENSE_CREATE_DATE_RANGE create/split-expense/create-date-range/:reportID/:transactionID

Usages

MONEY_REQUEST_RECEIPT_VIEW:

  • src/pages/iou/request/step/IOURequestStepScan/ReceiptPreviews/index.tsx:97

MONEY_REQUEST_HOLD_REASON:

  • src/libs/ReportUtils.ts:4896

SPLIT_EXPENSE:

  • src/libs/actions/IOU/index.ts:13197,13230

SPLIT_EXPENSE_SEARCH:

  • src/libs/actions/IOU/index.ts:13195,13228

SPLIT_EXPENSE_CREATE_DATE_RANGE:

  • Search for usages in split expense date range flow

Files to modify:

  • src/ROUTES.ts - Update route definitions
  • src/libs/Navigation/types.ts - Remove backTo from params
  • Components listed above

Migration Progress

  • MONEY_REQUEST_RECEIPT_VIEW
  • MONEY_REQUEST_HOLD_REASON
  • SPLIT_EXPENSE
  • SPLIT_EXPENSE_SEARCH
  • SPLIT_EXPENSE_CREATE_DATE_RANGE
Issue OwnerCurrent Issue Owner: @suneox

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Mar 2, 2026
  2. melvin-bot commented on May 14, 2026

    @melvin-bot

    This issue has not been updated in over 15 days. @mananjadhav, @mjasikowski, @huult eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  3. 31 remaining items

  4. suneox commented on Aug 21, 2026

    @suneox
    Contributor

    the implementation plan is finished and waiting for the regression testing period

  5. melvin-bot commented on Aug 24, 2026

    @melvin-bot

    @suneox / @huult

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.59-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-08-31. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  6. suneox commented on Aug 26, 2026

    @suneox
    Contributor

    Not overdue, the implementation plan is finished and waiting for prod deploy.

  7. melvin-bot commented on Aug 31, 2026

    @melvin-bot

    @suneox Huh... This is 4 days overdue. Who can take care of this?

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

Metadata

Metadata

Labels

DailyKSv2InternalRequires API changes or must be handled by Expensify staffSkip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions