We Make EDI Integration Easy
Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs.
What is a 839 - Project Cost Reporting document?
The 839 EDI document type is an electronic version of a paper Project Cost Reporting. Standard EDI formats include X12, ANSI, EDIFACT and its subsets.
The 839 EDI document type is used to report cost and schedule information of a project to support performance measurement, program management reporting, and contract funds status reporting..
What makes up the 839 - Project Cost Reporting document?
An EDI 839 - Project Cost Reporting document is organized into segment and data elements. A segment can contain at least one data element. Each data element contains a data field. There are an infinite number of possibilities available for a company to include data on an 839 Project Cost Reporting. There are an infinite number of possibilities available for a company to include data on an 839 - Project Cost Reporting.
How is a 839 - Project Cost Reporting used?
The 839 EDI document is sent by contractors, subcontractors, or government to report project costs. After the 839 Project Cost Reporting is received, a 997 Functional Acknowledgment is sent back from the receiver indicating that the 839 Project Cost Reporting was successfully received.
How is a 839 - Project Cost Reporting processed?
An EDI solution is required to process the EDI documents received into an ERP or accounting system 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.
eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.