Importing GL entries from Excel in GL Entry Batch Import

You have two methods for importing lines from a Microsoft Excel spreadsheet into GL Transaction Entry to automatically create journal entries. Both methods required that you create and format the spreadsheet and save it on your local system or a shared network folder. The first method uses GL Entry Batch Import Report to import the file after you have transferred it to your cloud storage using SA File Transfer Administration. These instructions describe the process using GL Entry Batch Import Report.

The second method uses the Import From Excel option in GL Transaction Entry. For more information, see Importing GL entries from Excel in GL Transaction Entry.

  1. Verify that the spreadsheet you want to import is formatted correctly, otherwise, the import will fail.
  2. Save the spreadsheet in .csv, comma separated value, format. The file name cannot contain spaces or more than 14 characters.
  3. Save the .csv file to an accessible folder on your system.
  4. Select System Administrator > Administration > File Transfer.
  5. Select the file you saved in step 3, and select Product Import from the Target Type.
  6. Click Transfer File.
  7. Select General Ledger > Entry > GLE Reports > GL Entry Batch Import.
  8. Click New One Time.
  9. Specify the report, schedule, and printing information.
  10. Click Next.
  11. In Batch Name, specify the batch name you want to assign to the transactions created from this spreadsheet.

    You must specify a unique batch name. If you specify a batch name that is already in use in the system, the import fails and a message prints on the report after the report is processed: SAPB Batch Entry XXXX already exists

  12. In Input directory on Server, specify the location of the .csv file using this format: /reports/[Tenant ID]/.
    This is the same as the file location specified in the Print directory field in SA Company Setup-Required.
  13. In Input File Name, specify the name of the .csv file to import.

    If you specify an invalid path or file name, the import fails and a message prints on the report after the report is processed: File PATH.FILENAME not found.

  14. Click Next.
  15. To store the results of this report, specify a job name or number.
  16. Click Finish to process the report.
  17. Follow the instructions to update GL batch transactions.