[Due for payment 2026-01-27] Invoice - "Multiple attendees required for this category" appears on invoice row

[jponikarchuk]

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.3-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: #79050
Email or phone of affected tester (no customers): sjnodijsodijsoijsio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Search

Action Performed:

Preconditions:

• Rules are enabled.
• Enable Attendee tracking in Rules.
• Make Advertising category require attendees in category settings.
• Invoice is enabled.

1. Go to staging.new.expensify.com
2. Open FAB > Send invoice.
3. Enter amount > Next.
4. Select a user > Next.
5. On confirm page, select Advertising category.
6. Send the invoice.
7. Go to Reports > Expenses.
8. Click Type dropdown.
9. Select Invoice and click Apply.

Expected Result:

"Multiple attendees required for this category" will not appear on invoice row.

Actual Result:

"Multiple attendees required for this category" appears on invoice row.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @JmillsExpensify (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.

[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.

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #79050 - "feat: add ability to require attendees based on category selection (rework)" by @ikevin127 (High confidence)
Related Issues: #79008 (invoice submission issue that was fixed in the same PR)

Recommendation: ROLL FORWARD

The causing PR is clear and the fix is straightforward. A small patch to add the invoice check in the search list display logic is simpler than reverting this large feature PR that adds the "require attendees for category" functionality.

Labels: Keeping DeployBlockerCash (frontend bug in App requires App fix)

Detailed Analysis

Evidence
PR #79050 added the ability to require attendees based on category selection. The PR correctly handles invoice validation during submission by adding a check in MoneyRequestConfirmationList.tsx that skips the validation when iouType !== CONST.IOU.TYPE.INVOICE. This prevents the validation from blocking invoice submission. However, the violation still appears in the Search/Reports list view because TransactionListItem.tsx does not have the same check.

Verification
Affected file: src/components/SelectionListWithSections/Search/TransactionListItem.tsx (lines 159-167)

The syncMissingAttendeesViolation() function is called without checking if the transaction belongs to an invoice report. PR #79050 merged on 2026-01-14 and aligns with when this bug appeared in staging (version 9.3.3-0).

Root Cause
The PR has two code paths for handling the missingAttendees violation:

1. Submission validation (MoneyRequestConfirmationList.tsx): Correctly skips invoices
2. Display in search list (TransactionListItem.tsx): Missing the invoice check

The fix should add a check for reportForViolations?.type === CONST.REPORT.TYPE.INVOICE before calling syncMissingAttendeesViolation() to skip invoice transactions.