Follow

ID219 - Closed Call Data Entry Issues Overview & Sample

95% of the new clients we take on have inaccurate data in contract profit reports, mostly due to things like a technician entering a milometer reading instead of miles. Then you have 97,000 miles showing as a cost on a contract. This alert is meant to catch where either users ignored the popup warnings for these values you setup in Tools/Options/ServiceCalls/Additional Options OR you do not have any values setup for the popup warnings.

We will alert you if an invoiced call exceeds any of the numbers you input for the corresponding values above. This alert will ignore calls that have status "Scheduled" until they are closed, at which time it will then check the sanity numbers.

You have the option to have this alert only fire for calls where the Technicians is flagged as a ZCJFieldTech using the attribute/custom property identified in Variable1 above.  (that attribute type must be Yes/No).  If you don't specify an attribute to use then the alert will fire for all techs.

This alert typically runs every 15 minutes and it's important that these are fixed before they are invoiced as you will have to void and re-bill if you wait until invoiced.

 

ScreenShot.png

You will see the invoice number if it's been invoiced otherwise it says UnInvoiced, Let us know if you are getting these too late.

 

ScreenShot.png

General information

This report helps you find data entry errors that can cause profitability to be wrong. A technician or dispatcher may fat figure an odometer reading giving you a mileage of 9,234 miles. This may not show up in your balance sheet because most people use the same account for revenue and cost so they offsite, but when you run profitability it will be hugely wrong. This alert will find errors like this. 

Example:

Active report variables:

  # of business hours for response - 10

  # of hours for Travel - 2

  # of hours for Labor - 4

  # of miles for mileage - 100

 See the Trigger Action column to understand which of the 4 variables triggered this alert.

**Please note:

Response Time = when call logged to when tech arrives

Actual Hours = actual time from arrival to completion. The difference between labor hours and actual hours is labor hours is what is billed on the service call (this can be overridden by the user or by eAuto depending on how you have your bill codes set up for incremental billing) and actual hours is the actual hours from arrival to completion. 

Actions:

Void the Call and change the data to the correct information then re-invoice. 

Please note Response Time shown comes directly from eAutomate. So if it is off, then review the Service Call to ensure tech dispatch time is correct. If it is, then make sure your Company Hours set in eAuto are correct and/or the the tech's eAuto Employee Record reflects the Service Hours he/she works.

Reason why this would not make any difference

Time:

For time to have an impact you have to have burden rate.  You really need to have a burden rate in every employee file so you are charging the time that technicians spend on site to the contract.  Otherwise all your contracts will have Zero cost for time. 

(See THIS LINK on Calculating Burden Rate.)

ScreenShot.png.jpg

Where do I find out what GL’s are being affected?

To find out where the cost of labor and payroll expense offset are done.  This is all under the Billing account cost.  You can find this in lists and codes.  If they are the same they will offset and the net GP entry is Zero.  Most companies do this.  This still allows for tracking of burden rate to the contract without creating additional work for the Accounting staff.  

ScreenShot.png

Mileage and Travel

Mileage and travel is also done in the Billing Account Code and the same rule applies if they are both offsetting each other.

ScreenShot.png

The difference is that Travel and Mileage expense are set companywide in the options settings:

We suggest to use the burden rate to travel cost and then set the per mile to your mileage reimbursement or $0.50 for company vechiles.

ScreenShot.png

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk