Bill Management Method, System, Device and Storage Medium Based on a Relationship Tree

Abstract

The present invention provides a bill management method, system, device and storage medium based on a relationship tree. The method includes: configuring a regional supplier as a parent node, with current child nodes and historical child nodes hanging under the parent node, and configuring a service terminal as a current child node; generating bill information based on the relationship tree path and amount when the service terminal generates a bill; when the current child node is transferred to another parent node, the current child node is converted into a historical child node under the current parent node, and the bill information of the current child node is used as the bill information of the historical child node of the current parent node; the parent node summarizes and encrypts the bill information to obtain the parent node bill information, and the parent node bill information at least includes the relationship tree path and amount of each bill; and performing settlement according to the bill information of the parent node. The present invention can avoid manual reconciliation by business personnel, automatically handle the situation of supplier relationship adjustment, and ensure data consistency and integrity.

Description

Background Art

[0002] Traditional MICE systems rely on offline business Excel to maintain supplier reconciliation data, and then manually enter this data into the system. This method is relatively inefficient, increasing the workload of MICE business personnel, and manual operations are prone to errors. At the same time, it increases the workload of auditors in the later stage. After the modification, the supplier information is incorporated into the MICE system, and payment orders are automatically generated based on the settlement balance sheet. The business makes payments to suppliers by associating payment documents, reducing the input and review costs of orders. While enhancing data transparency, it also strengthens the consistency between MICE internal data and supplier data.

[0003] Moreover, in actual operations, changes in the relationships between regional suppliers and between regional suppliers and subordinate service terminals may also occur. In such cases, it is difficult to settle accounts payable and accounts receivable, and it is very easy to cause confusion in the bill relationships.

[0004] Therefore, the present invention provides a bill management method, system, device, and storage medium based on a relationship tree. Summary of the Invention

[0005] Aiming at the problems in the prior art, the purpose of the present invention is to provide a bill management method, system, device, and storage medium based on a relationship tree, which overcomes the difficulties of the prior art, can avoid manual account reconciliation by business personnel, automatically handle situations of supplier relationship adjustments, and ensure data consistency and integrity.

[0006] An embodiment of the present invention provides a bill management method based on a relationship tree, including the following steps:

[0007] S110: Configure regional suppliers as parent nodes, with the current child nodes and historical child nodes hanging under the parent nodes, and configure service terminals as current child nodes.

[0008] S120: Generate a bill information based on the relationship tree path and amount when generating a bill for the service terminal.

[0009] S130: When the current child node is transferred from the current parent node to another parent node, the current child node is transformed into a historical child node under the current parent node, and the bill information of the current child node is used as the bill information of the historical child node of the current parent node.

[0010] S140: The parent node summarizes the bill information of the current child nodes and historical child nodes hanging under it and encrypts it to obtain the parent node bill information, which at least includes the relationship tree path and amount of each bill. And

[0011] S150: Settle accounts according to the bill information of the parent node.

[0012] Preferably, in the step S110, it further includes:

[0013] Generate a shared blockchain based on all the parent nodes, and each parent node establishes a private blockchain respectively. The private blockchain includes at least a private data area and a public data area, and the public data area is only accessible to the shared blockchain.

[0014] Preferably, in the step S120, it includes:

[0015] S121. Generate a bill information based on the relationship tree path and amount when the service terminal generates a bill.

[0016] S122. Record the bill information in the public data area of the private blockchain of the parent node to generate a common data block.

[0017] S123. Obtain the bill information based on the smart contract and publish it. And

[0018] S124. When the public data areas of other network operators meeting a preset ratio confirm the bill information, add the common data block to the shared blockchain.

[0019] Preferably, in the step S130, it includes:

[0020] S131. When the current child node is transferred from the current parent node to other parent nodes, the current child node is transformed into a historical child node under the current parent node.

[0021] S132. Take the bill information generated by the current child node under the current parent node as the bill information of the historical child node of the current parent node.

[0022] S133. Record the bill information of the historical child node of the current parent node in the public data area of the private blockchain of the parent node to generate a common data block.

[0023] S134. Obtain the bill information of the historical child node of the current parent node based on the smart contract and publish it. And

[0024] S135. When the public data areas of other network operators meeting a preset ratio confirm the bill information of the historical child node of the current parent node, add the common data block to the shared blockchain.

[0025] Preferably, the step S140 further includes the following steps: Generate a common data block from the parent node bill information and write it into the shared blockchain.

[0026] Preferably, the step S150 includes the following steps:

[0027] Settle the payment to the preset account of the parent node according to the common data blocks in the shared blockchain.

[0028] Preferably, the step S150 includes the following steps:

[0029] S151. Perform a payment operation on at least one of the bills based on the relationship tree path and amount in the parent node bill information, and the payment operation includes verification information based on the relationship tree path and amount.

[0030] S152. After the parent node receives the verification information of the relationship tree path, traverse the bill information of the current child nodes and historical child nodes under the parent node to find whether there is bill information that meets the verification information. If so, execute step S153; if not, execute step S154.

[0031] S153. Make a payment to the preset account of the parent node based on the verification information. And

[0032] S154. Terminate the payment operation.

[0033] Preferably, after the step S153, the following steps are further included:

[0034] S155. Delete the bill information from the current child nodes and historical child nodes.

[0035] An embodiment of the present invention further provides a bill management system based on a relationship tree for implementing the above-mentioned bill management method based on a relationship tree. The bill management system based on a relationship tree includes:

[0036] A node configuration module that configures regional suppliers as parent nodes, with current child nodes and historical child nodes hanging under the parent nodes, and configures service terminals as current child nodes.

[0037] A bill information module that generates a bill information based on the relationship tree path and amount when the service terminal generates a bill.

[0038] A node conversion module. When the current child node is transferred from the current parent node to other parent nodes, the current child node is converted into a historical child node under the current parent node, and the bill information of the current child node is used as the bill information of the historical child node of the current parent node.

[0039] A bill summary module that summarizes and encrypts the bill information of the current child nodes and historical child nodes hanging under the parent node to obtain parent node bill information, and the parent node bill information includes at least the relationship tree path and amount of each bill. And

[0040] The bill settlement module performs settlement based on the bill information of the parent node.

[0041] An embodiment of the present invention also provides a bill management device based on a relationship tree, including:

[0042] A processor.

[0043] A memory, in which executable instructions of the processor are stored.

[0044] Wherein, the processor is configured to execute the steps of the above-mentioned bill management method based on a relationship tree by executing the executable instructions.

[0045] An embodiment of the present invention also provides a computer-readable storage medium for storing a program, and when the program is executed, it implements the steps of the above-mentioned bill management method based on a relationship tree.

[0046] The purpose of the present invention is to provide a bill management method, system, device and storage medium based on a relationship tree, which can avoid manual reconciliation by business personnel, automatically handle the situation of supplier relationship adjustment, and ensure data consistency and integrity. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] By reading the detailed description of the non-limiting embodiments with reference to the following drawings, other features, objects and advantages of the present invention will become more obvious.

[0048] Figure 1 is a flowchart of the bill management method based on a relationship tree of the present invention.

[0049] Figure 2 is a schematic diagram of the modules of the bill management system based on a relationship tree of the present invention.

[0050] Figure 3 is a schematic diagram of the structure of the bill management device based on a relationship tree of the present invention.

[0051] Figure 4 is a schematic diagram of the structure of the computer-readable storage medium according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0052] The following uses specific specific examples to illustrate the implementation manners of the present application. Those skilled in the art can easily understand other advantages and effects of the present application from the content disclosed in the present application. The present application can also be implemented or applied through other different specific implementation manners. Various details in the present application can also be modified or changed according to different viewpoints and application systems without departing from the spirit of the present application. It should be noted that, without conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0053] The following will describe the embodiments of the present application in detail with reference to the accompanying drawings, so that those skilled in the art to which the present application pertains can easily implement it. The present application can be embodied in various different forms and is not limited to the embodiments described herein.

[0054] In the description of the present application, the reference to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. means that the specific features, structures, materials, or characteristics represented by the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials, or characteristics represented can be combined in a suitable manner in any one or more embodiments or examples. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples represented in the present application and the features of different embodiments or examples.

[0055] In addition, the terms "first" and "second" are only used for illustrative purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "a plurality" is two or more, unless otherwise specifically defined.

[0056] To clearly illustrate the present application, devices irrelevant to the description are omitted, and the same or similar components throughout the specification are given the same reference numerals.

[0057] Throughout the specification, when it is said that a device is "connected" to another device, this includes not only the case of "direct connection", but also the case of "indirect connection" with other elements placed therebetween. In addition, when it is said that a certain device "includes" a certain component, unless there is a particularly contrary record, it does not exclude other components, but means that other components may also be included.

[0058] When it is said that a device is "on" another device, this may be directly on the other device, but there may also be other devices therebetween. When it is said that a device is "directly" "on" another device, there are no other devices therebetween.

[0059] Although in some instances the terms first, second, etc. are used herein to denote various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first interface and a second interface, etc. are indicated. Furthermore, as used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising", "including" indicate the presence of the features, steps, operations, elements, components, items, kinds, and / or groups, but do not preclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or" and "and / or" used herein are to be construed as inclusive, or meaning any one or any combination. Thus, "A, B, or C" or "A, B, and / or C" means "any of the following: A; B; C; A and B; A and C; B and C; A, B, and C". An exception to this definition occurs only when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0060] The technical terms used herein are only for referring to specific embodiments and are not intended to limit the present application. The singular forms used herein also include the plural forms as long as the statements do not clearly indicate the contrary meaning. The meaning of "including" used in the specification is to embody specific characteristics, regions, integers, steps, operations, elements, and / or components, and does not exclude the existence or addition of other characteristics, regions, integers, steps, operations, elements, and / or components.

[0061] Although not defined differently, including the technical terms and scientific terms used herein, all terms have the same meaning as generally understood by those skilled in the technical field to which the present application pertains. Terms defined in commonly used dictionaries are additionally interpreted as having a meaning consistent with the relevant technical literature and the content currently presented. As long as they are not defined, they should not be over-interpreted as ideal or overly formulaic meanings.

[0062] Figure 1 is a flowchart of the bill management method based on a relationship tree of the present invention. As Figure 1 shown, an embodiment of the present invention provides a bill management method based on a relationship tree, including the following steps:

[0063] S110. Configure the regional supplier as the parent node, with the current child node and the historical child node hanging under the parent node, and configure the service terminal as the current child node;

[0064] S120. Generate a bill information based on the relationship tree path and amount when the bill is generated by the service terminal;

[0065] S130. If the current child node is transferred from the current parent node to another parent node, the current child node is transformed into a historical child node under the current parent node, and the bill information of the current child node is used as the bill information of the historical child node of the current parent node;

[0066] S140. The parent node aggregates the bill information of the current child nodes and historical child nodes hanging under it and encrypts it to obtain the parent node bill information, and the parent node bill information includes at least the relationship tree path and amount of each bill; and

[0067] S150. Settle accounts according to the bill information of the parent node.

[0068] In a preferred embodiment, in step S110, it further includes:

[0069] Generate a shared blockchain based on all parent nodes, and each parent node establishes a private blockchain by itself. The private blockchain includes at least a private data area and a public data area, and the public data area is only accessible to the shared blockchain.

[0070] In this embodiment, the blockchain is a term in the field of information technology. Essentially, it is a shared database. The data or information stored in it has characteristics such as "non-forgery", "traceability throughout the process", "traceable", "open and transparent", and "collective maintenance". Based on these characteristics, blockchain technology has laid a solid foundation of "trust", created a reliable "cooperation" mechanism, and has broad application prospects. The blockchain is a distributed shared ledger and database, with characteristics such as decentralization, immutability, traceability throughout the process, traceability, collective maintenance, and open and transparency. These characteristics ensure the "honesty" and "transparency" of the blockchain and lay a foundation for creating trust in the blockchain. The rich application scenarios of the blockchain are basically based on the fact that the blockchain can solve the problem of information asymmetry and achieve collaborative trust and consistent actions among multiple parties. The blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithm.

[0071] In a preferred embodiment, in step S120, it includes:

[0072] S121. Generate a bill information based on the relationship tree path and amount when the service terminal generates a bill;

[0073] S122. Record the bill information in the public data area of the private blockchain of the parent node to generate a common data block;

[0074] S123. Obtain the bill information based on the smart contract and publish it; and

[0075] S124. When the billing information of the public data area of other network operators that meet the preset ratio is confirmed, the common data block is added to the shared blockchain.

[0076] In a preferred embodiment, in step S130, it includes:

[0077] S131. When the current child node is transferred from the current parent node to another parent node, the current child node is transformed into a historical child node under the current parent node;

[0078] S132. The billing information generated by the current child node under the current parent node is used as the billing information of the historical child node of the current parent node;

[0079] S133. The billing information of the historical child node of the current parent node is recorded in the public data area of the private blockchain of the parent node to generate a common data block;

[0080] S134. Obtain the billing information of the historical child node of the current parent node based on the smart contract and publish it; and

[0081] S135. When the billing information of the historical child node of the current parent node is confirmed by the public data areas of other network operators that meet the preset ratio, the common data block is added to the shared blockchain.

[0082] In a preferred embodiment, step S140 further includes the following steps: Generate a common data block from the parent node billing information and write it into the shared blockchain.

[0083] In a preferred embodiment, step S150 includes the following steps:

[0084] Settle accounts to the preset account of the parent node according to the common data block in the shared blockchain.

[0085] In a preferred embodiment, step S150 includes the following steps:

[0086] S151. Perform a payment operation on at least one bill based on the relationship tree path and amount in the parent node billing information, and the payment operation includes verification information based on the relationship tree path and amount;

[0087] S152. After the parent node receives the verification information of the relationship tree path, traverse the billing information of the current child nodes and historical child nodes under the parent node to find whether there is billing information that meets the verification information. If so, execute step S153; if not, execute step S154;

[0088] S153. Make a payment to the preset account of the parent node based on the verification information; and

[0089] S154. Terminate the payment operation.

[0090] In a preferred embodiment, after step S153, the following steps are further included:

[0091] S155. Delete the bill information from the current child node and the historical child node.

[0092] The specific implementation manner of the present invention is as follows:

[0093] Configure regional suppliers (for example, institutions that integrate tourism resources such as tourism resource providers in a large region, and each regional supplier has multiple subordinate service terminals) as parent nodes, with the current child node and the historical child node hanging under the parent node. Configure service terminals (for example, institutions that provide terminal services such as hotels and stations) as current child nodes. Generate a shared blockchain based on all parent nodes. Each parent node independently establishes a private blockchain, and the private blockchain at least includes a private data area and a public data area. The public data area is only accessible to the shared blockchain.

[0094] Generate a bill information based on the relationship tree path and amount when the service terminal generates a bill, record the bill information in the public data area of the private blockchain of the parent node, generate a common data block, obtain the bill information based on the smart contract and publish it. When the public data areas of other network operators meeting a preset ratio confirm the bill information, add the common data block to the shared blockchain.

[0095] When the current child node is transferred from the current parent node to other parent nodes, the current child node is transformed into a historical child node under the current parent node. Take the bill information generated by the current child node under the current parent node as the bill information of the historical child node of the current parent node. After using the present invention, no matter how the attribution of the service terminals among regional suppliers is adjusted intensively, the bill can be accurately traced, and the authenticity of the bill can be supervised in combination with the blockchain technology, avoiding the situation of bill loss or tampering after the service terminal migrates. Record the bill information of the historical child node of the current parent node in the public data area of the private blockchain of the parent node, generate a common data block. Obtain the bill information of the historical child node of the current parent node based on the smart contract and publish it. When the public data areas of other network operators meeting a preset ratio confirm the bill information of the historical child node of the current parent node, add the common data block to the shared blockchain.

[0096] The parent node summarizes and encrypts the bill information of the hanging current child node and historical child node to obtain the parent node bill information. The parent node bill information at least includes the relationship tree path and amount of each bill. Generate a common data block with the parent node bill information and write it into the shared blockchain.

[0097] The parent node's preset account is settled based on the shared data blocks in the shared blockchain. A payment operation is performed on at least one bill based on the relationship tree path and amount in the parent node's bill information, and the payment operation includes verification information based on the relationship tree path and amount; after the parent node receives the verification information of the relationship tree path, it traverses the bill information of the current child node and the historical child node under the parent node to find out whether there is bill information that meets the verification information. If so, it pays the parent node's preset account based on the verification information, and deletes the bill information from the current child node and the historical child node; if not, the payment operation is terminated.

[0098] The present invention can solve the problem that payment information cannot be automatically generated in the existing MICE system, eliminating the previous operation steps of relying on business personnel to manually create orders. By entering the supplier settlement data into the system, specific order details, payment amount and status can be quickly viewed, thereby ensuring data consistency and integrity.

[0099] The present invention helps to implement the settlement data of MICE suppliers into the system. It can also upload the supplier bill data maintained by the offline Excel of the business to the system. The uploaded data is strictly verified according to the standard rules during the system upload process, and the supplier's status and whitelist content are further judged. The total amount of the detailed accounting bill that meets the requirements is calculated, and a payment slip is generated; when the uploaded bill is confirmed, the payment application is submitted, and the payment is made after the financial review is completed. The business of the present invention adopts the offline Excel maintenance of supplier bill data method, and the probability of omission and error of manually maintained data is relatively high; changing to the system to generate payment slips ensures the accuracy and completeness of the settlement data to a certain extent. By importing the supplier's order into the system, the salesperson can quickly enter and query the order details and payment amount, reducing the manpower of manual entry and review, and achieving cost reduction and efficiency improvement to a certain extent. In addition, the processing capacity of the MICE system is improved, the system function is improved, and the system closed loop is promoted.

[0100] In a variation, the supplier information is maintained in the MICE system; the settlement balance is uploaded, and the order is created after verifying the supplier information and whitelist. The total payment amount of the supplier order = the cumulative payment amount of the details. When the uploaded supplier is Ctrip air tickets, train tickets, vacations, and car rentals, the system has automatically updated the details; according to the supplier ID in the settlement balance, the items / costs are entered into different supplier orders to generate details; the details are associated with the order ID, and the details correspond to the payment amount and payment status (the order status is: confirmed, canceled, completed); finally, the financial unit conducts batch review of payment orders.

[0101] Figure 2 2 is a module diagram of the bill management system based on the relationship tree of the present invention. As shown in FIG2 , the bill management system 5 based on the relationship tree of the present invention includes:

[0102] The node configuration module 51 configures the regional supplier as the parent node, with the current child node and the historical child node hanging under the parent node, and configures the service terminal as the current child node.

[0103] The bill information module 52 generates a bill information based on the relationship tree path and amount when the service terminal generates a bill.

[0104] The node conversion module 53, when the current child node is transferred from the current parent node to other parent nodes, the current child node is converted into a historical child node under the current parent node, and the bill information of the current child node is used as the bill information of the historical child node of the current parent node.

[0105] The bill summary module 54 summarizes and encrypts the bill information of the current child node and the historical child node hanging under the parent node to obtain the parent node bill information, and the parent node bill information includes at least the relationship tree path and amount of each bill.

[0106] The bill settlement module 55 settles accounts according to the bill information of the parent node.

[0107] In a preferred embodiment, the node configuration module 51 generates a shared blockchain based on all parent nodes, and each parent node establishes a private blockchain respectively. The private blockchain includes at least a private data area and a public data area, and the public data area is only accessible to the shared blockchain.

[0108] In a preferred embodiment, the bill information module 52 generates a bill information based on the relationship tree path and amount when the service terminal generates a bill, records the bill information in the public data area of the private blockchain of the parent node to generate a common data block, obtains the bill information based on the smart contract and publishes it. When the public data areas of other network operators meeting a preset ratio confirm the bill information, the common data block is added to the shared blockchain.

[0109] In a preferred embodiment, the node conversion module 53 is configured such that when the current child node is transferred from the current parent node to other parent nodes, the current child node is converted into a historical child node under the current parent node; the bill information generated by the current child node under the current parent node is used as the bill information of the historical child node of the current parent node; the bill information of the historical child node of the current parent node is recorded in the public data area of the private blockchain of the parent node to generate a common data block; obtains the bill information of the historical child node of the current parent node based on the smart contract and publishes it; when the public data areas of other network operators meeting a preset ratio confirm the bill information of the historical child node of the current parent node, the common data block is added to the shared blockchain.

[0110] In a preferred embodiment, the bill settlement module 55 settles accounts with the preset account of the parent node according to the common data blocks in the shared blockchain.

[0111] In a preferred embodiment, the bill settlement module 55 performs a payment operation on at least one bill based on the relationship tree path and amount in the parent node bill information. The payment operation includes verification information based on the relationship tree path and amount. After receiving the verification information of the relationship tree path, the parent node traverses the bill information of the current child nodes and historical child nodes under the parent node to find out whether there is bill information that meets the verification information. If so, it makes a payment to the preset account of the parent node based on the verification information and deletes the bill information from the current child nodes and historical child nodes. If not, the payment operation is terminated.

[0112] The bill management system based on the relationship tree of the present invention can avoid manual reconciliation by business personnel, automatically handle the situation of supplier relationship adjustment, and ensure data consistency and integrity.

[0113] The above embodiments are only preferred examples of the present invention and are not used to limit the present invention. Any equivalent substitution, modification, and change made within the principle of the present invention are within the protection scope of the present invention.

[0114] An embodiment of the present invention also provides a bill management device based on a relationship tree, including a processor and a memory, in which executable instructions of the processor are stored. Among them, the processor is configured to execute the steps of the bill management method based on the relationship tree by executing the executable instructions.

[0115] As shown above, the bill management system based on the relationship tree of the present invention can avoid manual reconciliation by business personnel, automatically handle the situation of supplier relationship adjustment, and ensure data consistency and integrity.

[0116] Those skilled in the art can understand that various aspects of the present invention can be implemented as a system, a method, or a program product. Therefore, various aspects of the present invention can be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which can be collectively referred to as "circuit", "module", or "platform" here.

[0117] Figure 3 is a schematic structural diagram of the bill management device based on the relationship tree of the present invention. The following will refer to Figure 3 to describe the electronic device 600 according to this embodiment of the present invention. Figure 3 The electronic device 600 shown is only an example and should not bring any limitations to the functions and usage scope of the embodiments of the present invention.

[0118] Such as Figure 3As shown, the electronic device 600 is presented in the form of a general-purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different platform components (including the storage unit 620 and the processing unit 610), a display unit 640, etc.

[0119] Among them, the storage unit stores program code, and the program code can be executed by the processing unit 610, so that the processing unit 610 executes the steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription transfer processing method part of this specification. For example, the processing unit 610 can execute steps as shown in Figure 1 the figure.

[0120] The storage unit 620 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 6201 and / or a cache storage unit 6202, and may further include a read-only storage unit (ROM) 6203.

[0121] The storage unit 620 may also include a program / utilities 6204 having a set (at least one) of program modules 6205. Such program modules 6205 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment.

[0122] The bus 630 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any bus structure in a variety of bus structures.

[0123] The electronic device 600 can also communicate with one or more external devices 700 (such as a keyboard, a pointing device, a Bluetooth device, etc.), can also communicate with one or more devices that enable a user to interact with the electronic device 600, and / or communicate with any device that enables the electronic device 600 to communicate with one or more other computing devices (such as a router, a modem, etc.). Such communication can be carried out through an input / output (I / O) interface 650. And, the electronic device 600 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 660. The network adapter 660 can communicate with other modules of the electronic device 600 through the bus 630. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms, etc.

[0124] An embodiment of the present invention also provides a computer-readable storage medium for storing a program, and the steps of a bill management method based on a relationship tree are implemented when the program is executed. In some possible implementation manners, various aspects of the present invention can also be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription circulation processing method part of this specification.

[0125] As shown above, the bill management system based on a relationship tree of the present invention in this embodiment can avoid manual reconciliation by business personnel, automatically handle the situation of supplier relationship adjustment, and ensure data consistency and integrity.

[0126] Figure 4 It is a schematic structural diagram of the computer-readable storage medium of the present invention. Refer to Figure 4 As shown, a program product 800 for implementing the above method according to an embodiment of the present invention is described. It can be a portable compact disc read-only memory (CD-ROM) and includes program code, and can run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited to this. In this document, a readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, apparatus, or device.

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

[0128] A computer-readable storage medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The readable storage medium may also be any readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0129] The program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and also including conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's device, executed as a stand-alone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., by using an Internet service provider to connect through the Internet).

[0130] In summary, the object of the present invention is to provide a bill management method, system, device, and storage medium based on a relationship tree, which can avoid manual reconciliation by business personnel, automatically handle the situation of supplier relationship adjustment, and ensure data consistency and integrity.

[0131] The above content is a further detailed description of the present invention in combination with specific preferred embodiments, and it cannot be determined that the specific implementation of the present invention is only limited to these descriptions. For those of ordinary skill in the technical field to which the present invention pertains, without departing from the concept of the present invention, several simple deductions or substitutions can be made, and all should be regarded as belonging to the protection scope of the present invention.

Claims

1. A bill management method based on a relationship tree, characterized in that, it includes the following steps: S110. Configure regional suppliers as parent nodes, with current child nodes and historical child nodes hanging under each parent node. Configure service terminals as current child nodes. Generate a shared blockchain based on all the parent nodes, and each parent node establishes a private blockchain respectively. The private blockchain at least includes a private data area and a public data area, and the public data area is only accessible to the shared blockchain; S120. Generate a bill information based on the relationship tree path and amount when the bill is generated by the service terminal; Record the bill information in the public data area of the private blockchain of the parent node to generate a common data block; Obtain the bill information based on a smart contract and publish it; and when the public data areas of other network operators meeting a preset ratio confirm the bill information, add the common data block to the shared blockchain; S130. When the current child node is transferred from the current parent node to other parent nodes, the current child node is transformed into a historical child node under the current parent node; regard the bill information generated by the current child node under the current parent node as the bill information of the historical child node of the current parent node; Record the bill information of the historical child node of the current parent node in the public data area of the private blockchain of the parent node to generate a common data block; Obtain the bill information of the historical child node of the current parent node based on a smart contract and publish it; when the public data areas of other network operators meeting a preset ratio confirm the bill information of the historical child node of the current parent node, add the common data block to the shared blockchain; S140. The parent node summarizes the bill information of the current child node and historical child node hanging under it and encrypts it to obtain parent node bill information, and the parent node bill information at least includes the relationship tree path and amount of each bill; and S150. Settle to a preset account of the parent node according to the common data block in the shared blockchain.

2. The bill management method based on a relationship tree according to claim 1, characterized in that, the step S150 includes the following steps: S151. Perform a payment operation on at least one bill based on the relationship tree path and amount in the parent node bill information, and the payment operation includes verification information based on the relationship tree path and amount; S152. After the parent node receives the verification information of the relationship tree path, traverse the bill information of the current child node and historical child node hanging under the parent node to find whether there is bill information that meets the verification information. If so, execute step S153; if not, execute step S154; S153. Make a payment to the preset account of the parent node based on the verification information; and S154. Terminate the payment operation.

3. The bill management method based on a relationship tree according to claim 2, characterized in that, after the step S153, the following steps are further included: S155. Delete the bill information from the current child node and historical child node.

4. A bill management system based on a relationship tree for implementing the bill management method based on a relationship tree described in claim 1, characterized in that, it includes: A node configuration module that configures a regional supplier as a parent node, with the current child node and historical child nodes hanging under the parent node, configures a service terminal as the current child node, generates a shared blockchain based on all the parent nodes, and each parent node establishes a private blockchain respectively. The private blockchain at least includes a private data area and a public data area, and the public data area is only accessible to the shared blockchain; A bill information module that generates a bill information based on the relationship tree path and amount when the bill is generated by the service terminal; Record the bill information in the public data area of the private blockchain of the parent node to generate a common data block; Obtain the bill information based on a smart contract and publish it; and when the public data areas of other network operators that meet a preset ratio confirm the bill information, add the common data block to the shared blockchain; A node conversion module that, when the current child node is transferred from the current parent node to other parent nodes, the current child node is converted into a historical child node under the current parent node; and takes the bill information generated by the current child node under the current parent node as the bill information of the historical child node of the current parent node; Record the bill information of the historical child node of the current parent node in the public data area of the private blockchain of the parent node to generate a common data block; Obtain the bill information of the historical child node of the current parent node based on a smart contract and publish it; when the public data areas of other network operators that meet a preset ratio confirm the bill information of the historical child node of the current parent node, add the common data block to the shared blockchain; A bill summary module that summarizes and encrypts the bill information of the current child node and historical child nodes hanging under the parent node to obtain parent node bill information, and the parent node bill information at least includes the relationship tree path and amount of each bill; and A bill settlement module that settles to a preset account of the parent node according to the common data block in the shared blockchain.

5. A bill management device based on a relationship tree, characterized in that, it includes: A processor; A memory that stores executable instructions of the processor; wherein, the processor is configured to execute the steps of the bill management method based on a relationship tree described in any one of claims 1 to 3 by executing the executable instructions.

6. A computer-readable storage medium for storing a program, characterized in that, when the program is executed by a processor, it implements the steps of the bill management method based on a relationship tree described in any one of claims 1 to 3.

Images