New April Hotfix and more changes for VAT
Check out the latest updates to Microsoft Dynamics GP 2016 and 2018.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Ask and you shall receive..... You'll be overjoyed to know that new functionality you've been asking for to automatically deposit cash receipts to a lump sum deposit in Bank Reconciliation is finally here!! We love your product suggestions and encourage you to keep them coming!
There were options in previous versions to have cash receipts automatically deposit to Bank Reconciliation, but they only deposited the cash receipts to individual deposits in Bank Rec. With this new functionality, you can have all the cash receipts in the same batch automatically deposit as a lump-sum or single deposit in to Bank Rec. How cool is that?
To use this new functionality in Microsoft Dynamics GP 2016, simply go to the Company Setup options and mark the option to 'Automatically post cash receipt deposits' and the system will take it from there. Now all cash receipts in the same batch will post to Bank Rec as a single deposit. (If you use Master Posting, a separate deposit will be created for each separate batch posted. However, if you are using Transaction Level Posting, then a separate deposit will be created for each posted transaction, as it does today.) The lump-sum deposit will have drill-back capability to view all the cash receipts that make up the deposit.
The receipts in a batch could be posted from the following windows:
The Deposit Number for the single deposit record created will be made up of the Batch Name, and the MMDD of the user date (no year), followed by an incremented number. For example, if you post a batch named 'BATCH1' on 4/12/2017, and then post another batch also named 'BATCH1' later in the day on 4/12/2017, you will see two lump-sum deposits created as follows:
Note: If you have the Project Accounting module installed, the PA security will take over the window, and cash receipt batches will continue to post as individual deposits to Bank Rec. This issue will be addressed in a future release.
Click HERE for more detailed documentation for Application features.Click HERE for Application feature VIDEO!!
Be sure to check back to the Microsoft Dynamics GP 2016 New Feature Blog Series Schedule page to review posted blog articles and upcoming blog posts to help you gear up for What's New in Microsoft Dynamics GP 2016 with great content, documentation, and videos.
Thank you!Cheryl Waswick | SR Support Engineer | Microsoft Dynamics GP
I added you suggestion below, Heather, to the Microsoft ideas site...as it agree that this would be a great enhancement to the Auto Deposit functionality.
LOVE that now we do have the option - it is definitely a big issue for some of my clients. Even though it has just been released, I have a suggestion for a better way of doing it.
A lot of sites don't allow transaction level posting, and even those that allow it, it means a double posting - at the series and then at financial. It is also essentially a different process for each method for end users.
What would be a better way I believe would have been to have a check box at the batch level to indicate post as a batch or post individual transactions.
This means sites could still group all their receipting off the bank statement (for example) into a single batch - and check the box for separate deposits (a bit like separate remittances in an accounts payable payment batch), while having a second batch that has all their physical cash and cheques that they could leave unmarked to have a batch deposit.
It would mean essentially an end user uses the same process for both - and simply has a check box to differentiate between the two.
But even without that enhancement - this feature did give me a "Yeehah" moment :-)
Olympic Software (NZ) Ltd
Business Applications communities