Electricity counting invoice delivery method and device, storage medium and server

Abstract

The embodiment of the invention discloses a digital-to-electronic invoice delivery method and device, a storage medium and a server, and relates to the field of financial processing. The method comprises the following steps: acquiring invoicing information; verifying the integrity and correctness of the invoicing information; if the verification is passed, generating a digital-to-electronic invoice in an electronic file format according to the invoicing information; performing signature processing on the original digital-to-electronic invoice by using the private key; querying a preset email address of a receiver according to the invoicing information; according to the invention, the signed digital-to-electronic invoice is sent to the receiver according to the mailbox address, the tampering and counterfeiting of data can be effectively prevented, the security of the digital-to-electronic invoice is greatly improved, and the manual operation and intervention are reduced by realizing the processes of subscription, automatic processing and the like, so that the generation, transmission and delivery processes of the digital-to-electronic invoice are more efficient and quicker.

Description

Technical Field

[0001] The present application relates to the field of financial processing, and in particular to a method, device, storage medium and server for delivering digital invoices. Background Art

[0002] Traditional invoice delivery has many inconveniences, such as easy loss, large storage space requirements, difficulty in finding, poor anti-counterfeiting performance, etc. With the rapid development of mobile Internet, digital invoices, as a new form of bills, are becoming more and more popular in the market due to their convenience, speed, easy verification and management. At the same time, traditional electronic bill delivery methods have certain limitations, including: security issues during the delivery process, users need to fill in the billing information before the invoice can be issued, resulting in low delivery efficiency. Summary of the invention

[0003] The embodiments of the present application provide a method, device, storage medium and server for delivering digital electricity invoices, which can solve the problems of low security and low efficiency in the delivery process of digital electricity invoices in the prior art. The technical solution is as follows: In a first aspect, an embodiment of the present application provides a method for delivering a digital invoice, the method comprising: Get invoicing information; Verify the completeness and correctness of the billing information; If the verification is successful, a digital invoice in electronic file format is generated according to the invoicing information; Use the private key to sign the digital electricity invoice; Querying the preset recipient's email address according to the invoicing information; The signed digital invoice is sent to the recipient according to the email address.

[0004] In a second aspect, an embodiment of the present application provides a delivery device for a digital invoice, the device comprising: An acquisition unit, used to acquire invoicing information; A verification unit, used to verify the integrity and correctness of the invoicing information; A generating unit, for generating a digital invoice in an electronic file format according to the invoicing information if the verification is passed; A signature unit, used to sign the digital electricity invoice using a private key; A query unit, used to query a preset recipient's email address according to the invoicing information; The sending unit is used to send the signed digital invoice to the recipient according to the email address.

[0005] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0006] In a fourth aspect, an embodiment of the present application provides a server, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0007] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least: By introducing electronic signature technology, digital invoices are digitally signed to ensure the authenticity and integrity of invoices in all links such as generation, transmission, and storage, effectively preventing data tampering and forgery, thereby greatly improving the security of digital invoices. Encryption technology is further used to encrypt digital invoices, so that only legitimate users with the corresponding decryption keys can access and view the invoice content, further enhancing the confidentiality and security of invoices. By implementing processes such as subscription and automated processing, manual operations and intervention are reduced, making the generation, transmission, and delivery of digital invoices more efficient and faster. This not only shortens the delivery cycle of invoices, but also reduces the risk of human error. The instant generation and transmission of digital invoices enables the recipient to quickly obtain invoice information without waiting for mailing or physical delivery, thereby improving overall business processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0009] Figure 1 It is a schematic diagram of the network architecture provided by the embodiment of the present application; Figure 2 It is a flowchart of the method for delivering digital electricity invoices provided in an embodiment of the present application; Figure 3 It is a structural schematic diagram of a digital invoice delivery device provided by the present application; Figure 4 It is a structural diagram of a server provided by this application. DETAILED DESCRIPTION

[0010] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0011] It should be noted that the method for delivering digital electricity invoices provided in this application is generally executed by a server, and accordingly, the delivery device for digital electricity invoices is generally set in the server.

[0012] Figure 1 An exemplary system architecture of a digital electronic invoice delivery method or a digital electronic invoice delivery device that can be applied to the present application is shown.

[0013] like Figure 1 As shown, the system architecture may include: a server 101 and a terminal device 102. The server 101 and the terminal device 102 may communicate with each other through a network, and the network is used as a medium for providing communication links between the above-mentioned units. The network may include various types of wired communication links or wireless communication links, for example: the wired communication link includes an optical fiber, a twisted pair or a coaxial cable, etc., and the wireless communication link includes a Bluetooth communication link, a wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link or a microwave communication link, etc.

[0014] The server 101 generates a digital electricity invoice and sends the generated digital electricity invoice to the terminal device 102 .

[0015] It should be noted that the server 101 and the terminal device 102 can be hardware or software. When the server 101 and the terminal device 102 are hardware, they can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the server 101 and the terminal device 102 are software, they can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module, which is not specifically limited here.

[0016] Various communication client applications can be installed on the terminal device of the present application, such as: video recording applications, video playback applications, voice interaction applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0017] The terminal device can be hardware or software. When the terminal device is hardware, it can be various terminal devices with display screens, including but not limited to smart phones, tablet computers, laptops, and desktop computers. When the terminal device is software, it can be installed in the terminal devices listed above. It can be implemented as multiple software or software modules (for example, to provide distributed services), or it can be implemented as a single software or software module, which is not specifically limited here.

[0018] When the terminal device is hardware, a display device and a camera may be installed thereon. The display device may be any device capable of realizing a display function, and the camera is used to collect video streams; for example, the display device may be a cathode ray tube display (CR), a light-emitting diode display (LED), an electronic ink screen, a liquid crystal display (LCD), a plasma display panel (PDP), etc. The user may use the display device on the terminal device to view displayed text, pictures, videos and other information.

[0019] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be used as required.

[0020] The following will be combined with the attached Figure 2 , the delivery method of the digital invoice provided in the embodiment of the present application is described in detail. Among them, the delivery device of the digital invoice in the embodiment of the present application can be Figure 1 The server shown.

[0021] See also Figure 2 , which is a flow chart of a method for delivering a digital invoice in accordance with an embodiment of the present application. Figure 2 As shown, the method of the embodiment of the present application may include the following steps: S201. Obtain invoicing information.

[0022] The server receives invoicing requests from the invoicing system, user input, or internal system through interfaces (such as Web API, RESTful services, etc.). The invoicing information specifically includes the invoice type (such as special VAT invoice, ordinary invoice, etc.), invoicing date, purchaser information (including name, taxpayer identification number, address, etc.), seller information (including name, taxpayer identification number, address, etc.), goods name, specifications, quantity, and possible other information (such as unit price, tax rate, tax amount, etc.). This information is submitted to the server in a structured form (such as JSON or XML), and the server parses it and stores it in memory or database for subsequent processing.

[0023] In some embodiments of the present application, the server may receive a QR code uploaded by the invoicing party and parse the QR code to obtain the invoicing information.

[0024] The server provides an interface (such as Web API, RESTful service, etc.) to allow the invoicing party to upload a QR code image containing the invoicing information. The invoicing party can use a mobile phone, scanner, or any device that can generate a QR code to encode the invoicing information into a QR code and upload it to the server through the interface. The QR code image received by the server usually exists in the form of binary data or a Base64-encoded string. Once the server receives the QR code image, it will use a QR code parsing library (such as ZXing, ZBar, etc.) to parse the QR code. The parsing process identifies the encoding format in the QR code (such as QRCode, Data Matrix, etc.) and decodes the text or data in it. These texts or data usually contain the encoded string of the invoicing information, which may be JSON, XML, or other structured format data that has been specifically encoded (such as URL encoding, Base64 encoding, etc.).

[0025] S202. Verify the integrity and correctness of the invoicing information.

[0026] The server performs a comprehensive validation of the received invoicing information. This includes checking whether all required fields have been filled in and whether the field values ​​comply with the predetermined formats and rules (such as date format, length and character set requirements of taxpayer identification numbers, format of address information, etc.). In addition, it will verify whether the invoice type is legal, whether the buyer and seller information is valid (it may need to be checked with the tax system or internal database), and the logical rationality of information such as the name, specification, and quantity of the goods. If any non-compliance is found, the server will return an error prompt and require resubmission or correction of the invoicing information.

[0027] S203. If the verification is successful, generate a digital invoice in electronic file format according to the invoicing information.

[0028] Among them, once the invoicing information is verified, the server will generate an electronic invoice file based on this information. This usually involves selecting an electronic invoice template that meets the standards of the State Administration of Taxation or industry, and filling in the invoicing information into the corresponding position of the template. The generated electronic invoice file will clearly display the invoice type, invoicing date, buyer and seller information, a detailed list of goods or services (including name, specifications, quantity, etc.), and possible other information (such as unit price, tax rate, tax amount, remarks, etc.). The electronic invoice file will be saved in an appropriate format (such as OFD, PDF, etc.) and is ready for the next step of processing.

[0029] S204. Use the private key to sign the digital invoice.

[0030] In order to ensure the immutability and authenticity of the electronic invoice, the server will use its private key to digitally sign the generated electronic invoice file. This usually involves the following steps: first, use a hash algorithm (such as SHA-256) to calculate the unique hash value of the electronic invoice file (i.e., the digital fingerprint of the file); then, use the server's private key to encrypt the hash value to generate a digital signature; finally, attach the digital signature to the electronic invoice file or store it in a separate file associated with the electronic invoice. In this way, the recipient can use the server's public key to verify the validity of the digital signature, thereby confirming the integrity and authenticity of the electronic invoice.

[0031] S205: Query the preset recipient's email address according to the invoicing information.

[0032] Before sending an electronic invoice, the server needs to know the recipient's email address. This is usually achieved by querying an internal database or system, where the purchaser's contact information (including email address) is stored. The server will use the purchaser's information (such as name or taxpayer identification number) as a query condition to retrieve the corresponding email address from the database. If a matching email address is found, it will proceed to the next step; if not found or the email address is invalid, the server may need to return an error prompt or require the user to manually enter the email address.

[0033] S206. Send the signed digital invoice to the recipient according to the email address.

[0034] The server will use the SMTP protocol or email sending service to send the signed electronic invoice file as an attachment to the recipient's email address via email. When constructing the email, the server will set the appropriate email subject (such as "Your electronic invoice has been issued"), the body (which may contain brief information about the invoice, a download link, or instructions for viewing the invoice), and the attachment (i.e. the signed electronic invoice file). After the email is sent, the server will record the sending log, including the sending time, the recipient's email address, the email status, and other information. If an error occurs during the sending process (such as network problems, invalid email address, etc.), the server will record the corresponding error information and may try to resend or notify relevant personnel to handle it.

[0035] In some embodiments of the present application, before obtaining the invoicing information, the method further includes: Set the mapping relationship between the invoicing information and the email address based on the invoicing party's setting instructions.

[0036] Among them, the server first receives the setting instructions from the invoicing party. These instructions are usually submitted to the server through a web interface, API interface or a special configuration tool. The server parses the received setting instructions and extracts the invoicing information (such as the purchaser's name, taxpayer identification number, etc.) and the corresponding email address. Based on the parsed invoicing information and email address, the server establishes a mapping relationship between them in an internal database or configuration file. This mapping relationship can be one-to-one or one-to-many (that is, one invoicing information corresponds to multiple recipient email addresses), depending on the needs and settings of the invoicing party. The established mapping relationship is stored in a secure and reliable database to ensure that the corresponding email address can be retrieved quickly and accurately when needed. The server may send a verification email or notification to the invoicing party to confirm that the mapping relationship has been correctly set and stored.

[0037] Through this step, the server can quickly find the corresponding recipient's email address based on the invoicing information, and send the electronic invoice to the correct recipient in the subsequent steps. This not only improves the accuracy and efficiency of invoice delivery, but also reduces the problem of invoices not being delivered or being delivered incorrectly due to incorrect email addresses.

[0038] In some embodiments of the present application, an encryption key is generated; Using the encryption key to encrypt the signed digital invoice; Upload the encrypted digital invoice to the database of the cloud service platform.

[0039] Before sending the electronic invoice, the server needs to generate a unique encryption key. This key can be a random number or string automatically generated based on an encryption algorithm (such as AES, RSA, etc.). The generation of encryption keys should ensure sufficient randomness and complexity to resist cracking and guessing attacks. After the key is generated, the server can store it in a secure location, such as a hardware security module (HSM) or an encryption key management service to ensure the security and availability of the key.

[0040] After the digital signature is completed, the server will use the generated encryption key to encrypt the signed electronic invoice. The encryption process usually involves taking the electronic invoice data (including the digital signature) as input, processing it through an encryption algorithm, and outputting the encrypted data. The encrypted electronic invoice cannot be directly read or modified by unauthorized parties. Only the legitimate recipient who holds the corresponding decryption key can decrypt and view the invoice content. This can effectively protect the confidentiality and integrity of the electronic invoice.

[0041] After encryption is completed, the server uploads the encrypted electronic invoice to the database of the cloud service platform. The cloud service platform provides a secure, reliable, and scalable storage environment to ensure the long-term preservation and quick access of electronic invoice data. During the upload process, the server can use the API interface or SDK provided by the cloud service platform to transmit the encrypted electronic invoice data to the cloud through security protocols such as HTTPS. The cloud service platform will further perform security processing and storage management on the uploaded data to ensure the security and availability of the data.

[0042] In some embodiments of the present application, it also includes: Receiving a user's invoice download request to the cloud service platform; the invoice download request carries a user ID and an invoice number; Verifying the identity of the user according to the user identifier; After the identity verification is passed, the target number of electronic invoices corresponding to the invoice number will be sent to the user.

[0043] The user initiates an invoice download request through the cloud service platform's web interface, mobile application, or other client tools. This request contains the user ID (such as user name, mobile phone number, email address, etc.) and the invoice number, which is used to specify the electronic invoice to be downloaded. After receiving this request, the server will parse it into a processable data structure and prepare for subsequent identity authentication and invoice retrieval operations.

[0044] The server will first verify the user's identity based on the user ID provided in the user request. This process may involve the following steps: Query user information: The server will query the user information associated with the user ID in its internal database or the user management system of the cloud service platform.

[0045] Verify credentials: If the system requires the user to log in or authenticate, the server also verifies that the user has provided valid credentials (such as a password, verification code, token, etc.).

[0046] Check permissions: After confirming the user's identity, the server also needs to check whether the user has the right to download the electronic invoice in the request. This may involve checking the user's role, permissions, or the access control list (ACL) of the invoice.

[0047] If the user passes the authentication and permission check, the server will do the following to send the electronic invoice: Retrieve invoice data: The server retrieves the electronic invoice data matching the invoice number in the user's request from the cloud service platform's database. Since the electronic invoices have been previously encrypted and stored in the cloud, the server needs to decrypt these data first (if they are still encrypted).

[0048] Send Invoice: After decryption, the server will send the electronic invoice to the user in an appropriate format such as PDF, OFD, etc. This can be achieved through email, web interface download link, mobile in-app notification, etc.

[0049] Logging: For audit and tracking purposes, the server will also record log information of invoice downloads, including download time, user ID, invoice number, etc.

[0050] Through the above steps, the server can safely and reliably process users' invoice download requests to the cloud service platform and ensure that only authenticated and authorized users can access and download their electronic invoices.

[0051] In some embodiments of the present application, it also includes: The transaction record of the digital electricity invoice is uploaded to the blockchain network, and the transaction record includes: generation record, download record and transfer record.

[0052] Transaction records refer to records of various operations and events related to digital invoices, including but not limited to: Generation record: record the basic information of the invoice, such as the generation time, generator, invoice number, and invoice content.

[0053] Download records: record the time each invoice is downloaded, the downloader (user ID), download method and other information.

[0054] Transfer records: If the ownership or use rights of an invoice are transferred (for example, during an invoice reimbursement or assignment), these transfer events will also be recorded.

[0055] The process of the server uploading the above transaction records to the blockchain network essentially creates a series of new blocks or transaction records on the blockchain, which are verified and confirmed by all participating nodes through encryption algorithms and consensus mechanisms. Once uploaded successfully, these transaction records become an unalterable part of the blockchain, and any attempt to modify or delete them will be detected and rejected by other nodes in the network.

[0056] Uploading the transaction records of digital invoices to the blockchain network can bring the following significant advantages: Immutability: The distributed ledger nature of blockchain ensures that transaction records cannot be tampered with once generated, thereby improving the authenticity and credibility of invoice data.

[0057] Transparency: All transaction records on the blockchain are publicly visible (but privacy protection can be achieved through technical means), which makes the circulation and use of invoices more transparent and easier to supervise and audit.

[0058] Traceability: Since transaction records on the blockchain are arranged in chronological order, the generation, circulation and use of invoices can be easily tracked, providing strong support for tax audits and dispute resolution.

[0059] In some embodiments of the present application, the step of generating a digital invoice in an electronic file format according to the invoicing information includes: Generate digital invoices in electronic file format according to the rules issued by the tax bureau.

[0060] Among them, the server verifies the received invoice data to ensure that all necessary fields are filled in and meet the format and logic requirements specified by the tax bureau. Verification may include checking data integrity, format correctness, tax calculation accuracy, etc. According to the electronic invoice XML template provided by the tax bureau, the server converts the verified invoice data into XML format. The XML structure contains all the necessary elements of the invoice and is organized according to the hierarchy and naming rules specified by the tax bureau. The server uses the company's private key to digitally sign the invoice data in XML format to ensure the authenticity and non-tamperability of the invoice. At the same time, the server may encrypt the invoice data to protect the security of sensitive information. The server converts the invoice data in XML format into PDF or other electronic file formats approved by the tax bureau. During the conversion process, the server ensures that the layout, font size, information display, etc. of the invoice comply with the regulations of the tax bureau.

[0061] The embodiments of the present application have the following beneficial effects when delivering digital invoices: By introducing electronic signature technology, digital invoices are digitally signed, ensuring the authenticity and integrity of invoices in all links such as generation, transmission, and storage, effectively preventing data tampering and forgery, thereby greatly improving the security of digital invoices. Encryption technology is further used to encrypt digital invoices, so that only legitimate users with corresponding decryption keys can access and view the invoice content, further enhancing the confidentiality and security of invoices.

[0062] By implementing subscription and automated processing, manual operations and intervention are reduced, making the generation, transmission and delivery of digital invoices more efficient and faster. This not only shortens the delivery cycle of invoices, but also reduces the risk of human error. The instant generation and transmission of digital invoices enables the recipient to quickly obtain invoice information without waiting for mailing or physical delivery, thereby improving overall business processing efficiency.

[0063] The transaction records of digital invoices are uploaded to the blockchain network, and the distributed ledger characteristics and immutability of the blockchain are utilized to ensure the security and credibility of the data. Any modification or deletion of the data will be detected and rejected by other nodes in the network, thus effectively preventing the risk of malicious tampering of the data. The transaction records on the blockchain are publicly visible (but the privacy information is protected), making the circulation and use of digital invoices more transparent and convenient for supervision and auditing. At the same time, through the chain data structure of the blockchain, the generation, circulation and use history of invoices can be easily tracked, providing strong support for tax audits and dispute resolution.

[0064] The promotion and application of digital invoices have greatly reduced the use of paper invoices, and reduced the consumption and dependence on resources such as paper, printing, and mailing. Since digital invoices are stored in digital form, they do not need to occupy a large amount of physical storage space, thus saving the company's storage costs. The introduction of automated processing procedures reduces the need for manual operation and management, and reduces the company's management costs. At the same time, the easy query and easy management features of digital invoices also improve the company's operational efficiency.

[0065] The following are device embodiments of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0066] See also Figure 3 , which shows a schematic diagram of the structure of a delivery device for digital invoices provided by an exemplary embodiment of the present application, hereinafter referred to as device 3. The device 3 can be implemented as all or part of the server through software, hardware or a combination of both. The device 3 includes: an acquisition unit 301, a verification unit 302, a generation unit 303, a signature unit 304, a query unit 305 and a sending unit 306.

[0067] An acquisition unit 301 is used to acquire invoicing information; Verification unit 302, used to verify the integrity and correctness of the invoicing information; A generating unit 303 is used to generate a digital invoice in an electronic file format according to the invoicing information if the verification is passed; The signature unit 304 is used to sign the digital electricity invoice using a private key; A query unit 305 is used to query a preset recipient's email address according to the invoicing information; The sending unit 306 is used to send the signed digital invoice to the recipient according to the email address.

[0068] In one or more possible embodiments, it further includes: The setting unit is used to set the mapping relationship between the invoicing information and the email address based on the setting instruction of the invoicing party.

[0069] In one or more possible embodiments, it further includes: An upload unit, used to generate an encryption key; Using the encryption key to encrypt the signed digital invoice; Upload the encrypted digital invoice to the database of the cloud service platform.

[0070] In one or more possible embodiments, it further includes: A download unit, used to receive a user's invoice download request to the cloud service platform; the invoice download request carries a user identifier and an invoice number; Verifying the identity of the user according to the user identifier; After the identity verification is passed, the target number of electronic invoices corresponding to the invoice number will be sent to the user.

[0071] In one or more possible embodiments, The sending unit 306 is also used to upload the transaction record of the digital electricity invoice to the blockchain network, and the transaction record includes: generation record, download record, modification record and transfer record.

[0072] In one or more possible embodiments, generating a digital invoice in an electronic file format according to the invoicing information includes: Generate digital invoices in electronic file format according to the rules issued by the tax bureau.

[0073] In one or more possible embodiments, obtaining the billing information includes: Receive the QR code uploaded by the invoicing party, and parse the QR code to obtain the invoicing information.

[0074] It should be noted that the device 3 provided in the above embodiment only uses the division of the above functional modules as an example when executing the delivery method of digital electronic invoices. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above functions. In addition, the delivery device of digital electronic invoices provided in the above embodiment and the delivery method embodiment of digital electronic invoices belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

[0075] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0076] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 2 The method steps of the embodiment shown in the figure can be found in the specific implementation process. Figure 2 The specific description of the illustrated embodiment will not be repeated here.

[0077] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the method for delivering digital electronic invoices as described in the above embodiments.

[0078] See also Figure 4 , which is a schematic diagram of the structure of a server provided in the embodiment of the present application. Figure 4 As shown, the server 400 may include: at least one processor 401 , at least one network interface 404 , a user interface 403 , a memory 405 , and at least one communication bus 402 .

[0079] The communication bus 402 is used to realize the connection and communication between these components.

[0080] The user interface 403 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 403 may also include a standard wired interface and a wireless interface.

[0081] The network interface 404 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0082] Among them, the processor 401 may include one or more processing cores. The processor 401 uses various interfaces and lines to connect various parts within the entire server 400, and executes various functions and processes data of the server 400 by running or executing instructions, programs, code sets or instruction sets stored in the memory 405, and calling data stored in the memory 405. Optionally, the processor 401 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (ProgrammableLogic Array, PLA). The processor 401 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 401, and it can be implemented separately through a chip.

[0083] Among them, the memory 405 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 405 includes a non-transitory computer-readable storage medium. The memory 405 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 405 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 405 may also be optionally at least one storage device located away from the aforementioned processor 401. As Figure 4 As shown, the memory 405 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an application program.

[0084] exist Figure 4In the server 400 shown in FIG. 1 , the user interface 403 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 401 can be used to call the application stored in the memory 405 and specifically execute the following steps: Figure 2 The specific process can be referred to Figure 2 As shown, no further description is given here.

[0085] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0086] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A method for delivering a digital invoice, characterized in that: include: Get invoicing information; Verify the completeness and correctness of the billing information; If the verification is successful, a digital invoice in electronic file format is generated according to the invoicing information; Use the private key to sign the digital electricity invoice; Querying the preset recipient's email address according to the invoicing information; The signed digital invoice is sent to the recipient according to the email address.

2. The method according to claim 1, characterized in that Before obtaining the billing information, the method further includes: Set the mapping relationship between the invoicing information and the email address based on the invoicing party's setting instructions.

3. The method according to claim 1 or 2, characterized in that: Also includes: Generate encryption keys; Using the encryption key to encrypt the signed digital invoice; Upload the encrypted digital invoice to the database of the cloud service platform.

4. The method according to claim 3, characterized in that Also includes: Receiving a user's invoice download request to the cloud service platform; the invoice download request carries a user ID and an invoice number; Verifying the identity of the user according to the user identifier; After the identity verification is passed, the target number of electronic invoices corresponding to the invoice number will be sent to the user.

5. The method according to claim 1, 2 or 4, characterized in that: Also includes: The transaction records of the digital invoice are uploaded to the blockchain network, and the transaction records include: generation records, download records, modification records and transfer records.

6. The method according to claim 5, characterized in that The step of generating a digital invoice in an electronic file format according to the invoicing information includes: Generate digital invoices in electronic file format according to the rules issued by the tax bureau.

7. The method according to claim 1 or 2 or 4 or 6, characterized in that: The obtaining of the billing information includes: Receive the QR code uploaded by the invoicing party, and parse the QR code to obtain the invoicing information.

8. A delivery device for digital invoices, characterized in that: include: An acquisition unit, used to acquire invoicing information; A verification unit, used to verify the integrity and correctness of the invoicing information; A generating unit, for generating a digital invoice in an electronic file format according to the invoicing information if the verification is passed; A signature unit, used to sign the digital electricity invoice using a private key; A query unit, used to query a preset recipient's email address according to the invoicing information; The sending unit is used to send the signed digital invoice to the recipient according to the email address.

9. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps as claimed in any one of claims 1 to 7.

10. A server, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 7.

Images