Transaction data calculation method, device, electronic device and storage medium

Abstract

The present disclosure provides a method for accounting for transaction data, including: parsing the business logic of a specified product agreement to obtain all agreement objects contained in the business logic. Determining the hierarchical relationship between agreement objects and the accounting elements related to each agreement object. Obtaining specified data from the data to be accounted for, the specified data being the transaction data corresponding to the accounting element. Based on the transaction data and the hierarchical relationship, constructing a hierarchical data accounting table, the hierarchical data accounting table counting the transaction data of the agreement objects of at least one level. The present disclosure also provides a transaction data accounting device, an electronic device, and a computer-readable storage medium.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and more specifically, to a method, device, electronic device and storage medium for calculating transaction data. Background Art

[0002] The traditional construction of banking information systems is product-centric. Through structured analysis (SA) and structured design (SD), each function in the core banking business process is modularized to maintain the independence of each module. The traditional product-centric modular R&D model couples key elements such as product agreements, balance accounts, and amounts. In a period when business processes are relatively stable and product types and attributes are relatively fixed, each product line can easily obtain a closed-loop view of global business data from its own product perspective, with clear interfaces, easy implementation, easy understanding, and easy modification and maintenance.

[0003] In the process of realizing the concept of the present disclosure, the inventors found that there are at least the following problems in the related technology: when the product sub-agreement is strongly associated with the account balance, amount, and period details, the loan product sub-agreement mark will run through the system itself as an accounting unit and connect to the upstream and downstream systems. Changes in the attributes of the product sub-agreement will directly affect the management of the balance and amount, and changes in the rules of the balance and amount will also directly affect the logical association of the product sub-agreement. Both parties need to be transformed simultaneously to complete a closed loop of business demand transformation.

[0004] Against the backdrop of today's increasingly rapid innovation and the continuous emergence of new business forms, new scenarios, and new models, this deeply bundled relationship has led to various drawbacks when banks transform their systems in response to business innovation, such as involving too many impacts, lengthening R&D cycles, slower response to business needs, and insufficient flexibility in product outcomes. Summary of the invention

[0005] In view of this, the present disclosure provides a method and device for calculating transaction data.

[0006] One aspect of the present disclosure provides a method for accounting for transaction data, comprising: parsing the business logic of a specified product agreement to obtain all agreement objects contained in the business logic. Determining the hierarchical relationship between the agreement objects and the accounting elements related to each of the agreement objects. Obtaining specified data from the data to be accounted for, the specified data being the transaction data corresponding to the accounting elements. Based on the transaction data and the hierarchical relationship, constructing a hierarchical data accounting table, the hierarchical data accounting table counting the transaction data of the agreement objects of at least one level.

[0007] According to an embodiment of the present disclosure, determining the hierarchical relationship between the protocol objects and the accounting elements related to each protocol object includes: determining whether the designated product protocol contains historical business logic; if the designated product protocol contains historical business logic, parsing the historical protocol objects contained in the historical business logic; determining the hierarchical relationship between the historical protocol objects and the protocol objects, and determining the accounting elements related to each historical protocol object and the accounting elements related to the protocol objects.

[0008] According to an embodiment of the present disclosure, when the hierarchical data accounting table counts transaction data of protocol objects of multiple levels, the hierarchical data accounting table is constructed based on the transaction data and the hierarchical relationship, and the hierarchical data accounting table counts transaction data of protocol objects of at least one level, including: selecting multiple target protocol objects, and the multiple target protocol objects have a hierarchical relationship; respectively determining the transaction data corresponding to the accounting elements related to the multiple target protocol objects; and constructing a target hierarchical data accounting table based on the hierarchical relationship between the multiple target protocols and the transaction data.

[0009] According to an embodiment of the present disclosure, determining the hierarchical relationship between the protocol objects and the accounting elements related to each of the protocol objects also includes: identifying the protocol parent object and protocol child objects contained in the protocol object, the protocol parent object having at least one level of protocol child objects; determining the accounting elements related to the protocol parent object and the accounting elements related to the protocol child objects at each level.

[0010] According to an embodiment of the present disclosure, the agreement parent object includes a product agreement number; the next-level agreement child object of the product agreement number includes a balance number; and the next-level agreement child object of the balance number includes a balance type.

[0011] According to an embodiment of the present disclosure, the accounting elements include at least one of the level type, level balance, interest balance, occurrence amount, occurrence details, debit and credit identification, work date, business number, and detail serial number.

[0012] According to an embodiment of the present disclosure, before obtaining designated data from the data to be accounted, wherein the designated data is the transaction data corresponding to the accounting element, the method further includes: preprocessing the data to be accounted, wherein the preprocessing includes performing a legality check and data format switching on the data to be processed.

[0013] Another aspect of the present disclosure provides an accounting device for transaction data, including: a parsing module, used to parse the business logic of a specified product agreement to obtain all agreement objects contained in the business logic; a determination module, used to determine the hierarchical relationship between the agreement objects and the accounting elements related to each of the agreement objects; an acquisition module, used to obtain specified data from the data to be accounted for, the specified data being the transaction data corresponding to the accounting elements; and a construction module, used to construct a hierarchical data accounting table based on the transaction data and the hierarchical relationship, the hierarchical data accounting table counting the transaction data of the agreement objects of at least one level.

[0014] Another aspect of the present disclosure provides an electronic device, which includes one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any of the methods described above.

[0015] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above method when executed.

[0016] According to the embodiments of the present disclosure, a method is provided for reconstructing and extracting product management and account balance management in a traditional core banking information system. By unbinding the hard association between product agreements and balances and amounts, the balance management logic is relatively transparent to the product business logic. At the same time, the adjustment of business rules does not directly affect the management of balances and amounts, which reduces the impact of the transformation of the product information system when adjusting business needs, and achieves the technical effect of meeting the business development needs of the bank faster and more efficiently. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0018] Figure 1 An exemplary system architecture to which the method and apparatus for accounting of transaction data disclosed in the present invention can be applied is schematically shown;

[0019] Figure 2A and 2B The application scenario of the transaction data accounting method according to the embodiment of the present disclosure is schematically shown;

[0020] Figure 3 A flowchart schematically shows a method for calculating transaction data according to an embodiment of the present disclosure;

[0021] Figure 4AA flowchart schematically shows a method for calculating transaction data according to another embodiment of the present disclosure;

[0022] Figure 4B A flowchart schematically shows a method for calculating transaction data according to another embodiment of the present disclosure;

[0023] Figure 4C A flowchart schematically shows a method for calculating transaction data according to another embodiment of the present disclosure;

[0024] Figure 4D A flowchart schematically shows a method for calculating transaction data according to another embodiment of the present disclosure;

[0025] Figure 5 A block diagram schematically shows a transaction data accounting device according to an embodiment of the present disclosure;

[0026] Fig. 6A A block diagram schematically shows a transaction data accounting device according to another embodiment of the present disclosure;

[0027] Figure 6B A block diagram schematically shows a transaction data accounting device according to another embodiment of the present disclosure;

[0028] Figure 6C A block diagram schematically shows a transaction data accounting device according to another embodiment of the present disclosure;

[0029] Fig.6D A block diagram schematically shows a transaction data accounting device according to another embodiment of the present disclosure; and

[0030] Figure 7 A block diagram of an electronic device suitable for a transaction data accounting device according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0031] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0032] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0033] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0034] In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0035] The embodiments of the present disclosure provide a method and device for accounting of transaction data. The method includes a process of parsing business logic and a process of accounting balance. In the process of parsing business logic, the business logic of a specified product agreement is parsed to obtain all agreement objects contained in the business logic. Then, the hierarchical relationship between the agreement objects and the accounting elements related to each agreement object are determined. Specified data is obtained from the data to be accounted for, and the specified data is the transaction data corresponding to the accounting element. Based on the transaction data and the hierarchical relationship, a hierarchical data accounting table is constructed, and the hierarchical data accounting table counts the transaction data of the agreement objects of at least one level, thereby realizing the accounting of the balance.

[0036] Figure 1 The exemplary system architecture 100 to which the transaction data accounting method and device according to the embodiment of the present disclosure can be applied is schematically shown. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0037] like Figure 1As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired and / or wireless communication links, etc.

[0038] The user can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 101, 102, 103, such as mobile banking applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients and / or social platform software, etc. (only as examples).

[0039] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0040] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0041] It should be noted that the accounting method for transaction data provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the accounting device for transaction data provided in the embodiment of the present disclosure can generally be set in the server 105. The accounting method for transaction data provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Correspondingly, the accounting device for transaction data provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Alternatively, the accounting method for transaction data provided in the embodiment of the present disclosure can also be executed by the terminal devices 101, 102, or 103, or can also be executed by other terminal devices different from the terminal devices 101, 102, or 103. Accordingly, the transaction data accounting device provided in the embodiment of the present disclosure may also be set in the terminal device 101, 102, or 103, or in other terminal devices different from the terminal device 101, 102, or 103.

[0042] For example, the data to be accounted and the product agreement may be originally stored in any one of the terminal devices 101, 102, or 103 (for example, the terminal device 101, but not limited thereto), or stored in an external storage device and may be imported into the terminal device 101. Then, the terminal device 101 may locally execute the accounting method for transaction data provided by the embodiment of the present disclosure, or send the data to be accounted and the product agreement to other terminal devices, servers, or server clusters, and the other terminal devices, servers, or server clusters that receive the data to be accounted and the product agreement may execute the accounting method for transaction data provided by the embodiment of the present disclosure.

[0043] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0044] Figure 2A and 2B The application scenario of the transaction data accounting method according to the embodiment of the present disclosure is schematically illustrated.

[0045] like Figure 2A As shown in the figure, common banks form a centralized system with product sub-agreements as the center. Taking a certain loan product as an example, the product sub-agreement (IOU) becomes the central coupling point of the entire loan accounting. The product sub-agreement has a strong association with the account balance, amount, and period details. The loan product sub-agreement marked "IOU" will be used as an accounting unit throughout the system itself and connect to upstream and downstream systems. There is a mutual influence between the product sub-agreement and the accounting elements (balance, amount, etc.). Changes in the product sub-agreement attributes (such as the status of newly added IOUs, no balance information in a specific status, etc.) will directly affect the accounting rules of balances and amounts. Changes in the accounting rules of balances and amounts (such as adjustments to account management rules, changes in account entries, etc.) will also directly affect the logical association of product sub-agreements.

[0046] like Figure 2B As shown, the transaction data accounting system disclosed in this disclosure is based on the premise of fully identifying the product business logic and account balance management logic in the product application system, clarifying the data entities involved in the product business process, clarifying their respective ownership, and unbinding the strong association between the product sub-agreement and the account balance and the amount of occurrence from the data storage level. After the unbinding is completed, the data access logic of the product layer is transparent to the account balance management layer.

[0047] By analyzing the business logic, sorting and routing the relationships between various accounting elements involved in the transaction data accounting rules, the association between product sub-agreements and balances (transaction data) is determined. At the same time, hierarchical statistics of different dimensions are performed on the relationships between the agreement objects and accounting elements involved in the accounting rules.

[0048] In this mode, the modification of product-level business rules will not affect the account balance management layer, and the account balance management layer only involves the management of balances and amounts. Its own data structure and logic remain relatively general, simple, and stable. In other words, product-level rules can be flexible and changeable, and the management rules within balance management can also be changed as needed, but the two will not have a mutually restrictive relationship. This can significantly improve the efficiency of the bank's information system in responding to business needs.

[0049] In order to better understand the professional terms involved in this plan, the relevant concepts are explained below.

[0050] (1) Product agreement: a legally binding contract signed by two parties A and B after reaching an agreement after negotiation in order to achieve certain common interests and wishes. In the banking industry, it generally refers to products involving fund transactions such as deposits, loans, and wealth management signed with customers. Banks use product agreements as a dimension as a carrier for business process processing in information systems. One product agreement (main agreement) can have multiple product sub-agreements attached to it.

[0051] (2) Product sub-agreement: a sub-contract signed under the framework of the product master agreement for specific detailed terms. Taking the banking industry as an example, a borrower (customer) needs to sign a loan contract when applying for a loan from a bank. This contract is the product master agreement for the loan, which stipulates the total amount of loans that can be issued, the maximum term, the product type, the product start and end dates, and other information. After the loan contract is signed, under the constraints of the loan amount and the product start and end dates, the bank can issue loans in batches according to actual conditions. Each time a loan is issued, a product sub-agreement (identified by "product agreement number + sub-agreement serial number", the sub-agreement of the loan product is referred to as "loan note") will be generated for accounting and management. The product sub-agreements are relatively independent of each other.

[0052] (3) Accounting balance: used to record the account balance of a specific product sub-agreement, recorded under a specific accounting title according to the debit and credit attributes of bank accounting, referred to as "balance". For example, a customer obtains a loan of 1 million yuan from a bank on day T, and the balance of the IOU at the end of day T is 1 million yuan. On day T+2, he returns 200,000 yuan to the bank, and the balance at the end of day T+2 is 800,000 yuan.

[0053] (4) Calculation of occurrence amount: used to record the change in the account balance of a specific product sub-agreement. The change amount can be positive or negative depending on the scenario, also referred to as "occurrence amount details". The bank calculates the balance and occurrence amount of a specific product sub-agreement at a certain point in time and in a certain scenario through the equation "end-of-period balance = beginning-of-period balance + current occurrence amount". For example, in the previous example, the beginning balance on date T is 0, the occurrence amount is 1 million, the ending balance on date T = 0 + 100 = 1 million, the beginning of the month on date T+2 is 1 million, the occurrence amount is -200,000, and the ending balance on date T = 1 million - 200,000 = 800,000.

[0054] (5) Period details: detailed information on the amount of payment obligations to be performed by both parties at a specific agreed time point, generated based on the product sub-agreement. Period details are an important calculation basis for core bank loans, time deposits and other periodic income products. For example, a customer obtained a loan of 1.2 million yuan from a bank on January 1 of the same year. The agreement stipulates that the principal should be repaid monthly and all interest should be repaid in the last month. In this case, period details will be generated on February 1 of the same year, March 1 of the same year, and so on until January 1 of the following year to record the principal and interest that the customer should repay (the amount to be repaid in each period is 100,000 yuan in principal, and the amount to be repaid in the last period is 100,000 yuan + interest).

[0055] Figure 3 A flowchart of a method for calculating transaction data according to an embodiment of the present disclosure is schematically shown.

[0056] like Figure 3 As shown, the method includes operations S201 to S204.

[0057] In operation S201, the business logic of the specified product protocol is parsed to obtain all protocol objects included in the business logic.

[0058] In operation S202, the hierarchical relationship between the agreement objects and the accounting elements related to each agreement object are determined.

[0059] In operation S203, designated data is obtained from the data to be calculated, where the designated data is transaction data corresponding to the calculation element.

[0060] In operation S204, a hierarchical data accounting table is constructed based on the transaction data and the hierarchical relationship, and the hierarchical data accounting table counts the transaction data of the agreement objects of at least one level.

[0061] In the public embodiments, the business logic of the bank's products is very complex. For example, loan products involve the acquisition of various interest rates such as fixed / variable, the calculation of interest amounts, the provision of interest income, repayments in various scenarios (such as normal, early, overdue), the transfer of non-performing loans to bad loans, and the return after the write-off, etc. At the same time, in response to the needs of business innovation, a new repayment method will be added, resulting in changes in the interest calculation formula. Therefore, when the terms of the product sub-agreement are implemented in the flexible and changeable business logic of the system, the balance accounting method needs to be more scalable.

[0062] This disclosure parses the business logic in the product agreement to obtain all the agreement objects involved in the business logic, which can lock the boundaries of the accounting rules and clarify the product business logic. Taking the loan product application system as an example, when a new business scenario appears and causes changes in business elements (such as customized requirements for interest rate types and calculation cycles), the new business logic can be parsed to quickly clarify the relevant agreement objects that are added or deleted without causing significant impact on other subsequent steps.

[0063] The agreement object includes but is not limited to the agreement number, sub-agreement serial number, balance number, and balance type. The accounting elements of the agreement object include but are not limited to the level type, level balance, interest balance, amount, details, debit and credit identification, work date, business number, and detail serial number.

[0064] The hierarchical data accounting table reflects the association between the balance level and the product sub-agreement. The balance level can be expanded vertically, and each level of balance can be attached with multiple hierarchical serial numbers and the balance number is used as the unique identifier. For example, the agreement parent object is the product agreement number, the next level agreement sub-object of the product agreement number includes the balance number, and the next level agreement sub-object of the balance number includes the balance type. The accounting elements of the product agreement number include the level type, working date, level sequence number, error level sequence number, level status, etc. The accounting elements of the balance number include the level balance, account balance, interest balance, working date, etc. The accounting elements of the balance type include the balance account, account number, working date, amount of occurrence, current level balance, current account balance, debit and credit flag, etc.

[0065] After determining the accounting elements related to each agreement object, obtain the transaction data corresponding to the accounting elements from the business data. Construct a hierarchical data accounting table based on the transaction data and hierarchical relationships. The hierarchical data accounting table can be constructed based on the transaction data corresponding to the accounting elements of one agreement object, or it can be constructed based on the transaction data corresponding to the accounting elements of agreement objects with adjacent hierarchical relationships. The hierarchical relationship between agreement objects can be set according to actual accounting needs. It can be one-to-one by default or one-to-many, and can be flexibly customized according to the actual needs of the product application system.

[0066] Through the disclosed embodiments, the core bank account processing logic is extracted to improve the efficiency of account processing. Key accounting elements such as accounting subjects, balances, and details of amounts incurred do not directly rely on the business logic at the product level, which better ensures the closed loop of business logic. It alleviates the constraints on bank technology research and development and business development, unties the strong correlation between core bank product sub-agreements and balance management, and avoids the mutual influence of balance accounting management rule adjustments and product business adjustments. It improves the flexibility of the research and development of core bank product application systems, and the application research and development in the two directions of product logic modules and balance logic modules can be implemented by different teams. Optimize the architectural layout of the core bank product application system to make it more reasonably connected to upstream and downstream application systems.

[0067] Reference below Figure 4A to Figure 4D , combined with specific embodiments Figure 3 The method shown is further explained.

[0068] Figure 4A A flowchart of a method for calculating transaction data according to another embodiment of the present disclosure is schematically shown.

[0069] like Figure 4A As shown, determining the hierarchical relationship between protocol objects and the accounting elements related to each protocol object includes operations S301~S303.

[0070] In operation S301 , it is determined whether the specified product agreement contains historical business logic.

[0071] In operation S302, if the designated product protocol includes historical business logic, the historical protocol object included in the historical business logic is parsed.

[0072] In operation S303, the hierarchical relationship between the historical protocol objects and the protocol objects is determined, and the accounting elements related to each historical protocol object and the accounting elements related to the protocol objects are determined.

[0073] In the disclosed embodiment, when the business logic of the product agreement changes, the historical hierarchical data accounting table can be modified according to the relationship between the agreement objects. The amount of modification of the accounting rules caused by the change of business logic is further reduced. For example, when the transaction participant under the same product agreement number changes, the level type to which the participant belongs and the balance number to which it belongs can be directly determined. The accounting element of the balance number is added to the historical hierarchical data accounting table, and the transaction data corresponding to the accounting element is obtained, so as to obtain the hierarchical data accounting table after the business logic is modified.

[0074] Figure 4B A flowchart of a method for calculating transaction data according to another embodiment of the present disclosure is schematically shown.

[0075] like Figure 4BAs shown, when the hierarchical data accounting table counts the transaction data of protocol objects of multiple levels, a hierarchical data accounting table is constructed based on the transaction data and the hierarchical relationship. The hierarchical data accounting table counts the transaction data of protocol objects of at least one level, including operations S304~S304.

[0076] In operation S304, a plurality of target protocol objects are selected, and a hierarchical relationship exists between the plurality of target protocol objects.

[0077] In operation S305, transaction data corresponding to the accounting elements related to the multiple target agreement objects are respectively determined.

[0078] In operation S306, a target hierarchical data accounting table is constructed based on the hierarchical relationship and transaction data between the multiple target protocols.

[0079] In the disclosed embodiment, there are multiple hierarchical data accounting tables, and each hierarchical data accounting table includes transaction data corresponding to the accounting object of at least one agreement object. For example, each balance number can be linked to multiple balance types, and the accounts, balances, and interest balances of specific business scenarios are recorded through "balance number + balance type". The occurrence details of the corresponding balance types of each balance level of the product are recorded through "balance number + balance type + working date + system business number + detail sequence number".

[0080] Specifically, according to the actual needs of the user, multiple target protocol objects are determined, and there is an adjacent hierarchical relationship between the multiple target protocol objects. The accounting elements of each target protocol object are further determined, the transaction data corresponding to the accounting elements are obtained, and the corresponding hierarchical data accounting table is constructed.

[0081] Figure 4C A flowchart of a method for calculating transaction data according to another embodiment of the present disclosure is schematically shown.

[0082] like Figure 4C As shown, determining the hierarchical relationship between protocol objects and the accounting elements related to each protocol object also includes operations S307~S308.

[0083] In operation S307, a protocol parent object and a protocol child object contained in the protocol object are identified, and the protocol parent object has at least one level of protocol child objects.

[0084] In operation S308, the accounting elements related to the agreement parent object and the accounting elements related to the agreement child objects at each level are determined.

[0085] In the disclosed embodiment, after obtaining all the protocol objects in the business logic, the hierarchical relationship between the protocol objects is determined. Specifically, the parent objects and child objects in all the protocol objects are determined, and a parent object has at least one child object. The hierarchical relationship is determined based on the relationship between the parent object and each child object. It should be noted that the relationship between the parent object and the child object can be flexibly set according to the actual needs of the product application system. Accordingly, the accounting elements related to the protocol parent object and the accounting elements related to the protocol child objects at each level are determined.

[0086] Through the embodiments of the present disclosure, the hierarchical relationship of all protocol objects in the business logic is clarified, so that in the process of transaction data accounting, the corresponding transaction data can be obtained directly according to the accounting elements of the protocol objects, without relying on the protocol sub-objects to calculate the transaction data, thereby realizing the decentralization of the accounting process.

[0087] Figure 4D A flowchart of a method for calculating transaction data according to another embodiment of the present disclosure is schematically shown.

[0088] like Figure 4D As shown, before obtaining designated data from the data to be calculated, where the designated data is transaction data corresponding to the accounting element, the method further includes operation S309.

[0089] In operation S309, the data to be calculated is preprocessed, and the preprocessing includes checking the legality of the data to be processed and switching the data format.

[0090] In the disclosed embodiment, the product application system connects to the external business system to import business data, that is, to obtain the data to be calculated. The input method includes importing in batches or manually importing from the system page. The data to be calculated includes but is not limited to participants, agreements, amounts, etc.

[0091] Before the accounting data is calculated, it is necessary to pre-process the data. Specifically, the pre-processing includes checking the legality of the accounting data and processing and converting it to adapt to the business logic processing of the product application system.

[0092] The following will further explain the transaction data accounting method disclosed in the present invention in combination with specific business scenarios.

[0093] 1. Business scenarios

[0094] Assume that on T day, the bank signs a loan agreement with a customer, and on T+1 day, the bank issues a loan of 100 million W to the customer (borrower). The loan is jointly funded by ICBC (M), ABC (A), and CCB (B) (i.e., a syndicated loan), and is managed uniformly for customers by M Bank. Each bank bears a share of 50 million W for M Bank, 25 million W for A Bank, and 25 million W for B Bank. M Bank is required to issue separate balance and amount details for each member bank (i.e., M\A\B), and accurately calculate the balance and amount details for the borrower.

[0095] On T+N, in order to reduce risks, Bank M sold 40 million W of its shares through marketing, 20 million W each to China Merchants Bank (C) and Bank of Communications (D). Bank M only held 10 million W for itself. The shares of Bank C and Bank D also required the lead bank (Bank M) to be able to separately calculate the balance and amount details.

[0096] 2. Construct hierarchical data relationship table

[0097] On day T, the bank signs a loan agreement with the customer. The system generates a product sub-agreement and establishes an association between the product sub-agreement and the balance level, as shown in Table 1. The generated balance for the customer is the 0th level (only one balance is set) and the 1st level balance of the syndicate dimension (divided by Bank M, Bank A, and Bank B, with three balances), that is:

[0098] The balance of the customer dimension is the parent node of the balance of the syndicate dimension. The cascade relationship between the balance levels can be determined by "Subordinate Balance Number" and "Existence of Subordinates". Each balance level is linked to one or more sub-balance units, which are sorted and registered by "Level Sequence Number". The sub-balance unit is a basic mapping unit (identified by "Balance Number"), and its business meaning is marked by the "Level Type" dictionary value. Other auxiliary mappings can be set. The arithmetic error caused by the different calculation dimensions of the parent and child is marked by the "Error Level Sequence Number" to indicate which level sequence number of the sub-balance level under the parent balance level will take over the error.

[0099] Table 1

[0100]

[0101] On T+1, the bank issues loans to customers, calculates balances through hierarchical relationships, and establishes an association between balances and accounting accounts, as shown in Table 2. Each balance number can customize the accounting balance type under it. In this example, each balance number has four types, which can also be customized as needed. The bottom-level accounting account number and amount information are registered through "balance number + balance type" identification. If a balance number has a lower level, according to accounting management rules, it does not store the account number, but only the amount.

[0102] Table 2

[0103]

[0104] In addition to the balance change on T+1 day, the amount details also need to be registered, as shown in Table 3. The complete amount information of a specific transaction (account, amount, debit and credit direction, reversal mark, etc.) can be registered by identifying "balance number + balance type + work date + system business number".

[0105] Table 3

[0106]

[0107] When Bank M sells its shares to Bank C and Bank D on T+N, a new second-level balance is added, and the balance of Bank M at the first level is assumed to be attached, and it is updated as the parent node of the second-level sales dimension level, as shown in Table 4. The account balances of the second-level balances are registered, and the splitting rules of the relevant balances are determined by the sub-agreement business rules, as shown in Table 5. The amount of occurrence is increased by registering the amount of each account of the second-level balance, as shown in Table 6.

[0108] Table 4

[0109]

[0110] Table 5

[0111]

[0112] Table 6

[0113]

[0114] Figure 5 A block diagram of a transaction data accounting device according to an embodiment of the present disclosure is schematically shown.

[0115] like Figure 5 As shown, the transaction data accounting device 400 includes:

[0116] The parsing module 410 is used to parse the business logic of the specified product protocol to obtain all protocol objects included in the business logic.

[0117] The determination module 420 is used to determine the hierarchical relationship between the protocol objects and the accounting elements related to each protocol object.

[0118] The acquisition module 430 is used to acquire designated data from the data to be calculated, where the designated data is transaction data corresponding to the calculation element.

[0119] The construction module 440 is used to construct a hierarchical data accounting table based on the transaction data and the hierarchical relationship, and the hierarchical data accounting table counts the transaction data of the protocol objects of at least one level.

[0120] According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging circuits, or can be implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.

[0121] For example, any multiple of the parsing module 410, the determination module 420, the acquisition module 430, and the construction module 440 can be combined in one module / unit / sub-unit for implementation, or any one of the modules / units / sub-units can be split into multiple modules / units / sub-units. Alternatively, at least part of the functions of one or more of these modules / units / sub-units can be combined with at least part of the functions of other modules / units / sub-units and implemented in one module / unit / sub-unit. According to an embodiment of the present disclosure, at least one of the parsing module 410, the determination module 420, the acquisition module 430, and the construction module 440 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware or in a suitable combination of any of them. Alternatively, at least one of the parsing module 410 , the determining module 420 , the acquiring module 430 , and the constructing module 440 may be at least partially implemented as a computer program module, and when the computer program module is executed, a corresponding function may be performed.

[0122] Reference below Figure 6A to Figure 6D , combined with specific embodiments Figure 5 The method shown is further explained.

[0123] Fig. 6AA block diagram of a transaction data accounting device according to another embodiment of the present disclosure is schematically shown.

[0124] like Fig. 6A As shown, the determination module 420 includes a judgment unit 4201, which is used to judge whether the specified product protocol contains historical business logic. A parsing unit 4202, which is used to parse the historical protocol object contained in the historical business logic if the specified product protocol contains historical business logic. A first determination unit 4203, which is used to determine the hierarchical relationship between the historical protocol object and the protocol object.

[0125] Figure 6B A block diagram of a transaction data accounting device according to another embodiment of the present disclosure is schematically shown.

[0126] like Figure 6B As shown, the construction module 440 includes a selection unit 4401, which is used to select multiple target protocol objects, and the multiple target protocol objects have a hierarchical relationship. A second determination unit 4402 is used to respectively determine the transaction data corresponding to the accounting elements related to the multiple target protocol objects. A construction unit 4403 is used to construct a target hierarchical data accounting table based on the hierarchical relationship and transaction data between the multiple target protocols.

[0127] Figure 6C A block diagram of a transaction data accounting device according to another embodiment of the present disclosure is schematically shown.

[0128] like Figure 6C As shown, the determination module 420 also includes an identification unit 4204, which is used to identify the protocol parent object and the protocol child object contained in the protocol object, and the protocol parent object has at least one level of protocol child objects. A third determination unit 4205 is used to determine the accounting elements related to the protocol parent object and the accounting elements related to the protocol child objects at each level.

[0129] Fig.6D A block diagram of a transaction data accounting device according to another embodiment of the present disclosure is schematically shown.

[0130] like Fig.6D As shown, the device 400 further includes a preprocessing module 450 for preprocessing the accounting data, wherein the preprocessing includes performing a legality check and data format switching on the data to be processed.

[0131] It should be noted that the accounting device part of transaction data in the embodiment of the present disclosure corresponds to the accounting method part of transaction data in the embodiment of the present disclosure. The description of the accounting device part of transaction data specifically refers to the accounting method part of transaction data, which will not be repeated here.

[0132] Figure 7A block diagram of an electronic device suitable for implementing the method described above according to an embodiment of the present disclosure is schematically shown. Figure 7 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0133] like Figure 7 As shown, the electronic device 500 according to an embodiment of the present disclosure includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage part 508 to a random access memory (RAM) 503. The processor 501 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 501 may also include an onboard memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0134] In RAM 503, various programs and data required for the operation of electronic device 500 are stored. Processor 501, ROM 502 and RAM 503 are connected to each other via bus 504. Processor 501 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 502 and / or RAM 503. It should be noted that the program can also be stored in one or more memories other than ROM 502 and RAM 503. Processor 501 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0135] According to an embodiment of the present disclosure, the electronic device 500 may further include an input / output (I / O) interface 505, which is also connected to the bus 504. The electronic device 500 may further include one or more of the following components connected to the I / O interface 505: an input portion 506 including a keyboard, a mouse, etc.; an output portion 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 508 including a hard disk, etc.; and a communication portion 509 including a network interface card such as a LAN card, a modem, etc. The communication portion 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed, so that a computer program read therefrom is installed into the storage portion 508 as needed.

[0136] According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the processor 501, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

[0137] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0138] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

[0139] For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 502 and / or the RAM 503 described above and / or one or more memories other than the ROM 502 and the RAM 503 .

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

[0141] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0142] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for calculating transaction data, comprising: Parse the business logic of the specified product protocol to obtain all protocol objects contained in the business logic; Determining the hierarchical relationship between the protocol objects and the accounting elements related to each of the protocol objects; Acquire designated data from the data to be calculated, wherein the designated data is transaction data corresponding to the calculation element; Based on the transaction data and the hierarchical relationship, a hierarchical data accounting table is constructed, wherein the hierarchical data accounting table counts transaction data of the protocol objects of at least one level; Wherein, the determining the hierarchical relationship between the protocol objects and the accounting elements related to each of the protocol objects further includes: Identify a protocol parent object and a protocol child object contained in the protocol object, wherein the protocol parent object has at least one level of protocol child objects; Determine the accounting elements related to the protocol parent object and the accounting elements related to the protocol child objects at each level.

2. The method according to claim 1, wherein: The determining of the hierarchical relationship between the protocol objects and the accounting elements related to each of the protocol objects includes: Determining whether the specified product agreement contains historical business logic; If the designated product protocol includes historical business logic, parsing the historical protocol object included in the historical business logic; Determine the hierarchical relationship between the historical protocol object and the protocol object, and determine the accounting elements related to each historical protocol object and the accounting elements related to the protocol object.

3. The method according to claim 1, wherein: When the hierarchical data accounting table counts transaction data of protocol objects of multiple levels, the hierarchical data accounting table is constructed based on the transaction data and the hierarchical relationship, and the hierarchical data accounting table counts transaction data of protocol objects of at least one level, including: Selecting a plurality of target protocol objects, wherein the plurality of target protocol objects have a hierarchical relationship between them; Respectively determining transaction data corresponding to the accounting elements related to the multiple target agreement objects; Based on the hierarchical relationship between the multiple target protocols and the transaction data, a target hierarchical data accounting table is constructed.

4. The method according to claim 1, wherein: The agreement parent object includes the product agreement number; The next level agreement sub-object of the product agreement number includes a balance number; The next level protocol sub-object of the balance number includes the balance type.

5. The method according to any one of claims 1 to 4, wherein: The accounting elements include at least one of level type, level balance, interest surplus, occurrence amount, occurrence details, debit and credit identification, work date, business number, and detail serial number.

6. The method according to claim 1, wherein: Before acquiring the designated data from the data to be calculated, wherein the designated data is the transaction data corresponding to the calculation element, the method further includes: The data to be calculated is preprocessed, and the preprocessing includes checking the legality of the data to be processed and switching the data format.

7. A transaction data accounting device, comprising: A parsing module, used to parse the business logic of a specified product protocol and obtain all protocol objects contained in the business logic; A determination module, used to determine the hierarchical relationship between the protocol objects and the accounting elements related to each of the protocol objects; An acquisition module, used for acquiring specified data from the data to be calculated, wherein the specified data is transaction data corresponding to the calculation element; A construction module, configured to construct a hierarchical data accounting table based on the transaction data and the hierarchical relationship, wherein the hierarchical data accounting table counts transaction data of at least one hierarchical agreement object; Wherein, the determining the hierarchical relationship between the protocol objects and the accounting elements related to each of the protocol objects further includes: Identify a protocol parent object and a protocol child object contained in the protocol object, wherein the protocol parent object has at least one level of protocol child objects; Determine the accounting elements related to the protocol parent object and the accounting elements related to the protocol child objects at each level.

8. An electronic device comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enables the processor to implement the method according to any one of claims 1 to 6.

Images