Expense - CONFIRMED label does not show on OD after confirming payment on ND

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.81-2
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #90202
Email or phone of affected tester (no customers): sdjsodnjiodsjsoinj2@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Admin invites member to the workspace.

1. Go to staging.new.expensify.com
2. [Member] Go to workspace chat, submit an expense and click Submit on the expense preview.
3. [Admin] Open member's report and click Approve.
4. [Member] Open the report.
5. [Member] Click More > Received payment > Yes, I've received payment.
6. [Member] Log into Old Dot with the same account.
7. [Member] On OD, go to Reports tab.
   → The report row with received payment from Step 5 does not show CONFIRMED label.
8. [Member] Open the report > click Reimbursement Received > Yes, Mark as Reimbursed.
9. [Member] Return to Reports tab.
   → The report row with reimbursement received now shows CONFIRMED label.

Expected Result:

In Step 7, after confirming Received payment on ND, OD should show CONFIRMED label on the report row.

Actual Result:

In Step 7, after confirming Received payment on ND, OD does not show CONFIRMED label on the report row.
In Step 9, CONFIRMED label is only shown after user confirms reimbursement on OD.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7162827_1779727306683.6.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7162827

Issue Owner

Current Issue Owner: @ishpaul777

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/590fa7b90f77da952a6122f1e10fc52ba99b29702acb92f96cb70e7ee1e335bd

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #90202

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

Proposal

Problem: When a submitter confirms "Received payment" on New Dot, the MarkReportPaymentReceived API command sends only {reportID, reportActionID} to the backend. New Dot optimistically updates correctly, but Old Dot never shows the CONFIRMED label — indicating the backend handler likely doesn't update the field(s) Old Dot reads for that label.

Solution: This appears to be a backend/internal issue. A separate internal investigation is needed.

The MarkReportPaymentReceived backend handler needs to be checked to ensure it updates the same report state/confirmed fields that Old Dot queries when rendering the CONFIRMED label. For comparison, Old Dot's own "Mark as Reimbursed" flow works correctly, so the backend handler for that flow can serve as a reference for what fields need updating.

Evidence

Frontend flow (correct):

1. Submitter sees "Received payment" option via isReceivedPaymentAction
2. Confirmation modal triggers markReportPaymentReceived via useLifecycleActions
3. Optimistic data correctly sets statusNum=REIMBURSED(4), stateNum=APPROVED(2) — New Dot shows the right state

The gap — minimal API params:
MarkReportPaymentReceivedParams sends only reportID and reportActionID. Compare with PayMoneyRequest which sends paymentMethodType, amount, chatReportID, full flag, etc. The backend must infer everything from just the report ID, and likely misses updating a legacy field Old Dot depends on for the CONFIRMED label.

Why OD's own confirm works: When the user confirms reimbursement through Old Dot's UI (step 8–9), that flow calls a different backend endpoint that does update the necessary fields — proving the data model supports it, but MarkReportPaymentReceived doesn't follow the same path.

---

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.

[joekaufmanexpensify]

cc @ishpaul777 as you worked on the backend changes for #83035. I agree we should fix this. However, I'm not convinced we need to block on it. The report is being marked as paid in both OldDot and NewDot when using the button in NewDot. If this Confirmed label is just a label and not a report sub-state that isn't being applied, that doesn't seem like a blocker to me personally. Curious what others think though.

cc @nabi-ebrahimi @Pujan92 too