[No QA] Docs updates for E/A#76033 KYB verification documents step for USD bank accounts

[MelvinBot]

Summary

Updates the Connect a US Business Bank Account help article to document the new in-app Verification step added in #76033. When automated verification fails during USD business bank account setup, users are now asked to upload the required documents (e.g., Tax ID Verification, Name Change Document, Company address verification, Address verification, Date of birth verification) directly in the flow, rather than only via Concierge.

Changes

• Rewrote the Documentation review item under What to expect after submitting your bank account details to describe the in-app Verification step, the Choose file / Verify actions, and the Finish via chat alternative.
• Expanded the FAQ Why am I asked for documents when adding my bank account? to list the documents that may be requested and how to submit them.
• Added retrieval keywords (verification documents, Tax ID Verification, address verification, verification failed, KYB documents).

Related

• Source PR: feat: Gather KYB documents when verification fails for USD BA's #76033
• Issue: [Due for payment 2026-06-17] Add KYB document uploads when checks fail #75707

All UI labels (Verification, Choose file, Verify, Finish via chat, and the document section titles) were verified against the exact localized strings merged in #76033. This step only appears for accounts that fail automated verification (a manually set account state), so it could not be reached in the live UI for screenshots.

@MrMuzyk, please review the files changed and confirm they reflect the current behavior. Then mark this PR Ready for review.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://1744e82b.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/wallet-and-payments/Connect-a-Business-Bank-Account

[VickyStash]

@MrMuzyk, please review the files changed and confirm they reflect the current behavior. Then mark this PR Ready for review.

I've reviewed it, makes sense to me but I can't open this PR for review, I don't have such an option cc @madmax330

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR improves the "Connect a Business Bank Account" article by replacing a vague description of the document verification step with specific, actionable guidance. The changes add new keywords for discoverability, expand the FAQ answer for "Why am I asked for documents?" with a detailed list of possible document requests, and update the inline verification step to describe the new in-app upload flow. The changes are well-structured and align with governance standards.

Scores Summary

• Readability: 9/10 - The new content is clear, scannable, and well-organized. The bulleted list of document types with dash-separated explanations is easy to parse. The inline step (line ~98) is information-dense but still readable.
• AI Readiness: 9/10 - New keywords ("verification documents", "Tax ID Verification", "address verification", "verification failed", "KYB documents") are realistic search phrases that match what users would actually type. YAML metadata including internalScope is present and well-scoped. Headings remain task-based and use question words as required.
• Style Compliance: 9/10 - UI element references use bold formatting correctly (Choose file, Verify, Finish via chat, Verification). Capitalization appears to match UI conventions. Terminology is consistent with naming conventions (e.g., "Concierge", "Workspace Admin").

Key Findings

• The expanded FAQ answer listing specific document types (Tax ID Verification, Name Change Document, Company address verification, Address verification, Date of birth verification) is a strong improvement for both human readers and AI retrieval. Users searching for these specific verification failures will now find relevant guidance.
• Bold formatting is applied consistently to all UI elements: Choose file, Verify, Finish via chat, and Verification.
• The new content correctly avoids placing links inside numbered step instructions, consistent with authoring guidelines.
• Minor observation: The phrase "Company address verification" uses lowercase "address verification" while "Tax ID Verification" and "Date of birth verification" capitalize "Verification". This appears intentional (matching UI labels), but worth confirming that these labels exactly match what users see in the product.
• The repeated instruction ("Upload each requested file with Choose file, then click Verify") appears in both the step 1 update (line ~98) and the FAQ expansion (line ~167). This duplication is acceptable since users may land on either section independently, but could be consolidated if brevity is preferred.

Recommendations

1. Confirm that the bold document type names (e.g., Tax ID Verification, Name Change Document, Address verification) exactly match the labels shown in the product UI, including capitalization. Per naming conventions, these must be literal matches.
2. Consider whether the duplication of the "Upload each requested file..." instruction across two sections is intentional. If so, no action needed -- it aids standalone readability of each section.

Files Reviewed

• docs/articles/new-expensify/wallet-and-payments/Connect-a-Business-Bank-Account.md — Keywords expanded with verification-related search terms; step 1 under "After you submit your details" rewritten to describe in-app document upload flow; FAQ answer for "Why am I asked for documents?" expanded with specific document types and upload instructions. All changes are well-aligned with governance standards.

[madmax330]

@stephanieelliott can you review the AI comments?

[stephanieelliott]

LGTM! I will sit on this til the change hits prod, then add another reviewer to merge it.

[melvin-bot]

Concierge reviewer checklist:

• I have verified the accuracy of the article
  • The article is within a hub that makes sense, and the navigation is correct
  • All processes, screenshots, and examples align with current product behavior.
  • All links within the doc have been verified for correct destination and functionality.
• I have verified the readability of the article
  • The article's language is clear, concise, and free of jargon.
  • The grammar, spelling, and punctuation are correct.
  • The article contains at least one image, or that an image is not necessary
• I have verified the formatting of the article
  • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
  • The article has proper text spacing and breaks for readability.
• I have verified the article has the appropriate tone and style
  • The article's tone is professional, friendly, and suitable for the target audience.
  • The article's tone, terminology, and voice are consistent throughout.
• I have verified the overall quality of the article
  • The article is not missing any information, nor does it contain redundant information.
  • The article fully addresses user needs.
• I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @RachCHopkins

[melvin-bot]

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

[RachCHopkins]

LGTM!

[OSBotify]

🚀 Deployed to staging by https://github.com/RachCHopkins in version: 9.4.8-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	failure ❌
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/RachCHopkins in version: 9.4.8-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/puneetlath in version: 9.4.8-3 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅