Difference between revisions of "Glossary"
Jump to navigation
Jump to search
Ascentadmin (talk | contribs) m |
Ascentadmin (talk | contribs) m |
||
| Line 299: | Line 299: | ||
| | | | ||
The text that will be displayed on the agreement renewal invoice. | The text that will be displayed on the agreement renewal invoice. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| <div id="AgreementRenewAs"> </div> | | <div id="AgreementRenewAs"> </div> | ||
| Line 311: | Line 306: | ||
| | | | ||
Used to indicate the type of invoice that will be created upon renewal. | Used to indicate the type of invoice that will be created upon renewal. | ||
| − | |||
| − | |||
|- | |- | ||
| <div id="AgreementRevenuesTotal"> </div> | | <div id="AgreementRevenuesTotal"> </div> | ||
| Line 320: | Line 313: | ||
| | | | ||
The total amount billed for the contract to date. | The total amount billed for the contract to date. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| <div id="AgreementSalesperson"> </div> | | <div id="AgreementSalesperson"> </div> | ||
| Line 332: | Line 320: | ||
| | | | ||
The salesperson that should be assigned to the invoices when billing occurs. | The salesperson that should be assigned to the invoices when billing occurs. | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| <div id="AgreementStatusCode"> </div> | | <div id="AgreementStatusCode"> </div> | ||
| Line 342: | Line 327: | ||
| | | | ||
The status code is used to track the agreements progress through the renewal process. | The status code is used to track the agreements progress through the renewal process. | ||
| − | + | |- | |
| − | + | | <div id="AgreementType"> </div> | |
| − | + | |- | |
| + | | Agreement Type | ||
| + | |- | ||
| + | | | ||
| + | Used to organize agreements by type. Agreement types are also used to establish setting for agreements by default. | ||
| + | |- | ||
| + | | <div id="Allocation"> </div> | ||
| + | |- | ||
| + | | Allocation | ||
| + | |- | ||
| + | | | ||
| + | Displays the allocation assigned to the selected agreement type. | ||
|- | |- | ||
| <div id="servicetype_AssignedBtn"> </div> | | <div id="servicetype_AssignedBtn"> </div> | ||
| Line 848: | Line 844: | ||
| | | | ||
Indicates the physical location. | Indicates the physical location. | ||
| + | |- | ||
| + | | <div id="Commissionable"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commissionable</div> | ||
| + | |- | ||
| + | | | ||
| + | When checked the item is commissionable. | ||
| + | |- | ||
| + | | <div id="corep_commrate"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commission Rate</div> | ||
| + | |- | ||
| + | | | ||
| + | If the representative is a salesperson, the commision rate is stored in this field. | ||
| + | |||
| + | |||
| + | |||
|- | |- | ||
| Line 854: | Line 867: | ||
| colspan="1" style="width: 1538px;" | <div class="fieldHeader"></div>Inventory: Equipment Build Checkbox</div> | | colspan="1" style="width: 1538px;" | <div class="fieldHeader"></div>Inventory: Equipment Build Checkbox</div> | ||
|- | |- | ||
| − | | When checked, an equipment record will be generated each time the item is billed. | + | | When checked, an equipment record will be generated each time the item is billed. Equipment build has a set of defaults that are defined for use during the process. |
| − | + | Prefix: Used when equipment auto-numbering is activated. | |
| + | [[Glossary#equip_type|EQ Type]] | ||
| + | Model | ||
| + | Manufacturer | ||
| + | Labor Warranty Period | ||
| + | Parts Warranty Period | ||
| + | Comment | ||
| Line 914: | Line 933: | ||
| | | | ||
The item's unit of measure. | The item's unit of measure. | ||
| + | |- | ||
| + | | <div id="MobileButton"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Inventory: Servicer Mobile Button</div> | ||
| + | |- | ||
| + | | | ||
| + | When checked, a mobile button will be made available in mobile for quick entry. | ||
|- | |- | ||
| <div id="shordesc"> </div> | | <div id="shordesc"> </div> | ||
| Line 949: | Line 975: | ||
| | | | ||
The price for the item when added to a transaction. | The price for the item when added to a transaction. | ||
| + | |- | ||
| + | | <div id="UseinMobile"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Inventory: Use in Mobile</div> | ||
| + | |- | ||
| + | | | ||
| + | When checked, the item will be available for use in mobile. | ||
|- | |- | ||
| <div id="Warehouse"> </div> | | <div id="Warehouse"> </div> | ||
| Line 984: | Line 1,017: | ||
| | | | ||
The extension number for the contact telephone number | The extension number for the contact telephone number | ||
| + | |- | ||
| + | | <div id="jobtype_Code"></div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Job Type Code</div> | ||
| + | |- | ||
| + | | | ||
| + | Used to recognize the job type. | ||
|- | |- | ||
| <div id="job_mainno"> </div> | | <div id="job_mainno"> </div> | ||
| Line 1,045: | Line 1,085: | ||
| | | | ||
The salesperson for the job. *Certain ERP systems require a salesperson. | The salesperson for the job. *Certain ERP systems require a salesperson. | ||
| + | |||
| + | |- | ||
| + | | <div id="job_sendtomobile"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Job: Send to Mobile Checkbox</div> | ||
| + | |- | ||
| + | | On save, if this checkbox is checked, the job will be made available in mobile. | ||
| Line 1,090: | Line 1,137: | ||
Status codes are used to determine the job's position in the work process. | Status codes are used to determine the job's position in the work process. | ||
|- | |- | ||
| − | | <div id=" | + | | <div id="job_statusbar"> </div> |
|- | |- | ||
| − | + | | <div class="fieldHeader">Job: Status Bar</div> | |
|- | |- | ||
| | | | ||
| − | + | The status bar indicates the job's status progress. | |
| + | |||
| + | |||
|- | |- | ||
| <div id="jobtype_Desc"> </div> | | <div id="jobtype_Desc"> </div> | ||
| Line 1,146: | Line 1,195: | ||
| | | | ||
The default priority that will be used when creating new jobs. | The default priority that will be used when creating new jobs. | ||
| + | |- | ||
| + | | <div id="ReportingGroups"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Reporting Groups</div> | ||
| + | |- | ||
| + | | | ||
| + | A group code can be assigned to a miscellaneous charge code to group like Item codes. | ||
| + | |- | ||
| + | | <div id="corep_repaddress"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Address</div> | ||
| + | |- | ||
| + | | | ||
| + | The mailing address for the representative. | ||
| + | |- | ||
| + | | <div id="corep_city"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: City</div> | ||
| + | |- | ||
| + | | | ||
| + | The city for the mailing address | ||
| + | |- | ||
| + | | <div id="corep_country"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Country</div> | ||
| + | |- | ||
| + | | | ||
| + | The country for the mailing address. | ||
| + | |- | ||
| + | | <div id="corep_repdivision"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Division</div> | ||
| + | |- | ||
| + | | | ||
| + | If division are in use, the representative division can be assigned. | ||
| + | |- | ||
| + | | <div id="corep_repemail"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Email</div> | ||
| + | |- | ||
| + | | | ||
| + | The email address used to contact the representative. | ||
| + | |- | ||
| + | | <div id="corep_repname"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Name</div> | ||
| + | |- | ||
| + | | | ||
| + | The name of the representative. | ||
| + | |- | ||
| + | | <div id="corep_repno"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Number</div> | ||
| + | |- | ||
| + | | | ||
| + | The representative number can be used to recognize a representative. | ||
| + | |- | ||
| + | | <div id="corep_repphone"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Phone</div> | ||
| + | |- | ||
| + | | | ||
| + | The telephone number used to contact the representative. | ||
| + | |- | ||
| + | | <div id="corep_state"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: State</div> | ||
| + | |- | ||
| + | | | ||
| + | The state for the mailing address. | ||
| + | |- | ||
| + | | <div id="corep_reptype"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Type</div> | ||
| + | |- | ||
| + | | | ||
| + | Types are used to organize representatives. | ||
| + | |- | ||
| + | | <div id="corep_zip"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Zip</div> | ||
| + | |- | ||
| + | | | ||
| + | The postal code for the mailing address. | ||
|- | |- | ||
| <div id="job_request"> </div> | | <div id="job_request"> </div> | ||
| Line 1,162: | Line 1,295: | ||
| | | | ||
Request notes are used to further define the work requested. | Request notes are used to further define the work requested. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| − | | <div id=" | + | | <div id="costtype_RevAcct"> </div> |
|- | |- | ||
| − | | colspan="1" style="width: 1538px;" | <div class="fieldHeader"> | + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue Account</div> |
|- | |- | ||
| | | | ||
| − | The | + | The sales account that will be assigned to transactions assigned this job type and cost type. |
|- | |- | ||
| − | | <div id=" | + | | <div id="costtype_RevSubacct"> </div> |
|- | |- | ||
| − | | colspan="1" style="width: 1538px;" | <div class="fieldHeader"> | + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue subaccount</div> |
|- | |- | ||
| | | | ||
| − | The | + | The sales sub-account that will be assigned to transactions assigned this job type and cost type. |
|- | |- | ||
| − | | <div id=" | + | | <div id="servicetype_Code"> </div> |
|- | |- | ||
| − | | colspan="1" style="width: 1538px;" | <div class="fieldHeader"> | + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Code</div> |
|- | |- | ||
| | | | ||
| − | + | Used to identify the service type. | |
|- | |- | ||
| − | | <div id=" | + | | <div id="servicetype_Desc"> </div> |
|- | |- | ||
| − | | colspan="1" style="width: 1538px;" | <div class="fieldHeader"> | + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Desc</div> |
|- | |- | ||
| | | | ||
| − | + | Used to describe the service type. | |
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| Line 1,200: | Line 1,339: | ||
| + | |||
| Line 1,205: | Line 1,345: | ||
| + | |- | ||
| + | | <div id="job_scheduledate"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Date</div> | ||
| + | |- | ||
| + | | | ||
| + | The date the technician is schedule to do the work. | ||
| + | |- | ||
| + | | <div id="job_scheduletime"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Time</div> | ||
| + | |- | ||
| + | | | ||
| + | The time the technician is schedule to do the work. | ||
| + | |- | ||
| + | | <div id="site_Address"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Address</div> | ||
| + | |- | ||
| + | | | ||
| + | The physical address for the site. This field is used in dispatching. | ||
| + | |- | ||
| + | | <div id="site_Branch"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Branch</div> | ||
| + | |- | ||
| + | | | ||
| + | The site branch is required if multi-branching is in use. | ||
| + | |- | ||
| + | | <div id="site_Chain"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Chain</div> | ||
| + | |- | ||
| + | | | ||
| + | The site's chain. Chains are not required. | ||
| + | |- | ||
| + | | <div id="site_City"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: City</div> | ||
| + | |- | ||
| + | | | ||
| + | The address city for the site. This field is used in dispatching. | ||
| + | |- | ||
| + | | <div id="site_CloneAddress"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Customer Address</div> | ||
| + | |- | ||
| + | | | ||
| + | When clicked, this button will clone the customer's address to the site. | ||
| + | |- | ||
| + | | <div id="site_CloneShipTo"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Ship To</div> | ||
| + | |- | ||
| + | | | ||
| + | When an item is selected, the ship to address will be copied to the site address fields. | ||
| + | |- | ||
| + | | <div id="site_Code"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Code</div> | ||
| + | |- | ||
| + | | | ||
| + | The site code can be used to identify the site. It is not required. | ||
| + | |- | ||
| + | | <div id="site_EST"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Established Date</div> | ||
| + | |- | ||
| + | | | ||
| + | The date the site was added. | ||
| + | |- | ||
| + | | <div id="site_Fax"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Fax Number</div> | ||
| + | |- | ||
| + | | | ||
| + | The site's Fax number. | ||
| + | |- | ||
| + | | <div id="site_Labor1"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Labor #1</div> | ||
| + | |- | ||
| + | | | ||
| + | Back office labor transaction entry can include two labor quick buttons. This item will be linked to the first button. | ||
| + | |- | ||
| + | | <div id="site_Labor2"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Labor #2</div> | ||
| + | |- | ||
| + | | | ||
| + | Back office labor transaction entry can include two labor quick buttons. This item will be linked to the second button. | ||
| + | |- | ||
| + | | <div id="site_Lat"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Latitude</div> | ||
| + | |- | ||
| + | | | ||
| + | The latitude for the site location. | ||
| + | |- | ||
| + | | <div id="site_Long"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Longitude</div> | ||
| + | |- | ||
| + | | | ||
| + | The longitude for the site location. | ||
| + | |- | ||
| + | | <div id="site_MainNo"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Main Number</div> | ||
| + | |- | ||
| + | | | ||
| + | The main business contact telephone number for the site. | ||
| + | |- | ||
| + | | <div id="site_MapCode"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Map Code</div> | ||
| + | |- | ||
| + | | | ||
| + | When using Key Maps or Rand McNally's Street Finders this will be the code to associate the location with a particular map page. | ||
| + | |- | ||
| + | | <div id="site_Name"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Name</div> | ||
| + | |- | ||
| + | | | ||
| + | The name of the site location. This is used to identify the site. | ||
| + | |- | ||
| + | | <div id="site_PriceLevels"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Price Level</div> | ||
| + | |- | ||
| + | | | ||
| + | The price level that should be used when billing jobs. | ||
| + | |- | ||
| + | | <div id="site_PContact"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Primary Contact</div> | ||
| + | |- | ||
| + | | | ||
| + | The site's primary contact. Contacts are management using the Contact Mangement system. | ||
| + | |- | ||
| + | | <div id="site_Priority"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Priority Code</div> | ||
| + | |- | ||
| + | | | ||
| + | The default priority code for new jobs added to the site. | ||
| + | |- | ||
| + | | <div id="site_Referral"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Referral Code</div> | ||
| + | |- | ||
| + | | | ||
| + | The site's referral code. Referral codes are not required. | ||
| + | |- | ||
| + | | <div id="site_Servicer1"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Servicer #1</div> | ||
| + | |- | ||
| + | | | ||
| + | The default primary servicer. New jobs will be automatically assigned to this servicer. | ||
| + | |- | ||
| + | | <div id="site_Servicer2"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Servicer #2</div> | ||
| + | |- | ||
| + | | | ||
| + | The secondary servicer for new jobs. | ||
| + | |- | ||
| + | | <div id="site_SLA"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: SLA</div> | ||
| + | |- | ||
| + | | | ||
| + | Check this box, if the site qualifies for SLA service. | ||
| + | |- | ||
| + | | <div id="site_State"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: State</div> | ||
| + | |- | ||
| + | | | ||
| + | The address state code for the site. This field is used in dispatching. | ||
| + | |- | ||
| + | | <div id="site_StoreNo"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Store Number</div> | ||
| + | |- | ||
| + | | | ||
| + | The store number for the site. The store number is directly tied to the Chains feature. | ||
| + | |||
| + | |- | ||
| + | | <div id="site_StoreType"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Store Type</div> | ||
| + | |- | ||
| + | | | ||
| + | The store type for the site. The store number is directly tied to the Chains feature. | ||
| + | |- | ||
| + | | <div id="site_Type"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Type</div> | ||
| + | |- | ||
| + | | | ||
| + | Site types are used to organize sites. Site types are not required. | ||
| + | |- | ||
| + | | <div id="site_Zip"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Site: Zip Code</div> | ||
| + | |- | ||
| + | | | ||
| + | The address postal code for the site. This field is used in dispatching. | ||
| Line 1,213: | Line 1,564: | ||
| + | |- | ||
| + | | <div id="job_solution"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution</div> | ||
| + | |- | ||
| + | | | ||
| + | Solutions are defined using the Solution Management feature. The solution defines the work done to complete the work. | ||
| + | |- | ||
| + | | <div id="job_solutionnotes"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution Notes</div> | ||
| + | |- | ||
| + | | | ||
| + | Solution notes are used to further define the work performed. | ||
| + | |- | ||
| + | | <div id="Subclass"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Subclass</div> | ||
| + | |- | ||
| + | | | ||
| + | The sub-classification is used in sales and cost account assignments. | ||
| + | |- | ||
| + | | <div id="TaxClass"> </div> | ||
| + | |- | ||
| + | | <div class="fieldHeader">Tax Class</div> | ||
| + | |- | ||
| + | | | ||
| + | The item's task class. | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div id="customertaxexemptno"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Exempt Number</div> | ||
| + | |- | ||
| + | | | ||
| + | If the customer is tax exempt, a value must be used in this field. | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div id="customertaxschedule"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Schedule</div> | ||
| + | |- | ||
| + | | | ||
| + | The customer's tax schedule. This information is assigned at the ERP level and cannot be altered when an ERP is in use. | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div id="customerterms"> </div> | ||
| + | |- | ||
| + | | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Terms</div> | ||
| + | |- | ||
| + | | | ||
| + | The customer's terms. This information is assigned at the ERP level and cannot be altered when an ERP is in use. | ||
|} | |} | ||
Revision as of 10:59, 22 December 2022
Account Manager
|
Account managers are responsible for the customer relationship. |
Active Status
|
Indicates that the record can be used to produce results.
|
Agreement: Auto Renew%
|
Indicates the amount percent of increase for the renewal.
|
Agreement: Billable Checkbox
|
When checked, indicates that the agreement can be billed.
|
Agreement: Billing Total
|
The total contract amount.
|
Agreement: Commission Rate
|
The commission rate that will be used when billing the agreement.
|
Agreement: Contact
|
The customer or site contact that handles the agreement.
|
Agreement: Deferred Revenues Total
|
The total deferred revenues posted to date.
|
Agreement: Frequency
|
The agreement frequency indicates the frequency used when billing the agreement.
|
Agreement: Gross Profit Contact Billed to Date
|
The agreement's gross profit based on billings to date.
|
Agreement: Gross Profit Contract Term to Date
|
The agreement's gross profit recorded on the contract to date.
|
Agreement: Labor Budget Balance %
|
Percentage of labor budget balance to date.
|
Agreement: Labor Budget Used %
|
Percentage of labor budget used to date.
|
Agreement: Labor Budget Hours Used to Date
|
The number of budgeted hours billed to date.
|
Agreement: Labor Hours Balance
|
The remainer of the budgeted hours to date.
|
Agreement: Labor Hours Budget
|
The number of labor hours budgeted for the contract's term.
|
Agreement: Last Increase
|
The increase amount from the last renewal.
|
Agreement: Number
|
Agreement numbers are used the identify agreements.
|
Agreement: Parts Billed to Date
|
The amount billed to date for parts. |
Agreement: Parts Budget
|
The total amount budgeted for parts on the agreement contract.
|
Agreement: Parts Budget Balance
|
The remainer of the amount budgeted for parts to date.
|
Agreement: Parts Budget Balance %
|
Percentage of parts budget balance to date.
|
Agreement: Parts Budget Used %
|
The amount of the parts budget billed to date.
|
Agreement: Price Level
|
The price level that will be used when billing the agreement.
|
Agreement: Pricing Method
|
Agreements can be priced based on the different methods.
Blanket: One price covers all items on the agreement.
By Site: Each site can have a different price.
By Equipment: Each equipment record can have a different price.
|
Agreement: Purchase Order
|
The purchase order provided by the customer for the agreement. |
Agreement: Renewable
|
Indicates that the agreement is eligible for renewal.
|
Agreement: Renewal Amount
|
The amount that will be billed on agreement renewal.
|
Agreement: Renewal Method
|
The renewal method field is used when determining the renewal contract amount. The contract amount can be a fixed amount, or changed based on a change percentage.
Fixed Amount: The renewal will use the exact amount in this field.
Change Percent: Increases the contract amount by the percent in the Renewal Amount field.
|
Agreement: Renewal Months
|
The contract months to use on the renewal.
|
Agreement: Renewal Text
|
The text that will be displayed on the agreement renewal invoice. |
Agreement: Renew As
|
Used to indicate the type of invoice that will be created upon renewal. |
Agreement: Revenues Total
|
The total amount billed for the contract to date. |
Agreement: Salesperson
|
The salesperson that should be assigned to the invoices when billing occurs. |
Agreement: Status Code
|
The status code is used to track the agreements progress through the renewal process. |
| Agreement Type |
Used to organize agreements by type. Agreement types are also used to establish setting for agreements by default. |
| Allocation |
Displays the allocation assigned to the selected agreement type. |
Button: Assigned
|
When clicked, displays all items assigned to the selected record. |
Button: Not Assigned
|
When clicked, displays all the records not assigned to the selected item. |
Classification
|
The classification is used in sales and cost account assignments. Classifications are assigned to Cost Types and Items.
|
Button: Remove all Assignments
|
When clicked, removes all assignments from the selected record.
|
Contact: Address
|
The contacts mailing address.
|
Contact: City
|
The city of the mailing address. |
Contact: Country
|
The country of the mailing address. |
Contact: Email
|
The contact's email address.
|
Contact: Established Date
|
The date the contact record was established.
|
Contact: Fax Number
|
The contact's fax number. |
Contact: First Name
|
The contact's first name.
|
Contact: Last Name
|
The contact's last name.
|
Contact: Name
|
The contacts full name.
|
Contact: Phone
|
The contact's telephone number.
|
Contact: Salutation
|
The salutation that should be used when communicating with the contact.
|
Contact: State
|
The state of the mailing address. |
Contact: Title
|
The contact title. ex: Mr., Mrs.
|
Contact: Type
|
Types can be used to organize contacts.
|
Contact: Zip
|
The postal code of the mailing address.
|
Cost Type
|
Cost types are used to manage general ledger sales and cost account allocations on transactions and billing.
|
Cost Type: Cost Account
|
The cost account that will be assigned to transactions assigned this job type and cost type. |
Cost Type: Cost Subaccount
|
The cost sub-account that will be assigned to transactions assigned this job type and cost type. |
Cost Type: Description
|
Used to describe the cost type.
|
Cost Type: Inventory Checkbox
|
When checked, indicates that the cost type can be used for inventory transactions.
|
Cost Type: Labor Checkbox
|
When checked, indicates that the cost type can be used for labor transactions.
|
Cost Type: Purchases Checkbox
|
When checked, indicates that the cost type can be used for purchase transactions.
|
Customer: Account Manager
|
The company representative that manages the customer's account.
|
Customer: Address
|
The customer's mailing address. |
Customer: Billing Contact
|
The primary billing contact assigned to the customer.
|
Customer: City
|
The customer's mailing address city. |
Customer: Country
|
The customer's mailing address country. |
Customer: Email
|
The email address for the primary customer contact. |
Customer: Ext
|
The main telephone numbers extension. |
Customer: Facebook
|
Link to the customer's Facebook account. |
Customer: Fax
|
The customer's contact fax number. |
Customer: LinkedIn
|
The customer's linked in accounnt handle. |
Customer: Name
|
The name of the organization that will be billed. Jobs can be created without a customer assignmnet, but not billed. |
Customer: Number
|
Customer numbers can be used to help identify a customer. Customer number requirement is based on ERP system. |
Customer: Price Level
|
The customer's price level. Price level requirement is based on ERP settings. |
Customer: Phone
|
The customer's business telephone number. |
Customer: Salesperson
|
The salesperson assigned to the customer's account. |
Customer: State
|
The customers address state. |
Customer: Twitter
|
The customer's twitter handle. |
Customer: Zip Code
|
The customer's address zip code. |
Equipment: Code
|
Equipment codes are used to identify equipment. Codes can be manually, or automatically assigned. |
Equipment: Comment
|
Comments related to the equipment record. |
Equipment: Coverage Date
|
The date coverage begins for the equipment record. |
Equipment: Description
|
Used to describe the equipment. |
Equipment: Item
|
Equipment records that are also inventory items will have the Item Code in this field. |
Equipment: Install Date
|
The date the equipment was installed on site. |
Equipment: Labor Warranty Checkbox
|
When checked, indicates the equipment is covered by a labor warranty. |
Equipment: Labor Warranty End
|
The date the labor warranty ends. |
Equipment: Labor Warranty Start
|
The date the labor warranty begins. |
Equipment: Level
|
Levels are linked to models. If the leve does not appear in the Level drop-list, check the selected models setup. |
Equipment: Manufacturer
|
The equipment's manufacturer. Manufacturers are linked to the equipment type. If you do not see the manufacturer in this list, verify that it is linked to the selected equipment type. |
Equipment: Model
|
The equipment model. Models are linked to a manufacturer. If the model does not appear in the model drop-list, check the selected manufacturer's setup. |
Equipment: Parts Warranty Checkbox
|
When checked, indicates the equipment is covered by a parts warranty. |
Equipment: Parts Warranty End
|
The date the parts warranty ends. |
Equipment: Parts Warranty Start
|
The date the parts warranty begins. |
Equipment: Sale Date
|
The date the equipment was sold to the customer. |
Equipment: Serial Number
|
The equipment's serial number. This is not required.
|
Equipment: Type
|
Equipment types are used to organize equipment. Manufacturers are assigned by equipment type. |
Equipment: Position/Locations
|
Indicates the physical location. |
Inventory: Commissionable
|
When checked the item is commissionable. |
Inventory: Commission Rate
|
If the representative is a salesperson, the commision rate is stored in this field.
|
| Inventory: Equipment Build Checkbox |
When checked, an equipment record will be generated each time the item is billed. Equipment build has a set of defaults that are defined for use during the process.
Prefix: Used when equipment auto-numbering is activated.
EQ Type
Model
Manufacturer
Labor Warranty Period
Parts Warranty Period
Comment
|
Inventory: Item Code
|
Used to identify the item. |
Inventory: Item Description
|
Describes the item. This information comes from the ERP system.
|
Inventory: Item Type
|
Indicates the type of Item. |
Inventory: Prefix
|
Used for equipment auto numbering. If a matrix is in use that calls for this prefix, the system will use the value in this field. |
Inventory: Price Code
|
The item's price code. The price code is used when calculating transaction pricing. |
Inventory: Product Line
|
The item's product line. |
Inventory: Sales UOM
|
The item's unit of measure. |
Inventory: Servicer Mobile Button
|
When checked, a mobile button will be made available in mobile for quick entry. |
Inventory: Short Description
|
A short description for the item. |
Inventory: Split Commission
|
When checked, commission on the item can be slit. |
Inventory: Trade Discount
|
When checked, discounts are allowed. |
Inventory: Unit Cost
|
The item's cost. |
Inventory: Unit Price
|
The price for the item when added to a transaction. |
Inventory: Use in Mobile
|
When checked, the item will be available for use in mobile. |
Inventory: Warehouse
|
The item's default warehouse. |
Job: Billed Status
|
Indicates where the job is in the billing process. |
Job: Contact
|
The site or customer contact assigned to the job. |
Job: Contact Email
|
The email address for the job contact. |
Job: Extension
|
The extension number for the contact telephone number |
Job: Job Type Code
|
Used to recognize the job type. |
Job: Main Number
|
The job's main contact telephone number |
Job: Number
|
Used to identify the job. |
Job: Payment Method
|
The default payment method.
|
Job: Phone
|
The contact telephone number for the job. |
Job: Primary Servicer
|
The primary servicer for the job. New jobs will automatically use the primary servicer. |
Job: Received Date
|
The date the job was received from the customer. |
Job: Reference Number
|
The default payment reference number.
|
Job: Salesperson
|
The salesperson for the job. *Certain ERP systems require a salesperson. |
Job: Send to Mobile Checkbox
|
| On save, if this checkbox is checked, the job will be made available in mobile.
|
Job: Service Type
|
Service types are used to organize jobs. Service type are organized by job type.
|
Job: SLA Checkbox
|
Check this box, if the job qualifies for SLA service. This defaults from the site. |
Job: SLA Expiration Date
|
The date the technician has to start the work in order to meet the SLA criteria. |
Job: SLA Expiration Time
|
The time the technician has to start the work in order to meet the SLA criteria.
|
Job: Status
|
Status codes are used to determine the job's position in the work process. |
Job: Status Bar
|
The status bar indicates the job's status progress. |
Job Type: Description
|
Used to describe the job type. |
Job Type: Estimated Hours
|
The hours estimated to complete the job. |
Job Type
|
Job types are used to organize jobs by type and service types. Job types are tied to the billing sales and cost accounts for transactions. |
Job Type: KPI Call Count Checkbox
|
When checked the jobs assigned the job type will be counted in the KPI analytics. |
Job Type: Opportunity
|
Marks the job type as a job opportunity. |
Job Type: Quoted $s
|
The dollars quoted for the job. |
Priority
|
The default priority that will be used when creating new jobs. |
Reporting Groups
|
A group code can be assigned to a miscellaneous charge code to group like Item codes. |
Representative: Address
|
The mailing address for the representative. |
Representative: City
|
The city for the mailing address |
Representative: Country
|
The country for the mailing address. |
Representative: Division
|
If division are in use, the representative division can be assigned. |
Representative: Email
|
The email address used to contact the representative. |
Representative: Name
|
The name of the representative. |
Representative: Number
|
The representative number can be used to recognize a representative. |
Representative: Phone
|
The telephone number used to contact the representative. |
Representative: State
|
The state for the mailing address. |
Representative: Type
|
Types are used to organize representatives. |
Representative: Zip
|
The postal code for the mailing address. |
Request
|
Requests are defined using the Request Management feature. The request defines the work requested. |
Request Notes
|
Request notes are used to further define the work requested. |
Revenue Account
|
The sales account that will be assigned to transactions assigned this job type and cost type. |
Revenue subaccount
|
The sales sub-account that will be assigned to transactions assigned this job type and cost type. |
Service Type: Code
|
Used to identify the service type. |
Service Type: Desc
|
Used to describe the service type.
|
Schedule Date
|
The date the technician is schedule to do the work. |
Schedule Time
|
The time the technician is schedule to do the work.
|
Site: Address
|
The physical address for the site. This field is used in dispatching. |
Site: Branch
|
The site branch is required if multi-branching is in use. |
Site: Chain
|
The site's chain. Chains are not required. |
Site: City
|
The address city for the site. This field is used in dispatching. |
Site: Clone From Customer Address
|
When clicked, this button will clone the customer's address to the site. |
Site: Clone From Ship To
|
When an item is selected, the ship to address will be copied to the site address fields. |
Site: Code
|
The site code can be used to identify the site. It is not required. |
Site: Established Date
|
The date the site was added. |
Site: Fax Number
|
The site's Fax number. |
Site: Labor #1
|
Back office labor transaction entry can include two labor quick buttons. This item will be linked to the first button. |
Site: Labor #2
|
Back office labor transaction entry can include two labor quick buttons. This item will be linked to the second button. |
Site: Latitude
|
The latitude for the site location. |
Site: Longitude
|
The longitude for the site location. |
Site: Main Number
|
The main business contact telephone number for the site. |
Site: Map Code
|
When using Key Maps or Rand McNally's Street Finders this will be the code to associate the location with a particular map page. |
Site: Name
|
The name of the site location. This is used to identify the site. |
Site: Price Level
|
The price level that should be used when billing jobs. |
Site: Primary Contact
|
The site's primary contact. Contacts are management using the Contact Mangement system. |
Site: Priority Code
|
The default priority code for new jobs added to the site. |
Site: Referral Code
|
The site's referral code. Referral codes are not required. |
Site: Servicer #1
|
The default primary servicer. New jobs will be automatically assigned to this servicer. |
Site: Servicer #2
|
The secondary servicer for new jobs. |
Site: SLA
|
Check this box, if the site qualifies for SLA service. |
Site: State
|
The address state code for the site. This field is used in dispatching. |
Site: Store Number
|
The store number for the site. The store number is directly tied to the Chains feature. |
Site: Store Type
|
The store type for the site. The store number is directly tied to the Chains feature. |
Site: Type
|
Site types are used to organize sites. Site types are not required. |
Site: Zip Code
|
The address postal code for the site. This field is used in dispatching.
|
Solution
|
Solutions are defined using the Solution Management feature. The solution defines the work done to complete the work. |
Solution Notes
|
Solution notes are used to further define the work performed. |
Subclass
|
The sub-classification is used in sales and cost account assignments. |
Tax Class
|
The item's task class. |
Tax Exempt Number
|
If the customer is tax exempt, a value must be used in this field. |
Tax Schedule
|
The customer's tax schedule. This information is assigned at the ERP level and cannot be altered when an ERP is in use. |
Terms
|
The customer's terms. This information is assigned at the ERP level and cannot be altered when an ERP is in use. |