Invoice issuing method and device, electronic equipment and computer storage medium

Abstract

The embodiment of the invention provides an invoice issuing method and device, electronic equipment and a computer storage medium, and the method comprises the steps: obtaining order data, and generating an invoice link according to the order data; responding to the invoice link triggered by the user, and obtaining an invoice title; and issuing an invoice according to the invoice title and the order data. By applying the invoice issuing method provided by the embodiment of the invention, the invoice can be automatically issued according to the selection of the user after the consumption of the user is completed, the docking difficulty and cost between systems are reduced, the invoice is issued without the operation of a merchant, and the invoice issuing efficiency is relatively high.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data processing technology, and in particular to an invoice issuance method, device, electronic device and computer storage medium. Background Art

[0002] With the development of the economy and the prosperity of the market, commercial activities in the life service industry are becoming increasingly frequent. Invoices are important proof documents for transactions, reimbursement vouchers, and important tools for tax supervision. The demand for issuing invoices is increasing. The promotion of digital electronic invoices is an important measure for the digital transformation of tax management.

[0003] Currently, after users make purchases, merchants issue digital electronic invoices.

[0004] However, the invoice issuance process for merchants to issue digital electronic invoices is cumbersome and complicated, and cannot meet the needs of accurate and efficient invoice issuance in different scenarios. Summary of the invention

[0005] In view of this, embodiments of the present application provide an invoice issuing method, device, electronic device and computer storage medium to at least partially solve the above problems.

[0006] According to a first aspect of an embodiment of the present application, there is provided an invoice issuing method, comprising: obtaining order data, generating an invoice link according to the order data; obtaining an invoice header in response to a user triggering the invoice link; and issuing an invoice according to the invoice header and the order data.

[0007] In one possible implementation, the obtaining of order data and the generating of an invoice link according to the order data include: in response to a user scanning an identification code, determining whether there is a cash register order corresponding to the identification code in a temporary table; if there is a cash register order corresponding to the identification code in the temporary table, generating the order data according to the cash register order corresponding to the identification code, generating an invoice link according to the order data, and deleting the cash register order corresponding to the identification code in the temporary table.

[0008] In one possible implementation, the obtaining of order data and generating an invoice link based on the order data include: if the cash register order corresponding to the identification code does not exist in the temporary table, querying whether there is corresponding order data for the identification code; if there is order data for the identification code, obtaining the order data and generating an invoice link based on the order data; if there is no order data for the identification code, returning a prompt message, wherein the prompt message is used to prompt that there is no corresponding order data for the identification code.

[0009] In a possible implementation, the method further includes: when the checkout is completed, calling a data transmission interface to save the checkout order of the completed checkout into a temporary table, and generating an identification code corresponding to the checkout order according to the checkout order.

[0010] In a possible implementation, generating an identification code corresponding to the cashier order based on the cashier order includes: obtaining the order number, cashier counter number, tax number and order time of the cashier order; and generating an identification code corresponding to the cashier order based on the order number, the cashier counter number, the tax number and the order time.

[0011] In one possible implementation, issuing an invoice based on the invoice header and the order data includes: obtaining an invoicing configuration; if the invoicing configuration indicates issuing an electronic invoice, issuing an electronic invoice based on the invoice header and the order data; if the invoicing configuration indicates issuing a paper invoice, generating invoice data based on the invoice header and the order data, and sending the invoice data to an invoice printer to issue a paper invoice.

[0012] In a possible implementation, the issuing of the invoice according to the invoice header and the order data includes: obtaining an invoice type, wherein the invoice type is used to indicate the type of the invoice; and issuing the invoice according to the invoice header, the order data, and the invoice type.

[0013] According to the second aspect of an embodiment of the present application, an invoice issuing device is provided, comprising: a first acquisition unit, used to acquire order data and generate an invoice link based on the order data; a second acquisition unit, used to acquire an invoice header in response to a user triggering the invoice link; and a generation unit, used to issue an invoice based on the invoice header and the order data.

[0014] According to a third aspect of an embodiment of the present application, there is provided an electronic device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform an operation corresponding to the method described in the first aspect.

[0015] According to a fourth aspect of an embodiment of the present application, a computer storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the method described in the first aspect is implemented.

[0016] According to a fifth aspect of an embodiment of the present application, a computer program product is provided, comprising computer instructions, wherein the computer instructions instruct a computing device to execute the method as described in the first aspect.

[0017] According to the invoice issuance method provided in the embodiment of the present application, order data is obtained, an invoice link is generated according to the order data, in response to the user triggering the invoice link, the invoice header is obtained, and an invoice is issued according to the invoice header and the order data, thereby realizing self-service invoicing. After the user completes the consumption, the invoice can be automatically issued according to the user's choice, reducing the difficulty and cost of docking between systems. There is no need for merchants to operate invoice issuance, and the invoice issuance efficiency is high. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0019] Figure 1 It is a flow chart of an invoice issuing method provided in an embodiment of the present application;

[0020] Figure 2 It is a flow chart of a method for generating an invoice link provided in an embodiment of the present application;

[0021] Figure 3 is a schematic diagram of an invoice issuing device provided in an embodiment of the present application;

[0022] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the embodiments of the present application should fall within the scope of protection of the embodiments of the present application.

[0024] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0025] It should be understood that although the terms first, second, third, etc. may be used in the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0026] Figure 1 is a flow chart of an invoice issuance method provided in an embodiment of the present application, such as Figure 1 As shown, the invoice issuance method includes the following steps 101 to 103:

[0027] Step 101: Obtain order data and generate an invoice link based on the order data.

[0028] Obtain the order data of the cash register order to be invoiced, which may include product details and product prices, etc. Generate an invoice link based on the order data. In one example, the invoice link may be a (Uniform Resource Locator, URL) address. In another example, the invoice link may be in the form of a QR code, which is not limited here.

[0029] Step 102: In response to the user triggering the invoice link, the invoice header is obtained.

[0030] After the user triggers the invoice link, the invoice header entered by the user is obtained, for example: the company name, company tax number, etc. The user can trigger the invoice link by clicking a URL address, scanning a QR code, etc. The specific triggering method can be confirmed according to the form of the invoice link.

[0031] Step 103: Issue an invoice based on the invoice header and order data.

[0032] In an embodiment of the present application, order data is obtained, an invoice link is generated based on the order data, in response to the user triggering the invoice link, the invoice header is obtained, and an invoice is issued based on the invoice header and the order data, thereby realizing self-service invoicing. After the user completes the consumption, the invoice can be automatically issued according to the user's choice, reducing the difficulty and cost of docking between systems. There is no need for merchants to operate the invoice, and the invoice issuance efficiency is high.

[0033] Figure 2 is a flow chart of a method for generating an invoice link provided in an embodiment of the present application. Figure 2 As shown, when generating an invoice link, the following method steps 201 to 205 may be performed:

[0034] Step 201 , in response to the user scanning the identification code, determine whether there is a cash register order corresponding to the identification code in the temporary table, if so, execute step 202 , otherwise execute step 203 .

[0035] After the user scans the identification code, it is determined whether there is a cash register order stored in the temporary table. The identification code can be a QR code, a barcode, etc., and the temporary table can be an Enterprise Resource Planning (ERP) temporary table. The cash register order is a charge order for the user to purchase a product. The identification code can be the identification code printed on the user's shopping receipt, or an electronic identification code.

[0036] Step 202: Generate order data according to the cash register order corresponding to the identification code, generate an invoice link according to the order data, and delete the cash register order corresponding to the identification code in the temporary table.

[0037] If a cash register order corresponding to the identification code is stored in the temporary table, the cash register order is read from the temporary table, and order data corresponding to the cash register order is generated according to the cash register order. The order data may include product details and product prices, etc. An invoice link is generated according to the acquired order data. After the invoice link is generated, the cash register order in the temporary table is deleted.

[0038] Step 203, check whether there is corresponding order data for the identification code, if so, execute step 204, otherwise execute step 205.

[0039] If there is no cash register order corresponding to the identification code in the temporary table, there are two possibilities. The first is that the cash register order in the temporary table has been queried according to the identification code, and the order data has been obtained according to the cash register order to generate an invoice link. At this time, the cash register order in the temporary table will be deleted. If the user scans the identification code again, the cash register order corresponding to the identification code will not be queried from the temporary table. The other possibility is that the cash register order has not been saved in the temporary table, or the identification code is an illegal identification code, etc. If there is no cash register order corresponding to the identification code in the temporary table, check whether there is corresponding order data for the identification code.

[0040] Step 204: Obtain order data and generate an invoice link based on the order data.

[0041] If there is order data for the identification code, it proves that the cash register order in the temporary table has been queried based on the identification code, and the order data has been obtained based on the cash register order to generate an invoice link, and the cash register order in the temporary table has been deleted. At this time, the order data corresponding to the identification code is obtained, and the invoice link is regenerated based on the order data. It should be noted that the regenerated invoice link may be the same as or different from the previously generated invoice link.

[0042] Step 205: Return prompt information.

[0043] If there is no order data for the identification code, a prompt message is returned. The prompt message is used to prompt that there is no corresponding order data for the identification code. The prompt message can be set as needed. For example, the prompt message can be "The order is on the way, please try again later", or the prompt message can be "There is no order data for this identification code", etc.

[0044] In an embodiment of the present application, in response to a user scanning an identification code, it is determined whether there is a cash register order corresponding to the identification code in the temporary table. If so, order data is generated according to the cash register order corresponding to the identification code, an invoice link is generated according to the order data, and the cash register order corresponding to the identification code in the temporary table is deleted. Otherwise, it is checked whether there is corresponding order data for the identification code. If so, the order data is obtained and an invoice link is generated according to the order data. Otherwise, a prompt message is returned. In this way, the order data and the invoice link can be obtained according to the identification code. The user can quickly obtain the invoice link when issuing an invoice, and when the order data fails to be obtained, the corresponding operation is performed, which can prevent extra time consumption due to the failure to obtain the order data, and can effectively improve the efficiency and accuracy of issuing invoices.

[0045] In a possible implementation, the invoice issuance method may also call the data transmission interface to save the completed cashier order into a temporary table when cashier is completed, and generate an identification code corresponding to the cashier order according to the cashier order.

[0046] When the cash register is completed, the data transmission interface is called to save the cash register order generated according to the cash register result into a temporary table. In one example, the cash register order can be saved into the ERP temporary table by calling the ERP interface. When the data transmission interface is called to save the cash register order generated according to the cash register result into the temporary table, an identification code corresponding to the cash register order will be generated, for example, a QR code, barcode, etc. corresponding to the cash register order will be generated, so that the user can obtain the cash register order in the temporary table according to the identification code after scanning the identification code.

[0047] In an embodiment of the present application, when the checkout is completed, the data transmission interface is called to save the completed checkout order into a temporary table, and an identification code corresponding to the checkout order is generated based on the checkout order, thereby realizing the saving of the checkout order and the generation of the identification code. When the user completes the checkout, the checkout order can be saved into a temporary table, and the corresponding identification code is generated, which is convenient for the user to obtain the invoicing link according to the identification code, thereby improving the user experience.

[0048] In one possible implementation, when generating an identification code corresponding to a cash register order based on a cash register order, the order number, cash register number, tax number and order time of the cash register order can be obtained, and the identification code corresponding to the cash register order can be generated based on the order number, cash register number, tax number and order time.

[0049] After the checkout is completed, an identification code for the checkout order is generated based on the order number, cashier counter number, tax number and order time of the checkout order. After the user scans the identification code, he can query whether there is a checkout order corresponding to the identification code in the temporary table based on one or more of the order number, cashier counter number, tax number and order time.

[0050] In an embodiment of the present application, an identification code corresponding to the cashier order is generated based on the order number, cashier counter number, tax number and order time. After scanning the identification code, the user can query the cashier order based on one or more of the order number, cashier counter number, tax number and order time. Fuzzy query can be implemented to prevent the inability to query the cashier order due to an error in the order number, thereby improving the user's invoicing experience.

[0051] In one possible implementation, the invoicing configuration can be obtained when issuing an invoice based on the invoice header and order data. If the invoicing configuration indicates issuing an electronic invoice, the electronic invoice is issued based on the invoice header and order data. If the invoicing configuration indicates issuing a paper invoice, the invoice data is generated based on the invoice header and order data, and the invoice data is sent to the invoice printer to issue a paper invoice.

[0052] You can get the invoicing configuration. Users can choose whether to issue a paper invoice or an electronic invoice. When the user chooses to issue a paper invoice, the invoicing configuration instructs the issuance of a paper invoice. At this time, the invoice data is generated according to the invoice header and order data, and the invoice data is sent to the dedicated invoice printer. After the invoice printer receives the invoice data, it prints the invoice data to issue a paper invoice.

[0053] When the user chooses to issue an electronic invoice, the invoice configuration instructs the issuance of an electronic invoice, generates an electronic invoice file based on the invoice header and order data, and implements the issuance of the electronic invoice. Optionally, before issuing an electronic invoice or a paper invoice, an invoice preview interface can be displayed. When the user confirms that it is correct, the paper invoice or electronic invoice is issued in response to the user triggering the confirmation button.

[0054] In an embodiment of the present application, an invoicing configuration is obtained. If the invoicing configuration indicates the issuance of an electronic invoice, an electronic invoice is issued based on the invoice header and order data. If the invoicing configuration indicates the issuance of a paper invoice, invoice data is generated based on the invoice header and order data, and the invoice data is sent to the invoice printer to issue a paper invoice. In this way, different invoices can be issued according to the user's choice, and electronic invoices or paper invoices can be issued on demand, without the need for manual processing by the merchant to achieve self-service invoicing.

[0055] In a possible implementation, when an invoice is issued based on the invoice header and order data, the invoice type can be obtained, wherein the invoice type is used to indicate the type of invoice, and the invoice is issued based on the invoice header, order data and invoice type.

[0056] Before issuing an invoice, you can also obtain the invoice type, which can indicate the type of invoice, such as ordinary invoice, special VAT invoice, etc., and issue the invoice corresponding to the invoice type according to the invoice header and order data, for example, issuing a special VAT invoice according to the invoice header and order data. It should be noted that after obtaining the invoice type, you can also obtain the invoice configuration to issue an electronic ordinary invoice, an electronic special VAT invoice, a paper ordinary invoice, and a paper special VAT invoice. The specific issuance method can refer to the description in the above embodiment, which will not be repeated here.

[0057] In an embodiment of the present application, the invoice type is obtained, and the invoice is issued according to the invoice header, order data and invoice type. This allows the issuance of different types of invoices, and the user can choose the type of invoice to be issued according to their needs, which can meet the different needs of users and improve user experience.

[0058] Figure 3 is a schematic diagram of an invoice issuing device provided in an embodiment of the present application, such as Figure 3 As shown, the device 300 includes:

[0059] The first acquisition unit 301 is used to acquire order data and generate an invoice link according to the order data;

[0060] The second acquisition unit 302 is used to acquire the invoice header in response to the user triggering the invoice link;

[0061] The generating unit 303 is used to issue an invoice according to the invoice header and the order data.

[0062] In the embodiment of the present application, the first acquisition unit 301 can be used to execute step 101 in the above method embodiment, the second acquisition unit 302 can be used to execute step 102 in the above method embodiment, and the generation unit 303 can be used to execute step 103 in the above method embodiment.

[0063] In one possible implementation, the first acquisition unit 301 can also be used to respond to the user scanning the identification code and determine whether there is a cash register order corresponding to the identification code in the temporary table. If there is a cash register order corresponding to the identification code in the temporary table, order data is generated according to the cash register order corresponding to the identification code, an invoice link is generated according to the order data, and the cash register order corresponding to the identification code in the temporary table is deleted.

[0064] In a possible implementation, the first acquisition unit 301 can also be used to query whether there is corresponding order data for the identification code if there is no cash register order corresponding to the identification code in the temporary table; if there is order data for the identification code, obtain the order data and generate an invoice link based on the order data; if there is no order data for the identification code, return a prompt message, wherein the prompt message is used to prompt that there is no corresponding order data for the identification code.

[0065] In a possible implementation, the invoice issuing device 300 can also be used to call the data transmission interface to save the completed checkout order into a temporary table when the checkout is completed, and generate an identification code corresponding to the checkout order according to the checkout order.

[0066] In one possible implementation, the invoice issuing device 300 can also be used to obtain the order number, cashier counter number, tax number and order time of the cashier order, and generate an identification code corresponding to the cashier order based on the order number, cashier counter number, tax number and order time.

[0067] In one possible implementation, the generation unit 303 can also be used to obtain the invoicing configuration. If the invoicing configuration indicates the issuance of an electronic invoice, the electronic invoice is issued based on the invoice header and the order data. If the invoicing configuration indicates the issuance of a paper invoice, the invoice data is generated based on the invoice header and the order data, and the invoice data is sent to the invoice printer to issue a paper invoice.

[0068] In a possible implementation, the generating unit 303 may also be used to obtain an invoice type, where the invoice type is used to indicate the type of invoice, and the invoice is issued according to the invoice header, order data and invoice type.

[0069] Reference Figure 4 , shows a schematic diagram of the structure of an electronic device according to an embodiment of the present application. The specific embodiment of the present application does not limit the specific implementation of the electronic device.

[0070] like Figure 4 As shown, the electronic device may include: a processor (processor) 402 , a communication interface (Communications Interface) 404 , a memory (memory) 406 , and a communication bus 408 .

[0071] in:

[0072] The processor 402 , the communication interface 404 , and the memory 406 communicate with each other via a communication bus 408 .

[0073] The communication interface 404 is used to communicate with other electronic devices or servers.

[0074] The processor 402 is used to execute the program 410, and specifically can execute the relevant steps in the above-mentioned invoice issuance method embodiment.

[0075] Specifically, the program 410 may include program codes, which include computer operation instructions.

[0076] The processor 402 may be a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; one or more GPUs; or processors of different types, such as one or more CPUs, one or more GPUs, and one or more ASICs.

[0077] The memory 406 is used to store the program 410. The memory 406 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0078] The program 410 may be specifically used to enable the processor 402 to execute the invoice issuing method in any of the aforementioned embodiments.

[0079] The specific implementation of each step in program 410 can refer to the corresponding description of the corresponding steps and units in any of the above-mentioned invoice issuance method embodiments, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described devices and modules can refer to the corresponding process description in the above-mentioned method embodiments, which will not be repeated here.

[0080] In an embodiment of the present application, order data is obtained, an invoice link is generated based on the order data, in response to the user triggering the invoice link, the invoice header is obtained, and an invoice is issued based on the invoice header and the order data, thereby realizing self-service invoicing. After the user completes the consumption, the invoice can be automatically issued according to the user's choice, reducing the difficulty and cost of docking between systems. There is no need for merchants to operate the invoice, and the invoice issuance efficiency is high.

[0081] An embodiment of the present application also provides a computer program product, including computer instructions, which instruct a computing device to execute operations corresponding to any one of the above-mentioned multiple method embodiments.

[0082] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.

[0083] The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor or programmable or dedicated hardware (such as an ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the invoice issuance method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the invoice issuance method shown herein, the execution of the code converts the general-purpose computer into a dedicated computer for executing the invoice issuance method shown herein.

[0084] Those of ordinary skill in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0085] The above implementation methods are only used to illustrate the embodiments of the present application, and are not limitations on the embodiments of the present application. Ordinary technicians in the relevant technical field can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application. Therefore, all equivalent technical solutions also belong to the scope of the embodiments of the present application. The scope of patent protection of the embodiments of the present application should be limited by the claims.

Claims

1. A method for issuing invoices, characterized in that: include: Obtain order data, and generate an invoice link based on the order data; In response to the user triggering the invoice link, obtaining the invoice header; An invoice is issued according to the invoice header and the order data.

2. The method according to claim 1, characterized in that The obtaining of order data and generating an invoice link according to the order data includes: In response to the user scanning the identification code, determining whether there is a cashier order corresponding to the identification code in the temporary table; If there is a cash register order corresponding to the identification code in the temporary table, the order data is generated according to the cash register order corresponding to the identification code, an invoice link is generated according to the order data, and the cash register order corresponding to the identification code in the temporary table is deleted.

3. The method according to claim 2, characterized in that The obtaining of order data and generating an invoice link according to the order data includes: If there is no cash register order corresponding to the identification code in the temporary table, check whether there is corresponding order data for the identification code. If there is order data for the identification code, obtain the order data and generate an invoice link based on the order data. If there is no order data for the identification code, return a prompt message, wherein the prompt message is used to prompt that there is no corresponding order data for the identification code.

4. The method according to claim 2, characterized in that: The method further comprises: When the checkout is completed, the data transmission interface is called to save the checkout order of the checkout completed into a temporary table, and an identification code corresponding to the checkout order is generated according to the checkout order.

5. The method according to claim 4, characterized in that The step of generating an identification code corresponding to the cashier order according to the cashier order includes: Get the order number, cashier number, tax number and order time of the cashier order; An identification code corresponding to the cashier order is generated according to the order number, the cashier counter number, the tax number and the order time.

6. The method according to claim 1, characterized in that The issuing of an invoice according to the invoice header and the order data includes: Get the invoicing configuration; If the invoicing configuration indicates issuing an electronic invoice, issuing an electronic invoice according to the invoice header and the order data; If the invoicing configuration indicates that a paper invoice is to be issued, invoice data is generated according to the invoice header and the order data, and the invoice data is sent to an invoice printer to issue a paper invoice.

7. The method according to claim 1, characterized in that The issuing of an invoice according to the invoice header and the order data includes: Obtaining an invoice type, wherein the invoice type is used to indicate the type of the invoice; An invoice is issued according to the invoice header, the order data and the invoice type.

8. An invoice issuing device, characterized in that: include: A first acquisition unit, used to acquire order data and generate an invoice link according to the order data; A second acquisition unit, configured to acquire an invoice header in response to a user triggering the invoice link; A generating unit is used to issue an invoice according to the invoice header and the order data.

9. An electronic device, characterized in that: include: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the invoice issuance method as described in any one of claims 1-7.

10. A computer storage medium, characterized in that: A computer program is stored thereon, and when the program is executed by a processor, the invoice issuing method as described in any one of claims 1-7 is implemented.

Images