Considerations before Moving Transactions:

• You can move batches or transactions you entered in General Ledger if they aren’t needed
• Before moving entries that originated in another application, make the correcting entries in the application of origin
• Removing transactions from interfacing applications may make batch-to-batch reconciliation between General Ledger and interfacing applications difficult
• Moving entries that don’t net to zero by Account and Accounting Date may cause an out of balance situation
• If you don’t want any of the entries in the new file, see these steps to use File Tools to rename the new.glt

If you can't post the entries and a journal entry has been made, you can move the batch. This could be due to and out of balance batch or the dates being outside GL posting dates. However, this may result in an out of balance between General Ledger and the interfacing application. Contact your Sage Consultant or Sage Expert Services for assistance with reconciliation issues

 

Identify the entries to move:

1. In General Ledger, select Inquiry, Entries.
2. Select the New GL transaction file and click OK.
   1. Click Select, select Add column after this column, and then click OK.
   2. From the GL transaction record, select other columns as needed and click OK.
      Note: You can use records such as Run Number, Sequence Number to identify individual transactions within a batch. Repeat these steps to show additional information on the inquiry.
   3. Make note of the Batch, Run and Application of Origin, and any additional information to identify the transaction.
   4. Click Close.
3. Click Close.

Moving the Entries:

 

1. In General Ledger, from the Tools menu, select Move Transactions, New to New.
2. In the Destination File Selection window, select an archive folder in the Look in box. This is where you’ll move the unwanted transactions.
3. In the File name box, accept the name NEW and click Open.
   • Note: If this is the first time you’re moving transactions into this folder, the message File not found. Okay to create? appears. Click Yes.
4. In the Print Selection window, enter a Cutoff date for the accounting date of the latest transaction to move.
5. Select Conditions.
   NOTE: If you don’t select conditions, it will move all transactions in the New file through the cutoff date.
   1. In the Field column, select Batch.
   2. In the Operator column, select Equal to.
   3. In the Value column, type the batch number.
   4. Click OK.
   5. Click Add.
   6. In the Field column, select Application.
   7. In the Operator column, select Equal to.
   8. In the Value column, type the application of origin.
   9. Click OK.
   10. Repeat the steps to condition by additional records needed to identify the transactions then click OK.
6. Click Start.
7. Review the journal to verify that the correct batch or entries moved without errors.
8. To view the entries in the archive folder, see steps to access moved entries.

 

Tip:

If moving the batch removes all items in the new file, the program deletes the new.glt file. Follow these steps to recreate the new file.

1. Go to Tasks, Record Entries.
2. A pop-up message will appear, The new.glt file does not exist, do you want to create it?.
3. Select Yes.
4. Click Cancel to close out of the entry window.