Account reconciliation method, system, device and storage medium based on data comparison

Abstract

The present invention provides a reconciliation method, system, device and storage medium based on data comparison, the method comprising: a payee account generates a payment information and a settlement information based on an order information; the payment information is sent to a payment database, and the bill code of the payment information has a mapping relationship with a non-fungible token and is added to the bill code table of the payment database; the settlement information is sent to the settlement database and sent to the payee account; when the payer account selects at least one settlement information for combined payment, the digital identity conversion information of the non-fungible tokens of all settlement information is embedded in the payment operation and fed back to the payee account; the payee account searches for the corresponding bill code in the bill code according to all the non-fungible tokens received in the payment operation, and generates a set of bill codes corresponding to the payment operation. The present invention can improve the accuracy of bills, enhance the confidentiality of financial processes, reduce manual intervention, and speed up financial processes.

Description

Background Art

[0002] After a customer orders a product, they will be given a bill for verification and settlement. The bill data comes from the order data, which may be different from the payment data. As the number of products booked increases, the scenarios become more and more complex. If a new scenario is not compatible or a process in the entire link is interrupted, the bill amount will be incorrect, which will lead to customer complaints or company losses.

[0003] Especially in current business cooperation, the financial personnel of many companies will combine and pay several bills within a certain period of time according to their own habits. If the amounts of many of the bills are the same (or the unit prices in the bills are the same), the payee will not know which bill the other party is paying, which will require subsequent manual intervention for reconciliation, resulting in additional labor costs and slow financial processes.

[0004] Therefore, the present invention provides a reconciliation method, system, device and storage medium based on data comparison. Summary of the invention

[0005] In response to the problems in the prior art, the purpose of the present invention is to provide a reconciliation method, system, device and storage medium based on data comparison, which overcomes the difficulties of the prior art, can improve the accuracy of bills, enhance the confidentiality of financial processes, reduce manual intervention, and speed up financial processes.

[0006] An embodiment of the present invention provides a reconciliation method based on data comparison, comprising the following steps:

[0007] S110. The payee account generates a payment information and a settlement information based on an order information, wherein the settlement information includes a unique non-fungible token, and the payment information includes a unique billing code having a mapping relationship with the non-fungible token;

[0008] S120, the payment information is sent to a payment database, and the billing code of the payment information has a mapping relationship with the non-fungible token and is added to the billing code table of the payment database;

[0009] S130, the settlement information is sent to the settlement database and to the payer's account;

[0010] S140. When the payer account selects at least one of the settlement information for combined payment, the digital identity conversion information of the non-fungible tokens of all the settlement information is embedded in the payment operation and fed back to the payee account;

[0011] S150. The payee account searches for a corresponding billing code in the billing code according to all the non-fungible tokens received in the payment operation, and generates a set of billing codes corresponding to the payment operation.

[0012] Preferably, the step S110 includes:

[0013] S111. The payee account generates a non-fungible token upload instruction according to order information, and stores the non-fungible token in the corresponding blockchain according to the non-fungible token upload instruction, and the digital identity of the ownership of the non-fungible token is the payee account;

[0014] S112. The payee account generates a unique billing code that has a mapping relationship with the non-fungible token based on the order information.

[0015] Preferably, the step S111 includes:

[0016] The payee account generates a non-fungible token upload instruction, an encrypted private key and an encrypted public key according to order information, and stores the non-fungible token and the encrypted private key in the corresponding blockchain according to the non-fungible token upload instruction.

[0017] Preferably, the step S112 includes:

[0018] The payee account generates a unique billing code that is mapped to the non-fungible token based on the order information, and encrypts the billing code using an encrypted public key and saves it.

[0019] Preferably, the step S130 includes:

[0020] S131, the settlement information is sent to a settlement database;

[0021] S132. When the settlement information is forwarded to the payer's account, the non-fungible token and the encrypted private key are stored in the blockchain of the payer's account, and the digital identity of the ownership of the non-fungible token is converted to the payer's account.

[0022] Preferably, the step S140 includes: when the payer account selects at least one of the settlement information for combined payment, the digital identity of the non-fungible token of all the settlement information to be paid is converted into the payee account, and the encrypted private key is sent to the payee account.

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

[0024] S151. The payee account searches for a corresponding bill code in the bill code according to the non-fungible token and the encrypted private key in the payment operation;

[0025] S152, decrypting the bill code;

[0026] S153. Find the bill code corresponding to the non-fungible token;

[0027] S154. Collect the billing code corresponding to each of the non-fungible tokens, and generate a set of billing codes corresponding to the payment operation for settlement.

[0028] An embodiment of the present invention further provides a reconciliation system based on data comparison, which is used to implement the above-mentioned reconciliation method based on data comparison. The reconciliation system based on data comparison includes:

[0029] An information generation module, wherein the payee account generates a payment information and a settlement information based on an order information, wherein the settlement information includes a unique non-fungible token, and the payment information includes a unique billing code having a mapping relationship with the non-fungible token;

[0030] Payment data module, the payment information is sent to a payment database, and the billing code of the payment information has a mapping relationship with the non-fungible token and is added to the billing code table of the payment database;

[0031] A settlement data module, wherein the settlement information is sent to a settlement database and to a payer's account;

[0032] A token feedback module, when the payer account selects at least one of the settlement information for combined payment, embeds the digital identity conversion information of the non-fungible tokens of all the settlement information into the payment operation and feeds it back to the payee account;

[0033] The bill reconciliation module, the payee account searches the bill code for the corresponding bill code according to all the non-fungible tokens received in the payment operation, and generates a set of bill codes corresponding to the payment operation.

[0034] An embodiment of the present invention further provides a reconciliation device based on data comparison, comprising:

[0035] processor;

[0036] a memory storing executable instructions of the processor;

[0037] Wherein, the processor is configured to perform the steps of the above-mentioned reconciliation method based on data comparison by executing the executable instructions.

[0038] An embodiment of the present invention further provides a computer-readable storage medium for storing a program, which, when executed, implements the steps of the above-mentioned reconciliation method based on data comparison.

[0039] The purpose of the present invention is to provide a reconciliation method, system, device and storage medium based on data comparison, which can improve the accuracy of bills, enhance the confidentiality of financial processes, reduce manual intervention, and speed up financial processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Other features, objectives and advantages of the present invention will become more apparent from a reading of the detailed description of non-limiting embodiments made with reference to the following accompanying drawings.

[0041] Figure 1 It is a flow chart of the reconciliation method based on data comparison of the present invention.

[0042] Figure 2 It is a module schematic diagram of the reconciliation system based on data comparison of the present invention.

[0043] Figure 3 It is a structural schematic diagram of the reconciliation device based on data comparison of the present invention.

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

[0045] The following describes the implementation methods of the present application through specific examples, and 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 methods, and the details in the present application can also be modified or changed in various ways according to different viewpoints and application systems without departing from the spirit of the present application. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.

[0046] The following is a detailed description of the embodiments of the present application with reference to the accompanying drawings so that those skilled in the art can easily implement the present application. The present application can be embodied in a variety of different forms and is not limited to the embodiments described herein.

[0047] In the representations of the present application, the representations with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" etc. mean that the specific features, structures, materials or characteristics represented in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the represented specific features, structures, materials or characteristics may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples represented in the present application and the features of the different embodiments or examples, unless they contradict each other.

[0048] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the representation of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0049] In order to clearly describe the present application, components irrelevant to the description are omitted, and the same reference symbols are given to the same or similar components throughout the specification.

[0050] Throughout the specification, when a device is said to be "connected" to another device, this includes not only the case of "direct connection" but also the case of "indirect connection" by placing other elements therebetween. In addition, when a device is said to "include" a certain component, unless otherwise stated, it does not exclude other components, but means that other components may be included.

[0051] When a device is said to be "on" another device, it may be directly on the other device, but there may also be other devices between it. In contrast, when a device is said to be "directly" on another device, there are no other devices between it.

[0052] Although the terms first, second, etc. are used to represent various elements in some examples, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first interface and the second interface, etc. are represented. Moreover, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising" and "including" indicate the existence of features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Therefore, "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". Only when the combination of elements, functions, steps or operations is inherently mutually exclusive in some way, will there be an exception to this definition.

[0053] The technical terms used herein are only used to refer to specific embodiments and are not intended to limit the present application. The singular form used herein also includes the plural form unless the sentence clearly indicates the contrary meaning. The meaning of "including" used in the specification is to specify 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.

[0054] Although not defined differently, all terms, including technical and scientific terms used herein, have the same meaning as those generally understood by those skilled in the art to which this application belongs. Terms defined in commonly used dictionaries are additionally interpreted as having meanings consistent with the relevant technical literature and the contents of the current disclosure, and unless defined, shall not be overly interpreted as ideal or very formal meanings.

[0055] Figure 1 Flow chart of the reconciliation method based on data comparison of the present invention. Figure 1 As shown, an embodiment of the present invention provides a reconciliation method based on data comparison, comprising the following steps:

[0056] S110. The payee account generates a payment information and a settlement information based on an order information. The settlement information includes a unique non-fungible token, and the payment information includes a unique billing code that has a mapping relationship with the non-fungible token. The non-fungible token mentioned in the present invention, that is, NFT, is called Non-Fungible Token. It is a unique cryptocurrency token used to represent digital assets (including jpg and video clip forms). NFT can be bought and sold, just like tangible assets. S120. The payment information is sent to the payment database, and the billing code of the payment information has a mapping relationship with the non-fungible token and is added to the billing code table of the payment database.

[0057] S130. The settlement information is sent to the settlement database and to the payer's account.

[0058] S140. When the payer account selects at least one settlement information for combined payment, the digital identity conversion information of the non-fungible tokens of all settlement information is embedded in the payment operation and fed back to the payee account.

[0059] S150. The payee account searches for the corresponding billing code in the billing code according to all non-fungible tokens received in the payment operation, and generates a set of billing codes corresponding to the payment operation.

[0060] Preferably, step S110 includes:

[0061] S111. The payee account generates a non-fungible token upload instruction according to an order information, and stores the non-fungible token in the corresponding blockchain according to the non-fungible token upload instruction. The digital identity of the ownership of the non-fungible token is the payee account.

[0062] S112. The payee account generates a unique billing code that has a mapping relationship with the non-fungible token based on the order information.

[0063] Preferably, step S111 includes:

[0064] The payee account generates a non-fungible token upload instruction, an encrypted private key and an encrypted public key according to an order information, and stores the non-fungible token and the encrypted private key in the corresponding blockchain according to the non-fungible token upload instruction.

[0065] Preferably, step S112 includes:

[0066] The payee account generates a unique billing code that is mapped to the non-fungible token based on the order information, and encrypts the billing code with the encrypted public key and saves it.

[0067] Preferably, step S130 includes:

[0068] S131. Settlement information is sent to the settlement database.

[0069] S132. When the settlement information is forwarded to the payer's account, the non-fungible token and the encrypted private key are stored in the blockchain of the payer's account, and the digital identity of the ownership of the non-fungible token is converted to the payer's account.

[0070] Preferably, step S140 includes: when the payer account selects at least one settlement information for combined payment, the digital identity of the non-fungible token of all settlement information to be paid is converted into the payee account, and the encrypted private key is sent to the payee account.

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

[0072] S151. The payee account searches for the corresponding bill code in the bill code based on the non-fungible token and encrypted private key in the payment operation.

[0073] S152. Decrypt the bill code.

[0074] S153. Find the billing code corresponding to the non-fungible token.

[0075] S154. Collect the billing code corresponding to each non-fungible token, generate a set of billing codes corresponding to the payment operation for account settlement.

[0076] The present invention accurately tracks bills by following the transfer of ownership of non-fungible tokens of bills. Even in the case of combined payment, the mapping relationship of accounts can be guaranteed to be accurate, which is conducive to AI improvement of finance, thereby enhancing the confidentiality of financial processes, reducing manual intervention, and speeding up financial processes. The transfer of ownership of non-fungible tokens involved in the present invention is a prior art and will not be repeated here.

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

[0078] First, the payee account generates a non-fungible token upload instruction, an encrypted private key and an encrypted public key according to an order information, and stores the non-fungible token and the encrypted private key in the corresponding blockchain according to the non-fungible token upload instruction. The payee account generates a unique bill code with a mapping relationship with the non-fungible token according to the order information, and encrypts the bill code with the encrypted public key and saves it.

[0079] The payment information is sent to the payment database, and the billing code of the payment information has a mapping relationship with the non-fungible token and is added to the billing code table of the payment database.

[0080] The settlement information is sent to the settlement database. When the settlement information is forwarded to the payer account, the non-fungible token and the encrypted private key are stored in the blockchain of the payer account, and the digital identity of the ownership of the non-fungible token is converted to the payer account.

[0081] When the payer account selects at least one settlement information for combined payment, the digital identity of the non-fungible tokens of all settlement information to be paid is converted to the payee account, and the encrypted private key is sent to the payee account.

[0082] Finally, the payee account looks up the corresponding billing code in the billing code based on the non-fungible token and encrypted private key in the payment operation. Decrypt the billing code. Find the billing code corresponding to the non-fungible token. Collect the billing code corresponding to each non-fungible token, generate a collection of billing codes corresponding to the payment operation, and clear the account.

[0083] Figure 2 Schematic diagram of the module of the reconciliation system based on data comparison of the present invention. Figure 2 As shown, the reconciliation system 5 based on data comparison of the present invention includes:

[0084] The information generation module 51, the payee account generates a payment information and a settlement information based on an order information, the settlement information includes a unique non-fungible token, and the payment information includes a unique billing code that has a mapping relationship with the non-fungible token.

[0085] Payment data module 52, the payment information is sent to the payment database, and the billing code of the payment information has a mapping relationship with the non-fungible token and is added to the billing code table of the payment database.

[0086] Settlement data module 53, the settlement information is sent to the settlement database and to the payer's account.

[0087] The token feedback module 54 embeds the digital identity conversion information of the non-fungible tokens of all settlement information into the payment operation and feeds it back to the payee account when the payer account selects at least one settlement information for combined payment.

[0088] The bill reconciliation module 55, the payee account searches the bill code for the corresponding bill code according to all the non-fungible tokens received in the payment operation, and generates a set of bill codes corresponding to the payment operation.

[0089] The account reconciliation system based on data comparison of the present invention can improve the accuracy of bills, enhance the confidentiality of financial processes, reduce manual intervention, and speed up financial processes.

[0090] The above embodiments are only preferred examples of the present invention and are not intended to limit the present invention. Any equivalent substitutions, modifications and changes made within the principles of the present invention are within the protection scope of the present invention.

[0091] The embodiment of the present invention further provides a reconciliation device based on data comparison, comprising a processor and a memory in which executable instructions of the processor are stored. The processor is configured to execute the steps of the reconciliation method based on data comparison by executing the executable instructions.

[0092] As shown above, the reconciliation system based on data comparison of this embodiment of the present invention can improve the accuracy of bills, enhance the confidentiality of financial processes, reduce manual intervention, and speed up financial processes.

[0093] It will be appreciated by those skilled in the art that various aspects of the present invention may be implemented as systems, methods or program products. Therefore, various aspects of the present invention may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, which may be collectively referred to herein as "circuits", "modules" or "platforms".

[0094] Figure 3 Schematic diagram of the structure of the reconciliation device based on data comparison of the present invention. Figure 3 The electronic device 600 according to this embodiment of the present invention is described. Figure 3 The electronic device 600 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0095] like Figure 3 As shown, the electronic device 600 is in the form of a general 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.

[0096] The storage unit stores program codes, which can be executed by the processing unit 610, so that the processing unit 610 executes the steps of various exemplary embodiments of the present invention described in the electronic prescription circulation processing method section of this specification. For example, the processing unit 610 can execute the following steps: Figure 1 Follow the steps shown in .

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

[0098] The storage unit 620 may also include a program / utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0099] Bus 630 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0100] The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may 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 (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 650. Furthermore, the electronic device 600 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 via a bus 630. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction 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.

[0101] The embodiment of the present invention also provides a computer-readable storage medium for storing a program, and the steps of the reconciliation method based on data comparison are implemented when the program is executed. In some possible implementations, various aspects of the present invention can also be implemented in the form of a program product, which includes a program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps of various exemplary embodiments of the present invention described in the above-mentioned electronic prescription circulation processing method section of this specification.

[0102] As shown above, the reconciliation system based on data comparison of this embodiment of the present invention can improve the accuracy of bills, enhance the confidentiality of financial processes, reduce manual intervention, and speed up financial processes.

[0103] Figure 4 Schematic diagram of the structure of the computer-readable storage medium of the present invention. Figure 4As shown, a program product 800 for implementing the above method according to an embodiment of the present invention is described, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

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

[0105] Computer readable storage media may include data signals propagated in baseband or as part of a carrier wave, wherein readable program codes are carried. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The readable storage medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, device, or device. The program codes contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination thereof.

[0106] 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 conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user 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 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., through the Internet using an Internet service provider).

[0107] In summary, the purpose of the present invention is to provide a reconciliation method, system, device and storage medium based on data comparison, which can improve the accuracy of bills, enhance the confidentiality of financial processes, reduce manual intervention, and speed up financial processes.

[0108] The above contents are further detailed descriptions of the present invention in combination with specific preferred embodiments, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

1. A reconciliation method based on data comparison, characterized in that: The following steps are involved: S110. The payee account generates a payment information and a settlement information based on an order information, wherein the settlement information includes a unique non-fungible token, and the payment information includes a unique billing code having a mapping relationship with the non-fungible token; S120, the payment information is sent to a payment database, and the billing code of the payment information has a mapping relationship with the non-fungible token and is added to the billing code table of the payment database; S130, the settlement information is sent to the settlement database and to the payer's account; S140. When the payer account selects at least one of the settlement information for combined payment, the digital identity conversion information of the non-fungible tokens of all the settlement information is embedded in the payment operation and fed back to the payee account; S150. The payee account searches for a corresponding billing code in the billing code according to all the non-fungible tokens received in the payment operation, and generates a set of billing codes corresponding to the payment operation.

2. The reconciliation method based on data comparison according to claim 1 is characterized in that: The step S110 includes: S111. The payee account generates a non-fungible token upload instruction according to order information, and stores the non-fungible token in the corresponding blockchain according to the non-fungible token upload instruction, and the digital identity of the ownership of the non-fungible token is the payee account; S112. The payee account generates a unique billing code that has a mapping relationship with the non-fungible token based on the order information.

3. The reconciliation method based on data comparison according to claim 2 is characterized in that: The step S111 includes: The payee account generates a non-fungible token upload instruction, an encrypted private key and an encrypted public key according to order information, and stores the non-fungible token and the encrypted private key in the corresponding blockchain according to the non-fungible token upload instruction.

4. The reconciliation method based on data comparison according to claim 3 is characterized in that: The step S112 includes: The payee account generates a unique billing code that is mapped to the non-fungible token based on the order information, and encrypts the billing code using an encrypted public key and saves it.

5. The reconciliation method based on data comparison according to claim 4 is characterized in that: The step S130 includes: S131, the settlement information is sent to a settlement database; S132. When the settlement information is forwarded to the payer's account, the non-fungible token and the encrypted private key are stored in the blockchain of the payer's account, and the digital identity of the ownership of the non-fungible token is converted to the payer's account.

6. The reconciliation method based on data comparison according to claim 5 is characterized in that: The step S140 includes: when the payer account selects at least one of the settlement information for combined payment, the digital identity of the non-fungible token of all the settlement information to be paid is converted into the payee account, and the encrypted private key is sent to the payee account.

7. The reconciliation method based on data comparison according to claim 6 is characterized in that: The step S150 includes the following steps: S151. The payee account searches for a corresponding bill code in the bill code according to the non-fungible token and the encrypted private key in the payment operation; S152, decrypting the bill code; S153. Find the bill code corresponding to the non-fungible token; S154. Collect the billing code corresponding to each of the non-fungible tokens, and generate a set of billing codes corresponding to the payment operation for settlement.

8. A reconciliation system based on data comparison, used to implement the reconciliation method based on data comparison according to claim 1, characterized in that: include: An information generation module, wherein the payee account generates a payment information and a settlement information based on an order information, wherein the settlement information includes a unique non-fungible token, and the payment information includes a unique billing code having a mapping relationship with the non-fungible token; Payment data module, the payment information is sent to a payment database, and the billing code of the payment information has a mapping relationship with the non-fungible token and is added to the billing code table of the payment database; A settlement data module, wherein the settlement information is sent to a settlement database and to a payer's account; A token feedback module, when the payer account selects at least one of the settlement information for combined payment, embeds the digital identity conversion information of the non-fungible tokens of all the settlement information into the payment operation and feeds it back to the payee account; The bill reconciliation module, the payee account searches the bill code for the corresponding bill code according to all the non-fungible tokens received in the payment operation, and generates a set of bill codes corresponding to the payment operation.

9. A reconciliation device based on data comparison, characterized in that: include: processor; a memory storing executable instructions of the processor; Wherein, the processor is configured to perform the steps of the reconciliation method based on data comparison according to any one of claims 1 to 6 by executing the executable instructions.

10. A computer-readable storage medium for storing a program, characterized in that: When the program is executed by a processor, the steps of the reconciliation method based on data comparison described in any one of claims 1 to 6 are implemented.

Images