Pay: Contractors, by Load Attributes, Non-Trucking, Single Contractor
Contractors can be paid according to the weight or volume of the loads that
your company delivers to a mill. For example you might pay a contractor $10.00/Tonne
or $40.00/MBF on the loads that you handle. You can also pay a contractor a
percentage of the revenue you receive from a mill. For example, if you are
paid by the mill $50 for harvesting, you could set up a contract to pay a
contractor 20 percent of that amount. This type of contract may be useful
when you have a large number of rate breaks on your revenue contract and merely
want to pay your contractors a percentage of what you get paid. If you had
to set up contractor pay rates for each revenue rate break, there could be substantial time wasted in maintaining
both a revenue and pay rate schedule. The alternative
of setting up just one rate (say 20 percent) can be much easier to maintain as
it automatically takes into account any revenue rate breaks or changes over
time.
If you only use single contractors to perform any given activity -- for
example you only use one contractor for felling or only one contractor for
skidding (possibly the same contractor, but it need not be) for all the loads from
a given block,
The Logger's
Edge has a simplified setup. The
major simplification is that if you have multiple contractors performing an
activity, you must specify the worker and/or equipment on every load ticket in
order to distinguish which contractor should be paid. If you only have one
contractor, you can avoid this step, saving substantial data entry time.
In your block setup (see below), you select 'Do Not Track Activities,
Employees, Equipment on Load Slips'. This selection eliminates the need to
track contractors on a load-by-load basis.

In the screen above, delimbing, felling, and loading are all checked, meaning
that I want to pay each of those three activities (on the block) on a load
attribute (not hourly) basis. Also, for each of the three activities, I
have only one contractor performing the activity. This setup tells
The Logger's
Edge that I want to pay a specific
contractor for a particular activity for all the loads from a given block and do not need to distinguish
between multiple contractors.
Once you have setup your block, you need to setup your pay contract for each
contractor, specifying their payment terms. As noted above, there are two basic
ways to pay contractors on a load-by-load basis: (1) pay by load attributes
(weight, volume, etc), or (2) pay as a percentage of load revenue.
These two cases are explained below.
Case I. You pay based on load attributes (weight, volume).
Steps:
- Set up the Contractor.
Select Setup | Vendors from the Main Menu
- Set up Activity. Select Setup |
Pay Activities from the Main Menu.
- Set up Activity to be Paid on
Block.
Select Setup | Blocks | Setup from the Main Menu. On the block you
must identify the activity for which a contractor will be paid. This
task must be performed for each block that has loads for which contractors
need to be paid.
- Set up Pay Contract.
Select Contracts | Payment Contracts | Contract Setup from the Main
Menu.
-
Enter
Load Slips. Select Data Entry | Load Slips | Load Data. You
do not need to enter the activities, workers or equipment on the load slip.
-
Run
Vendor (Contractor) Calculator. Select Calculators | Vendors - Full.
-
Review Vendor (Contractor) Statement. Select Reports
Vendor Statements.
Alternatively, Select Reports | Hourly | Vendors.
Case II. You pay based on percentage of load revenue.
This type of contract is special in that it its 'rate' is really
expressed as a percent of the revenue you earn on a load-by-load basis.
Thus, in order to use this type of contract, you must perform the additional
step of entering or calculating the revenue for each load (step 7 below).
- Set up the Contractor.**
Select Setup | Vendors from the Main Menu
- Set up Activity.** Select Setup |
Pay Activities from the Main Menu.
- Set up Activity to be Paid on
Block.**
Select Setup | Blocks | Setup from the Main Menu. On the block you
must identify which activity for which a contractor will be paid. This
task must be performed for each block that has loads for which contractors
need to be paid.
- Set up Pay Contract.
Select Contracts | Payment Contracts | Contract Setup from the Main
Menu.
-
Enter
Load Slips.** Select Data Entry | Load Slips | Load Data.
You do not need to enter the activities, workers or equipment on the load slip.
-
Enter Revenue on
Load Slip or Use
The Logger's
Edge to
Automatically Calculate Revenue.
In order for the 'percent of load revenue' pay contract to work, you must have
revenue entered for each load.
-
Run
Vendor (Contractor) Calculator.** Select Calculators |
Contractors - Full.
-
Review
Vendor (Contractor) Statement. Select Reports Contractor Statements.
**
Step is the same as in Case I.
Troubleshooting Common Errors:
1. "Error: PAY_CONTRACT_RATE not Set up For:
TICKET_NO = 6879 DATE_OUT = [8/3/2004 8:03:00 AM] and Activity = HARVESTING
Ticket: 6879 Detail:
Tract: 01-GREEN-1001
Destination: SS-DANVILLE
Species: MAPLE
Grade: NONE
Truck No: HL6004
Truck Type: 7C
Route: OFF"
This error occurs when a valid pay rate is not found for the a load slip for
a contractor on a load.
This message can be interpreted as:
"The is no pay rate for ticket 6879 (date out of 8/3/2004 8:03:00 AM) for the
activity HARVESTING."
In other words, you have told
The Logger's
Edge that you want to pay the activity
HARVESTING for all loads on the block, yet there is no valid pay contract for
the load ticket '6879'
Things to check when this occurs:
- Is there a pay contract setup? Do you have a pay contract set up to
pay the contractor for the specified activity (HARVESTING)?
- If there is a contract, is the 'CONTRACTOR' type set? (It should not be
Owner/Operator)
- Does the block on the pay contact match the block on the load?
- Is the Pay Date on the Load between the Start Date and End Date for the
Contract?
- Is there a valid rate in the rates grid? Does the rate have the
matching activity (HARVESTING)? Do the rate attributes (Destination,
Species, Sort, Grade, Truck, Route, etc) either match the load or are they blank
(meaning ALL). All load attributes must match or be blank. Is the effective date valid?
The effective date on the rate must precede the DATE OUT for the load.
2. "Error: No Conversion Set Up For LBS to CORD For
Block 01-GREEN-1001
Ticket: 6948 Detail:
Block: 01-GREEN-1001
Destination: IP-AUGUSTA
Species: PINE
Grade: NONE
Truck No: T'10001
Truck Type: 7A
Route: ON"
The fragment 'Ticket: 6948' refers to the ticket number. In this
example, the error occurs because a conversion factor is not found to convert 'LBS'
into 'CORD' and the matching pay contract rate for this load has a pay
basis of cords. Anytime,
The Logger's
Edge cannot convert the weight measure
on the block to the pay basis on the matching pay contract, you will receive this message. For example,
if you have set kilograms up on the block as your weight measure and want to pay
a contractor in cubic meters (M3) and you fail to set up a conversion factor, you
will receive a message such as 'No Conversion Set Up For KGS to M3'.
The fragment 'For Block 01-GREEN-1001' tells you the block that
has the problem. There are 2 conditions that give rise to this error.
1. There is no conversion set up on the block
to convert the weight on the tickets to your pay basis on your matching pay
contract. (For example, your loads may be entered in kilograms, but you
want to pay in cubic meters 'M3'.)
2. There is no 'Generic Conversion' available.
Generic conversions are those that never change under any circumstance, such as KGs to Tonnes and Lbs to Tons.
(If you think that the system is missing a generic conversion, contact a support
representative to assist you.)
If there is no conversion set up, as indicated in (1.) above, you must select option 'C' in the conversion
setup window in the block setup wizard (see below) and then manually enter your
conversion factors.

Things to check when you get a conversion error are:
- Check the block. Have you selected 'Use Block Specific Conversions'
in Conversion Setup step of the wizard?
- Check the 'Conversion Rates' grid. Is there an entry for the
'convert from' and 'convert to' columns that match what you are trying to
convert?
- If there is a matching 'convert from' and 'convert to' row, do the attributes
(e.g. destination, species, sort, grade, etc.) match those of the load?
The load attributes are included as part of the error message in order to
facilitate this comparison.
- If there is a attribute match, is the effective date correct? The
effective date must precede the 'Date Out' of the load.
The Logger's
Edge will select the rate that is the
most recent matching entry that precedes the 'Date Out' of the load.
3. "Error: Missing Load Revenue for Load= 7531 and Activity=
SKID"
The fragment 'Load= 7531' refers to the ticket number. Things to check when this occurs:
- Check to see if you have revenue on your load. You can check this on
the load slip.
This error occurs when there is no load revenue for the activity uses a
percent of load revenue contract. Check to see if the activity (SKID)
has revenue.
- Have you run the invoices calculator? If you are using
The Logger's
Edge to calculate revenue automatically,
you must run the invoices calculator to assign the revenue amounts to the
load.
- Do you have a revenue contract for the activity that matches the
activity of the pay contract (SKID)? The percent of load revenue rate
matches the revenue based on the activity.
4. The wrong rate is applied.
Things to check when this occurs:
- Are there multiple pay contracts setup for the same activity and block?
Check under Contracts | Payment Contracts | Setup from the Main Menu.
Check the attributes of the load versus those of the pay rates.
The Logger's
Edge will select the pay rate that
is a more specific match to the load. Make sure that the rate you want
applied is more specific.
- Are there multiple pay rates setup? Check under Contracts |
Payment Contracts | Setup from the Main Menu. Select the relevant pay
contract. Be sure that the pay date of the your load ticket is subsequent to
the rate you want applied. If so, is there another rate between the
date you think should apply and the date of the load ticket? If so, the
system will use that rate. The system will use the pay rate that is (1)
prior to the pay date of the your load ticket entry, and (2) the most recent of those that are prior to
the load ticket.
5. Multi-Pay Errors.
The Logger's
Edge allows you to split the payment for
the same activity between two different vendors. As a consequence, there
are occasions where the same activity (for a given ticket) will be paid twice
(or more) correctly. For most users, however, such multiple payments for
the same activity on the same load will be in error. When
The Logger's
Edge finishes a pay calculator it checks
to see if there are any multiple payments for an activity. If there are,
The Logger's
Edge reports a 'Multi-Pay Error'.
Example:
--------------------------MULTI PAY ERROR
---------------------------------------------
ERROR: MULTIPLE PAY FOR TICKET:7019, ACTIVITY: TRUCKING
Pay Date: 8/9/2004; Tract: 02-CLEAR-2102, DESTINATION IP-AUGUSTA
1) Pay Contract: 2BR - TRUCKING Paid to: 2BR; Amount: $165.78; Pay Period: [Aug
1 04 V]
2) Pay Contract: ARROW - TRUCKING Paid to: ARROW; Amount: $182.36; Pay Period:
[Aug 1 04 V]
The above error message says that the ticket '7019' has been paid twice for the
activity 'TRUCKING'. The two lines -- numbered 1) and 2) -- show each pay
contract that has been applied and the corresponding pay period with which the
payment is associated ('Aug 1 04 V' in this case). Presumably, one is the correct contract and the
other is incorrect. If both payments are correct, you don't need to do
anything. In this case, the error message serves as a harmless warning.
If you don't want to pay both contracts, you should check:
- Are there multiple pay contracts setup for the same activity and block?
Check under Contracts | Payment Contracts | Setup from the Main Menu.
Check the pay contracts listed in the error message for this ticket.
Specifically, check the attributes of the load versus those of the pay rates.
The Logger's
Edge will select the pay rate that
is a more specific match to the load. If the attributes of the good
and the bad pay contract are identical -- meaning the block,
destination, species, sort, etc. -- and the effective date is identical,
both rates will be applied. In order to avoid a multi-pay situation, make sure that the rate you want
applied is more specific. If you cannot make one or the other rate
more specific, you can change the effective date. Changing the
effective date will mean that one rate will apply for a given period of
time, and then be superseded by the rate with the more recent effective
date. Finally, if you cannot change the rate to make it more specific
or change the effective date, you should delete the offending rate
from the offending pay contract.
- Are there multiple pay rates setup for the same contract? Check under Contracts |
Payment Contracts | Setup from the Main Menu. Select the relevant pay
contract. Check the attributes of the load versus those of the pay
rates.
The Logger's
Edge will select the pay rate that
is a more specific match to the load. If the attributes of the good
and the bad pay rates are identical -- meaning the block,
destination, species, sort, etc. -- and the effective date is identical,
both rates will be applied. You probably don't want this result.
In order to avoid a multi-pay situation, make sure that the rate you want
applied is more specific. If you cannot make one or the other rate
more specific, you can change the effective date. Changing the
effective date will mean that one rate will apply for a given period of
time, and then be superseded by the rate with the more recent effective
date. Finally, if you cannot change the rate to make it more specific
or change the effective date, you should delete the offending rate.
- Does the multi-pay error for the ticket list two different pay periods
under which the load has been paid? If so, you may have edited the
date on the ticket to a different pay period after processing pay for it in
the original pay period. If that is the case, the system now has a pay
record for the old pay period and the new pay period. If the current
period's pay record is correct, you can just re-run the calculators for the
original pay period, which should clean out the offending pay record from
the original pay period.