Every TPA is uniquely identified by a Sender, Receiver, and Agreement ID. During a conversation between trading partners, the webMethods Chem eStandards Module uses this information to retrieve the TPAs for the initiator and fulfiller in the conversation and to process the business documents exchanged.

The Agreement ID is always the first TN XML document type name used to start the Chem eStandards conversation. . For the initiator of a Chem eStandards conversation, the first TN XML document type name is typically the TN XML document type name representing the internal back‐end document. For example, in the OrderCreate sample, the Agreement ID of the TPA for the "Buyer" conversation is "Internal PO Request". For the fulfiller of a Chem eStandards conversation, the first TN XML document type name is typically the TN XML document type name of the first Chem eStandards Payload document received. For example, in the OrderCreate sample, the Agreement ID of the TPA for the "Seller" conversation is "E41 Purchase Order Request Action Document."