[No QA] Add New Expensify Sage Intacct INT093 help article

[inimaga]

Explanation of Change

Adds the missing New Expensify HelpDot article for the Sage Intacct INT093 Export Error

Fixed Issues

Related to https://github.com/Expensify/Integration-Server/pull/8795

Follow-up to the missing New-Expensify counterpart to the PR #94355 and the article at https://help.expensify.com/articles/expensify-classic/connections/sage-intacct/Troubleshooting/Export-Errors/INT093-Export-Error

PROPOSAL: N/A

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• 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
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[OSBotify]

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

Updated articles:

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

[github-actions]

Navigation standard: Per HELPSITE_NAMING_CONVENTIONS.md (Navigation Instruction Standards), the Expensify Settings > Workspaces path differs between web and mobile. Provide platform-specific navigation, e.g. note the mobile hamburger menu ("On mobile, tap the hamburger menu in the top-left corner, then select Settings"), rather than a single merged path.

[github-actions]

Heading capitalization: Headings should use Sentence case (only the first word capitalized), not Title Case. Use ## How to fix the INT093 export error. Same applies to the other Title Case headings in this article. See HELPSITE_NAMING_CONVENTIONS.md (Sentence case) and TEMPLATE.md.

[github-actions]

Heading capitalization: FAQ questions are exempt from the task-based rule but must still use Sentence case. Use ## Does the INT093 error mean the integration is disconnected? (only the first word capitalized). Applies to the other FAQ questions on lines 49 and 53 as well.

[github-actions]

Readability: The literal error message is presented as plain body text and is easy to confuse with the surrounding prose. Consider formatting it as a blockquote or code block so the error string is visually distinct and scannable (HELP_AUTHORING_GUIDELINES.md, scannability/error-message emphasis).

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds one new article, INT093-Export-Error.md, documenting how to resolve the Sage Intacct INT093 export error caused by an expired credit card. It is a focused, single-workflow troubleshooting article with complete YAML metadata and a well-formed FAQ. Overall quality is strong; the main deviations are heading capitalization and minor formatting of the error message.

Scores Summary

• Readability: 8/10 - Clear, concise, well-sequenced steps and a logical flow from cause to fix to FAQ. Slightly weakened by the raw error message rendered as plain paragraph text rather than a code block or blockquote.
• AI Readiness: 9/10 - Complete metadata (title, description, keywords, internalScope), single workflow, task-based section headings including a How to Fix heading, and only H1 and H2 levels used. Retrieval-friendly keywords and scope.
• Style Compliance: 7/10 - Correct bolding of UI elements (Accounting, Sync Now) and exact-terminology navigation. Main issue is Title Case headings where governance and the PR checklist call for Sentence case.

Key Findings

• Metadata is exemplary: internalScope clearly states audience (Workspace Admins), covered workflow, and explicit exclusions per HELP_AUTHORING_GUIDELINES.md Section 3.
• Heading structure is compliant: one H1 title plus FAQ, task-based H2 sections and question-form FAQ entries. No generic or noun-only headings.
• Headings use Title Case throughout; governance examples and the naming conventions favor Sentence case (only the first word capitalized, aside from proper nouns like Sage Intacct and INT093).
• The error string is presented as an unstyled paragraph. Wrapping it in a code block or blockquote would improve scannability and match how error messages are typically distinguished.
• Single-workflow scope is respected; no scope creep into other Sage Intacct errors.

Recommendations

• Convert H2 and FAQ headings to Sentence case, for example How to fix the INT093 export error and Why the INT093 export error happens in Sage Intacct.
• Format the quoted error message as a code block or blockquote so it stands out from body text.
• Optional: align the Expensify navigation with the template pattern (Settings then Workspaces then Workspace Name then Accounting) for consistency with other articles.

Files Reviewed

• docs/articles/new-expensify/connections/sage-intacct/Troubleshooting/Export-Errors/INT093-Export-Error.md - New article; compliant structure and metadata; minor heading-casing and error-message formatting fixes recommended.

Note: This review is based solely on the changes proposed in the PR diff.

[OSBotify]

🚀 Deployed to staging by https://github.com/CortneyOfstad in version: 9.4.29-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[OSBotify]

🚀 Deployed to staging by https://github.com/CortneyOfstad in version: 9.4.31-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[OSBotify]

🚀 Deployed to production by https://github.com/grgia in version: 9.4.31-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android