CN112581196A - Billing verification method and device, readable medium and electronic equipment - Google Patents
Billing verification method and device, readable medium and electronic equipment Download PDFInfo
- Publication number
- CN112581196A CN112581196A CN202011446042.XA CN202011446042A CN112581196A CN 112581196 A CN112581196 A CN 112581196A CN 202011446042 A CN202011446042 A CN 202011446042A CN 112581196 A CN112581196 A CN 112581196A
- Authority
- CN
- China
- Prior art keywords
- invoiced
- tax
- invoice
- rule
- invoicing
- 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
- 238000012795 verification Methods 0.000 title claims abstract description 68
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000004590 computer program Methods 0.000 claims description 8
- 238000000926 separation method Methods 0.000 claims description 7
- 238000013524 data verification Methods 0.000 abstract description 6
- 238000004891 communication Methods 0.000 description 7
- 230000005236 sound signal Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000005096 rolling process Methods 0.000 description 2
- 230000029305 taxis Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000019771 cognition Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/10—Tax strategies
Landscapes
- Business, Economics & Management (AREA)
- Development Economics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Marketing (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Technology Law (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The disclosure relates to a billing verification method, a billing verification device, a readable medium and electronic equipment. The technical scheme provided by the disclosure comprises: the special characters, the tax numbers, the data item lengths, the data item formats, the remarks, the amount errors, the tax errors and the total errors of the invoices to be invoiced are verified, the overall verification of the invoices to be invoiced is completed, and the current requirements for verifying the invoiced data under complex conditions are met. In addition, the scheme can be used for carrying out compliance verification on various tickets, the ticket verification is carried out in each step of the verification, namely the scheme calls the same template for various tickets to complete the compliance verification. Therefore, compared with the traditional invoice data verification, when the invoice is issued, different verification templates or different interfaces are called according to different invoice types to complete the compliance verification, the scheme is more concentrated in verification and better in transportability.
Description
Technical Field
The disclosure relates to the technical field of electronic invoices, in particular to a billing verification method and device, a readable medium and electronic equipment.
Background
Along with the development of society, the significance and the function of the invoice in the social and economic activities of China are more and more obvious, the invoice is more and more concerned by the taxpayers, and the invoicing amount is increased by times. Meanwhile, the invoice surface data of the invoice is extremely important, and the invoice can be regarded as a valid invoice only if the invoice data format accords with tax policy rules, and then reimbursement and account reporting are carried out. Therefore, how to efficiently and quickly ensure the compliance verification of the invoicing data under the conditions of large invoicing amount and different invoicing scenes is very important, and the traditional invoice data verification is insufficient in cognition on the aspects and is difficult to meet the verification requirement of the invoicing data under the current complex conditions. In addition, in the traditional invoice data verification, different verification templates or interfaces are called according to different invoice types to complete compliance verification when invoices are issued, so that the verification is not concentrated enough, and the transportability is poor.
Disclosure of Invention
The invention aims to provide a general invoicing checking method, a general invoicing checking device, a general invoicing checking readable medium and general electronic equipment for checking invoice data integrally for multiple invoice types so as to meet the checking requirement of the invoice data under the current complex condition.
In order to achieve the above object, the present disclosure provides an invoicing verification method, including:
calling a preset special character library corresponding to the invoices according to the invoices to be invoiced to verify the mandatory items of the invoices;
calling a preset tax rule corresponding to the length according to the length of the tax to be invoiced to verify the tax of the invoiced;
calling a preset data item length rule corresponding to the invoicing type according to the invoicing type to verify the length of the data item to be invoiced;
calling a preset data item format rule corresponding to the invoicing type according to the invoicing type to verify the format of the data item to be invoiced;
calling a preset remark checking rule corresponding to the ticket type according to the ticket type of the to-be-invoiced ticket to check the remark of the to-be-invoiced ticket;
and carrying out sum error verification, tax error verification and invoice total error verification on the invoice to be invoiced.
Optionally, the invoking a preset special character library corresponding to the invoicing according to the invoicing category to check the mandatory item to be invoiced includes:
when the invoicing type to be invoiced is judged to be a special invoice, calling a first special character library to verify a required item to be invoiced, when special characters in the first special character library appear in the required item, verifying to obtain that the invoiced is not compliant, and marking the appeared special characters in the required item, wherein the first special character library comprises a line-changing character;
when the invoicing type of the invoicing is judged to be a non-special invoicing, calling a second special character library to check a required item of the invoicing, when special characters in the second special character library appear in the required item, checking to obtain that the invoicing is not in compliance, marking the appeared special characters in the required item, and the second special character library does not include a line-changing character.
Optionally, the invoking a preset tax rule corresponding to the length according to the length of the tax number to be invoiced to verify the tax number to be invoiced includes:
when the length of the tax number to be invoiced is judged to be 6-15 bits, judging whether the tax number to be invoiced meets a first tax number rule, and when the tax number to be invoiced does not meet the first tax number rule, verifying to obtain that the tax number to be invoiced is not in compliance, wherein the first tax number rule is any number-letter combination of 6-15 bits;
when the length of the tax number to be invoiced is judged to be 16-18 bits, judging whether the tax number to be invoiced meets a second tax number rule, a third tax number rule and a fourth tax number rule, and when the tax number to be invoiced does not meet any one of the second tax number rule, the third tax number rule and the fourth tax number rule, verifying to obtain an unqualified invoice to be invoiced, wherein the second tax number rule is a combination of 6 digits plus at most 12 digits and any number letters, the third tax number rule is a combination of 1 digit letters plus 6 digits plus at most 11 digits and any number letters, and the fourth tax number rule is a combination of 2 digits plus 6 digits plus at most 10 digits and any number letters;
when the length of the tax number to be invoiced is judged to be 19-20 bits, judging whether the tax number to be invoiced satisfies a fifth tax number rule, a sixth tax number rule, a seventh tax number rule, an eighth tax number rule and a ninth tax number rule, verifying that the invoice to be invoiced is not qualified when the tax number to be invoiced does not satisfy any one of the fifth tax number rule, the sixth tax number rule, the seventh tax number rule, the eighth tax number rule and the ninth tax number rule, wherein the fifth tax number rule is any combination of any number letters with 15 bits of identity numbers and at most 5 bits, the sixth tax number rule is any combination of any number letters with 18 bits of identity numbers and at most 2 bits, the seventh tax number rule is any combination of any number letters with 1 bit of identity numbers and at most 15 bits of identity numbers and at most 4 bits of number, and the eighth tax rule is any combination of letters with 1 bit of identity numbers and at most 1 bit of any number letters, the ninth tax rule is a combination of 6 digits plus at most 14 arbitrary digits and non-OISZ letters.
Optionally, the invoking a preset data item length rule corresponding to the invoicing type according to the invoicing type to be invoiced to check the length of the data item to be invoiced includes:
when the invoice type of the invoice to be invoiced is judged to be a special invoice, judging whether the tax number of a purchasing party of the invoice to be invoiced is empty or not, and checking to obtain that the invoice to be invoiced is not in compliance when the tax number of the purchasing party of the invoice to be invoiced is empty;
when the type of the to-be-invoiced ticket is judged to be the volume ticket, whether the length of the commodity name to be invoiced is 40 bytes or not is judged, and when the length of the commodity name to be invoiced is not 40 bytes, the to-be-invoiced ticket is checked to obtain the non-compliance.
Optionally, the invoking a preset data item format rule corresponding to the invoicing type according to the invoicing type to be invoiced to verify the format of the data item to be invoiced includes:
when the type of the invoices to be invoiced is judged to be a blue-word invoice, judging whether the data items to be invoiced meet a first data item format rule, and when the data items to be invoiced do not meet the first data item format rule, verifying to obtain that the invoices to be invoiced are not in compliance, wherein the first data item format rule comprises the following steps: the total amount is greater than 0; the sum of the commodity line is negative, and the sum of the commodity line is positive;
when the invoicing type of the invoicing is judged to be a red invoice, judging whether the data item to be invoiced meets a second data item format rule, and when the data item to be invoiced does not meet the second data item format rule, verifying to obtain that the invoicing is not in compliance, wherein the second data item format rule comprises: the total amount is less than 0, and the invoice is an unwritten invoice and is a valid invoice.
Optionally, the invoking a preset remark checking rule corresponding to the ticket type according to the ticket type of the to-be-invoiced ticket to check the remark of the to-be-invoiced ticket includes:
when the type of the to-be-invoiced invoice is judged to be a special invoice red-word invoice, judging whether the remark of the to-be-invoiced invoice contains first content, and when the remark of the to-be-invoiced invoice does not contain the first content, verifying to obtain non-compliance of the to-be-invoiced invoice, wherein the first content is as follows: issuing special invoice information table number of red value-added tax;
when the type of the invoices to be invoiced is judged to be a common red invoice, judging whether the remarks to be invoiced contain second content, and when the remarks to be invoiced do not contain the second content, verifying to obtain the non-compliance of the invoiced, wherein the second content is as follows: a corresponding positive invoice code and a corresponding positive invoice number;
when the type of the to-be-invoiced ticket is judged to be the invoicing, whether the remark to be invoiced contains third content is judged, when the remark to be invoiced does not contain the third content, the to-be-invoiced ticket is verified to be not compliant, and the third content is as follows: the invoicing remarks indicate the tax number and name of the enterprise to be opened;
when the type of the to-be-invoiced ticket is judged to be a difference taxation blue ticket, whether the remark of the to-be-invoiced ticket contains fourth content is judged, and when the remark of the to-be-invoiced ticket does not contain the fourth content, the to-be-invoiced ticket is verified to be not compliant, wherein the fourth content is as follows: the difference tax blue ticket needs to be marked at the beginning of remarking;
when the type of the to-be-invoiced ticket is judged to be the difference taxation red ticket, whether the remark of the to-be-invoiced ticket contains fifth content is judged, and when the remark of the to-be-invoiced ticket does not contain the fifth content, the non-compliance of the to-be-invoiced ticket is verified, wherein the fifth content is as follows: the difference taxation red ticket needs to be marked at the beginning of the remark.
Optionally, the method further comprises:
and when the invoices to be invoiced are in a tax-containing mode, converting the invoices to be invoiced into a non-tax mode according to a preset price and tax separation algorithm.
The present disclosure also provides a billing verification apparatus, including:
the special character checking module is used for calling a preset special character library corresponding to the invoices according to the invoices to be invoiced to check the mandatory items of the invoices;
the tax number checking module is used for calling a preset tax number rule corresponding to the length according to the length of the tax number to be invoiced to check the tax number to be invoiced;
the data item length checking module is used for calling a preset data item length rule corresponding to the invoicing type according to the invoicing type to check the length of the data item to be invoiced;
the data item format checking module is used for calling a preset data item format rule corresponding to the invoicing type according to the invoicing type to check the format of the data item to be invoiced;
the remark checking module is used for calling a preset remark checking rule corresponding to the kind of the invoice to be invoiced according to the kind of the invoice to be invoiced to check the remark to be invoiced;
and the error checking module is used for carrying out sum error checking, tax error checking and invoice total error checking on the invoices to be invoiced.
The present disclosure also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method.
The present disclosure also provides an electronic device, comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to implement the steps of the above method.
The technical scheme provided by the disclosure comprises: the special characters, the tax numbers, the data item lengths, the data item formats, the remarks, the amount errors, the tax errors and the total errors of the invoices to be invoiced are verified, the overall verification of the invoices to be invoiced is completed, and the current requirements for verifying the invoiced data under complex conditions are met. In addition, the scheme can carry out compliance verification on various tickets, and the compliance verification is carried out on the tickets in different steps of verification. In the scheme, the same template (invoice checking template) is called for various tickets to finish the compliance checking. Therefore, compared with the traditional invoice data verification method, when the invoices are issued, different verification templates (such as a value-added tax common invoice template and a value-added tax special invoice template) are called according to different invoice types or different interfaces to complete compliance verification, the verification in the scheme is more concentrated, and the portability is better.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure without limiting the disclosure. In the drawings:
fig. 1 is a flowchart of an invoicing verification method provided in an embodiment of the present disclosure.
Fig. 2 is a block diagram of an invoicing checking apparatus provided in an embodiment of the present disclosure.
Fig. 3 is a block diagram of an electronic device provided by an embodiment of the present disclosure.
Detailed Description
The following detailed description of specific embodiments of the present disclosure is provided in connection with the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present disclosure, are given by way of illustration and explanation only, not limitation.
The embodiment of the disclosure provides a billing verification method. Fig. 1 shows a flow chart of the billing verification method. As shown in fig. 1, the method includes:
and step S11, calling a preset special character library corresponding to the invoices according to the invoices to be invoiced, and verifying the mandatory entries of the invoices to be invoiced.
At least one preset special character library is prestored, and each preset special character library corresponds to at least one ticket type. Classifying the various tickets according to the requirement of the tax policy on the special characters which are not allowed to appear in the various mandatory tickets, wherein each class corresponds to the same preset special character library. Through the steps, the preset special character library corresponding to each ticket is called for each ticket to check the special characters of the mandatory items of each ticket, so that the special characters which do not accord with the regulation and can not appear on the ticket surface of the invoice are uniformly filtered and intercepted.
And step S12, calling a preset tax rule corresponding to the length according to the length of the tax to be invoiced to verify the tax of the invoiced.
Because the requirement on the format of the tax number in the tax policy is particularly high, the format, the length, the case and the like of the tax number need to be independently checked to ensure that the invoicing tax number is legal. Through the steps, different preset tax rules are set based on the length of the tax according to the requirement of the tax policy on the tax, and the preset tax rules corresponding to the length are called according to the length of the tax to-be-invoiced to verify the tax of the to-be-invoiced so as to complete the compliance verification of the purchasing tax and the selling tax in the invoice information.
And step S13, calling a preset data item length rule corresponding to the invoicing according to the invoicing type to verify the length of the data item to be invoiced.
Since the length requirements of the individual data items are not the same between different ticket types. And setting preset data item length rules for various tickets according to the requirements of the tax policy on the lengths of various data items of various tickets. The length rules of the preset data items may all be different, and then the length of the data item to be invoiced may be checked as follows: firstly, processing the difference of the length of each field of each ticket according to the ticket types, and walking a special logic verification branch to realize the step S13; and then, a universal data item length rule is checked, namely, the same data item length rule check is uniformly executed by all the invoices (namely, the method also comprises the step of carrying out a universal data item length rule check on the invoices to be invoiced). Similarly, the preset data item length rules may be partially the same and partially different, where the different parts are differences in lengths of fields of the invoices, and the same part is the general data item length check rule, where checking the length of the data item to be invoiced may be: and calling a preset data item length rule corresponding to the invoicing according to the invoicing type to verify the length of the data item to be invoiced (namely, the method only comprises the step S13).
And step S14, calling a preset data item format rule corresponding to the invoicing according to the invoicing type to verify the format of the data item to be invoiced.
Since the format requirements of the individual data items are not the same between different ticket types. And setting preset data item format rules for various tickets according to the requirements of the tax policy on various data item formats of various tickets. Through the steps, the format of the data item of the invoice is verified according to the types of the invoice.
And step S15, calling a preset remark checking rule corresponding to the kind of the ticket according to the kind of the ticket to be invoiced, and checking the remark to be invoiced.
According to the tax policy, the remarking requirements for special invoices such as red invoices, generation invoices, differential tax invoices and the like are different, so that the checking is required. Through the steps, the pre-set remark checking rule corresponding to the ticket type is called according to the ticket type of the to-be-invoiced ticket to check the remark of the to-be-invoiced ticket, so that the remark checking on special invoices such as red tickets, invoiced tickets, differential tax invoices and the like can be realized.
And step S16, carrying out sum error check, tax error check and invoice total error check on the invoice to be invoiced.
Through the steps, the amount error check, the tax error check and the invoice total error check are carried out on various invoices according to the error range allowed by the tax policy.
The technical scheme provided by the disclosure comprises: the special characters, the tax numbers, the data item lengths, the data item formats, the remarks, the amount errors, the tax errors and the total errors of the invoices to be invoiced are verified, the overall verification of the invoices to be invoiced is completed, and the current requirements for verifying the invoiced data under complex conditions are met. In addition, the scheme can carry out compliance verification on various tickets, and the compliance verification is carried out on the tickets in different steps of verification. In the scheme, the same template (invoice checking template) is called for various tickets to finish the compliance checking. Therefore, compared with the traditional invoice data verification method, when the invoices are issued, different verification templates (such as a value-added tax common invoice template and a value-added tax special invoice template) are called according to different invoice types or different interfaces to complete compliance verification, the verification in the scheme is more concentrated, and the portability is better.
Optionally, step S11 includes:
when the type of the invoices to be invoiced is judged to be a special invoice, calling a first special character library to verify the mandatory item of the invoices to be invoiced, when special characters in the first special character library appear in the mandatory item, verifying to obtain that the invoices to be invoiced are not compliant, and marking the appeared special characters in the mandatory item, wherein the first special character library comprises a line-changing character.
The special invoice is a value-added tax special invoice, and the required items comprise a seller address telephone, a buyer address telephone, a seller account-making bank and an account, a buyer account-making bank and an account and the like.
When the invoicing type of the invoicing is judged to be a non-special invoicing, calling a second special character library to check a required item of the invoicing, when special characters in the second special character library appear in the required item, checking to obtain that the invoicing is not in compliance, marking the appeared special characters in the required item, and the second special character library does not include a line-changing character.
The mandatory items of the non-special tickets are, for example, invoices, cashiers, invoice pipelines, specification models and the like.
Optionally, step S12 includes:
when the length of the tax number to be invoiced is judged to be 6-15 bits, whether the tax number to be invoiced meets a first tax number rule is judged, when the tax number to be invoiced does not meet the first tax number rule, the tax number to be invoiced is verified to be not in compliance, and the first tax number rule is any number-letter combination of 6-15 bits.
When the length of the tax number to be invoiced is judged to be 16-18 bits, whether the tax number to be invoiced meets a second tax number rule, a third tax number rule and a fourth tax number rule is judged, when the tax number to be invoiced does not meet any one of the second tax number rule, the third tax number rule and the fourth tax number rule, the non-compliance of the invoiced is verified, the second tax number rule is a combination of 6 bits of numbers and at most 12 bits of any number letters, the third tax number rule is a combination of 1 bit of letters and 6 bits of numbers and at most 11 bits of any number letters, and the fourth tax number rule is a combination of 2 bits of letters and 6 bits of numbers and at most 10 bits of any number letters.
When the length of the tax number to be invoiced is judged to be 19-20 bits, judging whether the tax number to be invoiced satisfies a fifth tax number rule, a sixth tax number rule, a seventh tax number rule, an eighth tax number rule and a ninth tax number rule, verifying that the invoice to be invoiced is not qualified when the tax number to be invoiced does not satisfy any one of the fifth tax number rule, the sixth tax number rule, the seventh tax number rule, the eighth tax number rule and the ninth tax number rule, wherein the fifth tax number rule is any combination of any number letters with 15 bits of identity numbers and at most 5 bits, the sixth tax number rule is any combination of any number letters with 18 bits of identity numbers and at most 2 bits, the seventh tax number rule is any combination of any number letters with 1 bit of identity numbers and at most 15 bits of identity numbers and at most 4 bits of number, and the eighth tax rule is any combination of letters with 1 bit of identity numbers and at most 1 bit of any number letters, the ninth tax rule is a combination of 6 digits plus at most 14 arbitrary digits and non-OISZ letters.
The above technical solution can be shown in the following table:
optionally, step S13 includes:
and when the invoice type to be invoiced is judged to be a special invoice, judging whether the tax number of the purchasing party to be invoiced is empty, and checking to obtain that the invoice to be invoiced is not in compliance when the tax number of the purchasing party to be invoiced is empty.
According to the tax policy, the purchasing tax number of the special invoice cannot be null, and the purchasing tax number of other invoices can be null. Therefore, when the special invoice is made, the user may be influenced by the habit of making other invoices to make the tax number of the purchasing party empty, so that an error occurs, and the error can be avoided through the step.
When the type of the to-be-invoiced ticket is judged to be the volume ticket, whether the length of the commodity name to be invoiced is 40 bytes or not is judged, and when the length of the commodity name to be invoiced is not 40 bytes, the to-be-invoiced ticket is checked to obtain the non-compliance.
According to the tax policy, the commodity name of the volume ticket is 40 bytes long, and the commodity names of other invoices are 90 bytes long. Therefore, when the invoice is issued, the user may be influenced by other invoice issuing habits to enable the length of the commodity name to be 90 bytes, so that errors occur, and the errors can be avoided through the step.
Optionally, step S14 includes:
when the type of the invoices to be invoiced is judged to be a blue-word invoice, judging whether the data items to be invoiced meet a first data item format rule, and when the data items to be invoiced do not meet the first data item format rule, verifying to obtain that the invoices to be invoiced are not in compliance, wherein the first data item format rule comprises the following steps: the total amount is greater than 0; and the sum is the negative commodity line, and the sum of the last commodity line is positive.
When the invoicing type of the invoicing is judged to be a red invoice, judging whether the data item to be invoiced meets a second data item format rule, and when the data item to be invoiced does not meet the second data item format rule, verifying to obtain that the invoicing is not in compliance, wherein the second data item format rule comprises: the total amount is less than 0, and the invoice is an unwritten invoice and is a valid invoice.
The blue invoice is positive invoice, the red invoice is negative invoice, and the data item format rule can include the following table:
optionally, step S15 includes:
when the type of the to-be-invoiced invoice is judged to be a special invoice red-word invoice, judging whether the remark of the to-be-invoiced invoice contains first content, and when the remark of the to-be-invoiced invoice does not contain the first content, verifying to obtain non-compliance of the to-be-invoiced invoice, wherein the first content is as follows: the special invoice information table number of the red value-added tax is issued.
When the type of the invoices to be invoiced is judged to be a common red invoice, judging whether the remarks to be invoiced contain second content, and when the remarks to be invoiced do not contain the second content, verifying to obtain the non-compliance of the invoiced, wherein the second content is as follows: a corresponding positive invoice code and a corresponding positive invoice number.
When the type of the to-be-invoiced ticket is judged to be the invoicing, whether the remark to be invoiced contains third content is judged, when the remark to be invoiced does not contain the third content, the to-be-invoiced ticket is verified to be not compliant, and the third content is as follows: the invoicing remarks indicate the tax number and name of the enterprise, and are actually filled.
When the type of the to-be-invoiced ticket is judged to be a difference taxation blue ticket, whether the remark of the to-be-invoiced ticket contains fourth content is judged, and when the remark of the to-be-invoiced ticket does not contain the fourth content, the to-be-invoiced ticket is verified to be not compliant, wherein the fourth content is as follows: the difference tax blue ticket needs to be noted at the beginning of the remark.
When the type of the to-be-invoiced ticket is judged to be the difference taxation red ticket, whether the remark of the to-be-invoiced ticket contains fifth content is judged, and when the remark of the to-be-invoiced ticket does not contain the fifth content, the non-compliance of the to-be-invoiced ticket is verified, wherein the fifth content is as follows: the difference taxation red ticket needs to be marked at the beginning of the remark.
The technical scheme is as follows: for a special-ticket red-word invoice, the remark must contain contents such as 'the number of a special invoice information table for issuing red-word value-added tax', and for a common red-word invoice, the remark must contain 'a corresponding positive invoice code' and 'a corresponding positive invoice number'; for the generation invoicing, the remarks must comprise 'the generation invoicing remarks express the generation enterprise tax number and the generation enterprise name, and are actually filled in'; for the difference tax blue ticket, the remark must contain "the difference tax blue ticket needs to be noted at the beginning of the remark", and if the difference tax red ticket is, the remark must contain "the difference tax red ticket needs to be noted at the beginning of the remark". When an invoice is a red invoice (a special red invoice or a common red invoice) and a difference taxation invoice, remark checking rules need to be overlapped.
Since the user may be in the tax-free mode when invoicing, the user needs to switch to the tax-free mode. Optionally, the method further comprises:
and when the invoices to be invoiced are in a tax-containing mode, converting the invoices to be invoiced into a non-tax mode according to a preset price and tax separation algorithm.
The preset price and tax separation algorithm is as follows (the unit price number is reserved with 8 decimal places, and the amount tax amount is reserved with 2 decimal places):
for non-discount tickets: the tax-free amount is the tax-containing amount/(1 + tax rate); non-tax unit price is non-tax amount/quantity (item quantity is not null and unit price is null); tax free unit price/(1 + tax rate) (the number of items is null and the unit price is not null); the amount is tax free amount/unit price; tax free unit price/(1 + tax rate) (unit price is calculated according to unit price without quantity unit price); tax amount is tax amount-tax free amount.
For discount tickets: the difference is the tax amount-deduction; no tax difference is difference/(1 + tax rate); the tax free amount is not the tax free difference and deduct the amount; non-tax unit price is non-tax amount/quantity (item quantity is not null and unit price is null); tax free unit price/(1 + tax rate) (the number of items is null and the unit price is not null); the amount is tax free amount/unit price; the non-tax unit price is the non-tax amount/quantity (the unit price is not null, and the unit price is calculated according to the quantity); tax amount is tax amount-tax free amount.
Optionally, step S16 includes:
and carrying out sum error check on the invoices to be invoiced.
The specific check rule may be: the error between the sum of money and the product of the quantity and the unit price cannot exceed 0.01 in both tax-containing and tax-free modes of each detail line. That is, when tax is included, the amount of tax-unit price of the commodity must be less than 0.01; when no tax is contained, the tax-free amount-tax-free unit price-commodity quantity must be less than 0.01, otherwise, the to-be-invoiced ticket is verified to be not compliant.
And carrying out tax error check on the invoice to be invoiced.
The specific check rule may be: the difference between the tax-containing amount and the non-tax amount of each detail line and the error between the tax amount cannot exceed 0.06; the error between the difference between the total tax-containing amount and the total non-tax-containing amount of the invoice and the total tax amount cannot exceed 1.27. This has a special treatment, for the list red ticket, because the multiple details are combined into one line, the difference between the tax-containing amount and the non-tax amount of the detail line and the error between the tax amount are calculated according to the condition that the error can not exceed 1.27.
And carrying out invoice total error verification on the invoices to be invoiced.
The specific check rule may be: the sum of the tax containing amount of each detail line must be equal to the total tax containing amount of the invoice; the sum of the tax free amount of each detail line must be equal to the total tax free amount of the invoice; the sum of the taxes of the various detail lines must equal the invoice total tax.
When the technical scheme is implemented, the invoice category code can be set to identify and judge whether the invoice to be invoiced belongs to a special value-added tax invoice or a common value-added tax electronic invoice or a rolling invoice and the like; the invoicing type can be set to identify and judge whether the invoices to be invoiced belong to blue-word invoices or red-word invoices; the identification of the type of invoice to be invoiced as belonging to the differential taxation invoice can be made based on the fact that the version number of the coding table is not null and the deduction in the first line detail in the invoice detail is not null.
Based on the above inventive concept, the embodiment of the present disclosure further provides an invoicing checking device 10. As shown in fig. 2, the billing verification apparatus 10 includes:
the special character checking module 11 is used for calling a preset special character library corresponding to the invoices according to the invoices to be invoiced to check the mandatory items of the invoices;
the tax number checking module 12 is configured to invoke a preset tax number rule corresponding to the length of the tax number to be invoiced to check the tax number to be invoiced according to the length of the tax number to be invoiced;
the data item length checking module 13 is configured to invoke a preset data item length rule corresponding to the invoicing type according to the invoicing type to check the length of the data item to be invoiced;
the data item format checking module 14 is configured to invoke a preset data item format rule corresponding to the invoicing type according to the invoicing type to be invoiced to check the format of the data item to be invoiced;
the remark checking module 15 is configured to invoke a preset remark checking rule corresponding to the kind of the invoice to be invoiced to check the remark to be invoiced according to the kind of the invoice to be invoiced;
and the error checking module 16 is used for carrying out sum error checking, tax error checking and invoice total error checking on the invoices to be invoiced.
The technical scheme provided by the disclosure comprises: the special characters, the tax numbers, the data item lengths, the data item formats, the remarks, the amount errors, the tax errors and the total errors of the invoices to be invoiced are verified, the overall verification of the invoices to be invoiced is completed, and the current requirements for verifying the invoiced data under complex conditions are met. In addition, the scheme can carry out compliance verification on various tickets, and the compliance verification is carried out on the tickets in different steps of verification. In the scheme, the same template (invoice checking template) is called for various tickets to finish the compliance checking. Therefore, compared with the traditional invoice data verification method, when the invoices are issued, different verification templates (such as a value-added tax common invoice template and a value-added tax special invoice template) are called according to different invoice types or different interfaces to complete compliance verification, the verification in the scheme is more concentrated, and the portability is better.
Optionally, the special character checking module 11 includes:
the special character checking submodule for the special tickets is used for calling a first special character library to check mandatory fill items of the invoices to be invoiced when the types of the invoices to be invoiced are judged to be the special tickets, when special characters in the first special character library appear in the mandatory fill items, the required invoiced tickets are checked to be not in compliance, the appeared special characters are marked out in the mandatory fill items, and the first special character library comprises line-changing characters.
The special invoice is a value-added tax special invoice, and the required items comprise a seller address telephone, a buyer address telephone, a seller account-making bank and an account, a buyer account-making bank and an account and the like.
The non-special-ticket special character checking sub-module is used for calling a second special character library to check a required item to be invoiced when the type of the invoiced ticket is judged to be a non-special ticket, when special characters in the second special character library appear in the required item, the required item to be invoiced is checked to obtain non-compliance of the invoiced ticket, the appeared special characters are marked in the required item, and the second special character library does not include a line-change character.
The mandatory items of the non-special tickets are, for example, invoices, cashiers, invoice pipelines, specification models and the like.
Optionally, the tax verification module 12 includes:
the first tax number length submodule is used for judging whether the tax number to be invoiced meets a first tax number rule or not when the length of the tax number to be invoiced is judged to be 6-15 bits, and verifying that the tax number to be invoiced is not in compliance when the tax number to be invoiced does not meet the first tax number rule, wherein the first tax number rule is any digital-letter combination of 6-15 bits.
The second tax number length submodule is used for judging whether the tax number to be invoiced meets a second tax number rule, a third tax number rule and a fourth tax number rule when the length of the tax number to be invoiced is 16-18 bits, verifying to obtain the non-compliance of the invoiced when the tax number to be invoiced does not meet any one of the second tax number rule, the third tax number rule and the fourth tax number rule, wherein the second tax number rule is a combination of 6 bits of numbers and at most 12 bits of any number letters, the third tax number rule is a combination of 1 bit of letters and 6 bits of numbers and at most 11 bits of any number letters, and the fourth tax number rule is a combination of 2 bits of letters and 6 bits of numbers and at most 10 bits of any number letters.
A third tax length submodule, configured to determine, when the length of the tax number to be invoiced is determined to be 19 to 20 bits, whether the tax number to be invoiced satisfies any of a fifth tax rule, a sixth tax rule, a seventh tax rule, an eighth tax rule and a ninth tax rule, and verify that the invoice to be invoiced is not in compliance with any of the fifth tax rule, the sixth tax rule, the seventh tax rule, the eighth tax rule and the ninth tax rule, the fifth tax rule is any combination of 15 bits of identification number and at most 5 bits of arbitrary number, the sixth tax rule is any combination of 18 bits of identification number and at most 2 bits of arbitrary number, the seventh tax rule is any combination of 1 bit of identification number and 15 bits of identification number and at most 4 bits of arbitrary number, and the eighth tax rule is any combination of 1 bit of identification number and 18 bits of identification number and at most 1 bit of number, the ninth tax rule is a combination of 6 digits plus at most 14 arbitrary digits and non-OISZ letters.
Optionally, the data item length checking module 13 includes:
and the special invoice data item length checking submodule is used for judging whether the tax number of the purchasing party of the invoicing is empty or not when judging that the invoice type of the invoicing is the special invoice, and checking to obtain that the invoicing is not in compliance when the tax number of the purchasing party of the invoicing is empty.
The system comprises a invoicing data item length checking submodule and a invoicing data item length checking submodule, wherein the invoicing data item length checking submodule is used for judging whether the length of the commodity name to be invoiced is 40 bytes or not when judging that the type of the invoiced is invoicing, and checking to obtain that the invoiced is not in compliance when the length of the commodity name to be invoiced is not 40 bytes.
Optionally, the data item format checking module 14 includes:
the blue invoice data item format checking submodule is used for judging whether the data item to be invoiced meets a first data item format rule when judging that the type of the invoice to be invoiced is a blue invoice, and checking to obtain that the invoice to be invoiced is not compliant when the data item to be invoiced does not meet the first data item format rule, wherein the first data item format rule comprises: the total amount is greater than 0; and the sum is the negative commodity line, and the sum of the last commodity line is positive.
The red invoice data item format checking submodule is used for judging whether the data item to be invoiced meets a second data item format rule when the type of the to-be-invoiced invoice is judged to be a red invoice, and checking to obtain that the to-be-invoiced invoice does not meet the second data item format rule when the data item to be invoiced does not meet the second data item format rule, wherein the second data item format rule comprises: the total amount is less than 0, and the invoice is an unwritten invoice and is a valid invoice.
The blue invoice is positive invoice, the red invoice is negative invoice, and the data item format rule can include the following table:
optionally, the remarks checking module 15 includes:
the special invoice red-character invoice remark checking submodule is used for judging whether the remark to be invoiced contains first content when the type of the special invoice to be invoiced is judged to be the special invoice red-character invoice, and checking whether the remark to be invoiced is not compliant when the remark to be invoiced does not contain the first content, wherein the first content is as follows: the special invoice information table number of the red value-added tax is issued.
The common red invoice remark checking submodule is used for judging whether the remark of the invoice to be invoiced contains second content when judging that the kind of the invoice to be invoiced is the common red invoice, and checking to obtain that the invoice to be invoiced is not compliant when the remark of the invoice to be invoiced does not contain the second content, wherein the second content is as follows: a corresponding positive invoice code and a corresponding positive invoice number.
The module for checking the candidate note for invoicing is configured to, when it is determined that the kind of the candidate note for invoicing is a candidate invoice, determine whether the candidate note for invoicing includes third content, and when the candidate note for invoicing does not include the third content, check to obtain that the candidate invoice is not compliant, where the third content is: the invoicing remarks indicate the tax number and name of the enterprise, and are actually filled.
The difference tax collection blue ticket remark checking submodule is used for judging whether the remark to be invoiced contains fourth content when the type of the remark to be invoiced is judged to be the difference tax collection blue ticket, and checking whether the remark to be invoiced does not contain the fourth content when the remark to be invoiced does not contain the fourth content, wherein the fourth content is as follows: the difference tax blue ticket needs to be noted at the beginning of the remark.
The difference tax collection red ticket remark checking submodule is used for judging whether the remark to be invoiced contains fifth content when the type of the remark to be invoiced is judged to be the difference tax collection red ticket, and checking whether the remark to be invoiced does not contain the fifth content when the remark to be invoiced does not contain the fifth content, wherein the fifth content is as follows: the difference taxation red ticket needs to be marked at the beginning of the remark.
The technical scheme is as follows: for a special-ticket red-word invoice, the remark must contain contents such as 'the number of a special invoice information table for issuing red-word value-added tax', and for a common red-word invoice, the remark must contain 'a corresponding positive invoice code' and 'a corresponding positive invoice number'; for the generation invoicing, the remarks must comprise 'the generation invoicing remarks express the generation enterprise tax number and the generation enterprise name, and are actually filled in'; for the difference tax blue ticket, the remark must contain "the difference tax blue ticket needs to be noted at the beginning of the remark", and if the difference tax red ticket is, the remark must contain "the difference tax red ticket needs to be noted at the beginning of the remark". When an invoice is a red invoice (a special red invoice or a common red invoice) and a difference taxation invoice, remark checking rules need to be overlapped.
Since the user may be in the tax-free mode when invoicing, the user needs to switch to the tax-free mode. Optionally, the billing verification apparatus 10 further includes:
and the price and tax separation module is used for converting the invoices to be invoiced into a non-tax mode according to a preset price and tax separation algorithm when the invoices to be invoiced are in a tax mode.
The preset price and tax separation algorithm is as follows (the unit price number is reserved with 8 decimal places, and the amount tax amount is reserved with 2 decimal places):
for non-discount tickets: the tax-free amount is the tax-containing amount/(1 + tax rate); non-tax unit price is non-tax amount/quantity (item quantity is not null and unit price is null); tax free unit price/(1 + tax rate) (the number of items is null and the unit price is not null); the amount is tax free amount/unit price; tax free unit price/(1 + tax rate) (unit price is calculated according to unit price without quantity unit price); tax amount is tax amount-tax free amount.
For discount tickets: the difference is the tax amount-deduction; no tax difference is difference/(1 + tax rate); the tax free amount is not the tax free difference and deduct the amount; non-tax unit price is non-tax amount/quantity (item quantity is not null and unit price is null); tax free unit price/(1 + tax rate) (the number of items is null and the unit price is not null); the amount is tax free amount/unit price; the non-tax unit price is the non-tax amount/quantity (the unit price is not null, and the unit price is calculated according to the quantity); tax amount is tax amount-tax free amount.
Optionally, the error checking module 16 comprises:
and the sum error checking submodule is used for carrying out sum error checking on the invoices to be invoiced.
The specific check rule may be: the error between the sum of money and the product of the quantity and the unit price cannot exceed 0.01 in both tax-containing and tax-free modes of each detail line. That is, when tax is included, the amount of tax-unit price of the commodity must be less than 0.01; when no tax is contained, the tax-free amount-tax-free unit price-commodity quantity must be less than 0.01, otherwise, the to-be-invoiced ticket is verified to be not compliant.
And the tax error checking submodule is used for carrying out tax error checking on the invoices to be invoiced.
The specific check rule may be: the difference between the tax-containing amount and the non-tax amount of each detail line and the error between the tax amount cannot exceed 0.06; the error between the difference between the total tax-containing amount and the total non-tax-containing amount of the invoice and the total tax amount cannot exceed 1.27. This has a special treatment, for the list red ticket, because the multiple details are combined into one line, the difference between the tax-containing amount and the non-tax amount of the detail line and the error between the tax amount are calculated according to the condition that the error can not exceed 1.27.
And the invoice total error checking submodule is used for carrying out invoice total error checking on the invoices to be invoiced.
The specific check rule may be: the sum of the tax containing amount of each detail line must be equal to the total tax containing amount of the invoice; the sum of the tax free amount of each detail line must be equal to the total tax free amount of the invoice; the sum of the taxes of the various detail lines must equal the invoice total tax.
When the technical scheme is implemented, the invoice category code can be set to identify and judge whether the invoice to be invoiced belongs to a special value-added tax invoice or a common value-added tax electronic invoice or a rolling invoice and the like; the invoicing type can be set to identify and judge whether the invoices to be invoiced belong to blue-word invoices or red-word invoices; the identification of the type of invoice to be invoiced as belonging to the differential taxation invoice can be made based on the fact that the version number of the coding table is not null and the deduction in the first line detail in the invoice detail is not null.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Based on the above inventive concept, the embodiments of the present disclosure further provide a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the above billing verification method.
Based on the inventive concept, the embodiment of the present disclosure further provides an electronic device. Fig. 3 is a block diagram illustrating an electronic device 700 according to an example embodiment. As shown in fig. 3, the electronic device 700 may include: a processor 701 and a memory 702. The electronic device 700 may also include one or more of a multimedia component 703, an input/output (I/O) interface 704, and a communication component 705.
The processor 701 is configured to control the overall operation of the electronic device 700, so as to complete all or part of the steps in the above-mentioned billing verification method. The memory 702 is used to store various types of data to support operation at the electronic device 700, such as instructions for any application or method operating on the electronic device 700 and application-related data, such as contact data, transmitted and received messages, pictures, audio, video, and the like. The Memory 702 may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk, or optical disk. The multimedia components 703 may include screen and audio components. Wherein the screen may be, for example, a touch screen and the audio component is used for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may further be stored in the memory 702 or transmitted through the communication component 705. The audio assembly also includes at least one speaker for outputting audio signals. The I/O interface 704 provides an interface between the processor 701 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 705 is used for wired or wireless communication between the electronic device 700 and other devices. Wireless Communication, such as Wi-Fi, bluetooth, Near Field Communication (NFC), 2G, 3G, 4G, NB-IOT, eMTC, or other 5G, etc., or a combination of one or more of them, which is not limited herein. The corresponding communication component 705 may thus include: Wi-Fi module, Bluetooth module, NFC module, etc.
In an exemplary embodiment, the electronic Device 700 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the above-described ticketing check method.
In another exemplary embodiment, a computer readable storage medium comprising program instructions which, when executed by a processor, implement the steps of the above-described invoicing verification method is also provided. For example, the computer readable storage medium may be the memory 702 described above including program instructions executable by the processor 701 of the electronic device 700 to perform the invoicing verification method described above.
The preferred embodiments of the present disclosure are described in detail with reference to the accompanying drawings, however, the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solution of the present disclosure within the technical idea of the present disclosure, and these simple modifications all belong to the protection scope of the present disclosure.
It should be noted that, in the foregoing embodiments, various features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various combinations that are possible in the present disclosure are not described again.
In addition, any combination of various embodiments of the present disclosure may be made, and the same should be considered as the disclosure of the present disclosure, as long as it does not depart from the spirit of the present disclosure.
Claims (10)
1. An invoicing verification method, comprising:
calling a preset special character library corresponding to the invoices according to the invoices to be invoiced to verify the mandatory items of the invoices;
calling a preset tax rule corresponding to the length according to the length of the tax to be invoiced to verify the tax of the invoiced;
calling a preset data item length rule corresponding to the invoicing type according to the invoicing type to verify the length of the data item to be invoiced;
calling a preset data item format rule corresponding to the invoicing type according to the invoicing type to verify the format of the data item to be invoiced;
calling a preset remark checking rule corresponding to the ticket type according to the ticket type of the to-be-invoiced ticket to check the remark of the to-be-invoiced ticket;
and carrying out sum error verification, tax error verification and invoice total error verification on the invoice to be invoiced.
2. The method as claimed in claim 1, wherein the invoking a preset special character library corresponding to the invoicing according to the invoicing category to verify the mandatory item to be invoiced comprises:
when the invoicing type to be invoiced is judged to be a special invoice, calling a first special character library to verify a required item to be invoiced, when special characters in the first special character library appear in the required item, verifying to obtain that the invoiced is not compliant, and marking the appeared special characters in the required item, wherein the first special character library comprises a line-changing character;
when the invoicing type of the invoicing is judged to be a non-special invoicing, calling a second special character library to check a required item of the invoicing, when special characters in the second special character library appear in the required item, checking to obtain that the invoicing is not in compliance, marking the appeared special characters in the required item, and the second special character library does not include a line-changing character.
3. The invoicing verification method according to claim 1, wherein the invoking a preset tax rule corresponding to the length according to the length of the tax number to be invoiced to verify the tax number to be invoiced comprises:
when the length of the tax number to be invoiced is judged to be 6-15 bits, judging whether the tax number to be invoiced meets a first tax number rule, and when the tax number to be invoiced does not meet the first tax number rule, verifying to obtain that the tax number to be invoiced is not in compliance, wherein the first tax number rule is any number-letter combination of 6-15 bits;
when the length of the tax number to be invoiced is judged to be 16-18 bits, judging whether the tax number to be invoiced meets a second tax number rule, a third tax number rule and a fourth tax number rule, and when the tax number to be invoiced does not meet any one of the second tax number rule, the third tax number rule and the fourth tax number rule, verifying to obtain an unqualified invoice to be invoiced, wherein the second tax number rule is a combination of 6 digits plus at most 12 digits and any number letters, the third tax number rule is a combination of 1 digit letters plus 6 digits plus at most 11 digits and any number letters, and the fourth tax number rule is a combination of 2 digits plus 6 digits plus at most 10 digits and any number letters;
when the length of the tax number to be invoiced is judged to be 19-20 bits, judging whether the tax number to be invoiced satisfies a fifth tax number rule, a sixth tax number rule, a seventh tax number rule, an eighth tax number rule and a ninth tax number rule, verifying that the invoice to be invoiced is not qualified when the tax number to be invoiced does not satisfy any one of the fifth tax number rule, the sixth tax number rule, the seventh tax number rule, the eighth tax number rule and the ninth tax number rule, wherein the fifth tax number rule is any combination of any number letters with 15 bits of identity numbers and at most 5 bits, the sixth tax number rule is any combination of any number letters with 18 bits of identity numbers and at most 2 bits, the seventh tax number rule is any combination of any number letters with 1 bit of identity numbers and at most 15 bits of identity numbers and at most 4 bits of number, and the eighth tax rule is any combination of letters with 1 bit of identity numbers and at most 1 bit of any number letters, the ninth tax rule is a combination of 6 digits plus at most 14 arbitrary digits and non-OISZ letters.
4. The invoicing verification method according to claim 1, wherein the verifying the length of the data item to be invoiced according to the invoiced type calling a preset data item length rule corresponding to the invoiced type comprises:
when the invoice type of the invoice to be invoiced is judged to be a special invoice, judging whether the tax number of a purchasing party of the invoice to be invoiced is empty or not, and checking to obtain that the invoice to be invoiced is not in compliance when the tax number of the purchasing party of the invoice to be invoiced is empty;
when the type of the to-be-invoiced ticket is judged to be the volume ticket, whether the length of the commodity name to be invoiced is 40 bytes or not is judged, and when the length of the commodity name to be invoiced is not 40 bytes, the to-be-invoiced ticket is checked to obtain the non-compliance.
5. The invoicing verification method according to claim 1, wherein the verifying the format of the data item to be invoiced according to the invoicing type calling a preset data item format rule corresponding to the invoicing type comprises:
when the type of the invoices to be invoiced is judged to be a blue-word invoice, judging whether the data items to be invoiced meet a first data item format rule, and when the data items to be invoiced do not meet the first data item format rule, verifying to obtain that the invoices to be invoiced are not in compliance, wherein the first data item format rule comprises the following steps: the total amount is greater than 0; the sum of the commodity line is negative, and the sum of the commodity line is positive;
when the invoicing type of the invoicing is judged to be a red invoice, judging whether the data item to be invoiced meets a second data item format rule, and when the data item to be invoiced does not meet the second data item format rule, verifying to obtain that the invoicing is not in compliance, wherein the second data item format rule comprises: the total amount is less than 0, and the invoice is an unwritten invoice and is a valid invoice.
6. The invoicing verification method according to claim 1, wherein the verifying the remarks to be invoiced by calling a preset remark verification rule corresponding to the invoiced type according to the invoiced type comprises:
when the type of the to-be-invoiced invoice is judged to be a special invoice red-word invoice, judging whether the remark of the to-be-invoiced invoice contains first content, and when the remark of the to-be-invoiced invoice does not contain the first content, verifying to obtain non-compliance of the to-be-invoiced invoice, wherein the first content is as follows: issuing special invoice information table number of red value-added tax;
when the type of the invoices to be invoiced is judged to be a common red invoice, judging whether the remarks to be invoiced contain second content, and when the remarks to be invoiced do not contain the second content, verifying to obtain the non-compliance of the invoiced, wherein the second content is as follows: a corresponding positive invoice code and a corresponding positive invoice number;
when the type of the to-be-invoiced ticket is judged to be the invoicing, whether the remark to be invoiced contains third content is judged, when the remark to be invoiced does not contain the third content, the to-be-invoiced ticket is verified to be not compliant, and the third content is as follows: the invoicing remarks indicate the tax number and name of the enterprise to be opened;
when the type of the to-be-invoiced ticket is judged to be a difference taxation blue ticket, whether the remark of the to-be-invoiced ticket contains fourth content is judged, and when the remark of the to-be-invoiced ticket does not contain the fourth content, the to-be-invoiced ticket is verified to be not compliant, wherein the fourth content is as follows: the difference tax blue ticket needs to be marked at the beginning of remarking;
when the type of the to-be-invoiced ticket is judged to be the difference taxation red ticket, whether the remark of the to-be-invoiced ticket contains fifth content is judged, and when the remark of the to-be-invoiced ticket does not contain the fifth content, the non-compliance of the to-be-invoiced ticket is verified, wherein the fifth content is as follows: the difference taxation red ticket needs to be marked at the beginning of the remark.
7. The billing verification method of any of claims 1-6, wherein the method further comprises:
and when the invoices to be invoiced are in a tax-containing mode, converting the invoices to be invoiced into a non-tax mode according to a preset price and tax separation algorithm.
8. An invoicing verification apparatus, comprising:
the special character checking module is used for calling a preset special character library corresponding to the invoices according to the invoices to be invoiced to check the mandatory items of the invoices;
the tax number checking module is used for calling a preset tax number rule corresponding to the length according to the length of the tax number to be invoiced to check the tax number to be invoiced;
the data item length checking module is used for calling a preset data item length rule corresponding to the invoicing type according to the invoicing type to check the length of the data item to be invoiced;
the data item format checking module is used for calling a preset data item format rule corresponding to the invoicing type according to the invoicing type to check the format of the data item to be invoiced;
the remark checking module is used for calling a preset remark checking rule corresponding to the kind of the invoice to be invoiced according to the kind of the invoice to be invoiced to check the remark to be invoiced;
and the error checking module is used for carrying out sum error checking, tax error checking and invoice total error checking on the invoices to be invoiced.
9. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
10. An electronic device, comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to carry out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011446042.XA CN112581196A (en) | 2020-12-08 | 2020-12-08 | Billing verification method and device, readable medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011446042.XA CN112581196A (en) | 2020-12-08 | 2020-12-08 | Billing verification method and device, readable medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112581196A true CN112581196A (en) | 2021-03-30 |
Family
ID=75131272
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011446042.XA Pending CN112581196A (en) | 2020-12-08 | 2020-12-08 | Billing verification method and device, readable medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112581196A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105809814A (en) * | 2014-12-30 | 2016-07-27 | 航天信息股份有限公司 | Invoice certification system supporting multiple invoice types and method |
| CN107818484A (en) * | 2016-09-14 | 2018-03-20 | 北京京东尚科信息技术有限公司 | Manage the method and system for rule of making out an invoice |
| CN109685586A (en) * | 2017-10-18 | 2019-04-26 | 航天信息股份有限公司 | A kind of processing method and system of VAT invoice data |
| CN110163735A (en) * | 2019-04-09 | 2019-08-23 | 平安科技（深圳）有限公司 | Concerning taxes data processing method, device, computer equipment and storage medium |
| CN111222928A (en) * | 2019-12-30 | 2020-06-02 | 航天信息股份有限公司 | Method and system for monitoring enterprise standard invoicing |
-
2020
- 2020-12-08 CN CN202011446042.XA patent/CN112581196A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105809814A (en) * | 2014-12-30 | 2016-07-27 | 航天信息股份有限公司 | Invoice certification system supporting multiple invoice types and method |
| CN107818484A (en) * | 2016-09-14 | 2018-03-20 | 北京京东尚科信息技术有限公司 | Manage the method and system for rule of making out an invoice |
| CN109685586A (en) * | 2017-10-18 | 2019-04-26 | 航天信息股份有限公司 | A kind of processing method and system of VAT invoice data |
| CN110163735A (en) * | 2019-04-09 | 2019-08-23 | 平安科技（深圳）有限公司 | Concerning taxes data processing method, device, computer equipment and storage medium |
| CN111222928A (en) * | 2019-12-30 | 2020-06-02 | 航天信息股份有限公司 | Method and system for monitoring enterprise standard invoicing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109949141B (en) | Financial settlement method and device | |
| CN107016420A (en) | A kind of method for processing business and device | |
| CN111198873B (en) | Data processing method and device | |
| CN111562965A (en) | Page data verification method and device based on decision tree | |
| CN111199145A (en) | Method, device, storage medium and electronic equipment for generating value-added tax report | |
| US20060039543A1 (en) | Rate modelling | |
| WO2024131523A1 (en) | Freight service processing method and computing device | |
| CN111142863A (en) | Page generation method and device | |
| CN115292344A (en) | Data dictionary construction method and device, electronic equipment and storage medium | |
| CN112581196A (en) | Billing verification method and device, readable medium and electronic equipment | |
| CN111914548A (en) | Intelligent document filling method and system and related equipment | |
| TWI501617B (en) | System and method for issuing electronic invoice by mobile phone | |
| WO2020080958A1 (en) | Systems and methods for encoding data in an electronic transaction | |
| CN113379019B (en) | Verification code generation method and device, storage medium and electronic equipment | |
| CN114444502A (en) | Chinese address detection method and device, equipment, medium and product thereof | |
| CN111865726B (en) | Service message testing method, device, computer system and storage medium | |
| CN111488180B (en) | Service information processing method and device, electronic equipment and storage medium | |
| CN114239532A (en) | Report generation method and device | |
| CN111210329A (en) | Accounting document generation method and device, storage medium and electronic equipment | |
| CN112990990A (en) | Invoice issuing method, device and system | |
| TWM588277U (en) | System for conversion of delivery file | |
| CN113515332B (en) | Data generation method, device, equipment and storage medium | |
| JP2000181975A (en) | Slip processing system and method using plural currencies | |
| CN117196876B (en) | Task money settlement method and device, electronic equipment and storage medium | |
| CN112749999A (en) | Method and system for issuing invoices in batches |
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 |