Business resource processing method, device, electronic device and storage medium

Abstract

The present application relates to the field of computer technology, and in particular to a business resource processing method, device, electronic device and storage medium for improving the processing efficiency of business resources. The method includes: in response to the accounting query operation for the target business resource, displaying the accounting service page; displaying the dependency graph between the various business nodes of the target business resource and the accounting details information and business node of each business node on the accounting service page, the dependency graph is created based on the node information and dependency information of each business node, each business node is a business processing node corresponding to each business system associated with the target business resource, and the accounting details information is determined based on the current accounting status of each business node for the third-party payment institution bills and bank bills for the target business resource. The present application effectively improves the processing efficiency by building a unified platform composed of multiple business nodes to converge the difference management method of each business resource.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a business resource processing method, device, electronic device, and storage medium. Background Art

[0002] In related technologies, business resource accounting is required to ensure its accuracy and security. Taking provision funds as an example, there are three reconciliation systems in provision fund accounting: internal accounting, external accounting, and internal-external accounting. Internal accounting includes account-to-account and account-to-document accounting, external accounting includes verification accounting, and internal-external accounting includes account-to-actual and verification-to-document accounting.

[0003] However, the three reconciliation systems used in reserve fund accounting are interconnected and interdependent, but none of them can be integrated to detect and locate anomalies. Currently, users must manually locate these anomalies, resulting in slow processing of discrepancies. Consequently, the business resource processing methods used in related technologies are inefficient. Summary of the Invention

[0004] Embodiments of the present application provide a business resource processing method, device, electronic device, and storage medium to improve the efficiency of resource difference processing.

[0005] The first business resource processing method provided in the embodiment of the present application includes:

[0006] In response to an accounting query operation for a target business resource, displaying an accounting service page;

[0007] The accounting service page displays a dependency graph between the various business nodes of the target business resource, as well as accounting details and business nodes of each business node. The dependency graph is created based on the node information of each business node and the dependency information between each business node. Each business node is a business processing node corresponding to each business system associated with the target business resource. The accounting details of each business node are determined based on the current accounting status of each business node for the third-party payment institution bills and bank bills for the target business resource.

[0008] The second service resource processing method provided in the embodiment of the present application includes:

[0009] receiving node identifiers and accounting details reported by each business node, and associating the node identifiers and the accounting details of each business node according to an association operation for associating the accounting details with the node identifiers, wherein each business node is a business processing node corresponding to each business system associated with the target business resource, and the accounting details of each business node is determined based on each business node's current accounting status of third-party payment institution bills and bank bills for the target business resource;

[0010] After receiving a trigger request for displaying an accounting service page triggered by an accounting query operation on the target business resource, the accounting details information of each business node is obtained and fed back to the requester, so that the requester displays a dependency graph between each business node, as well as the accounting details information of each business node and the accounting service page of the business node, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node.

[0011] The first service resource processing device provided in the embodiment of the present application includes:

[0012] A first response unit, configured to display an accounting service page in response to an accounting query operation on a target business resource;

[0013] The accounting service page displays a dependency graph between the various business nodes of the target business resource, as well as accounting details and business nodes of each business node. The dependency graph is created based on the node information of each business node and the dependency information between each business node. Each business node is a business processing node corresponding to each business system associated with the target business resource. The accounting details of each business node are determined based on the current accounting status of each business node for the third-party payment institution bills and bank bills for the target business resource.

[0014] Optionally, the first response unit is specifically configured to:

[0015] In response to a triggering operation of triggering a node control page, displaying the node control page;

[0016] In response to target business resource information, node information of each business node associated with the target business resource, and dependency information between each business node input through the node control page, the dependency graph is displayed on the node control page.

[0017] Optionally, when the accounting details information of the target service node is abnormal, the first responding unit is further configured to:

[0018] Displaying an abnormal status mark for the target business node with abnormal accounting detail information on the accounting service page; and

[0019] In response to a difference query operation on the target business node in the accounting service page, an exception control page including exception status information corresponding to the target business node is displayed, wherein the exception status information is used to indicate an exception generated during the accounting process of the target business node for the third-party payment institution bill and the bank bill.

[0020] Optionally, the device further includes:

[0021] The second response unit is used to respond to the difference confirmation operation for the target business node triggered by the abnormal control page, jump to the business system corresponding to the target business node, and the business system of the target business node performs difference confirmation and reports the difference reason for the target business node to the server, so that the server eliminates the difference status of the target business node and records relevant logs.

[0022] Optionally, the device further includes:

[0023] a third response unit, configured to, in response to a difference confirmation operation for the target service node triggered by the exception control page, obtain an input difference reason for the target service node, report the difference reason to a server, so that the server eliminates the difference status of the target service node and records a related log; and

[0024] Sending a prompt message to a party interested in the difference of the target service node, the prompt message including abnormal status information of the target service node and a reason for the difference.

[0025] The second service resource processing device provided in the embodiment of the present application includes:

[0026] a receiving unit, configured to receive node identifiers and accounting details reported by each business node, and associate the node identifiers and accounting details of each business node according to an association operation for associating the accounting details with the node identifiers, wherein each business node is a business processing node corresponding to each business system associated with a target business resource, and the accounting details of each business node is determined based on the current accounting status of each business node for third-party payment institution bills and bank bills for the target business resource;

[0027] A feedback unit is used to obtain the accounting details information of each business node and feed it back to the requester after receiving a trigger request for displaying the accounting service page triggered by an accounting query operation on the target business resource, so that the requester can display a dependency graph between each business node, as well as the accounting details information of each business node and the accounting service page of the business node, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node.

[0028] Optionally, the receiving unit is further configured to:

[0029] Before receiving the node identification and accounting details information reported by each business node, each business node for accounting for the target business resource is created based on the received target business resource information, the node information of each business node associated with the target business resource, and the dependency information between each business node, and the node information and the dependency information are stored, wherein the target business resource information, the node information and the dependency information are input through the node control page after receiving a trigger request triggered by the node control page and displaying the node control page.

[0030] Optionally, the accounting details information includes execution status information of each business node and accounting difference information obtained by each business node when calculating the third-party payment institution bill and the bank bill; the device further includes:

[0031] an alarm unit, configured to analyze the abnormal state of each service node based on the execution state information and the accounting difference information, combined with the dependency information between the service nodes;

[0032] According to the abnormal status of each business node obtained by analysis, combined with the pre-configured alarm convergence strategy, the target business node with abnormal accounting detail information is notified and alarmed, and the target business node is marked as abnormal.

[0033] Optionally, the device further includes:

[0034] an abnormality analysis unit, configured to analyze the abnormality status information of the target service node based on the execution status information and the accounting difference information reported by the target service node, and associate the abnormality status information of the target service node with a node identifier;

[0035] After receiving a difference query request triggered by the target service node and displaying abnormal status information of the target service node, acquiring abnormal status information corresponding to the target service node according to the node identifier in the difference query request;

[0036] The abnormal status information is returned to the requesting party, so that the requesting party displays an abnormal control page for the target service node according to the abnormal status information.

[0037] Optionally, the device further includes:

[0038] a difference confirmation unit, configured to receive a difference confirmation request for the target service node triggered by the abnormality control page;

[0039] Eliminate the difference state of the target service node according to the difference reason in the difference confirmation request, and record relevant logs.

[0040] Optionally, the device further includes:

[0041] The notification unit is used to determine other service nodes that depend on the service node according to the dependency information between the service nodes when one of the service nodes is re-run, and notify the other service nodes to re-run.

[0042] An electronic device provided in an embodiment of the present application includes a processor and a memory, wherein the memory stores program code, and when the program code is executed by the processor, the processor executes the steps of any one of the above-mentioned business resource processing methods.

[0043] An embodiment of the present application provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps of any of the aforementioned business resource processing methods.

[0044] An embodiment of the present application provides a computer-readable storage medium, which includes program code. When the program product is run on an electronic device, the program code is used to enable the electronic device to execute the steps of any one of the above-mentioned business resource processing methods.

[0045] The beneficial effects of this application are as follows:

[0046] The business resource processing method, device, electronic device and storage medium provided in the embodiments of the present application, since in the embodiments of the present application, users can register the business nodes corresponding to each business system associated with the target business resource, and each business node is used to calculate the third-party payment institution bills and bank bills for the target business resource. By integrating various reconciliation systems, accounting systems and other business systems, the dependency relationship between various business systems is intuitively displayed, and the execution status of the current data time is displayed from a global perspective. There is no need to manually locate differences, which can effectively improve the processing efficiency of business resources, and thus help to ensure the security of business resources.

[0047] Other features and advantages of the present application will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present application. The purposes and other advantages of the present application can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0049] Figure 1A An optional schematic diagram of a business resource processing method in the related art;

[0050] Figure 1B It is a full-process view of business resource accounting in related technologies;

[0051] Figure 2 This is an optional schematic diagram of an application scenario in an embodiment of the present application;

[0052] Figure 3 This is an optional schematic diagram of a business resource processing method in an embodiment of the present application;

[0053] Figure 4 This is an optional schematic diagram of an accounting service page in an embodiment of the present application;

[0054] Figure 5 This is an optional schematic diagram of an abnormality control page in an embodiment of the present application;

[0055] Figure 6 This is an optional schematic diagram of another abnormal control page in an embodiment of the present application;

[0056] Figure 7 This is an overall architecture diagram of a business resource processing system in an embodiment of the present application;

[0057] Figure 8 This is an ER diagram in an embodiment of the present application;

[0058] Figure 9 This is an optional schematic diagram of another business resource processing method in an embodiment of the present application;

[0059] Figure 10 This is a schematic diagram of an optional interaction implementation timing flow in an embodiment of the present application;

[0060] Figure 11 This is a schematic diagram of the composition structure of a first business resource processing device in an embodiment of the present application;

[0061] Figure 12 This is a schematic diagram of the structure of a second service resource processing device in an embodiment of the present application;

[0062] Figure 13 A schematic diagram of the hardware structure of an electronic device to which an embodiment of the present application is applied;

[0063] Figure 14 A schematic diagram of the hardware structure of another electronic device to which an embodiment of the present application is applied. DETAILED DESCRIPTION

[0064] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of the technical solutions of this application, but not all of them. Based on the embodiments described in this application document, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the technical solutions of this application.

[0065] The following is an introduction to some concepts involved in the embodiments of this application.

[0066] A third-party payment institution is an independent institution with sufficient strength and credibility, a payment license, and unified supervision by the central bank. It serves as the "middle platform" for funds between buyers and sellers during transactions. It operates through contracts with major banks and provides an online payment model that interfaces with the bank's payment and settlement systems.

[0067] A payment institution's customer funds account refers to an account opened by a payment institution for a customer in its own business system and used to record customer funds collection and payment settlement information. The third-party payment institution bill in the embodiments of this application mainly refers to the bill of this account.

[0068] Third-party payment service reserve funds: the prepaid monetary funds actually received by the payment institution for handling the payment services entrusted by the customer. The business resources in the embodiment of this application are mainly illustrated by the reserve funds, and other business resources are also applicable and are not specifically limited here.

[0069] Reserve Bank Account: refers to various bank accounts opened by payment institutions at the People's Bank of China or various payment banks in accordance with regulations for storing customer reserve funds. The bank bills in the embodiments of this application mainly refer to the bills of this account.

[0070] Reserve Fund Bank Statement: refers to the record of actual fund occurrence and changes in related balances that can be confirmed by the bank or external funding system. It is usually the balance and its change flow queried in the relevant system, and a transaction list reflecting the changes in the reserve fund account balance of the third-party payment institution.

[0071] The reserve fund supervision platform is a platform used to verify the consistency between payment institutions' customer funds accounts and reserve fund bank accounts and manage reserve funds. Third-party payment institutions monitor the flow of funds for their businesses and, in conjunction with reserve fund bank account statements, verify that the payment institutions' daily customer reserve fund deposit and withdrawal records are consistent with the reserve fund bank's records. This platform identifies any outstanding customer reserve fund items, offsets any outstanding funds, and monitors any outstanding funds.

[0072] Payment Platform Core System: This refers to the core balance accounting system within the payment platform, which records the balances and changes in customer accounts. Hereinafter referred to as the Core System.

[0073] The Payment Platform Order System refers to the payment platform's business system for completing customer transactions. It records customer payment information, including receipts, payments, and refunds. When customers execute quick payments, withdraw funds to bank cards, or refund orders to bank cards, changes are affected in both the reserve fund bank account and the customer's capital account. This system is hereby referred to as the Order System.

[0074] Bank voucher system: This refers to the system used by clearing organizations, banks, or other external funding providers to provide transaction confirmation documents. These documents reflect the final status of a transaction, including bank statements, payment statements, and refund statements. This system is referred to as the voucher system.

[0075] Bank Flow System: This refers to the system used by clearing organizations, banks, or external funding providers to record actual occurrences of reserve funds and changes in related balances. This system is hereafter referred to as the Flow System.

[0076] Netting: refers to the use of legal systems such as offsetting and contract novation to ultimately obtain a net claim or net debt of one party to another party. For example, market traders may have multiple transactions with the same content but opposite directions. When settling or ending the transaction, the claims of all parties can be offset within equal amounts and only the remaining balance can be paid.

[0077] Alarm convergence: This means that sometimes when an alarm is generated, it is often accompanied by other alarms. In this case, an alarm can be generated only for the root cause, and other alarms can be converged into sub-alarms and notifications can be sent together. For example, when a CPU (Central Processing Unit / Processor) load alarm appears on a cloud server, it is often accompanied by availability alarms for all the systems it carries. In the embodiment of the present application, it refers to integrating the three independent alarm systems involved in the three reconciliation systems in the related art into one system to achieve alarm convergence.

[0078] ER diagrams (Entity Relationship Diagrams): These diagrams represent entity types, attributes, and relationships, and are used to describe conceptual models of the real world. They are an effective way to describe conceptual models of real-world relationships. They are a way to represent conceptual relationship models. In the embodiments of this application, ER diagrams are used to represent the connections between various business nodes and the resulting results.

[0079] Offsetting is an accounting concept that means offsetting incorrect accounting entries, eliminating them within the corresponding amounts. Simply put, it involves making a reverse entry based on the original entry, or making an identical entry in red ink, to cancel out the original entry or to clear an existing entry.

[0080] Application operation interface: It is the medium for interaction and information exchange between the application system and the user. It realizes the conversion between the internal form of information and the form acceptable to humans. The purpose is to enable users to operate the application conveniently and efficiently to achieve two-way interaction and complete the work they want to complete with the help of the application. In the embodiment of the present application, the application operation interface includes human-computer interaction and graphical user interface. The specific application operation interface includes accounting service page, node control page, exception control page, etc. Among them, different application operation interfaces are used to display different content to users and realize different information interactions between users and applications.

[0081] Node control page: This is a user-oriented page used to input target business resource information, node information of each business node associated with the target business resource, and dependency information between each business node. It can also be used for adding, deleting, modifying, and adjusting the position of nodes.

[0082] The accounting service page is a user-facing page that displays detailed accounting information for each business node. In this embodiment of the present application, the accounting service page also displays a diagram of each business node and the dependencies between them. Furthermore, target business nodes with abnormal accounting details will be marked as abnormal on the accounting service page.

[0083] The exception control page is a user-facing page that displays detailed information, including exception status information, for the target business node. For example, it displays a general exception view list. In this embodiment of the present application, users can also use the exception control page to export exceptions and confirm daily exception clearance. Daily exception clearance is the difference confirmation process listed in this embodiment of the present application.

[0084] The following is a brief introduction to the design concept of the embodiment of this application:

[0085] The accounting system completes the voucher identification, bookkeeping, accounting, adjustment and offset operations in the accounting work through accounting calculation. Specifically, the reserve fund supervision platform in the relevant technology has three reconciliation systems in the reserve fund accounting, namely internal accounting, external accounting, and internal and external accounting. Among them, internal accounting includes account accounting and account-document accounting, external accounting includes confirmation accounting, and internal and external accounting includes account-actual accounting and certificate-document accounting. The reconciliation data source can be found in detail. Figure 1A As shown, it specifically includes internal accounts (B / C / Bank, enterprise / consumer / bank), internal vouchers (collection and payment return orders), bank balances (reserve fund flow) and bank bills (collection and payment return bills). Among them, application X is a third-party payment institution platform.

[0086] However, while these three reconciliation systems within reserve fund accounting are interconnected and interdependent, none of them can be integrated to detect and locate anomalies. Currently, users must manually locate these anomalies, resulting in slow resolution and increased financial risk.

[0087] See Figure 1B As shown in the figure, it is a full process view of the reserve fund accounting in related technologies. Among them, the X application core accounting balance is the resources recorded in the user's virtual account of the third-party payment institution, and the bank balance on the far right is the resources recorded in the actual account. Ultimately, it is necessary to ensure that the resources recorded in the virtual account and the resources loaded in the actual bank account are consistent. Figure 1B The vouchers shown in the , including receipts, refunds, payment invoices, and refund invoices, are compared with actual transaction records. When reserve funds are aggregated using netting, payment institutions can only aggregate customer accounts and reconcile the aggregate with the reserve bank, resulting in aggregate discrepancies. The causes of these discrepancies are difficult to pinpoint, and manual resolution is risky, posing a significant risk to fund security.

[0088] In view of this, the embodiments of the present application propose a business resource processing method, device, electronic device and storage medium. The embodiments of the present application are based on the accounting reconciliation principle and use a multi-dimensional reconciliation system to calculate the business resource differences between the internal third-party payment institution and the external bank side. In order to better realize the management of resource differences and financial analysis processing, a universal accounting dashboard is built to quickly locate differences. Therefore, the present application proposes a method for consolidating the management of differences in various business resources by building a unified platform, locating resource differences faster and more accurately, and realizing a method for quickly discovering problems and strengthening resource security. Specifically, in the present application, users can register the business nodes corresponding to each business system associated with the target business resource through a web (World Wide Web) page, and calculate the third-party payment institution bills and bank bills for the target business resource based on each business node. By integrating various business systems such as reconciliation systems and accounting systems, each dependency is intuitively displayed, and the execution status of the current data time is displayed from a global perspective. There is no need to manually locate differences, which can effectively improve the processing efficiency of business resources.

[0089] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application can be combined with each other if there is no conflict.

[0090] like Figure 2 , which is a schematic diagram of an application scenario of an embodiment of the present application. The application scenario diagram includes two terminal devices 210 and a server 220. The terminal devices 210 and the server 220 can communicate with each other through a communication network.

[0091] In an optional embodiment, the communication network is a wired network or a wireless network. The terminal device 210 and the server 220 can be directly or indirectly connected via wired or wireless communication, which is not limited in this application.

[0092] In the embodiment of the present application, the terminal device 210 is an electronic device used by the user, which can be a personal computer, mobile phone, tablet computer, notebook, e-book reader, smart home device, etc., which has certain computing capabilities and runs instant messaging software and websites or social software and websites. Figure 2 User A or user B can view the node control page, accounting service page and exception control page listed in the embodiments of the present application through the terminal device 210.

[0093] Among them, each terminal device 210 is connected to the server 220 through a wireless network. The server 220 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0094] For example, after a user logs in to the node control page through terminal device 210 and enters target business resource information, node information of each business node associated with the target business resource, and dependency information between each business node, terminal device 210 may send the target business resource information, node information of each business node associated with the target business resource, and dependency information between each business node to server 220. In addition, after the user triggers an accounting query operation for the target business resource, terminal device 210 may also send a trigger request to display the accounting service page to server 220, and then server 220 obtains accounting details of each business node and feeds it back to terminal device 210, thereby realizing interaction between terminal device 210 and server 220, etc.

[0095] Each terminal device may have an application installed, and the application operation page of the application may be any one or more of the above-mentioned ones. The application involved in the embodiments of the present application may be software, or a client such as a web page or a small program, and the server is an application server corresponding to the software, web page, or small program, without limiting the specific type of the client.

[0096] See Figure 3 , which is a flowchart of an implementation method of a service resource processing method provided in an embodiment of the present application, is applied to a terminal device 210. The specific implementation process of the method is as follows:

[0097] S31: In response to an accounting query operation for a target business resource, displaying an accounting service page;

[0098] S32: Display the dependency graph between each business node of the target business resource on the accounting service page, as well as the accounting details and business nodes of each business node, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node, and each business node is a business processing node corresponding to each business system associated with the target business resource. The accounting details of each business node are determined based on the current accounting status of each business node for the third-party payment institution bills and bank bills for the target business resource.

[0099] In the embodiment of the present application, the target business may be the payment institution reserve fund management business, and correspondingly, the target business resource refers to the third-party payment business reserve fund (referred to as reserve fund). Among them, the corresponding third-party payment institution bill and bank bill refer to internal data and external data respectively. Specifically, the third-party payment institution bill refers to the bill of the customer fund account of the third-party payment institution, and the bank bill refers to the bill of the reserve fund bank account. In the embodiment of the present application, the accounting of the third-party payment institution bill and the bank bill specifically includes the accounting between internal data, the accounting between external data, and the accounting between internal data and external data, for example Figure 1A shown.

[0100] Specifically, when reconciling third-party payment institution bills and bank statements for target business resources, the main internal data reconciliations involved include reconciling internal accounts and internal vouchers; reconciling external data includes reconciling external bank balances and bank statements; and reconciling internal and external data includes reconciling internal accounts and bank balances, and reconciling internal vouchers and bank statements. Specifically, the various business systems associated with the target business resources include: the (third-party) payment platform core system, the payment platform order system, the bank voucher system, and the bank transaction system.

[0101] See Figure 4 As shown, it is a schematic diagram of a calculation service page in an embodiment of the present application. The various business nodes displayed in the calculation service page are Figure 4 The hexagons shown are: core accounting amount, core bank flow, core merchant flow, core user flow, receipt, bank receipt, payment, bank payment, refund, bank refund, core cash withdrawal - payment, bank flow and other business processing nodes. The dependencies between the various business nodes can be Figure 4 This is reflected in the dependency diagram on the accounting service page shown, where interdependent business nodes are connected by lines. The connected business nodes have dependencies, and can be used to reconcile internal and external information flows. The arrows mean mutual comparison. Figure 4The core accounting amount node and the core bank flow node need to be reconciled on a per-account basis; the core bank flow needs to be reconciled with the core merchant flow and the core user flow; the internal reconciliation of collections needs to be performed between the receipt and the core bank flow; the internal reconciliation of payment / refunds needs to be performed between the core bank flow and the core withdrawal order-payment and refund; the collection reconciliation needs to be performed between the receipt and the bank receipt bill, and the payment reconciliation needs to be performed between the payment order and the accounts payable bill; the change payment reconciliation needs to be performed between the core withdrawal order-payment and refund and the bank payment bill; the refund reconciliation needs to be performed between the refund order and the bank refund bill; finally, the bill flow reconciliation also needs to be performed between the bank payment bill, bank receipt bill, bank refund bill and the bank flow, etc.

[0102] Among them, the accounting details information in the embodiment of the present application includes the data time of the most recent verification (such as which stage the verification has reached by hour or minute), the execution time of the verification, the verification status, whether there is an abnormality, the total amount of successful verification, the total amount of abnormal verification, etc. One or more of these accounting details information are real-time information. Figure 4 The accounting service page shown shows the execution time of the current verification, whether there are any data anomalies, etc.

[0103] In an embodiment of the present application, a dependency graph is created based on the node information of each business node and the dependency information between each business node. Users can register or adjust business nodes through the node control page. Specifically, the terminal device displays the node control page in response to the triggering operation of the node control page. After that, the user can enter the target business resource information and node information, the dependency relationship between business nodes, etc. in the node control page. In response to the target business resource information, the node information of each business node associated with the target business resource, and the dependency information between each business node entered through the node control page, a dependency graph is displayed on the node control page. Among them, the target business resource information specifically includes the bills of each third-party payment institution associated with the target business resource, bank bills, etc., such as the receipts, refund bills, core accounting amounts, etc. listed above, and bank bills include core bank flows, bank payment bills, bank refund bills, etc. The business nodes listed above are also created based on each business system.

[0104] In an embodiment of the present application, after the terminal device responds to the target business resource information, the node information of each business node associated with the target business resource, and the dependency information between each business node input through the node control page, it is also necessary to report this information to the server. The server creates each business node for accounting for the target business resource based on the received target business resource information, the node information of each business node associated with the target business resource, and the dependency information between each business node, and stores this node information and dependency information. Specifically, this node information and dependency information can be formatted and stored in a database.

[0105] After creating each business node, each business node can compare the third-party payment institution bills and bank bills for the target business resource based on the input target business resource information. For example, the core accounting amount node and the core bank flow node are mainly used to calculate whether the total amount of the internal account funds is consistent with the total amount summarized in the external accounting account. The payment order node and the bank payment bill node are used to calculate whether the internal payment order is consistent with the payment bill in the external accounting account. Of course, other business nodes are similar, mainly used to calculate whether the internal and external information flows are consistent. The internal information flow mainly refers to the information provided by the third-party payment institution, while the external information flow mainly refers to the information provided by the bank.

[0106] In an embodiment of the present application, during the process of calculating the bills of the third-party payment institution and the bank bills, each business node can report its own execution status information and the accounting difference information obtained by each business node from calculating the bills of the third-party payment institution and the bank bills to the server in real time (no need to report when there is no difference, or report that there is no difference). After the server receives the execution status information and accounting difference information reported by each business node, it stores this information in the database.

[0107] The execution status refers to execution success, execution failure, execution exception, etc. Specifically, accounting difference information is divided into two categories: reconciliation difference and accounting difference. Reconciliation refers to comparing the two data sources that need to be reconciled. There is no calculation logic, for example Figure 4 The shown reconciliation includes receipt reconciliation, payment reconciliation, internal reconciliation of receipts, internal reconciliation of payments / refunds, reconciliation of change payments, and reconciliation of refunds. Calculation includes calculation logic such as addition and subtraction, for example Figure 4 The account-by-account reconciliation, general ledger reconciliation and final bill flow trial balance are shown.

[0108] In addition, the server can also analyze the target business nodes with abnormalities and the abnormal status of each target business node based on the execution status information and accounting difference information reported by each business node, combined with the dependency information between each business node, and specifically divide them into data abnormalities, delay abnormalities, operation abnormalities, etc. Among them, for example, there is a data difference in the reconciliation process, one side has certain data, and the other side does not have the same data. The delay abnormality means that each reconciliation has an expected running time, such as 17:00 to calculate the bill for 15:00, but the accounting has not started at 17:00, etc. There are many cases of operation abnormalities, such as network disconnection, database connection disconnection, etc.

[0109] In addition, for target business nodes with abnormal accounting details, the abnormal status information of the target business node is analyzed based on the execution status information and accounting difference information reported by the target business node, and the abnormal status information of the target business node is associated with the node identifier and stored in the database. The abnormal status information specifically includes the reason for the abnormality of the target business node, the inspection time, the account date of the accounting, the task type, etc. The task type refers to any of the above-mentioned account reconciliation, general ledger reconciliation, internal reconciliation of collections, collection reconciliation, payment reconciliation, change payment reconciliation, refund reconciliation, bill flow reconciliation, etc.

[0110] In other words, the business resource processing method in the embodiment of the present application can provide users with a comprehensive view, clarifying node process anomalies, so that from the inside out, if any key node has an anomaly, it can be intuitively traced back to the source and the reason for the source error. It can also clearly understand which resources have been checked and whether there are any differences in these check results; it can intuitively see the current check status of key nodes, including the data time of the most recent check completion, the execution time of the check, the check status, whether there are any anomalies, the total amount of successful checks, and the total amount of abnormal checks; it intuitively shows the responsibilities of each block, provides simple help instructions, and how to handle different types of anomalies.

[0111] Optionally, when the accounting details information of the target business node is abnormal, an abnormal status mark for the target business node with abnormal accounting details information may be displayed on the accounting service page, for example, marked with a special color, marked with a special symbol, etc.

[0112] See Figure 4 As shown in the figure, the gray hexagons are target business nodes with abnormal accounting details. Figure 4There are data anomalies in the core bank flow node, specifically 107 data anomalies. In addition to the core bank flow node, there are also abnormal accounting details information in the payment order node and the bank flow node. Among them, there is 1 data anomaly in the payment order node and 3 data anomalies in the bank flow node.

[0113] In addition, during the reconciliation of change payment, there was a delay exception, but the execution status of the bank payment bill node and the core withdrawal order-payment and refund node used for change payment reconciliation did not show any abnormality, and the data contained in the calculated payment bill, core withdrawal order, etc. did not show any abnormality. Figure 4 In the manner shown, a gray number button 2 is marked on the line between the two nodes as an abnormal state mark of the delay abnormality type.

[0114] In the embodiments listed above, the target business nodes include three nodes: core bank flow, payment slip and bank flow. In the embodiment of the present application, the user can directly click on the target business node in the accounting service page to trigger a difference query operation for the target business node. At this time, the terminal device responds to the difference query operation for the target business node in the accounting service page and displays an abnormality control page including abnormal status information corresponding to the target business node, wherein the abnormal status information is mainly used to indicate the abnormality generated by the target business node in the process of accounting for the third-party payment institution bills and bank bills, specifically including the reason for the abnormality of the target business node, the inspection time, the account date of the accounting, the task type, etc.

[0115] like Figure 5 As shown, it is a schematic diagram of an abnormal control page listed in the embodiment of this application. For example, if a user clicks Figure 4 After the core bank flow node in the gray part shown, you can jump to Figure 5 The exception control page shown shows the exception status information corresponding to the core bank flow node, for example Figure 5 The abnormal status list is shown. This list displays the date of the account being reconciled, the task type, the consistency check result, the check time, and the reason for the exception. For the sub-account reconciliation task for March 13, 2020, an exception occurred in the consistency check between the total amount of the external accounting ledger and the total amount of the internal fund ledger. The exception is listed in the Consistency Check Result column of the table... The cause of the exception is a database switch failure. T0 refers to settlement to the merchant on the payment business day. If the payment is made on a non-business day, the merchant must wait until the next business day for settlement. T1 refers to the payment to the receiving bank, and settlement to the merchant is made the next business day.

[0116] In addition, the task flow details associated with the household verification task are also displayed below the abnormal status list, such as Figure 5 As shown, first you need to check the accounts, then the general ledger, general ledger details, balance entry, cumulative amount, and operating general ledger. The specific details that can be queried include historical records, node details, operation records (in Figure 5 in the abbreviation operation) and help improve (in Figure 5 For example, when the user clicks on the corresponding historical record of the household, Figure 5 As shown, there are two historical records. The first record is from 2020-03-13 01:00:00, and the verification result is successful. The second record is from 2020-03-13 02:00:00, and the verification result is failed. In addition, the node details section specifically displays the verification time, status, etc.

[0117] In addition, when displaying the queryable detailed information listed above, the abnormal parts can be marked with special colors, special fonts, etc., such as Figure 5 What is shown is that the abnormal content in the history record part is marked in gray, which can directly highlight the abnormal data in the accounting process to the user.

[0118] See Figure 6 As shown, it is a schematic diagram of another abnormal control page in the embodiment of the present application. For example, if the user clicks Figure 4 After the payment order node shown, you can jump to Figure 6 The exception control page shown is for the payment order node. The task type displayed on this page is "Income Reconciliation" and a list of exception statuses is also displayed. For the receipt reconciliation task for March 13, 2020, an exception occurred in the comparison between the internal payment order and the external bank payment invoice. This indicates a core failure and displays the exception results. The cause of the exception is a snapshot pull error.

[0119] In addition, the task flow details related to the collection reconciliation are further displayed below the abnormal status list. Among them, after pulling the flow, snapshot and bill, the bill data (flow data) related to the collection reconciliation is obtained, and further based on Figure 4 The listed collection order nodes and bank collection bill nodes are used to reconcile the collection data. In addition, the collection reconciliation task is also related to the internal reconciliation, that is, Figure 4 The internal reconciliation of receipts shown in requires reconciliation of external core bank statements with internal receipts, etc.

[0120] in, Figure 6The exception control page shown shows that there are exceptions in the snapshot pulling process. Specifically, according to the historical records, snapshot pulling failed at 2020-03-13 01:00:00 and snapshot pulling failed at 2020-03-13 02:00:00.

[0121] Alternatively, users can click Figure 4 Click the number buttons marked on the lines between the nodes shown to view detailed information about delay anomalies, etc. Of course, you can also directly click on the relevant business node to view the anomaly details and export the anomaly details.

[0122] In addition, the exception can be further closed. In the embodiment of the present application, the user can also confirm the difference through the exception control page. Figure 5 or Figure 6 A difference confirmation control has been added to the exception control page. This difference confirmation control can be displayed in a pop-up window, floating overlay, or directly on the exception control page. There are two specific ways to confirm differences: subsystem difference confirmation and manual difference confirmation.

[0123] The following is a detailed introduction to the processing of the above two methods:

[0124] Method 1: The terminal device responds to the difference confirmation operation for the target business node triggered by the exception control page, jumps to the business system (also called subsystem) corresponding to the target business node, and the business system of the target business node confirms the difference and reports the difference reason for the target business node to the server, so that the server eliminates the difference status of the target business node and records relevant logs.

[0125] Specifically, when a user triggers a discrepancy confirmation operation for a target business node through the exception control page, the terminal device responds by redirecting to the corresponding subsystem for processing. After the subsystem completes the processing, it packages the discrepancy reason and logs and submits them to the server. The server stores this data in a database and resolves the discrepancy. This discrepancy method generally involves high financial risk.

[0126] Method 2: The terminal device responds to the difference confirmation operation for the target business node triggered by the abnormal control page, obtains the input of the difference reason for the target business node, reports the difference reason to the server, so that the server eliminates the difference status of the target business node and records relevant logs; and sends a prompt message to the difference-concerned party for the target business node, the prompt message including the abnormal status information of the target business node and the difference reason.

[0127] This method is relatively simple. If a discrepancy can be confirmed using common logic, it can be confirmed directly on this page. Specifically, the user directly enters the reason for the discrepancy, and the terminal device then packages the exception details and the reason for the discrepancy and sends a prompt message to the relevant parties concerned about the discrepancy. The prompt message can be in the form of an email or text message.

[0128] It should be noted that, in the above embodiment, by clicking on the abnormal node in the page view, you can jump to the abnormal location list, such as Figure 5 or Figure 6 As shown, it provides upstream and downstream anomaly location queries for each node in the overall view, and each query content provides: historical records, node details, operation records and help improvements, etc. Users can display the content by clicking, which can simply and efficiently locate difference anomalies.

[0129] See Figure 7 As shown, it is an overall architecture diagram of a business resource processing system for implementing the above-mentioned business resource processing method in an embodiment of the present application. Specifically, the business resource processing system in the embodiment of the present application is specifically divided into three types of modules: web page module, Fable service module and batch run module.

[0130] in, Figure 7 The web system shown is the web page module, used to enable user interaction with the human-computer interface; the result reporting service, exception management service, and node management service all belong to the Fable service module, while various batch operations, health analysis, and alarm, reporting, and notification functions belong to the batch operation module. Table 1 details the modules included in the business resource processing system in this embodiment of the application, along with a description of each module's functionality.

[0131] Table 1 System module division

[0132]

[0133] There are three web page modules: node control page, exception control page, and accounting manager home page (i.e., the accounting service page listed in this article). The functions of these three web page modules are described below:

[0134] Among them, the node control page is used for adding, deleting, modifying and checking nodes, and adjusting their positions; the exception control page is used for viewing the general exception list, exporting exceptions and confirming exceptions daily, see Figure 5 、 Figure 6 As shown; the main page of the accounting manager is used to display the operating status of each node and the dependency diagram, etc., see Figure 4 shown.

[0135] The following is a brief introduction to the Fable service type modules. As shown in the table above, there are three Fable service type modules, namely: result reporting service, exception management service and node management service. The functions of these three Fable service modules are: result reporting service, which is used for each batch reporting interface service and has 1 interface; exception management service, which is used to connect to each system exception query and exception handling, and has 2 interfaces, exception query interface and exception handling interface; node management service, which includes resource node management, task node management, etc., dependency relationships, node mapping, error codes, etc. Among them, resource nodes and task nodes are all business nodes listed in the embodiments of this application.

[0136] In the embodiment of the present application, the business nodes include resource nodes corresponding to each business system and task nodes associated with the processing logic of each resource node; that is, the business nodes in the embodiment of the present application are divided into two categories, resource nodes and task nodes, such as Figure 4 The hexagons shown are all resource nodes, and the task nodes refer to which tasks are there, which are not shown in the figure. For example, the two resource nodes, payment slip and bank payment bill, are used to implement the task of payment reconciliation, and the task of payment reconciliation is composed of many small tasks (subtasks), such as pulling data sources, first-level reconciliation, second-level write-offs, etc. Among them, the dependency information between business nodes includes the dependency information between each resource node, and the dependency information between each task node associated with the relevant resource node. It should be noted that the dependency information in the embodiment of the present application specifically refers to the relationship between nodes, the node association relationship, etc.

[0137] Finally, let's introduce the batch run modules. As shown in the table above, there are three batch run modules: Batch Run Framework Upgrade, Health Analysis, and Alert & Report & Notification. The functions of these three batch run modules are:

[0138] Batch framework upgrades are used to connect to accounting manager reporting (internal packaging). Health analysis analyzes each node and the overall status based on the reported content and the overall task chain. Alarm, Report, and Notification processes are used to issue notifications based on the analyzed status and alarm convergence strategies. For example, this system analyzes the accounting process and results to identify business nodes with issues. If any, an alarm is generated. If no issues are identified, the correctness of the reconciliation results defined by the business definition is determined. If no issues are identified, financial statements are generated and reported.

[0139] See Figure 8 As shown, it is an ER diagram listed in the embodiment of the present application, which is used to reflect the relationship between each business node and the final result. The ER diagram can be used as the result finally displayed to the user by the business resource processing system listed in the embodiment of the present application.

[0140] exist Figure 8 There are several tables displayed in it, namely: task node registration table, resource registration table, business reporting result table, abnormal event table, abnormal level table and result confirmation log table.

[0141] The Task Node Registration Table and Resource Registration Table are primarily generated based on information entered by users when registering a business node, including target business resource information, node information for each business node, and inter-node dependency information. Specifically, the Task Node Registration Table includes a primary key: the task node ID (identifier); foreign keys (also known as reference keys): node name, accounting process ID, maximum reporting delay, state, and affected states. The Resource Registration Table includes a primary key: element ID; and foreign keys: type (resource relationship), view location, difference state, and exception state.

[0142] Among them, the business reporting result table is mainly generated based on the results reported by each business node, specifically including the primary key: reporting result ID; foreign keys: data start time, data end time, execution start time, execution end time, business ID, execution status (error code), error message, corresponding element node ID, task ID, total ratio, total amount, total difference ratio, total difference amount, etc.

[0143] The exception event table is based on the analysis of the results reported by each business node and contains the abnormal situations. Specifically, it includes the primary key: event ID; foreign keys: data start time, data end time, execution start time, execution end time, business identifier, exception error code, exception error message, total difference ratio, total difference amount, exception handling results, etc.

[0144] The exception registration table is generated based on the analyzed exception event table and resource registration table. It specifically includes the primary key: exception error code ID; foreign keys: reporting element ID, exception description, exception level, exception attention person, convergence strategy, alarm channel, difference query configuration, difference confirmation method (jump / general), etc.

[0145] The result confirmation log table is generated based on the difference confirmation listed above, and is related to the abnormal event table. Specifically, it includes the primary key: ID; foreign keys: reported result ID, operator, operation reason, operation time, etc.

[0146] In the embodiments of this application, based on the T0 fund accounting system, the efficiency of the payment platform's reserve fund accounting is increased to T0. At the same time, reconciliation performance and capacity are improved, making the accounting system more stable and streamlined. After the system is launched, fund discrepancies are identified faster, more accurately, and more clearly, and account aging is calculated more accurately. Automatic system write-offs are implemented, reducing manual workload and mitigated write-off risks. Ultimately, fund discrepancies can be quickly located, ensuring platform fund security.

[0147] See Figure 9 FIG. 2 is a flowchart of another method for processing business resources according to an embodiment of the present application, which is applied to the server 220. The specific implementation process of the method is as follows:

[0148] S91: Receive node identifiers and accounting details reported by each business node, and associate the node identifiers and accounting details of each business node according to an association operation for associating the accounting details with the node identifiers. Each business node is a business processing node corresponding to each business system associated with a target business resource, and the accounting details of each business node are determined based on the current accounting status of each business node for third-party payment institution bills and bank bills for the target business resource.

[0149] S92: After receiving a trigger request for displaying an accounting service page triggered by an accounting query operation on a target business resource, the accounting details information of each business node is obtained and fed back to the requester, so that the requester displays a dependency graph including the dependency relationships between each business node, as well as the accounting details information of each business node and the accounting service page of the business node, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node.

[0150] It should be noted that the specific implementation methods can be found in the above embodiments, and the repeated parts will not be repeated here. Since the embodiments of this application integrate various reconciliation and accounting systems, intuitively display various dependencies, and display the execution status of the current data time from a global perspective, it effectively improves the efficiency of anomaly location, ensures the timeliness of anomaly location, and thus helps to ensure the security of business resources.

[0151] Optionally, before receiving the node identification and accounting details reported by each business node, the following is further included:

[0152] Based on the received target business resource information, the node information of each business node associated with the target business resource, and the dependency information between each business node, each business node for accounting for the target business resource is created, and the node information and dependency information are stored, wherein the target business resource information, node information and dependency information are input through the node control page after receiving a trigger request triggered by the node control page and displaying the node control page.

[0153] Optionally, the accounting details information includes execution status information of each business node and accounting difference information obtained by each business node from calculating the third-party payment institution bill and the bank bill; the method further includes:

[0154] Based on the execution status information and accounting difference information, combined with the dependency information between each business node, the abnormal status of each business node is analyzed; based on the abnormal status of each business node obtained from the analysis, combined with the pre-configured alarm convergence strategy, the target business node with abnormal accounting detail information is notified and alarmed, and the target business node is marked as abnormal.

[0155] For example, when there is an abnormality in the accounting details information of the target business node, an alarm is generated and other related business nodes with dependencies are notified.

[0156] It should be noted that the embodiment of the present application integrates three independent alarm systems involved in the three reconciliation systems in the related art into one system, thereby achieving alarm convergence.

[0157] Optionally, the method further includes:

[0158] Based on the execution status information and accounting difference information reported by the target business node, the abnormal status information of the target business node is analyzed and associated with the node identifier; after receiving a difference query request triggered by the target business node to display the abnormal status information of the target business node, the abnormal status information corresponding to the target business node is obtained according to the node identifier in the difference query request; the abnormal status information is returned to the requester so that the requester displays the abnormal control page for the target business node according to the abnormal status information.

[0159] It should be noted that the specific implementation methods can be referred to the above embodiments, and the repeated parts will not be repeated. Among them, the abnormal status information includes the reason why the target business node has an abnormality, the inspection time, the account date of the accounting, the task type, etc.

[0160] Optionally, the method further includes:

[0161] Receive a difference confirmation request for the target business node triggered by the exception control page; eliminate the difference status of the target business node based on the difference reason in the difference confirmation request, and record relevant logs.

[0162] In this embodiment of the application, the server can perform exception management and analysis based on the results reported by each business node. This includes detailed analysis of the exception and the impact of the exception. Exception management specifically includes alarm timeliness, notification recipients, alarm convergence, and automatic resolution of the exception. In this embodiment of the application, by linking task operations on the data management platform, cross-system recovery can be achieved through the task relationships displayed on the page when an exception occurs.

[0163] Optionally, the method further includes:

[0164] When a rerun occurs on one of the service nodes, other service nodes that depend on the service node are determined based on the dependency information between the service nodes, and the other service nodes are notified to rerun.

[0165] Specifically, the reconciliation in the embodiment of the present application depends on internal data and external data. For example, the bank has previously provided a bill (the first data source). At this time, the relevant business nodes have begun to calculate according to the bill, and the program has been running. However, after the bank side discovered that part of the data in the bill was missing, it provided a complete bill again (the second data source). In this case, it is necessary to restart the business node to achieve a rerun. In addition, other dependent business nodes are notified to rerun. And in the embodiment of the present application, when a business node reruns, the nodes that depend on the node can be marked with color to indicate that they need to rerun or take the initiative to notify.

[0166] In addition, it should be noted that after obtaining the data of the second bank statement, the status bit can be further indicated by color, and the cause of the abnormality can be marked.

[0167] In summary, this application introduces a method for unified management of fund anomalies in the reserve fund management of payment institutions. Based on the accounting reconciliation principle, a multi-dimensional reconciliation system is used to calculate the fund differences between internal payment institutions and external banks. In order to better realize the management of fund differences and financial analysis and processing, a universal accounting dashboard is built to quickly locate differences. This application proposes a method to consolidate the management of fund differences of various businesses by building a unified platform, locate fund differences faster and more accurately, and realize the method of quickly discovering problems and strengthening fund security.

[0168] See Figure 10 FIG. 1 is a schematic diagram of an optional interactive implementation sequence flow of the business resource processing method in an embodiment of the present application. The specific implementation process of the method is as follows:

[0169] Step S1001: The web terminal receives information such as resource nodes, task nodes, and dependencies between nodes entered by the user in various systems during the registration phase;

[0170] Step S1002: The web terminal reports the information of the registered nodes and node dependencies to the backend service module;

[0171] Step S1003: The backend service module submits this information (registered node information and node dependency information) to the database for storage;

[0172] Step S1004: the database returns the stored result to the backend service module;

[0173] Step S1005: The backend service module notifies the web end of the storage result;

[0174] Step S1006: The business batch running module reports the execution status, reconciliation differences, and accounting differences of each business node to the backend service module;

[0175] Step S1007: The backend service module submits this information (execution status, reconciliation differences, and accounting differences reported by the business batch running module) to the database for storage;

[0176] Step S1008: The database returns the stored result to the backend service module;

[0177] Step S1009: The backend service module returns the stored results to the business batch running module;

[0178] Step S1010: The health analysis module sends a query request to the database for all records reported in the period, including all node information and resource information;

[0179] Step S1011: The database returns the corresponding data found to the health analysis module;

[0180] Step S1012: The health analysis module classifies abnormalities according to the reported records and nodes, specifically into: data abnormalities, delay abnormalities and operation abnormalities;

[0181] Step S1013: The health analysis module globally analyzes the impact of a certain business node, including abnormal impact, restart and recovery impact, etc.

[0182] The impact of restart recovery means that, for example, if business node A needs to do something that depends on business node B, then if business node A redoes the work, business node B also has to do it again.

[0183] Step S1014: The health analysis module marks the resource, task, and accounting process status;

[0184] Step S1015: The health analysis module submits the three types of resource status, namely resource, task, and accounting process status, to the database;

[0185] Step S1016: The database returns the stored results to the health analysis module;

[0186] Step S1017: The web terminal detects a status monitoring request triggered by the user;

[0187] Step S1018: The web terminal sends a main view & task view status query request to the backend service module;

[0188] Step S1019: The backend service module queries the database status;

[0189] Step S1020: the database returns the query result;

[0190] Step S1021: The backend service module returns the query results to the web terminal for display;

[0191] Among them, steps S1017 to S1021 specifically refer to that after the user triggers the accounting query operation for the target business resource, the web end can detect the status monitoring request triggered by the user, and then send the main view & task view status query request to the background service module. The background service module queries the corresponding data from the database and returns it to the web end for display through the background service module;

[0192] Step S1022: The web terminal detects a difference query request triggered by the user;

[0193] Step S1023: The web terminal sends a main view & task view status query request to the backend service module;

[0194] Step S1024: The backend service module queries the database for difference query rules and database tables of the business configuration;

[0195] The difference query rules of the business configuration refer to which differences are to be displayed. Data is queried from the database through configuration and then displayed to the user in the form of a page table.

[0196] Step S1025: The database returns the rules and database information to the backend service module;

[0197] Step S1026: the backend service module queries the corresponding differences;

[0198] Step S1027: the database returns the abnormal impression;

[0199] Step S1028: The backend service module returns the difference information to the web terminal so that the web terminal can display it to the user;

[0200] Step S1029: The web terminal detects a request to view differences triggered by the user;

[0201] Step S1030: The web terminal jumps to the subsystem for processing. After the subsystem completes the processing, the difference reasons and logs are packaged and submitted to the backend service module;

[0202] Step S1031: The backend service module sends a log record & difference status elimination request to the database;

[0203] Step S1032: The database returns the processing result to the backend service module;

[0204] Among them, steps S1022 to S1028 specifically refer to the process of confirming subsystem differences;

[0205] Step S1033: The web terminal receives the difference reason submitted by the user;

[0206] Step S1034: The web terminal packages the exception details and the reason for the discrepancy and sends an email to the concerned party (i.e., the discrepancy concerned party, including level 1 and level 2);

[0207] Step S1035: The web terminal submits the reason for the difference to the backend service module;

[0208] Step S1036: The backend service module sends a log record & difference status elimination request to the database;

[0209] Step S1037: The database returns the processing result to the backend service module;

[0210] Step S1038: The backend service module returns a message to the web end indicating that the difference has been successfully confirmed.

[0211] Among them, steps S1029 to S1032 specifically refer to the process of manual difference confirmation.

[0212] Based on the same inventive concept, the embodiment of the present application provides a schematic diagram of a transfer control device for a resource object. Figure 11 As shown, it is a schematic diagram of the structure of the service resource processing device 1100, which may include:

[0213] The first response unit 1101 is configured to display a calculation service page in response to a calculation query operation for a target business resource;

[0214] The accounting service page displays a dependency graph between the various business nodes of the target business resource, as well as accounting details and business nodes for each business node. The dependency graph is created based on the node information of each business node and the dependency information between each business node. Each business node is a business processing node corresponding to each business system associated with the target business resource. The accounting details of each business node are determined based on the current accounting status of each business node for third-party payment institution bills and bank bills for the target business resource.

[0215] Optionally, the first responding unit 1101 is specifically configured to:

[0216] In response to a triggering operation of triggering the node control page, displaying the node control page;

[0217] In response to target business resource information, node information of each business node associated with the target business resource, and dependency information between each business node input through the node control page, a dependency graph is displayed on the node control page.

[0218] Optionally, when the accounting details information of the target service node is abnormal, the first responding unit 1101 is further configured to:

[0219] Displaying abnormal status marks for target business nodes with abnormal accounting details on the accounting service page; and

[0220] In response to a difference query operation on the target business node in the accounting service page, an exception control page including exception status information corresponding to the target business node is displayed, wherein the exception status information is used to indicate the exceptions generated during the accounting process of the target business node for the third-party payment institution bills and bank bills.

[0221] Optionally, the device further comprises:

[0222] The second response unit 1102 is used to respond to the difference confirmation operation for the target business node triggered by the abnormal control page, jump to the business system corresponding to the target business node, and the business system of the target business node performs difference confirmation and reports the difference reason for the target business node to the server, so that the server eliminates the difference status of the target business node and records relevant logs.

[0223] Optionally, the device further comprises:

[0224] A third response unit 1103 is configured to, in response to a difference confirmation operation for a target service node triggered by the exception control page, obtain an input difference reason for the target service node, report the difference reason to the server, so that the server eliminates the difference status of the target service node and records relevant logs; and

[0225] A prompt message is sent to the party concerned about the difference of the target service node, and the prompt message includes abnormal status information of the target service node and the reason for the difference.

[0226] Based on the same inventive concept, the embodiment of the present application provides a schematic diagram of a transfer control device for a resource object. Figure 12 As shown, it is a schematic diagram of the structure of the service resource processing device 1200, which may include:

[0227] Receiving unit 1201 is configured to receive node identifiers and accounting details reported by each business node, and associate the node identifiers and accounting details of each business node according to an association operation for associating the accounting details with the node identifiers. Each business node is a business processing node corresponding to each business system associated with a target business resource, and the accounting details of each business node is determined based on the current accounting status of each business node for third-party payment institution bills and bank bills for the target business resource.

[0228] Feedback unit 1202 is used to obtain the accounting details information of each business node and feed it back to the requester after receiving a trigger request for displaying the accounting service page triggered by an accounting query operation on the target business resource, so that the requester can display the dependency graph between each business node, as well as the accounting details information of each business node and the accounting service page of the business node, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node.

[0229] Optionally, the receiving unit 1201 is further configured to:

[0230] Before receiving the node identification and accounting details information reported by each business node, create each business node for accounting for the target business resource based on the received target business resource information, the node information of each business node associated with the target business resource, and the dependency information between each business node, and store the node information and dependency information, wherein the target business resource information, node information and dependency information are input through the node control page after receiving a trigger request triggered by the node control page and displaying the node control page.

[0231] Optionally, the accounting details information includes execution status information of each business node and accounting difference information obtained by each business node when calculating the third-party payment institution bill and the bank bill; the device further includes:

[0232] Alarm unit 1203, used to analyze the abnormal status of each service node based on the execution status information and accounting difference information, combined with the dependency information between each service node;

[0233] Based on the abnormal status of each business node obtained through analysis and combined with the pre-configured alarm convergence strategy, the target business node with abnormal accounting details information is notified and alarmed, and the target business node is marked as abnormal.

[0234] Optionally, the device further comprises:

[0235] The abnormality analysis unit 1204 is configured to analyze the execution status information and accounting difference information reported by the target service node to obtain abnormal status information of the target service node, and associate the abnormal status information of the target service node with the node identifier;

[0236] After receiving a difference query request triggered by a target service node and displaying abnormal status information of the target service node, obtaining abnormal status information corresponding to the target service node according to the node identifier in the difference query request;

[0237] The abnormal status information is returned to the requester, so that the requester displays an abnormal control page for the target service node according to the abnormal status information.

[0238] Optionally, the device further comprises:

[0239] The difference confirmation unit 1205 is configured to receive a difference confirmation request for a target service node triggered by the abnormality control page;

[0240] According to the difference reason in the difference confirmation request, the difference status of the target business node is eliminated and relevant logs are recorded.

[0241] Optionally, the device further comprises:

[0242] The notification unit 1206 is configured to determine other service nodes that depend on the service node according to dependency information between the service nodes when a re-run occurs on one of the service nodes, and notify the other service nodes to re-run.

[0243] For the convenience of description, the above parts are divided into modules (or units) according to their functions and described separately. Of course, when implementing this application, the functions of each module (or unit) can be implemented in the same or multiple software or hardware.

[0244] After introducing the service resource processing method and apparatus according to an exemplary embodiment of the present application, an electronic device according to another exemplary embodiment of the present application is introduced next.

[0245] Those skilled in the art will appreciate that various aspects of the present application can be implemented as systems, methods, or program products. Therefore, various aspects of the present application can be specifically implemented in the following forms: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation that combines hardware and software aspects, which may be collectively referred to herein as a "circuit," "module," or "system."

[0246] Based on the same inventive concept as the above method embodiment, an electronic device is also provided in the embodiment of the present application. The electronic device can be used for transfer control of resource objects. In one embodiment, the electronic device can be a server, such as Figure 2 In this embodiment, the structure of the electronic device can be as follows: Figure 13 As shown, it includes a memory 1301 , a communication module 1303 and one or more processors 1302 .

[0247] Memory 1301 is used to store computer programs executed by processor 1302. Memory 1301 may primarily include a program storage area and a data storage area. The program storage area may store an operating system and programs required for running instant messaging functions, while the data storage area may store various instant messaging messages and operating instruction sets.

[0248] Memory 1301 may be a volatile memory, such as random-access memory (RAM); a non-volatile memory, such as read-only memory, flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 1301 may be a combination of the aforementioned memories.

[0249] The processor 1302 may include one or more central processing units (CPUs) or digital processing units, etc. The processor 1302 is configured to implement the above-mentioned service resource processing method when calling the computer program stored in the memory 1301 .

[0250] The communication module 1303 is used to communicate with terminal devices and other servers.

[0251] The specific connection medium between the memory 1301, the communication module 1303 and the processor 1302 is not limited in the embodiment of the present application. Figure 13 In the embodiment, the memory 1301 and the processor 1302 are connected via a bus 1304. The bus 1304 is connected to the processor 1302 via a bus 1304. Figure 13 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus 1304 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 13 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0252] The memory 1301 stores a computer storage medium, which stores computer executable instructions. The computer executable instructions are used to implement the business resource processing method of the embodiment of the present application. The processor 1302 is used to execute the above-mentioned business resource processing method, such as Figure 9 shown.

[0253] In another embodiment, the electronic device may also be other electronic devices, such as Figure 2 The terminal device 210 shown in FIG. In this embodiment, the structure of the electronic device can be as follows: Figure 14 As shown, it includes: a communication component 1410, a memory 1420, a display unit 1430, a camera 1440, a sensor 1450, an audio circuit 1460, a Bluetooth module 1470, a processor 1480 and other components.

[0254] The communication component 1410 is used to communicate with the server. In some embodiments, it can include a WiFi (Wireless Fidelity) module. The WiFi module is a short-range wireless transmission technology. Electronic devices can help users send and receive information through the WiFi module.

[0255] The memory 1420 can be used to store software programs and data. The processor 1480 executes various functions and data processing of the terminal device 210 by running the software programs or data stored in the memory 1420. The memory 1420 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. The memory 1420 stores an operating system that enables the terminal device 210 to run. In the present application, the memory 1420 can store the operating system and various application programs, and may also store code for executing the service resource processing method of the embodiment of the present application.

[0256] The display unit 1430 can also be used to display information input by the user or provided to the user, as well as a graphical user interface (GUI) for various menus of the terminal device 210. Specifically, the display unit 1430 may include a display screen 1432 disposed on the front of the terminal device 210. The display screen 1432 may be configured in the form of a liquid crystal display, a light-emitting diode, etc. The display unit 1430 can be used to display the game screen of the online game in the embodiments of the present application.

[0257] The display unit 1430 can also be used to receive input digital or character information and generate signal input related to user settings and function control of the terminal device 210. Specifically, the display unit 1430 may include a touch screen 1431 set on the front of the terminal device 210, which can collect user touch operations on or near it, such as clicking a button, dragging a scroll box, etc.

[0258] The touch screen 1431 can be covered on the display screen 1432, or the touch screen 1431 and the display screen 1432 can be integrated to realize the input and output functions of the terminal device 210. The integrated touch screen can be simply called a touch display screen. In this application, the display unit 1430 can display applications and corresponding operation steps.

[0259] The camera 1440 can be used to capture still images, and the user can send the image captured by the camera 1440 to the other user in the chat through the online game client. The camera 1440 can be one or more. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the processor 1480 to convert it into a digital image signal.

[0260] The terminal device may further include at least one sensor 1450, such as an acceleration sensor 1451, a distance sensor 1452, a fingerprint sensor 1453, and a temperature sensor 1454. The terminal device may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, a light sensor, and a motion sensor.

[0261] The audio circuit 1460, speaker 1461, and microphone 1462 can provide an audio interface between the user and the terminal device 210. The audio circuit 1460 can convert the received audio data into an electrical signal and transmit it to the speaker 1461, which converts it into a sound signal for output. The terminal device 210 can also be equipped with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 1462 converts the collected sound signal into an electrical signal, which is received by the audio circuit 1460 and converted into audio data. The audio data is then output to the communication component 1410 for transmission to, for example, another terminal device 210, or the audio data is output to the memory 1420 for further processing.

[0262] The Bluetooth module 1470 is used to exchange information with other Bluetooth devices having a Bluetooth module through the Bluetooth protocol. For example, the terminal device can establish a Bluetooth connection with a wearable electronic device (such as a smart watch) that also has a Bluetooth module through the Bluetooth module 1470 to exchange data.

[0263] The processor 1480 is the control center of the terminal device. It uses various interfaces and lines to connect various parts of the entire terminal. By running or executing software programs stored in the memory 1420 and calling data stored in the memory 1420, it performs various functions of the terminal device and processes data. In some embodiments, the processor 1480 may include one or more processing units; the processor 1480 may also integrate an application processor and a baseband processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the baseband processor mainly processes wireless communications. It is understandable that the above-mentioned baseband processor may not be integrated into the processor 1480. In the present application, the processor 1480 can run the operating system, application programs, user interface display and touch response, as well as the business resource processing method of the embodiment of the present application. In addition, the processor 1480 is coupled to the display unit 1430.

[0264] In some possible implementations, various aspects of the business resource processing method provided in the present application may also be implemented in the form of a program product, which includes program code. When the program product is run on a computer device, the program code is used to enable the computer device to execute the steps of the business resource processing method according to various exemplary embodiments of the present application described above in this specification. For example, the computer device may execute the following steps: Figure 3 Follow the steps shown in .

[0265] The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0266] The program product of the embodiment of the present application may be a portable compact disc read-only memory (CD-ROM) and include program code, and can be run on a computing device. However, the program product of the present application is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with a command execution system, device, or device.

[0267] A readable signal medium may include a data signal transmitted in baseband or as part of a carrier wave, which carries readable program code. Such a transmitted data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with a command execution system, apparatus, or device.

[0268] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0269] Those skilled in the art will appreciate that all or part of the steps of the above-mentioned method embodiments may be implemented by hardware associated with program instructions, and the aforementioned program may be stored in a computer-readable storage medium. When the program is executed, the program executes the steps of the above-mentioned method embodiments. The aforementioned storage medium includes various media that can store program codes, such as mobile storage devices, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical disks.

[0270] Alternatively, if the above-mentioned integrated unit of the embodiment of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

[0271] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application.

[0272] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if such changes and modifications fall within the scope of the claims of this application and their equivalents, this application is intended to include such changes and modifications.

Claims

1. A business resource processing method, characterized in that: The method includes: In response to an accounting query operation for a target business resource, displaying an accounting service page; A dependency graph between the various business nodes of the target business resource and accounting details of each business node are displayed on the accounting service page, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node, and each business node includes: the resource node corresponding to each business system associated with the target business resource, and the task nodes associated with the processing logic of each resource node; the dependency information between the various business nodes includes: the dependency information between the various resource nodes, and the dependency information between the various task nodes associated with the relevant resource nodes; the various business nodes are registered or adjusted through the node control page; the accounting details information of each business node is determined based on the current accounting status of each business node for the third-party payment institution bills and bank bills for the target business resource.

2. The method according to claim 1, wherein The dependency graph is created based on the node information of each service node and the dependency information between each service node, specifically including: In response to a triggering operation of triggering a node control page, displaying the node control page; In response to target business resource information, node information of each business node associated with the target business resource, and dependency information between each business node input through the node control page, the dependency graph is displayed on the node control page.

3. The method according to claim 1, wherein When the accounting details information of the target service node is abnormal, the method further includes: Displaying an abnormal status mark for the target business node with abnormal accounting detail information on the accounting service page; and In response to a difference query operation on the target business node in the accounting service page, an exception control page including exception status information corresponding to the target business node is displayed, wherein the exception status information is used to indicate an exception generated during the accounting process of the target business node for the third-party payment institution bill and the bank bill.

4. The method according to claim 3, wherein The method further comprises: In response to the difference confirmation operation for the target business node triggered by the exception control page, jump to the business system corresponding to the target business node, and the business system of the target business node confirms the difference and reports the difference reason for the target business node to the server, so that the server eliminates the difference status of the target business node and records relevant logs.

5. The method according to claim 3, wherein The method further comprises: In response to a difference confirmation operation for the target service node triggered by the exception control page, obtaining an input difference reason for the target service node, reporting the difference reason to a server, so that the server eliminates the difference status of the target service node and records relevant logs; and Sending a prompt message to a party interested in the difference of the target service node, the prompt message including abnormal status information of the target service node and a reason for the difference.

6. A business resource processing method, characterized in that: The method includes: receiving node identifiers and accounting details reported by each business node, and associating the node identifiers and accounting details of each business node according to an association operation for associating the accounting details with the node identifiers, wherein each business node includes: resource nodes corresponding to each business system associated with the target business resource, and each task node associated with the processing logic of each resource node; the accounting details of each business node is determined based on the current accounting status of each business node for third-party payment institution bills and bank bills for the target business resource; After receiving a trigger request for displaying an accounting service page triggered by an accounting query operation on the target business resource, the accounting details information of each business node is obtained and fed back to the requester, so that the requester displays a dependency graph including the dependency relationships between the business nodes, as well as the accounting details information of each business node and the accounting service page of the business node, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node, and the dependency information between each business node includes: dependency information between each resource node, and dependency information between each task node associated with the relevant resource node; each business node is registered or adjusted through the node control page.

7. The method according to claim 6, wherein Before receiving the node identification and accounting details information reported by each service node, the method further includes: Based on the received target business resource information, the node information of each business node associated with the target business resource, and the dependency information between each business node, each business node for accounting for the target business resource is created, and the node information and the dependency information are stored, wherein the target business resource information, the node information and the dependency information are input through the node control page after receiving a trigger request triggered by the node control page and displaying the node control page.

8. The method according to claim 6, wherein The accounting details information includes execution status information of each business node and accounting difference information obtained by each business node from calculating the third-party payment institution bill and the bank bill; the method further includes: Analyze the abnormal state of each business node based on the execution status information and the accounting difference information and the dependency information between the business nodes; According to the abnormal status of each business node obtained by analysis, combined with the pre-configured alarm convergence strategy, the target business node with abnormal accounting detail information is notified and alarmed, and the target business node is marked as abnormal.

9. The method according to claim 8, wherein The method further comprises: Analyze and obtain abnormal status information of the target service node based on the execution status information and accounting difference information reported by the target service node, and associate the abnormal status information of the target service node with a node identifier; After receiving a difference query request triggered by the target service node and displaying abnormal status information of the target service node, acquiring abnormal status information corresponding to the target service node according to the node identifier in the difference query request; The abnormal status information is returned to the requesting party, so that the requesting party displays an abnormal control page for the target service node according to the abnormal status information.

10. The method according to claim 9, wherein The method further comprises: receiving a difference confirmation request for the target service node triggered by the exception control page; Eliminate the difference state of the target service node according to the difference reason in the difference confirmation request, and record relevant logs.

11. The method according to any one of claims 6 to 10, wherein: The method further comprises: When a rerun occurs on one of the service nodes, other service nodes that depend on the service node are determined based on the dependency information between the service nodes, and the other service nodes are notified to rerun.

12. A business resource processing device, characterized in that: include: A first response unit, configured to display an accounting service page in response to an accounting query operation on a target business resource; A dependency graph between the various business nodes of the target business resource and accounting details of each business node are displayed on the accounting service page, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node, and each business node includes: the resource node corresponding to each business system associated with the target business resource, and the task nodes associated with the processing logic of each resource node; the dependency information between the various business nodes includes: the dependency information between the various resource nodes, and the dependency information between the various task nodes associated with the relevant resource nodes; the various business nodes are registered or adjusted through the node control page; the accounting details information of each business node is determined based on the current accounting status of each business node for the third-party payment institution bills and bank bills for the target business resource.

13. A business resource processing device, characterized in that: include: a receiving unit configured to receive node identifiers and accounting details reported by each business node, and associate the node identifiers and accounting details of each business node according to an association operation for associating the accounting details with the node identifiers, wherein each business node includes: resource nodes corresponding to each business system associated with a target business resource, and each task node associated with the processing logic of each resource node; the accounting details of each business node is determined based on the current accounting status of each business node for third-party payment institution bills and bank bills for the target business resource; A feedback unit is used to obtain the accounting details information of each business node and feed it back to the requester after receiving a trigger request for displaying the accounting service page triggered by an accounting query operation on the target business resource, so that the requester displays a dependency graph including the dependency relationships between the business nodes, the accounting details information of each business node and the accounting service page of the business node, wherein the dependency graph is created based on the node information of each business node and the dependency information between each business node, and the dependency information between each business node includes: the dependency information between each resource node, and the dependency information between each task node associated with the relevant resource node; each business node is registered or adjusted through the node control page.

14. An electronic device, characterized in that: It includes a processor and a memory, wherein the memory stores program code, and when the program code is executed by the processor, the processor executes the steps of any one of the methods described in claims 1 to 5 or the steps of any one of the methods described in claims 6 to 11.

15. A computer-readable storage medium, characterized in that The method comprises a program code, and when the program code is run on an electronic device, the program code is used to enable the electronic device to execute the steps of any one of the methods of claims 1 to 5 or the steps of any one of the methods of claims 6 to 11.

Images