Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Contract with service settings are used for specific leasing with services settings, i.e. it is mainly related to areas Operative Leasing and Fleet Management.

To complete it, it is necessary to have several other code lists set up – they are listed in the description of individual fields (for example, detailed contract statuses, numerical advice, etc.).

Availability of the code list via magnifying glass, Manual Setup or Configuration Workbook, name Contract with Services Setup. After confirming the selection, the Contract with Services Setup tab opens.

General Tab

  • Bonus Date

    • According to the selected value in this field, it will be added to the service permission line Invoice Date Bonus from Posted Purchase Invoice

    • Select an option Posting Date, VAT Date, Document Date

  • Default Maintenance Type Code

    • The user enters the default maintenance type for the insured event, which will be applied as the default value to the service permission

  • Summer Tire Life Expectancy (km)

    • The user enters the service life of summer tires in KM.

    • The value of the field is included in the calculation of the Tire Service service

  • Winter Tire Life Expectancy (km)

    • The user enters the lifetime of winter tires in KM.

    • The value of the field is included in the calculation of the Tire Service service

  • Year-Round Tire Life Expectancy (km)

    • The user enters the service life of the year-round tires in KM

    • The value is included in the calculation of the Tire Service service for all-season tires

  • Summer Tire Usage (Month per Year)

    • The user enters the number of months when summer tires are used

  • Winter Season Start Day

    • The user enters the day of the start of the winter season (for changing tires)

  • Winter Season Start Month

    • The user enters the month of the start of the winter season (for changing tires)

  • Winter Season End Day

    • The user enters the day of the end of the winter season (for changing tires)

  • Winter Season End Month

    • The user enters the month of the end of the winter season (for changing tires)

  • Maintenance Rate Calculation Type

    • User selects from values Per Interval, Per Operating Unit

    • The system will bring the selected value to the service of the contract, where it will be used to search for the service rate in the service rate price list.

  • Allow Fuel Reinvoicing without Posting Purchase

    • The user ticks if he wants to re-invoice fuel card transactions to the client even if the purchase invoice has not yet been posted. Only an error-free transaction can be reinvoiced to the client

  • Registration Date Before OnLine Insurance

    • Flag that the system checks in the wizard Preparation of the object for handover

    • If this field is checked, the system checks if the field is Leasing Company's First Registration Date on the subject and whether it is not higher than the beginning of the policy, i.e. Valid From Insurance policies reported online

Contract Recalculation Tab

It is used to set parameters for contract recalculation (change of mileage/time).

  • Mileage Recalculation

    • When changing the duration, the system calculates the contractual or annual mileage according to this setting

  • Do Not recalculate before

    • The data formula (e.g. 6M) will be used in the Contracts with Outrange Odometer Status report (see PD Contract Changes).

No.Series Tab

For a description of the number sequence settings, see Finance Setup

Field:

  • Mass Invoice Nos.

    • The user selects the number series under which invoices for mass insolvency payments will be generated

  • Mass Credit Memo Document

    • Invoice number + Sx – in case of mass cancellation of an invoice, the system adds the "S" flag to the invoice number.

      • If the user chooses Partial cancellation of the invoice, each subsequent credit memo will have number = invoice number + S + x (a number expressed as how many credit memos have been created from the mass invoice)

  • Mass Credit Memo Nos.

    • Mass Payment Invoice Credit Memo Nos.

    • For a description see Invoicing Sales

  • Mass Maint Reinvoice Nos.

    • The user selects the number series under which posted invoices for service permission from the mass task will be generated

      • The system creates unposted invoices in which it uses this number series, and then posts a sales invoice with the same number.

  • Fuel Purch. Cr. Memo Nos.

    • The user selects the number series under which the purchase credit memos for fuel will be generated

  • Fuel Card Posted Purchase Credit Memo Nos.

    • The user selects the number series under which the posted purchase credit memos for fuel will be generated

  • Fuel Purchase Invoice Numbers (Fuel Purch. Invoice Nos.)

    • The user selects the number series under which purchase invoices for fuel from the mass task will be generated

  • Fuel-Card Posted Purchase Invoice Numbers

    • The user selects the number series under which the purchase posted invoices for fuel from the Mass Task will be generated

  • Fuel Post. Purch. Cr. Memo Nos.

    • The user selects the number series under which sales credit memos for fuel will be generated

  • Fuel Sales Invoice Nos.

    • The user selects the number series under which sales invoices for fuel from the mass job will be generated

  • Master Agreement Nos.

    • The user selects the number series under which the customer's master agreements will be generated

  • Maint. Purch. Cr. Memo Nos. Purch. Cr. Memo Nos.)

    • The user selects the number sequence under which purchase credit memos for service permissions will be generated

  • Mainton Posted: Purch. Credit Memo Nos.

    • The user selects the number sequence under which posted purchase credit memos for service permissions will be generated

  • Service Purchase Invoice Nos. (Maint. Purch. Invoice Nos.)

    • The user selects the number series under which invoices for service permissions will be generated

  • Posted Purchase Invoice Nos. of Service Allowances

    • The user selects the number series under which invoices for service permissions will be generated

  • Mass Maint Credit Memo Nos.

    • The user selects the number sequence under which sales credit memos for service permissions will be generated

      • The system creates a non-posted credit memo in which it uses this number series, and then posts a sales credit memo with the same number.

  • Service Sales Invoice Numbers (Maint. Sales Invoice Nos.)

    • The user selects the number sequence under which sales invoices for service permissions will be generated

  • Maintenance Master Agreement Nos. (Maint. Agreement Nos.)

    • The user selects the number series under which the framework service agreements will be generated

  • Fuel Card Nos.

    • The user selects the number series under which fuel cards will be generated

  • Int. Maintenance Permission Nos.

    • The user selects the number series under which Service Permissions will be generated

  • Mass maint. Credit Memo Nos.)

    • The user selects the number series under which service credit memos will be generated

  • Mass Payment Credit Memo Nos.

    • A user selects a number sequence for the Posting Installment Credit Memos mass task for an unposted credit memo. After the job runs, the system uses the number sequence when it creates the unposted credit memo (in the background).

  • Mass Payment Posted Credit Memo Nos.

    • A user selects a number sequence for the Mass Posting Credit Memos for Installments batch task when creating a posted credit memo for installments.

Mass Invoicing Tab

  • Mass Invoicing Account No.

    • The field is used to specify the "temporary account" for mass invoicing (the invoice is marked Mass invoice A) except for the invoice print type Payment.

    • When posting, the system executes the entry:

      • Customer Posting Group(311xxx) Dimension MASS / Standard Sales Code                                                                                               

      • Mass Invoicing Account No. (e.g. 395xxx)/Customer Posting Group (311xxx) MA dimension

      • Customer Posting Group (311xxx) for Dimension 2 (Contracts)/

      • This means that a mass invoice for individual contracts will be unfinished in the customer entries in the open entries. In closed entries, a large invoice with the Mass dimension will be settled.

    • User selects the account number to which the mass invoice will be posted

  • Do Not Post Credit Memo from Payment Calendar

    • If YES, the function under the Cancel button in the payment calendar will not post a credit memo for the payment. Creates an unposted credit memo with the Payment Credit Memo flag YES.

    • If there is an NIE, the function under the Cancel button in the payment calendar will post a credit note for the payment.

  • Check for Billing Invoicing Difference

    • NO – the system will not check the value in the payment calendar and in the invoice lines – standard functionality

    • YES – The system will compare the value in the payment calendar fields against the invoice lines for each group.
      Group 1 - Principal, Interest
      Group 2 - Insurance
      Group 3 - Service

  • Account for Billing Invoicing Difference

    • Lookup to Tab. G/L Account (15) (chart of accounts)

  • VAT Prod. Posting Group for Billing Difference

    • lookup VAT Product Posting Group (324)

  • Standard Text Code – Fuel (PHM)

    • The user selects a standard text code with which a single line will be created in the mass sales invoice of fuel and it will be printed on the invoice

  • Standard Text Code – Service

    • The user selects a standard text code with which a single line will be inserted in the mass sales invoice of the service permission and printed on the invoice

  • Contract Dimension Value

    • The user enters a dimension value that the system adds to the header of the mass sales invoice (the system adds individual contract numbers to the lines)

    • For a description see Invoicing Sales

Road Tax Tab

Only for the Czech Republic and Slovakia.

Field:

  • Road Tax Service No.

    • The user selects the code of the service type for road tax, which will be added to the calculation when the road tax service is created

  • Value for Electric Car

    • Determining the type of fuel for electric vehicles

    • When creating a road tax in a contract (if the subject is not exempt from road tax), the system compares the value of this field with the value of the "Fuel type" field on the "Financed object". If the values are equal, then in the "Road Tax Pricelist" the system filters only to records that have the value "Electric Vehicle" in the "Object Category" field

  • Value for Personal Vehicle

    • Specifying a Group for Passenger Cars

    • When creating the road tax in the contract (if the object is not exempt from road tax) and if it is not an electric vehicle, the system compares the value of this field with the value of the "Catalogue Card Group" field on the "Financed Object" field. If the values are equal, then in the "Road Tax Pricelist" the system filters only to records that have the value "Passenger vehicle" in the "Object Category" field

  • Road Tax Legislation

    • The user selects from the options Czech or Slovak

    • It is used to filter the "Road Tax Pricelist" if it is not an electric car and a passenger car, see above.

    • The first one filters the number of axles in the "Road Tax Pricelist" as follows

      • Slovak

        • if there are 2 or fewer axles on the "Financed Object", then the "Road Tax Pricelist" filters to "1 or 2" in the "Number of axles" field

      • Czech

        • if there is 1 axle on the "Financed Object", then the "Road Tax Pricelist" filters to "1" in the "Number of axles" field,

        • if there are 2 axles on the "Financed Object", then the "Road Tax Pricelist" filters to "2" in the "Number of axles" field

    • Subsequently, if on the "Group of Cat. Cards" in the field "Type of Calculation of Forces. tax" equal to "sum of axle weights", is filtered in the "Road Tax Pricelist" according to the weight of the financed object as follows

      • Slovak

        • searches for the nearest lower value in the "Road Tax Pricelist" in the "Total weight to" field compared to the value on "Financed Object" in the "Total weight on axles" field

      • Czech

        • searches in the interval "Total weight from" and "Total weight to" in the "Road Tax Pricelist" against the value on "Financed Object" in the field "Total weight on axles"

  • Setting up a Road Tax Service (Road Tax Calc. Type)

    • The user selects from the Averaged or According to Discount Bands options

    • If Averaged, the OC calculates the total value of the road tax for the entire duration of the contract for sections according to the discount bands, then divides the calculated value evenly into installments. The result is one road tax service for the entire duration of the contract.

    • According to the discount bands, the OC establishes as many road tax services during the term of the contract as the number of road tax discount bands it identifies. The result may be several road tax services, within which the values of the tax to the instalment are different.

  • No labels