[No QA] Docs updates for E/A#97333 AUS Corpay certification TMD, illion report, bank statement

[MelvinBot]

Docs updates for E/A#97333

This draft updates the NewDot Global Reimbursement - Australia help article to reflect the AUS Corpay certification changes introduced in #97333.

What changed in the PR

The PR updated the AUD (Australia) non-USD bank account / Corpay setup flow with three user-facing changes:

1. TMD added to the disclosure paperwork — the disclosure documents shown during setup now include Corpay's Target Market Determination (TMD) alongside the existing Financial Services Guide (FSG) and Product Disclosure Statement (PDS).
2. illion report requirement for signers — both signers must be listed as directors on the company's illion report; they can't be any two people at the business.
3. Bank statement upload — a recent bank statement, dated within the last three months, is now requested for the business bank account being connected.

Help site changes made

Updated docs/articles/new-expensify/wallet-and-payments/Global-Reimbursement-Australia.md:

• Added the illion report signer requirement and the recent-bank-statement requirement to Australia Document Requirements.
• Added a note under Add Director Information that both signers must be listed as directors on the company's illion report.
• Added a new Review the Disclosure Paperwork and Provide a Bank Statement step documenting the FSG, PDS, and TMD disclosure documents plus the recent bank statement, and renumbered the subsequent steps.

@madmax330, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

[MelvinBot]

I checked the CI on this PR. Every code/content check is passing (build, check, verify, validate, dryRun, spellcheck, CLA, verifySignedCommits). There's nothing to fix by pushing.

The only red check is Check independent approval, which isn't a code failure — it's a gating check that stays red until an independent reviewer approves the PR. It can't be resolved with a commit; it clears once this docs update gets a review/approval.

Next step: review the changed help article and, if it looks good, approve the PR (or reply @MelvinBot mark this PR as ready for review per the description). That will satisfy the approval gate.

[madmax330]

LGTM, all you @stephanieelliott

[github-actions]

Heading rule violation (multiple # headings + non-task-based heading): Per HELP_AUTHORING_GUIDELINES.md Sections 2 and 4, an article may have only one # heading (the title) plus an optional # FAQ — all other sections must use ##. Additionally, Step N: prefixes are a forbidden generic/step-style heading. Change this newly added heading to a task-based ##, e.g. ## How to review the disclosure paperwork and provide a bank statement.

[MelvinBot]

Done in 44de7a1 — converted to a task-based ## heading: ## How to review the disclosure paperwork and provide a bank statement. Also converted the pre-existing # Step 1/2 and renumbered # Step 4/5 headings to task-based ## so the whole article now follows the single-#-heading rule.

[github-actions]

Heading rule violation: This renumbered heading still uses a second # heading with a Step N: prefix. Per HELP_AUTHORING_GUIDELINES.md Sections 2 and 4, use a single # title and convert this to a task-based ##, e.g. ## How to confirm test transactions.

[MelvinBot]

Done in 44de7a1 — now ## How to confirm test transactions.

[github-actions]

Heading rule violation: This renumbered heading still uses a second # heading with a Step N: prefix. Per HELP_AUTHORING_GUIDELINES.md Sections 2 and 4, use a single # title and convert this to a task-based ##, e.g. ## How to start sending global reimbursements.

[MelvinBot]

Done in 44de7a1 — now ## How to start sending global reimbursements.

[github-actions]

Redundancy / clarity: This "Recent bank statement (dated within the last three months)" requirement duplicates the existing "Bank statement for direct debit setup" line above and is also restated in the new Step 3 body (line 83). Per HELP_AUTHORING_GUIDELINES.md Section 6 (avoid vague/duplicated wording), consolidate the two bank-statement bullets into one clear requirement to avoid confusing the reader about how many statements are needed.

[MelvinBot]

Done in 44de7a1 — consolidated the two bullets into one: ✅ Recent bank statement (dated within the last three months) for the business bank account you're connecting, used for direct debit setup. It's now stated once in Document Requirements and referenced once in the setup flow.

[MelvinBot]

🤖 There's nothing to fix here in code — all real CI checks are passing (build, check, spellcheck, verify, validate, dryRun, etc.).

The only failing check is Check independent approval (the Verify peer review step). That check fails because the PR doesn't yet have an independent human approval — it is not caused by anything in the diff, and no code push can make it pass.

To clear it: this draft needs to be marked ready for review and approved by an independent reviewer. Since the PR description already asks you to confirm the docs, once you're satisfied you can comment @MelvinBot mark this PR as ready for review, and then have a reviewer approve it.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR updates the Global Reimbursement - Australia article to reflect the AUS Corpay certification changes: a new TMD disclosure document, an illion report signer requirement, and a recent bank statement requirement. The changes are accurate, well-scoped to a single workflow, and factually clear. The main issues stem from the article pre-existing structural pattern (multiple top-level Step N headings), which the new content extends rather than corrects.

Scores Summary

• Readability: 8/10 - New content is clear, concise, and action-oriented. Minor redundancy: the recent-bank-statement requirement now appears in three places (Document Requirements, new Step 3, and existing Step 2 Upload a Recent Bank Statement).
• AI Readiness: 5/10 - Feature names are spelled out well (FSG, PDS, TMD, illion, Corpay). However, the PR adds a new top-level Step 3: Review the Disclosure Paperwork and Provide a Bank Statement heading, which compounds two governance violations: (1) multiple top-level headings are prohibited (only the title plus FAQ allowed; these should be second-level), and (2) Step N prefixes are a forbidden generic-heading pattern per HELP_AUTHORING_GUIDELINES.md Section 2. The new heading follows the file existing (non-compliant) convention.
• Style Compliance: 7/10 - Bold UI terminology (Financial Services Guide (FSG), etc.) is applied correctly and step renumbering (Steps 3/4/5) is consistent. The new heading uses Title Case rather than the required Sentence case.

Key Findings

• Positive: Changes are accurate, single-workflow, and use exact feature names, which is good for retrieval.
• Positive: New disclosure paragraph correctly uses an explanatory paragraph (not a numbered step), consistent with step and cross-linking rules.
• Issue: New Step 3 heading violates the single top-level heading rule and the forbidden Step 1 generic-heading rule. It should be a task-based second-level heading (e.g., How to review the disclosure paperwork and provide a bank statement).
• Issue: The bank-statement requirement is now duplicated across three sections, which dilutes retrieval precision.

Recommendations

• Convert the new heading (and ideally the surrounding Step headings, since they are being renumbered anyway) from top-level to task-based second-level headings in Sentence case to satisfy the heading hierarchy and casing rules.
• Consolidate the recent-bank-statement mentions to avoid triplication. Keep it in Document Requirements and reference it once in the setup flow.
• Consider whether the new content still fits the existing single-top-level-heading structure or warrants aligning the whole file to governance in a follow-up.

Files Reviewed

• docs/articles/new-expensify/wallet-and-payments/Global-Reimbursement-Australia.md - Accurate content additions; heading structure and casing need adjustment to meet governance.

Note: Detailed line-by-line feedback has been provided as inline comments.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 69213d74cf

ℹ️ 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]

Remove Senior Officer option from AUD signer docs

With this new AUD-specific note saying both signers must be directors on the illion report, the surrounding instructions still tell users they can enter a “Director or Senior Officer” and that Expensify requires two “Directors or Senior Officers.” The current AUD signer flow only asks for director emails and tells users both signers must be listed as directors on the illion report (src/languages/en.ts:4314-4319, rendered in src/pages/ReimbursementAccount/NonUSD/SignerInfo/EnterEmail.tsx:92-95), so leaving the Senior Officer wording in the same section makes the help article internally contradictory for Australian onboarding.

Useful? React with 👍 / 👎.

[MelvinBot]

Good catch — done in 44de7a1. Removed the "or Senior Officer" wording from all three spots in the Add Director Information section so it now consistently says "Director(s)", matching the current AUD signer flow (which only collects director emails and requires both signers be listed as directors on the illion report).

[MelvinBot]

🤖 Nothing has changed since my previous comment — the only failing check is still Check independent approval, which fails because the PR has no independent human approval yet. It is not caused by anything in the diff and no code push can fix it. All real CI checks (build, check, spellcheck, verify, validate, dryRun, etc.) are passing.

To clear it, this draft needs to be marked ready for review and approved by an independent reviewer.

[madmax330]

@MelvinBot can you address the review feedback?

[MelvinBot]

Addressed all the review feedback in 44de7a1:

Heading rule (github-actions bot): Converted every # Step N: heading to a task-based ## heading in sentence case, so the article now uses a single top-level heading and complies with HELP_AUTHORING_GUIDELINES.md §2/§4:

• ## How to connect your Australian bank account
• ## How to submit bank and business information
• ## How to review the disclosure paperwork and provide a bank statement
• ## How to confirm test transactions
• ## How to start sending global reimbursements

(I converted Steps 1 & 2 too, not just the renumbered ones, so the whole file is consistent rather than half-migrated.)

Redundancy (github-actions bot): Consolidated the two bank-statement bullets in Australia Document Requirements into one — ✅ Recent bank statement (dated within the last three months) for the business bank account you're connecting, used for direct debit setup. The requirement is now stated once there and referenced once in the setup flow.

Remove Senior Officer wording (Codex, P2): Dropped "or Senior Officer" from all three spots in Add Director Information. I verified against the current AUD signer flow (src/languages/en.ts rendered in EnterEmail.tsx) — it only collects director emails and requires both signers be listed as directors on the illion report, so "Senior Officer" was contradictory.

Since this is a content-only edit to an existing article (no routing/config or new vocabulary), there were no additional required local checks to run beyond what CI covers. Let me know if you'd like any further tweaks.

[MelvinBot]

🤖 Still nothing to fix in code — the situation is unchanged since my previous comment. All real CI checks pass; the only failing one is Check independent approval (Verify peer review), which fails solely because the PR lacks an independent human approval. No code push can make it pass.

To clear it: mark this draft ready for review and get an independent reviewer to approve it.

[OSBotify]

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

Updated articles:

• articles/new-expensify/wallet-and-payments/Global-Reimbursement-Australia

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.4.55-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/Beamanator in version: 9.4.55-4 🚀

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

Bundle Size Analysis (Sentry):

• Android