Skip to content

[No QA] Update Global VaTax help pages to VAT IT branding#90391

Merged
lschurr merged 5 commits into
mainfrom
claude-updateVatItHelpPage
May 18, 2026
Merged

[No QA] Update Global VaTax help pages to VAT IT branding#90391
lschurr merged 5 commits into
mainfrom
claude-updateVatItHelpPage

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Explanation of Change

Updates the Global VaTax help pages (both New Expensify and Expensify Classic) to reflect the VAT IT partnership branding. Key changes:

  • Page titles and descriptions updated from "Global VaTax" to "VAT IT"
  • Connection instructions replaced with the new VAT IT onboarding flow (Auditor role-based setup instead of the VaTax Cloud signup form)
  • Added vat@expensify.com contact for questions
  • Fixed keyword typo ("Expensify CLassic" → "Expensify Classic" / "New Expensify")

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/636286

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

  • Verify that no errors appear in the JS console

Offline tests

N/A — docs-only change

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

  • 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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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

N/A — docs-only change

Android: mWeb Chrome

N/A — docs-only change

iOS: Native

N/A — docs-only change

iOS: mWeb Safari

N/A — docs-only change

MacOS: Chrome / Safari

N/A — docs-only change

Update connection instructions, titles, and descriptions on both
New Expensify and Expensify Classic help pages to reflect the
VAT IT partnership.

Co-authored-by: Nick Tooker <NickTooker@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team May 12, 2026 23:56
@github-actions github-actions Bot changed the title Update Global VaTax help pages to VAT IT branding [No QA] Update Global VaTax help pages to VAT IT branding May 13, 2026
@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented May 13, 2026

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

Updated articles:

@NickTooker NickTooker marked this pull request as ready for review May 13, 2026 20:20
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 13, 2026

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 @lschurr

@melvin-bot melvin-bot Bot requested review from lschurr and thesahindia and removed request for a team May 13, 2026 20:21
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 13, 2026

@thesahindia @lschurr One of you needs to 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]

NOTE: It looks like docs/redirects.csv was modified in this PR. Please see this SO for special instructions on how to review changes to that file.

Comment thread docs/articles/expensify-classic/connections/VAT-IT.md
Comment thread docs/articles/new-expensify/connections/VAT-IT.md
Comment thread docs/articles/expensify-classic/connections/VAT-IT.md
Comment thread docs/articles/new-expensify/connections/VAT-IT.md
Comment thread docs/articles/expensify-classic/connections/VAT-IT.md
Comment thread docs/articles/new-expensify/connections/VAT-IT.md
Comment thread docs/articles/expensify-classic/connections/VAT-IT.md
Comment thread docs/articles/new-expensify/connections/VAT-IT.md
Comment thread docs/articles/expensify-classic/connections/VAT-IT.md
Comment thread docs/articles/new-expensify/connections/VAT-IT.md
Comment thread docs/articles/expensify-classic/connections/VAT-IT.md
@github-actions
Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR renames the Global VaTax integration pages to VAT IT across both New Expensify and Expensify Classic, updates the onboarding flow, adds a contact email, fixes a keyword typo, and sets up redirects. While the rebranding intent is clear and the redirects are correctly configured, the new files carry forward several structural issues from the original articles and introduce an incomplete find-and-replace of the old branding.

Scores Summary

  • Readability: 7/10 - The articles are generally clear and scannable. Steps are concise and action-oriented. However, some sections could be tightened, and the inconsistent branding (mixing "Global VaTax" and "VAT IT" within the same article) will confuse readers.
  • AI Readiness: 4/10 - Multiple # headings violate the single-title rule (only one # allowed plus optional # FAQ). The internalScope field is missing from YAML metadata in both files. Several headings are noun-based rather than task-based, reducing retrieval precision.
  • Style Compliance: 5/10 - Headings such as "VAT-Recoverable Expenses" and "Tracking Your VAT Reclaim" are noun-only and do not start with an action verb or question word. The body text in the "How VAT Refunds Work" and "Tracking Your VAT Reclaim" sections still references "Global VaTax" instead of "VAT IT," which directly contradicts the purpose of this PR.

Key Findings

Critical issues that must be addressed:

  • Incomplete rebranding: In both VAT-IT.md files, the "How VAT Refunds Work" section body still says "Global VaTax simplifies this by handling" and "By syncing Expensify with Global VaTax." The "Tracking Your VAT Reclaim" section still references "Submission Analysis Report in Global VaTax." These must be updated to "VAT IT" to match the PR's stated purpose.
  • Heading hierarchy violation: Both files use four # headings beyond the title (# VAT-Recoverable Expenses, # How VAT Refunds Work, # How to Connect Expensify with VAT IT, # Tracking Your VAT Reclaim). Per HELP_AUTHORING_GUIDELINES.md Section 4, only one # heading (the article title) is permitted, plus an optional # FAQ. All content sections must use ##.
  • Non-task-based headings: "VAT-Recoverable Expenses" and "Tracking Your VAT Reclaim" are noun-only headings. Per Section 2, all headings (except # FAQ) must start with an action verb or question word (How, What, Where, Who, Why, When). Suggested alternatives: "What expenses are eligible for VAT recovery" and "How to track your VAT reclaim status."
  • Missing internalScope metadata: Both files omit the internalScope field required by HELP_AUTHORING_GUIDELINES.md Section 3 and TEMPLATE.md.

Positive aspects:

  • Proper redirects added in redirects.csv for both old URLs.
  • The keyword typo ("Expensify CLassic") from the old file has been corrected.
  • The New Expensify file correctly uses "New Expensify" in its keywords while the Classic file uses "Expensify Classic."
  • The updated connection steps (Auditor role-based setup) are clearer and more concise than the original 9-step process.
  • Contact email (vat@expensify.com) is a helpful addition.

Recommendations

  1. [Must fix] Replace all remaining "Global VaTax" references in the body text of both VAT-IT.md files with "VAT IT."
  2. [Must fix] Demote all # content headings to ##. Only the article title should use #.
  3. [Must fix] Rewrite noun-only headings to be task-based (e.g., "# VAT-Recoverable Expenses" becomes "## What expenses are eligible for VAT recovery").
  4. [Should fix] Add internalScope to the YAML frontmatter in both files, specifying the audience and workflow scope.
  5. [Consider] Verify whether the "Submission Analysis Report in Global VaTax" tracking reference is still accurate under the VAT IT partnership, or if the tracking tool/portal has also been rebranded.

Files Reviewed

  • docs/articles/expensify-classic/connections/VAT-IT.md - New file; has incomplete rebranding, heading hierarchy violations, and missing metadata.
  • docs/articles/new-expensify/connections/VAT-IT.md - New file; same issues as the Classic version (both files are nearly identical).
  • docs/redirects.csv - Redirects correctly configured for both old URLs. No issues.

Note: Both new VAT-IT.md files have identical structural issues since they share the same content. Fixes applied to one should be mirrored in the other.

Comment thread docs/articles/new-expensify/connections/VAT-IT.md
Comment thread docs/articles/expensify-classic/connections/VAT-IT.md
@lschurr lschurr merged commit 0a9b1f2 into main May 18, 2026
25 checks passed
@lschurr lschurr deleted the claude-updateVatItHelpPage branch May 18, 2026 16:46
@melvin-bot melvin-bot Bot added the Emergency label May 18, 2026
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 18, 2026

@lschurr 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.

Comment on lines +1 to +5
---
title: VAT IT Integration
description: Learn how to connect Expensify with VAT IT to simplify international VAT refunds for your business expenses.
keywords: [Expensify Classic, VAT IT, VAT refund, international expenses, tax compliance]
---
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.

Missing required metadata field: The YAML frontmatter is missing the internalScope field, which is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3. Add something like:

Suggested change
---
title: VAT IT Integration
description: Learn how to connect Expensify with VAT IT to simplify international VAT refunds for your business expenses.
keywords: [Expensify Classic, VAT IT, VAT refund, international expenses, tax compliance]
---
---
title: VAT IT Integration
description: Learn how to connect Expensify with VAT IT to simplify international VAT refunds for your business expenses.
keywords: [Expensify Classic, VAT IT, VAT refund, international expenses, tax compliance]
internalScope: Audience is workspace admins. Covers connecting Expensify Classic with VAT IT for VAT recovery, does not cover New Expensify setup or VAT policy details.
---

Comment on lines +1 to +5
---
title: VAT IT Integration
description: Learn how to connect Expensify with VAT IT to simplify international VAT refunds for your business expenses.
keywords: [New Expensify, VAT IT, VAT refund, international expenses, tax compliance]
---
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.

Missing required metadata field: The YAML frontmatter is missing the internalScope field, which is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3. Add something like:

Suggested change
---
title: VAT IT Integration
description: Learn how to connect Expensify with VAT IT to simplify international VAT refunds for your business expenses.
keywords: [New Expensify, VAT IT, VAT refund, international expenses, tax compliance]
---
---
title: VAT IT Integration
description: Learn how to connect Expensify with VAT IT to simplify international VAT refunds for your business expenses.
keywords: [New Expensify, VAT IT, VAT refund, international expenses, tax compliance]
internalScope: Audience is workspace admins. Covers connecting New Expensify with VAT IT for VAT recovery, does not cover Expensify Classic setup or VAT policy details.
---


---

# VAT-Recoverable Expenses
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.

Heading hierarchy violation: Only one # heading (the article title) is allowed per article, plus an optional # FAQ. All content section headings must use ##. This applies to this heading and the ones on lines 30, 42, and 53.

Additionally, this is a noun-only heading which violates the task-based heading rule. Headings must start with an action verb or question word (How, What, Where, Who, Why, When).

Suggested fix:

Suggested change
# VAT-Recoverable Expenses
## What expenses are eligible for VAT recovery


---

# VAT-Recoverable Expenses
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.

Heading hierarchy violation: Only one # heading (the article title) is allowed per article, plus an optional # FAQ. All content section headings must use ##. This applies to this heading and the ones on lines 30, 42, and 53.

Additionally, this is a noun-only heading which violates the task-based heading rule. Headings must start with an action verb or question word (How, What, Where, Who, Why, When).

Suggested fix:

Suggested change
# VAT-Recoverable Expenses
## What expenses are eligible for VAT recovery


# How VAT Refunds Work

VAT refund regulations vary by country and expense type, making the process complex. Global VaTax simplifies this by handling:
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.

Heading hierarchy + task-based heading violation: Must use ## instead of #, and the heading must be task-based (start with an action verb or question word).

Suggested fix:

Suggested change
VAT refund regulations vary by country and expense type, making the process complex. Global VaTax simplifies this by handling:
## How VAT refunds work with VAT IT


# How VAT Refunds Work

VAT refund regulations vary by country and expense type, making the process complex. Global VaTax simplifies this by handling:
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.

Heading hierarchy + task-based heading violation: Must use ## instead of #, and the heading must be task-based (start with an action verb or question word).

Suggested fix:

Suggested change
VAT refund regulations vary by country and expense type, making the process complex. Global VaTax simplifies this by handling:
## How VAT refunds work with VAT IT

@github-actions
Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR renames the Global VaTax integration documentation to VAT IT across both Expensify Classic and New Expensify, updates the connection steps, and adds proper redirects. While the rebranding intent is clear and the redirect setup is correct, the new files carry over several structural issues from the old articles and introduce an incomplete rebranding -- multiple sections still reference "Global VaTax" instead of "VAT IT."

Scores Summary

  • Readability: 6/10 - The content is generally clear and the updated connection steps (1-4) are concise and actionable. However, the inconsistent branding between "VAT IT" and leftover "Global VaTax" references creates confusion for readers.
  • AI Readiness: 3/10 - Multiple # headings are used for content sections (only one # is allowed for the title, plus optional # FAQ). The required internalScope YAML field is missing from both files. Several headings are noun-only rather than task-based, which hurts semantic retrieval.
  • Style Compliance: 4/10 - Heading hierarchy violates the governance rules. External full URLs are used instead of relative links. The rebranding is incomplete with "Global VaTax" still appearing in body text of the new VAT IT articles.

Key Findings

Critical issues that must be addressed:

  • Incomplete rebranding: Both new files still reference "Global VaTax" in two places each: (1) the "How VAT Refunds Work" section says "Global VaTax simplifies this by handling" and "By syncing Expensify with Global VaTax," and (2) the "Tracking Your VAT Reclaim" section says "via the Submission Analysis Report in Global VaTax." These must be updated to reference VAT IT.
  • Heading hierarchy violation: Content sections use # headings (# VAT-Recoverable Expenses, # How VAT Refunds Work, # How to Connect Expensify with VAT IT, # Tracking Your VAT Reclaim). Per HELP_AUTHORING_GUIDELINES.md Section 4, only the article title may use #. All content sections must use ##.
  • Missing internalScope metadata: Both files are missing the required internalScope field in YAML frontmatter (HELP_AUTHORING_GUIDELINES.md Section 3).

Additional issues:

  • Non-task-based headings: "VAT-Recoverable Expenses" and "Tracking Your VAT Reclaim" are noun-only headings. Per Section 2, all headings must start with an action verb or question word. Suggested rewrites: "What expenses are eligible for VAT recovery" and "How to track your VAT reclaim status."
  • "How VAT Refunds Work" is borderline acceptable but would be stronger as "How VAT refunds work with VAT IT" to include the feature name per Section 6.
  • External full URLs: Links to investopedia.com and use.expensify.com use full URLs. Per Section 7, relative links are preferred. External links may be acceptable for third-party sites, but the use.expensify.com link is an Expensify property and should use a relative path if possible.

Positive aspects:

  • Redirects from the old Global VaTax URLs to the new VAT IT URLs are correctly added for both Classic and New Expensify.
  • The updated connection steps (1-4) are clearer and more actionable than the previous 9-step process.
  • The addition of a contact email (vat@expensify.com) for questions is a helpful user-facing improvement.
  • Keywords in YAML frontmatter are appropriately updated, and the Classic article correctly fixes the previous typo ("CLassic" is now "Classic").

Recommendations

  1. [Must fix] Replace all remaining "Global VaTax" references in both VAT-IT.md files with "VAT IT" to complete the rebranding.
  2. [Must fix] Change all content section # headings to ## in both files.
  3. [Must fix] Add the internalScope field to YAML frontmatter in both files (e.g., internalScope: Audience is Workspace Admins. Covers VAT IT integration setup and VAT recovery tracking. Does not cover other accounting integrations.).
  4. [Should fix] Rewrite noun-only headings to be task-based (e.g., "VAT-Recoverable Expenses" becomes "What expenses are eligible for VAT recovery").
  5. [Nice to have] Include the feature name "VAT IT" in more headings to improve AI retrieval precision.

Files Reviewed

  • docs/articles/expensify-classic/connections/VAT-IT.md - New file; has incomplete rebranding, heading hierarchy violations, and missing metadata.
  • docs/articles/new-expensify/connections/VAT-IT.md - New file; same issues as the Classic version (content is nearly identical).
  • docs/articles/expensify-classic/connections/Global-VaTax.md - Deleted (replaced by VAT-IT.md).
  • docs/articles/new-expensify/connections/Global-VaTax.md - Deleted (replaced by VAT-IT.md).
  • docs/redirects.csv - Two redirects correctly added.

Note: Both new VAT-IT.md files share nearly identical content. All structural and branding fixes should be applied to both files consistently.


VAT refund regulations vary by country and expense type, making the process complex. Global VaTax simplifies this by handling:

- VAT analysis and calculation
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.

Stale brand name: This section still references "Global VaTax" but the article has been updated to be about "VAT IT". Update all references in this paragraph.

Suggested fix:

Suggested change
- VAT analysis and calculation
VAT refund regulations vary by country and expense type, making the process complex. VAT IT simplifies this by handling:


VAT refund regulations vary by country and expense type, making the process complex. Global VaTax simplifies this by handling:

- VAT analysis and calculation
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.

Stale brand name: This section still references "Global VaTax" but the article has been updated to be about "VAT IT". Update all references in this paragraph.

Suggested fix:

Suggested change
- VAT analysis and calculation
VAT refund regulations vary by country and expense type, making the process complex. VAT IT simplifies this by handling:

- Report preparation and submission to tax authorities

By syncing Expensify with Global VaTax, businesses can automate VAT reporting and reclaim eligible expenses efficiently.

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.

Stale brand name: "Global VaTax" should be "VAT IT" to match the updated article.

Suggested fix:

Suggested change
By syncing Expensify with VAT IT, businesses can automate VAT reporting and reclaim eligible expenses efficiently.

- Report preparation and submission to tax authorities

By syncing Expensify with Global VaTax, businesses can automate VAT reporting and reclaim eligible expenses efficiently.

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.

Stale brand name: "Global VaTax" should be "VAT IT" to match the updated article.

Suggested fix:

Suggested change
By syncing Expensify with VAT IT, businesses can automate VAT reporting and reclaim eligible expenses efficiently.


# How to Connect Expensify with VAT IT

Follow these steps to activate the integration:
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.

Heading hierarchy violation: Must use ## instead of #. Only one # heading (the article title) is allowed, plus optional # FAQ.

Suggested fix:

Suggested change
Follow these steps to activate the integration:
## How to connect Expensify with VAT IT


# How to Connect Expensify with VAT IT

Follow these steps to activate the integration:
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.

Heading hierarchy violation: Must use ## instead of #. Only one # heading (the article title) is allowed, plus optional # FAQ.

Suggested fix:

Suggested change
Follow these steps to activate the integration:
## How to connect Expensify with VAT IT

1. Create a dedicated Expensify user for VAT IT and assign that user the Auditor role.
2. Assign each relevant policy to that user so VAT IT can access the correct entities.
3. Confirm the invitation and access setup by email.
4. VAT IT verifies that the correct policies are visible and that the connection has been set up correctly.
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.

Terminology violation: Use "workspace" instead of "policy" per Expensify naming conventions.

Suggested fix:

Suggested change
4. VAT IT verifies that the correct policies are visible and that the connection has been set up correctly.
2. Assign each relevant workspace to that user so VAT IT can access the correct entities.

1. Create a dedicated Expensify user for VAT IT and assign that user the Auditor role.
2. Assign each relevant policy to that user so VAT IT can access the correct entities.
3. Confirm the invitation and access setup by email.
4. VAT IT verifies that the correct policies are visible and that the connection has been set up correctly.
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.

Terminology violation: Use "workspace" instead of "policy" per Expensify naming conventions.

Suggested fix:

Suggested change
4. VAT IT verifies that the correct policies are visible and that the connection has been set up correctly.
2. Assign each relevant workspace to that user so VAT IT can access the correct entities.

3. Confirm the invitation and access setup by email.
4. VAT IT verifies that the correct policies are visible and that the connection has been set up correctly.

Once VAT IT prepares your VAT reclaim documents in the required languages, they will submit them to the appropriate tax authorities. If you have questions about this process, reach out to vat@expensify.com.
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.

Terminology violation: "policies" should be "workspaces" per Expensify naming conventions.

Suggested fix:

Suggested change
Once VAT IT prepares your VAT reclaim documents in the required languages, they will submit them to the appropriate tax authorities. If you have questions about this process, reach out to vat@expensify.com.
4. VAT IT verifies that the correct workspaces are visible and that the connection has been set up correctly.

3. Confirm the invitation and access setup by email.
4. VAT IT verifies that the correct policies are visible and that the connection has been set up correctly.

Once VAT IT prepares your VAT reclaim documents in the required languages, they will submit them to the appropriate tax authorities. If you have questions about this process, reach out to vat@expensify.com.
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.

Terminology violation: "policies" should be "workspaces" per Expensify naming conventions.

Suggested fix:

Suggested change
Once VAT IT prepares your VAT reclaim documents in the required languages, they will submit them to the appropriate tax authorities. If you have questions about this process, reach out to vat@expensify.com.
4. VAT IT verifies that the correct workspaces are visible and that the connection has been set up correctly.


---

# Tracking Your VAT Reclaim
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.

Heading hierarchy + task-based heading violation: Must use ## instead of #, and heading must be task-based.

Suggested fix:

Suggested change
# Tracking Your VAT Reclaim
## How to track your VAT reclaim


---

# Tracking Your VAT Reclaim
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.

Heading hierarchy + task-based heading violation: Must use ## instead of #, and heading must be task-based.

Suggested fix:

Suggested change
# Tracking Your VAT Reclaim
## How to track your VAT reclaim


# Tracking Your VAT Reclaim

After submission, you can monitor the progress of your VAT reclaim via the **Submission Analysis Report** in Global VaTax.
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.

Stale brand name: "Global VaTax" should be "VAT IT" to match the updated article.

Suggested fix:

Suggested change
After submission, you can monitor the progress of your VAT reclaim via the **Submission Analysis Report** in Global VaTax.
After submission, you can monitor the progress of your VAT reclaim via the **Submission Analysis Report** in VAT IT.


# Tracking Your VAT Reclaim

After submission, you can monitor the progress of your VAT reclaim via the **Submission Analysis Report** in Global VaTax.
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.

Stale brand name: "Global VaTax" should be "VAT IT" to match the updated article.

Suggested fix:

Suggested change
After submission, you can monitor the progress of your VAT reclaim via the **Submission Analysis Report** in Global VaTax.
After submission, you can monitor the progress of your VAT reclaim via the **Submission Analysis Report** in VAT IT.

---


The Expensify-VAT IT integration helps businesses reclaim Value Added Tax (VAT) on international expenses. If your company is based in the U.S. but conducts business abroad, you can track expenses in [Expensify](https://use.expensify.com/expense-management) and sync them with VAT IT to simplify VAT recovery.
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.

Cross-linking violation: Per HELP_AUTHORING_GUIDELINES.md Section 7, use relative links only -- do not use full URLs. The links to https://use.expensify.com/expense-management and the Investopedia URL on line 10 should either be converted to relative links (if internal) or removed/simplified if external.

Note: The Investopedia link on line 10 is an external educational reference, which may be acceptable, but the use.expensify.com link should use a relative path if it points to an internal Expensify resource.

---


The Expensify-VAT IT integration helps businesses reclaim Value Added Tax (VAT) on international expenses. If your company is based in the U.S. but conducts business abroad, you can track expenses in [Expensify](https://use.expensify.com/expense-management) and sync them with VAT IT to simplify VAT recovery.
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.

Cross-linking violation: Per HELP_AUTHORING_GUIDELINES.md Section 7, use relative links only -- do not use full URLs. The links to https://use.expensify.com/expense-management and the Investopedia URL on line 10 should either be converted to relative links (if internal) or removed/simplified if external.

Note: The Investopedia link on line 10 is an external educational reference, which may be acceptable, but the use.expensify.com link should use a relative path if it points to an internal Expensify resource.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/lschurr in version: 9.3.76-0 🚀

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.77-3 🚀

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

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

Labels

Emergency 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