ANSI X12 837P - 5010 1000A NM1 Submitter Name

Image Description

May 21, 2026

The 1000A Submitter Name Loop within the ANSI X12 837 Professional transaction identifies the organization or individual responsible for submitting the healthcare claim transaction. In the 837P transaction, the NM1 segment within Loop 1000A is used to transmit the submitter’s name and organizational identifier information to the receiving clearinghouse or payer.

The submitter is often a healthcare provider, billing service, revenue cycle management company, or clearinghouse responsible for creating and transmitting the electronic claim file. This information helps downstream systems identify the origin of the transaction and determine where acknowledgements, rejections, and transaction responses should be routed.

The 1000A NM1 segment appears near the beginning of the transaction immediately after the BHT segment and before the receiver information in Loop 1000B. The segment is considered mandatory within the transaction structure and is used once per ST/SE transaction set.

In many real-world claim workflows, the submitter listed within the transaction may differ from the actual billing provider shown later in the file. For example, a physician practice may outsource claim submission activities to a third-party billing company or clearinghouse that transmits claims on the provider’s behalf.

Sample 837P (5010) – 1000A NM1 Submitter Name

> 1000A Submitter Name
  • ISA*00*          *00*          *ZZ*SENDERID       *ZZ*RECEIVERID     *250918*0535*^*00501*000000011*1*P*:~
  • GS*HC*SENDERCODE*RECEIVERCODE*20250918*0535*10022*X*005010X222A1~
    • ST*837*0001*005010X222A1~
    • BHT*0019*00*0001*20250918*0535*CH~
      • ...
      • ... additional transaction loops and segments ...
      • NM1*41*2*ECLAIMS BILLING SERVICES*****46*123456789~
      • ... additional transaction loops and segments ...
      • ...
    • SE*42*0001~
    GE*1*10022~
  • IEA*1*000000011~

In this example:

  • The first value (41) identifies the entity as the transaction submitter.
  • The second value (2) indicates the submitter is an organization rather than an individual person.
  • The third value contains the submitter name, which is commonly the billing company, provider organization, or clearinghouse submitting the transaction.
  • The value (46) identifies the type of identifier being transmitted for the submitter organization.
  • The final value contains the submitter identifier assigned by the receiver, clearinghouse, or trading partner arrangement.

In many production environments, the submitter identifier is assigned during the electronic trading partner enrollment process. Clearinghouses and payers commonly use this value to validate incoming transactions and associate the claim file with the appropriate submitter account, customer profile, or routing configuration.

Important: The 1000A Submitter Name loop identifies the organization responsible for transmitting the electronic claim transaction.

Note: The submitter identified within Loop 1000A is not always the same entity as the billing provider identified later within the 837 transaction.

ANSI X12® references are used for educational and interoperability discussion purposes only. Official implementation specifications should be obtained through licensed X12 publications and authorized distributors.


We hope you found this article helpful! Please reach out to us with questions/feedback.