CStoreOffice® Support & Learning

Troubleshooting

Why was my General Ledger import file rejected by Sage Intacct?

Sage Intacct enforces atomic imports: if a single record fails validation, the entire file is rejected. The most common causes are:

  • Unbalanced Journal entry: Total Debits do not equal total Credits within a station's day.
  • Account number with dashes: Sage Intacct expects single-segment account numbers. Ensure accounts like Sales Tax (22250) do not contain store prefixes or dashes.
  • Invalid location or dimension ID: An identifier in the file does not exist in Sage Intacct. Check character casing, as identifiers are case-sensitive.
  • Duplicate reference key: The station date has already been imported. See the re-posting question below.

Open the companion error file (err_*.csv) delivered with your export files to view the exact error reason and setting path.

How do I re-post a sales day that has already been imported?

Because CStoreOffice® generates a deterministic unique key (REFERENCE_NO) for each station date, Sage Intacct will prevent you from accidentally importing the same day twice.

If you adjust store closing data in CStoreOffice and regenerate the export:

  • Log into Sage Intacct.
  • Navigate to General Ledger > Journal Entries.
  • Locate and reverse or delete the original journal entry.
  • Import the newly generated CSV file.

Why did an AP Bill fail with an error about vendor payment terms?

In Sage Intacct, purchase bills require a calculated DUE_DATE. CStoreOffice® calculates this date using the payment terms configured on the vendor's master record in Sage Intacct. If a vendor record in Sage Intacct has no default terms assigned, CStoreOffice® flags an error in the companion file. Assign default terms to the vendor in Sage Intacct and regenerate the export.

How are store-to-store inventory transfers handled?

Store transfers between two retail stations do not involve an outside vendor and cannot be posted as AP Bills. Currently, store transfer transactions are flagged in the companion error file. They should be recorded in Sage Intacct via a manual general ledger entry between inter-store clearing accounts until your project team confirms automated transfer mapping rules.

Why do fuel purchase lines contain a Department ID?

In older accounting configurations, fuel purchase invoices were posted without a department. The Sage Intacct export automatically populates the DEPT_ID on fuel purchase lines using the Department ID assigned to that fuel grade. This aligns fuel revenue and fuel cost within the same departmental dimension on your financial statements.