If you have a handful of journal entries to be created in regular basis, whether for numerous accruals and reversals, allocation, or reclassification entries, setting up Recurring Transaction in Dynamics GP will be helpful and speed up your month end process.
Step 1 - Setup Recurring Batch
Path: Transaction > Financial > Batches
i. After entering the "Batch ID" and "Comment", setting up the "Frequency" is the most important part for recurring transaction. "Single Use" is the one we use all the time for single posting, once posted, the batch will remove from Batch ID. But if you set the Frequency to "Monthly", which means the batch automatically becomes a recurring batch, the batch will be there forever for multiple posting.
ii. There is another useful option here, "Clear Recurring Amounts", which will clear the amounts in journal entries after the posting. You can then later enter the amount in the journal entries after the posting. Assuming the amount value will be change every time but same account entry need to create monthly, you should select this option.
Step 2 - Setup the "Template"
Path: Transaction > Financial > General
i. Enter the Transaction Date, Reference, Account Codes, and amounts.
ii. Do make sure the Batch ID is pointing to the recurring batch that created just now in Step 1.
iii. Proceed to post the batch like normal process.
(Make a good habit of printing out Edit List Report before posting)
iv. If you check to the Lookup List in Batch ID, the recurring batch that you setup earlier will be there still after the posting. Note that the last date posted and times posted have been populated.
v. Take note that after the recurring batch is posted:-
- The transaction date has been changed based on the batch frequency
- Journal Entry will still be same
- Account and Amount will remain the same (unless you marked the "Clear Recurring Amounts")
vi. You may change the Accounts, Amounts, and anything in the journal entry screen after the first posting. Just don't forget to save the latest changes to the recurring batch.
***Take note that the batch will remain out there to post, it will not disappear unless user has deletes it.
Thank you "DynamicsGPInsights" for the great insights!
Step 1 - Setup Recurring Batch
Path: Transaction > Financial > Batches
i. After entering the "Batch ID" and "Comment", setting up the "Frequency" is the most important part for recurring transaction. "Single Use" is the one we use all the time for single posting, once posted, the batch will remove from Batch ID. But if you set the Frequency to "Monthly", which means the batch automatically becomes a recurring batch, the batch will be there forever for multiple posting.
ii. There is another useful option here, "Clear Recurring Amounts", which will clear the amounts in journal entries after the posting. You can then later enter the amount in the journal entries after the posting. Assuming the amount value will be change every time but same account entry need to create monthly, you should select this option.
Step 2 - Setup the "Template"
Path: Transaction > Financial > General
i. Enter the Transaction Date, Reference, Account Codes, and amounts.
ii. Do make sure the Batch ID is pointing to the recurring batch that created just now in Step 1.
iii. Proceed to post the batch like normal process.
(Make a good habit of printing out Edit List Report before posting)
iv. If you check to the Lookup List in Batch ID, the recurring batch that you setup earlier will be there still after the posting. Note that the last date posted and times posted have been populated.
v. Take note that after the recurring batch is posted:-
- The transaction date has been changed based on the batch frequency
- Journal Entry will still be same
- Account and Amount will remain the same (unless you marked the "Clear Recurring Amounts")
vi. You may change the Accounts, Amounts, and anything in the journal entry screen after the first posting. Just don't forget to save the latest changes to the recurring batch.
***Take note that the batch will remain out there to post, it will not disappear unless user has deletes it.
Thank you "DynamicsGPInsights" for the great insights!
This is a really authentic and informative blog. Share more posts like this.
ReplyDeleteOpenStack In Cloud Computing
Features Of OpenStack