CN111340517A - Method, system and related equipment for rapidly inquiring authenticity of invoice - Google Patents
Method, system and related equipment for rapidly inquiring authenticity of invoice Download PDFInfo
- Publication number
- CN111340517A CN111340517A CN202010222980.5A CN202010222980A CN111340517A CN 111340517 A CN111340517 A CN 111340517A CN 202010222980 A CN202010222980 A CN 202010222980A CN 111340517 A CN111340517 A CN 111340517A
- Authority
- CN
- China
- Prior art keywords
- invoice
- target
- elements
- interface
- authenticity
- 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 40
- 238000012545 processing Methods 0.000 claims abstract description 19
- 238000012800 visualization Methods 0.000 claims abstract description 10
- 238000012795 verification Methods 0.000 claims description 33
- 238000004590 computer program Methods 0.000 claims description 5
- 238000007689 inspection Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000012937 correction Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003909 pattern recognition Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/018—Certifying business or products
- G06Q30/0185—Product, service or business identity fraud
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
Abstract
The embodiment of the application discloses a method, a system and related equipment for rapidly inquiring authenticity of invoices, which are used for checking the authenticity of the invoices in batches. The method of the embodiment of the application comprises the following steps: acquiring invoice elements of a target invoice; identifying the type of the target invoice according to the target invoice element; sending the invoice elements of the target invoice to a preset invoice interface according to the type of the target invoice; receiving a query result returned by the preset invoice interface; performing visualization processing on the query result; and outputting the query report of the target invoice.
Description
Technical Field
The embodiment of the application relates to the field of data processing, in particular to a method, a system and related equipment for rapidly inquiring authenticity of an invoice.
Background
The invoice refers to the business certificate issued and collected by all units and individuals in purchasing and selling goods, providing or receiving services and doing other business activities, is the original basis for accounting, and is also the important basis for law enforcement inspection of auditing agencies and tax authorities.
In actual commercial activities, there are some invoices forged by lawless persons, which affect the normal use of the invoices. Thus, there is a need for authenticity verification of invoices, whether by individuals or businesses, to ensure that counterfeit or incorrect invoices are not received. At present, tax departments are provided with relevant website platforms, and can log in the websites to inquire the authenticity of invoices.
However, at present, the relevant websites of the tax department need the user to input various invoice elements of a single invoice at one time, and then the single invoice is queried. When a user has a plurality of invoices and needs to inquire the authenticity, the method is very inconvenient.
Disclosure of Invention
In view of the above problems, a first aspect of the present application provides a method for quickly querying authenticity of an invoice, including:
acquiring invoice elements of a target invoice;
identifying the type of the target invoice according to the target invoice element;
sending the invoice elements of the target invoice to a preset invoice interface according to the type of the target invoice;
receiving a query result returned by the preset invoice interface;
performing visualization processing on the query result;
and outputting the query result.
Optionally, the obtaining of the invoice element of the target invoice includes:
a target table is received, the target table including invoice elements of a target invoice therein.
Optionally, before receiving the face information of the invoice, the method further includes:
receiving a graphic verification code sent by an invoice inquiry interface;
acquiring an identification result of the graphic verification code;
and sending the identification result of the graphic verification code to the invoice inquiry interface.
Optionally, the obtaining of the invoice element of the target invoice includes:
receiving a scanned image of a target invoice;
and identifying the scanned image to obtain the invoice elements of the target invoice.
Optionally, the outputting the query result includes:
and if the query result is true, outputting the ticket face information of the invoice.
The second aspect of the present application provides a system for rapidly querying authenticity of an invoice, the system comprising:
the first acquisition unit is used for acquiring invoice elements of the target invoice;
the identification unit is used for identifying the type of the target invoice according to the target invoice element;
the first sending unit is used for sending the invoice elements of the target invoice to a preset invoice interface according to the type of the target invoice;
the first receiving unit is used for receiving the query result returned by the preset invoice interface;
the processing unit is used for performing visualization processing on the query result;
and the output unit is used for outputting the query result.
Optionally, the first obtaining unit is specifically configured to:
a target table is received, the target table including invoice elements of a target invoice therein.
Optionally, the system further comprises:
the second receiving unit is used for receiving the graphic verification code sent by the invoice inquiry interface;
the second acquisition unit is used for acquiring the identification result of the graphic verification code;
and the second sending unit is used for sending the identification result of the graphic verification code to the invoice inquiry interface.
Optionally, the first obtaining unit is specifically configured to:
receiving a scanned image of a target invoice;
and identifying the scanned image to obtain the invoice elements of the target invoice.
Optionally, the output unit is specifically configured to:
and when the query result is true, outputting the ticket face information of the invoice.
Optionally, the system further comprises:
a first checking unit for checking whether the invoicing date of the target invoice is within the inquireable period;
and the first reminding unit is used for sending out date error reminding when the first checking unit judges that the date error reminding is not the same.
Optionally, the system further comprises:
the second checking unit is used for checking whether the format of the invoice element conforms to the invoicing rule;
and the second reminding unit is used for sending out a format error reminding when the second checking unit judges that the format error reminding is not the format error reminding.
Corresponding to the method of the first aspect, the third aspect of the present application provides a computer readable storage medium having a computer program stored therein, which, when executed by a processor, causes the processor to perform the steps of the method of any one of the first aspect.
A fourth aspect of the application provides a computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the method according to any of the preceding first aspects.
According to the technical scheme, the embodiment of the application has the following advantages: the invoice inquiry method can inquire the authenticity of a plurality of invoices at one time, avoids the complex operation of a user when the user needs to inquire the invoices, reduces the operation amount of the user and improves the inquiry efficiency of the invoices.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flow chart of a method for rapidly querying whether an invoice is true or false in an embodiment of the present application;
fig. 2 is a schematic flow chart of a method for rapidly querying whether an invoice is true or false in an embodiment of the present application;
fig. 3 is a schematic flow chart of a method for rapidly querying whether an invoice is true or false in an embodiment of the present application;
fig. 4 is a schematic structural diagram of a system for rapidly querying authenticity of an invoice in an embodiment of the present application;
fig. 5 is a schematic structural diagram of a computer device in an embodiment of the present application.
Detailed Description
The embodiment of the application provides a method for rapidly inquiring authenticity of invoices, which is used for carrying out batch inquiry on the authenticity of the invoices.
Invoices are important vouchers in economic activities, and especially play a vital role in tax payment. In society, individuals or organizations are forced to receive counterfeit invoices in order to avoid situations where the invoices are forged to gain interest. However, for enterprises or other large organizations, the number of invoices which need to be processed in daily operation is huge, and the verification of the authenticity of the invoices consumes a great deal of energy of accountants. In order to save labor for verifying the invoice, the method for rapidly inquiring the authenticity of the invoice is provided, and accountants can be helped to rapidly verify the authenticity of the invoice.
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention.
Referring to fig. 1, an embodiment of a method for rapidly querying authenticity of an invoice in the present application includes:
101. acquiring invoice elements of a target invoice;
firstly, acquiring invoice factors of a target invoice needing to be distinguished from authenticity. The invoice elements referred by the application refer to the invoice surface information recorded on the invoice, and can comprise the invoice code, the invoice number, the invoice date, the invoice amount, the invoice check code and other invoice surface information of the target invoice. It is understood that the obtained invoice elements may not be limited to the above several kinds of invoice information, and the invoice elements required for querying the invoice may vary according to the invoice interface and the invoice type. The preferred embodiment is to obtain the invoice code, invoice number, invoice date of each target invoice, and obtain one of the invoice amount or invoice check code.
In some specific embodiments, the invoice elements may be stored in advance as an EXCEL or WPS processable form file, and the form file is read to obtain the invoice elements stored therein.
In other embodiments, the invoice elements on the target invoice can also be obtained by scanning the image of the invoice. For example, an image acquisition device is used to scan the whole invoice, and then the invoice elements of the target invoice are acquired through a text recognition mode. If the target invoice is provided with the two-dimensional code, only the two-dimensional code image of the target invoice can be scanned without scanning the whole invoice, so that the efficiency of acquiring invoice elements is improved, and the possibility of character recognition errors is reduced.
102. Identifying a type of the target invoice;
and judging the type of the target invoice according to the input invoice factors. For example, whether the invoice is a value-added tax special invoice or a value-added tax general invoice can be judged through the invoice code. Whether the items such as tax register number of the taxpayer, the amount of free value-added tax, the applicable tax rate, the amount of value-added tax to be paid and the like are included or not can be checked through the bill surface information of the invoice, if the items are included, the invoice is a value-added tax special invoice, and if the items are not included, the invoice is a value-added tax common invoice.
103. Sending the invoice elements of the target invoice to a preset invoice interface;
and sending the corresponding invoice elements to a preset invoice interface according to the type of the inquired target invoice. Due to the limitation of the invoice interface, if the invoice is a value-added tax common invoice, the invoice code, the invoice number, the invoicing date and the invoicing amount of the target invoice are sent to the preset invoice interface; if the invoice is a special value-added tax invoice, the last six digits of the invoice code, the invoice number, the invoice date and the invoice check code of the target invoice are sent to a preset invoice interface.
104. Receiving a query result returned by the preset invoice interface;
after step 103 is executed, the invoice interface returns a corresponding query result according to the invoice elements sent in step 103. If the returned query result is that the ticket is not checked, the target invoice can be identified as a forged invoice. If the returned result is the invoice verification detail, the invoice corresponding to the invoice element really exists. The invoice inspection detail can comprise various invoice surface information such as machine number, tax rate, goods name, price, seller name, taxpayer identification number, address, telephone and inspection times.
105. Performing visualization processing on the query result;
and integrating and displaying the query results acquired in the step 104 so as to facilitate batch reading of the user. In a preferred embodiment, according to the query result of step 103, the target invoice with the query result of non-existent invoice is processed according to the false invoice, and is marked as the false invoice; and (4) temporarily setting the query result as a true invoice, wherein the query result comprises the target invoice of the invoice verification detail.
106. And outputting a query report.
And outputting the authenticity of the target invoice to a display terminal in the form of an inquiry report or outputting the authenticity of the target invoice to a PDF (Portable document Format) or a form file, marking the invoice of which the inquiry result is nonexistent as a counterfeit invoice, and marking the target invoice of which the inquiry result comprises invoice verification details as a true invoice.
Optionally, the invoice inspection details in the query result can be output together, so that the accountants can more visually know the invoice surface information of the invoice, and further accounting and checking are performed. It is understood that the accountant may also preset to output only one or several items of specific ticket information in the query result, for example, only the seller name and the account number of the issuer in the invoice verification detail, so as to facilitate the seller verification by accounting.
In other embodiments, invoices with excessive number of checks may be further marked. The number of times of checking the invoice represents the number of times that the invoice is requested on the invoice interface, and if one invoice is checked for too many times, the invoice may have a counterfeit suspicion and needs manual check by an accountant. It will be appreciated that the number of invoice validations does not fully account for the authenticity of an invoice, and therefore this item of data should be used only as a reference to verify the authenticity of the target invoice.
In another embodiment of the present application, since the invoice interface may have a process of outputting the verification code, which may consume the time of the accountant to input the complicated verification code, a step of automatically inputting the verification code may be added to the method. Referring to fig. 2, the embodiment may include:
201. acquiring invoice elements of a target invoice;
202. identifying a type of the target invoice;
203. sending the invoice elements of the target invoice to a preset invoice interface;
steps 201 to 203 are similar to steps 101 to 103 of the embodiment shown in fig. 1, and are not described again here.
204. Receiving a graphic verification code sent by an invoice inquiry interface;
the verification code may need to be input at an invoice interface of a website, and if the verification code is input every time an invoice is checked, much time is consumed for accountants, so that the graphic verification code sent by the invoice inquiry interface is received by a machine for processing, and the type of the received verification code is usually a graphic containing characters.
205. Acquiring an identification result of the graphic verification code;
the pattern verification code is identified using image recognition techniques. The step can be finished by the system itself, or can be sent to a professional pattern recognition platform of a third party for recognition processing, so as to reduce the local calculation amount.
206. Sending the identification result of the graphic verification code to the invoice inquiry interface;
and sending the identification result of the graphic identification code to an invoice inquiry interface so as to obtain the normal use permission of the invoice inspection interface of the inquiry interface.
207. Receiving a query result returned by the preset invoice interface;
208. performing visualization processing on the query result;
209. and outputting a query report.
Steps 207 to 209 are similar to steps 104 to 106 of the embodiment shown in fig. 1, and are not described again here.
Due to the data volume limitation of the invoice inquiry interface, the invoice which is invoiced for too long time can not be checked through the invoice inquiry interface, and even if the invoice is checked, an inquiry result without the invoice can be returned. If the invoice issued on the same day is queried on the same day, the corresponding result cannot be queried due to the fact that the query interface is not updated timely. However, these situations should not be considered as the query invoice is necessarily a counterfeit invoice, and therefore, it is necessary to check the invoice date before checking the invoice to avoid falsely identifying a true invoice as a counterfeit invoice. In another embodiment of the present application, which is described in detail with reference to fig. 3, the embodiment includes:
301. acquiring invoice elements of a target invoice;
step 301 is similar to step 101 of the embodiment shown in fig. 1, and is not described herein again.
302. Checking whether the invoicing date of the target invoice is within a queryable period; if so, go to step 303; if not, go to step 304.
Checking whether the invoicing date of the target invoice is within one year, wherein the invoicing date is different from the date of the current day. If the above condition is not satisfied, the billing date is determined not to be within the queryable period, and step 303 should be performed. If the billing date is within the queryable period, step 304 is executed, and if not, step 303 is executed.
303. Sending out a date error prompt;
and sending out a date error prompt on a graphical interface, and displaying the invoice elements with the date errors so as to facilitate the correction of accountants.
304. Checking whether the format of the invoice element conforms to the invoicing rule; if so, go to step 305; if not, go to step 306.
Whether the format of the obtained invoice element meets the invoice rules is checked, for example, when the format is obviously wrong, such as the invoice date is 20201331 or the invoice code is 11 digits, the format of the invoice element can be determined not to meet the invoice rules, and the authenticity identification is not needed. If the format of the invoice element accords with the invoicing rule, executing step 306; if not, go to step 305.
305. Sending a format error prompt;
and sending a format error prompt on a graphical interface, and displaying the invoice elements with the wrong format so as to facilitate the correction of accountants.
306. Identifying a type of the target invoice;
307. sending the invoice elements of the target invoice to a preset invoice interface;
308. receiving a query result returned by the preset invoice interface;
309. performing visualization processing on the query result;
310. and outputting a query report.
Steps 306 to 310 are similar to steps 102 to 106 of the embodiment shown in fig. 1, and specific reference may be made to the detailed steps of the embodiment shown in fig. 1, which is not described herein again.
Corresponding to the above invoice querying method, the present application further provides an embodiment of a system for rapidly querying authenticity of an invoice, please refer to fig. 4, where the invoice querying system includes:
a first obtaining unit 401, configured to obtain an invoice element of a target invoice;
an identifying unit 402, which identifies the type of the target invoice according to the target invoice factor;
a first sending unit 403, configured to send an invoice element of the target invoice to a preset invoice interface according to the type of the target invoice;
a first receiving unit 404, configured to receive a query result returned by the preset invoice interface;
a processing unit 405, configured to perform visualization processing on the query result;
an output unit 406, configured to output the query result.
In some specific embodiments, the first obtaining unit 401 is specifically configured to:
a target table is received, the target table including invoice elements of a target invoice therein.
In some specific embodiments, the system further comprises:
a second receiving unit 407, configured to receive the graphic verification code sent by the invoice query interface;
a second obtaining unit 408, configured to obtain an identification result of the pattern verification code;
and a second sending unit 409, configured to send the identification result of the graphical verification code to the invoice querying interface.
In some specific embodiments, the first obtaining unit 401 is specifically configured to:
receiving a scanned image of a target invoice;
and identifying the scanned image to obtain the invoice elements of the target invoice.
In some specific embodiments, the output unit 406 is specifically configured to:
and when the query result is true, outputting the ticket surface information of the target invoice.
In some specific embodiments, the system further comprises:
a first checking unit 410 for checking whether the invoicing date of the target invoice is within the queriable term;
and the first reminding unit 411 is used for sending out date error reminding when the first checking unit judges that the date error reminding is not given.
In some specific embodiments, the system further comprises:
a second checking unit 412, configured to check whether a format of the invoice element conforms to an invoicing rule;
and a second reminding unit 413, configured to send a format error reminding if the second checking unit determines that the format error is not detected.
The present application also provides a computer-readable storage medium having a computer program stored thereon, which when executed by a processor, can implement the steps of:
acquiring invoice elements of a target invoice;
identifying the type of the target invoice according to the target invoice element;
sending the invoice elements of the target invoice to a preset invoice interface according to the type of the target invoice;
receiving a query result returned by the preset invoice interface;
performing visualization processing on the query result;
and outputting the query result.
Optionally, in some embodiments of the present application, the processor may be further configured to implement the following steps: the invoice elements for acquiring the target invoice comprise:
a target table is received, the target table including invoice elements of a target invoice therein.
Optionally, in some embodiments of the present application, the processor may be further configured to implement the following steps: prior to receiving the face information for the invoice, the method further comprises:
receiving a graphic verification code sent by an invoice inquiry interface;
acquiring an identification result of the graphic verification code;
and sending the identification result of the graphic verification code to the invoice inquiry interface.
Optionally, in some embodiments of the present application, the processor may be further configured to implement the following steps: the invoice elements for acquiring the target invoice comprise:
receiving a scanned image of a target invoice;
and identifying the scanned image to obtain the invoice elements of the target invoice.
Optionally, in some embodiments of the present application, the processor may be further configured to implement the following steps: the outputting the query result comprises:
and if the query result is true, outputting the ticket face information of the invoice.
Referring to fig. 5, the computer device 500 may include one or more Central Processing Units (CPUs) 501 and a memory 505, where one or more applications or data are stored in the memory 505. Memory 505 may be volatile storage or persistent storage, among others. The program stored in memory 505 may include one or more modules, each of which may include a sequence of instructions for operating on a computer device. Still further, the central processor 501 may be arranged in communication with the memory 505 to execute a series of instruction operations in the memory 505 on the computer device 500. The computer apparatus 500 may also include one or more power supplies 502, one or more wired or wireless network interfaces 503, one or more input-output interfaces 504, and/or one or more operating systems, such as Windows Server, Mac OSXTM, UnixTM, LinuxTM, FreeBSDTM, etc. The central processing unit 501 may perform corresponding operations in any of the embodiments shown in fig. 1 to fig. 3, which are not described herein again.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other media capable of storing program codes.
Claims (10)
1. A method for rapidly inquiring invoice authenticity is characterized by comprising the following steps:
acquiring invoice elements of a target invoice;
identifying the type of the target invoice according to the target invoice element;
sending the invoice elements of the target invoice to a preset invoice interface according to the type of the target invoice;
receiving a query result returned by the preset invoice interface;
performing visualization processing on the query result;
and outputting the query report of the target invoice.
2. The method for rapidly inquiring invoice authenticity according to claim 1, wherein the acquiring invoice elements of the target invoice comprises:
a target table is received, the target table including invoice elements of a target invoice therein.
3. The method for rapidly inquiring invoice authenticity according to claim 1, wherein before receiving face information of the invoice, the method further comprises:
receiving a graphic verification code sent by an invoice inquiry interface;
acquiring an identification result of the graphic verification code;
and sending the identification result of the graphic verification code to the invoice inquiry interface.
4. The method for rapidly inquiring invoice authenticity according to claim 1, wherein the acquiring invoice elements of the target invoice comprises:
receiving a scanned image of a target invoice;
and identifying the scanned image to obtain the invoice elements of the target invoice.
5. The method for rapidly inquiring invoice authenticity according to claim 1, wherein the outputting the inquiry report of the target invoice comprises:
and if the query result is true, outputting the ticket surface information of the target invoice.
6. The method for rapidly inquiring invoice authenticity according to claim 1, wherein the method further comprises:
checking whether the invoicing date of the target invoice is within a queryable period;
if the check result is negative, sending out a date error prompt.
7. The method for rapidly inquiring invoice authenticity according to claim 1, wherein the method further comprises:
checking whether the format of the invoice element conforms to the invoicing rule;
if not, sending out a format error prompt.
8. A system for rapidly verifying invoice genuineness, comprising:
the first acquisition unit is used for acquiring invoice elements of the target invoice;
the identification unit is used for identifying the type of the target invoice according to the target invoice element;
the first sending unit is used for sending the invoice elements of the target invoice to a preset invoice interface according to the type of the target invoice;
the first receiving unit is used for receiving the query result returned by the preset invoice interface;
the processing unit is used for performing visualization processing on the query result;
and outputting the query result.
9. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 7.
10. A computer arrangement comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010222980.5A CN111340517A (en) | 2020-03-26 | 2020-03-26 | Method, system and related equipment for rapidly inquiring authenticity of invoice |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010222980.5A CN111340517A (en) | 2020-03-26 | 2020-03-26 | Method, system and related equipment for rapidly inquiring authenticity of invoice |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111340517A true CN111340517A (en) | 2020-06-26 |
Family
ID=71182577
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010222980.5A Pending CN111340517A (en) | 2020-03-26 | 2020-03-26 | Method, system and related equipment for rapidly inquiring authenticity of invoice |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111340517A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113554029A (en) * | 2021-09-17 | 2021-10-26 | 北京奇虎科技有限公司 | Bill verification method, device, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103903171A (en) * | 2014-04-02 | 2014-07-02 | 浪潮软件集团有限公司 | Interactive network invoice authenticity checking method |
| CN105205706A (en) * | 2015-09-01 | 2015-12-30 | 深圳市金蝶友商电子商务服务有限公司 | Invoice query method and device |
| CN108255442A (en) * | 2018-01-15 | 2018-07-06 | 任海鹏 | A kind of electronic invoice examination print system and method |
| CN109741517A (en) * | 2018-12-26 | 2019-05-10 | 大象慧云信息技术有限公司 | A kind of invoice checking method, device and system |
| CN110111165A (en) * | 2019-05-13 | 2019-08-09 | 重庆天蓬网络有限公司 | True from false of bills checking method, system, medium and electronic equipment |
-
2020
- 2020-03-26 CN CN202010222980.5A patent/CN111340517A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103903171A (en) * | 2014-04-02 | 2014-07-02 | 浪潮软件集团有限公司 | Interactive network invoice authenticity checking method |
| CN105205706A (en) * | 2015-09-01 | 2015-12-30 | 深圳市金蝶友商电子商务服务有限公司 | Invoice query method and device |
| CN108255442A (en) * | 2018-01-15 | 2018-07-06 | 任海鹏 | A kind of electronic invoice examination print system and method |
| CN109741517A (en) * | 2018-12-26 | 2019-05-10 | 大象慧云信息技术有限公司 | A kind of invoice checking method, device and system |
| CN110111165A (en) * | 2019-05-13 | 2019-08-09 | 重庆天蓬网络有限公司 | True from false of bills checking method, system, medium and electronic equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113554029A (en) * | 2021-09-17 | 2021-10-26 | 北京奇虎科技有限公司 | Bill verification method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11663654B2 (en) | System and method for processing transaction records for users | |
| US20150287005A1 (en) | Bar coded monetary transaction system and method | |
| CN107609922A (en) | A kind of quick obtaining Merchant name and duty paragraph and the methods, devices and systems drawn a bill | |
| WO2020179055A1 (en) | Voucher analysis device, accounting system, voucher analysis method, and voucher analysis program | |
| CN106056418A (en) | Invoice submission method, device and system | |
| CN111127010A (en) | Transaction bill checking method, device, equipment and storage medium | |
| CN109214362B (en) | Document processing method and related equipment | |
| CN111145031B (en) | Insurance business customization method, device and system | |
| CN111784423B (en) | Invoice matching method and device, electronic equipment and storage medium | |
| CN111340517A (en) | Method, system and related equipment for rapidly inquiring authenticity of invoice | |
| CN111429135A (en) | Case management method, system and storage medium based on charge notice | |
| CN111311388A (en) | Invoice management system | |
| TW201506826A (en) | Method and system for processing issued transaction electronic certificate between paying party and receiving party | |
| CN116503184A (en) | Financial tax ticketing integrated management platform | |
| CN113807901A (en) | Electronic invoice detection method, terminal equipment and storage medium | |
| JP6612962B1 (en) | Electronic data determination system, electronic data determination device, electronic data determination method, electronic data determination program | |
| US20170185832A1 (en) | System and method for verifying extraction of multiple document images from an electronic document | |
| CN111784422A (en) | Data management method, device, storage medium and electronic equipment | |
| JP2011227787A (en) | Accounting transaction information reading device | |
| CN111445330A (en) | Account checking method and device | |
| EP3847608A1 (en) | A system and process for the verification of data | |
| KR20040052278A (en) | System and Method for Confirming Goods by Using Unique Identification Code | |
| CN113689248A (en) | Method for accurately inputting value-added tax invoice information, electronic equipment and storage medium | |
| JP6835382B1 (en) | Electronic data judgment system, electronic data judgment device, electronic data judgment method, electronic data judgment program | |
| KR20080011149A (en) | System for confirming goods by using unique identification code |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200626 |