[inimaga]

Held on:

• https://github.com/Expensify/Auth/pull/25468
• https://github.com/Expensify/Web-Expensify/pull/57126

Explanation of Change

Exact Online is not available yet, so workspace admins need a way to register interest before launch. This adds Exact Online with Coming soon and Join waitlist to Accounting and Connections. Signup shows the confirmation from the design and the same joined state across the account's workspaces.

Signup uses the existing account save action, works offline, keeps its timestamp on retries, and rolls back on failure. Beta users also see the waitlist until R1 adds the connection flow.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/691056

PROPOSAL: N/A (internal implementation issue)

Tests

Manual Test steps

1. Sign in as a workspace admin, enable Accounting, and open the Accounting page.
2. Verify Exact Online shows its icon, Coming soon, and Join waitlist.
3. Press Join waitlist. Verify the confirmation says “You’re on the waitlist” and “Concierge will send you a message to let you know when this integration is ready and how to connect.” Dismiss it with Got it.
4. Verify the row now says “You’re on the waitlist” without another signup button.
5. Reload the app, open Accounting in a second workspace, and verify the same joined state.

• Verify that no errors appear in the JS console

Offline tests

Automated tests verify that signup remains available offline, the queued save and optimistic update use one timestamp, and failure restores the absent value. Existing live connectors remain disabled offline.

QA Steps

Same as manual test steps above

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If the PR adds or modifies the UI:
  • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
  • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
  • I verified all new/changed elements have meaningful accessible names and roles.
  • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Exact.Online.Web.mp4

[melvin-bot]

@jayeshmangwani Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-15T15:38:42.404122Z	c1cfff3	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/CONST/index.ts	95.90% <ø> (ø)
src/ONYXKEYS.ts	100.00% <ø> (ø)
...rc/components/Icon/chunks/expensify-icons.chunk.ts	0.00% <ø> (ø)
src/libs/ExportOnyxState/masking.ts	80.95% <ø> (ø)
...es/workspace/accounting/ExactOnlineWaitlistRow.tsx	100.00% <100.00%> (ø)
...ages/workspace/accounting/PolicyAccountingPage.tsx	87.93% <100.00%> (+0.21%)	⬆️
...rc/pages/workspace/connections/ConnectionsGrid.tsx	90.90% <100.00%> (+81.81%)	⬆️
.../workspace/connections/ExactOnlineWaitlistCard.tsx	100.00% <100.00%> (ø)
...workspace/connections/WorkspaceConnectionsPage.tsx	93.22% <ø> (ø)
...ace/connections/useAccountingConnectionListings.ts	85.96% <100.00%> (+0.25%)	⬆️
... and 2 more
... and 32 files with indirect coverage changes

[inimaga]

@claude review

[dubielzyk-expensify]

This looks weird because there's space on the left on the badge:

It should be more like the badge above on Xero:

[JmillsExpensify]

LGTM

[rayane-d]

LGTM! I think the issues I found are NAB.

[rayane-d]

LGTM and tests well 🚀
Thanks!

Screen.Recording.2026-10-20.at.5.57.32.PM.mov

[melvin-bot]

@carlosmiceli Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[github-actions]

🚧 carlosmiceli has triggered a test Expensify/App build. You can view the workflow run here.

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #103997.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-69aaf74-f8df561-c33da868d6f492e8b21d9adeda665a1a939e4c0d/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-69aaf74-f8df561-2da73a2ed1b3fba7d1c2f595449b33acdcc0806d/index.html

Web 🕸️
https://103997.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/carlosmiceli in version: 9.5.16-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[MelvinBot]

No help site update needed. Exact Online can't be connected yet, so no existing article sentence is now wrong. The new Coming soon / Join waitlist row is a temporary placeholder that explains itself in the app. Document Exact Online when the connector launches.

---

view run

[mitarachim]

Deploy Blocker #104660 was identified to be related to this PR.

[jponikarchuk]

Deploy Blocker #104674 was identified to be related to this PR.

[OSBotify]

🚀 Deployed to staging by https://github.com/carlosmiceli in version: 9.5.18-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	cancelled 🔪

[MelvinBot]

No help site update needed. This PR adds a self-explanatory Exact Online "Coming soon" row with a Join waitlist button, but you still can't connect Exact Online, so no existing article sentence is now wrong. Document Exact Online when the connection flow ships.

---

view run

[OSBotify]

🚀 Deployed to production by https://github.com/grgia in version: 9.5.18-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS