Repository navigation
Description
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 (Unable to access customer account, could not reproduce in QA account)
Reproducible in production?: Needs Reproduction (Unable to access customer account, could not reproduce in QA account)
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: @VictoriaExpensify & Alannah Williams
Slack conversation (hyperlinked to channel name):
Action Performed:
- The user selects their Workspace
- They select the Accounting tab
- They click 'Card Reconciliation'
- They enable this
- They select the 'Workspace X'
- The screen refreshes to the Card Reconciliation tab with this disabled.
Expected Result:
The user can turn this on > select the account > the information saves and exports correctly
Actual Result:
The user turns card reconciliation on > selects the account > the screen refreshes with the button turned off.
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
For the customer's details check please OP
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022082045278223790573
- Upwork Job ID: 2082045278223790573
- Last Price Increase: 2026-08-23
Issue Owner
Current Issue Owner: @thelullabyyMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
exfy-zapier commentedon Jul 28, 2026
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
MelvinBot commentedon Jul 28, 2026
Issue Analysis
Symptom: On QBO, enabling Card Reconciliation → picking a reconciliation account → returning to the tab leaves the toggle OFF.
Most likely root cause (backend): The App code path is internally consistent — enabling the toggle optimistically writes
true, andSET_CARD_RECONCILIATION_BANK_ACCOUNTnever touches the toggle state. The toggle only flips back to OFF when the backend says so, via one of:TOGGLE_CARD_CONTINUOUS_RECONCILIATIONreturning non‑200, whosefailureDatareverts the optimistic value to!value→ OFF (Card.ts:1620-1636).OpenPolicyAccountingPagere‑fetch overwriting the optimistictruewith the backend's authoritative value, which stays OFF if the backend won't persist continuous reconciliation until a reconciliation account (or QBO auto‑sync) is associated first.Because the App side behaves correctly, the fix most likely lives outside this repo (Auth / Web‑Expensify — the
TOGGLE_CARD_CONTINUOUS_RECONCILIATIONcommand and its preconditions). This needs an internal engineer with access to those repos to confirm and fix — I can't propose an App code change for it. There is a related open App issue, #91505, suggesting the backend does gate continuous reconciliation on having a payable/reconciliation account set, which fits this symptom.To confirm: pull production logs for this workspace's
TOGGLE_CARD_CONTINUOUS_RECONCILIATIONandSET_CARD_RECONCILIATION_BANK_ACCOUNTcalls — did the toggle command return non‑200, and doesOpenPolicyAccountingPagereturn the continuous‑reconciliation field as0after the account is set?Investigation details
CardReconciliationPage.tsx:85-108. ToggleisActive={!!continuousReconciliation}is derived solely from the Onyx collection keyEXPENSIFY_CARD_USE_CONTINUOUS_RECONCILIATION_{effectiveDomainID}— read and written under the sameeffectiveDomainID, so it is not a key‑mismatch bug on the toggle itself.autoSync.enabled:disabled={!autoSync}. If auto‑sync is off the control is disabled entirely.toggleContinuousReconciliation,Card.ts:1572-1643—successDatakeeps the valuetrue; onlyfailureDatareverts it.setCardReconciliationAccount,Card.ts:1645-1668— writes only the bank‑account‑ID key; nosuccessData, so it cannot itself reset the toggle.CardReconciliationPagekeys offeffectiveDomainID(parsed from the card‑feed key, falling back topolicy.policyAccountID) —CardReconciliationPage.tsx:55,83— while the account‑settings page passespolicy.policyAccountIDtosetCardReconciliationAccount. If those differ for this workspace, the saved account row shows empty (though this would not by itself flip the toggle).Alternative explanations considered: a pure client key‑mismatch on the toggle (ruled out — read/write use the same
effectiveDomainID); a missing optimistic update (ruled out — the optimistic write is present). The remaining explanations all route through the backend response.Next Steps for Contributor+ team:
This looks like a backend (Auth/Web‑Expensify) issue rather than an App fix — please escalate to an internal engineer to confirm via logs whether
TOGGLE_CARD_CONTINUOUS_RECONCILIATIONis being rejected (and whether a reconciliation account is a required precondition).To refine:
@MelvinBot <your feedback>melvin-bot commentedon Jul 28, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (
External)melvin-bot commentedon Jul 28, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022082045278223790573
mukhrr commentedon Jul 28, 2026
@ahmedGaber93 I have a repro video in case you cannot.. I believe this is FE bug
melvin-bot commentedon Jul 31, 2026
@ahmedGaber93 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
ahmedGaber93 commentedon Aug 2, 2026
I am not able to reproduce it.
@mukhrr could you please share your steps and video? thanks!
62 remaining items
heekinho commentedon Sep 3, 2026
Nudged in slack for team's input. I'll keep adjusting the PRs so in case that solution is considered good we can quickly deploy it.
melvin-bot commentedon Sep 8, 2026
@heekinho Eep! 4 days overdue now. Issues have feelings too...
heekinho commentedon Sep 10, 2026
Actively working on it. Adjusted on the lastest sync today I create on PR on Web-Expensify and adjusted the App one.
heekinho commentedon Oct 9, 2026
App PR was just deployed to production. Closing