Resource accounting processing method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to the field of big data processing, and particularly discloses a resource accounting processing method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps of receiving a resource accounting request, obtaining an object identifier corresponding to the resource accounting request, and if it is determined that resource position data matched with the object identifier exists in an object resource position table, determining a resource interaction scene to which the resource position data belongs and resource change processing logic matched with the resource interaction scene. Updating the object resource position table and the resource change detail table according to the resource change processing logic and the resource position data, performing resource change summarization processing on the basis of the updated resource change detail table to obtain a resource change summarization share, and performing resource change summarization processing on the basis of the resource change summarization share. And performing resource accounting processing on the updated object resource position table to obtain a resource accounting result. By adopting the method, tedious business processing operation can be reduced, and the resource quantity accounting efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of big data processing technology, and in particular to a resource accounting processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the development of data processing technology and the promotion and application of various financial services, in order to ensure the security of resources in the business processing process and avoid errors in resource quantity statistics, financial institutions need to regularly count and calculate resource change information such as resource interaction volume and total resource volume in financial services. Traditionally, when counting and calculating resource change information of various financial services, it is usually adopted to record the resource interaction volume in real time according to the resource interaction time of the financial service triggered by the user, and calculate the total resource volume held by the financial service participants in real time based on the recorded resource interaction volume.

[0003] However, the traditional resource quantity statistics and accounting methods used, when the financial business volume is large and different types of financial businesses adopt different interaction modes, need to repeatedly record resource interactions and perform a large number of resource total quantity calculation operations based on the resource interaction time and interaction mode of different financial businesses. There are still problems such as cumbersome business resource statistics operations and low resource quantity accounting efficiency. Summary of the invention

[0004] Based on this, it is necessary to provide a resource accounting processing method, device, computer equipment, computer-readable storage medium and computer program product that can reduce the resource quantity recording operations and calculation operations in the financial business processing process and improve the efficiency of resource quantity accounting in response to the above-mentioned technical problems.

[0005] In a first aspect, the present application provides a resource accounting processing method, comprising: receiving a resource accounting request, and obtaining an object identifier corresponding to the resource accounting request; if it is determined that there is resource holding data matching the object identifier in the object resource holding table, determining the resource interaction scenario to which the resource holding data belongs; determining a resource change processing logic matching the resource interaction scenario, and updating the object resource holding table and the resource change details table according to the resource change processing logic and the resource holding data; performing resource change summary processing based on the updated resource change details table to obtain a resource change summary share corresponding to the object identifier, and performing resource accounting processing on the updated object resource holding table according to the resource change summary share to obtain a resource accounting result.

[0006] In an exemplary embodiment, the resource change summary processing is performed based on the updated resource change details table to obtain the resource change summary share corresponding to the object identifier, including: based on the updated resource change details table, determining the daily share change records associated with the object identifier in different resource interaction scenarios; performing resource change summary processing on the daily share change records in the different resource interaction scenarios to obtain the resource change summary share corresponding to the object identifier.

[0007] In an exemplary embodiment, resource accounting processing is performed on the updated object resource holding table based on the resource change summary share to obtain a resource accounting result, including: determining the previous day's resource balance corresponding to the current day's share change record, and determining the current day's total resource share based on the resource change summary share and the previous day's resource balance; performing resource accounting processing on the total amount of resources in the updated object resource holding table based on the current day's total resource share; if it is determined that the current day's total resource share is consistent with the updated total amount of resources, obtaining a resource accounting result with consistent resource amounts.

[0008] In an exemplary embodiment, the resource change processing logic that matches the resource interaction scenario is determined, and the object resource holding table and the resource change details table are updated according to the resource change processing logic and the resource holding data, including: when the resource interaction scenario to which the resource holding data belongs is a resource transfer scenario, the resource transfer processing logic that matches the resource transfer scenario is determined; the resource transfer amount is determined according to the resource holding data, and if the resource transfer amount meets the resource transfer condition, the total amount of resources in the object resource holding table is updated according to the resource transfer amount according to the resource transfer processing logic; a new resource transfer record is added to the resource change details table, and a resource change flag and a resource change category are added to the resource transfer record according to the resource transfer processing logic.

[0009] In an exemplary embodiment, the resource change processing logic that matches the resource interaction scenario is determined, and the object resource holding table and the resource change details table are updated according to the resource change processing logic and the resource holding data, including: when the resource interaction scenario to which the resource holding data belongs is a transfer custody processing scenario, the amount of custody transferred resources is determined according to the resource holding data; the transfer custody processing logic that matches the transfer custody processing scenario is determined, and according to the transfer custody processing logic, the resource frozen share and / or the total amount of resources in the object resource holding table are updated according to the amount of custody transferred resources; a new transfer custody processing record is added to the resource change details table, and according to the transfer custody processing logic, a resource change flag and a resource change category are added to the transfer custody processing record.

[0010] In an exemplary embodiment, the resource change processing logic that matches the resource interaction scenario is determined, and the object resource holding table and resource change details table are updated according to the resource change processing logic and the resource holding data, including: when the resource interaction scenario to which the resource holding data belongs is a resource closing scenario, the closing resource quantity is determined according to the resource holding data; the closing resource share corresponding to the object identifier is determined, and if it is determined that the closing resource quantity is less than the closing resource share, the resource closing processing logic corresponding to the resource closing scenario is determined; according to the resource closing processing logic, the frozen resource clearing processing in the next day's interaction mode is triggered, and according to the closing resource quantity, the total resource quantity and holding cost in the object resource holding table are updated; a new resource closing record is added to the resource change details table, and according to the resource closing processing logic, a resource change flag and resource change category are added to the resource closing record.

[0011] In the second aspect, the present application also provides a resource accounting processing device, including: an object identification acquisition module, used to receive a resource accounting request and obtain an object identification corresponding to the resource accounting request; a resource interaction scenario determination module, used to determine the resource interaction scenario to which the resource holding data belongs if it is determined that there is resource holding data matching the object identification in the object resource holding table; a data update module, used to determine the resource change processing logic matching the resource interaction scenario, and update the object resource holding table and the resource change details table according to the resource change processing logic and the resource holding data; a resource accounting processing module, used to perform resource change summary processing based on the updated resource change details table, obtain the resource change summary share corresponding to the object identification, and perform resource accounting processing on the updated object resource holding table according to the resource change summary share to obtain a resource accounting result.

[0012] In an exemplary embodiment, the resource accounting processing module also includes: a daily share change record determination unit, which is used to determine the daily share change records associated with the object identifier in different resource interaction scenarios based on the updated resource change details table; a resource change summary share determination unit, which is used to perform resource change summary processing on the daily share change records in the different resource interaction scenarios to obtain the resource change summary shares corresponding to the object identifier.

[0013] In an exemplary embodiment, the resource accounting processing module also includes: a unit for determining the total resource share for the day, which is used to determine the resource balance of the previous day corresponding to the share change record for the day, and determine the total resource share for the day based on the resource change summary share and the resource balance of the previous day; a resource accounting unit, which is used to perform resource accounting processing on the total amount of resources in the updated object resource holding table based on the total resource share for the day; and a resource accounting result obtaining unit, which is used to obtain a resource accounting result with consistent resource amount if it is determined that the total resource share for the day is consistent with the updated total amount of resources.

[0014] In an exemplary embodiment, the resource accounting processing module also includes: a resource transfer processing logic determination unit, which is used to determine the resource transfer processing logic that matches the resource transfer scenario when the resource interaction scenario to which the resource holding data belongs is a resource transfer scenario; a first update unit, which is used to determine the resource transfer amount based on the resource holding data, and if the resource transfer amount meets the resource transfer conditions, according to the resource transfer processing logic, update the total amount of resources in the object resource holding table according to the resource transfer amount; a resource transfer record adding unit, which is used to add a resource transfer record to the resource change details table, and add a resource change flag and a resource change category to the resource transfer record according to the resource transfer processing logic.

[0015] In an exemplary embodiment, the resource accounting processing module also includes: a custody transfer resource quantity determination unit, which is used to determine the custody transfer resource quantity according to the resource holding data when the resource interaction scenario to which the resource holding data belongs is a custody transfer processing scenario; a second updating unit, which is used to determine the custody transfer processing logic that matches the custody transfer processing scenario, and according to the custody transfer processing logic, updates the resource frozen share and / or total resource quantity in the object resource holding table according to the custody transfer resource quantity; a custody transfer processing record adding unit, which is used to add a custody transfer processing record to the resource change details table, and according to the custody transfer processing logic, add a resource change flag and a resource change category to the custody transfer processing record.

[0016] In an exemplary embodiment, the resource accounting processing module also includes: a resource closing processing logic determination unit, which is used to determine the share of liquidable resources corresponding to the object identifier, and if it is determined that the liquidated resource amount is less than the share of liquidable resources, determine the resource closing processing logic corresponding to the resource closing scenario; a third updating unit, which is used to trigger the frozen resource clearing processing in the next day's interactive mode according to the resource closing processing logic, and update the total resource amount and holding cost in the object resource holding table according to the liquidated resource amount; a resource closing record adding unit, which is used to add a resource closing record to the resource change details table, and add a resource change flag and resource change category to the resource closing record according to the resource closing processing logic.

[0017] In a third aspect, the present application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the above-mentioned resource accounting processing method when executing the computer program.

[0018] In a fourth aspect, the present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned resource accounting processing method is implemented.

[0019] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the above-mentioned resource accounting processing method when executed by a processor.

[0020] In the above-mentioned resource accounting processing method, device, computer equipment, computer-readable storage medium and computer program product, by receiving a resource accounting request, obtaining the object identifier corresponding to the resource accounting request, and determining the resource interaction scenario to which the resource holding data belongs when it is determined that there is resource holding data matching the object identifier in the object resource holding table, it can cover a variety of different resource interaction scenarios involved in the financial business processing process, so as to calculate the resource holding data in different resource interaction scenarios separately, so that the resource holding data in different resource interaction scenarios can be quickly queried or viewed according to actual needs later. Furthermore, by determining the resource change processing logic that matches the resource interaction scenario, the object resource holding table and the resource change details table are updated according to the resource change processing logic and the resource holding data, and the resource change summary processing is performed based on the updated resource change details table to obtain the resource change summary share corresponding to the object identifier, and the resource accounting processing is performed on the updated object resource holding table according to the resource change summary share to obtain the resource accounting result. This realizes the change summary and accounting of the holding data and change details corresponding to different resource interaction scenarios, and avoids the use of real-time recording, separate updating or separate accounting. This can reduce the resource quantity recording and calculation operations in the financial business processing process, and further improve the resource quantity accounting efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0022] FIG1 is an application environment diagram of a resource accounting processing method in one embodiment;

[0023] Figure 2 A schematic diagram of a process flow of a resource accounting processing method in one embodiment;

[0024] Figure 3 A distribution diagram of a resource interaction scenario to which resource holding data belongs in one embodiment;

[0025] Figure 4 It is a schematic diagram of a process of updating an object resource holding table and a resource change detail table in a resource transfer scenario in one embodiment;

[0026] Figure 5 It is a schematic diagram of a process of updating an object resource holding table and a resource change detail table in a resource transfer scenario in another embodiment;

[0027] Figure 6 It is a schematic diagram of a process of updating an object resource holding table and a resource change detail table in a custody transfer processing scenario in one embodiment;

[0028] Figure 7 It is a flowchart of updating the object resource holding table and resource change detail table in a scenario where the custody transfer-out review is successful in one embodiment;

[0029] Figure 8 It is a flowchart of updating the object resource position table and resource change detail table in a scenario where the confirmation of the escrow transfer-out confirmer fails in one embodiment;

[0030] Fig. 9 It is a flowchart of updating the object resource holding table and resource change detail table in a scenario where the custody transfer is successful in one embodiment;

[0031] Fig.10 It is a flowchart of updating the object resource holding table in a custody transfer-out freeze scenario in one embodiment;

[0032] Fig.11It is a schematic diagram of a process of updating the object resource holding table in a scenario where the custody transfer-out audit fails in one embodiment;

[0033] Fig.12 It is a schematic diagram of a process of updating the object resource holding table and the resource change detail table in a resource liquidation scenario in one embodiment;

[0034] Fig.13 It is a schematic diagram of a process of updating an object resource holding table in a resource freezing scenario in one embodiment;

[0035] Fig.14 It is a schematic diagram of a process of updating the object resource holding table in a resource unfreezing scenario in one embodiment;

[0036] Fig.15 A structural block diagram of a resource accounting processing device in one embodiment;

[0037] FIG. 16 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0038] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. It should be noted that in the embodiments of the present application, certain software, groups, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0039] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations. The acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with relevant provisions of national laws and regulations.

[0040] The resource accounting processing method provided in the embodiment of the present application can be applied to the application environment shown in Figure 1. Among them, the terminal 102 communicates with the server 104 through the network, and the data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, and projection devices. Portable wearable devices can be smart watches, smart bracelets, and head-mounted devices. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. The server 104 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services. Specifically, when the server 104 receives a resource accounting request triggered by the user based on the terminal 102, it obtains the object identifier corresponding to the resource accounting request, and when it is determined that there is resource holding data matching the object identifier in the object resource holding table, it determines the resource interaction scenario to which the resource holding data belongs. Furthermore, the server 104 can update the object resource holding table and the resource change detail table according to the resource change processing logic and the resource holding data by determining the resource change processing logic matching the resource interaction scenario. Among them, the server 104 can perform resource change summary processing based on the updated resource change detail table to obtain the resource change summary share corresponding to the object identifier, and can perform resource accounting processing on the updated object resource holding table according to the resource change summary share to obtain the resource accounting result. Among them, after obtaining the resource accounting result, the server 104 can feed back the resource accounting result to the terminal 102, and display the resource accounting result through the terminal 102 for the user to view and access.

[0041] In an exemplary embodiment, Figure 2 As shown, a resource accounting processing method is provided, which is described by taking the method applied to the server 104 in FIG. 1 as an example, and includes the following steps 202 to 206. Among them:

[0042] Step 202: Receive a resource accounting request and obtain an object identifier corresponding to the resource accounting request.

[0043] Among them, business processing personnel (such as financial institution staff, etc.) can trigger a resource accounting request based on the terminal, and the resource accounting request is used to implement resource accounting of resource holding data of users participating in financial business.

[0044] Specifically, if the server receives a resource accounting request from the terminal, it parses the resource accounting request and obtains the object identifier corresponding to the resource accounting request. The object identifier is used to indicate the specific user who needs to perform resource accounting processing (i.e., the user participating in financial services), and obtains the resource holding data corresponding to the specific user who needs to perform resource accounting processing for resource accounting processing.

[0045] Step 204: If it is determined that there is resource holding data matching the object identifier in the object resource holding table, the resource interaction scenario to which the resource holding data belongs is determined.

[0046] Specifically, the server may traverse or query the object resource storage table according to the object identifier to determine whether there is resource storage data matching the object identifier in the object resource storage table. If it is determined that there is resource storage data matching the object identifier in the object resource storage table, the resource processing operation performed on the corresponding resource storage data, such as resource transfer-in, resource transfer-out, etc., may be further determined, so that the resource interaction scenario to which the resource storage data belongs may be determined according to the resource processing operation performed.

[0047] Among them, the object resource holding table is provided with a plurality of different fields, which respectively store different object identifiers and resource holding data in different resource interaction scenarios. Thus, according to the object identifier corresponding to the resource accounting request, the object resource holding table can be traversed or queried to determine the resource holding data matching the object identifier from the object resource holding table.

[0048] In an exemplary embodiment, different resource interaction scenarios are set according to different resource interaction types. The resource interaction types include ordinary resource interaction types and special resource interaction types, and the ordinary resource interaction types and special resource interaction types involve different resource interaction processing operations. The ordinary resource interaction type only involves resource transfer operations under normal circumstances, including resource transfer-out operations and resource transfer-in operations, and corresponding resource transfer-in scenarios and resource transfer-out scenarios are set, while the special resource interaction type involves a variety of special resource interaction operations including resource freezing / thawing operations, resource transfer custody operations, and resource liquidation operations, and resource freezing scenarios, resource thawing scenarios, transfer custody processing scenarios, and resource liquidation scenarios are set respectively.

[0049] Among them, the resource transfer and custody specifically includes custody transfer-out operation and custody transfer-in operation. Custody transfer-out refers to the user's transfer of the bonds held in custody at the current financial institution to other financial institutions, while custody transfer-in refers to the user's transfer of the bonds held in custody at other financial institutions to the current financial institution. Among them, according to the different custody transfer operations, different custody transfer processing scenarios are further set, including custody transfer-out freezing scenario, custody transfer-out review success scenario, custody transfer-out review failure scenario, custody transfer-out confirmation failure scenario, and custody transfer-in success scenario.

[0050] For example, Figure 3 As shown, a distribution diagram of resource interaction scenarios to which resource holding data belongs is provided. Figure 3 It can be seen that the resource interaction scenarios to which the resource holding data belongs specifically include: 1) resource transfer-in scenario 01 and resource transfer-out scenario 02 under the general resource interaction type; 2) resource freeze scenario 03, resource thawing scenario 04, escrow transfer-out freeze scenario 05, escrow transfer-out review success scenario 06, escrow transfer-out review failure scenario 07, escrow transfer-out confirmer confirmation failure scenario 08, escrow transfer-in success scenario 09, and resource liquidation scenario 10 under the special resource interaction type.

[0051] Specifically: 1) Resource transfer-in scenario 01 indicates a buy-in transaction, i.e., the user's resource holding share increases; 2) Resource transfer-out scenario 02 indicates a sell-out transaction, i.e., the user's resource holding share decreases; 3) Resource freezing scenario 03 indicates judicial resource freezing, i.e., the user's frozen resource share increases; 4) Resource unfreezing scenario 04 indicates judicial resource unfreezing, i.e., the user's frozen resource share decreases; 5) Custodial transfer-out freezing scenario 05 indicates custodial transfer-out resource freezing, i.e., the user's frozen resource share increases; 6) Custodial transfer-out review success scenario 06 indicates that the transfer-out operation of the custodial resources is successfully reviewed, and the custodial resources of the current financial institution can be transferred to other financial institutions, i.e., the user's resource holding share and frozen resource share are both reduced; 7) Custodial transfer-out review success scenario 08 indicates that the transfer-out operation of the custodial resources is successfully reviewed, and the custodial resources of the current financial institution can be transferred to other financial institutions, i.e., the user's resource holding share and frozen resource share are both reduced; Failure scenario 07 indicates that the audit of the transfer-out operation of the custodial resources has failed, and the custodial resources of the current financial institution cannot be transferred to other financial institutions, that is, the user's frozen resource share is reduced; 8) Custody transfer-out confirmation failure scenario 08 indicates that the audit of the transfer-out operation of the custodial resources is successful, but the transferee confirmation fails, and the custodial resources of the current financial institution cannot be transferred to other financial institutions, that is, the user's resource holding share increases; 9) Custody transfer-in success scenario 09 indicates that the custodial resources transferred from other financial institutions to the current financial institution are received, that is, the user's resource holding share increases; 10) Resource liquidation scenario 10 indicates that the user's book-entry resources are forced to be sold in advance before expiration, that is, the user's resource holding share decreases and the holding cost changes.

[0052] Step 206, determine the resource change processing logic that matches the resource interaction scenario, and update the object resource holding table and resource change detail table according to the resource change processing logic and resource holding data.

[0053] Specifically, different resource interaction scenarios are respectively provided with different resource change processing logics. After determining the resource interaction scenario to which the resource holding data belongs, the resource change processing logic matching the corresponding resource interaction scenario is further determined, so as to update the object resource holding table and the resource change details table according to the resource holding data according to the resource change processing logic.

[0054] According to different resource change processing logics, different parameters in the object resource holding table can be updated, such as the total amount of resources and / or resource frozen shares in the object resource holding table. When updating the resource change details table, specifically for resource processing operations in different resource interaction scenarios, new or updated corresponding resource processing records are created, such as resource transfer-in records, resource transfer-out records, resource freezing records, custody transfer processing records, and resource liquidation records.

[0055] Exemplarily, resource interaction scenarios specifically include: resource transfer scenarios (including resource transfer-in scenarios and resource transfer-out scenarios), custody transfer processing scenarios, and resource liquidation scenarios, etc. In the corresponding resource interaction scenarios, the resource change processing logic matching the corresponding resource interaction scenarios can be followed, such as following the resource transfer processing logic corresponding to the resource transfer scenario, updating the total amount of resources in the object resource holding table according to the resource transfer amount, and adding a resource transfer record to the resource change details table. For another example, according to the custody transfer processing logic, the frozen resource share and / or total amount of resources in the object resource holding table are updated according to the custody transfer resource amount, and adding a custody transfer processing record to the resource change details table.

[0056] In an exemplary embodiment, the resource interaction scenario also includes a resource freezing scenario and a resource unfreezing scenario, and the custody transfer processing scenario may specifically include a custody transfer-out freezing scenario, a custody transfer-out audit success scenario, a custody transfer-out audit failure scenario, a custody transfer-out confirmation failure scenario, and a custody transfer-in success scenario. Among them, in the custody transfer-out freezing scenario and the custody transfer-out audit failure scenario, the object resource position table needs to be updated, and the resource change detail table does not need to be updated, while in the custody transfer-out audit success scenario, the custody transfer-out confirmation failure scenario, and the custody transfer-in success scenario, the object resource position table and the resource change detail table need to be updated.

[0057] Step 208, perform resource change summary processing based on the updated resource change details table to obtain the resource change summary share corresponding to the object identifier, and perform resource accounting processing on the updated object resource holding table based on the resource change summary share to obtain the resource accounting result.

[0058] Among them, the resource change details table records the resource processing records under different resource interaction scenarios, such as resource transfer-in records, resource transfer-out records, resource freezing records, custody transfer processing records, and resource liquidation records, etc., and also records the specific information such as the resource processing time and resource processing volume of the corresponding resource processing records.

[0059] Specifically, the server can determine the daily share change records in different resource interaction scenarios associated with the object identifier based on the updated resource change details table, such as the daily share change records of a user corresponding to the object identifier in different resource interaction scenarios such as resource transfer scenario, transfer custody processing scenario, and resource liquidation scenario. Among them, the daily share change record can be understood as the change record of the resource holding share corresponding to the resource processing operation triggered by the user in different resource interaction scenarios, such as the resource holding share increase record, the resource holding share decrease record, etc.

[0060] Among them, resource changes are summarized and processed by recording the daily share changes in different resource interaction scenarios, such as resource holding share increase records, resource holding share decrease records, resource frozen share increase records, resource frozen share decrease records, etc., to obtain the resource change summary share corresponding to the object identifier.

[0061] Furthermore, after obtaining the resource change summary share corresponding to the object identifier, the server determines the previous day's resource margin corresponding to the current day's share change record, and determines the current day's total resource share based on the resource change summary share and the previous day's resource margin. Specifically, the resource interaction date can be determined for the current day's share change record, and the previous day's resource margin of the day before the resource interaction date can be obtained, and the sum of the resource change summary share and the previous day's resource margin can be calculated to obtain the current day's total resource share.

[0062] Among them, after obtaining the total resource share of the day, the total amount of resources in the updated object resource position table is specifically processed for resource accounting based on the total resource share of the day, that is, the total resource share of the day and the total amount of resources are compared and calculated to determine whether the two are consistent. Among them, if it is determined that the total resource share of the day and the total amount of resources after the update are consistent, a resource accounting result with consistent resource quantity is obtained, and if the total resource share of the day and the total amount of resources after the update are inconsistent, a resource accounting result with inconsistent resource quantity is obtained, which indicates that there is currently a resource quantity calculation or statistical error, and it is necessary to re-record, count and calculate, etc., to solve the existing calculation errors or statistical errors and avoid resource losses for users and financial institutions.

[0063] In the above-mentioned resource accounting processing method, by receiving a resource accounting request, obtaining the object identifier corresponding to the resource accounting request, and determining that there is resource holding data matching the object identifier in the object resource holding table, the resource interaction scenario to which the resource holding data belongs is determined, thereby covering a variety of different resource interaction scenarios involved in the financial business processing process, so as to calculate the resource holding data in different resource interaction scenarios separately, so that the resource holding data in different resource interaction scenarios can be quickly queried or viewed according to actual needs in the future. Furthermore, by determining the resource change processing logic that matches the resource interaction scenario, the object resource holding table and the resource change details table are updated according to the resource change processing logic and the resource holding data, and the resource change summary processing is performed based on the updated resource change details table to obtain the resource change summary share corresponding to the object identifier, and the resource accounting processing is performed on the updated object resource holding table according to the resource change summary share to obtain the resource accounting result. This realizes the change summary and accounting of the holding data and change details corresponding to different resource interaction scenarios, and avoids the use of real-time recording, separate updating or separate accounting. This can reduce the resource quantity recording and calculation operations in the financial business processing process, and further improve the resource quantity accounting efficiency.

[0064] In an exemplary embodiment, Figure 4 As shown, in the resource transfer scenario, the step of updating the object resource holding table and the resource change detail table, that is, determining the resource change processing logic matching the resource interaction scenario, and updating the object resource holding table and the resource change detail table according to the resource change processing logic and resource holding data, specifically includes steps 402 to 406. Among them:

[0065] Step 402: When the resource interaction scenario to which the resource holding data belongs is a resource transfer scenario, determine a resource transfer processing logic that matches the resource transfer scenario.

[0066] The resource transfer scenario includes a resource transfer-out scenario and a resource transfer-in scenario, and the resource transfer processing logic specifically includes: a resource transfer-out processing logic corresponding to the resource transfer-out scenario, and a resource transfer-in processing logic corresponding to the resource transfer-in scenario.

[0067] Specifically, when the resource interaction scenario to which the resource holding data belongs is a resource transfer scenario, for example, when it is determined that the resource interaction scenario to which the resource holding data belongs is a resource transfer-out scenario, the resource transfer-out processing logic that matches the resource transfer-out scenario is determined; if it is determined that the resource interaction scenario to which the resource holding data belongs is a resource transfer-in scenario, the resource transfer-in processing logic that matches the resource transfer-in scenario is determined.

[0068] Step 404, determine the resource transfer amount according to the resource holding data. If the resource transfer amount meets the resource transfer conditions, update the total amount of resources in the object resource holding table according to the resource transfer amount according to the resource transfer processing logic.

[0069] The resource transfer scenario includes a resource transfer-out scenario and a resource transfer-in scenario, and the resource transfer amount specifically includes a resource transfer-out amount corresponding to the resource transfer-out scenario and a resource transfer-out amount corresponding to the resource transfer-in scenario.

[0070] Specifically, when the resource interaction scenario to which the resource holding data belongs is a resource transfer-out scenario, the resource transfer-out amount is determined according to the resource holding data, and the available resource share corresponding to the object identifier is determined, and the resource transfer-out amount and the available resource share are compared. When it is determined that the available resource share is greater than the resource transfer-out amount, it is determined that the resource transfer-out amount meets the resource transfer condition. Among them, the available resource share corresponding to the object identifier refers to the resource share held by the user corresponding to the object identifier and available for resource transfer (i.e., not frozen).

[0071] Furthermore, when it is determined that the resource transfer amount meets the resource transfer conditions, the total amount of resources in the object resource holding table is updated according to the resource transfer processing logic and the resource transfer amount. Specifically, the total amount of resources currently recorded in the object resource holding table is subtracted from the resource transfer amount to be transferred to obtain the updated total amount of resources. In the resource transfer scenario, since the total amount of resources in the object resource holding table is continuously reduced, when the total amount of resources is 0, the holding cost corresponding to the object identifier is cleared.

[0072] In an exemplary embodiment, when the resource interaction scenario to which the resource holding data belongs is a resource transfer-in scenario, the resource transfer-in amount is determined based on the resource holding data, and the current resource share corresponding to the object identifier is determined. Further, a preset holding share threshold value pre-set for the resource transfer-in scenario is obtained, and the current resource share is compared with the preset holding share threshold value. When it is determined that the current resource share is less than the preset holding share threshold value, it is determined that the resource transfer-in amount meets the resource transfer condition. Among them, the current resource share corresponding to the object identifier refers to the resource share (including unfrozen shares and frozen shares) held by the user corresponding to the object identifier, and the preset holding share threshold value represents the maximum resource holding share pre-set for the user corresponding to the object identifier.

[0073] Furthermore, when it is determined that the amount of resource transfer meets the resource transfer conditions, the total amount of resources in the object resource holding table is updated according to the resource transfer processing logic and the amount of resource transfer. Specifically, the total amount of resources currently recorded in the object resource holding table is increased by the current amount of resource transfer-out to obtain an updated total amount of resources.

[0074] Step 406, adding a new resource transfer record to the resource change details table, and adding a resource change flag and a resource change category to the resource transfer record according to the resource transfer processing logic.

[0075] Specifically, the resource transfer record specifically includes the resource transfer-out record in the resource transfer-out scenario and the resource transfer-in record in the resource transfer-in scenario. If the resource interaction scenario is the resource transfer-out scenario, a new resource transfer-out record is added to the resource change details table, and a resource change flag and a resource change category are added to the resource transfer-out record according to the resource transfer-out processing logic. Specifically, the resource change flag of "1-spot transaction" and the resource change category of "1-sell" are added to the resource transfer-out record.

[0076] Furthermore, when the resource interaction scenario is a resource transfer scenario, a new resource transfer record is added to the resource change details table, and a resource change flag and a resource change category are added to the resource transfer record according to the resource transfer processing logic. Specifically, a resource change flag of "1-spot transaction" and a resource change category of "1-buy" are added to the resource transfer record.

[0077] In an exemplary embodiment, Figure 5 As shown in the figure, in the resource transfer scenario, the steps for updating the object resource holding table and resource change details table include:

[0078] Step 1) Determine whether the requested data is legal.

[0079] Among them, the legality check method for determining whether the request data is legal includes: the code determines whether the field is empty or whether the business rules are reviewed. The request data that needs to be checked includes whether the relevant information of the user corresponding to the object identifier is correct, whether the account of the user corresponding to the object identifier is correct, and whether the bonds held by the user corresponding to the object identifier are tradable.

[0080] Step 2) querying the object resource holding table, and when it is determined that there is resource holding data matching the object identifier in the object resource holding table, determining the resource interaction scenario to which the resource holding data belongs.

[0081] If it is determined that there is resource holding data matching the object identifier in the object resource holding table, then the resource interaction scenario to which the resource holding data belongs is determined, specifically including a resource transfer-in scenario and a resource transfer-out scenario.

[0082] Step 3), when the resource interaction scenario to which the resource holding data belongs is a resource transfer-in scenario, the resource transfer-in amount is determined according to the resource holding data, and the current resource share corresponding to the object identifier is determined.

[0083] Step 4) determines whether the current resource share is less than a preset share threshold value set in advance for the resource transfer scenario.

[0084] Step 5), if the current resource share is less than the preset share threshold, the total resource amount currently recorded in the object resource holding table is increased by the current transferred-in resource transfer-out amount to obtain the updated total resource amount.

[0085] If the previously held resource share is greater than or equal to the preset held share threshold, the current update processing operation is terminated.

[0086] Step 6) Add a new resource transfer record to the resource change details table, and according to the resource transfer processing logic, add the resource change flag of "1-spot transaction" and the resource change category of "1-buy" to the resource transfer record.

[0087] After executing step 2), execute step 7). When the resource interaction scenario to which the resource holding data belongs is a resource transfer-out scenario, determine the resource transfer-out amount according to the resource holding data, and determine the available resource share corresponding to the object identifier.

[0088] Step 8) Determine whether the available resource share is greater than the resource transfer amount.

[0089] Step 9), when the available resource share is greater than the resource transfer amount, the total resource amount currently recorded in the object resource holding table is subtracted from the resource transfer amount to be transferred out to obtain the updated total resource amount.

[0090] If the available resource share is less than or equal to the resource transfer-out amount, the current update processing operation is terminated.

[0091] Step 10), add a new resource transfer record in the resource change details table, and according to the resource transfer processing logic, add the resource change flag of "1-cash transaction" and the resource change category of "1-sell" to the resource transfer record.

[0092] After executing step 6) or step 10), execute step 11). If there is no position data, add a new position record; if there is position data, update the position record.

[0093] In this embodiment, when the resource interaction scenario to which the resource holding data belongs is a resource transfer scenario, the resource transfer processing logic that matches the resource transfer scenario is determined, and the resource transfer amount is determined based on the resource holding data, so that the resource transfer condition is satisfied with the resource transfer amount. According to the resource transfer processing logic, the total amount of resources in the object resource holding table is updated according to the resource transfer amount, and a new resource transfer record is added to the resource change details table. At the same time, according to the resource transfer processing logic, a resource change flag and a resource change category are added to the resource transfer record, thereby covering a variety of different resource interaction scenarios involved in the financial business processing process, so as to calculate the resource holding data in different resource interaction scenarios separately, so that the resource holding data in different resource interaction scenarios can be quickly queried or viewed according to actual needs in the future, avoiding the use of real-time recording, separate updating or separate accounting methods, which can reduce the resource quantity recording and calculation operations in the financial business processing process, and further improve the resource quantity accounting efficiency.

[0094] In an exemplary embodiment, Figure 6 As shown, in the custody transfer processing scenario, the step of updating the object resource holding table and the resource change detail table, that is, determining the resource change processing logic matching the resource interaction scenario, and updating the object resource holding table and the resource change detail table according to the resource change processing logic and resource holding data, specifically includes steps 602 to 606. Among them:

[0095] Step 602: When the resource interaction scenario to which the resource holding data belongs is a custody transfer processing scenario, determine the custody transfer resource quantity according to the resource holding data.

[0096] Among them, the custody transfer processing scenarios specifically include the custody transfer-out review success scenario, the custody transfer-out confirmation party confirmation failure scenario, the custody transfer-in success scenario, the custody transfer-out freeze scenario, and the custody transfer-out review failure scenario. In the custody transfer-out freeze scenario and the custody transfer-out review failure scenario, the object resource position table needs to be updated, and there is no need to update the resource change details table. In the custody transfer-out review success scenario, the custody transfer-out confirmation party confirmation failure scenario, and the custody transfer-in success scenario, the object resource position table and the resource change details table need to be updated.

[0097] Specifically, when the resource interaction scenario to which the resource holding data belongs is a custody transfer processing scenario, such as a custody transfer-out review success scenario, a custody transfer-out confirmation failure scenario, a custody transfer-in success scenario, a custody transfer-out freeze scenario, or a custody transfer-out review failure scenario, the custody transfer resource quantity is determined based on the resource holding data. Specifically, the custody transfer resource quantity may be the custody transfer-out resource quantity, the custody transfer-in resource quantity, and the custody freeze resource quantity.

[0098] Step 604, determine the custody transfer processing logic that matches the custody transfer processing scenario, and update the resource freezing share and / or total resource amount in the object resource holding table according to the custody transfer processing logic and the custody transfer resource amount.

[0099] Among them, the custody transfer processing logic specifically includes: the first custody transfer-out processing logic corresponding to the scenario where the custody transfer-out review is successful, the second custody transfer-out processing logic corresponding to the scenario where the custody transfer-out confirmation party fails to confirm, the custody transfer-in processing logic corresponding to the scenario where the custody transfer-in is successful, the custody freeze processing logic corresponding to the custody transfer-out freeze scenario, and the third custody transfer-out processing logic corresponding to the scenario where the custody transfer-out review fails.

[0100] Specifically, after determining the custody transfer processing logic that matches the custody transfer processing scenario, such as determining the first custody transfer processing logic corresponding to the custody transfer review success scenario, according to the first custody transfer processing logic, based on the determined custody transfer resource amount, which can be the custody transfer resource amount, the resource frozen share and the total resource amount in the object resource holding table are updated. Specifically, the resource frozen share and the total resource amount in the object resource holding table are both reduced.

[0101] For example, Figure 7 As shown in the figure, it provides a schematic diagram of updating the object resource position table and resource change details table in the scenario where the custody transfer review is successful. Figure 7It can be seen that in the scenario where the custody transfer review is successful, first, it is necessary to determine whether the request data is legal, including whether the field is empty or whether the business rules are reviewed. The request data that needs to be checked includes whether the relevant information of the user corresponding to the object identifier is correct, whether the account of the user corresponding to the object identifier is correct, and whether the bonds held by the user corresponding to the object identifier are tradable. Secondly, according to the first custody transfer processing logic, according to the determined custody transfer resource volume, the resource frozen share and total resource volume in the object resource holding table are updated, specifically, the resource frozen share and total resource volume in the object resource holding table are reduced. Third, a new custody transfer review success record is added to the resource change details table, and the resource change flag of "5-transfer custody" and the resource change category of "5-transfer custody transfer accounting" are added to the custody transfer review success record.

[0102] In an exemplary embodiment, if the second custody transfer processing logic corresponding to the custody transfer confirmation failure scenario is determined, the total amount of resources in the object resource holding table is updated according to the second custody transfer processing logic and the determined custody transfer resource amount. Specifically, the total amount of resources in the object resource holding table is increased.

[0103] For example, Figure 8 As shown in the figure, it provides a schematic diagram of updating the object resource position table and resource change details table in the scenario where the confirmation of the custody transfer-out confirmer fails. Figure 8 It can be seen that in the scenario where the confirmation of the custodial transfer-out confirming party fails, first of all, it is also necessary to determine whether the request data is legal, including determining whether the field is empty or whether to review the business rules, etc. Secondly, according to the second custodial transfer processing logic, the total amount of resources in the object resource holding table is updated according to the determined amount of custodial transfer resources, specifically the total amount of resources in the object resource holding table is increased. Thirdly, a new record of the failed confirmation of the custodial transfer-out confirming party is added to the resource change details table, and the resource change flag of "5-transfer to custodial" and the resource change category of "7-transfer to custodial transfer-out return accounting" are added to the record of the failed confirmation of the custodial transfer-out confirming party.

[0104] In an exemplary embodiment, if the custody transfer processing logic corresponding to the custody transfer success scenario is determined, the total amount of resources in the object resource holding table is updated according to the custody transfer processing logic and the determined custody transfer resource amount. Specifically, when there is resource holding data corresponding to the object identifier in the object resource holding table, the corresponding total amount of resources is increased, and when there is no resource holding data corresponding to the object identifier in the object resource holding table, the resource holding data corresponding to the object identifier is added.

[0105] For example, Fig. 9As shown in the figure, it provides an example of updating the object resource position table and resource change details table in the scenario of successful custody transfer. Fig. 9 It can be seen that in the scenario of successful custody transfer, first of all, it is also necessary to determine whether the request data is legal, including whether the field is empty or whether to review the business rules. Secondly, according to the custody transfer processing logic, the total amount of resources in the object resource holding table is updated according to the determined custody transfer resource quantity, wherein, specifically, when there is resource holding data corresponding to the object identifier in the object resource holding table, the corresponding total amount of resources increases, and when there is no resource holding data corresponding to the object identifier in the object resource holding table, the resource holding data corresponding to the object identifier is added. Third, a new custody transfer success record is added to the resource change details table, and the resource change flag of "5-Transfer custody" and the resource change category of "6-Transfer custody transfer accounting" are added to the custody transfer success record.

[0106] In an exemplary embodiment, if the custody freeze processing logic corresponding to the custody transfer-out freeze scenario is determined, the resource freeze share in the object resource holding table is updated according to the custody freeze processing logic. Specifically, the resource freeze share in the object resource holding table is increased. In the custody transfer-out freeze scenario, the custody transferable share must be less than or equal to the available share, and the available share = total resource share - special transaction freeze share - transaction freeze share in the next day's transaction mode.

[0107] For example, Fig.10 As shown in the figure, it provides a schematic diagram of updating the object resource position table in the scenario of frozen custody transfer. Fig.10 It can be seen that in the scenario of custody transfer freezing, first of all, it is also necessary to determine whether the request data is legal, including whether the field is empty or whether the business rules are reviewed. Secondly, according to the custody transfer freezing processing logic, the resource freezing share in the object resource holding table is updated, specifically, the resource freezing share in the object resource holding table is increased.

[0108] In an exemplary embodiment, if the third custody transfer processing logic corresponding to the custody transfer audit failure scenario is determined, the resource frozen share in the object resource holding table is updated according to the third custody transfer processing logic. Specifically, the resource frozen share in the object resource holding table is reduced, and the total amount of resources in the object resource holding table does not change.

[0109] For example, Fig.11 As shown in the figure, it provides a schematic diagram of updating the object resource position table in the scenario where the custody transfer review fails. Fig.11It can be seen that in the scenario where the custody transfer review fails, first of all, it is also necessary to determine whether the request data is legal, including whether the field is empty or whether the business rules are reviewed. Secondly, according to the third custody transfer processing logic corresponding to the custody transfer review failure, the resource frozen share in the object resource position table is updated, specifically, the resource frozen share in the object resource position table is reduced.

[0110] Step 606: Add a new custody transfer processing record to the resource change details table, and add a resource change flag and a resource change category to the custody transfer processing record according to the custody transfer processing logic.

[0111] Among them, the custody transfer processing records specifically include custody transfer-out review success records, custody transfer-out confirmation party confirmation failure records, and custody transfer-in success records. The custody transfer processing logic specifically includes the first custody transfer-out processing logic corresponding to the custody transfer-out review success scenario, the second custody transfer-out processing logic corresponding to the custody transfer-out confirmation party confirmation failure scenario, and the custody transfer-in processing logic corresponding to the custody transfer-in success scenario.

[0112] Specifically, in the scenario where the custody transfer-out audit is successful, a new custody transfer-out audit success record is added to the resource change details table, and the resource change flag of "5-Transfer custody" and the resource change category of "5-Transfer custody transfer-out accounting" are added to the custody transfer-out audit success record.

[0113] Optionally, in the scenario where the custody transfer-out confirming party fails to confirm, a new custody transfer-out confirming party failure confirmation record is added to the resource change details table, and the resource change flag of "5-Transfer custody" and the resource change category of "7-Transfer custody transfer-out return accounting" are added to the custody transfer-out confirming party failure confirmation record.

[0114] Optionally, in the scenario where the custody transfer is successful, a new custody transfer success record is added to the resource change details table, and the resource change flag of "5-Custody Transfer" and the resource change category of "6-Custody Transfer Accounting" are added to the custody transfer success record.

[0115] In this embodiment, when the resource interaction scenario to which the resource holding data belongs is a transfer custody processing scenario, the amount of custody transferred resources is determined based on the resource holding data, and the transfer custody processing logic matching the transfer custody processing scenario is determined. According to the transfer custody processing logic, the resource frozen share and / or the total amount of resources in the object resource holding table are updated according to the amount of custody transferred resources, and a new transfer custody processing record is added to the resource change details table. At the same time, according to the transfer custody processing logic, a resource change flag and a resource change category are added to the transfer custody processing record, thereby covering a variety of different resource interaction scenarios involved in the financial business processing process, so as to calculate the resource holding data in different resource interaction scenarios separately, so that the resource holding data in different resource interaction scenarios can be quickly queried or viewed according to actual needs in the future, avoiding the use of real-time recording, separate updating or separate accounting methods, which can reduce the resource quantity recording and calculation operations in the financial business processing process, and further improve the resource quantity accounting efficiency.

[0116] In an exemplary embodiment, Fig.12 As shown, in the resource liquidation scenario, the step of updating the object resource holding table and the resource change detail table, that is, determining the resource change processing logic matching the resource interaction scenario, and updating the object resource holding table and the resource change detail table according to the resource change processing logic and resource holding data, specifically includes steps 1202 to 1208. Among them:

[0117] Step 1202: When the resource interaction scenario to which the resource holding data belongs is a resource liquidation scenario, determine the liquidation resource quantity according to the resource holding data.

[0118] Specifically, the server may traverse or query the object resource holding table according to the object identifier to determine whether there is resource holding data matching the object identifier in the object resource holding table. If it is determined that there is resource holding data matching the object identifier in the object resource holding table, the resource interaction scenario to which the resource holding data belongs is further determined. If the resource interaction scenario to which the resource holding data belongs is a resource liquidation scenario, the liquidation resource quantity is determined according to the resource holding data.

[0119] Step 1204, determine the share of liquidable resources corresponding to the object identifier, and if it is determined that the liquidation resource amount is less than the share of liquidable resources, determine the resource liquidation processing logic corresponding to the resource liquidation scenario.

[0120] Specifically, the total amount of resources and the special frozen resource share corresponding to the object identifier are determined, and the difference between the total amount of resources and the special frozen resource share is calculated to obtain the liquidable resource share corresponding to the object identifier.

[0121] Furthermore, the amount of closed resources is compared with the share of available resources to determine whether the amount of closed resources is less than the share of available resources. If it is determined that the amount of closed resources is less than the share of available resources, the resource closing processing logic corresponding to the resource closing scenario is determined. The resource closing processing logic is used to update the object resource holding table and the resource change detail table.

[0122] Step 1206, according to the resource liquidation processing logic, trigger the frozen resource clearing processing in the next day's interactive mode, and update the total resource amount and holding cost in the object resource holding table according to the liquidated resource quantity.

[0123] Specifically, when the resource interaction scenario to which the resource position data belongs is the resource liquidation scenario, according to the resource liquidation processing logic, the frozen resource clearing processing in the next-day interaction mode is triggered, and specifically, the frozen resources in the next-day interaction mode in the object resource position table are cleared. Among them, the next-day interaction mode refers to the T+1 interaction mode. In the T+1 interaction mode, the resources transferred in on the same day need to be transferred out on the next trading day. "T" refers to the transaction registration day, and "T+1" refers to the day after the registration day.

[0124] Furthermore, the resource liquidation scenario can be understood as forcing the user's book-entry resources to be sold in advance before expiration, that is, the user's resource holding share is reduced and the holding cost changes. In the resource liquidation scenario, the server can update the total amount of resources and holding cost in the object resource holding table according to the resource liquidation processing logic. Specifically, the total amount of resources and holding cost in the object resource holding table are both reduced.

[0125] Step 1208, add a new resource closing record in the resource change details table, and add a resource change flag and a resource change category to the resource closing record according to the resource closing processing logic.

[0126] Specifically, when the resource interaction scenario is a resource liquidation scenario, a new resource liquidation record is added to the resource change details table, and according to the resource liquidation processing logic, a resource change flag of "1-spot transaction" and a resource change category of "2-sell" are added to the resource liquidation record.

[0127] In an exemplary embodiment, Fig.13 As shown, it provides an example of updating the object resource holding table in the resource freezing scenario. Fig.13 It can be seen that in the resource freezing scenario, first of all, it is also necessary to determine whether the request data is legal, including whether the field is empty or whether the business rules are reviewed. Secondly, the resource freezing amount is determined according to the resource holding data, and the resource freezing share in the object resource holding table is updated according to the resource freezing processing logic corresponding to the resource freezing scenario, specifically, the resource freezing share is increased.

[0128] Among them, in the resource freezing scenario, according to the resource freezing processing logic, the frozen resources in the next day interactive mode are cleared, specifically, the frozen resources in the next day interactive mode in the object resource holding table are cleared.

[0129] Furthermore, if Fig.14 As shown in the figure, it provides an example of updating the object resource holding table in the resource unfreezing scenario. Fig.14 It can be seen that in the resource freezing scenario, first of all, it is also necessary to determine whether the request data is legal, including whether the field is empty or whether the business rules are reviewed. Secondly, the resource unfreezing amount is determined according to the resource holding data, and the resource unfreezing share in the object resource holding table is updated according to the resource unfreezing processing logic corresponding to the resource unfreezing scenario, specifically, the resource frozen share is reduced.

[0130] In this embodiment, when the resource interaction scenario to which the resource holding data belongs is a resource liquidation scenario, the liquidation resource quantity is determined according to the resource holding data, and the liquidation resource share corresponding to the object identifier is determined, so as to determine that the liquidation resource quantity is less than the liquidation resource share, and determine the resource liquidation processing logic corresponding to the resource liquidation scenario. Further, according to the resource liquidation processing logic, the frozen resource zeroing processing in the next day's interactive mode is triggered, and according to the liquidation resource quantity, the total resource quantity and the holding cost in the object resource holding table are updated, and a resource liquidation record is added to the resource change detail table, and at the same time, according to the resource liquidation processing logic, a resource change flag and a resource change category are added to the resource liquidation record, so as to cover a variety of different resource interaction scenarios involved in the financial business processing process, so as to calculate the resource holding data in different resource interaction scenarios separately, so that the resource holding data in different resource interaction scenarios can be quickly queried or viewed according to actual needs in the future, avoiding the use of real-time recording, separate updating or separate accounting methods, which can reduce the resource quantity recording operation and calculation operation in the financial business processing process, and further improve the resource quantity accounting efficiency.

[0131] In an exemplary embodiment, a resource accounting processing method is provided, which specifically includes the following processing steps:

[0132] Step 1): the server receives a resource accounting request and obtains an object identifier corresponding to the resource accounting request.

[0133] Step 2), if the server determines that there is resource holding data matching the object identifier in the object resource holding table, the resource interaction scenario to which the resource holding data belongs is determined.

[0134] Step 3), when the resource interaction scenario to which the resource holding data belongs is a resource transfer-out scenario, the server determines a resource transfer-out processing logic that matches the resource transfer-out scenario.

[0135] Step 4), the server determines the resource transfer amount based on the resource holding data, and determines the available resource share corresponding to the object identifier.

[0136] In step 5, the server compares the resource transfer amount with the available resource share, and when it is determined that the available resource share is greater than the resource transfer amount, it is determined that the resource transfer amount meets the resource transfer condition.

[0137] Step 6), when the resource transfer amount meets the resource transfer conditions and the available resource share is greater than the resource transfer-out amount, the server subtracts the resource transfer-out amount to be transferred from the total resource amount currently recorded in the object resource holding table to obtain the updated total resource amount.

[0138] Step 7), the server adds a new resource transfer record in the resource change details table, and according to the resource transfer processing logic, adds the resource change flag of "1-cash transaction" and the resource change category of "1-sell" to the resource transfer record.

[0139] After executing step 2), execute step 8), when the resource interaction scenario to which the resource holding data belongs is a resource transfer-in scenario, the server determines a resource transfer-in processing logic that matches the resource transfer-in scenario.

[0140] Step 9), the server determines the amount of resource transfer based on the resource holding data, and determines the current resource share corresponding to the object identifier, obtains the preset share threshold value pre-set for the resource transfer scenario, and compares the current resource share with the preset share threshold value.

[0141] Step 10), if the current resource share is less than the preset share threshold, the server increases the total resource amount currently recorded in the object resource holding table by the current transferred-in resource transfer-out amount to obtain an updated total resource amount.

[0142] Step 11), the server adds a new resource transfer record in the resource change details table, and according to the resource transfer processing logic, adds the resource change flag of "1-spot transaction" and the resource change category of "1-buy" to the resource transfer record.

[0143] After executing step 2), execute step 12). When the resource interaction scenario to which the resource holding data belongs is a scenario where the custody transfer review is successful, the server determines the amount of custody transfer resources based on the resource holding data, and determines the first custody transfer processing logic corresponding to the custody transfer review success scenario.

[0144] Step 13), the server updates the resource freezing share and the total resource amount in the object resource holding table according to the determined amount of managed transfer resources in accordance with the first managed transfer-out processing logic.

[0145] Step 14), the server adds a new custody transfer review success record in the resource change details table, and adds the resource change flag of "5-Custody Transfer" and the resource change category of "5-Custody Transfer Accounting" to the custody transfer review success record.

[0146] After executing step 2), execute step 15). When the resource interaction scenario to which the resource holding data belongs is a scenario in which the custody transfer confirmation party fails to confirm, the server determines the amount of custody transfer resources based on the resource holding data, and determines the second custody transfer processing logic corresponding to the scenario in which the custody transfer confirmation party fails to confirm.

[0147] Step 16), the server updates the total amount of resources in the object resource holding table according to the determined amount of resources to be transferred out of custody in accordance with the second custody transfer-out processing logic.

[0148] Step 17), the server adds a new record of failed confirmation by the escrow transfer-out confirming party in the resource change details table, and adds the resource change flag of "5-transfer of escrow" and the resource change category of "7-transfer of escrow transfer-out return accounting" to the record of failed confirmation by the escrow transfer-out confirming party.

[0149] After executing step 2), execute step 18). When the resource interaction scenario to which the resource holding data belongs is a successful custody transfer scenario, the server determines the amount of custody transfer resources based on the resource holding data and determines the custody transfer processing logic corresponding to the successful custody transfer scenario.

[0150] Step 19), the server updates the total amount of resources in the object resource holding table according to the determined amount of resources transferred in custody in accordance with the custody transfer processing logic.

[0151] Step 20), the server adds a new custody transfer success record in the resource change details table, and adds the resource change flag "5-Custody Transfer" and the resource change category "6-Custody Transfer Accounting" to the custody transfer success record.

[0152] After executing step 2), execute step 21). When the resource interaction scenario to which the resource holding data belongs is a managed transfer-out freeze scenario, the server determines the managed freeze resource quantity based on the resource holding data, and determines the managed freeze processing logic corresponding to the managed transfer-out freeze scenario.

[0153] Step 22), the server updates the resource freezing share in the object resource holding table according to the managed freezing processing logic and the determined managed frozen resource quantity.

[0154] After executing step 2), execute step 23). When the resource interaction scenario to which the resource holding data belongs is a custody transfer review failure scenario, the server determines the custody transfer resource amount based on the resource holding data, and determines the third custody transfer processing logic corresponding to the custody transfer review failure scenario.

[0155] Step 24), the server updates the resource frozen share in the object resource holding table according to the third custody transfer-out processing logic and the custody transfer-out resource amount.

[0156] The above-mentioned resource accounting processing method can cover a variety of different resource interaction scenarios involved in the financial business processing process, so as to calculate the resource holding data in different resource interaction scenarios respectively, so that the resource holding data in different resource interaction scenarios can be quickly queried or viewed according to actual needs in the future, and by utilizing the resource change summary share, the updated object resource holding table is subjected to resource accounting processing, and the resource accounting result is obtained. The position data and change details corresponding to different resource interaction scenarios are summarized and calculated, and the real-time recording, separate update or separate accounting are avoided. The resource quantity recording operation and calculation operation in the financial business processing process can be reduced, and the resource quantity accounting efficiency is further improved.

[0157] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0158] Based on the same inventive concept, the embodiment of the present application also provides a resource accounting processing device for implementing the resource accounting processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more resource accounting processing device embodiments provided below can refer to the limitations on the resource accounting processing method above, and will not be repeated here.

[0159] In an exemplary embodiment, Fig.15As shown, a resource accounting processing device is provided, including: an object identification acquisition module 1502, a resource interaction scenario determination module 1504, a data update module 1506 and a resource accounting processing module 1508, wherein:

[0160] The object identification acquisition module 1502 is used to receive a resource accounting request and acquire an object identification corresponding to the resource accounting request;

[0161] The resource interaction scenario determination module 1504 is used to determine the resource interaction scenario to which the resource holding data belongs if it is determined that there is resource holding data matching the object identifier in the object resource holding table;

[0162] The data update module 1506 is used to determine the resource change processing logic that matches the resource interaction scenario, and update the object resource holding table and resource change detail table according to the resource change processing logic and resource holding data;

[0163] The resource accounting processing module 1508 is used to perform resource change summary processing based on the updated resource change details table, obtain the resource change summary share corresponding to the object identifier, and perform resource accounting processing on the updated object resource holding table based on the resource change summary share to obtain the resource accounting result.

[0164] In the above-mentioned resource accounting processing device, by receiving a resource accounting request, an object identifier corresponding to the resource accounting request is obtained, and when it is determined that there is resource holding data matching the object identifier in the object resource holding table, the resource interaction scenario to which the resource holding data belongs is determined, thereby covering a variety of different resource interaction scenarios involved in the financial business processing process, so as to calculate the resource holding data in different resource interaction scenarios separately, so that the resource holding data in different resource interaction scenarios can be quickly queried or viewed according to actual needs later. Furthermore, by determining the resource change processing logic that matches the resource interaction scenario, the object resource holding table and the resource change details table are updated according to the resource change processing logic and the resource holding data, and the resource change summary processing is performed based on the updated resource change details table to obtain the resource change summary share corresponding to the object identifier, and the resource accounting processing is performed on the updated object resource holding table according to the resource change summary share to obtain the resource accounting result. This realizes the change summary and accounting of the holding data and change details corresponding to different resource interaction scenarios, and avoids the use of real-time recording, separate updating or separate accounting. This can reduce the resource quantity recording and calculation operations in the financial business processing process, and further improve the resource quantity accounting efficiency.

[0165] In an exemplary embodiment, the resource accounting processing module also includes: a daily share change record determination unit, which is used to determine the daily share change records associated with the object identifier in different resource interaction scenarios based on the updated resource change details table; a resource change summary share determination unit, which is used to perform resource change summary processing on the daily share change records in different resource interaction scenarios to obtain the resource change summary shares corresponding to the object identifier.

[0166] In an exemplary embodiment, the resource accounting processing module also includes: a unit for determining the total resource share of the day, which is used to determine the resource balance of the previous day corresponding to the share change record of the day, and determine the total resource share of the day according to the resource change summary share and the resource balance of the previous day; a resource accounting unit, which is used to perform resource accounting processing on the total amount of resources in the updated object resource holding table according to the total resource share of the day; and a resource accounting result acquisition unit, which is used to obtain a resource accounting result with consistent resource amount if it is determined that the total resource share of the day is consistent with the updated total resource amount.

[0167] In an exemplary embodiment, the resource accounting processing module also includes: a resource transfer processing logic determination unit, which is used to determine the resource transfer processing logic that matches the resource transfer scenario when the resource interaction scenario to which the resource holding data belongs is a resource transfer scenario; a first update unit, which is used to determine the resource transfer amount based on the resource holding data, and if the resource transfer amount meets the resource transfer conditions, according to the resource transfer processing logic, update the total amount of resources in the object resource holding table according to the resource transfer amount; a resource transfer record adding unit, which is used to add a resource transfer record to the resource change details table, and add a resource change flag and a resource change category to the resource transfer record according to the resource transfer processing logic.

[0168] In an exemplary embodiment, the resource accounting processing module also includes: a custody transfer resource quantity determination unit, which is used to determine the custody transfer resource quantity based on the resource holding data when the resource interaction scenario to which the resource holding data belongs is a custody transfer processing scenario; a second updating unit, which is used to determine the custody transfer processing logic that matches the custody transfer processing scenario, and according to the custody transfer processing logic, updates the resource frozen share and / or the total resource quantity in the object resource holding table according to the custody transfer resource quantity; a custody transfer processing record adding unit, which is used to add a custody transfer processing record to the resource change details table, and according to the custody transfer processing logic, add a resource change flag and a resource change category to the custody transfer processing record.

[0169] In an exemplary embodiment, the resource accounting processing module also includes: a resource closing processing logic determination unit, which is used to determine the share of liquidable resources corresponding to the object identifier, and if it is determined that the liquidated resource amount is less than the liquidated resource share, determine the resource closing processing logic corresponding to the resource closing scenario; a third updating unit, which is used to trigger the frozen resource clearing processing in the next day's interactive mode according to the resource closing processing logic, and update the total resource amount and holding cost in the object resource holding table according to the liquidated resource amount; a resource closing record adding unit, which is used to add a resource closing record to the resource change details table, and add a resource change flag and resource change category to the resource closing record according to the resource closing processing logic.

[0170] Each module in the resource accounting processing device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0171] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG16. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as object identification, object resource holding table, resource holding data, resource interaction scenario, resource change processing logic, resource change detail table, resource change summary share, and resource accounting results corresponding to the resource accounting request. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a resource accounting processing method is implemented.

[0172] Those skilled in the art will understand that the structure shown in FIG. 16 is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0173] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and each embodiment of the resource accounting processing method described above is implemented when the processor executes the computer program.

[0174] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, each embodiment of the resource accounting processing method described above is implemented.

[0175] In one embodiment, a computer program product is provided, including a computer program, which implements the various embodiments of the resource accounting processing method when executed by a processor.

[0176] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0177] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0178] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A resource accounting processing method, characterized in that: The method comprises: Receive a resource accounting request and obtain an object identifier corresponding to the resource accounting request; If it is determined that there is resource holding data matching the object identifier in the object resource holding table, determining the resource interaction scenario to which the resource holding data belongs; Determine a resource change processing logic that matches the resource interaction scenario, and update the object resource holding table and resource change detail table according to the resource change processing logic and the resource holding data; Based on the updated resource change details table, resource change summary processing is performed to obtain the resource change summary share corresponding to the object identifier, and according to the resource change summary share, resource accounting processing is performed on the updated object resource holding table to obtain the resource accounting result.

2. The method according to claim 1, characterized in that The performing resource change summary processing based on the updated resource change detail table to obtain the resource change summary share corresponding to the object identifier includes: Based on the updated resource change details table, determine the daily share change records associated with the object identifier in different resource interaction scenarios; The resource change summary processing is performed on the daily share change records in the different resource interaction scenarios to obtain the resource change summary share corresponding to the object identifier.

3. The method according to claim 2, characterized in that The step of performing resource accounting processing on the updated object resource holding table according to the resource change summary share to obtain a resource accounting result includes: Determine the resource surplus of the previous day corresponding to the share change record of the current day, and determine the total resource share of the current day according to the resource change summary share and the resource surplus of the previous day; According to the total resource share of the day, resource accounting processing is performed on the total amount of resources in the updated object resource holding table; If it is determined that the total resource share for the day is consistent with the updated total resource amount, a resource accounting result with consistent resource amount is obtained.

4. The method according to any one of claims 1 to 3, characterized in that: The determining of the resource change processing logic matching the resource interaction scenario, and updating the object resource holding table and the resource change detail table according to the resource change processing logic and the resource holding data, comprises: In a case where the resource interaction scenario to which the resource holding data belongs is a resource transfer scenario, determining a resource transfer processing logic matching the resource transfer scenario; Determine the resource transfer amount according to the resource holding data, and if the resource transfer amount meets the resource transfer condition, update the total amount of resources in the object resource holding table according to the resource transfer amount according to the resource transfer processing logic; A new resource transfer record is added to the resource change details table, and a resource change flag and a resource change category are added to the resource transfer record according to the resource transfer processing logic.

5. The method according to any one of claims 1 to 3, characterized in that: The determining of the resource change processing logic matching the resource interaction scenario, and updating the object resource holding table and the resource change detail table according to the resource change processing logic and the resource holding data, comprises: In a case where the resource interaction scenario to which the resource holding data belongs is a custody transfer processing scenario, determining the custody transfer resource amount according to the resource holding data; Determine the custody transfer processing logic matching the custody transfer processing scenario, and update the resource freezing share and / or total resource amount in the object resource holding table according to the custody transfer processing logic and the custody transfer resource amount; A new custody transfer processing record is added to the resource change details table, and a resource change flag and a resource change category are added to the custody transfer processing record according to the custody transfer processing logic.

6. The method according to any one of claims 1 to 3, characterized in that: The determining of the resource change processing logic matching the resource interaction scenario, and updating the object resource holding table and the resource change detail table according to the resource change processing logic and the resource holding data, comprises: In a case where the resource interaction scenario to which the resource holding data belongs is a resource liquidation scenario, determining a liquidation resource quantity according to the resource holding data; Determine the liquidation resource share corresponding to the object identifier, and if it is determined that the liquidation resource amount is less than the liquidation resource share, determine the resource liquidation processing logic corresponding to the resource liquidation scenario; According to the resource liquidation processing logic, trigger the clearing processing of frozen resources in the next day's interactive mode, and update the total resource amount and holding cost in the object resource holding table according to the liquidated resource amount; A resource closing record is newly added to the resource change detail table, and a resource change flag and a resource change category are added to the resource closing record according to the resource closing processing logic.

7. A resource accounting processing device, characterized in that: The device comprises: An object identification acquisition module is used to receive a resource accounting request and obtain an object identification corresponding to the resource accounting request; A resource interaction scenario determination module, configured to determine the resource interaction scenario to which the resource holding data belongs if resource holding data matching the object identifier exists in the object resource holding table; A data update module, used to determine the resource change processing logic matching the resource interaction scenario, and update the object resource holding table and resource change detail table according to the resource change processing logic and the resource holding data; The resource accounting processing module is used to perform resource change summary processing based on the updated resource change details table, obtain the resource change summary share corresponding to the object identifier, and perform resource accounting processing on the updated object resource holding table according to the resource change summary share to obtain the resource accounting result.

8. The device according to claim 7, characterized in that The resource accounting processing module further includes: A daily share change record determination unit, configured to determine, based on the updated resource change detail table, daily share change records associated with the object identifier in different resource interaction scenarios; The resource change summary share determination unit is used to perform resource change summary processing on the daily share change records under the different resource interaction scenarios to obtain the resource change summary share corresponding to the object identifier.

9. The device according to claim 8, characterized in that The resource accounting processing module further includes: The total resource share determination unit for the current day is used to determine the resource surplus of the previous day corresponding to the current day share change record, and determine the total resource share of the current day according to the resource change summary share and the resource surplus of the previous day; A resource accounting unit, configured to perform resource accounting processing on the total amount of resources in the updated object resource holding table according to the total resource share of the day; The resource accounting result obtaining unit is used to obtain a resource accounting result with consistent resource quantity if it is determined that the total resource share of the day is consistent with the updated total resource quantity.

10. The device according to any one of claims 6 to 9, characterized in that The data updating module further includes: A resource transfer processing logic determination unit, configured to determine a resource transfer processing logic matching the resource transfer scenario when the resource interaction scenario to which the resource holding data belongs is a resource transfer scenario; A first updating unit, configured to determine a resource transfer amount according to the resource holding data, and if the resource transfer amount satisfies a resource transfer condition, update the total amount of resources in the object resource holding table according to the resource transfer amount according to the resource transfer processing logic; The resource transfer record adding unit is used to add a resource transfer record to the resource change details table, and add a resource change flag and a resource change category to the resource transfer record according to the resource transfer processing logic.

11. The device according to any one of claims 6 to 9, characterized in that The data updating module further includes: A custody transfer resource quantity determination unit, configured to determine the custody transfer resource quantity according to the resource holding data when the resource interaction scenario to which the resource holding data belongs is a custody transfer processing scenario; A second updating unit is used to determine a custody transfer processing logic that matches the custody transfer processing scenario, and update the resource freezing share and / or total resource amount in the object resource holding table according to the custody transfer processing logic and the custody transfer resource amount; The custody transfer processing record adding unit is used to add a custody transfer processing record to the resource change details table, and add a resource change flag and a resource change category to the custody transfer processing record according to the custody transfer processing logic.

12. The device according to any one of claims 6 to 9, characterized in that The data updating module further includes: a resource liquidation processing logic determining unit, configured to determine a liquidable resource share corresponding to the object identifier, and if it is determined that the liquidation resource amount is less than the liquidable resource share, determine a resource liquidation processing logic corresponding to the resource liquidation scenario; A third updating unit is used to trigger the clearing of frozen resources in the next day's interactive mode according to the resource liquidation processing logic, and update the total amount of resources and the holding cost in the object resource holding table according to the liquidation resource amount; The resource closing record adding unit is used to add a resource closing record to the resource change detail table, and add a resource change flag and a resource change category to the resource closing record according to the resource closing processing logic.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images