Company Cards - Transactions import as reimbursable despite feed reimbursable setting being "Force no" (regression since Oct 21)

@Liz-Canary

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

Version Number:
Reproducible in staging?: Needs Reproduction
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: @Liz-Canary
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

In Old Dot (Classic), confirm the company card feed's reimbursable setting is set to "Force no."
Import/sync card transactions for this feed in New Expensify.
Check the reimbursable status of newly imported transactions.
Compare against transactions imported before Oct 21.

Expected Result:

All transactions from this card feed should import as non-reimbursable, per the feed's "Force no" setting — consistent with how imports behaved through Oct 20.

Actual Result:

Starting Oct 21, every transaction imported from this card comes in as reimbursable, despite the feed's reimbursable setting still being "Force no" in Old Dot. Imports through Oct 20 were correctly non-reimbursable.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

Screenshots/Videos

The screenshot, affected account and Melvin's analysis in Slack thread

View all open jobs on GitHub

⚠️ Preliminary analysis (low confidence) — treat as a starting point, not a conclusion.

This appears to be a backend/internal issue. A separate internal investigation is needed.

The App does not decide whether an imported card transaction is reimbursable. The backend sets that value during import, so the fix is outside the App repo. Please escalate to an internal engineer.

What I checked in the App

No App code reads or writes a card feed's reimbursable setting. forceReimbursable appears only as a type field at src/types/onyx/CardFeeds.ts:85.
The related App PRs are not merged, so they can't be the cause:
- Add Reimbursable setting to company card feeds (open)
- Show the Reimbursable toggle on Do Not Force company card expenses (open)
One App change merged on Oct 21, but it only affects display: Enforce the cash-expense reimbursable rule when defaultReimbursable is absent. It now shows the "· Reimbursable" / "· Non-reimbursable" label for every expense on a report, not only single-expense reports (MoneyRequestView.tsx:806-810). The label reads the stored value, so it doesn't invent "Reimbursable". But it may have made existing reimbursable card expenses visible starting Oct 21.

To confirm: compare the stored reimbursable value of a card transaction imported on Oct 20 with one imported on or after Oct 21 from the same feed. If both are stored as reimbursable, the Oct 21 date reflects the new label, not a change in import behavior.

Next Steps: Reply with @MelvinBot <your feedback> to refine this analysis.

view run

Working on this on the internal issue: #105127

All PRs are deployed, we should be good

Navigation Menu

Repository navigation

Company Cards - Transactions import as reimbursable despite feed reimbursable setting being "Force no" (regression since Oct 21) #105127

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Company Cards - Transactions import as reimbursable despite feed reimbursable setting being "Force no" (regression since Oct 21) #105127

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Activity

MelvinBot commented on Oct 27, 2026

madmax330 commented on Oct 28, 2026

madmax330 commented on Nov 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions