| Item |
Release Note |
|
New switch for duplicate ticket checking |
The standard duplicate ticket prevention rule is to preclude entry of a ticket with the same ticket # + date + destination as another ticket. Some users requested that the rule be more stringent. Specifically, they wanted the ability to prevent entry of two tickets with the same ticket # + tract/block + destination. If you'd like the more stringent setting invoked, let us know. |
|
Ability to Pay Based on Steps Rates |
The system now has the ability to pay based on a set of step rates. The most common way of implementing this functionality is when paying trucks a certain rate per load for trips that are of a certain length (e.g., 40-60 miles), and another rate per load for trips that are of another length (e.g., 61-80 miles). |
|
Ability to set overtime rules by employee |
The system now allows you to set up two sets of overtime rules and to assign employees to one or the other of the two sets of rules. |
|
Ability to Delete User Defined Reports |
Users can now delete a user defined report. |
|
Block Wizard now allows decimals in distance field |
The distances grid in the block setup wizard now uses the decimals in edit data setup to determine how many decimals to show in the grid. |
|
Enhancements to Overloads Functionality |
The overload feature has now been extended to allow users to associate different fines schedules with different mills. Additional documentation is forthcoming. |
|
Vendor Statement Updates |
We have modified the vendor statement formats for users who pay by the tonne-hour (common in Canada) so that the vendor statements will show the cycle time and the tonnage, and the tonne-hour pay rate for each load. |
|
Speed Up Cut and Paste |
The copy and paste feature that allows you to edit numerous rows in the grid at a time now works much faster than earlier versions. |
|
Pay by Net Volume |
Of particular interest to users who deal in both gross and net board footage: there is now another field available on the load slip to allow you to record and pay upon a gross (or net) scale volume, in addition to the scale volume field that already existed in earlier versions. |
|
Flag for Tree/Volume versus Volume/Tree |
For Canadian users: There is now a setting that allows you to enter the trees / volume ratio for the block (instead of the standard volume / tree). The reports that, by default, show the volume / tree ratio will now show the value as trees / volume when the new setting is enabled. (The setting must be enabled by an administrator in the Basic Setup Window on the Blocks tab. The setting is called Use Tree Count per Volume.) |
|
Modified Load Value Pay Logic |
Users who pay based on a percent of load value (somewhat common for timber dealers) can now calculate the load value by using either the revenue calculated by The Logger's Edge, or the revenue entered manually during the revenue reconciliation process. |
|
Enhancements to Cull Treatment: Pay by Cull using Cull Field on Load Ticket |
This feature will be of particular interest to US users who have to track cull on each load, and deduct pay for the cull. We have modified the program so that if you are paid a positive, but lower RATE for the cull amount on the load ticket, you no longer have to enter the cull amount as a separate ticket. Instead, you can now set up the rate that is applicable to the cull amount separately from your base rate from the mill. In addition, if are not paid at all for the cull amount, but you want the cull amount to show up as a separate line item on your settlements, you should also consider using this new feature. For more information see the Cull document in the Special Features section of our web site under the Loads Section. The document is called Pay Cull at a Separate Rate. |
|
Enhancements to Revenue Reconciliation Process |
For users that use our mill settlement reconciliation process, we've enhanced the way that the load revenue window works to make it immediately visible that you have been paid an amount for a ticket that is not consistent with the amount the Logger's Edge says is owing to you. For more information on this feature, see the Special Features section of our website. There is a document called Reconcile Mill Settlements that explains the feature in more detail. |
|
GST Can Now Be Included on Production Advances |
GST is now calculated for production advances and advance collections. |
|
Negative Rate Interaction with a Minimum Pay |
Logging companies with separate, but related trucking entities often have to set up both positive and negative rates mirrored rates for trucking so as not to distort their Tract P&L reports. This positive/negative rate approach worked well except in cases where users set a minimum payment for their truckers. In earlier versions, the minimum payment was not being applied properly to the negative payment. This version now invokes absolute value logic so that the minimum works correctly on both the positive and negative rates. |
|
Fixed Problem with Right-mouse click on Block/Tract Setup |
We introduced a very handy right mouse click feature in the block/tract setup right-mouse in version 4.5.0. With this version, we corrected an obscure error in that feature. You can now right mouse click to your heart's content. |
|
Primed Database Routine Now Removes Miscellaneous Items Assigned to
Inactive Blocks/Tracts |
The database priming routine will now remove miscellaneous entries associated with blocks/tracts that you have inactivated prior to completing the priming process. |
| Item |
Release Note |
|
Advance set-up |
(1) On Demand advance. This new type of
advance is issued to a vendor and then collected in some future pay
period. The collection of the advance may be timed to some event or
completion of some activity. The collection of the advance is handled
manually and can be set for any date or amount that you choose.
(2) Production advance. This new type of advance is issued to a vendor
and then collected in the future as loads are delivered. For example you
might advance a contractor $50,000 and then collect it back at a rate of
25% of the pay he is otherwise due for loads he worked on. Another
example might be a landowner who you advance $50,000 for stumpage prior
to harvesting. You might then reduce your stumpage payments to the
landowner at a rate of 25% until the principal amount of the advance had
been collected. The Logger's Edge has an automated way of collecting
advances against contractor pay statements.
(3) 'Mid-month' advance. This existing type of advance involves making
an advance in the middle of the month to a contractor for work already
performed. For example, you might advance a contractor 80 percent of the
pay he would be otherwise due at the 15th of the month. At the end of
the month, you would calculate his entire pay for the whole month and
then remit to him that amount less the amount advanced on the 15th. |
|
Construction - Bid Module |
Logger's Edge has a new Module available for Construction
Work. Previously construction work could be tracked in Logger's Edge
using Time/Material based revenue contracts. The Logger's Edge allows
you now to set up a job that is a construction project, prepare an
estimate and budget for the job, and then track your time and materials
in performing the job. You can also prepare invoices for the customer
for whom you are doing the work. Contact a Caribou Representative for
information on activating this module. |
|
Vendor Statement Configurability |
With Version 4.5, the employee and vendor statements that
are prepared by The Logger's Edge can be configured to meet the majority
of your business needs. You can dictate how load-based, hourly-based,
production-slip-based, and miscellaneous payments appear on your
statements. The load-based settings apply to both the grid view of the
statements, and the crystal report view. The other configuration
settings (hourly, production-slip-based, and miscellaneous) only apply
to the grid view of the statements.
Generally, a Caribou support representative will be involved to help you
with the configuration process.
For each of the three basic types of statements: (1) Employees, (2)
Vendors, and (3) Invoices, you can select the data items that will
appear on your statement, the order in which they will appear and any
sub-totals (both in the grid view, and to some degree in the crystal
reports as well).
For each basic type of statements (employee, vendor, invoices), you can
have multiple formats. For example, within the vendor statement type,
you may want to have a statement format for your loggers, one for your
landowners, and one for everyone else. |
|
Display Dist-Wt payments on statements |
There is a new section in the statements for loads paid
by distance weight. This can be activated by your Caribou
representative. |
|
Right mouse click support for blocks, pay contracts,
revenue contracts |
When in the Block(tract), Payment Contract or Revenue
Contract grid you can now right click on the row number of the contract
or block(tract) and get a pop menu that will allow for direct editing of
rates, distances, and conversions. This will allow editing without
having to go through the wizard. |
|
1099 Report |
We now have a report that contains the required
information for filling out a "1099'. |
|
Updates to the User defined Reports |
The user defined report utility now has a column that
allows you to suppress totals for items that are being grouped. This
will eliminate some of the redundancy in the totals that can be seen in
the user defined reports. |
|
User Defined Reports to allow calculations on groups |
The user defined report functionality has been modified
to allow calculations on a group. Please refer to the User defined
Report document for details. |
|
Pay minimum based on Distance |
A distance threshold field has been added to the arte
table for distance-weight rates. If the load distance is under the
distance threshold the minimum amount is paid but if the load is equal
to or greater then the distance threshold the amount is determined by
the rate times the distance. Also if you have the Distance Threshold
Field enabled on the rate table a warning is issued if the load has a
distance of 0.0. The system will still calculate pay as the Pay Minimum
amount. |
|
Ad Hoc Statements |
For users who make use of ad hoc statements we have added
some new functionality:
1. For Ad-Hoc statements that overlap another Ad-Hoc statement: when
viewing in the grid records that are on another Ad-Hoc Statement that is
not posted will show up in Pink. This means that the records are being
""stolen"" from another statement and will no longer show up on the
original statement.
2. For those who have posting enabled: when a statement is generated
that has previously posted records, these records will appear green and
WILL NOT be included in the printed statement.
3. For records that have been previously posted and unposted they may
appear orange on subsequent statements. Records that appear orange have
been posted on a statement, then appeared green on another statement,
then were unposted from the original statement. It should be noted that
the ""orange"" scenario would rarely occur. |
|
Correct Date Outs Prior to Date Ins Upon Load Import |
A warning is now displayed if the system imports a load
that has a date&time out which is prior to the date&time in. |
|
Load Count Field Usage |
The load count field on the load ticket
is now used in the reports. |
|
Log Inventory Module |
In the Cutting Edge and Logger's Edge there is a special
feature to manage your log inventory in a sort yard or log yard. The
Inventory function allows you to add to your inventory based on the
loads delivered to a destination, deplete your inventory based on loads
delivered to another destination (or volume consumed by a mill), and
close your inventory based on a certain closing date. |
|
Revenue activity code to be used for % LD revenue
payments |
Logger's Edge can now pay on a % Load basis for an
activity (such as trucking) that differs from the activity associated
with the revenue received (such as harvesting). This feature is
especially useful for users who pay truckers a % of the overall
harvesting rate they receive from the mill. |
|
Make Month Start a Basic Setup Item for Overtime Rules |
For the monthly overtime threshold rules the user
(in Basic Setup and System Configuration) can now set the day that the
month will start - e.g. entering a 3 will mean a month runs from January
3rd to February 2nd. |
|
Requested change to hourly employee statement for tree
counts |
The total earnings on the Hourly employee statement will
now include earnings for both Tree counts and hourly work. Contact a
Caribou Representative to enable this report. |
|
Disable date warnings setting in Basic Setup |
There is now a setting 'Disable Date
Warnings' in the system configuration that allows users to turn off date
checking on saving loads, time details, etc.. |
|
Add Non-Work Time as setting equip to NONE on Time Slip |
In the Multiple Activity Time slip ,
Logger's Edge has been changed it so that if you enter a type of time
that is 'NON WORK' (personal time, vacation, et al) the Equipment will
now Default to NONE. |
|
Add WCB number to Vendor Statement |
There is now an available column on the
vendors table that is called WCB_NUMBER. When this column is enabled (it
is not enabled by default), you can enter the vendor's WCB number and it
will appear on the generic vendor statement. |
|
Limit ticket entry based on tract setup |
There is now some error checking when saving a load slip.
This is to catch some errors before the calculators. A load slip save is
prevented if you save a load with attributes that are not set up in the
Cruise for the Block. This is controlled by a new basic setup item. |
|
Hourly Rate on the time slips |
You can have the hourly rate appear on the timeslips. It
is activated with a basic setup item |
|
Problems with time import - children not attached to
parents |
For users of the multiple activity timesheet when an
export/import of timesheets is done the multiple activities are now
exported and imported. |
|
User Defined Reports to allow calculations on groups |
The user defined report functionality has been modified
to allow calculations on a group. Please refer to the User defined
Report document for details. |
|
Add the Job Code to the Equipment Slips |
The Job Code field can now be added to the equipment
slips |
|
Pay by Chargeable Hours |
There is a new column on Time Details, Time Details
Equipment & Time Details Contractors called 'CHARGEABLE_HOURS'. When
this column is enabled, your invoice calculator will determine revenue
based on chargeable hours (not actual hours). This is only used for
Invoices. This would be used when you want to bill your customer a
different amount of time that what was actually worked. |
|
Truck Mileage entry allow 0 on odometer readings |
The start and end odometer reading can now be left at
zero and a mileage directly entered into Logger's Edge. There is a
toggle that allows this to apply to all trucks. |
|
Benefits and Percentage payments |
Benefit payments can now be proportioned by the
percentage to pay out on the load ticket. For example if you had a load
where you had split the bunching payment 40/60 between two contractors,
Logger's Edge will now proportion the benefit payment 40/60 as well. |
|
Payroll Item on Misc Expenses |
Employee misc. items can now be related to a payroll
item. The payroll item column determines if the misc. item is a payroll
(BONUS) or if it was a reimbursement (Meals, Travel, ext). Payroll items
and non payroll items will be included in different sections of the
employees statement. |
|
Enabled posting on the grids |
The posting function is now done in the grid as opposed
to the statement. |
|
Leave valid Rev Contract if Block Changes |
When changing a block reference in time entry and
production entry the revenue contract would be wiped out even though it
was an applicable contract. Now when a block reference is changed the
revenue contract will remain the same if it is an applicable contract. |
| Item |
Release Note |
|
New Pay Statement
Reports |
The
Reporter now contains a new submenu item under the Statements menu item
called Pay Reporting. This new feature allows users to run reports on
vendor pay, employee pay, or revenue over any date range (not simply by
pay period). Users have the option of selecting one or more
blocks/tracts, one or more destinations, one or more vendors, and one or
more activities. These reports are useful, for example, for showing how
much money a particular vendor or employee has been paid over the course
of the year for a particular activity. |
|
Ad Hoc Pay
Calculators |
This feature allows
users to calculate retroactive payments to contractors or employees for
loads delivered in prior periods. These retroactive payments need
to appear on the current period's statement. This feature is useful for
passing on fuel adjustments or retroactive rate changes related to prior
loads, but to issue the payment in the current period. This feature can
be enabled for an additional $550. |
|
IFTA Module
|
This
feature is useful for companies operating their own trucks in multiple
states and/or provinces. The feature allows users to enter fuel
purchases and mileage by state/province, and to generate a report
containing the information needed for inclusion on the IFTA quarterly
fuel tax filing. This feature can be enabled for an additional $250. |
|
User Defined Reports -
Print Date Range Selection on Report |
User-defined reports
now include the date selection criteria at the bottom of the report. |
|
Basic Setup Changes Now
Do Not Require a Program Restart |
The program no longer
needs to be restarted for basic setup changes to take effect. |
|
Make the User Defined
Report Title use the Report Name |
User-defined reports
now use the Report Name in the Header Title.
|
|
Make SQL Back-ups
Work for Terminal Services |
For clients using SQL
databases (rather than Access), back-ups can now be performed through
the software while logged on using Terminal Services. |
|
Update the Distance
Field in Similar Fashion to Volume Field |
When you add or edit
distances for destinations on a block/tract, the wizard will prompt you
(upon save of the block/tract) to update the load tickets relating to
the block / destination combinations with the newly input distance.
(Users who use this
feature should get in the habit of setting up distances for all
destinations to which they deliver, even if they need to set the
distance to 0 until they receive the actual information. Otherwise,
upon save of the block/tract wizard, the system will present a warning
message for each ticket whose destination does not have any entry in the
distances grid.) |
|
Georgia Timber Tax
Report |
There is a new report
now available for Georgia users to automate the tabulations required for
the Georgia Timber Tax Report. If you are interested in having this
feature enabled (for an additional $250), please contact a Caribou
Support representative. |
|
Load Revenue Tab
Added to Load Slip Grid |
This feature will be
particularly valuable to users who key their revenue information on a
load-by-load basis upon receipt of settlements from the mill. You can
now use the load slip grid and its corresponding filtering capabilities
to speed the data entry. For example, you can set the date range to
dates that correspond to your mill settlement, you can use the new
Excel-like filter to select a specific destination, and then use the
“group by” drop-down to group tickets by species/product. |
|
Add Volume Per Hour on
Reports 104 -110 |
These reports are particularly useful for users that track Tree Counts
on their time slips. This new column provides an estimate of
productivity (that is estimated volume produced per
hour harvested) where
the estimated volume is based on the tree counts and volume per tree
ratio set up on the block/tract.
The reports have also
been modified to use the full-founded equipment rates rather than the
standard equipment costing rates. |
|
Update the Ticket
Number in the Load Revenue Table when the Ticket is Changed on the Load |
The ticket number on
the load revenue window now reflects the ticket number from the load
itself when that ticket number is updated. (In earlier versions, the
ticket number displayed in the revenue window did not reflect edits.) |
|
On Vendor Statements,
Put in Truck# for “Is Pay Like Trucking” Activities. |
The
vendor statements now show the truck # for both the Trucking Activity as
well as any activities that are flagged as “Is Pay Like Trucking.” |
|
Block Production
Versus Budget Report (#147) |
This feature is
relevant for Canadian users. The system now has the ability to add
hourly equipment rates on a block-by-block basis for use in conjunction
with this report. This report allows users to monitor your production
progress for a block on a phase-by-phase basis relative to your
productivity targets. |
|
Block Equipment
Performance Against Budget |
This
report is relevant for Canadian users. The report is a complement to
report #147, but includes costing information so that you can compare
your actual machine hours and costs within a block by phase with your
targeted (budgeted) performance. |
|
Make Hourly Rate Display on the Time Slips an Optional Feature |
Users now have the
ability to control whether the hourly rate payable in connection with
the time slip is displayed in the time slip window or not. (Some users
like it hidden from the data entry window for confidentiality reasons,
while others like it enabled as a double-check of their data entry.)
|
| Item |
Release Note |
1. Add Pay Tab to load slip with pay
record & statement #
|
There is a new tab on the loadslip window that will show
all payments issued in connection with that specific ticket.
|
2. Ability to handle light loads
|
The system now allows users to set up minimum weights
for each truck, and to flag certain destinations as paying based on the
minimum thresholds for loads that weigh less than the minimum. The
system will then use the topped up weight as the pay basis for those
destinations. Note: if you import your load tickets, you can simply
import the top up weight from the mill, and then use that value for
payment and revenue calculations. |
| 3. Load Grid can now be filtered on
Pay Date (new checkbox) |
Users now have the option of calling up load tickets in
the ticket window grid listing based on either date out or date for pay. |
4. New Filter on Load Ticket &
Other Windows
|
There is a new Excel-like Auto Filter on all split-view
windows, including the load ticket window and time ticket windows. This
filter is great for limiting a list of entries based on one or more
attributes that appear in the columns of the grid. To invoke the filter,
simply click on the new button with a down-arrow in the top left corner
of any grid. That button will place an extra row in the grid. The extra
row will have drop-downs for each column showing a distinct list of
entries for that column. You can select a particular entry in the
drop-down list to filter your list of data to just those rows that have
the selected attribute.
To hide the auto-filter and restore your data to the full list view,
simply click again on the new drop-down button in the top left corner of
the grid window. That should remove the filter row from the grid. |
5. Priming (creating new database) based on active blocks
|
When a user creates a new database for the new
season/year (that is, when they create a primed database), they are now
able to carry forward transaction information for certain blocks that
were not completed in the prior year. To do so, the user should
deactivate all blocks in the current database that they do NOT want
ported forward. They should then run the File | Database Operations |
Create Primed Database routine. This action will create a copy of the
current database for the new year, clean out all transactional
information (time sheets, load slips, payments, etc) associated with the
deactivated blocks, but will retain the transactions associated with the
active blocks.
One the priming is complete, the user will most likely want to switch
back to last year's database, and reactivate the blocks so that they can
still do historic reporting in last year's database.
In the new database, the user is free to reactivate all blocks and
delete those that they no longer wish to retain.
Warning to user: all calculators must be current/up to date BEFORE you
begin the priming process. Calculators should not be run in the new
database because overtime calculations may be incomplete if worker time
in a given period was spent on a block that was not carried forward, and
one that was. |
| 6. Improve speed of grid loading
for large rate grids |
The rate grids available in the wizard (revenue rate
grids and payment rate grids) will now load much faster than in prior
versions. This performance improvement will be particularly noticeable
for users who have many, many rows in a single rate grid. |
7. Add Service Meter, Qty, and Product to Misc Expense table
|
The miscellaneous expense window (contractors) has
additional fields that can be enabled. These fields are: service meter
reading, quantity, and product. These fields are most helpful for users
that record their fuel bills, or other fluid expenses through the
Logger's Edge. They can now indicate the service meter reading when the
expense was incurred, and they can indicate the number of gallons,
litres, etc. of fuel or other fluids associated with a particular
expenditure. |
8. Ability to Copy Equipment
Costing Worksheets
|
Users can now copy a cost build-up worksheet for one
piece of equipment to another piece of equipment. There is now a combo
box in the cost build-up worksheet itself that allows the user to copy
the contents of the worksheet to the newly selected unit. |
9. Send Caribou your Database via
FTP
|
There is now a new menu item available for use by users
with an Access database to post their database directly to our ftp site.
The menu item is File | Database Operations | Send Database to Caribou
(FTP). |
| 10. Add "search by ticket number" to
load revenue entry window |
There is now a ticket look-up box in the revenue entry
window (Data Entry | Loadslips | Load Revenue). |
| 11. Miscellaneous imports from Excel |
There is a new menu item to allow users to import
miscellaneous expenses from Excel. This feature is great for users who
can download their fuel bills from the Internet and then import into the
Logger's Edge or Trucker's Edge for reporting. It is also good for users
who want to export their parts and repair bills from their accounting
system and import into the Logger's Edge (or Trucker's Edge) for
equipment operating expense reporting. |
12. Address Reloading of Loads grid
on a Cancel of a ticket
|
If you bring up a list of loads, and have filtered that
list by the block/tract or by one of the group by items on the left part
of the load ticket window, the system will remember that selection as
you edit tickets in the list. (Earlier versions would re-load the whole
grid based on the date range selection.) |
| 13. Put Miscellaneous Expenses on
Vendor Statement based on Appropriate Customer Pay Period |
For users using the special customer pay periods
functionality, miscellaneous entries will now attach themselves to the
specific customer period statement based on the customer on the revenue
contract to which you assign the miscellaneous entry. |
14. In Hourly statements, add
Miscellaneous Amounts for Contractors
|
The contractor hourly pay statment found under Reports |
Hourly | Contractors will now show miscellaneous entries made if the
contract worker is the only employee of the subcontractor - i.e. he is
self-employed.
If the worker works for a company with more than one employee, the
miscellaneous entries will not be shown on this report. (They will,
however, still be shown in the traditional vendor statement: Reports |
Vendor Statements.) |
15. Allow use of form for add/edit
in contractor misc window (as well as grid edit)
|
There is now a setting in the software to allow use of
an entry form for miscellaneous contractor expense entries, rather than
using the grid entry window. (Much like the existing load slip window,
miscellaneous entries can still be edited and reviewed in the grid, but
the add form allows for speedy save/add for users making numerous
entries. Contact a Caribou support representative if you'd like your
setting changed. |
| 16. Modified time slip save routine
so that users who cost trucks on a load basis (rather than an hourly
basis) cannot save time slips for non-trucking productive activities. |
The system now prevents saving a time slip where you
have entered a non-trucking, productive activity for a company-owned
truck, but your truck costing is based on Loads. If you need to enter
hours for activities other than log hauling performed by a truck (such
as lowbedding), you are advised to set up a piece of Equipment (not a
Truck) that represents this Truck and enter the hours for that alternate
piece of equipment. Note: this change was made so that the block
costing reports would not omit the costs associated with such hours. |
17. Autofill Distances if edits made
in the Load Slip GRID
|
The software will now update the distance field when a
ticket is edited in the load ticket grid. (In earlier versions, the
distance field would only update if the edit was made in the actual
ticket entry window itself.) |
| 18. Make columns in revenue & payment
contract rate grids correspond to fields on load slip |
The revenue and pay contract rate grids in the rate
setup wizards will now only show those load ticket attributes that are
enabled on the load slip itself. |
| |
|
| |
|
| |
|
| |
|
|
New Reports and Changes to Existing Reports |
| 1. Truck Deliveries Report -
Include Averages |
The Truck Delivery report now include average weights by
truck (report #601). |
| 2. Truck Load Revenue Report - Handle IS_PAY_LIKE_TRUCKING revenue |
The truck load revenue report now includes revenue not
only from the Trucking activity, but also from any other activity that
is checked as Is Pay Like Trucking under the Setup | Pay Activities menu
item.
|
3. New Report - Truck Statistics
|
There is a new truck statistics report that shows the
number of loads per day by truck, the average weight per load for the
truck, the average amount by which it falls short of its maximium
allowable weight, its total revenue, and its revenue per hour, based on
cycle times set up in the system. (#616.) |
4. New Report - Operating Costs by
Account
|
There is a new report called Equipment Operating Expense
by Account, which will allow you to view all expenses for a particular
account that you set up under Setup | Accounting | Account Codes. By
using account codes to categorize expenses into groups (e.g., fuel,
parts, tires, etc), you can use this report to see how much you are
spending in a particular category, and to what equipment unit those
expenses are connected. |
5. Add Service Meter to Truck &
Equip Operating Cost reports
|
The Equipment Operating Cost report (#503) and the Truck
Operacting Cost report (#605) will now show the service meter reading if
it is enabled on either the time slip and/or the Miscellaneous Expense
window. (The service meter field is a new field on the Miscellaneous
Expense table, as of Version 4.4.12.) |
6. New Report: Block/Sale/Tract
Statistics Report #144
|
We have added a new report called the Block (or
Tract/Sale) Statistics report (#144). It provides a nice snapshot of
activity on the block/tract/sale. It should be useful for all users, but
will be especially useful for those users who use different units of
measure to track deliveries from the same origin (e.g., mbf to some
mills and tons/tonnes to others). Specifically, the report shows:
- Total and average volume delivered to each destination, broken down by
type of wood.
- Total # of production days on the block (which is defined as the
number of days where the activity flagged as the Production Indicator
(under Setup | Pay Activities) appears on a time slip or a production
slip.
- Total # of days worked by each piece of equipment on the
block/sale/tract. |
7. New Report - Truck Operating
Cost by Account (#619)
|
There is a new report called Truck Operating Expense by
Account, which will allow you to view all expenses for a particular
account that you set up under Setup | Accounting | Account Codes. By
using account codes to categorize expenses into groups (e.g., fuel,
parts, tires, etc), you can use this report to see how much you are
spending in a particular category, and to what truck those expenses are
connected. |
| Item |
Release Note |
Issue # |
|
GENERAL FUNCTIONALITY |
| Add new table for ""Hi-Level
Phases"" - and new column in pay activity table |
We have added the ability to group Pay Activities into
higher-level activity groups, and have made use of these groups in
certain of our business reports to make the total costs for a particular
phase easier to track. For example, if you have both mechanical bunching
and hand falling occurring in the same block, you can set up a Pay
Activity for each, but relate each of them to a single high-level phase
called ""FALLING."" Certain of the key reports that show phase-by-phase
hours and costs will then provide totals per high-level phase (e.g.,
FALLING), with sub-totals for the individual pay activities (e.g.,
mechanical bunching versus hand falling).
You can set up your high-level phases under the menu item Setup |
Activity Groups. Once you've set up the groups here, you can then go to
your Pay Activity setup list (under Setup | Pay Activities), and set the
Activity Group Code accordingly. (The Activity Group Code will be set to
NONE by default. You may leave the value equal to NONE if you do not
choose to make use of the grouping feature.)
The following reports make use of these new high-level activity groups:
1. Report 102 - Activity Costs, Summary, By Actual Volume
2. Report 118 - Summary, by Activity, Full Founded Cost
3. Report 131 - Block, Profit by Activity *
4. Report 134 - Block Hourly Cost *
5. Report 133 - Block Hourly Equipment Cost |
7263 |
| Is Pay Like Trucking Flag to
Handle Trucking Fuel Surcharges |
We have added the ability to pay phases other than
trucking to the truck owner or truck driver on the load slip. This
feature allows contractors to pass on a fuel adjustment per-tonne (or
per m3) payment received from the mill to a contract trucker. There is a
new flag on the pay activities table called IS_PAY_LIKE_TRUCKING. If
you'd like this field enabled, contact a Caribou representative. |
7604 |
| New "Recalc" Pay Button in
Load Slip Window |
We have added a button on the load slip window that will
allow you to re-calculate payment and revenue on the load slip
immediately. This feature is particularly useful if you make a simple
correction to a few tickets and want the payment for them corrected
without re-running the full calculators. |
7134 |
| Add equipment to pay contract
grid & hourly worker rate grid - different rates for same contractor for
diff equipment. |
We can now enable a column for equipment on the pay
contracts grid so that you can pay different rates to a given contractor
who owns multiple pieces of equipment, where the rate depends on the
piece of equipment. Call a customer support representative if you'd like
this column added.
This new feature also allows a user to set up a rate differential for an
operator (employee or contract worker) in the Worker Activity Rates grid
that is based on the equipment that the operator is running. |
6665 |
| Revised window for doing Truck
Costing & Equipment Costing |
We have added entirely new cost build-up worksheets for
use in building up to equipment and truck costs. Existing users who
would like to make use of the new and much-improved costing worksheets
should contact a Caribou support representative. We have made the new
worksheets the standard for all new users. |
7038 |
| Improve the way equipment
costing & utilization reporting works |
We have modified the logic for equipment costing so that
equipment time is costed only for productive hours. Earlier versions of
the program costed all equipment time EXCEPT maintenance time, whether
it was productive time or non-productive time. We have changed the logic
based on client feedback so that only PRODUCTIVE equipment hours are
costed. The idea behind this change is that your standard and full-found
equipment cost have a certain amount of down time assumed in the rate.
Thus, the equipment down time (i.e., non-productive time) should not be
costed explicitly. (The operator down time will, however, continue to be
costed, just as it is costed for maintenance time.)
The system determines whether hours are productive or not based on the
Pay Activity Type of the Pay Activity on the time slip. Most users are
currently configured so that only the Pay Activity Type = 'REG PROD' is
flagged as productive time. Our recommendation is that the pay activity
type of 'NON PROD CHARGE' also be set to be productive time. You can
check your configuration by going to the menu item Setup | Pay Activity
Types. The column ""Production Time"" is checked for all pay activity
types that you currently have set to be treated as productive time.
Contact a Caribou support representative if you'd like to have your
production time settings modified.
Notes:
1. This new logic applies to truck costing as well IF you cost trucks on
an hourly basis.
2. The equipment utilization report has also been modified so that
"production hours" are all hours for those pay activity types where the
""Production Time" checkbox is set to true (checked). |
7662 |
| Update Statement Details or
Employee Details upon Miscellaneous Entry or Edit or Deletion |
When users make miscellaneous expense entries (under the
menu item Data Entry | Expenses), the user is no longer required to
rerun the calculators for the amounts to appear on the statements or on
the equipment/truck operating cost reports. |
7366 |
| New "Load Count" field enabled
on the load slip. |
There is now a new field on the load slip window that is
set to 1 by default. This field is currently used in the employee and
vendor statements to provide the load counts on the statements. We added
it to handle circumstances where users enter multiple tickets for a
single physical load (e.g. to handle weights and attributes of two bunks
on the truck). When users enter split tickets, they can now change the
load count from 1 to a value less than 1 (e.g., 0.5) so that when the
tickets are displayed on the vendor statement, the multiple rows
representing a single physical ticket will sum to 1 load.
This field is also useful if a user is creating a reversing ticket and a
new correcting ticket to correct a ticket error. By setting the
reversing ticket to -1 and the correcting ticket to 1, the three tickets
taken together (original, reversing, correcting) will sum to 1 load.
We have not made use of this new field in any reports other than the
vendor statements. If you have a particular interest in having this
field used in an existing report, please contact us to let us know. |
7423 |
| Add New Generic Fields to
Vendor Setup Grid |
We have added additional informational fields to the
Vendors table. These fields were added in response to user requests for
the ability to store WCB # and WCB Clearance Ltr Information. Contact a
Caribou Support Representative if you'd like to have these fields
enabled. |
6280 |
| Look at driver defaults when
importing loads |
When importing loads, the system will now check to see
if there is a default driver associated with the truck on the load slip.
If there is, the system will set the driver on the load slip to the
default driver UNLESS there is a driver in the import file itself (in
which case, the system will import the actual data rather than relying
on defaults). |
6774 |
| Add ability to flag a load as
NOT an overload - useful for clean-up loads |
We can now add a flag to the load slip so that the user
can tell the system NOT to treat a load as an overload, regardless of
its weight. This field is especially useful for flagging a load as a
clean-up load (a heavy load) so that it will be excluded from any
overload calculations. Contact a Caribou support representative if you'd
like this field enabled. |
6790 |
| Data Entry Validation of Dates
Using From/To Filters on Entry Windows |
In earlier versions of the system, users found it easy
to accidentally enter load slips, time slips, or miscellaneous expenses
with an incorrect rate. To help users catch such key entry errors, we
now compare the date on the entry (load slip, time slip, or
miscellaneous expense) with the ""From"" and ""To"" dates selected on
the viewing grid for load slips, time slips, and miscellaneous expenses
respectively. If the date on the entry is outside the From/To dates on
the entry grid, the system provides a warning to the user. This
feature may be irritating for some users at first, but we do believe it
will help eliminate data entry errors for many users. |
7030 |
| Ability to pay employee by
load where employee not entered on load slip |
Earlier versions would not allow payment to an EMPLOYEE
operator (e.g., loaderman, buncher, etc.) unless the employee was
entered on the Activities tab of the load slip. With this version, we
now allow such payment.
(Earlier versions of the program allowed payment to a CONTRACTOR
without the need to enter the contractor on the Activities tab of the
load slip, on the assumption that the contractor would be paid for ALL
load slips from the block. We simply made the treatment of Employees
symmetric with that of contractors in this scenario.) |
7032 |
| Add Destination Code to Truck
Overweight Functionality |
The new version allows users to set up different truck
weight thresholds that depend upon the destination. The Destination
field is not enabled by default, so contact a Caribou support
representative if you'd like this field enabled. |
7105 |
| Store settings for Ad Hoc
Statements |
The Ad Hoc statement selections are now stored when a
statement is created. This allows the statement to be recallled (by its
number) at a later date. So, you can now 'view' and print ad hoc
statements without having to recreate a new one each time. |
7114 |
| New fields added to the load
slip |
The load slip has a new Comment field.
The load slip also has a Load Count field which is used to manage the
load counts on the employee and vendor statements (Crystal Reports
versions), and the invoices (Crystal Report versions). This field is set
to 1 by default for all loads. If you enter multiple tickets for a
single truck load (for example because the load has multiple bunks that
are weighed separately, or multiple species that are stick scaled), you
can enter values less than one in this field so that the sum of the load
counts on the ""partial tickets"" together add up to 1 load.
For example, suppose you split a ticket into 2 sub-tickets that each
have a different species. You might use a naming convention that appends
a ""-1"" and a ""-2"" to each of the sub-tickets, and then set the load
count on each ticket to ""0.5"".
|
7525 |
| Make distance on
load slip default to distance on block |
If users set up distances to each
destination from a given block/tract during the block/tract setup, this
distance will be used to auto-fill the Distance field on the load slip
during load slip entry. (The auto-filling only works in the ticket entry
window itself; it does not currently auto-fill if edits are made in the
load slip grid.)
This feature is useful for people who pay by distance, or who want to
track the distances on the load slip for use in the "Log Haul Cost, by
Distance" report. |
7583 |
| Add
IS_PAY_LIKE_VENDOR to employees. |
Some users who manage a different set of
pay periods for their employees versus their contractor needed the
flexibility to specify that certain employees (generally employee truck
drivers) be paid on the contractor schedule. To accommodate this
request, we have added a field to the employee table so that users can
flag an employee to have their load-based payment paid on a vendor pay
period.
Note: if the employee has both hourly pay and load-based payment, the
hourly pay will still be process on the employee pay period, so the
employee will get two statements: one containing load-based payment,
which follows the vendor pay cycle, and one containing hourly and
miscellaneous payment, which follows the employee pay cycle.
Contact a Caribou support representative if you'd like this feature
enabled. |
7136 |
| Expose Certain Basic Setup
Defaults to User |
We have exposed certain configuration settings to the
user through a new menu selection called ""System Configuration"" under
the ""File"" main menu item. This menu item allows users to control
certain settings without the need for a Caribou support representative
to log on as an administrator. |
7141 |
| Employee Charge-out Rate now
supports NONE wildcard for rev contract |
When users set up an employee charge-out rate
differential under the menu item ""Setup | Workers | Employee Charge-Out
Rates,"" they can now use the keyword NONE in the revenue contract
column as a wildcard. NONE in the revenue contract column tells the
system to apply the rate differential to the employee's base charge-out
rate (set up under ""Setup | Workers | Base Pay Rates""), regardless of
the revenue contract on the time slip. |
7194 |
| Add Production Activity to
Time Summary Tab on Time Slip Entry Grid View |
For users with production activity enabled on the load
slip, we have added the production information to the summary tab of the
time sheet. |
7200 |
| Progress Bar for imports |
For users who import time slips, we have added a
progress bar during import. Specifically, we added the progress bar to
the following imports:
Employee_Time, Equipment_Time, Contractor_Time, Employee_Production
Contractor_Production,
|
7225 |
| Throw warning when enters
duplicate invoice # in Misc. Entry window |
The system will now warn the user if he/she attempts to
save a miscellaneous contractor expense with an invoice number that is a
duplicate of another entry. |
7346 |
| Add functionality to do
Reverse Conversions |
This feature should only be used for those clients with
'Scaled Volume' enabled on the load slip.
This feature allows you to convert the Scale Volume field on the load
ticket into the Weight (Gross and Net) and the Volume fields. It can be
used when you are entering your volumes manually into the Scale Volume
field, but you want to estimate the weight and volume of the loads. For
example, the scale volume might be in M3, but you might want to
""reverse-calculate"" weights in KGs and the volume in Tonnes.
Similarly, the Scale volume might be MBF and you might want to
""reverse-calculate"" the weights in LBs and the volume in Tons.
|
7419 |
| Additional import to handle
import files with Pieces (rather than loads) |
We have added the ability to import log detail
information from a hand-held scaling file. The import works in a similar
manner to the load imports --- they can be configured to work with
almost any format of information, as long as the information is in a
""txt"" file. The import will group logs into summarized detail records
based on the attributes (that is, ""C Parts"") that are enabled on the
load slip in the system. |
7422 |
| Avg Trip Time by Destination
and Short Vs Long Longs |
Users can now set up average trip times on their blocks
that can vary by route and truck type, and by other attributes on the
load slip. Earlier versions of the software only allowed trip times to
be based upon the destination.
This feature is used in truck tonne-hour costing. |
7426 |
| New Overload Functionality |
We have added new overload functionality that allows
users to generate overload deductions in two new ways:
(1) create overload deductions at a certain fixed rate per unit of
weight (e.g. $012/ton or $.23/Kg) over the truck's maximum weight;
and/or
(2) create overload deductions based on a stepped schedule (e.g. $50 for
1-2000 lbs overloaded, $100 for 2001 to 4000 lbs, etc).
In the standard overload functionality, the pay weight is reduced by the
amount of the overload, thereby resulting in an effective deduction
equal to the overload weight multiplied by the otherwise effective
payment rate. There is only one entry - the net pay entry - that is
created on vendor, employee or customer statements.
The extended functionality calculates pay based on the unadjusted pay
weight - it does not reduce the
pay weight like the standard method does. Instead, this method creates a
miscellaneous entry equal to
the amount of the calculated deduction. Thus, there are two entries -
the full pay for the load and a
miscellaneous deduction - that are created under the extended
functionality. |
7429 |
| Alternative Time Slip Window |
We have made an alternative time slip window that allows
a user to enter individual records for a given day all in one screen. If
you'd like the revised time slip window enabled, contact a Caribou
Support representative. Otherwise, your existing time slip window will
continue to function as it always has. |
7474 |
| Ability to Add an Advance
under Data Entry | Advances |
We have added an Add button under the Data Entry |
Advances window so that users can add a land-owner's advance directly
through this window. You must have the Advances functionality enabled to
have this functionality. |
7511 |
| Ability to automatically
reverse & correct erroneous tickets that have already been paid |
We have added the ability to automatically reverse
tickets that are in error. A "Reverse" button can be added to the load
slip window that will create a reversing ticket (with the original
ticket number and a "-REV" appended to the end with negative weights and
volumes, and another correcting ticket (with a "-COR" appended to the
original ticket number). This ticket can then be edited to correct the
problem with the original ticket.
When payment is processed (or reports are run), the functionality has
the effect of zero-ing out the original payment and creating a
correcting payment. The reversal ticket has a The load count value for
the reversing ticket is set to -1, and the load count value for the
correcting ticket is set to 1. These load counts are used on the
statements so that the reversals and corrections do not throw off the
load counts in the system.
Historically, users have had to create the reversing and correcting
ticket manually.Contact a Caribou representative if you want this
functionality enabled. |
7054 |
| New Calendar Control in
Split-View Window. |
We make use of a new calendar control in all split view
data entry windows. (The calendar used in earlier versions did not work
properly on some machines.) |
7093 |
| Loadslips should not allow
date out > date in IN GRID VIEW |
When a user edits a load slip number in the load edit
grid, the software now checks to ensure that "Date Out" is later than
"Date In." Earlier versions checked for this relationship in the ticket
edit window, but not in the grid itself. |
6582 |
| Error when importing load slip
activities if file has ticket not in the loadslips table |
The load activities import routine now provides an error
message to the user if the activities import contains a load ticket #
that is not already in the system. Any load activities whose
corresponding ticket number is already in the system will still be
imported correctly. |
6846 |
| Correction to Primary Key
violation when multiple users entered load slips concurrently. |
We have corrected a "primary key" error that would
sometimes occur in a multi-user environment when multiple users entered
load slips simultaneously. The system should now allow multiple users to
enter load slips at the same time with no errors arising during the
saving process. |
7073 |
| |
|
|
| REPORTING
CHANGES |
| Addition of a Summary View
Checkmark to User-Defined Reports |
When you run a user-defined report, the selection
criteria window will now have a ""Summary View"" checkmark so that users
can run the report in detail or summary view. |
7268 |
| Date sort on reports instead
of text sort (in crystal) |
Dates in the crystal reports will now sort as a date
field rather than a text field. To make this change, we needed to set
the date as the first column in the statement. If you had the date
included on your statements before this upgrade, you will need to go
under the menu item File | Configure Statements, and uncheck the "Date"
checkmark on each of your statement formats. (Otherwise, you will have
two date columns on your statements.) |
6802 |
| Resize font on vendor
statements |
We have created an optional vendor statement crystal
report that is identical to the one in earlier versions, but uses 8
point rather than 10 point font. If you are interested in using this
alternative format, please contact a Caribou Support representative. |
7086 |
| New Report Showing Vol/Hr &
$/Volume by Pay Activity Group |
We have added a new report under the Block menu item
called ""Block Equipment Summary."" (Report #133). This report makes use
of the new activity groups that we've added in version 4.4 (See Issue
#7,263 for more information.) The report shows the following information
on a block-by-block basis:
1. Total hours worked by each piece of equipment, by each high-level
phase, and then by the activities within that phase.
2. Total volume harvested for the entire block, with a volume per hour
for the high-level phase.
3. Total costs associated with each of those hours, based on the
Full-Founded rate set up for each piece of equipment.
4. Total $ / volume for each high-level phase of operation.
5. Equipment available hours & utilization percentages within each
block. Note that in instances where the same piece of equipment
performed two activities, we prorated the down hours for the piece of
equipment to the 2 activities based on each activity's share of
productive hours.
|
7254 |
| |
|
|
| Summary view of Equip
Utilization Rpt |
We have added a summary checkbox to the Equipment
Utilization Report under the ""Equipment"" menu item. (Report #501).
When checked, the report will show one row for each piece of equipment
with total available hours and utilization percentages for the entire
date range of the report. |
7262 |
| Summary P&L changes |
We have enhanced the revenue reporting on the Summary
P&L report in the following ways:
1. Revenue is in now grouped into three categories: (1) Revenue from
Loads; (2) All Other Revenue except Miscellaneous Income (e.g.,
hourly-based revenue); and (3) Miscellaneous Income (e.g., Fixed Fee
Income or Miscellaneous Income associated with a Load-Based Revenue
Contract). Earlier versions of the report excluded miscellaneous income
altogether.
2. Miscellaneous income is now presented in one of two ways depending on
the Basic setup item:
GROUP_BY_MISC_ACCOUNT_FOR_REPORTS. This is the same item that governs
how miscellaneous expenses will be presented.
If GROUP_BY_MISC_ACCOUNT_FOR_REPORTS = 0, Miscellaneous Income is
presented in one line as a lump sum.
If GROUP_BY_MISC_ACCOUNT_FOR_REPORTS = 1, Miscellaneous Income is
grouped by Account Code and presented a one line for each account.
The default value for grouping is 0. If you'd like to have your
miscellaneous income (or expenses) grouped by account code, contact a
support representative to make the change for you.
|
6962 |
| New Report - Block
Profitability - especially useful for US users (Report #135) |
We have added a block profitability report that shows
one row per block and summarizes the performance of each block. It
shows the start and end dates of the reports, the total load count,
total volume, revenue, costs (split between stumpage/depletion costs and
cut-haul costs), and average gross profitability and margins for the
block. |
7107 |
| New Report - Pay Period
Production and Cost Summary (Report #136) |
We have added a new report that shows, by pay period,
the number of loads, the volume delivered, total revenue, total costs,
and average gross profit for the pay period. The report can be run in
summary form (showing total counts, volumes, and dollars by pay period),
or it can be run in detail form. The detail version allows users to look
by tract/block/job at payment and volume fluctuations from one pay
period to the next. |
7573 |
| Employee Hourly Statement
Enhancements |
In earlier versions, users could not have both the slip
number and description on the hourly employee statement. (The report
would generate an error under such circumstances.) This version supports
both those fields on the hourly employee statement. (This report is
located under the ""Reports | Hourly | Employees menu item.) |
7499 |
| Changes to Employee Hourly
Report Format |
We have made some modifications to the employee hourly
reports (found under the menu item Reports | Hourly | Employees) to help
fit more information on one page. Specifically, we:
1. Put the date printed in the footer of the report to help reduce the #
of pages that are printed.
2. Made the printing routine recognize the column resizing that a user
does in the grid prior to printing.
(Please note that we are not able to control whether the report prints
in landscape or portrait view.) |
6600 |
| Ad hoc statement summary
button - total column just repeats the tax column |
We corrected a bug in the vendor statement Summary
button for users making use of Ad Hoc Vendor Statements. Earlier
versions of the software repeated the Tax $ amount in the Total $
column, rather than summing the Pay Amount and the Tax Amount in the
Total Column. |
6772 |
| Add Holdback and Advances to
Ad Hoc Vendor Statement Grid |
Holdbacks and advances will now appear in the vendor
statement grid for users who have Ad Hoc Statements enabled. (Earlier
versions had the items appearing in the final crystal report, but not in
the grid itself.) |
7483 |
| Page break after employee in
the “Daily Detail by Employee” |
We have added a page break to this report for each new
employee. |
7347 |
| Cruise Volume Report
Modification |
The Cruise Volume report has been enhanced to show the
lump sum purchase price on a tract and to calculate the difference
between the lump sum purchase price and the total depletions. |
7594 |
| Cruise Volume Report
Modification |
The Cruise Volume report (Report #130) now includes
volumes delivered on a particular tract/block even if the particular
combination of species/product on the load was not cruised. The actual
volume for these loads will appear as extra rows in the report, with a
cruise volume of zero.
Note: this report is widely used by our US users. |
6945 |
| Ability to filter revenue
contracts when running ad hoc invoices to exclude all contracts that are
load-based. |
When running ad hoc invoices, we have added a new check
box that allows users to exclude load-based revenue from the invoice.
This checkbox (labeled ""Exclude Load-Based"") allows users to generate
an invoice for a customer that has load slip activity in the same date
range as hourly activity (or fixed fee activity) without having the load
revenue appear on the hourly (or fixed fee) invoice. As a result of
this new functionality, users no longer need to set up a demo dummy
customer when they want to create an hourly invoice for a customer to
which they also deliver loads in the same period. Instead, users now
have the choice of whether to include loads on the invoice or not.
|
7043 |
| Portait invoice, 8 pt font,
checkbox to exclude loads from invoice |
Enhancements to invoices: there is now a portrait format
available, and the font has been reduced to fit more information on one
invoice. |
7115 |
| Tree Counts not consistently
appearing on Summary P&L rpt |
We have modified the Summary P&L so that the Tree Count
value appears straight from the time slips, regardless of whether there
is a positive vol/tree ratio on the block setup window. |
7153 |
| Enhancements to Truck Load
Revenue Report |
We have added the block to the Truck Load Revenue report
selection criteria window (in addition to Truck). We have added a column
in the report for block and now subtotal by block. |
7168 |
| Add the Block Reporting Basis
(e.g., M3) to the P&L report |
The Block Summary P&L report now displays the unit of
measure of the volume column for each block that appears in the report. |
7232 |
| Truck Export Rpt (#613) |
Logger's Edge users who have trucking contractors that
use the Trucker's Edge can generate an export of the truck contractor
load slip and payment information so that the Trucker's Edge user can
import the information directly, without re-keying the information. |
7701 |
| |
|
|
| Item |
Release Note |
| 1. New invoice statement views |
There is a new menu item for invoices that allows users
to view invoices by invoice number or by customer (for multiple
periods). The new menu item is located in the main program under Reports
| Invoices | By Customer, Statement #
There is also a new button in the By Pay Period view that allows users
to switch periods from within the invoice grid window. |
| 2. Truck costing based on tonne/hour |
For Canadian users: The system now has the capability to
cost company-owned trucks based on a tonne-hour calculation. Tonne-hours
are determined for each load based on the load's tonnes multiplied by
the average turn-around-time entered for the block. This average
turn-around time can be adjusted at the end of the block with the actual
turn-around-time.
See the documentation in the Support Section of our web site, under
Special Features. |
| 3. Loads, Profitability Report changes request |
We have made modifications to the Load Slips | Loads,
Profitability report to add additional load attribute columns (species,
etc) and to provide a summary view of the report. The user can now also
select both the tract AND destination when running the report. |
| 4. Rpt: 131 - New Block P&L Report |
We have added a new block P&L report called Block,
Profit by Activity. This report provides a nice combination of the Block
P&L report and the Block Activity Cost Summary report. If users break
their revenue rates down into phases that match their harvesting phases,
this report allows you to see profit by phase. |
| 5. Getting Permission Denied error on imports |
We have fixed the Permission Denied error that some
users operating in a multi-user environment encountered when trying to
import their load slips. |
| 6. Make truck cost by
distance work |
Trucks can now be costed by Distance for those users who
enter the distance on the load slip. |
| 7. Add Activity field to miscellaneous income, employee & contractor grids |
The miscellaneous income grid, miscellaneous employee
expenses, and miscellaneous contractor expense grids (under the Data
Entry main menu item) all have a new column for Pay Activity. This
activity attribute is now used on Customer Invoices where miscellaneous
items are charged to a customer. The activity attribute is also
available now for custom reporting. |
| 8. Take indexes off vendor statement detail table and other statement
tables |
We have removed some unnecessary indexes from the vendor
statement table, which results in a notable improvement in the
performance of the pay calculators when the same pay period is run over
and over again. The removal of these indexes also reduces the frequency
with which the database must be compacted. |
| 9. Revise the multipay query to
speed up processing time |
The multipay query that runs at the end of each
calculator has been modified to reduce the length of time it takes to
run the query. |
| 10. New Ad Hoc Invoices & Fix to Old Bug That Leaves Extraneous Invoice
Header |
There is a new menu item for invoices that allows users
to generate ad hoc invoices. This new feature allows users to generate
invoices for a given customer, a specific revenue contract (or
contracts), and a specific date range. Users are no longer limited to
generating invoices for a given pay period. The user selection criteria
(including the customer, revenue contract, and date range selections)
are saved with an invoice number so that the invoice can be reprinted at
any time.
See the support section of our web site under Special Features for
additional documentation. |
| 11. Put Revenue Contract on Invoices for hourly and production slip work |
The revenue contract is now displayed on the summary
page of invoices and is the second layer of grouping for the report,
after the pay type (load slips, hourly, etc). Earlier versions of the
invoices did not include the revenue contract. |
| 12. New employee statement views (by employee, switch periods) |
There is a new menu item for employees statements which
allows users to view employee statements by statement number or by
employee (for multiple periods). The new menu items is located in the
main program under Reports | Employee Statements | By Employee,
Statement #.
There is also a new button in the By Pay Period view that allows users
to switch pay periods from within the employee statement grid window. |
| 13. New vendor statement views (by vendor, switch periods) |
There is a new menu item for vendor statements which
allows users to view vendor statements by statement number or by vendor
(for multiple periods). The new menu items is located in the main
program under Reports | Vendor Statements | By Vendor, Statement #.
There is also a new button in the By Pay Period view that allows users
to switch pay periods from within the vendor statement grid window. |
| 14. Remove Blank Ad Hoc Statements |
In earlier versions, the ad hoc vendor statements used
by some users generated a vendor statement for all selected vendors,
whether those vendors had pay records for the date range, blocks, and
destinations selected by the user. The current version only generates
pay statements for those vendors with pay records meeting the user's
selections.
|
15. Display separate line item for GST payment
vs. collection on vendor
statement
|
On the statements we now have a separate GST line item
for all amounts PAID out to a contractor, and a separate line for all
amounts COLLECTED FROM (i.e., deducted from) a contractor (such as
miscellaneous deductions).
|
16. Email to Caribou - button on the calculator error report
|
There is now an email to Caribou button on the
calculator report window so that users needing assistance
troubleshooting errors can easily send the errors in an email to
Caribou.
|
