CA3129517A1

CA3129517A1 - Invoice information acquisition method and device, computer equipment and storage medium

Info

Publication number: CA3129517A1
Application number: CA3129517A
Authority: CA
Inventors: Ruizhe Hong; Daoliang Ren; Jian Hou; Jinzhi Guo; Weijun FAN
Original assignee: 10353744 Canada Ltd
Current assignee: 10353744 Canada Ltd
Priority date: 2020-09-01
Filing date: 2021-08-31
Publication date: 2022-03-01
Also published as: CN112132671A

Abstract

The present application relates to an invoice information collecting method and device, a computer equipment and a storage medium. The method comprises setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled;
setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces; and performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received. The above method enables enhancement of efficiency for pooling and managing invoices.

Description

INVOICE INFORMATION ACQUISITION METHOD AND DEVICE, COMPUTER
EQUIPMENT AND STORAGE MEDIUM
BACKGROUND OF THE INVENTION
Technical Field [0001] The present application relates to the field of invoice information processing technology, and more particularly to an invoice information collecting method, an invoice information collecting device, a computer equipment and a storage medium.
Description of Related Art

[0002] As an important credential for reimbursement, the invoice is widely applied in the reimbursement procedure. The most initial paper invoices were very popular, and the reimbursement procedure was designed around the paper invoices. Despite the online reimbursement procedure, invoices were still circulated offline, and it was required for the user to print the reimbursement document, stick the invoice(s) thereon and send it out, the whole operation was very inconvenient.

[0003] With the popularization of electronic invoices, they are increasingly adopted by more and more professions and fields of work. Offline circulation of electronic invoices is still employed in some reimbursement procedures, and it is required for users to print the electronic invoices before circulation. Simple PDF analyzing and pooling programs of electronic invoices have been developed for some reimbursement procedures, whereby electronic invoices are analyzed and then circulated.

[0004] As can be known from the above, pooling management of invoices is very unwieldy at present, great amount of manual operations is consumed therefor, and pooling management of invoices is low in efficiency. With regard to paper invoices are concerned, they are collected offline, and it is also required in the pooling management of paper invoices to manually extract invoice information of paper invoices. With regard to electronic invoices, although it is currently possible to circulate electronic invoices through analysis of the Date recue / Date received 202 1-1 1-01 electronic invoices, there is also no unified channel in the process of collecting electronic invoices, so this causes low efficiency in pooling management of electronic invoices.
SUMMARY OF THE INVENTION

[0005] In view of the above, there is an urgent need to provide an invoice information collecting method, an invoice information collecting device, a computer equipment and a storage medium capable of enhancing pooling management of invoices to address the foregoing technical problems.

[0006] There is accordingly proposed an invoice information collecting method, which comprises setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled; setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces; and performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received.

[0007] In one of the embodiments, the types of the invoices to be pooled include invoice image type of paper invoices and electronic invoice type, the plural invoice receiving interfaces include a first-type interface and a second-type interface, the invoice information of the invoices to be pooled includes nominal value information of the invoices to be pooled, and the step of setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces includes: configuring the invoice information analyzing mode of the first-type interface as a first analyzing mode when the first-type interface is employed to receive invoices to be pooled of the invoice image type, the first analyzing mode being employed to indicate performing information collection on the invoices to be pooled via image recognition technique; and configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic Date recue / Date received 202 1-1 1-01 invoice type, the second analyzing mode being employed to indicate performing information collection on the invoices to be pooled by a mode of obtaining nominal value information of the invoices to be pooled.

[0008] In one of the embodiments, the step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received includes: determining invoice images of first invoices to be pooled when the first-type interface receives the first invoices to be pooled, performing information collection on the invoice images by invoking optical character recognition service on the basis of the first analyzing mode, thereby obtaining nominal value information of the first invoices to be pooled.

[0009] In one of the embodiments, the second-type interface includes a first subtype interface and a second subtype interface, and the step of configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type includes: configuring invoice information analyzing mode of the first subtype interface as a first mode in the second analyzing mode when the first subtype interface is employed to receive second invoices to be pooled of the electronic invoice type coming from a mailbox, the first mode being employed to indicate extracting nominal value information from the second invoices to be pooled; and configuring invoice information analyzing mode of the second subtype interface as a second mode in the second analyzing mode when the second subtype interface is employed to receive third invoices to be pooled of the electronic invoice type coming from an application program, the second mode being employed to indicate receiving nominal value information of the third invoices to be pooled coming from the application program.

[0010] In one of the embodiments, the step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as Date recue / Date received 202 1-1 1-01 received includes: judging, when the first subtype interface receives the second invoices to be pooled coming from a first mailbox, whether the first mailbox has been bound to user information; if yes, binding the second invoices to be pooled to the user information, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled; if not, storing the second invoices to be pooled in a public invoice pool, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled.

[0011] In one of the embodiments, the invoice information collecting method further comprises:
receiving a binding request of the first mailbox, the binding request being employed to request binding of the user information to the first mailbox; generating a first verification code according to the binding request, and sending the first verification code to the first mailbox via a second mailbox; receiving a second verification code sent by an application page of the binding request, and judging whether the second verification code is identical with the first verification code; if yes, binding the first mailbox to the user information; and inquiring the public invoice pool via mailbox account of the first mailbox, obtaining invoices of the first mailbox before binding from the public invoice pool, and binding the obtained invoices to the user information.

[0012] In one of the embodiments, the step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received includes: when the second subtype interface receives the third invoices to be pooled coming from the application program and sent by a client side, obtaining nominal value information of the third invoices to be pooled on the basis of the second mode by the mode of receiving nominal value information of the third invoices to be pooled coming from the application program and sent by the client side; wherein the mode for the client side to obtain the nominal value information of the third invoices to be pooled coming from the application program includes the following: the client side invokes an interface of a public platform via an application account and an application key provided by the public Date recue / Date received 202 1-1 1-01 platform of the application program, and obtains a globally unique interface invoking credential of the public platform via the invoked interface; the client side invokes an invoice list interface of the public platform via the globally unique interface invoking credential, and obtains an invoice list of the public platform via the invoice list interface;
and the client side confirms and selects the third invoices to be pooled in the invoice list, and receives nominal value information of the third invoices to be pooled as returned by the public platform.

[0013] In one of the embodiments, the invoice information collecting method further comprises:
pooling invoice images of electronic invoices and/or paper invoices received by the plural invoice receiving interfaces; and releasing the pooled invoice images of the electronic invoices and/or paper invoices to a message queue, so that a reimbursement system extracts the invoice images of the electronic invoices and/or paper invoices from the message queue to perform automatic reimbursement.

[0014] An invoice information collecting device comprises a first setting-up module, for setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled; a second setting-up module, for setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces;
and a collecting module, for performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received.

[0015] A computer equipment comprises a memory, a processor and a computer program stored on the memory and executable on the processor, and the method steps according to anyone of the foregoing embodiments are realized when the processor executes the computer program.

[0016] A computer readable storage medium stores thereon a computer program, and the computer program realizes the method steps according to anyone of the foregoing embodiments upon execution by a processor.
Date recue / Date received 202 1-1 1-01

[0017] In the aforementioned invoice information collecting method, invoice information collecting device, computer equipment and storage medium, the information collecting system sets up plural invoice receiving interfaces for receiving invoices of identical type or different types to be pooled, and a corresponding invoice information analyzing mode is set up for each of the invoice receiving interfaces. When any of the invoice receiving interfaces receives invoices to be pooled, information collection is performed on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, and invoice information of the invoices to be pooled as received is obtained. Accordingly, regardless of the types of the invoices to be pooled, e.g.
electronic invoices or paper invoices, a corresponding invoice receiving interface is provided to receive the invoices to be pooled of the corresponding type. At the same time, a corresponding invoice infoiniation analyzing mode is set up with respect to the corresponding invoice receiving interface for performing information collection of the invoices to be pooled as received by the invoice receiving interface, so as to obtain the invoice information of the invoices to be pooled. Therefore, multi-channel automatic invoice pooling is realized, manual operation is dispensed with, and the efficiency for pooling and managing invoices is enhanced.
BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Fig. 1 is a view showing the environment in which an invoice information collecting method according to an embodiment is applied;

[0019] Fig. 2 is a flowchart schematically illustrating an invoice information collecting method according to an embodiment;

[0020] Fig. 3 is a flowchart schematically illustrating the collection of invoice information of a paper invoice according to an embodiment;

[0021] Fig. 4 is a flowchart schematically illustrating the collection of nominal value Date recue / Date received 202 1-1 1-01 information of invoices to be pooled via a mailbox pooling mode according to an embodiment;

[0022] Fig. 5 is a flowchart schematically illustrating pooling of a WeChat invoice according to an embodiment;

[0023] Fig. 6 is a flowchart schematically illustrating invoice reimbursement according to an embodiment;

[0024] Fig. 7 is a block diagram illustrating the structure of an invoice information collecting device according to an embodiment; and

[0025] Fig. 8 is a view showing the internal structure of a computer equipment according to an embodiment.
DETAILED DESCRIPTION OF THE INVENTION

[0026] To make more lucid and clear the objectives, technical solutions and advantages of the present application, the present application is described in greater detail below with reference to the accompanying drawings and embodiments. As should be understood, the specific embodiments as described here are merely meant to explain the present application, rather than to restrict the present application.

[0027] An invoice information collecting method provided by the present application is applied in the environment as shown in Fig. 1. Information collecting system 100 is employed to realize an invoice information collecting method of the present application.
As shown in Fig. 1, information collecting system 100 is provided with plural invoice receiving interfaces, such as interface 102, interface 104, interface 106, and so on. It is of course also possible to embody the plural invoice receiving interfaces as virtual interfaces set up inside the system, such as communication interfaces of different network protocols or various information invoking interfaces. These invoice receiving interfaces are employed to receive invoices to be pooled of identical type or different types. The invoices to be pooled may be images of paper invoices or electronic invoices. Information collecting system 100 Date recue / Date received 202 1-1 1-01 bases on the types of invoices to be pooled as received by the various invoice receiving interfaces to set up invoice information analyzing modes of the various invoice receiving interfaces. When any of the invoice receiving interfaces of information collecting system 100 receives invoices to be pooled as sent by a terminal device, information collection is performed on the received invoices to be pooled according to the invoice information analyzing mode of the specific invoice receiving interface to obtain invoice information of the received invoices to be pooled. Finally, the invoice information of the invoices to be pooled as received by the various invoice receiving interfaces as well as the invoices to be pooled are pooled together, and stored in database 200. The terminal device may be desktop computer 302, mobile phone 304 or iPad 306, and so on.

[0028] The present application provides an invoice information collecting method, and the method is applied in the information collecting system as shown in Fig. 1. In one embodiment, as shown in Fig. 2, an invoice information collecting method comprises the following steps.

[0029] S102 - setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled.

[0030] In the present embodiment, the information collecting system is provided with plural invoice receiving interfaces, whereby invoices to be pooled of identical type or different types are received. When the number of invoice receiving interfaces is two, the two invoice receiving interfaces are employed to receive invoices to be pooled of different types. When the number of invoice receiving interfaces is greater than two, the plural invoice receiving interfaces are divided into those that receive invoices to be pooled of identical type and those that receive invoices to be pooled of different types. The types of the invoices to be pooled include electronic invoice type and invoice image type of paper invoices. When the type of the invoices to be pooled is of the invoice image type of paper invoices, the invoices to be pooled are invoice images of paper invoices.

[0031] S104 - setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces.

Date recue / Date received 202 1-1 1-01

[0032] In the present embodiment, the information collecting system sets up corresponding invoice information analyzing mode in view of the type of the invoices to be pooled as received by each invoice receiving interface. The types of invoices to be pooled as received by the invoice receiving interfaces are different, so the corresponding invoice information obtaining modes are also different. Specifically, when a first invoice receiving interface receives invoice image type of paper invoices, a first invoice information analyzing mode is set up to obtain information of invoices to be pooled of the invoice image type of paper invoices. When a second invoice receiving interface receives electronic invoice type, a second invoice information analyzing mode is set up to obtain information of invoices to be pooled of the electronic invoice type. At this time, the first invoice information analyzing mode and the second invoice information analyzing mode are different, in other words, the pieces of information of invoices to be pooled as obtained by different modes are different, so information analysis of invoices to be pooled of different types can be realized.

[0033] In addition, even when the type of the invoices to be pooled as received by the invoice receiving interfaces is identical, the corresponding invoice information analyzing modes can also be different. Specifically, when a third invoice receiving interface receives the electronic invoice type, a third invoice information analyzing mode is set up to employ the first obtaining mode to obtain information of invoices to be pooled of the electronic invoice type. When a fourth invoice receiving interface receives the electronic invoice type, a fourth invoice information analyzing mode is set up to employ the second obtaining mode to obtain information of invoices to be pooled of the electronic invoice type.
The first obtaining mode and the second obtaining mode are different, the first obtaining mode is determined according to the specific form of the invoices to be pooled as received by the third invoice receiving interface, and the second obtaining mode is determined according to the specific form of the invoices to be pooled as received by the fourth invoice receiving interface. For instance, the invoices to be pooled as received by the third invoice receiving interface are PDF files sent from a mailbox, at this time the first obtaining mode is determined as to its information obtaining mode according to the PDF files sent in the form of mailbox. The invoices to be pooled as received by the fourth invoice receiving interface are PDF files sent from WeChat, at this time the second obtaining mode is determined as Date recue / Date received 202 1-1 1-01 to its information obtaining mode according to the PDF files sent in the form of WeChat.
Accordingly, the information collecting system is capable of receiving and obtaining invoices to be pooled of plural channels and plural types and invoice information of the invoices to be pooled.

[0034] S106 - performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received.

[0035] In the present embodiment, when the information collecting system reads and receives invoices to be pooled via any interface receiving interface, information collection is performed on the received invoices to be pooled according to the invoice information analyzing mode of this specific invoice receiving interface, so as to obtain invoice information of the received invoices to be pooled. The invoice information includes nominal value information of the invoices to be pooled, for instance, such essential information as billing date, invoice number, invoice code, taxpayer identification number of the buyer, taxpayer identification number of the seller, the sum of money, and the amount of tax, etc.

[0036] In the aforementioned invoice information collecting method, the information collecting system is provided with plural invoice receiving interfaces for receiving invoices to be pooled of identical type or different types, and each of the invoice receiving interfaces is provided with a corresponding invoice information analyzing mode. When any of the invoice receiving interfaces receives invoices to be pooled, information collection is performed on the received invoices to be pooled according to the invoice information analyzing mode of the specific invoice receiving interface to obtain invoice information of the received invoices to be pooled. Therefore, regardless of the types of the invoices to be pooled, e.g. electronic invoices or paper invoices, a corresponding invoice receiving interface is provided to receive the invoices to be pooled of the corresponding type. At the same time, a corresponding invoice information analyzing mode is set up with respect to the corresponding invoice receiving interface for performing information collection of the invoices to be pooled as received by the invoice receiving interface, so as to obtain the Date recue / Date received 202 1-1 1-01 invoice information of the invoices to be pooled. Therefore, multi-channel automatic invoice pooling is realized, manual operation is dispensed with, and the efficiency for pooling and managing invoices is enhanced.

[0037] In one embodiment, the types of the invoices to be pooled include invoice image type of paper invoices and electronic invoice type, the plural invoice receiving interfaces include a first-type interface and a second-type interface, and the invoice information of the invoices to be pooled includes nominal value information of the invoices to be pooled. Step S104 includes: configuring the invoice information analyzing mode of the first-type interface as a first analyzing mode when the first-type interface is employed to receive invoices to be pooled of the invoice image type, the first analyzing mode being employed to indicate performing information collection on the invoices to be pooled via image recognition technique; and configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type, the second analyzing mode being employed to indicate performing information collection on the invoices to be pooled by a mode of obtaining nominal value information of the invoices to be pooled.

[0038] In this embodiment, the information collecting system receives invoice images of paper invoices and electronic invoices. In this circumstance, with respect to the invoices of these two types, the information collecting system is provided with a first-type interface for receiving invoices to be pooled of the invoice image type and a second-type interface for receiving invoices to be pooled of the electronic invoice type. The invoice information analyzing mode of the first-type interface is a first analyzing mode, and the first analyzing mode is employed to indicate performing information collection on the invoices to be pooled via image recognition technique. For instance, the image recognition technique may be OCR (Optical Character Recognition) service technique. The first analyzing mode can be employed to indicate the use of OCR service technique to extract nominal value information in invoice images of paper invoices to perform information collection. The invoice information analyzing mode of the second-type interface is a second analyzing mode, and the second analyzing mode is employed to indicate performing information collection on the invoices to be pooled by a mode of obtaining nominal value information Date recue / Date received 202 1-1 1-01 of the invoices to be pooled. The mode of obtaining nominal value information of the invoices to be pooled can be to directly analyze PDF files of electronic invoices, to extract nominal value information in the PDF files. Alternatively, the mode of obtaining nominal value information of the invoices to be pooled can be to directly receive nominal value information containing the invoices to be pooled sent by a sender equipment.
Accordingly, it is realizable that the information collecting system receives both invoice images of paper invoices and electronic invoices, thereby obtains nominal value information corresponding to invoice images of paper invoices and electronic invoices.

[0039] In one embodiment, step S106 includes determining invoice images of first invoices to be pooled when the first-type interface receives the first invoices to be pooled, performing information collection on the invoice images by invoking optical character recognition service on the basis of the first analyzing mode, thereby obtaining nominal value information of the first invoices to be pooled.

[0040] In this embodiment, the first invoices to be pooled are invoice images of paper invoices, when the first-type interface of the information collecting system receives the invoice images, information recognition is performed on the invoice images by invoking optical character recognition service on the basis of the first analyzing mode, and nominal value information in the invoice images is extracted. Specifically, the first analyzing mode is employed to indicate the information collecting system to perform information collection on the invoices to be pooled via image recognition technique, and the information collecting system invokes optical character recognition service to perform information recognition on the invoice images at this time.

[0041] In an implementation scenario, as shown in Fig. 3, the following steps are followed to realize collection of invoice information of paper invoices:
1) The user triggers the photograph pooling button at the client side to call the camera, and shots the overall image of a paper invoice, whereby an invoice picture is obtained after the image is ascertained, the client side then invokes an invoice image recognizing interface at the server side to upload the invoice picture.

Date recue / Date received 202 1-1 1-01 2) The server side receives an invoice image recognizing request, temporarily stores the invoice picture in OSS (cloud storage service), in which overdue date can be set as one day, and invokes OCR service to recognize the invoice picture.
3) After the OCR service returns the nominal value information of the invoice, the server side checks whether five essentials of the invoice (namely invoice code, invoice number, invoice date, sum of the invoice, and verification code) are complete and whether their formats are correct, step 4) is performed if yes, and step 5) is performed if not.
4) Invoice check service is invoked, five essentials of invoice are used to check the invoice, step 6) is performed if check fails, and step 7) is performed if check passes.
5) Five essentials of invoice at the OCR service are returned, five essentials of invoice are displayed at the client side, the user corrects five essentials of invoice, "retry" is clicked after correction, and the interface is invoked to enter step 4) for invoice check.
6) Check failure information is returned to the client side, check failure information is displayed at the client side, and pooling ends.
7) Database is inquired via invoice code and invoice number to verify whether the invoice has been pooled, step 8) is performed if it has been pooled, and step 9) is performed if not.
8) Basic information and pooling information of the invoice are returned, and it is prompted at the client side that the user invoice has been pooled.
9) OSS temporary storage of the invoice image is set as permanent to serve as the electronic image of the invoice, pooling general service is invoked, and invoice structured data, namely non-structured data, is stored.

Date recue / Date received 202 1-1 1-01 10) Basic information of the invoice is returned to the client side, and it is prompted that the invoice has been successfully pooled.

[0042] Therefore, photograph pooling of the paper invoice has been achieved.

[0043] In one embodiment, the second-type interface includes a first subtype interface and a second subtype interface. The step of configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type includes:
configuring invoice information analyzing mode of the first subtype interface as a first mode in the second analyzing mode when the first subtype interface is employed to receive second invoices to be pooled of the electronic invoice type coming from a mailbox, the first mode being employed to indicate extracting nominal value information from the second invoices to be pooled; and configuring invoice information analyzing mode of the second subtype interface as a second mode in the second analyzing mode when the second subtype interface is employed to receive third invoices to be pooled of the electronic invoice type coming from an application program, the second mode being employed to indicate receiving nominal value information of the third invoices to be pooled coming from the application program.

[0044] Specifically, in one embodiment, step S106 includes: judging, when the first subtype interface receives the second invoices to be pooled coming from a first mailbox, whether the first mailbox has been bound to user information; if yes, binding the second invoices to be pooled to the user information, and extracting nominal value information from the second invoices to be pooled, to obtain the nominal value information of the second invoices to be pooled on the basis of the first mode; if not, storing the second invoices to be pooled in a public invoice pool, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled.

[0045] Preferably, the following steps are further included prior to step S106: receiving a binding request of the first mailbox, the binding request being employed to request binding Date recue / Date received 202 1-1 1-01 of the user information to the first mailbox; generating a first verification code according to the binding request, and sending the first verification code to the first mailbox via a second mailbox; receiving a second verification code sent by an application page of the binding request, and judging whether the second verification code is identical with the first verification code; if yes, binding the first mailbox to the user information;
and inquiring the public invoice pool via mailbox account of the first mailbox, obtaining invoices of the first mailbox before binding from the public invoice pool, and binding the obtained invoices to the user information.

[0046] In this embodiment, when the first subtype interface receives the second invoices to be pooled coming from the first mailbox, it is firstly judged whether the first mailbox has been bound to user information. If yes, the received second invoices to be pooled are bound to the user information. If not, the second invoices to be pooled are stored in the public invoice pool, to wait for binding of the first mailbox to the user information, and the corresponding second invoices to be pooled are then extracted from the public invoice pool for correlation with the user information.

[0047] The mode of binding the first mailbox to the user information is as follows: the user sends a binding request to the server side via an application page of the binding request, for requesting to bind the user information to the first mailbox. After the server side receives the binding request, it generates a corresponding first verification code, and sends the first verification code to the first mailbox via a second mailbox. The second mailbox may be a designated public mailbox for receiving invoices to be pooled as sent from the first mailbox. After receiving the first verification code via the first mailbox, the user inputs a second verification code at the application page of the binding request and sends the second verification code to the server side. Generally speaking, the input second verification code is the first verification code. After receiving the second verification code, the server side judges whether the second verification code is identical with the first verification code, if yes, then binds the first mailbox to the user information. At the same time, second invoices to be pooled as sent before binding of the first mailbox are obtained from the public invoice pool, and the second invoices to be pooled are bound to the user information. Specifically, nominal value information of the invoices to be pooled is collected by mailbox pooling mode. Specifically, the nominal value information of the Date recue / Date received 202 1-1 1-01 invoices to be pooled is collected by a mode of forwarding the public mailbox.
At this time, it is necessary for the information collecting system to first apply for a public mailbox. In the process of specific implementation, the first mailbox may be a mailbox to which the user is bound, the second mailbox may be a public mailbox, referring to Fig.
4, the following steps are specifically performed:
1) The user operates on the client side, clicks binding mailbox, enters mailbox binding page, writes down the mailbox address, the client side invokes a mailbox binding interface, and sends a mailbox binding request to the server side.
2) The server side receives the mailbox binding request, maintains the binding relation between the user and the mailbox, and the state is to be verified. A
verification code with a certain validation period is generated for the mailbox, and stored in a cache server for binding verification, and the public mailbox is used to send a verification code mail to the mailbox to be bound.
3) The client side jumps to a verification code input page, the user inputs the verification code received by the mailbox to be bound, verification is clicked, and the client side invokes a mailbox binding verification interface.
4) The server side receives the mailbox binding verification request, inquires the verification code in the cache server according to the mailbox to be verified, and verifies whether the verification code is correct; step 5) is performed if verification is not passed, and step 6) is performed if verification is passed.
5) Verification not being passed is returned, and corresponding prompt information is popped up at the client side.
6) Verification is passed, the binding relation of the user mailbox is maintained as already verified, the public invoice pool is searched as to whether there is invoice record to which the mailbox corresponds; if yes, the invoice is bound to user relation, and binding being successful is returned.

Date recue / Date received 202 1-1 1-01 7) After mailbox binding is successful, the user may edit mails via the bound mailbox, add invoice PDF files and other required attachments (such as taxi travel itinerary), or forward received mails that contain invoices and attachments, to the public mailbox.
8) Timed tasks are created, unread mails are regularly obtained from the public mailbox, mail uids are obtained and stored in a queue to be analyzed, and the state of the mails is updated as "read".
9) Each server starts up a mail analyzing thread pool, each thread obtains mail uids to be analyzed from the queue to be analyzed, to be placed in the queue to be analyzed, and step 10) is performed; if no task to be analyzed is obtained for many times, the thread may be laid dormant for awhile.
10) Detailed information (including mail title, sender, mail text, attachment etc.) of the mail is obtained via the mail uid, and it is judged whether the attachment contains any electronic invoice; step 11) is performed if mail attachment does not contain any electronic invoice, and step 12) is performed if there is still electronic invoice in the mail attachment.
11) A piece of mail analyzing record is added to record basic information of the mail (such as mail title, sender, time, etc.), analysis failure state is set up, the reason for analysis failure is recorded to make it convenient for the user to check, and a message is sent for reminder.
12) Precise five essentials information of the electronic invoice is extracted, database is inquired through invoice number and invoice code to verify whether the invoice has been pooled; step 11) is performed if it has been pooled, otherwise invoice checking service is invoked; step 13) is performed if invoice check fails, otherwise step 14) is performed.
13) The reason for invoice check failure is obtained to serve as the reason for mail analysis failure, and step 11) is performed.

Date recue / Date received 202 1-1 1-01 14) The invoice is pooled into the public invoice pool, and invoice information of the invoice is stored. The invoice information includes structured data and non-structured data. In other words, structured data and non-structured data of the invoice are stored. Moreover, it is judged whether the mail has been bound to the user, invoices in the public invoice pool are stored in a user invoice list in the case the mail has been bound to the user to maintain the relation between user and invoices, a piece of mail analyzing record is finally added to record the basic information of the mail (such as mail title, sender, time, etc.), mail analyzing state is set up as successful, and a message is sent for reminder.

[0048] In one embodiment, prior to step S106 is further included: receiving account and password information of a third mailbox. Step S106 includes: extracting nominal value information from the fourth invoices to be pooled to obtain the nominal value information of the fourth invoices to be pooled on the basis of the first mode while reading and receiving the fourth invoices to be pooled from the third mailbox through the first subtype interface according to the account and password information of the third mailbox.

[0049] In this embodiment, a scheme of directly connecting to the user mailbox is set up.
Specifically, user authorization is obtained, the server side stores mailbox account and password of the user, user mailbox is automatically connected through a timed task, and the mail is analyzed to obtain the fourth invoices to be pooled. Nominal value information is extracted from the fourth invoices to be pooled on the basis of the first mode to obtain the nominal value information of the fourth invoices to be pooled. This scheme is relatively high in convenience and compatibility, but not high in safety, there is a risk of password leakage, and processing efficiency cannot be guaranteed with the increase in bound mailboxes.

[0050] In one embodiment, prior to step S106 is further included: connecting with mailbox gateway. Step S106 includes: extracting nominal value information from fifth invoices to be pooled to obtain the nominal value information of the fifth invoices to be pooled on the basis of the first mode while receiving the fifth invoices to be pooled provided by the mailbox gateway and satisfying invoice rules.

Date recue / Date received 202 1-1 1-01

[0051] In this embodiment, a scheme of pushing mailbox gateway is set up.
Specifically, this scheme requires linking up with mailbox gateway, the capability to perform rule check on all received mails is provided by the mailbox gateway, where invoice rules are satisfied, the mails are pushed to the server through in such forms as message queue, and the server analyzes the mails. This scheme is extremely high in convenience, as user operation is dispensed with, high in safety, average in compatibility, support from the mailbox gateway is required, and mapping relationship between user systems should be further bound if the user system is different from the mailbox user system.

[0052] Each of the aforementioned three mailbox pooling schemes has its merits and disadvantages, and can be selected according to practical circumstances.

[0053] In one embodiment, step S106 includes: obtaining nominal value information of the third invoices to be pooled on the basis of the second mode through the mode of receiving the nominal value information of the third invoices to be pooled as sent by the client side and coming from an application program when the second subtype interface receives the third invoices to be pooled as sent by the client side and coming from the application program; wherein the mode for the client side to obtain the nominal value information of the third invoices to be pooled coming from the application program includes the following:
the client side invokes an interface of a public platform via an application account and an application key provided by the public platform of the application program, and obtains a globally unique interface invoking credential of the public platform via the invoked interface; the client side invokes an invoice list interface of the public platform via the globally unique interface invoking credential, and obtains an invoice list of the public platform via the invoice list interface; and the client side confirms and selects the third invoices to be pooled in the invoice list, and receives nominal value information of the third invoices to be pooled as returned by the public platform.

[0054] In this embodiment, the application program can be WeChat. The client side can be one that is set up to correspond to the server side of the information collecting system. To realize the invoice pooling function of WeChat, it is firstly necessary to register a WeChat public platform, and to obtain appId (application account) and appSecret (application key).

Date recue / Date received 202 1-1 1-01 Specifically, as shown in Fig. 5, WeChat invoice pooling operations are as follows:
1) The client side invokes a WeChat public platform interface via appId and appSecret, and obtains access token (globally unique interface invoking credential), which should be used in subsequent invoking of other WeChat public platform interfaces.
2) The client side invokes a WeChat public platform ¨ external app pull-up invoice list interface, to pull up the WeChat invoice list.
3) The user selects an invoice that should be pooled, and after clicking confirmation, WeChat will return card id (the corresponding identification number in the list) and encrypt code (encrypted password) to which the selected invoice corresponds.
4) The client side invokes WeChat public platform ¨ batch inquiry invoice detailed information interface via card id and encrypt code to obtain detailed information of the invoice selected by the user. The detailed information of the invoice includes nominal value information of the invoice and its electronic invoice.
5) The client side invokes a server side interface to send the detailed information of the invoice to the server side for pooling.
6) The server side verifies the invoice to be pooled, inquires the database via invoice numbers and invoice codes to screen invoices that are already pooled, pools the screen invoices, and returns pooling success information and pooling failure information to the client side.
7) The client side displays the pooling success information and pooling failure information.

[0055] Therefore, the aforementioned embodiments provide multi-channel invoice pooling modes, including the pooling of paper invoices and the pooling of electronic invoices.
Date recue / Date received 202 1-1 1-01

[0056] In one embodiment, after step S106 is further included: pooling invoice images of electronic invoices and/or paper invoices received by the plural invoice receiving interfaces;
and releasing the pooled invoice images of the electronic invoices and/or paper invoices to a message queue, so that a reimbursement system extracts the invoice images of the electronic invoices and/or paper invoices from the message queue to perform automatic reimbursement.

[0057] See Fig. 6 for specifics. When the user drafts reimbursement, WEB SDK
is provided to the reimbursement system for convenient selection of invoices to be reimbursed; the reimbursement system is introduced with this component, a callback function is provided after initialization, and this callback function will be introduced into the invoice data selected by the user for the reimbursement system to process the logic after invoice selection. The user drafts the reimbursement procedure, selects the invoice, and submits the procedure after verification by the reimbursement procedure, while the reimbursement system invokes a server side interface, and updates the invoice state as being in the process of reimbursement. If the procedure is not in conformity, it will be rejected, in which case the server side interface is invoked, and the invoice state is updated as to be reimbursed.
Once the procedure is examined and approved, the procedure ends, in which case the server side interface is invoked, and the invoice state is updated as having been reimbursed.
Considering that plural events (such as bookkeeping, etc.) might be processed for the procedure to pass, should abnormality occur in the processing of any other events, the procedure would not normally end, but the server side interface has already been invoked to update the invoice state as having been reimbursed, at this time a rollback interface can be invoked through token returned by the interface within the validation period.

[0058] With respect to the automatic reimbursement procedure, after the pooling of invoices is successful, the server side releases the invoice information to the message queue, and a reimbursement system that is in need of automatic reimbursement can subscribe the corresponding topic, perform service verification according to pooling user and invoice information after the invoice information is obtained, and automatically draft the reimbursement procedure for the user if automatic reimbursement conditions are met.

Date recue / Date received 202 1-1 1-01

[0059] As should be noted, the client side in Fig. 6 is employed not only to pull electronic invoice data of electronic invoices of the WeChat interface, but also to provide photographing function to obtain invoice images of paper invoices. In other words, the client end collects both paper invoice images and electronic invoice data.

[0060] In view of the scheme illustrated in Fig. 6 in combination with the schemes described in the previous embodiments, the following specific implementation can be adopted.

[0061] A relational database (such as Oracle/DB2/SQLServer/My SQL, etc.) is used to serve as permanent storage of data, and is held responsible for storing various entity definitions such as invoice subject information, invoice line information, and information of users bound to invoices, etc.

[0062] A memory database (such as Redis/Memcache, etc.) is used to serve as cache service, cache verification code, invoice check result, mail analyzing queue, etc.

[0063] OCR service and check service can be currently provided by mature service providers, while those having self research capabilities can also employ self research service.

[0064] The message queue can be a conventional message queue (such as RabbitMQ/ActiveMQ/RocketMQ, etc.), while those having self research capabilities can also employ a self-researched message queue.

[0065] As regards mailbox protocols, SMTP is employed for sending mails, while IMAP is suggested for use in obtaining mails.

[0066] B/S architecture or C/S architecture can likewise be used for implementation, while it is recommended to use an architecture and a technology stack that conform to JEE
technical specifications to implement server side applications, such as (but not limited to) SpringBoot+MyBatis. Such relatively prevalent technology stacks as .NET/C# can also be used.

[0067] To avoid single point of failure, cluster deployment of applications can be adopted, and Date recue / Date received 202 1-1 1-01 soft/hard load balancing is performed via Apache/Nginx/F5, etc. Considering from the viewpoint of cost and degree of importance, it generally suffices to use Apache/Nginx to perform soft load balancing.

[0068] As should be understood, although the various steps in the flowcharts are sequentially displayed as indicated by arrows, these steps are not necessarily executed in the sequences indicated by arrows. Unless otherwise explicitly noted in this paper, execution of these steps is not restricted by any sequence, as these steps can also be executed in other sequences (than those indicated in the drawings). Moreover, at least partial steps in the drawings may include plural sub-steps or multi-phases, these sub-steps or phases are not necessarily completed at the same timing, but can be executed at different timings, and these sub-steps or phases are also not necessarily sequentially performed, but can be performed in turns or alternately with other steps or with at least some of sub-steps or phases of other steps.

[0069] The present application further provides an invoice information collecting device, as shown in Fig. 7, the device comprises a first setting-up module 10, a second setting-up module 20 and a collecting module 30. The first setting-up module 10 is employed for setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled; the second setting-up module 20 is employed for setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces; and the collecting module 30 is employed for performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received.

[0070] In one of the embodiments, the types of the invoices to be pooled include invoice image type of paper invoices and electronic invoice type, the plural invoice receiving interfaces include a first-type interface and a second-type interface, and the invoice information of the invoices to be pooled includes nominal value information of the invoices to be pooled;
the second setting-up module 20 is specifically further employed for configuring the Date recue / Date received 202 1-1 1-01 invoice information analyzing mode of the first-type interface as a first analyzing mode when the first-type interface is employed to receive invoices to be pooled of the invoice image type, the first analyzing mode being employed to indicate performing information collection on the invoices to be pooled via image recognition technique; and configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type, the second analyzing mode being employed to indicate performing information collection on the invoices to be pooled by a mode of obtaining nominal value information of the invoices to be pooled.

[0071] In one of the embodiments, the collecting module 30 is specifically further employed for determining invoice images of first invoices to be pooled when the first-type interface receives the first invoices to be pooled, performing information collection on the invoice images by invoking optical character recognition service on the basis of the first analyzing mode, thereby obtaining nominal value information of the first invoices to be pooled.

[0072] In one of the embodiments, the second-type interface includes a first subtype interface and a second subtype interface, the second setting-up module 20 is specifically further employed for configuring invoice information analyzing mode of the first subtype interface as a first mode in the second analyzing mode when the first subtype interface is employed to receive second invoices to be pooled of the electronic invoice type coming from a mailbox, the first mode being employed to indicate extracting nominal value information from the second invoices to be pooled; and configuring invoice information analyzing mode of the second subtype interface as a second mode in the second analyzing mode when the second subtype interface is employed to receive third invoices to be pooled of the electronic invoice type coming from an application program, the second mode being employed to indicate receiving nominal value information of the third invoices to be pooled coming from the application program.

[0073] In one of the embodiments, the collecting module 30 is specifically further employed for judging, when the first subtype interface receives the second invoices to be pooled coming from a first mailbox, whether the first mailbox has been bound to user information;
if yes, binding the second invoices to be pooled to the user information, and extracting Date recue / Date received 202 1-1 1-01 nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled; if not, storing the second invoices to be pooled in a public invoice pool, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled.

[0074] In one of the embodiments, the invoice information collecting device further comprises a binding module for receiving a binding request of the first mailbox, the binding request being employed to request binding of the user information to the first mailbox; generating a first verification code according to the binding request, and sending the first verification code to the first mailbox via a second mailbox; receiving a second verification code sent by an application page of the binding request, and judging whether the second verification code is identical with the first verification code; if yes, binding the first mailbox to the user information; and inquiring the public invoice pool via mailbox account of the first mailbox, obtaining invoices of the first mailbox before binding from the public invoice pool, and binding the obtained invoices to the user information.

[0075] In one of the embodiments, the collecting module 30 is specifically further employed for obtaining nominal value information of the third invoices to be pooled on the basis of the second mode through the mode of receiving the nominal value information of the third invoices to be pooled as sent by the client side and coming from an application program when the second subtype interface receives the third invoices to be pooled as sent by the client side and coming from the application program; wherein the mode for the client side to obtain the nominal value information of the third invoices to be pooled coming from the application program includes the following: the client side invokes an interface of a public platform via an application account and an application key provided by the public platform of the application program, and obtains a globally unique interface invoking credential of the public platform via the invoked interface; the client side invokes an invoice list interface of the public platform via the globally unique interface invoking credential, and obtains an invoice list of the public platform via the invoice list interface; and the client side confirms and selects the third invoices to be pooled in the invoice list, and receives nominal value information of the third invoices to be pooled as returned by the public platform.
Date recue / Date received 202 1-1 1-01

[0076] In one of the embodiments, the invoice information collecting device further comprises a reimbursing module for pooling invoice images of electronic invoices and/or paper invoices received by the plural invoice receiving interfaces; and releasing the pooled invoice images of the electronic invoices and/or paper invoices to a message queue, so that a reimbursement system extracts the invoice images of the electronic invoices and/or paper invoices from the message queue to perform automatic reimbursement.

[0077] Specific definitions to the invoice information collecting device may be inferred from the aforementioned definitions to the invoice information collecting method, while no repetition is made in this context. The various modules in the aforementioned invoice information collecting device can be wholly or partly realized via software, hardware, and a combination of software with hardware. The various modules can be embedded in the form of hardware in a processor in a computer equipment or independent of any computer equipment, and can also be stored in the folin of software in a memory in a computer equipment, so as to facilitate the processor to invoke and perform operations corresponding to the aforementioned various modules.

[0078] In one embodiment, a computer equipment is provided, the computer equipment can be a server run by the information collecting system, and its internal structure can be as shown in Fig. 8. The computer equipment comprises a processor, a memory, a network interface and a database connected to each other via a system bus. The processor of the computer equipment is employed to provide computing and controlling capabilities. The memory of the computer equipment includes a nonvolatile storage medium, and an internal memory.
The nonvolatile storage medium stores therein an operating system, a computer program and a database. The internal memory provides environment for the running of the operating system and the computer program in the nonvolatile storage medium. The network interface of the computer equipment is employed to connect to an external terminal for interaction of external information data with the terminal. The computer program realizes an invoice information collecting method when it is executed by the processor.

[0079] As understandable to persons skilled in the art, the structure illustrated in Fig. 8 is merely a block diagram of partial structure relevant to the solution of the present application, and does not constitute any restriction to the computer equipment on which the solution of the Date recue / Date received 202 1-1 1-01 present application is applied, as the specific computer equipment may comprise component parts that are more than or less than those illustrated in Fig. 8, or may combine certain component parts, or may have different layout of component parts.

[0080] In one embodiment, there is provided a computer equipment that comprises a memory, a processor and a computer program stored on the memory and operable on the processor, and the processor realizes the following steps when it executes the computer program:
setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled; setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces; and performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received.

[0081] In one of the embodiments, the types of the invoices to be pooled include invoice image type of paper invoices and electronic invoice type, the plural invoice receiving interfaces include a first-type interface and a second-type interface, and the invoice information of the invoices to be pooled includes nominal value information of the invoices to be pooled;
the following steps are realized when the processor executes the computer program to realize the aforementioned step of setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces: configuring the invoice information analyzing mode of the first-type interface as a first analyzing mode when the first-type interface is employed to receive invoices to be pooled of the invoice image type, the first analyzing mode being employed to indicate performing information collection on the invoices to be pooled via image recognition technique; and configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type, the second analyzing mode being employed to indicate performing information collection on the invoices to be pooled by a mode of obtaining nominal value information of the invoices to be pooled.

Date recue / Date received 202 1-1 1-01

[0082] In one of the embodiments, when the processor executes the computer program to realize the aforementioned step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received, the following steps are specifically realized: determining invoice images of first invoices to be pooled when the first-type interface receives the first invoices to be pooled, performing information collection on the invoice images by invoking optical character recognition service on the basis of the first analyzing mode, thereby obtaining nominal value information of the first invoices to be pooled.

[0083] In one of the embodiments, the second-type interface includes a first subtype interface and a second subtype interface; when the processor executes the computer program to realize the aforementioned step of configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type, the following steps are specifically realized: configuring invoice information analyzing mode of the first subtype interface as a first mode in the second analyzing mode when the first subtype interface is employed to receive second invoices to be pooled of the electronic invoice type coming from a mailbox, the first mode being employed to indicate extracting nominal value information from the second invoices to be pooled; and configuring invoice information analyzing mode of the second subtype interface as a second mode in the second analyzing mode when the second subtype interface is employed to receive third invoices to be pooled of the electronic invoice type coming from an application program, the second mode being employed to indicate receiving nominal value information of the third invoices to be pooled coming from the application program.

[0084] In one of the embodiments, when the processor executes the computer program to realize the aforementioned step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as Date recue / Date received 202 1-1 1-01 received, the following steps are specifically realized: judging, when the first subtype interface receives the second invoices to be pooled coming from a first mailbox, whether the first mailbox has been bound to user information; if yes, binding the second invoices to be pooled to the user information, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled; if not, storing the second invoices to be pooled in a public invoice pool, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled.

[0085] In one of the embodiments, the following steps are realized when the processor executes the computer program: receiving a binding request of the first mailbox, the binding request being employed to request binding of the user information to the first mailbox; generating a first verification code according to the binding request, and sending the first verification code to the first mailbox via a second mailbox; receiving a second verification code sent by an application page of the binding request, and judging whether the second verification code is identical with the first verification code; if yes, binding the first mailbox to the user information; and inquiring the public invoice pool via mailbox account of the first mailbox, obtaining invoices of the first mailbox before binding from the public invoice pool, and binding the obtained invoices to the user information.

[0086] In one of the embodiments, when the processor executes the computer program to realize the aforementioned step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received, the following steps are specifically realized: when the second subtype interface receives the third invoices to be pooled coming from the application program and sent by a client side, obtaining nominal value information of the third invoices to be pooled on the basis of the second mode by the mode of receiving nominal value information of the third invoices to be pooled coming from the application program and sent by the client side;
wherein the mode for the client side to obtain the nominal value information of the third invoices to be pooled coming from the application program includes the following: the Date recue / Date received 202 1-1 1-01 client side invokes an interface of a public platform via an application account and an application key provided by the public platform of the application program, and obtains a globally unique interface invoking credential of the public platform via the invoked interface; the client side invokes an invoice list interface of the public platform via the globally unique interface invoking credential, and obtains an invoice list of the public platform via the invoice list interface; and the client side confirms and selects the third invoices to be pooled in the invoice list, and receives nominal value information of the third invoices to be pooled as returned by the public platform.

[0087] In one of the embodiments, the following steps are realized when the processor executes the computer program: pooling invoice images of electronic invoices and/or paper invoices received by the plural invoice receiving interfaces; and releasing the pooled invoice images of the electronic invoices and/or paper invoices to a message queue, so that a reimbursement system extracts the invoice images of the electronic invoices and/or paper invoices from the message queue to perform automatic reimbursement.

[0088] In one embodiment, there is provided a computer readable storage medium storing thereon a computer program, and the following steps are realized when the computer program is executed by a processor: setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled; setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces;
and performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received.

[0089] In one of the embodiments, the types of the invoices to be pooled include invoice image type of paper invoices and electronic invoice type, the plural invoice receiving interfaces include a first-type interface and a second-type interface, and the invoice information of the invoices to be pooled includes nominal value information of the invoices to be pooled;
the following steps are realized when the computer program is executed by a processor to realize the aforementioned step of setting up an invoice information analyzing mode for Date recue / Date received 202 1-1 1-01 each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces: configuring the invoice information analyzing mode of the first-type interface as a first analyzing mode when the first-type interface is employed to receive invoices to be pooled of the invoice image type, the first analyzing mode being employed to indicate performing information collection on the invoices to be pooled via image recognition technique; and configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type, the second analyzing mode being employed to indicate performing information collection on the invoices to be pooled by a mode of obtaining nominal value information of the invoices to be pooled.

[0090] In one of the embodiments, when the computer program is executed by a processor to realize the aforementioned step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received, the following steps are specifically realized: determining invoice images of first invoices to be pooled when the first-type interface receives the first invoices to be pooled, performing information collection on the invoice images by invoking optical character recognition service on the basis of the first analyzing mode, thereby obtaining nominal value information of the first invoices to be pooled.

[0091] In one of the embodiments, the second-type interface includes a first subtype interface and a second subtype interface; when the computer program is executed by a processor to realize the aforementioned step of configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type, the following steps are specifically realized: configuring invoice information analyzing mode of the first subtype interface as a first mode in the second analyzing mode when the first subtype interface is employed to receive second invoices to be pooled of the electronic invoice type coming from a mailbox, the first mode being employed to indicate extracting nominal value information from the second invoices to be pooled; and configuring invoice information Date recue / Date received 202 1-1 1-01 analyzing mode of the second subtype interface as a second mode in the second analyzing mode when the second subtype interface is employed to receive third invoices to be pooled of the electronic invoice type coming from an application program, the second mode being employed to indicate receiving nominal value information of the third invoices to be pooled coming from the application program.

[0092] In one of the embodiments, when the computer program is executed by a processor to realize the aforementioned step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received, the following steps are specifically realized: judging, when the first subtype interface receives the second invoices to be pooled coming from a first mailbox, whether the first mailbox has been bound to user information; if yes, binding the second invoices to be pooled to the user information, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled; if not, storing the second invoices to be pooled in a public invoice pool, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled.

[0093] In one of the embodiments, the following steps are realized when the computer program is executed by a processor: receiving a binding request of the first mailbox, the binding request being employed to request binding of the user information to the first mailbox;
generating a first verification code according to the binding request, and sending the first verification code to the first mailbox via a second mailbox; receiving a second verification code sent by an application page of the binding request, and judging whether the second verification code is identical with the first verification code; if yes, binding the first mailbox to the user information; and inquiring the public invoice pool via mailbox account of the first mailbox, obtaining invoices of the first mailbox before binding from the public invoice pool, and binding the obtained invoices to the user information.

[0094] In one of the embodiments, when the computer program is executed by a processor to Date recue / Date received 202 1-1 1-01 realize the aforementioned step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received, the following steps are specifically realized: when the second subtype interface receives the third invoices to be pooled coming from the application program and sent by a client side, obtaining nominal value information of the third invoices to be pooled on the basis of the second mode by the mode of receiving nominal value information of the third invoices to be pooled coming from the application program and sent by the client side;
wherein the mode for the client side to obtain the nominal value information of the third invoices to be pooled coming from the application program includes the following: the client side invokes an interface of a public platform via an application account and an application key provided by the public platform of the application program, and obtains a globally unique interface invoking credential of the public platform via the invoked interface; the client side invokes an invoice list interface of the public platform via the globally unique interface invoking credential, and obtains an invoice list of the public platform via the invoice list interface; and the client side confirms and selects the third invoices to be pooled in the invoice list, and receives nominal value information of the third invoices to be pooled as returned by the public platform.

[0095] In one of the embodiments, the following steps are realized when the computer program is executed by a processor: pooling invoice images of electronic invoices and/or paper invoices received by the plural invoice receiving interfaces; and releasing the pooled invoice images of the electronic invoices and/or paper invoices to a message queue, so that a reimbursement system extracts the invoice images of the electronic invoices and/or paper invoices from the message queue to perform automatic reimbursement.

[0096] As comprehensible to persons ordinarily skilled in the art, the entire or partial flows in the methods according to the aforementioned embodiments can be completed via a computer program instructing relevant hardware, the computer program can be stored in a nonvolatile computer-readable storage medium, and the computer program can include the flows as embodied in the aforementioned various methods when executed. Any reference to the memory, storage, database or other media used in the various embodiments provided Date recue / Date received 202 1-1 1-01 by the present application can all include nonvolatile and/or volatile memory/memories.
The nonvolatile memory can include a read-only memory (ROM), a programmable ROM
(PROM), an electrically programmable ROM (EPROM), an electrically erasable and programmable ROM (EEPROM) or a flash memory. The volatile memory can include a random access memory (RAM) or an external cache memory. To serve as explanation rather than restriction, the RAM is obtainable in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM
(DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM
(SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0097] Technical features of the aforementioned embodiments are randomly combinable, while all possible combinations of the technical features in the aforementioned embodiments are not exhausted for the sake of brevity, but all these should be considered to fall within the scope recorded in the Description as long as such combinations of the technical features are not mutually contradictory.

[0098] The foregoing embodiments are merely directed to several modes of execution of the present application, and their descriptions are relatively specific and detailed, but they should not be hence misunderstood as restrictions to the inventive patent scope. As should be pointed out, persons with ordinary skill in the art may further make various modifications and improvements without departing from the conception of the present application, and all these should pertain to the protection scope of the present application.
Accordingly, the patent protection scope of the present application shall be based on the attached Claims.

Date recue / Date received 202 1-1 1-01

Claims

1. An invoice information collecting method, characterized in comprising:
setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled;
setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces; and performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received.

2.
The method according to Claim 1, characterized in that the types of the invoices to be pooled include invoice image type of paper invoices and electronic invoice type, that the plural invoice receiving interfaces include a first-type interface and a second-type interface, that the invoice information of the invoices to be pooled includes nominal value information of the invoices to be pooled, and that the step of setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces includes:
configuring the invoice information analyzing rriode of the first-type interface as a first analyzing mode when the first-type interface is employed to receive invoices to be pooled of the invoice image type, the first analyzing mode being employed to indicate performing information collection on the invoices to be pooled via image recognition technique; and configuring the invoice information analyzing mode of the second-type interface as a second Date recue / Date received 2021-11-01 analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type, the second analyzing mode being employed to indicate performing information collection on the invoices to be pooled by a mode of obtaining nominal value information of the invoices to be pooled.

3.
The method according to Claim 2, characterized in that the step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received includes:
determining invoice images of first invoices to be pooled when the first-type interface receives the first invoices to be pooled, performing information collection on the invoice images by invoking optical character recognition service on the basis of the first analyzing mode, thereby obtaining nominal value information of the first invoices to be pooled.

4. The method according to Claim 2, characterized in that the second-type interface includes a first subtype interface and a second subtype interface, and that the step of configuring the invoice information analyzing mode of the second-type interface as a second analyzing mode when the second-type interface is employed to receive invoices to be pooled of the electronic invoice type includes:
configuring invoice information analyzing mode of the first subtype interface as a first mode in the second analyzing mode when the first subtype interface is employed to receive a second invoices to be pooled of the electronic invoice type coming from a mailbox, the first mode being employed to indicate extracting nominal value information from the second invoices to be pooled;
and configuring invoice information analyzing mode of the second subtype interface as a second mode in the second analyzing mode when the second subtype interface is employed to receive a third invoices to be pooled of the electronic invoice type coming from an application program, the second mode being employed to indicate receiving nominal value information of the third invoices to be pooled coming from the application program.

Date recue / Date received 2021-11-01

5.
The method according to Claim 4, characterized in that the step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received includes:
judging, when the first subtype interface receives the second invoices to be pooled coming from a first mailbox, whether the first mailbox has been bound to user information;
if yes, binding the second invoices to be pooled to the user information, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled;
if not, storing the second invoices to be pooled in a public invoice pool, and extracting nominal value information from the second invoices to be pooled on the basis of the first mode, to obtain the nominal value information of the second invoices to be pooled;
preferably, the method further comprising: receiving a binding request of the first mailbox, the binding request being employed to request binding of the user information to the first mailbox;
generating a first verification code according to the binding request, and sending the first verification code to the first mailbox via a second mailbox;
receiving a second verification code sent by an application page of the binding request, and judging whether the second verification code is identical with the first verification code;
if yes, binding the first mailbox to the user information; and inquiring the public invoice pool via mailbox account of the first mailbox, obtaining invoices of the first mailbox before binding from the public invoice pool, and binding the obtained invoices to the user information.

Date recue / Date received 2021-11-01

6. The method according to Claim 4, characterized in that the step of performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received includes:
when the second subtype interface receives the third invoices to be pooled coming from the application program and sent by a client side, obtaining nominal value information of the third invoices to be pooled on the basis of the second mode by the mode of receiving nominal value information of the third invoices to be pooled coming from the application program and sent by the client side;
wherein the mode for the client side to obtain the nominal value information of the third invoices to be pooled coming from the application program includes the following:
the client side invokes an interface of a public platform via an application account and an application key provided by the public platform of the application program, and obtains a globally unique interface invoking credential of the public platform via the invoked interface;
the client side invokes an invoice list interface of the public platform via the globally unique interface invoking credential, and obtains an invoice list of the public platform via the invoice list interface; and the client side confirms and selects the third invoices to be pooled in the invoice list, and receives nominal value information of the third invoices to be pooled as returned by the public platform.

7. The method according to Claim 1, characterized in further comprising:
pooling invoice images of electronic invoices and/or paper invoices received by the plural invoice receiving interfaces; and Date recue / Date received 2021-11-01 releasing the pooled invoice images of the electronic invoices and/or paper invoices to a message queue, so that a reimbursement system extracts the invoice images of the electronic invoices and/or paper invoices from the message queue to perform automatic reimbursement.

8. An invoice information collecting device, characterized in comprising:
a first setting-up module, for setting up plural invoice receiving interfaces, each for receiving invoices of identical type or different types to be pooled;
a second setting-up module, for setting up an invoice information analyzing mode for each of the invoice receiving interfaces according to the type(s) of the invoices to be pooled as received by each of the invoice receiving interfaces; and a collecting module, for performing information collection, when any of the invoice receiving interfaces receives the invoices to be pooled, on the received invoices to be pooled according to the invoice information analyzing mode of any of the invoice receiving interfaces, thereby obtaining invoice information of the invoices to be pooled as received.

9. A computer equipment, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the method steps according to anyone of Claims 1 to 7 are realized when the processor executes the computer program.

10. A computer readable storage medium, storing a computer program thereon, characterized in that the computer program realizes the method steps according to anyone of Claims 1 to 7 upon execution by a processor.

Date recue / Date received 2021-11-01