[Due for payment 2026-06-17] [Due for payment 2026-06-10] [$250] QBO - Selected vendor bill is missing when import locations is enabled

[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: 9.3.27-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #83416
Email or phone of affected tester (no customers): applausetester+270204abc@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Workspace is connected to QBO.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Accounting.
3. Click Export > Export out-of-pocket expenses as > Export as > Journal entry.
4. Click RHP back button.
5. Click Export company card expenses as > Export as > Vendor bill.
6. Close the RHP.
7. Click Import.
8. Click Locations.
9. Enable Import.
10. Close the RHP.
11. Click Export > Export company card expenses as > Export as.

Expected Result:

Vendor bill should be present in the list as it is selected.

Actual Result:

Vendor bill is missing in Export company card expenses when Vendor bill is selected and import locations is enabled.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022044010527197082814
• Upwork Job ID: 2044010527197082814
• Last Price Increase: 2026-04-21

Issue Owner

Current Issue Owner: @dmkt9

[MelvinBot]

Proposal

What is the root cause of that problem?

When the user enables "Import Locations" on QuickbooksLocationsPage.tsx, the toggle handler calls updateQuickbooksOnlineSyncLocations, which only updates the syncLocations config key. It does not check or reset nonReimbursableExpensesExportDestination.

Meanwhile, QuickbooksCompanyCardExpenseAccountSelectCardPage.tsx:59 hides the Vendor Bill option from the picker when locations are enabled (because QBO doesn't support locations on vendor bill exports). This creates a stale state: the config still says VENDOR_BILL, but the UI no longer shows it as a selectable option.

The incompatibility is already known — utils.ts:4-9 (canImportLocationsAsTags) explicitly checks that the non-reimbursable export destination is credit card or debit card (not vendor bill) to determine if locations can be imported as tags. But nothing acts on this check when toggling locations on.

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

In QuickbooksLocationsPage.tsx, when the user enables locations and the current nonReimbursableExpensesExportDestination is VENDOR_BILL, automatically reset it to CREDIT_CARD (the first valid option). This should use updateManyPolicyConnectionConfigs to update both syncLocations and nonReimbursableExpensesExportDestination atomically, along with the related account fields (nonReimbursableExpensesAccount and nonReimbursableBillDefaultVendor).

The updateQuickbooksOnlineSyncLocations callback should check qboConfig?.nonReimbursableExpensesExportDestination === CONST.QUICKBOOKS_NON_REIMBURSABLE_EXPORT_ACCOUNT_TYPE.VENDOR_BILL before dispatching the update, and if true, bundle the export destination reset into the same API call.

What alternative solutions did you explore? (Optional)

An alternative would be to reset the export destination reactively — e.g., adding a useEffect in QuickbooksCompanyCardExpenseAccountSelectCardPage that detects the incompatible state and auto-corrects. However, this is worse because the stale config would persist until the user navigates to the export page, and the backend could attempt to use the invalid VENDOR_BILL setting during a sync in the meantime.

---

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 - @dmkt9 (External)

[melvin-bot]

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