[No QA] Add Xero troubleshooting docs (Expensify Classic)#84822
[No QA] Add Xero troubleshooting docs (Expensify Classic)#84822stephanieelliott merged 1 commit intomainfrom
Conversation
|
|
||
| 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 violation: The error message text on lines 12-12 is displayed as plain paragraph text, making it hard to distinguish from the surrounding explanation. Wrap the error message in a blockquote (>) or code block so it visually stands out as a literal error string.
| XERO01 Error: Unable to complete action to Xero. Please reach out to Concierge for additional assistance. | |
| > XERO01 Error: Unable to complete action to Xero. Please reach out to Concierge for additional assistance. |
| @@ -0,0 +1,61 @@ | |||
| --- | |||
There was a problem hiding this comment.
Duplicate content: This file is identical to Connection-errors/XERO01-Error.md, Export-Errors/XERO01-Error.md, and Sync-Errors/XERO01-Error.md. Having four copies of the same content creates maintenance burden and confuses AI retrieval systems that may surface conflicting or redundant results. Consider using a single canonical file and linking to it from the other categories, or differentiating the content per category with context-specific troubleshooting steps.
| # XERO11 Sync Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO11 Sync Error: The connection to Xero has expired. Please follow prompts in the workspace to reconnect. |
| @@ -0,0 +1,72 @@ | |||
| --- | |||
There was a problem hiding this comment.
Duplicate content: This file is identical to Sync-Errors/XERO11-Sync-Error.md. Consider using a single canonical file to avoid maintenance duplication and AI retrieval confusion.
|
|
||
| # XERO45 Sync Error in Xero Integration | ||
|
|
||
| If you see the error: |
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| If you see the error: | |
| > XERO45 Sync Error: Unable to sync Xero data due to an invalid authentication token. Please disconnect and reconnect Xero in the workspace. |
| @@ -0,0 +1,99 @@ | |||
| --- | |||
There was a problem hiding this comment.
Duplicate content: This file is identical to Connection-errors/XERO45-Sync-Error.md and Sync-Errors/XERO45-Sync-Error.md. Three copies of the same content. Consider consolidating into a single canonical file.
|
|
||
| If you see the error: | ||
|
|
||
| XERO84 Sync Error: There was a problem syncing Xero data. Please select which Xero organization or company this workspace should sync with. |
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| XERO84 Sync Error: There was a problem syncing Xero data. Please select which Xero organization or company this workspace should sync with. | |
| > XERO84 Sync Error: There was a problem syncing Xero data. Please select which Xero organization or company this workspace should sync with. |
| @@ -0,0 +1,71 @@ | |||
| --- | |||
There was a problem hiding this comment.
Duplicate content: This file is identical to Connection-errors/XERO84-Sync-Error.md and Sync-Errors/XERO84-Sync-Error.md. Three copies of the same content. Consider consolidating into a single canonical file.
| # XERO08 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO08 Export Error: PDF of report is too large to export (>10MB). Please reach out to Concierge for additional assistance. |
| # XERO14 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO14 Export Error: Billable expenses require a customer. Please associate a customer on all billable transactions before exporting to Xero. |
| # XERO27 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO27 Export Error: Category not found. The category may be deleted or inactive in Xero so please select new category. |
| # XERO31 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO31 Export Error: This expense has already been marked as paid in Xero, so it can't be updated. |
HelpDot Documentation ReviewOverall AssessmentThis PR adds 30 new Markdown files for Xero integration error troubleshooting under Scores Summary
Key FindingsDuplicate files are the most significant issue. The following files are identical copies placed in multiple directories:
This means only 18 unique articles exist across 30 files. These duplicates create maintenance burden and will confuse search/AI systems. Heading hierarchy is broken in all files. Every error article has two H1 headings ( Error messages lack visual distinction. Error messages are rendered as plain paragraph text. Using a blockquote ( Positive aspects:
Recommendations
Files ReviewedAuthentication-and-Login-errors/
Connection-errors/
Export-Errors/ (17 files, all unique content)
Sync-Errors/
Troubleshooting root
Note: Detailed line-by-line feedback has been provided as inline comments. |
| # XERO33 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO33 Export Error: The report can't be exported because it's dated before the year-end lock date. Please update the year-end lock date in Xero and attempt to export again. |
| # XERO52 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO52 Export Error: All expenses must have a Xero account selected as the category. |
| # XERO56 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO56 Export Error: Unable to load Xero contacts. |
| # XERO68 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO68 Export Error: Currency not set up or enabled in Xero. Please add the currency in Xero, and try exporting again. |
| # XERO76 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO76 Export Error: This report was previously exported and then voided in Xero. Voided bills can't be updated or re-exported. |
| # XERO78 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO78 Export Error: Expense [merchant name] has an invalid category or tag. Please confirm the selected category or tag is active within Xero. |
| # XERO83 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO83 Export Error: XML post data has an invalid character. Please reach out to Concierge for additional assistance. |
| # XERO87 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO87 Export Error: Missing or invalid bank account. Please confirm an active bank account has been selected in the Expensify configurations before exporting. |
| # XERO93 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO93 Export Error: Expense [merchant name] has an invalid category. Please confirm the selected category is active, listed as an 'Expense' type, and has 'Show in Expense Claims' checked in Xero. |
| # XERO95 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO95 Export Error: The TaxType [XXXX] cannot be used with account [YYYY]. Please select a new category and attempt to export again. |
| # XERO99 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO99 Export Error: Xero invoice approval limit reached. The 'Early' Xero plan allows up to 5 bills per month. Please upgrade your plan or retry after the billing cycle resets. |
| # XERO44 Export Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO44 Export Error: Invoice status in Xero cannot be modified. This invoice was previously exported and then voided in Xero. Voided invoices can't be updated or re-exported. |
| # XERO73 Sync Error in Xero Integration | ||
|
|
||
| If you see the error: | ||
|
|
There was a problem hiding this comment.
Readability violation: Error message should be wrapped in a blockquote (>) to visually distinguish it from explanatory text.
| > XERO73 Sync Error: Could not retrieve Xero chart of accounts. Please make sure the accounts in Xero are set to 'Expense' type and have 'Show in Expense Claims' enabled. |
|
|
||
| --- | ||
|
|
||
| ## Reopen the Invoice in the Workspace and Create a New Invoice |
There was a problem hiding this comment.
Heading level violation: This ## Reopen the Invoice... heading appears as a standalone section after the --- divider, at the same level as the ## How to Fix heading. Since this is a sub-step of the fix workflow, it should use ### (a subsection under "How to Fix the XERO44 Export Error"), not ##. The same applies to ## Manually Recreate the Invoice in Xero on line 60.
| ## Reopen the Invoice in the Workspace and Create a New Invoice | |
| ### Reopen the Invoice in the Workspace and Create a New Invoice |
|
|
||
| --- | ||
|
|
||
| ## Manually Recreate the Invoice in Xero |
There was a problem hiding this comment.
Heading level violation: This should be ### to remain a sub-step under the fix section, consistent with the rest of the document structure.
| ## Manually Recreate the Invoice in Xero | |
| ### Manually Recreate the Invoice in Xero |
|
|
||
| --- | ||
|
|
||
| # How Do I Disconnect the Xero Connection? |
There was a problem hiding this comment.
Heading level violation: Use ## instead of # for FAQ questions.
| # How Do I Disconnect the Xero Connection? | |
| ## How Do I Disconnect the Xero Connection? |
|
|
||
| --- | ||
|
|
||
| # Why Does It Show That I’m Already Connected to Xero? |
There was a problem hiding this comment.
Heading level violation: Use ## instead of # for FAQ questions.
| # Why Does It Show That I’m Already Connected to Xero? | |
| ## Why Does It Show That I'm Already Connected to Xero? |
|
|
||
| --- | ||
|
|
||
| # Why Do Non-Reimbursable Expenses Show “Credit Card Misc” Instead of the Merchant? |
There was a problem hiding this comment.
Heading level violation: Use ## instead of # for FAQ questions.
| # Why Do Non-Reimbursable Expenses Show “Credit Card Misc” Instead of the Merchant? | |
| ## Why Do Non-Reimbursable Expenses Show "Credit Card Misc" Instead of the Merchant? |
|
|
||
| --- | ||
|
|
||
| # Why Are Company Card Expenses Still Exporting to the Wrong Account? |
There was a problem hiding this comment.
Heading level violation: Use ## instead of # for FAQ questions.
| # Why Are Company Card Expenses Still Exporting to the Wrong Account? | |
| ## Why Are Company Card Expenses Still Exporting to the Wrong Account? |
|
|
||
| --- | ||
|
|
||
| # What If I Fixed the Settings but Exports Still Fail? |
There was a problem hiding this comment.
Heading level violation: Use ## instead of # for FAQ questions.
| # What If I Fixed the Settings but Exports Still Fail? | |
| ## What If I Fixed the Settings but Exports Still Fail? |
|
|
||
| --- | ||
|
|
||
| # FAQ |
There was a problem hiding this comment.
FAQ structure violation: This file is already entirely an FAQ (titled "Xero FAQ" with # Xero FAQ at the top). Having a nested # FAQ section at line 156 with ## sub-questions creates a confusing double-FAQ structure. Either remove this nested section and promote its questions to be ## headings like the rest of the file, or integrate them into the main body above.
| This usually means the company card mapping is incorrect or the Preferred Exporter does not have the required permissions. | ||
|
|
||
| ## Step 1: Confirm Company Card Mapping | ||
|
|
There was a problem hiding this comment.
Heading level violation: The sub-steps under FAQ questions use ## Step 1: and ## Step 2: headings (lines 54 and 64), which are at the same level as the FAQ questions themselves. These should use ### to indicate they are sub-sections of the parent question.
| ### Step 1: Confirm Company Card Mapping |
|
|
||
| --- | ||
|
|
||
| ## Step 2: Confirm the Preferred Exporter Is a Domain Admin |
There was a problem hiding this comment.
Heading level violation: This should be ### to nest under the parent FAQ question, not ##.
| ## Step 2: Confirm the Preferred Exporter Is a Domain Admin | |
| ### Step 2: Confirm the Preferred Exporter Is a Domain Admin |
| - The error appears in the **report comments** section. | ||
| - Reports with errors will not automatically export until the issue is resolved. | ||
|
|
||
| ## How to Resolve Automatic Export Failures |
There was a problem hiding this comment.
Heading level violation: This ## How to Resolve Automatic Export Failures heading is a sub-section of the question above it ("Why Is My Report Not Automatically Exporting to Xero?"). If the question headings are changed to ## as recommended, this should become ###.
| ## How to Resolve Automatic Export Failures | |
| ### How to Resolve Automatic Export Failures |
| - **Paid** | ||
|
|
||
| If the report is in **Draft**, selecting Export may load an empty screen. | ||
|
|
There was a problem hiding this comment.
Heading level violation: This ## How to Resolve Manual Export Issues heading is a sub-section under the parent question. If the question headings become ##, this should become ###.
| ### How to Resolve Manual Export Issues |
|
|
||
| If you see a message that you are already connected when trying to connect for the first time, the existing connection may still be active in Xero. | ||
|
|
||
| ## How to Fix It |
There was a problem hiding this comment.
Heading level violation: This ## How to Fix It heading is a sub-section under the parent question. If the question headings become ##, this should become ###.
| ## How to Fix It | |
| ### How to Fix It |
|
|
||
| ## How to Fix It | ||
|
|
||
| Use **Expense Rules** in Expensify to standardize merchant names. |
There was a problem hiding this comment.
Heading level violation: This ## How to Fix It heading is a sub-section under the parent question. If the question headings become ##, this should become ###.
| Use **Expense Rules** in Expensify to standardize merchant names. | |
| ### How to Fix It |
|
|
||
| If you see the error: | ||
|
|
||
| XERO87 Export Error: Missing or invalid bank account. Please confirm an active bank account has been selected in the Expensify configurations before exporting. |
There was a problem hiding this comment.
AI Readiness violation: The phrase "Expensify configurations" is vague. It should specify the exact location, e.g., "the Workspace accounting settings" or "Settings > Workspaces > Accounting > Configure > Export" to help both readers and AI retrieval systems understand the precise navigation path.
|
|
||
| # Xero FAQ | ||
|
|
||
| --- |
There was a problem hiding this comment.
Readability violation: The horizontal rule (---) immediately after the # Xero FAQ heading (line 10) adds unnecessary visual noise. The H1 heading already creates visual separation. Consider removing this divider.
| --- |
|
|
||
| # Why Do Non-Reimbursable Expenses Show “Credit Card Misc” Instead of the Merchant? | ||
|
|
||
| If a merchant name in Expensify does not exactly match a Contact in Xero (for example, `Merchant` vs. `Merchant.com`), the expense will default to **Expensify Credit Card Misc** to prevent duplicate contacts. |
There was a problem hiding this comment.
AI Readiness violation: The phrase "Merchant name in Expensify does not exactly match a Contact in Xero (for example, Merchant vs. Merchant.com)" is helpful, but the heading "Credit Card Misc" is Xero-specific jargon without context. Consider expanding the description slightly, e.g., mentioning that "Credit Card Misc" refers to the default fallback Contact name "Expensify Credit Card Misc" that Xero uses when no match is found.
|
|
||
| ## How to Fix the XERO44 Export Error | ||
|
|
||
| You have two options depending on the invoice status in the Workspace. |
There was a problem hiding this comment.
Readability violation: The sentence "You have two options depending on the invoice status in the Workspace" is followed by a --- divider and then ## Reopen the Invoice.... The divider breaks the logical flow between the introduction and its options. Remove the --- to keep the options visually connected to their introductio
48C2
n.
| You have two options depending on the invoice status in the Workspace. |
| --- | ||
|
|
||
| ## How to Fix the XERO76 Export Error | ||
|
|
There was a problem hiding this comment.
Readability violation: The --- divider between "You have two options..." and the first option heading breaks the logical flow. Remove this divider to keep the options connected to their introduction.
- 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).
bc10a1d to
0891c39
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 🚀
|
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 (Classic)