Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
In my earl posts about posting groups, I have showed purchase and sales processes. But both of these processes have its opposite processes.
If our customer wants to return items to us, we can use the Sales Return Order for this. When we finish posting, we will get Return Receipt and Sales Credit Memo as result.
On other side, if we want to return items to our vendor, we can use the Purchase Return Order for this. As result of posting, we will get Return Shipment and Purchase Credit Memo.
I will not prepare flow chart about using posting groups, because we can use the same schemas as we already have in Item Sale Posting and Item Purchase Posting posts.
First, I will describe sales return process. When we post Return Receipt, we will get only these G/L Entries:
But, when we finish posting and post Sales Credit Memo, we will get more G/L Entries:
The similar situation is in purchase return process. When we post Return Shipment, we will get again only these G/L Entries:
But, when we post Purchase Credit Memo for this item, we will get more G/L Entries:
And, on the end when we run Adjust Cost – Item Entries batch job, we will get the following G/L Entries (variance between expected and actual cost):
Business Applications communities