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.
• Destination:  You can select any or all of your destinations.
• The "Summary Data" option generates a summary version of the report with only subtotals and totals by block/destination.
• The "Only Print Raw Data" option generates a report with the report detail, but with no subtotals or totals.
• The "Use Receipt Date" option uses the receipt date of the load revenue as the date identifier instead of the date hauled of the load.  The receipt date is an optional field that can be enabled so that revenue can be recorded by the date when your settlement is received from the mill. 

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

• Block Code:  Source Block of the Loads
• Destination:  Destination of the Loads
• 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
• Net Weight:  Net (Gross less Tare) load weight
• Beware:  if you have not set up sufficient information for the system to be able to determine the revenue rate that is applicable for this load (for example, you did not set up a rate for the particular block/destination combination), this column will show a "Not Paid" entry for the ticket, and the remaining columns will be blank.
• Activity:  Activity for which revenue was received
• Pay Weight:  Pay units used for determining revenue owing for the ticket.  May be true weight measures like tonnes or tons, but may be a volume measure like cubic meters, thousand board feet or cords.  For "Method 1" users (i.e., primarily mostly Canadian users), this pay weight will be determined during the invoice calculator process based on the revenue rate (and rate basis information) you set up in the system.  For "Method 2" users (i.e., primarily US users), this pay weight will be the pay weight entered in the Data Entry | Load Slips | Load Revenue window.
• Pay Rate:  Rate payable to you (i.e., the revenue rate the mill pays you).    For "Method 1" users, this rate will be the revenue rate determined during the invoice calculator process based on the revenue rate (and rate basis information) you set up in the system.  For "Method 2" users, this rate will be the rate entered in the Data Entry | Load Slips | Load Revenue window.
• Revenue:  Amount Received from the mill.  For "Method 1" users, this revenue will be calculated during the invoice calculator process.  For "Method 2" users, this rate will be the rate entered in the Data Entry | Load Slips | Load Revenue window.

• 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.
• The load counts in the summary and detail version make use of the "load count" field on the load slip to determine the how the load count for each entry.  For example, if you enter a ticket as two separate records with a load count of 0.5 on each, this report will show a total load count of 1.

Example Report 1 shows the detailed version of the report.  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.   Note that load where revenue is missing (not received) are shown as "Not Paid" -- see lines 18, 19, 21 and 22.

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 1

Example Report 2 shows the report where the "Summary Data Only" option has been selected.  In this example, each block/destination only has a total for deliveries and revenue; all the load-by-load detail is suppressed.

Example Report 2