Method for creating a receipt DDS by client GUID
The method creates a credit DDS according to the client's GUID (for a unit contract with the Customer account attribute).
The logic of the method is as follows. The required fields are checked, a client is searched for according to the specified clientGuid, for this client we are looking for an active share contract with the Additional and Client account signs set, and the incoming DDS is saved for this contract (without auto-acceptance). For a description of possible errors, see this link /documentation/article/272
Request Body
Amount
Calculated interest in foreign currency
"double"Calculated interest in national currency
"double"Checkout Id . This parameter is conditionally required. Passed if the value 101172 - Checkout is passed in the paymentTypeId parameter
"int64"client GUID. You need to pass the values that are passed in the borrower.guid parameter in the " Method for creating a client, application, contract ... (Revo) "
Comment
DDS date and time in unix timestamp format in milliseconds. If the field is not specified, the current date and time are used
"date-time"DDS number. If this parameter is not specified, then this number is generated automatically when the DDS is saved
"int64"Id Settlement / accounts from the reference " Banks "
"int64"Responses
OK
Account and reference number accounts . Mandatory for external DDS (if the externalAction flag is present). For internal DDS, the parameter value is taken from the directory automatically and does not need to be passed
"int64"Amount. Specified in local and foreign currencies. If the redemption occurred only in one currency (local) - amount. foreign indicated = 0
Cash flow type identifier:
101781 - Receipt
101782 - Expense
"int64"Cashier where the cash flow took place. The field is conditionally required, as it is transmitted only in case of cash payments
"int64"An accountable person is an employee who is responsible for funds. Started by the system user as a client. It is used when carrying out DDS mainly of the "Expense" type, the value is taken from the reference book " clients ". Required (if the externalAction flag is present). This field is needed to provide information about the reporting person who records the expense or receipt through the cashier or bank account
"int64"Comment. Optional field
Id of the transaction in the Contact system. This field is retained for backward compatibility and is marked for deletion. Do not use
"int64""int64"Check sum
Id of the user who created the DDS
"int32"Maturity date in the format YYYY-MM-DD. This field is reserved for backward compatibility. It is recommended to use the dateTime field.
If only the date field is specified when creating a DDS, then the DDS will be saved without time. If both fields are specified, the dateTime field will take precedence. Since the date and time are used. The date field will be ignored in this case.
These changes are important. These changes concern auto-acceptance. If DDS is saved over time, then DDS time will be used to create transactions during auto-acceptance. If DDS was saved without time, then the current system time will be substituted during auto-acceptance
"date"DDS date and time in unix timestamp format in milliseconds. See also the description of the date parameter
"date-time"The sign of the "external" DDS. External DDS is the movement of money that does not relate to the lending activities of the organization. The field is conditionally required
Identifier
"int64"sys transaction id Leader. This field is retained for backward compatibility and is marked for deletion. Do not use
sys no of transaction Leader. This field is retained for backward compatibility and is marked for deletion. Do not use
"int64"The second Cashier , along which the funds were moved during external DDS (parameter associated with cashOfficeId, however is for informational purposes only, does not mean automatic creation at the specified cash register). Required (if the externalAction flag is present)
"int64"Payment order number, transaction number within the payment system. When creating a new DDS, it is filled in automatically, if the value is not passed
Id of transaction in OSMP. This field is retained for backward compatibility and is marked for deletion. Do not use
"int64"Payment method. Possible values:
101171 - non-cash payment,
101172 - cash,
101173 - other
"int64"Account number from the reference book banks through which the money flows. If through the cashier (cash), it is not required
"int64""error""ok""int64"