[$250] Workspace - Account lists for credit card export appear on vendor bills

[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: v9.3.64-13
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-23133/folder/13176706/41236845/1372516412?sort=-identifier
Email or phone of affected tester (no customers): applausetester+ccardfeed@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 11 / Chrome, Samsung Galaxy A52 / Android 14, iPhone 13 / iOS 18.7.1
App Component: Workspace Settings

Action Performed:

Preconditions:

• Logged in to applausetester+ccardfeed@applause.expensifail.com
  Steps:

1. Navigate to the workspace "Company Cards tests - DO NOT DELETE!"
2. Go to Accounting and follow the steps to enable and connect to QBO using our QBO test account
3. Go back to Company cards
4. Click on an assigned card row
5. Click QuickBooks online credit card export row
6. Click a different account
7. Click QuickBooks online credit card export row again
8. Tap Default card
9. Click QuickBooks online credit card export row again
10. Tap the hyperlinked "export option" in the sub header of the list
11. Click Export company card expenses as row
12. Click Export as
13. Click debit card
14. Click < twice
15. Note its land to Quickbooks Online debit card export page and it shows the list of all the QBO debit card accounts
16. Click a different account
17. Click QuickBooks online debit card export row
18. Click the hyperlinked "export option" in the sub header
19. Click Export company card expenses as row
20. Click Export as
21. Click vendor bill
22. Click < twice

Expected Result:

User lands back on the card details page

Actual Result:

Account lists for credit card export appear on vendor bills

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @francoisl

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022049345552258303356
• Upwork Job ID: 2049345552258303356
• Last Price Increase: 2026-05-06

[MelvinBot]

Proposal

What is the root cause of that problem?

In companyCards/utils.tsx:69-82, the getExportMenuItem function has a fall-through switch where VENDOR_BILL falls through to the CREDIT_CARD case:

case CONST.QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.VENDOR_BILL:
case CONST.QUICKBOOKS_NON_REIMBURSABLE_EXPORT_ACCOUNT_TYPE.CREDIT_CARD: {
    data = creditCards ?? [];

This means when the export type is vendor bill, the function returns credit card accounts instead of accounts payable.

When the user changes the export type to vendor bill (via the "export option" hyperlink in the per-card flow) and then navigates back, they land on WorkspaceCompanyCardAccountSelectCardPage, which calls getExportMenuItem and displays whatever data it returns — with no guard against the vendor bill case. So credit card accounts are shown for vendor bills.

Note: the workspace-level account select page (DynamicQuickbooksCompanyCardExpenseAccountSelectPage) has a correct switch with separate cases and break statements, so this bug only affects the per-card flow.

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

1. In src/pages/workspace/companyCards/utils.tsx, break the fall-through by giving VENDOR_BILL its own case that sets data to accounts payable (from policy?.connections?.quickbooksOnline?.data?.accountPayable) instead of credit cards. The case should also set the appropriate exportType and selectedAccount for vendor bill.

2. In WorkspaceCompanyCardAccountSelectCardPage, add a guard: if exportMenuItem?.shouldShowMenuItem is false (which it is for vendor bill), navigate back to the card details page instead of rendering the account list. This prevents users from landing on this page via back-navigation when vendor bill is active.

Investigation details

Navigation flow that triggers the bug:

1. User is on the card details page, clicks "QBO credit card export row" → opens WorkspaceCompanyCardAccountSelectCardPage
2. Clicks the "export option" hyperlink in the subheader → navigates to workspace-level export settings
3. Changes export type to vendor bill
4. Clicks back twice → first back lands on DynamicQuickbooksCompanyCardExpenseAccountPage, second back lands on WorkspaceCompanyCardAccountSelectCardPage (still in the nav stack)
5. getExportMenuItem is called with vendor bill active → fall-through returns creditCards data

Why shouldShowMenuItem doesn't prevent this:
Line 63 sets shouldShowMenuItem = false for vendor bill, which hides the menu on the card details page. But WorkspaceCompanyCardAccountSelectCardPage (line 47-59) doesn't check shouldShowMenuItem — it renders whatever exportMenuItem?.data contains.

Also noted: DynamicQuickbooksCompanyCardExpenseAccountSelectPage line 46 uses CONST.QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.VENDOR_BILL instead of CONST.QUICKBOOKS_NON_REIMBURSABLE_EXPORT_ACCOUNT_TYPE.VENDOR_BILL. Both resolve to 'bill' so it works, but using the non-reimbursable constant would be more correct since this is the non-reimbursable export config.

---

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.

[MobileMage]

Proposal

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

When a user selects "Vendor bill" as the export type for company card expenses in QBO settings and then taps the account row, the account selection screen incorrectly shows credit card or debit card accounts instead of (or in addition to) the accounts payable list appropriate for vendor bills.

What is the root cause of that problem?

In DynamicQuickbooksCompanyCardExpenseAccountPage.tsx, the sections array is built unconditionally — the second row (account select) is always rendered regardless of the current nonReimbursableExpensesExportDestination. When the user selects "Vendor bill" and then navigates back to the account detail page, the second MenuItemWithTopDescription row still appears and pressing it opens DynamicQuickbooksCompanyCardExpenseAccountSelectPage. That page reads qboConfig?.nonReimbursableExpensesExportDestination to determine which account list to render; however, because updateManyPolicyConnectionConfigs applies an optimistic update and the Onyx value may not have fully propagated by the time the user navigates back, the switch statement can still resolve to the previous type (e.g. credit_card or debit_card) and render those accounts.

Additionally, vendor bills conceptually do not require a standalone "account" picker in this row — the accounts payable account for vendor bills is a separate concept already surfaced through the AP account field — so the second section row should be hidden when the destination is VENDOR_BILL, matching how the non-dynamic export configuration page (DynamicQuickbooksExportConfigurationPage.tsx) omits a separate account row for vendor bills.

App/src/pages/workspace/accounting/qbo/export/DynamicQuickbooksCompanyCardExpenseAccountPage.tsx

Lines 33 to 51 in d91ed96

	const sections = [
	{
	title: qboConfig?.nonReimbursableExpensesExportDestination ? translate(`workspace.qbo.accounts.${qboConfig?.nonReimbursableExpensesExportDestination}`) : undefined,
	description: translate('workspace.accounting.exportAs'),
	onPress: () => Navigation.navigate(createDynamicRoute(DYNAMIC_ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_COMPANY_CARD_EXPENSE_CARD_SELECT.path)),
	hintText: qboConfig?.nonReimbursableExpensesExportDestination ? translate(`workspace.qbo.accounts.${qboConfig?.nonReimbursableExpensesExportDestination}Description`) : undefined,
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.NON_REIMBURSABLE_EXPENSE_EXPORT_DESTINATION],
	},
	{
	title: qboConfig?.nonReimbursableExpensesAccount?.name,
	description: getQBONonReimbursableExportAccountType(translate, qboConfig?.nonReimbursableExpensesExportDestination),
	onPress: () => {
	if (!policyID) {
	return;
	}
	Navigation.navigate(createDynamicRoute(DYNAMIC_ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_COMPANY_CARD_EXPENSE_ACCOUNT_SELECT.path));
	},
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.NON_REIMBURSABLE_EXPENSE_ACCOUNT],
	},

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

In DynamicQuickbooksCompanyCardExpenseAccountPage.tsx, the sections array should conditionally exclude the account-select row when nonReimbursableExpensesExportDestination is CONST.QUICKBOOKS_NON_REIMBURSABLE_EXPORT_ACCOUNT_TYPE.VENDOR_BILL. Filter the second section out (or guard its construction) so it is only included when the destination is credit_card or debit_card. This prevents the account picker row from appearing at all for vendor bills, which eliminates the navigation path to the mismatched account list. The vendor bill accounts payable information is already handled by the separate Accordion section below (the default vendor toggle), so nothing is lost by omitting the account row for that export type.

App/src/pages/workspace/accounting/qbo/export/DynamicQuickbooksCompanyCardExpenseAccountPage.tsx

Lines 33 to 51 in d91ed96

	const sections = [
	{
	title: qboConfig?.nonReimbursableExpensesExportDestination ? translate(`workspace.qbo.accounts.${qboConfig?.nonReimbursableExpensesExportDestination}`) : undefined,
	description: translate('workspace.accounting.exportAs'),
	onPress: () => Navigation.navigate(createDynamicRoute(DYNAMIC_ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_COMPANY_CARD_EXPENSE_CARD_SELECT.path)),
	hintText: qboConfig?.nonReimbursableExpensesExportDestination ? translate(`workspace.qbo.accounts.${qboConfig?.nonReimbursableExpensesExportDestination}Description`) : undefined,
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.NON_REIMBURSABLE_EXPENSE_EXPORT_DESTINATION],
	},
	{
	title: qboConfig?.nonReimbursableExpensesAccount?.name,
	description: getQBONonReimbursableExportAccountType(translate, qboConfig?.nonReimbursableExpensesExportDestination),
	onPress: () => {
	if (!policyID) {
	return;
	}
	Navigation.navigate(createDynamicRoute(DYNAMIC_ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_COMPANY_CARD_EXPENSE_ACCOUNT_SELECT.path));
	},
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.NON_REIMBURSABLE_EXPENSE_ACCOUNT],
	},

What alternative solutions did you explore? (Optional)

N/A

[melvin-bot]

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

[melvin-bot]

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

[KJ21-ENG]

Proposal

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

On a workspace connected to QuickBooks Online, after assigning a company card and configuring per-card export, the user goes through this flow:

1. Set the card export to a debit-card account, then change the policy-level QBO non-reimbursable export destination to Vendor bill via the "export option" hyperlink in the per-card account-selection page.
2. Tap < twice.

Expected: land on the company card details page (as in step 14–15, the credit-card → debit-card transition behaves correctly).
Actual: land on the per-card account-selection page rendered with the credit-card account list while the page is now operating under a vendor-bill export destination.

The attached video confirms the symptom: the final screen sits at /workspaces/<id>/company-cards/<feed>/<cardID>/edit/export, the header reads "QuickBooks Online vendor bill export" and the description starts "Choose the QuickBooks Online vendor bill export account…", but the rendered list is the credit-card accounts ("Credit Card CAD", "Expensify Card Liability Account", "Giphy 1711", "Testing Credit Card", "Training - Credit Card - CC"). Repros on Web, Android, and iOS.

What is the root cause of that problem?

Two independent defects collaborate to produce the symptom.

Defect 1 — getExportMenuItem collapses QBO vendor_bill into the credit-card branch.

In src/pages/workspace/companyCards/utils.tsx, the QBO branch picks the data list via:

const qboConfig = nonReimbursableExpensesExportDestination ?? reimbursableExpensesExportDestination;

The first switch arm groups four cases together — QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.JOURNAL_ENTRY, …CHECK, …VENDOR_BILL, and QUICKBOOKS_NON_REIMBURSABLE_EXPORT_ACCOUNT_TYPE.CREDIT_CARD — and unconditionally loads creditCards data with the quickbooks_online_export_account NVP key.

The constants QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.VENDOR_BILL and QUICKBOOKS_NON_REIMBURSABLE_EXPORT_ACCOUNT_TYPE.VENDOR_BILL both resolve to the string 'bill' (src/CONST/index.ts lines 2773–2776 and 3093–3097). So when the policy's non-reimbursable destination is bill, the switch matches the reimbursable VENDOR_BILL case and returns data = creditCards. That is why the vendor-bill-titled page in the video renders the credit-card account list. Note that line 63 already sets shouldShowMenuItem = nonReimbursableExpensesExportDestination !== VENDOR_BILL — i.e. the function intends per-card export to be hidden under vendor bill — but the switch body still produces a populated credit-card list, ignoring that intent.

Defect 2 — WorkspaceCompanyCardAccountSelectCardPage does not handle a stale-stack re-entry when shouldShowMenuItem becomes false.

src/pages/workspace/companyCards/WorkspaceCompanyCardAccountSelectCardPage.tsx reads exportMenuItem via getExportMenuItem(...) and renders the list unconditionally. When the user changes the export destination to vendor bill via the hyperlinked sub-header (step 10/18), the older instance of this screen is still on the stack pointed at the same (policyID, cardID, feed). After < <, that stale instance re-renders with the new policy state, where exportMenuItem.shouldShowMenuItem === false and exportMenuItem.exportType is undefined for vendor bill. Nothing in the screen redirects, so it stays mounted and renders whatever data Defect 1 produced — exactly the page the user lands on at the end of the attached video.

The user-visible symptom requires both defects: Defect 1 supplies a wrong-but-non-empty list, and Defect 2 keeps the stale screen mounted when policy state has invalidated it. Fixing only Defect 1 leaves an empty list on the wrong screen; fixing only Defect 2 still leaves the credit-card list visible during the brief window before redirect, and leaves the same wrong list reachable through any other deep-link or back-stack path.

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

1. In src/pages/workspace/companyCards/utils.tsx, split QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.VENDOR_BILL out of the credit-card switch arm in the QBO branch. Treat 'bill' (when sourced from nonReimbursableExpensesExportDestination) as a default-equivalent case: return shouldShowMenuItem: false, data: [], exportType: undefined. This matches the existing intent of line 63 and aligns with how the card-details page already hides the menu row.
2. In src/pages/workspace/companyCards/WorkspaceCompanyCardAccountSelectCardPage.tsx, after computing exportMenuItem, if exportMenuItem?.shouldShowMenuItem === false or exportMenuItem?.exportType is undefined, call Navigation.goBack(ROUTES.WORKSPACE_COMPANY_CARD_DETAILS.getRoute(policyID, feed, cardID, backTo)) from a useEffect (or equivalent focus effect) so a stale-stack instance reconciles with the new policy state and redirects to the card details page — matching the expected behavior in the bug report.
3. No backend or API change is needed; the policy-level nonReimbursableExpensesExportDestination is already the source of truth and is read correctly.

Scope boundaries:

• Files touched: src/pages/workspace/companyCards/utils.tsx, src/pages/workspace/companyCards/WorkspaceCompanyCardAccountSelectCardPage.tsx.
• Platforms affected: Web, Android, iOS, MacOS (the shared per-card export selection screen). No platform-specific code paths are forked.
• Explicitly NOT touched: the Xero, NetSuite, Sage Intacct, and QBD branches of getExportMenuItem; the policy-level QBO export config screens (DynamicQuickbooksCompanyCardExpenseAccountPage, DynamicQuickbooksCompanyCardExpenseAccountSelectPage); setCompanyCardExportAccount and the SetCompanyCardExportAccount API parameters; WorkspaceCompanyCardDetailsPage rendering (it already correctly hides the menu row when shouldShowMenuItem is false).
• API contracts / backend behavior: unchanged.

What alternative solutions did you explore? (Optional)

• Defect-1-only fix. Only split out VENDOR_BILL from the credit-card switch arm in utils.tsx. Rejected as the sole fix because the stale screen would still render an empty list on the wrong-titled page, and the stale exportType could still mis-route a row tap through setCompanyCardExportAccount.
• Defect-2-only fix (full redirect on every render). Redirect from WorkspaceCompanyCardAccountSelectCardPage whenever shouldShowMenuItem is false. Rejected as the sole fix because the screen would still flash the credit-card list for one render cycle before navigating away, and any non-stack entry path (deep link, refresh) would briefly show the wrong list.
• MelvinBot's bot proposal — point VENDOR_BILL at accountPayable data. The bot suggests giving VENDOR_BILL its own case in utils.tsx that loads policy?.connections?.quickbooksOnline?.data?.accountPayable (which does exist on the QBO data type, src/types/onyx/Policy.ts:425) instead of an empty list, so a per-card vendor-bill account picker is materialized. The bot's diagnosis of Defect 1 (the fall-through) and the observation that the workspace-level DynamicQuickbooksCompanyCardExpenseAccountSelectPage correctly uses separate cases with break statements are both correct and align with our root-cause section. The divergence is on the fix shape: introducing a per-card vendor-bill picker is a feature addition that contradicts the existing code's intent — WorkspaceCompanyCardDetailsPage already hides the export menu row entirely when non-reimbursable is vendor_bill (shouldShowMenuItem set on line 63 of utils.tsx), so the design is "no per-card override under vendor bill" rather than "different per-card picker". The minimal fix matching that intent is to honor it on both ends (utils.tsx + the select page redirect), which is what this proposal does.
• Block navigation at the hyperlink source. Disable the "export option" hyperlink (step 10/18) when toggling away would invalidate the parent screen. Rejected because the policy-level export destination is a legitimate user setting and users should be free to change it; the per-card screen should react correctly, not the policy screen restrict.
• Server-side guard. Reject the per-card NVP write when the policy export destination is bill. Rejected as out-of-scope and unnecessary — the client already has the information needed to suppress the screen, and shouldShowMenuItem already encodes that intent.

[aswin-s]

🚨 Edited by proposal-police: This proposal was edited at 2026-04-29 05:20:47 UTC.

Proposal

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

When a user opens the workspace company-card per-card export selector, changes the workspace export destination to Vendor bill from the link inside that screen, and returns, the screen can still show a per-card account list even though Vendor bill should not allow per-card account mapping at all.

This is not only a QBO data issue inside the selector list. It is a shared workspace company-card flow problem: the helper that builds the menu item returns Vendor bill as if it were a credit-card path, and the selector page itself does not honor the helper’s shouldShowMenuItem flag once the route is already open.

What is the root cause of that problem?

The root cause is in src/pages/workspace/companyCards/utils.tsx, inside getExportMenuItem().

In the QBO branch:

• qboConfig is resolved from nonReimbursableExpensesExportDestination ?? reimbursableExpensesExportDestination, but shouldShowMenuItem is still computed only from nonReimbursableExpensesExportDestination.
• CONST.QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.VENDOR_BILL is still grouped into the credit-card switch branch, so when the resolved config is 'bill', the helper returns creditCards data and NVP_QUICKBOOKS_ONLINE_EXPORT_ACCOUNT instead of hiding the per-card selector.

The QBD branch has the same bug pattern:

• qbdConfig is resolved from exportQBD.nonReimbursable ?? exportQBD.reimbursable, but shouldShowMenuItem is still based only on exportQBD.nonReimbursable.
• CONST.QUICKBOOKS_DESKTOP_REIMBURSABLE_ACCOUNT_TYPE.VENDOR_BILL is still grouped into the creditCardAccounts branch, so Vendor bill is treated like a per-card credit-card export there too.

There is a second bug in src/pages/workspace/companyCards/WorkspaceCompanyCardAccountSelectCardPage.tsx:

• the page always renders SelectionScreen from exportMenuItem.data and never checks exportMenuItem.shouldShowMenuItem.
• WorkspaceCompanyCardDetailsPage already respects shouldShowMenuItem, but the selector page does not, so once the user is already on this route it can keep rendering an invalid screen state.

A working analog exists in the dedicated accounting pages:

• src/pages/workspace/accounting/qbo/export/DynamicQuickbooksCompanyCardExpenseAccountSelectPage.tsx treats Vendor bill as the payable-account path, not a credit-card path.
• src/pages/workspace/accounting/utils.tsx in getQBDReimbursableAccounts() maps QBD Vendor bill to payableAccounts, not creditCardAccounts.

That shows the shared company-card helper is the outlier.

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

1. src/pages/workspace/companyCards/utils.tsx — in both the QBO and QBD branches of getExportMenuItem(), compute shouldShowMenuItem from the resolved export mode (qboConfig / qbdConfig), not only from the non-reimbursable config field.
2. src/pages/workspace/companyCards/utils.tsx — remove Vendor bill from the credit-card switch fallthroughs in both branches so Vendor bill reaches the hidden/default path instead of returning creditCards / creditCardAccounts data.
3. src/pages/workspace/companyCards/WorkspaceCompanyCardAccountSelectCardPage.tsx — honor exportMenuItem.shouldShowMenuItem. If the export mode changes to Vendor bill while the page is open, the page should stop rendering the selector and return to the card-details route (or otherwise suppress the invalid selection screen) instead of showing stale or empty selector UI.
4. tests/unit/CompanyCardExportTest.ts — add coverage for QBO Vendor bill and QBD Vendor bill so the helper is required to return shouldShowMenuItem: false and no per-card export options for those modes.

What alternative solutions did you explore? (Optional)

Only fixing WorkspaceCompanyCardAccountSelectCardPage was not sufficient, because getExportMenuItem() would still incorrectly classify Vendor bill as a credit-card export mode for shared callers.

Only fixing getExportMenuItem() was also incomplete, because the selector page currently ignores shouldShowMenuItem, so a user who is already on that route can still remain on an invalid screen after the export destination changes.

[aswin-s]

Updated my proposal — QBD branch has the same Vendor bill fall-through bug as QBO, and added a suggestion to add unit test coverage for both.

[ryntgh]

🚨 Edited by proposal-police: This proposal was edited at 2026-05-12 14:40:03 UTC.

Proposal

What is the root cause of that problem?

In QBO company card flow, the export link is built with a base path that can drop the company card route context, which can produce an incorrect/duplicated dynamic QBO export route chain

App/src/pages/workspace/companyCards/utils.tsx

Line 109 in 9592e88

exportPageLink: createDynamicRoute(DYNAMIC_ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_EXPORT.path, basePath),

Then in DynamicQuickbooksExportConfigurationPage, back navigation relies on goBackFromExportConnection, but the page was not passing dynamicBackPath into that helper. In this case backTo was also return undefined, so the helper can fall back to regular back behavior instead of going to card details in vendor-bill mode

App/src/pages/workspace/accounting/qbo/export/DynamicQuickbooksExportConfigurationPage.tsx

Lines 51 to 53 in 9592e88

	const goBack = useCallback(() => {
	return goBackFromExportConnection(shouldShowVendorMenuItems, backTo);
	}, [backTo, shouldShowVendorMenuItems]);

App/src/libs/Navigation/helpers/goBackFromExportConnection.ts

Lines 10 to 20 in 9592e88

	function goBackFromExportConnection(shouldGoBackToSpecificRoute: boolean, backTo?: string, dynamicBackPath?: Route) {
	const feature = CONST.UPGRADE_FEATURE_INTRO_MAPPING.companyCards;
	const effectivePath = dynamicBackPath ?? backTo;
	// TODO: Remove `backTo` fallback once all routes using this helper are migrated to dynamic back paths.
	if (!(shouldGoBackToSpecificRoute && effectivePath?.includes(feature.alias))) {
	return Navigation.goBack(dynamicBackPath);
	}
	const companyCardDetailsPage = replaceCompanyCardsRoute(effectivePath);
	return Navigation.goBack(companyCardDetailsPage, {compareParams: false});
	}

After that, user can land on company-card account selection where vendor-bill flow still shows the credit-card account list branch

App/src/pages/workspace/companyCards/utils.tsx

Lines 69 to 75 in 9592e88

	const qboConfig = nonReimbursableExpensesExportDestination ?? reimbursableExpensesExportDestination;
	switch (qboConfig) {
	case CONST.QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.JOURNAL_ENTRY:
	case CONST.QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.CHECK:
	case CONST.QUICKBOOKS_REIMBURSABLE_ACCOUNT_TYPE.VENDOR_BILL:
	case CONST.QUICKBOOKS_NON_REIMBURSABLE_EXPORT_ACCOUNT_TYPE.CREDIT_CARD: {
	data = creditCards ?? [];

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

We need to update QBO export link generation to keep company card context when available using backTo

                exportPageLink: createDynamicRoute(DYNAMIC_ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_EXPORT.path, backTo ?? basePath),

App/src/pages/workspace/companyCards/utils.tsx

Line 109 in 9592e88

exportPageLink: createDynamicRoute(DYNAMIC_ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_EXPORT.path, basePath),

Then use useDynamicBackPath in DynamicQuickbooksExportConfigurationPage and pass it to goBackFromExportConnection

    const dynamicBackPath = useDynamicBackPath(DYNAMIC_ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_EXPORT.path);
    const goBack = useCallback(() => {
        return goBackFromExportConnection(shouldShowVendorMenuItems, backTo, dynamicBackPath);
    }, [backTo, dynamicBackPath, shouldShowVendorMenuItems]);

App/src/pages/workspace/accounting/qbo/export/DynamicQuickbooksExportConfigurationPage.tsx

Lines 51 to 53 in 9592e88

	const goBack = useCallback(() => {
	return goBackFromExportConnection(shouldShowVendorMenuItems, backTo);
	}, [backTo, shouldShowVendorMenuItems]);

What alternative solutions did you explore? (Optional)

N/A

Test Branch