You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[QBO TI CR] Block or warn admin enabling continuous reconciliation without a Travel Invoicing payable account set #91505
Admins can enable QBO Travel Invoicing continuous reconciliation under workspace advanced accounting without first setting travelInvoicingPayableAccountID in QBO Export config. The toggle saves successfully, the BE auto-sync runs on the next tick, and then fails on the first settlement with an actionable error in IS logs (Travel Invoicing payable account is not configured for QuickBooks Online. Set it under workspace accounting before enabling continuous reconciliation.). The admin doesn't see this until they realize JEs aren't posting to QBO.
Filing this so we can discuss with the design team what the better UX is. Two options that come to mind:
Disable the RC toggle in the QBO advanced accounting page until travelInvoicingPayableAccountID is set
Allow the toggle but surface an inline error / pending state on the toggle when the payable account is missing, pointing the admin at the Export config screen to set it
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.72-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
shawnborton commentedon May 25, 2026
Can you share some screenshots of what these pages currently look like today?
allgandalf commentedon Jun 1, 2026
oh it today
blimpich commentedon Jun 3, 2026
bump @allgandalf
melvin-bot commentedon Jun 4, 2026
@allgandalf Whoops! This issue is 2 days overdue. Let's get this updated quick!
allgandalf commentedon Jun 8, 2026
procrastination is bad, i'm on it today, sorry 😢
65 remaining items
rlinoz commentedon Aug 26, 2026
I dont think so, assigned myself and ben as reviewers
allgandalf commentedon Sep 1, 2026
I was out, back today, working on the PR review
melvin-bot commentedon Sep 7, 2026
@rlinoz / @blimpich @allgandalf
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.72-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: