Skip to content

Fix empty "Upload Additional Documents" page in NonUSD owner flow#91289

Open
yusufdeveloper2903 wants to merge 1 commit into
Expensify:mainfrom
yusufdeveloper2903:yusufdeveloper2903/fix-90505-empty-documents-page
Open

Fix empty "Upload Additional Documents" page in NonUSD owner flow#91289
yusufdeveloper2903 wants to merge 1 commit into
Expensify:mainfrom
yusufdeveloper2903:yusufdeveloper2903/fix-90505-empty-documents-page

Conversation

@yusufdeveloper2903
Copy link
Copy Markdown
Contributor

Explanation of Change

In the NonUSD (Corpay) bank account flow, the beneficial owner "Upload Additional Documents" sub-step could appear with no required upload fields, no requirements, and the user could skip it without entering anything.

The Documents page renders only four upload sections, each gated by getNeededDocumentsStatusForBeneficialOwner(currency, country, nationality). For workspace currency GBP, bank country GB, owner nationality GB, all four flags collapse to false, so the page shows only a heading and two paragraphs — an empty page.

The parent (BeneficialOwnerDetailsFormPages.tsx) was supposed to skip that page, but its skip rule was a narrow hardcoded country === GB && nationality === GB check that (1) did not match the actual render predicate, so the two could drift apart, and (2) read the bank country from the form draft only. When the country lives only in achData (e.g. after server hydration of the reimbursement account, where CountryFullStep does not re-write the draft because the value already equals the default), the draft value is '', the GB && GB clause is false, the page is not skipped, and the empty page renders.

This change derives the skip predicate from the same getNeededDocumentsStatusForBeneficialOwner function that drives the page's render, and reads country/currency through the same getCurrencyForNonUSDBankAccount helper already used by Documents.tsx and Confirmation.tsx (which falls back to achData.country). The Documents sub-step is now skipped exactly when all four document flags are false — i.e. exactly when the page would be empty — so "page is skipped" and "page is empty" can no longer diverge. This resolves the reported GBP/UK/UK case and is future-proof for any other combination where no documents are required.

Fixed Issues

$ #90505
PROPOSAL: #90505 (comment)

Tests

  1. Open or create a workspace whose output currency is non-USD and requires Corpay, e.g. GBP.
  2. Go to Workspace settings → Workflows → Connect bank account to start the NonUSD (Corpay) Add bank account flow.
  3. In the country step, select United Kingdom (GB) as the bank account country, and continue through the business-info steps to the Owner info step.
  4. Add/enter a beneficial owner with Nationality = United Kingdom (GB) and a US address, then continue through the owner sub-steps (Name → Nationality → Ownership % → Date of birth → Address).
  5. Tap Next on the Address sub-step and verify the flow goes straight to the Confirmation step — the empty "Upload Additional Documents" page is not shown.
  6. Regression check: repeat with a beneficial owner whose Nationality is not GB (e.g. France), or with a workspace currency of EUR / AUD / CAD, and verify the "Upload Additional Documents" page is shown with the correct required upload field(s).
  7. Back navigation: from Confirmation, press Back and verify it skips the hidden Documents step and lands on the previous visible step.
  • Verify that no errors appear in the JS console

Offline tests

This change adds no API calls. The skip decision is computed purely from locally available Onyx data (reimbursementAccountDraft, reimbursementAccount.achData, and policy.outputCurrency), so it behaves identically online and offline.

  1. Turn off the network connection.
  2. Run the steps above for the GBP/UK/UK case.
  3. Verify the empty "Upload Additional Documents" page is not shown, exactly as when online.

QA Steps

Same as the Tests section above (run on staging).

  • 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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

After Fix:
evidence_fix_after

evidence_02_fix_confirmation

Before Fix:
evidence_bug_before

evidence_03_bug_empty_documents

Comparison:
evidence_comparison

Derive the Documents skip predicate from getNeededDocumentsStatusForBeneficialOwner
so "page is skipped" can no longer drift from "page is empty", and read the bank
country via getCurrencyForNonUSDBankAccount (achData-aware) instead of the draft
only, so the predicate also fires when country lives only in achData.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@yusufdeveloper2903 yusufdeveloper2903 requested review from a team as code owners May 21, 2026 10:40
@melvin-bot melvin-bot Bot requested review from abzokhattab and heyjennahay and removed request for a team May 21, 2026 10:40
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 21, 2026

@abzokhattab 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]

@melvin-bot melvin-bot Bot requested review from a team and youssef-lr and removed request for a team May 21, 2026 10:40
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 21, 2026

@youssef-lr 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]

function BeneficialOwnerDetailsFormPages({stepNames, policyID, onFinished, backTo}: BeneficialOwnerDetailsFormPagesProps) {
const {translate} = useLocalize();
const [reimbursementAccountDraft] = useOnyx(ONYXKEYS.FORMS.REIMBURSEMENT_ACCOUNT_FORM_DRAFT);
const [reimbursementAccount] = useOnyx(ONYXKEYS.REIMBURSEMENT_ACCOUNT);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ PERF-11 (docs)

useOnyx(ONYXKEYS.REIMBURSEMENT_ACCOUNT) subscribes to the entire reimbursement account object, but only achData.country is used (via getCurrencyForNonUSDBankAccount). This causes unnecessary re-renders when any unrelated field on the reimbursement account changes.

Use a selector to extract only the needed field:

const [reimbursementAccountCountry] = useOnyx(ONYXKEYS.REIMBURSEMENT_ACCOUNT, {
    selector: (ra) => ra?.achData?.additionalData?.country,
});

Then pass the extracted value directly instead of the full object, or restructure getCurrencyForNonUSDBankAccount to accept the primitive values it actually needs.


Reviewed at: 16e329e | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

const {translate} = useLocalize();
const [reimbursementAccountDraft] = useOnyx(ONYXKEYS.FORMS.REIMBURSEMENT_ACCOUNT_FORM_DRAFT);
const [reimbursementAccount] = useOnyx(ONYXKEYS.REIMBURSEMENT_ACCOUNT);
const [policy] = useOnyx(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ PERF-11 (docs)

useOnyx(ONYXKEYS.COLLECTION.POLICY + policyID) subscribes to the entire policy object, but only outputCurrency is used (via getCurrencyForNonUSDBankAccount). Policy objects are large and change frequently, causing unnecessary re-renders.

Use a selector to extract only the needed field:

const [outputCurrency] = useOnyx(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`, {
    selector: (p) => p?.outputCurrency,
});

Then pass the extracted primitive value directly instead of the full policy object.


Reviewed at: 16e329e | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

@yusufdeveloper2903
Copy link
Copy Markdown
Contributor Author

Valid principle (PERF-11), but the suggested path is wrong — country is at achData.country
not achData.additionalData.country, so applying it verbatim would break the skip logic. Also, this matches the pattern used by all 12 callers of getCurrencyForNonUSDBankAccount; optimizing it properly means refactoring the shared helper + all call sites, which is out of scope here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant