[Due for payment 2026-04-20]ND, Expensify Feed shows "Deleted Feed" when trying to view "Unapproved Card" or "Reconciliation: Expensify Card groupby:card"

[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: 9.3.19-5
Reproducible in staging?: (Needs Reproduction) Transactions deleted when deleting card feed
Reproducible in production?: 9Needs 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: @abbagail
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Go to Reports > Accounting > Unapproved Card, or Reports > Accounting > Reconciliation (and update to Expensify Card, groupby:card)
2. See expenses that fall into that range
3. Feed column shows: "Deleted Feed."

Expected Result:

See "Expensify Card" or even "Expensify Card:workspace"

Actual Result:

"Deleted Feed" (This implies from help sources and AZ that the feed/connection is deactivated or removed and will no longer update. this is not accurate for Active Expensify Cards.)

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 video for the issue is in Slack thread

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[MelvinBot]

Proposal

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

In Reports > Accounting > Unapproved Card (or Reconciliation with Expensify Card groupby:card), the Feed column shows "Deleted Feed" for active Expensify Card transactions. This incorrectly implies the card feed has been deactivated or removed, when in fact the Expensify Card is active.

What is the root cause of that problem?

The root cause is that doesCardFeedExist() always returns false for Expensify Card transactions because the underlying getOriginalCompanyFeeds() function explicitly filters out the Expensify Card feed.

Here is the full chain:

1. SearchUIUtils.ts:1604 computes isCardFeedDeleted for each transaction:

   const isCardFeedDeleted = cardFeeds === undefined
       ? undefined
       : !doesCardFeedExist(transactionItem.bank as OnyxTypes.CompanyCardFeed, cardFeeds);

   For Expensify Card transactions, transactionItem.bank is 'Expensify Card' (CONST.EXPENSIFY_CARD.BANK, defined at CONST/index.ts:3634).

2. doesCardFeedExist() (CardUtils.ts:633-646) iterates over all card feeds and for each calls getOriginalCompanyFeeds(), then checks if the feed name exists in the result.

3. getOriginalCompanyFeeds() (CardUtils.ts:516-517) explicitly filters OUT the Expensify Card:

   if (key === CONST.EXPENSIFY_CARD.BANK) {
       return false;
   }

4. Since 'Expensify Card' is always excluded from company feeds, doesCardFeedExist returns false, setting isCardFeedDeleted = true.

5. TransactionItemRow/index.tsx:258-259 renders "Deleted feed" when isCardFeedDeleted is true, short-circuiting before checking the actual card name.

Additionally, 'Expensify Card' is not a valid CompanyCardFeed type value — CompanyCardFeed (CardFeeds.ts:8) is ValueOf<typeof CONST.COMPANY_CARD.FEED_BANK_NAME>, which only includes third-party feeds ('cdf', 'vcf', 'gl1025', 'stripe', etc.). The as CompanyCardFeed cast at SearchUIUtils.ts:1604 hides this type mismatch.

The same bug also affects the grouped-by-card view via getFeedNameForDisplay() (CardUtils.ts:670-691) which also calls doesCardFeedExist — see SearchUIUtils.ts:2330.

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

In SearchUIUtils.ts:1604, skip the doesCardFeedExist check when the transaction's bank is CONST.EXPENSIFY_CARD.BANK. Expensify Card is not a "company card feed" — it's Expensify's own card product managed through a separate data path. It should never be considered a "deleted feed."

The fix should set isCardFeedDeleted = false (not deleted) when transactionItem.bank === CONST.EXPENSIFY_CARD.BANK, and only call doesCardFeedExist for actual third-party company card feeds.

The same pattern should be applied in getCardSections (SearchUIUtils.ts:2330) where getFeedNameForDisplay is called for the grouped card view — either by adding the same guard, or by updating doesCardFeedExist / getFeedNameForDisplay to recognize Expensify Card feeds as always existing.

What alternative solutions did you explore? (Optional)

• Removing the EXPENSIFY_CARD.BANK filter from getOriginalCompanyFeeds: This would be risky because that function is used broadly across the codebase for company card feed management, where excluding the Expensify Card feed is intentional (it's a different data model).
• Modifying doesCardFeedExist to special-case Expensify Card: Possible but less clean — doesCardFeedExist is specifically about company card feeds, and mixing in Expensify Card awareness would blur that abstraction.
• Handling it in TransactionItemRow: Too late in the data flow — the isCardFeedDeleted flag is already set incorrectly by that point.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.

[HiepPP]

Proposal

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

The Feed column displays "Deleted feed" for active Expensify Card transactions when viewing Reports > Accounting > Unapproved Card or Reconciliation with group-by:card enabled.

What is the root cause of that problem?

The doesCardFeedExist() function incorrectly uses getOriginalCompanyFeeds() to validate feed existence. This function explicitly filters out CONST.EXPENSIFY_CARD.BANK because it was designed for feed selection UI where Expensify Cards are excluded.

App/src/libs/CardUtils.ts

Lines 516 to 517 in 8ff17a6

	if (key === CONST.EXPENSIFY_CARD.BANK) {
	return false;

When getFeedNameForDisplay() calls doesCardFeedExist(), Expensify Card feeds fail the existence check and return "Deleted feed" instead of "Expensify Card".

App/src/libs/CardUtils.ts

Lines 682 to 685 in 8ff17a6

	const feedExists = doesCardFeedExist(feed, cardFeeds);
	if (!feedExists) {
	return translate('workspace.companyCards.deletedFeed');

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

Add special case handling for Expensify Cards in two locations:

1. In src/libs/CardUtils.ts, add an early return in getFeedNameForDisplay() before the doesCardFeedExist() check:

// Expensify Card is a built-in feed that always exists, bypass the existence check
if (feed === CONST.EXPENSIFY_CARD.BANK) {
  return translate("common.expensifyCard");
}

2. In src/libs/SearchUIUtils.ts, update the isCardFeedDeleted calculation to handle Expensify Cards:

// Expensify Card is a built-in feed that always exists, so it's never considered deleted.
let isCardFeedDeleted: boolean | undefined;
if (cardFeeds === undefined) {
  isCardFeedDeleted = undefined;
} else if (transactionItem.bank === CONST.EXPENSIFY_CARD.BANK) {
  isCardFeedDeleted = false;
} else {
  isCardFeedDeleted = !doesCardFeedExist(
    transactionItem.bank as OnyxTypes.CompanyCardFeed,
    cardFeeds,
  );
}

These changes bypass the flawed existence check for Expensify Cards since they are built-in feeds that always exist.

What alternative solutions did you explore? (Optional)

Considered modifying doesCardFeedExist() to return true for Expensify Cards, but this would change the semantics of "company card feed existence" in all contexts. The special case approach is more localized and aligns with how other display functions handle Expensify Cards.

---

Files Modified:

• src/libs/CardUtils.ts - Added special case for Expensify Card in getFeedNameForDisplay()
• src/libs/SearchUIUtils.ts - Added special case for Expensify Card in isCardFeedDeleted calculation

Testing Performed:

• Reproduced the issue
• Applied the fix
• Verified the fix resolves the issue
• Checked for edge cases
• ESLint passes for modified files
• Prettier formatting passes

[github-actions]

⚠️ @HiepPP Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.