[No QA] Add QuickBooks Online troubleshooting docs (Expensify Classic)#84817
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| This issue must be resolved in QuickBooks Online. | ||
|
|
||
| ### Enable Billable Expenses |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ### for sub-sections. HelpDot style requires headings to be # (H1) or ## (H2) only -- ### and deeper are not permitted. This applies to both ### Enable Billable Expenses (line 36) and ### Update the Account in the Chart of Accounts (line 45).
| ### Enable Billable Expenses | |
| ## Enable Billable Expenses |
| 5. Enable **Make expenses and items billable**. | ||
| 6. Save your changes. | ||
|
|
||
| ### Update the Account in the Chart of Accounts |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###.
| ### Update the Account in the Chart of Accounts | |
| ## Update the Account in the Chart of Accounts |
| 3. Go to **Account and Settings**. | ||
| 4. Select the **Expenses** tab. | ||
| 5. Enable **Make expenses and items billable**. | ||
| 6. Save your changes. |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows. This applies to line 43 (Save your changes) and line 52 (Save your changes). Consider rewording to "Confirm your changes" or restructuring the step to end with a "Confirm" action.
|
|
||
| This issue can be resolved by syncing categories and updating invalid expenses. | ||
|
|
||
| ### Sync QuickBooks Online Categories |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies here and to ### Recategorize Invalid Expenses on line 46.
| ### Sync QuickBooks Online Categories | |
| ## Sync QuickBooks Online Categories |
|
|
||
| This refreshes the Chart of Accounts from QuickBooks Online. | ||
|
|
||
| ### Recategorize Invalid Expenses |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###.
| ### Recategorize Invalid Expenses | |
| ## Recategorize Invalid Expenses |
|
|
||
| You can resolve this by updating record names or manually managing Vendor records. | ||
|
|
||
| ### Option 1: Edit the Employee Name in QuickBooks Online |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. HelpDot style limits headings to # and ## only. This applies to both ### Option 1 (line 37) and ### Option 2 (line 56).
| ### Option 1: Edit the Employee Name in QuickBooks Online | |
| ## Option 1: Edit the Employee Name in QuickBooks Online |
|
|
||
| --- | ||
|
|
||
| ### Option 2: Manually Create Vendor Records and Disable Automatic Entity Creation |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###.
| ### Option 2: Manually Create Vendor Records and Disable Automatic Entity Creation | |
| ## Option 2: Manually Create Vendor Records and Disable Automatic Entity Creation |
|
|
||
| ## How to Fix the ONL097 Export Error | ||
|
|
||
| You can resolve this by adjusting export settings or creating Vendor records. |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. HelpDot style limits headings to # and ## only. This applies to ### Option 1 (line 35), ### Option 2 (line 51), and ### Option 3 (line 67).
| You can resolve this by adjusting export settings or creating Vendor records. | |
| ## Option 1: Change the Export Type to Check |
|
|
||
| Retry exporting the report. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###.
| --- | |
| ## Option 2: Enable Automatically Create Entities |
|
|
||
| Then click **Sync Now** and retry exporting the report. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###.
| --- | |
| ## Option 3: Manually Create a Vendor Record |
|
|
||
| 1. Open the affected report. | ||
| 2. Review all billable expenses. | ||
| 3. Confirm each billable expense has a valid customer or project selected. |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all three sub-headings in this file: ### Confirm All Billable Expenses Have a Customer or Project (line 40), ### Confirm the Customer or Project Is Active in QuickBooks Online (line 47), and ### Sync QuickBooks Online (line 55).
| 3. Confirm each billable expense has a valid customer or project selected. | |
| ## Confirm All Billable Expenses Have a Customer or Project |
|
|
||
| This issue can be resolved by syncing and updating invalid tags. | ||
|
|
||
| ### Sync the QuickBooks Online Connection |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all three sub-headings: ### Sync the QuickBooks Online Connection (line 37), ### Update Invalid Tags on the Report (line 46), and ### Check for Unsupported Characters (line 55).
| ### Sync the QuickBooks Online Connection | |
| ## Sync the QuickBooks Online Connection |
| The ONL298 error typically indicates: | ||
|
|
||
| - A location was removed or renamed in QuickBooks Online. | ||
| - The location tag is no longer synced to the Workspace. |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all three sub-headings: ### Sync the QuickBooks Online Connection (line 23), ### Update Invalid Location Tags on the Report (line 32), and ### Check for Unsupported Characters (line 41).
| - The location tag is no longer synced to the Workspace. | |
| ## Sync the QuickBooks Online Connection |
|
|
||
| This issue can be resolved by adjusting export settings and verifying currencies. | ||
|
|
||
| ### Export as Vendor Bills in Multi-Currency Environments |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all three sub-headings: ### Export as Vendor Bills in Multi-Currency Environments (line 42), ### Confirm Account and Vendor Currency Match (line 56), and ### Check for Duplicate Vendor or Employee Records (line 67).
| ### Export as Vendor Bills in Multi-Currency Environments | |
| ## Export as Vendor Bills in Multi-Currency Environments |
| When this occurs, some transactions may be created in QuickBooks Online while others are not, resulting in a partial export. | ||
|
|
||
| This is generally a QuickBooks Online system issue, not a Workspace configuration issue. | ||
|
|
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all three sub-headings: ### Check QuickBooks Online Status (line 31), ### Delete Partial Transactions in QuickBooks Online (line 37), and ### Re-export the Report (line 48).
| ## Check QuickBooks Online Status |
|
|
||
| --- | ||
|
|
||
| ## How to Fix the ONL531 Export Error |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to both sub-headings: ### Refresh the Export Configuration (line 34) and ### Confirm All Mapped Values Are Active (line 49).
| ## How to Fix the ONL531 Export Error | |
| ## Refresh the Export Configuration |
| The ONL562 error typically indicates: | ||
|
|
||
| - The vendor associated with the report creator or submitter has a different currency than the selected A/P or A/R account. | ||
| - Duplicate vendor records exist with different currencies assigned. |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to both sub-headings: ### Confirm Vendor Currency (line 23) and ### Confirm A/P or A/R Account Currency (line 36).
| - Duplicate vendor records exist with different currencies assigned. | |
| ## Confirm Vendor Currency |
| This is a QuickBooks Online currency configuration issue, not a Workspace configuration issue. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all three sub-headings: ### Select a Different Export Account (line 31), ### Confirm Currency Matches Across Report, Vendor, and Export Account (line 47), and ### Confirm the Report Currency Is Correct (line 69).
| ## Select a Different Export Account |
|
|
||
| - A Vendor record already exists in QuickBooks Online. | ||
| - The email address on the Vendor record does not exactly match the email address used in Expensify. | ||
| - The same email address appears on multiple records (such as both an Employee and a Vendor). |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all three sub-headings: ### Confirm the Vendor Email Matches Expensify (line 24), ### Check for Duplicate Records (line 35), and ### Disable Automatic Entity Creation (If Needed) (line 50).
| - The same email address appears on multiple records (such as both an Employee and a Vendor). | |
| ## Confirm the Vendor Email Matches Expensify |
| QuickBooks Online does not support negative or zero-dollar checks. When reimbursable expenses are exported as checks, QuickBooks validates the total and blocks unsupported amounts. | ||
|
|
||
| This is a QuickBooks Online export limitation, not a Workspace configuration issue. | ||
|
|
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to both sub-headings: ### Change $0.00 Expenses to Non-Reimbursable (line 31) and ### Change the Export Type from Check (line 44).
| ## Change $0.00 Expenses to Non-Reimbursable |
|
|
||
| --- | ||
|
|
||
| ## How to Fix the ONL715 Export Error |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to both sub-headings: ### Refresh the Export Configuration (line 34) and ### Confirm All Mapped Values Are Active (line 49).
| ## How to Fix the ONL715 Export Error | |
| ## Refresh the Export Configuration |
| This issue can be resolved by reviewing billable expenses and updating categories. | ||
|
|
||
| ### Confirm Billable Expenses on the Report | ||
|
|
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to both sub-headings: ### Confirm Billable Expenses on the Report (line 47) and ### Confirm the Account Type Is Supported (line 55).
| ## Confirm Billable Expenses on the Report |
| ## How to Fix the ONL912 Export Error | ||
|
|
||
| This issue can be resolved by confirming active mappings and refreshing the Workspace. | ||
|
|
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all three sub-headings: ### Confirm Accounts Are Active (line 35), ### Confirm Related Records Are Active (line 46), and ### Sync the Workspace (line 57).
| ## Confirm Accounts Are Active |
github-actions
bot
changed the title
| ### Confirm the Account Is Active | ||
|
|
||
| 1. Log in to QuickBooks Online. | ||
| 2. Open the **Chart of Accounts**. |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to both sub-headings in this section and to ### Update Export Settings in Expensify (line 78).
| 2. Open the **Chart of Accounts**. | |
| ## Update Export Settings in Expensify |
| Log in to QuickBooks Online and create the required account type in the **Chart of Accounts**, based on your selected export option: | ||
|
|
||
| - **Vendor Bills** → Requires an **Accounts Payable** account | ||
| - **Journal Entries** → Requires: |
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to both sub-headings: ### Create the Required Account Type in QuickBooks Online (line 43) and ### Change the Export Type in Expensify (line 67).
| - **Journal Entries** → Requires: | |
| ## Create the Required Account Type in QuickBooks Online |
| internalScope: Audience is Workspace Admins and Domain Admins using the QuickBooks Online integration. Covers common export failures, manual export restrictions, company card mapping issues, disconnecting the integration, and negative expense exports. Does not cover specific QuickBooks error codes. | ||
| --- | ||
|
|
||
| # QuickBooks Online FAQ |
There was a problem hiding this comment.
FAQ structure violation: The H1 heading should be # FAQ, not # QuickBooks Online FAQ. Per HelpDot style, FAQ sections must use # FAQ as the heading.
| # QuickBooks Online FAQ | |
| # FAQ |
| 3. Click **Accounting**. | ||
| 4. Click **Configure**. | ||
| 5. Open the **Advanced** tab. | ||
| 6. Disable **Automatically Create Entities**. |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| 6. Disable **Automatically Create Entities**. | |
| 7. Click **Confirm**. |
| If the export account currency does not match the report currency: | ||
|
|
||
| 1. Go to **Settings > Workspaces**. | ||
| 2. Select your Workspace. |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| 2. Select your Workspace. | |
| 7. Click **Confirm**. |
| - Deactivate duplicate records if appropriate. | ||
|
|
||
| Only one active Vendor record should contain the matching email. | ||
|
|
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| 7. Click **Confirm**. |
| If the report total is negative or zero: | ||
|
|
||
| 1. Go to **Settings > Workspaces**. | ||
| 2. Select your Workspace. |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| 2. Select your Workspace. | |
| 7. Click **Confirm**. |
| 7. Click **Save**. | ||
|
|
||
| Then retry exporting the report. | ||
|
|
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| 7. Click **Confirm**. |
| 3. Click **Accounting**. | ||
| 4. Click **Configure**. | ||
| 5. Open the **Export** tab. | ||
| 6. Change the export type for **Reimbursable expenses** from **Journal Entry** to **Vendor Bill**. |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| 6. Change the export type for **Reimbursable expenses** from **Journal Entry** to **Vendor Bill**. | |
| 7. Click **Confirm**. |
| 7. Click **Save**. | ||
|
|
||
| Then retry exporting the report. | ||
|
|
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| 7. Click **Confirm**. |
| 2. Select your Workspace. | ||
| 3. Click **Accounting**. | ||
| 4. Click **Configure**. | ||
| 5. Open the **Export** tab. |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows. This same issue also appears on line 47.
| 5. Open the **Export** tab. | |
| 7. Click **Confirm**. |
| 2. Select your Workspace. | ||
| 3. Click **Accounting**. | ||
| 4. Click **Configure**. | ||
| 5. Open the **Export** tab. |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows. This same issue also appears on line 47.
| 5. Open the **Export** tab. | |
| 7. Click **Confirm**. |
|
|
||
| --- | ||
|
|
||
| ## How to Confirm ONL493 Is Resolved |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| ## How to Confirm ONL493 Is Resolved | |
| 7. Click **Confirm**. |
| @@ -0,0 +1,87 @@ | |||
| --- | |||
There was a problem hiding this comment.
Readability / structural concern: This file is nearly identical to Sync-Errors/ONL046-Sync-Error.md. Having duplicate articles for the same error code across two directories creates maintenance risk and may confuse both readers and AI retrieval systems. Consider consolidating into a single article in one location, or clearly differentiating the content if the error behaves differently in connection vs. sync contexts.
| @@ -0,0 +1,64 @@ | |||
| --- | |||
There was a problem hiding this comment.
Readability / structural concern: This file is nearly identical to Sync-Errors/ONL224-Sync-Error.md. Consider consolidating into a single article to avoid duplicate content and maintenance burden.
| @@ -0,0 +1,62 @@ | |||
| --- | |||
There was a problem hiding this comment.
Readability / structural concern: This file is nearly identical to Sync-Errors/ONL193-Sync-Error.md. Consider consolidating into a single article to avoid duplicate content and reduce maintenance burden.
| 4. Click **Configure**. | ||
| 5. Open the **Export** tab. | ||
| 6. Set **Reimbursable expenses** to **Vendor Bill**. | ||
| 7. Save your changes. |
There was a problem hiding this comment.
Button label violation: Per Expensify style, use "Confirm" instead of "Save" at the end of flows.
| 7. Save your changes. | |
| 7. Save your changes. |
Actually, since this step instructs to save in QuickBooks Online (a third-party app), "Save" is acceptable here. However, note that line 52 references saving in QBO which is fine, but the pattern should be reviewed for Expensify-specific flows where "Confirm" is correct.
HelpDot Documentation ReviewOverall AssessmentThis PR adds 35 new markdown documentation files covering QuickBooks Online troubleshooting for Expensify Classic, organized into four subdirectories (Authentication-and-Login-errors, Connection-errors, Export-Errors, Sync-Errors) plus a general FAQ. The documentation is impressively well-structured, consistent, and user-friendly. Each error code article follows a uniform template: error description, cause explanation, step-by-step fix, and FAQ section. The writing is clear and accessible, and the YAML metadata is thorough. There are a few issues worth addressing, most notably duplicate files across directories and some heading hierarchy concerns. Scores Summary
Key FindingsPositive aspects:
Issues to address:
Recommendations
Files Reviewed
Note: This review covers the full set of proposed changes. Detailed line-by-line feedback can be provided as inline comments if requested. |
|
|
||
| If you see the error: | ||
|
|
||
| ONL193: Couldn’t connect to QuickBooks Online. |
There was a problem hiding this comment.
Readability: The error message text should be formatted as a blockquote or code block to visually distinguish it from the surrounding explanatory text. This improves scannability and helps readers quickly identify the exact error string. For example:
| ONL193: Couldn’t connect to QuickBooks Online. | |
| > ONL193: Couldn't connect to QuickBooks Online. |
This pattern should be applied consistently across all error articles in this PR.
|
|
||
| --- | ||
|
|
||
| ## How to Review Receipts After ONL329 |
There was a problem hiding this comment.
AI Readiness: The heading references the error code without the full feature context. Consider a more descriptive heading like ## How to Review Receipts After the ONL329 Export Error. This helps AI systems and search engines understand the content without needing the surrounding context.
| ## How to Fix the ONL888 Export Error | ||
|
|
||
| You can resolve this by reopening the period or adjusting the export date. | ||
|
|
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. HelpDot style limits headings to # and ## only. This applies to both sub-headings: ### Reopen the Closed Reporting Period (line 35) and ### Change the Export Date in Expensify (line 53). Note: These headings are nested under the ## How to Fix section, but HelpDot does not support ### depth. Restructure to use ## headings or convert to numbered steps within the parent section.
| ## Reopen the Closed Reporting Period |
| If the report is in **Draft** status, selecting export may result in an empty screen. | ||
|
|
||
| ### How to resolve manual export issues | ||
|
|
There was a problem hiding this comment.
Heading level violation: Use ## instead of ###. This applies to all ### sub-headings in this file (lines 21, 36, 48, 64, 80).
| ## How to resolve manual export issues |
| 3. Click **Accounting**. | ||
| 4. Click **Configure**. | ||
| 5. Open the **Export** tab. | ||
| 6. Set **Reimbursable expenses** to **Vendor Bill**. |
There was a problem hiding this comment.
Button label note (cross-cutting): Across this PR, many Expensify-specific flows end with Click **Save**. Per Expensify style, flows that finalize settings within Expensify should use Click **Confirm**. Steps that occur within QuickBooks Online (a third-party app) can appropriately use "Save your changes." Please audit all files in this PR and update Click **Save** to Click **Confirm** for Expensify flow steps only.
- Root: Configure, Connect, 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-quickbooks-online-expensify-classic
branch
from
dd75022 to
7837b35
Compare
stephanieelliott
deleted the
helpsite-quickbooks-online-expensify-classic
branch
|
@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 QBO integration error messages (Classic)