Bill data processing method, device and system and storage medium

Abstract

The embodiment of the invention provides a bill data processing method, device and system and a storage medium. Comprising the steps of obtaining credit data through an application program interface; in response to the operation that the first worker selects the reconciliation time range and confirms the reconciliation time range, bill data are generated according to the confirmed reconciliation time range and the credit data; analyzing the bill data to obtain a bill attribution; classifying all the bill data according to the bill attribution, so as to generate a plurality of sub-bill checking tasks; calling a preset workflow engine, and inputting a plurality of sub-bill checking tasks to generate a plurality of task flows; and in each task flow, packaging the sub-bill checking task corresponding to each task flow to form a transmission data packet, and sending the transmission data packet to each credit sharing system, so that each credit sharing system analyzes the transmission data packet to obtain the sub-bill checking task corresponding to the bill attribution, and processes the sub-bill checking task. The method is used for achieving the effect of improving the bill data processing efficiency.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a bill data processing method, device, system and storage medium. Background Art

[0002] In the financial management of modern enterprises, reconciliation is an important part of ensuring the accuracy and consistency of financial data. Especially for large enterprises with multiple branches, the head office needs to reconcile accounts with each branch regularly to ensure that the financial data of each branch is consistent with the records of the head office.

[0003] In the prior art, the XML files of each credit provider are read and stored in a database. The head office extracts data every quarter, checks it manually, and confirms it with each branch and credit provider via email to form the final billing data.

[0004] However, manual verification and confirmation is not only time-consuming and labor-intensive, but also prone to human errors. Summary of the invention

[0005] The embodiments of the present application provide a bill data processing method, device, system and storage medium to achieve the effect of improving the bill data processing efficiency.

[0006] In a first aspect, an embodiment of the present application provides a bill data processing method, which is applied to a general credit system, comprising:

[0007] Obtain credit data through the application program interface; in response to the first staff member selecting and confirming the reconciliation time range, generate bill data according to the confirmed reconciliation time range and credit data; parse the bill data to obtain the bill location; classify all bill data according to the bill location to generate multiple sub-bill verification tasks; call the preset workflow engine, and input multiple sub-bill verification tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill verification task; in each task flow, package the sub-bill verification tasks corresponding to each task flow to form a transmission data packet; send the transmission data packet to each sub-credit system so that each sub-credit system obtains the transmission data packet of the bill location, and parses the transmission data packet to obtain the sub-bill verification task corresponding to the bill location, and processes the sub-bill verification task.

[0008] In a possible implementation, before calling the preset workflow engine, it also includes: creating a preset process model; adding a start event and a first parallel gateway in the preset process model, and connecting the start event to the first parallel gateway; creating multiple branches from the first parallel gateway, wherein each branch is connected to a service task; after each sub-bill verification task, adding a second parallel gateway to merge multiple branches; adding an end event in the preset process model, and connecting the second parallel gateway to the end event to generate a process instance; deploying the process instance to the workflow engine template, and starting the process instance to obtain the preset workflow engine.

[0009] In one possible implementation, the sub-bill verification tasks corresponding to each task flow are packaged to form a transmission data packet, including: encrypting the sub-bill verification tasks using a preset algorithm to obtain an encrypted data packet; signing the encrypted data packet using a private key to obtain a digital signature; and combining the digital signature and the encrypted data packet to form a transmission data packet.

[0010] In a second aspect, the present application embodiment provides a bill data processing method, which is applied to each credit system, including:

[0011] Receive a transmission data packet sent by the general credit system, wherein the transmission data packet is the credit data obtained by the general credit system through the application program; in response to the first staff member selecting a reconciliation time range and confirming the operation, generate bill data according to the confirmed reconciliation time range and credit data, parse the bill data to obtain the bill location, and classify all bill data according to the bill location to generate multiple sub-bill verification tasks; call a preset workflow engine, and input multiple sub-bill verification tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill verification task; in each task flow, package the sub-bill verification tasks corresponding to each task flow; parse the transmission data packet to obtain the sub-bill verification tasks corresponding to the bill location; and process the sub-bill verification tasks.

[0012] In one possible implementation, the sub-bill verification task is processed, including: traversing all orders in the sub-bill verification task to determine whether any order is an inter-provincial joint guarantee order; if any order is an inter-provincial joint guarantee order, an early warning is issued for any order to prompt a second staff member to determine whether any order needs to be adjusted; in response to the second staff member selecting a target joint guarantee system and triggering an adjustment button operation, any order is sent to the target joint guarantee system so that the credit system of the target joint guarantee company processes any order; in response to the second staff member triggering a no adjustment button operation, the details of any order are displayed to enable the second staff member to check the order.

[0013] In one possible implementation, a transmission data packet is parsed to obtain a sub-bill verification task corresponding to the bill location, including: format parsing the transmission data packet according to a preset format to obtain a digital signature and an encrypted data packet; obtaining a public key of the general credit system by querying the blockchain network; using the public key to verify the digital signature, and comparing the obtained verification result with the encrypted data packet for consistency; if the verification result is consistent with the encrypted data packet, decrypting the encrypted data packet using a preset algorithm to obtain the sub-bill verification task corresponding to the bill location; if the verification result is inconsistent with the encrypted data packet, sending a prompt message to the general credit system.

[0014] In a third aspect, an embodiment of the present application provides a bill data processing device, which is applied to a general credit system, including:

[0015] The credit data acquisition module is used to obtain credit data through an application program interface.

[0016] The bill data generation module is used to generate bill data according to the confirmed reconciliation time range and credit data in response to the first staff member selecting and confirming the reconciliation time range.

[0017] The location parsing module is used to parse the billing location from the billing data.

[0018] The sub-bill checking task generation module is used to classify all bill data according to the bill location to generate multiple sub-bill checking tasks.

[0019] The task flow generation module is used to call a preset workflow engine and input multiple sub-bill verification tasks to generate multiple task flows, where each task flow corresponds to a sub-bill verification task.

[0020] The data packaging module is used to package the sub-bill verification tasks corresponding to each task flow in each task flow to form a transmission data packet.

[0021] The data packet sending module is used to send the transmission data packet to each sub-credit system so that each sub-credit system can obtain the transmission data packet of the bill location, and parse the transmission data packet to obtain the sub-bill verification task corresponding to the bill location, and process the sub-bill verification task.

[0022] In a fourth aspect, an embodiment of the present application provides a bill data processing device, which is applied to each credit system, including:

[0023] The data packet receiving module is used to receive transmission data packets sent by the general credit system, wherein the transmission data packets are credit data obtained by the general credit system through the application program; in response to the operation of the first staff member selecting a reconciliation time range and confirming it, generate bill data according to the confirmed reconciliation time range and credit data, parse the bill data to obtain the bill location, and classify all bill data according to the bill location to generate multiple sub-bill verification tasks; call the preset workflow engine, and input multiple sub-bill verification tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill verification task; in each task flow, the sub-bill verification tasks corresponding to each task flow are packaged.

[0024] The data packet parsing module is used to parse the transmission data packet to obtain the sub-bill verification task corresponding to the bill location.

[0025] The task processing module is used to process sub-bill verification tasks.

[0026] In the fifth aspect, an embodiment of the present application provides a total credit system, including: a memory, a processor; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory, so that the processor executes the first aspect above and / or various possible implementations of the first aspect.

[0027] In the sixth aspect, an embodiment of the present application provides a credit rating system, including: a memory, a processor; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory, so that the processor executes the above second aspect and / or various possible implementations of the second aspect.

[0028] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored. When the computer execution instructions are executed by a processor, they are used to implement the first aspect and / or various possible implementation methods of the first aspect, or the second aspect and / or various possible implementation methods of the second aspect.

[0029] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect, or the second aspect and / or various possible implementations of the second aspect.

[0030] The bill data processing method, device, system and storage medium provided in the embodiment of the present application use a preset workflow engine to simultaneously generate multiple parallel task flows, and each task flow corresponds to a sub-bill verification task of a sub-credit system. In each task flow, the sub-bill verification task corresponding to each task flow is packaged to form a transmission data packet, and the transmission data packet is sent to each sub-credit system, so that each sub-credit system parses the transmission data packet after obtaining the transmission data packet to obtain the sub-bill verification task corresponding to the sub-credit system, and processes the sub-bill verification task of the sub-credit system of the data. By sending the sub-bill verification task to each sub-credit system through the general credit system at the same time, the occurrence of human errors can be reduced, thereby improving the efficiency of bill data processing. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0032] Figure 1 A schematic diagram of a scenario of a bill data processing method provided in an embodiment of the present application;

[0033] Figure 2 A flowchart of a bill data processing method provided in an embodiment of the present application;

[0034] Figure 3 A schematic diagram of the structure of the bill data processing device provided in the embodiment of the present application Figure 1 ;

[0035] Figure 4 A schematic diagram of another bill data processing device provided in an embodiment of the present application Figure 2 ;

[0036] Figure 5 A schematic diagram of the structure of the general credit system provided for this application;

[0037] Figure 6 A schematic diagram of the structure of the credit system provided for this application.

[0038] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0039] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0040] In order to clearly understand the technical solution of the present application, the solution of the prior art is first described in detail. In the financial management of modern enterprises, billing data verification is an important link to ensure the accuracy and consistency of financial data. Especially for large enterprises with multiple branches, the head office needs to reconcile accounts with each branch regularly to ensure that the financial data of each branch is consistent with the records of the head office. In the prior art, the following method is usually used for reconciliation. First, the head office reads financial data from each credit provider. These data are usually stored in the form of extensible markup language files. The head office stores the data in these files in a central database. The head office extracts relevant data from the database every quarter for manual verification. In the manual verification process, the financial staff needs to check whether the financial data between the head office and each branch is consistent one by one. After the verification is completed, the head office sends the verification results to each branch and credit provider by email, requiring them to confirm the accuracy of the data. After receiving the email, each branch and credit provider need to review the data and feedback the confirmation results to the head office. Finally, the head office forms the final billing data based on the feedback information. However, this method of manual verification and confirmation has many disadvantages. First of all, the manual verification process is time-consuming and labor-intensive, and is prone to human errors, which can lead to inaccurate billing data and affect the company's financial decisions.

[0041] In view of the above technical problems, the inventors have come up with the idea of ​​building a general credit system, which obtains the credit data of credit merchants regularly through the application program interface. The staff of the general credit system selects the reconciliation time range on the reconciliation page of the system, generates bill data according to the confirmed reconciliation time range and the corresponding credit data, and classifies the bills and data according to the bill attribution in all the bill data, and generates the sub-bill verification tasks corresponding to each sub-credit system. A preset workflow engine is used to generate multiple parallel task flows at the same time, and each task flow corresponds to a sub-bill verification task of a sub-credit system. In each task flow, the sub-bill verification tasks corresponding to each task flow are packaged to form a transmission data packet, and the transmission data packet is sent to each sub-credit system, so that each sub-credit system parses the transmission data packet after obtaining the transmission data packet to obtain the sub-bill verification task corresponding to the sub-credit system, and processes the sub-bill verification task of the data sub-credit system. By sending the sub-bill verification tasks to each sub-credit system at the same time through the general credit system, the occurrence of human errors can be reduced, thereby improving the efficiency of bill data processing.

[0042] Based on the above creative findings, the inventor proposed the technical solution of the present application.

[0043] Figure 1 A schematic diagram of a scenario of a bill data processing method provided in an embodiment of the present application. Figure 1 As shown, the specific application scenarios of this application include: a general credit system 101, various branch credit systems 102 and a credit merchant system 103.

[0044] Specifically, the general credit system 101 obtains the credit data of the credit provider system 103 through the application program interface; the first staff member selects the reconciliation time range on the reconciliation page of the general credit system 101 and clicks to confirm, the general credit system 101 generates billing data according to the confirmed reconciliation time range and credit data, parses the billing location from the billing data, and classifies all billing data according to the billing location to generate multiple sub-bill verification tasks, calls the preset workflow engine, and inputs multiple sub-bill verification tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill verification task; in each task flow, the sub-bill verification tasks corresponding to each task flow are packaged to form transmission data packets, and each transmission data packet is sent to each sub-credit system 102, each sub-credit system 102 obtains its corresponding transmission data packet, and parses the transmission data packet to obtain the corresponding sub-bill verification task, and performs verification and confirmation processing on each order in the sub-bill verification task.

[0045] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0046] Figure 2 A flowchart of a bill data processing method provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the main execution diagram of this embodiment is Figure 1 The total credit system shown may also be other devices with similar functions, and this embodiment is not particularly limited here. The method includes:

[0047] S201: Obtain credit data through an application programming interface.

[0048] Among them, credit data is usually provided by the credit rating system of credit rating companies. These credit rating companies usually provide RESTful API or SOAP API. RESTful API uses HTTP protocol for communication, and the commonly used data format is JSON (JavaScript Object Notation). SOAP API is an XML-based protocol, and the commonly used data format is XML (eXtensible Markup Language).

[0049] Specifically, according to the API document, configure the HTTP request, including the URL, request method, and header information, etc. Use a programming language to send the HTTP request, parse the response data returned by the API, obtain the credit data, and store it.

[0050] S202: In response to the first staff member selecting and confirming the reconciliation time range, generating bill data according to the confirmed reconciliation time range and credit data.

[0051] The default reconciliation time range is the last quarter. The billing data includes the data of various financial items such as income, expenditure, accounts receivable, accounts payable, etc. of each credit system.

[0052] Specifically, the first staff member selects the time range for the required reconciliation through the user interface. After the selection is completed, the staff member confirms the time range. The general credit system extracts the financial data within the corresponding time period based on the confirmed reconciliation time range, and the system integrates and matches the extracted financial data. First. The system performs a preliminary match on the financial data between each branch credit system. For inconsistent data, the general credit system automatically corrects it using preset verification rules and algorithms. For example, common input errors can be checked for rationality based on historical data and business rules. After the automatic verification and correction are completed, the general credit system generates the final billing data.

[0053] S203: Analyze the billing data to obtain the billing location.

[0054] Specifically, if the billing data directly contains location information, such as a branch name or an area code, the field is directly read to determine the billing location; if the billing data does not contain direct location information, the billing location is inferred through other associated fields.

[0055] S204: Classify all bill data according to the bill location to generate multiple sub-bill verification tasks.

[0056] Among them, the billing data includes multiple orders.

[0057] Specifically, all bill data are traversed, all bill data are classified according to the billing location of each order, and all orders with the same billing location are organized into a sub-bill verification task.

[0058] S205: Calling a preset workflow engine, and inputting a plurality of sub-bill checking tasks to generate a plurality of task flows, wherein each task flow corresponds to a sub-bill checking task.

[0059] Among them, a workflow engine is a software system or component used to define, execute and manage business processes or workflows.

[0060] Specifically, before calling the preset workflow engine, the definition process of the preset workflow engine is also included, including Sa1~Sa6:

[0061] Sa1: Create a preset process model.

[0062] Specifically, create and edit process models through the web interface provided by flowable, open the flowable process configuration visualization page, and create a new process model.

[0063] Sa2: Add a start event and the first parallel gateway to the preset process model, and connect the start event to the first parallel gateway.

[0064] Among them, the parallel gateway is a type of gateway in business process modeling and annotation, which is used to manage parallel branches and merge branches in the process. The main function of the parallel gateway is to allow multiple process paths to be executed simultaneously without conditional judgment or selection.

[0065] Specifically, a start event is added to the created preset process model, and a first parallel gateway is added to the preset process model, and the start event is connected to the parallel branch of the first parallel gateway.

[0066] Sa3: Create multiple branches from the first parallel gateway, where each branch is connected to a service task.

[0067] Specifically, each branch created from the first parallel gateway will be connected to a service task respectively, so that the general credit system executes multiple service tasks simultaneously, and each service task corresponds to an independent branch.

[0068] Sa4: Add a second parallel gateway after each sub-bill reconciliation task to merge multiple branches.

[0069] Specifically, after each service task is completed, these branches will converge to the second parallel gateway, wherein the function of the second parallel gateway is to wait for the service tasks of all branches to be completed before continuing to execute subsequent process steps.

[0070] Sa5: Add an end event to the preset process model and connect the second parallel gateway to the end event to generate a process instance.

[0071] Specifically, an end event is added after the second parallel gateway. After the second parallel gateway completes the merging of all service tasks, the process will continue to execute until the end event, marking the end of the process. Convert the designed process model into a process instance.

[0072] Sa6: Deploy the process instance to the workflow engine template and start the process instance to obtain the preset workflow engine.

[0073] Specifically, the process instance is deployed to a preconfigured workflow engine template, and the deployed process instance is started in the workflow engine template.

[0074] Specifically, the flowable workflow engine is called, and multiple sub-bill verification tasks are input to replace the service tasks in the process instance to obtain multiple task flows.

[0075] S206: In each task flow, the sub-bill checking tasks corresponding to each task flow are packaged to form a transmission data packet.

[0076] Specifically, the packaging process includes Sb1~Sb3:

[0077] Sb1: Use a preset algorithm to encrypt the sub-bill verification task to obtain an encrypted data packet.

[0078] The preset algorithm may be a symmetric encryption algorithm or an asymmetric encryption algorithm.

[0079] Specifically, in each task flow, the corresponding sub-bill verification task is input into a preset encryption algorithm, and the encryption operation is performed to form an encrypted data packet.

[0080] Sb2: Use the private key to sign the encrypted data packet to obtain a digital signature.

[0081] Specifically, the encrypted data packet is signed using the private key of the general credit system to obtain a digital signature.

[0082] Sb3: Combine the digital signature and encrypted data packets to form a transmission data packet.

[0083] Specifically, the digital signature and the encrypted data packet are combined in JSON format to form a transmission data packet.

[0084] S207: Send the transmission data packet to each sub-credit system so that each sub-credit system obtains the transmission data packet of the bill location, and parses the transmission data packet to obtain the sub-bill verification task corresponding to the bill location, and processes the sub-bill verification task.

[0085] Specifically, the transmission data packet is sent to each sub-credit system through a secure network, and an email is automatically sent to each sub-credit system through Spring-boot to remind the staff of each sub-credit system to process the sub-bill verification tasks in each sub-credit system.

[0086] In summary, a preset workflow engine is used to simultaneously generate multiple parallel task flows, and each task flow corresponds to a sub-bill verification task of a sub-credit system. In each task flow, the sub-bill verification task corresponding to each task flow is packaged to form a transmission data packet, and the transmission data packet is sent to each sub-credit system, so that each sub-credit system parses the transmission data packet after obtaining the transmission data packet to obtain the sub-bill verification task corresponding to the sub-credit system, and processes the sub-bill verification task of its own sub-credit system. By sending sub-bill verification tasks to each sub-credit system at the same time through the general credit system, the occurrence of human errors can be reduced, thereby improving the efficiency of bill data processing.

[0087] In another embodiment of the present application, the execution subject of this embodiment is Figure 1 Each sub-credit system shown may also be other devices with similar functions, and this embodiment is not particularly limited here. The method includes:

[0088] S301: Receive a transmission data packet sent by the general credit system, wherein the transmission data packet is the credit data obtained by the general credit system through the application program; in response to the first staff member selecting a reconciliation time range and confirming the operation, generate bill data according to the confirmed reconciliation time range and credit data, parse the bill data to obtain the bill location, and classify all bill data according to the bill location to generate multiple sub-bill verification tasks; call a preset workflow engine, and input multiple sub-bill verification tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill verification task; in each task flow, the sub-bill verification tasks corresponding to each task flow are packaged.

[0089] S302: Parse the transmission data packet to obtain the sub-bill verification task corresponding to the bill location.

[0090] Specifically, the parsing process includes Sc1~Sc5:

[0091] Sc1: Parse the transmission data packet according to the preset format to obtain the digital signature and encrypted data packet.

[0092] Specifically, the transmission data packet is parsed according to the JSON format, and the data signature and the encrypted data packet are extracted from the parsed JSON data.

[0093] Sc2: Obtain the public key of the total credit system by querying the blockchain network.

[0094] Specifically, by accessing the blockchain network, the public key of the total credit system is queried and obtained.

[0095] Sc3: Use the public key to verify the digital signature and compare the verification result with the encrypted data packet to see if they are consistent.

[0096] Specifically, the public key of the total credit system is used to verify the digital signature, obtain a verification result, and compare the verification result with the encrypted data packet to see if they are consistent.

[0097] Sc4: If the verification result is consistent with the encrypted data packet, the encrypted data packet is decrypted using a preset algorithm to obtain the sub-bill verification task corresponding to the bill location.

[0098] Specifically, if the verification result is consistent with the encrypted data packet, it means that the encrypted data packet has authenticity and integrity, and the preset algorithm is continued to be used to decrypt the encrypted data packet to obtain the sub-bill verification task corresponding to the bill location.

[0099] Sc5: If the verification result is inconsistent with the encrypted data packet, a prompt message is sent to the general credit system.

[0100] Specifically, if the verification result is inconsistent with the encrypted data packet, an email is sent to the general credit system so that the general credit system resends the sub-bill verification task to the location where the bill belongs.

[0101] S303: Process the sub-bill verification task.

[0102] Specifically, the process of processing the sub-bill checking task includes Sd1 to Sd4:

[0103] Sd1: Traverse all orders in the sub-bill verification task to determine whether any order is an inter-provincial joint guarantee order.

[0104] Among them, inter-provincial joint guarantee orders refer to orders involving cross-provincial joint guarantee agreements or arrangements. In the case of inter-provincial joint guarantee, institutions or companies in different provinces jointly participate in the joint guarantee, involving resource allocation and risk management in multiple provinces.

[0105] Specifically, each sub-credit system traverses all orders in the sub-bill verification task. During the traversal process, each sub-credit system checks the type of each order to determine whether it is an inter-provincial joint guarantee order.

[0106] Sd2: If any order is an inter-provincial guarantee order, an early warning will be issued for any order to prompt the second staff member to determine whether any order needs to be adjusted.

[0107] Specifically, if the credit system determines that an order is an inter-provincial guarantee order, an early warning prompt will be generated, where the early warning prompt can be a pop-up window, notification or other form, clearly stating that the order is an inter-provincial guarantee order, and a second staff member is required to make a judgment. The second staff member needs to judge whether the order needs to be transferred to other joint guarantee systems for processing based on the early warning prompt.

[0108] Sd3: In response to the second staff member selecting the target joint guarantee system and triggering the adjustment button operation, any order is sent to the target joint guarantee system so that the credit system of the target joint guarantee company processes any order.

[0109] Specifically, the second staff member selects the target joint guarantee system to be adjusted according to the early warning prompt, triggers the adjustment button, confirms that the order will be adjusted to the target joint guarantee system, and the credit system sends the order to the selected target joint guarantee system so that the target joint guarantee system receives the order and processes it.

[0110] Sd4: In response to the second staff member triggering the no-adjustment button operation, displaying the details of any order so that the second staff member can check the order.

[0111] Specifically, if the second staff member does not determine the order as an order to be adjusted, after the second staff member triggers the no-adjustment button, the details of the order are displayed so that the second staff member can check and process the order.

[0112] In summary, when the sub-credit system determines that an order is an inter-provincial joint guarantee order, an adjustment plan is proposed, and the sub-credit system of the bill's location determines whether the order needs to be adjusted. When adjustment is needed, in response to the second staff member selecting the target joint guarantee system and triggering the adjustment button, the order is sent to the target joint guarantee system so that the target joint guarantee system can process the order. The sub-credit system determines whether the order needs to be adjusted, which can further improve the efficiency of bill data processing.

[0113] Figure 3 A schematic diagram of the structure of the bill data processing device provided in the embodiment of the present application Figure 1 .like Figure 3 As shown, the bill data processing device includes a credit data acquisition module 301, a bill data generation module 302, a place of origin analysis module 303, a sub-bill verification task generation module 304, a task flow generation module 305, a data packaging module 306 and a data packet sending module 307.

[0114] The credit data acquisition module 301 is used to acquire credit data through an application program interface.

[0115] The bill data generation module 302 is used to generate bill data according to the confirmed account reconciliation time range and credit data in response to the first staff member selecting and confirming the account reconciliation time range.

[0116] The location parsing module 303 is used to parse the billing location from the billing data.

[0117] The sub-bill checking task generating module 304 is used to classify all the bill data according to the bill location to generate multiple sub-bill checking tasks.

[0118] The task flow generation module 305 is used to call a preset workflow engine and input multiple sub-bill checking tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill checking task.

[0119] The data packaging module 306 is used to package the sub-bill checking tasks corresponding to each task flow in each task flow to form a transmission data packet.

[0120] The data packet sending module 307 is used to send the transmission data packet to each sub-credit system so that each sub-credit system can obtain the transmission data packet of the bill location, and parse the transmission data packet to obtain the sub-bill verification task corresponding to the bill location, and process the sub-bill verification task.

[0121] In a possible implementation, the bill data processing device also includes a workflow engine building module, which is used to create a preset process model; add a start event and a first parallel gateway in the preset process model, and connect the start event to the first parallel gateway; create multiple branches from the first parallel gateway, each branch is connected to a service task; after each sub-bill verification task, add a second parallel gateway to merge multiple branches; add an end event in the preset process model, and connect the second parallel gateway to the end event to generate a process instance; deploy the process instance to the workflow engine template, and start the process instance to obtain the preset workflow engine.

[0122] In one possible implementation, the data packaging module 306 is specifically used to encrypt the sub-bill verification task using a preset algorithm to obtain an encrypted data packet; sign the encrypted data packet using a private key to obtain a digital signature; and combine the digital signature and the encrypted data packet to form a transmission data packet.

[0123] The bill data processing device provided in this embodiment can execute the method provided in the above method embodiment, and its implementation principle and technical effect are similar, and this embodiment will not be repeated here.

[0124] Figure 4 A schematic diagram of another bill data processing device provided in an embodiment of the present application Figure 2 .like Figure 4 As shown, the bill data processing device includes: a data packet receiving module 401, a data packet parsing module 402 and a task processing module 403.

[0125] The data packet receiving module 401 is used to receive a transmission data packet sent by the general credit system, wherein the transmission data packet is the credit data obtained by the general credit system through the application program; in response to the operation of the first staff member selecting a reconciliation time range and confirming it, generate bill data according to the confirmed reconciliation time range and credit data, parse the bill data to obtain the bill location, and classify all bill data according to the bill location to generate multiple sub-bill verification tasks; call a preset workflow engine, and input multiple sub-bill verification tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill verification task; in each task flow, the sub-bill verification tasks corresponding to each task flow are packaged.

[0126] The data packet parsing module 402 is used to parse the transmission data packet to obtain the sub-bill verification task corresponding to the bill location.

[0127] The task processing module 403 is used to process the sub-bill verification task.

[0128] In one possible implementation, the task processing module 403 is specifically used to traverse all orders in the sub-bill verification task and determine whether any order is an inter-provincial joint guarantee order; if any order is an inter-provincial joint guarantee order, an early warning is issued for any order to prompt the second staff member to determine whether any order needs to be adjusted; in response to the second staff member selecting the target joint guarantee system and triggering the adjustment button operation, any order is sent to the target joint guarantee system so that the credit system of the target joint guarantee company processes any order; in response to the second staff member triggering the no adjustment button operation, the details of any order are displayed so that the second staff member can check the order.

[0129] In one possible implementation, the data packet parsing module 402 is specifically used to parse the transmission data packet in a preset format to obtain a digital signature and an encrypted data packet; obtain the public key of the general credit system by querying the blockchain network; use the public key to verify the digital signature, and compare the obtained verification result with the encrypted data packet to see if they are consistent; if the verification result is consistent with the encrypted data packet, use a preset algorithm to decrypt the encrypted data packet to obtain the sub-bill verification task corresponding to the bill location; if the verification result is inconsistent with the encrypted data packet, send a prompt message to the general credit system.

[0130] The bill data processing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0131] Figure 5 The schematic diagram of the structure of the total credit system provided for this application. Figure 5 As shown, the total credit system provided by this embodiment includes: at least one processor 501 and a memory 502. Optionally, the system also includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected via a bus 504.

[0132] In a specific implementation process, at least one processor 501 executes the computer-executable instructions stored in the memory 502, so that at least one processor 501 executes the above method.

[0133] The specific implementation process of the processor 501 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0134] Figure 6 The structural diagram of the credit system provided for this application. Figure 6 As shown, the credit system provided in this embodiment includes: at least one processor 601 and a memory 602. Optionally, the system also includes a communication component 603. The processor 601, the memory 602 and the communication component 603 are connected via a bus 604.

[0135] In a specific implementation process, at least one processor 601 executes the computer execution instructions stored in the memory 602, so that at least one processor 601 executes the above method.

[0136] The specific implementation process of the processor 601 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0137] In the above embodiments, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly implemented as a hardware processor, or can be implemented by a combination of hardware and software modules in the processor.

[0138] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.

[0139] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0140] An embodiment of the present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0141] An embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0142] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0143] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0144] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0145] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0146] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0147] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0148] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0149] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A bill data processing method, characterized in that: Applied to the general credit system, including: Obtain credit data through the application program interface; In response to the first staff member selecting and confirming the reconciliation time range, generating bill data according to the confirmed reconciliation time range and the credit data; Parsing the bill data to obtain the billing location; Classify all bill data according to the bill location to generate multiple sub-bill checking tasks; Calling a preset workflow engine, and inputting the multiple sub-bill checking tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill checking task; In each task flow, the sub-bill checking tasks corresponding to each task flow are packaged to form a transmission data packet; The transmission data packet is sent to each sub-credit system so that each sub-credit system obtains the transmission data packet of the bill location, and parses the transmission data packet to obtain the sub-bill verification task corresponding to the bill location, and processes the sub-bill verification task.

2. The method according to claim 1, characterized in that Before calling the preset workflow engine, the method further includes: Create preset process models; Adding a start event and a first parallel gateway in the preset process model, and connecting the start event to the first parallel gateway; Creating a plurality of branches from the first parallel gateway, wherein each branch is connected to a service task; After each sub-bill checking task, adding a second parallel gateway to merge the multiple branches; Adding an end event in the preset process model, and connecting the second parallel gateway to the end event to generate a process instance; The process instance is deployed into a workflow engine template, and the process instance is started to obtain the preset workflow engine.

3. The method according to claim 1, characterized in that The step of packaging the sub-bill checking tasks corresponding to each task flow to form a transmission data packet includes: Encrypt the sub-bill checking task using a preset algorithm to obtain an encrypted data packet; Sign the encrypted data packet using a private key to obtain a digital signature; The digital signature and the encrypted data packet are combined to form the transmission data packet.

4. A bill data processing method, characterized in that: Applied to various credit systems, including: Receive a transmission data packet sent by the general credit system, wherein the transmission data packet is the credit data obtained by the general credit system through the application program; in response to the operation of the first staff selecting a reconciliation time range and confirming it, generate bill data according to the confirmed reconciliation time range and the credit data, parse the bill data to obtain the bill location, and classify all bill data according to the bill location to generate multiple sub-bill checking tasks; call a preset workflow engine, and input the multiple sub-bill checking tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill checking task; in each task flow, the sub-bill checking tasks corresponding to each task flow are packaged; Parsing the transmission data packet to obtain the sub-bill checking task corresponding to the bill attribution location; The sub-bill verification task is processed.

5. The method according to claim 4, characterized in that The processing of the sub-bill checking task includes: Traverse all orders in the sub-bill checking task to determine whether any order is an inter-provincial joint guarantee order; If any of the orders is an inter-provincial joint guarantee order, an early warning is issued for the order to prompt the second staff member to determine whether any of the orders needs to be adjusted; In response to the second staff selecting the target joint guarantee system and triggering the adjustment button operation, sending the any order to the target joint guarantee system so that the credit system of the target joint guarantee company processes the any order; In response to the second staff member triggering the no-adjustment button operation, the details of any order are displayed to enable the second staff member to check the order.

6. The method according to claim 4, characterized in that The parsing of the transmission data packet to obtain the sub-bill checking task corresponding to the bill attribution location includes: Parsing the transmission data packet according to a preset format to obtain a digital signature and an encrypted data packet; Obtaining the public key of the total credit system by querying the blockchain network; Verify the digital signature using the public key, and compare the obtained verification result with the encrypted data packet to see whether they are consistent; If the verification result is consistent with the encrypted data packet, the encrypted data packet is decrypted using a preset algorithm to obtain the sub-bill verification task corresponding to the bill attribution location; If the verification result is inconsistent with the encrypted data packet, a prompt message is sent to the general credit system.

7. A bill data processing device, characterized in that: Applied to the general credit system, including: A credit data acquisition module, used to acquire credit data through an application program interface; A bill data generating module, configured to generate bill data according to the confirmed account reconciliation time range and the credit data in response to the first staff member selecting and confirming the account reconciliation time range; A location parsing module, used for parsing the bill data to obtain the bill location; A sub-bill checking task generating module, used to classify all bill data according to the bill attribution location to generate multiple sub-bill checking tasks; A task flow generation module, used to call a preset workflow engine and input the multiple sub-bill checking tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill checking task; A data packaging module is used to package the sub-bill checking tasks corresponding to each task flow in each task flow to form a transmission data packet; The data packet sending module is used to send the transmission data packet to each sub-credit system so that each sub-credit system obtains the transmission data packet of the bill location, and parses the transmission data packet to obtain the sub-bill verification task corresponding to the bill location, and processes the sub-bill verification task.

8. A bill data processing device, characterized in that: Applied to various credit systems, including: A data packet receiving module is used to receive a transmission data packet sent by a general credit system, wherein the transmission data packet is credit data obtained by the general credit system through an application program; in response to the operation of the first staff selecting a reconciliation time range and confirming it, generate bill data according to the confirmed reconciliation time range and the credit data, parse the bill data to obtain the bill location, and classify all bill data according to the bill location to generate multiple sub-bill checking tasks; call a preset workflow engine, and input the multiple sub-bill checking tasks to generate multiple task flows, wherein each task flow corresponds to a sub-bill checking task; in each task flow, the sub-bill checking tasks corresponding to each task flow are packaged; A data packet parsing module, used for parsing the transmission data packet to obtain a sub-bill checking task corresponding to the bill attribution location; The task processing module is used to process the sub-bill verification task.

9. A total credit system, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 3.

10. A credit system, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 4 to 6.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 3, or the method according to any one of claims 4 to 6 when executed by a processor.

Images