Transaction splitting method, device and computer program product

Abstract

The invention discloses a transaction splitting method and device and a computer program product, and relates to the technical field of financial engineering, and the method comprises the steps: obtaining a transaction instruction record of a superior product and a corresponding subordinate product list; and splitting the transaction amount to each subordinate product according to the transaction instruction record and the subordinate product list to obtain a transaction splitting scheme of each subordinate product. The transaction amount is intelligently split according to the superior product transaction instruction record and the subordinate product list, a specific transaction splitting scheme is generated for each subordinate product, manual intervention in the calculation process is reduced, and the speed of bank asset escrow superior product transaction splitting is increased.

Description

Technical Field

[0001] The present application relates to the field of financial engineering technology, and in particular to a transaction splitting method, device and computer program product. Background Art

[0002] There is a hierarchical relationship among bank asset custody products. When existing superior products are conducting inter-bank transactions, custody and clearing personnel are required to calculate the split amounts of each subordinate product and split the transaction amounts into subordinate products. The manual calculation of the details of the split amounts of each subordinate product is complicated, the labor cost is high, and the transaction splitting speed is slow.

[0003] Therefore, how to quickly split the transaction amount of the bank's asset custody parent products and obtain a specific transaction splitting plan has become an issue that needs to be solved urgently.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a transaction splitting method, device and computer program product, aiming to solve the technical problem of how to quickly split the transaction amount of bank asset custody parent products and obtain a specific transaction splitting plan.

[0006] To achieve the above objectives, the present application proposes a transaction splitting method, which comprises:

[0007] Obtain the transaction instruction records of the upper-level product and the corresponding lower-level product list;

[0008] The transaction amount is split into each subordinate product according to the transaction instruction record and the subordinate product list to obtain a transaction splitting plan for each subordinate product.

[0009] In one embodiment, the step of splitting the transaction amount into each subordinate product according to the transaction instruction record and the subordinate product list to obtain a transaction splitting plan for each subordinate product includes:

[0010] Obtaining the transaction amount of the upper-level product according to the transaction instruction record;

[0011] Determining whether a subordinate product is a repurchase transaction product based on the subordinate product list;

[0012] If yes, the transaction amount is split into the subordinate products according to the preset repurchase transaction rules to obtain the first split amount details;

[0013] If not, intelligently calculate the transaction amount according to the transaction instruction record and the list of subordinate products, split the transaction amount into the subordinate products, and obtain a second split amount detail;

[0014] A transaction splitting plan for each subordinate product is obtained based on the first splitting amount details and the second splitting amount details.

[0015] In one embodiment, after the step of splitting the transaction amount into each subordinate product according to the transaction instruction record and the subordinate product list to obtain the transaction splitting plan for each subordinate product, the step further includes:

[0016] The transaction splitting plan is verified based on the preset verification process and the transaction instruction record, and the transaction splitting plan with a passed verification result is submitted, and the transaction splitting plan with a failed verification result is reported as an error.

[0017] In one embodiment, the step of verifying the transaction splitting scheme based on the preset verification process and the transaction instruction record, submitting the transaction splitting scheme with a passed verification result, and reporting an error for the transaction splitting scheme with a failed verification result also includes:

[0018] Determine whether the subordinate product is a spot sale product or a positive repurchase product based on the subordinate product list;

[0019] If yes, query the subordinate product and decide whether to enter the preset verification process according to the query result;

[0020] If not, the preset verification process is entered based on the transaction splitting plan and the transaction instruction record.

[0021] In one embodiment, the step of verifying the transaction splitting scheme based on the preset verification process and the transaction instruction record, submitting the transaction splitting scheme with a passed verification result, and reporting an error for the transaction splitting scheme with a failed verification result also includes:

[0022] Obtain historical transaction records of bank asset custody products;

[0023] Construct a verification process based on the historical transaction records of the bank's asset custody products.

[0024] In one embodiment, the steps of verifying the transaction splitting scheme based on the preset verification process and the transaction instruction record, submitting the transaction splitting scheme with a passed verification result, and reporting an error verification result of the transaction splitting scheme with a failed verification result include:

[0025] Verify the transaction splitting scheme based on a preset verification process to determine whether the transaction amount is split into the same subordinate product;

[0026] If yes, the verification result is determined to be failed, and an error is reported for the transaction splitting plan;

[0027] If not, the transaction splitting plan is verified based on the transaction instruction record and the verification process to determine whether the bond codes are consistent. The transaction splitting plan with a passed verification result is submitted, and the transaction splitting plan with a failed verification result is reported as an error.

[0028] In one embodiment, if not, then verifying the transaction splitting plan based on the transaction instruction record and the verification process, determining whether the bond codes are consistent, submitting the transaction splitting plan with a passed verification result, and reporting an error for the transaction splitting plan with a failed verification result includes:

[0029] Verifying the transaction splitting plan based on the transaction instruction record and the verification process to determine whether the bond codes are consistent;

[0030] If not, the verification result is determined to be failed, and an error is reported for the transaction splitting plan;

[0031] If so, the transaction splitting plan is verified based on the transaction instruction record and the verification process to determine whether the tail difference exists. The transaction splitting plan with a passed verification result is submitted, and the transaction splitting plan with a failed verification result is reported as an error.

[0032] In one embodiment, if so, the transaction splitting scheme is verified based on the transaction instruction record and the verification process to determine whether there is a tail difference, and the transaction splitting scheme with a passed verification result is submitted, and the transaction splitting scheme with a failed verification result is reported as an error, and the steps include:

[0033] Obtaining a split total amount according to the transaction split plan;

[0034] Verify the transaction splitting plan based on the transaction instruction record and the verification process to determine whether there is a tail difference;

[0035] If not, verify whether the split total is equal to the transaction amount based on the verification process, submit the transaction splitting plan if the verification result is yes, and report the transaction splitting plan if the verification result is no;

[0036] If so, the tail difference is automatically processed, the verification result is determined to be passed, and the transaction splitting plan is submitted.

[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a transaction splitting device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the transaction splitting method described above.

[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the transaction splitting method described above are implemented.

[0039] One or more technical solutions proposed in this application have at least the following technical effects:

[0040] According to the acquired transaction instruction records of the upper-level products and the corresponding list of lower-level products, the transaction amount is intelligently split, and a specific transaction splitting plan is generated for each lower-level product, reducing manual intervention in the calculation process and improving the speed of transaction splitting of the upper-level products of bank asset custody. Therefore, the intelligent and automatic splitting of the transaction amount according to the transaction instruction records and the list of lower-level products can realize the rapid splitting of the transaction amount of the upper-level products of bank asset custody. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0042] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0043] Figure 1 A flowchart of the first embodiment of the transaction splitting method of the present application is provided;

[0044] Figure 2 A flowchart of the second embodiment of the transaction splitting method of the present application is provided;

[0045] Figure 3 A flowchart of the third embodiment of the transaction splitting method of the present application is provided;

[0046] Figure 4 A flowchart of the fourth embodiment of the transaction splitting method of the present application is provided;

[0047] Figure 5 A flowchart of the fifth embodiment of the transaction splitting method of the present application is provided;

[0048] Figure 6 This is a schematic diagram of the overall process of the transaction splitting method for this application;

[0049] Figure 7 This is a schematic diagram of the module structure of the transaction splitting device according to an embodiment of the present application;

[0050] Figure 8 This is a schematic diagram of the device structure of the hardware operating environment involved in the transaction splitting method in the embodiment of the present application.

[0051] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0052] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0053] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0054] The main solution of the embodiment of the present application is: by obtaining the transaction instruction records of the upper-level products and the corresponding list of lower-level products, the total transaction amount of the upper-level products is intelligently split, and a transaction splitting plan for each lower-level product is generated to improve the processing efficiency of inter-bank transactions.

[0055] The embodiments of the present application take into account that since there is an obvious upper-lower level relationship between bank asset custody products, when the upper-level products are traded between banks, the custody and clearing personnel are required to manually calculate the split amount details of each lower-level product. However, the manual calculation process is complicated, resulting in low splitting efficiency.

[0056] Therefore, this application provides a solution. By obtaining the transaction instruction records of the upper-level products and the corresponding list of lower-level products, the total transaction amount of the upper-level products is intelligently split on the manager side, and a transaction splitting plan for each lower-level product is generated. By intelligently splitting the transaction amount, the transaction amount is allocated to the lower-level products according to the intelligent calculation results, reducing manual intervention and increasing the speed of transaction splitting. Therefore, intelligent splitting on the manager side realizes the rapid splitting of the transaction amount of the upper-level products of bank asset custody, and improves the processing efficiency of inter-bank transactions.

[0057] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a hosting comprehensive service platform, etc. The following takes the hosting comprehensive service platform as an example to illustrate this embodiment and the following embodiments.

[0058] Based on this, the present application embodiment provides a transaction splitting method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the transaction splitting method of the present application.

[0059] In this embodiment, the transaction splitting method includes steps S10 to S20:

[0060] Step S10, obtaining the transaction instruction record of the upper-level product and the corresponding lower-level product list;

[0061] In the hierarchical relationship of bank asset custody products, the upper-level product usually refers to a larger investment portfolio or collective product that includes multiple lower-level products, such as collective asset management plans, funds, trust plans or other similar collective investment tools.

[0062] Subordinate products are subdivisions of superior products, representing different investment directions and asset categories in superior products. In interbank transactions, the transaction amount of superior products needs to be split into different subordinate products to ensure that subordinate products can obtain corresponding investment returns and risk management effects.

[0063] The transaction instruction record includes information about the transaction parties, transaction types, transaction amounts, transaction methods, and other record information that instructs the subsequent transaction process. The list of subordinate products includes a series of product information about the subordinate products, such as the product name, product code, asset type, and legal documents.

[0064] The custodial comprehensive service platform first connects to the trading system through the preset API interface and uses the manager's authentication information to log in to the trading system.

[0065] Furthermore, the upper-level products meeting the query conditions are searched in the transaction system according to the preset query conditions. The preset query conditions include: the upper-level products have not been split, the transaction split date is the query date or after the query date, and the upper-level products in the in-process split mode require the instruction workflow node to be in the accounting handling or instruction error correction.

[0066] Further, the corresponding lower-level products are queried in the transaction system according to the instruction transaction records that meet the query conditions to obtain detailed information of the lower-level products. The detailed information is tabulated to obtain a list of lower-level products corresponding to the upper-level products.

[0067] In order to facilitate the subsequent splitting of transaction amounts, the transaction instruction records and the corresponding subordinate product lists are organized into a certain data structure, and then encapsulated into a JSON format response according to this data structure. To obtain the transaction instruction records and subordinate product lists of different upper-level products, it is only necessary to send a request through the HTTP response protocol, without the need to repeatedly log in to the transaction system for query and collection.

[0068] Step S20, splitting the transaction amount into each subordinate product according to the transaction instruction record and the subordinate product list, and obtaining a transaction splitting plan for each subordinate product.

[0069] The transaction instruction record contains the total transaction amount of the upper-level product, and the lower-level product list contains detailed information of the lower-level products. The split amount is calculated and allocated based on the transaction instruction record and the lower-level product list, and the transaction amount is split to each lower-level product according to the intelligent calculation results to obtain a specific transaction split plan for each lower-level product.

[0070] Specifically, as a feasible implementation, the step S20 of splitting the transaction amount into each subordinate product according to the transaction instruction record and the subordinate product list to obtain the transaction splitting plan for each subordinate product may include:

[0071] Extract characteristic factors that affect the split of transaction amounts from transaction instruction records and subordinate product lists, such as profit margin, risk level, etc. Select and transform characteristic factors according to business needs and goals to adapt to subsequent intelligent algorithm processing.

[0072] Furthermore, random forest is selected as the intelligent algorithm processing framework. The historical transaction data and split results are used as training data to train the random forest intelligent algorithm processing framework, so as to adjust the parameters and hyperparameters of the model and optimize the performance of the model.

[0073] Furthermore, the model considers the setting of the priority and weight of the characteristic factors, for example, prioritizing the subordinate products according to their profit margins. By combining the preset business requirements and constraints, the trained model evaluates and predicts the new transaction instruction records and the list of subordinate products, and obtains the split amount of each subordinate product and the transaction splitting plan of each subordinate product.

[0074] Furthermore, in order to avoid overfitting of the random forest intelligent algorithm framework, use validation data sets or real-time data for testing to evaluate the accuracy and efficiency of the algorithm. Based on the feedback of the test results, evaluate the accuracy and efficiency of the algorithm, and iterate and optimize the random forest intelligent algorithm framework based on the test results and feedback to improve the performance and adaptability of the algorithm.

[0075] It is understandable that in order for managers to more conveniently view and manage transaction splitting plans, the random forest intelligent algorithm framework can be integrated into the existing custody comprehensive service platform, a friendly user interface can be designed, and the operation of the custody comprehensive service platform can be monitored to ensure the stability and reliability of the platform.

[0076] In this embodiment, by constructing a random forest intelligent algorithm framework, the transaction amount is intelligently split into each subordinate product, thereby achieving rapid splitting of the transaction amount of the bank asset custody parent product, improving the processing efficiency of inter-bank transactions, and ensuring the accuracy of the splitting of the parent product transaction amount.

[0077] The above is only a feasible implementation of step S20 provided in this embodiment, and this embodiment does not specifically limit the specific implementation of step S20.

[0078] This embodiment provides a transaction splitting method, which intelligently splits the transaction amount according to the acquired upper-level product transaction instruction record and the corresponding lower-level product list, generates a specific transaction splitting plan for each lower-level product, reduces manual intervention in the calculation process, and improves the speed of splitting the bank asset custody upper-level product transaction. Therefore, the transaction amount is intelligently and automatically split according to the transaction instruction record and the lower-level product list, and the transaction amount of the bank asset custody upper-level product is quickly split.

[0079] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction and will not be repeated later.

[0080] On this basis, please refer to Figure 2 , Figure 2 This is a flow chart of the second embodiment of the transaction splitting method of the present application.

[0081] In this embodiment, the step S20 of splitting the transaction amount into each subordinate product according to the transaction instruction record and the subordinate product list to obtain the transaction splitting plan for each subordinate product may include steps S201 to S205:

[0082] Step S201, obtaining the transaction amount of the upper-level product according to the transaction instruction record;

[0083] Transaction instruction records contain the transaction amount of the parent product. Since transaction splitting is to split the transaction amount of the parent product into the lower-level products according to certain rules, transaction splitting requires using a query statement to obtain the transaction amount corresponding to the parent product from the transaction instruction record for subsequent transaction splitting.

[0084] Step S202, judging whether the subordinate product is a repurchase transaction product based on the subordinate product list;

[0085] Repo transactions refer to the sale of securities or other assets held by an enterprise or financial institution, and the agreement with the buyer to repurchase the securities or other assets at an agreed price at a certain time in the future. If a parent product is a repo transaction product, it does not mean that all the subordinate products corresponding to the parent product will automatically become repo transaction products.

[0086] Repurchase transactions are defined based on specific transaction contracts and terms, which are usually reached separately between the two parties to the transaction. The repurchase transaction attributes of the upper-level product will not be directly passed on to its lower-level products unless there is a clear agreement or provision in the relevant contract or agreement.

[0087] Because the price of repurchase transaction products is agreed in advance, in the process of splitting the transaction amount of the upper-level product, it is necessary to determine whether the specific lower-level product is a repurchase transaction product based on the lower-level product detailed information recorded in the lower-level product list, and give special treatment to the repurchase transaction product.

[0088] Step S203: If yes, the transaction amount is split into the subordinate products according to the preset repurchase transaction rules to obtain the first split amount details;

[0089] Traverse each subordinate product in the subordinate product list. If a subordinate product is a repurchase transaction product, since the repurchase transaction product defines the specific transaction details based on the specific transaction contract and terms, it is necessary to split the transaction amount to this subordinate product according to the repurchase transaction rules preset in the contract to obtain the split amount details of the subordinate product.

[0090] It should be noted that the preset repurchase transaction rules are set before the transaction splitting process, and the transaction amounts of the subordinate products serving as repurchase transaction products are split according to bond splitting or product splitting.

[0091] Step S204: if not, intelligently calculate the transaction amount according to the transaction instruction record and the list of subordinate products, split the transaction amount into the subordinate products, and obtain a second split amount detail;

[0092] Traverse each subordinate product in the subordinate product list. If a subordinate product is not a repurchase transaction product, there is no clear contract or terms for the subordinate product in advance that stipulates the specific split amount details. It is necessary to use the transaction instruction record and the subordinate product list to intelligently calculate the transaction amount, split the transaction amount into subordinate products, and obtain the split amount details of the non-repurchase transaction products in the subordinate product list.

[0093] Specifically, as a feasible implementation, if not, the transaction amount is intelligently calculated according to the transaction instruction record and the list of subordinate products, and the transaction amount is split into the subordinate products. Step S204 of obtaining the second split amount details may include:

[0094] Define specific splitting rules for the transaction amount based on the transaction instruction records and the list of subordinate products. For example, the transaction amount is allocated based on the proportion of each subordinate product in the total transaction amount. Another example is that the amount can be allocated based on the priority order of the subordinate products, and the products with higher priorities are given priority in allocating the transaction amount.

[0095] Furthermore, the key factors in the specific splitting rules are parameterized. For example, the proportion and priority are set as parameters, and the specific splitting rules can be adjusted by dynamically adjusting the parameters in the subsequent process.

[0096] Furthermore, the type of algorithm to be used is determined according to the parameters of the key factors of the specific splitting rule. For example, if it is a proportional splitting, a proportional allocation algorithm can be used; if it is a priority splitting, a greedy algorithm can be used. Python is selected as the writing language of the splitting algorithm, and the selected algorithm is implemented as a computer program for automatic calculation.

[0097] In this embodiment, the algorithm is implemented as a computer program by selecting the algorithm type and specific programming language. By inputting specific transaction instruction records and a list of subordinate products, the splitting algorithm automatically and intelligently calculates the split amount details of the subordinate products, and obtains the detailed split amount details of the subordinate products of non-repurchase products. Intelligent splitting is performed through the splitting algorithm to improve splitting efficiency and splitting accuracy.

[0098] The above is only a feasible implementation of step S204 provided in this embodiment, and this embodiment does not specifically limit the specific implementation of step S204.

[0099] Step S205, obtaining a transaction splitting plan for each subordinate product based on the first splitting amount details and the second splitting amount details.

[0100] Since the upper-level products correspond to different lower-level products, the lower-level products in the lower-level product list may be repurchase transaction products or may not be repurchase transaction products. The splitting rules for the split amount details of the lower-level products that are repurchase transaction products are based on product splitting or bond splitting, and the split amount details of the lower-level products that are not repurchase transaction products are determined by the intelligent splitting algorithm.

[0101] The transaction splitting plan for the upper-level product to split the lower-level product needs to be combined with the split amount details of the repurchased products and non-repurchased products to obtain a comprehensive transaction splitting plan. The transaction splitting plan details the split amount and product type of each lower-level product. After the manager submits the transaction splitting plan, the custodian clearing staff can directly perform the clearing operation according to the transaction splitting plan without manual splitting adjustment.

[0102] In this embodiment, the product type of the subordinate product is judged. If a subordinate product is a repurchase transaction product, it is split according to bonds or products to obtain the first split amount details of the repurchase transaction product; if a subordinate product is not a repurchase transaction product, it is intelligently split according to the transaction instruction record and the subordinate product list to obtain the second split amount details. Combined with the first split amount details and the second split amount details, a transaction splitting plan for the upper-level product is generated. The product type of the subordinate product is judged, and different types of products are subjected to different splitting operations, so as to achieve accurate splitting of the transaction amount of the bank asset custody upper-level product. At the same time, the intelligent calculation of the split amount improves the splitting speed, and the retention of the specific transaction splitting plan reduces the incidence of subsequent complaints.

[0103] Based on the first embodiment and / or the second embodiment of the present application, the third embodiment of the present application is proposed. In the third embodiment of the present application, the same or similar contents as those of the above-mentioned first and second embodiments can be referred to the above introduction, and will not be repeated in the following.

[0104] On this basis, please refer to Figure 3 , Figure 3 This is a flow chart of the third embodiment of the transaction splitting method of the present application.

[0105] In this embodiment, the transaction amount is split into each subordinate product according to the transaction instruction record and the subordinate product list, and the transaction splitting scheme of each subordinate product is obtained after step S20, which further includes step S30:

[0106] Step S30, verifying the transaction splitting scheme based on the preset verification process and the transaction instruction record, submitting the transaction splitting scheme with a passed verification result, and reporting an error verification result for the transaction splitting scheme with a failed verification result.

[0107] Since the transaction amount is intelligently calculated based on the transaction instruction record and the list of subordinate products, the transaction amount is split into subordinate products according to the result of the intelligent calculation to obtain the transaction splitting plan. In order to ensure the accuracy of the transaction splitting plan, the custody and clearing personnel can directly perform clearing operations according to the transaction splitting plan without additional manual inspection. The transaction splitting plan is automatically verified according to the preset verification process and transaction instruction records, which indirectly improves the speed of overall transaction splitting and the processing efficiency of inter-bank transactions.

[0108] The preset verification process is a verification process obtained by optimizing the process of historical verification of transaction splitting plans, including a series of verification process points such as verifying whether the transaction amount is split into the same subordinate product, verifying whether the bond codes are the same, verifying whether there is a tail difference, and verifying whether the total split amount is equal to the transaction amount after the tail difference is processed.

[0109] It should be noted that only when all verification process points in the verification process are passed, can the transaction splitting plan be submitted from the manager to the custodian liquidator. If any step in the verification process of the transaction splitting plan fails to pass the verification, the verification result will be failed, and an error will be reported directly in the custodian comprehensive service platform to remind the manager to check.

[0110] The transaction splitting plan is verified according to the preset verification process and transaction instruction records, the transaction splitting plan that passes all the verification process points is submitted, and the transaction splitting plan that fails to pass the verification process points is reported as an error.

[0111] In this embodiment, the transaction splitting plan is automatically verified through a preset verification process and transaction instruction records, and the transaction splitting plan that passes the verification is submitted. The custodian liquidator directly performs clearing operations based on the submitted verified splitting plan without the need for additional manual verification, and quickly completes the transaction splitting operation of the parent product, which not only improves the speed of transaction splitting, but also ensures the accuracy of the transaction splitting plan.

[0112] Based on the above embodiments of the present application, a fourth embodiment of the method of the present application is proposed. In the fourth embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be repeated in the following.

[0113] On this basis, please refer to Figure 4 , Figure 4 This is a flow chart of the fourth embodiment of the transaction splitting method of the present application.

[0114] In this embodiment, the transaction splitting scheme is verified based on the preset verification process and the transaction instruction record, and the transaction splitting scheme with a passed verification result is submitted. The transaction splitting scheme with a failed verification result is reported as an error before S30 also includes steps S231 to S233:

[0115] Step S231, judging whether the subordinate product is a spot sale product or a positive repurchase product based on the subordinate product list;

[0116] Repo is a type of repo transaction, which refers to an agreement between a financial institution or bank to purchase financial assets such as treasury bills and government bonds and repurchase them at a certain time in the future. The seller holds these assets during the agreed period and receives a certain amount of interest paid by the seller. Spot bond sales refer to the spot transaction between the two parties to transfer bonds at an agreed price, with one party selling the bonds.

[0117] In order to ensure that the cash sale products and repurchase products in the subordinate products comply with financial regulatory requirements after the transaction split, the position structure of the subordinate products after the transaction split needs to be queried. The number of positions of the cash sale products and repurchase products in the subordinate products needs to be queried. To query the number of positions of the cash sale products and repurchase products in the subordinate products, it is necessary to further determine whether the subordinate products are cash sale products or repurchase products based on the detailed information of the subordinate products recorded in the subordinate product list.

[0118] Step S232: If yes, query the lower-level product and decide whether to enter the preset verification process according to the query result;

[0119] If a subordinate product is a current securities sale product or a positive repurchase product, the number of positions of the subordinate product will be queried, and reminders will be displayed for subordinate products with insufficient positions. In order to ensure that the subordinate products can be traded smoothly after the transaction split, the transaction split plan corresponding to the subordinate product with insufficient positions cannot enter the preset verification process. Only when the manager handles the display reminder and queries again, and the number of positions of the subordinate product reaches a certain standard, will it enter the preset verification process.

[0120] For subordinate products whose holding quantity has reached the relevant standards during the initial query, the transaction splitting plan corresponding to this subordinate product is verified.

[0121] Step S233: if not, enter the preset verification process based on the transaction splitting plan and the transaction instruction record.

[0122] If a subordinate product is not a spot sale product or a positive repurchase product, after the transaction is split, there is no need to consider whether the spot sale product or the positive repurchase product violates relevant regulations and adjust the position structure. The preset verification process can be entered according to the specific transaction split plan and transaction instruction records.

[0123] In this embodiment, by traversing the list of subordinate products, it is determined whether the subordinate product is a positive repurchase product or a spot sale product, and an interface reminder is displayed for subordinate products with insufficient holdings to ensure that the subordinate products can be smoothly liquidated when performing liquidation operations according to the transaction splitting plan.

[0124] Based on the above embodiments of the present application, a fifth embodiment of the method of the present application is proposed. In the fifth embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be repeated in the following.

[0125] On this basis, please refer to Figure 5 , Figure 5 This is a flowchart of the fifth embodiment of the transaction splitting method of the present application.

[0126] In this embodiment, the transaction splitting scheme is verified based on the preset verification process and the transaction instruction record, and the transaction splitting scheme with a passed verification result is submitted. Before step S30 of reporting an error verification result of a transaction splitting scheme with a failed verification result, steps A1 to A2 are also included:

[0127] Step A1, obtaining historical transaction records of bank asset custody products;

[0128] Since the historical transaction records of bank asset custody products contain a large amount of actual transaction data, these actual transaction data can reflect the real transaction situation and possible problems. By analyzing these data, a more accurate and practical verification process can be constructed, thereby improving the accuracy of the verification of the transaction splitting plan.

[0129] Before verifying the transaction splitting plan according to the preset verification process, it is necessary to first obtain the historical transaction records of the bank's asset custody products in order to build a verification process based on historical transaction records. The historical transaction records of the bank's asset custody products can be obtained by querying the database used by the bank's internal system to store and manage various data through a database query language. Alternatively, the historical transaction records of the bank's asset custody products can be obtained from the bank's API interface programmatically.

[0130] Step A2: construct a verification process based on the historical transaction records of the bank asset custody product.

[0131] Conduct in-depth analysis of the collected historical transaction records to identify common patterns, anomalies and potential risk points in transaction splitting. Set verification points for the anomalies and potential risk points that may exist in the transaction splitting process. Only transaction splitting plans that pass all verification points can be submitted to the custodian and liquidator. If one verification point fails during the verification process, the transaction splitting plan cannot be submitted to the custodian and liquidator for liquidation operations.

[0132] In this embodiment, a more complete and accurate verification process is constructed by obtaining the historical transaction records of bank asset custody products to ensure the accuracy of the transaction splitting plan. The automated verification process reduces human participation and manual operations, reduces the risk of human errors, improves the efficiency of bank transaction processing, and realizes the rapid splitting of the transaction amount of the bank asset custody parent product.

[0133] Based on the above embodiments of the present application, a sixth embodiment of the present application is proposed. In the sixth embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be described in detail later.

[0134] In this embodiment, the transaction splitting scheme is verified based on the preset verification process and the transaction instruction record, and the transaction splitting scheme with a passed verification result is submitted, and the transaction splitting scheme with a failed verification result is reported as step S30, which includes steps S301 to S303:

[0135] Step S301, verifying the transaction splitting scheme based on a preset verification process to determine whether the transaction amount is split into the same subordinate product;

[0136] Determining whether the transaction amount is split into the same lower-level product is the first verification process point of the preset verification process for verifying the transaction splitting plan. The transaction splitting plan that passes this verification process point will be verified at the next verification process point. The verification result of the transaction splitting plan that fails this verification process point is considered to have failed. An error is directly reported for the transaction splitting plan with a failed verification result.

[0137] The transaction splitting plan contains the details of the split amount of each subordinate product. In order to ensure that the transaction amount is reasonably allocated to each subordinate product, the accuracy of the transaction splitting plan is verified, and it is determined whether the transaction amount is split into the same subordinate product based on the transaction splitting plan. According to the judgment result, an error is reported for the transaction splitting plan that fails the verification, and the verification splitting plan that passes this verification is further verified.

[0138] Step S302: If yes, determine that the verification result is not passed, and report an error for the transaction splitting plan;

[0139] If the transaction amount is split into the same lower-level product, it means that the transaction splitting plan is unreasonable, and the verification result of this process verification point is failed. The transaction splitting plan that fails this process verification point will be directly reported as an error.

[0140] Step S303, if not, verify the transaction splitting plan based on the transaction instruction record and the verification process to determine whether the bond codes are consistent, submit the transaction splitting plan with a passed verification result, and report an error if the transaction splitting plan has a failed verification result.

[0141] If the transaction amount is not split into the same lower-level product, the transaction splitting plan passes the verification of the first verification process point. The transaction splitting plan can be further verified according to the transaction instruction record and the verification process to determine whether the instruction bond code in the transaction instruction record and the split bond code in the transaction splitting plan are consistent. According to the further verification results, the transaction splitting plan can be reported as an error or submitted.

[0142] Specifically, in a feasible implementation manner, step S303 may include steps S331 to S333:

[0143] Step S331, verifying the transaction splitting plan based on the transaction instruction record and the verification process to determine whether the bond codes are consistent;

[0144] The second verification process point of the verification process is to determine whether the bond codes are consistent according to the transaction instruction records and the transaction splitting plan. The transaction splitting plan that passes this verification process point will be further subdivided to the third verification point of the verification process, and further verification will be performed according to the subdivided verification process; if the transaction splitting plan does not pass this verification process point, the verification result is determined to be failed, and an error will be directly reported for the transaction splitting plan with a failed verification result.

[0145] Since the product type of the lower-level product may be a bond, it is necessary to determine whether the instruction bond code recorded in the transaction instruction record and the split code in the transaction split plan are consistent. Only when the bond codes are consistent can the transaction settlement proceed smoothly.

[0146] Step S332: if not, determine that the verification result is not passed, and report an error for the transaction splitting plan;

[0147] If the instruction bond code recorded in the transaction instruction record and the split code in the transaction split plan are inconsistent, it means that during the transaction split process, the transaction amount was split into the wrong subordinate product and the transaction split plan was wrong. The transaction split plan with inconsistent instruction bond code and split code will be directly reported as an error.

[0148] Step S333: If yes, then verify the transaction splitting plan based on the transaction instruction record and the verification process to determine whether the tail difference exists. Submit the transaction splitting plan with a passed verification result, and report an error if the transaction splitting plan fails the verification result.

[0149] If the instruction bond code recorded in the transaction instruction record and the split code in the transaction split plan are consistent, it means that the subsequent clearing operation can be carried out. However, since there will be a tail difference in the process of allocating the transaction amount to each subordinate product, when the sum of the transaction amounts of each subordinate product is less than the total transaction amount, a tail difference will be generated. Therefore, in order to further confirm the accuracy of the transaction split plan and solve the adverse effects of the tail difference, so that the custodian liquidator can directly perform clearing operations according to the transaction split plan and improve the speed of transaction splitting, it is necessary to perform a tail difference check based on the transaction instruction record and the transaction split plan, and report an error or submit the transaction split plan based on the tail difference check result.

[0150] In this embodiment, the transaction splitting scheme that passes the first verification point is further verified, and the consistency between the instruction bond code recorded in the transaction instruction record and the splitting code in the transaction splitting scheme is set as the second verification point of the verification process. The transaction splitting scheme that fails to pass the second verification point is directly reported as an error, and the transaction splitting scheme that passes the second verification point is verified for the tail difference. By setting multiple verification process points, the accuracy of the transaction splitting scheme is ensured, so that the custodian liquidator can directly perform clearing operations according to the transaction splitting scheme, thereby improving the speed of transaction splitting.

[0151] The above is only a feasible implementation of step S303 provided in this embodiment, and this embodiment does not specifically limit the specific implementation of step S303.

[0152] In this embodiment, the first process point of the verification process set according to the historical transaction instruction record is to determine whether the transaction amount is split into the same subordinate product, and directly report an error for the transaction splitting plan that does not pass the first process point; further verify the transaction splitting plan that passes the first process point, set to determine whether the bond code is consistent as the second verification point of the verification process, directly report an error for the transaction splitting plan that does not pass the second process point, and perform a tail difference check on the transaction splitting plan that passes the second process point. By setting multiple verification process points in the verification process, the accuracy of the transaction splitting plan is ensured, so that the transaction splitting plan that passes all verification process points can be submitted to the custodian liquidator, and the custodian liquidator can directly perform clearing operations according to the transaction splitting plan, and no additional verification is required, thereby improving the speed of transaction splitting.

[0153] Based on the above embodiments of the present application, a seventh embodiment of the present application is proposed. In the seventh embodiment of the present application, the same or similar contents as those of the above embodiments can be referred to the above introduction, and will not be described in detail later.

[0154] In this embodiment, if yes, then the transaction splitting scheme is verified based on the transaction instruction record and the verification process to determine whether the tail difference exists, and the transaction splitting scheme with a passed verification result is submitted. The step S333 of reporting an error verification result of a failed transaction splitting scheme may include steps S1 to S4:

[0155] Step S1, obtaining the total split amount according to the transaction splitting plan;

[0156] The transaction splitting plan includes the splitting details of each subordinate product. The splitting amount of each subordinate product is added together to obtain the total splitting amount.

[0157] It should be noted that during the transaction splitting process, due to calculation accuracy, rounding or system processing, the total amount of the split of the lower-level product may not be consistent with the transaction amount of the upper-level product, which is also the reason for the tail difference. Therefore, the transaction amount of the upper-level product cannot be directly equated with the total amount of the split of the lower-level product. The total amount of the split needs to be obtained based on the split amount details in the transaction splitting plan.

[0158] Step S2, verifying the transaction splitting plan based on the transaction instruction record and the verification process to determine whether there is a tail difference;

[0159] The third verification process point is to determine whether there is a tail difference. When the sum of the transaction amounts of all subordinate products is less than the transaction amount, a tail difference is generated. The tail difference will affect the bank's reputation and customer trust when it comes to sensitive businesses such as fund custody. Therefore, it is necessary to determine whether there is a tail difference based on the transaction instruction records and transaction splitting plan, and to deal with the existing tail difference in a timely manner to prevent the risk from further expanding or evolving into a more serious problem.

[0160] The total amount obtained by adding up the split amount details of each subordinate product in the transaction split plan is compared with the transaction amount in the transaction instruction record. If the total amount is less than the transaction amount, it means that there is a tail difference.

[0161] Step S3: if not, verify whether the split total is equal to the transaction amount based on the verification process, submit the transaction splitting plan if the verification result is yes, and report the transaction splitting plan if the verification result is no;

[0162] If the sum of the split amount details is not less than the transaction amount, it means that the sum of the split amount details may be equal to the transaction amount or greater than the transaction amount. Since there are two situations, further judgment is required to distinguish between the two situations.

[0163] The fourth process point of the verification process is to determine whether the total split amount is equal to the transaction amount. If the total split amount is equal to the transaction amount, the verification result is yes, indicating that there is no tail difference and the transaction split plan has passed all process points of the verification process. The transaction split plan can be submitted from the manager to the custodian liquidator.

[0164] If the total amount of the splits is not equal to the transaction amount, the verification result is no, that is, the total amount of the splits is greater than the transaction amount, which indicates that there are errors and deviations in the transaction splitting plan. This transaction splitting plan does not pass the fourth process point and a direct error is reported for the transaction splitting plan.

[0165] Step S4: If yes, the tail difference is automatically processed, the verification result is determined to be passed, and the transaction splitting plan is submitted.

[0166] If the sum of the split amount details is less than the transaction amount, it indicates that there is a tail difference in the transaction process. The tail difference is automatically added to the subordinate product with the largest split amount to eliminate the tail difference. After eliminating the tail difference, the verification result is passed, and the transaction split plan is submitted to the custodian liquidator so that the custodian liquidator can perform liquidation operations based on the transaction split plan without manual split adjustment.

[0167] Adding the tail difference to the sub-product with the largest split amount can ensure that the amount of this product is closest to the original transaction amount, thereby reducing the risk caused by improper handling of the tail difference. Since the sub-product with the largest split amount often bears the main transaction amount, it is more logical and common sense to add the tail difference to this product.

[0168] It should be noted that the tail difference is usually the amount difference caused by calculation accuracy, rounding or system processing. In the process of automatically processing the tail difference, the accuracy and reliability of the custody comprehensive service platform should be ensured, and the custody comprehensive service platform should be tested and reviewed regularly to ensure the correctness and compliance of the tail difference processing.

[0169] In this embodiment, by performing a tail difference check, it is determined whether the split total is equal to the transaction amount, and the two situations where the split total is not equal to the transaction amount are distinguished in detail, and more detailed verification process points are set, and a transaction splitting plan after automatically processing the tail difference or a transaction splitting plan where the split total is equal to the transaction amount is submitted, and a transaction splitting plan that does not pass the verification process point is directly reported as an error, completing the overall verification process. By verifying the transaction splitting plan, not only the accuracy of the transaction splitting plan is ensured, but the automated verification process also improves the transaction amount splitting speed, and realizes the rapid splitting of the transaction amount of the bank asset custody upper product.

[0170] Reference Figure 6 , Figure 6 This is the overall process diagram of the transaction splitting method for this application. Figure 6 , the overall process of the transaction splitting method of this application is explained.

[0171] like Figure 6 As shown, to split the transaction amount of the bank asset custody parent product, it is first necessary to obtain the inter-bank transaction records of the parent product and the corresponding list of subordinate products.

[0172] Furthermore, based on the obtained interbank transaction records and the corresponding list of subordinate products, it is determined whether the subordinate product is a repurchase transaction product. If so, the transaction amount can be split by bonds or products. If not, the proportion of the transaction amount is intelligently calculated, and the transaction amount is allocated to each subordinate product according to the intelligently calculated proportion.

[0173] Furthermore, it is determined whether the subordinate product is an inter-bank spot bond sale transaction product or an inter-bank repurchase transaction product. If so, the bond holding quantity of the subordinate product is queried. If the quantity is insufficient, a reminder is displayed on the interface; if not, the verification process is entered.

[0174] Furthermore, judging whether the transaction amount is split into the same subordinate product according to the split amount details is the first verification process point of the verification process. If the judgment result is yes, the verification result is determined to be failed and an error is directly reported; if the judgment result is no, enter the next verification process point.

[0175] Furthermore, the second verification process point is to verify whether the split bond code and the bond code of the transaction instruction match according to the transaction instruction record. If the bond code does not match, it means that the verification result is not passed and an error is directly reported; only if the bond code matches can it enter the next verification process point.

[0176] Finally, the final difference check of the verification process is the third verification process point. If there is a final difference, the final difference will be automatically processed and added to the detail with the largest split amount. The verification result is passed and the specific split data will be submitted to the custodian liquidator; if there is no final difference, check whether the split amount is equal to the total transaction amount. Whether the split amount is equal to the total transaction amount is the last verification process point of the verification process. If the split amount is equal to the total transaction amount, the verification result is passed and the specific split data will be submitted to the custodian liquidator. If the split amount is not equal to the total transaction amount, the verification result is failed and an error is directly reported.

[0177] According to the above content, the manager directly splits the transaction on the custody comprehensive service platform. This application transaction splitting method supports intelligent calculation and allocation of split quotas and verification prompts for the split plan, and supports automatic processing of tail differences; the custody and clearing personnel obtain the split details pushed by the manager and directly perform clearing operations without manual split adjustments. Complaints caused by the lack of valid documents can be avoided, and the transaction amount of the upper-level products of bank asset custody can be quickly split.

[0178] This application also provides a transaction splitting device, please refer to Figure 7 , the transaction splitting device comprises:

[0179] Acquisition module 10, used to acquire transaction instruction records of upper-level products and corresponding lower-level product lists;

[0180] The custody integrated service platform first connects to the trading system through the preset API interface and uses the manager's authentication information to log in to the trading system. According to the preset query conditions, the trading system searches for the upper-level products that meet the query conditions. According to the instruction transaction records that meet the query conditions, the trading system searches for the corresponding lower-level products and obtains the detailed information of the lower-level products. The detailed information is tabulated to obtain a list of lower-level products corresponding to the upper-level products.

[0181] A plan generating module 20 is used to split the transaction amount into each subordinate product according to the transaction instruction record and the subordinate product list, and obtain a transaction splitting plan for each subordinate product;

[0182] The product type of the subordinate product is judged. If a subordinate product is a repurchase transaction product, it is split according to bonds or products to obtain the first split amount details of the repurchase transaction product; if a subordinate product is not a repurchase transaction product, it is intelligently split according to the transaction instruction record and the subordinate product list to obtain the second split amount details. Combined with the first split amount details and the second split amount details, the transaction split plan of the parent product is generated. The product type of the subordinate product is judged, and different types of products are split differently, which realizes the accurate splitting of the transaction amount of the bank asset custody parent product. At the same time, the intelligent calculation of the split amount improves the splitting speed, and the retention of specific transaction splitting plans reduces the incidence of subsequent complaints.

[0183] The transaction splitting device provided by the present application adopts the transaction splitting method in the above embodiment, which can solve the technical problem of transaction splitting. Compared with the prior art, the beneficial effects of the transaction splitting device provided by the present application are the same as the beneficial effects of the transaction splitting method provided by the above embodiment, and other technical features in the transaction splitting device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0184] The present application provides a transaction splitting device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the transaction splitting method in the above-mentioned embodiment 1.

[0185] Reference below Figure 8, which shows a schematic diagram of the structure of a transaction splitting device suitable for implementing the embodiment of the present application. The transaction splitting device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The transaction splitting device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0186] like Figure 8 As shown, the transaction splitting device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the transaction splitting device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the transaction splitting device to communicate wirelessly or wired with other devices to exchange data. Although the transaction splitting device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0187] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0188] The transaction splitting device provided by the present application adopts the transaction splitting method in the above embodiment, which can solve the technical problem of transaction splitting. Compared with the prior art, the beneficial effects of the transaction splitting device provided by the present application are the same as the beneficial effects of the transaction splitting method provided by the above embodiment, and the other technical features in the transaction splitting device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0189] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0190] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0191] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, wherein the computer-readable program instructions are used to execute the transaction splitting method in the above-mentioned embodiment.

[0192] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0193] The computer-readable storage medium may be included in the transaction splitting device; or may exist independently without being assembled into the transaction splitting device.

[0194] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the transaction splitting device, the transaction splitting device: obtains the transaction instruction record of the upper-level product and the corresponding lower-level product list; splits the transaction amount into each lower-level product according to the transaction instruction record and the lower-level product list, and obtains the transaction splitting plan for each lower-level product.

[0195] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0196] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0197] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0198] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned transaction splitting method, and can solve the technical problem of transaction splitting. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the transaction splitting method provided in the above-mentioned embodiment, and will not be repeated here.

[0199] The present application also provides a computer program product, including a computer program, which implements the steps of the transaction splitting method as described above when executed by a processor.

[0200] The computer program product provided by this application can solve the technical problem of transaction splitting. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the transaction splitting method provided by the above embodiment, which will not be repeated here.

[0201] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A transaction splitting method, characterized in that: The method comprises: Obtain the transaction instruction records of the upper-level product and the corresponding lower-level product list; The transaction amount is split into each subordinate product according to the transaction instruction record and the subordinate product list to obtain a transaction splitting plan for each subordinate product.

2. The method according to claim 1, characterized in that The step of splitting the transaction amount into each subordinate product according to the transaction instruction record and the subordinate product list to obtain a transaction splitting plan for each subordinate product includes: Obtaining the transaction amount of the upper-level product according to the transaction instruction record; Determining whether a subordinate product is a repurchase transaction product based on the subordinate product list; If yes, the transaction amount is split into the subordinate products according to the preset repurchase transaction rules to obtain the first split amount details; If not, intelligently calculate the transaction amount according to the transaction instruction record and the list of subordinate products, split the transaction amount into the subordinate products, and obtain a second split amount detail; A transaction splitting plan for each subordinate product is obtained based on the first splitting amount details and the second splitting amount details.

3. The method according to claim 1, characterized in that After the step of splitting the transaction amount into each subordinate product according to the transaction instruction record and the subordinate product list to obtain the transaction splitting plan for each subordinate product, the step further includes: The transaction splitting plan is verified based on the preset verification process and the transaction instruction record, and the transaction splitting plan with a passed verification result is submitted, and the transaction splitting plan with a failed verification result is reported as an error.

4. The method according to claim 3, characterized in that The step of verifying the transaction splitting scheme based on the preset verification process and the transaction instruction record, submitting the transaction splitting scheme with a passed verification result, and reporting an error verification result for the transaction splitting scheme with a failed verification result also includes: Determine whether the subordinate product is a spot sale product or a positive repurchase product based on the subordinate product list; If yes, query the subordinate product and decide whether to enter the preset verification process according to the query result; If not, the preset verification process is entered based on the transaction splitting plan and the transaction instruction record.

5. The method according to claim 3, characterized in that The step of verifying the transaction splitting scheme based on the preset verification process and the transaction instruction record, submitting the transaction splitting scheme with a passed verification result, and reporting an error verification result for the transaction splitting scheme with a failed verification result also includes: Obtain historical transaction records of bank asset custody products; Construct a verification process based on the historical transaction records of the bank's asset custody products.

6. The method according to claim 3, characterized in that The step of verifying the transaction splitting scheme based on the preset verification process and the transaction instruction record, submitting the transaction splitting scheme with a passed verification result, and reporting the transaction splitting scheme with a failed verification result includes: Verify the transaction splitting plan based on a preset verification process to determine whether the transaction amount is split into the same subordinate product; If yes, the verification result is determined to be failed, and an error is reported for the transaction splitting plan; If not, the transaction splitting plan is verified based on the transaction instruction record and the verification process to determine whether the bond codes are consistent. The transaction splitting plan with a passed verification result is submitted, and the transaction splitting plan with a failed verification result is reported as an error.

7. The method according to claim 6, characterized in that If not, the transaction splitting scheme is verified based on the transaction instruction record and the verification process to determine whether the bond codes are consistent, and the transaction splitting scheme with a passed verification result is submitted, and the transaction splitting scheme with a failed verification result is reported as an error, and the steps include: Verifying the transaction splitting plan based on the transaction instruction record and the verification process to determine whether the bond codes are consistent; If not, the verification result is determined to be failed, and an error is reported for the transaction splitting plan; If so, the transaction splitting plan is verified based on the transaction instruction record and the verification process to determine whether the tail difference exists. The transaction splitting plan with a passed verification result is submitted, and the transaction splitting plan with a failed verification result is reported as an error.

8. The method according to claim 7, characterized in that If so, the transaction splitting scheme is verified based on the transaction instruction record and the verification process to determine whether there is a tail difference, and the transaction splitting scheme with a passed verification result is submitted, and the transaction splitting scheme with a failed verification result is reported as an error, and the steps include: Obtaining a split total amount according to the transaction split plan; Verify the transaction splitting plan based on the transaction instruction record and the verification process to determine whether there is a tail difference; If not, verify whether the split total is equal to the transaction amount based on the verification process, submit the transaction splitting plan if the verification result is yes, and report the transaction splitting plan if the verification result is no; If so, the tail difference is automatically processed, the verification result is determined to be passed, and the transaction splitting plan is submitted.

9. A transaction splitting device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the transaction splitting method according to any one of claims 1 to 8.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the transaction splitting method according to any one of claims 1 to 8 are implemented.

Images