Invoice application management method and device and computer readable storage medium

Abstract

The invention provides an invoice application management method, an invoice application management device and a computer readable storage medium. The method comprises the following steps: acquiring invoice operation request information sent by a business system; furthermore, an invoice operation interface is provided for the business system, operation information executed by the user on the invoice operation interface is acquired, and corresponding target operation is executed according to the operation information; the target operation comprises querying a target invoice from a preset invoice pool, uploading the target invoice to the invoice pool or issuing the target invoice, invoice information of a plurality of invoices is recorded in the invoice pool, and a business invoice relationship between each occupied invoice and the associated business is recorded in the invoice pool; and obtaining a request for establishing business invoice relation data for the target invoice sent by the business system, searching the corresponding target invoice according to the business invoice relation data, recording the target invoice as an occupied state, and recording a target business occupying the target invoice. The invention further provides an invoice application management device for implementing the method and a computer readable storage medium. Unified invoice management in an enterprise can be realized, and data redundancy is avoided.

Description

Technical Field

[0001] The present invention relates to the field of invoice management, and in particular, to an invoice application management method, and an invoice application management device and a computer-readable storage medium for implementing the method. Background Art

[0002] At present, according to the management requirements of the expenditure reporting business of enterprises, the existing expenditure documents are manually configured and customized to achieve the integration of information in different business areas, including expense information, budget information, invoice information, etc. Since enterprises use a large number of invoices in production and operation, including input invoices and output invoices, and different invoices involve different business systems, in order to manage invoices, each business system usually designs an invoice control program for its own business system, and each business system manages and stores its own invoices separately.

[0003] Invoice sub-table interfaces are defined for different business systems and different document types. The document sub-table needs to redundantly store part of the invoice face data and business-invoice relationship data, and dozens of pre-actions and post-actions need to be expanded to call different invoice verification interfaces and business-invoice relationship write-back interfaces during document delivery, review, and rollback. Due to the existence of the above problems, multiple business systems have multiple configuration entries for different documents, and the configuration is complex. Enterprise employees need to be familiar with the operation of different business systems, which has a high learning cost. In addition, the invoice operation interfaces of various business systems often cannot share logic. The coupling between the business system and the invoice sub-table interface and invoice data is high, and the maintainability is poor, resulting in redundant storage of a large amount of data.

[0004] Moreover, since each business system often needs to develop its own invoice management component, the development work of the invoice management component is repeated, which increases the company's operating costs. Summary of the invention

[0005] The first object of the present invention is to provide an invoice application management method for uniformly managing invoices of multiple business systems of an enterprise.

[0006] A second object of the present invention is to provide an invoice application management device for implementing the above-mentioned invoice application management method.

[0007] A third object of the present invention is to provide a computer-readable storage medium for implementing the above-mentioned invoice application management method.

[0008] To achieve the first purpose of the present invention, the invoice application management method provided by the present invention includes obtaining invoice operation request information issued by the business system; and, providing an invoice operation interface to the business system, and obtaining operation information performed by the user in the invoice operation interface, and performing corresponding target operations according to the operation information; the target operation includes querying the target invoice from a preset invoice pool, uploading the target invoice to the invoice pool, or issuing the target invoice, the invoice pool records the invoice information of multiple invoices, and the invoice pool records the business invoice relationship between each occupied invoice and the associated business; obtaining a request for establishing business invoice relationship data for the target invoice issued by the business system, searching for the corresponding target invoice according to the business invoice relationship data, recording the target invoice as being in an occupied state, and recording the target business occupying the target invoice.

[0009] As can be seen from the above scheme, the present invention designs a unified invoice application management device, and multiple different business systems can call the invoice application management device and manage invoices in a unified manner. The invoice application management device is provided with an invoice pool to uniformly manage the enterprise's incoming invoices and outgoing invoices, thereby avoiding redundant storage of invoice data in multiple different business systems. Since the invoice application management device provides a unified query and operation interface, users are prevented from repeatedly learning and becoming familiar with the invoice query and operation interfaces under different business systems.

[0010] In addition, according to whether each invoice is associated with a specific business, the invoice status can be automatically managed by setting the status of the target invoice, that is, whether the target invoice is occupied. This can ensure the automatic association of the corresponding relationship between the invoice and the business, and improve the accuracy of invoice management.

[0011] A preferred solution is that the method also includes: obtaining a request issued by the business system to delete the business-invoice relationship data for the target invoice, obtaining the recorded business-invoice relationship data for the target invoice, deleting the business-invoice relationship data for the target invoice, and recording the target invoice as being in an unoccupied state.

[0012] It can be seen that once the target invoice is released, the invoice application management device records the target invoice as unoccupied, so that the target invoice can be used by other businesses. In addition, once the association between the target invoice and the target business is cancelled, the invoice application management device can automatically delete the business-invoice relationship data corresponding to the target invoice, and can realize the automatic update of the invoice status.

[0013] A further solution is to obtain a request from the business system to establish business-invoice relationship data for the target invoice, and after searching for the corresponding target invoice based on the business-invoice relationship data, before recording the target invoice as being in an occupied state, further execute: determining that the target invoice is in an unoccupied state.

[0014] In this way, the business invoice relationship data between the target invoice and the target business is established only when it is determined that the target invoice is not in use, which can avoid the problem of repeated use and repeated reimbursement of the target invoice.

[0015] A further solution is to obtain a request from the business system to establish business-invoice relationship data for the target invoice, and after searching for the corresponding target invoice based on the business-invoice relationship data, if the target invoice is in an occupied state, return a prompt message indicating that the invoice is occupied to the business system.

[0016] It can be seen that once the target invoice has been occupied, it can no longer be occupied by the enterprise business, that is, the target invoice can only establish an association relationship with one business, thereby ensuring that each invoice can only correspond to one business.

[0017] A further solution is that the invoice pool also records the structured data, business-invoice relationship data, account-invoice relationship data and invoice format data of each invoice.

[0018] It can be seen that by uniformly storing various invoice structured data, business invoice relationship data, account invoice relationship data, invoice format data and other information through the invoice pool, it is possible to avoid the problem of data redundancy caused by each business system storing its own invoice data.

[0019] A further solution is that the invoice pool is an input invoice pool; providing an invoice operation interface to the business system includes: providing an invoice search interface to the business system, obtaining the target invoice from the input invoice pool after obtaining the search conditions entered by the user, and returning the data of the target invoice to the business system.

[0020] In this way, users can conveniently search for invoices through a unified invoice search interface, thereby improving invoice search efficiency.

[0021] A further solution is to return the target invoice data to the business system in accordance with the format requirements of the business system.

[0022] A further solution is that the invoice pool is an input invoice pool; when the target operation is to upload a target invoice to the invoice pool, the target invoice is verified, and after the target invoice passes the verification, the target invoice is recorded in the input invoice pool.

[0023] It can be seen that all the input invoices stored in the input invoice pool have been verified, thereby ensuring that all the invoice data stored in the input invoice pool are data that meet the verification requirements.

[0024] To achieve the second objective, the invoice application management device provided by the present invention includes a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, each step of the invoice application management method is implemented.

[0025] To achieve the third objective, the present invention provides a computer readable storage medium storing a computer program, and when the computer program is executed by a processor, each step of the invoice application management method is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 It is a structural block diagram of an embodiment of the input invoice application management device of the present invention.

[0027] Figure 2 It is a flow chart of an embodiment of the input invoice application management method of the present invention.

[0028] Figure 3 It is a structural block diagram of an embodiment of the sales invoice application management device of the present invention.

[0029] Figure 4 It is a flow chart of an embodiment of the sales invoice application management method of the present invention.

[0030] The present invention is further described below in conjunction with the accompanying drawings and embodiments. DETAILED DESCRIPTION

[0031] The invoice application management method of the present invention is implemented by an invoice application management device, which can be called by multiple business systems and provide unified invoice management services for multiple business systems. The invoice application management device of the present invention is provided with a processor and a memory, and a computer program is stored on the memory. The processor implements the above-mentioned invoice application management method by executing the computer program.

[0032] Embodiments of the input invoice application management method and input invoice application management device: See also Figure 1This embodiment provides an input invoice application management device 20, which can communicate with multiple business systems and be called by multiple business systems, for example, it can be called by the reimbursement business system 11, the engineering project system 12, the electricity fee settlement system 13, etc. Of course, it can also include other business systems such as the business travel reimbursement application system. Each business system can call the input invoice application management device 20 and perform invoice management work, such as inputting input invoices to the input invoice application management device 20, searching and querying input invoices from the input invoice application management device 20, or performing association operations on input invoices, such as corresponding a certain input invoice to a specific business. The input invoice application management device 20 can respond to the operations issued by each business system and return the execution results to each business system, such as the successful entry of a certain input invoice, or return the data of the input invoice obtained by the search, etc.

[0033] The input invoice application management device 20 has an input invoice pool 30 for storing input invoices generated by various business systems. Preferably, the input invoice pool 30 can store multiple types of invoices, including value-added tax invoices, fiscal bills, other invoices, etc. In addition, the input invoice pool 30 stores the invoice structured data 31, invoice status data 32, business relationship data 33, account-invoice relationship data 34, and invoice format data 35 of each input invoice. Since the input invoices of each business system are stored in the input invoice pool 30, each business system does not need to store the input invoices, thereby reducing the problem of data storage redundancy caused by each business system storing the input invoices separately. When the user needs to query the input invoice on the business system, the business system needs to call the input invoice application management device 20 to search and query the input invoice. After the input invoice application management device 20 returns the data of the input invoice to the business system, the user can browse the specific data of the input invoice on the business system.

[0034] A unified query interface module 21 and a unified operation interface module 22 are also provided in the input invoice application management device 20. When a user needs to query a certain input invoice through the front-end interface of a certain business system, a request message for querying the input invoice can be sent to the input invoice application management device 20. After receiving the request message for querying the input invoice, the input invoice application management device 20 returns a unified query interface to the business system. The returned unified query interface adopts a humanized interactive design, and is provided with multiple query methods such as advanced condition query, element retrieval query, and QR code scanning query. The user can also use a scanner, barcode scanning gun and other scanning devices to input search conditions, and query the input invoices in the input invoice pool 30 in combination with fuzzy matching query and precise positioning. After searching and obtaining the input invoice to be queried, the input invoice application management device 20 returns the data of the searched input invoice to the business system, such as the issuer of the invoice, the amount, etc.

[0035] The input invoice application management device 20 can receive the input invoices uploaded by various business systems. For this purpose, the input invoice application management device 20 is provided with a unified operation interface module 22. When each business system needs to upload the input invoice by itself, the input invoice application management device 20 provides each business system with a unified input invoice upload operation interface. The input invoice upload operation interface allows users to manually upload a single file, upload batch files, scan and upload QR codes, etc. The unified operation interface module 22 can also automatically identify, extract, and verify the invoice face information, person-invoice relationship information, invoice format, and image information of the uploaded input invoice through the character automatic recognition program, and extract it, and write it into the input invoice pool 30, making the data entry of the input invoice very convenient.

[0036] In addition, for the input invoices uploaded to the input invoice pool 30, the input invoice application management device 20 needs to check the input invoices, that is, to perform a compliance check. To this end, the input invoice application management device 20 sets input invoice compliance verification rules and input invoice duplication verification rules. Preferably, the verification rules can be preset according to the business management requirements of different invoice types. For example, the inspection rules include whether the purchaser's information name is incorrect, whether the purchaser's tax number is incorrect, and the linked invoice verification. Before the business application associates and references the invoice, the input invoice application management device 20 will also automatically perform a compliance check on the target input invoice that needs to be associated, and automatically query whether the target input invoice already has a business invoice relationship to achieve duplication verification. Once any non-compliance points are found, early warning prompts will be promptly fed back to ensure the risk control of business documents or business systems that effectively use invoices.

[0037] In addition, the input invoice application management device 20 will also manage the business-invoice relationship of the input invoice. When the business document or business system is in the stage of occupying a target input invoice, the input invoice application management device 20 will automatically write the business-invoice relationship data 33 of the target input invoice, for example, write it into the business-invoice relationship data table in the input invoice pool 30. When the business document or business system is in the stage of releasing the target input invoice, the input invoice application management device 20 will automatically search for the existing business-invoice relationship data 33 in the input invoice pool 30 for deletion. The operation of deleting the business-invoice relationship data 33 is performed automatically, without the need for each business application to process, which can reduce the risk of missed processing and erroneous processing, and accurately control the correctness of the business-invoice relationship data.

[0038] Combine the following Figure 2 The implementation process of the input invoice application management method is introduced. First, the input invoice application management device 20 executes step S11 to determine whether an operation of querying a target invoice issued by a certain business system is received. For example, a user initiates a request to search for a certain input invoice through a certain business system. The input invoice application management device 20 provides a unified query interface to the business system. The user can enter search keywords such as the invoice issuer, invoice date, invoice amount, etc. through the query interface. The input invoice application management device 20 searches for the target input invoice that meets the requirements from the input invoice pool 30, that is, executes step S12. Then, the input invoice application management device 20 returns the data of the searched target input invoice to the business system, and displays the data of the target input invoice in a preset format on the business system.

[0039] If the user needs to establish business-invoice relationship data for a target input invoice, the user sends a request to establish business-invoice relationship data for the target input invoice on the business system. At this time, the input invoice application management device 20 executes step S14 to obtain the request to establish business-invoice relationship data for the target input invoice, and executes step S15 to determine whether the current state of the target input invoice is occupied. Preferably, when the user first enters an input invoice into the input invoice pool 30, the input invoice is in an unoccupied state.

[0040] If the target input invoice is in an unoccupied state, step S16 is executed to record the input invoice as an occupied state, and record the target business associated with the target input invoice. At this time, the target input invoice and the target business form a one-to-one correspondence. Specifically, if a certain accommodation invoice is associated with a certain travel reimbursement business, then the accommodation invoice is occupied by the travel reimbursement business, and the accommodation invoice can no longer be used by other businesses, thereby avoiding the problem of repeated use and repeated reimbursement of the same invoice.

[0041] If in step S15, the target input invoice for which the user needs to establish business relationship data is in an occupied state, step S19 is executed to issue a prompt message indicating that the target input invoice is occupied, and no new business relationship data will be established. In this way, the same invoice can be prevented from being reused and reimbursed repeatedly.

[0042] Then, step S17 is executed, and the input invoice application management device 20 determines whether a request for deleting the business relationship data for the target input invoice is received. If yes, step S18 is executed to find the business ticket relationship data corresponding to the target input invoice from the business ticket relationship data table recorded in the input invoice pool 30, and delete the business ticket relationship data. At the same time, the state of the target input invoice is recorded as unoccupied. In this way, the target input invoice can be associated with other businesses again, that is, a business ticket relationship can be established with other businesses.

[0043] It can be seen that multiple business systems can manage input invoices through the same developed input invoice application management device 20, and there is no need to develop separate invoice management components for each business system, thereby reducing the internal development cost of the enterprise. In addition, the input invoice application management device 20 can uniformly store and manage the input invoices of multiple business systems, thereby reducing data redundancy. Moreover, since the input invoice application management device 20 can automatically record the status of each invoice and automatically establish and delete business invoice relationship data, it is not necessary for each business system to process through its own logic. By uniformly controlling the business invoice relationship of each input invoice, the accuracy of the use of input invoices can be improved.

[0044] Sales invoice application management method and sales invoice application management device embodiment: See also Figure 3 This embodiment provides a sales invoice application management device 50, which can communicate with multiple business systems and be called by multiple business systems, for example, it can be called by the income business system 41, the project accounting system 42, the marketing accounting system 43, etc. Each business system can call the sales invoice application management device 50 and perform invoice management work, such as inputting sales invoices to the sales invoice application management device 50, searching and querying sales invoices from the sales invoice application management device 50, or performing association operations on sales invoices, such as corresponding a certain sales invoice to a specific business. The sales invoice application management device 50 can respond to the operations issued by each business system and return the execution results to each business system, such as the successful entry of a certain sales invoice, or return the data of the sales invoice obtained by the search, etc.

[0045] The sales invoice application management device 50 has a sales invoice pool 60 for storing sales invoices of various business systems. Preferably, the sales invoice pool 60 can store multiple types of invoices, including value-added tax invoices, fiscal bills, other invoices, etc. In addition, the sales invoice pool 60 stores invoice structured data 61, invoice status data 62, business relationship data 63, account-invoice relationship data 64, invoice format data 65, etc. of each sales invoice. Since the sales invoices of various business systems are stored in the sales invoice pool 60, each business system does not need to store the sales invoices, thereby reducing the problem of data storage redundancy caused by each business system storing the sales invoices separately. When the user needs to query the sales invoice on the business system, the business system needs to call the sales invoice application management device 50 to search and query the sales invoice. After the sales invoice application management device 50 returns the data of the sales invoice to the business system, the user can browse the specific data of the sales invoice on the business system.

[0046] The sales invoice application management device 50 is also provided with a unified invoicing interface module 51, a taxation interface 52, and a unified query interface module 53. When a user needs to query a sales invoice through the front-end interface of a business system, a request message for querying the sales invoice can be sent to the sales invoice application management device 50. After receiving the request message for querying the sales invoice, the sales invoice application management device 50 returns a unified query interface to the business system. The user can search and query the sales invoice by inputting the information of the sales invoice to be searched in the unified query interface. After the sales invoice to be queried is obtained through the search, the sales invoice application management device 50 returns the data of the sales invoice obtained through the search to the business system, such as the payee and amount of the invoice.

[0047] The sales invoice application management device 50 can provide a unified invoicing service for each business system. For this purpose, a unified invoicing interface module 51 is set. The unified invoicing interface module 51 is connected to the tax authority through the tax interface 52 to facilitate the invoicing. In this embodiment, the unified invoicing interface module 51 can support the filling of invoicing information of multiple types of value-added tax invoices, including special value-added tax invoices, ordinary value-added tax invoices, special electronic value-added tax invoices, ordinary electronic value-added tax invoices, digital invoices (special value-added tax invoices), digital invoices (ordinary invoices), digital paper invoices (special value-added tax invoices), digital paper invoices (ordinary invoices), etc. In addition, for digital invoice types, it also supports the filling of invoicing information of multiple special invoices, including real estate rental service invoices, real estate sales service invoices, construction service invoices, cargo transportation service invoices, etc.

[0048] When a user needs to issue an invoice, he needs to fill in the invoice master table information and product information, wherein the invoice master table information filled in includes the seller's name, seller's taxpayer identification number, seller's address, seller's phone number, seller's bank account, seller's bank account number, buyer's name, buyer's taxpayer identification number, buyer's address, buyer's phone number, buyer's bank account, buyer's email address, remarks, invoice issuer information, etc. The invoice product information filled in includes item name, specification model, unit, quantity, unit price (tax included), amount (tax included), tax rate, tax amount, etc. Preferably, the unified invoicing interface module 51 can support single addition, batch import, deletion, discount line operation, etc. of product detail lines, that is, when obtaining product information, the unified invoicing interface module 51 can obtain the product detail information imported in batches from the business system, thereby providing great convenience for the user to issue invoices.

[0049] In addition, when each business system issues an invoice through the sales invoice application management device 50, the sales invoice application management device 50 will verify the invoice to be issued. Therefore, the sales invoice application management device 50 integrates the invoice compliance verification interface, the invoice issuance interface, and the invoice result query interface, and sets the invoice compliance verification rules for pre-configuration according to the business management requirements of different invoice types, such as the general invoice purchaser mandatory verification, the special invoice purchaser information mandatory verification, the remarks compliance verification, etc. Before submitting the invoice data to the tax authority for invoicing, the sales invoice application management device 50 can automatically perform compliance verification on the reported invoice data, and once any non-compliant points are found, timely feedback warning prompts are given to reduce the invoice failure rate. If the invoice data passes the verification, it is automatically uploaded to the tax authority through the tax interface 52 and the invoice operation is performed. In addition, the sales invoice application management device 50 can automatically call the invoice result query interface to obtain the issued sales invoice from the tax authority, and store the obtained sales invoice in the sales invoice pool 60.

[0050] In addition, the sales invoice application management device 50 will also manage the business invoice relationship of the sales invoice. When the business document or business system is in the stage of occupying a target sales invoice, the sales invoice application management device 50 will automatically write the business invoice relationship data 63 of the target sales invoice, for example, write it into the business invoice relationship data table in the sales invoice pool 60. When the business document or business system is in the stage of releasing the target sales invoice, the sales invoice application management device 50 will automatically search for the existing business invoice relationship data 63 in the sales invoice pool 60 for deletion. The operation of deleting the business invoice relationship data 63 is performed automatically, without the need for each business application to process, which can reduce the risk of missed processing and erroneous processing, and accurately control the correctness of the business invoice relationship data.

[0051] Combine the following Figure 4The specific process of the sales invoice application management method is introduced. First, execute step S21 to obtain the invoice request information issued by the business system. When the user needs to issue an invoice, the sales invoice application management device 50 can be called through each business system. The sales invoice application management device 50 provides a unified invoicing interface. The user can enter the information required for invoicing through the unified invoicing interface, such as the type of sales invoice to be issued, the invoice amount, the payee, and other information. Then, the sales invoice application management device 50 executes step S22 to obtain information such as the invoice type and invoice data from the business system.

[0052] Next, step S23 is executed, and the sales invoice application management device 50 performs a compliance check on the acquired invoice data. For example, the invoice data is checked for compliance based on the type of invoice to be issued. If the invoice to be issued is an ordinary invoice, it is necessary to determine whether the invoice data contains the purchaser's information, etc. If it is a special value-added tax invoice, it is necessary to determine whether the invoice information includes the purchaser's taxpayer number and other information.

[0053] If the invoice data to be issued does not pass the compliance check, step S24 is executed to return a prompt message to the business system. Preferably, the prompt message includes not only the information that the invoice data is non-compliant, but also the reason for the non-compliance, such as the lack of a certain information or which information is wrong, so that the user can verify and modify the invoicing data in time.

[0054] If the invoice data to be issued passes the compliance check, step S25 is executed, and the unified invoicing interface module 51 uploads the invoice data to be issued to the tax authority through the tax interface 52, and the tax authority issues the invoice. After the tax authority has completed issuing the invoice, step S26 is executed to obtain the invoice that has been issued from the tax authority, and the obtained sales invoice is stored in the sales invoice pool 60. In this way, each sales invoice stored in the sales invoice pool 60 is obtained from the tax authority, which can ensure the accuracy of the data of each sales invoice stored in the sales invoice pool 60.

[0055] In addition, if the user needs to establish business invoice relationship data for a certain target sales invoice, the user issues a request to establish business invoice relationship data for the target sales invoice on the business system. At this time, the sales invoice application management device 50 determines whether the current state of the target sales invoice is occupied. If the target sales invoice is not occupied, the sales invoice is recorded as occupied, and the target business associated with the target sales invoice is recorded. At this time, the target sales invoice forms a one-to-one correspondence with the target business. If the target sales invoice for which the user needs to establish business relationship data is occupied, a prompt message indicating that the target sales invoice is occupied is issued, and no new business relationship data is established. In this way, the same invoice can be prevented from being reused and reimbursed repeatedly.

[0056] If the sales invoice application management device 50 subsequently receives a request to delete the business relationship data for the target sales invoice, the business invoice relationship data corresponding to the target sales invoice is found from the business invoice relationship data table recorded in the sales invoice pool 60, and the business invoice relationship data is deleted, and at the same time, the state of the target sales invoice is recorded as unoccupied. In this way, the target sales invoice can be associated with other businesses again, that is, a business invoice relationship can be established with other businesses.

[0057] In this embodiment, before the user issues an invoice, the invoice data to be issued is first verified. Only after passing the verification is the invoice data uploaded to the tax authority for invoicing, which can avoid the probability of invoicing failure.

[0058] In addition, it should be noted that both the input invoice application management device and the output invoice application management device can be implemented on various electronic devices, which have a processor, a memory, and a computer program stored in the memory and executable on the processor, such as an information processing program for implementing the above-mentioned information processing method. When the processor executes the computer program, it implements the various steps of the above-mentioned invoice application management method.

[0059] For example, a computer program may be divided into one or more modules, one or more modules are stored in a memory and executed by a processor to complete each module of the present invention. One or more modules may be a series of computer program instruction segments capable of completing a specific function, and the instruction segments are used to describe the execution process of the computer program in a terminal device.

[0060] The processor referred to in the present invention may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the terminal device, and uses various interfaces and lines to connect various parts of the entire terminal device.

[0061] The memory can be used to store computer programs and / or modules. The processor realizes various functions of the terminal device by running or executing the computer programs and / or modules stored in the memory and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function, etc.; the data storage area can store data created according to the use of the mobile phone, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0062] Computer readable storage medium: If the computer programs stored in the input invoice application management device and the output invoice application management device are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing related hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement each step of the above-mentioned input invoice application management method or the output invoice application management method.

[0063] The computer program includes computer program code, which may be in source code form, object code form, executable file or some intermediate form, etc. Computer readable media may include: any entity or device capable of carrying computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0064] Finally, it should be emphasized that the above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various changes and modifications. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. Invoice application management methods, including: Obtain invoice operation request information issued by the business system; Features: Providing the business system with an invoice operation interface, obtaining operation information performed by the user on the invoice operation interface, and performing corresponding target operations according to the operation information; The target operation includes querying a target invoice from a preset invoice pool, uploading a target invoice to the invoice pool, or issuing a target invoice, wherein the invoice pool records invoice information of multiple invoices, and the invoice pool records the business invoice relationship between each occupied invoice and the associated business; Obtain a request for establishing business-invoice relationship data for a target invoice issued by the business system, search for the corresponding target invoice according to the business-invoice relationship data, record that the target invoice is in an occupied state, and record the target business that occupies the target invoice.

2. The invoice application management method according to claim 1, characterized in that: The method also includes: obtaining a request issued by the business system to delete the business invoice relationship data for the target invoice, obtaining the recorded business invoice relationship data for the target invoice, deleting the business invoice relationship data for the target invoice, and recording that the target invoice is in an unoccupied state.

3. The invoice application management method according to claim 1, characterized in that: A request for establishing business invoice relationship data for a target invoice issued by the business system is obtained. After searching for the corresponding target invoice according to the business invoice relationship data, before recording the target invoice as being in an occupied state, the following is further performed: Determine that the target invoice is in an unoccupied state.

4. The invoice application management method according to claim 3, characterized in that: A request for establishing business-invoice relationship data for the target invoice is obtained from the business system. After searching for the corresponding target invoice according to the business-invoice relationship data, if the target invoice is in an occupied state, a prompt message indicating that the invoice is occupied is returned to the business system.

5. The invoice application management method according to any one of claims 1 to 4, characterized in that: The invoice pool also records the structured data, business-invoice relationship data, account-invoice relationship data and invoice format data of each invoice.

6. The invoice application management method according to any one of claims 1 to 4, characterized in that: The invoice pool is an input invoice pool; Providing the business system with an invoice operation interface includes: providing the business system with an invoice search interface, obtaining the target invoice from the input invoice pool after obtaining the search conditions input by the user, and returning the data of the target invoice to the business system.

7. The invoice application management method according to claim 6, characterized in that: When returning the target invoice data to the business system, the target invoice data is returned in accordance with the format requirements of the business system.

8. The invoice application management method according to any one of claims 1 to 4, characterized in that: The invoice pool is an input invoice pool; When the target operation is to upload a target invoice to the invoice pool, the target invoice is verified, and after the target invoice passes the verification, the target invoice is recorded in the input invoice pool.

9. The invoice application management device is characterized by: The method comprises a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, each step of the invoice application management method as claimed in any one of claims 1 to 8 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, each step of the invoice application management method as described in any one of claims 1 to 8 is implemented.

Images