[No QA] Create Reimbursement-Payment-Methods.md

[stephanieelliott]

Related: https://github.com/Expensify/Expensify/issues/601019

Created to address:

2. Reimbursement Methods & International Payments Guide

Expected Impact: HIGH

Signal	Evidence
Search data	Consistently thinnest results (605-700 bytes) for "SGD reimbursement", "global reimbursements", "direct ach", "direct reimbursement", "can i get reimbursed with a check"
Escalation data	167 low-confidence "Reimbursements" escalations/week -- international bank issues, payment method confusion, missing status updates
Concierge friction	Reimbursement delays/confusion is a recurring friction theme

Recommendation: Create/expand reimbursement content covering:

• All available payment methods (ACH, check, global/international)
• Currency-specific setup guides (especially non-USD)
• Reimbursement status tracking and timeline expectations
• Common failure reasons and resolution steps
• Add keyword coverage for "direct reimbursement", "global", "SGD", "CAD", "check payment"

Est. weekly impact: 50-70 fewer escalations + highest search gap closure

[github-actions]

Readability violation: This line says "one of two methods," but the article describes three payment methods: ACH reimbursement, global reimbursement, and Pay elsewhere. The intro paragraph (line 8) correctly lists all three.

Suggested change

	Workspace Admins can reimburse approved reports in Expensify using one of two methods:
	Workspace Admins can reimburse approved reports in Expensify using one of three methods:

[github-actions]

AI Readiness / Heading hierarchy violation: This section uses # (H1) but the equivalent parallel section "ACH reimbursement timelines" on line 88 uses ## (H2). Parallel sections should use the same heading level for consistent hierarchy. Since all body sections in this article use ##, this should also be ##.

Suggested change

	---
	## Global Reimbursement timelines

[github-actions]

AI Readiness / Readability violation: This H1 heading ("Reimbursement payment methods") repeats the YAML title nearly verbatim, creating redundancy. In sibling articles (e.g., Pay-Expenses.md, Connect-a-Business-Bank-Account.md), the first H1 after the intro introduces a distinct section topic rather than restating the title. Consider either removing this heading entirely (letting the intro stand on its own before the first real section) or renaming it to introduce the first substantive section, such as # Reimbursement method types.

[github-actions]

Readability violation (possible broken link): The URL contains a double hyphen (Global-Reimbursement--Singapore) which looks like a typo. This may result in a broken link. Please verify the correct file name.

Suggested change

	- [CAD](https://help.expensify.com/articles/new-expensify/wallet-and-payments/Global-Reimbursement-Canada) (Canada)
	- [SGD](https://help.expensify.com/articles/new-expensify/wallet-and-payments/Global-Reimbursement-Singapore) (Singapore)

[github-actions]

Readability violation (factual inconsistency): This line lists "USD, CAD, GBP, EUR, or AUD" but omits SGD (Singapore), which is listed as a supported currency in both the "What reimbursement payment types are available" section (line 44) and the "Supported Currencies" section (line 108). Please add SGD for consistency.

Suggested change

	Workspace business bank accounts can be connected in USD, CAD, GBP, EUR, or AUD. Global reimbursement supports member bank accounts in 190+ countries.
	Workspace business bank accounts can be connected in USD, CAD, GBP, EUR, AUD, or SGD. Global reimbursement supports member bank accounts in 190+ countries.

[github-actions]

AI Readiness / Heading hierarchy violation: The "ACH reimbursement timelines" section uses ## (H2), making it appear subordinate to the previous H2 sections ("How Workspace Admins pay multiple reports in bulk"). However, this is a standalone top-level topic, not a subsection of bulk payments. To fix the hierarchy, either:

• Promote this to # (H1) to match the "Global Reimbursement timelines" section, or
• Demote "Global Reimbursement timelines" to ## (H2) to match this one.

Both timeline sections should use the same heading level since they are parallel topics.

[github-actions]

Readability violation: The bullet list describes only two items (direct reimbursement and Pay elsewhere), but the article actually covers three distinct methods: ACH reimbursement, global reimbursement, and Pay elsewhere. Direct reimbursement is presented as a single category here but is later split into ACH and global reimbursement. Consider adding a third bullet for global reimbursement, or explicitly noting that "direct reimbursement" includes both ACH and global variants. As written, a reader may not understand the relationship between the three methods introduced in the opening paragraph and the two listed here.

[github-actions]

Readability violation (formatting): The bullet items on lines 89-90 have an extra leading space before the -, creating inconsistent indentation compared to the rest of the article. This could cause unexpected Markdown rendering.

Suggested change

	- **Rapid Reimbursement:** Eligible payments are typically received by the member in one business day. Applies to payments under $100 when total withdrawals are under $10,000 in the past 24 hours.
	- **Rapid Reimbursement:** Eligible payments are typically received by the member in one business day. Applies to payments under $100 when total withdrawals are under $10,000 in the past 24 hours.
	- **Standard ACH reimbursement:** All other ACH payments are typically received by the member in four to five business days.

[OSBotify]

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

Updated articles:

• articles/new-expensify/wallet-and-payments/Reimbursement-Payment-Methods

[github-actions]

HelpDot Documentation Review

Overall Assessment

This is a well-structured new article that fills a significant content gap around reimbursement payment methods, timelines, and supported currencies. The writing is clear, the step-by-step instructions are easy to follow, and the article directly addresses the search and escalation data cited in the PR description. There are a few structural and consistency issues that should be resolved before merging.

Scores Summary

• Readability: 8/10 - Clear, well-organized prose at an appropriate reading level. Step-by-step instructions are concise and scannable. Minor issues: the intro states "one of two methods" then effectively describes three options (ACH, global, Pay elsewhere), which could momentarily confuse readers even though ACH and global are subcategories of "direct reimbursement." The relationship between these concepts could be made slightly more explicit.
• AI Readiness: 7/10 - Good YAML metadata with a well-formed internalScope and strong keyword coverage. However, the heading hierarchy has an inconsistency that will hurt AI parsing (see Key Findings), and some FAQ headings lack question marks which reduces their effectiveness as self-contained question-answer pairs for retrieval.
• Style Compliance: 7/10 - Consistent use of Expensify terminology (Workspace Admin, member, Pay elsewhere). Formatting and bold usage for UI elements is correct throughout. Deductions are for the heading level inconsistency, a likely typo in a link, and a minor content inconsistency in the final FAQ answer.

Key Findings

Issues to address:

1. Heading hierarchy inconsistency (H1 vs H2): The "ACH reimbursement timelines" section uses ## (H2), but the parallel "Global Reimbursement timelines" section uses # (H1). These are sibling sections covering the same type of content (timelines) and should both use ##. Similarly, "Supported Currencies for Global Reimbursement" is a ## under the # Global Reimbursement timelines heading, which creates an unintended parent-child relationship. Per HelpDot conventions, articles should use # only for major top-level sections and ## for subsections. The recommended structure would be to make "Global Reimbursement timelines" an ## heading to match "ACH reimbursement timelines."

2. Broken or malformed link to Singapore guide: The Supported Currencies section links to Global-Reimbursement--Singapore (note the double dash). This is likely a typo and should be Global-Reimbursement-Singapore. Additionally, no Global-Reimbursement-Singapore.md file currently exists in the repository, so this link will 404. Either the file needs to be created as a companion PR, or the link should be removed or noted as forthcoming.

3. FAQ headings missing question marks: All four FAQ headings are phrased as questions but lack terminal question marks (e.g., "What is direct reimbursement" should be "What is direct reimbursement?"). This is important for AI retrieval since these headings serve as the question in a Q&A pair.

4. Currency list inconsistency in final FAQ answer: The last FAQ answer ("When is Pay elsewhere used") ends with: "Workspace business bank accounts can be connected in USD, CAD, GBP, EUR, or AUD." This omits SGD, which is listed as a supported currency earlier in the article. This creates a contradiction within the same document.

5. Minor whitespace issue: The bullet list under "ACH reimbursement timelines" has a leading space before the dash on both items ( - **Rapid Reimbursement:**). While this may render correctly in most Markdown parsers, it is inconsistent with the formatting elsewhere in the article.

Positive aspects:

• The article structure logically progresses from concepts to actions to timelines to FAQ, which matches how a Workspace Admin would consume this information.
• Excellent cross-linking to related articles (report statuses, bank account setup, global reimbursement setup, and all six currency-specific guides).
• The keyword list in the YAML front matter directly addresses the thin search results cited in the PR description (SGD, global reimbursement, direct reimbursement, check payment concepts).
• The internalScope field is well-formed with clear audience, coverage, and exclusions.
• Step-by-step instructions for both single and bulk payment flows are clear, numbered correctly, and include both web and mobile navigation context.
• The Rapid Reimbursement eligibility criteria are specific and actionable (under $100, under $10,000 in 24 hours).

Recommendations

1. [Must fix] Change # Global Reimbursement timelines to ## Global Reimbursement timelines to maintain consistent heading hierarchy.
2. [Must fix] Fix the double-dash typo in the Singapore link (Global-Reimbursement--Singapore to Global-Reimbursement-Singapore) and confirm the target file exists or will be created.
3. [Must fix] Add question marks to all FAQ headings.
4. [Must fix] Add SGD to the currency list in the final FAQ answer, or remove the trailing paragraph from that FAQ entry since it partially duplicates earlier content.
5. [Should fix] Remove the leading space before the dashes in the ACH reimbursement timelines bullet list for consistent formatting.
6. [Consider] In the intro paragraph under "Reimbursement payment methods," consider briefly clarifying that ACH and global reimbursement are both forms of direct reimbursement to make the two-method framing immediately clear.

Files Reviewed

• docs/articles/new-expensify/wallet-and-payments/Reimbursement-Payment-Methods.md (new file, 143 lines) -- Strong foundational article with a few structural issues to resolve before merge.

Review based on the proposed diff only. Compared against existing HelpDot articles in the same directory for style and convention benchmarking.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4bff5f75c0

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Replace broken Singapore reimbursement doc link

The SGD entry points to .../Global-Reimbursement--Singapore, but there is no matching article under docs/articles/new-expensify/wallet-and-payments (only U.S., Canada, UK, Europe, and Australia guides exist), so users following this link will hit a dead page instead of setup instructions. Please link to an existing destination or remove the SGD link until the Singapore guide exists.

Useful? React with 👍 / 👎.