company & Administration

Avoid errors in General Ledger journal entry imports

We've updated the import service to determine how rows are grouped into General Ledger journal entry records. You may need to update your import file formats before your next import.

Key benefits

• More accurate journal entry imports

• Consistent record grouping across import files

• Reduced risk of import processing errors

How it works

The import service now uses header-level fields to identify the start of a new journal entry record.

For General Ledger journal entry imports, the header-level fields are:

• Journal

• Date

• Description

When a row contains a value in any of these fields, the import service treats that row as the start of a new journal entry record. Rows with all header-level fields left blank are treated as line items for the most recent record.

Action required

If your existing import files repeat Journal, Date, or Description values on every row, update those files before your next import.

For each journal entry:

• Enter Journal, Date, and Description only on the first row.

• Leave those fields blank on line item rows.

If line item rows contain values in header-level fields, the import service treats each row as a separate journal entry. This can cause imports to fail when individual rows do not contain balanced debit and credit amounts, resulting in a Transaction out of balance error.

Permissions and other requirements

Subscription	Company
Regional availability	All regions
User type	Business
Permissions	Company Setup Checklist: Run You also need permission to access the specific applications of Intacct where you want to import data.