972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Finance

EDI 141 Product Service Claim Response

The X12 document used to report the status of a product service claim and the items accepted and rejected for payment.

Sent by
Manufacturer or warranty provider
Received by
Servicing organization or dealer
Standard
ANSI ASC X12

What is an EDI 141?

The EDI 141 Product Service Claim Response is the ANSI X12 transaction set used to transmit the status of a product service claim and the items accepted and rejected for payment from the claim.

Warranty claims often contain several items, such as parts, labor and travel. The response tells the servicing organization exactly which items will be paid and why others were rejected, so it can correct and resubmit or close the claim. Claims can be partly paid. Each line carries its own status.

How the EDI 141 worksDiagram of the EDI 141 Product Service Claim Response. Manufacturer or warranty provider sends it to servicing organization or dealer. It usually follows 142. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required N1 loop with N1 (Party Identification) and detail: the required LX loop with LX (Transaction Set Line Number) and REF (Reference Information). 1 optional loops are listed by their first segment.How the EDI 141 worksProduct Service Claim Response: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS142Product Service ClaimEDI 141SENDERManufacturer orwarranty providerRECEIVERServicing organizationor dealer997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code WAGS … GETransaction set 141ST … SEHEADINGBGNBeginning SegmentRequired loop N1 · repeats up to 2N1Party IdentificationDETAILRequired loop LX · repeats manytimesLXTransaction Set LineNumberREFReference InformationSUMMARY+ 1 optional loop, starting with:TDSBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 141. Your trading partner's implementation guide adds its own requirements.
How the EDI 141 worksDiagram of the EDI 141 Product Service Claim Response. Manufacturer or warranty provider sends it to servicing organization or dealer. It usually follows 142. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required N1 loop with N1 (Party Identification) and detail: the required LX loop with LX (Transaction Set Line Number) and REF (Reference Information). 1 optional loops are listed by their first segment.How the EDI 141 worksProduct Service Claim Response: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS142Product Service ClaimEDI 141SENDERManufacturer orwarrantyproviderRECEIVERServicingorganization ordealer997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code WA (GS … GE)Transaction set 141 (ST … SE)HEADINGBGNBeginning SegmentRequired loop N1 · repeats up to 2N1Party IdentificationDETAILRequired loop LX · repeats manytimesLXTransaction Set LineNumberREFReference InformationSUMMARY+ 1 optional loop, starting with:TDSBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 141. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 141, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 141 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Reporting approval of warranty claims
  • Rejecting claim items with reasons
  • Reporting claim status during review

Where it fits in the document flow

Usually follows 142 Product Service Claim
This document 141 Product Service Claim Response
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 141 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • N1
  • LX
  • REF
  • TDS
  • SE

Practical example

The 141 in practice

A dealer submits a warranty claim for an engine repair with parts, eight hours of labor and travel. The manufacturer approves the parts and six hours of labor, rejects two hours as above the standard time and rejects travel. It sends a 141 with the decisions and reasons, and the dealer accepts the adjustment.

Implementation

Implementation considerations for the 141

  • Give a reason for every rejected claim item.
  • Reference claim and item numbers exactly.
  • Reconcile approved amounts with payments.
  • Track resubmissions of corrected claim items.

How ECOM helps

Automate the 141 with ECOM

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Industry

Automotive

Schedules, ship notices, labels, self-billing and multi-plant routing for automotive suppliers.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 141?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us