Electronic invoice issuing method and system, electronic device, and computer storage medium
By introducing message generation, receiving, and invoicing modules into the invoicing system, invoicing messages are generated and verified, solving the problem of incorrect invoicing caused by invoicing information errors and transmission interruptions, and realizing the accuracy and completeness of electronic invoicing.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- AISINO CORPORATION
- Filing Date
- 2024-12-17
- Publication Date
- 2026-06-19
Smart Images
Figure CN122243600A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to an electronic invoice issuance method, system, electronic device, and computer storage medium. Background Technology
[0002] Currently, electronic invoices are usually issued using an invoicing system. Users send invoicing information to the invoicing system, and the system automatically generates electronic invoices.
[0003] However, the existing invoicing system may issue incorrect invoices if there are errors in the invoicing information or if the invoicing information is interrupted during transmission. Summary of the Invention
[0004] In view of this, embodiments of this application provide an electronic invoice issuance method, system, electronic device, and computer storage medium to at least partially solve the above-mentioned problems.
[0005] According to a first aspect of the embodiments of this application, an electronic invoice issuance method is provided, applied to an invoicing system, the invoicing system including a message generation module, a message receiving module, and an invoicing module, the method comprising:
[0006] The message generation module receives invoicing information and the target invoice type for the electronic invoice to be issued, generates an invoicing message, and sends the invoicing message to the message receiving module.
[0007] The message receiving module performs integrity verification on the received invoice message, and sends the invoice message to the invoice module when the verification is successful.
[0008] The invoicing module issues the electronic invoice based on the received invoicing message.
[0009] In some embodiments, the invoicing message includes the invoicing information, the target invoice type of the electronic invoice to be issued, and a message tag;
[0010] The message receiving module performs integrity verification on the received invoicing message, including:
[0011] The message receiving module parses the invoice message;
[0012] The message receiving module determines that the verification is successful after confirming that the invoicing message includes the invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag.
[0013] The message generation module generates an invoice message based on the invoicing information configured by the user in the configuration interface and the target invoice type for which the electronic invoice to be issued is to be generated.
[0014] The message generation module generates a unique message tag;
[0015] Based on the invoicing information, the target invoice type to be issued, and the message tag, the invoice is generated.
[0016] [HZTC-HXRJGS241002][HS2411341CCN] Ticket information.
[0017] In some embodiments, after the message receiving module determines that the invoicing message includes the invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag, the method further includes:
[0018] The message receiving module determines the first information type included in the invoicing information and the second information type required for the electronic invoice to be issued based on the parsing result.
[0019] When the first information type matches the second information type, the verification is deemed successful.
[0020] In some embodiments, the invoicing system further includes a parsing module;
[0021] Before the invoicing module issues the electronic invoice based on the received invoicing message, the method further includes:
[0022] The message receiving module sends the invoicing message to the parsing module;
[0023] The parsing module determines the invoicing information based on the invoicing message, and determines the electronic invoice style based on the target invoice type;
[0024] The parsing module sends the invoicing information and the electronic invoice template to the invoicing module;
[0025] The invoicing module issues the electronic invoice based on the received invoicing message, including:
[0026] The invoicing module issues the electronic invoice based on the invoicing information and the electronic invoice template.
[0027] In some embodiments, the parsing module sends the invoicing information and the electronic invoice template to the invoicing module, including:
[0028] The parsing module determines the target invoicing information required to issue the target invoice type based on the target invoice type.
[0029] The target invoice information is obtained from the invoice information, and the target invoice information and the electronic invoice template are sent to the invoice module.
[0030] The invoicing module issues the electronic invoice based on the invoicing information and the electronic invoice template, including:
[0031] The invoicing module issues the electronic invoice based on the target invoicing information and the electronic invoice template.
[0032] In some embodiments, obtaining the target invoice information from the invoice information and sending the target invoice information and the electronic invoice template to the invoice module includes:
[0033] The parsing module stores the target invoicing information and the electronic invoice template in a message queue, so as to send the target invoicing information and the electronic invoice template to the invoicing module through the message queue.
[0034] In some embodiments, the invoicing module issues the electronic invoice based on the target invoicing information and the electronic invoice template, including:
[0035] The invoicing module obtains the target invoicing information and the electronic invoice template from the message queue;
[0036] The invoicing module determines whether the target invoicing information meets preset conditions;
[0037] When the invoicing module determines that the target invoicing information meets preset conditions, it issues the electronic invoice based on the target invoicing information and the electronic invoice template.
[0038] According to a second aspect of the embodiments of this application, an invoicing system is provided, the invoicing system including a message generation module, a message receiving module and an invoicing module, the invoicing system being used to execute the electronic invoice issuance method described in the first aspect.
[0039] According to a third aspect of the embodiments of this application, an electronic device is provided, including: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface complete communication via the communication bus.
[0040] [HZTC-HXRJGS241002][HS2411341CCN] communication between each other; the memory is used to store at least one executable instruction, which causes the processor to perform an operation corresponding to the electronic invoice issuance method described in the first aspect.
[0041] According to a fourth aspect of the embodiments of this application, a computer storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the electronic invoice issuance method as described in the first aspect.
[0042] According to the electronic invoice issuance method provided in this application, the message generation module of the invoicing system generates an invoicing message based on the invoicing information configured by the user in the configuration interface and the target invoice type to be issued. The message receiving module further verifies the integrity of the invoicing message, and upon successful verification, issues the electronic invoice through the invoicing module. This application, by verifying the integrity of the invoicing message, can determine its correctness and improve the accuracy of electronic invoice issuance. Attached Figure Description
[0043] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.
[0044] Figure 1 A schematic diagram of an invoicing system applicable to embodiments of this application;
[0045] Figure 2 This is a flowchart illustrating the steps of an electronic invoice issuance method according to an embodiment of this application;
[0046] Figure 3 This is a flowchart illustrating the steps of an electronic invoice issuance method according to another embodiment of this application;
[0047] Figure 4 This is a structural block diagram of an invoicing system according to another embodiment of this application;
[0048] Figure 5 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation
[0049] To enable those skilled in the art to better understand the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art should fall within the protection scope of the embodiments of this application.
[0050] The specific implementation of the embodiments of this application will be further described below with reference to the accompanying drawings.
[0051] This application provides a method for issuing electronic invoices, applied to an invoicing system, such as... Figure 1 As shown, it includes a message generation module 101, a message receiving module 102, and an invoicing module 103 connected to each other. The specific method is as follows: Figure 2 As shown, it includes:
[0052] S201, the message generation module receives the invoicing information and the target invoice type for the electronic invoice to be issued, generates an invoicing message, and sends the invoicing message to the message receiving module.
[0053] In this embodiment of the application, the message generation module receives invoicing information and the target invoice type for the electronic invoice to be issued, generates an invoicing message, and further sends the invoicing message to the message receiving module.
[0054] [HZTC-HXRJGS241002][HS2411341CCN]
[0055] In one example, the invoicing system has a configuration interface where users can enter configuration information and select the target invoice type for the electronic invoice to be issued. After the user completes the input, the message generation module generates an invoicing message based on the invoicing information configured by the user in the configuration interface and the target invoice type for the electronic invoice to be issued, and sends the invoicing message to the message receiving module.
[0056] In one example, the invoicing system can also connect to third-party applications and receive invoicing information and target invoice types for electronic invoices to be issued from third-party applications.
[0057] In one example, the invoice types in this application embodiment may include general VAT invoices and special VAT invoices.
[0058] S202, the message receiving module performs integrity verification on the received invoicing message, and sends the invoicing message to the invoicing module when the verification is successful.
[0059] In this embodiment, after receiving the invoicing message, the message receiving module performs integrity verification on the invoicing message, that is, determines whether the information included in the invoicing message is complete. Specifically, this can be whether the invoicing message includes invoicing information and the target invoice type for the electronic invoice to be issued, or whether the invoicing information includes necessary information, such as the company name, taxpayer identification number, and invoice amount. When the verification is successful, the message receiving module sends the invoicing message to the invoicing module.
[0060] S203, the invoicing module issues electronic invoices based on the received invoicing message.
[0061] In this embodiment of the application, after receiving the verified invoicing message, the invoicing module parses the invoicing message to issue an electronic invoice.
[0062] The electronic invoice issuance method provided in this application involves a message generation module of the invoicing system generating an invoicing message based on the invoicing information configured by the user in the configuration interface and the target invoice type to be issued. The message receiving module further verifies the integrity of the invoicing message, and upon successful verification, issues the electronic invoice through the invoicing module. This application, by verifying the integrity of the invoicing message, ensures its correctness and improves the accuracy of electronic invoice issuance.
[0063] Furthermore, the invoicing message in this embodiment includes invoicing information, the target invoice type for the electronic invoice to be issued, and a message tag. The message receiving module performs integrity verification on the received invoicing message, which may include the following steps:
[0064] S1021, the message receiving module parses the invoice message.
[0065] In this embodiment, the message receiving module parses the invoicing message to determine the content included in the invoicing information. Specifically, the complete invoicing message in this embodiment should include invoicing information, the target invoice type for the electronic invoice to be issued, and a message tag.
[0066] Specifically, in this embodiment of the application, the message tag is added by the message generation module. After receiving the invoicing information and the target invoice type of the electronic invoice to be issued, the message generation module generates a unique message tag. Based on the invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag, the invoicing message is generated to distinguish different invoicing messages. Furthermore, the message tag in this embodiment of the application can also be used to monitor the invoicing process. The message tag can be used to determine whether the invoicing message has been completed, and the message tag can be used to communicate between various modules to maintain the consistency of invoicing message transmission.
[0067] [HZTC-HXRJGS241002][HS2411341CCN]
[0068] S1022, the message receiving module determines that the invoicing message includes invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag, and confirms that the verification is successful.
[0069] In this embodiment of the application, after parsing the invoice message, the message receiving module determines the content included in the invoice message. When the message receiving module determines that the invoice message includes invoice information, the target invoice type to be issued as an electronic invoice, and a message tag, it determines that the verification is successful.
[0070] The message receiving module in this embodiment of the application verifies the consistency of the invoice message, thereby ensuring the integrity and correctness of the invoice message and improving the accuracy of electronic invoice issuance.
[0071] Furthermore, after the message receiving module determines that the invoicing message includes invoicing information, the target invoice type to be issued as an electronic invoice, and a message tag, this embodiment may also include the following steps:
[0072] S204, the message receiving module determines the first information type included in the invoice information and the second information type required for the electronic invoice to be issued based on the parsing result.
[0073] In this embodiment, after parsing the invoice message, the message receiving module determines the first information type included in the invoice information. Specifically, the information type includes a first information type and a second information type, which may include name, taxpayer identification number, amount, bank name, bank account number, address, telephone number, etc. It then determines the second information type required for issuing the electronic invoice of the target invoice type.
[0074] In one example, if the target invoice type is a general VAT invoice, the second information type is determined to include the company name and taxpayer identification number; if the target invoice type is a special VAT invoice, the second information type is determined to include the name, taxpayer identification number, bank, bank account number, address, and telephone number.
[0075] S205, the message receiving module determines that the first information type matches the second information type, and that the invoicing message includes invoicing information, the target invoice type of the electronic invoice to be issued, and a message tag, and confirms that the verification is successful.
[0076] In this embodiment of the application, after the message receiving module receives the first information type and the second information type, it compares the first information type and the second information type to determine whether the first information type and the second information type match. If the first information type matches the second information type, and the invoicing message includes invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag, the verification is confirmed to be successful.
[0077] Specifically, in the embodiments of this application, "matching" specifically means that the first information type and the second information type are completely identical, or that the first information type includes the second information type.
[0078] In one example, if the first information type includes name, taxpayer identification number, bank, and bank account number, and the second information type is name and taxpayer identification number, then the first information type and the second information type are determined to match.
[0079] In one example, if the first information type includes name, bank name, and bank account number, and the second information type includes name and taxpayer identification number, then it is determined that the first information type and the second information type do not match.
[0080] The message receiving module of this application determines the first information type included in the invoicing information and the second information type required for issuing the electronic invoice of the target invoice type. It matches the first information type and the second information type, and can perform multiple verifications. When the first information type matches the second information type and the invoicing message includes the invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag, the verification is confirmed to be successful. This can further ensure the correctness of the invoicing message and further improve the accuracy of electronic invoicing.
[0081] Furthermore, the invoicing system in this embodiment of the application also includes a parsing module, which, based on the received invoice...
[0082] [HZTC-HXRJGS241002][HS2411341CCN] Invoice information, before issuing an electronic invoice, the following steps may also be included:
[0083] S206, the message receiving module sends the invoice message to the parsing module.
[0084] In this embodiment of the application, when the message receiving module determines that the verification is successful, the message receiving module sends the invoice message to the parsing module, which is specifically used to parse the invoice message.
[0085] S207, the parsing module determines the invoice information based on the invoice message, and determines the electronic invoice style based on the target invoice type.
[0086] In this embodiment of the application, after parsing the invoice message, the parsing module determines the invoice information carried in the invoice message. At the same time, it determines the electronic invoice style based on the correspondence between the target invoice type and the electronic invoice style.
[0087] In one example, the layout of different electronic invoice styles in this application embodiment is different.
[0088] S208, the parsing module sends the invoice information and electronic invoice template to the invoice module.
[0089] In this embodiment of the application, after obtaining the invoice information and the electronic invoice template, the parsing module sends the invoice information and the electronic invoice template to the invoice issuing module, so that the invoice issuing module can issue an electronic invoice based on the invoice information and the electronic invoice template.
[0090] In one example, the invoicing system of this application embodiment further includes a message queue, which is specifically set between the parsing module and the invoicing module. After the parsing module obtains the invoicing information and the electronic invoice template, it stores the invoicing information and the electronic invoice template in the message queue. When the invoicing module is idle, it can read the invoicing information and the electronic invoice template from the message queue to issue an invoice using the invoicing information and the electronic invoice template.
[0091] In one example, the parsing module also retrieves message tags and stores the message tags, invoicing information, and e-invoice template in a message queue. The invoicing module can retrieve the message tags, invoicing information, and e-invoice template from the message queue to monitor the invoicing process through the message tags.
[0092] Furthermore, the parsing module sends the invoice information and electronic invoice template to the invoicing module, which may also include the following steps:
[0093] S2081, The parsing module determines the target invoicing information required to issue the target invoice type based on the target invoice type.
[0094] In this embodiment of the application, after parsing the invoice information, the parsing module obtains the target invoice type and determines the target invoice information required to issue the target invoice type based on the target invoice type.
[0095] In one example, if the target invoice type is a general VAT invoice, the required target invoice information is determined to include the name and taxpayer identification number. The name and taxpayer identification number are then filtered in the invoice information, and other invoice information is deleted.
[0096] S2082, the parsing module obtains the target invoice information from the invoice information, and sends the target invoice information and electronic invoice template to the invoice module.
[0097] In this embodiment of the application, the parsing module obtains the target invoice information from the invoice information and stores the target invoice information and the electronic invoice template in the message queue, so that the invoice module can obtain the target invoice information and the electronic invoice template from the message queue.
[0098] This application embodiment uses a parsing module to filter invoice information from the invoice information, which can filter out useless invoice information and thus improve the accuracy of electronic invoice issuance.
[0099] Furthermore, the invoicing module of this application embodiment issues an electronic invoice based on the target invoicing information and the electronic invoice template, which may include the following steps:
[0100] [HZTC-HXRJGS241002][HS2411341CCN]
[0101] S2083, the invoicing module retrieves the target invoicing information and electronic invoice template from the message queue.
[0102] In this embodiment of the application, after the parsing module stores the target invoicing information and the electronic invoice template in the message queue, the invoicing module retrieves the target invoicing information and the electronic invoice template from the message queue.
[0103] In one example, the invoicing module of this application embodiment retrieves the target invoicing information and electronic invoice template from the message queue when idle.
[0104] S2084, the invoicing module determines whether the target invoicing information meets the preset conditions.
[0105] In this embodiment, after obtaining the target invoice information, the invoicing module verifies the target invoice information to determine whether it meets preset conditions. Specifically, the invoicing module determines the preset conditions corresponding to the target invoice information based on its type. The invoicing system pre-stores preset conditions corresponding to various types of target invoice information, which can be set according to actual needs.
[0106] In one example, if the target invoice information is a name, the preset condition is the full name. That is, the input name is compared with the full name to determine whether the target invoice information meets the preset condition, i.e., whether the target invoice information is incorrect. For example, if the target invoice information is XX Company and the corresponding preset condition is XX Limited Company, then the target invoice information does not meet the preset condition.
[0107] In one example, if the target invoice information is an amount, the preset condition is the number of decimal places. That is, the number of decimal places of the input amount is compared with the preset number of decimal places to determine whether the target invoice information meets the preset condition, i.e., to determine whether the target invoice information is incorrect. For example, if the target invoice information is 54.12, the corresponding preset condition is 3 decimal places, then the target invoice information does not meet the preset condition.
[0108] S2085, When the invoicing module determines that the target invoicing information meets the preset conditions, it issues an electronic invoice based on the target invoicing information and the electronic invoice template.
[0109] In this embodiment of the application, when the invoicing module determines that the target invoicing information meets the preset conditions, that is, when it determines that the target invoicing information does not contain errors, the invoicing module uses the verified target invoicing information and the electronic invoice template to issue an electronic invoice, so as to improve the accuracy of issuing electronic invoices.
[0110] Further, please refer to Figure 3 As shown in the embodiment of this application, another method for issuing electronic invoices is provided and applied to an invoicing system, specifically including:
[0111] The message generation module receives invoicing information and the target invoice type for the electronic invoice to be issued, generates a unique message tag, and generates an invoicing message based on the invoicing information, the target invoice type for the electronic invoice to be issued, and the message tag.
[0112] The message receiving module parses the invoice message, determines the content included in the invoice information, identifies the first information type included in the invoice information, and determines the second information type required for issuing the electronic invoice of the target invoice type. It then determines whether the first information type and the second information type match. If the first information type matches the second information type, and the invoice message includes the invoice information, the target invoice type of the electronic invoice to be issued, and the message tag, the verification is confirmed to be successful.
[0113] The parsing module parses the invoicing message to determine the invoicing information carried within it. Simultaneously, based on the correspondence between the target invoice type and the electronic invoice format, it determines the electronic invoice format. Further, the parsing module obtains the target invoice type and, based on that, determines the target invoicing information required to issue the target invoice. The target invoicing information and the electronic invoice format are then stored in a message queue.
[0114] The invoicing module retrieves the target invoicing information and electronic invoice template from the message queue, and determines whether the target invoicing information meets the preset conditions. If the target invoicing information meets the preset conditions, the module issues an electronic invoice based on the target invoicing information and electronic invoice template.
[0115] Furthermore, embodiments of this application provide another invoicing system, specifically as follows: Figure 4 As shown, the invoicing system includes a message generation module 401, a message receiving module 402, a parsing module 403, and an invoicing module 404. The invoicing system of this embodiment is used to implement the corresponding electronic invoice issuance methods in the foregoing method embodiments and has the beneficial effects of the corresponding method embodiments, which will not be repeated here. Furthermore, the functional implementation of each module in the invoicing system of this embodiment can refer to the description of the corresponding parts in the foregoing method embodiments, which will also not be repeated here.
[0116] Reference Figure 5 This document illustrates a schematic diagram of an electronic device according to an embodiment of this application. The specific embodiments of this application do not limit the specific implementation of the electronic device.
[0117] like Figure 5 As shown, the electronic device may include: a processor 502, a communication interface 504, a memory 506, and a communication bus 508.
[0118] in:
[0119] The processor 502, communication interface 504, and memory 506 communicate with each other via communication bus 508.
[0120] Communication interface 504 is used to communicate with other electronic devices or servers.
[0121] The processor 502 is used to execute program 510, which can specifically execute the relevant steps in the above-described embodiment of the electronic invoice issuance method.
[0122] Specifically, program 510 may include program code that includes computer operation instructions.
[0123] Processor 502 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; or they may be processors of different types, such as one or more CPUs and one or more ASICs.
[0124] Memory 506 is used to store program 510. Memory 506 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.
[0125] Specifically, program 510 can be used to cause processor 502 to perform the following operations:
[0126] In an optional implementation, program 510 is further configured to ensure that the processor 502 performs the specific steps in program 510. The specific implementation of each step in program 510 can be found in the corresponding steps and units described in the above-described embodiments of the electronic invoice issuance method, and will not be repeated here. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the devices and modules described above can be referred to the corresponding process descriptions in the foregoing method embodiments, and will not be repeated here.
[0127] This application also provides a computer program product, including computer instructions that instruct a computing device to perform an operation corresponding to any of the electronic invoice issuance methods in the above-described multiple method embodiments.
[0128] It should be noted that, depending on the implementation needs, the various components / steps described in the embodiments of this application can be broken down into more components / steps, or two or more components / steps or parts of the operation of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of this application.
[0129] The methods described in the embodiments of this application can be implemented in hardware, firmware, or 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 as computer code downloaded over a network that is originally stored in a remote recording medium or a non-transitory machine-readable medium and will be stored in a local recording medium. Thus, the methods described herein can be stored as 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 is understood that the computer, processor, microprocessor controller, or programmable hardware includes storage components (e.g., RAM, ROM, flash memory, etc.) capable of storing or receiving software or computer code that, when accessed and executed by the computer, processor, or hardware, implements the electronic invoice issuance method described herein. Furthermore, when a general-purpose computer accesses code used to implement the electronic invoice issuance method shown herein, the execution of the code transforms the general-purpose computer into a dedicated computer for executing the electronic invoice issuance method shown herein.
[0130] Those skilled in the art will recognize that the units and method steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.
[0131] The above embodiments are only used to illustrate the embodiments of this application, and are not intended to limit the embodiments of this application. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the embodiments of this application. Therefore, all equivalent technical solutions also fall within the scope of the embodiments of this application, and the patent protection scope of the embodiments of this application should be defined by the claims.
Claims
1. A method for issuing electronic invoices, characterized in that, Applied to an invoicing system, the invoicing system including a message generation module, a message receiving module, and an invoicing module, the method includes: The message generation module receives invoicing information and the target invoice type for the electronic invoice to be issued, generates an invoicing message, and sends the invoicing message to the message receiving module. The message receiving module performs integrity verification on the received invoice message, and sends the invoice message to the invoice module when the verification is successful. The invoicing module issues the electronic invoice based on the received invoicing message.
2. The method according to claim 1, characterized in that, The invoicing message includes the invoicing information, the target invoice type for the electronic invoice to be issued, and a message tag; The message receiving module performs integrity verification on the received invoicing message, including: The message receiving module parses the invoice message; The message receiving module determines that the verification is successful after confirming that the invoicing message includes the invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag. The message generation module generates an invoice message based on the invoicing information configured by the user in the configuration interface and the target invoice type for which the electronic invoice to be issued is to be generated. The message generation module generates a unique message tag; The invoicing message is generated based on the invoicing information, the target invoice type to be issued as an electronic invoice, and the message tag.
3. The method according to claim 2, characterized in that, After the message receiving module determines that the invoicing message includes the invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag, the method further includes: The message receiving module determines the first information type included in the invoicing information and the second information type required for the electronic invoice to be issued based on the parsing result. The message receiving module determines that the verification is successful when it finds that the first information type matches the second information type, and that the invoicing message includes the invoicing information, the target invoice type of the electronic invoice to be issued, and the message tag.
4. The method according to claim 1, characterized in that, The invoicing system also includes a parsing module; Before the invoicing module issues the electronic invoice based on the received invoicing message, the method further includes: The message receiving module sends the invoicing message to the parsing module; The parsing module determines the invoicing information based on the invoicing message, and determines the electronic invoice style based on the target invoice type; The parsing module sends the invoicing information and the electronic invoice template to the invoicing module; [HZTC-HXRJGS241002][HS2411341CCN] The invoicing module issues the electronic invoice based on the received invoicing message, including: The invoicing module issues the electronic invoice based on the invoicing information and the electronic invoice template.
5. The method according to claim 4, characterized in that, The parsing module sends the invoicing information and the electronic invoice template to the invoicing module, including: The parsing module determines the target invoicing information required to issue the target invoice type based on the target invoice type. The parsing module obtains the target invoice information from the invoice information, and sends the target invoice information and the electronic invoice template to the invoice module; The invoicing module issues the electronic invoice based on the invoicing information and the electronic invoice template, including: The invoicing module issues the electronic invoice based on the target invoicing information and the electronic invoice template.
6. The method according to claim 5, characterized in that, The step of obtaining the target invoice information from the invoice information and sending the target invoice information and the electronic invoice template to the invoice module includes: The parsing module stores the target invoicing information and the electronic invoice template in a message queue, so as to send the target invoicing information and the electronic invoice template to the invoicing module through the message queue.
7. The method according to claim 6, characterized in that, The invoicing module issues the electronic invoice based on the target invoicing information and the electronic invoice template, including: The invoicing module obtains the target invoicing information and the electronic invoice template from the message queue; The invoicing module determines whether the target invoicing information meets preset conditions; When the invoicing module determines that the target invoicing information meets the preset conditions, it issues the electronic invoice based on the target invoicing information and the electronic invoice template.
8. An invoicing system, characterized in that, The invoicing system includes a message generation module, a message receiving module, and an invoicing module, and the invoicing system is used to execute the electronic invoice issuance method according to any one of claims 1-7.
9. An electronic device, comprising: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the electronic invoice issuance method as described in any one of claims 1-7.
10. A computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the electronic invoice issuance method as described in any one of claims 1-7.