[Due for payment 2026-07-21] [$250] Unable to import QuickBooks Online Items in New Expensify

[m-natarajan]

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

---

Version Number: v9.4.15-3
Reproducible in staging?: Y
Reproducible in production?: Y
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:

1. Connect a workspace to QuickBooks Online.
2. Navigate to the accounting integration settings in New Expensify.
3. Review the available coding/import options.

Expected Result:

A Coding option should be available, allowing admins to import Items from QuickBooks Online, similar to the functionality available in Classic.

Actual Result:

There is no option in New Expensify to import QuickBooks Online Items. The Coding/Item import functionality available in Classic is not present.

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

Recording.3051.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022067977545780823362
• Upwork Job ID: 2067977545780823362
• Last Price Increase: 2026-06-19

Issue Owner

Current Issue Owner: @mallenexpensify

[MelvinBot]

Proposal

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

New Expensify has no option to import Items from a QuickBooks Online (QBO) connection, even though Classic Expensify supports it. The QBO accounting import menu only exposes Accounts, Classes, Customers, Locations, and Taxes.

What is the root cause of that problem?

This is a feature-parity gap, not a regression — QBO Items import was never built in New Expensify.

The plumbing is only half-stubbed: the QBO config type already declares the field but nothing reads, writes, or surfaces it.

• src/types/onyx/Policy.ts:506-507 — syncItems: boolean; is present but explicitly marked /** TODO: Will be handled in another issue */.
• There is no SYNC_ITEMS key in QUICKBOOKS_CONFIG, no Items page, no route/screen, no menu entry, and no updateQuickbooksOnlineSyncItems action or UPDATE_QUICKBOOKS_ONLINE_SYNC_ITEMS write command.

By contrast, QuickBooks Desktop already ships this exact feature (boolean toggle), which is the pattern to mirror.

Evidence — QBD has it, QBO doesn't

• QBD Items toggle page: QuickbooksDesktopItemsPage.tsx — a single ToggleSettingOptionRow bound to qbdConfig.importItems, calling QuickbooksDesktop.updateQuickbooksDesktopSyncItems.
• QBD menu entry exists in QuickbooksDesktopImportPage.tsx; the QBO sections array in QuickbooksImportPage.tsx has no Items entry.
• CONST: QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS exists; QUICKBOOKS_CONFIG has SYNC_CLASSES/SYNC_CUSTOMERS/SYNC_LOCATIONS/SYNC_TAX/SYNC_PEOPLE but no items key (CONST/index.ts).
• Write commands: UPDATE_QUICKBOOKS_DESKTOP_SYNC_ITEMS exists in API/types.ts; there is no UPDATE_QUICKBOOKS_ONLINE_SYNC_ITEMS.

⚠️ This requires backend work outside the App repo

The App frontend changes (below) are necessary but not sufficient. A QBO toggle is a no-op until the backend (Web-Expensify/Auth) provides an UpdateQuickbooksOnlineSyncItems command and the QBO sync actually pulls Items from QuickBooks Online into the connection config. An internal engineer with access to those repos must confirm/build the backend piece and clarify how Classic imports QBO Items (as a boolean toggle like QBD, or as a mapped entity with a "displayed as" sub-page like Classes/Customers). That answer determines the exact frontend shape.

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

App-side scaffolding, mirroring QBD Items (assuming the boolean-toggle model is confirmed by the backend behavior):

1. Add SYNC_ITEMS: 'syncItems' to QUICKBOOKS_CONFIG in CONST/index.ts.
2. New QuickbooksItemsPage.tsx under qbo/import/ — a toggle on qboConfig.syncItems calling a new updateQuickbooksOnlineSyncItems action.
3. Add the Items entry to the QBO sections array in QuickbooksImportPage.tsx.
4. New updateQuickbooksOnlineSyncItems in libs/actions/connections/QuickbooksOnline.ts + UPDATE_QUICKBOOKS_ONLINE_SYNC_ITEMS write command in API/types.ts.
5. Add route/screen wiring: ROUTES.ts, SCREENS.ts, Navigation/types.ts, ModalStackNavigators/index.tsx, WORKSPACE_TO_RHP.ts, linkingConfig/config.ts.
6. Add qbo.items translations in en.ts and es.ts.

What alternative solutions did you explore? (Optional)

N/A

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/94055) to create a draft PR — but note the App-side toggle won't function until the backend command exists, so backend coordination should come first.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[MobileMage]

Proposal

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

New Expensify's QuickBooks Online (QBO) accounting integration does not expose a "coding" option to import QBO Items, even though Expensify Classic does. When an admin opens the QBO import menu, they see Accounts, Classes, Customers, Locations, and (non-US) Taxes — but there is no Items row, so QBO Items can never be brought into Expensify from NewDot.

What is the root cause of that problem?

The QBO import menu is built from a static sections array in QuickbooksImportPage, and that array simply has no entry for Items. It only renders Accounts, Classes, Customers, Locations, and conditionally Taxes:

App/src/pages/workspace/accounting/qbo/import/QuickbooksImportPage.tsx

Lines 38 to 63 in c6a9edb

	const sections: QBOSectionType[] = [
	{
	description: translate('workspace.accounting.accounts'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CHART_OF_ACCOUNTS.getRoute(policyID)),
	title: translate('workspace.accounting.importAsCategory'),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.ENABLE_NEW_CATEGORIES],
	},
	{
	description: translate('workspace.qbo.classes'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CLASSES.getRoute(policyID)),
	title: translate(`workspace.accounting.importTypes.${syncClasses ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_CLASSES],
	},
	{
	description: translate('workspace.qbo.customers'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CUSTOMERS.getRoute(policyID)),
	title: translate(`workspace.accounting.importTypes.${syncCustomers ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_CUSTOMERS],
	},
	{
	description: translate('workspace.qbo.locations'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_LOCATIONS.getRoute(policyID)),
	title: translate(`workspace.accounting.importTypes.${syncLocations ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_LOCATIONS],
	},
	];

This is a missing-wiring gap, not a broken condition. Interestingly, the QBO config type already declares the field — syncItems: boolean is defined on QBOConnectionConfig in src/types/onyx/Policy.ts#L507 — but a grep across src/pages/workspace/accounting/qbo and src/libs/actions/connections/QuickbooksOnline.ts shows syncItems is never read or written anywhere on the App side. There is no SYNC_ITEMS/IMPORT_ITEMS key in CONST.QUICKBOOKS_CONFIG (src/CONST/index.ts#L2910-L2937), no POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_ITEMS route, no screen constant, no QuickbooksItemsPage, and no updateQuickbooksOnlineSyncItems action/command.

The full template for what's missing already exists in the QuickBooks Desktop integration, which ships a complete Items import. QBD renders an Items menu row (QuickbooksDesktopImportPage.tsx#L46-L50), has a dedicated toggle page QuickbooksDesktopItemsPage, a CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS key (src/CONST/index.ts#L2905), a route POLICY_ACCOUNTING_QUICKBOOKS_DESKTOP_ITEMS, a screen QUICKBOOKS_DESKTOP_ITEMS, and an action updateQuickbooksDesktopSyncItems that hits WRITE_COMMANDS.UPDATE_QUICKBOOKS_DESKTOP_SYNC_ITEMS. So the read path (menu) is missing the row and the write path (action + API command) does not exist for QBO at all.

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

Mirror the QBD Items pattern into QBO. QBO Items in Classic are a simple on/off import (they flow into expense line items, not an entity-map like classes/customers), so this should be a boolean toggle — matching importItems on QBD rather than the IntegrationEntityMap shape used by syncClasses/syncCustomers. Concretely: add SYNC_ITEMS: 'syncItems' to CONST.QUICKBOOKS_CONFIG; add updateQuickbooksOnlineSyncItems to src/libs/actions/connections/QuickbooksOnline.ts using the existing buildOnyxDataForQuickbooksConfiguration helper and a new WRITE_COMMANDS.UPDATE_QUICKBOOKS_ONLINE_SYNC_ITEMS; add the route POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_ITEMS, the screen constant, the ModalStackNavigators entry, and an en/es workspace.qbo.items/itemsDescription translation. Then push a new section into QuickbooksImportPage and build a QuickbooksItemsPage toggle modeled on QuickbooksDesktopItemsPage:

sections.push({
    description: translate('workspace.qbo.items'),
    action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_ITEMS.getRoute(policyID)),
    title: translate(qboConfig?.syncItems ? 'workspace.accounting.imported' : 'workspace.accounting.notImported'),
    subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_ITEMS],
});

This is safe because it adds a new independent config field and a new section object — it doesn't change the existing entity-map sections, the locations-to-report-fields effect, or the non-US taxes branch. The one hard dependency outside the App repo: the UpdateQuickbooksOnlineSyncItems API command (and confirmation that syncItems is actually returned in the synced QBO config) must exist on Web-Expensify/Auth. Since syncItems is already typed on QBOConnectionConfig but no command writes it, this should be confirmed as a backend dependency before/alongside the frontend work, exactly as QBD's UpdateQuickbooksDesktopSyncItems backs its toggle.

What alternative solutions did you explore? (Optional)

Modeling QBO Items as an IntegrationEntityMap (None/Tag/Report field) like classes/customers with a "Displayed as" sub-page. I rejected it because QBO Items in Classic import as expense line-item data rather than a tag/report-field dimension, so the simpler boolean toggle (matching QBD's importItems) is the faithful and lower-risk mapping.

[ahmdshrif]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[lorretheboy]

Note: Not duplicated, MobileMage's proposal is invalid as it posted before Help Wanted label

Proposal

What is the root cause of that problem?

New Expensify simply never built the QBO Items import UI. The QBO import page renders a fixed list of sections — Accounts, Classes, Customers, Locations, and (non‑US) Taxes — and there is no Items entry, so admins have no way to reach it:

App/src/pages/workspace/accounting/qbo/import/QuickbooksImportPage.tsx

Lines 38 to 72 in c6a9edb

	const sections: QBOSectionType[] = [
	{
	description: translate('workspace.accounting.accounts'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CHART_OF_ACCOUNTS.getRoute(policyID)),
	title: translate('workspace.accounting.importAsCategory'),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.ENABLE_NEW_CATEGORIES],
	},
	{
	description: translate('workspace.qbo.classes'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CLASSES.getRoute(policyID)),
	title: translate(`workspace.accounting.importTypes.${syncClasses ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_CLASSES],
	},
	{
	description: translate('workspace.qbo.customers'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CUSTOMERS.getRoute(policyID)),
	title: translate(`workspace.accounting.importTypes.${syncCustomers ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_CUSTOMERS],
	},
	{
	description: translate('workspace.qbo.locations'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_LOCATIONS.getRoute(policyID)),
	title: translate(`workspace.accounting.importTypes.${syncLocations ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_LOCATIONS],
	},
	];
	if (policy?.connections?.quickbooksOnline?.data?.country !== CONST.COUNTRY.US) {
	sections.push({
	description: translate('workspace.accounting.taxes'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_TAXES.getRoute(policyID)),
	title: translate(syncTax ? 'workspace.accounting.imported' : 'workspace.accounting.notImported'),
	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_TAX],
	});
	}

Everything an Items toggle needs is missing on the QBO side: there is no SYNC_ITEMS key in the QBO config constants…

App/src/CONST/index.ts

Lines 2910 to 2937 in c6a9edb

	QUICKBOOKS_CONFIG: {
	ENABLE_NEW_CATEGORIES: 'enableNewCategories',
	SYNC_CLASSES: 'syncClasses',
	SYNC_CUSTOMERS: 'syncCustomers',
	SYNC_LOCATIONS: 'syncLocations',
	SYNC_TAX: 'syncTax',
	EXPORT: 'export',
	EXPORTER: 'exporter',
	EXPORT_DATE: 'exportDate',
	NON_REIMBURSABLE_EXPENSES_ACCOUNT: 'nonReimbursableExpensesAccount',
	NON_REIMBURSABLE_EXPENSES_EXPORT_DESTINATION: 'nonReimbursableExpensesExportDestination',
	REIMBURSABLE_EXPENSES_ACCOUNT: 'reimbursableExpensesAccount',
	REIMBURSABLE_EXPENSES_EXPORT_DESTINATION: 'reimbursableExpensesExportDestination',
	NON_REIMBURSABLE_BILL_DEFAULT_VENDOR: 'nonReimbursableBillDefaultVendor',
	NON_REIMBURSABLE_CREDIT_CARD_DEFAULT_VENDOR: 'nonReimbursableCreditCardDefaultVendor',
	NON_REIMBURSABLE_EXPENSE_EXPORT_DESTINATION: 'nonReimbursableExpensesExportDestination',
	NON_REIMBURSABLE_EXPENSE_ACCOUNT: 'nonReimbursableExpensesAccount',
	RECEIVABLE_ACCOUNT: 'receivableAccount',
	AUTO_SYNC: 'autoSync',
	ENABLED: 'enabled',
	SYNC_PEOPLE: 'syncPeople',
	AUTO_CREATE_VENDOR: 'autoCreateVendor',
	REIMBURSEMENT_ACCOUNT_ID: 'reimbursementAccountID',
	COLLECTION_ACCOUNT_ID: 'collectionAccountID',
	ACCOUNTING_METHOD: 'accountingMethod',
	TRAVEL_INVOICING_VENDOR: 'travelInvoicingVendorID',
	TRAVEL_INVOICING_PAYABLE_ACCOUNT: 'travelInvoicingPayableAccountID',
	},

…no QBO Items page, no route, and no update action (unlike QuickBooks Desktop, which has all three). The config type already carries a syncItems flag, but it is marked TODO and nothing reads or writes it:

App/src/types/onyx/Policy.ts

Lines 506 to 507 in c6a9edb

	/** TODO: Will be handled in another issue */
	syncItems: boolean;

So the data shape exists, but the entire front‑end layer (menu item → page → action) was never implemented for QBO.

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

Mirror the QuickBooks Desktop Items implementation for QBO:

1. Add a SYNC_ITEMS: 'syncItems' key to QUICKBOOKS_CONFIG here:

App/src/CONST/index.ts

Lines 2910 to 2937 in c6a9edb

	QUICKBOOKS_CONFIG: {
	ENABLE_NEW_CATEGORIES: 'enableNewCategories',
	SYNC_CLASSES: 'syncClasses',
	SYNC_CUSTOMERS: 'syncCustomers',
	SYNC_LOCATIONS: 'syncLocations',
	SYNC_TAX: 'syncTax',
	EXPORT: 'export',
	EXPORTER: 'exporter',
	EXPORT_DATE: 'exportDate',
	NON_REIMBURSABLE_EXPENSES_ACCOUNT: 'nonReimbursableExpensesAccount',
	NON_REIMBURSABLE_EXPENSES_EXPORT_DESTINATION: 'nonReimbursableExpensesExportDestination',
	REIMBURSABLE_EXPENSES_ACCOUNT: 'reimbursableExpensesAccount',
	REIMBURSABLE_EXPENSES_EXPORT_DESTINATION: 'reimbursableExpensesExportDestination',
	NON_REIMBURSABLE_BILL_DEFAULT_VENDOR: 'nonReimbursableBillDefaultVendor',
	NON_REIMBURSABLE_CREDIT_CARD_DEFAULT_VENDOR: 'nonReimbursableCreditCardDefaultVendor',
	NON_REIMBURSABLE_EXPENSE_EXPORT_DESTINATION: 'nonReimbursableExpensesExportDestination',
	NON_REIMBURSABLE_EXPENSE_ACCOUNT: 'nonReimbursableExpensesAccount',
	RECEIVABLE_ACCOUNT: 'receivableAccount',
	AUTO_SYNC: 'autoSync',
	ENABLED: 'enabled',
	SYNC_PEOPLE: 'syncPeople',
	AUTO_CREATE_VENDOR: 'autoCreateVendor',
	REIMBURSEMENT_ACCOUNT_ID: 'reimbursementAccountID',
	COLLECTION_ACCOUNT_ID: 'collectionAccountID',
	ACCOUNTING_METHOD: 'accountingMethod',
	TRAVEL_INVOICING_VENDOR: 'travelInvoicingVendorID',
	TRAVEL_INVOICING_PAYABLE_ACCOUNT: 'travelInvoicingPayableAccountID',
	},

2. Add an updateQuickbooksOnlineSyncItems action in QuickbooksOnline.ts (optimistic + API command), modeled on QBD's updateQuickbooksDesktopSyncItems.

3. Add a QBO Items page with a toggle, reusing the QBD Items page as the template:

App/src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx

Lines 16 to 45 in c6a9edb

	function QuickbooksDesktopItemsPage({policy}: WithPolicyProps) {
	const {translate} = useLocalize();
	const styles = useThemeStyles();
	const policyID = policy?.id ?? '-1';
	const qbdConfig = policy?.connections?.quickbooksDesktop?.config;
	return (
	<ConnectionLayout
	displayName="QuickbooksDesktopItemsPage"
	headerTitle="workspace.qbd.items"
	title="workspace.qbd.itemsDescription"
	accessVariants={[CONST.POLICY.ACCESS_VARIANTS.ADMIN, CONST.POLICY.ACCESS_VARIANTS.CONTROL]}
	policyID={policyID}
	featureName={CONST.POLICY.MORE_FEATURES.ARE_CONNECTIONS_ENABLED}
	contentContainerStyle={[styles.pb2, styles.ph5]}
	connectionName={CONST.POLICY.CONNECTIONS.NAME.QBD}
	onBackButtonPress={() => Navigation.goBack(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_DESKTOP_IMPORT.getRoute(policyID))}
	>
	<ToggleSettingOptionRow
	title={translate('workspace.accounting.import')}
	switchAccessibilityLabel={translate('workspace.qbd.items')}
	isActive={!!qbdConfig?.importItems}
	onToggle={(isEnabled) => QuickbooksDesktop.updateQuickbooksDesktopSyncItems(policyID, isEnabled, !!qbdConfig?.importItems)}
	pendingAction={PolicyUtils.settingsPendingAction([CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS], qbdConfig?.pendingFields)}
	errors={ErrorUtils.getLatestErrorField(qbdConfig, CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS)}
	onCloseError={() => clearQBDErrorField(policyID, CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS)}
	/>
	</ConnectionLayout>
	);
	}

4. Register the new route/screen, then add the Items section to the QBO import list, exactly like the QBD import page does it:

App/src/pages/workspace/accounting/qbd/import/QuickbooksDesktopImportPage.tsx

Lines 46 to 50 in c6a9edb

	{
	description: translate('workspace.qbd.items'),
	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_DESKTOP_ITEMS.getRoute(policyID)),
	subscribedSettings: [CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS],
	},

The new section reads/writes qboConfig.syncItems and subscribes to CONST.QUICKBOOKS_CONFIG.SYNC_ITEMS for pending/error feedback, matching the surrounding sections in the QBO import page.

What alternative solutions did you explore? (Optional)

If Items in QBO is a simple on/off (no display‑as mapping), the import page could render an inline toggle row instead of navigating to a dedicated sub‑page, avoiding the extra route/page. The page‑based approach is preferred for consistency with the other QBO coding options and with QBD.

[yusufdeveloper2903]

Proposal

What is the root cause of that problem?

This is a missing-feature bug, not a regression. The QuickBooks Online (QBO) Import menu in New Expensify simply never exposes an "Items" option, while Classic does.

The QBO import menu is built from a hard-coded sections array that only ever lists Chart of Accounts, Classes, Customers, Locations (and conditionally Taxes):

• App/src/pages/workspace/accounting/qbo/import/QuickbooksImportPage.tsx

  Lines 38 to 72 in d81cc58

  	const sections: QBOSectionType[] = [
  	{
  	description: translate('workspace.accounting.accounts'),
  	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CHART_OF_ACCOUNTS.getRoute(policyID)),
  	title: translate('workspace.accounting.importAsCategory'),
  	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.ENABLE_NEW_CATEGORIES],
  	},
  	{
  	description: translate('workspace.qbo.classes'),
  	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CLASSES.getRoute(policyID)),
  	title: translate(`workspace.accounting.importTypes.${syncClasses ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
  	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_CLASSES],
  	},
  	{
  	description: translate('workspace.qbo.customers'),
  	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CUSTOMERS.getRoute(policyID)),
  	title: translate(`workspace.accounting.importTypes.${syncCustomers ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
  	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_CUSTOMERS],
  	},
  	{
  	description: translate('workspace.qbo.locations'),
  	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_LOCATIONS.getRoute(policyID)),
  	title: translate(`workspace.accounting.importTypes.${syncLocations ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
  	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_LOCATIONS],
  	},
  	];
  	if (policy?.connections?.quickbooksOnline?.data?.country !== CONST.COUNTRY.US) {
  	sections.push({
  	description: translate('workspace.accounting.taxes'),
  	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_TAXES.getRoute(policyID)),
  	title: translate(syncTax ? 'workspace.accounting.imported' : 'workspace.accounting.notImported'),
  	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_TAX],
  	});
  	}

There is no syncItems entry in that array, and correspondingly no route, no screen, no settings page, and no action wired up for QBO items anywhere in the app.

The data model is actually already half-built: the field exists in the QBO config type but was explicitly deferred:

• App/src/types/onyx/Policy.ts

  Lines 506 to 507 in d81cc58

  	/** TODO: Will be handled in another issue */
  	syncItems: boolean;

  — syncItems: boolean; with the comment TODO: Will be handled in another issue.

Everything downstream of that type was left unimplemented for QBO:

• No SYNC_ITEMS key in QUICKBOOKS_CONFIG (only SYNC_CLASSES/SYNC_CUSTOMERS/SYNC_LOCATIONS/SYNC_TAX exist):

  App/src/CONST/index.ts

  Lines 2910 to 2937 in d81cc58

  	QUICKBOOKS_CONFIG: {
  	ENABLE_NEW_CATEGORIES: 'enableNewCategories',
  	SYNC_CLASSES: 'syncClasses',
  	SYNC_CUSTOMERS: 'syncCustomers',
  	SYNC_LOCATIONS: 'syncLocations',
  	SYNC_TAX: 'syncTax',
  	EXPORT: 'export',
  	EXPORTER: 'exporter',
  	EXPORT_DATE: 'exportDate',
  	NON_REIMBURSABLE_EXPENSES_ACCOUNT: 'nonReimbursableExpensesAccount',
  	NON_REIMBURSABLE_EXPENSES_EXPORT_DESTINATION: 'nonReimbursableExpensesExportDestination',
  	REIMBURSABLE_EXPENSES_ACCOUNT: 'reimbursableExpensesAccount',
  	REIMBURSABLE_EXPENSES_EXPORT_DESTINATION: 'reimbursableExpensesExportDestination',
  	NON_REIMBURSABLE_BILL_DEFAULT_VENDOR: 'nonReimbursableBillDefaultVendor',
  	NON_REIMBURSABLE_CREDIT_CARD_DEFAULT_VENDOR: 'nonReimbursableCreditCardDefaultVendor',
  	NON_REIMBURSABLE_EXPENSE_EXPORT_DESTINATION: 'nonReimbursableExpensesExportDestination',
  	NON_REIMBURSABLE_EXPENSE_ACCOUNT: 'nonReimbursableExpensesAccount',
  	RECEIVABLE_ACCOUNT: 'receivableAccount',
  	AUTO_SYNC: 'autoSync',
  	ENABLED: 'enabled',
  	SYNC_PEOPLE: 'syncPeople',
  	AUTO_CREATE_VENDOR: 'autoCreateVendor',
  	REIMBURSEMENT_ACCOUNT_ID: 'reimbursementAccountID',
  	COLLECTION_ACCOUNT_ID: 'collectionAccountID',
  	ACCOUNTING_METHOD: 'accountingMethod',
  	TRAVEL_INVOICING_VENDOR: 'travelInvoicingVendorID',
  	TRAVEL_INVOICING_PAYABLE_ACCOUNT: 'travelInvoicingPayableAccountID',
  	},

• No updateQuickbooksOnlineSyncItems action — the QBO actions file stops at syncTax and friends:

  App/src/libs/actions/connections/QuickbooksOnline.ts

  Lines 459 to 468 in d81cc58

  	function updateQuickbooksOnlineSyncTax<TSettingValue extends Connections['quickbooksOnline']['config']['syncTax']>(policyID: string, settingValue: TSettingValue) {
  	const onyxData = buildOnyxDataForQuickbooksConfiguration(policyID, CONST.QUICKBOOKS_CONFIG.SYNC_TAX, settingValue, !settingValue);
  	const parameters: UpdateQuickbooksOnlineGenericTypeParams = {
  	policyID,
  	settingValue: JSON.stringify(settingValue),
  	idempotencyKey: String(CONST.QUICKBOOKS_CONFIG.SYNC_TAX),
  	};
  	API.write(WRITE_COMMANDS.UPDATE_QUICKBOOKS_ONLINE_SYNC_TAX, parameters, onyxData);
  	}

• No POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_ITEMS route (only ..._LOCATIONS, ..._TAXES, etc.):

  App/src/ROUTES.ts

  Lines 3566 to 3582 in d81cc58

  	POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_LOCATIONS: {
  	route: 'workspaces/:policyID/accounting/quickbooks-online/import/locations',
  	getRoute: (policyID: string | undefined) => {
  	if (!policyID) {
  	Log.warn('Invalid policyID is used to build the POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_LOCATIONS route');
  	}
  	return `workspaces/${policyID}/accounting/quickbooks-online/import/locations` as const;
  	},
  	},
  	POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_LOCATIONS_DISPLAYED_AS: {
  	route: 'workspaces/:policyID/accounting/quickbooks-online/import/locations/displayed-as',
  	getRoute: (policyID: string | undefined) => `workspaces/${policyID}/accounting/quickbooks-online/import/locations/displayed-as` as const,
  	},
  	POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_TAXES: {
  	route: 'workspaces/:policyID/accounting/quickbooks-online/import/taxes',
  	getRoute: (policyID: string) => `workspaces/${policyID}/accounting/quickbooks-online/import/taxes` as const,
  	},

Contrast with QuickBooks Desktop (QBD), where the identical feature is fully implemented end-to-end and is the perfect reuse template:

• Config type:

  App/src/types/onyx/Policy.ts

  Line 1689 in d81cc58

  importItems: boolean;

  — importItems: boolean;
• CONST:

  App/src/CONST/index.ts

  Line 2905 in d81cc58

  IMPORT_ITEMS: 'importItems',

  — IMPORT_ITEMS: 'importItems'
• Action:

  App/src/libs/actions/connections/QuickbooksDesktop.ts

  Lines 463 to 475 in d81cc58

  	function updateQuickbooksDesktopSyncItems<TSettingValue extends Connections['quickbooksDesktop']['config']['importItems']>(
  	policyID: string,
  	settingValue: TSettingValue,
  	oldSettingValue?: TSettingValue,
  	) {
  	const onyxData = buildOnyxDataForQuickbooksConfiguration(policyID, CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS, settingValue, oldSettingValue);
  	const parameters: UpdateQuickbooksDesktopGenericTypeParams = {
  	policyID,
  	settingValue: JSON.stringify(settingValue),
  	idempotencyKey: String(CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS),
  	};
  	API.write(WRITE_COMMANDS.UPDATE_QUICKBOOKS_DESKTOP_SYNC_ITEMS, parameters, onyxData);
  	}

  — updateQuickbooksDesktopSyncItems
• Route:

  App/src/ROUTES.ts

  Lines 2257 to 2260 in d81cc58

  	POLICY_ACCOUNTING_QUICKBOOKS_DESKTOP_ITEMS: {
  	route: 'workspaces/:policyID/accounting/quickbooks-desktop/import/items',
  	getRoute: (policyID: string) => `workspaces/${policyID}/accounting/quickbooks-desktop/import/items` as const,
  	},

• Settings page:

  App/src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx

  Lines 16 to 45 in d81cc58

  	function QuickbooksDesktopItemsPage({policy}: WithPolicyProps) {
  	const {translate} = useLocalize();
  	const styles = useThemeStyles();
  	const policyID = policy?.id ?? '-1';
  	const qbdConfig = policy?.connections?.quickbooksDesktop?.config;
  	return (
  	<ConnectionLayout
  	displayName="QuickbooksDesktopItemsPage"
  	headerTitle="workspace.qbd.items"
  	title="workspace.qbd.itemsDescription"
  	accessVariants={[CONST.POLICY.ACCESS_VARIANTS.ADMIN, CONST.POLICY.ACCESS_VARIANTS.CONTROL]}
  	policyID={policyID}
  	featureName={CONST.POLICY.MORE_FEATURES.ARE_CONNECTIONS_ENABLED}
  	contentContainerStyle={[styles.pb2, styles.ph5]}
  	connectionName={CONST.POLICY.CONNECTIONS.NAME.QBD}
  	onBackButtonPress={() => Navigation.goBack(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_DESKTOP_IMPORT.getRoute(policyID))}
  	>
  	<ToggleSettingOptionRow
  	title={translate('workspace.accounting.import')}
  	switchAccessibilityLabel={translate('workspace.qbd.items')}
  	isActive={!!qbdConfig?.importItems}
  	onToggle={(isEnabled) => QuickbooksDesktop.updateQuickbooksDesktopSyncItems(policyID, isEnabled, !!qbdConfig?.importItems)}
  	pendingAction={PolicyUtils.settingsPendingAction([CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS], qbdConfig?.pendingFields)}
  	errors={ErrorUtils.getLatestErrorField(qbdConfig, CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS)}
  	onCloseError={() => clearQBDErrorField(policyID, CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS)}
  	/>
  	</ConnectionLayout>
  	);
  	}

• Import-menu entry:

  App/src/pages/workspace/accounting/qbd/import/QuickbooksDesktopImportPage.tsx

  Lines 47 to 49 in d81cc58

  	description: translate('workspace.qbd.items'),
  	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_DESKTOP_ITEMS.getRoute(policyID)),
  	subscribedSettings: [CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS],

So: QBO config type declares syncItems but it was left as a TODO → no CONST key / action / route / screen / page were built for QBO → the import-menu sections array has no Items entry → admins see no way to import QBO Items in New Expensify.

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

Implement the QBO Items toggle by mirroring the already-shipped QBD Items flow (every piece named below already exists for QBD and is in scope to copy). syncItems is a boolean, so this is a simple on/off toggle just like syncTax — not an IntegrationEntityMap like classes/customers.

1. Type — drop the TODO on the existing field; syncItems: boolean already lives at Policy.ts:506-507, so no new field is needed.
2. CONST — add SYNC_ITEMS: 'syncItems' to QUICKBOOKS_CONFIG (

   App/src/CONST/index.ts

   Lines 2910 to 2937 in d81cc58

   	QUICKBOOKS_CONFIG: {
   	ENABLE_NEW_CATEGORIES: 'enableNewCategories',
   	SYNC_CLASSES: 'syncClasses',
   	SYNC_CUSTOMERS: 'syncCustomers',
   	SYNC_LOCATIONS: 'syncLocations',
   	SYNC_TAX: 'syncTax',
   	EXPORT: 'export',
   	EXPORTER: 'exporter',
   	EXPORT_DATE: 'exportDate',
   	NON_REIMBURSABLE_EXPENSES_ACCOUNT: 'nonReimbursableExpensesAccount',
   	NON_REIMBURSABLE_EXPENSES_EXPORT_DESTINATION: 'nonReimbursableExpensesExportDestination',
   	REIMBURSABLE_EXPENSES_ACCOUNT: 'reimbursableExpensesAccount',
   	REIMBURSABLE_EXPENSES_EXPORT_DESTINATION: 'reimbursableExpensesExportDestination',
   	NON_REIMBURSABLE_BILL_DEFAULT_VENDOR: 'nonReimbursableBillDefaultVendor',
   	NON_REIMBURSABLE_CREDIT_CARD_DEFAULT_VENDOR: 'nonReimbursableCreditCardDefaultVendor',
   	NON_REIMBURSABLE_EXPENSE_EXPORT_DESTINATION: 'nonReimbursableExpensesExportDestination',
   	NON_REIMBURSABLE_EXPENSE_ACCOUNT: 'nonReimbursableExpensesAccount',
   	RECEIVABLE_ACCOUNT: 'receivableAccount',
   	AUTO_SYNC: 'autoSync',
   	ENABLED: 'enabled',
   	SYNC_PEOPLE: 'syncPeople',
   	AUTO_CREATE_VENDOR: 'autoCreateVendor',
   	REIMBURSEMENT_ACCOUNT_ID: 'reimbursementAccountID',
   	COLLECTION_ACCOUNT_ID: 'collectionAccountID',
   	ACCOUNTING_METHOD: 'accountingMethod',
   	TRAVEL_INVOICING_VENDOR: 'travelInvoicingVendorID',
   	TRAVEL_INVOICING_PAYABLE_ACCOUNT: 'travelInvoicingPayableAccountID',
   	},

   ), mirroring QBD's IMPORT_ITEMS.
3. Action — add updateQuickbooksOnlineSyncItems to QuickbooksOnline.ts by copying updateQuickbooksOnlineSyncTax verbatim and swapping the key/command (

   App/src/libs/actions/connections/QuickbooksOnline.ts

   Lines 459 to 468 in d81cc58

   	function updateQuickbooksOnlineSyncTax<TSettingValue extends Connections['quickbooksOnline']['config']['syncTax']>(policyID: string, settingValue: TSettingValue) {
   	const onyxData = buildOnyxDataForQuickbooksConfiguration(policyID, CONST.QUICKBOOKS_CONFIG.SYNC_TAX, settingValue, !settingValue);
   	const parameters: UpdateQuickbooksOnlineGenericTypeParams = {
   	policyID,
   	settingValue: JSON.stringify(settingValue),
   	idempotencyKey: String(CONST.QUICKBOOKS_CONFIG.SYNC_TAX),
   	};
   	API.write(WRITE_COMMANDS.UPDATE_QUICKBOOKS_ONLINE_SYNC_TAX, parameters, onyxData);
   	}

   ). It reuses the existing buildOnyxDataForQuickbooksConfiguration helper already used by every sibling setter, plus a new WRITE_COMMANDS.UPDATE_QUICKBOOKS_ONLINE_SYNC_ITEMS and its UpdateQuickbooksOnlineGenericTypeParams mapping.
4. Route + Screen — add POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_ITEMS to ROUTES.ts (mirror QBD's at

   App/src/ROUTES.ts

   Lines 2257 to 2260 in d81cc58

   	POLICY_ACCOUNTING_QUICKBOOKS_DESKTOP_ITEMS: {
   	route: 'workspaces/:policyID/accounting/quickbooks-desktop/import/items',
   	getRoute: (policyID: string) => `workspaces/${policyID}/accounting/quickbooks-desktop/import/items` as const,
   	},

   ) and a matching QUICKBOOKS_ONLINE_ITEMS screen in SCREENS.ts, then register it in ModalStackNavigators/index.tsx next to the existing QBD registration (

   App/src/libs/Navigation/AppNavigator/ModalStackNavigators/index.tsx

   Line 730 in d81cc58

   [SCREENS.WORKSPACE.ACCOUNTING.QUICKBOOKS_DESKTOP_ITEMS]: () => require<ReactComponentModule>('../../../../pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage').default,

   ).
5. Page — create QuickbooksOnlineItemsPage.tsx as a near-clone of QuickbooksDesktopItemsPage.tsx (

   App/src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx

   Lines 16 to 45 in d81cc58

   	function QuickbooksDesktopItemsPage({policy}: WithPolicyProps) {
   	const {translate} = useLocalize();
   	const styles = useThemeStyles();
   	const policyID = policy?.id ?? '-1';
   	const qbdConfig = policy?.connections?.quickbooksDesktop?.config;
   	return (
   	<ConnectionLayout
   	displayName="QuickbooksDesktopItemsPage"
   	headerTitle="workspace.qbd.items"
   	title="workspace.qbd.itemsDescription"
   	accessVariants={[CONST.POLICY.ACCESS_VARIANTS.ADMIN, CONST.POLICY.ACCESS_VARIANTS.CONTROL]}
   	policyID={policyID}
   	featureName={CONST.POLICY.MORE_FEATURES.ARE_CONNECTIONS_ENABLED}
   	contentContainerStyle={[styles.pb2, styles.ph5]}
   	connectionName={CONST.POLICY.CONNECTIONS.NAME.QBD}
   	onBackButtonPress={() => Navigation.goBack(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_DESKTOP_IMPORT.getRoute(policyID))}
   	>
   	<ToggleSettingOptionRow
   	title={translate('workspace.accounting.import')}
   	switchAccessibilityLabel={translate('workspace.qbd.items')}
   	isActive={!!qbdConfig?.importItems}
   	onToggle={(isEnabled) => QuickbooksDesktop.updateQuickbooksDesktopSyncItems(policyID, isEnabled, !!qbdConfig?.importItems)}
   	pendingAction={PolicyUtils.settingsPendingAction([CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS], qbdConfig?.pendingFields)}
   	errors={ErrorUtils.getLatestErrorField(qbdConfig, CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS)}
   	onCloseError={() => clearQBDErrorField(policyID, CONST.QUICKBOOKS_DESKTOP_CONFIG.IMPORT_ITEMS)}
   	/>
   	</ConnectionLayout>
   	);
   	}

   ). It reuses the existing ToggleSettingOptionRow component, reading !!qboConfig?.syncItems and calling the new action.
6. Import menu — push one entry into the QBO sections array (

   App/src/pages/workspace/accounting/qbo/import/QuickbooksImportPage.tsx

   Lines 38 to 72 in d81cc58

   	const sections: QBOSectionType[] = [
   	{
   	description: translate('workspace.accounting.accounts'),
   	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CHART_OF_ACCOUNTS.getRoute(policyID)),
   	title: translate('workspace.accounting.importAsCategory'),
   	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.ENABLE_NEW_CATEGORIES],
   	},
   	{
   	description: translate('workspace.qbo.classes'),
   	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CLASSES.getRoute(policyID)),
   	title: translate(`workspace.accounting.importTypes.${syncClasses ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
   	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_CLASSES],
   	},
   	{
   	description: translate('workspace.qbo.customers'),
   	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_CUSTOMERS.getRoute(policyID)),
   	title: translate(`workspace.accounting.importTypes.${syncCustomers ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
   	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_CUSTOMERS],
   	},
   	{
   	description: translate('workspace.qbo.locations'),
   	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_LOCATIONS.getRoute(policyID)),
   	title: translate(`workspace.accounting.importTypes.${syncLocations ?? CONST.INTEGRATION_ENTITY_MAP_TYPES.NONE}`),
   	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_LOCATIONS],
   	},
   	];
   	if (policy?.connections?.quickbooksOnline?.data?.country !== CONST.COUNTRY.US) {
   	sections.push({
   	description: translate('workspace.accounting.taxes'),
   	action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_TAXES.getRoute(policyID)),
   	title: translate(syncTax ? 'workspace.accounting.imported' : 'workspace.accounting.notImported'),
   	subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_TAX],
   	});
   	}

   ), styled like the existing syncTax push (imported/not-imported title), e.g.:

{
    description: translate('workspace.qbo.items'),
    action: () => Navigation.navigate(ROUTES.POLICY_ACCOUNTING_QUICKBOOKS_ONLINE_ITEMS.getRoute(policyID)),
    title: translate(syncItems ? 'workspace.accounting.imported' : 'workspace.accounting.notImported'),
    subscribedSettings: [CONST.QUICKBOOKS_CONFIG.SYNC_ITEMS],
}

(destructure syncItems alongside the existing fields at QuickbooksImportPage.tsx:28.)

7. Copy — add workspace.qbo.items / itemsDescription to en.ts/es.ts, mirroring the QBD strings (

   App/src/languages/en.ts

   Line 4774 in d81cc58

   itemsDescription: 'Choose how to handle QuickBooks Desktop items in Expensify.',

   ).

This is purely additive and follows the QBD blueprint one-to-one, so it carries minimal risk. Minor naming/copy details can be discussed in the PR phase.

What alternative solutions did you explore? (Optional)

Generalize the QBO/QBD items pages into one shared component parameterized by connection name. While it removes some duplication, the two configs use different field names (syncItems vs importItems), different CONST namespaces, and different actions, so the abstraction adds indirection for very little saved code. Mirroring the proven QBD flow keeps each connection self-contained and consistent with how Classes/Customers/Locations are already structured per-connection.

[melvin-bot]

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

[godzillaxbox19982014-lgtm]

Proposal

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

Unable to import QuickBooks Online Items in New Expensify

What is the root cause of that problem?

I traced this to the path that handles QuickBooks:

• src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx:29 (QuickbooksDesktopItemsPage): featureName={CONST.POLICY.MORE_FEATURES.ARE_CONNECTIONS_ENABLED}
• src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx:31 (QuickbooksDesktopItemsPage): connectionName={CONST.POLICY.CONNECTIONS.NAME.QBD}
• src/pages/workspace/accounting/qbo/import/QuickbooksTaxesPage.tsx:21 (qboConfig): const qboConfig = policy?.connections?.quickbooksOnline?.config;
• The local evidence matches this recurring failure shape: shared workspace list builds options without the same eligibility filter as another workspace surface. Here, src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx:29 and src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx:31 do not agree on the same QuickBooks value, so the user-visible path can show a missing or stale state even though nearby data already has the needed context.

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

• Update src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx:29 to derive QuickBooks from the workspace setup and policy state that owns this flow before the value is consumed.
• Carry the same normalized value through src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx:31; that follows the safer family move to move the rule into the shared selector/helper, so the write/optimistic/read paths agree instead of only changing the visible component.
• Keep the change inside the Workspace, Policy, Categories, Tags, Rules surface and avoid changing account/admin permission surfaces, policy owner/current-user exceptions.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

1. Add or update a regression in tests/unit/Policy*.ts for the exact issue flow: Unable to import QuickBooks Online Items in New Expensify.
2. Cover the counter-case near src/pages/workspace/accounting/qbd/import/QuickbooksDesktopItemsPage.tsx:29 so valid existing QuickBooks behavior still works.
3. Manually repeat the issue steps after the patch and confirm the visible state/action is no longer stale.

What alternative solutions did you explore? (Optional)

• I would not add a broad new condition outside these referenced paths; the safer fix is to keep QuickBooks consistent at the first read/write boundary shown above.

[melvin-bot]

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