EDI 180 Return Merchandise Authorization and Notification Workflow

A store returns team sends 120 defective kettles back to the vendor's returns centre with a handwritten RMA number on the pallet label. The vendor had authorized only 96 units for return and told the retailer to keep the rest against an allowance, but that answer sat in an email thread. The dock receives 120, the credit team issues credit for 96, the retailer deducts 120 from the next payment, and three departments spend a month arguing over 24 kettles nobody wanted.

The X12 180 exists to stop that argument. It carries the return request, the vendor's line-by-line answer and the notice that goods were shipped back, all with coded reasons, dispositions and reference numbers a warehouse scanner and a receivables system can both read. When the 180 is mapped well, the RMA on the label, the count at the door and the credit amount all trace to the same authorized line.

• What this guide covers: the four uses of the 180, its header and BLI line segments, the three RDR code lists, matching an RMA at the dock, return accounting, and India's GST credit note and e-way bill rules for returned goods.
• What it adds: a request and response payload pair, a costed return in dollars and rupees, an incident trace, and a partner onboarding checklist.

One 180 format, four messages from return request to consumer return

The 180 is a single format used in both directions, and the purpose code in BGN01 tells the receiver which message it is reading. X12 describes the set as covering a request for return, the authorization or disposition of a return, notification of return and notification of a consumer return.

In practice a retailer or distributor sends a request, the vendor answers with dispositions per line, and the returning party may later send a notice once goods have shipped. A consumer-return notice is different again: it reports that a shopper sent an item straight to the manufacturer, which matters when the retailer still expects a credit or a replacement for that unit.

Our return-to-vendor deduction blueprint looks at matching RTV deductions against dock counts using 856 and 810 data. This article sits one step earlier: it explains the 180 itself, segment by segment, so the authorization that later justifies a deduction is captured in a structured message instead of an inbox.

Header segments that identify the return and the original order

The 180 heading holds the identifiers everyone downstream will search on: the request or RMA number, the purchase order the goods came from, the parties and the dates. In version 004010 only ST and BGN are mandatory in the heading; everything else is optional, which is why partner guides must say which optional segments they require.

• BGN beginning segment: BGN01 purpose code, BGN02 the sender's reference such as the request number, BGN03 date, and BGN06 a second reference that a vendor response often uses to quote the original request.
• PRF purchase order reference: ties the return to the purchase order on which the goods were bought, which credit teams need to find the original price.
• DTM date reference: up to ten dates in the heading; partners often use 097 for creation and agree a qualifier such as 036 for the RMA expiry.
• N9 reference identification: carries the RMA number, most often with qualifier QJ, Return Material Authorization Number, or RZ, Returned Goods Authorization Number.
• N1 loop: buyer, seller and the return-to address, with N3 and N4 for street and geography so labels print the right destination.
• TD5 and TD1 carrier details: optional routing and weight for vendors that dictate the return carrier or pay the freight.

BLI item lines: product IDs, quantity and the reason for each unit

Every returned item is a BLI loop, and the BLI segment carries up to four product identifiers, the quantity and the unit of measure. The reason or disposition for that line sits in the RDR segment inside the same loop, so a single message can return defective units, refuse excess stock and authorize recalled goods side by side.

BLI01 and BLI02 are the mandatory first qualifier and identifier, such as a UPC, with BLI08 to BLI13 offering three more pairs for a vendor item number or SKU. BLI03 is quantity and BLI04 the unit. If BLI05 or BLI06 is present the other is required, so a unit price cannot be sent without its price identifier code.

Request from retailer (BGN01 13) and vendor response (BGN01 11), X12 004010 180

ST*180*0001~
BGN*13*RR2611030042*20261103*0915~
PRF*4500918812~
DTM*097*20261103~
N1*BY*NORTHGATE HOME STORES*92*0412~
N1*SE*BRIGHTLINE HOUSEWARES*92*BHW77~
BLI*UP*012345678905*120*EA~
RDR**DM***N~
SE*9*0001~

ST*180*0002~
BGN*11*RMA55821*20261104*1130**RR2611030042~
PRF*4500918812~
DTM*036*20261204~
N9*QJ*RMA55821~
N1*ST*BRIGHTLINE RETURNS DC*92*RDC02~
BLI*UP*012345678905*96*EA~
RDR*RA~
BLI*UP*012345678905*24*EA~
RDR*KA~
SE*11*0002~

Notes: RDR02 DM = defective merchandise found on inspection; RDR05 N = not used.
RDR01 RA = return with authorization number; KA = keep with an allowance.
DTM 036 used here for RMA expiry by partner agreement. ISA/GS envelopes omitted.

The pair shows the split that caused the kettle dispute. The retailer asked to return 120; the vendor authorized 96 with RMA55821 and told the store to keep 24 against an allowance. Both answers are in one structured message, so the warehouse label can print 96, not 120.

Disposition codes decide whether goods move, stay or get destroyed

RDR01 is the most consequential element in the 180 because it decides whether a truck is booked at all. Of its 14 codes in version 004010, several mean no freight should move: keep with an allowance, keep and repair, dispose, or request denied. A translator that ignores RDR01 and prints labels for every line wastes freight and creates unauthorized receipts.

EDI 180 return workflows in X12 version 004010 encode the vendor decision in RDR01, where 14 disposition codes separate shipped returns such as RA from keep-in-place outcomes such as KA, KR and DI, so a warehouse management system should book freight only for the shipping codes listed in the partner's implementation guide.

Response reason codes a vendor uses to deny or hold a request

When a vendor refuses or pauses a line, RDR03 says why, and that code should drive the next action automatically. Version 004010 lists 14 response reasons, from more information requested to return time limit exceeded. A line may carry RDR02 or RDR03, never both, so the request reason and the vendor's reply sit in separate messages.

• MI more information: route the line back to the store or DC with a task to supply the missing detail before the request expires.
• PR picture requested: attach photos to the case; the authorization stays pending until the vendor reviews them.
• SR sample requested: ship one unit under a sample reference, keep the rest on hold.
• RT time limit exceeded: stop the claim and move the goods to markdown or disposal under the buyer's own policy.
• QD quantity difference: reconcile the requested count with invoiced quantity before resubmitting.
• NR no record of sale: check the PRF purchase order; the item may have been bought from another supplier.

Request reasons in RDR02 deserve the same care on the way out. The list has 29 codes, and the difference between DM, defective on inspection at the selling unit, DR, defective reported by the consumer, and DT, damaged in transit, decides who pays. A DT line points at the inbound carrier, not the vendor, and often belongs in a freight claim instead of a return.

Matching the authorized RMA at the receiving door

The vendor's returns centre should receive only what the 180 authorized, and it should know that before the trailer is opened. Load the authorized lines as expected receipts keyed by RMA, scan the RMA label at the door, and treat any unit without a matching authorized line as an exception rather than a receipt.

That control fails in predictable ways. The trace below follows the kettle return when the 180 response existed but was never loaded as an expected receipt, so the dock received against the PO alone.

1. 04 Nov 11:30, response sent: vendor 180 BGN11 RMA55821 authorizes 96 units RA and 24 units KA; the translator posts it to a returns mailbox instead of creating an expected receipt.
2. 10 Nov 15:45, store ships: the store builds pallet P-0412-0091 with all 120 units, labels it RMA55821 by hand and books carrier PRO 778-302915.
3. 13 Nov 08:20, dock receipt: the returns centre receives 118 units against PO 4500918812 in transaction RCV-2611-4410; 2 units are missing and 22 units arrive that were never authorized.
4. 14 Nov 10:05, credit posted: receivables issues credit memo CM-88214 for 96 units from the RMA, ignoring the receipt; the retailer separately deducts 120 units on remittance 0007712.
5. 21 Nov 16:30, dispute opened: collections opens case D-5520 for 24 units; with expected receipts loaded, the dock would have refused 22 units at the door and held credit on the 2-unit shortage.

Once a credit is decided, many partners send it as an 812 credit or debit adjustment that quotes the RMA. Our guide to the EDI 812 credit and debit adjustment covers that message and the deduction disputes around it.

Credit timing and return accounting under ASC 606 and Ind AS 115

Return credits should follow received units, while the expected cost of returns belongs in the books from the original sale. Under ASC 606-10-55-23 and Ind AS 115 paragraph B21, a seller that grants a right of return recognises revenue only for consideration it expects to keep, a refund liability for the rest, and an asset for the right to recover the goods.

The 180 helps the estimate as well as the posting. Disposition history by reason code shows how many requested units are actually authorized, how many are kept with allowances and how many are refused, which feeds the expected-return rate. ASC 606-10-55-28 also matters: exchanges of one product for another of the same type, quality, condition and price are not treated as returns, so size or colour swaps should not inflate the refund liability.

Return credits issued from an EDI 180 authorization should follow the warehouse receipt count, not the RMA quantity, so a 96-unit RMA with 94 units received at $18.50 produces a $1,739.00 return credit and a $37.00 hold, consistent with refund liability measurement under ASC 606-10-55-23.

India: return e-way bills and Section 34 credit note deadlines

An Indian return needs two GST documents the 180 does not create on its own: an e-way bill for the movement and, usually, the supplier's credit note. Both have hard rules, so the 180 response and the receipt should trigger them rather than leaving them to month-end.

CGST Rule 138(1) requires an e-way bill when a registered person causes movement of goods with consignment value above fifty thousand rupees, whether in relation to a supply or for reasons other than supply. In the example, 96 units at ₹1,450 plus tax exceed that value, so Part A must be filed before the truck leaves. How the return is documented, by delivery challan or by the buyer's own invoice, is covered in our guide to delivery challans under Rule 55.

• Credit note trigger: Section 34(1) of the CGST Act lets the supplier issue credit notes where goods supplied are returned by the recipient.
• Declaration deadline: the credit note goes in the return for the month of issue, and no later than 30 November after the end of the financial year of supply or the annual return date, whichever is earlier.
• Recipient reversal: under the proviso substituted from 1 October 2025, the supplier's output tax is not reduced unless the registered recipient has reversed the input tax credit attributable to the credit note.
• Cut-off risk: a March sale returned after the following November cannot carry a GST credit note at all, so long return cycles need a different commercial settlement.

Indian supplier credit notes for goods returned under an EDI 180 authorization must be declared by 30 November after the financial year of supply under CGST Act Section 34(2), and from 1 October 2025 output tax falls only after the recipient reverses the matching input tax credit.

Translator rules that reject a bad 180 before a pallet is built

Most return disputes start with a 180 that was syntactically valid but commercially incomplete. A translator and the returns module can reject those messages on arrival with fixed rules, and a 997 or 999 acknowledgement tells the sender at once. Human review is needed only where the content requires judgement, such as photos or condition notes.

Acknowledgements should be returned within the partner's agreed window so the sender knows the request is valid before staff build a pallet. Our guide to the 997 functional acknowledgment explains how to read accepted and rejected group responses.

Partner onboarding checklist for a first 180 exchange

Onboarding a 180 partner is mostly agreement on optional segments and codes, followed by tests that prove the warehouse and credit steps react correctly. Write the agreements into the implementation guide before testing, because a missing qualifier discovered in production means returns arrive with no RMA to match.

A well-mapped 180 turns returns from an email negotiation into a sequence the dock, credit team and tax team can each verify. The wider logistics and supply chain library covers the receipt, deduction and settlement steps around it. If you are planning EDI or returns software work and want a view on scope and effort, share your requirements and we will respond with a proposed approach.