[No QA] Add Certinia troubleshooting docs (Expensify Classic only)#84814
[No QA] Add Certinia troubleshooting docs (Expensify Classic only)#84814stephanieelliott merged 1 commit intomainfrom
Conversation
Concierge reviewer checklist:
For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member? cc @sonialiap |
|
@Gonals @sonialiap 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] |
|
@MelvinBot why is the PR author checklist test failing? As this is an .md file under /docs, the PR author checklist should be skipped |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| @@ -0,0 +1,64 @@ | |||
| --- | |||
| title: CER047 Export Error in Certinia Integration | |||
There was a problem hiding this comment.
Copy-paste error (Sync vs Export): This file is in the Sync-Errors/ directory, but the title says "CER047 Export Error in Certinia Integration." The title, description, heading, and body references should say "Sync Error" instead of "Export Error" to match its categorization. This same issue appears in the description (line 3), keywords (line 4), internalScope (line 5), the H1 heading (line 8), and the H2 section headings (lines 18, 30). Please update all occurrences of "Export Error" to "Sync Error" throughout this file.
| title: CER047 Export Error in Certinia Integration | |
| title: CER047 Sync Error in Certinia Integration |
| @@ -0,0 +1,66 @@ | |||
| --- | |||
| title: CER074 Export Error in Certinia Integration | |||
There was a problem hiding this comment.
Copy-paste error (Sync vs Export): This file is in the Sync-Errors/ directory, but the title says "CER074 Export Error in Certinia Integration." The title, description, heading, and body references should say "Sync Error" instead of "Export Error" to match its categorization. This same issue appears in the description (line 3), keywords (line 4), internalScope (line 5), the H1 heading (line 8), and the H2 section headings (lines 18, 32). Please update all occurrences of "Export Error" to "Sync Error" throughout this file.
| title: CER074 Export Error in Certinia Integration | |
| title: CER074 Sync Error in Certinia Integration |
| @@ -0,0 +1,66 @@ | |||
| --- | |||
| title: CER937 Export Error in Certinia Integration | |||
There was a problem hiding this comment.
Copy-paste error (Sync vs Export): This file is in the Sync-Errors/ directory, but the title says "CER937 Export Error in Certinia Integration." The title, description, heading, and body references should say "Sync Error" instead of "Export Error" to match its categorization. This same issue appears in the description (line 3), keywords (line 4), internalScope (line 5), the H1 heading (line 8), and the H2 section headings (lines 18, 30). Please update all occurrences of "Export Error" to "Sync Error" throughout this file.
| title: CER937 Export Error in Certinia Integration | |
| title: CER937 Sync Error in Certinia Integration |
| internalScope: Audience is Workspace Admins and Certinia Admins using the Certinia integration. Covers resolving the CER937 error caused by an outdated Certinia integration configuration. Does not cover other Certinia error codes. | ||
| --- | ||
|
|
||
| # CER937 Error in Certinia Integration |
There was a problem hiding this comment.
Content duplication concern: CER937 appears in three separate directories -- Authentication-and-Login-errors/, Export-Errors/, and Sync-Errors/ -- with nearly identical content (same title, same fix steps, same FAQ). This creates a maintenance burden and risks content drift over time. Consider one of these approaches:
- Single canonical article with a note that CER937 can appear during authentication, export, or sync operations.
- Hub-level cross-references that link to one canonical CER937 article from each category.
If there is a deliberate reason to keep three copies (e.g., different audiences land in different categories), each file should at minimum differentiate its content to explain why the error surfaces in that specific context (authentication vs. export vs. sync).
| internalScope: Audience is Workspace Admins using the Certinia integration. Covers resolving the CER047 export error caused by missing Expense Ops Edit permissions. Does not cover other Certinia error codes. | ||
| --- | ||
|
|
||
| # CER047 Export Error in Certinia Integration |
There was a problem hiding this comment.
Content duplication concern: CER047 appears in both Export-Errors/ and Sync-Errors/ with nearly identical content. If the error genuinely appears in both contexts, each article should explain the context-specific scenario (e.g., "when this error occurs during a sync..." vs "when this error occurs during an export..."). Otherwise, consolidate into a single article and cross-reference from the other category.
| internalScope: Audience is Workspace Admins using the Certinia integration. Covers resolving the CER074 export error caused by missing or incorrect Permission Controls. Does not cover other Certinia error codes. | ||
| --- | ||
|
|
||
| # CER074 Export Error in Certinia Integration |
There was a problem hiding this comment.
Content duplication concern: CER074 appears in both Export-Errors/ and Sync-Errors/ with nearly identical content. If the error genuinely appears in both contexts, each article should explain the context-specific scenario. Otherwise, consolidate into a single article and cross-reference from the other category.
| If you see the error: | ||
|
|
||
| CER937: Please update Expensify in Certinia. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>) or inline code block to visually distinguish it from surrounding prose. As plain text, it blends into the paragraph and is harder to scan. This applies to all 17 error articles in this PR.
| > CER937: Please update Expensify in Certinia. |
| If you see the error: | ||
|
|
||
| CER047: "Ops Edit" permission is required to edit approved records. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>) or inline code block to visually distinguish it from surrounding prose.
| > CER047: "Ops Edit" permission is required to edit approved records. |
|
The checklist isn't being skipped because one of the files in this PR falls outside the The workflow at paths-ignore: ['docs/articles/**/*.md', 'docs/redirects.csv', 'docs/assets/images/**']Your 17 That Once triggered, the check crashes with To fix this, you have two options:
|
| If you see the error: | ||
|
|
||
| CER061: Object validation failed. The credit terms for the selected account are not correctly defined. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>) to visually distinguish it from surrounding prose.
| > CER061: Object validation failed. The credit terms for the selected account are not correctly defined. |
| If you see the error: | ||
|
|
||
| CER074: Insufficient permissions for Resource. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER074: Insufficient permissions for Resource. |
| If you see the error: | ||
|
|
||
| CER076: Employee not found in Certinia. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER076: Employee not found in Certinia. |
| If you see the error: | ||
|
|
||
| CER089: Assignment required for Project. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER089: Assignment required for Project. |
| If you see the error: | ||
|
|
||
| CER091: Invalid field name. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER091: Invalid field name. |
| If you see the error: | ||
|
|
||
| CER289: Duplicate value on record. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER289: Duplicate value on record. |
| If you see the error: | ||
|
|
||
| CER493: Necessary field unavailable in mapping. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER493: Necessary field unavailable in mapping. |
| If you see the error: | ||
|
|
||
| CER521: Assignment resource must match expense report resource. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER521: Assignment resource must match expense report resource. |
| If you see the error: | ||
|
|
||
| CER552: No project managers found in Certinia. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER552: No project managers found in Certinia. |
| If you see the error: | ||
|
|
||
| CER937: Please update Expensify in Certinia. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER937: Please update Expensify in Certinia. |
| If you see the error: | ||
|
|
||
| CER047: "Ops Edit" permission is required to edit approved records. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER047: "Ops Edit" permission is required to edit approved records. |
| If you see the error: | ||
|
|
||
| CER074: Insufficient permissions for Resource. | ||
|
|
There was a problem hiding this comment.
Readability / Formatting violation: The error message text should be formatted as a blockquote (>).
| > CER074: Insufficient permissions for Resource. |
| Disconnecting removes the active integration and clears imported options. | ||
|
|
||
| ### How to disconnect Certinia | ||
|
|
There was a problem hiding this comment.
AI Readiness / Heading hierarchy violation: ### heading should be ## per HelpDot standards.
| ## How to disconnect Certinia |
| - **Project Status** = Closed | ||
| - **Closed for Expense Entry** = Checked | ||
|
|
||
| ### How to resolve project export limitations |
There was a problem hiding this comment.
AI Readiness / Heading hierarchy violation: ### heading should be ## per HelpDot standards.
| ### How to resolve project export limitations | |
| ## How to resolve project export limitations |
|
|
||
| Yes. Project settings in Certinia can prevent expenses from exporting. | ||
|
|
||
| ### Expenses can be exported when: |
There was a problem hiding this comment.
AI Readiness / Heading hierarchy violation: ### headings like "Expenses can be exported when:" and "Expenses cannot be exported when:" (lines 96 and 102) should be ## per HelpDot standards. No heading level deeper than H2 should be used.
|
|
||
| ## Can I Retry the Export? | ||
|
|
||
| Yes. After enabling **Expense Ops Edit** and selecting **Sync Now**, retry the export. If the error persists, confirm the permission is applied to the exact user connected to the integration. |
There was a problem hiding this comment.
AI Readiness / FAQ Title Case violation: FAQ questions throughout this file use Title Case ("Can I Retry the Export?", "Does CER047 Mean My Expense Was Deleted?", "Is CER047 Caused by Workspace Settings?"). Use sentence case instead for consistency: "Can I retry the export?", "Does CER047 mean my expense was deleted?", "Is CER047 caused by workspace settings?" This applies to all FAQ sections across all error articles in this PR.
| Yes. After enabling **Expense Ops Edit** and selecting **Sync Now**, retry the export. If the error persists, confirm the permission is applied to the exact user connected to the integration. | |
| ## Can I retry the export? |
| - Required credit term fields are missing on the associated account. | ||
| - Credit term configuration does not meet Certinia validation requirements. | ||
| - The export is being blocked due to incomplete payment term settings. | ||
|
|
There was a problem hiding this comment.
Readability violation: The phrase "Enter one or more in Days Offset" is unclear. It should specify what to enter -- e.g., "Enter a value of one or more in Days Offset" or "Set Days Offset to at least 1."
|
|
||
| ### How to verify company card export mapping | ||
|
|
||
| 1. Go to the navigation tabs on the left. |
There was a problem hiding this comment.
Readability / Navigation path concern: The navigation instructions here say "Go to the navigation tabs on the left" and then "Click Settings" followed by "Click Domains." This Expensify Classic navigation path appears multiple times in this file (lines 49-52, 64-66, 80-82). Consider using a consistent, concise format such as: "Go to Settings > Domains > Company Cards" to match the compact navigation path style used in the error articles (e.g., "Settings > Workspaces").
| This means Certinia has detected that the Expensify integration configuration is outdated and must be updated before exports or syncs can proceed. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Readability violation: Horizontal rules (---) are used as section dividers between every section (lines 17, 34, 51, and before FAQ). This is excessive in a short article and creates visual clutter rather than improving scannability. Headings already provide sufficient visual separation. Consider removing all --- dividers, or reserving them only before the # FAQ section as a convention to separate the main content from FAQs. This pattern applies to all 16 error articles in this PR.
| --- | ||
| title: CER937 Error in Certinia Integration | ||
| description: Learn what the CER937 error means in Certinia and how to update the Expensify integration configuration to restore syncing. | ||
| keywords: CER937, Certinia export error, update Expensify in Certinia, Certinia connection issue, Expensify Certinia sync error, Workspace Admin |
There was a problem hiding this comment.
AI Readiness / Keywords concern: The keywords include "Certinia export error" but this file is in the Authentication-and-Login-errors/ directory. Consider replacing "Certinia export error" with "Certinia authentication error" or "Certinia login error" to match the categorization and improve search discoverability for authentication-related queries.
| keywords: CER937, Certinia export error, update Expensify in Certinia, Certinia connection issue, Expensify Certinia sync error, Workspace Admin | |
| keywords: CER937, Certinia authentication error, update Expensify in Certinia, Certinia connection issue, Expensify Certinia sync error, Workspace Admin |
github-actions
bot
changed the title
| title: Certinia Integration FAQ and Export Troubleshooting | ||
| description: Learn why reports may not export to Certinia, how to manually export, fix company card export issues, manage project limitations, and disconnect the Certinia integration. | ||
| keywords: Certinia export not working, automatic export failed, manual export Certinia, company card wrong account export, preferred exporter domain admin, disconnect Certinia, Certinia project status export limitation, assignment status export, Workspace Admin | ||
| internalScope: Audience is Workspace Admins and Domain Admins using the Certinia integration. Covers common export failures, manual export restrictions, company card export mapping, project limitations, and disconnecting Certinia. Does not cover specific Certinia error codes. |
There was a problem hiding this comment.
AI Readiness / YAML metadata concern: The frontmatter keywords field includes "Workspace Admin" as a keyword. While the internalScope field correctly references the audience, consider also adding navigation-path keywords like "Settings, Workspaces, Accounting, Domains" to improve AI retrieval for users searching by navigation context.
|
|
||
| --- | ||
|
|
||
| ## Why the CER076 Export Error Happens in Certinia |
There was a problem hiding this comment.
Expensify Style Compliance concern: Line 18 says "Add the user's Expensify email address to the employee record." The word "user" should generally be "member" per Expensify terminology guidelines. However, since this refers to a Certinia record context rather than an Expensify role, this may be acceptable. Please confirm whether "member" is more appropriate here.
| ## Why the CER076 Export Error Happens in Certinia | |
| 4. Add the member's Expensify email address to the employee record. |
|
|
||
| The CER091 error typically indicates: | ||
|
|
||
| - A required field exists but is hidden under field-level security. |
There was a problem hiding this comment.
Readability violation: The sentence "Certinia requires required fields to be visible and accessible to the connected user profile during export" is redundant ("requires required"). Consider rephrasing:
| - A required field exists but is hidden under field-level security. | |
| Certinia needs all required fields to be visible and accessible to the connected user profile during export. |
PR Description InconsistencyThe PR title says "Add Certinia troubleshooting docs (Expensify Classic only)" but the PR body says:
This appears to be a copy-paste error from a previous PR. The body should reference Certinia and Expensify Classic to match the actual content. |
|
|
||
| # Certinia FAQ | ||
|
|
||
| ## Why is my report not automatically exporting to Certinia? |
There was a problem hiding this comment.
AI Readiness / Structure note: This file is structured differently from the individual error articles. The error articles use # FAQ as an H1 heading with ## subheadings for each question. This FAQ file uses ## directly for questions with ### for sub-steps. While the overall structure works as a standalone FAQ page, the ### sub-headings should still be promoted to ## per the heading hierarchy standard (see separate comments on those lines). Also consider whether this file should follow the same # FAQ convention used by the error articles for consistency across the Certinia Troubleshooting section.
HelpDot Documentation ReviewOverall AssessmentThis PR adds 17 new Markdown documentation files and 1 hub HTML file for Certinia integration error troubleshooting under Expensify Classic. The articles follow a consistent template structure (error description, cause, fix steps, FAQ) and cover a meaningful range of Certinia error codes. However, several critical issues -- primarily copy-paste errors in the Sync-Errors directory and near-identical content duplication across directories -- need to be addressed before merging. Scores Summary
Key FindingsCritical Issues
Moderate Issues
Minor Issues
Positive Aspects
Recommendations
Files Reviewed
Final Recommendation: Request ChangesThe copy-paste errors in Sync-Errors files and near-identical content duplication are significant issues that would degrade both user experience and AI retrieval accuracy. These must be addressed before merging. This review covers only the proposed changes in the PR diff, not pre-existing content. All file paths are relative to |
stephanieelliott
requested review from
CortneyOfstad
and removed request for
Gonals and
sonialiap
stephanieelliott
force-pushed
the
helpsite-certinia-new-and-classic
branch
from
0f91864 to
341abf2
Compare
- Expensify Classic: Certinia articles (Auth, Export, Sync errors, FAQ). - Expensify Classic: add Sync-Errors hub page for Certinia so Sync-Errors articles are reachable (Auth and Export hubs already on main). Part of Integration Errors Revamp (splitting PR #83106).
stephanieelliott
force-pushed
the
helpsite-certinia-new-and-classic
branch
from
341abf2 to
b0ecbc8
Compare
Reviewer Checklist
Screenshots/VideosAndroid: HybridAppAndroid: mWeb ChromeiOS: HybridAppiOS: mWeb SafariMacOS: Chrome / Safari |
|
🚀 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 🚀
|
4 participants
Master project issue https://github.com/Expensify/Expensify/issues/469226
Breaking main PR into smaller batches: #83106
Creates .MD files for NetSuite integration error messages (New Expensify)
Explanation of Change
see above
Fixed Issues
https://github.com/Expensify/Expensify/issues/469226
Tests
Offline tests
QA Steps
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectioncanBeMissingparam foruseOnyxtoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari