CN111143512A - Bill information detection method and device and computer equipment - Google Patents
Bill information detection method and device and computer equipment Download PDFInfo
- Publication number
- CN111143512A CN111143512A CN201911356082.2A CN201911356082A CN111143512A CN 111143512 A CN111143512 A CN 111143512A CN 201911356082 A CN201911356082 A CN 201911356082A CN 111143512 A CN111143512 A CN 111143512A
- Authority
- CN
- China
- Prior art keywords
- information
- bill
- type
- protocol
- content
- 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
- 238000001514 detection method Methods 0.000 title claims abstract description 95
- 238000004458 analytical method Methods 0.000 claims abstract description 26
- 238000000034 method Methods 0.000 claims description 33
- 238000004590 computer program Methods 0.000 claims description 14
- 230000000694 effects Effects 0.000 abstract description 4
- 238000012550 audit Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 9
- 230000008859 change Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000007726 management method Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
- G06F16/334—Query execution
- G06F16/3344—Query execution using natural language analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/36—Creation of semantic tools, e.g. ontology or thesauri
- G06F16/367—Ontology
-
- 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/04—Billing or invoicing
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/10—Tax strategies
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/123—Tax preparation or submission
Abstract
The invention relates to a bill information detection method, a device, computer equipment and a storage medium, which are characterized in that the bill information of a bill to be detected and the file information of a protocol file corresponding to the bill information are obtained, semantic analysis is carried out on the protocol content in the file information to obtain a service range corresponding to the protocol content, a target bill type corresponding to the service range is determined according to a knowledge map, when the bill type of the bill to be detected is consistent with the target bill type and is a type corresponding to the identity of a billing party, whether the information of the billing party corresponds to the information of a signing party in the file information or not and whether the name of an item in the bill corresponds to the protocol content or not are judged, and when the information of the billing party corresponds to the information of the signing party and the name of the item corresponds to the protocol content, the bill information can be determined to pass detection. The scheme can be combined with the relevant information in the protocol file and the bill to judge whether the bill passes the detection or not, and the effect of improving the comprehensiveness of detecting the bill information is achieved.
Description
Technical Field
The invention relates to the technical field of internet information, in particular to a bill information detection method, a bill information detection device, computer equipment and a computer readable storage medium.
Background
The continuous development of economy drives the development of a plurality of enterprises, business trips are usually required between the enterprises, and a plurality of bills are usually generated between the enterprises, so in the business trip management affairs between the enterprises, the bill information is usually required to be detected to judge whether the bill information conforms to the regulations.
Therefore, the traditional bill information detection method has the defect of incomplete detection.
Disclosure of Invention
Based on this, it is necessary to provide a method, an apparatus, a computer device and a computer readable storage medium for detecting bill information, aiming at the technical problem of incomplete detection of the conventional technology.
A bill information detection method comprises the following steps:
acquiring bill information of a bill to be detected; the bill information comprises bill types, information of invoices making parties and project names;
acquiring file information of a protocol file corresponding to the bill information of the bill to be detected; the file information comprises protocol subscriber information and protocol content;
performing semantic analysis on the protocol content to obtain a service range corresponding to the protocol content; determining the type of the target bill corresponding to the service range according to a preset knowledge graph; the knowledge graph comprises corresponding relations between different service ranges and bill types;
if the bill type is consistent with the target bill type and the bill type is the type corresponding to the identity of the invoicer, judging whether the information of the invoicer corresponds to the information of the agreement endorser and whether the project name corresponds to the agreement content;
and when the invoicing party information corresponds to the agreement signing party information and the project name corresponds to the agreement content, determining that the billing information passes the detection.
In one embodiment, further comprising:
judging whether the bill type is the type corresponding to the identity of the invoicing party or not according to the information of the invoicing party and the knowledge graph; the knowledge graph also comprises the corresponding relation between the identity of the invoicing party and the bill type.
In one embodiment, further comprising:
if the bill type is not consistent with the target bill type, or if the bill type is not the type corresponding to the identity of the invoicing party, determining that the bill information of the bill to be detected does not pass the detection;
adding a bill type error mark into the bill to be detected, and outputting first prompt information that the bill type of the bill to be detected does not pass the detection;
and/or the presence of a gas in the gas,
when at least one of the invoicer information, the agreement endorser information and the project name does not correspond to the agreement content, determining that the invoice information does not pass the detection; adding a bill information error mark into the bill to be detected, and outputting second prompt information that the bill information of the bill to be detected does not pass the detection.
In one embodiment, before acquiring the ticket information of the ticket to be detected, the method further includes:
acquiring bill information of a bill which passes the detection;
acquiring file information of the protocol file corresponding to the bill which passes the detection as reference file information;
acquiring a service range corresponding to the invoicing party in the detected bill information as a reference service range according to the reference file information;
associating the bill type in the detected bill information with the reference service range to serve as a first corresponding relation;
associating the identity of the invoicer in the detected bill information with the bill type in the detected bill information to serve as a second corresponding relation;
and obtaining the knowledge graph according to the first corresponding relation and the second corresponding relation.
In an embodiment, after obtaining the knowledge graph according to the first corresponding relationship and the second corresponding relationship, the method further includes:
when the protocol content in the reference file information is changed, acquiring a changed service range corresponding to the changed protocol content;
and updating the first corresponding relation in the knowledge graph according to the changed service range to obtain an updated knowledge graph.
In one embodiment, the file information further includes: the position of the protocol subscriber and the implementation position of the protocol content;
the semantic analysis of the protocol content to obtain the service range corresponding to the protocol content includes:
performing semantic analysis on the protocol content to obtain the position of a corresponding protocol subscriber and the implementation position of the protocol content;
and performing semantic analysis according to the position of the protocol subscriber, the implementation position of the protocol content and the protocol content, and determining a service range corresponding to the protocol content.
In one embodiment, the agreement subscriber comprises a plurality of agreement subscribers; when the invoicing party information corresponds to the agreement signing party information and the project name corresponds to the agreement content, determining that the billing information passes the detection comprises the following steps:
and when the invoicing party information corresponds to at least one agreement signing party information and the project name corresponds to the agreement content, determining that the billing information passes the detection.
A ticket information detection apparatus comprising:
the acquisition module is used for acquiring the bill information of the bill to be detected; the bill information comprises bill types, information of invoices making parties and project names; acquiring file information of a protocol file corresponding to the bill information of the bill to be detected; the file information comprises protocol subscriber information and protocol content;
the analysis module is used for carrying out semantic analysis on the protocol content to obtain a service range corresponding to the protocol content; determining the type of the target bill corresponding to the service range according to a preset knowledge graph; the knowledge graph comprises corresponding relations between different service ranges and bill types;
the first detection module is used for judging whether the invoicing party information corresponds to the agreement signing party information or not and whether the project name corresponds to the agreement content or not if the ticket type is consistent with the target ticket type and the ticket type is the type corresponding to the identity of the invoicing party;
and the second detection module is used for determining that the ticket information passes the detection when the ticket issuing party information corresponds to the agreement signing party information and the project name corresponds to the agreement content.
A computer device comprising a processor and a memory, the memory storing a computer program, the processor implementing the ticket information detection method as described above when executing the computer program.
A computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements a ticket information detection method as described above.
According to the bill information detection method, the bill information detection device, the computer equipment and the storage medium, through acquiring the bill information of the bill to be detected and the file information of the protocol file corresponding to the bill information, semantic analysis is conducted on the protocol content in the file information to obtain the service range corresponding to the protocol content, the target bill type corresponding to the service range is determined according to the knowledge map, when the bill type of the bill to be detected is consistent with the target bill type and is the type corresponding to the identity of the invoicing party, whether the information of the invoicing party is corresponding to the information of the signing party in the file information or not and whether the item name in the bill is corresponding to the protocol content or not are judged, and when the information of the invoicing party is corresponding to the information of the signing party and the item name is corresponding to the protocol content, the bill information can be determined to pass detection. Compared with the traditional method for comparing the bills which pass the historical examination and verification, the method and the device can be used for judging whether the bills pass the detection or not by combining the protocol files and the related information in the bills, so that the effect of improving the comprehensiveness of detecting the bill information is realized.
Drawings
FIG. 1 is a diagram of an exemplary scenario for detecting billing information;
FIG. 2 is a schematic flow chart diagram of a method for detecting ticket information in one embodiment;
FIG. 3 is a schematic flow chart of a method for detecting ticket information in another embodiment;
FIG. 4 is a block diagram showing the structure of a bill information detecting apparatus according to an embodiment;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
It should be noted that the terms "first \ second \ third" related to the embodiments of the present invention only distinguish similar objects, and do not represent a specific ordering for the objects, and it should be understood that "first \ second \ third" may exchange a specific order or sequence when allowed. It should be understood that the terms first, second, and third, as used herein, are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in other sequences than those illustrated or otherwise described herein.
The method for detecting the bill information provided by the invention can be applied to the application scene shown in fig. 1, and fig. 1 is an application scene diagram of the method for detecting the bill information in one embodiment. The terminal 102 may include at least one database, a preset knowledge map may be stored in the database, and the terminal 102 may obtain the ticket information and the protocol file information of the ticket that has passed the audit from the database, and compare the ticket information with the ticket information of the ticket to be audited. In one embodiment, as shown in FIG. 1, a server 104 is included, and the terminal 102 communicates with the server 104 over a network. The server 104 may include at least one database, which may include the ticket information and the protocol content, and may further include the above-mentioned knowledge map, the database may store the ticket information that has passed the audit, and the terminal 102 may obtain the ticket information that has passed the audit and the related protocol content information from the server 104, and compare and audit with the ticket information of the ticket to be audited. The terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, and tablet computers, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In an embodiment, a method for detecting ticket information is provided, referring to fig. 2, fig. 2 is a schematic flowchart of the method for detecting ticket information in an embodiment, which is described by taking the method as an example applied to the terminal in fig. 1, and the method for detecting ticket information may include the following steps:
step S101, acquiring bill information of a bill to be detected; the ticket information includes a ticket type, biller information, and a project name.
The bill to be detected may be a bill which is not yet detected, may be a negotiable securities issued by a drawer legally and issued by oneself or instructed by others to unconditionally pay a certain amount of money to a payee or a drawer, and may be various negotiable securities and vouchers, such as stocks, enterprise bonds, invoices, bills, drafts, money orders, checks and the like. The bill to be detected can include various bill information, for example, the bill information can include the bill type, the information of the invoicer, the project name and the like, and the bill information can also include the information of the bill value, the bill number, the information of the invoicer and the like corresponding to the project name. There may be one or more item names. Specifically, the bill may be an invoice or a receipt, and when the bill is an invoice, the invoice may include, but is not limited to, an invoice number, an invoice type, information of a receiver, an invoice item, an amount, information of a drawer, and the like. The receipt may include, but is not limited to, receipt type, payee information, billing item, amount, drawer information, and the like. The information of the drawer can include the name, registration number, tax number and other information of the drawer, and the information of the drawer can include the name, registration number, tax number and other information of the drawer. The terminal 102 may obtain the information in the ticket by receiving a scanned file or receiving an electronic part, etc.
Step S102, acquiring file information of a protocol file corresponding to the bill information of the bill to be detected; the file information includes protocol subscriber information and protocol contents.
The protocol file includes a broad protocol file and a narrow protocol file, and the broad protocol file may be a 'contract' type document commonly used by a social group or an individual to process various social relationships and transactions, including a contract, an agreement, a treaty, an agreement, a joint declaration, a joint statement, a statement and the like. The narrow agreement document can be a contractual document with economic or other relation, which is formed after a country, a political party, an enterprise, a group or an individual negotiates or co-negotiates about a certain problem and obtains a consensus. The protocol file can correspond to the bill to be detected, and the file information in the protocol file can also correspond to the bill information in the bill to be detected. The file information in the protocol file may include information such as protocol subscriber information and protocol contents, wherein there may be two or more protocol subscribers. Specifically, the agreement document may be a contract, and the contract may include information on names of parties to whom the contract is made, information on the contents or products of the cooperation, locations of the institutions of the cooperation, locations where the cooperation occurs, and the like. The contracting party information may be name information of each party under contract, and the agreement content may be the cooperation content or the product information. The terminal 102 obtains the file information of the protocol file by receiving a scanned file or receiving an electronic part.
Step S103, performing semantic analysis on the protocol content to obtain a service range corresponding to the protocol content; determining a target bill type corresponding to a service range according to a preset knowledge graph; the knowledge graph comprises corresponding relations between different service ranges and bill types.
Different service ranges can be determined by different protocol contents, and the different service ranges can correspond to different target bill types. The knowledge map can be a management business knowledge map, and the knowledge map can comprise corresponding relations between different business ranges and bill types. The terminal 102 may perform semantic analysis on the protocol content to obtain a service range corresponding to the protocol content, and may also determine a target bill type corresponding to the service range according to a preset knowledge graph. Specifically, when the agreement is contract, the terminal 102 may perform semantic analysis according to the content of the contract to determine a reasonable service range corresponding to the contract, and then determine a target bill type corresponding to the service range through a preset knowledge graph, for example, the bill type corresponding to the business service may be a regular tax control invoice meeting tax requirements, and the bill type corresponding to the non-business service may be a receipt.
And step S104, if the bill type is consistent with the target bill type and the bill type is the type corresponding to the identity of the invoicer, judging whether the information of the invoicer corresponds to the information of the protocol endorser and whether the project name corresponds to the protocol content.
The ticket type may be the ticket type of the ticket to be audited, the terminal 102 may compare the target ticket type determined according to the service range with the audit ticket, and when the ticket type of the ticket to be audited is consistent with the target ticket type and the ticket type is the type corresponding to the identity of the invoicing party, the next determination may be performed. Specifically, the ticket type may be an invoice or a receipt, when the service scope determined from the agreement content in the above step is an operating service, the corresponding target ticket type may be an invoice, and when the service scope is a non-operating service, the corresponding target ticket type may be a receipt or an invoice. In addition, the identity information of the invoicing parties is different, and the corresponding bill types are also different. In one embodiment, further comprising: judging whether the bill type is the type corresponding to the identity of the invoicing party or not according to the information of the invoicing party and the knowledge graph; the knowledge graph also comprises the corresponding relation between the identity of the invoicing party and the bill type. In this embodiment, the knowledge graph may further include a corresponding relationship between the identity of the invoicing party and the type of the ticket, and the terminal 102 may determine, according to the information of the invoicing party, whether the type of the ticket is a type corresponding to the identity of the invoicing party in the knowledge graph. Specifically, the invoicer identity may be a utility or a non-utility, and the corresponding ticket type may be a receipt or an invoice when the invoicer identity is a utility, and the corresponding ticket type may be an invoice when the invoicer identity is a non-utility. Through the embodiment, the terminal 102 can determine whether the bill type conforms to the identity information of the invoicer according to the knowledge graph, so that the validity of the bill to be detected can be detected more comprehensively. When the bill type of the bill to be audited is the invoice and the target bill type corresponding to the service range comprises the invoice, determining that the bill type of the bill to be audited meets the requirement; and when the type of the bill to be audited is a receipt and the identity of the invoicing party is the cause unit, determining that the type of the bill to be audited meets the requirement. When determining that the ticket type of the ticket to be audited is consistent with the target ticket type and the ticket type is the type corresponding to the identity of the invoicer, the terminal 102 may determine whether the information of the invoicer corresponds to the information of the agreement endorser, and may also determine whether the project name corresponds to the agreement content.
And step S105, when the invoicing party information corresponds to the agreement signing party information and the project name corresponds to the agreement content, determining that the billing information passes the detection.
The information of the agreement signing party can be the name of the agreement signing party, the information of the invoicing party can be the name of the invoicing party, and the project name can be the project name in the bill to be audited. The terminal 102 may determine whether the invoicing party information and the agreement signing party information in the to-be-checked bill correspond to each other, and whether the project name and the agreement content correspond to each other after determining that the bill type meets the requirement, and may determine that the bill information in the to-be-checked bill passes the detection when the invoicing party information and the agreement signing party information correspond to each other and the project name and the agreement content correspond to each other. Specifically, the type of the ticket may be an invoice or a receipt, when the type of the ticket is an invoice, the item name corresponding to the invoice may be an administrative service name, such as an advertisement, a promotion, a training and the like, and when the type of the ticket is a receipt, the item name corresponding to the receipt may be a non-administrative service name. When the agreement document is a contract, the terminal 102 may compare the invoicing party information in the invoice to be audited with the contracting party information in the contract, compare the project name in the invoice with the cooperation content in the contract, and when the invoicing party information in the invoice is consistent with the contracting party information in the contract and the project name in the invoice and the cooperation content in the contract are within the range, the terminal 102 may determine that the invoice passes the detection. The terminal 102 may also compare the biller information in the receipt to be audited with the endorser information in the contract, compare the project name in the receipt with the collaborative content in the contract, and when the biller information in the data and the endorser information in the contract are consistent and the project name in the receipt and the collaborative content in the contract are within range, the terminal 102 may determine that the invoice passes the detection.
In one embodiment, further comprising: if the bill type is not consistent with the target bill type or if the bill type is not the type corresponding to the identity of the invoicer, determining that the bill information of the bill to be detected does not pass the detection; adding a bill type error mark into the bill to be detected, and outputting first prompt information that the bill type of the bill to be detected does not pass the detection.
In this embodiment, the terminal 102 may determine that the ticket information of the ticket to be detected does not pass the detection when the ticket type is determined to be inconsistent with the target ticket type or the ticket type is not a type corresponding to the identity of the invoicing party. Specifically, when the type of the ticket to be detected is a receipt, but the item name in the ticket to be detected is an administrative business, and is different from the target ticket type determined according to the business range, it may be determined that the receipt does not pass the detection; in the knowledge map, the identity of the invoicing party corresponding to the receipt can be an institution, and when the type of the to-be-detected receipt is the receipt, but the identity of the invoicing party is not the institution, the to-be-detected receipt can be determined not to pass the detection. After determining that the bill to be detected does not pass the detection, the terminal 102 may add an error mark indicating that the bill type is wrong to the bill to be detected, and may output a first prompt message indicating that the bill type of the bill to be detected does not pass the detection. The form of the error flag is not limited, and the first prompt information output by the terminal 102 may be output to a device of a relevant auditor, for example, a device such as a mobile phone or a computer, and the relevant auditor may process the ticket according to the first prompt information. Through the embodiment, the terminal 102 can output the error information in time when detecting that the bill type is failed, so that the related auditors can audit the bill which is not passed through the detection more quickly, and the efficiency of detecting the bill information is improved.
In one embodiment, when the invoicer information and at least one of the agreement endorsement information, the project name and the agreement content do not correspond, determining that the invoicer information does not pass the detection; and adding a bill information error mark to the bill to be detected, and outputting second prompt information that the bill information of the bill to be detected does not pass the detection.
In this embodiment, when detecting that the information of the invoicing party is inconsistent with the information of the agreement signing party, or detecting that the item name is inconsistent with the content of the agreement, the terminal 102 may determine that the information of the invoicing party does not pass the detection. Specifically, when the terminal 102 detects that the information of the invoicers in the ticket is not in the information of the agreement endorsers, it may be determined that the ticket does not pass the detection; when the terminal 102 detects that any item name of the ticket is not in the protocol content, it may be determined that the ticket does not pass the detection. The agreement may be a contract, the agreement subscriber information may be a contract partner, and the agreement content may be a partner content. When detecting that the ticket does not meet the requirement due to the information of the issuing party or the name of the item, the terminal 102 may add a ticket information error flag to the ticket, where the error cause may include a specific error reason of the ticket, such as that the information of the issuing party does not meet the requirement or that the name of the item does not meet the requirement, and the terminal 102 may further generate second prompt information according to the error information, and may further send the second prompt information to a device of a related auditor, such as a mobile phone or a computer, so that the related auditor processes the ticket that does not pass the detection according to the second prompt information. The second prompt message may include information such as a flag that the ticket fails to pass detection and a specific error type. Through the embodiment, when the bill information error is detected, the error information can be output in time, so that the related auditors can audit the bills which do not pass the detection more quickly, and the efficiency of detecting the bill information is improved.
The bill information detection method obtains the bill information of the bill to be detected and the file information of the protocol file corresponding to the bill information, semantic analysis is carried out on the protocol content in the file information to obtain a service range corresponding to the protocol content, determining the type of the target bill corresponding to the service range according to the knowledge map, when the bill type of the bill to be detected is consistent with the type of the target bill, and is the type corresponding to the identity of the invoicing party, whether the information of the invoicing party corresponds to the information of the signing party in the file information or not, whether the project name and the protocol content in the bill correspond or not is judged, when the information of the invoicer corresponds to the information of the endorser, and the item name corresponds to the protocol content, it can be determined that the ticket information passes the detection, and when the error of the ticket type is detected, or when the bill information is wrong, the related error information can be output in time, and related auditors are prompted to process the bills which do not pass the detection. Compared with the traditional method for comparing the bills which pass the audit with the history, the scheme can judge whether the bills pass the audit or not by combining the protocol files and the related information in the bills, thereby realizing the effect of improving the comprehensiveness of detecting the bill information.
In one embodiment, before acquiring the ticket information of the ticket to be detected, the method further comprises the following steps: acquiring bill information of a bill which passes the detection; acquiring file information of a protocol file corresponding to the detected bill as reference file information; acquiring a service range corresponding to the invoicing party in the detected bill information as a reference service range according to the reference file information; associating the bill type in the detected bill information with the reference service range to serve as a first corresponding relation; associating the identity of the invoicer in the detected bill information with the bill type in the detected bill information to serve as a second corresponding relation; and obtaining the knowledge graph according to the first corresponding relation and the second corresponding relation.
In this embodiment, the detected ticket may be a ticket meeting the above-mentioned ticket information detection requirement, and the ticket information of the detected ticket may be stored in a database, such as a financial database. The database may further store file information of a plurality of protocol files, and the terminal 102 may determine a service range of the protocol file according to the protocol content in the file information. The terminal 102 may obtain the ticket information of the ticket that has passed the detection from the database, and according to the information of the biller in the ticket information of the ticket that has passed the detection, may obtain the protocol file of which the information of the signer includes the information of the biller from the database, and then may determine, according to the protocol content in the obtained protocol file, and according to the protocol content, a service range corresponding to the protocol file, so that a reference service range corresponding to the ticket information of the ticket that has passed the ticket may be determined according to the service range. Specifically, the terminal 102 may associate the ticket type in the acquired ticket that has passed the detection with the acquired corresponding service range, to obtain a corresponding relationship between the ticket type and the service range, which is used as the first corresponding relationship. Specifically, the type of the bill may include an invoice and a receipt, the business scope may include an operational business and a non-operational business, and the like, the terminal 102 may correspond the invoice to the operational business, the invoice to the non-operational business, and the receipt to the non-operational business, and the terminal 102 may determine whether the business belongs to the operational business or the non-operational business according to the name of the item in the bill. For example, when the terminal 102 detects that the item name in the invoice belongs to an operating service or a non-operating service, it may be determined that the type of the bill corresponding to the item name is reasonable; when the terminal 102 detects that the item name in the receipt belongs to the business, it can be determined that the type of the ticket corresponding to the item name is not reasonable. In addition, the identity information of the invoicer is determined by the information of the invoicer in the detected ticket, the identity type of the invoicer can comprise an institution, a non-institution and the like, and the terminal 102 can further associate the identity corresponding to the information of the invoicer in the detected ticket information with the ticket type to obtain the corresponding relationship between the identity of the invoicer and the ticket type as the second corresponding relationship. For example, the ticket type may include an invoice, a receipt, and the like, the ticket type corresponding to the above-mentioned utility unit may be the receipt and the invoice, the ticket type corresponding to the above-mentioned non-utility unit may be the invoice, and when the terminal 102 detects that the identity of the invoicer in the receipt to be audited is the non-utility unit, the ticket type of the receipt may be determined to be wrong. In addition, the terminal 102 may obtain the knowledge graph according to the correspondence between the ticket type and the service range and the correspondence between the identity of the invoicing party and the ticket type, and the knowledge graph may further include accumulated management service data. The knowledge map can be used for judging whether the bill type of the bill to be audited meets the requirement of the project name in the bill or not, and whether the bill type of the bill to be audited corresponds to the identity of the invoicing party in the bill or not. Through the embodiment, the terminal 102 can associate the bill type meeting the requirement with the service range and associate the identity of the invoicing party with the bill type according to the bill information in the detected bill, so that when the terminal 102 detects the bill information, whether the bill information meets the requirement or not can be quickly judged through the knowledge graph, and the bill information detection efficiency is improved.
In one embodiment, after obtaining the knowledge graph according to the first corresponding relationship and the second corresponding relationship, the method further includes: when the protocol content in the reference file information is changed, acquiring a changed service range corresponding to the changed protocol content; and updating the first corresponding relation in the knowledge graph according to the changed service range to obtain the updated knowledge graph.
In this embodiment, the protocol content in the protocol file may be changed, for example, the protocol content may be increased or decreased, and the change of the protocol content may affect the judgment of the validity of the item name in the ticket information. When detecting the change of the protocol content, the terminal 102 obtains a service range corresponding to the protocol content according to the changed protocol content, for example, a non-business service or a business service, replaces the service range before the change with the service range after the change in the knowledge graph, and can update the first corresponding relationship by corresponding the bill type originally corresponding to the service range before the change in the knowledge graph to obtain the updated knowledge graph. The protocol change content can be obtained by periodically detecting the online protocol content or manually uploading the protocol change content. Through the embodiment, the terminal 102 can update the knowledge graph in time when the protocol content of the protocol file changes, so that when the bill information is detected through the knowledge graph, the timeliness of the information in the knowledge graph is ensured, and the effectiveness of bill information detection is improved.
In one embodiment, the file information further includes: the position of the protocol subscriber and the implementation position of the protocol content; performing semantic analysis on the protocol content to obtain a service range corresponding to the protocol content, wherein the service range comprises the following steps: performing semantic analysis on the protocol content to obtain the position of the corresponding protocol subscriber and the implementation position of the protocol content; and performing semantic analysis according to the position of the protocol subscriber, the implementation position of the protocol content and the protocol content, and determining a service range corresponding to the protocol content.
In this embodiment, the position of the agreement signing party may be a work place of the signing party in the agreement document, the implementation position of the agreement content may be position information of the agreement content executing the agreement document, for example, the agreement document may be a contract, the position of the agreement signing party may be a location of an organization of the signing party in the contract, and the implementation position of the agreement content may be a labor place, specifically, a location of a project. The terminal 102 may perform semantic analysis according to the position of the protocol subscriber, the implementation position of the protocol content, and determine a service range corresponding to the protocol content. Specifically, the terminal 102 may determine, through semantic analysis, a service range corresponding to the protocol content in the protocol file from at least one of a property of a location where the protocol subscriber is located, a property of a location where the protocol content is implemented, and a protocol content, and may determine, for example, whether the service range is an operational service or a non-operational service according to whether the location where the protocol content is implemented is a school or an office building. Through the embodiment, the terminal 102 can judge the service range corresponding to the protocol content according to various conditions, so that the reliability of bill information detection is improved.
In one embodiment, the agreement subscriber comprises a plurality of agreement subscribers; when the information of the invoicing party corresponds to the information of the protocol signing party and the project name corresponds to the protocol content, determining that the information of the invoicing party passes the detection, and the method comprises the following steps: and when the information of the invoicers corresponds to the information of at least one agreement signing party and the item name corresponds to the agreement content, determining that the information of the invoicers passes the detection.
In this embodiment, the agreement endorser may include a plurality of agreement endorsers, and the terminal 102 may determine that the ticket information passes the detection when the ticket issuing information corresponds to at least one of the endorser information and the item name corresponds to the agreement content in the ticket information detection. Specifically, the agreement may be a contract, there may be a plurality of partners in the contract, and when the terminal 102 detects that the information of the invoicing party corresponds to any one partner, and the item name in the ticket and the content of the contract both correspond, it may be determined that the ticket information of the ticket passes the detection. Through the embodiment, when a plurality of protocol subscribers exist, the terminal 102 can determine that the information of the invoicers in the bill meets the requirements only by detecting the correspondence between the information of the invoicers and at least one protocol subscriber, so that the detection calculated amount is reduced, and the bill information detection efficiency is improved.
In one embodiment, as shown in fig. 3, fig. 3 is a schematic flow chart of a method for detecting ticket information in another embodiment. In this embodiment, the terminal 102 may obtain information of an invoice or a receipt and contract information, where the invoice or receipt information may include information of a biller, a collector, a project name, an amount of money, and the like of the invoice or the receipt, and the contract information may include information of a contract signing party, a cooperation content, a location of a cooperation party mechanism, a cooperation place, and the like; the terminal 102 can judge whether the bill belongs to an invoice or a receipt, when the bill belongs to the invoice according to the type, whether the information of the invoicing party and the contract signing party in the invoice is in accordance or not, whether the information of the invoicing item and the contract content is in accordance or not can be judged, and when the information is in accordance, the invoice can be judged to pass the detection; when the bill type is other than the receipt, the error of the bill type can be judged, and corresponding prompt information can be output; when the bill type is a professional receipt, whether the invoicing party in the receipt is a cause unit or not can be detected, and if not, the fact that the bill type is wrong can be prompted; if yes, semantic analysis can be carried out on contract information comprising the invoicing party to obtain the operation range of the invoicing party, and whether the operation range belongs to the operational service or the non-operational service can be judged through the operation range knowledge graph; when the terminal 102 detects that the item content in the receipt does not belong to the operation range of the business unit, the error information of the bill type can be prompted; when the terminal 102 detects that the item content in the receipt belongs to the operation range of the business unit, whether the information of the invoicing party and the contract signing party in the receipt is in accordance or not, whether the information of the invoicing item and the contract content is in accordance or not can be judged, and when the information is in accordance, the invoice can be judged to pass the detection; otherwise, the bill non-compliance information can be prompted. Through the embodiment, the terminal 102 can determine whether the bill passes the detection or not by combining the contract content and various information in the bill, thereby realizing the effect of improving the comprehensiveness of detecting the bill information.
In an embodiment, there is provided a bill information detecting apparatus, and referring to fig. 4, fig. 4 is a block diagram illustrating a structure of the bill information detecting apparatus in an embodiment, the bill information detecting apparatus may include:
the acquiring module 400 is used for acquiring the bill information of the bill to be detected; the bill information comprises bill types, information of invoices making parties and project names; acquiring file information of a protocol file corresponding to the bill information of the bill to be detected; the file information comprises protocol subscriber information and protocol content.
An analysis module 402, configured to perform semantic analysis on the protocol content to obtain a service range corresponding to the protocol content; determining the type of the target bill corresponding to the service range according to a preset knowledge graph; the knowledge graph comprises corresponding relations between different service ranges and bill types.
A first detecting module 404, configured to determine whether the invoice information corresponds to the agreement signer information, and whether the project name corresponds to the agreement content, if the invoice type is consistent with the target invoice type and the invoice type is a type corresponding to the identity of the invoker.
A second detecting module 406, configured to determine that the ticket information passes detection when the ticket issuer information corresponds to the agreement signer information and the item name corresponds to the agreement content.
The bill information detection device of the present invention corresponds to the bill information detection method of the present invention one to one, and for the specific limitations of the bill information detection device, reference may be made to the limitations of the bill information detection method in the foregoing. All or part of each module in the bill information detection device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, and the computer device may be a terminal, and its internal structure diagram may be as shown in fig. 5, and fig. 5 is an internal structure diagram of the computer device in one embodiment. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a ticket information detection method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the configuration shown in fig. 5 is a block diagram of only a portion of the configuration associated with aspects of the present invention and is not intended to limit the computing devices to which aspects of the present invention may be applied, and that a particular computing device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, which includes a processor and a memory, the memory storing a computer program, the processor implementing the ticket information detection method according to any one of the above embodiments when executing the computer program.
One of ordinary skill in the art will understand that all or part of the processes of implementing the method for detecting ticket information according to any of the above embodiments may be implemented by a computer program, which may be stored in a non-volatile computer-readable storage medium, to instruct related hardware, and when executed, the computer program may include the processes of the above embodiments of the methods. Any reference to memory, storage, databases, or other media used in embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
Accordingly, in an embodiment, a computer-readable storage medium is also provided, on which a computer program is stored, wherein the program, when executed by a processor, implements the ticket information detection method according to any one of the above embodiments.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A bill information detection method is characterized by comprising the following steps:
acquiring bill information of a bill to be detected; the bill information comprises bill types, information of invoices making parties and project names;
acquiring file information of a protocol file corresponding to the bill information of the bill to be detected; the file information comprises protocol subscriber information and protocol content;
performing semantic analysis on the protocol content to obtain a service range corresponding to the protocol content; determining the type of the target bill corresponding to the service range according to a preset knowledge graph; the knowledge graph comprises corresponding relations between different service ranges and bill types;
if the bill type is consistent with the target bill type and the bill type is the type corresponding to the identity of the invoicer, judging whether the information of the invoicer corresponds to the information of the agreement endorser and whether the project name corresponds to the agreement content;
and when the invoicing party information corresponds to the agreement signing party information and the project name corresponds to the agreement content, determining that the billing information passes the detection.
2. The method of claim 1, further comprising:
judging whether the bill type is the type corresponding to the identity of the invoicing party or not according to the information of the invoicing party and the knowledge graph; the knowledge graph also comprises the corresponding relation between the identity of the invoicing party and the bill type.
3. The method of claim 1, further comprising:
if the bill type is not consistent with the target bill type, or if the bill type is not the type corresponding to the identity of the invoicing party, determining that the bill information of the bill to be detected does not pass the detection;
adding a bill type error mark into the bill to be detected, and outputting first prompt information that the bill type of the bill to be detected does not pass the detection;
and/or the presence of a gas in the gas,
when at least one of the invoicer information, the agreement endorser information and the project name does not correspond to the agreement content, determining that the invoice information does not pass the detection; adding a bill information error mark into the bill to be detected, and outputting second prompt information that the bill information of the bill to be detected does not pass the detection.
4. The method of claim 2, wherein before acquiring the ticket information of the ticket to be detected, the method further comprises:
acquiring bill information of a bill which passes the detection;
acquiring file information of the protocol file corresponding to the bill which passes the detection as reference file information;
acquiring a service range corresponding to the invoicing party in the detected bill information as a reference service range according to the reference file information;
associating the bill type in the detected bill information with the reference service range to serve as a first corresponding relation;
associating the identity of the invoicer in the detected bill information with the bill type in the detected bill information to serve as a second corresponding relation;
and obtaining the knowledge graph according to the first corresponding relation and the second corresponding relation.
5. The method of claim 4, wherein after obtaining the knowledge-graph according to the first corresponding relationship and the second corresponding relationship, further comprising:
when the protocol content in the reference file information is changed, acquiring a changed service range corresponding to the changed protocol content;
and updating the first corresponding relation in the knowledge graph according to the changed service range to obtain an updated knowledge graph.
6. The method of claim 1, wherein the file information further comprises: the position of the protocol subscriber and the implementation position of the protocol content;
the semantic analysis of the protocol content to obtain the service range corresponding to the protocol content includes:
performing semantic analysis on the protocol content to obtain the position of a corresponding protocol subscriber and the implementation position of the protocol content;
and performing semantic analysis according to the position of the protocol subscriber, the implementation position of the protocol content and the protocol content, and determining a service range corresponding to the protocol content.
7. The method of claim 1, wherein the agreement subscriber comprises a plurality of agreement subscribers; when the invoicing party information corresponds to the agreement signing party information and the project name corresponds to the agreement content, determining that the billing information passes the detection comprises the following steps:
and when the invoicing party information corresponds to at least one agreement signing party information and the project name corresponds to the agreement content, determining that the billing information passes the detection.
8. A bill information detecting apparatus, comprising:
the acquisition module is used for acquiring the bill information of the bill to be detected; the bill information comprises bill types, information of invoices making parties and project names; acquiring file information of a protocol file corresponding to the bill information of the bill to be detected; the file information comprises protocol subscriber information and protocol content;
the analysis module is used for carrying out semantic analysis on the protocol content to obtain a service range corresponding to the protocol content; determining the type of the target bill corresponding to the service range according to a preset knowledge graph; the knowledge graph comprises corresponding relations between different service ranges and bill types;
the first detection module is used for judging whether the invoicing party information corresponds to the agreement signing party information or not and whether the project name corresponds to the agreement content or not if the ticket type is consistent with the target ticket type and the ticket type is the type corresponding to the identity of the invoicing party;
and the second detection module is used for determining that the ticket information passes the detection when the ticket issuing party information corresponds to the agreement signing party information and the project name corresponds to the agreement content.
9. A computer device comprising a processor and a memory, the memory storing a computer program, characterized in that the processor implements the steps of the ticket information detection method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the ticket information detection method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911356082.2A CN111143512A (en) | 2019-12-25 | 2019-12-25 | Bill information detection method and device and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911356082.2A CN111143512A (en) | 2019-12-25 | 2019-12-25 | Bill information detection method and device and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111143512A true CN111143512A (en) | 2020-05-12 |
Family
ID=70519923
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911356082.2A Pending CN111143512A (en) | 2019-12-25 | 2019-12-25 | Bill information detection method and device and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143512A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113487396A (en) * | 2021-05-10 | 2021-10-08 | 广州城建职业学院 | Intelligent financial management tool based on cloud framework |
| CN113704498A (en) * | 2021-09-01 | 2021-11-26 | 云知声（上海）智能科技有限公司 | Intelligent auditing method and system for document |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109583827A (en) * | 2018-10-15 | 2019-04-05 | 平安科技（深圳）有限公司 | Invoice collation method, apparatus, computer equipment and storage medium |
| CN109978684A (en) * | 2019-04-11 | 2019-07-05 | 深圳微众税银信息服务有限公司 | A kind of bank acceptance checking method, system and relevant device |
| US20190333611A1 (en) * | 2018-04-30 | 2019-10-31 | International Business Machines Corporation | Identifying Repetitive Portions of Clinical Notes and Generating Summaries Pertinent to Treatment of a Patient Based on the Identified Repetitive Portions |
-
2019
- 2019-12-25 CN CN201911356082.2A patent/CN111143512A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190333611A1 (en) * | 2018-04-30 | 2019-10-31 | International Business Machines Corporation | Identifying Repetitive Portions of Clinical Notes and Generating Summaries Pertinent to Treatment of a Patient Based on the Identified Repetitive Portions |
| CN109583827A (en) * | 2018-10-15 | 2019-04-05 | 平安科技（深圳）有限公司 | Invoice collation method, apparatus, computer equipment and storage medium |
| CN109978684A (en) * | 2019-04-11 | 2019-07-05 | 深圳微众税银信息服务有限公司 | A kind of bank acceptance checking method, system and relevant device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113487396A (en) * | 2021-05-10 | 2021-10-08 | 广州城建职业学院 | Intelligent financial management tool based on cloud framework |
| CN113704498A (en) * | 2021-09-01 | 2021-11-26 | 云知声（上海）智能科技有限公司 | Intelligent auditing method and system for document |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210224902A1 (en) | Systems and methods for electronic account certification and enhanced credit reporting | |
| US10783116B2 (en) | Systems and methods for managing data | |
| CN110473078B (en) | Information processing method, device, gateway server and medium in invoice issuing | |
| CN110633963A (en) | Electronic bill processing method, electronic bill processing device, computer-readable storage medium and equipment | |
| US20090171723A1 (en) | Systems and methods for electronic account certification and enhanced credit reporting | |
| US20090094156A1 (en) | Automated Budget Management, Multiple Payment, and Payment Authority Management | |
| US20130325706A1 (en) | System, method, apparatus, and computer program product for improved payment processing | |
| CN110147365B (en) | Method, device, equipment and medium for checking business data and financial data | |
| CN102171716A (en) | A process and system for providing real-time processing service | |
| CN108090824B (en) | Data checking method and device, computer equipment and readable storage medium | |
| WO2020233402A1 (en) | Accounts payable order validation method, apparatus and device, and storage medium | |
| CN111143512A (en) | Bill information detection method and device and computer equipment | |
| CN111709718A (en) | Intelligent warranty asset service platform, method and storage medium based on artificial intelligence | |
| US20130332374A1 (en) | Fraud prevention for real estate transactions | |
| CN110912804B (en) | Intelligent batched lawyer letter sending system and method based on block chain | |
| CN113077331A (en) | Personal financial credit evaluation system and method based on big data | |
| CN114663205A (en) | Financial statement processing method and device, computer equipment and storage medium thereof | |
| CN111311277B (en) | Bill processing method and device based on block chain network and related equipment | |
| CN111242773A (en) | Virtual resource application docking method and device, computer equipment and storage medium | |
| US20160132964A1 (en) | Tax refund loan system absent irs and fms debt indicator | |
| CN111242782A (en) | Service processing method, device and equipment based on block chain and readable medium | |
| CN113051257B (en) | Service data cleaning method and device | |
| CN111126966A (en) | Bill auditing method and device, computer equipment and computer-readable storage medium | |
| CN114037527A (en) | Transaction data processing method and device, computer equipment and storage medium | |
| CN114240588A (en) | Annuity plan reconciliation method, device, equipment and medium based on block chain |
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: 20200512 |
|
| RJ01 | Rejection of invention patent application after publication |