...
Global Dimension 2 Activation
By checking this box, the user activates the use of the contract number as the 2nd global dimension across the entire system.
The default setting is YES.
Contract Dimension (Leasing)
In this field, you must set up the dimension code of the leasing module where the system will store the contract number.
VAT Rounding Code
The setting determines how the system will round VAT in the financing module, such as VAT in the service payment calendar.
If the VAT rounding code is set to 4 decimal places, but the rounding of payments is to 2 decimal places, then when posting the payment, the system creates a Rounding line in the invoice lines, in which it posts the deviations that have arisen.
If the field is blank, the system takes the VAT rounding from the General Ledger Setup from the Amount Rounding Precision field (recommended setting).
Posting Group Priority
This parameter affects the way in which the system fills in the business posting groups on the contract. The setting options are:
From Template
The system will always use the business posting groups from the contract template. If they are empty on the pattern, the system reports an error.
From Customer
Adds the General Bus/Posting Group, VAT Bus/Posting Group, and Customer Posting Group fields from the customer card, regardless of the posting groups that are set up on the contract template.
Ak je na vzore v účtoskupine pro Indiv. The system copies the invoice blank value when validating the customer on the contract, to the contract card, to the Posting group field for Indiv. Customer Invoice Posting Group
From Customer When Empty Contract
gradually adds the fields General Bus. Posting Group, VAT Bus-Posting Group, Customer Posting Group from the customer's card, if the field is empty on the contract (each field is evaluated separately).
The system, when validating the customer on the contract, copies it to the contract card, to the Posting group field for Indiv. Customer Invoice Posting Group
VAT Bus. Post. Group from Customer
field VAT Bus. Posting Group From Customer=Yes, completes the VAT Bus. Posting Group field from the customer's card, regardless of what the current value is, regardless of the setting of the Posting Group Priority field
This setting turns on the override of the VAT business posting group in the header of the financing contract when the customer number is filled with the VAT code of the business posting group on the customer card.
This option is used where it is necessary to distinguish between domestic taxable payers and domestic non-taxable payers in the VAT control statement.
Shift Posting Date of Sales Invoice To Open Period
If checked, then when fulfilling the "Posting Date" in the invoice, the system checks whether the "Posting Period" from the payment or in case of cancellation from the copy of the document is closed. If this period is closed, then the 1st day of the open period is filled in by the posting date. The changed "posting date" will then be written into the payment (calendar line from which we post).
Paym. Posting Selection Method)
The user selects the method of selecting payments to be posted within the batch for mass payment invoicing (Month/Day) see description in the Calculation tab, Decisive field for payment invoicing, see PD Customer Invoicing
Used for contracts that have contracts with services=N
Decisive day for mass payment invoicing (Determ. Day for Payments Batch Posting)
A numeric field to fill in the number in days.
The field is used:
in the Batch Payment Posting task (planner without services) To filter the payments that will be charged:
In OneCore Settings, in the Method of Selecting Payments to Post, if the value is:
Day: takes a work date, adds the value in the Decisive day field for mass payment posting, and gets a new date. Then it filters the payments so that the posting date must be <= the date thus obtained.
B.C. User work date or system date for scheduler = 19.12. The set decisive date is 20. The system calculates 19.12 + 20days = 9.1. It filters all payments that have Posting Date <= 9.1. and posts them
Moon: if the serial number of the day from the working date is >= Decisive price for mass payment posting, then it filters to the posting date of payments until the end of the next month. If < Decisive price for mass payment posting, it filters the payments to the end of the current month.
B.C. User work date or system date for scheduler = 19.12. The set decisive date is 20. The system invoices all payments in a given month.
If the Work date was 21.12, which is more like the Decisive date i.e. 20, the system charges the installments of the following month.
in Task Batch – CI and Accr. Posting Scheduler
if the value is Day in the Payment Posting Selection Method field in OneCore Settings, it takes the working date, adds the value in the Decisive Price field for mass payment posting and gets a new date. It then filters the accrual lines so that the posting date must be <= the date thus obtained.
Migration Date
If the implementation of the OC also involves the migration of existing contracts from the original system of the leasing company, it is recommended to enter the date of the final migration (the last day of posting in the source system).
Check Reason Code in Posting
If Y, the system checks whether the Reason Code is filled in during posting (the list of documents and tasks in which the check is applied is given in PD General Ledger Setup Kódy příčiny(Reason Codes)
Tolerances for creating a document from GAC (LCY)
This is an amount that is a tolerance within which the user is asked to create an invoice/credit note when manually posting from GA. The system puts the value of the Amount field from the SPK into an absolute value and then compares whether this value is less than or equal to this tolerance
The tolerance value is entered as positive
It is recommended to enter a value around zero (e.g. 0.2)
...
The tab is used to set the default values for automatic creation of an opportunity before the contract termination (functionality described in PD Adresář_OC_CZ in the current version Address book)
Field:
Default Period Before Contract Termination
E.g.: 6M. According to this setting, we will be able to calculate the start date of the task to create an automatic opportunity for Contract renewal
Default Renewal Opportunity Type
When you click on the field, you can see the values from the Opportunity Types table. The user selects the Opportunity Type Code that they want to use for Renewal. The set value is tightened to the "Opportunity Type" field on the opportunity card after the automatic creation of the Renewal opportunity
Default Renewal Sales Cycle Code
When you click on the field, you can see the values from the Sales Cycles table. The user selects the Sales cycle type code for contract renewal, which has a value of = Renewal in the "Type" field
The set value is tightened to the Sales Cycle Type field on the opportunity card when automatically creating a Renewal opportunity
...