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 · Finance

EDI 819 Joint Interest Billing and Operating Expense Statement

The X12 document an asset operator uses to send periodic expense details to the co-owners of the asset, such as an oil and gas property.

Sent by
Operator of the jointly owned asset
Received by
Non-operating owners (working interest partners)
Standard
ANSI ASC X12

What is an EDI 819?

The EDI 819 Joint Interest Billing and Operating Expense Statement is the ANSI X12 transaction set used to transmit periodic expense details from the operator of an asset to the various owners of that asset, for example the operation of a petroleum lease or property with multiple owners.

In oil and gas, one company operates a well or lease on behalf of several working interest owners and bills each its share of the costs. The joint interest billing lists the expenses by category and property, and each partner's share, so partners can audit and record them without paper statements.

How the EDI 819 worksDiagram of the EDI 819 Joint Interest Billing and Operating Expense Statement. Operator of the jointly owned asset sends it to non-operating owners (working interest partners). It usually starts the exchange. It is usually followed by 820 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BOS (Beginning Segment for Joint Interest Billing and Operating Expense Statement), detail: the required JIL loop with JIL (Line Item Detail for the Operating Expense Statement) and summary: AMT (Monetary Amount Information) and CTT (Transaction Totals). 3 optional loops are listed by their first segment.How the EDI 819 worksJoint Interest Billing and Operating Expense Statement: who sends it, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 819SENDEROperator of the jointlyowned assetRECEIVERNon-operating owners(working interestpartners)997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY820PaymentOrder/Remittance Advice997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code JBGS … GETransaction set 819ST … SEHEADINGBOSBeginning Segment for JointInterest Billing and OperatingExpense Statement+ 1 optional loop, starting with:N1DETAILRequired loop JIL · repeats up to10,000JILLine Item Detail for theOperating ExpenseStatement+ 1 optional loop, starting with:JIDSUMMARYAMTMonetary Amount InformationCTTTransaction Totals+ 1 optional loop, starting with:PSABlue 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 819. Your trading partner's implementation guide adds its own requirements.
How the EDI 819 worksDiagram of the EDI 819 Joint Interest Billing and Operating Expense Statement. Operator of the jointly owned asset sends it to non-operating owners (working interest partners). It usually starts the exchange. It is usually followed by 820 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BOS (Beginning Segment for Joint Interest Billing and Operating Expense Statement), detail: the required JIL loop with JIL (Line Item Detail for the Operating Expense Statement) and summary: AMT (Monetary Amount Information) and CTT (Transaction Totals). 3 optional loops are listed by their first segment.How the EDI 819 worksJoint Interest Billing and Operating ExpenseStatement: who sends it, where it fits and whatthe standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 819SENDEROperator of thejointly ownedassetRECEIVERNon-operatingowners(workinginterestpartners)997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY820Payment Order/Remittance Advice997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code JB (GS … GE)Transaction set 819 (ST … SE)HEADINGBOSBeginning Segment for JointInterest Billing and OperatingExpense Statement+ 1 optional loop, starting with:N1DETAILRequired loop JIL · repeats up to10,000JILLine Item Detail for theOperating ExpenseStatement+ 1 optional loop, starting with:JIDSUMMARYAMTMonetary AmountInformationCTTTransaction Totals+ 1 optional loop, starting with:PSABlue 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 819. Your trading partner'simplementation guide adds its own requirements.

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

  • Billing partners for their share of operating costs
  • Reporting capital and operating expenses by property
  • Supporting joint venture audits

Where it fits in the document flow

This document 819 Joint Interest Billing and Operating Expense Statement
Usually followed by 820 Payment Order/Remittance Advice997 Functional Acknowledgment

Structure

Mandatory segments in the 819 (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
  • BOS
  • N1
  • JIL
  • JID
  • AMT
  • PSA
  • CTT
  • SE

Practical example

The 819 in practice

An operator runs a group of wells owned with three partners. Each month it sends each partner an 819 listing the drilling, lease operating and overhead costs by property, the partner's working interest percentage and the amount billed. The partners load the statements into their accounting systems and pay their shares.

Implementation

Implementation considerations for the 819

  • Use expense categories consistent with the joint operating agreement.
  • Show each partner's interest percentage and calculation.
  • Reconcile statements with property and partner master data.
  • Support audits with detail that partners can trace.

How ECOM helps

Automate the 819 with ECOM

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Industry

Manufacturing

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

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 finance documents

All 58 finance documents

Need help with the EDI 819?

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

Request a Demo Contact us