[Due for payment 2025-09-19] [$250] Only show "Go to Expensify Classic to manage your settings" for Certinia

[trjExpensify]

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: v9.1.94-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: No
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @davidcardoza
Slack conversation (hyperlinked to channel name): #convert

Action Performed:

1. Sign-up for a new account
2. Choose "Manage my team's expenses"
3. Choose 1000+
4. Complete onboarding
5. Switch to Classic
6. Choose "Other" in the Inbox task for accounting connection.
7. Click "Try New Expensify" to switch back to NewDot
8. Go to the workspace settings
9. Click Accounting
10. Observe the "Go to Expensify Classic to manage..." message
11. Click More features
12. Observe the locks on categories, tags etc.

Expected Result:

As all other proper accounting integrations have now been built in NewDot, only Certinia (FinancialForce) should be included in the logic to prompt to go back to Classic to manage the integration settings.

Actual Result:

The admin can't enable or manage coding like categories, tags, tax rates etc in NewDot.

Note: This logic seems to include indirect integrations as well, which is the driving force behind these blocks in accounting etc.

Workaround:

Use Classic.

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
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

2025-08-14_21-09-10.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021956097357218726178
• Upwork Job ID: 1956097357218726178
• Last Price Increase: 2025-08-14

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (External)

[melvin-bot]

Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

[Krishna2323]

🚨 Edited by proposal-police: This proposal was edited at 2025-08-14 21:02:02 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

Only show "Go to Expensify Classic to manage your settings" for Certinia

What is the root cause of that problem?

• New feat

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

• We need to only pass FinancialForce/Certinia here:
  

  App/src/pages/workspace/accounting/PolicyAccountingPage.tsx

  Line 109 in 62542b0

  const hasUnsupportedNDIntegration = !isEmptyObject(policy?.connections) && hasUnsupportedIntegration(policy, accountingIntegrations);

• Check all other uses of hasUnsupportedIntegration and update those too.
• We can also update hasUnsupportedIntegration to use default value of just Certinia.
• We can update the workspace.accounting.goToODToSettings translations if required.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

What alternative solutions did you explore? (Optional)

Result

[nkdengineer]

🚨 Edited by proposal-police: This proposal was edited at 2025-08-14 22:27:29 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

The admin can't enable or manage coding like categories, tags, tax rates etc in NewDot.

What is the root cause of that problem?

We are considering CONST.POLICY.CONNECTIONS.NAME as UnsupportedIntegration here

App/src/libs/PolicyUtils.ts

Lines 1272 to 1274 in 8fff396

	function hasUnsupportedIntegration(policy: Policy | undefined, accountingIntegrations?: ConnectionName[]) {
	return !(accountingIntegrations ?? Object.values(CONST.POLICY.CONNECTIONS.NAME)).some((integration) => !!policy?.connections?.[integration]);
	}

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

We should create a new const like UNSUPPORTED_INTEGRATIONS

        UNSUPPORTED_INTEGRATIONS: {
            NAME: {
                CERTINIA: 'certinia',
            }
        },

Then update this line to

    const connectionNames = CONST.POLICY.UNSUPPORTED_INTEGRATIONS.NAME;

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

What alternative solutions did you explore? (Optional)

NA

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[phr555]

PROPOSAL

Please re-state the problem that we are trying to solve in this issue.
The admin can't enable or manage coding like categories, tags, tax rates etc in NewDot.

What is the root cause of that problem?

App/src/pages/workspace/accounting/PolicyAccountingPage.tsx

Line 107 in 8c5d0e9

const hasUnsupportedNDIntegration = !isEmptyObject(policy?.connections) && hasUnsupportedIntegration(policy, accountingIntegrations);

hasUnsupportedNDIntegration should check our policy connections against a list of non direct accounting integrations. Instead, it's comparing the policy connections against a list of the direct accounting integrations in the src/CONST/inde.js file:

CONNECTIONS: {
            NAME: {
                // Here we will add other connections names when we add support for them
                QBO: 'quickbooksOnline',
                QBD: 'quickbooksDesktop',
                XERO: 'xero',
                NETSUITE: 'netsuite',
                SAGE_INTACCT: 'intacct',
            },

Either this list is missing a key value pair (OTHER: 'other'?), or we should have a separate object listing non-direct connections that exist within the other option.

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

Maybe add key OTHER: 'other' to the NAME object above, but I would want to debug the code and better understand if there are multiple possible non direct integrations that we want to check for within 'other'.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
N/A

What alternative solutions did you explore? (Optional)