Method, device and equipment for issuing electronic invoice

Abstract

The present application relates to a method, device and equipment for issuing electronic invoices, the method comprising: after the electronic invoice of the current invoicing subject is successfully issued, if it is determined that the next subject to be invoiced is different from the current invoicing subject, the tax disk interface number and invoicing items of the next subject to be invoiced are read from the first server; the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing items are obtained from the second server; the tax disk corresponding to the next subject to be invoiced is started with the tax disk interface number; it is determined that the next subject to be invoiced corresponding to the tax disk is consistent with the subject to be invoiced indicated in the pre-invoicing data; the pre-invoicing data is sent to the invoicing assistant client; wherein the invoicing assistant client is used to organize the pre-invoicing data into a preset invoicing format and send it to the invoicing server; the invoicing server is used to issue an electronic invoice corresponding to the pre-invoicing data. The present application is used to solve the problem of low invoicing efficiency caused by a large number of repetitive manual operations during the invoicing process.

Description

Technical Field

[0001] The present application relates to the field of software technology, and in particular to a method, device and equipment for issuing electronic invoices. Background Art

[0002] At present, the application of electronic invoices has been piloted in many provinces and cities. Some enterprises do not deploy interfaces between enterprises and tax bureaus. When issuing electronic invoices, they need to use third-party invoicing assistant clients to cooperate with them. When electronic invoices need to be issued, they rely on manual operations under different invoicing entities to switch between multiple invoicing entities and start third-party invoicing assistant clients. In the invoicing process, there are a lot of repetitive manual operations, and the invoicing efficiency is low. Summary of the invention

[0003] The present application provides a method, device and equipment for issuing electronic invoices, so as to solve the problem of low invoicing efficiency caused by a large number of repetitive manual operations during the invoicing process.

[0004] In a first aspect, an embodiment of the present application provides a method for issuing an electronic invoice, comprising:

[0005] After the electronic invoice of the current invoicing subject is successfully issued, if it is determined that the next invoicing subject is different from the current invoicing subject, the tax disk interface number and invoicing items of the next invoicing subject are read from the first server;

[0006] Acquire, from the second server, the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item;

[0007] Using the tax disk interface number to start the tax disk corresponding to the next entity to be invoiced;

[0008] Determining that the next subject to be invoiced corresponding to the tax disk is consistent with the subject to be invoiced indicated in the pre-invoicing data;

[0009] The pre-invoicing data is sent to an invoicing assistant client; wherein the invoicing assistant client is used to organize the pre-invoicing data into a preset invoicing format and send it to an invoicing server; the invoicing server is used to issue an electronic invoice corresponding to the pre-invoicing data.

[0010] Optionally, starting the tax disk corresponding to the next subject to be invoiced with the tax disk interface number includes:

[0011] Reading the tax disk interface address corresponding to the tax disk interface number from the list of invoice information to be issued pre-configured in the first server;

[0012] A start request is sent to the tax disk interface address, where the start request is used to start the tax disk.

[0013] Optionally, sending the pre-invoicing data to an invoicing assistant client includes:

[0014] Reading the address of the invoicing client corresponding to the next invoicing entity from the first server;

[0015] According to the address of the invoicing client, the pre-invoicing data is sent to the invoicing client, and the invoicing client is instructed to send the pre-invoicing data to the invoicing assistant client.

[0016] Optionally, obtaining the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item from the second server includes:

[0017] Reading, from the second server, sales data corresponding to the next subject to be invoiced and the invoicing item;

[0018] The sales data with complete reservation information is extracted from the sales data, and the sales data with complete reservation information is used as the pre-invoicing data.

[0019] Optionally, reading the invoicing items of the next subject to be invoiced from the first server includes:

[0020] Determining whether the first server includes the invoicing item corresponding to the next entity to be invoiced;

[0021] If not, read the address of the third server corresponding to the next entity to be invoiced and the first login information from the list of information to be invoiced; send a download request to the third server according to the address of the third server and the first login information; obtain the invoicing item corresponding to the next entity to be invoiced returned by the third server according to the download request.

[0022] Optionally, after the electronic invoice of the invoicing entity is successfully issued, the following further includes:

[0023] Reading the address of the fourth server and the second login information corresponding to the current invoicing subject from the list of invoicing information to be issued;

[0024] Sending a target address acquisition request to the fourth server according to the address of the fourth server and the second login information;

[0025] Obtaining the target address of the current invoicing entity returned by the fourth server according to the target address acquisition request;

[0026] The successfully issued electronic invoice is sent to the target address.

[0027] Optionally, after acquiring the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item, and before starting the tax disk corresponding to the next subject to be invoiced with the tax disk interface number, the method further includes:

[0028] Read the registry, and clear the tax disk interface number and tax disk interface address corresponding to the invoicing subject in the registry.

[0029] Optionally, determining that the next subject to be invoiced is different from the subject of current invoicing includes:

[0030] From the to-be-invoiced information list in the first server, read the next to-be-invoiced subject of the current invoicing subject in a preset order;

[0031] It is determined that the next invoicing subject is different from the current invoicing subject.

[0032] In a second aspect, an embodiment of the present application provides a device for issuing an electronic invoice, including:

[0033] A reading module, for reading the tax disk interface number and invoicing items of the next subject to be invoiced from the first server after the electronic invoice of the current invoicing subject is successfully issued, if it is determined that the next subject to be invoiced is different from the current invoicing subject;

[0034] An acquisition module, used for acquiring, from the second server, the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item;

[0035] A starting module, used to start the tax disk corresponding to the next subject to be invoiced with the tax disk interface number;

[0036] A determination module, used for determining whether the next subject to be invoiced corresponding to the tax disk is consistent with the subject to be invoiced indicated in the pre-invoicing data;

[0037] The invoicing module is used to send the pre-invoicing data to the invoicing assistant client; wherein the invoicing assistant client is used to organize the pre-invoicing data into a preset invoicing format and send it to the invoicing server; the invoicing server is used to issue an electronic invoice corresponding to the pre-invoicing data.

[0038] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a communication bus, wherein the processor and the memory communicate with each other via the communication bus;

[0039] The memory is used to store computer programs;

[0040] The processor is used to execute the program stored in the memory to implement the method for issuing electronic invoices described in the first aspect.

[0041] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method for issuing an electronic invoice as described in the first aspect.

[0042] The above technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application, after the electronic invoice of the current invoicing subject is successfully issued, if the next invoicing subject is different from the current invoicing subject, it means that the electronic invoice of the next invoicing subject is to be issued, and the tax disk corresponding to the tax disk interface number is automatically started by reading the tax disk interface number of the next invoicing subject, thereby realizing the switching of the invoicing subject; and automatically obtaining the pre-invoicing data corresponding to the next invoicing subject and the invoicing item from the second server, if the next invoicing subject corresponding to the tax disk is consistent with the invoicing subject indicated in the pre-invoicing data, it means that the pre-invoicing data corresponding to the next invoicing subject has been found, indicating that the preparations before the current invoicing have been completed, and then the pre-invoicing data is sent to the invoicing assistant client, and the pre-invoicing data is sent to the invoicing server through the invoicing assistant client to realize the issuance of electronic invoices. In the embodiment of the present application, the tax disks of different invoicing subjects are automatically switched throughout the invoicing process, and the invoicing is automatically realized without a large number of repetitive manual operations, which effectively improves work efficiency and saves manpower. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0044] In order to more clearly illustrate the embodiments of the present invention 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, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0045] Figure 1a A schematic diagram of the system architecture for issuing electronic invoices provided in an embodiment of the present application;

[0046] Figure 1b A flowchart of a method for issuing an electronic invoice provided in an embodiment of the present application;

[0047] Figure 2 A flowchart of another method for issuing an electronic invoice provided in an embodiment of the present application;

[0048] Figure 3 A schematic diagram of the structure of a device for issuing electronic invoices provided in an embodiment of the present application;

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

[0050] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution 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 part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0051] The embodiment of the present application provides a method for issuing electronic invoices to solve the problem in the prior art that a large number of repetitive manual operations during the invoicing process lead to low invoicing efficiency.

[0052] First, combine Figure 1a The system architecture for issuing electronic invoices in the embodiment of the present application is described. The system architecture includes: an RPA (Robotic Process Automation) server, a first server, a second server, a third server, and a fourth server; wherein the RPA server communicates with the first server, the second server, the third server, and the fourth server, respectively. In the specific implementation, the RPA server can communicate with each server through the network, and the above network includes but is not limited to: a wide area network, a local WIFI local area network. The RPA server can be deployed on a computer or a server.

[0053] Among them, the first server is used to store the list of information to be invoiced and data related to the invoicing items. The list of information to be invoiced includes: the mapping relationship between parameters such as the name of the entity to be invoiced (for example: company name), unified social credit code, tax number, user name, password, tax disk interface number and tax disk interface address; the second server is used to store sales data, and the sales data includes: real estate company name, real estate project, room number, amount, purchaser and telephone number, etc.; the third server is used to store data related to the invoicing items, such as: the entity to be invoiced, invoicing items, project installments, building room number and occupancy time, etc.; the fourth server is used to send invoicing notifications.

[0054] See also Figure 1b Based on the above system architecture, the present application embodiment provides a method for issuing electronic invoices, which is implemented by using RPA (Robotic Process Automation) technology. The method mainly includes the following steps:

[0055] Step 101, after the electronic invoice of the current invoicing subject is successfully issued, if it is determined that the next invoicing subject is different from the current invoicing subject, the tax disk interface number and invoicing items of the next invoicing subject are read from the first server;

[0056] In the process of issuing an electronic invoice, if the electronic invoice of the current invoicing subject is successfully issued, and it is determined that the next invoicing subject is different from the current invoicing subject, it means that the invoicing subject needs to be switched. Specifically, the next invoicing subject of the current invoicing subject can be read from the invoicing information list in the first server according to a preset order; and it is determined that the next invoicing subject is different from the current invoicing subject.

[0057] When switching the invoicing subject, the focus is on starting the tax disk used by the invoicing subject. Specifically, a first folder can be pre-set in the first server, and a list of invoicing information to be stored in the first folder. The list of invoicing information to be stored may include: mapping relationships between parameters such as the name of the invoicing subject (for example, company name), unified social credit code, tax number, user name, password, tax disk interface number, and tax disk interface address. When switching the invoicing subject, the tax disk interface number corresponding to the next invoicing subject is read from the list of invoicing information to be stored, so as to start the corresponding tax disk using the tax disk interface number.

[0058] In addition to the above-mentioned list of information to be invoiced, the mapping relationship between the subject to be invoiced and the invoicing item can also be pre-configured in the first server, wherein the invoicing item is used to guide the RPA robot to clarify the invoicing item of the electronic invoice to be issued by the subject to be invoiced. In the specific implementation, a second folder can be set in the first server. If the invoicing item corresponding to the next subject to be invoiced is read from the second folder, the invoicing item is directly read to perform the subsequent steps. For example, taking the real estate industry as an example, the mapping relationship between real estate company A1 and real estate project D1 is stored in the second folder. If the next subject to be invoiced is read from the list of information to be invoiced as A1, the real estate project D1 corresponding to A1 is read from the second folder. In addition, data related to the invoicing item, such as project installment, building room number and occupancy time, can also be pre-configured in the second folder.

[0059] If no invoicing item is configured in the first server, the address of the third server corresponding to the next subject to be invoiced and the first login information can be read from the list of information to be invoiced; a download request is sent to the third server according to the address of the third server and the first login information; and the invoicing item corresponding to the next subject to be invoiced returned by the third server according to the download request is obtained.

[0060] If the invoicing item is not directly read in the first server, the third server is logged in and the invoicing item is downloaded from the third server to guide the subsequent acquisition of pre-invoicing data.

[0061] Step 102, obtaining the pre-invoicing data corresponding to the next invoicing entity and the invoicing item from the second server;

[0062] The role of the next subject to be invoiced and the corresponding invoicing item is to guide the RPA robot to automatically obtain the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item from the second server.

[0063] For example: from the first server, it is read that the next entity to be invoiced is Company B, and it is read that the invoicing project corresponding to Company B is Real Estate Project C. When obtaining the pre-invoicing data, the data that the entity to be invoiced is Company B and the invoicing project is Company C is obtained from the second server.

[0064] In a specific implementation, the second server may be a server storing sales data. When obtaining the pre-invoicing data from the second server, firstly, the address of the second server and the login information of the second server are read from the list of information to be invoiced of the first server, and a request to read the sales data is sent to the second server according to the address of the second server and the login information of the second server, and the sales data returned by the second server according to the request to read the sales data is obtained, and the sales data with complete reserved information is extracted from the sales data, and the sales data with complete reserved information is used as the pre-invoicing data.

[0065] In specific implementation, the reserved information may include: buyer's name (eg company name or personal name), identity number (eg unified social credit code or ID number), telephone number, amount and tax rate, etc.

[0066] In an embodiment of the present application, the extracted pre-invoicing data is data with complete reserved information. When reading the pre-invoicing data, it is determined whether the reserved information in the sales data is complete, and the sales data with complete reserved information is used as the pre-invoicing data. Subsequently, electronic invoices are only issued for data with complete reserved information. If the reserved information is incomplete, no invoice is issued. This avoids the situation where invalid invoices are issued due to human negligence, and solves the problem in the prior art that when issuing electronic invoices, manual screening and recording of abnormal data are required, which inevitably leads to problems such as missing data and low efficiency.

[0067] Step 103, start the tax disk corresponding to the next invoicing entity with the tax disk interface number;

[0068] When switching the invoicing subject, the focus is on switching the tax disk, and starting the tax disk corresponding to the next invoicing subject by reading the tax disk interface number from the first server. Specifically, read the tax disk interface address corresponding to the tax disk interface number from the invoicing information list pre-configured in the first server; send a start request to the tax disk interface address, and the start request is used to start the tax disk.

[0069] In the specific implementation, the RPA robot reads the tax disk interface address corresponding to the tax disk interface number, calls the USB hub (Universal Serial Bus Hub) control program to send a start request to the tax disk interface address to start the tax disk.

[0070] In order to further ensure the correctness of issuing electronic invoices, after step 102 and before step 103, it also includes: reading the registry and clearing the tax disk interface number and tax disk interface address corresponding to the current invoicing entity in the registry, so as to eliminate the influence of the current invoicing entity on the next invoicing entity during the invoicing process.

[0071] Step 104, determining whether the next invoicing entity corresponding to the tax disk is consistent with the invoicing entity indicated in the pre-invoicing data;

[0072] If the next invoicing entity corresponding to the tax disk is consistent with the invoicing entity indicated in the pre-invoicing data, it means that the tax disk of the next invoicing entity has been activated, and the pre-invoicing data corresponding to the next invoicing entity has been found, indicating that the preparations before the current invoicing have been completed and formal invoicing can be carried out. If they are inconsistent, invoicing cannot be carried out, indicating that the tax disk has not been activated or the pre-invoicing data obtained is incorrect.

[0073] Step 105, sending the pre-invoicing data to the invoicing assistant client; wherein the invoicing assistant client is used to organize the pre-invoicing data into a preset invoicing format and send it to the invoicing server; the invoicing server is used to issue an electronic invoice corresponding to the pre-invoicing data.

[0074] The invoicing assistant client supports the import of batch pre-invoicing data, realizes data interaction with the invoicing server, and thus realizes invoicing. Among them, the invoicing server is used to fill the pre-invoicing data into the preset invoicing template according to the pre-invoicing data and the preset invoicing template to generate an electronic invoice, thereby realizing the issuance of an electronic invoice.

[0075] In the embodiment of the present application, after the electronic invoice of the current invoicing subject is successfully issued, if the next invoicing subject is different from the current invoicing subject, it means that the electronic invoice of the next invoicing subject is to be issued. By reading the tax disk interface number of the next invoicing subject, the tax disk corresponding to the tax disk interface number is automatically started, and the switching of the invoicing subject is realized; and the pre-invoicing data corresponding to the next invoicing subject and the invoicing item is automatically obtained from the second server. If the next invoicing subject corresponding to the tax disk is consistent with the invoicing subject indicated in the pre-invoicing data, it means that the pre-invoicing data corresponding to the next invoicing subject has been found, indicating that the preparations before the current invoicing have been completed, and then the pre-invoicing data is sent to the invoicing assistant client, and the pre-invoicing data is sent to the invoicing server through the invoicing assistant client to realize the issuance of electronic invoices. In the embodiment of the present application, the tax disks of different invoicing subjects are automatically switched throughout the invoicing process, and the invoicing is automatically realized without a large amount of repetitive manual operations, which effectively improves work efficiency and saves manpower.

[0076] like Figure 2 As shown, in order to further improve the degree of automation of the method for issuing electronic invoices provided by the present application, in the embodiment of the present application, after the electronic invoice of the invoicing subject is successfully issued, it also includes:

[0077] Step 201, reading the address of the fourth server and the second login information corresponding to the invoicing subject from the list of invoicing information to be issued;

[0078] The fourth server is a notification management system, which is used to send notifications or emails to users. The fourth server is logged in through the address of the fourth server and the second login information.

[0079] Step 202, sending a target address acquisition request to the fourth server according to the address of the fourth server and the second login information;

[0080] After logging in to the fourth server, a target address acquisition request corresponding to the current invoicing subject that has successfully issued the invoice is sent to the fourth server to obtain the target address, so as to send the issued electronic invoice to the target address.

[0081] Step 203, obtaining the target address of the current invoicing entity returned by the fourth server according to the target address acquisition request;

[0082] The target address may be the user's email address or the address of the user's office system.

[0083] Step 204: Send the successfully issued electronic invoice to the target address.

[0084] According to the same method, after the next entity to be invoiced successfully issues an invoice, the address of the fourth server and the third login information corresponding to the next entity to be invoiced can also be read from the list of information to be invoiced; according to the address and the third login information of the fourth server, a target address acquisition request is sent to the fourth server; the target address of the next entity to be invoiced returned by the fourth server according to the target address acquisition request is obtained; and the successfully issued electronic invoice is sent to the target address.

[0085] In the embodiment of the present application, the successfully issued electronic invoice is automatically sent to the target address to notify the customer that the invoice is successfully issued, so that the customer can check whether the electronic invoice is correct, which is more intelligent and automated.

[0086] Considering the actual situation, for a group company, there are usually multiple subsidiaries. Accordingly, there are multiple entities to be invoiced in the list of invoicing information to be issued on the first server. When obtaining the pre-invoicing data from the second server, the pre-invoicing data corresponding to each entity to be invoiced and the invoicing items in the list of invoicing information to be issued can be obtained at one time. From the first server, the address of the invoicing client corresponding to each entity to be invoiced is read, and the pre-invoicing data corresponding to the entity to be invoiced is distributed to the respective invoicing clients according to the address of the invoicing client corresponding to each entity to be invoiced. When invoicing, the invoicing client is instructed to send the pre-invoicing data to the invoicing assistant client in accordance with the preset order, so as to issue the electronic invoices of each entity to be invoiced in turn. When returning the issued electronic invoices, after a batch of invoices for the same entity to be invoiced are issued, they are fed back to the corresponding invoicing client, which brings convenience to the distribution of electronic invoices, and users can understand the progress of invoicing through the invoicing client.

[0087] For example: in the list of information to be invoiced, three entities to be invoiced G1, G2 and G3 are stored in sequence. After obtaining the pre-invoicing data S1 of the entity to be invoiced G1, the pre-invoicing data S2 of the entity to be invoiced G2 and the pre-invoicing data S3 of the entity to be invoiced G3, the pre-invoicing data S1 is sent to the invoicing client of G1 according to the address of the invoicing client of the entity to be invoiced G1; the pre-invoicing data S2 is sent to the invoicing client of G2 according to the address of the invoicing client of the entity to be invoiced G2; and the pre-invoicing data S3 is sent to the invoicing client of G3 according to the address of the invoicing client of the entity to be invoiced G3.

[0088] When invoicing, the RPA robot first instructs the invoicing client of G1 to send the pre-invoicing data to the invoicing assistant client in the order of the invoicing entities stored in the invoicing information list to achieve invoicing, and returns the issued electronic invoice for G1 to the invoicing client of G1 for the customer to view. After the electronic invoice for G1 is successfully issued, the invoicing entity G2 after G1 is read from the invoicing information list to invoice, instructs the invoicing client of G2 to send the pre-invoicing data to the invoicing assistant client to achieve invoicing, and returns the issued electronic invoice for G2 to the invoicing client of G2; after the electronic invoice for G2 is successfully issued, the invoicing entity G3 after G2 is read from the invoicing information list to invoice, instructs the invoicing client of G3 to send the pre-invoicing data to the invoicing assistant client to achieve invoicing, and returns the issued electronic invoice for G3 to the invoicing client of G3.

[0089] Based on the same concept, an apparatus for issuing electronic invoices is provided in the embodiment of the present application. The specific implementation of the apparatus can be found in the description of the method embodiment, and the repetitive parts will not be repeated. Figure 3 As shown, the device mainly includes:

[0090] The reading module 301 is used to read the tax disk interface number and invoicing items of the next invoicing entity from the first server after the electronic invoice of the current invoicing entity is successfully issued, if it is determined that the next invoicing entity is different from the current invoicing entity;

[0091] In specific implementation, when it is determined that the next subject to be invoiced is different from the subject to be invoiced currently, the next subject to be invoiced of the subject to be invoiced currently can be read from the list of invoiced information in the first server in a preset order to determine that the next subject to be invoiced is different from the subject to be invoiced currently.

[0092] The acquisition module 302 is used to acquire the pre-invoicing data corresponding to the next invoicing subject and the invoicing item from the second server;

[0093] The start module 303 is used to start the tax disk corresponding to the next invoicing subject with the tax disk interface number;

[0094] A determination module 304 is used to determine whether the next subject to be invoiced corresponding to the tax disk is consistent with the subject to be invoiced indicated in the pre-invoicing data;

[0095] The invoicing module 305 is used to send the pre-invoicing data to the invoicing assistant client; wherein the invoicing assistant client is used to organize the pre-invoicing data into a preset invoicing format and send it to the invoicing server; the invoicing server is used to issue an electronic invoice corresponding to the pre-invoicing data.

[0096] In the embodiment of the present application, after the electronic invoice of the current invoicing subject is successfully issued, if the next invoicing subject is different from the current invoicing subject, it means that the electronic invoice of the next invoicing subject is to be issued. By reading the tax disk interface number of the next invoicing subject, the tax disk corresponding to the tax disk interface number is automatically started, and the switching of the invoicing subject is realized; and the pre-invoicing data corresponding to the next invoicing subject and the invoicing item is automatically obtained from the second server. If the next invoicing subject corresponding to the tax disk is consistent with the invoicing subject indicated in the pre-invoicing data, it means that the pre-invoicing data corresponding to the next invoicing subject has been found, indicating that the preparations before the current invoicing have been completed, and then the pre-invoicing data is sent to the invoicing assistant client, and the pre-invoicing data is sent to the invoicing server through the invoicing assistant client to realize the issuance of electronic invoices. In the embodiment of the present application, the tax disks of different invoicing subjects are automatically switched throughout the invoicing process, and the invoicing is automatically realized without a large amount of repetitive manual operations, which effectively improves work efficiency and saves manpower.

[0097] In the embodiment of the present application, the startup module 303 is specifically used to read the tax disk interface address corresponding to the tax disk interface number from the list of invoice information pre-configured in the first server; send a startup request to the tax disk interface address, and the startup request is used to start the tax disk.

[0098] In the embodiment of the present application, the invoicing module 305 is specifically used to read the address of the invoicing client corresponding to the next entity to be invoiced from the first server; send the pre-invoicing data to the invoicing client according to the address of the invoicing client, and instruct the invoicing client to send the pre-invoicing data to the invoicing assistant client.

[0099] In the embodiment of the present application, the acquisition module 302 is specifically used to read the sales data corresponding to the next subject to be invoiced and the invoicing item from the second server; extract the sales data with complete reserved information from the sales data, and use the sales data with complete reserved information as pre-invoicing data.

[0100] In the embodiment of the present application, the reading module 301 is specifically used to determine whether the first server includes the invoicing item corresponding to the next subject to be invoiced; if not, read the address and first login information of the third server corresponding to the next subject to be invoiced from the list of information to be invoiced; send a download request to the third server according to the address and the first login information of the third server; and obtain the invoicing item corresponding to the next subject to be invoiced returned by the third server according to the download request.

[0101] In an embodiment of the present application, the device for issuing electronic invoices also includes: a notification module, which is specifically used to read the address and second login information of the fourth server corresponding to the invoicing entity from the list of information to be invoiced; send a target address acquisition request to the fourth server according to the address and second login information of the fourth server; obtain the target address of the invoicing entity returned by the fourth server according to the target address acquisition request; and send the successfully issued electronic invoice to the target address.

[0102] In the embodiment of the present application, the successfully issued electronic invoice is automatically sent to the target address to notify the customer that the invoice is successfully issued, so that the customer can check whether the electronic invoice is correct, which is more intelligent and automated.

[0103] In an embodiment of the present application, the device for issuing electronic invoices also includes: a clearing module, which is used to read a registration table and clear the tax disk interface number and tax disk interface address corresponding to the current invoicing entity in the registration table to eliminate the influence of the current invoicing entity on the next invoicing entity.

[0104] Based on the same concept, an electronic device is also provided in the embodiment of the present application, such as Figure 4 As shown, the electronic device mainly includes: a processor 401, a memory 402 and a communication bus 403, wherein the processor 401 and the memory 402 communicate with each other through the communication bus 403. The memory 402 stores a program that can be executed by the processor 401, and the processor 401 executes the program stored in the memory 402 to implement the following steps:

[0105] After the electronic invoice of the current invoicing subject is successfully issued, if it is determined that the next invoicing subject is different from the current invoicing subject, the tax disk interface number and invoicing items of the next invoicing subject are read from the first server;

[0106] Obtaining the pre-invoicing data corresponding to the next invoicing subject and invoicing item from the second server;

[0107] Use the tax disk interface number to start the tax disk corresponding to the next invoicing entity;

[0108] Determine that the next invoicing entity corresponding to the tax disk is consistent with the invoicing entity indicated in the pre-invoicing data;

[0109] The pre-invoicing data is sent to the invoicing assistant client; wherein the invoicing assistant client is used to organize the pre-invoicing data into a preset invoicing format and send it to the invoicing server; the invoicing server is used to issue an electronic invoice corresponding to the pre-invoicing data.

[0110] The communication bus 403 mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 403 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0111] The memory 402 may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Alternatively, the memory may also be at least one storage device located away from the processor 401.

[0112] The above-mentioned processor 401 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., and can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0113] In another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed on a computer, the computer executes the method for issuing an electronic invoice described in the above embodiment.

[0114] In the above embodiments, it can be implemented in whole or in part by a client, hardware, firmware or any combination thereof. When implemented using a client, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, a computer instruction is transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape, etc.), an optical medium (e.g., a DVD) or a semiconductor medium (e.g., a solid-state hard disk), etc.

[0115] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0116] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for issuing electronic invoices, characterized in that: include: After the electronic invoice of the current invoicing subject is successfully issued, if it is determined that the next invoicing subject is different from the current invoicing subject, the tax disk interface number and invoicing items of the next invoicing subject are read from the first server; Acquire, from the second server, the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item; Using the tax disk interface number to start the tax disk corresponding to the next entity to be invoiced; Determining that the next subject to be invoiced corresponding to the tax disk is consistent with the subject to be invoiced indicated in the pre-invoicing data; Sending the pre-invoicing data to an invoicing assistant client; wherein the invoicing assistant client is used to organize the pre-invoicing data into a preset invoicing format and send it to an invoicing server; the invoicing server is used to issue an electronic invoice corresponding to the pre-invoicing data; The step of starting the tax disk corresponding to the next invoicing entity with the tax disk interface number includes: Reading the tax disk interface address corresponding to the tax disk interface number from the list of invoice information to be issued pre-configured in the first server; Sending a start request to the tax disk interface address, wherein the start request is used to start the tax disk; The step of reading the invoicing items of the next invoicing entity from the first server includes: Determining whether the first server includes the invoicing item corresponding to the next entity to be invoiced; If not, read the address of the third server and the first login information corresponding to the next subject to be invoiced from the list of information to be invoiced; send a download request to the third server according to the address of the third server and the first login information; obtain the invoicing item corresponding to the next subject to be invoiced returned by the third server according to the download request; Among them, after the electronic invoice of the invoicing entity is successfully issued, it also includes: Reading the address of the fourth server and the second login information corresponding to the current invoicing subject from the list of invoicing information to be issued; Sending a target address acquisition request to the fourth server according to the address of the fourth server and the second login information; Obtaining the target address of the current invoicing entity returned by the fourth server according to the target address acquisition request; Sending the successfully issued electronic invoice to the target address; Among them, the list of information to be invoiced includes: the mapping relationship between the name of the entity to be invoiced, the unified social credit code, the tax number, the user name, the password, the tax disk interface number and the parameters of the tax disk interface address; the data related to the invoicing project includes the entity to be invoiced, the invoicing project, the project installment, the building room number and the occupancy time.

2. The method for issuing electronic invoices according to claim 1, characterized in that: The sending of the pre-invoicing data to the invoicing assistant client comprises: Reading the address of the invoicing client corresponding to the next invoicing entity from the first server; According to the address of the invoicing client, the pre-invoicing data is sent to the invoicing client, and the invoicing client is instructed to send the pre-invoicing data to the invoicing assistant client.

3. The method for issuing electronic invoices according to claim 1, characterized in that: The step of obtaining, from the second server, the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item includes: Reading, from the second server, sales data corresponding to the next subject to be invoiced and the invoicing item; The sales data with complete reservation information is extracted from the sales data, and the sales data with complete reservation information is used as the pre-invoicing data.

4. The method for issuing electronic invoices according to claim 1, characterized in that: After obtaining the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item, and before starting the tax disk corresponding to the next subject to be invoiced with the tax disk interface number, the method further includes: Read the registry, and clear the tax disk interface number and tax disk interface address corresponding to the invoicing subject in the registry.

5. The method for issuing electronic invoices according to claim 1, characterized in that: The determining that the next subject to be invoiced is different from the subject of the current invoicing includes: From the to-be-invoiced information list in the first server, read the next to-be-invoiced subject of the current invoicing subject in a preset order; It is determined that the next invoicing subject is different from the current invoicing subject.

6. A device for issuing electronic invoices, characterized in that: include: A reading module, for reading the tax disk interface number and invoicing items of the next subject to be invoiced from the first server after the electronic invoice of the current invoicing subject is successfully issued, if it is determined that the next subject to be invoiced is different from the current invoicing subject; An acquisition module, used for acquiring, from the second server, the pre-invoicing data corresponding to the next subject to be invoiced and the invoicing item; A starting module, used to start the tax disk corresponding to the next subject to be invoiced with the tax disk interface number; A determination module, used for determining whether the next subject to be invoiced corresponding to the tax disk is consistent with the subject to be invoiced indicated in the pre-invoicing data; An invoicing module, used to send the pre-invoicing data to an invoicing assistant client; wherein the invoicing assistant client is used to organize the pre-invoicing data into a preset invoicing format and send it to an invoicing server; the invoicing server is used to issue an electronic invoice corresponding to the pre-invoicing data; The step of starting the tax disk corresponding to the next invoicing entity with the tax disk interface number includes: Reading the tax disk interface address corresponding to the tax disk interface number from the list of invoice information to be issued pre-configured in the first server; Sending a start request to the tax disk interface address, wherein the start request is used to start the tax disk; The step of reading the invoicing items of the next invoicing entity from the first server includes: Determining whether the first server includes the invoicing item corresponding to the next entity to be invoiced; If not, read the address of the third server and the first login information corresponding to the next subject to be invoiced from the list of information to be invoiced; send a download request to the third server according to the address of the third server and the first login information; obtain the invoicing item corresponding to the next subject to be invoiced returned by the third server according to the download request; Among them, after the electronic invoice of the invoicing entity is successfully issued, it also includes: Reading the address of the fourth server and the second login information corresponding to the current invoicing subject from the list of invoicing information to be issued; Sending a target address acquisition request to the fourth server according to the address of the fourth server and the second login information; Obtaining the target address of the current invoicing entity returned by the fourth server according to the target address acquisition request; Sending the successfully issued electronic invoice to the target address; Among them, the list of information to be invoiced includes: the mapping relationship between the name of the entity to be invoiced, the unified social credit code, the tax number, the user name, the password, the tax disk interface number and the parameters of the tax disk interface address; the data related to the invoicing project includes the entity to be invoiced, the invoicing project, the project installment, the building room number and the occupancy time.

7. An electronic device, characterized in that: include: A processor, a memory and a communication bus, wherein the processor and the memory communicate with each other via the communication bus; The memory is used to store computer programs; The processor is used to execute the program stored in the memory to implement the method for issuing electronic invoices as described in any one of claims 1 to 5.

Images