New: Drop-in replacement for Change Healthcare APIs

EDI 839 Project Cost Reporting

Functional Group PK

X12M Supply Chain Subcommittee

This Draft Standard for Trial Use contains the format and establishes the data contents of the Project Cost Reporting Transaction Set (839) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides the transmission of cost and schedule information to support performance measurement (earned value), program management reporting, and contract funds status reporting. This transaction set will also support the Department of Defense (DoD), Department of Energy (DoE), NASA, and other government agency Cost/Schedule Control Systems Criteria (C/SCSC) and funds status reporting requirements. It is designed to serve the needs of government agencies, prime contractors, and their subcontractors.

Heading

Position
Segment
Name
Max use
  1. To indicate the start of a transaction set and to assign a control number

  2. To indicate the beginning of the project cost reporting transaction set, and information to identify a program name, number, contract type, and security classification.

  3. To specify identifying numbers.

  4. To identify the product to be delivered or the service to be performed

  5. To indicate the total monetary amount.

  6. To qualify percent amounts, and supply percent amounts

  7. To specify pertinent dates and times

  8. CFT Loop Mandatory
    Repeat 100
    1. To identify the cost reporting type, type of units reported, and funds details for the Contract Funds Status Report (CFSR)

    2. BSD Loop Optional
      Repeat >1
      1. To define discrete line items within industry or government reports

      2. To specify identifying numbers.

      3. To indicate the total monetary amount.

      4. To specify quantity information.

      5. To indicate a quantity and/or amount for an identified period

      6. To qualify percent amounts, and supply percent amounts

      7. To provide a free form format that would allow the transmission of text information.

  9. N1 Loop Mandatory
    Repeat 200
    1. To identify a party by type of organization, name and code

      At least one iteration of the N1 loop is required to identify the contractor.
    2. To specify additional names or those longer than 35 characters in length

    3. To specify the location of the named party

    4. To specify the geographic place of the named party

    5. To identify a person or office to whom administrative communications should be directed

    6. To specify pertinent dates and times

  10. To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.