[No QA] Create Sage-Intacct-Troubleshooting.md for New Expensify #82344
[No QA] Create Sage-Intacct-Troubleshooting.md for New Expensify #82344stephanieelliott merged 2 commits intomainfrom
Conversation
copy over the troubleshooting section from Classic since this is missing for New
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| @@ -0,0 +1,206 @@ | |||
| --- | |||
| title: Sage-Intacct-Troubleshooting.md | |||
There was a problem hiding this comment.
YAML Metadata Violation: The title field should contain a human-readable title, not the filename.
Fix: Change to:
title: Troubleshoot Sage Intacct Connection IssuesThis makes the title more descriptive and user-friendly while improving AI readability.
| --- | ||
| title: Sage-Intacct-Troubleshooting.md | ||
| description: Learn how to troubleshoot common synchronization and export errors between Expensify and Sage Intacct. | ||
| keywords: [Sage Intacct, troubleshooting, sync errors, export errors, Expensify Classic] |
There was a problem hiding this comment.
YAML Metadata Violation: The keywords include "Expensify Classic" which is incorrect terminology.
Fix: Remove "Expensify Classic" and add more relevant keywords like:
keywords: [Sage Intacct, troubleshooting, sync errors, export errors, connection, authentication, credit card]
| keywords: [Sage Intacct, troubleshooting, sync errors, export errors, Expensify Classic] | ||
| --- | ||
|
|
||
|
|
There was a problem hiding this comment.
Missing Breadcrumb: Add a breadcrumb navigation path below the H1 heading to help users understand their location in the documentation hierarchy.
Fix: Add after line 7:
Settings > Workspaces > Accounting > Sage Intacct
| Synchronizing and exporting data between Expensify and Sage Intacct streamlines financial processes, but errors can occasionally occur due to incorrect settings, missing data, or configuration issues. This guide outlines solutions to common issues, ensuring a seamless connection between your systems. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading Structure Violation: This should be a level 2 heading (##) not level 1 (#). The document should only have one H1 at the top.
Fix: Change to ## Common Sage Intacct Sync & Export Errors
| --- | ||
|
|
||
| # Common Sage Intacct Sync & Export Errors | ||
|
|
There was a problem hiding this comment.
Heading Structure Violation: This should be a level 2 heading (##) not level 1 (#) for consistency with document structure.
Fix: Change to ## Authentication Error
|
|
||
| **Error Message:** | ||
| *Sage Intacct experienced the following error trying to synchronize your workspace: Authentication error.* | ||
|
|
There was a problem hiding this comment.
Heading Level Violation: Using level 2 (##) for subsections under main topics creates poor hierarchy. These subsections should use level 3 (###).
Fix: Change to ### Why This Happens (and apply to all similar subsection headings throughout the document)
|
|
||
| ## Why This Happens | ||
| This error occurs when Expensify cannot authenticate the Sage Intacct connection due to incorrect credentials. | ||
|
|
There was a problem hiding this comment.
Heading Level Violation: This subsection heading should be level 3 (###) not level 2 (##) for proper hierarchy.
Fix: Change to ### How to Fix It
|
|
||
| 3. **Retry Connection** | ||
| - Attempt to sync again after making these changes. | ||
|
|
There was a problem hiding this comment.
Vague Reference Violation: "these changes" is a vague reference that could confuse AI and users about what specific changes to make.
Fix: Be more explicit:
- Attempt to sync again after adding Expensify to the Web Services authorizations list.
| **Note:** If the error persists, remove and re-add Expensify from the Web Services authorizations list. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading Structure Violation: This should be level 2 (##) to maintain consistency with other main issue headings in the document.
Fix: Change to ## Company Card Expenses Exporting to the Wrong Account
| **Behavior:** | ||
| Company card transactions are exporting to the wrong account. | ||
|
|
||
| ## Why This Happens |
There was a problem hiding this comment.
Heading Level Violation: Subsection headings should use level 3 (###) not level 2 (##).
Fix: Change to ### Why This Happens
| ## Why This Happens | ||
| This can be caused by incorrect account mapping, export settings, or user permissions. | ||
|
|
||
| ## How to Fix It |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### How to Fix It
| 2. **Confirm Card Mapping in Domain Control** | ||
| - Ensure company cards are mapped to the correct accounts. | ||
|
|
||
| 3. **Merge SmartScanned Receipts** |
There was a problem hiding this comment.
Vague Reference Violation: "them" is vague - be specific about what should be merged.
Fix: Change to:
- If SmartScanned receipts should have merged with company card transactions, verify the transactions match and manually merge the receipts if necessary.
|
|
||
| 3. **Merge SmartScanned Receipts** | ||
| - If SmartScanned receipts should have merged with company card transactions, verify and manually merge them if necessary. | ||
|
|
There was a problem hiding this comment.
Button Label Violation: Use "Next" instead of "Continue" to follow Expensify naming conventions.
Fix: Update the navigation path to reflect actual button labels used in the interface.
| - If multiple workspaces connect to the same accounting system, ensure expenses export under the correct workspace. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading Structure Violation: This should be level 2 (##) to match other main issue headings.
Fix: Change to ## Credit Card Configuration is Missing
|
|
||
| **Error Message:** | ||
| *Sage Intacct: Credit Card Configuration is Missing / You haven't yet set up credit cards in Sage Intacct.* | ||
|
|
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### Why This Happens
|
|
||
| ## Why This Happens | ||
| Sage Intacct requires a configured credit card account to process non-reimbursable expenses. | ||
|
|
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### How to Fix It
| - **Expiration:** Required but not crucial for roll-up card accounts. | ||
| - **Vendor ID:** Typically, the bank or card provider. | ||
|
|
||
| 2. **Link the Account in Expensify** |
There was a problem hiding this comment.
Button Label Violation: Verify if "Save" is the correct button label. In Expensify, final confirmation buttons typically use "Confirm" instead of "Save".
Fix: If this is the final step in a flow, change to:
- Click **Confirm**.
| - Go to **Expensify > Settings > Workspaces > [Workspace Name] > Accounting > Configure > Export**. | ||
| - Select the newly created credit card account. | ||
| - Click **Save**. | ||
|
|
There was a problem hiding this comment.
Heading Structure Violation: This should be level 2 (##) to match other main issue headings.
Fix: Change to ## Expensify Not Displaying Customers/Projects
|
|
||
| # Expensify Not Displaying Customers/Projects | ||
|
|
||
| **Behavior:** Customers or projects from Sage Intacct are not appearing in Expensify. |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### Why This Happens
| **Behavior:** Customers or projects from Sage Intacct are not appearing in Expensify. | ||
|
|
||
| ## Why This Happens | ||
| The Sage Intacct web services user lacks the required permissions. |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### How to Fix It
|
|
||
| 2. **Sync the Connection** | ||
| - In **Expensify**, go to **Settings > Workspaces > [Workspace Name] > Accounting > Sync Now**. | ||
|
|
There was a problem hiding this comment.
Heading Structure Violation: This should be level 2 (##) to match other main issue headings.
Fix: Change to ## ExpensiError INT009: Employee Manager Does Not Have a User Associated
|
Test comment |
| - In **Expensify**, go to **Settings > Workspaces > [Workspace Name] > Accounting > Sync Now**. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### Why This Happens
|
|
||
| # ExpensiError INT009: Employee Manager Does Not Have a User Associated | ||
|
|
||
| ## Why This Happens |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### How to Fix It
|
|
||
| - **If Using Approvals** | ||
| 1. Set the **First Approver** in **Sage Intacct > Time & Expenses > Configure Time & Expenses**. | ||
| 2. Ensure the **First Approver** is a Sage Intacct admin. |
There was a problem hiding this comment.
Heading Structure Violation: This should be level 2 (##) to match other main issue headings.
Fix: Change to ## ExpensiError INT012: "Reason for Expense" Note is Invalid
| 1. Set the **First Approver** in **Sage Intacct > Time & Expenses > Configure Time & Expenses**. | ||
| 2. Ensure the **First Approver** is a Sage Intacct admin. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### Why This Happens
| --- | ||
|
|
||
| # ExpensiError INT012: "Reason for Expense" Note is Invalid | ||
|
|
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### How to Fix It
|
|
||
| 1. **Disable Requirement in Sage Intacct** | ||
| - Go to **Time & Expenses > Configure Time & Expenses**. | ||
| - Under **Expense Report Requirements**, uncheck **Reason for Expense**. |
There was a problem hiding this comment.
Heading Structure Violation: This should be level 2 (##) to match other main issue headings.
Fix: Change to ## ExpensiError INT028: Use of an Empty Location is Invalid
| - Go to **Time & Expenses > Configure Time & Expenses**. | ||
| - Under **Expense Report Requirements**, uncheck **Reason for Expense**. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### Why This Happens
| --- | ||
|
|
||
| # ExpensiError INT028: Use of an Empty Location is Invalid | ||
|
|
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### How to Fix It
|
|
||
| 2. **Sync Expensify** | ||
| - Go to **Settings > Workspaces > [Workspace Name] > Accounting > Sync Now**. | ||
|
|
There was a problem hiding this comment.
Heading Structure Violation: This should be level 2 (##) to match other main issue headings.
Fix: Change to ## ExpensiError INT043: Not Authorized to Execute This Function
HelpDot Documentation ReviewOverall AssessmentThis PR adds a comprehensive troubleshooting guide for Sage Intacct integration by porting content from Expensify Classic. While the document provides valuable technical solutions to common errors, it has significant structural and formatting inconsistencies that reduce its effectiveness for both human readers and AI-powered help systems. Scores Summary
Key FindingsCritical Issues:
Positive Aspects:
RecommendationsPriority 1 (Must Fix):
Priority 2 (Recommended):
Additional ContextGiven this is temporary content per the PR description, I recommend focusing only on Priority 1 fixes for quick merge. |
| - Go to **Settings > Workspaces > [Workspace Name] > Accounting > Sync Now**. | ||
|
|
||
| 3. **Re-export the Report** | ||
| - Retry the export after syncing. |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### Why This Happens
| - Retry the export after syncing. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### How to Fix It
| - **Accounts Payable:** All | ||
|
|
||
| 2. **Sync Connection in Expensify** | ||
| - Go to **Settings > Workspaces > [Workspace Name] > Accounting > Sync Now**. |
There was a problem hiding this comment.
Heading Structure Violation: This should be level 2 (##) to match other main issue headings.
Fix: Change to ## ExpensiError INT054: No Sage Intacct Employee Found
| 2. **Sync Connection in Expensify** | ||
| - Go to **Settings > Workspaces > [Workspace Name] > Accounting > Sync Now**. | ||
|
|
||
| 3. **Retry Export** |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### Why This Happens
| 3. **Retry Export** | ||
| - Attempt to export again. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Heading Level Violation: This should be level 3 (###) not level 2 (##).
Fix: Change to ### How to Fix It
|
|
||
| ## Why This Happens | ||
| Expensify cannot find a matching employee record in Sage Intacct. | ||
|
|
There was a problem hiding this comment.
Vague Reference Violation: "they" is vague - be specific about what records to delete.
Fix: Change to:
- Delete duplicate employee records if they exist.
Detailed Examples of Issues1. YAML Title Issue (Line 2): # Current (INCORRECT):
title: Sage-Intacct-Troubleshooting.md
# Should be:
title: Sage Intacct Troubleshooting2. Heading Hierarchy Issue:
HelpDot standard (as seen in Connect-to-Sage-Intacct.md and Configure-Sage-Intacct.md):
3. Comparison with Other Troubleshooting Guides:
This doc mixes multiple patterns making it harder to scan. Files for reference:
|
github-actions
bot
changed the title
|
A preview of your ExpensifyHelp changes have been deployed to https://7b231078.helpdot.pages.dev ⚡️ Updated articles: |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 33ee03fc9d
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| 1. **Verify Permissions** | ||
| - In **Sage Intacct**, go to **Company > Users > Subscriptions**. | ||
| - Ensure the web services user has **Read-Only** permissions for the **Accounts Receivable (AR)** module. |
There was a problem hiding this comment.
The troubleshooting step for missing customers/projects tells admins to grant Accounts Receivable (AR) access, but the New Expensify setup guide for this same integration requires Projects (Read-only) when using projects/customers. In environments where AR is enabled but Projects access is missing, following this instruction will not restore project/customer imports, so the documented fix is ineffective for the stated error.
Useful? React with 👍 / 👎.
Concierge reviewer checklist:
For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member? |
|
@brianlee-expensify Please 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] |
|
Ignoring the bot comments since this is going to be replaced very soon - this is just a copy of the Classic page til the integration errors project replaces it |
Reviewer Checklist
Screenshots/VideosAndroid: HybridAppAndroid: mWeb ChromeiOS: HybridAppiOS: mWeb SafariMacOS: Chrome / Safari |
stephanieelliott
deleted the
helpsite-update-add-sage-troubleshooting
branch
|
🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.21-0 🚀
|
|
🚀 Deployed to production by https://github.com/mountiny in version: 9.3.21-4 🚀
|
3 participants
Copying this section over from Classic since this page is missing for New.
This will be replaced very shortly by @CortneyOfstad with the integrations error project so not worth putting a lot of time into improving it for format or AI retrieval .