CN110689418B - Bill generation method and device - Google Patents

Abstract

One or more embodiments of the present specification disclose a method and an apparatus for generating a bill, which are used to integrate a bill generation process into one device, thereby achieving an effect of generating a bill quickly and easily. The method comprises the following steps: retrieving relevant transaction data of the first user from at least one service node; the service node is used for recording the related transaction data generated in the user transaction process; determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data; generating a bill for the first user based on the first transaction data.

Description

Bill generation method and device

technical field

This document relates to the technical field of data processing, and in particular to a bill generation method and device.

Background technique

With the rapid increase in the number of merchants, the tasks undertaken by the billing platform are becoming more and more onerous. One of the problems facing the billing platform today is how to save resources as much as possible and ensure the timely output of a large number of merchant bills.

The existing merchant billing system relies on the scheduling and quality inspection functions provided by ODPS (Open Data Processing Service) to generate corresponding billing nodes, while the billing platform is only responsible for exporting CSV (Comma-Separated Values, comma-separated value) file format bill. The existing method distributes the life cycle of a single bill into two systems (that is, the billing platform and ODPS), so if the bill is wrong, the two systems need to be checked, and, because the scheduling of ODPS is too flexible, the call chain The road is too deep, and as the number of bills increases, the billing links will only become more and more complicated.

Contents of the invention

The purpose of one or more embodiments of this specification is to provide a bill generation method and device, which are used to integrate the bill generation process into one device, so as to achieve the effect of quickly and easily generating bills.

In order to solve the above technical problems, one or more embodiments of this specification are implemented as follows:

In one aspect, one or more embodiments of this specification provide a bill generation method, including:

Retrieving the relevant transaction data of the first user from at least one service node; wherein the service node is used to record the relevant transaction data generated during the user's transaction process;

determining the bill request information of the first user, and processing the relevant transaction data according to the bill request information to obtain first transaction data;

A bill for the first user is generated according to the first transaction data.

On the other hand, one or more embodiments of this specification provide a bill generation device, including:

A calling module, which calls the relevant transaction data of the first user from at least one service node; wherein, the service node is used to record the relevant transaction data generated during the user's transaction process;

A processing module, which determines the bill request information of the first user, processes the relevant transaction data according to the bill request information, and obtains first transaction data;

The generation module generates the first user's bill according to the first transaction data.

In another aspect, one or more embodiments of this specification provide a bill generation device, including:

processor; and

A memory arranged to store computer-executable instructions that, when executed, cause the processor to:

Retrieving the relevant transaction data of the first user from at least one service node; wherein the service node is used to record the relevant transaction data generated during the user's transaction process;

determining the bill request information of the first user, and processing the relevant transaction data according to the bill request information to obtain first transaction data;

A bill for the first user is generated according to the first transaction data.

In another aspect, one or more embodiments of the present specification provide a storage medium for storing computer-executable instructions, and the executable instructions implement the following processes when executed:

Retrieving the relevant transaction data of the first user from at least one service node; wherein the service node is used to record the relevant transaction data generated during the user's transaction process;

determining the bill request information of the first user, and processing the relevant transaction data according to the bill request information to obtain first transaction data;

A bill for the first user is generated according to the first transaction data.

By adopting the technical solution of an embodiment of this specification, the bill generation process can be integrated on one device without relying on other platforms, thereby making the bill generation faster and more unified; in addition, it is precisely because of the unified bill generation link This makes the generation process of each bill a clear linear link, which makes it easy to troubleshoot various problems in the bill generation process and reduces the error probability of the bill generation process.

Description of drawings

In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or prior art. Obviously, in the following description The accompanying drawings are only some embodiments described in one or more embodiments of this specification. For those skilled in the art, other drawings can also be obtained according to these drawings without creative labor. .

Fig. 1 is a schematic flowchart of a method for generating a bill according to an embodiment of the present specification;

Fig. 2 is a schematic block diagram of a bill generation device according to an embodiment of the present specification;

Fig. 3 is a schematic block diagram of a bill generation device according to an embodiment of the present specification.

Detailed ways

One or more embodiments of this specification provide a bill generation method and device, which are used to integrate the bill generation process into one device, so as to achieve the effect of quickly and easily generating bills.

In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the following will describe the technical solutions in one or more embodiments of this specification in conjunction with the drawings in one or more embodiments of this specification The technical solution is clearly and completely described, and obviously, the described embodiments are only a part of the embodiments in this specification, rather than all the embodiments. Based on one or more embodiments in this specification, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of this document.

Fig. 1 is a schematic flowchart of a method for generating a bill according to an embodiment of this specification. As shown in Fig. 1, the method for generating a bill is applied to a billing platform, including:

S102. Retrieve relevant transaction data of the first user from at least one service node.

Among them, each service node can be used as a domain to record the relevant transaction data generated during the user's transaction process. Relevant transaction data may include any one or multiple transaction data that may be generated during different types of transactions, such as transaction amount, transaction times, transaction time, transaction user information, and the like. Each service node can store transaction data of at least one type of transaction, for example, service node a is used to store related transaction data in the transfer process, service node b is used to store related transaction data in the payment process, and service node c is used to store Relevant transaction data during the collection process, etc.

S104. Determine bill request information of the first user, and process relevant transaction data according to the bill request information to obtain first transaction data.

Wherein, the bill request information may include information such as a preset bill output rule, a request for generating one or more bills, and a bill storage address. According to different information carried in the bill request information, the relevant transaction data is processed in different ways, and the specific processing methods will be described in detail in the following embodiments.

S106. Generate a bill for the first user according to the first transaction data.

By adopting the technical solution of an embodiment of this specification, the bill generation process can be integrated on one device without relying on other platforms, thereby making the bill generation faster and more unified; in addition, it is precisely because of the unified bill generation link This makes the generation process of each bill a clear linear link, which makes it easy to troubleshoot various problems in the bill generation process and reduces the error probability of the bill generation process.

In one embodiment, before performing the above steps, relevant transaction data generated during the user's transaction needs to be recorded on each service node. Since each service node is divided according to different transaction types, each service node is used to store transaction data generated during different types of transactions. Record the relevant transaction data in the service node b, record the relevant transaction data in the storage collection process in the service node c, and so on.

In this embodiment, relevant transaction data may be recorded according to the transaction information of the user during the transaction. For example, if the transaction information is "User A transfers 100 yuan to user B", after analyzing the transaction data, it is known that during the transaction process, the payer is user A, the payee is user B, and the transaction amount is 100 yuan. The payer, payee, transaction amount and other data are recorded on the service node corresponding to the transfer transaction type.

After the relevant transaction data is recorded in each service node, when it is necessary to generate a bill for the user, the user's relevant transaction data can be obtained from at least one service node, and then the user's bill can be generated.

In one embodiment, after the relevant transaction data of the first user is retrieved from at least one service node, the relevant transaction data can be checked to determine whether the relevant transaction data is accurate, and after determining that the relevant transaction data is accurate, determine the second A user's bill request information (that is, execute S104).

In this embodiment, the relevant transaction data can be checked from various aspects, such as checking whether the transaction amount recorded in the relevant transaction data is accurate, whether the transaction time is accurate, whether the user information involved in the transaction is accurate, and whether the record format of the transaction data is accurate wait. When checking data such as transaction amount, transaction time, and user information involved in the transaction, the transaction information of the user's transaction can be obtained first, and the transaction information of the user's transaction can be stored in the designated storage area of the billing platform or in other in the server.

For example, the transaction information is "User A transfers 100 yuan to user B", and the relevant transaction data obtained from the service node is: the payer is user A, the payee is user B, and the transaction amount is 100 yuan. By analyzing the transaction information and comparing the transaction information with the obtained relevant transaction data, it is judged whether the obtained relevant transaction data is accurate. If there is at least one piece of relevant transaction data inconsistent with the transaction information, it can be determined that the acquired relevant transaction data is inaccurate.

In this embodiment, before generating the bill, by checking the correctness of the relevant transaction data recorded on the service node, it is ensured that the correct relevant transaction data is obtained, thereby ensuring that an accurate bill is generated for the user.

In one embodiment, the bill request information includes preset bill output rules. Therefore, when processing the relevant transaction data according to the bill request information, the relevant transaction data can be summarized first to obtain the data wide table corresponding to the relevant transaction data; Corresponding processing is performed on the relevant transaction data to obtain the first transaction data conforming to the bill output rule.

Among them, the bill output rules are used to constrain the data output format of various relevant transaction data. For example, the bill output rule includes the timestamp format corresponding to the transaction time, and the timestamp format is in the form of yyyyMMddHHmmss, where "yyyy" indicates the year, "MM" indicates the month, "dd" indicates the day, "HH" indicates the hour, and "mm" Indicates minutes, "ss" indicates seconds.

In this embodiment, the acquired related transaction data is processed according to the preset bill output rules to obtain the first transaction data, and then the user's bill is generated according to the first transaction data, so that all transactions in the generated user bill The data conforms to certain rules, rather than in a disorganized form, which is convenient for users to view and facilitates the management of transaction data by the billing platform.

In one embodiment, the bill generation links that need to be executed to generate various bills can be pre-configured, and each link node included in each bill generation link is configured with its own node attributes; wherein, the node attributes include user information, Information such as the operation type in the bill generation process, each bill generation link includes at least one link node.

In this embodiment, each link node is configurable, which enables the configuration personnel to configure each link node according to business requirements, so that the configuration personnel can simply, clearly and clearly manage the bill generation link. each link node. In addition, the bill generation process is node-based, so that each operation step only needs to focus on its own logic without considering the upper and lower environments. Therefore, for each individual link node, its own operation logic is simple and controllable, which is important for the overall scheduling In other words, each link node is independent of each other, so it is easy to implement distributed scheduling and maximize the use of system resources.

Based on the above embodiment, if the bill request information includes a request to generate multiple bills, when multiple bills are generated, it is first necessary to determine the bill generation links that need to be executed to generate each bill; and then determine the node attributes of each link node; Then compare the link nodes corresponding to each bill generation link to determine whether the node attributes of the link nodes corresponding to each bill generation link are the same; if there are node attributes in the link nodes corresponding to each bill generation link For the same link nodes, the link nodes with the same node attributes in each bill generation link are merged.

For example, the bill request information includes the request to generate user A's transaction detailed bill and summary bill, that is, two bills need to be generated at the same time, and because the two bills are different, the bill generation link that needs to be executed to generate each bill corresponds to the Link nodes are different. Specifically, the bill generation link of the transaction detailed bill includes a link node X, and the node attributes of the link node X are: the user information is user A, and the operation type is to obtain transaction detailed data. The bill generation link for summarizing bills includes link node X and link node Y. The node attributes of the link node X are: the user information is user A, the operation type is to obtain transaction detailed data, and the node attributes of link node Y are : The user information is user A, and the operation type is to summarize all detailed data. It can be seen that the bill generation links of the transaction detail bill and the summary bill contain the same link node X, so the link node X corresponding to the transaction detail bill and the link node X corresponding to the summary bill can be merged.

In this embodiment, after merging link nodes with the same node attribute, the output results of the merged link nodes in different bills are also merged. Following the above example, after merging the link node X corresponding to the transaction detailed bill and the link node X corresponding to the summary bill (that is, merging the operations of obtaining detailed data in the process of generating the two bills), output the transaction detail bill and When summarizing bills, only one detail data needs to be output, instead of outputting the detail data corresponding to the transaction detail bill and the detail data corresponding to the summary bill separately, thus greatly saving resources.

In this embodiment, by merging the link node X corresponding to the transaction detailed bill and the link node X corresponding to the summary bill, the operation corresponding to the link node with the same node attribute is only executed once, thereby avoiding the billing platform to Repeated execution of the same operation corresponding to the same link node greatly reduces system load and resource consumption.

In one embodiment, the bill request information includes a bill storage address. Therefore, after the first user's bill is generated, the bill can be output to the bill storage address, so that the first user can view the bill from the bill storage address.

In summary, certain embodiments of the subject matter have been described. Other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.

The above is the method for generating a bill provided by one or more embodiments of this specification. Based on the same idea, one or more embodiments of this specification further provide a device for generating a bill.

Fig. 2 is a schematic structural diagram of a bill generation device according to an embodiment of the present specification. As shown in Fig. 2, the bill generation device 200 is applied to a bill platform, including:

The retrieval module 210 retrieves the relevant transaction data of the first user from at least one service node; wherein, the service node is used to record the relevant transaction data generated during the user's transaction process;

The processing module 220 determines the bill request information of the first user, processes the relevant transaction data according to the bill request information, and obtains the first transaction data;

The generating module 230 generates a bill of the first user according to the first transaction data.

In one embodiment, the bill request information includes preset bill output rules;

The processing module 220 includes:

A summary unit, which summarizes relevant transaction data and obtains a wide data table corresponding to the relevant transaction data;

The processing unit processes the relevant transaction data in the wide data table according to the bill output rules, and obtains the first transaction data conforming to the bill output rules.

In one embodiment, the device 200 also includes:

The verification module checks the relevant transaction data after retrieving the relevant transaction data of the first user from at least one service node, so as to determine whether the relevant transaction data is accurate;

The processing module 220 includes:

The determining unit is configured to determine the bill request information of the first user after determining that the relevant transaction data is accurate.

In one embodiment, the billing request information includes a request to generate multiple bills;

The device 200 also includes:

The first determination module determines the bill generation links that need to be executed to generate each bill; each bill generation link includes at least one link node;

The second determination module determines the node attributes of each link node; wherein, the node attributes include at least one item of user information and operation types in the bill generation process;

The comparison module compares the link nodes corresponding to each bill generation link to determine whether the node attributes of the link nodes corresponding to each bill generation link are the same;

The merging module is configured to merge the link nodes corresponding to the bill generation links if the node attributes of the link nodes corresponding to the bill generation links are the same.

In one embodiment, the device 200 also includes:

Configuration module, before determining the bill generation links that need to be executed to generate each bill, configure the bill generation links that need to be executed to generate various bills respectively; and configure their own nodes for each link node included in the bill generation link Attributes.

In one embodiment, the bill request information also includes a bill storage address;

The device 200 also includes:

The output module outputs the bill to the bill storage address.

Using the device of an embodiment of this specification, the bill generation process can be integrated into one device without relying on other platforms, so that the generation of bills is faster and more unified; in addition, it is precisely because of the unified bill generation link , so that the generation process of each bill is a clear linear link, so that various problems in the bill generation process can be easily checked, and the error probability of the bill generation process can be reduced.

Those skilled in the art should understand that the above-mentioned bill generation device can be used to implement the above-mentioned bill generation method, and the detailed description thereof should be similar to the above-mentioned part of the method description, and will not be repeated here to avoid tediousness.

Based on the same idea, one or more embodiments of this specification further provide a bill generation device, as shown in FIG. 3 . The bill generation device may have relatively large differences due to different configurations or performances, and may include one or more processors 301 and memory 302, and one or more storage applications or data may be stored in the memory 302. Wherein, the storage 302 may be a short-term storage or a persistent storage. The application program stored in the memory 302 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the statement generation device. Furthermore, the processor 301 may be configured to communicate with the memory 302, and execute a series of computer-executable instructions in the memory 302 on the bill generation device. The bill generation device may also include one or more power sources 303, one or more wired or wireless network interfaces 304, one or more input and output interfaces 305, and one or more keyboards 306.

Specifically in this embodiment, the bill generation device includes a memory, and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and each A module may comprise a series of computer-executable instructions in a statement generating device, and configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

Retrieving the relevant transaction data of the first user from at least one service node; wherein the service node is used to record the relevant transaction data generated during the user's transaction process;

determining the bill request information of the first user, and processing the relevant transaction data according to the bill request information to obtain first transaction data;

A bill for the first user is generated according to the first transaction data.

Optionally, the bill request information includes preset bill output rules;

The computer-executable instructions, when executed, may also cause the processor to:

Summarizing the relevant transaction data to obtain a wide data table corresponding to the relevant transaction data;

For each of the relevant transaction data in the data wide table, corresponding processing is performed on each of the relevant transaction data according to the bill output rule, to obtain the first transaction data conforming to the bill output rule.

Optionally, when the computer-executable instructions are executed, the processor can also:

After the relevant transaction data of the first user is retrieved from at least one service node, the relevant transaction data is checked to determine whether the relevant transaction data is accurate;

After it is determined that the relevant transaction data is accurate, the bill request information of the first user is determined.

Optionally, the bill request information includes a request to generate multiple bills;

The computer-executable instructions, when executed, may also cause the processor to:

Determine the bill generation link that needs to be executed to generate each of the bills; each of the bill generation links includes at least one link node;

determining node attributes of each of the link nodes; wherein, the node attributes include at least one item of user information and operation types in the bill generation process;

comparing the link nodes corresponding to each of the bill generation links to determine whether the node attributes of the link nodes corresponding to each of the bill generation links are the same;

If yes, merge the link nodes corresponding to each of the bill generation links.

Optionally, when the computer-executable instructions are executed, the processor can also:

Before determining the bill generation links that need to be executed to generate each of the bills, configure the bill generation links that need to be executed to generate various bills; and configure each link node included in the bill generation link respective node properties.

Optionally, the bill request information also includes a bill storage address;

The computer-executable instructions, when executed, may also cause the processor to:

outputting the bill to the bill storage address.

One or more embodiments of the present specification also provide a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, the one or more programs include instructions, and when the instructions include multiple application programs When executed by an electronic device, the electronic device can be made to execute the above-mentioned bill generation method, and specifically used to execute:

Retrieving the relevant transaction data of the first user from at least one service node; wherein the service node is used to record the relevant transaction data generated during the user's transaction process;

determining the bill request information of the first user, and processing the relevant transaction data according to the bill request information to obtain first transaction data;

A bill for the first user is generated according to the first transaction data.

The systems, devices, modules, or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.

For the convenience of description, when describing the above devices, functions are divided into various units and described separately. Of course, when implementing one or more embodiments of this specification, the functions of each unit can be implemented in one or more software and/or hardware.

Those skilled in the art should understand that one or more embodiments of this specification may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, one or more embodiments of the present description may employ a computer program embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. The form of the product.

One or more embodiments of the present specification are described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present specification. It should be understood that each process and/or block in the flowchart and/or block diagrams, and a combination of processes and/or blocks in the flowchart and/or block diagrams can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer-readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of computer readable media.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

One or more embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, refer to part of the description of the method embodiment.

The above description is only one or more embodiments of this specification, and is not intended to limit this specification. For those skilled in the art, various modifications and changes may occur in one or more embodiments of this description. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included within the scope of claims of one or more embodiments of this specification.

Claims (10)

1. A bill generation method comprising:

retrieving relevant transaction data for a first user from a plurality of service nodes; each service node is used for recording the related transaction data generated by the user in different types of transaction processes;

determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;

generating a bill for the first user according to the first transaction data;

the processing the related transaction data according to the bill request information to obtain first transaction data includes: summarizing the related transaction data to obtain first transaction data;

the billing request information includes a request to generate a plurality of bills; generating a bill for the first user based on the first transaction data, comprising: determining bill generation links which need to be executed for generating each bill respectively, wherein each bill generation link comprises at least one link node; determining a node attribute of each of the link nodes; and if the link nodes with the same node attribute exist in the link nodes respectively corresponding to the bill generation links, merging the link nodes with the same node attribute, and merging the output results of the link nodes with the same node attribute.

2. The method of claim 1, the bill request information includes preset bill output rules;

the processing the related transaction data according to the bill request information to obtain first transaction data includes:

summarizing the related transaction data to obtain a data width table corresponding to the related transaction data;

and correspondingly processing each related transaction data in the data wide table according to the bill output rule to obtain the first transaction data according with the bill output rule.

3. The method of claim 1, after retrieving the relevant transaction data for the first user from the at least one service node, further comprising:

checking the related transaction data to judge whether the related transaction data is accurate or not;

the determining the billing request information of the first user comprises:

and when the related transaction data is determined to be accurate, determining the bill request information of the first user.

4. The method of claim 1, prior to determining a bill generation link to be executed for each of the bills, the method further comprising:

configuring a bill generation link which is required to be executed for generating various bills respectively; and configuring respective node attributes for each link node included in the bill generation link.

5. The method of claim 1, the billing request information further comprising a billing storage address;

the method further comprises the following steps:

and outputting the bill to the bill storage address.

6. A bill generation apparatus comprising:

the calling module is used for calling related transaction data of the first user from the plurality of service nodes; the service node is used for recording the related transaction data generated by the user in different types of transaction processes;

the processing module is used for determining bill request information of the first user and processing the related transaction data according to the bill request information to obtain first transaction data;

the generating module is used for generating a bill of the first user according to the first transaction data;

the processing module is used for summarizing the related transaction data to obtain first transaction data;

the generation module is used for determining a bill generation link which needs to be executed for generating each bill respectively, and each bill generation link comprises at least one link node; determining a node attribute of each link node; and if the link nodes with the same node attribute exist in the link nodes respectively corresponding to the bill generation links, merging the link nodes with the same node attribute, and merging the output results of the link nodes with the same node attribute.

7. The apparatus of claim 6, the bill request information comprising preset bill output rules;

the processing module comprises:

the summarizing unit summarizes the related transaction data to obtain a data width table corresponding to the related transaction data;

and the processing unit is used for correspondingly processing each related transaction data in the data wide table according to the bill output rule to obtain the first transaction data according with the bill output rule.

8. The apparatus of claim 6, further comprising:

the checking module is used for checking the related transaction data of the first user after the related transaction data of the first user is called from at least one service node so as to judge whether the related transaction data is accurate or not;

the processing module comprises:

and the first determining unit is used for determining the bill request information of the first user after the related transaction data are determined to be accurate.

9. A bill generation device comprising:

a processor; and

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

retrieving relevant transaction data for a first user from a plurality of service nodes; the service node is used for recording the related transaction data generated by the user in different types of transaction processes;

determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;

generating a bill for the first user according to the first transaction data;

the processing the related transaction data according to the bill request information to obtain first transaction data includes: summarizing the related transaction data to obtain first transaction data;

the billing request information includes a request to generate a plurality of bills; generating a bill for the first user based on the first transaction data, comprising: determining bill generation links which need to be executed for generating each bill respectively, wherein each bill generation link comprises at least one link node; determining a node attribute of each link node; if the link nodes with the same node attribute exist in the link nodes respectively corresponding to the bill generation links, the link nodes with the same node attribute are merged, and the output results of the link nodes with the same node attribute are merged.

10. A storage medium storing computer-executable instructions that, when executed, implement the following:

retrieving relevant transaction data for a first user from a plurality of service nodes; the service node is used for recording the related transaction data generated by the user in different types of transaction processes;

determining bill request information of the first user, and processing the related transaction data according to the bill request information to obtain first transaction data;

generating a bill for the first user according to the first transaction data;

the processing the related transaction data according to the bill request information to obtain first transaction data includes: summarizing the related transaction data to obtain first transaction data;

the billing request information includes a request to generate a plurality of bills; generating a bill for the first user based on the first transaction data, comprising: determining bill generation links which need to be executed for generating each bill respectively, wherein each bill generation link comprises at least one link node; determining a node attribute of each of the link nodes; if the link nodes with the same node attribute exist in the link nodes respectively corresponding to the bill generation links, the link nodes with the same node attribute are merged, and the output results of the link nodes with the same node attribute are merged.

Images