An RMA transaction communicates authorization for the return of merchandise and provides notification about the return process. Typically, a supplier or distribution center sends this to a customer or retailer in response to a return request, though it may also originate from a customer organization to acknowledge or formalize return procedures. The BGN (Beginning Segment) establishes the transaction purpose and RMA number, the RDR (Return Disposition Reason) explains why items are being returned or what action is required, and the BLI (Baseline Item Data) loop structures line-item details about each product being returned, allowing the transaction to convey authorization status, quantities, and disposition instructions for individual SKUs. Additional segments such as DTM (Date/Time Reference), N1 (Name), and carrier-related segments support tracking dates, identifying parties involved, and specifying return logistics.

Consider a scenario where TechCorp Wholesale receives a shipment of computer monitors from Global Electronics Manufacturing and discovers several units have display defects. TechCorp initiates a return request, and Global Electronics responds by sending an X12 180 RMA transaction that authorizes the return of 15 defective units. The transaction includes the RMA number in the BGN segment, specifies the return disposition reason (product defect), and lists each monitor in the BLI loop with its serial number, original purchase order reference, and instructions that the unit should be inspected and either refurbished or scrapped. The transaction also identifies TechCorp’s receiving location via the N1 loop and specifies the preferred carrier and shipping instructions through TD5 and PKG segments, enabling TechCorp to prepare the return shipment with confidence that Global Electronics has formally approved the return.