Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Automatically translated by Lango

...

  • Checks if the user is running functions from a change copy (i.e. the flag of the contract is Change Copy=Y):

    • If Y, it continues

    • If N, it displays an error message and does not continue:

      image-20240619-110646.png
  • Checks if the logged-in user is the owner of the change copy:

    • If so, it continues.

    • If not, it displays an error message:

      image-20240619-110709.png
  • Checks if there are active variants for the contract:

    • If not, it continues

    • If so, it displays information about the existence of an active variant and asks if the user wants to continue:

      image-20240619-110734.png
      • After confirmation, it sets Variant Status=Inactive on all active variants and continues.

  • Asks if the user really wants to overwrite the original:

    image-20240619-110757.png
    • After confirmation, it performs a flag check to see if the contract has been recalculated.

  • Checking that the contract payment calendar is up-to-date (if the contract has been recalculated after the change - ActivateChangeCopy function):

    • Service-Updated (150)=Y and

    • Insurance-Updated (151)=Y and

    • Payments-Updated (152)=Y– all three must be Y, otherwise it will display the message:

      image-20240619-110825.png
      • and does not transfer the change copy.

      • If all symptoms are Y, proceed to the next step.

  • Checks if there are insurance contracts for the financing contract to be reported or unsubscribed online.

    • To report a new insurance policy The system checks whether the insurance contract contains:

      • Insurance Reporting OnLine = Yes

      • Insurance Company Check-in Date = empty

      • Termination Code = Empty

    • If there is an insurance policy that meets these conditions, it checks whether the insurance framework contract contains the flag Insurance Company Verification Required = Yes. If:

      • Yes

        • Checks if the Verified = Yes fields are present on the insurance contract if:

          • No

            • Displays the error message "Verified must be Yes on insurance contract XY" and stops the change copy transfer process

          • Yes

            • Checks if the fuse Valid From < the current date. If :o Yes - Displays Yes, it checks whether Valid From is equal to the date in the field Object Return Date on Financed Object Card. If Yes, the policy opt-out system will use the Valid To From the fuse the current system date, and to the insurance company's calendar and commission calendar Completes rows for the period from returning the object to the current date (The daily rate will be applied according to the "daily rate calculation" set on the insurance company's product, see below for an example). If not, you will receive the error message "Insurance XXX. Valid from must be >= current date!" And the transfer of the change copy stopso No - in the OC there is a

Current date is 04.06.2024, Financed Object Return = 31.5.2024, insurance contracts:

Insurance company

Commodity

RS No.

Insurance Contract Type 

Valid From

Valid To

Date of Reporting

Check-out date

GCP

CASCO

 IFR00003

 Proper Insurance

 15.09.2021

 31.05.2024

 15.08.2021

 04.06.2024

GCP

MTPL

IFR00002

 Proper Insurance

 15.09.2021

 31.05.2024

 15.08.2021

 04.06.2024

GCP

MTPL

 IFR00039

 Area

 05.06.2024

 03.06.2025

 05.06.2024

 

Notification:

  • In the statement definition, it is necessary to set the "Disposals" report to the Valid to field from the statement line, not from the Insurance contract

Insurance calendar for a regular insurance client:

Payment No.

LS Payment No.

Period From

Period To

Posting Date

Amount

Pro Rata

001

001A

15.09.2021

30.09.2021

15.09.2021

210

Yes

002

001

01.10.2021

31.10.2021

01.10.2021

420

No

 

 

 

 

 

 

 

 

 

 

 

 

 

 

035

034

01.05.2024

31.05.2024

01.06.2024

420

No

Insurance Calendar for Insurance Company Regular Insurance :

Payment No.

Period From

Period To

Posting Date

Amount

Pro Rata

001

15.09.2021

14.10.2021

15.09.2021

420

No

002

15.10.2021

14.10.2021

15.10.2021

420

No

 

 

 

 

 

 

 

 

 

 

 

 

035

15.04.2024

14.05.2024

15.04.2024

420

No

036

15.05.2024

04.06.2024

15.05.2024

 294

No

      • No

        • In the OC, the preparation for calling the service for reporting the insurance policy (reporting addition)

          ,

          continues with the process of transferring the change copy

          continues

  • To unsubscribe from an insurance policy online, the system checks whether the insurance contract includes:

    • OnLine Reporting = Yes

    • Insurance Company Check-out Date = blank

    • Termination Code = non-empty, or Early Termination = Yes

  • When there is an insurance policy that meets these conditions, it checks:

    • If the policy says Valid To < the current date. If:

      • Yes

        • Checks on Termination Code whether it has Allowed to terminate retroactively = Yes. If:

          • Yes

            o Preparation for calling the service to unsubscribe the insurance policy (attrition reporting). The proclamation takes place in the background.

          • No or Termination Code is not filled in

            o Displays the error message "Insurance XXX. Valid to must be>= current date!" and the change copy transfer stops

      • No

        • Preparation for calling the service to unsubscribe the insurance policy (report attrition). The proclamation takes place in the background.

  • If there is no policy on the contract that meets the conditions for unsubscribing or reporting, it proceeds to the next check

  • Checking the Strict Changes List Policy flag in OneCore Setup:

    • If n

      • On the last line in the Contract Change History, toggles:

        • flag Closed on Y

        • Customer Approval flag on Y

        • Cust.Approval Date=sysdate

        • add date Approved On=sysdate

    • If Y

      • Checks if the flag is Closed=Y (i.e. it was toggled by the user to approve the change before the transfer)

      •  If Y

        • Performs a change copy transfer

      • If n

        • Displays a message and does not transfer the change copy:

          image-20240619-110911.png
        • The user then opens the Contract Change History on the change copy, closes the line, and transfers the change copy.

  • Change Copy Transfer

    • Before transferring, the system adds the following changes to the line:

      • Financing Period-New from the Financing Period (in Month) field from the change copy

    • In the ReplacebyChangeCopy function, the check is again:

      • Service-Updated (150)=Y and

      • Insurance-Updated (151)=Y and

      • Payments-Updated (152)=Y and

      • Calculation Lines-Updated=Y and Complete Calculation=Y– all must be Y, otherwise they will display the message:

        • Changes requiring recalculation have been made to the change copy. Please run recalculation before transferring the change copy.

    • The system copies all the data of the change copy to the original, then deletes the change copy

    • If it is a Leasing with delivery of goods=Y, the contract has been transferred and a corrective VAT document for the original and a new document for the new customer have been created, then the system will post these documents when transferring the change copy. See also Převod smlouvy s dodáním zboží na jiného zákazníka and Převod smlouvy

    • On the original contract, he sets:

      • Change Copy Exists=N

      • Change Copy=N

      • Last Change Code from Last Line of Contract Change History

      • Adds the date and time of the last modification.

...