Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
In July 2017 we received cheque from our US based customer and deposited the same in our USD account further, we updated the customer ledger and applied the payment against outstanding invoices.
After five days bank informed that the cheque was dishonored. In July 2017 we received the new cheque and our receivable accountant entered the payment in the NAV and keep it as unapplied.
At the time of July 2017 Bank reconciliation we cleared the new cheque (cleared by the bank) and the old cheque was kept as outstanding deposit in the bank statement and posted the bank reconciliation.
Once we realized this mistake the bank reconciliation was already posted. We tried to unapply the dishonored cheque in our system but system wont allowed it, probably due to exchange gain/ loss entry as the account is in USD.
To rectify this mistake we made a sales invoice and credited our USD Bank GL account. As a result of this transaction, our customer account is now balanced.
During our August 2017 bank reconciliation we noted that this sales invoice entry (in which we used USD bank account) is not appearing in the bank statement, which is necessary to set off the outstanding dishonored cheque appearing at bank reconciliation level.
Please suggest the solution for this problem.
Business Applications communities