Skip to content

[No QA] [Hold for feature] [No QA] Update help docs for Release 1: Vendor Matching for QuickBooks Online (QBO)#96350

Open
MelvinBot wants to merge 7 commits into
mainfrom
claude-qboVendorMatchingR1
Open

[No QA] [Hold for feature] [No QA] Update help docs for Release 1: Vendor Matching for QuickBooks Online (QBO)#96350
MelvinBot wants to merge 7 commits into
mainfrom
claude-qboVendorMatchingR1

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Design GH for image: https://github.com/Expensify/Expensify/issues/660973 (

Details

Documents the Release 1 (QuickBooks Online) vendor matching feature for non-reimbursable company card expenses. Per the request on the tracking issue, vendor matching is documented as a standalone help article rather than being folded into the general QBO configuration doc.

What changed

  • New article new-expensify/connections/quickbooks-online/Vendor-Matching.md (QuickBooks Online Vendor Matching) covering:
    • Prerequisites (QBO connected + Credit/Debit card export type; Vendor field is Admin-only)
    • The Vendors workspace tab (below Taxes, above Workflows; visibility controlled by the export setting)
    • Setting a Default vendor fallback
    • How vendors are assigned (Merchant Rule → fuzzy match → manual selection; Concierge system message)
    • Export precedence (expense vendor → workspace default → "Credit Card Misc")
    • Inactive vendor violation behavior
  • Updated Configure-Quickbooks-Online.md with two brief cross-links (Import → Vendors, Export → Credit/Debit card → Default vendor) so the config doc stays focused on connection setup and doesn't duplicate vendor matching logic.

Scoped in Expensify/Expensify#634620.

Related Issues

Resource Updates tracking issue: Expensify/Expensify#634620

Tests / QA

Help site content only (no code changes). Reviewer should confirm the article accurately describes the Release 1 QBO vendor matching behavior and that feature/UI labels match the shipped product before merge.

Adds a standalone Vendor-Matching.md article documenting the imported vendor list, Vendor expense field, auto-matching, default vendor fallback, and export behavior for QBO Credit/Debit card company card expenses (Release 1). Adds minimal cross-links from Configure-Quickbooks-Online.md to avoid duplicating vendor matching logic.

Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
@github-actions github-actions Bot changed the title Update help docs for Release 1: Vendor Matching for QuickBooks Online (QBO) [No QA] Update help docs for Release 1: Vendor Matching for QuickBooks Online (QBO) Jul 16, 2026
@OSBotify

This comment has been minimized.

@stephanieelliott stephanieelliott added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Jul 16, 2026
@stephanieelliott
stephanieelliott marked this pull request as ready for review July 16, 2026 20:41
@stephanieelliott
stephanieelliott self-requested a review as a code owner July 16, 2026 20:41
@OSBotify

This comment has been minimized.

- **Export company card expenses as**:
- Credit card (default)
- Debit card
- Optionally set a **Default vendor** as a fallback for expenses that don't have a vendor set. Learn how vendors are imported, matched, and exported in [QuickBooks Online Vendor Matching](/articles/new-expensify/connections/quickbooks-online/Vendor-Matching).

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.

Broken cross-link: Same issue as above — /Vendor-Matching does not exist. Update to /articles/new-expensify/connections/quickbooks-online/Manage-Vendor-Matching-for-QuickBooks-Online so the link resolves to the article added in this PR.

3. Under **Export company card expenses as**, select **Credit card** or **Debit card**.
4. Select a **Default vendor**.

The default vendor is used only when an expense doesn't already have a vendor assigned. If no default vendor is configured, expenses export to **Credit Card Misc**.

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.

Navigation phrasing: The rest of this doc and the sibling article use "the navigation tabs (on the left on web, on the bottom on mobile)". Here it reads "Click the navigation tabs (on the left on web, on the bottom on mobile), then go to..." — that's fine, but use the exact UI value casing: [workspace name] should be [Workspace Name] to match the placeholder convention used in Configure-Quickbooks-Online.md.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 080e47c187

ℹ️ 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".

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR adds a well-structured standalone article documenting QuickBooks Online vendor matching for non-reimbursable company card expenses, plus two brief cross-links from the existing Configure-Quickbooks-Online.md. The new article is scoped to a single workflow, uses complete YAML frontmatter (including internalScope), and follows the task-based heading model closely. The main concern is a filename/link mismatch that would produce broken cross-links, plus a few small consistency and terminology issues.

Scores Summary

  • Readability: 9/10 - Clear, concise, scannable. Ordered lists correctly convey assignment/export precedence; navigation phrasing matches the unified web/mobile convention. One typo ("workspce").
  • AI Readiness: 9/10 - Complete metadata with internalScope, task-based headings, full feature name used throughout, only H1 and H2 (plus exempt FAQ), realistic search keywords. Strong retrieval profile.
  • Style Compliance: 7/10 - UI labels (Vendor field, Vendors tab, Default vendor, Credit card, Debit card, Export company card expenses as) are bolded and used consistently. Docked for the broken cross-link target and inconsistent casing of "Merchant Rule".

Key Findings

  • Broken cross-links (must fix): Both new links in Configure-Quickbooks-Online.md point to /articles/new-expensify/connections/quickbooks-online/Vendor-Matching, but the new file is Manage-Vendor-Matching-for-QuickBooks-Online.md. The link target must match the actual filename or the links will 404.
  • Anchor text vs. destination mismatch: Cross-link anchors and the PR body call the feature "QuickBooks Online Vendor Matching", while the article title/H1 is "Manage Vendor Matching for QuickBooks Online". Align these so anchor text reflects the destination.
  • Typo: "workspce merchant rule" should be "workspace merchant rule".
  • Inconsistent terminology casing: "Merchant Rule" vs "merchant rule" vs "merchant name" appear in the same section. Use the exact UI label consistently and match capitalization exactly (naming conventions Core UI Referencing Rules).
  • Positives: Single-workflow scope, complete internalScope, task-based headings throughout, FAQ questions are properly question-based, screenshot placeholder uses the correct non-rendered HTML-comment format with a specific Purpose, and cross-linking is limited to genuine prerequisite/deep-dive context.

Recommendations

  1. Fix the two cross-link targets in Configure-Quickbooks-Online.md to point to the real filename (Manage-Vendor-Matching-for-QuickBooks-Online), or rename the new file to match the intended Vendor-Matching slug consistently across the PR.
  2. Standardize the feature name between anchor text, PR body, and article title.
  3. Correct the "workspce" typo and standardize "Merchant Rule" casing to the exact UI label.

Recommendation: Needs work (minor). Content quality is high, but the broken cross-links are a blocking issue that must be resolved before merge.

Files Reviewed

  • docs/articles/new-expensify/connections/quickbooks-online/Manage-Vendor-Matching-for-QuickBooks-Online.md - New article, strong overall; fix typo and terminology casing.
  • docs/articles/new-expensify/connections/quickbooks-online/Configure-Quickbooks-Online.md - Two cross-links added; link targets do not match the new filename (broken links).

Note: This is a top-level summary review based only on the proposed diff.

Co-authored-by: Alex Beaman <Beamanator@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

Fixed the failing spellcheck check.

Cause: A typo — workspce instead of workspace — on line 23 of the new Manage-Vendor-Matching-for-QuickBooks-Online.md article. cspell flagged it as an unknown word.

Fix: Corrected the spelling and pushed to the branch. This was the only failing check (the remaining review item is just a pending reviewer assignment, not a failure).

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

Clarified availability and requirements for QuickBooks Online vendor matching feature for Workspace Admins.
@stephanieelliott stephanieelliott changed the title [No QA] Update help docs for Release 1: Vendor Matching for QuickBooks Online (QBO) [Hold for feature] [No QA] Update help docs for Release 1: Vendor Matching for QuickBooks Online (QBO) Jul 17, 2026
@github-actions github-actions Bot changed the title [Hold for feature] [No QA] Update help docs for Release 1: Vendor Matching for QuickBooks Online (QBO) [No QA] [Hold for feature] [No QA] Update help docs for Release 1: Vendor Matching for QuickBooks Online (QBO) Jul 17, 2026
@OSBotify

This comment has been minimized.

@stephanieelliott stephanieelliott self-assigned this Jul 17, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

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

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants