[No QA] Update VAT-IT.md

[brianlee-expensify]

updating references from "Global VaTax" to "VAT IT"

Explanation of Change

Fixed Issues

$
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 that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • 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 (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• 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

[OSBotify]

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

Updated articles:

• articles/new-expensify/connections/VAT-IT

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR corrects the product name from "Global VaTax" to "VAT IT" in three places within the VAT IT integration article. The change is a straightforward terminology fix that brings the article into consistency -- the file title, YAML metadata, and several other references already used "VAT IT," while three instances still used the old "Global VaTax" name.

Scores Summary

• Readability: 10/10 - The changed lines are clear, concise, and flow naturally. Replacing an inconsistent product name improves scannability and reduces reader confusion.
• AI Readiness: 10/10 - The changes ensure the correct product name ("VAT IT") appears consistently, which improves semantic retrieval accuracy. An AI system searching for "VAT IT" will now match all relevant passages rather than missing those that previously referenced "Global VaTax."
• Style Compliance: 10/10 - The changes align with the naming conventions governance rule: "Use the exact text shown in the product UI" and "Do not substitute synonyms." Correcting an outdated product name to the current one is exactly the kind of fix these rules demand.

Key Findings

• The three replacements are correct and consistent with the rest of the article, which already uses "VAT IT" in the title, YAML metadata, keywords, and several body paragraphs.
• No new structural, formatting, or terminology issues are introduced by this diff.
• Pre-existing structural concerns exist in the file (multiple # headings where governance requires only one # title plus optional # FAQ, missing internalScope in YAML metadata, some headings that are not task-based), but those are outside the scope of this PR and should be addressed separately.

Recommendations

• Approve this PR as-is. The changes are minimal, correct, and improve consistency.
• Consider a follow-up PR to address pre-existing governance gaps in this file, specifically: restructuring # headings to use ## (only one # title is allowed per governance), adding internalScope to the YAML frontmatter, and revising section headings to be task-based (e.g., "# Tracking Your VAT Reclaim" could become "## How to track your VAT reclaim in VAT IT").

Files Reviewed

• docs/articles/new-expensify/connections/VAT-IT.md - Three instances of "Global VaTax" correctly replaced with "VAT IT." No issues introduced.

This review assessed only the proposed changes in the diff, not pre-existing content.

[melvin-bot]

@stephanieelliott looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[github-actions]

Pre-existing structural issue (not introduced by this PR): The heading above this line (# How VAT Refunds Work, line 28) uses a # heading, but per HELP_AUTHORING_GUIDELINES.md Section 4, only one # heading is allowed per article (the article title), plus an optional # FAQ. All content sections must use ##. This file has four # content headings that should be demoted to ##.

Additionally, several headings in this file are not task-based (e.g., "VAT-Recoverable Expenses", "Tracking Your VAT Reclaim") — headings must start with an action verb or question word per Section 2.

The naming fix on this line is correct. Consider addressing the structural issues in a follow-up.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a straightforward terminology correction, replacing three instances of "Global VaTax" with "VAT IT" in the VAT IT integration article. The change ensures the partner name is consistent throughout the document, matching the article title and other existing references that already used "VAT IT."

Scores Summary

• Readability: 8/10 - The changed lines are clear, scannable, and well-structured. No readability issues introduced by this diff.
• AI Readiness: 6/10 - The diff itself is clean, but the file it modifies has pre-existing governance gaps (noted below as context, not scored against this PR). The changes do not introduce any new AI readiness issues. Score reflects that this PR does not address the missing internalScope field in YAML frontmatter, which is required per HELP_AUTHORING_GUIDELINES.md Section 3, though that is a pre-existing issue rather than something introduced by this change.
• Style Compliance: 9/10 - The terminology correction aligns the partner name consistently with the rest of the article and is the right fix. No naming convention violations in the changed lines.

Key Findings

• Positive: The correction resolves an inconsistency where the article title, YAML metadata, and some body text already referred to "VAT IT," but three passages still used the outdated name "Global VaTax." All three instances are now consistent.
• Pre-existing issues (not introduced by this PR): The file has governance gaps that exist in the unchanged portions, including missing internalScope in YAML frontmatter (required by HELP_AUTHORING_GUIDELINES.md Section 3), non-task-based headings (e.g., "VAT-Recoverable Expenses," "How VAT Refunds Work," "Tracking Your VAT Reclaim"), and use of # headings for content sections where ## is required (per TEMPLATE.md, only the article title should use #; all content sections should use ##). These are not part of this diff and are noted only for future reference.

Recommendations

• This PR: Approve as-is. The naming correction is accurate and necessary.
• Future improvement: Consider a follow-up PR to bring the full article into governance compliance -- add internalScope to frontmatter, convert content # headings to ##, and rephrase headings to be task-based (e.g., "How to connect Expensify with VAT IT," "How to track your VAT reclaim").

Files Reviewed

• docs/articles/new-expensify/connections/VAT-IT.md -- Three instances of "Global VaTax" corrected to "VAT IT." All changes are accurate and improve consistency.

Review based on governance rules in docs/HELPSITE_NAMING_CONVENTIONS.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/TEMPLATE.md.

[brianlee-expensify]

very simple update, no QA needed

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.89-1 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS