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 · Master data

EDI 625 Well Information

The X12 document used to exchange engineering, geological and environmental information about non-financial well activities.

Sent by
Oil and gas operator or service company
Received by
Partner, regulator or data provider
Standard
ANSI ASC X12

What is an EDI 625?

The EDI 625 Well Information is the ANSI X12 transaction set that facilitates the exchange of engineering, geological and environmental information related to non-financial well activities. It can be used between private industry trading partners, and with regulators, to relay information about wells.

Operators report well data such as locations, completions, production tests and environmental information to partners and regulatory agencies. A standard format avoids rekeying data into different agencies' and partners' systems. Data can cover drilling, completion, testing and environmental work over a well's life, and is used by partners, regulators and data vendors.

How the EDI 625 worksDiagram of the EDI 625 Well Information. Oil and gas operator or service company sends it to partner, regulator or data provider. 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 HL loop with HL (Hierarchical Level). 4 optional loops are listed by their first segment.How the EDI 625 worksWell Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 625SENDEROil and gas operator orservice companyRECEIVERPartner, regulator ordata provider997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code WLGS … GETransaction set 625ST … SEHEADINGBGNBeginning SegmentRequired loop HL · repeats many timesHLHierarchical Level+ 4 optional loops, starting with:LIECIDN1LMBlue 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 625. Your trading partner's implementation guide adds its own requirements.
How the EDI 625 worksDiagram of the EDI 625 Well Information. Oil and gas operator or service company sends it to partner, regulator or data provider. 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 HL loop with HL (Hierarchical Level). 4 optional loops are listed by their first segment.How the EDI 625 worksWell Information: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 625SENDEROil and gasoperator orservicecompanyRECEIVERPartner,regulator or dataprovider997 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 WL (GS … GE)Transaction set 625 (ST … SE)HEADINGBGNBeginning SegmentRequired loop HL · repeats manytimesHLHierarchical Level+ 4 optional loops, starting with:LIECIDN1LMBlue 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 625. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting well completion data to regulators
  • Sharing well information with partners
  • Exchanging environmental data about wells

Where it fits in the document flow

This document 625 Well Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 625 (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
  • HL
  • LIE
  • PPA
  • CID
  • N1
  • LM
  • LQ
  • SE

Practical example

The 625 in practice

An operator completes a new well. It sends the state regulator and its working interest partners a 625 with the well identifier, location, depths, completion details and initial test results. The regulator updates its well records, and partners update their reservoir models.

Implementation

Implementation considerations for the 625

  • Use standard well identifiers, such as API numbers.
  • Follow regulators' reporting requirements and deadlines.
  • Keep engineering units consistent across reports.
  • Separate well information from financial billing (819).

How ECOM helps

Automate the 625 with ECOM

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

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

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

Related transactions

Related master data documents

All 25 master data documents

Need help with the EDI 625?

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

Request a Demo Contact us