Reciprocating money data management method and system, computer equipment and storage medium

Abstract

The invention discloses a transaction data management method and system, computer equipment and a storage medium, and the method can obtain newly added fund data when a client triggers a new added income fund, and sets associated data based on the newly added fund data. And creating a service node according to the service data in the associated data, and generating service approval information according to the service node. And performing service approval through the second client, and verifying the transaction information according to the fed-back first approval result data, thereby storing the newly added fund data. According to the method, a plurality of clients can execute operation on the same platform through a unified standardized component, and when the clients trigger new income adding funds, multi-dimensional standardized associated data is automatically matched according to the new income adding funds, so that the consistency and real-time updating of related information of exchange funds are ensured. Moreover, the business process is automatically executed according to the business data in the associated data, so that the management efficiency of the transaction data is improved.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and in particular to a method, system, computer equipment and storage medium for managing accounts receivable and payable data. Background Art

[0002] Receivables data is a type of data generated in the field of financial technology such as leasing business. Receivables data management includes business items such as payment management, payment and collection process management, and audit and archiving. These business items will be scattered to different business lines and directions according to specific business locations, which will result in additional development work required every time a new collection item is added.

[0003] Since development work requires a certain development cycle, the management response speed and flexibility of accounts receivable data are limited. It may not be possible to respond quickly when faced with new business needs. Especially when it comes to offline collection and reconciliation, since the newly added collection items cannot be synchronized to the relevant business departments in time, the efficiency of accounts receivable management will be reduced, which in turn affects the operational efficiency of the entire financial system and the accuracy of financial management. Summary of the invention

[0004] In view of this, the embodiments of the present application provide a method, system, computer device and storage medium for managing accounts receivable data to quickly synchronize the management status of accounts receivable data and improve the management efficiency of accounts receivable data.

[0005] According to one aspect of the present application, a method for managing receivables and payables data is provided, the method comprising:

[0006] Acquiring newly added payment data, the newly added payment data including data specified by the first client and / or data generated by the first client when executing a transaction; the first client establishing a communication connection with the server through a unified standardized interface;

[0007] Setting associated data based on the newly added payment data, wherein the associated data includes business data and verification data, and the verification data is key information extracted from the newly added payment data;

[0008] Creating a business node according to the business data in the associated data, and generating business approval information according to the business node;

[0009] Sending the business approval information to a second client, and receiving first approval result data fed back by the second client for the business approval information, wherein the second client is a client associated with the business node; the second client establishes a communication connection with the server through a unified standardized interface;

[0010] If the first approval result data includes a first conclusion identifier, acquiring transaction information of the transaction business, performing verification on the transaction information based on the verification data, and storing the newly added amount data as current amount data according to the verification result;

[0011] If the first approval result data includes a second conclusion identifier, resubmission information is sent to the first client.

[0012] According to another aspect of the present application, a current account data management system is provided, comprising: a server and at least one first client and at least one second client that establish communication connection with the server through a unified standardized interface; the server comprises:

[0013] An acquisition module, used to acquire newly added payment data, wherein the newly added payment data includes data specified by the first client and / or data generated by the first client when executing a transaction business;

[0014] An association setting module, used to set association data based on the newly added payment data, wherein the association data includes business data and verification data, and the verification data is key information extracted from the newly added payment data;

[0015] A node creation module, used to create a business node according to the business data in the associated data, and generate business approval information according to the business node;

[0016] An approval request module, used to send the business approval information to a second client, and receive first approval result data fed back by the second client for the business approval information, wherein the second client is a client associated with the business node; the second client establishes a communication connection with the server through a unified standardized interface;

[0017] A verification module, configured to obtain a transaction amount of the transaction business when the first approval result data includes a first conclusion identifier, verify the transaction amount based on the running amount, and store the newly added amount data according to the verification result;

[0018] A feedback module is used to send resubmission information to the first client when the first approval result data includes a second conclusion identifier.

[0019] According to another aspect of the present application, a computer device is provided, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the above-mentioned method for managing accounts receivable data when executing the computer program.

[0020] According to another aspect of the present application, a storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned account data management method is implemented.

[0021] By means of the above technical scheme, the embodiment of the present application provides a method, system, computer device and storage medium for managing accounts receivable data. The method can obtain the newly added payment data when the client triggers the newly added payment, and set the associated data based on the newly added payment data. Among them, the associated data includes business data and verification data. Then create a business node according to the business data in the associated data, and generate business approval information according to the business node. Automatically send the business approval information to the second client, and receive the first approval result data fed back by the second client for the business approval information. If the first approval result data includes a first conclusion identifier, the transaction information of the transaction business is obtained, and the transaction information is verified based on the verification data, and the newly added payment data is stored as accounts receivable data according to the verification result; if the first approval result data includes a second conclusion identifier, a resubmission information is sent to the first client. The method can enable multiple clients to perform operations on the same platform through unified and standardized components, and when the client triggers the newly added payment, the multi-dimensional standardized associated data is automatically matched according to the newly added payment data to ensure the consistency and real-time update of the information related to the accounts receivable. In addition, the business process is automatically executed according to the business data in the associated data to complete the creation, search, collection, transaction verification, storage and other operations of accounts receivable items, thereby improving the management efficiency of accounts receivable data.

[0022] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] 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:

[0024] Figure 1 An application scenario diagram of a method for managing receivables and payables data provided by an embodiment of the present application is shown;

[0025] Figure 2 A schematic diagram of a flow chart of a method for managing receivables and payables data provided in an embodiment of the present application is shown;

[0026] Figure 3 A schematic diagram of the flow relationship of current account data provided by an embodiment of the present application is shown;

[0027] Figure 4 A schematic diagram of a flow chart for verifying the amount of a transaction provided in an embodiment of the present application is shown;

[0028] Figure 5 A schematic diagram of a refund application data management process provided in an embodiment of the present application is shown;

[0029] Figure 6 A schematic diagram of the refund approval process provided in an embodiment of the present application is shown;

[0030] Figure 7 A schematic diagram of a process for updating a status tag provided in an embodiment of the present application is shown;

[0031] Figure 8 A structural diagram of a current account data management system provided by an embodiment of the present application is shown;

[0032] Fig. 9 A schematic diagram of the structure of a computer device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0033] The present application will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other without conflict.

[0034] Before describing the specific implementation methods of the present application, some concepts involved in the specific implementation methods are first described.

[0035] The accounts receivable data described in the embodiments of the present application generally refers to various payment records stored in the financial management system, including but not limited to: accounts receivable, accounts payable, advances received, prepaid accounts, special payments and receipts, bills, contracts, agreements, etc.

[0036] The newly added payment data described in the embodiments of the present application refers to payment data triggered by the client and used to be stored in the data management system for unified management. The newly added payment data can be created and input through the creation function interface of the current payment data management system, and after being set and processed by the current payment data management system, it is stored in the current payment data management system. In some embodiments, the newly added payment data, after being stored, can also be referred to as current payment data.

[0037] The current account data management system described in the embodiment of the present application refers to a combination of hardware devices and software applications used to provide an operating environment for the current account data management method. Figure 1 In the context of financial technology applications shown in the figure. Figure 1The application scenario shown in the figure, combined with the current account data management method, can form a current account data management system. According to specific business needs, the current account data management system can be given different system names, including but not limited to financial system, transaction system, leasing system, accounting system, audit system, etc.

[0038] The current account data management system may include a server and multiple clients. The server may be deployed in the cloud to receive, send, manage, and maintain the current account data. Multiple clients may establish a communication connection with the server to receive and send the current account data, and to generate and display a specific user interface based on the current account data so that users can perform interactive actions.

[0039] In order to meet the business needs of the current account data management system, the server and the client should have data communication capabilities and certain data processing capabilities. Therefore, the server and the client are respectively configured with functional components for realizing communication and data processing capabilities. For example, the server may include a processor and a communication module. Among them, the processor can perform management and maintenance on the current account data by running an application program related to the current account data management method. The communication module is configured to connect to the client and is used to establish a communication connection channel with multiple clients to receive and send current account data.

[0040] Similarly, the client may also include a controller and a communicator. The controller processes the receivables data by running an application program related to the receivables data management method, thereby presenting the receivables data according to the processing result. The communicator is configured to connect to the server and establish a communication connection channel with the server to receive and send the receivables data.

[0041] Multiple clients that establish communication connections with the server can be divided into different types according to specific business needs. Taking the leasing business as an example, the leasing business includes operations, products, business, assets, marketing, finance and other business departments involved in the current account data. These business departments can participate in different stages of current account data management according to their different functions. For example, when the product department executes a product transaction, it will generate transaction data of the type of goods payment. These transaction data will be uploaded to the current account data management system and are called new payment data. The finance department needs to approve the new payment data.

[0042] Since different business departments participate in different business stages in the process of current account data management, different business departments need different types of clients to perform data management work in the corresponding business stages. In some embodiments, multiple clients can be divided into a first client and a second client. Among them, the first client is used to trigger current account management business, such as adding new collections, initiating refund applications, etc. The second client is used to perform approval business, such as approving new collections and refund applications. For example, operations, products, business, assets, marketing and other departments initiate new collections through the first client, and finance and other departments approve the new collections through the second client.

[0043] It should be noted that the first client and the second client are only used to distinguish the roles of the client in the process of managing the current account data, and do not limit the client itself and the specific functions that the client can perform. Under the premise of meeting the hardware requirements, some clients can be used as both the first client and the second client. When performing current account data management, the client can perform the functions of the first client or the second client by running different types of current account data management applications or by logging in to user information with different permissions.

[0044] In order to improve the consistency and synchronization of payment data, the first client and the second client can establish a communication connection with the server through a unified standardized interface. Among them, the unified standardized interface is a communication interface developed based on network connection requirements and specific communication transmission protocols. For example, the unified standardized interface can be a combination of one or more interfaces such as RESTful API, OpenAPISpecification, GraphQL, gRPC, WebSocket, Server-Sent Events (SSE), JMS API, etc. In some embodiments, a specific unified standardized interface can also be customized based on the security and communication method of the specific business scenario to achieve a communication connection between the server and the client.

[0045] The unified standardized interface can make the communication between the client and the server more efficient, secure and maintainable in a standardized way. In addition, the unified standardized interface can also enable clients of multiple business departments scattered in different regions to perform business operations on the management platform provided by the same server, improving the consistency of business information and real-time update performance.

[0046] In some embodiments, the client may further include an output component for presenting the receivables data, including but not limited to a display, a speaker, a buzzer, a vibration motor, an indicator light, etc. The client may display a user interface for managing the receivables data through the output component. The user interface may be presented through a dedicated financial management application or through a specific web page.

[0047] For example, when the user interface is presented through a dedicated financial management application, the client may also include a memory for storing application files of the financial management application. When executing a transaction or financial management process, the user may control the controller of the client to run the financial management application through an application startup instruction. After the financial management application is running, the communicator may be called to establish a communication connection with the server, and receive or send receivables data according to the operation needs.

[0048] For another example, when the user interface is presented through a web page, the user can control the client to run a browser application, and enter the address of the current account management web page in the browser application to control the client to access the web page of the current account management platform. In the process of accessing the web page, the server will send web page content data and current account data to the client according to the web page content. After receiving the web page content data and current account data, the client can render the web page through the browser application to present the user interface related to the current account data management.

[0049] It should be noted that the display method of the above-mentioned user interface related to the management of accounts receivable data is only an example and does not limit the specific presentation method. In actual applications, both the client and the server can receive, send and process accounts receivable data through dedicated applications, network applications, applets, multi-application collaboration, etc. according to specific hardware conditions and user needs.

[0050] Based on this, the client in the embodiments of the present application can be one or more combinations of personal computers, mobile terminals, smart home devices, smart wearable devices, vehicle information systems, workstations, industrial control terminals, virtual reality devices, augmented reality devices and other devices.

[0051] The method for managing receivables data provided in the embodiment of the present application can be applied to a server, that is, after a communication connection is established between a client and a server, the server can build a receivables data management platform by running the receivables data management method. The client can access the receivables data management platform by running a management application or accessing a specific network address to participate in the receivables data management business.

[0052] Based on the server described in the above embodiment, a method for managing receivables data is provided in this embodiment, such as Figure 2 As shown, the method includes:

[0053] S101. Obtain new payment data.

[0054] The newly added payment data may be data specified by the first client. That is, in some embodiments, after users in the operations, products, business, assets, marketing and other departments run the current payment data management application through a terminal device such as a personal computer, they can log in to the user information of the corresponding department's authority through the management application, so that the terminal device has the business function of the first client. After running the application and logging in the user information, the first client can present a user interface for current payment data management.

[0055] The user interface may include multiple business-related function options, such as the name, type, approval authority, number, etc. of the newly added collection. The user may add a new collection by specifying the specific value of the corresponding function option in the user interface and clicking Submit or other confirmation function controls. As the newly added collection is input, the first client may generate the newly added payment data according to the specific value specified by the user. After the newly added payment data is generated, the first client may send the newly added payment data to the server through a data transmission channel with the server, so that the server may obtain the newly added payment data.

[0056] In other embodiments, the newly added payment data may also be data generated by the first client when executing a transaction business. The newly added payment data may also be automatically generated based on the user's transaction behavior by reading the data generated during the transaction process. For example, when the first client displays the QR code for receiving payment, the current payment data management application may monitor the scanned state corresponding to the QR code. When the QR code is detected to be scanned, the payment user information of the currently logged-in user and the payment user information of the user who scanned the QR code may be obtained respectively, and the name, type, approval authority and other information may be matched in combination with the business department, function, management authority and other information to which the payment user information belongs. And through automatic numbering, the corresponding business number of the payment business is assigned to generate the newly added payment data. Similarly, after generating the newly added payment data, the first client may send the newly added payment data to the server through the data transmission channel with the server, so that the server can obtain the newly added payment data.

[0057] When the newly added payment data is data generated by the first client when executing a transaction business, the first client can read transaction business related files when executing the transaction business, and extract multi-dimensional information of the newly added payment data from the related files based on data screening and processing functions.

[0058] That is, in a feasible implementation, the first client can obtain the transaction business file in response to the initiation instruction of the transaction business. And extract the original text information from the transaction business file. Then, based on the text information preprocessing algorithm, preprocess the original text information. Among them, the preprocessing can convert the natural language text into structured text, including text cleaning, tokenization, stop words removal, stemming, lemmatization, part-of-speech tagging, named entity recognition (NamedEntity Recognition, NER), removal or replacement of sensitive words, text normalization, synonym replacement, text deduplication, text encoding, serialization processing, etc. After obtaining the structured text through preprocessing, the first client can perform semantic analysis through the pre-trained semantic processing model. The semantic processing model is a model used to understand and generate natural language text in natural language processing (NLP). The semantic processing model can output corresponding classification labels based on the input structured text information. Each classification label can correspond to a dimension information of a newly added payment data. By setting different classification labels, multiple dimensions information of the newly added payment data can be automatically identified, and the newly added payment data with multiple dimensions information can be obtained.

[0059] In a feasible implementation, the newly added payment data can also be generated by the server according to the transaction business of the first client, that is, the first client can send information or files related to the transaction business to the server. The server then extracts the original text information from the transaction business file. Based on the text information preprocessing algorithm, the original text information is preprocessed, and based on the semantic processing model, the classification labels corresponding to the multiple dimensional information of the newly added payment data are output, and the multiple dimensional information of the newly added payment data is automatically identified to obtain the newly added payment data with multiple dimensional information.

[0060] It should be noted that the specific content included in the newly added payment data can be actively input by the user, that is, the newly added payment data includes the data specified by the first client. The newly added payment data can also be automatically generated after identifying and analyzing the business data related to the transaction behavior, that is, the newly added payment data includes the data generated by the first client when executing the transaction business. The newly added payment data can also be partially actively input by the user and partially automatically generated by identifying and analyzing the business data, that is, the newly added payment data includes the data specified by the first client and the data generated by the first client when executing the transaction business.

[0061] S102: Setting associated data based on the newly added payment data.

[0062] like Figure 3 As shown, after obtaining the newly added payment data, the server can match and associate the business process based on the newly added payment data, that is, obtain the associated data associated with the newly added payment data by data matching. Among them, the associated data includes business data. Business data refers to the data that has an associated relationship with the specific transaction business corresponding to the newly added payment data. The business data can be used to determine the specific business process subsequently triggered by the newly added payment. For example, business data may include whether approval is required, the approval authority required, the specific approval node, whether verification is required, the specific verification content, etc.

[0063] After obtaining the newly added payment data, the server can match the business data based on the multi-dimensional information in the newly added payment data based on the business process trigger rules pre-set by the current payment data management platform. Among them, the pre-set business process trigger rules are used to set matching strategies for different dimensional information respectively, and the matching strategies can be set based on comprehensive settings such as information type and information value.

[0064] For example, the newly added payment data obtained by the server may include "payment type: service fee, payment amount: 2000, department information: business department". In the process of business data matching, the service fee business process can be matched based on the service fee according to the pre-set business process trigger rules; the low amount range can be matched based on the payment amount 2000, and then the approval process for the low amount is determined: general approval, and approval authority: ordinary clerk approval; then the information synchronization node in the business process is matched based on the business department, so as to obtain business data, which includes business process: service fee, approval process: general approval, approval authority: ordinary clerk, information synchronization node: business department and other contents.

[0065] The associated data may also include verification data, which is key information extracted from the newly added payment data. In some embodiments, the verification data may include transaction data, which is a type of data automatically generated based on the newly added payment data and used to perform verification on the transaction amount later. Therefore, the transaction amount of the transaction data is equal to the amount of the newly added payment data. For example, when the newly added payment data obtained includes the content "service fee, 2000", the server may automatically set an associated transaction amount of 2000 for subsequent verification of the transaction amount.

[0066] In order to set the associated data, the server can perform data matching through the multi-dimensional information in the newly added payment data. During the matching process, each dimensional information can preset a project label so that the server can perform data matching based on the project label. When the newly added payment data is input through the option control in the user interface provided by the current account data management system, a standardized project label can be directly specified. However, since most of the business data is natural language text content, the newly added payment data generated by the business data cannot directly obtain the project label converted from the table, which may affect the accuracy of the matching results. Therefore, in order to set the associated data based on the newly added payment data, the server can extract the first project label and the second project label from the newly added payment data. Among them, the first project label is the project label specified by the first client. The second label is the project label corresponding to the business data, and the business data is the data generated when the first client performs a transaction business.

[0067] After extracting the first project tag and the second project tag, the server may perform standardization on the second project tag to generate a third project tag. The third project tag is a project tag in a preset project tag library that is synonymous with the second project tag. A project tag library may be pre-set in the server, and the project tag library may store standardized project tags and the association relationship between standardized project tags and non-standardized project tags. After obtaining the second project tag, the server may perform matching in the project tag library based on the second project tag. When the match hits any standardized project tag, a project tag synonymous with the second project tag, i.e., the third project tag, may be obtained.

[0068] Then match the associated data according to the first project tag and the third project tag. For example, the server reads the contract text during the transaction and reads the content "prepaid AA project payment", which is used to represent the payment type keyword, that is, the second project tag. However, since "prepaid AA project payment" is not a standardized project tag, it is necessary to match the synonymous standardized project tag in the preset project tag library based on the second project tag, that is, to obtain the third project tag "prepayment". Then, set the associated data based on the third project tag "prepayment", thereby reducing the impact of the randomness of the natural language text on the associated data setting process and improving the accuracy of the associated data setting process.

[0069] In order to make the collection process of each payment traceable, in a feasible implementation, the server can also obtain the identification information of the newly added payment data. The identification information includes at least one of the business serial number, the user ID, and the identification number of the first client. A traceability identifier is generated based on the identification information, the first project tag, and the third project tag, and then the traceability identifier is added to the newly added payment data to make the newly added payment data traceable.

[0070] The traceability identifier can be in the form of one or more combinations of characters, numbers, and barcodes, and is used to mark each payment data. The server can set a unique index for each payment data by setting the traceability identifier. In the subsequent management of the current payment data, the specific payment can be located by the traceability identifier or some characters in the traceability identifier, thereby performing data management related to the payment data.

[0071] S103: Create a business node according to the business data in the associated data, and generate business approval information according to the business node.

[0072] After setting the associated data, the server can automatically generate the appropriate business process based on the business data in the associated data, and create business nodes based on the business process. Among them, the business node refers to the personnel, department or client that directly participates in a specific business in the business process. In the server, the business node can be represented by the personnel ID, department ID or client ID. For example, according to the business data with the content of "Business process: service fee, approval process: general approval, approval authority: general clerk, information synchronization node: business department", it can be determined that the business nodes are: business personnel is YW0010, approval personnel is SP PT0001, and information synchronization personnel are YW0001~YW0010.

[0073] After creating a business node, the server can generate business-related information according to the business node, wherein the business-related information is used to present a business-related user interface in the client corresponding to the business node, so that the corresponding client can perform corresponding business process operations. Since business personnel and information synchronization personnel do not participate in specific business approvals, in some embodiments, the server can also generate business approval information only for business nodes determined to participate in approval, that is, generate business approval information for approval personnel, approval departments, and approval clients. Based on this, the information generated related to approval is called business approval information, and the business approval information can be used to present an approval-related user interface on the second client.

[0074] S104: Send the business approval information to the second client, and receive first approval result data fed back by the second client in response to the business approval information.

[0075] After determining the service node, the server may obtain the second client identification information corresponding to the service node based on the determined service node, and after generating the service approval information, send the service approval information to the second client corresponding to the service node based on the second client identification information.

[0076] After receiving the business approval information, the second client can generate an approval-related user interface based on the business approval information. Exemplarily, the approval-related user interface can include key information related to the newly added payment data, such as payment type, payment amount, department, etc. In order to perform the approval work, the approval-related user interface can also include approval function controls, such as approval controls and rejection controls. Through interactive operations on the second client, the second client can feedback the approval result data for the business approval information to the server.

[0077] Among them, for business processes at different stages, the second client can feedback different types of approval result data to the server. For the convenience of description, in the embodiment of the present application, the approval result data fed back at the stage of adding new funds is referred to as the first approval result data, and the approval result data fed back at the stage of refunds and other current funds is referred to as the second approval result data.

[0078] Depending on the different operations performed on the user interface during the approval process, the approval result data may include different conclusion identifiers, namely, a first conclusion identifier and a second conclusion identifier, wherein the first conclusion identifier is used to indicate that the approval is passed, and the second conclusion identifier is used to indicate that the approval is not passed. For example, after the approver clicks the approval control on the approval interface provided by the second client, the second client can be controlled to feedback the approval result data containing the first conclusion identifier to the server. Similarly, after the approver clicks the rejection control on the approval interface provided by the second client, the second client can be controlled to feedback the approval result data containing the second conclusion identifier to the server.

[0079] The first conclusion identifier and the second conclusion identifier can be represented by a character string of a specific numerical value, such as the approval result data fed back by the second client to the server includes the "Approval result" field. By setting the specific value of this field, the approval result is indicated. The first conclusion identifier can be set to 01, and when "Approval result=01", it means that the approval is passed. Similarly, the second conclusion identifier can be set to 00, and when "Approval result=00", it means that the approval is not passed.

[0080] It should be noted that when approving different businesses, the approval results may not be limited to approval and rejection, but may also include results such as suggested modifications, approval after reexamination after modification, and approval with modifications. For this reason, the approval result data fed back by the second client to the server may also include other types of conclusion identifiers. For example, the third conclusion identifier indicating suggested modifications, the fourth conclusion identifier indicating approval after reexamination after modification, the fifth conclusion identifier indicating approval with modifications, etc. Similarly, the third conclusion identifier, the fourth conclusion identifier, and the fifth conclusion identifier may also be represented by specific numerical values, which are not listed here one by one.

[0081] S105: If the first approval result data includes a first conclusion identifier, obtain transaction information of the transaction business, perform verification on the transaction information based on the verification data, and store the newly added amount data as current amount data according to the verification result.

[0082] After obtaining the first approval result data fed back by the second client, the server can read the first approval result data to determine the approval result of the second client for the current business. If the first conclusion identifier is read in the first approval result data, that is, when the approval is passed, the server can obtain the transaction amount of the transaction business and perform verification on the transaction information according to the verification data set in the associated data.

[0083] During the verification process, the server can compare the verification data and transaction information. When the verification data and transaction information meet the preset relationship, a verification result of passing the verification is generated; when the verification data and transaction information do not meet the preset relationship, a verification result of failing the verification is generated. The preset relationship can be a comparison of numerical values, a comparison of information consistency, etc. For example, when obtaining new payment data, the payment type read from the new payment data is "service fee", and when executing a transaction business, it is also necessary to read the payment type from the transaction information generated by the transaction business. If the payment type read is also "service fee", a verification result of passing the verification can be generated.

[0084] In a feasible implementation, the transaction information may include the transaction amount, and the verification data may include the transaction data. After approval, the server may verify the transaction information by comparing the transaction amount with the transaction amount in the transaction data. Figure 4 As shown, the server can read the transaction amount from the transaction information (S1601), and extract the running amount from the verification data (S1602). If the transaction amount is greater than or equal to the running amount, a verification result of passing the verification can be generated, and a transaction voucher can be generated (S1603), and the newly added amount data and the transaction voucher can be stored (S1604).

[0085] Similarly, if the transaction amount is less than the turnover amount, a verification result indicating that the verification failed can be generated, and a first prompt message (S1605) can be generated. The first prompt message can include the verification result of the transaction amount and the turnover amount, and is used to notify the corresponding client. Therefore, the first prompt message can be "The current transaction amount does not meet the turnover amount requirement, please check carefully" and the like. The server then sends the first prompt message to the first client and the second client (S1606) to notify the corresponding client to execute processing on the transaction business whose transaction amount does not meet the requirements.

[0086] In another feasible implementation, the associated data also includes contract data associated with the newly added payment data, and if the first approval result data includes a first conclusion identifier, the server can also extract transaction data related to the contract from the transaction information. The transaction data is data generated by the first client when executing a transaction business.

[0087] When verifying the transaction data based on the contract data, if the contract data is consistent with the transaction data, a verification result of passing the verification is generated, and the newly added payment data is stored. If the contract data is inconsistent with the transaction data, a second prompt message is generated. Similarly, the second prompt message may also include prompt content of the verification result of the verification inconsistency, and may include specific inconsistent item content. Such as "The current payer is inconsistent with the contract payer, please check" and other content. The server then sends the second prompt message to the first client and the second client to notify the corresponding client to execute processing on the transaction business with inconsistent contract content.

[0088] S105: If the first approval result data includes a second conclusion identifier, send resubmission information to the first client.

[0089] After obtaining the first approval result, if the server reads the second conclusion identifier in the first approval result, it means that the current new payment business has not passed the approval. Therefore, the server can send a resubmission message to the first client to prompt the first client to make modifications and resubmit the new payment data.

[0090] In order to obtain a prompt effect and improve the efficiency of the management of accounts receivable data, in a feasible implementation, the second client can mark the approval items that have not been approved during the approval process, and add the marked approval items to the first approval result and feedback to the server. The server can generate resubmission information based on the first approval result, and the resubmission information includes the marked content that has not been approved, so that after the server sends the resubmission information to the first client, the first client can display the marked content, so that the first client can resubmit the new payment data according to the marked content.

[0091] It can be seen that in the above embodiment, by executing the corresponding steps of the current account data management method, the server can use unified and standardized components to enable various business departments to perform operations on the same platform, thereby ensuring the consistency and real-time update of information. In addition, it can be synchronized to the client or financial management system of other business departments in a timely manner through the server, ensuring that all departments can obtain accurate and consistent information, simplifying the information flow process, eliminating duplication of work, and saving time and resources.

[0092] Moreover, by implementing the current account management method, the server can have the ability to intelligently configure and manage new funds. In the face of ever-changing corporate needs, there is no need for continuous iterative development. With just one-click configuration, you can realize online business such as collection, refund, transaction clearing, and collection approval, thereby reducing human intervention and improving work efficiency. At the same time, the management platform built by the server can also automatically connect to the financial system, push relevant business data, and reduce the possibility of manual operation errors, thereby solving the problem of business and financial differences. In addition, by implementing the current account management method, the server can not only solve a large number of problems in daily work in a short period of time, but also reduce the number of human interventions, further saving human resource costs.

[0093] Further, as a refinement and expansion of the specific implementation of the above embodiment, in order to fully illustrate the specific implementation process of this embodiment, this application provides another method for managing current account data, such as Figure 5 As shown, the method includes:

[0094] S201. Obtain refund application data.

[0095] The refund application data is data generated by the first client when executing a refund service. The first client can perform a refund operation based on a user interface provided by the current account data management platform. For example, a refund control may be provided on some of the funds in the user interface. The user controls the first client to generate refund application data by clicking the refund control. Since the refund application is initiated for a specific amount, the corresponding amount information may be included in the refund application data. After the first client generates the refund application data, it may send the refund application data to the server.

[0096] S202: Create a refund node according to the refund application data, and generate refund approval information according to the refund node.

[0097] After obtaining the refund application data, the server can read the content of the refund application data to obtain the amount involved in the refund application data and the amount-related information, and then create a refund node based on the refund application data. For some amounts, since the business stages, permissions, and other contents involved are consistent, the refund node can be created directly through the previous business node. That is, in a feasible implementation, when creating a refund node based on the refund application data, the server can read the amount information or traceability identifier involved in the refund application data, and search for the corresponding associated data based on the amount information or traceability identifier, and determine the business process and business node based on the associated data, thereby determining the refund node based on the business node.

[0098] After creating the refund node, the server can generate refund approval information according to the refund node, and the refund approval information can be used to present a refund approval user interface on the second client. Therefore, the refund approval information may include the amount information associated with the refund application, the initiator information, the refund method, and other contents.

[0099] S203: Send the refund approval information to the second client, and receive second approval result data fed back by the second client with respect to the refund node information.

[0100] After determining the refund node, the server can send the refund approval information to the second client corresponding to the refund node based on the determined refund node. After receiving the refund approval information, the second client can generate an approval-related user interface based on the refund approval information. Similarly, the user interface for refund approval can also include information related to the amount and functional controls for executing approval work. Through interactive operations on the second client, the second client can feedback approval result data for the refund approval information to the server. In order to facilitate the distinction from the approval result data of the new amount stage, the approval result data generated for the approval of the refund business is called the second approval result.

[0101] S204: Execute a refund service according to the second approval result data.

[0102] After obtaining the second approval result data fed back by the second client, the server can execute the refund service according to the second approval result data. Figure 6 As shown, in a feasible implementation, the server may first read the conclusion identifier from the second approval result. The conclusion identifier is a first conclusion identifier used to indicate that the approval is passed or a second conclusion identifier used to indicate that the approval is not passed. If the second approval result includes the first conclusion identifier, indicating that the current refund application is approved, a refund service execution instruction may be sent to the second client, so that the second client initiates a payment request to the first client.

[0103] If the second approval result includes a second conclusion mark, indicating that the current refund application has not been approved, a refund receipt message may be sent to the first client to prompt the first client to reapply for a refund. In order to obtain a better prompt effect, the refund receipt message may include content used to characterize the reason for the refund failure, such as items that do not meet the refund requirements.

[0104] S205: According to the execution result of the refund service, update the newly added amount data associated with the refund application data.

[0105] Since the refund operation will modify the previously stored payment data, the server can update the newly added payment data associated with the refund application data according to the execution result of the refund service. The execution result of the refund service can be obtained by monitoring the refund amount, refund method, and refund status of the specific refund service to obtain different execution results. For example, the execution result can be a refund payment failure, a full refund success, or a partial refund success, etc. According to different execution results, the stored current account data can be updated.

[0106] It can be seen that in the above embodiment, after receiving the refund application, the server can automatically create a refund business node by matching the associated data of the corresponding amount of the refund business, and send the refund approval information to the second client of the refund business node to trigger the approval process. There is no need for the first client to specify the approval node, thereby reducing human intervention and improving the execution efficiency of the refund approval business.

[0107] In a feasible implementation, the server can also set and update the business status of the current account data according to the execution progress of each business stage. Figure 7 As shown in the figure, after obtaining the newly added payment data, the server creates a status tag and sets the current business status value of the status tag to the pending association state. At the same time, the business progress monitoring process is started to monitor the execution progress of each business stage. When the setting association data is monitored, the status tag can be updated to the pending approval state.

[0108] Similarly, through the business progress monitoring process, whether the approval is submitted is monitored. When the business approval information is sent to the second client, the status label can be updated to the pending approval state. The execution of the approval business is monitored through the business progress monitoring process. When the first approval result data is monitored to include the second conclusion identifier, since the approval has not passed, the status label can be updated to be modified to the pending approval state. When the first approval result data is monitored to include the first conclusion identifier, the verification result can continue to be monitored. If the verification passes, the status label is updated to the payment confirmed state. The storage module of the server performs data storage according to the status label, that is, when the status label is in the payment confirmed state, a payment voucher is generated and the newly added payment data is stored.

[0109] For the refund business, the execution progress of each stage of the refund business can also be monitored through the business monitoring process. When the refund application data is monitored, a status tag can be created and the status tag can be set to the pending approval state. When the second approval result data includes the second conclusion identifier through the business monitoring process, the status tag can be updated to the approval rejection state. When the second approval result data includes the first conclusion identifier through the business monitoring process, the status tag is updated to the refund payment state. And the payment result is monitored, and the status tag is updated according to the payment result. That is, if the payment result is failed, the status tag is updated to the refund payment failure state. If the payment result is full success, the status tag is updated to the full refund success state. If the payment result is partially successful, the status tag is updated to the partial refund success state. The storage module of the server can perform data storage according to the status tag, that is, when the status tag is the full refund success state or the partial refund success state, a payment voucher is generated and the stored current account data is updated.

[0110] Furthermore, as a specific implementation of the current account data management method, the present application embodiment also provides a current account data management system, such as Figure 8 As shown, the accounts receivable data management system includes: a server and at least one first client and at least one second client that establish communication connection with the server through a unified standardized interface.

[0111] The server includes: an acquisition module, an association setting module, a node creation module, an approval request module, a verification module and a feedback module.

[0112] The acquisition module is used to acquire the newly added payment data, wherein the newly added payment data includes data specified by the first client and / or data generated by the first client when executing a transaction business;

[0113] The association setting module is used to set association data based on the newly added payment data, wherein the association data includes business data and verification data, and the verification data is key information extracted from the newly added payment data;

[0114] The node creation module is used to create a business node according to the business data in the associated data, and generate business approval information according to the business node;

[0115] The approval request module is used to send the business approval information to the second client, and receive the first approval result data fed back by the second client for the business approval information, wherein the second client is a client associated with the business node; the second client establishes a communication connection with the server through a unified standardized interface;

[0116] The verification module is used to obtain transaction information of the transaction business when the first approval result data includes a first conclusion identifier, and to verify the transaction information based on the verification data, and to store the newly added amount data as current amount data according to the verification result;

[0117] The feedback module is used to send resubmission information to the first client when the first approval result data includes a second conclusion identifier.

[0118] It should be noted that for other corresponding descriptions of the functional units involved in the accounts receivable data management system provided in the embodiment of the present application, reference can be made to the corresponding descriptions in the accounts receivable data management method described in the above embodiment, and will not be repeated here.

[0119] Based on the current account data management system provided in the above embodiment, the collection, refund, transaction clearing, collection approval and other business can be systematized and online through one-click configuration, thereby reducing human intervention, improving work efficiency, and at the same time, the payment data has good traceability.

[0120] like Fig. 9 As shown, the embodiment of the present application also provides a computer device, which can be specifically a personal computer, a server, a network device, etc. The computer device includes a bus, a processor, a memory and a communication interface, and can also include an input and output interface and a display device. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store location information. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the steps in each method embodiment are implemented.

[0121] Those skilled in the art will appreciate that the structure of the above-mentioned computer device is only a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components, or combine certain components, or have a different arrangement of components.

[0122] In one embodiment, a computer-readable storage medium is provided. The computer-readable storage medium may be non-volatile or volatile, and stores a computer program thereon. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0123] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0124] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

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

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

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

Claims

1. A method for managing current account data, characterized in that: The method comprises: Acquiring newly added payment data, the newly added payment data including data specified by the first client and / or data generated by the first client when executing a transaction; the first client establishing a communication connection with the server through a unified standardized interface; Setting associated data based on the newly added payment data, wherein the associated data includes business data and verification data, and the verification data is key information extracted from the newly added payment data; Creating a business node according to the business data in the associated data, and generating business approval information according to the business node; Sending the business approval information to a second client, and receiving first approval result data fed back by the second client for the business approval information, wherein the second client is a client associated with the business node; the second client establishes a communication connection with the server through a unified standardized interface; If the first approval result data includes a first conclusion identifier, acquiring transaction information of the transaction business, performing verification on the transaction information based on the verification data, and storing the newly added amount data as current amount data according to the verification result; If the first approval result data includes a second conclusion identifier, resubmission information is sent to the first client.

2. The method according to claim 1, characterized in that The method further comprises: Acquire refund application data, where the refund application data is data generated by the first client when executing a refund service; Creating a refund node according to the refund application data, and generating refund approval information according to the refund node; Sending the refund approval information to the second client, and receiving second approval result data fed back by the second client with respect to the refund node information; Execute a refund service according to the second approval result data; According to the execution result of the refund business, the current account data associated with the refund application data is updated.

3. The method according to claim 2, characterized in that Executing a refund service according to the second approval result data includes: Reading a conclusion identifier from the second approval result; If the second approval result includes the first conclusion identifier, sending a refund service execution instruction to the second client, so that the second client initiates a payment request to the first client; If the second approval result includes a second conclusion identifier, refund receipt information is sent to the first client.

4. The method according to claim 1, characterized in that: The associated data is set based on the newly added payment data, including: Extracting a first item tag and a second item tag from the newly added payment data, wherein the first item tag is a item tag specified by the first client; the second item tag is a item tag corresponding to business data; and the business data is data generated when the first client executes a transaction business; performing standardization on the second project label to generate a third project label, wherein the third project label is a project label in a preset project label library that is synonymous with the second project label; The associated data is matched according to the first item tag and the third item tag.

5. The method according to claim 4, characterized in that The method further comprises: Acquire identification information of the newly added payment data, where the identification information includes at least one of a business serial number, a user ID, and an identification number of the first client; generating a traceability identifier based on the identification information, the first item tag, and the third item tag; The traceability identifier is added to the newly added payment data.

6. The method according to claim 1, characterized in that According to the verification result, the newly added amount data is stored as current amount data, including: Reading the transaction amount from the transaction information, and extracting the running amount from the verification data; If the transaction amount is greater than or equal to the turnover amount, a transaction voucher is generated, and the newly added amount data and the transaction voucher are stored; If the transaction amount is less than the turnover amount, a first prompt message is generated, and the first prompt message is sent to the first client and the second client.

7. The method according to claim 1, characterized in that The verification data also includes contract data associated with the newly added payment data. If the first approval result data includes a first conclusion identifier, the method further includes: verifying the transaction information based on the contract data; If the contract data is consistent with the transaction information, storing the newly added payment data; If the contract data is inconsistent with the transaction information, second prompt information is generated, and the second prompt information is sent to the first client and the second client.

8. A data management system for current account, characterized in that: include: A server and at least one first client and at least one second client that establish communication connection with the server through a unified standardized interface; the server comprises: An acquisition module, used to acquire newly added payment data, wherein the newly added payment data includes data specified by the first client and / or data generated by the first client when executing a transaction business; An association setting module, used to set association data based on the newly added payment data, wherein the association data includes business data and verification data, and the verification data is key information extracted from the newly added payment data; A node creation module, used to create a business node according to the business data in the associated data, and generate business approval information according to the business node; An approval request module, used to send the business approval information to a second client, and receive first approval result data fed back by the second client for the business approval information, wherein the second client is a client associated with the business node; the second client establishes a communication connection with the server through a unified standardized interface; A verification module, configured to obtain transaction information of the transaction business when the first approval result data includes a first conclusion identifier, verify the transaction information based on the verification data, and store the newly added amount data as current amount data according to the verification result; A feedback module is used to send resubmission information to the first client when the first approval result data includes a second conclusion identifier.

9. A computer device comprising a storage medium, a processor, and a computer program stored in the storage medium and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images