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 · Government and regulatory

EDI 176 Court Submission

The X12 document used to submit a legal document or claim, with supporting documentation, to a court or other designated recipient.

Sent by
Party to a case or its attorney
Received by
Court or designated recipient
Standard
ANSI ASC X12

What is an EDI 176?

The EDI 176 Court Submission is the ANSI X12 transaction set used to submit a legal document or claim, with supporting documentation, to a court or other designated recipient. It can also be returned to the submitter to indicate the status of the submission.

Creditors filing proofs of claim in bankruptcy cases, or parties filing routine documents, can submit them electronically and receive confirmation. Many courts have their own electronic filing systems, so the format depends on what each court accepts.

How the EDI 176 worksDiagram of the EDI 176 Court Submission. Party to a case or its attorney sends it to court or designated recipient. It usually follows 175. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required FGS loop with FGS (Form Group). 5 optional loops are listed by their first segment.How the EDI 176 worksCourt Submission: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS175Court and LawEnforcement NoticeEDI 176SENDERParty to a case or itsattorneyRECEIVERCourt or designatedrecipient997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code FCGS … GETransaction set 176ST … SEHEADINGBGNBeginning SegmentRequired loop FGS · repeats many timesFGSForm Group+ 5 optional loops, starting with:LMAMTBBCNM1EFIBlue 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 176. Your trading partner's implementation guide adds its own requirements.
How the EDI 176 worksDiagram of the EDI 176 Court Submission. Party to a case or its attorney sends it to court or designated recipient. It usually follows 175. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required FGS loop with FGS (Form Group). 5 optional loops are listed by their first segment.How the EDI 176 worksCourt Submission: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS175Court and Law Enforcement NoticeEDI 176SENDERParty to a caseor its attorneyRECEIVERCourt ordesignatedrecipient997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code FC (GS … GE)Transaction set 176 (ST … SE)HEADINGBGNBeginning SegmentRequired loop FGS · repeatsmany timesFGSForm Group+ 5 optional loops, starting with:LMAMTBBCNM1EFIBlue 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 176. Your trading partner'simplementation guide adds its own requirements.

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

  • Filing proofs of claim in bankruptcy cases
  • Submitting legal documents to courts
  • Receiving submission status

Where it fits in the document flow

Usually follows 175 Court and Law Enforcement Notice
This document 176 Court Submission
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 176 (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
  • FGS
  • LM
  • LQ
  • AMT
  • BBC
  • NM1
  • DTM
  • EFI
  • BIN
  • SE

Practical example

The 176 in practice

After receiving a bankruptcy notice, a lender files a proof of claim. Its system sends the court a 176 with the case number, the claim amount, the basis of the claim and supporting documents. The court records the claim and returns its status.

Implementation

Implementation considerations for the 176

  • Check which electronic filing formats each court accepts.
  • Meet the court's deadlines for each filing.
  • Attach all required supporting documents.
  • Keep filing confirmations with the case records.

How ECOM helps

Automate the 176 with ECOM

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related government and regulatory documents

All 29 government and regulatory documents

Need help with the EDI 176?

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

Request a Demo Contact us