CN113139408A - Bill checking method, device and storage medium - Google Patents
Bill checking method, device and storage medium Download PDFInfo
- Publication number
- CN113139408A CN113139408A CN202010066182.8A CN202010066182A CN113139408A CN 113139408 A CN113139408 A CN 113139408A CN 202010066182 A CN202010066182 A CN 202010066182A CN 113139408 A CN113139408 A CN 113139408A
- Authority
- CN
- China
- Prior art keywords
- bill
- file
- checking
- inspected
- ticket
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000012795 verification Methods 0.000 claims abstract description 18
- 238000007689 inspection Methods 0.000 claims description 41
- 238000012545 processing Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 8
- 238000007781 pre-processing Methods 0.000 claims description 6
- 238000000605 extraction Methods 0.000 claims description 5
- 230000006870 function Effects 0.000 description 14
- 230000008569 process Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000003086 colorant Substances 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
- G06V30/40—Document-oriented image-based pattern recognition
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V10/00—Arrangements for image or video recognition or understanding
- G06V10/20—Image preprocessing
- G06V10/26—Segmentation of patterns in the image field; Cutting or merging of image elements to establish the pattern region, e.g. clustering-based techniques; Detection of occlusion
- G06V10/267—Segmentation of patterns in the image field; Cutting or merging of image elements to establish the pattern region, e.g. clustering-based techniques; Detection of occlusion by performing operations on regions, e.g. growing, shrinking or watersheds
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
- G06V30/10—Character recognition
- G06V30/22—Character recognition characterised by the type of writing
- G06V30/224—Character recognition characterised by the type of writing of printed characters having additional code marks or containing code marks
- G06V30/2247—Characters composed of bars, e.g. CMC-7
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
- G06V30/10—Character recognition
Landscapes
- Engineering & Computer Science (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Multimedia (AREA)
- Theoretical Computer Science (AREA)
- Artificial Intelligence (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
A bill checking method comprises the steps of obtaining a bill file to be checked and identifying bill information of the bill file to be checked when a bill checking command is received; sending the identified bill information to a bill verification end for checking; and receiving the checking result sent by the bill verifying end. The bill checking device can automatically check bills and improve bill checking efficiency.
Description
Technical Field
The present disclosure relates to computer technology, and more particularly, to a method and apparatus for checking bills and a storage medium.
Background
In general, a large number of bills are generated in enterprises, for example, bills which are frequently processed are required to be used in payment and reimbursement, the bills may have false bills and wrong bills, financial staff is required to manually network to access a tax invoice verification system, bills to be verified are added one by one to be checked and then registered, and therefore time is consumed, and meanwhile errors are prone to occur.
Disclosure of Invention
The application provides a bill checking method, a bill checking device and a storage medium, which can achieve the purposes of automatically checking bills and improving bill checking efficiency.
The application provides a bill checking method, which comprises the following steps: when a bill checking command is received, acquiring a bill file to be checked, and identifying bill information of the bill file to be checked; sending the identified bill information to a bill verification end for checking; and receiving the checking result sent by the bill verifying end.
In an exemplary embodiment, before the ticket information for identifying the ticket file to be inspected, the method further includes:
preprocessing the acquired bill file to be inspected; the pretreatment comprises at least one of the following modes: compressing the bill files with the size exceeding a preset size; prompting uploading errors for other types of files which are not the bill files; and processing the bill files lower than the page identification requirement.
In an exemplary embodiment, before the ticket information for identifying the ticket file to be inspected, the method further includes: judging whether the acquired bill file to be inspected is a multi-bill combined file; when the document is judged to be a multi-bill combined document, cutting the multi-bill combined document into a plurality of single-bill documents; and each single ticket file is used as a ticket file to be checked.
In an exemplary embodiment, the method further includes: when receiving an extraction command, extracting the bill information of the selected bill file to be inspected and/or extracting the bill information of the selected inspected bill file for summarizing and outputting; the ticket information includes at least one of: bill name, bill issuing date, bill type, bill amount, bill issuing unit, bill inspection result, bill issuing unit code, bill code and bill number.
In an exemplary embodiment, the method further includes: prompting the checking state of the acquired bill file; the ping state includes at least one of: the inspection is already carried out; invalid parameters, unselected, waiting for inspection; when the inspection state is inspected, the inspection state further includes an inspection result; the inspection result includes: checking passed, checking failed and checking inconsistent.
In an exemplary embodiment, after receiving the result of the verification sent by the bill validation end, the method further includes: and correspondingly storing the inspection result and the bill file to be inspected.
In an exemplary embodiment, the method further includes: and checking the duplicate of the acquired bill file to be checked.
In an exemplary embodiment, the above-mentioned duplication checking of the acquired ticket file to be checked includes at least one of the following ways: when the MD5 value of the currently acquired ticket file to be checked is judged to be the same as the MD5 value of the acquired ticket file to be checked, judging that the currently acquired ticket to be checked is a repeated ticket file to be checked; and when the note information of the currently identified note file to be inspected is judged to be the same as the note information of the identified note file to be inspected, judging that the currently identified note to be inspected is the repeated inspection note file.
The present application further provides a bill checking device, which includes: the bill acquisition module is used for acquiring a bill file to be inspected; the bill identification module is used for identifying bill information of the bill file to be inspected, and the bill information comprises a bill inspection code; the bill sending module is used for sending the identified bill information to a bill verification end for checking; and the bill receiving module is used for receiving the checking result sent by the bill verifying end.
The present application also relates to a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a method as described in any of the embodiments.
Compared with the prior art, the method and the device have the advantages that the bill information is automatically identified and sent to the bill checking end to be checked, and the checking result is received and fed back to the user, so that the bill checking efficiency is greatly improved.
The method and the device facilitate the user to collect the summary bill information by automatically identifying the bill information and providing the function of extracting the bill information for the user.
The method and the device have the advantages that the duplicate checking function for obtaining the bill files is added, and account errors are avoided when repeated identification and collection are carried out.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. Other advantages of the application may be realized and attained by the instrumentalities and combinations particularly pointed out in the specification, claims, and drawings.
Drawings
The accompanying drawings are included to provide an understanding of the present disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the examples serve to explain the principles of the disclosure and not to limit the disclosure.
FIG. 1 is a flowchart of a method for checking a ticket according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an operation interface for checking a user according to an embodiment of the present disclosure;
FIG. 3 is a user interface for recognition according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of interaction and functional logic according to an embodiment of the present application;
fig. 5 is a schematic diagram of a bill checking device module according to an embodiment of the present application.
Detailed Description
The present application describes embodiments, but the description is illustrative rather than limiting and it will be apparent to those of ordinary skill in the art that many more embodiments and implementations are possible within the scope of the embodiments described herein. Although many possible combinations of features are shown in the drawings and discussed in the detailed description, many other combinations of the disclosed features are possible. Any feature or element of any embodiment may be used in combination with or instead of any other feature or element in any other embodiment, unless expressly limited otherwise.
The present application includes and contemplates combinations of features and elements known to those of ordinary skill in the art. The embodiments, features and elements disclosed in this application may also be combined with any conventional features or elements to form a unique inventive concept as defined by the claims. Any feature or element of any embodiment may also be combined with features or elements from other inventive aspects to form yet another unique inventive aspect, as defined by the claims. Thus, it should be understood that any of the features shown and/or discussed in this application may be implemented alone or in any suitable combination. Accordingly, the embodiments are not limited except as by the appended claims and their equivalents. Furthermore, various modifications and changes may be made within the scope of the appended claims.
Further, in describing representative embodiments, the specification may have presented the method and/or process as a particular sequence of steps. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. Other orders of steps are possible as will be understood by those of ordinary skill in the art. Therefore, the particular order of the steps set forth in the specification should not be construed as limitations on the claims. Further, the claims directed to the method and/or process should not be limited to the performance of their steps in the order written, and one skilled in the art can readily appreciate that the sequences may be varied and still remain within the spirit and scope of the embodiments of the present application.
The technical solutions of the present application will be described in more detail below with reference to the accompanying drawings and embodiments.
As shown in fig. 1, a bill checking method according to an embodiment of the present invention includes the following steps:
s101, when a bill checking command is received, acquiring a bill file to be checked, and identifying bill information of the bill file to be checked;
for example, the bill file to be checked can be in the form of a picture file, a PDF file, a two-dimensional code, and the like of an entity bill.
Illustratively, the ticket information includes a ticket challenge code; for example, when the document is an invoice, the invoice identifier includes an invoice code and an invoice number. The ticket information may also include the ticket name, date the ticket was issued, type of ticket, amount of ticket, unit of ticket issued, etc.
In an exemplary embodiment, as shown in fig. 2, a user may select a ticket file to be checked from a local or cloud document by "adding a file" in an operation interface, add the selected ticket file to a function file list, select a single ticket file, or add a plurality of ticket files to the list in one step to realize import in one-click. The inspection can be performed directly, or the inspection can be performed after clicking the "start inspection" or "start identification" button after selecting the file in the list in fig. 2, and the whole inspection process is automatically processed.
S102, sending the identified bill information to a bill verification end for checking;
and S103, receiving the checking result sent by the bill verifying end.
Illustratively, the identification of the ticket information may be performed on the ticket to be inspected by OCR technology.
Illustratively, when the bill file to be checked is an invoice file, the bill verification end is a national tax invoice checking system. The client is connected with the national tax invoice checking system through an interface, and the invoice code and the invoice number of the identified invoice file are automatically input into the national tax invoice checking system for checking. The client only needs to receive the checking result generated by the national tax invoice checking system.
An exemplary embodiment, before the step S101, identifying the ticket information of the ticket file to be inspected, further includes: and step S104, preprocessing the acquired bill file to be inspected.
In one exemplary embodiment, the pre-processing comprises at least one of:
A. compressing the bill files with the size exceeding a preset size; due to the fact that the uploading and sending speed is reduced due to the fact that the bill files are too large, the verification speed can be improved due to the fact that the bill files are suitable for the size, and the situation that a user waits for too long is avoided.
B. Prompting uploading errors for other types of files which are not the bill files; because the user sometimes uploads other files as the bill file by mistake, the verification process is performed again to cause the waste of verification time, so that the user needs to avoid the problem.
C. And processing the bill files lower than the page identification requirement. When the definition and the brightness of the page are not good, the accuracy of the identified page information can be affected, so that the condition of verification failure is avoided by processing in advance.
An exemplary embodiment, before the step S101, identifying the ticket information of the ticket file to be inspected, further includes the steps of:
s105, judging whether the acquired bill file to be inspected is a multi-bill combined file;
s106, when the multi-bill combined file is judged, cutting the multi-bill combined file into a plurality of single-bill files; and each single ticket file is used as a ticket file to be checked.
In order to avoid that a user uploads bill files to be inspected one by one, the cutting function of the bills is added, so that the user can be allowed to upload one file with a plurality of bills simultaneously, the file is automatically cut into the plurality of bill files during identification and then inspected, and the bill inspection efficiency is further improved. In one exemplary embodiment, the multi-note combined file can be cut by adopting an object detection algorithm.
In an exemplary embodiment, the above-mentioned bill checking method further includes step S107, when receiving the extraction command, extracting the bill information of the selected bill file to be checked, and/or extracting the bill information of the selected checked bill file for summary output.
In one exemplary embodiment, the billing information includes at least one of: bill name, bill issuing date, bill type, bill amount, bill issuing unit, bill inspection result, bill issuing unit code, bill code and bill number.
The user can extract the bill information for gathering after the bill verification after the bill file is uploaded, and also can extract the bill information for gathering after the bill information is only identified before the bill file is not verified, so that the user can conveniently count accounts at any time.
As shown in fig. 3, when the user selects the "start extraction" command, the user can automatically extract the ticket information of the uploaded ticket file and select the required ticket information by selecting the "extract invoice" function option.
In an exemplary embodiment, the above-mentioned bill checking method further includes step S108 of prompting the checking status of the acquired bill file.
In one exemplary embodiment, the ping status includes at least one of: checked, invalid parameters, unselected, waiting for check; when the inspection state is inspected, the inspection state further includes an inspection result; the inspection result includes: checking passed, checking failed and checking inconsistent.
As shown in fig. 2, the current functional interface displays the inspection state of the bill file uploaded by the user, and different colors are adopted to prompt different inspection states, when the inspection passes through the prompt inspection, a green prompt can be adopted to prompt a positive inspection result; when the inspection is not passed, the inspection information is not uniform, the invalid parameter, etc. may prompt a negative inspection result in red.
In an exemplary embodiment, after the step S103 receives the inspection result sent by the bill verification end, the method further includes a step S109 of storing the inspection result in correspondence with the bill file to be inspected.
So that the user can consult and extract at any time.
In the embodiment of the invention, the bill information of the identified bill file is collected and stored, so that a user can extract the bill information before or after verification.
In an exemplary embodiment, the ticket checking method further includes step S110, performing duplication checking on the acquired ticket file to be checked. If the user accidentally uploads and examines the same bill file, errors and even economic losses are caused to subsequent statistics, and the problems are avoided by the method.
In an exemplary embodiment, the duplication checking of the acquired ticket file to be checked includes at least one of the following ways:
in the first mode, when the MD5 value of the currently acquired ticket file to be checked is judged to be the same as the MD5 value of the already acquired ticket file to be checked, the currently acquired ticket to be checked is judged to be the repeated ticket file. As known to those skilled in the art, each photo has only one MD5 value, and if there is a ticket file with the same MD5 value, it indicates that uploading is repeated.
And secondly, when the note information of the currently identified note file to be inspected is judged to be the same as the note information of the identified note file to be inspected, judging that the currently identified note to be inspected is the repeatedly inspected note file. When the user repeatedly takes a plurality of pictures with the same bill, the plurality of repeatedly taken pictures have different MD5 values, and at the moment, the judgment of repeatedly checking the bill file cannot be carried out through the MD5 value. Further comparison of the identified bill information is needed to judge, and when the comparison is consistent, the bill file which is checked repeatedly is represented, and the user is prompted.
As shown in fig. 5, an embodiment of the present invention further provides a bill checking apparatus, including the following modules:
the bill acquiring module 10 is used for acquiring a bill file to be inspected;
the bill identifying module 20 is used for identifying the bill information of the bill file to be inspected;
the bill sending module 30 is used for sending the identified bill information to a bill verification end for checking;
and the bill receiving module 40 is used for receiving the checking result sent by the bill verifying end.
An embodiment of the present invention further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method described in any one of the above.
As shown in fig. 4, the interaction and function module diagram of the embodiment of the present invention includes a user operation module and a code automatic processing module.
The user operation module is used for providing a function interface for a user to enter, selecting the condition bill class file and receiving a command button of 'start checking' or 'start identification' clicked by the user on the operation interface.
And the code automation processing module is used for providing preprocessing on the file at a client (Cilent), wherein the preprocessing is the processing mode such as A, B, C mentioned above. After the processing is finished, the user can be provided for identification checking and/or identification extraction, and the user can select according to the needs of the user.
Specifically, as shown in fig. 2 and 3, the user performs the one-touch operation as follows
Opening a function interface by a user, and selecting a corresponding function tab;
clicking 'add file', selecting target file from local or cloud file and adding the target file into the functional file list, wherein single file addition and multi-file one-step addition into the list are supported
After selecting file, clicking 'begin check' or 'begin identify' button, only waiting code to process corresponding file automatically
Code feedback result, user obtains corresponding function data
Specifically, the checking function code processing flow is as follows:
firstly, the client preprocesses the file
Submitting file to server checking module
Thirdly, judging whether the document is a multi-bill type document or not, if so, firstly cutting bills
Identifying code and num codes on single note
Submitting code and num to national tax inspection system for inspecting authenticity
Returning the result of examination by the national tax examination system
Seventh, the server gathers the data and sends it to the client
The user obtains corresponding data
Ninthly, end of flow
Specifically, the identification function code processing flow is as follows:
firstly, the client preprocesses the file
Submitting the file to the server identification module
Thirdly, judging whether the document is a multi-bill type document or not, if so, firstly cutting bills
Submitting the document to the identification module
The identification module begins to identify the bill field content
Client obtains returned identification data
The user obtains corresponding data
The procedure is finished
The present application also relates to a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a method as described in any of the embodiments.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
Claims (10)
1. A method of validating a ticket, comprising:
when a bill checking command is received, acquiring a bill file to be checked, and identifying bill information of the bill file to be checked;
sending the identified bill information to a bill verification end for checking;
and receiving the checking result sent by the bill verifying end.
2. The method of claim 1, wherein the identifying the ticket information of the ticket file to be inspected further comprises:
preprocessing the acquired bill file to be inspected; the pretreatment comprises at least one of the following modes:
compressing the bill files with the size exceeding a preset size;
prompting uploading errors for other types of files which are not the bill files;
and processing the bill files lower than the page identification requirement.
3. The method of claim 1, wherein the identifying the ticket information of the ticket file to be inspected further comprises:
judging whether the acquired bill file to be inspected is a multi-bill combined file;
when the document is judged to be a multi-bill combined document, cutting the multi-bill combined document into a plurality of single-bill documents; and each single ticket file is used as a ticket file to be checked.
4. The method of claim 1, further comprising:
when receiving an extraction command, extracting the bill information of the selected bill file to be inspected and/or extracting the bill information of the selected inspected bill file for summarizing and outputting;
the ticket information includes at least one of: bill name, bill issuing date, bill type, bill amount, bill issuing unit, bill inspection result, bill issuing unit code, bill code and bill number.
5. The method of claim 1, further comprising:
prompting the checking state of the acquired bill file; the ping state includes at least one of: the inspection is already carried out; invalid parameters, unselected, waiting for inspection;
when the inspection state is inspected, the inspection state further includes an inspection result; the inspection result includes: checking passed, checking failed and checking inconsistent.
6. The method according to claim 1, wherein after receiving the result of the verification sent by the bill validator, the method further comprises: and correspondingly storing the inspection result and the bill file to be inspected.
7. The method of claim 1, further comprising: and checking the duplicate of the acquired bill file to be checked.
8. The method according to claim 7, wherein the duplication checking of the acquired ticket file to be checked comprises at least one of the following ways:
when the MD5 value of the currently acquired ticket file to be checked is judged to be the same as the MD5 value of the acquired ticket file to be checked, judging that the currently acquired ticket to be checked is a repeated ticket file to be checked;
and when the note information of the currently identified note file to be inspected is judged to be the same as the note information of the identified note file to be inspected, judging that the currently identified note to be inspected is the repeated inspection note file.
9. A bill checking apparatus, comprising:
the bill acquisition module is used for acquiring a bill file to be inspected;
the bill identification module is used for identifying bill information of the bill file to be inspected, and the bill information comprises a bill inspection code;
the bill sending module is used for sending the identified bill information to a bill verification end for checking;
and the bill receiving module is used for receiving the checking result sent by the bill verifying end.
10. A computer storage medium on which a computer program is stored, which computer program, when being executed by a processor, carries out the method according to any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010066182.8A CN113139408A (en) | 2020-01-20 | 2020-01-20 | Bill checking method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010066182.8A CN113139408A (en) | 2020-01-20 | 2020-01-20 | Bill checking method, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113139408A true CN113139408A (en) | 2021-07-20 |
Family
ID=76808924
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010066182.8A Pending CN113139408A (en) | 2020-01-20 | 2020-01-20 | Bill checking method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113139408A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113643082A (en) * | 2021-08-30 | 2021-11-12 | 平安国际融资租赁有限公司 | Invoice processing method and device based on artificial intelligence, computer equipment and medium |
| CN114819896A (en) * | 2022-04-22 | 2022-07-29 | 贵州爱信诺航天信息有限公司 | AI-based bill management system, method and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108090084A (en) * | 2016-11-23 | 2018-05-29 | 卓望数码技术（深圳）有限公司 | A kind of knowledge management method and system |
| CN109741517A (en) * | 2018-12-26 | 2019-05-10 | 大象慧云信息技术有限公司 | A kind of invoice checking method, device and system |
| CN109785500A (en) * | 2018-12-28 | 2019-05-21 | 远光软件股份有限公司 | A kind of bill checking method and associated terminal and storage device |
| CN109829769A (en) * | 2019-01-31 | 2019-05-31 | 中国电子科技集团公司第四十三研究所 | A kind of electronic invoice duplicate checking method and system |
| US10423938B1 (en) * | 2015-11-20 | 2019-09-24 | United Services Automobile Association | Identifying negotiable instrument fraud using distributed ledger systems |
| WO2019227577A1 (en) * | 2018-05-31 | 2019-12-05 | 平安科技（深圳）有限公司 | Invoice authenticity verification method, apparatus, computer device, and storage medium |
-
2020
- 2020-01-20 CN CN202010066182.8A patent/CN113139408A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10423938B1 (en) * | 2015-11-20 | 2019-09-24 | United Services Automobile Association | Identifying negotiable instrument fraud using distributed ledger systems |
| CN108090084A (en) * | 2016-11-23 | 2018-05-29 | 卓望数码技术（深圳）有限公司 | A kind of knowledge management method and system |
| WO2019227577A1 (en) * | 2018-05-31 | 2019-12-05 | 平安科技（深圳）有限公司 | Invoice authenticity verification method, apparatus, computer device, and storage medium |
| CN109741517A (en) * | 2018-12-26 | 2019-05-10 | 大象慧云信息技术有限公司 | A kind of invoice checking method, device and system |
| CN109785500A (en) * | 2018-12-28 | 2019-05-21 | 远光软件股份有限公司 | A kind of bill checking method and associated terminal and storage device |
| CN109829769A (en) * | 2019-01-31 | 2019-05-31 | 中国电子科技集团公司第四十三研究所 | A kind of electronic invoice duplicate checking method and system |
Non-Patent Citations (3)
| Title |
|---|
| 刘栋: "人像采集中脏数据筛查方法研究", 《公安信息化》, no. 2, 31 December 2019 (2019-12-31), pages 29 - 32 * |
| 杨帆 等: "《精通图像处理经典算法 MATLAB版》", 30 April 2014, 北京航空航天大学出版社, pages: 301 - 303 * |
| 韩莹 等: "一种在去重备份系统中的源端去重算法", 《科技通报》, vol. 32, no. 1, 31 January 2016 (2016-01-31), pages 145 - 149 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113643082A (en) * | 2021-08-30 | 2021-11-12 | 平安国际融资租赁有限公司 | Invoice processing method and device based on artificial intelligence, computer equipment and medium |
| CN113643082B (en) * | 2021-08-30 | 2024-05-14 | 平安国际融资租赁有限公司 | Invoice processing method and device based on artificial intelligence, computer equipment and medium |
| CN114819896A (en) * | 2022-04-22 | 2022-07-29 | 贵州爱信诺航天信息有限公司 | AI-based bill management system, method and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113139408A (en) | Bill checking method, device and storage medium | |
| CN110851677A (en) | Reimbursement certificate processing method, device, terminal and computer readable storage medium | |
| CN110634223A (en) | Bill verification method and device | |
| CN111091349A (en) | Voucher binding system, method and equipment | |
| CN103970728A (en) | Comparison method and system for file | |
| CN112487982A (en) | Merchant information auditing method, system and storage medium | |
| CN113435439A (en) | Document auditing method and device, storage medium and electronic device | |
| CN110738184B (en) | Early warning information generation method and device for paper certificates | |
| CN114331315A (en) | Social security service processing method and device combining RPA and AI | |
| CN113971664B (en) | SSD-based business auditing method and device, electronic equipment and storage medium | |
| CN111950380A (en) | Bill auditing method and device, electronic equipment and computer-readable storage medium | |
| CN112818653A (en) | Form archiving method and device and warehouse management system | |
| CN106656763A (en) | Method and device for sending offline message | |
| CN116798061A (en) | Bill auditing and identifying method, device, terminal and storage medium | |
| CN116340044A (en) | Fault analysis method, device, equipment and storage medium | |
| CN113286001B (en) | Electronic file uploading method and system | |
| CN115019325A (en) | Service processing method and device based on image recognition and storage medium | |
| KR101654905B1 (en) | Method for eximining genuineness and device for eximining genuineness of the issued document | |
| CN114758753A (en) | Medical image storage system | |
| CN113742287B (en) | Archive data archiving method based on data center, computer device and computer readable storage medium | |
| CN112633251B (en) | Target document acquisition method and device based on text recognition and storage medium | |
| CN113037521A (en) | Method for identifying state of communication equipment, communication system and storage medium | |
| CN114862401B (en) | Payment exception processing method, device, equipment and medium | |
| CN116824604B (en) | Financial data management method and system based on image processing | |
| US20240193606A1 (en) | Control of network systems for automatic assessment and remediation of processing anomalies |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |