Skip to main content
Skip table of contents

Division Order Header Level and Global Information

Business Background

What is a Division Order

A division order is most commonly referred to in the industry as a division of interest, DOI, or pay sheet. It outlines the ownership in a producing well or group of wells drilled in the same spaced geographical boundary. A division order lists the owners of the production with their interest type, percentage of interest expressed in decimal form, and pay status information.

Why would a client use a Division Order

Division Orders are ultimately used by both Revenue and Cost accountants to either disburse the revenue produced from the well(s) or bill the working interest owners for their share of the costs associated with drilling and maintaining the well(s).

Division Order or Land Analysts create the initial division order outlining the ownership and then maintain it over the lifetime of the well(s) by ensuring the ownership is kept current with record title. The DO or Land Analysts review legal documents and revise ownership accordingly.

Division Orders Configurations

Feature level configurations
(default settings)

Description

auto_approve:
division_orders: false
releases: false
suspenses: false
transfers: false

  • Turns workflow on or off

  • If false, workflow must be set up under User Setup menu

  • If true, workflow will not exist and all maintenance will be auto approved

do_revenue: false

  • Set to True to display correct layout for Division Order fields

do_calc_gwi_from_nri: false

  • Set to True to input all NRI values and systematically calculate the GWI and DI

  • Set to False to input both NRI and GWI and only calculate the DI

do_calc_nri_from_gwi: false

  • Set to True to input all GWI values and systematically calculate the NRI and DI

  • Set to False to input both NRI and GWI and only calculate the DI

rebuild_ca_from_do: false

  • Set to True to allow users the option to rebuild contract allocations during the division order posting process based on the allocations outlined in the DO

do_allow_do_delete: false

  • Set to True to allow users to delete posted division orders where no activity has taken place and thus no data integrity issues exist

auto_do_assets: false

  • Set to True to allow meters to automatically create DO Assets based on

base_contract: false

  • Set to True to allow users to add a contract to an entire cycle of ownership instead of updating each line individually

bg_link_lois: false

  • Set to True to expose a ‘Tag’ column on burden group owners inside a burden group

  • Used to link a burden group owner to a particular line of interest

do_backdate: false

  • Set to True to allow users to backdate a posted division order and its lines of interest

  • If bg_versioned config is also true, the backdate process should also back date the burden group owners within the burden groups

dist_ppa_triggers: false

  • Set to True to enable a user to generate a Distribution PPA through a DO revision

bg_versioned: false

  • Set to True to activate effective dated burden groups

  • Exposes a burden group owner's From and To Date fields within a burden group

do_arkansas_royalty: false

  • Set to True to enable an AR DO check box on a Division Order

  • Enhances Division Order DI Calculations process to systematically calculate for Arkansas DOs with TIK

  • Ensures RI owners receive a full 1/8 and remaining owners share in the TIK burden

do_auto_increment: false

  • Set to True to autogenerate division order numbers from a number pool upon creation of a new division order

  • Number Pool must also be set in the configuration

  • Thor command must be run to kick off the initial process at go-live

do_release_reason: true

  • Set to False to hide the required ‘Reason for Maintenance’ field in the Division Order header

owner_queue:
only_suspend_new_records: false

  • Set to True to enforce a validation that prevents users from changing suspense codes on revisions due to the potential implications in future Distribution PPAs

  • When set, users must complete a suspense batch and thus select all prior versions of the Division Order and ensure data integrity in Distribution PPAs

Top level Configurations
(default settings)

Description

chairman:

reserved_workers: 5

  • If code supports chairman logic, this config controls the number of workers set aside for chairman to use in the posting process

scales:

do_interest: 9

  • Set the scale to indicate the decimal place value to be used across the division order module

upstream_division_order_number_pool: 1000-999999

  • Used to indicate number pool when do_auto_increment configuration is True

Elements of a Division Order Header

Division Order Header fields → Types, Stages and Products

Types, stages and products are descriptors of a division order and are selected by the creator of the division order in the division order header area.

Types include Estimated, True or Inactive

  • Estimated indicates the ownership in the division of interest is an estimation and formal title has yet to be determined

  • True indicates the ownership in the division of interest is aligned with record title

  • Inactive indicates the division order will no longer be used for Revenue Disbursement or Cost Billing

Stages include STD, BPO or APO

  • STD indicates a standard division order that is not subject to a Payout

  • BPO indicates a payout is present and the well has not yet paid out

  • APO indicates a payout is present and the well has reached payout

Products typically include, but are not limited to, All, Oil, Gas

  • All indicates the ownership does not differ by product

  • Oil vs Gas indicates the ownership may be different based on product produced

  • Products may be amended via a code table to include additional products where necessary such as Helium or Condensate

Lifecycles

Lifecycles allow the user to create different Division of Interests (DOIs) under a single shared DO Header. Each Lifecycle created under the Lifecycle Manager results in a separate tab of ownership in the Owner Queue

There are 4 elements to each Lifecycle: Stage, Product, Description Type, and Description

  • Stage (see above)

    • Indicates whether or not the related wells are subject to a Payout

    • The [Stage] selected in the header portion of the Division Order denotes whether or not the ownership is currently in a Before or After Payout stage

  • Product (see above)

    • Each cycle must assigned to a Product

  • Ownership Type

    • This field is a drop down list of values sourced from a code table whereby users can elect such descriptions as JIB, Revenue, Entitlement, Special Revenue, etc

    • It is a required field

  • Type Description

    • This field is optional and simply allows the user to add a detailed description of the ownership where needed

Each cycle also has a checkbox to indicate if the associated ownership for that cycle should be used for JIB or Revenue. Selection drives whether or not the JIB and/or Revenue Process will use that ownership in its monthly processing.

Division Order tabs

Lines of Interest

All cycles created in the Lifecycle Manager generate a tab of ownership. Collectively these tabs of ownership exist together under the Lines of Interest tab.

Burden Groups

A burden group is a means to capture the ownership of a lease or group of leases by working interest owners. If multiple working interest owners share in the ownership of a lease, their ownership allocation share is reflected in the burden group. In order to indicate which leases are owned by which set of working interest owners, the burden group number is assigned to the owner’s line of interest in the owner queue of the division order.

Related Assets

This area serves as the place to link Wells to the outlined ownership. One or many may be linked so long as the ownership attributed to the wells is an exact match. If a user links a Cost Center, this will not get picked up in the Distribution Process. The attached wells must be a type of [well].

Legal Descriptions

The legal description tab consists of a field to enter a pooled unit spaced acreage value followed by three unique grids to capture Jeffersonian, Non-Jeffersonian, and/or Offshore legal descriptions.

This section is meant to capture the legal description of the pooled unit as it may differ from the legal description provided at a well/meter level in the Well Completion Master area of the application.

Aggregator

The aggregator tab at its core it is meant to serve as a means to build ownership in a division order using ownership from one or more existing division orders. We see this functionality commonly leveraged in one of two ways.

When only a single cycle of ownership in an existing DO needs to be revised

  • A user can upload a DO with the revised cycle and a DO Type = Inactive

  • Then, the user can check out the DO in need of a revision and elect to aggregate this uploaded revised cycle into the DO, replacing the original ownership

When a new DO very closely resembles an existing DO

  • Users can copy the DO or they can use the Aggregator to add the ownership of the similar DO into the existing other DO

Versions/History

The versions/history tab stores all past versions of the Division Order. As Division Orders are revised and new sequence numbers are created, the prior versions are archived and stored under this tab. These versions are read-only but can be opened and viewed to see the ownership at the time they were used in the Revenue or JIB process.

Division Order Owner Queue

Base Contracts

Each cycle of ownership must be related to a Base Contract. The relationship is built by selecting a contract from the pop-up. By adding a base contract, the assumption is being made that all owners within that cycle are being disbursed under the same contract

Override Contract

An option exists in the Owner Queue to relate a specific line of interest to a contract that differs from the base contract used for all ownership.

By denoting an Override Contract on the line of interest, that particular owner will disburse under the terms of its own contract when running the Revenue Process.

Fee Exemption Groups

It is very common for Oil and Gas leases to contain language that exempts the mineral owner from bearing the costs associated with things like transportation, gathering, and or processing. These exemptions are typically outlined in lease provision clauses.

Within a division order, if a mineral owner is exempt from any type of fee, this exemption can be notated by assigning the owner’s line of interest to the Fee Exemption Group that contains the fee

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.