Electronic invoice generation method, device and equipment, readable storage medium and program product

Abstract

The invention relates to an electronic invoice generation method and device, equipment, a readable storage medium and a program product. The method comprises the steps of firstly, obtaining an invoicing application of a target user, then, generating electronic invoice invoicing data according to the invoicing application of the target user, and finally, obtaining authorization information of a supplier server, and sending the electronic invoice invoicing data to the supplier server according to the authorization information, and the supplier server generates the electronic invoice according to the electronic invoice issuing data. By adopting the method, the electronic invoice can be automatically generated according to the electronic invoice invoicing data, manual invoicing is not needed, the invoicing efficiency is higher, meanwhile, the electronic invoice invoicing data is sent after the authorization information of the supplier server is obtained, the electronic invoice invoicing data transmission safety is improved, and the invoicing safety is higher.

Description

Technical Field

[0001] The present application relates to the technical field of electronic invoices, and in particular to an electronic invoice generation method, apparatus, device, readable storage medium and program product. Background Art

[0002] At present, traditional procurement platforms usually include multiple supplier systems, and the invoicing information between multiple supplier systems is different. Therefore, in the existing invoice issuance process, it is usually necessary to manually connect with the supplier system, check the invoice information required by the invoices of different supplier systems, and then manually issue the invoices.

[0003] However, this method has low efficiency and security in issuing invoices. Summary of the invention

[0004] Based on this, it is necessary to provide an electronic invoice generation method, device, equipment, readable storage medium and program product that can provide invoicing efficiency and security in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for generating an electronic invoice, the method comprising:

[0006] Obtain the target user's invoicing application;

[0007] Generate electronic invoice data based on invoicing application;

[0008] Obtain the authorization information of the supplier server, and send the electronic invoice issuance data to the supplier server according to the authorization information, so that the supplier server can generate an electronic invoice based on the electronic invoice issuance data.

[0009] In one embodiment, obtaining authorization information of a supplier server, and sending electronic invoice issuance data to the supplier server according to the authorization information, includes:

[0010] According to the Token interface of the supplier server, obtain the access token AccessToken provided by the supplier server;

[0011] Encrypting the electronic invoice data according to a preset encryption algorithm to obtain encrypted electronic invoice data;

[0012] The encrypted electronic invoice data is sent to the supplier server based on the Access Token.

[0013] In one embodiment, after sending the electronic invoice billing data to the supplier server according to the authorization information, the method further includes:

[0014] If a verification failure message is received from the supplier server, the electronic invoice billing data modified by the target user is obtained. The verification failure message is sent by the supplier server after the verification of the electronic invoice billing data fails;

[0015] Send the modified electronic invoice billing data to the supplier server.

[0016] In one embodiment, the method further comprises:

[0017] Receive the address information sent by the supplier server. The address information is sent by the supplier server after the electronic invoice is issued;

[0018] Update the status information of the electronic invoice based on the address information.

[0019] In a second aspect, the present application provides a method for generating an electronic invoice, the method comprising:

[0020] Receive electronic invoice issuance data;

[0021] Verify the electronic invoice issuance data and obtain the verification result;

[0022] If the verification result is passed, an electronic invoice is generated based on the electronic invoice issuance data.

[0023] In one embodiment, the method further comprises:

[0024] If the verification result is verification failure, a verification failure message is sent;

[0025] The modified electronic invoice issuing data is received, and an electronic invoice is generated according to the modified electronic invoice issuing data.

[0026] In one embodiment, generating an electronic invoice based on electronic invoice issuance data includes:

[0027] Determine whether the ticket needs to be split;

[0028] If not, generate an electronic invoice based on the electronic invoice issuance data;

[0029] If yes, a preset number of electronic invoices are generated based on the bill splitting data and the electronic invoice issuance data.

[0030] In one embodiment, the method further comprises:

[0031] After the electronic invoice is issued, the address information of the electronic invoice is sent so that the terminal can update the status information of the electronic invoice according to the address information.

[0032] In a third aspect, the present application also provides an electronic invoice generation device, the device comprising:

[0033] The acquisition module is used to obtain the invoicing application of the target user;

[0034] The first generation module is used to generate electronic invoice issuance data according to the invoice issuance application;

[0035] The sending module is used to obtain the authorization information of the supplier server and send the electronic invoice issuance data to the supplier server according to the authorization information, so that the supplier server can generate an electronic invoice based on the electronic invoice issuance data.

[0036] In a fourth aspect, the present application further provides an electronic invoice generation device, the device comprising:

[0037] A receiving module, used for receiving electronic invoice issuance data;

[0038] A verification module is used to verify the electronic invoice issuance data and obtain the verification result;

[0039] The second generation module is used to generate an electronic invoice based on the electronic invoice issuance data if the verification result is passed.

[0040] In a fifth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the electronic invoice generation method described in any one of the first aspect or the second aspect is implemented.

[0041] In a sixth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the electronic invoice generation method described in any one of the first aspect or the second aspect is implemented.

[0042] In a seventh aspect, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the electronic invoice generation method described in any one of the first aspect or the second aspect.

[0043] The above-mentioned electronic invoice generation method, device, equipment, readable storage medium and program product first obtain the target user's invoice application, then generate the electronic invoice billing data according to the target user's invoice application, and finally obtain the authorization information of the supplier server, and send the electronic invoice billing data to the supplier server according to the authorization information, so that the supplier server can generate an electronic invoice according to the electronic invoice billing data. In this way, after the target user enters the invoice application at the terminal, the electronic invoice billing data is automatically generated, and the electronic invoice billing data is sent to the supplier server according to the obtained authorization information of the supplier server. The supplier automatically generates an electronic invoice according to the electronic invoice billing data, without the need for manual invoicing, so the invoicing efficiency is higher. At the same time, after obtaining the authorization information of the supplier server, the electronic invoice billing data is sent, which improves the security of the electronic invoice billing data transmission, and the invoicing security is higher. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1 An application environment diagram of an electronic invoice generation method in one embodiment;

[0046] Figure 2 A schematic diagram of a process of generating an electronic invoice in one embodiment;

[0047] Figure 3 A schematic diagram of a flow chart of a method for generating an electronic invoice in another embodiment;

[0048] Figure 4 A schematic diagram of a flow chart of a method for generating an electronic invoice in another embodiment;

[0049] Figure 5 A schematic diagram of a flow chart of a method for generating an electronic invoice in another embodiment;

[0050] Figure 6 A schematic diagram of a flow chart of a method for generating an electronic invoice in another embodiment;

[0051] Figure 7 A schematic diagram of a flow chart of a method for generating an electronic invoice in another embodiment;

[0052] Figure 8 A schematic diagram of a flow chart of a method for generating an electronic invoice in another embodiment;

[0053] Fig. 9 A schematic diagram of a flow chart of a method for generating an electronic invoice in another embodiment;

[0054] Fig.10 It is a structural block diagram of an electronic invoice generating device in one embodiment;

[0055] Fig.11 It is a structural block diagram of an electronic invoice generating device in another embodiment;

[0056] Fig.12 is an internal structure diagram of a computer device in one embodiment;

[0057] Fig.13 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0059] The electronic invoice generation method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the supplier server 104 through the network. The data storage system can store the data that the supplier server 104 needs to process. The data storage system can be integrated on the supplier server 104, or it can be placed on the cloud or other network servers. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablets, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The head-mounted device can be a virtual reality (VR) device, an augmented reality (AR) device, smart glasses, etc. The supplier server 104 can be an independent physical server, or it can be a server cluster or distributed system composed of multiple physical servers, or it can be a cloud server that provides cloud computing services.

[0060] In an exemplary embodiment, Figure 2 As shown, a method for generating an electronic invoice is provided, and the method is applied to Figure 1 The terminal 102 in the example is used for explanation, and the steps include the following steps 201 to 203.

[0061] in:

[0062] Step 201: Obtain the target user's invoicing application.

[0063] The invoicing application of the target user may include the invoicing type of the target user and specific invoicing data. Optionally, the invoicing type includes issuing an ordinary paper invoice or an electronic invoice.

[0064] Step 202: Generate electronic invoice data according to the invoicing application.

[0065] If the target user's invoicing application is an electronic invoice, the electronic invoice invoicing data is generated according to the invoicing application. Optionally, the electronic invoice invoicing data may include invoice details, purchaser's name, purchaser's tax number, purchaser's telephone number, purchaser's address, purchaser's bank account information, invoice serial number, unit price, tax rate and other information.

[0066] Step 203, obtaining authorization information of the supplier server, and sending the electronic invoice issuance data to the supplier server according to the authorization information, so that the supplier server can generate an electronic invoice according to the electronic invoice issuance data.

[0067] In order to improve the security of electronic invoice data transmission, before sending data, obtain the authorization information of the supplier server. Optionally, through role-based access control, for example, according to the user information of the terminal login, determine the identity of the logged-in user, and different users correspond to different access rights to ensure that users can only access and operate data within the scope of their own authority. Send the electronic invoice data to the supplier server according to the authorization information. Optionally, data can be transmitted through HTTPS (Hypertext Transfer Protocol Secure), thereby ensuring the security and integrity of the electronic invoice data during transmission.

[0068] In the above embodiment, first, the target user's invoicing application is obtained, then the electronic invoice invoicing data is generated according to the target user's invoicing application, and finally, the authorization information of the supplier server is obtained, and the electronic invoice invoicing data is sent to the supplier server according to the authorization information, so that the supplier server can generate an electronic invoice according to the electronic invoice invoicing data. In this way, after the target user enters the invoicing application at the terminal, the electronic invoice invoicing data is automatically generated, and the electronic invoice invoicing data is sent to the supplier server according to the obtained authorization information of the supplier server. The supplier automatically generates an electronic invoice according to the electronic invoice invoicing data, without the need for manual invoicing, so the invoicing efficiency is higher. At the same time, after the authorization information of the supplier server is obtained, the electronic invoice invoicing data is sent, which improves the security of the electronic invoice invoicing data transmission, and the invoicing security is higher.

[0069] In one embodiment, the above step 203 obtains the authorization information of the supplier server, and sends the electronic invoice billing data to the supplier server according to the authorization information, such as Figure 3 As shown, it may include:

[0070] Step 301: Obtain an access token provided by the supplier server according to the Token interface of the supplier server.

[0071] The Token interface is a security mechanism that can perform identity authentication and data transmission between the terminal and the supplier server. The terminal obtains the Access Token provided by the supplier server, which is also the authorization credential for the terminal to access other interfaces of the supplier server.

[0072] Step 302: encrypt the electronic invoice data according to a preset encryption algorithm to obtain encrypted electronic invoice data.

[0073] In order to further improve the security of data transmission, the electronic invoice issuance data may be encrypted before transmission. Optionally, the preset encryption algorithm may be RSA (RSA algorithm, public key cryptography) encryption technology. The sensitive data in the electronic invoice issuance data is encrypted by the encryption algorithm to obtain the encrypted electronic invoice issuance data.

[0074] Step 303: Send the encrypted electronic invoice billing data to the supplier server according to the Access Token.

[0075] Then, based on the obtained Access Token, the corresponding interface of the supplier server can be accessed, and the encrypted electronic invoice billing data is sent to the supplier server, which then performs the invoicing operation.

[0076] In the above embodiment, by obtaining the Access Token of the supplier server and encrypting the electronic invoice billing data, and then sending the encrypted electronic invoice billing data to the supplier server according to the Access Token, the security of data transmission is improved, thereby ensuring the accuracy of the billing data.

[0077] In the embodiment of the present application, in order to improve the accuracy of electronic invoice generation, after the electronic invoice billing data is sent to the supplier server according to the authorization information, such as Figure 4 As shown, the method also includes:

[0078] Step 401: If a verification failure message is received from the supplier server, the electronic invoice billing data modified by the target user is obtained.

[0079] The verification failure message is sent by the supplier server after the verification of the electronic invoice billing data fails. If the verification failure message is received, it means that the electronic invoice billing data may be abnormal, such as the wrong name of the electronic invoice purchaser, etc. At this time, the terminal reminds the target user to check and modify the billing application, and then obtains the modified electronic invoice billing data of the target user.

[0080] Step 402, sending the modified electronic invoice billing data to the supplier server.

[0081] After modification, the modified electronic invoice billing data is sent to the supplier server. Optionally, the modified electronic invoice billing data is encrypted and then sent to the supplier server according to the Access Token. At the same time, the initial invoice application sent last time is invalidated.

[0082] Optional, to facilitate the terminal to check the status information of the electronic invoice, such as Figure 5 As shown, the method also includes:

[0083] Step 501, receiving address information sent by the supplier server.

[0084] The address information is sent by the supplier server after the electronic invoice is issued. Optionally, the address information can be encrypted before being sent.

[0085] Step 502: Update the status information of the electronic invoice according to the address information.

[0086] After the terminal obtains the address information, it decrypts it and obtains the specific file of the electronic invoice through the address information. Optionally, it can be a PDF file or OFD (Open Fixed-layout Document) to obtain an XML file. The file can include specific information such as the invoice serial number, invoice attachments, and invoiced amount. The terminal's electronic invoice status information is updated according to the specific information of the electronic invoice, and the user can be prompted that the electronic invoice issuance is completed.

[0087] In the above embodiment, after the electronic invoice is issued, the status information of the electronic invoice is updated by receiving the address information of the electronic invoice, so as to facilitate the user to view the electronic invoice.

[0088] In an exemplary embodiment, Figure 6 As shown, a method for generating an electronic invoice is provided, and the method is applied to Figure 1 The supplier server 104 in the example is used for explanation, and the steps include the following steps 601 to 603. Among them:

[0089] Step 601, receiving electronic invoice issuance data.

[0090] The electronic invoice billing data sent by the receiving terminal is decrypted.

[0091] Step 602: Verify the electronic invoice issuance data to obtain a verification result.

[0092] Verify the electronic invoice data, for example, verify the buyer's name, buyer's tax number, buyer's phone number, buyer's address, buyer's bank information, unit price, tax rate and other information based on the data stored locally on the supplier's server to determine whether there are any abnormalities.

[0093] Step 603: If the verification result is passed, an electronic invoice is generated according to the electronic invoice issuance data.

[0094] If the verification result is passed, that is, the billing data of the electronic invoice is correct, the electronic invoice can be generated based on the electronic invoice data. Optionally, before generating the electronic invoice, it is determined whether the bill needs to be split. The number of generated electronic invoices can be determined based on the user's choice, such as Figure 7 As shown, including:

[0095] Step 701, determine whether the ticket needs to be split.

[0096] Among them, splitting the invoice means whether the electronic invoice needs to be split into multiple electronic invoices.

[0097] Step 702: If not, generate an electronic invoice based on the electronic invoice issuance data.

[0098] If the bill does not need to be split, an electronic invoice will be generated based on the electronic invoice issuance data.

[0099] Step 703: If yes, generate a preset number of electronic invoices based on the bill splitting data and the electronic invoice issuance data.

[0100] Among them, the bill splitting data can be information such as the number of bills split selected by the user and the amount corresponding to each electronic invoice after the bill splitting. The electronic invoice can be split into multiple invoices based on the bill splitting data and the electronic invoice issuance data. The preset number, that is, the number of bills split, can be selected by the user, and this application does not impose any restrictions on this.

[0101] Optionally, after the electronic invoice is issued, the address information of the electronic invoice is sent so that the terminal can update the status information of the electronic invoice according to the address information.

[0102] After the electronic invoice is issued, the address information of the electronic invoice is transmitted back to the terminal. The terminal can obtain the specific content of the electronic invoice based on the address information, and then update the status information of the electronic invoice.

[0103] In the above embodiment, the electronic invoice can be split according to the needs of the user, which improves the flexibility of electronic invoice issuance. After the electronic invoice is issued, the address information of the electronic invoice is sent to the terminal for easy viewing by the terminal user.

[0104] In one embodiment, Figure 8 As shown, the method also includes:

[0105] Step 801: If the verification result is verification failure, a verification failure message is sent.

[0106] If the verification result is a verification failure, that is, there is abnormal data in the electronic invoice issuance data, the supplier server sends a verification failure message to the terminal, and the terminal prompts the target user to make changes.

[0107] Step 802: receiving the modified electronic invoice issuance data, and generating an electronic invoice according to the modified electronic invoice issuance data.

[0108] After the target user makes the modification, the modified electronic invoice billing data sent by the receiving terminal is verified. After the verification is passed, an electronic invoice is generated based on the modified electronic invoice billing data. If the verification result is still a verification failure, the above steps are repeated until the verification result is a verification success.

[0109] In the above embodiment, the accuracy of the electronic invoice issuance is ensured by verifying the electronic invoice issuance data.

[0110] In the embodiments of the present application, Fig. 9As shown, it is a system flow chart of the electronic invoice generation method provided by the embodiment of the present application, including the terminal generating invoice data, data transmission between the terminal and the supplier server, the supplier server issuing electronic invoices and returning the electronic invoice information. The terminal determines whether it is an electronic invoice according to the invoice application. If it is not an electronic invoice, paper invoice data is generated for manual invoicing. If it is an electronic invoice, the electronic invoice invoice data is generated, and then the authorization information of the supplier server is obtained. According to the authorization information, the electronic invoice invoice data is sent to the supplier server. The supplier server verifies the electronic invoice invoice data. If the verification fails, it returns to the terminal and prompts the user to modify the electronic invoice invoice data. If the verification passes, it continues to determine whether the bill needs to be split. If so, multiple electronic invoices are generated according to the bill splitting information entered by the user. If the bill does not need to be split, one electronic invoice is generated. After the bill is completed, the address information of the electronic invoice is returned to the terminal, and the terminal updates the billing status of the electronic invoice according to the address information. Optionally, during the automated invoicing process, by setting up an error handling mechanism, timely processing can be performed when errors are detected. At the same time, the terminal and supplier server record the user's access to the system and operation logs, including access time, operation content, and operation results, etc. At the same time, a data backup and recovery strategy is set up to regularly back up system data to prevent data loss of electronic invoices and ensure the security of electronic invoicing.

[0111] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0112] Based on the same inventive concept, the embodiment of the present application also provides an electronic invoice generation device for implementing the electronic invoice generation method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more electronic invoice generation device embodiments provided below can refer to the limitations of the electronic invoice generation method above, and will not be repeated here.

[0113] In an exemplary embodiment, Fig.10As shown, there is provided a 1000, comprising: an acquisition module 1001, a first generation module 1002 and a sending module 1003, wherein:

[0114] Acquisition module 1001, used to acquire the invoicing application of the target user;

[0115] The first generating module 1002 is used to generate electronic invoice issuance data according to the invoice issuance application;

[0116] The sending module 1003 is used to obtain the authorization information of the supplier server, and send the electronic invoice billing data to the supplier server according to the authorization information, so that the supplier server can generate an electronic invoice according to the electronic invoice billing data.

[0117] In one of the embodiments, the sending module 1003 is specifically used to obtain an access token Access Token provided by the supplier server according to the token Token interface of the supplier server; encrypt the electronic invoice billing data according to a preset encryption algorithm to obtain the encrypted electronic invoice billing data; and send the encrypted electronic invoice billing data to the supplier server according to the Access Token.

[0118] In one of the embodiments, the device also includes a first receiving module, which is used to obtain the modified electronic invoice billing data of the target user if a verification failure message sent by the supplier server is received, and the verification failure message is sent by the supplier server after the verification of the electronic invoice billing data fails; and send the modified electronic invoice billing data to the supplier server.

[0119] In one of the embodiments, the device also includes a second receiving module for receiving address information sent by a supplier server, where the address information is sent by the supplier server after the electronic invoice is issued; and updating the status information of the electronic invoice according to the address information.

[0120] Each module in the above-mentioned electronic invoice generation device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0121] In an exemplary embodiment, Fig.11 As shown, an electronic invoice generation device 1100 is provided, comprising: a receiving module 1101, a verification module 1102 and a second generation module 1103, wherein:

[0122] Receiving module 1101, used for receiving electronic invoice issuance data;

[0123] Verification module 1102, used to verify the electronic invoice issuance data and obtain verification results;

[0124] The second generating module 1103 is used to generate an electronic invoice according to the electronic invoice issuing data if the verification result is passed.

[0125] In one of the embodiments, the device also includes a verification message sending module, which is used to send a verification failure message if the verification result is a verification failure; receive the modified electronic invoice billing data, and generate an electronic invoice based on the modified electronic invoice billing data.

[0126] In one embodiment, the second generation module 1103 is specifically used to determine whether it is necessary to split the bill; if not, generate an electronic invoice based on the electronic invoice issuance data; if so, generate a preset number of electronic invoices based on the bill splitting data and the electronic invoice issuance data.

[0127] In one of the embodiments, the device further includes an address information sending module, which is used to send the address information of the electronic invoice after the electronic invoice is issued, so that the terminal can update the status information of the electronic invoice according to the address information.

[0128] Each module in the above-mentioned electronic invoice generation device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0129] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Fig.12As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, an electronic invoice generation method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0130] Those skilled in the art will understand that Fig.12 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0131] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: obtaining an invoicing application of a target user; generating electronic invoice billing data based on the invoicing application; obtaining authorization information of a supplier server, and sending the electronic invoice billing data to the supplier server based on the authorization information, so that the supplier server can generate an electronic invoice based on the electronic invoice billing data.

[0132] In one embodiment, when the processor executes the computer program, the following steps are also implemented: according to the token interface of the supplier server, an access token Access Token provided by the supplier server is obtained; the electronic invoice billing data is encrypting according to a preset encryption algorithm to obtain the encrypted electronic invoice billing data; and the encrypted electronic invoice billing data is sent to the supplier server according to the Access Token.

[0133] In one embodiment, when the processor executes the computer program, the following steps are also implemented: if a verification failure message is received from a supplier server, the modified electronic invoice billing data of the target user is obtained, and the verification failure message is sent by the supplier server after the verification of the electronic invoice billing data fails; the modified electronic invoice billing data is sent to the supplier server.

[0134] In one embodiment, when the processor executes the computer program, the processor also implements the following steps: receiving address information sent by the supplier server, the address information is sent by the supplier server after the electronic invoice is issued; and updating the status information of the electronic invoice according to the address information.

[0135] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.13 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store supplier system data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an electronic invoice generation method is implemented.

[0136] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: receiving electronic invoice billing data; verifying the electronic invoice billing data to obtain a verification result; if the verification result is verification passed, generating an electronic invoice based on the electronic invoice billing data.

[0137] In one embodiment, when the processor executes the computer program, the following steps are also implemented: if the verification result is a verification failure, a verification failure message is sent; and modified electronic invoice issuance data is received, and an electronic invoice is generated according to the modified electronic invoice issuance data.

[0138] In one embodiment, when the processor executes the computer program, the following steps are also implemented: determining whether it is necessary to split the bill; if not, generating an electronic invoice based on the electronic invoice issuance data; if so, generating a preset number of electronic invoices based on the bill splitting data and the electronic invoice issuance data.

[0139] In one embodiment, when the processor executes the computer program, the following steps are also implemented: after the electronic invoice is issued, the address information of the electronic invoice is sent, so that the terminal can update the status information of the electronic invoice according to the address information.

[0140] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: obtaining an invoicing application from a target user; generating electronic invoice invoicing data based on the invoicing application; obtaining authorization information from a supplier server, and sending the electronic invoice invoicing data to the supplier server based on the authorization information, so that the supplier server can generate an electronic invoice based on the electronic invoice invoicing data.

[0141] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: according to the token interface of the supplier server, an access token Access Token provided by the supplier server is obtained; the electronic invoice billing data is encrypting according to a preset encryption algorithm to obtain the encrypted electronic invoice billing data; and the encrypted electronic invoice billing data is sent to the supplier server according to the Access Token.

[0142] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if a verification failure message is received from a supplier server, the modified electronic invoice billing data of the target user is obtained, and the verification failure message is sent by the supplier server after the verification of the electronic invoice billing data fails; the modified electronic invoice billing data is sent to the supplier server.

[0143] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving address information sent by the supplier server, the address information is sent by the supplier server after the electronic invoice is issued; updating the status information of the electronic invoice according to the address information.

[0144] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving electronic invoice billing data; verifying the electronic invoice billing data to obtain a verification result; if the verification result is that the verification is passed, generating an electronic invoice based on the electronic invoice billing data.

[0145] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the verification result is a verification failure, a verification failure message is sent; and modified electronic invoice issuance data is received, and an electronic invoice is generated according to the modified electronic invoice issuance data.

[0146] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining whether it is necessary to split the bill; if not, generating an electronic invoice based on the electronic invoice issuance data; if so, generating a preset number of electronic invoices based on the bill splitting data and the electronic invoice issuance data.

[0147] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: after the electronic invoice is issued, the address information of the electronic invoice is sent so that the terminal can update the status information of the electronic invoice according to the address information.

[0148] In one embodiment, a computer program product is provided, including a computer program, which implements the following steps when executed by a processor: obtaining an invoicing application from a target user; generating electronic invoice billing data based on the invoicing application; obtaining authorization information from a supplier server, and sending the electronic invoice billing data to the supplier server based on the authorization information, so that the supplier server can generate an electronic invoice based on the electronic invoice billing data.

[0149] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: according to the token interface of the supplier server, an access token Access Token provided by the supplier server is obtained; the electronic invoice billing data is encrypting according to a preset encryption algorithm to obtain the encrypted electronic invoice billing data; and the encrypted electronic invoice billing data is sent to the supplier server according to the Access Token.

[0150] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if a verification failure message is received from a supplier server, the modified electronic invoice billing data of the target user is obtained, and the verification failure message is sent by the supplier server after the verification of the electronic invoice billing data fails; the modified electronic invoice billing data is sent to the supplier server.

[0151] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving address information sent by the supplier server, the address information is sent by the supplier server after the electronic invoice is issued; updating the status information of the electronic invoice according to the address information.

[0152] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving electronic invoice billing data; verifying the electronic invoice billing data to obtain a verification result; if the verification result is that the verification is passed, generating an electronic invoice based on the electronic invoice billing data.

[0153] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the verification result is a verification failure, a verification failure message is sent; and modified electronic invoice issuance data is received, and an electronic invoice is generated according to the modified electronic invoice issuance data.

[0154] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining whether it is necessary to split the bill; if not, generating an electronic invoice based on the electronic invoice issuance data; if so, generating a preset number of electronic invoices based on the bill splitting data and the electronic invoice issuance data.

[0155] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: after the electronic invoice is issued, the address information of the electronic invoice is sent so that the terminal can update the status information of the electronic invoice according to the address information.

[0156] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

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

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

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

Claims

1. A method for generating an electronic invoice, characterized in that: The method comprises: Obtain the target user's invoicing application; Generate electronic invoice billing data according to the billing application; The authorization information of the supplier server is obtained, and the electronic invoice issuance data is sent to the supplier server according to the authorization information, so that the supplier server can generate an electronic invoice according to the electronic invoice issuance data.

2. The method according to claim 1, characterized in that: The obtaining of authorization information from the supplier server and sending the electronic invoice issuance data to the supplier server according to the authorization information includes: According to the token interface of the supplier server, obtain the access token Access Token provided by the supplier server; Encrypting the electronic invoice data according to a preset encryption algorithm to obtain encrypted electronic invoice data; The encrypted electronic invoice billing data is sent to the supplier server according to the Access Token.

3. The method according to claim 1, characterized in that After sending the electronic invoice billing data to the supplier server according to the authorization information, the method further includes: If a verification failure message sent by the supplier server is received, the electronic invoice billing data modified by the target user is obtained, wherein the verification failure message is sent by the supplier server after verification of the electronic invoice billing data fails; The modified electronic invoice billing data is sent to the supplier server.

4. The method according to claim 1, characterized in that The method further comprises: Receiving address information sent by the supplier server, wherein the address information is sent by the supplier server after the electronic invoice is issued; The status information of the electronic invoice is updated according to the address information.

5. A method for generating an electronic invoice, characterized in that: The method comprises: Receive electronic invoice issuance data; Verifying the electronic invoice issuance data to obtain a verification result; If the verification result is that the verification is passed, an electronic invoice is generated according to the electronic invoice issuance data.

6. The method according to claim 5, characterized in that The method further comprises: If the verification result is verification failure, sending a verification failure message; The modified electronic invoice issuance data is received, and an electronic invoice is generated according to the modified electronic invoice issuance data.

7. The method according to claim 5, characterized in that The step of generating an electronic invoice according to the electronic invoice issuance data comprises: Determine whether the ticket needs to be split; If not, generating an electronic invoice based on the electronic invoice issuance data; If so, a preset number of electronic invoices are generated based on the bill splitting data and the electronic invoice issuance data.

8. The method according to claim 5, characterized in that The method further comprises: After the electronic invoice is issued, the address information of the electronic invoice is sent so that the terminal can update the status information of the electronic invoice according to the address information.

9. An electronic invoice generating device, characterized in that: The device comprises: The acquisition module is used to obtain the invoicing application of the target user; A first generating module, used to generate electronic invoice issuance data according to the invoicing application; The sending module is used to obtain the authorization information of the supplier server, and send the electronic invoice billing data to the supplier server according to the authorization information, so that the supplier server can generate an electronic invoice according to the electronic invoice billing data.

10. An electronic invoice generating device, characterized in that: The device comprises: A receiving module, used for receiving electronic invoice issuance data; A verification module, used to verify the electronic invoice issuance data and obtain a verification result; The second generating module is used to generate an electronic invoice according to the electronic invoice issuing data if the verification result is that the verification is passed.

11. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 or 5 to 8 are implemented.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

13. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images