Customer Entry Batch Update Report overview

Customer > Entry > ARE Reports > Customer Entry Batch Update

Function acronym: AREBU

Use this page to update Customer Transaction Entry with the transactions that are associated with the specified batch name.

After the Customer Entry Batch Update Report is complete, the Last Update Date and Operator Initials fields in the batch header file are updated. If this is a one-time batch, the transactions are deleted. If it is a recurring batch, the transactions remain.

A new journal that details the batch transactions is created. SA Journal Setup is updated with a new journal record. You can use the Customer Entry Journal Print Report to reprint the journal.

Any batch that has been maintained during the day should be updated before the end of the day. This assures that General Ledger information is always current at the start of a new day. If you do not update batches at the end of the day, update them on a regular basis.

Accounts Receivable and General Ledger are updated by the Customer Entry Batch Update Report the same way as Customer Transaction Entry is updated.

If you attempt to update a recurring batch that has been posted within the last 30 days, the This Batch Has Been Posted Within The Last 30 Days, Do You Wish To Continue message is displayed.

If a recurring batch is run twice within the last 30 days as a stored report, the update occurs. The This Batch Has Been Posted Within The Last 30 Days is included on the report.

Messages can be displayed at the bottom of the screen or on the Customer Entry Batch Update Report.