CN113034778A - Invoice information approval method and system - Google Patents
Invoice information approval method and system Download PDFInfo
- Publication number
- CN113034778A CN113034778A CN201911350832.5A CN201911350832A CN113034778A CN 113034778 A CN113034778 A CN 113034778A CN 201911350832 A CN201911350832 A CN 201911350832A CN 113034778 A CN113034778 A CN 113034778A
- Authority
- CN
- China
- Prior art keywords
- invoice
- information
- rule
- invoice information
- approval
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07D—HANDLING OF COINS OR VALUABLE PAPERS, e.g. TESTING, SORTING BY DENOMINATIONS, COUNTING, DISPENSING, CHANGING OR DEPOSITING
- G07D7/00—Testing specially adapted to determine the identity or genuineness of valuable papers or for segregating those which are unacceptable, e.g. banknotes that are alien to a currency
- G07D7/003—Testing specially adapted to determine the identity or genuineness of valuable papers or for segregating those which are unacceptable, e.g. banknotes that are alien to a currency using security elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
Landscapes
- Business, Economics & Management (AREA)
- Development Economics (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Computer Security & Cryptography (AREA)
- Economics (AREA)
- Finance (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides an invoice information approval method and an invoice information approval system, which are used for solving the problem of low approval efficiency in the prior art. The method comprises the following steps: receiving an approval request, wherein the approval request carries invoice information to be approved, and the invoice information is used for generating an electronic invoice; the invoice information is approved according to validation rules, which include at least one rule dynamically configured based on the plug-in form.
Description
Technical Field
The invention relates to the technical field of electronic invoices, in particular to an invoice information approval method and an invoice information approval system.
Background
In the current billing business handling, the invoice information corresponding to the request for approval initiated by the taxpayer needs to be approved, and the invoice can be billed after the approval is passed.
At present, some tax information management systems are usually used for performing stepwise approval on part of information included in invoice information, for example, after a system for recording basic information of taxpayers approves the identity of the taxpayer who initiates an approval request, a system for recording enterprise risk information approves the risk condition of an enterprise involved in the invoice information. In such a way, the approval needs to be completed by matching a plurality of systems, the time is long, the approval efficiency is low, and the billing efficiency is affected.
Disclosure of Invention
The invention provides an invoice information approval method and an invoice information approval system, which are used for solving the problem of low approval efficiency in the prior art.
In a first aspect, an embodiment of the present invention provides an invoice information approval method, including:
receiving an approval request, wherein the approval request carries invoice information to be approved, and the invoice information is used for generating an electronic invoice;
the invoice information is approved according to validation rules, which include at least one rule dynamically configured based on the form of the plug-in.
In an optional implementation manner, the approval request further carries signature information corresponding to the invoice information;
the authorizing the invoice information according to the validation rules includes:
verifying the invoice information according to the signature information;
and when the verification is determined to pass, the invoice information is approved according to the verification rule.
In an optional implementation manner, the validation rule includes a first rule that the number of invoices made by the ticket buyer in a preset period does not exceed a first number threshold;
the authorizing the invoice information according to the validation rules includes:
determining the billing quantity of the first ticket buyer in the preset period based on a file information base comprising historical billing records of the ticket buyer; the first ticket buyer is the ticket buyer indicated by the ticket buyer identifier contained in the invoice information;
and authorizing the billing amount of the first ticket buyer in the preset period according to the first rule.
In an optional implementation manner, the verification rule includes a second rule that the invoice limit does not exceed the first limit threshold;
the authorizing the invoice information according to the validation rules includes:
and authorizing the invoice quota contained in the invoice information according to the second rule.
In an optional implementation, the method further includes:
when the invoice information passes the approval of the verification rule, configuring an invoice identifier for the invoice information, wherein the invoice identifier comprises at least one of an invoice classification code, an invoice number and an invoice unique identification code;
and adding labels to the invoice information after the invoice identifier is configured.
In a second aspect, an embodiment of the present invention provides an invoice information approval system, including:
the receiving module is used for receiving an approval request, wherein the approval request carries invoice information to be approved, and the invoice information is used for generating an electronic invoice;
and the approval module is used for approving the invoice information according to a verification rule, wherein the verification rule comprises at least one rule dynamically configured based on a plug-in form.
In an optional implementation manner, the approval request further carries signature information corresponding to the invoice information;
the approval module is specifically configured to:
verifying the invoice information according to the signature information;
and when the verification is determined to pass, the invoice information is approved according to the verification rule.
In an optional implementation manner, the validation rule includes a first rule that the number of invoices made by the ticket buyer in a preset period does not exceed a first number threshold;
the approval module is specifically configured to:
determining the billing quantity of the first ticket buyer in the preset period based on a file information base comprising historical billing records of the ticket buyer; the first ticket buyer is the ticket buyer indicated by the ticket buyer identifier contained in the invoice information;
and authorizing the billing amount of the first ticket buyer in the preset period according to the first rule.
In an optional implementation manner, the verification rule includes a second rule that the invoice limit does not exceed the first limit threshold;
the approval module is specifically configured to:
and authorizing the invoice quota contained in the invoice information according to the second rule.
In an optional implementation, the system further includes:
the configuration module is used for configuring invoice identification for the invoice information when the invoice information passes the approval of the verification rule, wherein the invoice identification comprises at least one item of invoice classification code, invoice number and invoice unique identification code;
and the signing module is used for signing the invoice information after the invoice identifier is configured.
In a third aspect, an embodiment of the present invention provides an electronic device, including:
a memory and a processor;
a memory for storing program instructions;
and the processor is used for calling the program instructions stored in the memory and executing the method of any implementation mode of the first aspect according to the obtained program.
In a fourth aspect, the present invention provides a computer-readable storage medium storing computer instructions, which, when executed on a computer, cause the computer to perform the above method.
In the embodiment of the invention, when an approval request carrying the electronic invoice is received, the invoice information is approved according to the verification rule comprising at least one rule dynamically configured based on the plug-in form. The invoice information is approved uniformly by adopting the verification rule without processing the approval process by a plurality of systems, so that the flow can be simplified, and the approval efficiency of the invoice information is effectively improved; in addition, the embodiment of the invention can adjust the rules included in the verification rules by adding or deleting the plug-in, thereby realizing the dynamic deployment of the rules, having certain expandability and leading the approval mode to be more flexible.
Drawings
Fig. 1 is a schematic flow chart illustrating an invoice information approval method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an approval process according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an approval business model according to an embodiment of the present invention;
fig. 4 is a block diagram illustrating an invoice information approval system according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The plurality of the present invention means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. In addition, it should be understood that although the terms first, second, etc. may be used to describe various data in embodiments of the present invention, these data should not be limited by these terms. These terms are only used to distinguish the data from each other.
The embodiment of the invention provides an invoice information approval method and system, which are used for solving the problem of low approval efficiency in the prior art. The method and the system are based on the same inventive concept, and because the principles of solving the problems of the method and the system are similar, the implementation of the system and the method can be mutually referred, and repeated parts are not repeated.
Referring to fig. 1, an invoice information approval method provided for an embodiment of the present invention may be implemented by an approval system for approving invoice information, and the method includes:
step S101, an approval request is received, wherein the approval request carries invoice information to be approved, and the invoice information is used for generating an electronic invoice.
Wherein, the invoice information comprises the contents presented on the electronic invoice, such as ticket buyer information, seller information and purchase item information; the ticket buyer information and the seller information comprise respective enterprise names, taxpayer identification numbers, addresses, telephones, account opening lines, account numbers and the like; the purchase item information includes item name, amount, tax rate, tax amount, etc.
And S102, authorizing the invoice information according to the verification rule, wherein the verification rule comprises at least one rule dynamically configured based on the plug-in form.
The plug-in is a reusable program which can be packaged with custom service logic and can be flexibly started or stopped. In the embodiment of the invention, the execution logic of the rule for approving the invoice information is encapsulated into a plug-in, and when the deletion rule is added according to the actual situation, the rule for approving the invoice information is dynamically configured in a mode of enabling or disabling the plug-in.
In the embodiment of the invention, the invoice information is approved uniformly by adopting the verification rule without processing the approval process by a plurality of systems, so that the flow can be simplified, and the approval efficiency of the invoice information is effectively improved; by adding or deleting the plug-in, the rules included in the verification rules can be adjusted, dynamic deployment of the rules is realized, certain expandability is realized, and the approval mode is more flexible.
In an alternative embodiment, the approval system is associated with a billing platform for interacting with the user of the ticket buyer, and the billing platform can be implemented in a manner of setting a human-computer interaction interface in the approval system or as a separate system. The taxpayer of the ticket buyer can input invoice information on the billing platform and trigger a billing request for indicating the billing platform to issue an electronic invoice. Based on this, the receiving approval request specifically includes: and receiving an approval request sent by the invoicing platform when receiving the invoicing request triggered by the taxpayer.
In an alternative embodiment, the approval system may be provided with a file information base for recording taxpayer file information, where the taxpayer file information includes taxpayer basic information, taxpayer tax authority, risk taxpayer information, taxpayer white list, historical invoicing records of the invoices corresponding to the taxpayer, and other information, such as tax type approval information, invoice lot approval table, invoice receipt/payment stop information table, and the like. In specific implementation, the approval system can acquire and synchronously update local taxpayer file information from the existing tax bureau system for recording and managing taxpayer related information, such as a levying and managing system, a risk identification and processing system and the like by using an external interface; alternatively, an import method may be adopted to periodically import the taxpayer-related information in the tax office system, such as the risk taxpayer information, into the approval system, so as to update the taxpayer profile information in the profile information base.
Based on this, in an optional implementation manner, when the taxpayer of the ticket buyer inputs the invoice information on the invoicing platform, the invoicing platform can acquire the taxpayer file information corresponding to the taxpayer from the file information base of the approval system, and determine the alternative information possibly contained in the input invoice information of the taxpayer based on the acquired taxpayer file information, so that the taxpayer can select the alternative information, the process of inputting the invoice information by the taxpayer is simplified, and the efficiency is improved. Specifically, for example, based on the historical invoicing record of the buyer included in the taxpayer profile information, invoice top-up information (such as the above-mentioned invoice purchaser information) can be intelligently recommended to the taxpayer of the ticket purchaser according to the frequency of the invoicing address of the ticket purchaser, so that when the invoice top-up information that the taxpayer needs to enter the invoice information at present is the recommended invoice top-up information, the recommended invoice top-up information is directly selected without being entered again by the taxpayer.
Furthermore, in order to avoid tampering the invoice information to be approved, the data security is ensured. In an optional implementation manner, the approval request further carries signature information corresponding to the invoice information; before the invoice information is approved according to the verification rule, the method further comprises the following steps:
verifying the invoice information according to the signature information; the signature information is used for signing the invoice information; in specific implementation, the signature information can be generated by the invoicing platform based on the invoice information by adopting a certain algorithm.
If the verification is confirmed to pass, the invoice information is continuously approved according to the verification rule; and if the verification is determined not to pass, sending a signature abnormity notice to the invoicing platform, and stopping subsequent operations.
Further, in an optional implementation, the method further includes:
and A1, configuring invoice identification for the invoice information when the invoice information passes the approval of the verification rule. The invoice identification comprises at least one item of invoice classification codes, invoice numbers and invoice unique identification codes; for example, the invoice identification may include an invoice classification code, an invoice number; or the invoice identification may comprise an invoice unique identification code; or the invoice identification may include an invoice classification code, an invoice number, and an invoice unique identification code.
Specifically, configuring the invoice identifier for the invoice information may be implemented by referring to the following manners: inquiring whether a ticket source (namely, an unused invoice identifier) pre-distributed by a tax bureau in an approval system is sufficient, and configuring the invoice identifier for invoice information based on the pre-distributed ticket source when the ticket source is determined to be sufficient; and when the ticket source is determined to be insufficient, stopping the operation and outputting a reminder of the insufficient ticket source. In addition, during specific implementation, a ticket source management module can be independently arranged in the approval system to control the ticket sources pre-distributed by the tax bureau, and when the ticket sources in the ticket source management module are lower than a preset quantity threshold, the warning prompt of insufficient ticket sources is output. In the embodiment of the invention, the invoice source distributed by the approval system based on the tax bureau is uniformly configured with the invoice identifier for the invoice information, so that the only control of the invoice source can be realized.
And A2, tagging the invoice information after the invoice identifier is configured.
In specific implementation, partial information can be extracted from the invoice information after the invoice identifier is configured to be used as summary information to generate signature information so as to tag the invoice information after the invoice identifier is configured; or the signature information corresponding to the invoice information carried in the approval request, the invoice identifier, the invoice ID and the like can be used for signing the invoice information after the invoice identifier is configured; the invoice ID may be a number, a name, etc. set in the approval system for distinguishing the received invoice information.
Further, in an optional implementation manner, a micro service may be configured in the approval system, and the approval system may implement the method by using the micro service, for example, allocating an approval task that needs to be performed on invoice information when a tax payer triggers an invoice request through a scheduling service, scheduling different service instances to be executed to implement load balancing under a highly concurrent invoice request, approving signature information carried in the approval request through a signature service, approving the invoice information through a verification service, and signing the invoice information configured with an invoice identifier through the signature service, so as to ensure approval efficiency, thereby improving invoice efficiency and enhancing invoice experience.
Further, in an optional implementation manner, in order to record the relevant process nodes in the approval process, subsequent tracing is facilitated, and the relevant process nodes can be marked in a tagging manner. Specifically, referring to fig. 2, an embodiment of the present invention provides an approval business flow chart, which illustrates the interaction between the invoicing platform and the approval system, and the flow nodes marked by the tags. Specifically, the method comprises the following steps:
step S201, when the taxpayer of the ticket buyer triggers the operation of inputting the invoice information on the billing platform, the billing platform inquires taxpayer file information related to the taxpayer in the approval system to determine invoice information to be approved and determine signature information corresponding to the invoice information.
Step S202, the invoicing platform sends an approval request to an approval system, wherein the approval request carries the invoice information to be approved and the signature information corresponding to the invoice information.
In step S203, the approval system receives the invoice information and the signature information.
Step S204, the approval system verifies the signature information, namely, the invoice information is verified according to the signature information; when the verification passes (Y), step S205 is executed; and when the verification fails to pass the verification (N), generating signature abnormal information and sending the signature abnormal information to the invoicing platform.
Step S205, the approval system approves the invoice information, namely, the invoice information is approved according to the verification rule; when the pass (Y) is approved, step S206 is executed; and when the approval fails to pass the (N), stopping the operation, and marking the flow node based on the invoice ID and the signature information.
Step S206, the approval system judges whether the ticket source is sufficient; if yes (Y), step S207 is executed, and if no (N), the operation is stopped, and the flow node is marked based on the invoice ID and the signature information.
Step S207, the approval system configures an invoice identifier for the invoice information.
And S208, the approval system signs the invoice information after the invoice identification is configured and sends the signed invoice information to the invoicing platform. In specific implementation, the flow node may be marked based on signature information, invoice identification, and invoice ID corresponding to the invoice information carried in the approval request.
Furthermore, the taxpayer file information in the file information base can be used for providing service logic data support for the approval process when the invoice information is approved according to the verification rule and the relevant comparison information is needed. For ease of understanding, referring to fig. 3, an embodiment of the present invention provides an approval business model diagram illustrating the interaction between the billing platform, the approval system, and the tax office system providing taxpayer profile information to the approval system during the approval process. As shown in fig. 3, the approval process includes:
b1, the invoicing platform sends the invoice information (i.e. the aforementioned invoice information to be approved) entered by the taxpayer of the ticket buyer to the approval system.
B2, the approval system approves the invoice information according to at least one dynamically configured rule (specifically, three rules are illustrated in fig. 3, which are the first rule, the second rule and the third rule) in the validation rules, using the taxpayer file information provided by the tax bureau system as the comparison information. Fig. 3 specifically illustrates two tax bureau systems, namely a levying system and a risk identification and processing system.
B3, the approval system sends the approval results to the billing platform. When the approval result is passed, the approval system also sends invoice information which is signed and configured with an invoice identifier to the invoicing platform so that the invoicing platform generates an electronic invoice based on the invoice information.
Further, for convenience of implementation, the embodiment of the present invention takes as an example that the validation rule specifically includes at least one of the following rules, and describes a process of approving the invoice information according to the validation rule.
(1) The verification rule comprises a first rule, wherein the first rule is that the number of invoices of the purchaser in a preset period does not exceed a first number threshold; based on this, the invoice information is approved according to the verification rule, and the method comprises the following steps:
determining the billing quantity of the first ticket buyer in the preset period based on a file information base comprising historical billing records of the ticket buyer; the first ticket buyer is the ticket buyer indicated by the ticket buyer identifier contained in the invoice information; and authorizing the billing amount of the first ticket buyer in a preset period according to a first rule.
The preset period and the first number threshold in the first rule can be set according to actual conditions, such as the number of invoices issued by the ticket buyer in one month does not exceed 20, and the like, and are not limited herein; the identifier of the ticket buyer can be the name of the ticket buyer or the taxpayer identification number of the ticket buyer corresponding to the information of the ticket buyer included in the invoice information.
(2) The verification rule comprises a second rule, and the second rule is that the invoice limit does not exceed the first limit threshold; and authorizing the invoice information according to the verification rule, comprising the following steps: the invoice limit (i.e., the value of the aforementioned amount) included in the invoice information is approved according to the second rule.
(3) The verification rule comprises a third rule, the third rule is that the taxpayer of the ticket buyer does not belong to the risk taxpayer and/or is not in the deadlock period, and the invoice information is approved according to the verification rule, and the third rule comprises the following steps: according to the taxpayer identification number in the ticket buyer information contained in the invoice information, determining taxpayer file information corresponding to the taxpayer identification number in a file information base, and determining that the invoice information can be approved through a third rule when the taxpayer indicated by the taxpayer identification number belongs to a white list taxpayer; and when the taxpayer indicated by the taxpayer identification number is determined not to belong to the white list taxpayer, the taxpayer file information corresponding to the taxpayer identification number is approved according to a third rule, namely whether the taxpayer indicated by the taxpayer identification number belongs to a risk taxpayer or not and whether the taxpayer is in a lock-up period or not is judged.
Based on the same inventive concept as the method embodiment, the embodiment of the present invention provides an invoice information approval system 400, referring to fig. 4, including:
the receiving module 401 is configured to receive an approval request, where the approval request carries invoice information to be approved, and the invoice information is used to generate an electronic invoice;
an approval module 402 for approving the invoice information according to validation rules, the validation rules including at least one rule dynamically configured based on the plug-in form.
In the embodiment of the invention, the invoice information is approved uniformly by adopting the verification rule without processing the approval process by a plurality of systems, so that the flow can be simplified, and the approval efficiency of the invoice information is effectively improved; by adding or deleting the plug-in, the rules included in the verification rules can be adjusted, dynamic deployment of the rules is realized, certain expandability is realized, and the approval mode is more flexible.
In an optional implementation manner, the approval request further carries signature information corresponding to the invoice information;
authorization module 402 is specifically configured to:
verifying the invoice information according to the signature information;
and when the verification is determined to pass, the invoice information is approved according to the verification rule.
In an optional embodiment, the validation rule includes a first rule that the number of invoices made by the ticket buyer in a preset period does not exceed a first number threshold;
authorization module 402 is specifically configured to:
determining the billing quantity of a first ticket buyer in a preset period based on a file information base comprising historical billing records of the ticket buyer; the first ticket buyer is the ticket buyer indicated by the ticket buyer identifier contained in the invoice information;
and authorizing the billing amount of the first ticket buyer in a preset period according to a first rule.
In an optional implementation manner, the verification rule comprises a second rule, and the second rule is that the invoice limit does not exceed the first limit threshold;
authorization module 402 is specifically configured to:
and authorizing the invoice quota contained in the invoice information according to a second rule.
In an optional embodiment, the system further comprises:
the configuration module 403 is configured to configure an invoice identifier for the invoice information when the invoice information passes the approval of the validation rule, where the invoice identifier includes at least one of an invoice classification code, an invoice number, and an invoice unique identification code;
and a tagging module 404, configured to tag the invoice information after the invoice identifier is configured.
Corresponding to the above method, an embodiment of the present invention further provides an electronic device, as shown in fig. 5, including:
a communication interface 501, a memory 502, and a processor 503;
wherein, the processor 503 communicates with other devices through the communication interface 501; a memory 502 for storing program instructions; the processor 503 is used for calling the program instructions stored in the memory 502 and executing the method approved by the system in the above embodiment according to the obtained program.
In the embodiment of the present application, the specific connection medium among the communication interface 501, the memory 502, and the processor 503 is not limited, for example, a bus may be divided into an address bus, a data bus, a control bus, and the like.
In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.
In the embodiment of the present application, the memory may be a nonvolatile memory, such as a Hard Disk Drive (HDD) or a solid-state drive (SSD), and may also be a volatile memory, for example, a random-access memory (RAM). The memory can also be, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.
Further, an embodiment of the present invention also provides a computer-readable storage medium, which stores computer instructions, and when the computer instructions are executed on a computer, the computer is caused to execute the above method.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (12)
1. An invoice information approval method, comprising:
receiving an approval request, wherein the approval request carries invoice information to be approved, and the invoice information is used for generating an electronic invoice;
the invoice information is approved according to validation rules, which include at least one rule dynamically configured based on the form of the plug-in.
2. The method of claim 1, wherein the approval request further carries signature information corresponding to the invoice information;
the authorizing the invoice information according to the validation rules includes:
verifying the invoice information according to the signature information;
and when the verification is determined to pass, the invoice information is approved according to the verification rule.
3. The method of claim 1, wherein the validation rule comprises a first rule that a number of invoices made by a purchaser over a preset period does not exceed a first number threshold;
the authorizing the invoice information according to the validation rules includes:
determining the billing quantity of the first ticket buyer in the preset period based on a file information base comprising historical billing records of the ticket buyer; the first ticket buyer is the ticket buyer indicated by the ticket buyer identifier contained in the invoice information;
and authorizing the billing amount of the first ticket buyer in the preset period according to the first rule.
4. The method of claim 1, wherein the validation rule comprises a second rule that an invoice limit does not exceed a first limit threshold;
the authorizing the invoice information according to the validation rules includes:
and authorizing the invoice quota contained in the invoice information according to the second rule.
5. The method of any one of claims 1-4, further comprising:
when the invoice information passes the approval of the verification rule, configuring an invoice identifier for the invoice information, wherein the invoice identifier comprises at least one of an invoice classification code, an invoice number and an invoice unique identification code;
and adding labels to the invoice information after the invoice identifier is configured.
6. An invoice information approval system, comprising:
the receiving module is used for receiving an approval request, wherein the approval request carries invoice information to be approved, and the invoice information is used for generating an electronic invoice;
and the approval module is used for approving the invoice information according to a verification rule, wherein the verification rule comprises at least one rule dynamically configured based on a plug-in form.
7. The system of claim 6, wherein said approval request further carries signature information corresponding to said invoice information;
the approval module is specifically configured to:
verifying the invoice information according to the signature information;
and when the verification is determined to pass, the invoice information is approved according to the verification rule.
8. The system of claim 6, wherein the validation rule includes a first rule that the number of invoices made by a purchaser over a preset period does not exceed a first number threshold;
the approval module is specifically configured to:
determining the billing quantity of the first ticket buyer in the preset period based on a file information base comprising historical billing records of the ticket buyer; the first ticket buyer is the ticket buyer indicated by the ticket buyer identifier contained in the invoice information;
and authorizing the billing amount of the first ticket buyer in the preset period according to the first rule.
9. The system of claim 6, wherein the validation rule includes a second rule that an invoice limit does not exceed a first limit threshold;
the approval module is specifically configured to:
and authorizing the invoice quota contained in the invoice information according to the second rule.
10. The system of any one of claims 6-9, further comprising:
the configuration module is used for configuring invoice identification for the invoice information when the invoice information passes the approval of the verification rule, wherein the invoice identification comprises at least one item of invoice classification code, invoice number and invoice unique identification code;
and the signing module is used for signing the invoice information after the invoice identifier is configured.
11. An electronic device, comprising:
a memory and a processor;
a memory for storing program instructions;
a processor for calling the program instructions stored in the memory and executing the method of any one of claims 1 to 5 according to the obtained program.
12. A computer-readable storage medium having stored thereon computer instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911350832.5A CN113034778A (en) | 2019-12-24 | 2019-12-24 | Invoice information approval method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911350832.5A CN113034778A (en) | 2019-12-24 | 2019-12-24 | Invoice information approval method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113034778A true CN113034778A (en) | 2021-06-25 |
Family
ID=76452134
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911350832.5A Pending CN113034778A (en) | 2019-12-24 | 2019-12-24 | Invoice information approval method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113034778A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113592571A (en) * | 2021-07-27 | 2021-11-02 | 北京沃东天骏信息技术有限公司 | Bill issuing early warning method, device, equipment and computer readable medium |
| CN115994743A (en) * | 2023-03-24 | 2023-04-21 | 广东电网有限责任公司 | Document abstract specification management method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6826542B1 (en) * | 1999-11-23 | 2004-11-30 | Ipayables, Inc. | System and method for collecting, enhancing and distributing invoices electronically via the internet |
| US20140258104A1 (en) * | 2013-03-06 | 2014-09-11 | Bottomline Technologies (De) Inc. | Automatic payment component for an electronic invoice payment system |
| CN106504044A (en) * | 2016-11-09 | 2017-03-15 | 百望金赋科技有限公司 | A kind of billing method and system |
| CN108961030A (en) * | 2018-08-15 | 2018-12-07 | 腾讯科技（深圳）有限公司 | About the data processing method of electronic bill, device, system, medium and equipment |
| CN109213612A (en) * | 2018-08-10 | 2019-01-15 | 航天信息股份有限公司 | A kind of invoice issuing method and system based on webservice interface |
| CN109767309A (en) * | 2018-12-10 | 2019-05-17 | 航天信息股份有限公司 | A kind of method and system obtaining invoice examination information |
-
2019
- 2019-12-24 CN CN201911350832.5A patent/CN113034778A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6826542B1 (en) * | 1999-11-23 | 2004-11-30 | Ipayables, Inc. | System and method for collecting, enhancing and distributing invoices electronically via the internet |
| US20140258104A1 (en) * | 2013-03-06 | 2014-09-11 | Bottomline Technologies (De) Inc. | Automatic payment component for an electronic invoice payment system |
| CN106504044A (en) * | 2016-11-09 | 2017-03-15 | 百望金赋科技有限公司 | A kind of billing method and system |
| CN109213612A (en) * | 2018-08-10 | 2019-01-15 | 航天信息股份有限公司 | A kind of invoice issuing method and system based on webservice interface |
| CN108961030A (en) * | 2018-08-15 | 2018-12-07 | 腾讯科技（深圳）有限公司 | About the data processing method of electronic bill, device, system, medium and equipment |
| CN109767309A (en) * | 2018-12-10 | 2019-05-17 | 航天信息股份有限公司 | A kind of method and system obtaining invoice examination information |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113592571A (en) * | 2021-07-27 | 2021-11-02 | 北京沃东天骏信息技术有限公司 | Bill issuing early warning method, device, equipment and computer readable medium |
| CN115994743A (en) * | 2023-03-24 | 2023-04-21 | 广东电网有限责任公司 | Document abstract specification management method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102170008B1 (en) | Controlled application distribution | |
| CN107977457B (en) | Data clearing method, system and computer readable storage medium | |
| CN107995003A (en) | The charging and settlement method of international roaming communication, relevant apparatus and distributed system | |
| CN105447734B (en) | Order information processing method and system | |
| CN108171488B (en) | Data processing method, device and system | |
| CN113034778A (en) | Invoice information approval method and system | |
| CN110046785A (en) | A kind of method for processing business, equipment and its electronic equipment | |
| CN108924185A (en) | Interface creation method and device | |
| CN111325586B (en) | Bill generation method, device, server and medium based on block chain network | |
| CN110599133B (en) | Data processing method, device and storage medium based on blockchain network | |
| CN110111188B (en) | Business handling method and equipment | |
| CN115630961A (en) | Digital rights and interests service system and method based on block chain technology | |
| CN115983991A (en) | Flow adjusting method, device, equipment and medium | |
| CN105205652B (en) | Revision method and revision system of ERP (enterprise resource planning) document | |
| CN114493756A (en) | Resource management method, device, equipment and storage medium | |
| CN112529647B (en) | Block chain-based commodity transaction method, device and computer equipment | |
| CN114398226A (en) | Network asset report generation method and device | |
| CN107909371A (en) | Method of payment, payment mechanism, computer installation and computer-readable recording medium | |
| CN112132509A (en) | Refund processing method, device, medium and terminal equipment | |
| CN112434347A (en) | Rental business processing method, device, equipment and system | |
| US20190266665A1 (en) | Managing subscription life-cycles | |
| CN110648123A (en) | Digital asset construction method and device and electronic equipment | |
| EP2618293A2 (en) | Feature licensing framework for third party feature credit management | |
| CN110458701A (en) | A kind of data processing method, device, block chain node device and medium | |
| CN109254768B (en) | Method for acquiring certificate making information, terminal equipment and medium |
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 |