[$250] E-Receipts Generated in Classic but Not Displayed in New Expensify (Collect Plan)

[m-natarajan]

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:
Reproducible in staging?: Needs Reproduction (Reproduction blocked)
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @nicollyrodrigues-max
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Open a workspace on the Collect plan
2. Create or review card expenses
3. In New Expensify (ND): Open an expense
4. Observe no eReceipt displayed
5. In Classic Expensify: Open the same expense
6. Observe eReceipt is generated and visible

Expected Result:

E-receipts should:
Be generated and visible in both Classic and New Expensify

Actual Result:

Classic:
E-receipts are generated and visible
New Expensify:
E-receipts are not displayed

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

The screenshots and video for the issue are in Slack thread

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @thesahindia

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022042621694076641665
• Upwork Job ID: 2042621694076641665
• Last Price Increase: 2026-04-17

[MelvinBot]

Proposal

What is the root cause of that problem?

In New Expensify, the eReceipts toggle is nested inside the Rules feature (App/src/pages/workspace/rules/IndividualExpenseRulesSection.tsx:242-254), which requires a Control plan. Collect (Team) plan users are redirected to an upgrade page when they try to enable Rules (App/src/pages/workspace/WorkspaceMoreFeaturesPage.tsx:328-331), making the eReceipts toggle completely inaccessible.

Without Rules enabled, policy.eReceipts stays false/undefined, so the backend never sets hasEReceipt=true on card transactions. The frontend simply checks transaction.hasEReceipt (App/src/libs/TransactionUtils/index.ts:553-554) and renders nothing when it's falsy.

In Classic Expensify, eReceipts is a standalone expense setting available on all paid plans including Collect (App/docs/articles/expensify-classic/workspaces/Expense-Settings.md:50-57). The upgrade doc (App/docs/Hidden/collect-upgrade.md:54) confirms eReceipts are enabled by default on Collect — disabling them is listed as an advanced action that triggers a Control upgrade prompt.

This is a plan-gating mismatch between Classic and New Expensify: eReceipts went from a basic feature (all paid plans) to being locked behind a Control-only feature (Rules).

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

Make the eReceipts policy setting available to Collect (Team) plan workspaces without requiring the full Rules feature. Two approaches:

1. Preferred: When enabling Rules on a Collect plan triggers an upgrade redirect, still auto-enable policy.eReceipts for USD workspaces (similar to how App/src/libs/actions/Policy/Policy.ts:5421 does it for Control upgrades). This ensures parity with Classic behavior where eReceipts are on by default for all paid USD workspaces.

2. Alternative: Move the eReceipts toggle out of the Rules page into a section accessible to Collect plans (e.g., the main Expense Settings or More Features page), so Collect users can enable/disable it independently of Rules.

What alternative solutions did you explore? (Optional)

A backend-only fix (always setting hasEReceipt=true for USD card transactions regardless of policy.eReceipts) was considered but rejected because it would bypass the workspace-level toggle entirely, removing admin control over the feature.

Investigation details

Key code references:

• App/src/pages/workspace/WorkspaceMoreFeaturesPage.tsx:328-331 — Collect plan redirect when enabling Rules
• App/src/pages/workspace/rules/IndividualExpenseRulesSection.tsx:242-254 — eReceipts toggle (inside Rules page, Control-only)
• App/src/libs/actions/Policy/Policy.ts:5007-5012 — eReceipts auto-enabled only for Control + USD
• App/src/libs/actions/Policy/Policy.ts:5421 — Upgrade-to-Control auto-enables eReceipts for USD
• App/src/libs/TransactionUtils/index.ts:553-554 — hasEReceipt() check
• App/src/libs/ReceiptUtils.ts:58-63 — eReceipt display gating
• App/docs/articles/expensify-classic/workspaces/Expense-Settings.md:50-57 — Classic: eReceipts on all paid plans
• App/docs/Hidden/collect-upgrade.md:54 — Confirms eReceipts enabled by default on Collect in Classic

Data flow:

1. Backend checks policy.eReceipts when processing card transactions → sets hasEReceipt=true if enabled
2. Collect plans can't enable Rules → can't access eReceipts toggle → policy.eReceipts stays false
3. Frontend checks transaction.hasEReceipt → false → no eReceipt rendered
4. Classic Expensify has eReceipts as a standalone setting, enabled by default on all paid USD workspaces

---

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.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022042621694076641665

[Sado771]

Proposal
Problem
[Re-state the problem here in your own words. For example: "The app currently fails to maintain focus on the 'Add Expense' button after a user returns from the camera view on Android, causing a break in keyboard navigation flow."]

Root Cause
The root cause is located in [File path, e.g., src/pages/IOURequestStepAmount.tsx]. Specifically, at line [Line number], the [Function name] does not account for [Specific condition, e.g., the asynchronous nature of the navigation pop transition]. This leads to [The symptom, e.g., the focus being reset to the top of the container instead of the triggering element].

Proposed Changes
To resolve this, I will implement the following changes:

Modify [File Path]:

Update the useEffect hook to capture the reference of the triggering element using useRef.

Implement InteractionManager.runAfterInteractions to ensure the focus restoration occurs only after the screen transition animation is complete.

Update [Helper File, if applicable]:

In src/libs/Accessibility/index.ts, I will ensure the moveAccessibilityFocus utility is correctly handling the specific component type.

TypeScript

// Example of the logic to be implemented:
const buttonRef = useRef(null);

useEffect(() => {
    if (isFocused && !wasFocused) {
        InteractionManager.runAfterInteractions(() => {
            if (buttonRef.current) {
                buttonRef.current.focus();
            }
        });
    }
}, [isFocused]);

Alternative Solutions
I considered using autoFocus on the element, but rejected it because it would trigger every time the page mounts, even when not navigating back from the specific sub-flow, which would violate the general UX guidelines for other entry points.

[Ltbltbltbltb]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On Collect (Team) plan workspaces, card expenses show no eReceipt in New Expensify, even though Classic Expensify generates and displays the eReceipt for the same transaction.

What is the root cause of that problem?

The bug has two cascading points of failure, both in src/libs/ReceiptUtils.ts (getThumbnailAndImageURIs):

First failure — early exit on line 42:

if (!hasReceipt(transaction) && !receiptPath && !receiptFileName) {
    return {isEmptyReceipt: true};   // ← exits here for Collect card transactions
}

hasReceipt is defined as:

function hasReceipt(transaction) {
    return !!transaction?.receipt?.state || hasEReceipt(transaction);
}

hasEReceipt only checks !!transaction?.hasEReceipt. For Collect (Team) plan workspaces, the Expensify backend never sets hasEReceipt: true on the transaction (it only does so for Control/Corporate plans). Card expenses without a manually-uploaded receipt also have no receipt.state, so hasReceipt returns false, and the function exits with {isEmptyReceipt: true} before ever reaching the eReceipt route.

Second failure — line 58 reads the raw field:

const hasEReceipt = !hasReceiptSource(transaction) && transaction?.hasEReceipt;

Even if the early exit were bypassed, this line reads transaction?.hasEReceipt directly (not via the utility function), so it would still yield false for Collect plan managed card transactions.

Classic Expensify has its own rendering path that generates an eReceipt view client-side for any managed card transaction missing a physical receipt, regardless of the hasEReceipt flag — that is why Classic shows them but New Expensify does not.

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

Two minimal changes across two files.

1. Extend hasEReceipt in src/libs/TransactionUtils/index.ts to mirror Classic's logic:

// Before
function hasEReceipt(transaction: Transaction | undefined | null): boolean {
    return !!transaction?.hasEReceipt;
}

// After
function hasEReceipt(transaction: Transaction | undefined | null): boolean {
    return !!transaction?.hasEReceipt || isManagedCardTransaction(transaction);
}

isManagedCardTransaction is already defined in the same file (line 1343) and returns !!transaction?.managedCard. This fix automatically propagates through hasReceipt(), unblocking the early exit in ReceiptUtils.ts.

2. Replace the raw field read in src/libs/ReceiptUtils.ts with the utility function:

// Before — import
import {hasReceipt, hasReceiptSource, isFetchingWaypointsFromServer} from './TransactionUtils';

// After — import
import {hasEReceipt as transactionHasEReceipt, hasReceipt, hasReceiptSource, isFetchingWaypointsFromServer} from './TransactionUtils';

// Before — line 58
const hasEReceipt = !hasReceiptSource(transaction) && transaction?.hasEReceipt;

// After — line 58
const hasEReceipt = !hasReceiptSource(transaction) && transactionHasEReceipt(transaction);

With these two changes: (a) hasReceipt now returns true for managed card transactions, bypassing the {isEmptyReceipt: true} early exit; (b) line 58 uses the updated utility instead of the raw flag; (c) ReportActionItemImage.tsx:144 (const isEReceipt = ... && hasEReceipt(transaction)) already calls the utility, so it gets the fix for free. No other files need to change.

Contributor Details

Field	Value
Contributor email	lucastrba@gmail.com
Upwork Profile	https://www.upwork.com/freelancers/~01d016059c6701ebaa

[FraktalDeFiDAO]

Hi! I'd like to work on this issue. I have experience with React Native and expense reporting systems. Could you please assign it to me? I can have a fix ready within 24-48 hours.

[melvin-bot]

📣 @FraktalDeFiDAO! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>