The first line in the General Ledger import rejection file includes the first entry from the import file, even though the entry imported successfully. This will create a duplicate entry when you import the reject file.

The Force Zero Proof was set to No (GL Settings, Processing Options) when you performed the import.

The import rejected at least one transaction for a legitimate reason. For example, the account doesn’t exist, a closed accounting period, invalid date or other invalid data, control account, etc.

The import process copies the first entry from the original import file as the first line in the reject file.

If the first entry rejects for a legitimate reason, the reject file will contain this entry twice.

Don't use No for the Force Zero Proof setting when importing

When using GL Tools, Import Transactions, set the Force Zero Proof setting (GL Settings, Processing Options) to something other than No.

If at least one entry legitimately rejects, the whole batch will reject.

Edit the reject file to correct the rejection errors, then import the corrected reject file.

Use No for the Force Zero Proof when importing

If you need to use No for the Force Zero Proof setting when importing, edit the reject file to remove the first line.

The first line will either be invalid (copied from the original file) or a duplicate line.

After removing that first line and correcting the rejection errors, then import the corrected reject file.