[No QA] Add INT093 export error HelpDot article for Sage Intacct

[MelvinBot]

Explanation of Change

Adds a new HelpDot article documenting the INT093 Sage Intacct export error, which previously had no help-site page.

The article explains that the error (INT093 Export Error: Credit Card [X] is invalid. Please check the card’s expiration date in Sage Intacct and update it if it has expired.) is caused by an expired credit card in Sage Intacct, and walks Workspace Admins through updating the card's expiration date in Sage Intacct, syncing the Workspace in Expensify, and retrying the export.

The article was written to comply with docs/TEMPLATE.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/HELPSITE_NAMING_CONVENTIONS.md (single workflow, only #/## headings, task-based headings, YAML metadata with internalScope, exact UI labels, FAQ section), and follows the established format of the sibling articles in the Export-Errors folder.

New file: docs/articles/expensify-classic/connections/sage-intacct/Troubleshooting/Export-Errors/INT093-Export-Error.md

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/651620
PROPOSAL:

Tests

1. Build the docs site locally (or preview the rendered Markdown).
2. Navigate to the Sage Intacct > Troubleshooting > Export Errors section and open the INT093 Export Error in Sage Intacct Integration article.
3. Verify the title, body, steps, and FAQ render correctly with only #/## headings and no broken formatting.

• Verify that no errors appear in the JS console

Offline tests

N/A — static help-site Markdown content.

QA Steps

1. On the published help site, confirm the INT093 article is reachable under the Sage Intacct Export Errors section.
2. Confirm the content matches the approved copy.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

Screenshots/Videos

N/A — documentation-only change.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://8f75871d.helpdot.pages.dev ⚡️

Updated articles:

• articles/expensify-classic/connections/sage-intacct/Troubleshooting/Export-Errors/INT093-Export-Error

[melvin-bot]

Concierge reviewer checklist:

• I have verified the accuracy of the article
  • The article is within a hub that makes sense, and the navigation is correct
  • All processes, screenshots, and examples align with current product behavior.
  • All links within the doc have been verified for correct destination and functionality.
• I have verified the readability of the article
  • The article's language is clear, concise, and free of jargon.
  • The grammar, spelling, and punctuation are correct.
  • The article contains at least one image, or that an image is not necessary
• I have verified the formatting of the article
  • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
  • The article has proper text spacing and breaks for readability.
• I have verified the article has the appropriate tone and style
  • The article's tone is professional, friendly, and suitable for the target audience.
  • The article's tone, terminology, and voice are consistent throughout.
• I have verified the overall quality of the article
  • The article is not missing any information, nor does it contain redundant information.
  • The article fully addresses user needs.
• I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @Kel-Expensify

[melvin-bot]

@Kel-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]

[github-actions]

Step formatting: This step bundles four distinct UI actions (navigate to Settings > Workspaces, select your Workspace, click Accounting, click Sync Now) into a single numbered step. Per HELP_AUTHORING_GUIDELINES.md Section 5, steps must be sequential and clear. Split into discrete steps to match the established sibling Export-Errors articles, e.g.:

Suggested change

	If the credit card’s expiration date is current in Sage Intacct and the Workspace has synced, the export should complete successfully.
	3. In Expensify, go to **Settings > Workspaces**.
	4. Select your Workspace.
	5. Click **Accounting**.
	6. Click **Sync Now**.
	7. Retry exporting the report.

[github-actions]

Correction to my previous suggestion (to avoid duplicating the existing "Retry exporting the report." step on line 40). Split line 39 into discrete sequential steps only:

Suggested change

	If the credit card’s expiration date is current in Sage Intacct and the Workspace has synced, the export should complete successfully.
	3. In Expensify, go to **Settings > Workspaces**.
	4. Select your Workspace.
	5. Click **Accounting**.
	6. Click **Sync Now**.

The following "Retry exporting the report." line will then become step 7.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 656d4cdd12

ℹ️ 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".

[chatgpt-codex-connector]

Add the New Expensify INT093 article

Every other Sage Intacct export error article in expensify-classic has a matching file under docs/articles/new-expensify/connections/sage-intacct/Troubleshooting/Export-Errors (checked repo-wide; INT093-Export-Error.md is now the only missing counterpart), so adding this only to the Classic tree leaves users browsing the New Expensify Sage Intacct export-error hub with no INT093 help page. Please add the mirrored New Expensify article as well, using New Expensify navigation where it differs, so both help hubs expose the new error.

Useful? React with 👍 / 👎.

[github-actions]

HelpDot Documentation Review

Overall Assessment:
This PR adds one new HelpDot article documenting the INT093 Sage Intacct export error (INT093-Export-Error.md). It is a single-workflow troubleshooting article explaining the cause of the error and walking Workspace Admins through updating an expired credit card in Sage Intacct, syncing the Workspace, and retrying the export. The article is well-structured and closely follows the governance specs.

Scores Summary:

• Readability: 9/10 - Clear, concise, scannable prose with sequential, action-oriented steps and a focused FAQ.
• AI Readiness: 9/10 - Complete YAML metadata including internalScope, task and question based headings, a full How-to heading using the feature name, and strong search-aligned keywords. Single workflow only.
• Style Compliance: 8/10 - Exact UI labels are bolded (Accounting, Sync Now) and navigation paths are explicit; minor inconsistencies noted below.

Key Findings:

• Heading hierarchy is fully compliant: one title heading, one FAQ heading, and only level-two headings for all other sections. No deeper levels, no generic or topic-only headings.
• All non-FAQ section headings are task or question based (How to Fix..., Why the INT093 Export Error Happens...), and FAQ entries lead with question words. Compliant with Section 2.
• Metadata is complete and search-intent aligned: title, description, keywords, and a properly scoped internalScope with explicit exclusions.
• Single primary workflow with no setup, troubleshooting, or design mixing - good adherence to Sections 1 and 6.
• Minor: The error message string is rendered as a plain paragraph. Consider a blockquote or code block so it visually reads as a system error and improves scannability.
• Minor: The error text uses a curly apostrophe. Please verify it matches the exact product string, since straight ASCII punctuation is safer for retrieval and matching.
• Minor: The Expensify navigation path deviates slightly from the canonical Settings, Workspaces, Workspace Name, Section pattern - acceptable, but aligning improves consistency with sibling articles.
• No cross-links are present. Acceptable here since the workflow is self-contained, though a link to broader Sage Intacct export-error or sync troubleshooting content could reinforce context.

Recommendations:

• Format the error message as a blockquote or code block to set it apart from body text.
• Confirm the apostrophe and punctuation in the error string matches the exact UI and product text.
• Optionally align the Expensify navigation path with the canonical Settings, Workspaces, Workspace Name, Accounting phrasing.

Files Reviewed:

• INT093-Export-Error.md - New file. Compliant and ready, with minor polish suggestions above.

Note: Detailed line-by-line feedback has been provided as inline comments.