Add Certinia FFA vendor matching to workspace features

[ShridharGoel]

Explanation of Change

Adds Certinia FFA as a vendor matching source in the App. The Vendors row in workspace More Features now shows for workspaces with a configured Certinia FFA connection (isConfigured true and hasPSA false), and the Certinia default vendor page reads the synced vendor list through the shared getCertiniaVendors helper.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/680694
PROPOSAL:

Tests

Setup

1. Connect a workspace to Certinia FFA (isConfigured = true, hasPSA = false).
2. Sync the connection so vendor accounts come into connections.financialforce.data.vendors.
3. Enable the vendor matching beta for your test account.
4. Have at least two company cards assigned.

Steps

1. Open Workspace → More Features.
   • FFA connection + beta on → Vendors row is visible.
   • Beta off → row is hidden.
   • PSA connection (hasPSA = true) → row is hidden, even with beta on.
2. Open Workspace → Vendors.
   • Synced Certinia vendors appear in the list.
   • If the list is empty, the Certinia empty-state text shows ("no vendors found").
3. Create a manual expense with a merchant name close to a synced vendor name.
   • The vendor field auto-fills with the matched Certinia vendor.
   • The expense view shows the vendor name.
4. Create a merchant rule with a vendor from the Certinia list.
   • New expenses with that merchant get the rule's vendor.

---

1. Archive a vendor account in Certinia, re-sync.
2. Open an expense that has that vendor set.
   • An "inactive vendor" error shows on the expense/report.

---

1. Create non-reimbursable expenses like this on one report:
   • 2 expenses on card A with matched vendor X
   • 1 expense on card A with matched vendor Y
   • 1 expense on card B with matched vendor X
   • 1 expense on card A with no matched vendor.
2. Export the report to Certinia.
   • Expected: 4 purchase invoices, one per (card, vendor account) group.

---

1. Create a new report.
2. Create a non-reimbursable card expense with an account that is not added as a contact in Certinia.
3. Ensure the merchant added has a matching vendor.
4. Verify that the vendor got updated.
5. Submit and approve the report.
6. Export it to Certinia.
7. Verify that export succeeded even though the report owner/submitter was not added as a contact in Certinia.

• Verify that no errors appear in the JS console

Offline tests

1. Open Workspace > More features while offline.
2. Verify the Vendors row matches the last known connection state from Onyx.

QA Steps

Same as tests.

• 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 followed proper code patterns (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and 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 followed the guidelines as stated in the Review Guidelines
• 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 a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• 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.
• 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

MacOS: Chrome / Safari

See https://github.com/Expensify/Integration-Server/pull/9405

Related PRs

• Integration-Server
• Auth
• Web-Expensify
• App [This]

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
...ages/workspace/WorkspaceMoreFeaturesPage/index.tsx	68.21% <ø> (ø)
src/libs/PolicyUtils.ts	81.90% <94.11%> (+0.19%)	⬆️
...ting/certinia/export/CertiniaDefaultVendorPage.tsx	0.00% <0.00%> (ø)
... and 6 files with indirect coverage changes