Sales Credit Memos where inventory is not returned
-
Sales Credit Memos where inventory is not returned
Posted by ryan.porter@milgro.com on June 27, 2018 at 4:45 pm-
We are currently in the middle of training on our new 2017 NAV system.Ā An issue came up in our training today for which I searched the forum, but was unable to find an answer.Ā Some posts were close, but not quite our situation.Ā Posting to see how other might handle this situation.
We sell live plants which are obviously perishable.Ā At times, due to quality issues or transportation issues, the product arrives at the customer, but is unacceptable.Ā In most cases, it does not make sense to return the product as the plants cannot survive both the return trip nor being reshipped. Ā
We are trying to find the best way to enter credit to the customer and account for the loss in our system, while at the same time, tie the loss to the sale?Ā We have tried tying the credit to the line item on the sales order, but have not been able to give the credit without also receiving the items back into inventory.Ā One thought was to receive the inventory back in the system (possibly to a dummy warehouse) and then scrap it, but that seemed a little messy to me. Ā
Question:Ā Has anyone had experience issuing credits on sales for which the product is NOT returned?Ā If so, I’m interested in how you handle it?Ā My experience with NAV is limited as we are new to the NAV world and would like to draw on the experience of this forum.
Thanks for any help you might be able to provide.
——————————
Ryan Porter [Designation]
Controller
Milgro Nursery
—————————— -
The messy process you noted is generally the best as far as I know.Ā While you could just credit the customer by posting a credit memo hitting a sales contra account for the amount, this would only solve the GL and customer balance issue.Ā However this would not address the tracking of inventory or recording accurate sales quantities.Ā You would need to show the credit as a reduction in sales quantity so that you would accurately report on sales quantity.Ā And if you subsequently reshipped product as replacement, you would show double the sales quantity unless you also recorded the return.
One modification that I have seen is to include a checkbox on the sales credit memo line indicating whether the product was being returned.Ā If the box was checked, then the return was processed but then a negative adjustment was immediately posted to remove the product from inventory.Ā The adjustment used the same document number so it kept the whole transaction together.Ā This approach is really just automating the process you noted previously.
——————————
Dave Wiser
Controller
Beckwith & Kuffel
Seattle WA
——————————
——————————————- -
Paul Simpson
MemberJune 28, 2018 at 6:22 AM
I’d agree with Dave Wiser as that being the most sensible route.I would suggest being sure to use NAV’s Return Reason Codes as you can get that to direct the returns automatically to a separate Location (called “dummy warehouse” or “customer scrap for refund”) so the user doesn’t have to remember to do so to ensure they’re not inadvertently returned back to your main shipping Location(s). You may find those Return Reason Codes could become very useful for reporting down the line if you don’t already have systems in place for that.
——————————
Paul Simpson
Business Analyst
Vado
Cheddar
——————————
——————————————- -
We create the Sales Credit Memo with a Return Reason Code (Damage).Ā The Return Reason Code is set to a Default Location (Damage).
The inventory that goes into the Default Location (Damage) is moved out of that location through the Phys Inventory Journal.Ā The Cost of the Damaged product is expensed as Damage (set up through Gen Business Posting Group used on the Physical Inventory Journal entries).Ā
Sales Credit Memo:
Dr. SalesĀ Ā Cr. A/R
Dr. InventoryĀ Ā Cr.Ā COGPhysical Inventory Journal Posting:
Dr. DamageĀ Cr.Ā InventoryMost of our functionality is standard NAV code.Ā We have some custom code regarding the Phys Inventory Journal process to capture dimensions the way we need them.
Hopefully this will give you thought for another way to manage your damaged product
——————————
Kari Strandberg
Accounting Manager
Bernatello’s Pizza, Inc
Maple Lake MN
——————————
——————————————- -
Jim Brewer
MemberJune 28, 2018 at 11:24 AM
Maybe I’m over simplifying this, but since the product is already out of the system, why not use a Sales Journal entry to generate a Credit Memo line and post it? It wouldn’t create a Posted Sales Credit Memo with headers and detail lines, but as I understand it, you’re just trying to credit the Customer for dollars. I hope this helps!——————————
Jim Brewer
Silverware
Phoenix AZ
——————————
——————————————- -
It might not be the best way, but we also come across similar situations.Ā We created a resource that we use in credit memos for inventory that we cannot/ will not get back in and want to be able to create a document to effect sales and AR.
——————————
Zack Monroe
South Atlantic, LLC
Wilmington NC
——————————
——————————————- -
Major Williams
MemberJuly 3, 2018 at 9:19 AM
we perform this the messy way. return to a virtual warehouse or bin and it is reviewed and cleared out each month.If you are not concerned with sending the customer CM document, you can post a sales journal instead.Ā This would provide a credit towards the invoice. There is not a document associated with it.
——————————
Major Williams
Farmers Investment Co
Sahuarita AZ
——————————
——————————————- -
Just wanted to say thanks for the thoughts on this subject.Ā Being new to NAV, I felt maybe we were missing something.Ā After reading the comments, it appears we are headed in the right direction.Ā We are going to try the different methods mentioned and see which one best meets our needs. Ā
Really appreciate this Forum!
——————————
Ryan Porter [Designation]
Controller
Milgro Nursery
——————————
——————————————-
ryan.porter@milgro.com replied 7 years, 3 months ago 1 Member · 0 Replies -
-
0 Replies
Sorry, there were no replies found.
The discussion ‘Sales Credit Memos where inventory is not returned’ is closed to new replies.