Create a new contract
There is the following process for creating a contract for the specified application:
-
First, a ticket is created. You can find a description of creating an application here . Please note that when creating an order in the channel of receipt, you must uncheck the "Automatic creation of a contract" (Admin -> E-commerce -> Channels -> Channel Name).
-
Then initialization of the contract on the loan application occurs.
-> 3. The last step is creating a new contract . The JSON file created in the previous step is inserted into the request body
Request Body
Additional
Barcode
Branch ID
"int64"Captive
Client ID
"int64""int64"Comment
Agent ID
"int64"Collector ID
"int64"Creation date in YYYY format -MM-DD
"date"Loan conditions
"double"Do not carry over from holidays and weekends (Yes / No)
Possibility of repayment before maturity upon auto-acceptance (Yes / No)
"double"the first day of accrual of additional interest on overdue fixed assets
"int32"last day of accrual of additional interest on overdue fixed assets
"int32"charge additional interest on overdue fixed assets (as a separate type of amount)
accrue interest on the day the contract is issued (in this case, interest is accrued on both the first and last days of the tranche)
Accrue interest on overdue fixed assets (Yes / No)
Penalty on calendar days (Yes / No)
Accrue interest at the end of the loan term (Yes / No)
Credit line type
"int64"Method for calculating dates
"int64"Day of delay for calculating late penalties
"int32""int32"Number of days before switching to a rate in case of delay. If the delinqIntRateDelay field has a value of 0, then the interest rate in case of delay is used from the first day of interest accrual on the tranche (if there is a delay in the previous tranches), otherwise, the usual interest rate will continue to operate from the beginning of the tranche for the specified number of days
"int32"Interest rate on delay
"double"Discounting activated
Early renewal from the current date (Yes / No) (otherwise, prolongation from the end date of the current tranche)
"int32"Fees
Do not charge first weekend penalties
Late Penalty (Fixed Amount)
"double"Prepayment offset method
"int64"Full shift of the schedule from the actual date of issue (Yes / No)
Loan product identifier
"int64"rate in the first period
"double"rate in the second period
"double""int64"Interest method
"int64"Interest rate
"double"Grace period (without interest accrued for this period)
"int32"Deferred grace period (in days)
"int32""double"Calculate percentage of the amount in the contract
Interest rate type
"int64"Percentage of the issue amount (by which we determine whether to consider it as a friend)
"double"Reduced interest rate for each friend
"double"Minimum interest rate
"double""int32"Mandatory interest period
"int32""double""LOAN_AMOUNT_PERCENTAGE_PER_YEAR""double""FROM_DELINQUENCY_START_BY_STATUS""FROM_TRANCHE_REPAYMENT_DATE"Penalty rates
Type of fines calculation
"int64""int64"Parts of the principal
Prolongation period (Specified in days)
"int32"Number of days after the end of the schedule until the fines stop
"int32"number of tranches in the first period
"int32"Number of tranches to calculate the second period repayment rate. Now it makes sense to display this field only when the interest calculation method is selected (parameter interestCalcMethodId) Remaining with two rates (101226). If this field is greater than zero, then when calculating the schedule for the second period, the repayment rate is calculated based on the specified number of tranches, the calculated repayment rate is stored in the contract
"int32"number of tranches in the second period
"int32"Maturity rate
"double"Order of repayment
"int64"To recalculate the schedule to the budget billing date (Yes / No)
Shift the date of the first repayment to the next business day when calculating
Control of short-term (adjusting the date of the last repayment so that the term of the contract does not exceed 1 year)
Stop penalties after the end of the schedule (Yes / No)
Number of tranches
"int32"The length of the period between redemptions
"int32"Use the interest rate on arrears to calculate the UCI.
If the contract under this field is YES, and the interest rate on arrears is not zero, then when calculating the UCI for the contract, a schedule is created taking into account the interest rate for arrears and UCI is calculated from this schedule
Return to regular interest rate from the next tranche after the delay is repaid. If the useDelinqIntRateTillNextTranche field = YES (true), then the return to the regular rate after the delay is repaid will be from the beginning of the next tranche, if NO (false) - from the next day after the delay is repaid
Use EPS for discounting (instead of CPM)
Loan Specialist ID
"int64"Loan product identifier
"int64"Credit product name
Currency identifier
"int64""date-time""date""int32""int32"Specified amount for distribution of prepayment by interest
"double""int64""int64"Date of withholding order
"date"Originals received
"int64""double"Estimated contribution (Rate)
"double"First maturity date in the format YYYY-MM-DD
"date"Fixed Estimated Contribution (Amount)
"double"Fixed Insurance Premium (Amount)
"double"Fixed entry fee (Amount)
"double"Flag "For issue"
"int64""date-time""double"Contract ID ( when creating a new contract - you do not need to specify it )
"int64"Date of delivery on initiation
"date"Insurance
Insurance premium (Rate)
"double"Insurance policy
Insurance premium amount
"double"Insurance premium rate
"double"Scheduled issue date in the format YYYY-MM-DD
"date"Entry Fee (Rate)
"double"Upload date (if the contract was transferred from a third-party accounting system). Upload date This field automatically records the contract migration date. In this case, the field Loading date = the date on which we load the balances. All settlement of the contract will start from this date. If the contract was created in BS (not migrated), then the field will be NULL
"date"Loan amount
"double"Loan Application ID
"int64"Loan category identifier
"int64"Loan stage.
The mechanism for setting loanStage is as follows:
the loanStage parameter is set to the loan stage (1, 2, 3 ... etc.). When creating a new loan application (if it is the first for this client), this field is filled with the value 1. If the application is approved, then in the contract this field will contain 1 value 2 (step 2), provided that the first application for this client was approved.
Example:
an application with a step 3 is created, the application goes to the decision making system (which will be pre-configured in the system), there an expression will be executed that will apply the loan product that corresponds to the stage of the loan. When the application is approved in the decision-making system, the value of the loanStage parameter in the contract will be set to 3
"int32"Seller Commission Rate
"double""double"IFRS reserve rate
"double"Contract number
Offer code
"int64""int32"Previous number of renewals / restructurings (when transferring from a third-party accounting system)
"int32"Repayment rate
"double"Scheduled maturity date in the format YYYY-MM-DD
"date"Department ID
"int64""double"Flag of the Code of Laws
Claim amount of debt
"double"Date of appeal to court
"date""date"Responses
OK
Additional
The schedule was calculated automatically when issuing
Barcode
"int64"Captive
"int64"Client ID
"int64"Contract closing date
"date-time"Contract closing status identifier: - ** 101481 ** - Suppressed ** 101482 ** - Restructured - ** 101483 ** - Decommissioned - ** 101484 ** - Corrected - ** 101485 ** - Decommissioned by assignment - ** 101486 ** - Canceled
"int64""int64"Comment
Result of the NewOutgoing request by the Contact service
Date + time of successful execution of the NewOutgoing request
"date-time"Contact transfer receipt code (if not empty - PayOutgoing request was successful)
"int64"Collector ID
"int64"Sequence violation line
"int64"Department ID of the user who created the contract
"int64"User ID who created the contract
"int32"Creation date in YYYY format -MM-DD
"date"Loan conditions
"int64""int64"Credit product name
"int64"The current system status of the contract. Possible values can be viewed in the Status History method
"int64""date-time""date""int32""int32"Specified amount for distribution of prepayment by interest
"double""int64""int64"Date of withholding order in YYYY-MM-DD format
"date"Originals received
"int64"Full maturity date
"date-time""double""double"EPS (for the investor). The field was added in the 2.0.0-69 release in metadata as read-only (cannot be changed from the interface)
"double"Estimated contribution (Rate)
"double"First maturity date in the format YYYY-MM-DD
"date"Fixed Estimated Contribution (Amount)
"double"Fixed Insurance Premium (Amount)
"double"Fixed entry fee (Amount)
"double"Flag "For issue"
"int64""date-time"UCS
"double""double""int64"Contract ID ( when creating a new contract - you do not need to specify it )
"int64"Is the contract indexed (currency)
Date of delivery on initiation
"date"Insurance
Insurance premium (Rate)
"double"Insurance policy
Insurance premium amount
"double"Insurance premium rate
"double"Date of issue of the contract
"date-time"In the process of issuing
Scheduled issue date in the format YYYY-MM-DD
"date"Entry Fee (Rate)
"double""date"Upload date (if the contract was transferred from a third-party accounting system). Upload date This field automatically records the contract migration date. In this case, the field Loading date = the date on which we load the balances. All settlement of the contract will start from this date. If the contract was created in BS (not migrated), then the field will be NULL
"date"Loan amount
"double"Loan Application ID
"int64""int64"Loan stage.
The mechanism for setting loanStage is as follows:
the loanStage parameter is set to the loan stage (1, 2, 3 ... etc.). When creating a new loan application (if it is the first for this client), this field is filled with the value 1. If the application is approved, then in the contract this field will contain 1 value 2 (step 2), provided that the first application for this client was approved.
Example:
an application with a step 3 is created, the application goes to the decision making system (which will be pre-configured in the system), there an expression will be executed that will apply the loan product that corresponds to the stage of the loan. When the application is approved in the decision-making system, the value of the loanStage parameter in the contract will be set to 3
"int32"Market rate. The field was added in the 2.0.0-69 release in metadata as read-only (cannot be changed from the interface)
"double"Seller Commission Rate
"double""double"IFRS reserve rate
"double"Contract number
Offer code
"int64""int32"Previous number of renewals / restructurings (when transferring from a third-party accounting system)
"int32"Has been extended
Repayment rate
"double"Scheduled maturity date in the format YYYY-MM-DD
"date"Link to the restructured contract
"int64"Charts
"int64""double"Flag of the Code of Laws
Claim amount of debt
"double"Date of appeal to court
"date""date""error""ok""int64"