Well Information (625) is an X12 transaction used to transmit detailed data about oil, gas, or water wells between organizations in the energy and utilities sectors. Operators, service companies, and regulatory agencies exchange this transaction set to document well characteristics, locations, measurements, and associated technical details. The transaction set is typically sent in response to requests for well data or as part of regular reporting and compliance submissions. The ST (Transaction Set Header) and BGN (Beginning Segment) establish the message context, while the hierarchical HL (Hierarchical Level) loop structures well-related information. Within each hierarchical level, the LIE (Individual or Event Location) loop, combined with mandatory PPA (Property Location) segments and optional MEA (Measurements) segments, captures specific geographic and physical attributes of the well.

For example, a major oil operator such as ConocoPhillips might send a 625 transaction to the Texas Railroad Commission containing well inventory information. The message would use HL loops to organize data for multiple wells, with each well’s geographic coordinates and surface location captured through the LIE and PPA segments. The CID (Characteristic/Class ID) loop would record well characteristics like depth classification or well type using QTY (Quantity) segments, while the N1 (Name) loop would identify the well operator, lease holder, and other responsible parties. Reference identifiers and yes/no questions in REF and YNQ segments would provide API numbers, well status confirmations, and other regulatory details required for compliance reporting.