1. Operator Sub-Account There is an option when emailing the PDF of the run statement to also include an XLSX copy of the tickets.
   
2. Under the #80 Company > First Purchaser tab > Statements subtab, you can select Expanded, Standard, or Basic Option.

The Basic option provides less detail. The Column headings are Operator Number, Operator Name, Lease Number, Lease Name, Ticket Date, Ticket Number, Tank ID, Observed Gravity, Contract Price, Net Barrels, Gross Vale, and Lease State.

If you import gross and net volumes, the Override option on Run Ticket will be selected. If this is the case, do not include the net volumes when importing. This will force the system to auto-calculate the net. Also see Net Volume Calculations in afor more information on how the net is calculated.

Pak Accounting now allows run tickets in First Purchaser to accept a negative price. The Company Option is on the Advanced First Purchaser Tab. This option will default to checked.

A run ticket with a negative price will process accordingly.

In order to achieve the correct severance tax calculation on a negative value, which varies by state, the Minimum Price Per field on the Severance Tax Rate Maintenance Special Options Tab can be utilized for the taxes based on value. Be sure to check “Adjust negative price to Minimum Price Per when calculating taxable value.”

The taxes/fees based on volume will still be calculated as before, while the taxes based on value will be calculated based on the Minimum Price Per.

Pak Accounting provides the ability to hold tickets if necessary. A ticket can be held and subsequently released in Daily Run Ticket Maintenance. Any tickets that are held will not be reported on the Run Statement and have the ability to be exported via CODE or get paid. They will move forward to the new accounting month when the current month is closed. A list of held tickets can be generated on the Cost of Crude Report.

Tickets that have been held should not be confused with RRC-held leases. Oil should not be picked up on these leases.

For Tanks, the Gross Volume is calculated based on the tank strappings and the change in the Starting Gauge and Ending Gauge.

For Meters and T/G Adj, the Gross Volume is the difference between the Starting Reading and the Ending Reading.

The Net Volume is calculated using factors to adjust the Obs. Temp to 60 degrees F and the Obs Gravity to 40. If there is a BS&W factor, the Net Volume is further reduced by the BS&W factor. For Meters, if there is a meter factor, the Net Volume is further adjusted by this factor.

1. Operator Sub-Account: There is an option when emailing the PDF of the run statement to also include an XLSX copy of the tickets.
   
2. Under the #80 Company > First Purchaser tab > Statements subtab, you can select Expanded, Standard, or Basic Option.

The Basic option provides less detail. The Column headings are Operator Number, Operator Name, Lease Number, Lease Name, Ticket Date, Ticket Number, Tank ID, Observed Gravity, Contract Price, Net Barrels, Gross Vale, and Lease State.

The most common reason is that the effective date on the price contract is not the effective date of the ticket being priced. (For example, a ticket dated October 15th would not show as priced using the price contract pictured below because the price contract is not effective until November 1st.)

NOTE: When setting up a new price contract, the effective date will default to the first day of the current month (computer date). (For example, I set up a new contract on November 26th for tickets dated October 1st, but the contract will default to November 1st. I have to change the effective date on the price contract to October 1st to price October tickets.

Other Reasons tickets might not be priced:

Property is set as a Station and not a Lease on the Property maintenance> General tab

The Price Index has not been set up.

The Purchaser on the Price Contract is not set to price tickets:

Find out the following:

1. Has the FP cycle been started?
   If Yes, see #2-
2. Have tickets been extracted to Revenue yet?
   If not, clear the cycle, update the Allocation and Recalculate the Tickets. Then, start the cycle again.
   If yes, did the client just extract the tickets and is a restore a viable option?
   If restore is not an option, update the Allocation and do correction tickets.
   C1 Ticket - reversal of original ticket
   C2 Ticket - This new ticket will look at the new Allocation
   You can then use the Selective Extract option to Extract the tickets to Revenue.

NOTE: Remember, Allocations are entered at the Allocation Header level!

When tickets are extracted to Revenue, the system takes all of the entries for a property and creates one entry per property. (Ex. 100 tickets in FP totaling 150,000.00 are extracted to Rev for Property A. In GL, you will only see one entry for Property A-9601. Therefore, if a C1 Reversal Ticket and a C2 Correction ticket equal the same amount, the system will squeeze these to a 0.00 entry, and no entry will be posted to GL. (If this happens, why were they doing the correction tickets, to begin with- maybe it needed a rev correction, not a ticket correction.) If the Reversal Ticket is 100,000 and the correction ticket equals 150,000, you would only see an entry in the GL of 50,000 (9601-Property A 50,000.00).

Depending on the desired results of the ticket correction, you might need to Extract the C1 ticket and then go back and extract the C2 ticket (Selective Extract).

Is this a current run statement, or are you trying to run a historical run statement?

If current run statement - Check the Property general tab>Operator for Run statement; if incorrect, change to the correct operator, recalculate tickets, and then run the run statement again.

If historical run statement - Run statement looks at the current Operator on the property and does not retain the historical operator. If the operator has changed since the time of the original run statement, you will need to change the run statement to the correct operator, run the statement, and then change the Operator for the Run statement on the Property Master back to the current Operator.

You can enter the ticket as the current cycle month but with a backdated ticket date (E.g., cycle month 11/2023, ticket date 10/5/2023). Or, you can clear the cycle/month, which will open the previous account month in Daily Run Ticket. Clearing a cycle does not affect tickets that have already been extracted to revenue (i.e., the tickets will not be paid again).

Check the effective date of the contract under Pricing/Other File Maintenance > Price Contract

Has that Price Contract been added to that property? If so, check that effective date as well. Look under Property > Price Contract tab

Check in Company Maintenance > Company > General Tab > Entry Date From field.

If you have used the Correction Ticket Utility and did not alter either of the tickets, there will not be a GL transaction, as the tickets zero each other out.

If you have not done a correcting ticket, check the name of the Purchaser. The Sub-Account code of the Purchaser must be the same as the Company Code to which you wish to send these transactions. (very important to note when using the Copy Company feature)

Unfortunately, there is not a mass delete feature for Run Tickets.

Use the Mass Change Utility. See Purchaser/Operator > Utilities > Mass Change Utility

Check the measurement of the oil volume defined in increments to compute the total tank capacity. Negative numbers are not allowed. Must be in 1/4-inch increments. (found in the Tank/Meter Maint).