Invoice - Invoice with 0 amount can be created

[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.83-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91310
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Critical User Impact
Device used: Windows 11 pro /Chrome
App Component: Workspace Settings

Action Performed:

Precondition:
Run Onyx.merge('betas', ['newManualExpenseFlow']); in console.
Enable Invoices in workspace settings.
User never sent an invoice for any user

1. Go to staging.new.expensify.com
2. Go to invoice room.
3. Click + > Send invoice.
4. Enter amount > Next.
5. On confirm page, change the amount to 0.
6. Click Send invoice.
7. Open the invoice.

Expected Result:

Invoice with 0 amount cannot be sent.

Actual Result:

" Unexpected error sending this invoice. Please try again later.Invoices must be greater than zeroUnexpected error creating this chat. Please try again later. " error shown after creating the invoice.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7163848_1779833158301.bandicam_2026-05-27_00-52-48-229.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7163848

[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/f19e7fe74fe6106bf23f661fccd14dbfaee3c252bf6a9830df4657ab117d0a5c

[melvin-bot]

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

[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

What is the root cause of that problem?

When a first-time invoice sender (no invoicing details yet) changes the amount to 0 on the confirmation page and clicks "Send invoice", the confirm action in confirmAction.ts:84 short-circuits to navigate to the CompanyInfo step before validate() is called at line 89. Then IOURequestStepCompanyInfo.tsx:80-108 calls sendInvoice() directly without any amount validation, allowing $0 invoices to reach the backend which rejects them.

The amount validation logic in useConfirmationValidation and MoneyRequestUtils.isValidMoneyRequestAmount correctly rejects $0 invoices — it just never gets invoked on this code path.

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

Move the validate() call in confirmAction.ts so it runs before the CompanyInfo short-circuit. This way the existing amount validation catches $0 invoices regardless of whether the user has invoicing details set up.

What alternative solutions did you explore? (Optional)

Adding amount validation directly in IOURequestStepCompanyInfo.tsx's submit function. This would also work but duplicates validation logic that already exists in useConfirmationValidation. The proposed fix is simpler — it ensures the existing validation always runs.

Investigation details

Data flow:

1. User enters a valid amount, navigates to the confirmation page
2. On the confirmation page, user changes amount to 0 via the inline amount field
3. User clicks "Send invoice"
4. confirmAction.ts:84 checks iouType === INVOICE && !hasInvoicingDetails(policy) → true for first-time senders → navigates to CompanyInfo and returns before validation
5. IOURequestStepCompanyInfo.submit() calls sendInvoice() with amount=0 — no amount check
6. Backend rejects: "Invoices must be greater than zero"

Related issue: #90661 (same underlying bug, reported earlier)

---

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.