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 105 Business Entity Filings

The bi-directional X12 document businesses and government administrators use to exchange required business entity filings, such as annual reports.

Sent by
Business entity, registered agent or government office
Received by
Government office or business entity
Standard
ANSI ASC X12

What is an EDI 105?

The EDI 105 Business Entity Filings is the bi-directional ANSI X12 transaction set business entities, government administrators and regulators can use to exchange required business entity filing information, such as annual reports.

Corporations and other entities must file reports with the jurisdictions where they are formed or registered to do business. Registered agents and service companies file for many entities and benefit from a structured electronic format, while government offices can return acknowledgments and status the same way. Fees are often paid with the filing.

How the EDI 105 worksDiagram of the EDI 105 Business Entity Filings. Business entity, registered agent or government office sends it to government office or business entity. It usually starts the exchange. 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 NM1 loop with NM1 (Individual or Organizational Name) and detail: the required HL loop with HL (Hierarchical Level). 5 optional loops are listed by their first segment.How the EDI 105 worksBusiness Entity Filings: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 105SENDERBusiness entity,registered agent orgovernment officeRECEIVERGovernment office orbusiness entity997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code BFGS … GETransaction set 105ST … SEHEADINGBGNBeginning SegmentRequired loop NM1 · repeats many timesNM1Individual or Organizational Name+ 2 optional loops, starting with:AMTLMDETAILRequired loop HL · repeats many timesHLHierarchical Level+ 3 optional loops, starting with:LMNM1EFIBlue 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 105. Your trading partner's implementation guide adds its own requirements.
How the EDI 105 worksDiagram of the EDI 105 Business Entity Filings. Business entity, registered agent or government office sends it to government office or business entity. It usually starts the exchange. 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 NM1 loop with NM1 (Individual or Organizational Name) and detail: the required HL loop with HL (Hierarchical Level). 5 optional loops are listed by their first segment.How the EDI 105 worksBusiness Entity Filings: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 105SENDERBusiness entity,registered agentor governmentofficeRECEIVERGovernmentoffice orbusiness entity997 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 BF (GS … GE)Transaction set 105 (ST … SE)HEADINGBGNBeginning SegmentRequired loop NM1 · repeatsmany timesNM1Individual orOrganizational Name+ 2 optional loops, starting with:AMTLMDETAILRequired loop HL · repeats manytimesHLHierarchical Level+ 3 optional loops, starting with:LMNM1EFIBlue 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 105. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 105, 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 105 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 annual reports for business entities
  • Filing changes such as registered agent updates
  • Receiving filing acknowledgments

Where it fits in the document flow

This document 105 Business Entity Filings
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 105 (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
  • AMT
  • NM1
  • LM
  • LQ
  • HL
  • NX2
  • REF
  • LX
  • EFI
  • SE

Practical example

The 105 in practice

A registered agent service files annual reports for 2,000 client companies across several states. Its system sends each state office a 105 with each entity's officers, address and registered agent. The offices accept the filings and return confirmations.

Implementation

Implementation considerations for the 105

  • Follow each jurisdiction's filing requirements and deadlines.
  • Keep entity identifiers consistent with official records.
  • Track filing confirmations and fees paid.
  • Check which jurisdictions accept electronic filings in this format.

How ECOM helps

Automate the 105 with ECOM

Solution

Enterprise Integration

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

Solution

EDI Integration

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

Industry

Financial Services

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

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 105?

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

Request a Demo Contact us