CN113592571A - Bill issuing early warning method, device, equipment and computer readable medium - Google Patents

Bill issuing early warning method, device, equipment and computer readable medium Download PDF

Info

Publication number
CN113592571A
CN113592571A CN202110848022.3A CN202110848022A CN113592571A CN 113592571 A CN113592571 A CN 113592571A CN 202110848022 A CN202110848022 A CN 202110848022A CN 113592571 A CN113592571 A CN 113592571A
Authority
CN
China
Prior art keywords
information
bill
ticket
user portrait
data
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
Application number
CN202110848022.3A
Other languages
Chinese (zh)
Inventor
胡海龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Century Trading Co Ltd, Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN202110848022.3A priority Critical patent/CN113592571A/en
Publication of CN113592571A publication Critical patent/CN113592571A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Commerce
    • G06Q30/04Billing or invoicing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2457Query processing with adaptation to user needs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28Databases characterised by their database models, e.g. relational or object models
    • G06F16/284Relational databases

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Finance (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computational Linguistics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application discloses a bill issuing early warning method, a bill issuing early warning device, bill issuing equipment and a computer readable medium, and relates to the technical field of computers, wherein the method comprises the following steps: receiving a bill making request, and generating pre-drawing bill information corresponding to the bill making request; generating user portrait data according to the pre-drawing ticket information; generating corresponding relation data of the bill issuing time and the user portrait data; in response to determining that the ticket issuing request is abnormal based on the correspondence data, the ticket issuing request is intercepted. Therefore, whether the invoicing is abnormal or not is determined according to the corresponding relation between the bill making time determined by the generated user portrait data and the user portrait data, the order with the wrong invoicing is predicted in advance, early warning and interception are carried out before the invoicing, the success rate of the invoicing of the value-added tax bill data is improved, the freight loss caused by the wrong invoicing of enterprises is reduced, and the user experience is improved.

Description

Bill issuing early warning method, device, equipment and computer readable medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a computer readable medium for issuing a bill with an early warning.
Background
At present, when a value added tax paper bill is issued, if the issuing is wrong, the user needs to find the issuing mistake after receiving the paper bill, so that the issuing cost is high.
In the process of implementing the present application, the inventor finds that at least the following problems exist in the prior art:
when invoicing, the problem of invoicing can not be predicted in advance, the problem of invoicing can not be intercepted in advance or the interception efficiency is not high, so that the resource waste is caused, and the invoicing efficiency is low.
Disclosure of Invention
In view of this, embodiments of the present application provide a method, an apparatus, a device, and a computer readable medium for billing a bill, which can solve the problems that whether billing has a problem cannot be predicted in advance, billing with a problem cannot be intercepted in advance, or interception efficiency is not high, which causes resource waste and billing efficiency to be low in the prior art.
In order to achieve the above object, according to an aspect of an embodiment of the present application, there is provided a method for issuing an early warning on a bill, including:
receiving a bill making request, and further generating pre-drawing bill information corresponding to the bill making request;
generating user portrait data according to the pre-drawing ticket information;
generating corresponding relation data of the bill issuing time and the user portrait data;
in response to determining that the ticket issuing request is abnormal based on the correspondence data, the ticket issuing request is intercepted.
Optionally, generating pre-proposed ticket information corresponding to the ticket issuing request includes:
acquiring transaction information corresponding to the bill making request;
and generating the pre-booking ticket information based on the transaction information.
Optionally, generating the pre-vote information includes:
calling a ticket extraction information template to determine a corresponding field value according to a preset field and transaction information in the ticket extraction information template so as to generate ticket extraction information;
generating order list information according to the ticket extraction information;
and generating the pre-ticket-drawing information based on the ticket-drawing information and the order list information.
Optionally, generating the pre-vote information further includes:
splitting each report information corresponding to the order list information based on a preset splitting dimension to obtain splitting information;
and aggregating the split information to generate the pre-proposed ticket information.
Optionally, generating user representation data comprises:
acquiring corresponding user information according to the pre-ticket-drawing information;
acquiring corresponding historical user portrait data based on the user information;
and updating the pre-drawing ticket information to historical user portrait data so as to generate user portrait data with different dimensions.
Optionally, generating data of correspondence between the billing time and the user portrait data includes:
extracting user portrait data in a preset time period, and further determining bill issuing time and a corresponding user portrait data value of the user portrait data in the preset time period;
and drawing a corresponding relation curve chart of the bill making time and the user portrait data value according to the bill making time and the corresponding user portrait data value, and further determining the corresponding relation curve chart as corresponding relation data of the bill making time and the user portrait data.
Optionally, determining that the ticket issuing request is abnormal based on the correspondence data includes:
determining the change information of the user portrait data value in the target time period according to the corresponding relation curve graph;
determining an abnormal time period according to the change information;
and determining that the bill issuing request is abnormal in response to determining that the time corresponding to the bill issuing request is within the abnormal time period.
Optionally, determining the abnormal time period according to the change information includes:
determining the curvature corresponding to the change information;
and determining the curvatures which are larger than a preset threshold value in the curvatures, and determining the time periods corresponding to the curvatures which are larger than the preset threshold value as abnormal time periods.
In addition, this application still provides a bill has offered early warning device, includes:
the receiving unit is configured to receive the bill making request and further generate the pre-drawing bill information corresponding to the bill making request;
a user portrait data generation unit configured to generate user portrait data based on the pre-roll ticket information;
a correspondence data generation unit configured to generate correspondence data of the ticket issuing time and the user portrait data;
an interception unit configured to intercept the ticket issuing request in response to determining that the ticket issuing request is abnormal based on the correspondence data.
Optionally, the receiving unit is further configured to:
acquiring transaction information corresponding to the bill making request;
and generating the pre-booking ticket information based on the transaction information.
Optionally, the receiving unit is further configured to:
calling a ticket extraction information template to determine a corresponding field value according to a preset field and transaction information in the ticket extraction information template so as to generate ticket extraction information;
generating order list information according to the ticket extraction information;
and generating the pre-ticket-drawing information based on the ticket-drawing information and the order list information.
Optionally, the receiving unit is further configured to:
splitting each report information corresponding to the order list information based on a preset splitting dimension to obtain splitting information;
and aggregating the split information to generate the pre-proposed ticket information.
Optionally, the user representation data generating unit is further configured to:
acquiring corresponding user information according to the pre-ticket-drawing information;
acquiring corresponding historical user portrait data based on the user information;
and updating the pre-drawing ticket information to historical user portrait data so as to generate user portrait data with different dimensions.
Optionally, the correspondence data generation unit is further configured to:
extracting user portrait data in a preset time period, and further determining bill issuing time and a corresponding user portrait data value of the user portrait data in the preset time period;
and drawing a corresponding relation curve chart of the bill making time and the user portrait data value according to the bill making time and the corresponding user portrait data value, and further determining the corresponding relation curve chart as corresponding relation data of the bill making time and the user portrait data.
Optionally, the intercepting unit is further configured to:
determining the change information of the user portrait data value in the target time period according to the corresponding relation curve graph;
determining an abnormal time period according to the change information;
and determining that the bill issuing request is abnormal in response to determining that the time corresponding to the bill issuing request is within the abnormal time period.
Optionally, the intercepting unit is further configured to:
determining the curvature corresponding to the change information;
and determining the curvatures which are larger than a preset threshold value in the curvatures, and determining the time periods corresponding to the curvatures which are larger than the preset threshold value as abnormal time periods.
In addition, this application still provides a bill has opened early warning electronic equipment, includes: one or more processors; and a storage device for storing one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the ticketing warning method as described above.
In addition, the application also provides a computer readable medium, on which a computer program is stored, and when the program is executed by a processor, the method for issuing an early warning for a bill is realized.
One embodiment of the above invention has the following advantages or benefits: in the method, under the condition of issuing the paper value-added tax bill, the pre-bill information corresponding to the bill issuing request is generated by receiving the bill issuing request; calling an intelligent analysis engine to generate user portrait data according to the pre-proposed ticket information; calling a ticket raising alarm interception engine to generate corresponding relation data of the ticket making time and the user portrait data; in response to determining that the ticket issuing request is abnormal based on the correspondence data, the ticket issuing request is intercepted. Therefore, whether the invoicing is abnormal or not is determined according to the corresponding relation between the bill making time determined by the generated user portrait data and the user portrait data, and the abnormal invoicing is intercepted. The method can realize that the order with the wrong invoicing is predicted in advance, early warning and interception are carried out before real invoicing, the success rate of invoicing of the value-added tax invoice is improved, the freight loss of an enterprise caused by the wrong invoicing is reduced, and the user experience is improved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a further understanding of the application and are not to be construed as limiting the application. Wherein:
fig. 1 is a schematic view of a main flow of a ticket issuing warning method according to a first embodiment of the present application;
fig. 2 is a schematic view of a main flow of a ticket issuing warning method according to a second embodiment of the present application;
fig. 3 is a schematic view of an application scenario of a note issuing early warning method according to a third embodiment of the present application;
fig. 4 is a schematic diagram of main units of a ticket issuing warning apparatus according to an embodiment of the present application;
FIG. 5 is an exemplary system architecture diagram to which embodiments of the present application may be applied;
fig. 6 is a schematic structural diagram of a computer system suitable for implementing the terminal device or the server according to the embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a main flow of a bill issuing warning method according to a first embodiment of the present application, and as shown in fig. 1, the bill issuing warning method includes:
step S101, receiving a bill making request, and further generating pre-drawing bill information corresponding to the bill making request.
The bill may include an invoice or a receipt, and the present application does not limit the specific form of the bill.
In this embodiment, an execution subject (for example, a server) of the ticket issuing early warning method may receive a ticket issuing request from a terminal device (for example, a smart phone, a tablet computer, or the like) through a wired connection or a wireless connection. In particular, it may be a request for making a paper ticket. The execution subject, upon receiving the ticket issuing request, may generate corresponding pre-roll ticket information based on the ticket issuing request. Specifically, the pre-booking information may be information generated by processing transaction information purchased by the user, and may specifically include information of a ticket collector, information of a buyer, information of a seller, an amount of invoicing, and the like.
In this embodiment, generating the pre-booking note information corresponding to the note issuing request includes:
and acquiring the transaction information corresponding to the bill making request. The transaction information may be, for example, order information, and may contain basic purchase information such as the name of the item purchased, the quantity, the item code, the item price, the consignee and harvest address, whether a special or general ticket is issued, etc.
And generating the pre-booking ticket information based on the transaction information. After acquiring the transaction information, the executive body may acquire qualification information of the corresponding seller (e.g., a company name, a taxpayer identification number, a registered phone number, a registered address, a bank number, an issuer of an account) based on the transaction information, whether a plurality of orders are combined, a billing mode of the orders, whether the orders are mailed or taken after successful billing, and the like, and further invoke a bill information assembly system to convert the information acquired based on the transaction information into standard format data required for billing. The standard format data, that is, the billing information data meeting the enterprise requirements, for example, the converted standard format data is:
{ "orderNo": 1234, "money": 122, "skuList": [ { "skuName": apple "}. Wherein orderNo is order number, money is money amount, skuList is inventory list, and skuName is name corresponding to commodity code.
Furthermore, the execution main body may assemble the converted standard format data to generate pre-ticket-submission information, and generate a bill of lading, where the bill of lading may be T001.
In some optional implementation manners of this embodiment, generating the pre-vote information includes:
and calling the ticket extraction information template to determine a corresponding field value according to a preset field and the transaction information in the ticket extraction information template so as to generate the ticket extraction information.
For example, the preset fields may include company name, bill number, biller, ticket type, amount of the bill, time of the bill, consolidated billing, taxpayer identification number, and ticket heading. The field value corresponding to the preset field may be a company name: XX corporation; the number of the bill of newspaper: t001; and (4) billing party: XX division, Inc.; the bill type: value added tax special bills; the reporting amount is as follows: 222, c; reporting time: 2021-04-2817: 20: 08; merging and invoicing: is that; taxpayer identification number: XXM; raising the bill head: XX company.
And generating order list information according to the ticket drawing information.
For example, the executing entity may determine a corresponding order number according to the bill number of each piece of bill information, and then generate the order list information based on the head-up, the order amount, the real-time amount, and the order placing time of the bill corresponding to each determined order number.
Order list information, for example:
order number: t001; raising the bill head: XX corporation; amount of the order: 105; real open money 105; the order-giving time is as follows: 2021-03-3013:25:05
Order number: t002; raising the bill head: XX corporation; amount of the order: 18; actual opening of the gold account 18; the order-giving time is as follows: 2021-03-3013:25:06
Order number: t003; raising the bill head: XX corporation; amount of the order: 99; real opening of the gold 99; the order-giving time is as follows: 2021-03-3013:25:07
And generating the pre-ticket-drawing information based on the ticket-drawing information and the order list information.
The pre-ticket-drawing information comprises ticket-drawing information and order list information.
After generating the pre-vote information and the order list information, the executing body may combine to generate the pre-vote information.
In some optional implementation manners of this embodiment, generating the pre-vote information further includes:
and splitting each report information corresponding to the order list information based on a preset splitting dimension to obtain splitting information.
Specifically, after the execution subject generates the order list information, each report information in the order list information may be verified, and it is specifically verified whether the mandatory information item in the report information is completely filled and verified on the invoicing qualification of the user. If the executive main body determines that the information required item is not completely filled or the user invoicing qualification verification is not passed, or the executive main body determines that the information required item is not completely filled and the user invoicing qualification verification is not passed, the executive main body directly prompts the failure of the report of the pre-invoicing information, and directly skips and does not process the pre-invoicing information, so that the follow-up analysis of an intelligent analysis engine is avoided, the resource waste is reduced, and the processing efficiency of the invoicing system is improved.
When the execution subject determines that the bill of lading information passes the verification, the bill of lading information can be split, and the split dimension can be specifically split according to the split dimension of the user bill of lading, wherein the split dimension can specifically comprise dimensions such as order number, invoicing party, invoicing address, invoicing party, invoicing amount and invoicing time. For example, the executing agent may determine a parent order and a corresponding child order according to each order number in the order list information, and then split the corresponding ticket drawing information according to the determined parent order and the determined child order, so as to obtain split information.
For example, the splitting information may include (where the order corresponding to the order number T001 is a parent order, and the orders corresponding to the order numbers T0011 and T0012 are child orders of the order corresponding to the order number T001), specifically:
order number: t001; raising the bill head: XX corporation; amount of the order: 105; real open money 105; the order-giving time is as follows: 2021-03-3013:25:05
Order number: t0011; raising the bill head: XX corporation; amount of the order: 6; real opening of gold amount 6; the order-giving time is as follows: 2021-03-3013:25:06
Order number: t0012; raising the bill head: XX corporation; amount of the order: 99; real opening of the gold 99; the order-giving time is as follows: 2021-03-3013:25:07
And aggregating and splitting the information to generate the pre-proposed ticket information, wherein the pre-proposed ticket information can comprise user information, such as the information of a mobile phone number, an identity card number and the like of the user.
The aggregation and splitting information may be information for aggregating sub-transactions placed in the same parent order. For example, order number: t001, T0011 and T0012; raising the bill head: XX corporation; amount of the order: 105. 18, 99; real open money 105, 18, 99; the order-giving time is as follows: 2021-03-3013: 25:05, 2021-03-3013: 25:06, 2021-03-3013: 25:07, that is, the pre-extracted ticket information, which is only one way of aggregating the split information, and the way of aggregating the split information is not particularly limited in this application.
Step S102, generating user portrait data according to the pre-proposed ticket information.
The intelligent analysis engine is a core component which can analyze information and can generate portrait data based on the information and is supported by a program written by a developer.
After the execution main body obtains the pre-ticket-drawing information, the intelligent analysis engine can be called to extract user information in the pre-ticket-drawing information, such as a mobile phone number, an identity card number and the like of a user. The executive may then retrieve corresponding historical user representation data based on the user information. The pre-extracted ticket information is then updated to historical user representation data to generate user representation data. The user image data may include, for example, invoicing party information and billing address information corresponding to the user information. Billing amount information, etc. For example, the intelligent analysis engine may analyze all the ticket information currently applied by the current user and applied by the history, and further draw the application ticket portrait data of the user.
Step S103, generating corresponding relation data of the bill issuing time and the user portrait data.
The ticket raising alarm intercepting engine may be a core component supported by a program written by a developer for analyzing user portrait data output by the intelligent analysis engine.
The execution main body can call the ticket raising alarm interception engine to judge whether the current application information is abnormal or not by combining the user portrait data provided by the intelligent analysis engine, and if the current application information is abnormal, the execution main body gives an alarm and raises the ticket to intercept. The method is particularly used for combining abnormal attribute information of an intelligent analysis engine (for example, an invoicing party is supposed to be company A, but an actual invoicing company is supposed to be company B, and the abnormal attribute belongs to the abnormal information.
After the intelligent analysis engine generates user image data (corresponding to each dimension data, which can include dimensions such as order number, invoicing party, invoicing address, invoicing party, invoicing amount, invoicing time and the like), the execution main body can call the ticket raising alarm interception engine to perform early warning analysis based on the user image data. Specifically, in this embodiment, generating the correspondence data between the billing time and the user portrait data includes:
the execution main body can call the ticket raising alarm interception engine to extract user portrait data in a preset time period, and further determine the billing time of the user portrait data in the preset time period and a corresponding user portrait data value.
For example, the ticket raising alarm interception engine may extract the last 10 minutes of user portrait data for early warning interception analysis, and the data of the last time is configurable, so as to facilitate later dynamic adjustment of the extraction time.
According to the bill making time and the corresponding user portrait data value (for example, when the user portrait data is the bill making party, the corresponding user portrait data value is company A, company B, company C, etc.), drawing the corresponding relation curve graph of the bill making time and the user portrait data value, namely, sequentially connecting the user portrait data value corresponding to each bill making time according to the time sequence to generate the corresponding relation curve graph of the bill making time and the user portrait data value.
For example, a time of 8:00 for a ticket offer corresponds to company A; 8:10 corresponds to company B; 8:20 corresponds to company C. The executive body can sequentially connect companies corresponding to 8:00-8:10-8:20 in the same coordinate system, namely sequentially connect nodes corresponding to company A, company B and company C in the same coordinate system, and further generate a corresponding relation curve chart of the bill issuing time and the user portrait data value. For example, company a, company B, and company C may be sequentially located from bottom to top in the ordinate of the same coordinate system, and the present application does not specifically limit the positions of the ordinate where company a, company B, and company C are located in the same coordinate system. And determining the corresponding relation curve graph as corresponding relation data of the bill making time and the user portrait data.
In this embodiment, determining that the ticket issuing request is abnormal based on the correspondence data includes:
and determining the change information of the user portrait data value in the target time period according to the corresponding relation curve graph.
For example, the target time period may be a time period in a graph of correspondence between the optional billing time and the user portrait data value, and may be, for example, a time period from 8:00 to 8: 20. The execution body may acquire curvature information of a curve for a period of 8:00-8:20, i.e., change information of the user portrait data value within a target period.
And determining an abnormal time period according to the change information.
Specifically, determining an abnormal time period according to the change information includes:
determining the curvature corresponding to the change information; and determining the curvatures which are larger than a preset threshold value in the curvatures, and determining the time periods corresponding to the curvatures which are larger than the preset threshold value as abnormal time periods.
When the execution main body determines that the curvature of a curve corresponding to a certain time period (for example, the time period of 8:10-8: 20) is greatly increased and is greater than a preset threshold value in the time period of 8:00-8:20 according to the change information of the user portrait data value in the target time period, the execution main body can determine that the billing data in the certain time period is abnormal and needs to perform interception alarm. This certain period is determined as an abnormal period.
And determining that the bill issuing request is abnormal in response to determining that the time corresponding to the bill issuing request is within the abnormal time period.
When the execution subject determines that the time corresponding to the received ticket issuing request is within the determined abnormal time period, it may be determined that the ticket issuing request is abnormal.
Step S104, responding to the abnormal bill making request determined based on the corresponding relation data, and intercepting the bill making request.
When the execution subject determines that the bill making request is abnormal, the execution subject can intercept the bill making request and store abnormal data (for example, the making party should be company A, but the actual making party should be company B, which belongs to the abnormal data).
In the embodiment, the pre-bill information corresponding to the bill making request is generated by receiving the bill making request; generating user portrait data according to the pre-drawing ticket information; generating corresponding relation data of the bill issuing time and the user portrait data; in response to determining that the ticket issuing request is abnormal based on the correspondence data, the ticket issuing request is intercepted. Therefore, whether the invoicing is abnormal or not is determined according to the corresponding relation between the bill making time determined by the generated user portrait data and the user portrait data, and the abnormal invoicing is intercepted. The method can realize that the order with the wrong invoicing is predicted in advance, early warning and interception are carried out before real invoicing, the success rate of invoicing of the value-added tax invoice is improved, the freight loss of an enterprise caused by the wrong invoicing is reduced, and the user experience is improved.
Fig. 2 is a schematic main flow chart of a bill issuing early warning method according to a second embodiment of the present application, and as shown in fig. 2, the bill issuing early warning method includes:
step S201, receiving a bill making request, and further generating pre-drawing bill information corresponding to the bill making request.
Step S202, generating user portrait data according to the pre-proposed ticket information.
The principle of step S201 to step S202 is similar to that of step S101 to step S102, and is not described here again.
Specifically, step S202 can also be realized by step S2021 to step S2023:
step S2021, acquiring corresponding user information according to the pre-ticket-drawing information.
In step S2022, corresponding historical user image data is acquired based on the user information.
Step S2023, updating the pre-drawing information to the historical user image data, and further generating user image data with different dimensions (e.g. dimensions of order number, invoicing party, invoicing address, invoicing party, invoicing amount, invoicing time, etc.). For example, the user portrait data of different dimensions may be:
time: 2021-05-21; the user: XX corporation; and (4) billing party: company A; billing amount: 300
Time: 2021-05-23; the user: XX corporation; and (4) billing party: company A; billing amount: 500
Time: 2021-05-25; the user: XX corporation; and (4) billing party: company B; billing amount: 1000
For example, the execution subject may invoke the intelligent analysis engine to extract the user information according to the bill of lading information provided upstream, so as to conveniently and accurately depict the billing model of the user's application. After the user information is acquired, historical user portrait data generated by the user can be acquired, and the historical user portrait data comprises mechanism information of invoicing, invoice receiving address information, invoice amount information and the like. Then, the executive body can maintain the billing information of the current application in the historical portrait information by combining the historical user portrait data, and enrich the user portrait data. According to different dimensions (such as invoicing party, invoicing address, invoicing party, invoicing amount, invoicing time and the like), generating user portrait data of different attributes such as invoicing party, invoicing address, invoicing party, invoicing amount, invoicing time and the like, and generating the invoicing party portrait according to the sequence of the user dimension reporting time.
According to the embodiment, the generated user portrait data can be more accurate by updating the pre-drawing ticket information corresponding to the currently received ticket making request into the historical user portrait data.
In step S203, data of correspondence between the billing time and the user portrait data is generated.
Step S204, responding to the abnormal bill making request determined based on the corresponding relation data, and intercepting the bill making request.
The principle of step S203 to step S204 is similar to that of step S103 to step S104, and is not described here again.
In addition, the execution main body can call a bill early warning information display system, operation management and interface display are carried out on the warning information, and operation personnel and system maintenance personnel can check the warning information conveniently. The early warning data generated by the bill early warning information display system can be stored in a database in real time, and the bill early warning information display is that the early warning information generated by the reading system is displayed on a page in real time for operation or operation and maintenance personnel to check.
Fig. 3 is a schematic view of an application scenario of a ticket issuing warning method according to a third embodiment of the present application. The bill issuing early warning method can be applied to scenes that paper special bills are not intercepted or the intercepting efficiency is low when bills are issued. For example, as shown in fig. 3, a transaction system of an executing subject (which may be a server, for example) acquires transaction information. The executing entity may generate a ticket issuing request based on the transaction information. Then, the bill information assembly and reporting system of the executive body can generate corresponding pre-ticket-drawing information according to the received bill making request, and then generate corresponding report information according to the pre-ticket-drawing information. The bill of lading information may include: transaction information, reporting amount and qualification information. After generating the bill of lading information, the executing agent may invoke the intelligent analysis engine to generate user portrait data based on the bill of lading information. The user representation data may include organization information, amount information, etc., and the specific content of the user representation data is not limited in this application. After generating the user portrait data, the executive body can call a bill early warning interception system to judge whether to intercept financial bill information corresponding to a bill to be issued. The financial bill information may include transaction information, amount of the submission, and qualification information. When the financial bill information is not intercepted, the execution subject can call the bill issuing system to issue the bill corresponding to the financial bill information. When the financial bill information is intercepted, the execution main body can call the bill early warning interception information display system to display the intercepted financial bill information (specifically displayed information such as early warning statement bill, corresponding organization information for bill making, amount information and the like) so as to be checked by an operator.
Fig. 4 is a schematic diagram of main units of a ticket issuing warning apparatus according to an embodiment of the present application. As shown in fig. 4, the ticket issuing warning apparatus includes a receiving unit 401, a user portrait data generating unit 402, a correspondence data generating unit 403, and an intercepting unit 404.
The receiving unit 401 is configured to receive a ticket issuing request, and further generate pre-proposed ticket information corresponding to the ticket issuing request.
A user representation data generating unit 402 configured to generate user representation data based on the pre-roll ticket information.
A correspondence data generation unit 403 configured to generate correspondence data of the ticket issuing time and the user portrait data.
An interception unit 404 configured to intercept the ticket issuing request in response to determining that the ticket issuing request is abnormal based on the correspondence data.
In some embodiments, the receiving unit 401 is further configured to: acquiring transaction information corresponding to the bill making request; and generating the pre-booking ticket information based on the transaction information.
In some embodiments, the receiving unit 401 is further configured to: calling a ticket extraction information template to determine a corresponding field value according to a preset field and transaction information in the ticket extraction information template so as to generate ticket extraction information; generating order list information according to the ticket extraction information; and generating the pre-ticket-drawing information based on the ticket-drawing information and the order list information.
In some embodiments, the receiving unit 401 is further configured to: splitting each report information corresponding to the order list information based on a preset splitting dimension to obtain splitting information; and aggregating the split information to generate the pre-proposed ticket information.
In some embodiments, user representation data generation unit 402 is further configured to: acquiring corresponding user information according to the pre-ticket-drawing information; acquiring corresponding historical user portrait data based on the user information; and updating the pre-drawing ticket information to historical user portrait data so as to generate user portrait data with different dimensions.
In some embodiments, the correspondence data generation unit 403 is further configured to: extracting user portrait data in a preset time period, and further determining bill issuing time and a corresponding user portrait data value of the user portrait data in the preset time period; and drawing a corresponding relation curve chart of the bill making time and the user portrait data value according to the bill making time and the corresponding user portrait data value, and further determining the corresponding relation curve chart as corresponding relation data of the bill making time and the user portrait data.
In some embodiments, intercept unit 404 is further configured to: determining the change information of the user portrait data value in the target time period according to the corresponding relation curve graph; determining an abnormal time period according to the change information; and determining that the bill issuing request is abnormal in response to determining that the time corresponding to the bill issuing request is within the abnormal time period.
In some embodiments, intercept unit 404 is further configured to: determining the curvature corresponding to the change information; and determining the curvatures which are larger than a preset threshold value in the curvatures, and determining the time periods corresponding to the curvatures which are larger than the preset threshold value as abnormal time periods.
It should be noted that, in the present application, the bill issuing early warning method and the bill issuing early warning apparatus have a corresponding relationship in the specific implementation content, so the repeated content is not described again.
Fig. 5 illustrates an exemplary system architecture 500 to which the ticket issuing warning method or the ticket issuing warning apparatus according to the embodiment of the present application can be applied.
As shown in fig. 5, the system architecture 500 may include terminal devices 501, 502, 503, a network 504, and a server 505. The network 504 serves to provide a medium for communication links between the terminal devices 501, 502, 503 and the server 505. Network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 501, 502, 503 to interact with a server 505 over a network 504 to receive or send messages or the like. The terminal devices 501, 502, 503 may have various communication client applications installed thereon, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (for example only).
The terminal devices 501, 502, 503 may be various electronic devices having a ticketing warning processing screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 505 may be a server (i.e., an executing agent) that provides various services, such as a back-office management server (for example only) that supports ticketing requests submitted by users using the terminal devices 501, 502, 503. The background management server can receive the bill making request and further generate the pre-drawing bill information corresponding to the bill making request; generating user portrait data according to the pre-proposed ticket information; generating corresponding relation data of the bill issuing time and the user portrait data; in response to determining that the ticket issuing request is abnormal based on the correspondence data, the ticket issuing request is intercepted. Therefore, whether the invoicing is abnormal or not is determined according to the corresponding relation between the bill making time determined by the generated user portrait data and the user portrait data, and the abnormal invoicing is intercepted. The method can realize that the order with the wrong invoicing is predicted in advance, early warning and interception are carried out before real invoicing, the success rate of invoicing of the value-added tax invoice is improved, the freight loss of an enterprise caused by the wrong invoicing is reduced, and the user experience is improved.
It should be noted that the method for providing a warning of a ticket issuing according to the embodiment of the present application is generally executed by the server 505, and accordingly, the warning device for providing a ticket issuing is generally disposed in the server 505.
It should be understood that the number of terminal devices, networks, and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use in implementing a terminal device of an embodiment of the present application. The terminal device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data necessary for the operation of the computer system 600 are also stored. The CPU601, ROM602, and RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output section 607 including a signal processing section such as a Cathode Ray Tube (CRT), a liquid crystal credit authorization inquiry processor (LCD), and the like, and a speaker and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.
In particular, according to embodiments disclosed herein, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments disclosed herein include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present application are executed when the computer program is executed by the Central Processing Unit (CPU) 601.
It should be noted that the computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a receiving unit, a user image data generating unit, a correspondence data generating unit, and an intercepting unit. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs, and when the one or more programs are executed by one device, the device receives a ticket making request, and further generates pre-drawing ticket information corresponding to the ticket making request; generating user portrait data according to the pre-drawing ticket information; generating corresponding relation data of the bill issuing time and the user portrait data; in response to determining that the ticket issuing request is abnormal based on the correspondence data, the ticket issuing request is intercepted. Therefore, whether the invoicing is abnormal or not is determined according to the corresponding relation between the bill making time determined by the generated user portrait data and the user portrait data, and the abnormal invoicing is intercepted.
According to the technical scheme of the embodiment of the application, the order with the wrong invoicing can be predicted in advance, early warning and interception are carried out before real invoicing, the success rate of invoicing of the value-added tax receipt is improved, the freight loss of an enterprise caused by the wrong invoicing is reduced, and meanwhile, the user experience is improved.
The above-described embodiments should not be construed as limiting the scope of the present application. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (11)

1. A bill issuing early warning method is characterized by comprising the following steps:
receiving a bill making request, and further generating pre-drawing bill information corresponding to the bill making request;
generating user portrait data according to the pre-proposed ticket information;
generating corresponding relation data of the bill issuing time and the user portrait data;
intercepting the ticket issuing request in response to determining that the ticket issuing request is abnormal based on the correspondence data.
2. The method of claim 1, wherein the generating of the pre-roll ticket information corresponding to the ticketing request comprises:
acquiring transaction information corresponding to the bill making request;
and generating pre-booking ticket information based on the transaction information.
3. The method of claim 2, wherein generating the pre-vote information comprises:
calling a ticket extraction information template to determine a corresponding field value according to a preset field in the ticket extraction information template and the transaction information so as to generate ticket extraction information;
generating order list information according to the ticket extraction list information;
and generating the pre-ticket-drawing information based on the ticket-drawing information and the order list information.
4. The method of claim 3, wherein generating the pre-vote information further comprises:
splitting each report information corresponding to the order list information based on a preset splitting dimension to obtain splitting information;
and aggregating the split information to generate the pre-proposed ticket information.
5. The method of claim 1, wherein generating user representation data comprises:
acquiring corresponding user information according to the pre-ticket-drawing information;
acquiring corresponding historical user portrait data based on the user information;
and updating the pre-drawing ticket information to the historical user portrait data so as to generate user portrait data with different dimensions.
6. The method of claim 1, wherein generating the correspondence data between the ticket issuance time and the user representation data comprises:
extracting user portrait data in a preset time period, and further determining bill issuing time and a corresponding user portrait data value of the user portrait data in the preset time period;
and drawing a corresponding relation curve chart of the bill making time and the user portrait data value according to the bill making time and the corresponding user portrait data value, and further determining the corresponding relation curve chart as corresponding relation data of the bill making time and the user portrait data.
7. The method of claim 6, wherein said determining that the billing request is anomalous based on the correspondence data comprises:
determining the change information of the user portrait data value in the target time period according to the corresponding relation curve graph;
determining an abnormal time period according to the change information;
and determining that the bill making request is abnormal in response to determining that the time corresponding to the bill making request is within the abnormal time period.
8. The method of claim 7, wherein determining an abnormal time period from the variance information comprises:
determining the curvature corresponding to the change information;
and determining the curvatures which are larger than a preset threshold value in the curvatures, and determining the time periods corresponding to the curvatures which are larger than the preset threshold value as abnormal time periods.
9. The utility model provides a bill has an early warning device which characterized in that includes:
the receiving unit is configured to receive a bill making request and further generate pre-drawing bill information corresponding to the bill making request;
a user portrait data generation unit configured to generate user portrait data from the pre-proposed ticket information;
a correspondence data generation unit configured to generate correspondence data of a ticket issuing time and the user portrait data;
an interception unit configured to intercept the ticket issuing request in response to determining that the ticket issuing request is abnormal based on the correspondence data.
10. An electronic device for issuing an early warning for a bill, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.
11. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-8.
CN202110848022.3A 2021-07-27 2021-07-27 Bill issuing early warning method, device, equipment and computer readable medium Pending CN113592571A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110848022.3A CN113592571A (en) 2021-07-27 2021-07-27 Bill issuing early warning method, device, equipment and computer readable medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110848022.3A CN113592571A (en) 2021-07-27 2021-07-27 Bill issuing early warning method, device, equipment and computer readable medium

Publications (1)

Publication Number Publication Date
CN113592571A true CN113592571A (en) 2021-11-02

Family

ID=78250540

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110848022.3A Pending CN113592571A (en) 2021-07-27 2021-07-27 Bill issuing early warning method, device, equipment and computer readable medium

Country Status (1)

Country Link
CN (1) CN113592571A (en)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6058380A (en) * 1995-12-08 2000-05-02 Mellon Bank, N.A. System and method for electronically processing invoice information
US20080301018A1 (en) * 2007-05-31 2008-12-04 At & T Knowledge Ventures, L.P. Revenue assurance tool
CN105630785A (en) * 2014-10-27 2016-06-01 航天信息股份有限公司 Invoice use abnormity early-warning method and system
CN107949859A (en) * 2015-07-08 2018-04-20 美国联合包裹服务公司 For detecting system, the method and computer program product of charging exception
CN110175318A (en) * 2019-04-16 2019-08-27 中国平安财产保险股份有限公司 A kind of settlement of insurance claim attachment generation method and device
CN110458633A (en) * 2019-08-20 2019-11-15 东莞市盟大塑化科技有限公司 Invoice data generation method, system and computer equipment based on block chain technology
CN111768546A (en) * 2020-06-30 2020-10-13 新奥(中国)燃气投资有限公司 Method, device and system for automatically early warning abnormal enterprise invoices
CN112668041A (en) * 2020-12-17 2021-04-16 平安消费金融有限公司 Document file generation method and device, computer equipment and storage medium
CN112686742A (en) * 2020-12-24 2021-04-20 航天信息股份有限公司 Sales invoice risk early warning method and device, storage medium and electronic equipment
CN112700115A (en) * 2020-12-29 2021-04-23 航天信息股份有限公司 Risk identification method for invoice sales
CN112800848A (en) * 2020-12-31 2021-05-14 中电金信软件有限公司 Structured extraction method, device and equipment of information after bill identification
CN112990991A (en) * 2019-12-18 2021-06-18 北京沃东天骏信息技术有限公司 Method and device for merging invoices
CN113034778A (en) * 2019-12-24 2021-06-25 航天信息股份有限公司 Invoice information approval method and system

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6058380A (en) * 1995-12-08 2000-05-02 Mellon Bank, N.A. System and method for electronically processing invoice information
US20080301018A1 (en) * 2007-05-31 2008-12-04 At & T Knowledge Ventures, L.P. Revenue assurance tool
CN105630785A (en) * 2014-10-27 2016-06-01 航天信息股份有限公司 Invoice use abnormity early-warning method and system
CN107949859A (en) * 2015-07-08 2018-04-20 美国联合包裹服务公司 For detecting system, the method and computer program product of charging exception
CN110175318A (en) * 2019-04-16 2019-08-27 中国平安财产保险股份有限公司 A kind of settlement of insurance claim attachment generation method and device
CN110458633A (en) * 2019-08-20 2019-11-15 东莞市盟大塑化科技有限公司 Invoice data generation method, system and computer equipment based on block chain technology
CN112990991A (en) * 2019-12-18 2021-06-18 北京沃东天骏信息技术有限公司 Method and device for merging invoices
CN113034778A (en) * 2019-12-24 2021-06-25 航天信息股份有限公司 Invoice information approval method and system
CN111768546A (en) * 2020-06-30 2020-10-13 新奥(中国)燃气投资有限公司 Method, device and system for automatically early warning abnormal enterprise invoices
CN112668041A (en) * 2020-12-17 2021-04-16 平安消费金融有限公司 Document file generation method and device, computer equipment and storage medium
CN112686742A (en) * 2020-12-24 2021-04-20 航天信息股份有限公司 Sales invoice risk early warning method and device, storage medium and electronic equipment
CN112700115A (en) * 2020-12-29 2021-04-23 航天信息股份有限公司 Risk identification method for invoice sales
CN112800848A (en) * 2020-12-31 2021-05-14 中电金信软件有限公司 Structured extraction method, device and equipment of information after bill identification

Similar Documents

Publication Publication Date Title
US20220284082A1 (en) Authentication challenges based on fraud initiation requests
US11257134B2 (en) Supplier invoice reconciliation and payment using event driven platform
US20200265409A1 (en) Systems and methods to split bills and requests for payment from debit or credit account
US10650472B2 (en) Single use account pool processing system and method
US20240078596A1 (en) System and method for aggregating and presenting financial information
US11803854B1 (en) System and method for fraud detection using event driven architecture
US20200074562A1 (en) Systems and methods for generating product-merchant data links
CN111861745B (en) Service wind control method and device
CN113205402A (en) Account checking method and device, electronic equipment and computer readable medium
CN110942392A (en) Service data processing method, device, equipment and medium
CA3141753A1 (en) Real-time provisioning of targeted, alternative product information based on structured messaging data
CN112258306B (en) Account information checking method, device, electronic equipment and storage medium
CN115439264A (en) Insurance business customization method, device and system
CN110991992B (en) Processing method and device of business process information, storage medium and electronic equipment
CN113806400A (en) Financial data processing method and device, storage medium and electronic equipment
CN112241915A (en) Loan product generation method and device
CN115391343A (en) Bill data processing method and device, electronic equipment and storage medium
CN113592571A (en) Bill issuing early warning method, device, equipment and computer readable medium
CN111526184B (en) Business auditing method and device
US11625772B1 (en) System and method for providing real time financial account information using event driven architecture
CN114066615A (en) Trusted payment method, device, electronic equipment and storage medium
CN110992046A (en) Management method and device for aggregated payment and computer storage medium
US12008639B1 (en) System and method for closing financial accounts using event driven architecture
CN114997977B (en) Data processing method, device, electronic equipment and computer readable medium
US20230419279A1 (en) Systems and methods for real-time billpay using credit-based products

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