Report

For the typical user in Canada: You are looking for an audit report to identify any tickets that may have slipped through the Invoice Calculator without having revenue attached to them.

For the typical user in the United States: You are looking for an audit report to identify any tickets that may have slipped through the Invoice Calculator without having revenue attached to them. In addition, you are looking for a report to identify all tickets where you have not yet recorded receipt of revenue for the ticket from the mill.

Focus:

This report focuses on the revenue side of load ticket transactions and allows users to identify tickets where revenue has not been successfully processed by the system.

When using this report, it is important to understand that the Logger's Edge can be configured one of two ways in the Basic Setup portion of the software.

Method 1 (typical for Canadian users) Load Revenue is calculated when the invoice calculator is run. The user is not required to enter actual revenue for each ticket under the Data Entry| Loads Slips | Load Revenue menu item when the physical settlement is received from the mill. For users following Method 1, this report has a single purpose: to identify those tickets where the user has not set up sufficient information for the system to calculate the revenue owing from the mill.

Method 2 (typical for U.S. users), Load Revenue is calculated when the invoice calculator is run to show the user what the mill should pay for each ticket, but the system still expects the user to make a corresponding explicit entry for the revenue from each and every ticket (under Data Entry | Load Slips | Load Revenue menu item) when the physical mill settlement is received. For users following Method 2, this report has two purposes: 1) to identify those tickets where the user has not set up sufficient information for the system to calculate the revenue owing from the mill; and 2) to show all tickets in a given date range where revenue has not been posted to The Logger's Edge from the actual mill settlements.

This report is a companion report to the Mill Settlements, All Loads report except that this one shows only loads where revenue has not been processed properly (for Method 1 users), and/or where revenue has not been recorded in The Logger's Edge as having been paid (for Method 2 users).

Selection Window:

The selection window allows you to filter the report by:

Date Range: You can either select a pay period, or you can simply enter the start and end date directly into the selection criteria window. The Period selection is merely a short-cut for entering a date range, so you can always edit the start and end dates to be any date you choose. For example, you can pick a period defined as 8/1/2004 to 8/12/2004, and then extend the end date by three days to 8/15/2004. If you leave the end time blank, the program will assume you want the entire day for the end date. In the example below, the start date/time is 8/1/2004 00:00:00 (a blank is assumed to be time 00:00:00) and the end date/time is 8/15/2004 00:00:00. Because the end date time is blank (or 00:00:00), the program assumes you want the whole day of the 15th and makes the end date/time 8/16/2004 00:00:00. In the selection query, the program returns records whose start date/time is greater than OR equal to the start/date time and strictly less than the end date/time.
Note: for report information that is based on load tickets, the report uses the Date Out (not the Date In).
Block: You can select any or all of your blocks.
You can Sort the report by either Date/Time, or by Block.
The "Only Print Raw Data" option generates a report with the report detail, but with no subtotals or totals.

Detailed Description:

The report shows payments due for each load on an activity-by-activity basis. The columns are:

Block Code: Source Block of the loads
Date: Date (out) on the load ticket
Ticket: Load ticket number
Load No: Secondary Load # entered on the load ticket itself (if used -- otherwise will appear as NONE)
Date Out: Exit date/time of the load
Destination: Destination on the load ticket
Net Weight: Net (Gross less Tare) load weight
Contract: Revenue Contract under which activity should be paid (If the system cannot ascertain which revenue contract to which the ticket should belong because the user has entered insufficient information on the revenue rate setup, this column will show "Not Paid."
Activity: Activity for which revenue was received (column will be blank if contract column says "Not Paid")
Pay Weight: Pay units used for calculating revenue. May be true weight measures like tonnes or tons, but may be a volume measure like cubic metres, thousand board feet or cords. (column will be blank if contract column says "Not Paid")
Rate: Pay rate used to calculate revenue for the ticket
Revenue: By definition, any tickets that appear in this report will say "Not Paid" (or the column will be blank if the "Contract" column showed as "Not Paid")
Cheque #: Will always be blank in this report because the revenue and cheque # have not been (and will not be) recorded for the tickets displayed in this report.

Key Notes:

You must run the invoice calculator before you run this report.
This report makes NO distinction between Header and Detail records (C_Part_13) for piece-based systems.
Be aware that if each load ticket should have revenue entries for multiple activities (e.g., logging broken out separately from trucking), the ticket will only appear as unpaid in this report if ALL activities are unpaid. If any activity has been paid, the ticket will not appear in the list.

Report:

Example:

The report is ordered first by block and then destination within each block. Totals are provided for each destination within a block and for the block as a whole. Though not shown, there is also a grand total for all blocks and destinations at the bottom of the report.

Method 1 Users (typical Canadian user): A "Not Paid" in the Contract column implies a rate setup problem on the part of the user. A "Not Paid" in the Revenue column indicates that you explicitly set up a $0 pay rate for the ticket, or that your pay weight was 0 for the ticket.

Method 2 Users (typical U.S. user): A "Not Paid" in the Contract column implies a rate setup problem on the part of the user. A "Not Paid" in the Revenue column indicates that you have not yet recorded your revenue from the mill under the "Data Entry | Loads | Load Revenue window.)

Example Report