Note: This help system contains standard information, some of which might not apply to your franchise. Click the Help button on the relevant forms or menus to see any existing help file specific to your Autoline configuration for that form or menu. Alternatively, a help file may exist in the Warranty Table of Contents specific to your manufacturer.
Warning: Most of the parameter options require an access privilege of priority 9 and are normally set up by, or on advice from, a consultant.
Warranty parameters are normally created by dealer code rather than by Point-of-Sale company number. One entry is usually required per dealer code.
To access warranty parameters:
The CLAIMS MENU is displayed.
Select the Service and repair claims option.
If a pop-up menu lists the Point-of-Sale companies on Autoline, select the required Point-of-Sale company.
The Warranty Claims form is displayed.
Select the Parameters option from the Edit menu or click the Edit claim system parameters toolbar button 
The Parameters form is displayed.
Warning: Most of the parameter options require access priority 9 and are normally set up by, or on advice from, a consultant.
See also Financial Tab.
This form is displayed when you select Edit > Parameters from the menu bar of the Claims form or click the Edit claim system parameters toolbar button . It allows you to edit specific warranty parameters as distinct from general parameters.
Tip: There may be a button on this form which will display more manufacturer-specific parameters.
Tabs:
SL Accounts (Not used by all manufacturers.)
Mark up (Not used by all manufacturers.)
Dealer number: Number assigned to the dealership by the manufacturer
Archiving
Days to keep before archiving: Number of days for which closed claims are held before they are archived.
Days to keep in archive: Number of days for which claims are held in the archive until they are permanently deleted.
Auto archive: Number of days between each auto-archive, or 0 for no auto-purge.
Last archive: Date of last archive.
Rules
This section specifies the rules the system uses to generate a claim.
Allow multiple claims per POS invoice: When selected, enables one invoice to contain all the claims for that job.
Sublet labour type: First character of labour rate code used in Point-of-Sale to identify sublet warranty work, usually obtained from the site contact.
Repair date from: Usually set to O.
Use today if above date is blank: Select this check box to use today's date if the Repair date from field is blank.
Main op required: Not used by all manufacturers.
Causal part reqd.: When selected, forces the requirement of a causal part to be set.
Max labour lines: Maximum number of labour lines per claim.
Max parts allowed: Maximum number of parts per claim.
Max tasks per claim: Maximum number of tasks per claim.
Submission number: Automatically assigned by the system when you submit claims to the manufacturer. Usually set to 0 (zero) initially. When you submit a claim, it increments by one. Therefore, it identifies the last claim submission file to the manufacturer.
Tip: To keep overpayments out of your profit and loss accounts until year end, set contingent liability.
Warranty suspense cost centre: Cost centre of bank account in nominal ledger.
Warranty suspense expense code: Expense code of bank account in nominal ledger.
Create separate VAT element: A tick causes line 10 in the grid to contain the total VAT amount, while other lines are nett values. If the parameter is ticked, you see VAT displayed in the list of claim/payment elements with Parts, Labour, and so on. This allows VAT to be written off to a different Nominal Ledger account from the parts, labour, and so on.
Note: Create separate VAT element is usually left blank. Line 10 in the grid would then not normally contain the total VAT amount.
Fixed price menus are separate element: A tick indicates that menus are treated as one payment element.
Last claim number (at bottom of form): Last claim number generated by the system when a new warranty claim is created in Service Point-of-Sale as part of the invoicing process.
Note: Last claim number can either start at zero or be dictated by the dealer/business according to the existing claim number range.
Claim/payment elements:
Tip: To edit Claim/payment elements, place the cursor on the grid line you want to edit and double-click.
Description: Text for the payment line - for example: Labour, Parts, Mileage, Sublet and Handling.
W/o CC (Write off cost centre): Cost centre code for the rejection of related charges.
Note: Nominal accounts, Max %, and Max val are dictated by the dealer/business.
W/o EX (Write off expense code): Expense code for the rejection of related charges.
Max %: Maximum allowed write-off percentage value.
Max val: Maximum allowed write-off value.
Inc' (Elements included): A code marking the line as a component of the payment or claim.
The Description and Inc columns will look similar to the following example in the table:
Description W/o CC W/o EX Max % Max val Inc' Labour L Parts NP Mileage I Sublet S Handling HH
Use manual payments: Y (Yes), N (No) or 0 (No payments available).
Priority to override write-off max: User access priority level (1 to 9) required to override the pre-set maximum write-off value.
Accounts integration: Post payments direct to accounts.
Task header rtscode: Repair time schedule code attached to the task record header.
Task identifier: Must be set to 2, but Tasks do not apply to all manufacturers.
Single claim print format: Print format to be used when printing a single claim.
Claim group print format: Print format to be used when printing a claim group.
Light validation: Determines whether light validation of the claim is required and at what stage of editing it is carried out. Select, by using the drop-down button
, the Autoline module or modules (if any) to perform light validation of the claim record:
P: Light validation in Point-of-Sale only
M: Light validation in Manufacturer systems only
B: Light validation in both Point of Sale and Manufacturer systems
N: No light validation at all
Tip: Where a cost clerk with little knowledge of warranty procedures needs to complete and invoice a claim, light validation enables the system to accept less information on a valid claim in places such as Point of Sale.
The requirements for a valid warranty claim using light validation are:
- Complete VIN (17 characters, all numeric)
- Vehicle model code
- Customer concern code
- Condition code
Sales Ledger Accounts required for the manufacturer. (Not used by all manufacturers.)
Not used by all manufacturers. The Mark up tab enables you to set parameters for handling charge percentage calculations.
Tip: Click in a grid cell (usually Part number), then click the Ellipsis button. This displays a Stock Records form that enables you to perform Part number- or Word Search searches.
Grid:
Part number: Enables you to add parts after raising a WIP or creating an invoice.
Description: Reason for the mark-up.
%: Required percentage of handling charge.
Maximum: Maximum value of the WIP in relation to the claim payment.
Add?: Tick if parts are to be added to the WIP.
This form is displayed when you click the manufacturer-specific parameters button on the Parameters form (if applicable to your franchise). It displays manufacturer-specific parameters.
See also: Look-up Files.
Claim prefix: Claims may be alpha-numeric but the generic warranty system supports only numeric claim numbers. In those circumstances, an alpha prefix would have to be added to the claim at the point of transmission. In that case, the prefix you use here must normally be one that the dealership has never used before. If we set a prefix they have already used, lots of claims may be rejected by a manufacturer system because it will regard them as duplicates.
Serial number location: Different dealers/businesses might store the vehicle serial number in different places on the marketing vehicle record. If the dealer/business stores the serial number in the Reg number field, you would normally select R. If it is in the Chassis number field, you would normally select C. If the dealer/business stores it somewhere else, contact the development department for a product enhancement.