Scan expense with violations moved to the processing report

[mitarachim]

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.2.58-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #74041
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: MacBook Air 15.6.1 Chrome
App Component: Money Requests

Action Performed:

1. Sign in to ND with expensifail account
2. Create a workspace, set Submission frequency to Instantly
3. Open workspace chat, create a couple of manual expenses, verify they are grouped in one report
4. Click "+" button and create a scan expense in the workspace chat, uploading receipt, that will fail the scan
5. Verify the scan expense is created in the separate report, while scanning
6. Repeat step 4, uploading a valid receipt, but not setting the category

Expected Result:

Scan expense is created as a new expense report while it is scanning. If a violation exists, but no existing draft reports, the expense will be left on the draft report it’s on

Actual Result:

Scan expense with violations is moved to the processing report, if no empty reports exist in the workspace

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7003095_1763062950148.scan_expenses_with_violations.mp4

View all open jobs on GitHub

[melvin-bot]

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

[mitarachim]

Issue was found while executing QA for PR #74041

[parasharrajat]

Let's first confirm if this is really an issue.

[twisterdotcom]

Scan expense with violations is moved to the processing report, if no empty reports exist in the workspace

@garrettmknight, king of Instant Submit can correct me if I'm wrong, but this is correct. If the report is still with the first manager and has not been approved at all yet, then it can go on the Processing report.

In the event the Processing report HAS been approved at least once, then the expense with violations should stay on a new Processing report instead.

[garrettmknight]

This is expected in the current version of Instant Submit. We don't separate violations on separate reports yet.