Cloud-based Accounting Integration
The #1 Integration Platform | 1 800 755 6921
Find us on:

EDI - Connecting your Accounting to a World of Trading Partners
Next Steps
Contact me
Request more information

Request Information
Name:*
Company:
Phone:*
Email:*
Accounting package:
Questions or comments:
Please include me in the eBridge mailing list.

EDI Document Type - 141 Product Service Claim Response

What is a 141 Product Service Claim Response?

The 141 Product Service Claim Response document contains information regarding the Product Service Claim Response Transaction Set (141) for use within the context of an Electronic Data Interchange (EDI) environment. Standard EDI formats include X12, ANSI, EDIFACT and its subsets. Click here to read more about supported EDI Standards.


What makes up the 141 Product Service Claim Response document?

A 141 Product Service Claim Response document is organized into the following segment and data elements. A segment can contain at least one data element. Examples of data elements on the 141 Product Service Claim Response document includes the date the product was sold, delivered, and placed in service as well as identify the product model and serial numbers. It can specify the class of service expected from this individual sale.

How is it used?

The 141 Product Service Claim Response document can be used to transmit the status of a product service claim and the items accepted and rejected for payment from the product ser-vice claim. Furthermore, each product service claim submission could have represented the repair of several individual products and each pair could have consisted of several repair actions involving parts and labor.

The Process and Standards

An EDI solution is required to process the EDI documents received into a financial system (click here to view all available financial systems eBridge integrates into) or into a readable format for manual entry.  Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed. 

Click here to find your trading partner

Why eBridge Connections?

Integration with Sage MAS 90, MAS 200, MAS 500, PFW, Business Vision, Sage Pro and more
EDI integration with Microsoft Dynamics Navision, Microsoft Dynamics Axapta and more
 
Integration with Epicor Enterprise, Vantage and iScala
 

Click here for information on benefits, pre-configured trading partner connections, EDI document types and more