Use three separate checkpoints: authorize what the customer is expected to return, record what actually arrives and decide how the accepted goods should be handled. Versa Cloud ERP supports those checkpoints with the RMA and New RMA Receipt workflows. Creating the RMA does not make the goods available, and the receiving team should not accept an item into stock merely because a return was approved.
This separation protects two records at once. Customer service retains the agreed reason and expected quantity, while the warehouse records the actual product, quantity and condition it received.
Build the expected return from the sale when possible
An RMA can be created from a sales order, carrying the customer, product, quantity, price and a relationship to the original sales-order line. The user selects a return reason and the quantity eligible to return. This gives receiving a defined expectation rather than an unstructured package.
The RMA line can also record the receiving facility and relevant serial context. If the original shipment was not brought into Versa Cloud ERP, the RMA supports an “Enter without prior sales history” path, but the team must still identify the product, quantity, facility and return reason. For serial-controlled goods, use one RMA line per expected serial number where that process applies.
Record arrival separately from authorization
When the package arrives, Receiving -> New RMA Receipt shows open RMA lines. The receiving record captures quantities accepted and rejected, with a rejection reason where applicable. Where Warehouse Management is enabled, the receiver can select or record the Bin Location used for accepted goods.
The receiver should compare the parcel with the RMA before posting:
| Evidence | Question to resolve |
|---|---|
| Product and quantity | Is this what the RMA authorized? |
| Lot or serial identifier | Is this the same controlled item the customer was expected to return? |
| Physical condition | Is it acceptable for the intended disposition, or should it remain rejected or segregated? |
| Receiving facility and Bin Location | Where is the item actually being held? |
| Customer agreement | Is inspection required before a credit or replacement can proceed? |
A customer is authorized to send back two units. One is unopened and one has visible damage. Receiving can record the accepted and rejected quantities separately instead of putting both into one undifferentiated available balance. Customer service and finance can then base the remedy on the recorded outcome.
Keep uncertain goods out of ordinary fulfillment
Posting an accepted RMA receipt can return inventoried quantity through the receipt process. That makes the accepted-versus-rejected decision material. If the item's usability is still uncertain, the warehouse needs a defined hold or segregation practice before treating it as ordinary saleable stock.
Versa Cloud ERP records the receipt, location and inventory result. The responsible person still decides whether company policy permits resale, refurbishment, write-off or another outcome. A Bin Location can identify where the item is held, but a location name alone is not a condition assessment.
Give customer service and finance a verified handoff
After receiving, customer service should compare the recorded quantity and condition with the promised remedy. Finance should use the related RMA receipt and invoice records when creating or reviewing a credit. If the inspection result changes the agreement, update the customer before issuing both a financial and physical remedy.
For a buyer, the key fit question is whether the return process preserves the difference between expected, received, accepted and rejected quantities. Versa Cloud ERP supplies those linked records so warehouse evidence can drive the next customer and financial decision without making an authorization look like completed receipt.
Ask the Versa Cloud ERP AI Advisor about receiving and assessing customer returns
