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 11 Next »

By the transfer of a financing contract, we mean the process by which a new customer (the so-called successor) enters into all the rights and obligations of the original customer without changing the terms and conditions. Therefore, the financing contract will be transferred from the original customer to the new customer without any changes.

The contract transfer procedure is as follows:

  • The transfer of a contract has several steps, some of which can be omitted depending on the processes in the leasing company:

    • We recommend that you perform the contract transfer operations on the change copy of the contract

    • Change the detailed status if the user wants to stop invoicing, for example (optional step)

    • Registration of input data for transfer into the contract

    • Transfer Approval

    • Stopping insurance contracts and creating e.g. new contracts by copying

      • Execute the transfer

      • In addition, the settings from the OneCore Settings are needed to perform the transfer (see Nastavení Business).

      • The condition is that the transfer has been approved and that the detailed contract status has allowed the transfer.

      • The system automatically sets the effectiveness of the transfer to the 1st day of the unposted payment period

  • Optional step – change the detailed status to one that does not allow invoicing from the payment calendar (if the leasing company wants to ensure that no further invoicing is done if the transfer is not completed). The user starts the Contract Status Change Wizard and changes the contract status from active, e.g. to temporarily suspended. After changing the detailed status, the contract will remain in the change copy (or on the variant) – see the previous chapter for a description of the steps to change the detailed status.

On the contract card, in the Contract Transfer tab, it is necessary to fill in the data related to the transfer of the contract:

  • New Customer No.

    • User selects manually from customers

  • New Customer Name

    • Fills in the system automatically after selecting New Customer No.

  • New Framework Agreement No.

    • The number is selected by the user after entering the New Customer No. from the List of Framework Agreements filtered to the number of the new customer (only for contracts with OPL or GMP services)

  • New Master Agreement Customer No.

    •  Non-editable by the user

    •  fills in the OC automatically according to the Framework Agreement No. from the card of the relevant RS

  • Transfer Request Receipt Date

    • The user fills in the date of the transfer request

  • Documents for approval

    • The user fills in the date of receipt of documents for approval of the transfer

  • Transfer Reason

    • Selects the user from the list Transfer reasons

  • Transfer Status

    • Any change in the transfer status will be recorded in the Contract Transfer History (see below). The transfer statuses are: Empty, Request Accepted, Waiting to Be Accepted, Transfer Rejected, Transfer Approved, Contract Transferred.

  • Transfer Status To execute the transfer, the transfer must be approved. Contract transferred cannot be set manually, set by wizard after completion of the transfer.

  • If the transfer is approved, the user wants to make the transfer and the contract has insurance contracts, the user runs the wizard for changes (not yet the wizard for transfer), creates a change copy and terminates the original insurance contracts (if there is a flag Insurance Report on the insurance policies). Online = Yes, fills in the Termination Code) and creates new insurance contracts (e.g. by copying insurance policies). It is necessary to have the validity until the original WG and the validity from the new WG in accordance with:

    • Set the end of the original insurance policy to the last day of the last posted period

    • The start of new insurance policies is set to the first day of the follow-up. unposted period

      • If there is a flag on the framework contracts of new insurance contracts Insurance Verification Required = Yes, verifies insurance contracts by using the Verification of the poj.

  • Then sets Contract Transfer Status=Transfer Approved

  • User on the same change copy (as he terminated the insurance contracts) starts the Contract Transfer Wizard (in step 1/3 selects Change Type Code=with wizard number 4046865).

The system performs several checks before opening the first step of the wizard:

  • Before opening the first step of the special wizard, the system checks the contract to see if it is in the automatic extension mode (contract Extension = Y flag). If it is, it displays a message and does not run the wizard – no recalculation of the payment calendar is allowed in this contract mode: "Contract extension is Y, change is not possible."

    • If the contract is not in automatic extension mode (i.e. Contract extension=N), it continues.

  • Whether the given detailed status allows the transfer to be carried out (table Detailed Contract Statuses, flag Allow Contract Transfer). If the detailed status does not allow the transfer, the OC will display the message: "Allow Contract Transfer must be Yes in Detailed Contract Status: Code=XY. The present value is No." and the conversion process stops.

  • Whether the Contract Transfer Status is Transfer Approved, if not, it will display the message: "Contract Transfer Status must be equal to "Transfer Approved" in Financing Contract Header: Number: XY. The present value is "XY." and the process stops.

  • Whether it is filled in New Customer No., if not, it will display the message: "The New Customer No. field must have a value (Must not be zero or empty) in the Financing Contract Header: Number: XY table." and the process stops.

  • Check if a user can make a transfer

    • In User Settings, the logged-in user must have Contract Transfer=A, otherwise the system will display a message and will not allow to continue

  • Check the customer to see if they're blocked

    • If the field Blocked=A is on the customer, the system displays a message and does not allow to continue

  • Checking the existence of an active fuel card – only for contracts with Financing with services=A:

    • It checks the existence of active fuel cards in the Fuel Card Organizer for the given contract. Checks the following tabs (filters) The data on the card are:

      • the Financing Contract No. the same as the original contract number (i.e. the Card belongs to the contract), and

      • Card Validity Date To > Transfer Effective Date and Current

      • The Blocking Date or Card Return Date or Card Exclusion Date is not filled in.

    • If it finds active cards, the system checks the Transfer Active Fuel Cards flag in OneCore Setup:

      • If Transfer Active Fuel Cards=N:

        • displays the error message "There are active fuel cards for the contract, the transfer cannot be carried out." and stops the process.

      • If Transfer Active Fuel Cards=Y:

        • It goes on.

  • Whether the original insurance contracts are terminated (it is necessary to close them before starting the transfer wizard). If not, the OC will display the message: "It is not possible to transfer a financing contract that does not terminate insurance contract No. XY to the original customer!" and the process stops.

  • Checks if the customer contact has incidents in the contact's Incidents:

    • Retrieves the contact number of a new customer, then

    • In Incidents, the contact looks for records:

      • Contact No=same

      • Active=Y

    •  If it also finds records, it displays them in step 1/3.

If all the conditions according to the previous points are met, the first step of the conversion wizard will be displayed.

Step 1:

  • Financing Contract No.

    • Fills up the system automatically

  • Current Customer

    • The system will automatically fill in the number of the current customer from the contract

  • Current Customer Name

    • The system will automatically add the name of the current customer from the contract

  • Object Handover Date

    • The system will automatically fill in the date of handover of the object from the contract

  • Successor (new customer)

    • The system will automatically fill in the number of the new customer from the contract

  • New Customer Name

    • The system automatically adds the name of the new customer from the contract

  • Transfer Effective at Date

    • The OC determines automatically, it is the first calendar day of the nearest open (unposted) payment period.

    • When clicked, the contract payment calendar opens.

  • Incidents

    • The system will check if the new customer has a record in the contact incidents (for incidents, see PD Address Book - Contact):

      • If not, it will display info: Successor is not in the incidents...

      • If it is, will it display info? Successor is in the incident list, do you really want to transfer the contract?

  • Number of Records in Incidents

    • Displays the number of customer contact records in incidents

    • After clicking, an overview of incidents of the new customer's contact will open (filter to the contact number and Active=Y)

  • New Framework Agreement No. (linen for OPL)

    • It is possible to select a new successor framework agreement number.

Step 2:

  • Transfer Fee - Posting Date

    • By default, the transfer fee posting date will be displayed as the effective date of the transfer (it is also the date of the VAT liability). Modifies the user as needed.

  • Fee Payment Terms Code

    • The number of days due date of the transfer fee invoice. By default, the code is displayed according to OneCore Settings, modified by the user as needed.

  • Fee Amount Excl. VAT

    • Default 0.00. To be entered manually by the user as needed.

  • Fee Customer No.:

    • The number of the customer to whom the fee invoice will be issued. By default, it is the successor (new customer), but the user can also enter the original customer.

  • Branch No.

    • The number of the branch that is making the transfer. Selects the user from the Store List table. Selects by the user as needed.

Step 3:

In step 3, the OC displays a summary of the important data of the contract transfer. The user has the option to check the effective date of the transfer once again, after clicking on the date in the Transfer Effectiveness to date field, the payment calendar of the financing contract will be opened.

After confirming by the Complete button, the OC will execute:

  • Performs contract recalculation if contract flags are different than Y:

    • Paymens - Updated

    • Calculation Lines- Updated

    • Insurance – Updated

    • Service - Updated

  • Filters insurance contracts in Preparation status with Valid from=change date (first day of next unposted payment)

  • The wizard calls the contract transfer codeunit, which executes:

    • Filters installments:

      • Financing Contract No.=Contract No.

      • Type=Payment

      • Postind Date=>workdate

      • Posted=N

    • On the found installments, he changes:

      • Customer No=new customer number

      • Bill-to Customer No=empty

    • In the Contract header, change Contract Transfer Status=Contract Transfered

    • In the Previous Customer No field, fill in the Customer No. number.

    • Executes the contract - changes the customer on the contract card, i.e.  into Customer No. in the contract is taken over by New Customer No. from the Contract Transfer tab.

  • Validation Customer No. retrieves the new customer's data from the address book (name, address, phone number, payment terms, etc.).

  • After customer validation, the wizard overwrites the posting groups regardless of the OneCore Setup setting, the Posting Group Priority field:

    • Header." Gen. Bus. Posting Group" := customer." Gen. Bus. Posting Group';

    • Header." VAT Business Posting Group" := customer." VAT Bus. Posting Group';

    • Header." Customer Posting Group" := customer." Customer Posting Group";

    • Header." Ind. Inv. Customer Post. Group" := customer." Customer Posting Group";

  • If the contract has Financing with Services=Y, evaluates that it is not empty New Master Agreement No. and differs from Master Agreement No, then it takes the value to Master Agreement No.

    • Validation copies data from the framework agreement

  • If the detailed contract status does not correspond to Det.Contract Status after Activation in OneCore Setup and there is an allowed transition from Det.Contract Status to this detailed status, then it sets the detailed contract status to Det.Contract Status after Activation.

  • Searches for contract services in Status=Preparation and/or Active, then changes them:

    • Gen.Bus.Posting group

    • VAT Bus. Posting Group from Customer

    • flags services with Service – Updated=N so that the service is recalculated

  • Create a line in Contract Transfer History

  • Then searches for a financing object that has the same detailed contract status and updates it to Customer Contract No. (end of codeunit)

  • Triggers contract recalculation

  • The wizard will then create a non-posted individual invoice for the transfer fee if the entered fee amount was different from zero (it will need to be posted after the change copy is transferred)

  • Overwrites the customer on the newly created insurance contract in the status Preparation to the successor, after the change of the customer, the posting groups on the policies are updated and then recalculates these insurance contracts and changes their status to Active

    • If there are policies on the contract as an add-on to the main insurance, you must select the correct number of the main policy to which the add-on is related in the "Supplement to Insurance Contract" field in the copy of the additional policy

  • Deletes the transfer data in the Transfer tab of the contract card

  • Changes the due date of the first unposted payment after transfer to the last day of the payment period depending on the parameter in OneCore Setup:

    • Change Payment Due Date After Transfer =N – does not shift the due date

    • Shift Payment Due Date After Transfer=A – shift the payment due date to the last day of the payment period of the given payment

  • Block all original customer entries from penalty depending on the parameter in the OneCore Setup if Set Fin.Charge Memo Blocking for old customer ledger entries when Transfering=Y

  • If there is a flag on the contract Leasing with delivery of goods = Yes and in OneCore Setup is an array Balance VAT on Leasing with Delivery of Goods = Yes (see also Převod smlouvy s dodáním zboží na jiného zákazníka then:

    • The system will generate calculation inputs with the variant VAT - Supply of Goods:

      • For a tax credit memo to the original customer on the balance of the tax liability on the contract; It is calculated as the total liability from the already booked calculation inputs (initial document + all corrective documents issued so far) minus the transactions booked so far also with regard to the financed VAT in the payment calendar

      • For a tax document (invoice) to a new customer for a performance on the contract that has not yet been posted; it is calculated as the total newly calculated obligation minus the supplies booked so far also with regard to the financed VAT in the payment calendar

    • If set to Settle VAT in Leasing with delivery of goods = No, calculation inputs are not generated and tax documents for VAT transfer from the original to the new customer will not be issued.

 

  • In the last step, the user transfers the change copy after checking the data

  • When transferring a change copy, the user

    • Post an individual transfer invoice (if one was generated)

    • If the OneCore Setup A check mark in the field Transfer Customer Change to Active Fuel Cards (Transfer Active Fuel Cards) = Yes and exist on the financing contract Fuel Cardswhere:

      • Card Validity Date To > the effective date of the transfer and at the same time

      • Not filled in Blocking Date or Card Return Date or Card Exclusion Date

    • When transferring a change copy, the system overwrites the customer to the successor on the fuel cards

    • If there is a flag on the contract Leasing with delivery of goods = Yes and in OneCore Setup is an array Balance VAT on Leasing with Delivery of Goods = Yes

      • The system generates and posts the documents  

        • Credit note to the original customer with the amount according to the calculation input (negative amount)

        • Invoice (new tax document) to a new customer with the amount according to the calculation input (positive amount).

  • No labels