EDI 176 Court Submission

Functional Group TC

X12F Finance Subcommittee

This Draft Standard for Trial Use contains the format and establishes the data contents of the Court Submission Transaction Set (176) for use within an Electronic Data Interchange (EDI) environment. This transaction set can be used to submit a legal document or a claim and supporting documentation to a court or other designated recipient. It can be transmitted to the submitter to indicate the date and docket information assigned, or it can be transmitted to the submitter to indicate claim disposition or an opinion deciding a case.


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

  2. To indicate the beginning of a transaction set.

  3. To specify identifying numbers.

  4. CDS Loop Mandatory
    Repeat >1
    1. To identify and describe a specific court case

    2. To specify pertinent dates and times

    3. To provide a description of the included specification or technical data items.

    4. To specify identifying numbers.

    5. To identify specific actions already taken on a legal claim, and/or indicate that information related to a previously filed claim is being updated by this transaction

    6. To describe court events and actions in a specific court case

    7. LM Loop Optional
      Repeat >1
      1. To transmit standard code list identification information

      2. Code to transmit standard industry codes

    8. BBC Loop Optional
      Repeat >1
      1. To identify the basis and type of a legal claim

      2. To indicate the total monetary amount.

    9. NM1 Loop Optional
      Repeat >1
      1. To supply the full name of an individual or organizational entity

      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 specify identifying numbers.

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

    10. EFI Loop Optional
      Repeat >1
      1. To provide basic information about the electronic format of the interchange data.

      2. To transfer binary data in a single data segment and to allow identification of the end of the data segment through a count. There is no identification of the internal structure of the binary data in this segment.

  5. 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.