Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MelvinBot wants to merge 1 commit into
base: main
Choose a base branch
from
+55 −0
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 55 additions & 0 deletions ...c/connections/sage-intacct/Troubleshooting/Export-Errors/INT093-Export-Error.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
---
title: INT093 Export Error in Sage Intacct Integration

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 24, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

description: Learn what the INT093 export error means and how to update an expired credit card in Sage Intacct before exporting from Expensify.
keywords: INT093, Sage Intacct credit card invalid, credit card expired Sage Intacct, expiration date export error, Cash Management credit card, Sync Now Sage Intacct, Expensify Sage Intacct integration, Workspace Admin
internalScope: Audience is Workspace Admins using the Sage Intacct integration. Covers resolving the INT093 export error caused by an expired credit card in Sage Intacct. Does not cover other Sage Intacct export, sync, or connection errors.
---

# INT093 Export Error in Sage Intacct Integration

If you see 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.

This means the credit card used on the export has expired in Sage Intacct.

Sage Intacct validates the credit card during export, and an expired expiration date causes the export to fail.

---

## Why the INT093 Export Error Happens in Sage Intacct

The INT093 error indicates that the credit card referenced in the export is no longer valid in Sage Intacct because its expiration date has passed.

Sage Intacct checks the card’s default expiration date during export. If that date is in the past, the card is treated as invalid and the export fails.

This is a credit card expiration issue in Sage Intacct, not a category, tag, or employee record error.

---

## How to Fix the INT093 Export Error

Follow the steps below to update the expired credit card and retry the export.

1. In Sage Intacct, go to **Applications > Cash Management > Credit Card**.
2. Confirm the default expiration date is not in the past. If it is in the past, adjust the fields to a date well into the future and save your changes.
3. In Expensify, go to **Settings > Workspaces**, select your Workspace, click **Accounting**, and click **Sync Now**.
4. Retry exporting the report.

If the credit card’s expiration date is current in Sage Intacct and the Workspace has synced, the export should complete successfully.

@github-actions github-actions Bot Jun 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 github-actions Bot Jun 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


---

# FAQ

## Does the INT093 Error Mean the Integration Is Disconnected?

No. The error indicates an expired credit card in Sage Intacct, not a connection issue.

## Why Do I Need to Run Sync Now After Updating the Card?

Selecting **Sync Now** refreshes the card details from Sage Intacct so the updated expiration date is reflected before you retry the export.

## What Should I Enter for the Expiration Date?

Set the default expiration date to a date well into the future so the card remains valid for current and upcoming exports.
Loading