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
{{ message }}
Repository navigation
Expense - Negative amount can be paid when there is held expense, which leads to error #72141
Version Number: 9.2.28-0 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:#65001 Email or phone of affected tester (no customers):applausetester+sdosdijodsjnois1@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Delayed submissions and Add approvals are disabled.
Go to staging.new.expensify.com
Go to workspace chat.
Create a negative expense (amount: -10) in workspace chat.
Create an expense (amount: 30) in workspace chat.
Open expense report.
Hold the expense with positive amount (amount:30).
Click Submit.
Click Mark as paid.
Click Pay only -10.00.
Expected Result:
App will not show the option to pay the negative amount.
Actual Result:
App shows the option to pay the negative amount and it throws error.
👋 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:
Identify the pull request that introduced this issue and revert it.
I checked on the classic and it seems to be possible so do you know why the requests are not passing @nkuoch ? this is the request id 98f76e6b483770bb-LAX
So I need help what we should do on the frontend now, should we disable completely option for paying ? so then the button Mark ${negative value} as paid will be inactive. Or should we allow users to pay only to pay total which in case of the video from the issue will be $20?
@lakchote@pasyukevich@kubabutkiewicz@joekaufmanexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Activity
melvin-bot commentedon Oct 8, 2025
Triggered auto assignment to @joekaufmanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Oct 8, 2025
Triggered auto assignment to @marcochavezf (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 8, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 8, 2025
👋 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:
18 remaining items
kubabutkiewicz commentedon Oct 16, 2025
I checked on the classic and it seems to be possible so do you know why the requests are not passing @nkuoch ? this is the request id
98f76e6b483770bb-LAXnkuoch commentedon Oct 18, 2025
98f76e6b483770bb-LAX is calling PayMoneyRequest
So it's throwing with
kubabutkiewicz commentedon Oct 20, 2025
So I need help what we should do on the frontend now, should we disable completely option for paying ? so then the button
Mark ${negative value} as paidwill be inactive. Or should we allow users to pay only to pay total which in case of the video from the issue will be $20?nkuoch commentedon Oct 20, 2025
oh, sorry, maybe I can do a back end fix to allow marking a negative report as paid: https://github.com/Expensify/Auth/pull/17730
joekaufmanexpensify commentedon Oct 22, 2025
Backend PR merged
melvin-bot commentedon Oct 22, 2025
@lakchote @pasyukevich @kubabutkiewicz @joekaufmanexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
joekaufmanexpensify commentedon Oct 23, 2025
@kubabutkiewicz the backend PR was deployed.
kubabutkiewicz commentedon Oct 24, 2025
Looks like its working now,
joekaufmanexpensify commentedon Oct 27, 2025
Great. Closing this out as I think it's all set. LMK if anything else is needed!