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 142 Product Service Claim

The X12 document a servicing organization uses to claim for service performed on a product, with the product, owner and repair details.

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

What is an EDI 142?

The EDI 142 Product Service Claim is the ANSI X12 transaction set used to transmit the servicing organization, claimant, manufacturer, seller and purchaser of a product. It can specify the product's current usage, the dates it was sold, delivered and placed in service, and the service performed.

Dealers and service centers claim reimbursement from manufacturers for warranty repairs. The claim identifies the product, the failure, the parts and labor used and the amounts claimed, and the manufacturer responds with the 141.

How the EDI 142 worksDiagram of the EDI 142 Product Service Claim. Servicing organization or dealer sends it to manufacturer or warranty provider. It usually follows 140 and 143. It is usually followed by 141 and 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), the required N9 loop with N9 (Extended Reference Information), the required LIN loop with LIN (Item Identification), the required PRR loop with PRR (Problem Report) and the required REP loop with REP (Repair Action). 8 optional loops are listed by their first segment.How the EDI 142 worksProduct Service Claim: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS140Product Registration143Product ServiceNotificationEDI 142SENDERServicing organizationor dealerRECEIVERManufacturer orwarranty provider997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY141Product Service ClaimResponse997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code WAGS … GETransaction set 142ST … SEHEADINGBGNBeginning SegmentRequired loop N1 · repeats up to 4N1Party IdentificationDETAILRequired loop LX · repeats manytimesLXTransaction Set LineNumberRequired loop N9 · repeatsmany timesN9Extended ReferenceInformationRequired loop LIN · repeatsmany timesLINItem IdentificationRequired loop PRR · repeatsmany timesPRRProblem ReportRequired loop REP · repeatsmany timesREPRepair Action+ 7 optional loops, starting with:LMN1CIDMEAIT1AMTSUMMARY+ 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 142. Your trading partner's implementation guide adds its own requirements.
How the EDI 142 worksDiagram of the EDI 142 Product Service Claim. Servicing organization or dealer sends it to manufacturer or warranty provider. It usually follows 140 and 143. It is usually followed by 141 and 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), the required N9 loop with N9 (Extended Reference Information), the required LIN loop with LIN (Item Identification), the required PRR loop with PRR (Problem Report) and the required REP loop with REP (Repair Action). 8 optional loops are listed by their first segment.How the EDI 142 worksProduct Service Claim: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS140Product Registration143Product Service NotificationEDI 142SENDERServicingorganization ordealerRECEIVERManufacturer orwarrantyprovider997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY141Product Service Claim Response997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code WA (GS … GE)Transaction set 142 (ST … SE)HEADINGBGNBeginning SegmentRequired loop N1 · repeats up to 4N1Party IdentificationDETAILRequired loop LX · repeats manytimesLXTransaction Set LineNumberRequired loop N9 · repeatsmany timesN9Extended ReferenceInformationRequired loop LIN · repeatsmany timesLINItem IdentificationRequired loop PRR · repeatsmany timesPRRProblem ReportRequired loop REP · repeatsmany timesREPRepair Action+ 7 optional loops, starting with:LMN1CIDMEAIT1AMTSUMMARY+ 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 142. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 142, 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 142 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

  • Claiming warranty repairs
  • Claiming service under service contracts
  • Reporting failures for quality analysis

Where it fits in the document flow

Usually follows 140 Product Registration143 Product Service Notification
This document 142 Product Service Claim
Usually followed by 141 Product Service Claim Response997 Functional Acknowledgment

Structure

Mandatory segments in the 142 (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
  • N9
  • LIN
  • LM
  • LQ
  • PRR
  • CID
  • MEA
  • REP
  • IT1
  • AMT
  • TDS
  • SE

Practical example

The 142 in practice

A truck dealer replaces a faulty fuel injector under warranty. It sends the manufacturer a 142 with the vehicle's serial number, mileage, in-service date, the failure code, the part replaced and the labor time. The manufacturer validates the claim against the warranty and responds with a 141.

Implementation

Implementation considerations for the 142

  • Use the manufacturer's failure and labor codes.
  • Include usage, such as hours or mileage, for warranty checks.
  • Reference recalls when the repair is recall work.
  • Submit claims within the warranty claim deadlines.

How ECOM helps

Automate the 142 with ECOM

Industry

Manufacturing

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

Industry

Automotive

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

Solution

Financial Document Automation

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

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 142?

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

Request a Demo Contact us