[Design Doc] Add global reimbursement functionality to NewDot

[JmillsExpensify]

Design Document for review is here

Problem statement
Control policies on New Dot do not support payments for companies in our non US markets (UK, Europe, Australia etc.). These companies can in fact pay in-app but they cannot set up their BBA in New Dot, so effectively they cannot access international payments as a feature unless they start on Classic. This means Control policies on New Dot are not at feature parity with Classic. Till we have this, those customers that use global reimbursements on Classic cannot be migrated. Further any new lead that needs this cannot stay on New Dot. If we want to convert them, we will have to send them to Classic.

A secondary problem is that the existing non USD BBA setup flow on Classic is sub-optimal on two levels:

1. The UX, which is a docusign power form as outlined is clunky to navigate and is not on-brand or best-in-class from a UX perspective
2. The process flow itself introduces several time traps as we rely on the customer to be thorough in their submission but wait to hear from the Corpay team if in fact, they were, which takes days, sometimes weeks.

Solution
Bring the setup of non USD BBAs to New Dot. Build the UI to collect the information and documents in product and use Corpay APIs to get the data over to them, and listen to their webhooks to get notified when approved

Implementation Issues:

Frontend

Phase 1

• [HOLD for payment 2024-11-01] [GR Phase 1] Create reusable “PushRowWithModal” component #50895
• [HOLD for payment 2024-11-11] [GR Phase 1] Create reusable “UploadFile” component #50894
• [HOLD for payment 2024-11-07] [HOLD for payment 2024-10-30] [GR Phase 1] Create empty components for all 6 steps and put them together creating a ‘frame’ of the whole process #50893
• [HOLD for payment 2024-10-29] [GR Phase 1] Add a mechanism that allows DEVS and QAs ONLY to connect accounts that are non USD #50892

Frontend PHASE 2

• [HOLD for payment 2024-12-03] [GR Phase 2] Step 6 Agreements and finish screen (without API calls) #50902
• [$250] [HOLD for payment 2024-11-26] [GR Phase 2] Step 5 Director information screen (without API calls) #50901
• [HOLD for payment 2024-11-29] [GR Phase 2] Step 4 Beneficial owner screen (without API calls) #50900
• [HOLD for payment 2024-11-20] [GR Phase 2] Step 3 Business info screen (without save API call) #50899
• [HOLD for payment 2024-11-26] [GR Phase 2] Step 2 Bank account details screen (without API calls) #50898
• [HOLD for payment 2024-11-07] [GR Phase 2] Step 1 Select your country (without API calls) #50897

Frontend PHASE 3

• [GR Phase 3] Navigate user to correct step when returning to process #50910
• [GR Phase 3] Step 6 - navigation, default data, logic and API call to save it #50909
• [GR Phase 3]. Step 5 enter signer info - chat view #50908
• [GR Phase 3] Step 5 - navigation, default data, logic and API call to save it #50907
• [GR Phase 3] Step 4 - navigation, default data, logic and API call to save it #50906
• [GR Phase 3] Step 3 - navigation, default data, logic and API call to save it #50905
• [GR Phase 3] Step 2 - navigation, default data, validation logic and API call to save it #50904
• [GR Phase 3] Step 1 - navigation, default data logic and API call to save data #50903

PHASE 4

• [GR Phase 4] Glue together Connect Bank Account screen (pre-step 1) with freshly created frame #50912
• [GR Phase 4] Connect bank account screen changes (pre-step 1) - UI #50911

Backend

• https://github.com/Expensify/Expensify/issues/436577
• https://github.com/Expensify/Expensify/issues/436579
• https://github.com/Expensify/Expensify/issues/436582
• https://github.com/Expensify/Expensify/issues/436583
• https://github.com/Expensify/Expensify/issues/436584
• https://github.com/Expensify/Expensify/issues/436586

[melvin-bot]

Current assignee @JmillsExpensify is eligible for the NewFeature assigner, not assigning anyone new.

[JmillsExpensify]

Adding myself to keep track of this for BugZero.

[JmillsExpensify]

Still on the radar, though the immediate focus is completing the feature in OldDot.

[JmillsExpensify]

@nikihatesgh Did you want to take this one over?

[JmillsExpensify]

Posted in Slack asking for volunteers. I'm going to remove my assignment though.

[nikihatesgh]

This is not going to be prioritized by EOY so with the change of focus for 2024 I am closing this out and we can pick it back up when GR is prioritized as a feature to be added to NewDot.

[AndrewGable]

I have read and reviewed this Design Doc!

[AndrewGable]

I have read and reviewed this Design Doc!

[madmax330]

Starting implementation this week

[ryanschaffer]

I have read and reviewed this Design Doc!

[heyjennahay]

I have read and reviewed this Design Doc!

[madmax330]

Implementation is ongoing

[madmax330]

Implementation is ongoing

[madmax330]

Same

[madmax330]

Aiming to get it done by Dec 1st.

[madmax330]

Implementation is still ongoing

[madmax330]

Same

[madmax330]

Same

[madmax330]

Working on implementation still