CN113506161A - Invoice checking method and device, storage medium and electronic equipment - Google Patents
Invoice checking method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN113506161A CN113506161A CN202110802898.4A CN202110802898A CN113506161A CN 113506161 A CN113506161 A CN 113506161A CN 202110802898 A CN202110802898 A CN 202110802898A CN 113506161 A CN113506161 A CN 113506161A
- Authority
- CN
- China
- Prior art keywords
- data
- invoice
- financial
- detail
- checking
- 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
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/123—Tax preparation or submission
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/125—Finance or payroll
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Technology Law (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Data Mining & Analysis (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses a method and a device for checking invoices, electronic equipment and a storage medium, and relates to the field of office automation. The invoice checking method comprises the following steps: acquiring invoice detail data; wherein the invoice detail data comprises a plurality of invoice data; acquiring financial detail data; wherein the financial detail data comprises a plurality of financial data; checking the invoice detail data and the financial detail data according to preset rule data; when the verification fails, a verification difference report is generated. The invoice data can be automatically checked, and checking efficiency and accuracy are improved.
Description
Technical Field
The present application relates to the field of office automation, and in particular, to a method, a system, an apparatus, a storage medium, and an electronic device for invoice verification.
Background
In the enterprise tax payment link, the consistency of the accounting data and the bill data is ensured before the value-added tax declaration. However, as the scale of enterprises and the complexity of business fields and the related transaction amount and transaction amount are enlarged, the management of business data and financial data is disjointed, and the risk of data inconsistency is increased. At present, most enterprises check invoice data in a mode of manually checking accounts one by one and combining invoices one by one with a general data statistical tool (such as excel, WPS and a digital calculator) and the like. The manual processing mode brings low efficiency of enterprise tax management and high risk of error-prone related work.
Disclosure of Invention
In order to solve the technical problems, the application provides an invoice checking method, a related device and a storage medium, and solves the problems of inaccuracy and low efficiency in manual invoice checking in the related technology.
In a first aspect, the present application provides a method for checking an invoice, including:
acquiring invoice detail data; wherein the invoice detail data comprises a plurality of invoice data;
acquiring financial detail data; wherein the financial detail data comprises a plurality of financial data;
checking the invoice detail data and the financial detail data according to preset rule data;
when the verification fails, a verification difference report is generated.
In a second aspect, the present application provides an invoice checking device, including:
the acquiring unit is used for acquiring invoice detail data; wherein the invoice detail data comprises a plurality of invoice data;
the acquisition unit is further used for acquiring financial detail data; wherein the financial detail data comprises a plurality of financial data;
the checking unit is used for checking the invoice detail data and the financial detail data according to preset rule data;
and the generating unit is used for generating a verification difference report when the verification fails.
In another aspect, the present application provides an apparatus, which may implement the invoice checking method of the first aspect. For example, the apparatus may be a chip (such as a baseband chip, or a communication chip, etc.) or a server. The above-described method may be implemented by software, hardware, or by executing corresponding software by hardware.
In one possible implementation manner, the structure of the apparatus includes a processor, a memory; the processor is configured to support the device to execute corresponding functions in the invoice checking method. The memory is used for coupling with the processor, which holds the necessary programs (instructions) and/or data for the device. Optionally, the apparatus may further include a communication interface for supporting communication between the apparatus and other network elements.
In another possible implementation manner, the apparatus may include a unit module for performing corresponding actions in the above method.
In yet another possible implementation, the wireless communication device includes a processor and a transceiver, the processor is coupled to the transceiver, and the processor is configured to execute a computer program or instructions to control the transceiver to receive and transmit information; the processor is further configured to implement the above-described method when the processor executes the computer program or instructions.
Yet another aspect of the present application provides an apparatus, comprising: a memory and a processor; wherein the memory stores a set of program codes, and the processor is configured to call the program codes stored in the memory and execute the method of the aspects.
The application further provides an electronic device comprising the above apparatus. Electronic devices include, but are not limited to, cell phones, computers, tablets, personal computers, servers or workstations, and the like.
Yet another aspect of the present application provides a computer-readable storage medium having stored therein instructions, which when executed on a computer, cause the computer to perform the method of the above-described aspects.
Yet another aspect of the present application provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the above-described aspects.
The method comprises the steps of obtaining invoice data and financial data within a specified range, checking the invoice detail data and the financial detail data according to preset rule data, generating a checking difference report when checking fails, automatically checking the invoice data and the financial data to be declared before value-added tax declaration, meeting the requirement of consistency of the tax amount of the invoice data and the tax amount of the financial data, and solving the problems of low efficiency and poor accuracy caused by manual checking in the related technology.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a diagram of a network architecture provided by an embodiment of the present application;
FIG. 2 is a flow chart illustrating a method for invoice reconciliation according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an invoice checking device provided in an embodiment of the present application
Fig. 4 is another schematic structural diagram of an invoice verification device provided in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance. It will be apparent to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
Fig. 1 shows an exemplary system architecture of an invoice reconciliation method or an invoice reconciliation apparatus that can be applied to the present application.
As shown in fig. 1, the system architecture may include a finance system 101, an invoice verification device 102 (hereinafter referred to as verification device 102), and a tax system 103. The financial system is deployed in the enterprise, and the tax system is deployed in the tax bureau. The financial system 101 and the tax system 103 may be hardware or software. When the fiscal system 101 and the tax system 103 are hardware, the fiscal system 101, the collating device 102 and the tax system 103 may communicate with each other via a network, which is used as a medium for providing communication links between the above-mentioned units. The network may include various types of wired or wireless communication links, such as: the wired communication link comprises an optical fiber, a twisted pair of wires, or a coaxial cable, and the wireless communication link comprises: a bluetooth communication link, a WIreless-FIdelity (Wi-Fi) communication link, or a microwave communication link, etc. The financial system 101 and the verification means 102 may be deployed on the same physical machine or on different physical machines.
The collating device 102 may be hardware or software. When the collating device 102 is hardware, it may be implemented as a distributed server cluster composed of a plurality of servers, or may be implemented as a single server. When the verification apparatus 102 is software, it may be implemented as a plurality of software or software modules (for example, for providing distributed services), or may be implemented as a single software or software module, and is not limited in particular.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. Any number of terminal devices, networks, and servers may be used, as desired for implementation.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
Referring to fig. 2, fig. 2 is a schematic flow chart of an invoice verification method provided in an embodiment of the present application, where the method includes:
s201, acquiring invoice detail data.
The invoice detail data comprises invoice data of a plurality of value-added tax invoices, and the fields contained in the invoice data are as follows: the invoice data specifically comprises the following components of invoicing units, invoicing dates, purchasing units, tax types, tax rates, tax amount, amount and the like: the value-added tax invoice collection data, the invoice deduction and transfer data and the invoice checking data are obtained. The verification means may obtain invoice detail data from a financial system of the enterprise or a tax system of the tax bureau within a specified invoice range, which may be a specified month and/or a specified billing unit, for example: the checking device acquires invoice data of invoices issued by the unit of 7 months A.
In one or more possible embodiments, the checking device obtains invoice detail data from a tax system, the user selects a tax period for authentication in the tax system based on an operation interface, the tax system screens out invoice data according to the tax period for authentication, then the user checks invoice data needing deduction based on the operation interface, and the checking device takes invoice data with deduction type of deduction as final invoice detail data.
In one or more possible embodiments, the checking device obtains invoice data from a financial system of the enterprise, the state of the invoice data of the financial system is divided into a managed invoice and an unmanaged invoice, the managed invoice data has a managed invoice time, the checking device obtains invoice data in a specified managed period, the managed period is a time interval, the financial system or the checking device stores a checked account table, the checked account table stores checked (i.e., checked account) invoice data, and the checking device deducts the invoice data in the managed period from the invoice data in the checked account table to obtain invoice detail data.
In one or more possible embodiments, the invoice data further includes an invoicing time, the checking device obtains invoice data in a specified invoicing period, the invoicing period is a time interval, the accounting system or the checking device stores a checked table in which checked (i.e. checked) invoice data is stored, and the checking device deducts invoice data in the checked table from the invoice data in the invoicing period to obtain final invoice detail data.
Further, the collation apparatus further includes:
and displaying the invoice detail data according to the invoice status classification.
For example: the checking device displays the invoice detail data of the received invoice and the invoice not received in a classified way, or displays the invoice detail data of the received invoice and the invoice not authenticated according to the authenticated invoice (the withholding type is withholding checking). The invoice detail data can be displayed on a financial system, a tax system, a visual interface of a user side and the like.
S202, acquiring financial detail data.
Wherein the financial detail data comprises a plurality of financial data, the financial data may be data generated from accounting documents or documents of the enterprise, and the fields in the financial data include: abstract, subject, amount, tax amount, certificate making date, lending direction, etc., such as: the financial data specifically includes: the financial evidence making data, the reimbursement sheet and the material purchase sheet data. The checking device acquires the financial detail data in the financial system according to the designated range, the checking device acquires the financial detail data from the financial system based on the designated invoice range in the S201, and the time interval of the financial data is lagged behind the time interval of the invoice data when the time interval is set because the financial data generally lags behind the invoice data.
In one or more possible embodiments, the reconciliation device obtains financial data for a specified subject during the accounting period, and deducts financial data from the reconciled table from the financial data for the specified subject during the accounting period to obtain final financial detail data. For example: the user sets a billing period through an operation interface, financial data is screened in the billing period, then the financial data with the appointed subject of 'tax due, value added tax due and income tax due' is acquired, and the final financial data is obtained after the financial data in the reconciliation table is deducted.
And S203, checking the invoice detail data and the financial detail data according to preset rule data.
The invoice can generate a corresponding accounting document after being used, so that the invoice and the accounting document have an association relationship, and the rule data represents the pre-established association relationship between the invoice and the accounting document. For example: the checking device collects the value-added tax input invoice from the tax system to form an invoice standing book, a calling interface of the invoice standing book is provided for a service end to use, the financial system generates an accounting certificate of the invoice after the service end calls the invoice, and then the financial system stores the incidence relation between the invoice and the accounting certificate.
In one or more possible embodiments, the generating of the rule data includes:
the method comprises the steps of establishing a first association relationship between invoice data and financial data according to money, namely establishing the first association relationship between the invoice and the accounting voucher with the same money, wherein the money on the common invoice and the accounting voucher is random, and the establishment of the association relationship between the invoice data of the invoice and the financial data of the accounting voucher through the money has high accuracy in a specified time interval.
Establishing a second incidence relation between the invoice data and the financial data according to the invoice seller unit and the current unit in the voucher auxiliary account; the method comprises the steps of recording the units with the current of each accounting voucher in a voucher auxiliary account, enabling the invoice seller unit to correspond to invoice data, enabling the current unit to correspond to the accounting voucher, and establishing the incidence relation between the invoice and the accounting voucher according to the same characteristics of the invoice seller unit and the current unit in a specified time interval.
And establishing a third association relationship between the invoice data and the financial data according to the price and tax sum of the invoice seller unit and the current unit in the certificate auxiliary account, wherein the price and tax sum represents the sum of the amount and the tax amount, and the invoice and the accounting certificate with the same price and tax sum are established with the association relationship in a specified time interval.
And generating rule data according to the first association relationship, the second association relationship and the third association relationship, wherein the rule data simultaneously comprises the three association relationships, and the invoice data and the financial data can be checked when the invoice data and the financial data meet any one of the association relationships.
Further, the checking the invoice detail data and the financial detail data according to preset rule data includes:
selecting a target invoice data from the invoice detail data in a traversal mode;
querying the financial data associated with the target invoice data in the financial detail data according to the rule data; and when the tax amount of the target invoice data is equal to that of the target financial data, the target invoice data and the target financial data are successfully checked. And if the target financial data associated with the target invoice data is not inquired, the target invoice data is not checked. It is understood that the present application may also traverse and select target financial data from the financial detail data to automatically check the target invoice data with the association relationship.
Further, checking according to the front-end service: and if the invoice and the accounting voucher have an association relationship and are consistent in tax amount, the verification is successful. And searching the voucher of the corresponding month and the invoice which has the association relation with the voucher, and automatically checking that the sum of the income tax subject amount is equal to the sum of the invoice tax (if the effective tax is available, and if the effective tax is unavailable, the tax is available).
Further, the consistency of the value-added tax invoice issued in about 1 to 3 months after posting is checked according to a single round-trip unit and the tax amount: the current voucher only has one unit of communication, the sum of the subject amount of the income tax is obtained, about 1 to 3 months is obtained (for example, if the accounting period is 2020-9 months, invoice data with invoicing date of 2020-7-1 to 2020-9-31 days is obtained), and according to the purchasing unit of a single invoice and the invoice tax amount, if the check is consistent, the sum is automatically matched. If there are multiple invoices of the same buyer unit and invoice tax amount or multiple same accounting data in the same period, no check is made.
And S204, generating a check difference report when the check fails.
Wherein, when the invoice data does not have the associated financial data or the invoice data and the tax amount of the associated financial data are different, the checking fails, a checking difference report is generated, and the checking difference report comprises the following fields: invoice data which is not related to financial data and the quantity of the invoice data, and invoice data which is different from the financial detailed data and the invoice detailed data in tax amount difference and tax amount and the quantity of the invoice data. For invoice data or financial data that fails to be checked, the financial staff can adjust the invoice data or financial data according to the check difference report. And when the verification is successful, displaying a success prompt message, and then executing a subsequent invoice declaration process.
According to the embodiment of the application, invoice data and financial data in a specified range are obtained, the invoice detail data and the financial detail data are checked according to preset rule data, a check difference report is generated when the check fails, automatic check of the invoice data and the financial data to be declared is achieved before value-added tax declaration, the requirement of the tax amount of the invoice data and the tax amount consistency of the financial data is met, the problems that efficiency is low and accuracy is poor due to manual check in the related technology are solved, automatic check is conducted based on the preset rule data, and the invoice check efficiency and accuracy can be improved.
The invoice reconciliation method is described in detail above with reference to FIG. 2. Correspondingly, the structure of a device in the embodiment of the application is schematically shown.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a checking apparatus 3 for an invoice provided in an embodiment of the present application, where the checking apparatus 3 for an invoice may include: an acquisition unit 301, a collation unit 302, and a generation unit 303.
An obtaining unit 301, configured to obtain invoice detail data; wherein the invoice detail data comprises a plurality of invoice data;
the acquiring unit 301 is further configured to acquire financial detail data; wherein the financial detail data comprises a plurality of financial data;
a checking unit 302, configured to check the invoice detail data and the financial detail data according to preset rule data;
a generating unit 303, configured to generate a report of the verification discrepancy when the verification fails.
In one or more possible embodiments, the obtaining invoice detail data includes:
selecting invoice data with deduction type of deduction checking in a tax system according to the tax period of authentication to obtain final invoice detail data; or
Acquiring invoice data in a receiving and managing period;
deducting invoice data in the reconciliation table from the invoice data in the receipt and management period to obtain invoice detail data; or
Acquiring invoice data in an invoicing period;
and deducting invoice data in the reconciliation table from the invoice data in the invoicing period to obtain final invoice detail data.
In one or more possible embodiments, the financial details data obtained includes:
acquiring financial data of a specified subject in a billing period;
and deducting the financial data in the checked account table from the financial data of the specified subject in the accounting period to obtain final financial detail data.
In one or more possible embodiments, the collating means 3 further includes:
the rule setting unit is used for establishing a first incidence relation between the invoice data and the financial data according to the amount of money;
establishing a second incidence relation between the invoice data and the financial data according to the invoice seller unit and the current unit in the certificate auxiliary account
Establishing a third association relation between the invoice data and the financial data according to the price and tax sum of the invoice seller unit and the current unit in the certificate auxiliary account;
and generating rule data according to the first association relationship, the second association relationship and the third association relationship.
In one or more possible embodiments, the checking the invoice detail data and the financial detail data according to preset rule data includes:
selecting a target invoice data from the invoice detail data;
querying the financial data associated with the target invoice data in the financial detail data according to the rule data;
and when the tax amount of the target invoice data is equal to that of the target financial data, the target invoice data and the target financial data are successfully checked.
In one or more possible embodiments, the collating means 3 further includes:
and the display unit is used for displaying the invoice detail data according to the invoice status classification.
In one or more possible embodiments, the discrepancy report includes: invoice data which is not related to financial data and the quantity of the invoice data, and invoice data which is different from the financial detailed data and the invoice detailed data in tax amount difference and tax amount and the quantity of the invoice data.
The embodiment of the present application and the embodiment of the method in fig. 2 are based on the same concept, and the technical effects brought by the embodiment are also the same, and the specific process may refer to the description of the embodiment of the method in fig. 2, and will not be described again here.
The invoice checking device 3 may be a server or a terminal device, and the invoice checking device 4 may also be a field-programmable gate array (FPGA), an application-specific integrated chip (asic), a system on chip (SoC), a Central Processor Unit (CPU), a Network Processor (NP), a digital signal processing circuit, a Micro Controller Unit (MCU), or a Programmable Logic Device (PLD) or other integrated chips, which implement related functions.
Referring to fig. 4, a schematic structural diagram of an invoice verification apparatus is provided in an embodiment of the present application. As shown in fig. 4, the checking device 400 may be the checking device in fig. 1, and the checking device 400 for the invoice may include: at least one processor 401, at least one network interface 404, a user interface 403, memory 405, at least one communication bus 402.
Wherein a communication bus 402 is used to enable connective communication between these components.
Optionally, the user interface 403 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 403 may also include a standard wired interface and a wireless interface.
The network interface 404 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.
The Memory 405 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 405 includes a non-transitory computer-readable medium. The memory 405 may be used to store instructions, programs, code sets, or instruction sets. The memory 405 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 405 may alternatively be at least one storage device located remotely from the aforementioned processor 401. As shown in fig. 4, the memory 405, which is a type of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and an application program.
In the invoice checking apparatus 400 shown in fig. 4, the user interface 403 is mainly used for providing an input interface for the user to obtain data input by the user; the processor 401 may be configured to call an application program stored in the memory 405 for configuring an application program interface, and specifically perform the following steps:
acquiring invoice detail data; wherein the invoice detail data comprises a plurality of invoice data;
acquiring financial detail data; wherein the financial detail data comprises a plurality of financial data;
checking the invoice detail data and the financial detail data according to preset rule data;
when the verification fails, a verification difference report is generated.
In one or more possible embodiments, processor 401 executing the obtaining invoice detail data includes:
selecting invoice data with deduction type of deduction checking in a tax system according to the tax period of authentication to obtain final invoice detail data; or
Acquiring invoice data in a receiving and managing period;
deducting invoice data in the reconciliation table from the invoice data in the receipt and management period to obtain invoice detail data; or
Acquiring invoice data in an invoicing period;
and deducting invoice data in the reconciliation table from the invoice data in the invoicing period to obtain final invoice detail data.
In one or more possible embodiments, processor 401 performs the obtaining financial specification data including:
acquiring financial data of a specified subject in a billing period;
and deducting the financial data in the checked account table from the financial data of the specified subject in the accounting period to obtain final financial detail data.
In one or more possible embodiments, processor 401 is further configured to perform: establishing a first incidence relation between the invoice data and the financial data according to the amount;
establishing a second incidence relation between the invoice data and the financial data according to the invoice seller unit and the current unit in the certificate auxiliary account
Establishing a third association relation between the invoice data and the financial data according to the price and tax sum of the invoice seller unit and the current unit in the certificate auxiliary account;
and generating rule data according to the first association relationship, the second association relationship and the third association relationship.
In one or more possible embodiments, processor 401 performs said checking of said invoice detail data and financial detail data according to preset rule data, including:
selecting a target invoice data from the invoice detail data;
querying the financial data associated with the target invoice data in the financial detail data according to the rule data;
and when the tax amount of the target invoice data is equal to that of the target financial data, the target invoice data and the target financial data are successfully checked.
In one or more possible embodiments, processor 401 is further configured to perform:
and displaying the invoice detail data according to the invoice status classification.
In one or more possible embodiments, the discrepancy report includes: invoice data which is not related to financial data and the quantity of the invoice data, and invoice data which is different from the financial detailed data and the invoice detailed data in tax amount difference and tax amount and the quantity of the invoice data.
The concept of this embodiment is the same as that of the embodiment of the method in fig. 2, and the technical effects brought by the embodiment are also the same, and the specific process can refer to the description of the embodiment in fig. 2, and will not be described again here.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory or a random access memory.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.
Claims (10)
1. An invoice checking method is characterized by comprising the following steps:
acquiring invoice detail data; wherein the invoice detail data comprises a plurality of invoice data;
acquiring financial detail data; wherein the financial detail data comprises a plurality of financial data;
checking the invoice detail data and the financial detail data according to preset rule data;
when the verification fails, a verification difference report is generated.
2. The method of claim 1, wherein said obtaining invoice detail data comprises:
selecting invoice data with deduction type of deduction checking in a tax system according to the tax period of authentication to obtain final invoice detail data; or
Acquiring invoice data in a receiving and managing period;
deducting invoice data in the reconciliation table from the invoice data in the receipt and management period to obtain invoice detail data; or
Acquiring invoice data in an invoicing period;
and deducting invoice data in the reconciliation table from the invoice data in the invoicing period to obtain final invoice detail data.
3. The method of claim 1, wherein said obtaining financial detail data comprises:
acquiring financial data of a specified subject in a billing period;
and deducting the financial data in the checked account table from the financial data of the specified subject in the accounting period to obtain final financial detail data.
4. The method according to claim 1, 2 or 3, wherein before the obtaining invoice detail data and financial detail data within a preset range, the method further comprises:
establishing a first incidence relation between the invoice data and the financial data according to the amount;
establishing a second incidence relation between the invoice data and the financial data according to the invoice seller unit and the current unit in the voucher auxiliary account;
establishing a third association relation between the invoice data and the financial data according to the price and tax sum of the invoice seller unit and the current unit in the certificate auxiliary account;
and generating rule data according to the first association relationship, the second association relationship and the third association relationship.
5. The method according to claim 4, wherein said checking said invoice and financial details data according to preset rules data comprises:
selecting a target invoice data from the invoice detail data;
querying the financial data associated with the target invoice data in the financial detail data according to the rule data;
and when the tax amount of the target invoice data is equal to that of the target financial data, the target invoice data and the target financial data are successfully checked.
6. The method of claim 1, 2 or 4, further comprising:
and displaying the invoice detail data according to the invoice status classification.
7. The method of claim 6, wherein the discrepancy report comprises: invoice data which is not related to financial data and the quantity of the invoice data, and invoice data which is different from the financial detailed data and the invoice detailed data in tax amount difference and tax amount and the quantity of the invoice data.
8. An invoice reconciliation apparatus comprising:
the acquiring unit is used for acquiring invoice detail data; wherein the invoice detail data comprises a plurality of invoice data;
the acquisition unit is further used for acquiring financial detail data; wherein the financial detail data comprises a plurality of financial data;
the checking unit is used for checking the invoice detail data and the financial detail data according to preset rule data;
and the generating unit is used for generating a verification difference report when the verification fails.
9. An electronic device comprising a processor and a memory, wherein the memory is configured to store a computer program comprising program instructions, and wherein the processor is configured to invoke the program instructions to perform the method of any of claims 1-7.
10. A computer-readable storage medium, characterized in that the computer storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110802898.4A CN113506161A (en) | 2021-07-15 | 2021-07-15 | Invoice checking method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110802898.4A CN113506161A (en) | 2021-07-15 | 2021-07-15 | Invoice checking method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113506161A true CN113506161A (en) | 2021-10-15 |
Family
ID=78012919
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110802898.4A Pending CN113506161A (en) | 2021-07-15 | 2021-07-15 | Invoice checking method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113506161A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170316474A1 (en) * | 2016-04-27 | 2017-11-02 | Intuit Inc. | Method and system for providing invoices generated through a business invoicing system to a customer user of a personal financial management and bill payment system |
| CN109583827A (en) * | 2018-10-15 | 2019-04-05 | 平安科技（深圳）有限公司 | Invoice collation method, apparatus, computer equipment and storage medium |
| CN111028026A (en) * | 2019-12-20 | 2020-04-17 | 邦邦汽车销售服务(北京)有限公司 | Invoice matching method and system |
| CN111105548A (en) * | 2019-12-13 | 2020-05-05 | 远光软件股份有限公司 | Batch checking device and method for value-added tax special invoices |
| CN111402019A (en) * | 2020-03-09 | 2020-07-10 | 南京金信通信息服务有限公司 | Value-added tax invoice online verification method and system suitable for enterprise settlement |
| CN111798221A (en) * | 2020-07-20 | 2020-10-20 | 四川中电启明星信息技术有限公司 | Value-added tax invoice management system |
| CN112258256A (en) * | 2020-10-22 | 2021-01-22 | 北京中电普华信息技术有限公司 | Method and system for processing invoice posting |
| CN112785402A (en) * | 2021-01-28 | 2021-05-11 | 南方电网深圳数字电网研究院有限公司 | Bill information processing method, bill information processing system, and storage medium |
| CN112883858A (en) * | 2021-02-07 | 2021-06-01 | 北京奥普思凯科技有限公司 | Reimbursement invoice auditing method and device and storage medium |
-
2021
- 2021-07-15 CN CN202110802898.4A patent/CN113506161A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170316474A1 (en) * | 2016-04-27 | 2017-11-02 | Intuit Inc. | Method and system for providing invoices generated through a business invoicing system to a customer user of a personal financial management and bill payment system |
| CN109583827A (en) * | 2018-10-15 | 2019-04-05 | 平安科技（深圳）有限公司 | Invoice collation method, apparatus, computer equipment and storage medium |
| CN111105548A (en) * | 2019-12-13 | 2020-05-05 | 远光软件股份有限公司 | Batch checking device and method for value-added tax special invoices |
| CN111028026A (en) * | 2019-12-20 | 2020-04-17 | 邦邦汽车销售服务(北京)有限公司 | Invoice matching method and system |
| CN111402019A (en) * | 2020-03-09 | 2020-07-10 | 南京金信通信息服务有限公司 | Value-added tax invoice online verification method and system suitable for enterprise settlement |
| CN111798221A (en) * | 2020-07-20 | 2020-10-20 | 四川中电启明星信息技术有限公司 | Value-added tax invoice management system |
| CN112258256A (en) * | 2020-10-22 | 2021-01-22 | 北京中电普华信息技术有限公司 | Method and system for processing invoice posting |
| CN112785402A (en) * | 2021-01-28 | 2021-05-11 | 南方电网深圳数字电网研究院有限公司 | Bill information processing method, bill information processing system, and storage medium |
| CN112883858A (en) * | 2021-02-07 | 2021-06-01 | 北京奥普思凯科技有限公司 | Reimbursement invoice auditing method and device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110473036A (en) | A kind of method and apparatus generating order number | |
| CN113112348A (en) | Processing method and device of social security data, electronic equipment and storage medium | |
| CN113506161A (en) | Invoice checking method and device, storage medium and electronic equipment | |
| CN110852868A (en) | Automatic auditing method and device, equipment and server | |
| CN113592450A (en) | Invoice checking method and device based on central platform invoice center, storage medium and electronic equipment | |
| CN115222499A (en) | Internal settlement method, internal settlement device, storage medium, and settlement server | |
| CN113313566A (en) | Internal settlement method, internal settlement device, storage medium and electronic equipment | |
| CN114004668A (en) | Order management method and system | |
| CN109272399B (en) | Credit card management method and device | |
| CN113888340A (en) | Docking processing method, device, equipment and storage medium for configured insurance products | |
| CN113450166A (en) | Sales invoice processing method and corresponding business management system | |
| CN112862264A (en) | Enterprise operation condition analysis method, computer device and computer storage medium | |
| CN110782330A (en) | Configuration method of accounting voucher of financial cloud platform | |
| CN111801698A (en) | Payment two-dimensional code management method, payment two-dimensional code management equipment, payment system and storage medium | |
| CN110070442A (en) | A kind of refund processing method, server and storage medium | |
| CN110020845A (en) | For handling terminal, method and the storage medium of transaction | |
| CN113643014B (en) | Block chain-based transaction management method, apparatus, device, medium, and program | |
| CN113283974A (en) | Accounting document checking method and device, storage medium and electronic equipment | |
| CN113592444A (en) | Calculation method and device of money transfer amount, storage medium and electronic equipment | |
| CN113506092A (en) | Method and device for managing research and development adding items, storage medium and electronic equipment | |
| CN113298520A (en) | Method and device for generating out-of-price fund issuance voucher, storage medium and electronic equipment | |
| CN115170260A (en) | Financial certification making method and device, storage medium and computer equipment | |
| CN116205398A (en) | Material management method, device, terminal equipment and storage medium | |
| CN114066583A (en) | Method and device for cancelling internal cash flow, storage medium and terminal equipment | |
| CN115131013A (en) | Monitoring method, device, storage medium and computer equipment for fund settlement |
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 |