Skip to content

[Design Doc] Add global reimbursement functionality to NewDot #20459

@JmillsExpensify

Description

@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

Frontend PHASE 2

Frontend PHASE 3

PHASE 4

Backend

Metadata

Metadata

Labels

NewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type
No fields configured for issues without a type.

Projects

Status

Done

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions