X12 transaction code
X12 180 Return Merchandise Authorization And Notification
X12 180 Return Merchandise Authorization And Notification: explore its business purpose, mapping identifiers, validation tests and 5 partner references across 5 listed channels.
- Standard
- X12
- Code
- 180
- Partner references
- 5
Implementation guide
X12 180 mapping and validation
X12 180 Return Merchandise Authorization And Notification is used when a return is requested, authorized or notified. Preserve return authorization, original order and returned item so the return authorization in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | return authorization return authorization, original order and returned item |
|
| Update the receiving system | Processing the return authorization ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the return authorization Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 810 Invoice
accounts-receivable or accounts-payable invoice: a bill is ready for the buyer to process.
- X12 861 Receiving Advice Acceptance Certificate
goods receipt or acceptance record: received goods are counted or accepted.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a return is requested, authorized or notified. Name the operational owner of the return authorization and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map return authorization, original order and returned item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic return authorization data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful return authorization processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 180 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic return authorization data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out return authorization without processing it twice.
Document structure
X12 180 Return Merchandise Authorization And Notification at the element level
The X12 180 reference contains 22 segment entries and 75 data elements; 42 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 22
- Data elements
- 75
- Mandatory elements
- 42
| Segment | Elements | Mandatory |
|---|---|---|
| BGN | 5 | 3 |
| PRF | 2 | 1 |
| DTM | 4 | 1 |
| N9 | 3 | 1 |
| NTE | 1 | 1 |
| N1 | 2 | 1 |
| N3 | 2 | 1 |
| PER | 7 | 1 |
| BLI | 6 | 2 |
| PID | 3 | 1 |
- Transaction Set Purpose Code
- Reference Identification
- Date
- Purchase Order Number
- Date/Time Qualifier
- Reference Identification Qualifier
- Description
- Entity Identifier Code
Find your trading partner for X12 180
5 partners, 5 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 180 Return Merchandise Authorization And Notification appears in this catalog
The largest groups of classified 180 catalog entries are in retail, building & hardware and e-commerce & marketplaces.
By industry
- retail 3 channels
- building & hardware 1 channel
- e-commerce & marketplaces 1 channel
By network
- Rithum 2 channels
- CommerceHub 1 channel
FAQ
X12 180 questions
What is X12 180 Return Merchandise Authorization And Notification used for?
180 is used when a return is requested, authorized or notified. It carries information for the return authorization. Match it to your business system using return authorization, original order and returned item.
Which partners list X12 180?
The directory on this page links 5 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
What should I map for X12 180?
Start with return authorization, original order and returned item and the target return authorization. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 180 error handling?
Test a return quantity larger than the original shipment and require review. Keep authorization separate from physical receipt so stock is not increased early. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 180 relate to other EDI messages?
X12 810 Invoice; X12 861 Receiving Advice Acceptance Certificate are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 180 and 810?
180 is used when a return is requested, authorized or notified. 810 is used when a bill is ready for the buyer to process. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
