oildex revenue detail (cdex)description: a signed numeric field in the form +/- xxxxxxxxx.xx...
TRANSCRIPT
March 19, 2018
Version 5.6.0
Oildex Revenue Detail (CDEX) Data Guide (For Sending and Receiving CDEX Formatted Data)
Copyright 2015–2018, Oildex, a service of Transzap, Inc. All rights reserved. 2
Version 5.6.0
Contents
CDEX Record Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Type 1 - Check Detail Line Item Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Type 2 - Check Summary Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Type 3 - Transmission Summary Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Type 7 - New Property Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Type 8 - New Property Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Product & Transaction Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Product Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Transaction Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18State Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Reports & Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Acknowledgment Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Delivery Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Error and Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Oildex Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CDEX Record FormatsOildex Revenue Detail currently supports five record formats for transmitting CDEX files:
Type 1 - Check Detail Line Item Record Type 2 - Check Summary Record Type 3 - Transmission Summary Record Type 7 - New Property Identification Record Type 8 - New Property Summary Record
A description of each record, field requirements, and acceptable values or settings is included on the following pages. It should be noted that:
All fields, including alphanumeric will be right justified with leading zeros. Blanks are not allowed, except where specifically indicated.
Signed numeric fields must have either a plus (+) or minus (-) sign in the first (left-most) position of the field. All decimal points are implied. They are not to be inserted into the CDEX records. When Record Types 1 and 2
are received, the Julian date of the split will be in columns 113-115. For Record Type 7 the Julian date will be in columns 130-132. This should be used as a reference only.
Type 1 - Check Detail Line Item Record
Field 1 Record Type
Field 2 Company Code
Field 3 Check Number
Column: 1
Length: 1
Description: A numeric code used to identify and separate different CDEX formats. (1 for Type 1 records)
Column: 2-3
Length: 2
Description: An alphanumeric field used to identify the sending/receiving company. Sending companies will input the receiver’s code, and receivers will get the sender’s code.
Column: 4-15
Length: 12
Description: An alphanumeric field used to identify the check number. Its primary use is to allow the by-check correlation of the hard copy check stubs to the CDEX electronic data. When the checks are received, the check number and actual check amount can be compared with the CDEX transmitted data. All check numbers must be unique. In the case where the actual check number is not available in the transmitting company’s system, a pseudo check number must be assigned. For example, a pseudo check number could be a combination of owner number and Julian date.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 3
Version 5.6.0
Field 4 Unit/Property Lease Code
Field 5 From Production Date
Field 6 Production Date
Field 7 Product Code
Field 8 Transaction Code
Column: 16-29
Length: 14
Description: An alphanumeric field that identifies the unit, property, or lease number associated with the payment detail.
Column: 30-33
Length: 4
Description: Year and month in the form MMYY. When used for a single production month, the month and year of production are identified. The production and payment data should be reported for single production months. This should be a standard for both current and out-of-period bookings. When the individual month’s data cannot be identified and the data spans several months, this field identifies the first month of production.
Column: 34-37
Length: 4
Description: Year and month in the form MMYY. When used for a single production month, this field will be the same as From Production Date (Field 5). When used with out-of-period data spanning several months, this field identifies the last month of production.
Column: 38-39
Length: 2
Description: A numeric code that identifies the product. The available Product Codes can be found on page 17. The Product Codes are used to associate all revenues and expenses by product on a lease, unit, or property.
Column: 40-41
Length: 2
Description: A numeric code that describes the particular revenues, deductions, and reimbursements. The available Transaction Codes can be found on page 18. Transaction Code ‘00’ identifies the normal sale of a product. As such, it usually has an associated lease gross volume and severance tax value. Therefore, ‘00’ can only be used in the Transaction Code 1 field and should not be used in the Transaction Code 2 field.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 4
Version 5.6.0
Field 9 Lease Gross Volume
Field 10 Lease Gross Severance Tax
Field 11 Lease Net Value
Field 12 Owner Share Lease Net Value
Field 13 Transaction Code
Column: 42-53
Length: 12
Description: A signed numeric field in the form +/- XXXXXXXXX.XX (implied decimal). This field is used only when Transaction Code 1 is ‘00’. Depending on the product code used, this volume may express BBL, MCF, GAL, or LONG TONS. Fractions of measurement are not reported for MCF and GAL (100 MCF would appear as +00000010000 in the record, with an implied decimal).
Column: 54-62
Length: 9
Description: A signed numeric field in the form +/- XXXXXX.XX (implied decimal). This field is used only when Transaction Code 1 is ‘00’. Although this field indicates a value withheld or subtracted from the lease gross value, the convention is to report it as a positive number. Where out-of-period corrections involve a reduction in severance tax, this value will be a negative number.
Column: 63-74
Length: 12
Description: A signed numeric field in the form +/- XXXXXXXXX.XX (implied decimal). When Transaction Code 1 is ‘00’, this field is the Lease Gross Value minus the Lease Gross Severance Tax. Note: The Lease Gross Value is not represented by a field in the detail information.
Column: 87-88
Length: 2
Description: A signed numeric field in the form +/- XXXXXXXXX.XX (implied decimal). The actual amount dispersed for the owner on a particular lease, unit, or property for a particular product. This represents the owner’s share of the Lease Net Value.
Column: 87-88
Length: 2
Description: A numeric code that describes the particular revenues, deductions, and reimbursements. The available Transaction Codes can be found on Page 14. All Transaction Codes except ‘00’ may be used. If the Lease Gross Value of Charge/Reimbursement/WPT and Owner Share of Charge/Reimbursement/WPT are zero, this field should be left blank.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 5
Version 5.6.0
Field 14 Lease Gross Value of Charge or Reimbursement
Field 15 Owner Share of Lease Gross Value of Charge or Reimbursement
Field 16 Transmission Date
Field 17 Type of Interest
Column: 89-100
Length: 12
Description: A signed numeric field in the form +/- XXXXXXXXX.XX (implied decimal). Used for Transaction Codes other than ‘00’ to identify the specific Charge (deduction) or Reimbursement.
Column: 101-112
Length: 12
Description: A signed numeric field in the form +/- XXXXXXXXX.XX (implied decimal). The actual amount withheld for the owner on a particular lease, unit, or property for a particular product. This represents the owner’s share of the Lease Gross Value of the specific Charge (deduction) or Reimbursement.
Column: 113-115
Length: 3
Description: A numeric field that identifies the Julian date when the data was distributed to the receiver by Oildex. It should be zero filed or left blank by the sending company.
Column: 116
Length: 1
Description: An alphanumeric field that describes the type of owner interest. This field should be blank if not available. Type of interest: Code B - Blanchard Code M - miscellaneous Code N - Net Profit Payment Code O - Overriding Code P - Production Payments Code R - Royalty Code S - Special Overriding Code R - Royalty Code T - Tax Code W - Working Code X - Buy/Purchase
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 6
Version 5.6.0
Field 18 Decimal Flag
Field 19 Decimal Interest
Field 20 BTU Factor
Field 21 Blank
Total record length = 132.
Column: 117
Length: 1
Description: A numeric flag that indicates the type of decimal used. 0 or blank = Net value based on division of interest decimal1 = Settlement based on adjusted division order decimal
Column: 118-126
Length: 9
Description: A numeric field that contains the owner’s decimal in the form X.XXXXXXXX (implied decimal).
Column: 127-130
Length: 4
Description: A numeric field that represents the BTU factor in the form X.XXX (implied decimal).
Column: 131-132
Length: 2
Description: Reserved for future use.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 7
Version 5.6.0
Type 2 - Check Summary Record
Field 1 Record Type
Field 2 Company Code
Field 3 Check Number
Field 4 Record Count
Field 5 Actual Check Amount
Column: 1
Length: 1
Description: An alphanumeric field used to identify and separate different CDEX formats. (2 or Type 2 records)
Column: 2-3
Length: 2
Description: An alphanumeric field used to identify the sending/receiving company. The sending companies will input the receiver’s code, and the receivers will get the sender’s code.
Column: 4-15
Length: 12
Description: An alphanumeric field used to identify the check number. This should be the same number as in the preceding Type 1 records.
Column: 16-19
Length: 4
Description: A numeric field indicating the number of detail line items (preceding Type 1 records) for this check. If the record count exceeds 10,000, enter the last four digits in this field (11343 would appear as 1343)
Column: 20-31
Length: 12
Description: A signed numeric field in form +/- XXXXXXXXX.XX (implied decimal). This is the summarized amount taken from the two Owner share fields from all previous Type 1 records.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 8
Version 5.6.0
Field 6 Net-Out Flag
Field 7 Payment Flag
Field 8 Effective Date
Field 9 Lease Gross Volume Hash Total
Field 10 Lease Gross Severance Tax Hash Total
Column: 32
Length: 1
Description: An alphanumeric field that should be set to “Y” to indicate a net-out agreement and “N” or blank when there is not a net-out agreement.
Column: 33
Length: 1
Description: An alphanumeric flag that identifies the type of payment being made. Code E - Electronic Funds Transfer Code W - Wire Transfer Code C or blank - Manual Check Code N - Netted
Column: 34-37
Length: 4
Description: The date on which the payment is effective and the funds moved. In the form MMDD.
Column: 38-50
Length: 13
Description: A signed numeric field in the form +/- XXXXXXXXXX.XX (implied decimal). This field is the total of the Lease Gross Volume for all previous Type 1 records.
Column: 51-60
Length: 10
Description: A signed numeric field in the form +/- XXXXXXX.XX (implied decimal). This field is the total of the Lease Gross Severance Tax for all previous Type 1 records.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 9
Version 5.6.0
Field 11 Lease Net Value Has Total
Field 12 Owner Share Lease Net Hash Total
Field 13 Lease Gross Value of Charge or Reimbursement Hash Total
Field 14 Owner Share of Lease Gross Value of Charge or Reimbursement Hash Total
Field 15 Transmission Date
Field 16 Owner Number
Column: 61-73
Length: 13
Description: A signed numeric field in the form +/- XXXXXXXXX.XX (implied decimal). This field is the total of the Lease Net Value for all previous Type 1 records.
Column: 74-86
Length: 13
Description: A signed numeric field in the form +/- XXXXXXXXXX.XX (implied decimal). This field is the total of the Owner HASH TOTAL Share Lease Net Value for all previous Type 1 records.
Column: 87-99
Length: 13
Description: A signed numeric field in the form +/- XXXXXXXXXX.XX (implied decimal). This field is the total of Lease Gross Value of Charge/Reimbursement for all previous Type 1 records.
Column: 100-112
Length: 13
Description: A signed numeric field in the form +/- XXXXXXXXXX.XX (implied decimal). This field is the total of the Owner Share of Lease Gross Value of Charge/Reimbursement for all previous Type 1 records.
Column: 113-115
Length: 3
Description: A numeric field that identifies the Julian date when the data was distributed to the receiver by Oildex. It should be zero filled or left blank by the transmitting company.
Column: 116-127
Length: 12
Description: An alphanumeric field that contains the owner interest number for the check being transmitted. It must be non-blank and non-zero.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 10
Version 5.6.0
Field 17 Blank
Total Record Length = 132
Column: 128-132
Length: 5
Description: Reserved for future use
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 11
Version 5.6.0
Type 3 - Transmission Summary Record
Field 1 Record Type
Field 2 Check Count
Field 3 Check Total
Field 4 Blank
Total record length = 132
Column: 1
Length: 1
Description: A numeric code used to identify and separate different CDEX formats. (3 for Type 3 records)
Column: 2-6
Length: 5
Description: A numeric field containing the total number of checks (count of the Type 2 records) transmitted.
Column: 7-20
Length: 14
Description: A signed numeric field containing the total amount for all checks transmitted. In the form +/- XXXXXXXXXXX.XX (implied decimal).
Column: 21-132
Length: 112
Description: Reserved for future use.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 12
Version 5.6.0
Type 7 - New Property Identification
Field 1 Record Type A
Field 2 Company Code
Field 3 Property Number
Field 4 Property Name
Field 5 Operator Name
Field 6 State Code
Column: 1
Length: 1
Description: A numeric code used to identify and separate different CDEX formats. (7 for Type 7 records)
Column: 2-3
Length: 2
Description: An alphanumeric field used to identify the sending/receiving company.
Column: 4-17
Length: 14
Description: An alphanumeric field used to identify the lease, unit, or property.
Column: 18-57
Length: 40
Description: An alphanumeric field that contains the name of the property being identified.
Column: 58-77
Length: 20
Description: An alphanumeric field that contains the name of the operator of the property.
Column: 78-79
Length: 2
Description: A numeric field that contains the API identification for the State in which the property is located. A list of State Codes can be found on page 22.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 13
Version 5.6.0
Field 7 County Code
Field 8 Decimal Interest
Field 9 Type of Interest
Field 10 Lease Description
Column: 80-82
Length: 3
Description: A numeric field that contains the API identification for the county in which the property is located.
Column: 83-91
Length: 9
Description: A numeric field that contains the decimal interest for the property, in the form X.XXXXXXXX (implied decimal).
Column: 92
Length: 1
Description: An alphanumeric field that describes the type of owner interest. This field should be blank if not available. Code and Type of Interest: Code B - Blanchard Code M - Miscellaneous Code N - Net Profit Payment Code O - Overriding Code P - Production Payments Code R - Royalty Code S - Special Overriding Royalty Code T - Tax Code W - Working Code X - Buy/Purchase
Column: 93-129
Length: 37
Description: A free form alphanumeric field that contains a description of the lease including additional information such as section, township, range, etc.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 14
Version 5.6.0
Field 11 Transmission Date
Total record length = 132
Column: 130-132
Length: 3
Description: A numeric field that identifies the Julian date when the program was distributed to the receiver by Oildex. It should be zero filled or left blank from the transmitting company.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 15
Version 5.6.0
Type 8 - New Property Summary
Field 1 Record Type
Field 2 Record Count
Field 3 Blank
Total record length = 132
Column: 1
Length: 1
Description: A numeric code used to identify and separate different CDEX formats. (8 for Type 8 records)
Column: 2-6
Length: 5
Description: A numeric field that contains the total number of Type 7 records sent. This is used as a hash total to confirm a transmission.
Column: 7-132
Length: 126
Description: Reserved for future use.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 16
Version 5.6.0
Product & Transaction CodesThis section contains the product and transaction codes.
Product Codes
The following codes represent valid products for CDEX:
Code Product Reported Units
00 State Withholding
05 Combination of Products
10 Oil of Undetermined Origin BBL
11 Oil Well Oil BBL
12 Condensate BBL
13 Plant Condensate BBL
20 Gas of Undetermined Origin MCF
21 Oil Well Gas MCF
22 Gas Well Gas MCF
23 Irrigation Gas MCF
30 LNG With No Determined Breakdown GAL
31 Methane GAL
32 Ethane GAL
33 Propane GAL
34 Butane GAL
35 Isobutane GAL
36 Gasoline GAL
40 Non-Hydrocarbon Products
41 Sulphur LONG TONS
42 Salt Water BBL
43 Carbon Dioxide MCF
44 Helium MCF
50 Old Ocean Settlement AFT
60 Other Product
90 Undefined Product
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 17
Version 5.6.0
Transaction Codes
The following codes represent valid transactions for CDEX:
Code Transaction
00 Normal Sale of Product (Normally has an associated Gross Volume and may or may not have an associated Severance Tax Value).
01 Settled MMBTU Volume
02 Royalty % and Value
03 Conservation Tax
04 School Tax
05 State Withholding Tax
06 State NRA (Non-Resident Alien) Tax
07 Federal NRA Tax
08 Backup Withholding Tax
10 Unspecified Deduction or Reimbursement (Please use minimally)
11 Federal Income Taxes - Oil & Gas
12 State Income Taxes - Oil & Gas
13 Mining Rights Taxes - Oil & Gas
14 Ad Valorem Taxes - Oil & Gas
15 Taxes Paid for Co-Owners - Oil & Gas
16 Tax Reimbursement - Oil & Gas
17 Tax Credit allowed on Payment of Production Taxes - Gas
18 Petroleum and Gas Fund - Oil & Gas
19 Subsidence Abatement Fund - Oil & Gas
20 Royalty Paid for Co-Owners - Oil & Gas
21 Manual Accounting Entry to Prevent Over/Under Payment
23 Transportation - Oil
24 Dehydration - Oil
25 Gas Deduction for Compression, Sweetening, Dehydration and/or Transportation
26 Reimbursement to Working Interest for Gas Royalty Deduction
27 Dehydration Reimbursements for Gas Purchases
28 Purchased Gas Resold
29 Deficiency and Pre-Paid Gas
30 Interest Payment
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 18
Version 5.6.0
*Transaction Code Notes:
Transaction Codes 45, 46, 47, and 48To create consistency, we ask that all CDEX senders use Transaction Code 45, 46, 47, and 48 with the file format below:
Fields 1 through 7 - would be populated as in a normal transaction
Field 8 - normally use transaction code “00”
Fields 9 through 12 - normal volume and values
Field 13 - use transaction code 45, 46, 47, or 48 as appropriate
Field 14 - normally should contain a negative gross deduction value for field 13
Field 15 - normally should contain a negative net deduction value for field 13
Fields 16 through 21 - would be populated as in a normal transaction
31 Joint Venture Charges (JIB)
43 Transportation - Gas
44 Dehydration - Gas
45* Marketing
46* Compression
47* Gathering
48* Processing and/or Sweetening
50 Override
51 Supplemental
52 Overriding Royalty
53 Royalty
54 Net Proceeds
60 Oklahoma SB 1048
61 New Mexico SB 0621
62* Utah Withholding
63* Montana State Withholding SB 439
64* North Dakota Withholding HB 1198
65* Colorado State Withholding
66 Pennsylvania State Withholding
70 Windfall Profit
71 WFPT - Tier 1
72 WFPT - Tier 2
Code Transaction
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 19
Version 5.6.0
Transaction Code 62 - Utah WithholdingTo create consistency, we ask that all CDEX senders use Transaction Code 62 with the file format below. In addition, we ask that senders create a separate line of detail by property for the new code.
Fields 1 through 7 - would be populated as in a normal transaction
Field 8 - we recommend using transaction code “00”
Fields 9 through 12 - should contain zero’s
Field 13 - use transaction code 62
Field 14 - should contain zero’s
Field 15 - should contain a negative value associated with transaction code 62
Fields 16 through 21 - would be populated as in a normal transaction
Transaction Code 63 - Montana State Withholding SB439Withholding commences in January 2008
To create consistency, we ask that all CDEX senders use Transaction Code 63 with the file format below. In addition, we ask that senders create a separate line of detail by property of the new code.
Fields 1 through 7 - would be populated as a normal transaction
Field 8 - we recommend using transaction code “00”
Fields 9 through 12 - should contain zero’s
Field 13 - use transaction code 63
Field 14 - should contain zero’s
Field 15 - should contain a negative value associated with transaction code 63
Fields 16 through 21 - would be populated as a normal transaction
Transaction Code 64 - North Dakota State Withholding HB1198Withholding commences in January 2014
To create consistency, we ask that all CDEX senders use Transaction Code 64 with the file format below. In addition, we ask that senders create a separate line of detail by property for the new code.
Fields 1 through 7 - would be populated as a normal transaction
Field 8 - we recommend using transaction code “00”
Fields 9 through 12 - should contain zero’s
Field 13 - use transaction code 64
Field 14 - should contain zero’s
Field 15 - should contain a negative value associated with transaction code 64
Fields 16 through 21 - would be populated as a normal transaction
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 20
Version 5.6.0
Transaction Code 65 - Colorado State WithholdingWithholding commences in April 2014
To create consistency, we ask that all CDEX senders use Transaction Code 65 with the file format below. In addition, we ask that senders create a separate line of detail by property for the new code.
Fields 1 through 7 - would be populated as a normal transaction
Field 8 - we recommend using transaction code “00”
Fields 9 through 12 - should contain zero’s
Field 13 - use transaction code 65
Field 14 - should contain zero’s
Field 15 - should contain a negative value associated with transaction code 65
Fields 16 through 21 - would be populated as a normal transaction
Transaction Code 66 - Pennsylvania State WithholdingWithholding commences in January 2018
To create consistency, we ask that all CDEX senders use Transaction Code 66 with the file format below. In addition, we ask that senders create a separate line of detail by property for the new code.
Fields 1 through 7 - would be populated as a normal transaction
Field 8 - recommend using transaction code “00”
Fields 9 through 12 - should contain zero’s
Field 13 - use transaction code 66
Field 14 - should contain zero’s
Field 15 - should contain a negative value associated with transaction code 66
Fields 16 through 21 - would be populated as a normal transaction
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 21
Version 5.6.0
State Codes
The following codes represent API state codes for CDEX:
Code State Code State
01 Alabama 29 New Jersey
02 Arizona 30 New Mexico
03 Arkansas 31 New York
04 California 32 North Carolina
05 Colorado 33 North Dakota
06 Connecticut 34 Ohio
07 Delaware 35 Oklahoma
08 D.C. 36 Oregon
09 Florida 37 Pennsylvania
10 Georgia 38 Rhode Island
11 Idaho 39 South Carolina
12 Illinois 40 South Dakota
13 Indiana 41 Tennessee
14 Iowa 42 Texas
15 Kansas 43 Utah
16 Kentucky 44 Vermont
17 Louisiana 45 Virginia
18 Maine 46 Washington
19 Maryland 47 West Virginia
20 Massachusetts 48 Wisconsin
21 Michigan 49 Wyoming
22 Minnesota 50 Alaska
23 Mississippi 51 Hawaii
24 Missouri 55 Alaska Offshore
25 Montana 56 Pacific Offshore
26 Nebraska 60 Northern Gulf of Mexico
27 Nevada 61 Atlantic Coast Offshore
28 New Hampshire
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 22
Version 5.6.0
Reports & MessagesThis section contains the reports and messages in Oildex Revenue Detail (CDEX) product.
Acknowledgment Reports
When incoming CDEX files are received and processed by Oildex, an Acknowledgment Report is generated and forwarded to the sender. This report contains the following information.
List of the checks in the file, which includes a summary of the check numbers, receivers, lines, amounts, and owner numbers.
Receiver’s contact information
Oildex Support contact numbers and email addresses
The Acknowledgment Report also contains any error or warning messages related to the file. It is sent to the company contact person’s email address listed in the Oildex account.
Delivery Reports
When incoming CDEX files are received, processed, and distributed to trading partners by Oildex, a Delivery Report is generated and forwarded to the receiver. This report contains the following information:
List of the checks in the file, which includes a summary of the check numbers, senders, lines, amounts, and owner numbers
Sender’s contact information
Oildex Support contact numbers and email addresses
The Delivery Report also contains an error or warning messages related to the file. It is sent to the company contact person’s email address listed in the Oildex account.
Error and Warning Messages
One of the most important factors in transmitting CDEX formatted data is the use of common data formats by both the sending and receiving companies. When incorrect data are used within the record fields, errors will occur. In order to prevent the sending of non-standardized data, CDEX has incorporated verification and editing checks into the sending module.
When a data problem occurs resulting in an Error message, the check number or property number referenced in the Error message will be rejected and will not be processed. The sender should correct the error described for that data record, and resend the corrected record. When a data problem occurs resulting in a Warning message, the data will still be processed and distributed to the receivers.
Error and Warning messages appear on the Acknowledgment and Delivery Reports.
Error messages include:
Bad Format - Check Detail Line: ### The line number is a Type 1 record with a bad data format. (This may sometimes bew due to control characters being introduced into the text data or the abrupt termination of an FTP transmission of the file.)
Bad Format - Check Summary Line: ### The line number is a Type 2 record with a bad data format. (This may sometimes be due to control characters being introducted into the text data or the abrupt termination of an FTP transmission of the file.)
Bad Format - Transmission Summary Line: ### The line number is a Type 3 record with a bad data format. (This may sometimes be due to control characters being introduced into the text data or the abrupt termination of an FTP transmission of the file.)
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 23
Version 5.6.0
Bad Format - New Property ID Line: ### The line number is a Type 7 record with a bad data format. (This may sometimes be due to control characters being introduced into the text data or the abrupt termination of an FTP transmission of the file.)
Bad Format - New Property ID Summary Line: ### The line number is a Type 8 record with a bad data format. (This may sometimes be due to control characters being introduced into the text data or the abrupt termination of an FTP transmission of the file.)
Invalid Record Type at Line ### The line number does not begin with 1, 2, 3, 7, or 8 in column 1. (This may also be caused by a line containing all blanks. Empty line breaks are allowed however. They will not cause this error to occur.)
Check Numbers Changed with no Type 2 Record - ###/### There was no Type 2 record found in going from the first check number noted in the message to the second check number that was encountered in the file (The first check number will not be processed. The following warning may also appear: Warning: Check Number ### Ignored - No Type 2 Record.)
Check Number ### had an Incorrect Record Count The Record Count field (columns 16-19 in the Type 2 records does not match the number of Type 1s preceding it.
Rejected Check Number: ### - Sum Mismatch of # in Lease Gross Volume The sum of the Lease Gross Volume fields (columns 41-53) in all preceding Type 1s does not match the Lease Gross Volume Total in the Type 2 record.
Rejected Check Number: ### - Sum Mismatch of # in Lease Gross Volume Severance Tax The sum of the Lease Gross Severance Tax fields (columns 54-62) in all preceding Type 1s does not match the Lease Gross Severance Tax Total in the Type 2 record.
Rejected Check Number: ### Sum Mismatch of # in Lease Net Value The sum of the Lease Net Value fields (columns 63-74) in all preceding Type 1s does not match the Lease Net Value Total in the type 2 record.
Rejected Check Number: ### - Sum Mismatch of # in Owner Share of Lease Net Value The sum of the Owner Share of Lease Net Value fields (columns 75-86) in all preceding Type 1s does not match the Owner Share of Lease Net Value Total (columns 74-86) in the Type 2 record.
Rejected Check Number: ### - Sum Mismatch of # in Lease Gross Value of C/R/WPT The sum of the Lease Gross Value of C/R/WPT fields (columns 89-100) in all preceding Type 1s does not match the Owner Share of Lease Net Value Total (columns 74-86) in the type 2 record.
Rejected Check Number: ### - Sum Mismatch of # in Owner Share of Lease Gross Value of C/R/WPT The sum of the Owner Share of Lease Gross Value of C/R/WPT fields (columns 101-112) in all preceding Type 1s does not match the Owner Share of Lease Gross Value of C/R/WPT Total (columns 100-112) in the Type 2 record.
Rejected Check Number: ### - Sum of owner share totals did not equal check summary amount The sum of the Owner Share of Lease Net Value Total (columns 74-86) and the Owner Share of Lease Gross Value of C/R/WPT Total (columns 100-112) in the Type 2 record does not match the Check Amount value (columns 20-31).
Rejected Check Number: ### - Invalid Transaction Code 2 Non-zero C/R/WPT fields requires this to be populated. The Transaction Code 2 field in the Type 1 record (columns87-88_ cannot be blank if the Lease Gross Value of C/R/WPT or Owner Share of Lease Gross Value of C/R/WPT has a value (is non-zero).
Rejected Check Number: ### - 00 is invalid for this Transaction Code field The Transaction Code 2 field in the Type 1 record (columns 87-88) cannot be “00” if the Lease Gross Value of C/R/WPT or Owner Share of Lease Gross Value of C/R/WPT has a value (is non-zero).
Warning messages include:
Check Number T02_011C4C_1 - Invalid FromProductionDate at Line: 0.0. This date has ProductionDate greater than current date.
Duplicate Check Number: ### - Ignored. The check number has been previously sent. Duplicate Property Number: ### - Ignored. The property number has been previously sent. Zero Detail Line - Line: ### - Ignored. The line number contains all zeroes as values for Lease Gross Volume
(columns 42-53), Lease Gross Severance Tax (columns 54-62), Lease Net Value (columns 63-74), Owner Interest Lease Net Value (columns 75-86), Lease Gross Value of C/R/WPT (columns 89-100), and Owner Interest of Lease Gross Value of C/R/WPT (columns 101-112).
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 24
Version 5.6.0
Invalid FromProductionDate at Line: 0.0. This date has ProductionDate greater than current date.
Oildex Support
Senders and receivers of CDEX data should contact Oildex Support with any issues related to transmissions or quality of data.
Copyright 2012–2018, Oildex, a service of Transzap, Inc. All rights reserved. 25
Version 5.6.0