|
Load Paid, Multi-Pay (#309)
|
|
Why:
You need a listing of loads that have been paid more than once
(accidentally) for the same load.
Focus:
Focus of Report is to provide a detailed listing, by load, of who has been
paid more than once for an activity activity. You can use this report as a
diagnostic tool to identify loads that have been paid (more than once) in error. The most
common source of multi-pay errors is overlapping pay contracts that are setup to
pay the same activity on wood delivered out of the same block. For example
you could set up a duplicate contract to pay two different vendors for loads
from the same block.
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
- The "Only Print Raw Data" option generates a report with the
report detail, but with no subtotals or totals.

Detailed Description:
The report shows all payments for each load on an activity-by-activity basis. The
columns are:
- Date: Haul date of the load
- Block Code: Source Block of the Loads
- Ticket: Load ticket number
- Load No: Internal load tracking number (unique number assigned to
each load)
- Destination: Destination of the Loads
- Net: Net (Gross less Tare) load weight
- Volume: Volume of the load. The unit of measure for the
volume is based on the unit of measure identified for the source block
when it was setup.
- Pay Activity: Activity Paid
- Contract: Contract under which activity was paid
- Payee: Who was paid
- Pay Rate: Pay rate
- Pay Weight: Pay units used for calculating payments. May be
true weight measures like tonnes or tons, but may be a volume measure like
cubic metres, thousand board feet or cords.
- Pay: Amount Paid
Multiple rows should appear for each load that has been paid more than once.
Key Notes:
- Report covers all loads
- Calculators for Employee pay and for Vendor Pay must be run in order for
payment data to appear in the report.
- One common source of multi-pay errors is when a load has been paid in
one pay period. Then the date on the load is moved to a different pay
period and paid in the new pay period. The load will appear to have
been paid in both periods -- hence a multi-pay error. The key here is
to re-run the pay calculators for the first period; this step deletes the
original payment and leaves the second (presumably correct) payment.
Report:
Example One:
Example Report 1 shows the report where the "Sort by Date/Time" has
been selected. In this example, loads are sorted by date, and then by
block for each date. In this example, there are two pay contracts
("2BR - TRUCKING" and "WK - TRUCKING") that have both paid a
set of loads for the loading ("LOAD") activity. If this
duplication is in error, you would review each contract and identify the terms
that are incorrect.
Example Report 1
Example Two:
Example Report 2 shows the report where the "Sort by Block" option
has been selected.
Example Report 2