[No QA] Update Track Taxes help article for SmartScan VAT extraction

[MelvinBot]

Explanation of Change

Documents the SmartScan VAT extraction feature (now being rolled out to all customers) in the Track Taxes help article. Previously the article implied tax was only applied from workspace/category defaults or entered manually; it now reflects that SmartScan reads the tax amount printed on a receipt and applies it automatically, with manual override still available.

Changes to docs/articles/new-expensify/workspaces/Track-Taxes.md:

• Intro: Added a sentence noting that SmartScan reads the receipt's tax amount and applies it automatically where possible, and that users can review/edit it.
• FAQ "What should I do if the tax amount on my expense is missing or incorrect?": Updated to explain that SmartScan now attempts to read the tax amount from the receipt, and manual entry still applies when there's no tax line on the receipt or the applied amount is wrong.
• Keywords: Added SmartScan tax, scanned tax, receipt tax for discoverability.

Kept the public copy intentionally simple — the detailed matching/capping and foreign-currency behavior is internal troubleshooting detail and is being scoped for an internal SO article instead (see the resource-updates scope).

AI tests: Per the test-selection-matrix, a content-only edit to an existing help article triggers none of the App code-test bundles (lint/typecheck/test/storybook target TS/TSX; the docs gate is for routing/config changes, not body text). No new/renamed/removed articles, so docs routing is unchanged.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/578883
PROPOSAL:

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• 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 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
• 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

[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 @lydiabarclay

[melvin-bot]

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a small, targeted update to the Track Taxes article, adding SmartScan tax-reading behavior to the introductory paragraph and to one FAQ answer. It also expands the YAML keywords array with three new search-relevant terms. The changes are factual, well-scoped, and improve both user clarity and search discoverability.

Scores Summary

• Readability: 9/10 - The added sentences are clear, concise, and flow naturally within their surrounding context. The intro addition is slightly long when combined with the existing sentence (the paragraph now packs four distinct ideas into one block), but the language itself is clean and scannable.
• AI Readiness: 9/10 - The three new keywords (SmartScan tax, scanned tax, receipt tax) directly match realistic user search queries and strengthen retrieval. The YAML metadata block already contains internalScope is missing (pre-existing, not introduced by this PR), so no penalty is applied. The new content uses the full feature name "SmartScan" consistently.
• Style Compliance: 10/10 - "SmartScan" matches exact product terminology. No prohibited language is introduced. No UI element references are altered or misnamed. The FAQ answer remains in proper question-and-answer format under the existing # FAQ heading.

Key Findings

• The new keywords are well-chosen and align with how users actually search for tax-on-receipt behavior.
• Both content additions consistently use "SmartScan" (correct product term with correct casing), satisfying the deterministic writing and exact UI terminology rules.
• The FAQ revision replaces a somewhat vague explanation with a more specific description of SmartScan behavior, which improves both user understanding and AI retrieval quality.
• No structural changes are made (headings, hierarchy, sections), so governance rules around heading format and article structure are unaffected.
• Pre-existing gap: the YAML frontmatter still lacks internalScope, which is required by HELP_AUTHORING_GUIDELINES.md Section 3. This is not introduced by this PR, so it is not scored against, but it is worth noting for a future follow-up.

Recommendations

• Consider splitting the introductory paragraph into two sentences or two short paragraphs to improve scannability. The first could cover manual tax rate selection, and the second could cover SmartScan auto-detection. This would make it easier for users (and AI) to extract the SmartScan-specific information.
• In a future PR, consider adding internalScope to the YAML metadata to fully comply with the authoring spec.

Files Reviewed

• docs/articles/new-expensify/workspaces/Track-Taxes.md - Minor content additions (keywords, intro text, FAQ answer). Clean and compliant with governance standards.

[github-actions]

Missing required metadata field: The YAML frontmatter is missing the internalScope field, which is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3. Since you're already updating the metadata block, please add it. Example:

Suggested change

	keywords: [New Expensify, tax rates, VAT, GST, QST, PST, expense tax codes, foreign currency taxes, workspace settings, SmartScan tax, scanned tax, receipt tax]
	keywords: [New Expensify, tax rates, VAT, GST, QST, PST, expense tax codes, foreign currency taxes, workspace settings, SmartScan tax, scanned tax, receipt tax]
	internalScope: Audience is Workspace Admins on Collect and Control plans. Covers tax rate setup and SmartScan tax extraction. Does not cover accounting integration tax sync.

[OSBotify]

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

Updated articles:

• articles/new-expensify/workspaces/Track-Taxes

[github-actions]

Missing required metadata: The YAML frontmatter is missing the internalScope field, which is required per HELP_AUTHORING_GUIDELINES.md Section 3 and TEMPLATE.md. Since you're already updating the metadata block, consider adding it. Example:

Suggested change

	keywords: [New Expensify, tax rates, VAT, GST, QST, PST, expense tax codes, foreign currency taxes, workspace settings, SmartScan tax, scanned tax, receipt tax]
	keywords: [New Expensify, tax rates, VAT, GST, QST, PST, expense tax codes, foreign currency taxes, workspace settings, SmartScan tax, scanned tax, receipt tax]
	internalScope: Audience is Workspace Admins on Collect and Control plans. Covers setting up and managing tax rates in a workspace, does not cover accounting integration tax sync or personal expense tax tracking.