Electronic invoice processing based on virtual mailbox

Abstract

Embodiments of the present description provide an electronic invoice processing method and apparatus based on a virtual mailbox. The electronic invoice processing method based on the virtual mailbox comprises: in a process of parsing electronic invoice mail, receiving, by means of the virtual mailbox, an electronic invoice mail sent by an invoice platform, the invoice platform creating the electronic invoice mail on the basis of a transaction bill, and sending the mail on the basis of a virtual mailbox address configured by an invoice service for the virtual mailbox; parsing the electronic invoice mail after receiving the electronic invoice mail, and determining an invoice acquisition type according to the parsing result; and performing invoice acquisition according to an invoice acquisition mode corresponding to the invoice acquisition type, thereby realizing acquisition of an electronic invoice by means of parsing the electronic invoice mail.

Description

Electronic invoice processing based on virtual mailbox Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a method and device for processing electronic invoices based on a virtual mailbox. Background Art

[0002] With the continuous development and promotion of the Internet, the application scope of online services provided based on the Internet has become wider and wider, and has gradually covered most users. In this case, various forms of online service scenarios have emerged. For example, after applying for an electronic invoice online and sending the electronic invoice to the user's designated mailbox, the electronic invoice can be extracted by scanning the email of the electronic invoice in the mailbox and automatically parsing the email. In the process of scanning and parsing the email in the mailbox, other emails in the mailbox will be scanned, which may pose a risk of data leakage. Summary of the Invention

[0003] One or more embodiments of the present specification provide an electronic invoice processing method based on a virtual mailbox, comprising: receiving an electronic invoice email sent by an invoice platform through a virtual mailbox, wherein the electronic invoice email is created based on a transaction bill and is sent based on a virtual mailbox address configured for the virtual mailbox by the invoice service; parsing the electronic invoice email in the virtual mailbox, and determining the invoice acquisition type based on the parsing result; acquiring the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

[0004] One or more embodiments of the present specification provide an electronic invoice processing device based on a virtual mailbox, including: an invoice email acquisition module, configured to receive an electronic invoice email sent by an invoice platform through a virtual mailbox, wherein the electronic invoice email is created based on a transaction bill and is sent based on a virtual mailbox address configured for the virtual mailbox by the invoice service; an invoice email parsing module, configured to parse the electronic invoice email in the virtual mailbox and determine the invoice acquisition type based on the parsing result; an invoice acquisition module, configured to acquire an invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

[0005] One or more embodiments of the present specification provide an electronic invoice processing device based on a virtual mailbox, comprising: a processor; and a memory configured to store computer-executable instructions, wherein the computer-executable instructions, when executed, cause the processor to: receive an electronic invoice email sent by an invoice platform through a virtual mailbox, wherein the electronic invoice email is created based on a transaction bill and is sent based on a virtual mailbox address configured for the virtual mailbox by an invoice service; parse the electronic invoice email in the virtual mailbox, and determine the invoice acquisition type based on the parsing result; and acquire the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain the electronic invoice.

[0006] One or more embodiments of the present specification provide a computer-readable storage medium for storing computer-executable instructions, which implement the following process when executed: receiving an electronic invoice email sent by an invoice platform through a virtual mailbox, wherein the electronic invoice email is created based on a transaction bill and is sent based on a virtual mailbox address configured for the virtual mailbox by an invoice service; parsing the electronic invoice email in the virtual mailbox, and determining the invoice acquisition type based on the parsing result; acquiring the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0008] FIG1 is a schematic diagram of an implementation environment of an electronic invoice processing method based on a virtual mailbox provided in one or more embodiments of this specification.

[0009] FIG2 is a flowchart of a method for processing electronic invoices based on a virtual mailbox provided in one or more embodiments of this specification.

[0010] FIG3 is a flowchart of a method for processing electronic invoices based on a virtual mailbox, which is applied to a user invoice processing scenario and provided by one or more embodiments of this specification.

[0011] FIG4 is a flowchart of a method for processing electronic invoices based on a virtual mailbox, which is applied to an institutional invoice processing scenario, provided in one or more embodiments of this specification.

[0012] FIG5 is a flowchart of a method for processing electronic invoices based on a virtual mailbox and applied to an institutional payment scenario, provided in one or more embodiments of this specification.

[0013] FIG6 is a schematic diagram of an embodiment of an electronic invoice processing device based on a virtual mailbox provided by one or more embodiments of this specification.

[0014] FIG7 is a schematic diagram of the structure of an electronic invoice processing device based on a virtual mailbox provided by one or more embodiments of this specification. DETAILED DESCRIPTION

[0015] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this document.

[0016] The electronic invoice processing method based on a virtual mailbox provided in one or more embodiments of this specification is applicable to the implementation environment of electronic invoice processing. Referring to Figure 1, the implementation environment at least includes: a server 101, on which the server 101 runs an invoice service server, which is used to perform virtual mailbox management, email parsing, electronic invoice processing and other related processes; an invoice platform 102, which is used to generate electronic invoices, create and send electronic invoice emails; and a user terminal 103 of a user or an institution terminal 104 of an institution, through which the user accesses the invoice platform 102 to apply for electronic invoices, and the institution similarly accesses the invoice platform 102 to apply for electronic invoices through the institution terminal 104; in addition, an invoice service client is also running on the user terminal 103 or the institution terminal 104, and the specific form of the client can be an application, a subroutine within the application, a service module within the application, or a web program.

[0017] The server 101 can be a single server, a server cluster consisting of several servers, or one or more cloud servers in a cloud computing platform; the user terminal 103 or the institutional terminal 104 can specifically be a mobile phone, a personal computer, a tablet computer, an e-book reader, a device for information interaction based on VR (Virtual Reality, virtual reality technology), a vehicle-mounted terminal, an IoT device, a wearable smart device, a laptop computer, a desktop computer, etc.

[0018] In this implementation environment, during the electronic invoice application process, the user applies for an invoice through the user terminal 103 or the institution applies for an invoice through the institution terminal 104 to the invoice platform 102, and submits a virtual email address during the invoice application process. The virtual email address is configured by the invoice service for the virtual email address. After receiving the invoice application, the invoice platform 102 creates an electronic invoice email based on the transaction bill and sends the electronic invoice email to the virtual email address.

[0019] After the invoice platform 102 sends the electronic invoice email, the invoice service receives the electronic invoice email sent by the invoice platform 102 through the virtual mailbox, and parses and processes the received electronic invoice email. Specifically, the electronic invoice email in the virtual mailbox is parsed, the invoice acquisition type is determined according to the parsing result, and the invoice is acquired according to the invoice acquisition method corresponding to the invoice acquisition type to obtain the electronic invoice.

[0020] This specification provides one or more embodiments of a method for processing electronic invoices based on a virtual mailbox as follows.

[0021] 2 , the electronic invoice processing method based on a virtual mailbox provided in this embodiment is applied to invoice services. The method specifically includes steps S202 to S206 .

[0022] Step S202: Receive the electronic invoice email sent by the invoice platform through the virtual mailbox.

[0023] The virtual mailbox described in this embodiment refers to an electronic mailbox that receives and stores emails through an email receiving server. A virtual mailbox can also be an email storage space configured with an email receiving server to receive and store emails. For example, a virtual mailbox can also be an email storage space that does not have user login, email sending, or email forwarding functions.

[0024] The virtual mailbox is configured with a virtual email address, which is an email address used to send emails to the virtual mailbox, that is, an email address for receiving emails in the virtual mailbox. In this embodiment, the virtual mailbox is provided by the invoice service, that is, the virtual mailbox can be an email storage space provided by the invoice service for receiving and storing emails. Optionally, the virtual mailbox address is obtained after the invoice service activates the virtual mailbox. The applicant for activating the virtual mailbox can be a user or an organization.

[0025] Specifically, the virtual mailbox includes: the user virtual mailbox obtained by the user after activating the virtual mailbox in the invoice service, and / or the institution virtual mailbox obtained by the institution after activating the virtual mailbox in the invoice service; accordingly, the virtual mailbox address configured by the virtual mailbox includes: the virtual mailbox address of the user virtual mailbox (user mailbox address), and / or the virtual mailbox address of the institution virtual mailbox (institution mailbox address).

[0026] During the specific execution process, during the virtual mailbox activation process, the virtual mailbox is activated through the invoice service. Specifically, in an optional implementation manner provided by this embodiment, the virtual mailbox is activated in the following manner: according to the activation request submitted by the user or organization through the invoice service, the virtual mailbox for storing electronic invoice emails is activated; according to the domain name information and the identification information of the user or the organization, the virtual mailbox address is generated and configured to the virtual mailbox.

[0027] The user's identification information can be a digital identifier that uniquely identifies the user, such as the user's contact number. The organization's identification information can also be a digital identifier that uniquely identifies the organization, or it can be a digital identifier of a designated member of the organization, such as the contact number of the organization's legal user or administrative user. Specifically, when generating a virtual email address, an address in the format of "contact number + domain name information" can be generated as the virtual email address.

[0028] In specific implementation, after obtaining a virtual mailbox and a virtual mailbox address through opening a virtual mailbox in the invoice service, the user or organization can apply for an electronic invoice through the invoice platform (third-party invoice platform) provided by a third party for issuing electronic invoices. After the invoice platform issues the electronic invoice, the invoice platform can also send an electronic invoice email to the corresponding email address based on the email address entered by the user or organization. In this embodiment, based on the user or organization obtaining a virtual mailbox and a virtual mailbox address through opening a virtual mailbox, the virtual mailbox address needs to be entered during the process of issuing electronic invoices on the invoice platform. Accordingly, the invoice platform will send an electronic invoice email to the virtual mailbox corresponding to the virtual mailbox address.

[0029] Optionally, the electronic invoice email is created based on the transaction bill, and the electronic invoice email is sent based on the virtual mailbox address configured by the invoice service for the virtual mailbox.

[0030] In an optional implementation provided by this embodiment, the invoice platform sends the electronic invoice email in the following manner: creating an electronic invoice email of the transaction bill according to the invoice application instruction; and sending the electronic invoice email according to the input virtual email address.

[0031] Specifically, an invoice application instruction can be submitted by a user, and a virtual email address can also be entered by the user. The virtual email address entered by the user can be the user's virtual email address, or the organization email address of an organization virtual email address with which the user has a specific relationship, such as the organization email address of an organization to which the user belongs as a member. Additionally, an invoice application instruction can be submitted by an organization, and a virtual email address can also be entered by the organization. The virtual email address entered by the organization is the organization email address of the organization virtual email address.

[0032] In actual applications, when a user or organization issues an electronic invoice on an invoice platform, they can submit an invoice application offline. For example, the user or organization can apply for electronic invoice issuance to the invoice platform by scanning a QR code. For example, the invoice application instruction is generated after the user scans the invoice application code on the transaction bill and enters the user's virtual email address on the invoice application page obtained by scanning the code.

[0033] Among them, the invoice application code can be a QR code for invoice application on a paper transaction bill printed and generated after a user or organization conducts a transaction with a merchant, or it can be a QR code for invoice application displayed on an electronic transaction bill generated after a user or organization conducts a transaction with a merchant.

[0034] Furthermore, while issuing electronic invoices on the invoice platform, users or organizations can also submit electronic invoice applications online. For example, a user can submit an electronic invoice application to the invoice platform for a transaction invoice listed in an invoice list within an application. For example, the invoice application instruction is submitted to the invoice platform via the invoice list for the transaction invoice included in the invoice service host program.

[0035] During the specific implementation process, in order to improve the transaction convenience between users or institutions and merchants, users or institutions can pay for orders by presenting payment vouchers, and generate a transaction bill after the order payment is completed. For example, the transaction bill is generated after the order payment is made based on the user's payment code, or after the funds are transferred out of the institution's account based on the institution's payment voucher.

[0036] In addition, when a user makes an order payment as a member of an institution, he or she may also use the institution payment voucher assigned to the user by the institution to make order payment and generate a transaction bill after the payment is completed. For example, the transaction bill is generated after the user's institution payment voucher is used to transfer funds from the institution account associated with the institution payment voucher and make order payment.

[0037] It should be noted that when a user issues an electronic invoice on the invoice platform, in addition to the aforementioned method of entering the user's own user virtual mailbox email address, if the user is a member of an organization, the user can also enter the organization email address of the organization's virtual mailbox. By entering the organization email address, the electronic invoice email generated by the invoice platform will be sent to the organization's virtual mailbox. For example, the virtual mailbox address entered by the user includes the organization email address of the user's organization entered on the invoice application page of the invoice platform; here, the organization email address is obtained by the organization after applying for a virtual mailbox on the invoice service.

[0038] Step S204: Parse the electronic invoice email in the virtual mailbox and determine the invoice acquisition type based on the parsing result.

[0039] In actual scenarios, there are different invoice platforms, and the content of the electronic invoice emails sent by different invoice platforms may be different. For example, the electronic invoice emails sent by some invoice platforms directly include the electronic invoice attachments, and the electronic invoice emails sent by some invoice platforms include the electronic invoice download link. You need to download the electronic invoice through the download link. The electronic invoice emails sent by some invoice platforms include the electronic invoice access code and access link. You need to enter the access code in the window generated after the access link is triggered. The electronic invoice is allowed to be viewed only after the access code verification is passed.

[0040] In view of this, in order to increase the success rate of parsing the electronic invoice emails sent by the invoice platform, thereby improving the success rate of obtaining electronic invoices, this embodiment determines the invoice acquisition type of the currently parsed electronic invoice email through parsing during the parsing of the electronic invoice email, thereby providing a basis for subsequent electronic invoice acquisition based on the invoice acquisition type.

[0041] The following uses three scenarios as examples: the electronic invoice email sent by the invoice platform directly contains an attachment of the electronic invoice, the electronic invoice email sent by the invoice platform contains a download link of the electronic invoice, and the electronic invoice email sent by the invoice platform contains an access code and access link of the electronic invoice to specifically explain the parsing process of the electronic invoice email. The parsing process of the electronic invoice email in other scenarios is similar and will not be repeated here in this embodiment.

[0042] In a scenario where the electronic invoice email sent by the invoice platform directly includes an attachment of the electronic invoice, this embodiment provides an optional implementation method of parsing the electronic invoice email in the virtual mailbox, and determining the invoice acquisition type based on the parsing result, including: parsing the electronic invoice email to obtain invoice attachment information, and determining that the invoice acquisition type is an attachment extraction type based on the invoice attachment information.

[0043] In the scenario where the electronic invoice email sent by the invoice platform contains a download link for the electronic invoice, this embodiment provides an optional implementation method of parsing the electronic invoice email in the virtual mailbox, and determining the invoice acquisition type based on the parsing result, including: parsing the electronic invoice email to obtain download keywords and download links, and determining that the invoice acquisition type is a download type based on the download keywords and the download link.

[0044] In the scenario where the electronic invoice email sent by the invoice platform contains the access code and access link of the electronic invoice, this embodiment provides an optional implementation method of parsing the electronic invoice email in the virtual mailbox, and determining the invoice acquisition type based on the parsing result, including: parsing the electronic invoice email to obtain the invoice access code and access link, and determining that the invoice acquisition type is the access code acquisition type based on the invoice access code and access link.

[0045] Step S206: Obtain the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

[0046] In specific implementation, based on the above-mentioned analysis to determine the invoice acquisition type of the currently parsed electronic invoice email, this step, in the process of obtaining the electronic invoice, starts from the invoice acquisition type and obtains the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain the electronic invoice.

[0047] The above provides three scenarios: the electronic invoice email sent by the invoice platform directly contains an attachment of the electronic invoice, the electronic invoice email sent by the invoice platform contains a download link of the electronic invoice, and the electronic invoice email sent by the invoice platform contains an access code and access link of the electronic invoice. These three scenarios are also used as examples here to illustrate the specific process of obtaining electronic invoices in these three scenarios. The specific process of obtaining electronic invoices in other scenarios is similar and will not be repeated in this embodiment.

[0048] In the scenario where the electronic invoice email sent by the invoice platform directly includes an attachment of the electronic invoice, the above-mentioned parsing of the electronic invoice email obtains the invoice attachment information, and determines that the invoice acquisition type is the attachment extraction type based on the invoice attachment information. Based on this, an optional implementation method provided by this embodiment is to obtain the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain the electronic invoice, including: extracting the invoice attachment in the electronic invoice email, and adding the obtained electronic invoice to the electronic invoice pool of the user under the invoice service.

[0049] In the scenario where the electronic invoice email sent by the invoice platform contains a download link for the electronic invoice, the electronic invoice email is parsed to obtain the download keyword and the download link, and the invoice acquisition type is determined to be a download type based on the download keyword and the download link. Based on this, an optional implementation provided by this embodiment is to obtain the invoice in accordance with the invoice acquisition method corresponding to the invoice acquisition type to obtain the electronic invoice, including: triggering the download link to download the invoice in accordance with the download method corresponding to the download type to obtain the electronic invoice.

[0050] In the scenario where the electronic invoice email sent by the invoice platform contains the access code and access link of the electronic invoice, the above-mentioned parsing of the electronic invoice email obtains the invoice access code and access link, and determines that the invoice acquisition type is the access code acquisition type based on the invoice access code and access link. Based on this, an optional implementation method provided by this embodiment is to obtain the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain the electronic invoice, including: entering the invoice access code in the input interface after the access link is triggered according to the access code acquisition type to access the electronic invoice.

[0051] In actual applications, the purpose of obtaining electronic invoices in many scenarios is for reimbursement. To meet this demand, this embodiment obtains electronic invoices according to the invoice acquisition method corresponding to the invoice acquisition type. After obtaining the electronic invoice, automatic reimbursement processing can be performed based on the obtained electronic invoice. Specifically, in an optional implementation provided by this embodiment, reimbursement processing is performed in the following manner: the electronic invoice is associated with the transaction bill; a reimbursement form carrying the electronic invoice and the transaction bill is generated according to the reimbursement instruction and submitted to the institution.

[0052] It should be pointed out that the transaction bill can be generated after the funds are transferred out from the institution's account based on the institution's payment voucher. The virtual mailbox for receiving the electronic invoice email can be the institution's virtual mailbox obtained by the institution when opening a virtual mailbox in the invoice service. On this basis, in another optional implementation manner provided by this embodiment, reimbursement processing is carried out in the following manner: according to the transaction information recorded in the electronic invoice, the transaction bill corresponding to the transaction information is obtained in the bill list of the institution; the electronic invoice is associated with the transaction bill to perform reimbursement processing based on the electronic invoice and the transaction bill.

[0053] In addition, it should be pointed out that the virtual email address entered by the user can be the institutional email address of the user's organization entered by the user on the invoice application page of the invoice platform; here, the institutional email address can be obtained by the organization after applying for a virtual email address for the invoice service. On this basis, in an optional implementation provided by this embodiment, the electronic invoice can also be processed as follows: obtain the transaction bill from the user's bill list; synchronize the transaction bill to the organization, and associate it with the electronic invoice.

[0054] To sum up, the electronic invoice processing method based on virtual mailbox provided by this embodiment is that during the electronic invoice application process, the user or organization applies for an invoice to the invoice platform and submits a virtual mailbox address during the invoice application process. The virtual mailbox address is configured by the invoice service for the virtual mailbox. After receiving the invoice application, the invoice platform creates an electronic invoice email based on the transaction bill and sends the electronic invoice email to the submitted virtual mailbox address; thereafter, the invoice service receives the electronic invoice email sent by the invoice platform through the virtual mailbox, and parses the received electronic invoice email. The invoice acquisition type of the currently parsed electronic invoice email is determined through the parsing process, and the invoice is acquired according to the invoice acquisition method corresponding to the invoice acquisition type to obtain the corresponding electronic invoice, thereby realizing the acquisition of electronic invoices based on the invoice acquisition type. On the basis of improving the success rate of parsing the electronic invoice email sent by the invoice platform, the success rate of acquiring electronic invoices is improved.

[0055] In addition, this embodiment uses a virtual mailbox to receive and parse electronic invoice emails in a targeted manner, which on the one hand improves the security of electronic invoice mailing, and on the other hand avoids the risk of user data leakage caused by the virtual mailbox storing user data and causing the user data to be parsed.

[0056] The following takes the application of an electronic invoice processing method based on a virtual mailbox provided by this embodiment in a user invoice processing scenario as an example, and combines Figure 3 to further illustrate the electronic invoice processing method based on a virtual mailbox provided by this embodiment. Referring to Figure 3, the electronic invoice processing method based on a virtual mailbox applied to the user invoice processing scenario specifically includes the following steps.

[0057] Step S302: Receive the electronic invoice email sent by the invoice platform through the user's virtual mailbox.

[0058] Optionally, an electronic invoice email is created based on the transaction bill and sent based on the user's email address configured by the invoice service for the user's virtual mailbox.

[0059] Optionally, the electronic invoice email is created after receiving the invoice application instruction; wherein, the invoice application instruction is generated after the user scans the invoice application code of the transaction bill and enters the user's email address through the invoice application page obtained by scanning the code; or, the invoice application instruction is submitted to the invoice platform through the bill list of the transaction bill contained in the host program of the invoice service.

[0060] Optionally, a transaction bill is generated after the user pays for an order based on the user's payment code, or is generated after the user transfers funds from an institutional account associated with the institutional payment voucher and pays for an order based on the user's institutional payment voucher.

[0061] Step S304: Parse the electronic invoice email in the user's virtual mailbox to obtain invoice attachment information.

[0062] Step S306: Determine, based on the invoice attachment information, that the invoice acquisition type is an attachment extraction type.

[0063] Step S308: extract the invoice attachment from the electronic invoice email to obtain the electronic invoice.

[0064] Step S310: Add the obtained electronic invoice to the user's electronic invoice pool under the invoice service.

[0065] It should be noted that any one of steps S302 to S310 or any combination of multiple steps can be replaced by the corresponding technical means provided in the above steps S202 to S206 according to the needs of implementation and deployment, and will not be described one by one here.

[0066] The following takes the application of an electronic invoice processing method based on a virtual mailbox provided by this embodiment in an institutional invoice processing scenario as an example, and combines Figure 4 to further illustrate the electronic invoice processing method based on a virtual mailbox provided by this embodiment. Referring to Figure 4, the electronic invoice processing method based on a virtual mailbox applied to the institutional invoice processing scenario specifically includes the following steps.

[0067] Step S402: Receive the electronic invoice email sent by the invoice platform through the organization's virtual mailbox.

[0068] Optionally, the electronic invoice email is created based on the transaction bill and sent based on the institutional email address configured for the institutional email address by the invoice service; the institutional email address is obtained by the institution after activating a virtual mailbox in the invoice service.

[0069] Optionally, a transaction bill is generated after a funds transfer payment is made from the institution's account based on the institution's payment voucher.

[0070] Step S404: Parse the electronic invoice email in the organization's virtual mailbox to obtain download keywords and download links.

[0071] Step S406: Determine the invoice acquisition type as a download type based on the download keyword and the download link.

[0072] Step S408: trigger the download link to download the invoice according to the download method corresponding to the download type to obtain the electronic invoice.

[0073] Step S410: Associating the electronic invoice with the transaction bill.

[0074] Step S412: Generate a reimbursement form containing the electronic invoice and transaction bill according to the reimbursement instruction for reimbursement processing.

[0075] It should be noted that any one of steps S402 to S412 or any combination of multiple steps can be replaced by the corresponding technical means provided in the above steps S202 to S206 according to the needs of implementation and deployment, and will not be described one by one here.

[0076] The following takes the application of an electronic invoice processing method based on a virtual mailbox provided by this embodiment in an institutional payment scenario as an example, and combines Figure 5 to further illustrate the electronic invoice processing method based on a virtual mailbox provided by this embodiment. Referring to Figure 5, the electronic invoice processing method based on a virtual mailbox applied to the institutional payment scenario specifically includes the following steps.

[0077] Step S502: Receive the electronic invoice email sent by the invoice platform through the organization's virtual mailbox.

[0078] Optionally, the electronic invoice email is created based on the transaction bill and sent based on the institutional email address configured for the institutional virtual mailbox by the invoice service; the virtual mailbox includes the institutional virtual mailbox obtained by the institution when activating a virtual mailbox in the invoice service.

[0079] Optionally, the electronic invoice email is created after receiving the invoice application instruction submitted by the user; wherein, the invoice application instruction is generated after the user scans the invoice application code of the transaction bill and enters the user's email address through the invoice application page obtained by scanning the code; or, the invoice application instruction is submitted to the invoice platform through the bill list of the transaction bill contained in the host program of the invoice service.

[0080] Optionally, a transaction bill is generated based on the user's institutional payment voucher after funds are transferred from the institutional account associated with the institutional payment voucher and the order payment is made.

[0081] Step S504: parse the electronic invoice email in the organization's virtual mailbox and determine the invoice acquisition type based on the parsing result.

[0082] Step S506: Obtain the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

[0083] Step S508: According to the transaction information recorded in the electronic invoice, the transaction bill corresponding to the transaction information is obtained from the institution's bill list.

[0084] Step S510: Associating the electronic invoice with the transaction bill to perform reimbursement processing based on the electronic invoice and the transaction bill.

[0085] It should be noted that any one of steps S502 to S510 or any combination of multiple steps can be replaced by the corresponding technical means provided in the above steps S202 to S206 according to the needs of implementation and deployment, and will not be described one by one here.

[0086] This specification provides an embodiment of an electronic invoice processing device based on a virtual mailbox as follows.

[0087] In the above embodiment, a method for processing electronic invoices based on a virtual mailbox is provided. Correspondingly, an apparatus for processing electronic invoices based on a virtual mailbox is also provided, which will be described below with reference to the accompanying drawings.

[0088] 6 , which shows a schematic diagram of an embodiment of an electronic invoice processing device based on a virtual mailbox provided by this embodiment.

[0089] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0090] This embodiment provides an electronic invoice processing device based on a virtual mailbox, which runs on an invoice service. The device includes: an invoice email acquisition module 602, which is configured to receive an electronic invoice email sent by an invoice platform through a virtual mailbox, wherein the electronic invoice email is created based on a transaction bill and is sent based on a virtual mailbox address configured for the virtual mailbox by the invoice service; an invoice email parsing module 604, which is configured to parse the electronic invoice email in the virtual mailbox and determine the invoice acquisition type based on the parsing result; an invoice acquisition module 606, which is configured to acquire an invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

[0091] This specification provides an embodiment of an electronic invoice processing device based on a virtual mailbox as follows.

[0092] Corresponding to the above-described electronic invoice processing method based on a virtual mailbox, based on the same technical concept, one or more embodiments of this specification also provide an electronic invoice processing device based on a virtual mailbox. The electronic invoice processing device based on a virtual mailbox is used to execute the above-mentioned electronic invoice processing method based on a virtual mailbox. Figure 6 is a structural diagram of an electronic invoice processing device based on a virtual mailbox provided by one or more embodiments of this specification.

[0093] This embodiment provides a virtual mailbox-based electronic invoice processing device, including: As shown in FIG7 , the virtual mailbox-based electronic invoice processing device may vary significantly depending on configuration or performance. It may include one or more processors 701 and memory 702. Memory 702 may store one or more applications or data. Memory 702 may be either ephemeral or persistent. The applications stored in memory 702 may include one or more modules (not shown), each of which may include a series of computer-executable instructions for the virtual mailbox-based electronic invoice processing device. Furthermore, processor 701 may be configured to communicate with memory 702 to execute the series of computer-executable instructions in memory 702 on the virtual mailbox-based electronic invoice processing device. The virtual mailbox-based electronic invoice processing device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, one or more keyboards 706, and the like.

[0094] In a specific embodiment, an electronic invoice processing device based on a virtual mailbox includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions in the electronic invoice processing device based on the virtual mailbox, and is configured to be executed by one or more processors. The one or more programs include the following computer-executable instructions: receiving an electronic invoice email sent by an invoice platform through a virtual mailbox, the electronic invoice email is created based on a transaction bill, and is sent based on a virtual mailbox address configured for the virtual mailbox by an invoice service; parsing the electronic invoice email in the virtual mailbox, and determining the invoice acquisition type based on the parsing result; acquiring the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

[0095] An embodiment of a computer-readable storage medium provided in this specification is as follows.

[0096] Corresponding to the above-described method for processing electronic invoices based on a virtual mailbox, based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0097] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which implement the following process when executed: receiving an electronic invoice email sent by an invoice platform through a virtual mailbox, the electronic invoice email being created based on a transaction bill and sent based on a virtual mailbox address configured for the virtual mailbox by an invoice service; parsing the electronic invoice email in the virtual mailbox, and determining the invoice acquisition type based on the parsing result; acquiring the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

[0098] It should be noted that the embodiment of a computer-readable storage medium in this specification and the embodiment of an electronic invoice processing method based on a virtual mailbox in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0099] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. For example, the device embodiment, equipment embodiment and computer-readable storage medium embodiment are similar to the method embodiment, so the description is relatively simple. For relevant content in the device embodiment, equipment embodiment and computer-readable storage medium embodiment, please refer to the partial description of the method embodiment.

[0100] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0101] In the 1930s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages ​​and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0102] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.

[0103] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0104] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0105] Those skilled in the art will appreciate that one or more embodiments of this specification may be provided as a method, system, or computer program product. Thus, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0106] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0107] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0108] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0109] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0110] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0111] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer-readable storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0112] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising at least one ..." does not exclude the presence of additional identical elements in the process, method, commodity, or apparatus comprising the element.

[0113] One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. One or more embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0114] The foregoing description is merely an example of the present invention and is not intended to limit the present invention. Persons skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be included within the scope of the claims herein.

Claims

1. A method for processing electronic invoices based on a virtual mailbox, applied to invoice services, comprising: Receiving an electronic invoice email sent by the invoice platform through a virtual mailbox, wherein the electronic invoice email is created based on the transaction bill and is sent based on a virtual mailbox address configured by the invoice service for the virtual mailbox; Parsing the electronic invoice email in the virtual mailbox and determining the invoice acquisition type according to the parsing result; Obtain the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

2. According to the electronic invoice processing method based on a virtual mailbox in claim 1, the virtual mailbox is activated in the following manner: Activate the virtual mailbox for storing electronic invoice emails according to an activation request submitted by a user or organization through the invoice service; The virtual mailbox address is generated according to the domain name information and the identification information of the user or the organization and is configured for the virtual mailbox.

3. According to the electronic invoice processing method based on a virtual mailbox in claim 1, the invoice platform sends the electronic invoice email in the following manner: Create an electronic invoice email for the transaction bill according to the invoice application instruction; The electronic invoice email is sent according to the input virtual email address.

4. According to the virtual mailbox-based electronic invoice processing method of claim 3, the invoice application instruction is generated after the user scans the invoice application code of the transaction bill and enters the user's virtual mailbox address on the invoice application page obtained by scanning the code; Alternatively, the invoice application instruction is submitted to the invoice platform through the bill list of the transaction bill contained in the host program of the invoice service.

5. The electronic invoice processing method based on a virtual mailbox according to claim 3, wherein the transaction bill is generated after the user pays for the order based on the user's payment code; Alternatively, the transaction bill is generated after the user's institutional payment voucher is used to transfer funds from an institutional account associated with the institutional payment voucher and pay for the order.

6. The method for processing electronic invoices based on a virtual mailbox according to claim 4, wherein parsing the electronic invoice email in the virtual mailbox and determining the invoice acquisition type based on the parsing result comprises: Parsing the electronic invoice email to obtain invoice attachment information, and determining the invoice acquisition type as the attachment extraction type based on the invoice attachment information; Accordingly, obtaining an electronic invoice by using the invoice obtaining method corresponding to the invoice obtaining type includes: The invoice attachment is extracted from the electronic invoice email, and the obtained electronic invoice is added to the electronic invoice pool of the user under the invoice service.

7. The method for processing electronic invoices based on a virtual mailbox according to claim 4, wherein after the electronic invoice is obtained according to the invoice obtaining method corresponding to the invoice obtaining type, the method further comprises: Associating the electronic invoice with the transaction bill; A reimbursement form carrying the electronic invoice and the transaction bill is generated according to the reimbursement instruction and submitted to the institution.

8. The electronic invoice processing method based on a virtual mailbox according to claim 3, wherein the transaction bill is generated after funds are transferred out of the institution's account based on the institution's payment voucher; The virtual mailbox includes the institution virtual mailbox obtained by the institution through opening a virtual mailbox in the invoice service; After the step of obtaining the electronic invoice according to the invoice obtaining method corresponding to the invoice obtaining type is performed, the method further includes: Obtaining, from the institution's bill list, a transaction bill corresponding to the transaction information based on the transaction information recorded in the electronic invoice; The electronic invoice is associated with the transaction bill to perform reimbursement processing based on the electronic invoice and the transaction bill.

9. The electronic invoice processing method based on a virtual mailbox according to claim 3, wherein the virtual mailbox address comprises the institutional mailbox address of the user's institution entered by the user on the invoice application page of the invoice platform; The organization's email address is obtained by the organization after opening a virtual mailbox for the invoice service.

10. The electronic invoice processing method based on a virtual mailbox according to claim 9, wherein after the electronic invoice is obtained according to the invoice obtaining method corresponding to the invoice obtaining type, the method further comprises: Obtain the transaction bill from the bill list of the user; The transaction bill is synchronized to the institution and associated with the electronic invoice.

11. The method for processing electronic invoices based on a virtual mailbox according to claim 1, wherein parsing the electronic invoice email in the virtual mailbox and determining the invoice acquisition type based on the parsing result comprises: Parsing the electronic invoice email to obtain a download keyword and a download link, and determining the invoice acquisition type as a download type based on the download keyword and the download link; Accordingly, obtaining an electronic invoice by using the invoice obtaining method corresponding to the invoice obtaining type includes: The download link is triggered according to the download method corresponding to the download type to download the invoice and obtain the electronic invoice.

12. The method for processing electronic invoices based on a virtual mailbox according to claim 1, wherein parsing the electronic invoice email in the virtual mailbox and determining the invoice acquisition type based on the parsing result comprises: Parsing the electronic invoice email to obtain an invoice access code and an access link, and determining the invoice acquisition type as an access code acquisition type based on the invoice access code and the access link; Accordingly, obtaining an electronic invoice by using the invoice obtaining method corresponding to the invoice obtaining type includes: According to the access code acquisition type, the invoice access code is input on the input interface after the access link is triggered to access the electronic invoice.

13. An electronic invoice processing device based on a virtual mailbox, running on an invoice service, comprising: An invoice email acquisition module is configured to receive an electronic invoice email sent by the invoice platform through a virtual mailbox, wherein the electronic invoice email is created based on the transaction bill and is sent based on a virtual mailbox address configured by the invoice service for the virtual mailbox; an invoice email parsing module configured to parse the electronic invoice email in the virtual mailbox and determine the invoice acquisition type based on the parsing result; The invoice acquisition module is configured to acquire the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain the electronic invoice.

14. An electronic invoice processing device based on a virtual mailbox, comprising: processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: Receiving an electronic invoice email sent by the invoice platform through a virtual mailbox, wherein the electronic invoice email is created based on the transaction bill and is sent based on the virtual mailbox address configured for the virtual mailbox by the invoice service; Parsing the electronic invoice email in the virtual mailbox and determining the invoice acquisition type according to the parsing result; Obtain the invoice according to the invoice acquisition method corresponding to the invoice acquisition type to obtain an electronic invoice.

15. A computer-readable storage medium for storing computer-executable instructions, wherein the computer-executable instructions implement the steps of the method of claim 1 when executed.

Images