You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In OldDot now, we show submitters the Received reimbursement option when they have an Approved or Done report. (It's shown whether payments are set to Direct, Indirect, or None.
If an admin does pay a report via ACH, we remove the option for the submitter. If the admin marks the report as paid, the submitter can still use Received reimbursement.
When the user taps Received reimbursement we show an error modal explaining that they should only use this if the company pays them outside of Expensify and they have actually received payment.
Proceeding there marks the report as paid and adds a report comment reflecting the action.
Once the user marks that they received reimbursement, we continue showing the button, and they can complete the process again to add additional report comments. This is a bit odd...but perhaps we do it in case the first time is an accident or something, so the user can indicate when they do actually receive payment.
This button is only shown to submitters, not admins.
Once a report is marked as reimbursed, the admin has the option to Unapprove it, which negates the action. (We show this even if approvals are off, and the report was never actually approved). This also strikes me as odd, but I feel like maintaining parity across platforms for this action feels most important right now.
One change from OldDot: I feel like this button fits best in the More menu on the report in NewDot, but curious if design agrees.
I also feel like we might want to call it Received payment in NewDot to match the Pay button there, which we call Reimburse in OldDot.
We have some pretty specific BE logic around this button that we don't want to change. Specifically, that marking a report as payment received shouldn't create a payment entry in the company's connected accounting system as this should only be controlled by the admin and not a submitter.
Coming from here, we want to add the
Received reimbursementoption for submitters in NewDot to maintain parity with OldDot.OldDot
Approved report
2026-02-20_11-06-50.mp4
Done report
2026-02-20_11-08-21.mp4
Admin action to "unapprove" report after marking received reimbursement
2026-02-20_11-29-14.mp4
Final NewDot mocks (figma)
Notes
Received reimbursementoption when they have anApprovedorDonereport. (It's shown whether payments are set toDirect,Indirect, orNone.Received reimbursement.Received reimbursementwe show an error modal explaining that they should only use this if the company pays them outside of Expensify and they have actually received payment.Unapproveit, which negates the action. (We show this even if approvals are off, and the report was never actually approved). This also strikes me as odd, but I feel like maintaining parity across platforms for this action feels most important right now.Moremenu on the report in NewDot, but curious if design agrees.Received paymentin NewDot to match thePaybutton there, which we callReimbursein OldDot.cc @JmillsExpensify @trjExpensify @heyjennahay
EXFY-19750
Issue Owner
Current Issue Owner: @mallenexpensifyUpwork Automation - Do Not Edit