[No QA] Add Xero troubleshooting docs (New Expensify)#84821
[No QA] Add Xero troubleshooting docs (New Expensify)#84821stephanieelliott merged 1 commit intomainfrom
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| --- | ||
|
|
||
| # How to Fix the XERO01 Error | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO01 Error should be ## (H2), not # (H1). Only the article title should be H1. Subsections like "How to Fix" should use H2 to maintain a proper heading hierarchy.
| ## How to Fix the XERO01 Error |
|
|
||
| --- | ||
|
|
||
| # FAQ |
There was a problem hiding this comment.
Heading hierarchy violation: # FAQ should remain H1 per HelpDot convention, but the same file uses H1 for "How to Fix the XERO01 Error" on line 38, creating two competing H1 sections under the article title. The fix is to demote "How to Fix" to H2, keeping the document structure as: H1 title, H2 subsections, H1 FAQ.
Note: This same pattern (H1 for "How to Fix" sections) repeats across all error files in this PR. Please apply the fix consistently.
| - Xero requires reauthorization for security reasons. | ||
|
|
||
| Xero requires periodic reauthentication to maintain a secure integration. | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Reconnect Xero in New Expensify should be ## (H2), not # (H1). Only the article title should use H1. This applies to all "How to Fix/Reconnect" sections across the PR files.
| ## How to Reconnect Xero in New Expensify |
|
|
||
| --- | ||
|
|
||
| # How to Fix the XERO45 Sync Error |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO45 Sync Error should be ## (H2). Only the article title should be H1.
| # How to Fix the XERO45 Sync Error | |
| ## How to Fix the XERO45 Sync Error |
| Follow the steps below to select the correct Xero organization and retry the sync. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO84 Sync Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO84 Sync Error |
| --- | ||
|
|
||
| # How to Fix the XERO01 Error | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO01 Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO01 Error |
HelpDot Documentation ReviewOverall AssessmentThis PR adds 30 new markdown files documenting Xero integration error codes for New Expensify. The documentation covers authentication, connection, export, sync errors, and a general FAQ page. The writing quality is consistently strong across all files, with clear problem-error-solution structure. The files follow the established pattern set by the existing NetSuite troubleshooting docs. Scores Summary
Key FindingsPositive aspects:
Cross-category file duplication (intentional pattern):
Items to consider:
Recommendations
Files Reviewed
Unique content files (after removing duplicates): 19 files out of 30 total. |
|
|
||
| --- | ||
|
|
||
| # How to Fix the XERO45 Sync Error |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO45 Sync Error should be ## (H2). Only the article title should be H1.
| # How to Fix the XERO45 Sync Error | |
| ## How to Fix the XERO45 Sync Error |
| Follow the steps below to select the correct Xero organization and retry the sync. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO84 Sync Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO84 Sync Error |
| --- | ||
|
|
||
| # How to Fix the XERO01 Error | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO01 Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO01 Error |
|
|
||
| --- | ||
|
|
||
| # How to Fix the XERO08 Export Error |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO08 Export Error should be ## (H2). Only the article title should be H1.
| # How to Fix the XERO08 Export Error | |
| ## How to Fix the XERO08 Export Error |
|
|
||
| This is a billable expense configuration issue, not a connection issue. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO14 Export Error should be ## (H2). Only the article title should be H1.
| --- | |
| ## How to Fix the XERO14 Export Error |
| --- | ||
|
|
||
| # How to Fix the XERO27 Export Error | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO27 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO27 Export Error |
| --- | ||
|
|
||
| # How to Fix the XERO31 Export Error | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO31 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO31 Export Error |
| This is a financial lock setting issue in Xero, not a connection issue. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO33 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO33 Export Error |
|
|
||
| --- | ||
|
|
||
| # How to Fix the XERO44 Export Error |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO44 Export Error should be ## (H2). Only the article title should be H1.
| # How to Fix the XERO44 Export Error | |
| ## How to Fix the XERO44 Export Error |
| - The category is inactive in Xero’s Chart of Accounts. | ||
| - The account is not enabled for expense claims in Xero. | ||
|
|
||
| If the category is missing or invalid, Xero blocks the export. |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO52 Export Error should be ## (H2). Only the article title should be H1.
| If the category is missing or invalid, Xero blocks the export. | |
| ## How to Fix the XERO52 Export Error |
| ## Why the XERO56 Export Error Happens in Xero | ||
|
|
||
| The XERO56 error typically occurs when: | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO56 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO56 Export Error |
| - An expense or report uses a currency that has not been added in Xero. | ||
| - Multi-currency is not enabled in the Xero organization. | ||
| - Xero does not recognize the currency during export. | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO68 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO68 Export Error |
| This is a document status restriction in Xero, not a connection issue. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO76 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO76 Export Error |
| - A tracking category or tracking option (tag) has been deleted or made inactive. | ||
| - The account is not enabled for expense claims in Xero. | ||
| - The Workspace has not synced after changes were made in Xero. | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO78 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO78 Export Error |
| - Merchant names. | ||
| - Expense descriptions. | ||
| - Tags or tracking categories. | ||
| - Comments or notes. |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO83 Export Error should be ## (H2). Only the article title should be H1.
| - Comments or notes. | |
| ## How to Fix the XERO83 Export Error |
| The XERO87 error typically occurs when: | ||
|
|
||
| - The destination bank account selected in the Workspace no longer exists in Xero. | ||
| - The bank account has been deleted or made inactive in Xero. |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO87 Export Error should be ## (H2). Only the article title should be H1.
| - The bank account has been deleted or made inactive in Xero. | |
| ## How to Fix the XERO87 Export Error |
| - The Workspace has not synced after changes were made in Xero. | ||
|
|
||
| If any of these conditions apply, Xero blocks the export. | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO93 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO93 Export Error |
| - An expense is categorized under an account that is not configured for expense claims. | ||
| - A tax code intended for expense accounts is applied to an invoice-related or revenue account. | ||
| - The selected account type in Xero does not support the chosen TaxType. | ||
| - The account does not have **Show in Expense Claims** enabled. |
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO95 Export Error should be ## (H2). Only the article title should be H1.
| - The account does not have **Show in Expense Claims** enabled. | |
| ## How to Fix the XERO95 Export Error |
| - An additional bill is exported from the Workspace. | ||
|
|
||
| Once the monthly limit is reached, Xero blocks additional bill approvals until: | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO99 Export Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO99 Export Error |
| --- | ||
|
|
||
| # How to Fix the XERO01 Error | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Fix the XERO01 Error should be ## (H2). Only the article title should be H1.
| ## How to Fix the XERO01 Error |
| - Xero requires reauthorization for security reasons. | ||
|
|
||
| Xero requires periodic reauthentication to maintain a secure integration. | ||
|
|
There was a problem hiding this comment.
Heading hierarchy violation: # How to Reconnect Xero in New Expensify should be ## (H2). Only the article title should be H1.
| ## How to Reconnect Xero in New Expensify |
| 3. Click **Accounting**. | ||
| 4. Review the Xero connection status. | ||
| 5. If prompted, reconnect or reauthorize the Xero integration. | ||
| 6. Click **Save**. |
There was a problem hiding this comment.
Style compliance -- button label: Per Expensify style guidelines, the final action button at the end of a flow should be labeled Confirm, not Save. Please verify the actual button label in the product UI and update accordingly. If the button truly reads "Save" in this context, keep it; but if this is the final confirmation step, it should read "Confirm."
This same pattern (Click **Save**) appears in many files across this PR -- please audit all instances.
|
|
||
| 1. Tap the navigation tabs on the bottom. | ||
| 2. Tap **Workspaces**. | ||
| 3. Select your Workspace. |
There was a problem hiding this comment.
Style compliance -- button label: Click **Save** -- per Expensify style guidelines, the final action button at the end of a flow should be Confirm, not Save. Please verify the actual UI label. The same applies to Tap **Save** on line 62.
| 3. Select your Workspace. | |
| 6. Click **Confirm**. |
|
|
||
| If you see the error: | ||
|
|
||
| XERO01 Error: Unable to complete action to Xero. Please reach out to Concierge for additional assistance. |
There was a problem hiding this comment.
Readability: The error message text on this line is plain, unstyled text that blends with the surrounding prose. Consider wrapping it in a blockquote (>) or code block to visually distinguish it as an error message. This improves scannability. For example:
> XERO01 Error: Unable to complete action to Xero. Please reach out to Concierge for additional assistance.
This pattern applies to the error message display in all 30 files in this PR.
|
|
||
| XERO01 Error: Unable to complete action to Xero. Please reach out to Concierge for additional assistance. | ||
|
|
||
| It means there is a connection issue between the Workspace and Xero. |
There was a problem hiding this comment.
AI Readiness -- vague reference: "It means there is a connection issue..." -- starting a sentence with "It" after a blockquote/error message creates an ambiguous reference. Rephrase to be explicit:
| It means there is a connection issue between the Workspace and Xero. | |
| This error means there is a connection issue between the Workspace and Xero. |
github-actions
bot
changed the title
|
|
||
| ## Does the XERO01 Error Affect All Exports? | ||
|
|
||
| It can. If the Xero connection is disrupted, multiple reports or exports may fail until the connection is restored. |
There was a problem hiding this comment.
AI Readiness -- vague reference: "It can." starts the answer with a pronoun that lacks a clear antecedent. Rephrase for clarity:
| It can. If the Xero connection is disrupted, multiple reports or exports may fail until the connection is restored. | |
| Yes. If the Xero connection is disrupted, multiple reports or exports may fail until the connection is restored. |
| Yes. You must use a Xero account with admin permissions for the connected organization. | ||
|
|
||
| ## Will Disconnecting Remove My Configuration? | ||
|
|
There was a problem hiding this comment.
AI Readiness -- vague reference: "It may remove imported options..." -- "It" is ambiguous. Rephrase:
| Yes. Disconnecting may remove imported options and accounting settings. Save your configuration before disconnecting so you can reapply any custom settings if needed. |
|
|
||
| ## Run Sync | ||
|
|
||
| 1. Go to **Settings > Workspaces > [Workspace Name] > Accounting**. |
There was a problem hiding this comment.
AI Readiness -- non-descriptive heading: "Run Sync" is too generic. Headings should include the full task context so AI systems and readers scanning the page can understand what is being synced and why. Consider:
| 1. Go to **Settings > Workspaces > [Workspace Name] > Accounting**. | |
| ## Run Sync After Reconnecting Xero |
This same issue applies to all "Run Sync" headings across the PR files (e.g., XERO84-Sync-Error.md, XERO73-Sync-Error.md, etc.).
| ## Retry the Export | ||
|
|
||
| 1. Open the report. | ||
| 2. Retry exporting to Xero. |
There was a problem hiding this comment.
AI Readiness -- non-descriptive heading: "Retry the Export" is too generic. Consider including the error context: "Retry the Xero Export After Updating the Category". This applies to all "Retry the Export" headings across the Export-Errors files.
|
|
||
| 1. Open the report in Expensify. | ||
| 2. Review the error message in the comments. | ||
| 3. Make the required corrections. |
There was a problem hiding this comment.
AI Readiness -- non-descriptive heading: "How to Resolve Automatic Export Failures" is a sub-heading under the question, but if the questions are promoted to ## (as recommended), this becomes ### which violates heading depth rules. Consider folding this content directly into the question's answer rather than using a separate sub-heading. The same applies to "How to Resolve Manual Export Issues" on line 45 and "How to Fix It" on line 80.
|
|
||
| ## Recreate the Invoice in the Workspace | ||
|
|
||
| If the invoice status in the Workspace is: |
There was a problem hiding this comment.
Readability: The terms "invoice" and "report" are used interchangeably in this section (e.g., "Open the invoice" on line 42, "Move the expenses to a new invoice" on line 44, but "Submit the new invoice" on line 45). In Expensify, the document is a "report" that exports as an "invoice" to Xero. Clarify the terminology to avoid confusion -- use "report" when referring to the Expensify side and "invoice" only when referring to the Xero side.
| 2. Retry exporting to Xero. | ||
|
|
||
| If all expenses have valid Xero categories, the export should complete successfully. | ||
|
|
There was a problem hiding this comment.
AI Readiness -- vague reference: "It can affect one or multiple expenses." -- "It" lacks a clear antecedent. Rephrase:
| The XERO52 error can affect one or multiple expenses. All expenses on the report must have valid Xero categories. |
| --- | ||
|
|
||
| # FAQ | ||
|
|
There was a problem hiding this comment.
AI Readiness -- vague reference: "It affects exports that require access to Xero contacts..." -- "It" is ambiguous. Rephrase:
| The XERO56 error affects exports that require access to Xero contacts, such as billable expenses or vendor-related transactions. |
|
|
||
| --- | ||
|
|
||
| # FAQ |
There was a problem hiding this comment.
AI Readiness -- vague reference: "It can affect one or multiple expenses..." -- "It" is ambiguous. Rephrase to name the error explicitly:
| # FAQ | |
| The XERO78 error can affect one or multiple expenses depending on how many use inactive categories or tags. |
| # FAQ | ||
|
|
||
| ## Does the XERO93 Error Affect Only One Expense? | ||
|
|
There was a problem hiding this comment.
AI Readiness -- vague reference: "It affects any expense using an invalid or inactive category." -- "It" is ambiguous. Rephrase:
| The XERO93 error affects any expense using an invalid or inactive category. |
|
|
||
| # FAQ | ||
|
|
||
| ## Does the XERO87 Error Affect Reimbursable Reports? |
There was a problem hiding this comment.
AI Readiness -- vague reference: "It typically affects non-reimbursable exports..." -- "It" is ambiguous. Rephrase:
| ## Does the XERO87 Error Affect Reimbursable Reports? | |
| The XERO87 error typically affects non-reimbursable exports that require a designated bank account in the export configuration. |
| 3. Retry exporting to Xero. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
AI Readiness -- vague reference: "It affects bill exports that count toward the monthly approval limit..." -- "It" is ambiguous. Rephrase:
| The XERO99 error affects bill exports that count toward the monthly approval limit on the **Early** plan. |
| --- | ||
| title: Xero FAQ | ||
| description: Learn how to resolve common Xero export issues, automatic export failures, and connection problems in New Expensify. | ||
| keywords: Xero export not working, report not exporting automatically Xero, manually export report Xero, disconnect Xero New Expensify, already connected to Xero error |
There was a problem hiding this comment.
AI Readiness -- incomplete keywords: The keywords list is missing important terms that users might search for, such as "Xero troubleshooting", "Xero FAQ New Expensify", "Workspace Admin", and "Xero connection troubleshooting". Adding these would improve discoverability for both AI retrieval and search.
| keywords: Xero export not working, report not exporting automatically Xero, manually export report Xero, disconnect Xero New Expensify, already connected to Xero error | |
| keywords: Xero export not working, report not exporting automatically Xero, manually export report Xero, disconnect Xero New Expensify, already connected to Xero error, Xero troubleshooting, Xero FAQ New Expensify, Workspace Admin |
|
|
||
| ## Who Can Manually Export Reports? | ||
|
|
||
| Only **Workspace Admins** can manually export reports to Xero. |
There was a problem hiding this comment.
Readability -- confusing structure: This page is itself titled "Xero FAQ" (line 8), so having a separate # FAQ section at the bottom creates redundant nesting -- an FAQ within an FAQ. Consider either removing this bottom FAQ section and folding these two questions into the main body as additional top-level questions, or renaming this section to something like "## General Questions" to distinguish it from the error-specific questions above.
- Root: Configure, Connect, Xero-Troubleshooting. - Troubleshooting: Auth, Connection, Export, Sync errors, FAQ. - Hub pages already exist on main. Part of Integration Errors Revamp (splitting PR #83106).
stephanieelliott
force-pushed
the
helpsite-xero-new-expensify
branch
from
e41febc to
636466d
Compare
|
@stephanieelliott looks like this was merged without a test passing. Please add a note explaining why this was done and remove the |
|
🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.36-0 🚀
|
|
🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.36-10 🚀
|
3 participants
Master project issue https://github.com/Expensify/Expensify/issues/469226
Breaking main PR into smaller batches: #83106
Creates .MD files for Xero integration error messages (New Expensify)