Return-to-Supplier Authorisation

A buyer may need to return goods that are defective, excess or wrongly delivered, and the supplier often asks for an authorisation before accepting the shipment so that the reference ties the physical parcel to a reviewed case. A fictional retailer with ten damaged blenders asks its supplier for a return reference identifying the item, quantity and reason before shipping them back.

Confirm whether the return is allowed under contract, warranty and applicable law, because not every unwanted item can be returned, defective goods may carry distinct rights, and a supplier's portal rule does not override mandatory law. The supplier may call its reference an RMA, return materials authorisation or another label, while the buyer's system can have a separate internal return number, so keep both identifiers.

Oracle's NetSuite guide describes obtaining the vendor's RMA, recording item, quantity and value, approving the internal return, shipping goods and then logging a vendor credit or refund, and it explicitly distinguishes the vendor reference from an internal return number. Oracle's supplier-return workflow similarly records the RMA number and returned quantity before arranging shipping documents, but these are software examples and parties must follow their own contract and process.

Record exact product identifiers, serial or lot numbers and condition, and photograph visible damage when useful and permitted, since a mismatch can delay inspection or credit. A quality hold may precede the return, so a fictional food importer keeps a suspect lot segregated and follows applicable safety instructions before any return transport, because an authorisation does not mean every safety question is resolved.

Check packaging and carrier requirements as well, since hazardous, fragile or temperature-sensitive goods may need special handling and a generic return label may be unsafe or non-compliant, as when a fictional battery supplier specifies an approved carrier and packing method. Clarify who pays freight and bears transit risk, record the decision before shipping expensive goods, and verify any expiry date or receiving location, because a package arriving at the wrong depot can be lost in the supplier's intake.

A fictional supplier that gives a return window of 14 days expects the buyer to schedule pickup and keep proof of shipment. Ship only the authorised units, include the requested paperwork and retain tracking, remembering that a shipping confirmation proves dispatch, not the supplier's receipt or acceptance.

Discrepancies need reconciliation, as when a fictional buyer ships ten units and the supplier reports nine, so both sides inspect packing photos and carrier records before final credit. Credit, refund, repair and replacement are different outcomes, so state which the supplier agreed to and monitor completion, because a return reference is only the start of the process.

Update inventory and accounts at the right stages under the business's accounting policy, since the authorisation itself is not proof that goods left or that credit was granted, which is why a fictional accounts payable clerk who sees an authorisation but no credit follows up rather than reducing the bill. Some goods cannot safely be returned and may need local disposal with supplier approval, so document the agreed remedy and any certificate required and do not ship hazardous goods merely because an RMA number exists.

Keep customer returns separate from supplier returns, since a customer's authorisation to send an item to the retailer is not the supplier's permission to accept it back upstream. Track open cases by age, because a delivered return without credit can remain unresolved for weeks, and ownership and follow-up protect cash and inventory accuracy.