CN112884536A

CN112884536A - Electronic invoice management method and device, computer equipment and storage medium

Info

Publication number: CN112884536A
Application number: CN202110133951.6A
Authority: CN
Inventors: 周聪; 曹传奎; 董佳佳; 杜海
Original assignee: Nanjing Suning Software Technology Co ltd
Current assignee: Nanjing Suning Software Technology Co ltd
Priority date: 2021-02-01
Filing date: 2021-02-01
Publication date: 2021-06-01
Also published as: CA3147372A1; CA3147372C

Abstract

The application relates to a management method and device of electronic invoices, computer equipment and a storage medium. The method comprises the following steps: receiving a billing request containing an access token sent by a third-party application, wherein the billing request is used for requesting to bill an electronic invoice of a target order; when the third-party application is identified as the application authorized to be accessed according to the access token, generating a billing page of the target order according to the billing request, and issuing the billing page to the third-party application; receiving invoicing information in an invoicing page sent by a third-party application, and generating an electronic invoice of a target order according to the invoicing information; and associating the electronic invoice with the access token so as to manage the electronic invoice of the target order through the access token. The method can manage the electronic invoice of the order of the consumer without the user information of the consumer.

Description

Electronic invoice management method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of invoice management technologies, and in particular, to a method and an apparatus for managing electronic invoices, a computer device, and a storage medium.

Background

According to the national policy requirements of 'accelerating the popularization and use of electronic invoices, supporting enterprises and operators to make electronic invoices according to regulations and allowing the electronic invoices to be used as reimbursement certificates' and the like, the rapid development of the electronic invoices already covers most business fields, and industries such as retail, e-commerce, travel and the like. Especially in the fast-service industry such as supermarkets, catering and the like, the electronic invoice is more generally applied. Typically, a merchant prints a two-dimensional code on a shopping receipt, and a consumer self-issues an electronic invoice by scanning the two-dimensional code.

However, the following problems are common in the conventional code scanning electronic invoice issuing:

in the industry of applying code scanning to issue electronic invoices, non-member consumers are a large group. After the electronic invoice is issued, the background cannot acquire the user information of the non-member consumer, so that the association of the order, the invoice and the consumer is difficult to realize, and the invoice management of the electronic invoice of the consumer by the background is not facilitated.

Disclosure of Invention

In view of the above, it is desirable to provide a method, an apparatus, a computer device and a storage medium for managing electronic invoices, which can manage electronic invoices of a customer's order without requiring user information of the customer.

A method of managing electronic invoices, the method comprising: receiving a billing request containing an access token sent by a third-party application, wherein the billing request is used for requesting to bill an electronic invoice of a target order; when the third-party application is identified as the application authorized to be accessed according to the access token, generating a billing page of the target order according to the billing request, and issuing the billing page to the third-party application; receiving invoicing information in an invoicing page sent by a third-party application, and generating an electronic invoice of a target order according to the invoicing information; and associating the electronic invoice with the access token so as to manage the electronic invoice of the target order through the access token.

In one embodiment, the method for managing electronic invoices further comprises the following steps: when receiving a billing authority request sent by a third-party application, acquiring a user name of the third-party application and a key corresponding to the user name, wherein the billing authority request is used for requesting the authority of issuing an electronic invoice of a target order; and obtaining an access token according to the user name and the key, and sending the access token to the third-party application.

In one embodiment, after associating the electronic invoice with the access token, the method further includes: sending prompt information representing the success of issuing the electronic invoice to a third-party application; when receiving an invoice lookup request sent by a third-party application, if the invoice lookup request contains an access token, acquiring invoice information of the electronic invoice according to the access token, and issuing the invoice information of the electronic invoice to the third-party application.

In one embodiment, after associating the electronic invoice with the access token, the method further includes: receiving a new line replacement request sent by a third-party application, wherein the new line replacement request is used for requesting to replace the invoice new line of the electronic invoice; when the access token in the head-up replacement request is identified, issuing a head-up replacement page to the third-party application; and receiving the invoice new head sent by the third-party application in the new head replacement page, replacing the invoice new head in the electronic invoice with the replaced invoice new head to obtain the replaced electronic invoice, and associating the replaced electronic invoice with the access token.

Preferably, after the replaced electronic invoice is obtained, the method further comprises: the electronic invoice before replacement is punched; and issuing the invoice information of the replaced electronic invoice to a third-party application.

In one embodiment, before issuing the new page to the third-party application, the method further includes: identifying first order information of the electronic invoice according to the new head replacement request; inquiring the head-up replacement times of the electronic invoice recorded in the head-up replacement record table according to the first order information; when the number of times of head-up replacement is greater than the preset number of times, issuing prompt information representing failure of head-up replacement of the electronic invoice to a third-party application; and when the head-up replacement frequency is less than or equal to the preset frequency, the step of issuing a head-up replacement page to a third-party application is carried out.

In one embodiment, after generating the electronic invoice of the target order according to the invoicing information, the method further comprises the following steps: receiving a paper invoice replacement request sent by a third-party application, wherein the paper invoice replacement request is used for requesting to replace an electronic invoice with a paper invoice; when the access token in the paper invoice replacement request is identified, storing second order information of the electronic invoice into a billing pool of the paper invoice, wherein the billing pool of the paper invoice is used for storing the order information of the paper invoice to be billed; and (5) the electronic invoice is punched and sold.

In one embodiment, before receiving the invoicing request sent by the third-party application, the method further includes: receiving order information to be placed of a target order sent by an order placing system; generating an identification code of the target order; generating first encryption information of an identification code according to the order information to be made and by adopting a random salt value; encrypting the identification code by adopting first encryption information to obtain an encrypted identification code; and issuing the encrypted identification code to the order opening system. Receiving an invoicing request sent by a third-party application, wherein the invoicing request comprises: and receiving an invoicing request sent by the third-party application, wherein the invoicing request is obtained by scanning the encrypted identification code provided by the order issuing system through the third-party application. The management method of the electronic invoice further comprises the following steps: and extracting second encryption information from the invoicing request, and if the second encryption information is matched with the first encryption information, issuing an invoicing page to a third-party application according to the invoicing request.

An apparatus for managing electronic invoices, the apparatus comprising: the receiving module is used for receiving a billing request containing the access token and sent by a third-party application, wherein the billing request is used for requesting to bill an electronic invoice of a target order; the issuing module is used for generating an invoicing page of the target order according to the invoicing request and issuing the invoicing page to the third-party application when the third-party application is identified as the application authorized to be accessed according to the access token; the generation module is used for receiving the invoicing information in the invoicing page sent by the third-party application and generating an electronic invoice of the target order according to the invoicing information; and the management module is used for associating the electronic invoice with the access token so as to manage the electronic invoice of the target order through the access token.

A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of any of the above embodiments when executing the computer program.

A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any of the above embodiments.

The management method, the device, the computer equipment and the storage medium of the electronic invoice receive a billing request containing an access token and sent by a third-party application, wherein the billing request is used for requesting to bill an electronic invoice of a target order, when the third-party application is identified as an application authorized to be accessed according to the access token, a billing page of the target order is generated according to the billing request, the billing page is issued to the third-party application, billing information in the billing page sent by the third-party application is received, the electronic invoice of the target order is generated according to the billing information, and the electronic invoice is associated with the access token so as to carry out invoice management on the electronic invoice of the target order through the access token. Therefore, the background can manage the electronic invoice of the target order of the consumer through the access token for authorizing the third-party application to access without using the user information of the consumer, so that the management of the background on the order of the non-member consumer is realized, and the management of the background on the electronic invoice of the non-member system is expanded.

Drawings

FIG. 1 is a diagram of an application environment of a method for managing electronic invoices, in one embodiment;

FIG. 2 is a diagram illustrating an exemplary implementation of a method for managing electronic invoices, in accordance with an embodiment;

FIG. 3 is a flow diagram illustrating a method for managing electronic invoices, in one embodiment;

FIG. 4 is a schematic diagram of a generic plate for an electronic type invoice in one embodiment;

FIG. 5 is a flow diagram that illustrates information interaction between various devices when a user queries for an electronic invoice, under an embodiment;

FIG. 6 is an interface diagram of a display interface of a third party application in one embodiment;

FIG. 7 is a schematic flow chart illustrating a process for head-up replacement of electronic invoices in one embodiment;

FIG. 8 is an interface diagram that illustrates a change page for a paper invoice displayed on a third-party application, in one embodiment;

FIG. 9 is a schematic flow chart diagram illustrating the paper invoice replacement process for electronic invoices in one embodiment;

FIG. 10 is a flow diagram that illustrates information interaction between various devices in the electronic invoicing of a target order, under an embodiment;

FIG. 11 is a block diagram of an electronic invoice management apparatus, according to an embodiment;

FIG. 12 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The management method of the electronic invoice can be applied to the application environment shown in fig. 1. As shown in fig. 1, the background 104 is used for implementing an electronic invoice management method of the present application. Specifically, the user sends an invoicing request containing the access token to the background 104 through a third-party application on the terminal 102, and the invoicing request is used for requesting to invoice the target order electronically. And when the background 104 identifies that the third-party application is an application authorized to be accessed according to the access token, the billing page of the target order is generated according to the billing request, and the billing page is issued to the third-party application on the terminal 102. Further, a third party application on the terminal 102 presents an invoicing page to the user. The user inputs the billing information of the target order on the billing page. The terminal 102 sends an invoicing page containing invoicing information to the back office 104. Further, the background 104 receives the invoicing information in the invoicing page sent by the third-party application, and generates an electronic invoice of the target order according to the invoicing information. In turn, the back office 104 associates the electronic invoice with the access token for invoice management of the electronic invoice for the target order via the access token. Therefore, the background can manage the electronic invoice of the target order of the consumer through the access token for authorizing the third-party application to access without using the user information of the consumer, so that the management of the background on the order of the non-member consumer is realized, and the management of the background on the electronic invoice of the non-member system is expanded.

The management method of the electronic invoice provided by the application can also be applied to the application scene shown in fig. 2. As shown in fig. 2, the application scenario includes a merchant billing subsystem, a third-party application, an invoice pre-billing subsystem, an invoice billing subsystem, and the like. The invoice pre-issuing subsystem and the invoice issuing subsystem are systems arranged in the background 104. A third party application on the terminal 102 is used to manage electronic invoices issued by the user. The merchant billing subsystem is used for providing order information of the target order to the user, so that the user can send a billing request to the background 104 through the third-party application to request to bill the electronic invoice of the target order. Specifically, as shown in FIG. 2, the user is a consumer. The merchant billing subsystem prints the receipt of the target order and delivers the receipt to the consumer; the consumer uses a third-party application to scan the two-dimensional code in the receipt to obtain order information of the target order; the consumer uses the third party application to submit the invoicing application to the invoice pre-issuing subsystem; the consumer views and manages the invoice information of the electronic invoice returned by the invoice pre-issuing subsystem through the third-party application. For information interaction between systems or devices in the application scenario shown in fig. 2, reference may also be made to the following detailed description of a method for managing an electronic invoice in various embodiments.

In one embodiment, as shown in fig. 3, a method for managing electronic invoices is provided, which is described by taking the method as an example applied to the background in fig. 1. The background comprises an invoice pre-issuing subsystem and an invoice issuing subsystem. The electronic invoice management method comprises the following steps:

s302, receiving a billing request containing the access token sent by the third-party application, wherein the billing request is used for requesting to bill the electronic invoice of the target order.

In this embodiment, the user sends a billing request to the invoice pre-billing subsystem through a third-party application on the terminal to request the electronic invoice for the target order. The billing request includes an access token. The access token is used to identify the third party application as an application for which access has been granted. Specifically, the invoice pre-issuing subsystem generates an access token and issues the access token to the terminal. And the third-party application on the terminal packages the access token into the invoicing request, so that the invoicing subsystem can identify the third application as the application authorized to be accessed according to the access token in the invoicing request.

S304, when the third-party application is identified as the application authorized to be accessed according to the access token, generating a billing page of the target order according to the billing request, and issuing the billing page to the third-party application.

In this embodiment, the invoice pre-billing subsystem analyzes the billing request to obtain the access token in the billing request. Further, an access token is identified. And when the third-party application is identified as the application authorized to be accessed according to the access token, generating an invoicing page of the target order according to the invoicing request. The invoicing request is used for requesting to invoice the electronic invoice of the target order, and an invoicing page of the target order can be generated according to the invoicing request. The invoice pre-issuing subsystem may be preset with a first general template of an invoice issuing page, and general information for issuing the electronic invoice, such as general field information of "tax payment number", "new line", "address", and "contact call" in the electronic invoice, is set in the first general template. When the invoicing request is received, acquiring data information of the target order for filling in the electronic invoice according to the target order indicated in the invoicing request, and filling the data information into the first general template to generate an invoicing page of the target order. The data information of the target order for filling in the electronic invoice can include basic information of an invoicing enterprise, transaction data, invoicing items and the like. For example, the billing page may be an HTML5 (hypertext 5.0) page form, and the HTML5 page form includes billing enterprise basic information, transaction data, billing items. And further, issuing an invoicing page to the third-party application.

And S306, receiving the invoicing information in the invoicing page sent by the third-party application, and generating an electronic invoice of the target order according to the invoicing information.

In this embodiment, when the third-party application receives the billing page, the billing page is displayed at the terminal. And filling out the invoicing information of the electronic invoice on the invoicing page by the user. Such as head-up information and tax payment number information. And further, the third-party application sends the invoicing information in the invoicing page to the invoicing subsystem. As shown in fig. 2, the invoicing subsystem sends invoicing data containing invoicing information to the invoicing subsystem through message middleware, so that the invoicing subsystem generates an electronic invoice of the target order according to the invoicing data. Specifically, the invoice issuing subsystem presets a second general template of the electronic type invoice, and a general plate type of the electronic type invoice is set in the second general template, as shown in fig. 4. And the invoice issuing subsystem fills various information in the invoice data into the second universal template so as to generate the electronic invoice of the target order. Further, the invoicing subsystem feeds back electronic invoices to the invoicing subsystem.

And S308, associating the electronic invoice with the access token so as to manage the electronic invoice of the target order through the access token.

In this embodiment, the invoice pre-invoice subsystem associates an electronic invoice for the target order with the access token. The invoice pre-issuing subsystem can query the electronic invoice of the target order through the incidence relation of the access token, so that invoice management can be carried out on the electronic invoice of the target order through the access token. Furthermore, the access token is used to identify the third party application as an application for which access is authorized, whereby the invoicing subsystem manages the third party application via the access token. When the third-party application carries the access token to access the invoice pre-billing subsystem, the invoice pre-billing subsystem inquires the electronic invoice of the target order according to the access token. For non-member users, the third-party application can be directly used for directly applying for issuing the electronic invoice of the target order, and the electronic invoice of the target order can be inquired from the invoice pre-issuing subsystem through the third-party application. The invoice pre-issuing subsystem performs invoice management on the electronic invoice of the target order through the access token associated with the third-party application, and can query the electronic invoice of the target order of the third-party application through the access token and return invoice information of the electronic invoice to the third-party application. Therefore, the management of the background on the orders of the non-member users is realized, and the management of the background on the electronic invoices of the non-member system is expanded.

The management method of the electronic invoice comprises the steps of receiving an invoicing request containing an access token and sent by a third-party application, wherein the invoicing request is used for requesting to invoice the electronic invoice of a target order, generating an invoicing page of the target order according to the invoicing request when the third-party application is identified to be an authorized application according to the access token, issuing the invoicing page to the third-party application, receiving invoicing information in the invoicing page sent by the third-party application, generating the electronic invoice of the target order according to the invoicing information, associating the electronic invoice with the access token, and carrying out invoice management on the electronic invoice of the target order through the access token. Therefore, the background can manage the electronic invoice of the target order of the consumer through the access token for authorizing the third-party application to access without using the user information of the consumer, so that the management of the background on the order of the non-member consumer is realized, and the management of the background on the electronic invoice of the non-member system is expanded.

In one implementation, before the step of receiving the invoicing request including the access token sent by the third-party application, the method further includes: when receiving a billing authority request sent by a third-party application, acquiring a user name of the third-party application and a key corresponding to the user name, wherein the billing authority request is used for requesting the authority of issuing an electronic invoice of a target order; and obtaining an access token according to the user name and the key, and sending the access token to the third-party application.

In this embodiment, the access token is obtained by the invoice pre-issuing subsystem according to the user name of the third-party application and the key corresponding to the user name. The invoicing subsystem identifies the third party application as an application for which access is authorized by means of the access token. And when the third-party application sends the invoicing application request to the invoicing subsystem for the first time, the invoicing subsystem sends the access token to the third-party application. That is, in the first invoicing application request, the third-party application sends an invoicing permission request to the invoice pre-invoicing subsystem. The invoicing authority request is used for requesting the electronic invoice authority of the target order from the invoice pre-invoicing subsystem. At the moment, the invoice pre-issuing subsystem acquires a user name of the third-party application and a key corresponding to the user name, and acquires an access token according to the user name of the third-party application and the key corresponding to the user name. The access token of the third-party application may be generated according to the user name of the third-party application and the key corresponding to the user name to obtain the access token. The invoice pre-issuing subsystem may further include a plurality of access tokens, allocate the access tokens to the third-party application according to the user name of the third-party application and the key corresponding to the user name, associate the access tokens with the user name of the third-party application and the key corresponding to the user name, and obtain the corresponding access tokens through the user name of the third-party application and the key corresponding to the user name. Further, the third party application may encapsulate the access token in a subsequent invoicing request for issuing the electronic invoice, so that the invoice pre-issuing subsystem responds to the invoicing request based on the access token, and issues the electronic invoice corresponding to the invoicing request. For example, the third party application encapsulates the access token in a subsequent invoicing request for issuing an electronic invoice for the target order, so that the invoice pre-issuing subsystem responds to the invoicing request based on the access token and issues the electronic invoice for the target order corresponding to the invoicing request. Therefore, the electronic invoice of the target order of the user of the third-party application can be managed based on the access token, so that the order of the non-member consumer is managed by the background, and the management of the electronic invoice of the non-member system by the background is expanded.

In an embodiment, after the step of associating the electronic invoice with the access token, the method further includes: sending prompt information representing the success of issuing the electronic invoice to a third-party application; when receiving an invoice lookup request sent by a third-party application, if the invoice lookup request contains an access token, acquiring invoice information of the electronic invoice according to the access token, and issuing the invoice information of the electronic invoice to the third-party application.

In this embodiment, after the invoice pre-issuing subsystem obtains the generated electronic issuing of the target order, a prompt message indicating that the electronic invoice is successfully issued is sent to the third-party application. When the user inquires the issued electronic invoice through the third-party application, the third-party application sends an invoice inquiry request to the invoice pre-issuing subsystem. And if the invoice pre-issuing subsystem detects that the invoice lookup request contains the access token, the third party application issues the invoice information of the electronic invoice. For example, referring to FIG. 5, a consumer views an electronic invoice requested using a third party application, via an authorized access token as a query credential, and via a remote service invocation interface requesting an invoice preforging subsystem. The invoice pre-issuing subsystem inquires the electronic invoice applied by the consumer according to the binding relationship between the access token and the electronic invoice of the target order when applying for issuing the invoice, acquires related information such as invoice data, format files and order information, and writes the related information into an invoice detail page. The invoice detail page is then returned to the third party application. Therefore, the third-party application and the electronic invoice of the user in the background are bound through the access token, the background can manage the electronic invoice of the user without user information, and the user can inquire the electronic invoice of the user without registration information.

In an embodiment, after the step of associating the electronic invoice with the access token, the method further includes: receiving a new line replacement request sent by a third-party application, wherein the new line replacement request is used for requesting to replace the invoice new line of the electronic invoice; when the access token in the head-up replacement request is identified, issuing a head-up replacement page to the third-party application; and receiving the invoice new head sent by the third-party application in the new head replacement page, replacing the invoice new head in the electronic invoice with the replaced invoice new head to obtain the replaced electronic invoice, and associating the replaced electronic invoice with the access token.

Preferably, after the step of obtaining the replaced electronic invoice, the method further includes: the electronic invoice before replacement is punched; and issuing the invoice information of the replaced electronic invoice to a third-party application.

In this embodiment, the back-office provides a new-line service for electronic invoices that have been issued. The invoice pre-issuing subsystem which can be a background provides the head-up replacement service of issued electronic invoices. As shown in fig. 6, a third party application provides a component for replacing heads. The user can send a head-up replacement request to the background by triggering the head-up replacement component. And when the background identifies the access token in the new line replacement request, issuing a new line replacement page to the third-party application. An editable component is provided in the new header replacement page, and the editable component is used for receiving the new invoice edited by the user. And/or, providing a replaceable invoice in a head-up replacement page. And the user selects the corresponding replaced invoice to raise the head in a triggering mode. The new head of the changed invoice can be determined through the new head change page. And the background replaces the original invoice of the electronic invoice with the replaced invoice to obtain the replaced electronic invoice, and associates the replaced electronic invoice with the access token. Therefore, when the third-party application inquires the replaced electronic invoice, the background can inquire the replaced electronic invoice through the access token. And further, the background carries out cancellation on the electronic invoice before replacement and issues invoice information of the replaced electronic invoice to a third-party application. Therefore, the new head of the issued electronic invoice can be replaced, and the use requirements of users are met.

It should be noted that, in the conventional way of issuing electronic invoices, a way of replacing the electronic invoices in a new line is not provided. If the electronic invoice needs to be replaced, the user needs to contact the customer service to manually modify the electronic invoice by the customer service, so as to obtain the replaced electronic invoice. In this embodiment, a service is provided in which the user provides self-service head-up replacement. A user can initiate a head-up replacement request for replacing the head-up of the electronic invoice to the background through the third-party application, and the background provides a service for replacing the head-up of the invoice for the third-party application. Therefore, the automatic invoice head-up replacement operation of the electronic invoice is realized.

In an embodiment, before the step of issuing the new page to the third-party application, the method further includes: identifying first order information of the electronic invoice according to the new head replacement request; inquiring the head-up replacement times of the electronic invoice recorded in the head-up replacement record table according to the first order information; when the number of times of head-up replacement is greater than the preset number of times, issuing prompt information representing failure of head-up replacement of the electronic invoice to a third-party application; and when the head-up replacement frequency is less than or equal to the preset frequency, the step of issuing a head-up replacement page to a third-party application is carried out.

In this embodiment, the invoice pre-issuing subsystem limits the number of times of head-up replacement of the electronic invoice in the self-service invoice head-up replacement service provided by the user. Specifically, preset times are preset, and the preset times are used for limiting the number of times of head-up replacement of the electronic invoice. The invoice pre-issuing subsystem records the head-up replacement times of each issued electronic invoice through a head-up replacement record table. The number of times of head-up replacement of the electronic invoices is associated with the order information of each electronic invoice. The invoice pre-issuing subsystem identifies first order information of the electronic invoice according to the head-up replacement request, and then inquires the head-up replacement times of the electronic invoice recorded in the head-up replacement record table according to the first order information. And when the number of times of head-up replacement is less than or equal to the preset number of times, entering a step of issuing a head-up replacement page to a third-party application so as to continuously execute the operation of invoice head-up replacement. Otherwise, prompt information representing the head-up replacement failure of the electronic invoice is sent.

Particularly, the invoice head-up is indispensable as an important component element of the electronic invoice, and the invoice head-up selected by a consumer for issuing the electronic invoice is usually more concentrated on a certain number of invoice head-up. Meanwhile, the action of raising the head of the changed invoice is a very common operation of changing the invoice in the invoice field. For example, referring to the flow shown in fig. 7, for an electronic invoice that has been issued, a self-service function of replacing the invoice head-up is provided for the consumer. And the consumer clicks a change head-up button in the third-party application, and the front end sends a head-up change request to the invoice pre-issuing subsystem. In order to prevent the consumer from maliciously and unlimitedly replacing the heads, the electronic invoice is pulled out, and the invoice pre-issuing subsystem limits the times of self-help head-up replacement of a single electronic invoice of the consumer by utilizing the configuration of the unified configuration management platform. The invoice pre-opening subsystem inquires a head-up changing record table according to order information after receiving a head-up changing application request of a consumer, checks whether the head-up changing times of the consumer exceeds the limit, and returns front-end description information that the head-up changing times are over the limit and self-service replacement is not allowed if the head-up changing times are over, and requests a service desk if the head-up changing times need to be replaced if the head-up changing times are over. If the invoice is not over-limit, returning to replace the head-up page, editing the head-up information by the consumer, and submitting the invoice application to the invoice pre-issuing subsystem again.

The invoice pre-issuing subsystem receives the application submitted by the consumer to replace the platform head, stores the application into the head-up-replacing record list, flushes and sells the original electronic invoice, updates the state of the original electronic invoice into the flushed and sold state, and issues the electronic invoice for replacing the head-up invoice. The consumer can look up the new invoice information by the invoice inquiry list.

In an embodiment, after the step of generating the electronic invoice of the target order according to the invoicing information, the method further includes: receiving a paper invoice replacement request sent by a third-party application, wherein the paper invoice replacement request is used for requesting to replace an electronic invoice with a paper invoice; when the access token in the paper invoice replacement request is identified, storing second order information of the electronic invoice into a billing pool of the paper invoice, wherein the billing pool of the paper invoice is used for storing the order information of the paper invoice to be billed; and (5) the electronic invoice is punched and sold.

Electronic invoices are a new invoice form, and some consumers do not accept the electronic invoices. Meanwhile, some enterprises need value-added tax special invoices for verification and sale, and electronic invoices cannot be verified and sold. Therefore, the function of exchanging the paper invoice for the electronic invoice is very important. In the embodiment, the value-added tax common paper invoice is exchanged by self. As shown in fig. 6, a component in the third party application is provided to replace the paper invoice. The user can realize sending paper invoice change request to the back platform through triggering the subassembly of changing the paper invoice. And when the background identifies the access token in the paper invoice replacement request, storing the second order information of the electronic invoice into a billing pool of the paper invoice so as to read the second order information from the billing pool and issue the paper invoice corresponding to the electronic invoice based on the second order information. Wherein the first order information may be the same as the second order information. Meanwhile, the electronic invoice is punched and sold. In addition, when the access token in the paper invoice replacement request is identified, a replacement page of the paper invoice can be issued to the third-party application, the replacement page of the paper invoice is used for receiving mailing information of the paper invoice input by the user, and the replacement page of the paper invoice is shown in fig. 8. And after the background receives the mailing information of the paper invoice sent by the third-party application, associating the mailing information of the paper invoice with the second order information in the invoicing pool so as to inquire the mailing information of the paper invoice through the second order information after the paper invoice is invoiced.

See, for example, the flow chart in fig. 9. For the issued electronic invoice, a self-service function of exchanging paper invoices is provided for consumers. And the consumer clicks a paper invoice replacing button in the third-party application, the front end sends an application request for replacing the paper invoice to the invoice pre-issuing subsystem, and the invoice pre-issuing subsystem inquires an invoice replacing record according to the second order information of the electronic invoice and checks whether the target order is replaced by the paper invoice. If the paper invoice is replaced, the front-end description information is returned, and the invoice is replaced by the paper invoice and cannot be replaced again. And if the paper invoice is not exchanged, returning to the front end to exchange the paper invoice page, and submitting a paper invoice exchange request after the customer fills in the mailing information of the paper invoice.

The invoice pre-issuing subsystem receives a paper invoice replacing request submitted by the front end, then stores the paper invoice replacing request into the invoice replacing record list, and flushes and sells the original electronic invoice, and the state of the original electronic invoice is updated to be flushed and sold. And storing the second order information exchanged with the paper invoice into a billing pool of the paper invoice. The financial invoicer inquires the order information of the paper invoice through the invoicing pool of the invoice pre-invoicing subsystem, and mails the invoice according to the mailing information submitted by the consumer after the paper invoice is opened online.

It should be noted that, in the conventional way of issuing an electronic invoice, a way of replacing a paper invoice with the electronic invoice is not provided. If the paper invoice of the electronic invoice needs to be replaced, the user needs to contact the customer service to manually handle the paper invoice by the customer service, so that the paper invoice is obtained. In the embodiment, the service that the user provides self-service replacement of the paper invoice is provided. The user can initiate a request for replacing the paper invoice of the electronic invoice to the background through the third-party application, and the background provides a service for replacing the paper invoice for the third-party application. Therefore, the operation of automatically replacing the paper invoice for the electronic invoice is realized.

In an embodiment, before the step of receiving an invoicing request sent by a third-party application, the method further includes: receiving order information to be placed of a target order sent by an order placing system; generating an identification code of the target order; generating first encryption information of an identification code according to the order information to be made and by adopting a random salt value; encrypting the identification code by adopting first encryption information to obtain an encrypted identification code; and issuing the encrypted identification code to the order opening system. The step of receiving an invoicing request sent by a third-party application includes: and receiving an invoicing request sent by the third-party application, wherein the invoicing request is obtained by scanning the encrypted identification code provided by the order issuing system through the third-party application. After the step of receiving the invoicing request sent by the third-party application, the method further includes: and extracting second encryption information from the invoicing request, and if the second encryption information is matched with the first encryption information, issuing an invoicing page to a third-party application according to the invoicing request.

In the embodiment, the process of issuing the electronic invoice of the target order is subjected to data encryption by means of identification code encryption. And the order placing system sends the information of the order to be placed of the target order to the background. And the background generates an identification code of the target order according to the information of the order to be opened of the target order. Wherein, the identification code can be a two-dimensional code. Further, first encryption information of the identification code is generated according to the information of the order to be made and by adopting the random salt value. And then, the identification code is encrypted by adopting the first encryption information to obtain the encrypted identification code. The encrypted identification code contains first encryption information. And finally, the background issues the encrypted identification code to the order opening system. And the user scans the encrypted identification code by adopting a third-party application to obtain first encryption information and order information of the target order. Furthermore, the third party application sends an invoicing request to the background, wherein the invoicing request comprises second encryption information. Typically, the second encryption information is the same as the first encryption information. And the background extracts the second encryption information from the billing request and performs matching identification on the second encryption information and the first encryption information generated by the background. When the second encryption information is the same as the first encryption information, the second encryption information matches the first encryption information. And the background executes the operation step of issuing the invoicing page to the third-party application according to the invoicing request. In another implementation, the encrypted identification code includes information associated with the first encryption information. And finally, the background issues the encrypted identification code to the order opening system. And the user scans the encrypted identification code by adopting a third-party application to obtain the associated information of the first encrypted information and the order information of the target order. Furthermore, the third party application sends an invoicing request to the background, wherein the invoicing request comprises second encryption information. In this case, the second encryption information includes information related to the first encryption information. And the background extracts the second encryption information from the billing request and performs matching identification on the second encryption information and the first encryption information generated by the background. And if the matching identification result is that the first encryption information and the second encryption information are related, matching the second encryption information with the first encryption information.

See, for example, fig. 10. The order issuing system is an issuing subsystem of the merchant, and the identification code is a two-dimensional code. The consumer places an order, and the billing subsystem of the merchant pushes the order information of the target order to the invoice pre-billing subsystem through the remote service calling interface; and after the invoice pre-issuing subsystem receives the information of the order to be issued of the target order, the signature field of the two-dimensional code is generated by using the random salt value and the information of the order to be issued in an encryption mode based on the information of the order to be issued. The signature field is used for preventing network attack, so that the safety of the two-dimension code information is ensured. Wherein the random salt value is a randomly generated irregular character. And finally, the two-dimensional code link is sent to an invoicing subsystem of the merchant. And the billing subsystem of the merchant prints the shopping receipt with the two-dimensional code image and delivers the shopping receipt to the consumer. The consumer obtains the encrypted information in the two-dimensional code by scanning the two-dimensional code, and then packages the encrypted information into the invoicing request, so that the invoice pre-issuing subsystem can conveniently identify the invoicing request through the encrypted information in the invoicing request, and then issue an electronic invoice of a target order.

The electronic invoice management method can realize the management of the electronic invoice of the non-member user by the background. For example, a user scans codes and issues tickets based on a third-party application, offline code scanning and issuing scenes are enriched, the defect that electronic invoices of a traditional code scanning and issuing non-member system cannot be uniformly managed is overcome, and collection management of the electronic invoices of the non-member system is achieved by adopting an access token authorized by the third-party application. In addition, self-service of the electronic invoice of the user side is enriched. In particular, compared with traditional code scanning and billing, the third-party application provides abundant self-service services for users. The method has the advantages that functions of changing invoice head-up, downloading format files of electronic invoices, sending invoicing results, integrating with third-party application and the like are included, user experience is improved, working pressure of counter personnel is reduced, tax risks are reduced, and labor cost is reduced.

It should be understood that, although the steps in the flowchart are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

The application also provides a management device of the electronic invoice. As shown in fig. 11, a management apparatus for electronic invoices includes a receiving module 112, a sending module 114, a generating module 116, and a management module 118. The receiving module 112 is used for receiving an invoicing request which is sent by a third-party application and contains an access token, wherein the invoicing request is used for requesting to invoice an electronic invoice of a target order; the issuing module 114 is configured to generate an invoicing page of the target order according to the invoicing request and issue the invoicing page to the third-party application when the third-party application is identified as an application authorized to be accessed according to the access token; the generating module 116 is configured to receive invoicing information in an invoicing page sent by a third-party application, and generate an electronic invoice of a target order according to the invoicing information; and the management module 118 is used for associating the electronic invoice with the access token so as to perform invoice management on the electronic invoice of the target order through the access token.

In an embodiment, the device for managing electronic invoices further comprises a first sending module, configured to obtain a user name and a key corresponding to the user name of a third-party application when receiving a request for permission to invoice sent by the third-party application, where the request for permission to invoice an electronic invoice in a target order is used to request permission to invoice; and obtaining an access token according to the user name and the key, and sending the access token to the third-party application.

In an embodiment, the management device for the electronic invoice further comprises a second sending module, configured to send, to a third-party application, a prompt message indicating that the electronic invoice is successfully issued; when receiving an invoice lookup request sent by a third-party application, if the invoice lookup request contains an access token, acquiring invoice information of the electronic invoice according to the access token, and issuing the invoice information of the electronic invoice to the third-party application.

In an embodiment, the management device for the electronic invoices further comprises a first replacement module, a second replacement module and a third-party application module, wherein the first replacement module is used for receiving a new-heading replacement request sent by the third-party application, and the new-heading replacement request is used for requesting to replace the invoice new-heading of the electronic invoices; when the access token in the head-up replacement request is identified, issuing a head-up replacement page to the third-party application; and receiving the invoice new head sent by the third-party application in the new head replacement page, replacing the invoice new head in the electronic invoice with the replaced invoice new head to obtain the replaced electronic invoice, and associating the replaced electronic invoice with the access token. Preferably, after the replaced electronic invoice is obtained, the method further comprises: the electronic invoice before replacement is punched; and issuing the invoice information of the replaced electronic invoice to a third-party application.

In an embodiment, the management device for the electronic invoice further comprises a judging module, a head-up replacing module and a data processing module, wherein the judging module is used for identifying first order information of the electronic invoice according to the head-up replacing request; inquiring the head-up replacement times of the electronic invoice recorded in the head-up replacement record table according to the first order information; when the number of times of head-up replacement is greater than the preset number of times, issuing prompt information representing failure of head-up replacement of the electronic invoice to a third-party application; and when the head-up replacement frequency is less than or equal to the preset frequency, the step of issuing a head-up replacement page to a third-party application is carried out.

In an embodiment, the management device for the electronic invoice further comprises a second replacement module, configured to receive a paper invoice replacement request sent by a third-party application, where the paper invoice replacement request is used to request to replace the electronic invoice with a paper invoice; when the access token in the paper invoice replacement request is identified, storing second order information of the electronic invoice into a billing pool of the paper invoice, wherein the billing pool of the paper invoice is used for storing the order information of the paper invoice to be billed; and (5) the electronic invoice is punched and sold.

In an embodiment, the management apparatus for electronic invoices further comprises an encryption module, configured to receive order information to be placed of a target order sent by an order placing system; generating an identification code of the target order; generating first encryption information of an identification code according to the order information to be made and by adopting a random salt value; encrypting the identification code by adopting first encryption information to obtain an encrypted identification code; and issuing the encrypted identification code to the order opening system. The receiving module 112 is specifically configured to receive an invoicing request sent by a third-party application, where the invoicing request is obtained by scanning, by the third-party application, an encrypted identification code provided by the order issuing system. The management device of the electronic invoice further comprises a matching module, wherein the matching module is used for extracting second encryption information from the invoicing request, and if the second encryption information is matched with the first encryption information, the step of issuing an invoicing page to a third-party application according to the invoicing request is carried out.

For specific limitations of the management device of the electronic invoice, reference may be made to the above limitations of the management method of the electronic invoice, which are not described herein again. The modules in the management device of the electronic invoice can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server supporting a backend system, and its internal structure diagram may be as shown in fig. 12. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile 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 an operating system and computer programs in the non-volatile storage medium. The network interface of the computer equipment is used for being connected with an external terminal so as to receive order information of a target order sent by a third-party application on the terminal and a request related to an electronic invoice of the sent target order. The computer program is executed by a processor to implement a method of managing electronic invoices.

Those skilled in the art will appreciate that the architecture shown in fig. 12 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: receiving a billing request containing an access token sent by a third-party application, wherein the billing request is used for requesting to bill an electronic invoice of a target order; when the third-party application is identified as the application authorized to be accessed according to the access token, generating a billing page of the target order according to the billing request, and issuing the billing page to the third-party application; receiving invoicing information in an invoicing page sent by a third-party application, and generating an electronic invoice of a target order according to the invoicing information; and associating the electronic invoice with the access token so as to manage the electronic invoice of the target order through the access token.

In one embodiment, the processor, when executing the computer program, performs the steps of: when receiving a billing authority request sent by a third-party application, acquiring a user name of the third-party application and a key corresponding to the user name, wherein the billing authority request is used for requesting the authority of issuing an electronic invoice of a target order; and obtaining an access token according to the user name and the key, and sending the access token to the third-party application.

In one embodiment, the processor, when executing the computer program, performs the steps of: sending prompt information representing the success of issuing the electronic invoice to a third-party application; when receiving an invoice lookup request sent by a third-party application, if the invoice lookup request contains an access token, acquiring invoice information of the electronic invoice according to the access token, and issuing the invoice information of the electronic invoice to the third-party application.

In one embodiment, the processor, when executing the computer program, performs the steps of: receiving a new line replacement request sent by a third-party application, wherein the new line replacement request is used for requesting to replace the invoice new line of the electronic invoice; when the access token in the head-up replacement request is identified, issuing a head-up replacement page to the third-party application; and receiving the invoice new head sent by the third-party application in the new head replacement page, replacing the invoice new head in the electronic invoice with the replaced invoice new head to obtain the replaced electronic invoice, and associating the replaced electronic invoice with the access token. Preferably, after the replaced electronic invoice is obtained, the method further comprises: the electronic invoice before replacement is punched; and issuing the invoice information of the replaced electronic invoice to a third-party application.

In one embodiment, the processor, when executing the computer program, performs the steps of: identifying first order information of the electronic invoice according to the new head replacement request; inquiring the head-up replacement times of the electronic invoice recorded in the head-up replacement record table according to the first order information; when the number of times of head-up replacement is greater than the preset number of times, issuing prompt information representing failure of head-up replacement of the electronic invoice to a third-party application; and when the head-up replacement frequency is less than or equal to the preset frequency, the step of issuing a head-up replacement page to a third-party application is carried out.

In one embodiment, the processor, when executing the computer program, performs the steps of: receiving a paper invoice replacement request sent by a third-party application, wherein the paper invoice replacement request is used for requesting to replace an electronic invoice with a paper invoice; when the access token in the paper invoice replacement request is identified, storing second order information of the electronic invoice into a billing pool of the paper invoice, wherein the billing pool of the paper invoice is used for storing the order information of the paper invoice to be billed; and (5) the electronic invoice is punched and sold.

In one embodiment, the processor, when executing the computer program, performs the steps of: receiving order information to be placed of a target order sent by an order placing system; generating an identification code of the target order; generating first encryption information of an identification code according to the order information to be made and by adopting a random salt value; encrypting the identification code by adopting first encryption information to obtain an encrypted identification code; and issuing the encrypted identification code to the order opening system. When the processor executes the computer program to realize the step of receiving the invoicing request sent by the third-party application, the following steps are specifically realized: and receiving an invoicing request sent by the third-party application, wherein the invoicing request is obtained by scanning the encrypted identification code provided by the order issuing system through the third-party application. The processor, when executing the computer program, implements the steps of: and extracting second encryption information from the invoicing request, and if the second encryption information is matched with the first encryption information, issuing an invoicing page to a third-party application according to the invoicing request.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving a billing request containing an access token sent by a third-party application, wherein the billing request is used for requesting to bill an electronic invoice of a target order; when the third-party application is identified as the application authorized to be accessed according to the access token, generating a billing page of the target order according to the billing request, and issuing the billing page to the third-party application; receiving invoicing information in an invoicing page sent by a third-party application, and generating an electronic invoice of a target order according to the invoicing information; and associating the electronic invoice with the access token so as to manage the electronic invoice of the target order through the access token.

In one embodiment, the computer program when executed by the processor implements the steps of: when receiving a billing authority request sent by a third-party application, acquiring a user name of the third-party application and a key corresponding to the user name, wherein the billing authority request is used for requesting the authority of issuing an electronic invoice of a target order; and obtaining an access token according to the user name and the key, and sending the access token to the third-party application.

In one embodiment, the computer program when executed by the processor implements the steps of: sending prompt information representing the success of issuing the electronic invoice to a third-party application; when receiving an invoice lookup request sent by a third-party application, if the invoice lookup request contains an access token, acquiring invoice information of the electronic invoice according to the access token, and issuing the invoice information of the electronic invoice to the third-party application.

In one embodiment, the computer program when executed by the processor implements the steps of: receiving a new line replacement request sent by a third-party application, wherein the new line replacement request is used for requesting to replace the invoice new line of the electronic invoice; when the access token in the head-up replacement request is identified, issuing a head-up replacement page to the third-party application; and receiving the invoice new head sent by the third-party application in the new head replacement page, replacing the invoice new head in the electronic invoice with the replaced invoice new head to obtain the replaced electronic invoice, and associating the replaced electronic invoice with the access token. Preferably, after associating the electronic invoice with the access token, the method further comprises: the electronic invoice before replacement is punched; and issuing the invoice information of the replaced electronic invoice to a third-party application.

In one embodiment, the computer program when executed by the processor implements the steps of: identifying first order information of the electronic invoice according to the new head replacement request; inquiring the head-up replacement times of the electronic invoice recorded in the head-up replacement record table according to the first order information; when the number of times of head-up replacement is greater than the preset number of times, issuing prompt information representing failure of head-up replacement of the electronic invoice to a third-party application; and when the head-up replacement frequency is less than or equal to the preset frequency, the step of issuing a head-up replacement page to a third-party application is carried out.

In one embodiment, the computer program when executed by the processor implements the steps of: receiving a paper invoice replacement request sent by a third-party application, wherein the paper invoice replacement request is used for requesting to replace an electronic invoice with a paper invoice; when the access token in the paper invoice replacement request is identified, storing second order information of the electronic invoice into a billing pool of the paper invoice, wherein the billing pool of the paper invoice is used for storing the order information of the paper invoice to be billed; and (5) the electronic invoice is punched and sold.

In one embodiment, the computer program when executed by the processor implements the steps of: receiving order information to be placed of a target order sent by an order placing system; generating an identification code of the target order; generating first encryption information of an identification code according to the order information to be made and by adopting a random salt value; encrypting the identification code by adopting first encryption information to obtain an encrypted identification code; and issuing the encrypted identification code to the order opening system. When the computer program is executed by the processor to implement the step of receiving the invoicing request sent by the third-party application, the following steps are specifically implemented: and receiving an invoicing request sent by the third-party application, wherein the invoicing request is obtained by scanning the encrypted identification code provided by the order issuing system through the third-party application. The computer program when executed by a processor implements the steps of: and extracting second encryption information from the invoicing request, and if the second encryption information is matched with the first encryption information, issuing an invoicing page to a third-party application according to the invoicing request.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method of managing electronic invoices, the method comprising:

receiving an invoicing request containing an access token and sent by a third-party application, wherein the invoicing request is used for requesting to invoice an electronic invoice of a target order;

when the third-party application is identified as an application authorized to be accessed according to the access token, generating an invoicing page of the target order according to the invoicing request, and issuing the invoicing page to the third-party application;

receiving invoicing information in the invoicing page sent by the third-party application, and generating an electronic invoice of the target order according to the invoicing information;

and associating the electronic invoice with the access token so as to perform invoice management on the electronic invoice of the target order through the access token.

2. The method of claim 1, further comprising:

when receiving a billing authority request sent by the third-party application, acquiring a user name of the third-party application and a key corresponding to the user name, wherein the billing authority request is used for requesting authority of issuing an electronic invoice of the target order;

and obtaining the access token according to the user name and the secret key, and sending the access token to the third-party application.

3. The method of claim 1, wherein, after associating the electronic invoice with the access token, further comprising:

sending prompt information representing that the electronic invoice is successfully issued to the third-party application;

when receiving an invoice inquiry request sent by the third-party application, if the invoice inquiry request contains the access token, acquiring invoice information of the electronic invoice according to the access token, and issuing the invoice information of the electronic invoice to the third-party application.

4. The method of claim 1, wherein, after associating the electronic invoice with the access token, further comprising:

receiving a new line replacement request sent by the third-party application, wherein the new line replacement request is used for requesting to replace the invoice new line of the electronic invoice;

when the access token in the new line replacement request is identified, issuing a new line replacement page to the third-party application;

receiving the invoice new line sent by the third-party application in a new line replacement page, replacing the invoice new line in the electronic invoice with the replaced invoice new line to obtain a replaced electronic invoice, and associating the replaced electronic invoice with the access token;

preferably, after the obtaining of the replaced electronic invoice, the method further includes:

the electronic invoice before replacement is subjected to offset;

and issuing the invoice information of the replaced electronic invoice to the third-party application.

5. The method of claim 4, wherein prior to issuing the new page to the third-party application, further comprising:

identifying first order information of the electronic invoice according to the head-up replacement request;

inquiring the head-up replacement times of the electronic invoice recorded in a head-up replacement record table according to the first order information;

when the number of times of head-up replacement is greater than the preset number of times, issuing prompt information representing failure of head-up replacement of the electronic invoice to the third-party application;

and when the head-up replacement frequency is less than or equal to the preset frequency, the step of issuing a head-up replacement page to the third-party application is carried out.

6. The method according to claim 1, further comprising, after generating an electronic invoice for the target order based on the billing information:

receiving a paper invoice replacement request sent by the third-party application, wherein the paper invoice replacement request is used for requesting to replace the electronic invoice with a paper invoice;

when the access token in the paper invoice replacement request is identified, storing second order information of the electronic invoice into a billing pool of the paper invoice, wherein the billing pool of the paper invoice is used for storing the order information of the paper invoice to be billed;

and carrying out punching and selling on the electronic invoice.

7. The method of claim 1, wherein before receiving the invoice request sent by the third-party application, the method further comprises:

receiving the information of the target order to be placed, which is sent by the order placing system;

generating an identification code of the target order;

generating first encryption information of the identification code according to the to-be-opened order information and by adopting a random salt value;

encrypting the identification code by adopting the first encryption information to obtain an encrypted identification code;

issuing the encrypted identification code to the order opening system;

the receiving of the invoicing request sent by the third-party application comprises: receiving an invoicing request sent by a third party application, wherein the invoicing request is obtained by scanning the encrypted identification code provided by the order issuing system through the third party application;

the method further comprises the following steps: and extracting second encryption information from the invoicing request, and if the second encryption information is matched with the first encryption information, issuing an invoicing page to the third-party application according to the invoicing request.

8. An apparatus for managing electronic invoices, the apparatus comprising:

the receiving module is used for receiving a billing request containing an access token, which is sent by a third-party application, wherein the billing request is used for requesting to bill an electronic invoice of a target order;

the issuing module is used for generating an invoicing page of the target order according to the invoicing request and issuing the invoicing page to the third-party application when the third-party application is identified as an application authorized to be accessed according to the access token;

the generating module is used for receiving the invoicing information in the invoicing page sent by the third-party application and generating an electronic invoice of the target order according to the invoicing information;

and the management module is used for associating the electronic invoice with the access token so as to manage the electronic invoice of the target order through the access token.

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 7 are implemented when the computer program is executed by the processor.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.