This article covers what comes out of the box with your ComputerEase STAC Connector for payroll data mapping.
Payroll Import Data Mapping Chart
ComputerEase Field | Field Description | ServiceTrade Data Mapping | Labor Item Export | Clock Event Export |
<emp> * | Code that represents your employee. | user_computerease_id | Productized | Productized |
<type> * |
|
|
Productized | Custom |
<otmult> |
Used only in conjunction with types 2 (Overtime) & 3 (Double) above |
From your business rules. Note: If not provided, overtime will be 1.5x and double will be 2x |
Productized | Productized |
<class> | Employee work class/ |
From your business rules. Single entity mapping. |
Productized | Productized |
<job> | Job code | Custom | Custom | |
<phase> | Phase code (if applicable) | Custom | Custom | |
<cat> | Category code (if applicable) |
|
Custom | Custom |
<department> | Department code; employee expense accounts for payroll will come from the department. |
From your business rules. If not provided, will be empty. Single entity mapping |
Productized | Productized |
<worktype> |
Referred to as "work location"
|
Single entity mapping | Productized | Productized |
<unionloc> | Local of the union the employee is working in (if union employee.) | parsed from user_computerease_id (Ex. "CEEMPNUMBER|UNIONINFO") | Custom | Custom |
<billat> | Hourly rate at which to bill work for T&M work. |
|
Not Supported | Not Supported |
<hours> * | Hours worked. | From the labor job item quantity or the clock event duration. | Productized | Productized |
<rate> | Hourly rate. |
|
Not Supported | Not Supported |
<amount> | Total dollar amount earned for record; used only in conjunction with types 7 (Other), 8 (NonTax) and 9 (Bonus) | Not Supported | Not Supported | |
<date> | Date work was performed. | From the labor job item used on date or the clock event date. | Productized | Productized |
<des1> | Description of work done. | Single entity mapping | Productized | Productized |
<des2> | Description of work done. | Single entity mapping | Productized | Productized |
<wcomp1> | Workers' compensation code. | Not Supported | Not Supported | |
<wcomp2> | Secondary workers' compensation code (gen liability) | Not Supported | Not Supported | |
<state> | State where work was performed. | From the job’s location record in ServiceTrade. | Productized | Productized |
<local> | Local taxing authority where work was performed. | Single entity mapping | Custom | Custom |
<units> | Units completed during the entry. | Not Supported | Not Supported | |
<costtype> | Used only in conjunction with types 7 (Other) or 8 (NonTax) and in conjunction with a job/phase/category; default cost types in ComputerEase are 1-6 but can be 1-16. | Not Supported | Not Supported | |
<costcode> | This is the same as job, phase and category above with the exception that they are all together in one field. | Custom | Custom | |
<equipnum> | Code for the equipment used during this entry. | Not Supported | Not Supported | |
<equipcode> | Cost/revenue code used for this cost code. | Not Supported | Not Supported | |
<equiporder> | Equipment work order number. | Not Supported | Not Supported | |
<equiphours> | Hours the equipment was used. | Not Supported | Not Supported | |
<equipdes> | Description to go with equipment entry. | Not Supported | Not Supported | |
<equipdate> | Date equipment was used. | Not Supported | Not Supported | |
<account> | GL expense account only if type is 7 (Other) or 8 (NonTax); otherwise GL expense account defaults from the department. | From your business rules. If not provided, will default from the department. | Productized | Productized |
<starttime> | hh:mm or hhmm | Not Supported | Not Supported | |
<endtime> | hh:mm or hhmm | Not Supported | Not Supported | |
<workticket> | Service Management work ticket | Not Supported | Not Supported |
Note: Any fields not listed here are currently not supported via the standard Connector. Please inquire with your Account Manager about customization needs so that we can determine whether your request is feasible.
Glossary
- Single Entity Mapping: We can tie this to a single ServiceTrade data point.
- Double Entity Mapping: We can determine this value based on up to two ServiceTrade data points.
- Productized: Included in the base price of the services estimate and subscription fee.
- Custom: Will impact time and materials fees for implementation services.
- Not Supported: Not productized and not available for customization at this time.
Comments
0 comments
Please sign in to leave a comment.