RMA vs VRMA
# ask-stanley-ai
a
RMA vs VRMA
c
AI generated answer (using internal Slack threads):
In NetSuite, both RMA (Return Merchandise Authorization) and VRMA (Vendor Return Merchandise Authorization) are used to manage the return of items, but they are used in different contexts. RMA is typically used when a customer returns goods to your business. The RMA process in NetSuite allows you to track the return of the item, issue a refund or credit to the customer, and return the item to inventory if necessary. On the other hand, VRMA is used when your business needs to return goods to a vendor. This could be due to a variety of reasons such as receiving faulty items. The VRMA process allows you to track the return of the item, receive a credit from the vendor, and remove the item from your inventory. When a vendor repairs the returned items and sends them back, you can't receive these items back to inventory through the VRMA. The VRMA is designed to work when the vendor sends a credit and not repair the items. In this case, you need to create a new Purchase Order (PO) to receive the repaired item. Then apply the credit from the VRMA to the Bill from the new PO so your costing doesn’t go out of whack. Alternatively, you could do an inventory adjustment if finance is okay with it. However, inventory adjustment can play a bit of havoc with your average cost. Another option is to use Inventory Statuses. The damaged item is moved into "bad" or unsaleable stock, this meaning it cannot be committed to orders. Then when the replacement item comes in, move it back to "good" saleable stock. The inventory status change transaction itself does not have a PDF form attached, but with script you could generate a pseudo "Damaged Inventory Replacement" PDF. The inventory remains in your asset GL. If the supplier then decides to just credit you, you can easily generate a VRA from the "bad" inventory status. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.801122606
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.786407292
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.78110218
Please provide your feedback on this answer.