CN116882747A

CN116882747A - Invoice monitoring processing method and device, computer equipment and storage medium

Info

Publication number: CN116882747A
Application number: CN202310857086.9A
Authority: CN
Inventors: 曾潇
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2023-07-12
Filing date: 2023-07-12
Publication date: 2023-10-13

Abstract

The application provides an invoice monitoring and processing method, an invoice monitoring and processing device, computer equipment and a storage medium, wherein the invoice monitoring and processing method comprises the following steps: updating the monitoring rules in the channel monitoring rule table according to the monitoring rules in the monitoring list; updating the monitoring rule of the monitoring list according to the monitoring rule of the monitoring list; receiving a monitoring return code corresponding to each invoice information sent by a third party mechanism, and recording at least one monitoring return code into a monitoring table; sending a monitoring return code in the monitoring table to a third party mechanism, receiving an invoice state sent by the third party mechanism, and generating risk information according to the invoice state; and acquiring invoice information corresponding to the monitoring return code from the monitoring table, acquiring a terminal number corresponding to the invoice information from the channel monitoring rule table, and transmitting risk information to a channel end corresponding to the channel number. The application ensures timeliness of invoice status acquisition and monitoring efficiency of invoice risk, and ensures that each related channel end can timely acquire the risk of the invoice corresponding to the invoice information.

Description

Invoice monitoring processing method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of distributed systems, and in particular, to an invoice monitoring method, an invoice monitoring device, a computer device, and a storage medium.

Background

The value-added tax invoice verification system is a transaction necessary precondition type system based on an organization level and capable of being used by a plurality of systems in a financial institution. The tracking and monitoring of the checked value-added tax invoice state is an important part for timely early warning of each system, and particularly plays an important role in risk management and control.

At present, aiming at risk management and control of invoices, a terminal mainly sends a monitoring request to a third party institution through a value-added tax invoice verification system to obtain invoice states sent by the third party institution, and the terminal manually determines invoice risks according to the invoice states, so that risk monitoring efficiency of the invoices is low.

Disclosure of Invention

The application provides an invoice monitoring and processing method, an invoice monitoring and processing device, computer equipment and a storage medium, which are used for solving the problem of low invoice risk monitoring efficiency of the current invoice risk management and control method.

In a first aspect, the present application provides an invoice monitoring and processing method, including:

receiving a monitoring list sent by a channel end; the monitoring list comprises invoice information, monitoring rules and verification results; the invoice information is a unique identification of the invoice; the monitoring rule characterizes a monitoring starting date and a monitoring expiration date for monitoring the invoice; the verification result is used for representing the authenticity of the invoice;

Acquiring a channel monitoring rule table corresponding to the channel end, and updating the monitoring rule in the channel monitoring rule table according to the monitoring rule in the monitoring list; the channel monitoring rule table is recorded with invoice information, monitoring rules and channel numbers; the channel number is a unique identifier of a channel end;

acquiring a monitoring table, and updating the monitoring rule of the monitoring table according to the monitoring rule of the monitoring table; invoice information and monitoring rules are recorded in the monitoring table;

transmitting at least one invoice information in the monitoring table to a third party mechanism, receiving a monitoring return code corresponding to each invoice information transmitted by the third party mechanism, and recording at least one monitoring return code into the monitoring table; the third party mechanism is used for determining invoice states of invoice information; the monitoring return code is a unique identifier of the invoice information in the third party mechanism, and is used for being called by the third party mechanism to obtain an invoice state corresponding to the invoice information;

sending a monitoring return code in the monitoring table to the third party mechanism according to a preset monitoring period, receiving an invoice state sent by the third party mechanism, and generating risk information according to the invoice state; the risk information is used for representing the risk degree of the invoice state of the invoice information corresponding to the monitoring return code;

And acquiring invoice information corresponding to the monitoring return code from the monitoring table, acquiring a terminal number corresponding to the invoice information from the channel monitoring rule table, and sending the risk information to a channel end corresponding to the channel number.

In the above scheme, the channel end comprises a front end;

receiving a monitoring list sent by a channel end, wherein the monitoring list comprises:

the method comprises the steps of sending an information input page to the front end, and receiving invoice information and verification results output by the front end according to the information input page; the information input page is used for inputting invoice information and verification results of the invoice information by the front end through inputting page information or importing files;

sending a rule maintenance page to a front end, and receiving a monitoring rule output by the front end according to the rule maintenance page; the rule maintenance page is used for displaying at least one rule item; the rule items are used for being selected by the front end, and at least one rule item selected by the front end forms a monitoring rule;

and summarizing the invoice information, the verification result and the monitoring rule to obtain the monitoring list.

In the above scheme, the channel end comprises an interface end;

receiving a monitoring list message and a monitoring rule message which are sent by the interface terminal;

extracting invoice information and verification results in the monitoring list message, and extracting monitoring rules in the monitoring rule message;

In the above scheme, obtaining the channel monitoring rule table corresponding to the channel end, and updating the monitoring rule in the channel monitoring rule table according to the monitoring rule in the monitoring list, including:

acquiring a channel monitoring rule table recorded with channel numbers of the channel ends;

if the channel monitoring rule table is determined to have invoice information in the monitoring list, replacing the monitoring rule corresponding to the invoice information in the channel monitoring rule table with the monitoring rule in the monitoring list;

if the channel monitoring rule table is determined to not have the invoice information in the monitoring list, inputting the invoice information and the monitoring rule in the monitoring list into the channel monitoring rule table, and inputting the channel number of the channel end sending the monitoring list into the channel monitoring rule table.

In the above scheme, updating the monitoring rule of the monitoring table according to the monitoring rule of the monitoring list includes:

if the monitoring list is determined to have invoice information in the monitoring list, extracting a monitoring identifier corresponding to the invoice information;

if the monitoring identifier is determined to be the execution monitoring, setting the monitoring rule in the monitoring list as a first rule, and setting the monitoring rule of the invoice information in the monitoring list as a second rule;

if the monitoring expiration date in the second rule is determined to be greater than the monitoring expiration date in the first rule, not updating the monitoring rule in the monitoring table;

and if the monitoring due date in the second rule is not more than the monitoring due date in the first rule, setting the next date of the monitoring due date in the second rule as the monitoring starting date in the second rule, and setting the monitoring due date in the second rule as the monitoring due date in the first rule.

In the above scheme, sending at least one invoice information in the monitoring table to a third party mechanism, receiving a monitoring return code corresponding to each invoice information sent by the third party mechanism, and entering at least one monitoring return code into the monitoring table, including:

Traversing the monitoring start day of each monitoring rule in the monitoring table, and setting invoice information corresponding to the monitoring rule of which the monitoring start day is the current day as target invoice information;

transmitting at least one target invoice information to a third party mechanism, and receiving a monitoring return code transmitted by the third party mechanism;

and recording the monitoring return code into the monitoring table and associating the monitoring return code with target invoice information.

In the above scheme, the sending the monitoring return code in the monitoring table to the third party mechanism according to the preset monitoring period, and receiving the invoice state sent by the third party mechanism includes:

sequentially extracting monitoring return codes in a monitoring table according to a monitoring period, and transmitting the extracted monitoring return codes to the third party mechanism;

receiving risk information sent by the third party mechanism according to the monitoring return code, and acquiring an invoice state corresponding to the monitoring return code from a monitoring table; wherein the contents of the invoice status include any of normal, voided, inconsistent and no such invoice.

In the above scheme, generating risk information according to the invoice state includes:

if the invoice state content is determined to be normal, determining that the risk type recorded in the risk information is risk-free;

If the invoice state content is determined to be invalid, determining the risk type recorded in the risk information as a first-level risk;

if the invoice state content is inconsistent, determining that the risk type recorded in the risk information is secondary risk;

if the invoice state content is determined to be the condition that the invoice is not checked, determining that the risk type recorded in the risk information is three-level risk;

and recording the risk information and invoice information acquired from the monitoring table into a preset risk information table.

In the above scheme, the step of sending the risk information to the channel end corresponding to the channel number includes:

if the channel end is determined to be the front end, inputting the risk information into a preset risk early warning template to obtain a risk early warning message; wherein, the risk pre-alarm text is rendering data for generating a web page;

the risk pre-alarm message is sent to the front end, and the front end is controlled to render the risk pre-alarm message, so that a risk pre-alarm page is obtained; the risk early warning page is a network page for displaying risk information.

In the above scheme, the channel end comprises a front end;

After the risk information is sent to the channel end corresponding to the channel number, the method further comprises:

the risk inquiry page is sent to the front end, and the front end attribute information and inquiry information sent by the front end according to the risk inquiry page are received;

if the front-end attribute information is determined to have the query authority, acquiring risk information from a preset risk information table by the query information, and inputting the acquired risk information into a preset risk early warning template to obtain a risk pre-warning message;

In a second aspect, the present application provides an invoice monitoring and processing apparatus, comprising:

the input module is used for receiving the monitoring list sent by the channel end; the monitoring list comprises invoice information, monitoring rules and verification results; the invoice information is a unique identification of the invoice; the monitoring rule characterizes a monitoring starting date and a monitoring expiration date for monitoring the invoice; the verification result is used for representing the authenticity of the invoice;

The channel module is used for acquiring a channel monitoring rule table corresponding to the channel end and updating the monitoring rule in the channel monitoring rule table according to the monitoring rule in the monitoring list; the channel monitoring rule table is recorded with invoice information, monitoring rules and channel numbers; the channel number is a unique identifier of a channel end;

the monitoring module is used for acquiring a monitoring table and updating the monitoring rule of the monitoring table according to the monitoring rule of the monitoring table; invoice information and monitoring rules are recorded in the monitoring table;

the third party module is used for sending at least one invoice information in the monitoring table to a third party mechanism, receiving a monitoring return code corresponding to each invoice information sent by the third party mechanism, and inputting at least one monitoring return code into the monitoring table; the third party mechanism is used for determining invoice states of invoice information; the monitoring return code is a unique identifier of the invoice information in the third party mechanism, and is used for being called by the third party mechanism to obtain an invoice state corresponding to the invoice information;

the risk identification module is used for sending the monitoring return code in the monitoring table to the third party mechanism according to a preset monitoring period, receiving the invoice state sent by the third party mechanism and generating risk information according to the invoice state; the risk information is used for representing the risk degree of the invoice state of the invoice information corresponding to the monitoring return code;

And the risk forwarding module is used for acquiring invoice information corresponding to the monitoring return code from the monitoring table, acquiring a terminal number corresponding to the invoice information from the channel monitoring rule table, and sending the risk information to a channel end corresponding to the channel number.

In a third aspect, the present application provides a computer device comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes the computer-executable instructions stored in the memory to implement the methods described above.

In a fourth aspect, the present application provides a computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method described above.

In a fifth aspect, the application provides a computer program product comprising a computer program which, when executed by a processor, implements the method described above.

The application provides an invoice monitoring processing method, device, computer equipment and storage medium, which are characterized in that a channel monitoring rule list corresponding to a channel end is obtained through receiving a monitoring list sent by the channel end, and the monitoring rule in the channel monitoring rule list is updated according to the monitoring rule in the monitoring list so as to realize the determination of the monitoring rule of the channel end and the determination of the channel end of a relevant party related to invoice information, and ensure that each channel end related to the invoice information is incorporated into the channel monitoring rule list.

And updating the monitoring rule of the monitoring table according to the monitoring rule of the monitoring list by acquiring the monitoring table so as to realize the technical effect of determining the monitoring rule of invoice information according to the monitoring list.

By means of the method that at least one invoice information in the monitoring table is sent to a third party mechanism, monitoring return codes corresponding to each invoice information sent by the third party mechanism are received, and at least one monitoring return code is recorded in the monitoring table, the technical effect of monitoring and managing each invoice information based on the monitoring table is achieved by means that each invoice information is included in the category of invoice state monitoring based on the monitoring return codes.

The technical scheme of automatically monitoring the invoice state of each invoice information according to a fixed period is realized by sending the monitoring return code in the monitoring table to the third party mechanism according to a preset monitoring period, receiving the invoice state sent by the third party mechanism and generating risk information according to the invoice state, so that timeliness of invoice state acquisition and monitoring efficiency of invoice risk are ensured; by generating the risk information according to the invoice state, the technical effect of automatically determining the invoice risk based on the invoice state is achieved, and the invoice risk identification efficiency and identification reliability are improved.

The invoice information corresponding to the monitoring return code is obtained from the monitoring table, the terminal number corresponding to the invoice information is obtained from the channel monitoring rule table, the risk information is sent to the channel end corresponding to the channel number, the risk information of the invoice information is sent to the channel end corresponding to the relevant party, the risk of the invoice corresponding to the invoice information can be timely obtained by each relevant channel end, and timeliness and comprehensiveness of information sharing are guaranteed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is a schematic diagram of an application scenario of an invoice monitoring and processing method of the present application;

FIG. 2 is a flow chart of an embodiment 1 of an invoice monitoring processing method according to the present application;

FIG. 3 is a flow chart of example 2 of an invoice monitoring process method according to the present application;

FIG. 4 is a block diagram of an invoice monitoring and processing apparatus according to embodiment 3 of the present application;

fig. 5 is a schematic diagram of a hardware structure of a computer device in the computer device according to the present application.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

It should be noted that the invoice monitoring and processing method, the device, the computer equipment and the storage medium of the application can be used in the technical field of the distributed system, and can also be used in any field except the technical field of the distributed system.

The specific application scene of the application is as follows: referring to fig. 1, a server 11 running an invoice monitoring and processing method is installed in an organization-level system 1, and the organization-level system is generally connected with each service system in a distributed system, so as to be a unified system capable of interfacing with a plurality of service systems in a large-scale financial institution, and the server 11 relates to a monitoring mechanism for checking and organizing the organization-level system for value-added tax invoices. The value-added tax invoice verification system is a transaction necessary precondition type system based on an organization level and capable of being used by a plurality of systems in a financial institution. The tracking and monitoring of the state of the checked value-added tax invoice is an important part for timely early warning of each system, and particularly has an important effect on risk management and control, so that the problems of maintenance of invoice monitoring rules after checking, continuous monitoring rules of invoice states, timing update of monitoring information, early warning after abnormal information receiving and the like are solved. The server 11 is connected to at least one channel end 12 and a third party authority 13, respectively.

To solve this problem, the server 11 receives the monitoring list transmitted from the channel side 12; the monitoring list comprises invoice information, monitoring rules and verification results; the invoice information is the unique identification of the invoice; the monitoring rule characterizes the monitoring starting date and the monitoring expiration date for monitoring the invoice; the verification result is used for representing the authenticity of the invoice;

The server 11 acquires a channel monitoring rule table corresponding to the channel end 12, and updates the monitoring rules in the channel monitoring rule table according to the monitoring rules in the monitoring list; invoice information, monitoring rules and channel numbers are recorded in the channel monitoring rule table; the channel number is a unique identification of the channel end 12;

the server 11 acquires a monitoring table and updates the monitoring rule of the monitoring table according to the monitoring rule of the monitoring table; the monitoring table records invoice information and monitoring rules;

the server 11 sends at least one invoice information in the monitoring table to the third party mechanism 13, receives monitoring return codes corresponding to each invoice information sent by the third party mechanism 13, and records the at least one monitoring return code in the monitoring table; wherein the third party mechanism 13 is used for determining invoice states of invoice information; the monitoring return code characterizes the invoice state of the invoice information and is monitored by the third party mechanism 13;

the server 11 sends a monitoring return code in a monitoring table to the third party mechanism 13 according to a preset monitoring period, receives the invoice state sent by the third party mechanism 13, and generates risk information according to the invoice state; the risk information is used for representing the risk degree of the invoice state of the invoice information corresponding to the monitoring return code;

The server 11 acquires invoice information corresponding to the monitoring return code from the monitoring table, acquires a terminal number corresponding to the invoice information from the channel monitoring rule table, and transmits risk information to the channel end 12 corresponding to the channel number.

Therefore, the technical scheme realizes the construction of an organization-level value-added tax invoice verification system platform of the multi-system, and realizes an invoice unified processing mechanism aiming at the multi-system and multi-access channels and an interaction mechanism between a local database and a third party system.

The invoice monitoring and processing method provided by the application realizes the technical scheme of automatically monitoring the invoice state of each invoice information according to a fixed period, ensures timeliness of invoice state acquisition and invoice risk monitoring efficiency, ensures that each relevant channel end can timely acquire the risk of the invoice corresponding to the invoice information, and ensures timeliness and comprehensiveness of information sharing. Aims to solve the technical problems in the prior art.

The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Example 1:

referring to fig. 2, the present application provides an invoice monitoring and processing method, which includes:

s201: receiving a monitoring list sent by a channel end; the monitoring list comprises invoice information, monitoring rules and verification results; the invoice information is the unique identification of the invoice; the monitoring rule characterizes the monitoring starting date and the monitoring expiration date for monitoring the invoice; the verification results are used to characterize the authenticity of the invoice.

In the step, the verification result is value-added tax invoice verification, which is an important way for verifying the authenticity of trade by a way of interfacing a third party institution in various different scenes such as trade financing, cross-border payment and the like by a financial institution. The third party organization is a third party invoice verification system (such as an electronic invoice service platform) and/or a national tax administration nationwide value-added tax invoice verification platform.

In a preferred embodiment, the channel end comprises a front end;

the method comprises the steps of sending an information input page to a front end, and receiving invoice information and verification results output by the front end according to the information input page; the information input page is used for inputting invoice information and verification results of the invoice information by the front end through inputting page information or importing files;

A rule maintenance page is sent to the front end, and a monitoring rule output by the front end according to the rule maintenance page is received; the rule maintenance page is used for displaying at least one rule item; the rule items are used for being selected by the front end, and at least one rule item selected by the front end forms a monitoring rule;

and summarizing invoice information, verification results and monitoring rules to obtain a monitoring list.

The front end is a terminal device used by each institution teller, and the teller checks the value-added tax invoice by inputting page information or importing files through the front end to obtain a check result and store the check result in a database, so that the technical effects of receiving the invoice information and the check result output by the front end through the information input page are realized.

The method mainly is used for carrying out single or batch monitoring rule maintenance on the invoice and mainly comprises the steps of monitoring whether the invoice is monitored, monitoring the starting date, monitoring the expiration date, monitoring the update mark and the like, so that the maintenance of front-end monitoring maintenance is realized.

In another preferred embodiment, the channel end comprises an interface end;

receiving a monitoring list message and a monitoring rule message sent by an interface terminal;

and summarizing invoice information, checking results and monitoring the rule to obtain a monitoring list.

The interface terminal is an external terminal for sending the monitoring list message by calling a preset interface, the interface is a computer interface for generating a monitoring rule message, and the external terminal is a terminal device outside an internal system of a bank. And the external terminal generates a monitoring rule message from the invoice information and the verification result thereof and the monitoring rule by calling the interface terminal.

And after receiving the monitoring rule message, extracting invoice information, verification results and monitoring rules in the monitoring rule message to generate a monitoring list for subsequent processing.

In summary, the step creates a set of front-end access system and a set of access mechanism (namely, a method that an external terminal sends a monitoring list message through an interface), wherein the front-end access system can realize ticket-increasing information input or file input through a front-end input mode, and maintenance of monitoring rules after verification; after the interface access mechanism receives verification of ticket adding information of each system in an interface mode, the monitoring rule maintenance message is sent, the ticket adding monitoring rule is maintained and updated, the monitoring ticket adding list is sent to a third party mechanism at regular time, and the monitoring duration is controlled.

Setting up a front-end input system, wherein a monitoring part mainly relates to a front-end monitoring rule maintenance page; constructing a monitoring list after background verification is completed and sending the monitoring list at fixed time; night time queries for monitoring anomaly information.

The monitoring part mainly relates to monitoring rule maintenance message receiving, monitoring list message receiving, pushing and inquiring abnormal information, receiving and inquiring a real-time monitoring list and the like.

S202: acquiring a channel monitoring rule table corresponding to a channel end, and updating the monitoring rule in the channel monitoring rule table according to the monitoring rule in the monitoring list; invoice information, monitoring rules and channel numbers are recorded in the channel monitoring rule table; the channel number is a unique identification of the channel end.

In the step, a channel monitoring rule list corresponding to a channel end is obtained by receiving a monitoring list sent by the channel end, and the monitoring rule in the channel monitoring rule list is updated according to the monitoring rule in the monitoring list so as to realize the determination of the monitoring rule of the channel end and the determination of the channel end of a relevant party related to invoice information, thereby ensuring that each channel end related to the invoice information is included in the channel monitoring rule list.

In this embodiment, a "channel monitoring rule table" is established, and is mainly used for storing descriptions of different monitoring rules of different channels on invoices, and the dimensions are invoice information and channel numbers.

In a preferred embodiment, obtaining a channel monitoring rule table corresponding to a channel end, and updating the monitoring rule in the channel monitoring rule table according to the monitoring rule in the monitoring list, including:

acquiring a channel monitoring rule table recorded with channel numbers of channel ends;

if the invoice information in the monitoring list is determined to be in the channel monitoring rule table, replacing the monitoring rule corresponding to the invoice information in the channel monitoring rule table with the monitoring rule in the monitoring list;

if the channel monitoring rule list does not have the invoice information in the monitoring list, inputting the invoice information and the monitoring rule in the monitoring list into the channel monitoring rule list, and inputting the channel number of the channel end sending the monitoring list into the channel monitoring rule list.

Illustratively, the monitoring list is obtained through different channels such as access through the front end or the interface end, and each invoice mainly comprises: invoice number, invoice code, channel system mark, monitor expiration date, monitor mark and other attributes; the invoice number and the invoice code are invoice information, the channel system identifier is a channel number, and the channel system identifier is a unique identifier of a channel end; the monitoring expiration date refers to the expiration date for monitoring the invoice; the monitoring identity characterizes whether the invoice is monitored.

Judging whether data (invoice number, invoice code and channel system identifier are used as unique identifiers) exists in the channel monitoring rule table, and if so, updating the monitoring rule of the channel system; if not, insert.

S203: acquiring a monitoring table, and updating the monitoring rule of the monitoring table according to the monitoring rule of the monitoring table; the monitoring table records invoice information and monitoring rules.

In the step, the monitoring rule of the monitoring table is updated according to the monitoring rule of the monitoring table by acquiring the monitoring table, so that the technical effect of determining the monitoring rule of invoice information according to the monitoring table is realized.

The monitoring list sent by each channel end is processed through preset background logic to perform unified processing, in particular to record and process the same invoice aiming at different channel ends, the same invoice of different channel ends is recorded in the monitoring list, and meanwhile, channel numbers of different channel ends are recorded in the channel monitoring rule list.

In this embodiment, a "monitoring table" is established, and is mainly used for storing the final monitoring rule of the invoice, and the dimension is invoice information.

In a preferred embodiment, updating the monitoring rules of the monitoring table according to the monitoring rules of the monitoring list comprises:

If the invoice information in the monitoring list is determined to be in the monitoring list, extracting a monitoring identifier corresponding to the invoice information;

if the monitoring mark is determined to be the execution of monitoring, the monitoring rule in the monitoring list is set as a first rule, and the monitoring rule of the invoice information in the monitoring list is set as a second rule;

if the monitoring expiration date in the second rule is determined to be greater than the monitoring expiration date in the first rule, the monitoring rule in the monitoring table is not updated;

if the monitoring due date in the second rule is not greater than the monitoring due date in the first rule, setting the next date of the monitoring due date in the second rule as the monitoring start date in the second rule, and setting the monitoring due date in the second rule as the monitoring due date in the first rule.

Illustratively, whether data (invoice number+invoice code is used as a unique identifier) exists in the monitoring table is judged, if yes, whether the monitoring identifier is yes is continuously judged, if yes, whether the original monitoring expiration date is larger than the new expiration date is judged, if yes, the monitoring table is not updated, if not, the monitoring starting date is the original expiration date +1, and meanwhile the expiration date is updated.

S204: at least one invoice information in the monitoring table is sent to a third party mechanism, a monitoring return code corresponding to each invoice information sent by the third party mechanism is received, and at least one monitoring return code is input into the monitoring table; the third party mechanism is used for determining the invoice state of the invoice information; the monitoring return code is the unique identification of the invoice information in the third party institution, and is used for being called by the third party institution to obtain the invoice state corresponding to the invoice information.

In the step, at least one invoice information in the monitoring table is sent to the third party mechanism, the monitoring return code corresponding to each invoice information sent by the third party mechanism is received, and the at least one monitoring return code is recorded in the monitoring table, so that the invoice information is brought into the category of invoice state monitoring based on the monitoring return code, and the technical effect of monitoring and managing the invoice information based on the monitoring table is realized.

Illustratively, the monitoring part mainly involves sending a timing monitoring list to the third party institution, monitoring the list in real time, and receiving abnormal information push of the third party verification system/tax bureau through implementation of a preset third party institution interface mechanism. The method is mainly used for integrating the invoices processed in the background and then sending the integrated invoices to a third party verification system/tax bureau interface, wherein the monitoring list is used for long-term monitoring, and the real-time monitoring query is used for instant risk abnormal information query.

In a preferred embodiment, at least one invoice information in the monitoring table is sent to a third party mechanism, a monitoring return code corresponding to each invoice information sent by the third party mechanism is received, and the at least one monitoring return code is entered into the monitoring table, including:

and recording the monitoring return code into a monitoring table and associating the monitoring return code with the target invoice information.

Illustratively, a long-term monitoring list is sent to a third party verification system by querying the monitoring list for the day of the monitoring start day at a preset time interval (e.g., at night), once a day is timed, and a "monitoring return code" is saved.

Timing task real-time monitoring and inquiring: and inquiring risk abnormality information from a third-party verification mechanism according to the monitoring return code.

Further, the monitoring expiration date in the first rule may be a preset system date, a monitoring list is obtained from the interface access channel, the monitoring table of the background database is queried first, if the monitoring is in progress, if the monitoring expiration date of the invoice is greater than or equal to the system date, the monitoring is described, and the risk abnormality information is queried to the third party verification mechanism directly through a monitoring return code in the table.

If no data exists in the table or the monitoring expiration date is smaller than the system date, the monitoring is finished or the monitoring is not finished before the table, a monitoring list message is directly sent to a third party verification mechanism, and the returned monitoring return code is put in storage.

S205: sending a monitoring return code in a monitoring table to a third party mechanism according to a preset monitoring period, receiving an invoice state sent by the third party mechanism, and generating risk information according to the invoice state; the risk information is used for representing the risk degree of the invoice state of the invoice information corresponding to the monitoring return code.

In the step, the monitoring return code in the monitoring table is sent to the third party mechanism according to a preset monitoring period, the invoice state sent by the third party mechanism is received, and the technical scheme of automatically monitoring the invoice state of each invoice information according to a fixed period is realized according to the way of generating the risk information according to the invoice state, so that timeliness of invoice state acquisition and monitoring efficiency of invoice risk are ensured; by generating the risk information according to the invoice state, the technical effect of automatically determining the invoice risk based on the invoice state is achieved, and the invoice risk identification efficiency and identification reliability are improved.

In a preferred embodiment, the monitoring return code in the monitoring table is sent to the third party mechanism according to a preset monitoring period, and the receipt of the invoice status sent by the third party mechanism includes:

sequentially extracting monitoring return codes in the monitoring table according to the monitoring period, and transmitting the extracted monitoring return codes to a third party mechanism;

receiving risk information sent by a third party mechanism according to the monitoring return code, and acquiring an invoice state corresponding to the monitoring return code from a monitoring table; wherein the contents of the invoice status include any of normal, voided, inconsistent and no such invoice.

Further, generating risk information according to the invoice status includes:

if the invoice state is inconsistent, determining that the risk type recorded in the risk information is secondary risk;

if the invoice state is determined to be checked, determining that the risk type recorded in the risk information is three-level risk;

The risk information is obtained from a third party organization (such as a third party verification system) at fixed time, and a 'risk information table' is stored, so that the risk information is pushed to each access channel according to a 'channel monitoring rule table' query system needing to push the risk information.

In this embodiment, a "risk information table" is established, and is mainly used for saving risk information of an invoice.

S206: and acquiring invoice information corresponding to the monitoring return code from the monitoring table, acquiring a terminal number corresponding to the invoice information from the channel monitoring rule table, and transmitting risk information to a channel end corresponding to the channel number.

In the step, the invoice information corresponding to the monitoring return code is acquired from the monitoring table, the terminal number corresponding to the invoice information is acquired from the channel monitoring rule table, the risk information is transmitted to the channel end corresponding to the channel number, the risk information of the invoice information is transmitted to the channel end corresponding to the relevant party, the risk of the invoice corresponding to the invoice information can be timely acquired by each relevant channel end, and timeliness and comprehensiveness of information sharing are guaranteed.

Therefore, the application realizes the technical effect of automatically monitoring the checked invoice for a long time, improves the verification efficiency of the authenticity of the business background and the long-time monitoring, and sends the risk information to each corresponding channel end so as to realize the effect of timely warning the invoice risk to the channel end.

In a preferred embodiment, the step of sending the risk information to the channel end corresponding to the channel number includes:

if the channel end is determined to be the front end, inputting risk information into a preset risk early warning template to obtain a risk early warning message; the risk pre-alarm text is rendering data for generating a network page;

the risk pre-warning message is sent to the front end, and the front end is controlled to render the risk pre-warning message, so that a risk pre-warning page is obtained; the risk early warning page is a network page for displaying risk information.

Illustratively, the channel end includes a front end; the front end is accessed into a system risk early warning page, and risk information is displayed in real time. The data to be displayed in the HTML is realized through js, instead of directly inputting the data in the HTML, so that the rendering data is based on risk pre-alarm text in js format; page rendering is the whole process of the browser changing HTML into an image that is seen by the human eye. The render, which is often developed, is the process of generating HTML and stuffing it into the DOM, and sometimes is dedicated to the process of generating the desired HTML by some code logic.

Example 2:

referring to fig. 3, the present application provides an invoice monitoring and processing method, which includes:

S301: receiving a monitoring list sent by a channel end; the monitoring list comprises invoice information, monitoring rules and verification results; the invoice information is the unique identification of the invoice; the monitoring rule characterizes the monitoring starting date and the monitoring expiration date for monitoring the invoice; the verification results are used to characterize the authenticity of the invoice.

This step corresponds to S201 in embodiment 1, and thus will not be described here.

S302: acquiring a channel monitoring rule table corresponding to a channel end, and updating the monitoring rule in the channel monitoring rule table according to the monitoring rule in the monitoring list; invoice information, monitoring rules and channel numbers are recorded in the channel monitoring rule table; the channel number is a unique identification of the channel end.

This step corresponds to S202 in embodiment 1, and thus will not be described here.

S303: acquiring a monitoring table, and updating the monitoring rule of the monitoring table according to the monitoring rule of the monitoring table; the monitoring table records invoice information and monitoring rules.

This step corresponds to S023 in embodiment 1, and thus will not be described here.

S304: at least one invoice information in the monitoring table is sent to a third party mechanism, a monitoring return code corresponding to each invoice information sent by the third party mechanism is received, and at least one monitoring return code is input into the monitoring table; the third party mechanism is used for determining the invoice state of the invoice information; the monitoring return code is the unique identification of the invoice information in the third party institution, and is used for being called by the third party institution to obtain the invoice state corresponding to the invoice information.

This step corresponds to S204 in embodiment 1, and thus will not be described here.

S305: sending a monitoring return code in a monitoring table to a third party mechanism according to a preset monitoring period, receiving an invoice state sent by the third party mechanism, and generating risk information according to the invoice state; the risk information is used for representing the risk degree of the invoice state of the invoice information corresponding to the monitoring return code.

This step corresponds to S205 in embodiment 1, and thus will not be described here.

S306: and acquiring invoice information corresponding to the monitoring return code from the monitoring table, acquiring a terminal number corresponding to the invoice information from the channel monitoring rule table, and transmitting risk information to a channel end corresponding to the channel number.

This step corresponds to S206 in embodiment 1, and thus will not be described here.

S307: the risk query page is sent to the front end, and the front end attribute information and query information sent by the front end according to the risk query page are received;

Illustratively, the front-end accesses a system risk query page, and the front-end attribute information input by the front-end includes: channel number (e.g., front end organization name, front end teller number), the query information entered includes: monitoring conditions such as a certain date before the expiration date, risk type and the like; and inquiring corresponding invoice information from the risk information table to improve the inquiry convenience of the invoices with risks, thereby realizing inquiry and display of global risk information of all jurisdictions.

S308: receiving a query message sent by an interface terminal, and receiving interface terminal attribute information and query information sent by the interface terminal according to a risk query page;

if the attribute information of the interface terminal has the query authority, the query information acquires risk information from a preset risk information table and sends the risk information to the interface terminal.

Illustratively, the interface-side attribute information input by the external terminal through the interface includes: channel number (for example: organization name of external terminal, teller number of external terminal), and the input inquiry information includes: monitoring conditions such as a certain date before the expiration date, risk type and the like; and inquiring corresponding invoice information from the risk information table to improve the inquiry convenience of the invoices with risks, thereby realizing inquiry and display of global risk information of all jurisdictions.

The feedback of the risk information of the external terminal is only aimed at inquiring the risk information of the invoice corresponding to the inquiring information sent at the present time, and is not used for long-term monitoring so as to ensure the data security in the risk information table.

Example 3:

referring to fig. 4, the present application provides an invoice monitoring and processing device 4, which includes:

an input module 41, configured to receive a monitoring list sent by a channel end; the monitoring list comprises invoice information, monitoring rules and verification results; the invoice information is the unique identification of the invoice; the monitoring rule characterizes the monitoring starting date and the monitoring expiration date for monitoring the invoice; the verification result is used for representing the authenticity of the invoice;

the channel module 42 is configured to obtain a channel monitoring rule table corresponding to the channel end, and update the monitoring rule in the channel monitoring rule table according to the monitoring rule in the monitoring list; invoice information, monitoring rules and channel numbers are recorded in the channel monitoring rule table; the channel number is the unique identifier of the channel end;

the monitoring module 43 is configured to obtain a monitoring table, and update a monitoring rule of the monitoring table according to a monitoring rule of the monitoring table; the monitoring table records invoice information and monitoring rules;

The third party module 44 is configured to send at least one invoice information in the monitoring table to a third party mechanism, receive a monitoring return code corresponding to each invoice information sent by the third party mechanism, and record the at least one monitoring return code in the monitoring table; the third party mechanism is used for determining the invoice state of the invoice information; the monitoring return code is a unique identifier of the invoice information in the third party institution, and is used for being called by the third party institution to obtain an invoice state corresponding to the invoice information;

the risk identification module 45 is configured to send a monitoring return code in the monitoring table to a third party mechanism according to a preset monitoring period, receive an invoice state sent by the third party mechanism, and generate risk information according to the invoice state; the risk information is used for representing the risk degree of the invoice state of the invoice information corresponding to the monitoring return code;

the risk forwarding module 46 is configured to obtain invoice information corresponding to the monitoring return code from the monitoring table, obtain a terminal number corresponding to the invoice information from the channel monitoring rule table, and send risk information to a channel end corresponding to the channel number.

Optionally, the invoice monitoring and processing device 4 includes:

A front-end query module 47, configured to send a risk query page to the front-end, and receive front-end attribute information and query information sent by the front-end according to the risk query page; if the front-end attribute information is determined to have the query authority, acquiring risk information from a preset risk information table by the query information, and inputting the acquired risk information into a preset risk early warning template to obtain a risk pre-warning message; the risk pre-warning message is sent to the front end, and the front end is controlled to render the risk pre-warning message, so that a risk pre-warning page is obtained; the risk early warning page is a network page for displaying risk information.

The interface end query module 48 is configured to receive a query message sent by the interface end, and receive interface end attribute information and query information sent by the interface end according to the risk query page; if the attribute information of the interface terminal has the query authority, the query information acquires risk information from a preset risk information table and sends the risk information to the interface terminal.

Example 4:

fig. 5 is a block diagram of a computer device, which is shown according to an exemplary embodiment, the computer device 5 may be a control circuit in the information management system 1, which refers to one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic element implementations in the information management system for performing the invoice monitoring processing method.

Specifically, the computer device 5 includes: a processor 52 and a memory 51 communicatively coupled to the processor 52; the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory 51 to implement the above-mentioned invoice monitoring and processing method, where the components of the invoice monitoring and processing apparatus may be dispersed in different computer devices, and the computer device 5 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including a stand-alone server, or a server cluster formed by a plurality of application servers) for executing a program, and so on. The computer device of the present embodiment includes at least, but is not limited to: a memory 51, a processor 52, which may be communicatively coupled to each other via a system bus, as shown in fig. 5. It should be noted that fig. 5 only shows a computer device with components-but it should be understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead. In the present embodiment, the memory 51 (i.e., readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 51 may be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the memory 51 may also be an external storage device of a computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like. Of course, the memory 51 may also include both internal storage units of the computer device and external storage devices. In this embodiment, the memory 51 is generally used to store an operating system installed in a computer device and various application software, such as program codes of the invoice monitoring processing apparatus of the third embodiment. Further, the memory 51 may also be used to temporarily store various types of data that have been output or are to be output. Processor 52 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 52 is typically used to control the overall operation of the computer device. In this embodiment, the processor 52 is configured to execute the program code or process data stored in the memory 51, for example, execute the invoice monitoring processing device, so as to implement the invoice monitoring processing method of the above embodiment.

The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional modules described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or processor to perform some of the steps of the methods of the various embodiments of the application. It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU for short), other general purpose processors, digital signal processor (Digital Signal Processor, DSP for short), application specific integrated circuit (Application Specific Integrated Circuit, ASIC for short), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution. The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile memory NVM, such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk or optical disk, etc.

To achieve the above object, the present application also provides a computer-readable storage medium such as a flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application store, etc., on which computer-executable instructions are stored, which when executed by the processor 52, perform the corresponding functions. The computer-readable storage medium of the present embodiment is for storing computer-executable instructions for implementing the invoice monitoring processing method, which when executed by the processor 52 implement the invoice monitoring processing method of the above-described embodiment.

The storage medium may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). It is also possible that the processor and the storage medium reside as discrete components in a computer device or a master device.

The application provides a computer program product, which comprises a computer program, wherein the computer program realizes the invoice monitoring processing method when being executed by a processor.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. An invoice monitoring and processing method, which is characterized by comprising the following steps:

2. The invoice monitoring and processing method according to claim 1, wherein the channel end comprises a front end;

3. The invoice monitoring and processing method according to claim 1, wherein the channel end comprises an interface end;

4. The invoice monitoring processing method according to claim 1, wherein obtaining a channel monitoring rule table corresponding to the channel end, updating the monitoring rule in the channel monitoring rule table according to the monitoring rule in the monitoring list, comprises:

5. The invoice monitoring processing method according to claim 1, wherein updating the monitoring rule of the monitoring table according to the monitoring rule of the monitoring list includes:

6. The invoice monitoring and processing method according to claim 1, wherein transmitting at least one invoice information in the monitoring table to a third party authority, receiving a monitoring return code corresponding to each invoice information transmitted by the third party authority, and entering at least one monitoring return code into the monitoring table, comprises:

7. The invoice monitoring and processing method according to claim 1, wherein the steps of transmitting the monitoring return code in the monitoring table to the third party mechanism according to a preset monitoring period, and receiving the invoice status transmitted by the third party mechanism include:

8. The invoice monitoring and processing method according to claim 7, wherein generating risk information according to the invoice status includes:

9. The invoice monitoring and processing method according to claim 1, wherein transmitting the risk information to a channel end corresponding to the channel number includes:

10. The invoice monitoring and processing method according to claim 1, wherein the channel end comprises a front end;

11. An invoice monitoring and processing device, comprising:

12. A computer device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1 to 10.

13. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1 to 10.