How to Extract Data from a Division Order

Updated Jul 1, 2026 6 min read

A division order sets each owner's decimal share of production revenue, and a division order analyst keys those interests into the revenue system on every well. Here is how to extract that data automatically with OCR, which fields to capture, how to handle eight-place decimal interests, and how the data flows into your oil and gas accounting software.

// Try it now, no signup required

PDF, JPG, PNG, BMP, HEIC, TIFF

Upload a document to extract

Free on your own files. No credit card, no signup to test.

A division order is short, but it carries the one number that has to be exactly right: each owner's decimal share of production revenue. On every well, a division order analyst reads the owner, the property or unit, the effective date, and the decimal interest, then sets up or updates that owner in the revenue system. When a new well comes online with dozens of owners, or an acquisition lands a few thousand division orders on the same desk, that keying becomes the bottleneck that holds up the first revenue run. This is how to extract that data automatically, which fields matter, and how to keep an eight-place decimal interest from getting transposed on the way into your accounting software.

What is a division order?

A division order is a document that states each owner's decimal share of production revenue from a well or unit and directs the operator or purchaser on how to distribute the proceeds. It lists the owner, the property or well, the effective date, and the decimal interest computed from the title opinion. The owner signs it to confirm their interest and payment details before revenue is released. A division order does not change ownership; it tells the operator how to pay the owners that the title work already established.

What fields should you extract from a division order?

The fields that drive owner setup and revenue are consistent across layouts, even when the form is not. Capture these on every division order:

  • Owner name and owner number, exactly as written, so the record matches the existing account.
  • Property or well and unit identifier, including the API number or property code when present.
  • Effective date, which sets the production month the interest begins.
  • Interest type, royalty, overriding royalty, working interest, or net profits, because each pays differently.
  • Decimal interest, usually carried to eight decimal places, which is the figure revenue is calculated against.
  • Owner address and tax ID, for the 1099 and the check or ACH, where the form includes them.

Get those six things right and the owner is ready to pay. The decimal interest is the field that cannot be wrong, because a transposed digit eight places out still moves real money on every check.

How do you extract data from a division order with OCR?

The workflow is the same one that handles any structured upstream document. First the engine classifies the file, recognizing that the document is a division order rather than a lease or a JIB statement, which matters when the file arrives as a mixed packet. Then OCR converts the page to machine-readable text, including any signature block and hand-completed fields. Then layout-aware extraction ties each value to its label, so the eight-place decimal under the owner line is captured as the decimal interest, not as a stray number. Finally the values run through validation and anything low-confidence routes to a person. To understand why classification comes first on a mixed file, see document classification software, and for the distinction between reading the page and pulling named fields, read OCR vs data extraction.

How do you handle eight-place decimal interests accurately?

Decimal interests are the reason accuracy matters more here than on most documents. A division order commonly states an interest like 0.01562500, and a single misread digit changes the owner's revenue. The dependable pattern is straight-through processing for high-confidence reads and a short review queue for anything the engine flags, so an analyst confirms the few uncertain decimals instead of rekeying every owner. A good extraction also validates that the decimals across a unit sum sensibly and flags an interest that does not, which catches a misread before it reaches a revenue run.

What is the difference between a division order and a division order title opinion?

A division order title opinion is the attorney's analysis of who owns what in a tract or unit, and it is where the decimal interests are first computed. The division order is the operational document sent to each owner that states their confirmed decimal share and collects their signature and payment details. The title opinion is the source; the division order is the instruction to pay. Document processing software reads both, pulling the computed interests off the opinion and the confirmed owner and decimal data off the division order itself.

Can OCR read scanned and signed division orders?

Yes. Division orders are routinely printed, signed, and scanned back, and older ones arrive as faxes or images in a well file. Intelligent character recognition reads hand-completed fields and signatures, and layout-aware extraction finds the owner, property, and decimal interest no matter where they sit on the page or which operator's form it is. Low-confidence reads route to a reviewer, so an analyst verifies the few uncertain fields instead of retyping an entire division order off a scan.

How does the extracted data get into oil and gas accounting software?

Extraction is only useful if the data lands where owner accounting actually happens. After the engine reads a division order, it exports the owner, property, effective date, interest type, and decimal interest as a file or pushes them through an API into oil and gas accounting and land platforms such as Quorum, P2 EnergyLink, W Energy Software, PakEnergy, and OGsys. That means the owner is set up and the interest is loaded without an analyst keying the decimal twice, and the export carries a confidence score and an audit trail on every value.

How much time does automated division order processing save?

The savings scale with owner count. A well with fifty owners is fifty division orders to read and key, and a package of new wells or an acquisition can run into the thousands. Reading and keying each one by hand takes minutes; extraction takes seconds and routes only the uncertain decimals to review. The result is that the first revenue run is not waiting on data entry, and the analysts spend their time confirming interests and clearing title questions instead of typing eight-place decimals off a stack of forms.

Automate division order extraction with DocuOCR

A division order is small, but the decimal interest on it controls real money, and there are a lot of them. Automating the read keeps the keying off your analysts and the errors off your revenue runs. DocuOCR classifies a mixed well or land file, reads division orders, leases, JIB statements, AFEs, and run tickets, extracts the fields your land and accounting teams need, and exports clean data with an audit trail. See the full workflow on our oil and gas document processing software page, learn how the underlying pipeline works on intelligent document processing, and start with the underlying lease agreement OCR if leases are your first priority. You can test it on your own documents first, no signup required.

Extract your documents with DocuOCR

DocuOCR's AI OCR software turns any document into clean, structured data in seconds. No template setup required.

Start free

← Back to all articles