General Ledger > Entering and Posting Transactions > About Importing Batches

About Importing Batches

You can use the Options > Import command on the G/L Journal Entry screen to transfer to General Ledger batches of transactions that were:

Exported by Sage 300 ledgers at other physical locations.
Created by non-Sage 300 programs.

After importing the transactions, you can edit, print and post them in Sage 300 General Ledger.

Note: If the batch file does not contain valid data, it is not imported.

Tip: To see how the data records should be organized, we recommend that you export a record from Sage 300 in the format that you want to import. (For more information on creating batches for importing, see the "Import Data into Sage 300" topic in the help.)

Importing Batches from Another Location

Generally, you use the Import feature to transfer Sage 300 batches that are created in another location for posting to your General Ledger. (If your subledgers are in the same company as your General Ledger, they create batches directly in General Ledger.)

Import batches can be created off-site in one of two ways:

By using the G/L Journal Entry screen in the remote site to create the batch. Then, you use the Options > Export command on the G/L Journal Entry screen to create a batch that can be imported by your General Ledger.
By creating a General Ledger batch in a database that does not have General Ledger activated. For example, if you have a branch office database that contains Accounts Receivable or Accounts Payable ledgers—but no General ledger—Sage 300 will create a G/L import batch file when you create a batch for posting to General Ledger.

Import batches created automatically by Sage 300 are in CSV text format (comma separated values).

Importing Batches from Non-Sage 300 Programs

The only way to transfer batches created by non-Sage 300 programs into General Ledger is to import them.

As with transactions generated by Sage 300 subledgers, the source code attached to the detail indicates the transactions’ source ledger and type. You must define your source codes in the source program, and then add them to General Ledger before you export transactions.