WO2019019701A1 - 一种空白发票的回收处理方法、存储介质和服务器 - Google Patents

一种空白发票的回收处理方法、存储介质和服务器 Download PDF

Info

Publication number
WO2019019701A1
WO2019019701A1 PCT/CN2018/082840 CN2018082840W WO2019019701A1 WO 2019019701 A1 WO2019019701 A1 WO 2019019701A1 CN 2018082840 W CN2018082840 W CN 2018082840W WO 2019019701 A1 WO2019019701 A1 WO 2019019701A1
Authority
WO
WIPO (PCT)
Prior art keywords
invoice
blank
tax control
target
target blank
Prior art date
Application number
PCT/CN2018/082840
Other languages
English (en)
French (fr)
Inventor
熊俊超
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019019701A1 publication Critical patent/WO2019019701A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G06Q40/123—Tax preparation or submission

Definitions

  • the present application relates to the field of financial technology, and in particular, to a method for recycling a blank invoice, a storage medium, and a server.
  • the flow of blank invoices is: purchase blank invoices from the tax bureau ⁇ tax filing tray ⁇ core board ⁇ billing terminal.
  • the blank invoice on the invoicing terminal needs to be recycled to the core board, for example, if the user of the invoicing terminal thinks that there is no need to use so many blank invoices for a while, the blank invoice needs to complete the recycling process from the invoicing terminal to the core board.
  • the enterprise's invoice management system needs to call the recycling interface of the dedicated tax control server (such as Baiwang's tax control server), which is provided by the browser plug-in. Javascript interface to achieve.
  • the invoice management system often calls the tax control recovery interface to cause the browser to respond slowly or even jam, which is easy when the browser is stuck, the user closes the browser, and the client computer loses power.
  • the invoice management system of the enterprise can not know the return result of the tax control recycling interface in time and accurately, so it is difficult to determine whether the result of recycling the blank invoice is successful or not, which leads to the inventory of the blank invoice stored in the invoice management system and the tax control system. Inconsistent issues.
  • the embodiment of the present application provides a blank invoice distribution processing method and a server, which are intended to solve the problem of inconsistency between the inventory of the blank invoice stored in the existing invoice management system and the tax control system.
  • a method for recycling blank invoices including:
  • abnormal recovery record refers to the last time the target tax invoice is invoked to invoke the tax control recovery interface provided by the tax control system without receiving a return Historical record of results
  • the invoice management table records invoice information of a blank invoice currently available on the core board, and the terminal invoice inventory table records the blank invoices available for each invoicing terminal on the invoice management system.
  • Invoice Information
  • invoice information of the target blank invoice is recorded in the invoice management table of the tax control system, and is recorded in the terminal invoice inventory table of the invoice management system, performing a preset inventory update operation;
  • the tax control recovery interface provided by the tax control system is invoked on the target blank invoice
  • the preset inventory update operation includes the following steps:
  • the target blank invoice is updated to a blank invoice inventory that is not distributed by the invoice management system.
  • a computer readable storage medium is stored, the computer readable storage medium storing computer readable instructions that, when executed by a processor, implement the steps of a method for recycling a blank invoice described above .
  • a server comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the computer readable instructions The steps of the blank invoice recycling process.
  • the query Before calling the tax control recycling interface to recover the target blank invoice, when the query knows that the target blank invoice has a recycling history, first query whether the invoice information of the target blank invoice is in the invoice management table and the terminal invoice inventory table, if , indicating that the target blank invoice has been recycled, but the information recorded in the terminal invoice inventory table is deviated, so the invoice information of the target blank invoice is deleted from the terminal invoice inventory table, and the target blank invoice is updated to the blank invoice.
  • the inventory information recorded in the terminal invoice inventory table, the blank invoice inventory and the inventory information recorded in the invoice management table are unified; if the target blank invoice does not have an abnormal recovery record, it is known that the invoice related information must be recorded.
  • the tax control recycling interface can be called for the target blank invoice recovery operation, and the invoice information of the target blank invoice is taken from the terminal invoice inventory after the return result of the tax control recycling interface is successful. Delete in the table, update the target blank invoice Blank invoice stock. It can be seen that regardless of whether the target blank invoice has an abnormal recovery record and whether the history call tax recovery interface is successful, this solution can ensure that the target blank invoice to be recycled is recycled, and the undistributed blank invoice inventory stored in the invoice management system is ensured. Consistent with the tax control system.
  • FIG. 1 is a flow chart of an embodiment of a method for recycling blank invoices according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a step 106 of a method for recycling a blank invoice in an application scenario according to an embodiment of the present application;
  • FIG. 3 is a schematic flowchart of determining whether to perform a recycling operation again by determining the cumulative number of times of recycling in a usage scenario in a blank invoice recovery method according to an embodiment of the present application;
  • FIG. 4 is a structural diagram of an embodiment of a blank invoice recycling processing device according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a server according to an embodiment of the present application.
  • an embodiment of a method for recycling a blank invoice in this embodiment includes:
  • the user may log in to the invoice management system first.
  • the user needs to verify the user's account number, password, and the like. If the verification is passed, the user is successfully logged into the invoice management system.
  • the invoice management system can query which billing terminals are under the management authority of the user, and the billing terminals are the above-mentioned target billing terminals. The invoice management system then queries which of the available blank invoices on the one or more of the target invoicing terminals, and determines the target blank invoice to be distributed currently.
  • the foregoing step 101 may include: querying and displaying an available blank invoice of the billing terminal under the current user's management authority; and then acquiring the blank invoice number segment to be recycled selected by the current user; and then belonging to the blank invoice A blank invoice within the range of the segment is determined as the target blank invoice to be reclaimed. That is, after the invoice management system queries the available blank invoices of the respective billing terminals under the current user authority, the available blank invoices can be displayed to the user through the display interface, and the user can select the blanks to be recycled on the display interface.
  • the invoice number segment of the invoice such as 1 ⁇ 100. After the user clicks the "Recycle" button, it indicates that the user has selected to complete, and these blank invoices of paragraphs 1 to 100 are determined as the above-mentioned target blank invoice.
  • the invoice management system may generate a corresponding recycling instruction, and the invoice management system performs subsequent steps on the target blank invoice according to the recycling instruction to complete the recycling operation.
  • the invoice management system may record the history of the blank invoice recovery, which may include the execution time of the blank invoice and the operation user. Returns information such as results.
  • the history record is the abnormal recovery record mentioned above.
  • the invoice management system may be pre-set with a recycling record table, which records a history record of each recycling operation of the target blank invoice, and each time a blank invoice performs a recycling operation, the invoice management system
  • the basic information and/or detailed information of this recycling operation can be recorded in this recycling record table, which includes the return result of this recycling operation.
  • the invoice management system only needs to query the recycling record table to know whether the target blank invoice has an abnormal recovery record without returning a result.
  • step 102 if it is found that there is an abnormal recovery record about the target blank invoice, it means that the target blank invoice has been executed at least once, and the result of the last recycling operation is unknown (because no tax control is received) The result returned by the interface), so step 103 can be performed to further confirm whether the previous recycling operation is successful; otherwise, if the abnormal recovery record about the target blank invoice is not found, only the following two cases may exist for the target blank invoice. : In the first case, the target blank invoice has been subjected to a recycle operation, but the result of the return is a recycle failure; in the second case, the target blank invoice has not been subjected to a recycle operation. It can be seen that, in either case, in order to recover the target blank invoice, the recycling operation needs to be performed on the target blank invoice, and step 105 is called to call the tax control recovery interface for the recovery operation.
  • the target blank invoice in the case that the abnormal recovery record about the target blank invoice is not queried, it is impossible to exist that "the target blank invoice has been subjected to the recycling operation and the return result is the recovery success". This is because if the target blank invoice has been successfully recycled, the target blank invoice will be deleted from the blank invoice available on the target invoicing terminal and added to the available blank invoice inventory on the core board. At 101 o'clock, the target blank invoice will not be determined.
  • step 103 Determine whether the invoice information of the target blank invoice is recorded in the invoice management table of the tax control system, and is recorded in the terminal invoice inventory table of the invoice management system, and if yes, execute step 106, and if not, Then perform step 104;
  • invoice management table records invoice information of a blank invoice currently available on the core board
  • terminal invoice inventory table records invoice information of available blank invoices of each invoicing terminal on the invoice management system.
  • the invoice information of the target blank invoice is recorded in the invoice management table, it indicates that the tax control system (the system of the dedicated tax control server) has determined that the target blank invoice is successfully recovered and is available as a core board.
  • Blank invoice which means that the target blank invoice has been recycled; and if the invoice information of the target blank invoice is recorded in the terminal invoice inventory table, it indicates that the invoice management system considers that the target blank invoice is still in the invoicing terminal, and the target is blank. The invoice was not recycled or was successfully recycled. However, for the same target blank invoice, it is impossible to be both on the core board and on the billing terminal, which indicates that there must be a table record that is biased.
  • the terminal invoice inventory table has a deviation from the record of the target blank invoice at this time, so it is necessary to perform step 106 to update the inventory information on the invoice management system in order to maintain the tax. Consistent on the control system.
  • step 104 may be performed for processing.
  • step 105 can be performed to call the tax control recycling interface again for the target blank invoice to complete the recycling of the target blank invoice.
  • the invoice management system may call the tax control recovery interface provided by the tax control system for the target blank invoice to perform the recycling operation.
  • the tax control recovery interface will feed back the information of the success or failure of the recovery (ie, return the result), and if the "recovery success" of the feedback of the tax control recovery interface is received,
  • the information can be determined that the target blank invoice has been recycled, so that step 106 is performed to perform a preset inventory update operation. If the “recovery failure” information fed back from the tax control collection interface is received, it can be determined that the target blank invoice recovery fails, that is, the return result of the tax control collection interface is unsuccessful.
  • the preset processing mode may be used for processing. For example, the related alarm information may be fed back to the designated administrator, or the recovery operation may be directly ended, or the above steps 102-105 may be performed again to retry the recovery.
  • Target blank invoices and more.
  • the return result of the tax control collection interface is not received, it may be determined that the history record of the target blank invoice is the abnormal recovery record.
  • the preset inventory update operation is performed, the purpose of which is to ensure that the blank invoice inventory on the invoice management system is consistent with that in the tax control system.
  • step 106 may specifically include the following steps:
  • the target blank invoice has been transferred from the target invoicing terminal to the core board, so it can be deleted from the terminal invoice inventory table.
  • the blank invoice inventory not distributed by the invoice management system refers to the inventory of the blank invoices available on the core board recorded on the invoice management system, and under normal circumstances, the recorded inventory and tax control
  • the inventory recorded in the invoice management table on the system is consistent. Therefore, after the target blank invoice is transferred to the core board, the invoice management table on the tax control system will naturally add the target blank invoice, so accordingly, the blank invoice inventory not distributed by the invoice management system needs to be added.
  • the target blank invoice is stated to maintain the consistency of the two forms on the inventory record.
  • the terminal invoice inventory table is used to record the inventory of blank invoices available on each invoicing terminal on the invoice management system
  • another "core board inventory table” is used to record the inventory of blank invoices available on the core board.
  • the invoice management system can also use the same form to simultaneously record the "inventory of blank invoices available on each invoicing terminal on the invoice management system" and "record on the invoice management system”.
  • the inventory of blank invoices available on the core board" is recorded as a blank invoice inventory table.
  • the terminal invoice inventory table is equivalent to a sub-form in the blank invoice inventory table, and when used, the content and information recorded in the terminal invoice inventory table can be directly inquired from the blank invoice inventory table.
  • the embodiment may further include:
  • step 105 adding the cumulative number of recovery of the target blank invoice by one;
  • step 302 determining whether the return result of the tax control recovery interface is successful, and if so, executing step 106, if not, executing step 303;
  • step 303 Determine whether the cumulative number of times the target blank invoice is accumulated exceeds a preset threshold, and if yes, end the recycling operation, and if no, return to step 102.
  • step 301 in the application scenario, for each same invoice, the tax collection recovery interface is invoked once, and the cumulative number of collections of the blank invoice is incremented by one, and the tax collection recovery that has been called for the blank invoice is counted by collecting the accumulated number of times. The number of times the interface. Therefore, if it is determined in step 302 that the return result of the tax control collection interface is unsuccessful, step 303 may be performed to determine whether the cumulative number of times the target blank invoice is accumulated exceeds a preset threshold, and if so, the blank invoice for the target is known. After the tax control recycling interface has been called for many times, the recycling cannot be successfully completed. It can be determined that the target blank invoice has an abnormal condition.
  • the recycling operation is ended, and the information about the unsuccessful recovery of the target blank invoice can be fed back to the designated administrator; If not, you can return to step 102 to re-inquire the target blank invoice again and call the tax control recovery interface to ensure the successful recovery of the target blank invoice, and keep the blank invoice of the invoice management system as much as possible. Inventory is consistent with the tax control system. In practical applications, in general, after the tax control recovery interface is called twice for the same blank invoice, the recovery success rate of the blank invoice can reach 99.99%, so the above steps 301 ⁇ 303 can basically ensure the target blank invoice to be recycled. Complete the recycling operation.
  • the embodiment may also add relevant identifiers during the execution process. Specifically, before the step 105, the preset flag information corresponding to the target blank invoice is modified to be abnormal in the invoice management system; if the return result of the tax control collection interface is successful, the preset is The flag information is modified to be normal; if the return result of the tax control collection interface is unsuccessful, the information about the unsuccessful recovery of the target blank invoice is fed back to the designated administrator.
  • the identification information of the target blank invoice is set to "abnormal", for example, set to 0, after the tax control recovery interface is invoked, if the tax control is performed.
  • the return result of the recycling interface is unsuccessful (as opposed to the successful recovery, that is, as long as the recovery is successful, the return result of this tax control recycling interface is considered unsuccessful), the target blank invoice always exists in the recycling operation. Abnormal status, so you can feedback relevant information to the designated administrator to remind the designated administrator to perform related maintenance.
  • the designated administrator can quickly locate the blank invoice location where the exception occurs by using the preset flag information of the blank invoice, thereby helping the designated administrator to check and handle the abnormal situation.
  • the preset flag information is modified to be normal, for example, set to "1"
  • the blank invoice that is normally recovered can be distinguished from the blank invoice that is recovered abnormally.
  • the solution may also insert the invoice related information of the target blank invoice during the recycling process and combine the preset flag information corresponding to the target blank invoice to determine whether the target blank invoice has a corresponding abnormal recovery record.
  • the invoice related information of the target blank invoice is retrieved into the invoice database of the invoice management system; if the return result of the tax control collection interface is unsuccessful, the The invoice related information of this recycling is deleted in the invoice database.
  • the above invoice related information refers to basic information and/or detailed information related to the target blank invoice.
  • the basic information may include the applicant of the invoice, the application department, the application date, the purchaser, the purchase date, the warehousing personnel, the warehousing time and the like;
  • the detailed information may include the invoice type of the invoice, the invoice denomination, the invoice score, the invoice code, and the like.
  • two different forms may be used in the invoice database to store the basic information and detailed information.
  • the step 102 includes: querying whether the invoice related information of the target blank invoice is collected last time in the invoice database, and the preset flag information corresponding to the target blank invoice is abnormal, and if yes, determining the query An abnormal recovery record for the target blank invoice exists on the invoice management system.
  • the scenarios identified for the anomaly recovery record can be discussed in two ways:
  • the invoice information for the target blank invoice can also be used for inventory reconciliation. If the return result of this tax control recycling interface is successful, it is not necessary to delete the invoice related information of this recycling, which will help the manager to query the invoice related information of each blank invoice that has been successfully recovered through these two forms, and It checks against the blank invoice inventory to verify that the data in the blank invoice inventory is accurate. If the return result of the tax control recovery interface is unsuccessful, the current recycling cannot be considered to be valid, and thus the invoice related information of the current recycling needs to be deleted from the invoice database.
  • the blank invoice inventory stored in the invoice management system and the tax control system may be periodically (e.g., executed once an hour).
  • the blank invoice inventory is synchronized, which is based on the blank invoice inventory in the tax control system.
  • the invoice management system can also find invoice data with deviations between the two blank invoices, and report the inconsistent invoice data to the designated administrator for subsequent maintenance and processing.
  • FIG. 4 is a structural diagram showing an embodiment of a blank invoice recycling processing apparatus in the embodiment of the present application.
  • a recycling processing device for a blank invoice includes:
  • the target invoice determining module 401 is configured to determine a target blank invoice to be recovered in the blank invoice available on the target invoicing terminal;
  • the recovery record query module 402 is configured to query whether there is an abnormal recovery record about the target blank invoice on the invoice management system, where the abnormal recovery record refers to the tax that is sent by the tax control system to the target blank invoice last time. Control the recycle interface without receiving a history of the returned results;
  • the invoice information determining module 403 is configured to: if the query result of the recycle record query module 402 is yes, determine whether the invoice information of the target blank invoice is recorded in the invoice management table of the tax control system, and record in the In the terminal invoice inventory table of the invoice management system, the invoice management table records invoice information of a blank invoice currently available on the core board, and the terminal invoice inventory table records the available invoices of each invoicing terminal on the invoice management system. Invoice information for blank invoices;
  • the first triggering module 404 is configured to trigger the inventory update module 407 if the result of the determination by the invoice information determining module 403 is YES;
  • the interface calling module 405 is configured to: if the query result of the recycle record query module 402 is negative, invoke the tax control recovery interface provided by the tax control system on the target blank invoice;
  • the second triggering module 406 is configured to trigger the inventory update module 407 if the return result of the current tax control recovery interface is successful;
  • the inventory update module 407 includes:
  • the information deleting unit 4071 is configured to delete the invoice information of the target blank invoice from the terminal invoice inventory table;
  • the invoice stock updating unit 4072 is configured to update the target blank invoice to the blank invoice inventory that is not distributed by the invoice management system.
  • the recycling processing device of the blank invoice may further include:
  • a first flag information modification module configured to: in the invoice management system, corresponding to the target blank invoice, before the interface invoking module invokes the tax control recovery interface provided by the tax control system on the target blank invoice
  • the preset flag information is modified to be abnormal
  • the second flag information modification module is configured to: if the return result of the tax control collection interface is successful, modify the preset flag information to be normal;
  • the information feedback module is configured to: if the return result of the tax control collection interface is unsuccessful, feed back information about the unsuccessful recovery of the target blank invoice to the designated administrator.
  • the recycling processing device of the blank invoice may further include:
  • a related information insertion module configured to insert the target blank invoice book into an invoice database of the invoice management system before the interface calling module invokes the tax control recovery interface provided by the tax control system on the target blank invoice Invoice related information for recycling;
  • the related information deleting module is configured to delete the invoice related information of the current recycling from the invoice database if the return result of the tax control recycling interface is unsuccessful;
  • the recovery record query module includes:
  • the related information querying unit is configured to query whether the invoice related information of the target blank invoice is reclaimed in the invoice database, and the preset flag information corresponding to the target blank invoice is abnormal;
  • a recovery record determining unit configured to: if the query result of the related information query unit is yes, determine that an abnormal recovery record regarding the target blank invoice exists on the invoice management system.
  • the target invoice determination module includes:
  • the invoice query display unit is configured to query and display the available blank invoices of the invoicing terminal under the current user's management authority;
  • a selected segment obtaining unit configured to obtain a blank invoice number segment to be recovered selected by the current user
  • the recycling invoice determining unit is configured to determine the blank invoice falling within the range of the blank invoice number segment as the target blank invoice to be recycled.
  • the recycling processing device of the blank invoice may further include:
  • a recycling accumulation module configured to increase the cumulative number of collections of the target blank invoice by one before the interface calling module invokes the tax control recovery interface provided by the tax control system on the target blank invoice;
  • the cumulative number judgment module is configured to determine whether the cumulative number of times of the target blank invoices exceeds a preset threshold if the return result of the tax control collection interface is unsuccessful;
  • the query triggering module is configured to trigger the recycle record query module if the judgment result of the cumulative count determination module is negative.
  • FIG. 5 is a schematic diagram of a server according to an embodiment of the present application.
  • the server 5 of this embodiment includes a processor 50, a memory 51, and computer readable instructions 52 stored in the memory 51 and executable on the processor 50, such as performing a blank invoice.
  • the procedure for recycling the processing method When the processor 50 executes the computer readable instructions 52, the steps in the embodiment of the method for recycling the blank invoices described above are implemented, such as steps 101 to 106 shown in FIG.
  • the processor 50 executes the computer readable instructions 52, the functions of the modules/units in the various apparatus embodiments described above are implemented, such as the functions of the modules 401 to 407 shown in FIG.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Processing Of Solid Wastes (AREA)

Abstract

本申请公开了一种空白发票的回收处理方法，用于解决无法获知税控回收接口的返回结果时，容易导致发票管理系统存储的空白发票的库存与税控系统中的不一致的问题。本申请提供的方法包括：在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票；查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录，若是，则判断是否所述目标空白发票的发票信息既记录在发票管理表中又记录在终端发票库存表中；若判断为是，则执行预设的库存更新操作；若否，则对所述目标空白发票调用所述税控系统提供的税控回收接口；若返回结果为成功，则更新发票管理系统的空白发票库存。本申请还提供了存储介质和服务器。

Description

一种空白发票的回收处理方法、存储介质和服务器
本申请申明享有2017年7月24日递交的申请号为201710605534.0、名称为“一种空白发票的回收处理方法、存储介质和服务器”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及金融技术领域，尤其涉及一种空白发票的回收处理方法、存储介质和服务器。
 背景技术
目前，空白发票的流转过程为：从税局购买空白发票→报税盘→核心板→开票终端。当在开票终端上的空白发票需要回收至核心板时，比如在开票终端的用户认为暂时不需要使用这么多空白发票的情况下，则空白发票需要完成从开票终端→核心板的回收过程。在这个回收过程中，企业的发票管理系统需要调用专用的税控服务器（例如百望的税控服务器）的回收接口（简称税控回收接口），该税控回收接口通过浏览器插件对外提供的Javascript接口来实现。
然而，在回收空白发票过程中，发票管理系统调用该税控回收接口时常常导致浏览器响应缓慢甚至卡死，当出现浏览器卡死、用户关闭浏览器、客户电脑断电等意外情况时容易导致企业本地的发票管理系统无法及时准确地获知税控回收接口的返回结果，从而难以确定回收空白发票的结果是成功还是失败，进而导致发票管理系统存储的空白发票的库存与税控系统中的不一致的问题。
 技术问题
本申请实施例提供了一种空白发票的分发处理方法和服务器，旨在解决现有的发票管理系统存储的空白发票的库存与税控系统中的不一致的问题。
 技术解决方案
第一方面，提供了一种空白发票的回收处理方法，包括：
在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票；
查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录，所述异常回收记录是指上一次对所述目标空白发票调用所述税控系统提供的税控回收接口而没有接收到返回结果的历史记录；
若查询到发票管理系统上存在关于所述目标空白发票的异常回收记录，则判断是否所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，所述发票管理表记录有核心板上当前可用的空白发票的发票信息，所述终端发票库存表记录有所述发票管理系统上各个开票终端的可用的空白发票的发票信息；
若所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，则执行预设的库存更新操作；
若查询到发票管理系统上不存在关于所述目标空白发票的异常回收记录，则对所述目标空白发票调用所述税控系统提供的税控回收接口；
若本次税控回收接口的返回结果为成功，则执行预设的库存更新操作；
所述预设的库存更新操作包括如下步骤：
将所述目标空白发票的发票信息从所述终端发票库存表中删除；
将所述目标空白发票更新至所述发票管理系统未分发的空白发票库存中。
第二方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，所述计算机可读指令被处理器执行时实现上述的空白发票的回收处理方法的步骤。
第三方面，提供了一种服务器，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时上述的空白发票的回收处理方法的步骤。
 有益效果
本申请在调用税控回收接口回收目标空白发票之前，在查询得知该目标空白发票存在回收历史时，先查询该目标空白发票的发票信息是否同时在发票管理表和终端发票库存表中，若是，则表示该目标空白发票已经回收完成，但终端发票库存表记录的信息存在偏差，因此将该目标空白发票的发票信息从所述终端发票库存表中删除，并将目标空白发票更新至空白发票库存中，以保持所述终端发票库存表记录的库存信息、空白发票库存与发票管理表中记录的库存信息三者统一；如果该目标空白发票不存在异常回收记录，可知其发票相关信息必然记录在终端发票库存表中，因此可以对该目标空白发票调用税控回收接口进行回收操作，并在本次税控回收接口的返回结果为成功之后将目标空白发票的发票信息从所述终端发票库存表中删除，将目标空白发票更新至空白发票库存中。可见，不论该目标空白发票是否存在异常回收记录，以及历史调用税控回收接口是否成功，本方案均能保证待回收的目标空白发票完成回收，且确保发票管理系统存储的未分发的空白发票库存与该税控系统中的一致。
 附图说明
图1为本申请实施例中一种空白发票的回收处理方法一个实施例流程图；
图2为本申请实施例中一种空白发票的回收处理方法步骤106在一个应用场景下的流程示意图；
图3为本申请实施例中一种空白发票的回收处理方法在一个应用场景下通过回收累计次数的判断来确定是否再次进行回收操作的流程示意图；
图4为本申请实施例中一种空白发票的回收处理装置一个实施例结构图；
图5为本申请一实施例提供的服务器的示意图。
 本发明的实施方式
请参阅图1，本实施例中一种空白发票的回收处理方法一个实施例包括：
101、在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票；
本实施例中，用户可以先登录该发票管理系统，登录时，需要验证用户的账号、密码等身份信息，若验证通过，则成功登录该发票管理系统。此时，发票管理系统可以查询该用户的管理权限下有哪些开票终端，这些开票终端即为上述的目标开票终端。然后发票管理系统查询一个或多个所述目标开票终端上有哪些可用的空白发票，并从中确定出当前待分发的目标空白发票。
具体地，上述步骤101可以包括：查询并展示当前用户的管理权限下开票终端的可用的空白发票；然后，获取所述当前用户选中的待回收的空白发票号段；再将属于所述空白发票号段范围内的空白发票确定为当前待回收的目标空白发票。也即，在发票管理系统查询到当前用户权限下的各个开票终端的可用空白发票之后，可以通过展示界面的形式将这些可用的空白发票展示给用户，用户可以在展示界面上选中需要回收的空白发票的发票号段，比如1~100号。在用户点击“回收”按钮之后，表示用户选择完成，将1~100号段的这些空白发票确定为上述的目标空白发票。
需要说明的是，在确定出目标空白发票之后，该发票管理系统可以生成相应的回收指令，进而该发票管理系统根据该回收指令对上述的目标空白发票执行后续步骤来完成回收操作。
102、查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录，若是，则执行步骤103，若否，则执行步骤105；其中，所述异常回收记录是指上一次对所述目标空白发票调用所述税控系统提供的税控回收接口而没有接收到返回结果的历史记录
本实施例中，每当某个空白发票执行一次回收操作时，发票管理系统可以记录下这个空白发票这次回收的历史记录，具体可以包括该空白发票该次回收操作的执行时间、操作用户、返回结果等信息。其中，若该空白发票的某条历史记录表明该空白发票在上一次调用税控回收接口时没有接收到该税控回收接口返回的结果时，则该条历史记录为上面所说的异常回收记录。
特别地，所述发票管理系统上可以预设有回收记录表，所述回收记录表记录有关于目标空白发票每次回收操作的历史记录，每当一个空白发票执行一次回收操作时，发票管理系统可以将这次回收操作的基本信息和/或详细信息记录到这个回收记录表中，这些信息中包括了这次回收操作的返回结果。在执行步骤102时，发票管理系统只需查询该回收记录表即可得知所述目标空白发票是否存在没有返回结果的异常回收记录。
对于上述步骤102，如果查询到存在关于所述目标空白发票的异常回收记录，则表示该目标空白发票已经执行过至少一次回收操作，且上一次回收操作的结果未知（因没有接收到税控回收接口返回的结果），因此可以执行步骤103进一步确认之前的回收操作是否成功；反之，如果查询不到关于所述目标空白发票的异常回收记录，则对于该目标空白发票只可能存在以下两种情况：第一种情况，该目标空白发票已执行过回收操作，但返回结果为回收失败；第二种情况，该目标空白发票未执行过回收操作。可见，不论是上述两种情况中的哪种情况，为了回收该目标空白发票，均需要对该目标空白发票执行回收操作，需要执行步骤105调用税控回收接口进行回收操作。
需要说明的是，在查询不到关于所述目标空白发票的异常回收记录情况下，是不可能存在“该目标空白发票已执行过回收操作且返回结果为回收成功”这种情况的。这是因为，若该目标空白发票之前已经回收成功，该目标空白发票将会从目标开票终端上可用的空白发票中删除，并添加至核心板上的可用空白发票库存中，这样，在执行步骤101时就不会确定到该目标空白发票了。
103、判断是否所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，若是，则执行步骤106，若否，则执行步骤104；
需要说明的是，所述发票管理表记录有核心板上当前可用的空白发票的发票信息，所述终端发票库存表记录有所述发票管理系统上各个开票终端的可用的空白发票的发票信息。
可以理解的是，如果目标空白发票的发票信息记录在发票管理表中，则表示税控系统（专用的税控服务器的系统）已经确定将该目标空白发票回收成功，并作为核心板上的可用空白发票，也即表示该目标空白发票已经回收完成了；而如果目标空白发票的发票信息记录在该终端发票库存表中，则表示发票管理系统认为该目标空白发票仍在开票终端那里，目标空白发票并未被回收或被回收成功。然而，对于同一个目标空白发票来说，其不可能既在于核心板上又在于开票终端上，这说明其中必然有一个表格的记录是存在偏差的。基于存疑时服从税控系统的原则，可以认为此时该终端发票库存表对于目标空白发票的记录存在偏差，因此需要执行步骤106，对发票管理系统上的库存信息进行更新，以求保持与税控系统上的一致。
而对于不满足步骤103的判定条件的情况，可以执行步骤104进行处理。
104、按照预设流程处理；
对于判断得知不满足“所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中”这个条件时，可以预先设置相应的流程进行处理。如可以反馈相关的告警信息给指定管理员，或可以直接结束本次分发操作。进一步地，还可以判断所述目标空白发票的发票信息是否记录在该发票管理表中，若是，则认为该目标空白发票的上一次回收操作的结果为失败，但由于未知原因（比如网络丢包）导致发票管理系统没有接收到税控回收接口返回的结果。这种情况下，可以执行步骤105，对该目标空白发票再一次调用税控回收接口，以完成该目标空白发票的回收。
105、对所述目标空白发票调用所述税控系统提供的税控回收接口；
发票管理系统为了完成对目标空白发票的回收，或者为了确保该目标空白发票回收成功，可以对该目标空白发票调用所述税控系统提供的税控回收接口，进行回收操作。
可以理解的是，在调用税控回收接口之后，一般情况下，该税控回收接口会反馈回收成功与否的信息（即返回结果），若接收到税控回收接口反馈的“回收成功”的信息，则可以确定该目标空白发票已完成回收，从而执行步骤106，执行预设的库存更新操作。若接收到税控回收接口反馈的“回收失败”的信息，则可以确定该目标空白发票回收失败，也即本次税控回收接口的返回结果为不成功。此时，可以采用预设的处理方式进行处理，比如，可以反馈相关的告警信息给指定管理员，或者可以直接结束本次回收操作，或者还可以再次执行上述步骤102~105，重新尝试回收该目标空白发票，等等。
需要说明的是，若没有接收到税控回收接口的返回结果，则可以确定该目标空白发票本次回收的历史记录为上述的异常回收记录。
106、执行预设的库存更新操作；
若本次税控回收接口的返回结果为成功，则执行预设的库存更新操作，其目的为确保发票管理系统上的空白发票库存与税控系统中的保持一致。
本实施例中，如图2所示，步骤106具体可以包括如下步骤：
201、将所述目标空白发票的发票信息从所述终端发票库存表中删除；
202、将所述目标空白发票更新至所述发票管理系统未分发的空白发票库存中。
对于上述步骤201，在得知该目标空白发票回收成功之后，该目标空白发票已从目标开票终端转移到核心板上，因此可将其从终端发票库存表中删除。
对于上述步骤202，可以理解的是，发票管理系统未分发的空白发票库存指的是发票管理系统上记录的核心板上可用的空白发票的库存，在正常情况下，其记录的库存与税控系统上发票管理表中记录的库存一致。因此，当目标空白发票转移到核心板上之后，税控系统上的该发票管理表自然会添加上该目标空白发票，因此相应地，该发票管理系统未分发的空白发票库存也需要添加上所述目标空白发票，从而维持两张表格在库存记录上的一致。
需要说明的是，本实施例中可以分别使用两张不同的表格来记录发票管理系统上各个开票终端上可用的空白发票的库存，以及发票管理系统上记录的核心板上可用的空白发票的库存，比如采用该终端发票库存表来记录发票管理系统上各个开票终端上可用的空白发票的库存，采用另一张“核心板库存表”来记录核心板上可用的空白发票的库存。在一个应用场景下，为了便于表格的管理，该发票管理系统也可以采用一张相同的表格来同时记录“发票管理系统上各个开票终端上可用的空白发票的库存”和“发票管理系统上记录的核心板上可用的空白发票的库存”，记为空白发票库存表。这样，上述的终端发票库存表相当于该空白发票库存表中的一个子表格，在使用时，可以直接从该空白发票库存表中查询到终端发票库存表中记录的内容和信息。
进一步地，在另一个应用场景下，如图3所示，本实施例还可以包括：
301、在步骤105之前，将所述目标空白发票的回收累计次数加1；
302、判断本次税控回收接口的返回结果是否为成功，若是，则执行步骤106，若否，则执行步骤303；
303、判断所述目标空白发票的回收累计次数是否超过预设的阈值，若是，则结束本次回收操作，若否，则返回执行步骤102。
关于步骤301，本应用场景下，针对同一空白发票，每调用一次税控回收接口，则将该空白发票的回收累计次数加1，通过回收累计次数统计针对该空白发票已调用过的税控回收接口的次数。从而，在步骤302判断得知本次税控回收接口的返回结果为不成功时，可以执行步骤303判断目标空白发票的回收累计次数是否超过预设的阈值，若是，则可知针对该目标空白发票已经多次调用税控回收接口后仍无法回收成功，可以认定该目标空白发票存在异常状况，因此结束本次回收操作，并可以反馈关于所述目标空白发票回收不成功的信息至指定管理员；若否，则可以返回执行步骤102，重新对该目标空白发票进行再一次的查询和税控回收接口的调用，以确保该目标空白发票的回收成功，并尽可能地保持发票管理系统的空白发票库存与税控系统中的一致。在实际应用中，一般来说，对同一空白发票调用两次税控回收接口之后，该空白发票的回收成功率可以达到99.99%，因而上述步骤301~303可以基本上确保待回收的目标空白发票完成回收操作。
进一步地，为了便于发票管理系统的管理员维护系统和检查相关异常错误，本实施例还可以在执行过程中加入相关标识。具体为：在步骤105之前，在所述发票管理系统中将所述目标空白发票对应的预设标志信息修改为异常；若本次税控回收接口的返回结果为成功，则将所述预设标志信息修改为正常；若本次税控回收接口的返回结果为不成功，则反馈关于所述目标空白发票回收不成功的信息至指定管理员。可以理解的是，通过对目标空白发票的标识信息进行设置，调用税控回收接口前，将标识信息置为“异常”，比如置为0，在调用税控回收接口以后，若本次税控回收接口的返回结果为不成功（与回收成功相反，即只要不能确定回收成功，就可以认为本次税控回收接口的返回结果为不成功），则该目标空白发票在回收操作上总是存在异常状况的，因此可以反馈相关信息给指定管理员，以提醒指定管理员进行相关维护。当指定管理员进行维护处理时，指定管理员可以通过空白发票的预设标志信息快速定位到发生异常的空白发票位置，从而有助于指定管理员对异常情况的检查和处理。而当本次税控回收接口的返回结果为成功时，则将该预设标志信息修改为正常，比如置为“1”，可以将正常回收的空白发票与回收异常的空白发票区分开来。
更进一步地，本方案还可以在回收处理过程中插入目标空白发票当次回收的发票相关信息并结合目标空白发票对应的预设标志信息，来确定该目标空白发票是否存在相应的异常回收记录。具体为，在步骤105之前，向所述发票管理系统的发票数据库中插入所述目标空白发票本次回收的发票相关信息；若本次税控回收接口的返回结果为不成功，则从所述发票数据库中删除所述本次回收的发票相关信息。
其中，上述的发票相关信息是指该目标空白发票相关的基础信息和/或详细信息。基础信息可以包括发票的申请人员、申请部门、申请日期、购买人员、购买日期、入库人员、入库时间等信息；详细信息可以包括发票的发票类型、发票面额、发票分数、发票代码等信息。特别地，该发票数据库中可以采用两张不同的表格分别存放所述基础信息和详细信息。
本实施例中，通过目标空白发票的发票信息和预设标志信息，可以确定得知该目标空白发票是否存在相应的异常回收记录。具体地，上述步骤102包括：查询所述发票数据库中是否存在所述目标空白发票上一次回收的发票相关信息，且所述目标空白发票对应的预设标志信息为异常，若是，则确定查询到发票管理系统上存在关于所述目标空白发票的异常回收记录。针对异常回收记录确定的情景，可以分下述两种情况进行讨论：
一、假设发票管理系统接收到了税控回收接口的返回结果，则不论该返回结果为成功或者不成功，本方案均会进行相应的处理（参考上述内容），该目标空白发票不存在异常回收记录；
二、假设发票管理系统没有接收到税控回收接口的返回结果，此时，既不属于上述的“本次税控回收接口的返回结果为成功”也不属于上述的“本次税控回收接口的返回结果为不成功”，因此，发票数据库中插入的所述目标空白发票本次回收的发票相关信息保留，且该目标空白发票的预设标志信息依然为异常。可见，这种情况下目标空白发票的本次回收的回收记录则会成为其异常回收记录，在下一次针对该目标空白发票执行本实施例提供的空白发票的回收处理方法时，步骤102的条件满足，进入步骤103。
另一方面，目标空白发票的发票信息还可以用于库存的核对。若本次税控回收接口的返回结果为成功，则无需删除本次回收的发票相关信息，这将有利于管理人员通过这两张表格查询各个已回收成功的空白发票的发票相关信息，并将其与空白发票库存进行核对，以核查空白发票库存中的数据是否准确无误。而若本次税控回收接口的返回结果为不成功，则不能认为本次回收是有效的，因而需要从所述发票数据库中删除所述本次回收的发票相关信息。
另外，本申请中，为了进一步确保发票管理系统存储的空白发票库存与该税控系统中的一致，还可以定期（如每小时执行一次）将发票管理系统存储的空白发票库存与税控系统中的空白发票库存进行同步，以税控系统中的空白发票库存为准。在同步更新过程中，发票管理系统还可以找出空白发票库存中两者存在偏差的发票数据，将这些存在偏差的发票数据报告给指定的管理员，以便于后续的维护和处理。
图4示出了本申请实施例中一种空白发票的回收处理装置一个实施例结构图。本实施例中，一种空白发票的回收处理装置包括：
目标发票确定模块401，用于在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票；
回收记录查询模块402，用于查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录，所述异常回收记录是指上一次对所述目标空白发票调用所述税控系统提供的税控回收接口而没有接收到返回结果的历史记录；
发票信息判断模块403，用于若所述回收记录查询模块402的查询结果为是，则判断是否所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，所述发票管理表记录有核心板上当前可用的空白发票的发票信息，所述终端发票库存表记录有所述发票管理系统上各个开票终端的可用的空白发票的发票信息；
第一触发模块404，用于若所述发票信息判断模块403的判断结果为是，则触发库存更新模块407；
接口调用模块405，用于若所述回收记录查询模块402的查询结果为否，则对所述目标空白发票调用所述税控系统提供的税控回收接口；
第二触发模块406，用于若本次税控回收接口的返回结果为成功，则触发所述库存更新模块407；
所述库存更新模块407包括：
信息删除单元4071，用于将所述目标空白发票的发票信息从所述终端发票库存表中删除；
发票库存更新单元4072，用于将所述目标空白发票更新至所述发票管理系统未分发的空白发票库存中。
进一步地，所述空白发票的回收处理装置还可以包括：
第一标志信息修改模块，用于在所述接口调用模块对所述目标空白发票调用所述税控系统提供的税控回收接口之前，在所述发票管理系统中将所述目标空白发票对应的预设标志信息修改为异常；
第二标志信息修改模块，用于若本次税控回收接口的返回结果为成功，则将所述预设标志信息修改为正常；
信息反馈模块，用于若本次税控回收接口的返回结果为不成功，则反馈关于所述目标空白发票回收不成功的信息至指定管理员。
进一步地，所述空白发票的回收处理装置还可以包括：
相关信息插入模块，用于在所述接口调用模块对所述目标空白发票调用所述税控系统提供的税控回收接口之前，向所述发票管理系统的发票数据库中插入所述目标空白发票本次回收的发票相关信息；
相关信息删除模块，用于若本次税控回收接口的返回结果为不成功，则从所述发票数据库中删除所述本次回收的发票相关信息；
所述回收记录查询模块包括：
相关信息查询单元，用于查询所述发票数据库中是否存在所述目标空白发票上一次回收的发票相关信息，且所述目标空白发票对应的预设标志信息为异常；
回收记录确定单元，用于若所述相关信息查询单元的查询结果为是，则确定查询到发票管理系统上存在关于所述目标空白发票的异常回收记录。
进一步地，所述目标发票确定模块包括：
发票查询展示单元，用于查询并展示当前用户的管理权限下开票终端的可用的空白发票；
选中号段获取单元，用于获取所述当前用户选中的待回收的空白发票号段；
回收发票确定单元，用于将属于所述空白发票号段范围内的空白发票确定为当前待回收的目标空白发票。
进一步地，所述空白发票的回收处理装置还可以包括：
回收累计模块，用于在所述接口调用模块对所述目标空白发票调用所述税控系统提供的税控回收接口之前，将所述目标空白发票的回收累计次数加1；
累计次数判断模块，用于若本次税控回收接口的返回结果为不成功，则判断所述目标空白发票的回收累计次数是否超过预设的阈值；
查询触发模块，用于若所述累计次数判断模块的判断结果为否，则触发所述回收记录查询模块。
图5是本申请一实施例提供的服务器的示意图。如图5所示，该实施例的服务器5包括：处理器50、存储器51以及存储在所述存储器51中并可在所述处理器50上运行的计算机可读指令52，例如执行空白发票的回收处理方法的程序。所述处理器50执行所述计算机可读指令52时实现上述各个空白发票的回收处理方法实施例中的步骤，例如图1所示的步骤101至106。或者，所述处理器50执行所述计算机可读指令52时实现上述各装置实施例中各模块/单元的功能，例如图4所示模块401至407的功能。
以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (20)

  1. 一种空白发票的回收处理方法，其特征在于，包括：
    在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票；
    查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录，所述异常回收记录是指上一次对所述目标空白发票调用所述税控系统提供的税控回收接口而没有接收到返回结果的历史记录；
    若查询到发票管理系统上存在关于所述目标空白发票的异常回收记录，则判断是否所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，所述发票管理表记录有核心板上当前可用的空白发票的发票信息，所述终端发票库存表记录有所述发票管理系统上各个开票终端的可用的空白发票的发票信息；
    若所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，则执行预设的库存更新操作；
    若查询到发票管理系统上不存在关于所述目标空白发票的异常回收记录，则对所述目标空白发票调用所述税控系统提供的税控回收接口；
    若本次税控回收接口的返回结果为成功，则执行预设的库存更新操作；
    所述预设的库存更新操作包括如下步骤：
    将所述目标空白发票的发票信息从所述终端发票库存表中删除；
    将所述目标空白发票更新至所述发票管理系统未分发的空白发票库存中。
  2. 根据权利要求1所述的空白发票的回收处理方法，其特征在于，所述空白发票的回收处理方法还包括：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，在所述发票管理系统中将所述目标空白发票对应的预设标志信息修改为异常；
    若本次税控回收接口的返回结果为成功，则将所述预设标志信息修改为正常；
    若本次税控回收接口的返回结果为不成功，则反馈关于所述目标空白发票回收不成功的信息至指定管理员。
  3. 根据权利要求2所述的空白发票的回收处理方法，其特征在于，所述空白发票的回收处理方法还包括：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，向所述发票管理系统的发票数据库中插入所述目标空白发票本次回收的发票相关信息；
    若本次税控回收接口的返回结果为不成功，则从所述发票数据库中删除所述本次回收的发票相关信息；
    所述查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录包括：
    查询所述发票数据库中是否存在所述目标空白发票上一次回收的发票相关信息，且所述目标空白发票对应的预设标志信息为异常，若是，则确定查询到发票管理系统上存在关于所述目标空白发票的异常回收记录。
  4. 根据权利要求1所述的空白发票的回收处理方法，其特征在于，所述在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票包括：
    查询并展示当前用户的管理权限下开票终端的可用的空白发票；
    获取所述当前用户选中的待回收的空白发票号段；
    将属于所述空白发票号段范围内的空白发票确定为当前待回收的目标空白发票。
  5. 根据权利要求1至4中任一项所述的空白发票的回收处理方法，其特征在于，还包括：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，将所述目标空白发票的回收累计次数加1；
    若本次税控回收接口的返回结果为不成功，则判断所述目标空白发票的回收累计次数是否超过预设的阈值；
    若所述目标空白发票的回收累计次数不超过预设的阈值，则返回执行所述查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录的步骤。
  6. 一种空白发票的回收处理装置，包括：
    目标发票确定模块，用于在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票；
    回收记录查询模块，用于查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录，所述异常回收记录是指上一次对所述目标空白发票调用所述税控系统提供的税控回收接口而没有接收到返回结果的历史记录；
    发票信息判断模块，用于若所述回收记录查询模块的查询结果为是，则判断是否所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，所述发票管理表记录有核心板上当前可用的空白发票的发票信息，所述终端发票库存表记录有所述发票管理系统上各个开票终端的可用的空白发票的发票信息；
    第一触发模块，用于若所述发票信息判断模块的判断结果为是，则触发库存更新模块；
    接口调用模块，用于若所述回收记录查询模块的查询结果为否，则对所述目标空白发票调用所述税控系统提供的税控回收接口；
    第二触发模块，用于若本次税控回收接口的返回结果为成功，则触发所述库存更新模块；
    所述库存更新模块包括：
    信息删除单元，用于将所述目标空白发票的发票信息从所述终端发票库存表中删除；
    发票库存更新单元，用于将所述目标空白发票更新至所述发票管理系统未分发的空白发票库存中。
  7. 根据权利要求6所述的空白发票的分发处理装置，其特征在于，所述空白发票的回收处理装置还可以包括：
    第一标志信息修改模块，用于在所述接口调用模块对所述目标空白发票调用所述税控系统提供的税控回收接口之前，在所述发票管理系统中将所述目标空白发票对应的预设标志信息修改为异常；
    第二标志信息修改模块，用于若本次税控回收接口的返回结果为成功，则将所述预设标志信息修改为正常；
    信息反馈模块，用于若本次税控回收接口的返回结果为不成功，则反馈关于所述目标空白发票回收不成功的信息至指定管理员。
  8. 根据权利要求7所述的空白发票的分发处理装置，其特征在于，所述空白发票的回收处理装置还可以包括：
    相关信息插入模块，用于在所述接口调用模块对所述目标空白发票调用所述税控系统提供的税控回收接口之前，向所述发票管理系统的发票数据库中插入所述目标空白发票本次回收的发票相关信息；
    相关信息删除模块，用于若本次税控回收接口的返回结果为不成功，则从所述发票数据库中删除所述本次回收的发票相关信息；
    所述回收记录查询模块包括：
    相关信息查询单元，用于查询所述发票数据库中是否存在所述目标空白发票上一次回收的发票相关信息，且所述目标空白发票对应的预设标志信息为异常；
    回收记录确定单元，用于若所述相关信息查询单元的查询结果为是，则确定查询到发票管理系统上存在关于所述目标空白发票的异常回收记录。
  9. 根据权利要求6所述的空白发票的分发处理装置，其特征在于，所述目标发票确定模块包括：
    发票查询展示单元，用于查询并展示当前用户的管理权限下开票终端的可用的空白发票；
    选中号段获取单元，用于获取所述当前用户选中的待回收的空白发票号段；
    回收发票确定单元，用于将属于所述空白发票号段范围内的空白发票确定为当前待回收的目标空白发票。
  10. 根据权利要求6至9任一项所述的空白发票的分发处理装置，其特征在于，所述空白发票的回收处理装置还可以包括：
    回收累计模块，用于在所述接口调用模块对所述目标空白发票调用所述税控系统提供的税控回收接口之前，将所述目标空白发票的回收累计次数加1；
    累计次数判断模块，用于若本次税控回收接口的返回结果为不成功，则判断所述目标空白发票的回收累计次数是否超过预设的阈值；
    查询触发模块，用于若所述累计次数判断模块的判断结果为否，则触发所述回收记录查询模块。
  11. 一种服务器，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票；
    查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录，所述异常回收记录是指上一次对所述目标空白发票调用所述税控系统提供的税控回收接口而没有接收到返回结果的历史记录；
    若查询到发票管理系统上存在关于所述目标空白发票的异常回收记录，则判断是否所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，所述发票管理表记录有核心板上当前可用的空白发票的发票信息，所述终端发票库存表记录有所述发票管理系统上各个开票终端的可用的空白发票的发票信息；
    若所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，则执行预设的库存更新操作；
    若查询到发票管理系统上不存在关于所述目标空白发票的异常回收记录，则对所述目标空白发票调用所述税控系统提供的税控回收接口；
    若本次税控回收接口的返回结果为成功，则执行预设的库存更新操作；
    所述预设的库存更新操作包括如下步骤：
    将所述目标空白发票的发票信息从所述终端发票库存表中删除；
    将所述目标空白发票更新至所述发票管理系统未分发的空白发票库存中。
  12. 根据权利要求11所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还包括：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，在所述发票管理系统中将所述目标空白发票对应的预设标志信息修改为异常；
    若本次税控回收接口的返回结果为成功，则将所述预设标志信息修改为正常；
    若本次税控回收接口的返回结果为不成功，则反馈关于所述目标空白发票回收不成功的信息至指定管理员。
  13. 根据权利要求12所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还包括：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，向所述发票管理系统的发票数据库中插入所述目标空白发票本次回收的发票相关信息；
    若本次税控回收接口的返回结果为不成功，则从所述发票数据库中删除所述本次回收的发票相关信息；
    所述查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录包括：
    查询所述发票数据库中是否存在所述目标空白发票上一次回收的发票相关信息，且所述目标空白发票对应的预设标志信息为异常，若是，则确定查询到发票管理系统上存在关于所述目标空白发票的异常回收记录。
  14. 根据权利要求11所述的服务器，其特征在于，所述在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票包括：
    查询并展示当前用户的管理权限下开票终端的可用的空白发票；
    获取所述当前用户选中的待回收的空白发票号段；
    将属于所述空白发票号段范围内的空白发票确定为当前待回收的目标空白发票。
  15. 根据权利要求11至14任一项所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还包括：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，将所述目标空白发票的回收累计次数加1；
    若本次税控回收接口的返回结果为不成功，则判断所述目标空白发票的回收累计次数是否超过预设的阈值；
    若所述目标空白发票的回收累计次数不超过预设的阈值，则返回执行所述查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录的步骤。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其特征在于，所述计算机可读指令被处理器执行时实现如下步骤：
    在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票；
    查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录，所述异常回收记录是指上一次对所述目标空白发票调用所述税控系统提供的税控回收接口而没有接收到返回结果的历史记录；
    若查询到发票管理系统上存在关于所述目标空白发票的异常回收记录，则判断是否所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，所述发票管理表记录有核心板上当前可用的空白发票的发票信息，所述终端发票库存表记录有所述发票管理系统上各个开票终端的可用的空白发票的发票信息；
    若所述目标空白发票的发票信息记录在所述税控系统的发票管理表中，且记录在所述发票管理系统的终端发票库存表中，则执行预设的库存更新操作；
    若查询到发票管理系统上不存在关于所述目标空白发票的异常回收记录，则对所述目标空白发票调用所述税控系统提供的税控回收接口；
    若本次税控回收接口的返回结果为成功，则执行预设的库存更新操作；
    所述预设的库存更新操作包括如下步骤：
    将所述目标空白发票的发票信息从所述终端发票库存表中删除；
    将所述目标空白发票更新至所述发票管理系统未分发的空白发票库存中。
  17. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述计算机可读指令被处理器执行时还实现如下步骤：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，在所述发票管理系统中将所述目标空白发票对应的预设标志信息修改为异常；
    若本次税控回收接口的返回结果为成功，则将所述预设标志信息修改为正常；
    若本次税控回收接口的返回结果为不成功，则反馈关于所述目标空白发票回收不成功的信息至指定管理员。
  18. 根据权利要求17所述的计算机可读存储介质，其特征在于，所述计算机可读指令被处理器执行时还实现如下步骤：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，向所述发票管理系统的发票数据库中插入所述目标空白发票本次回收的发票相关信息；
    若本次税控回收接口的返回结果为不成功，则从所述发票数据库中删除所述本次回收的发票相关信息；
    所述查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录包括：
    查询所述发票数据库中是否存在所述目标空白发票上一次回收的发票相关信息，且所述目标空白发票对应的预设标志信息为异常，若是，则确定查询到发票管理系统上存在关于所述目标空白发票的异常回收记录。
  19. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述在目标开票终端上可用的空白发票中确定当前待回收的目标空白发票包括：
    查询并展示当前用户的管理权限下开票终端的可用的空白发票；
    获取所述当前用户选中的待回收的空白发票号段；
    将属于所述空白发票号段范围内的空白发票确定为当前待回收的目标空白发票。
  20. 根据权利要求16至19任一项所述的计算机可读存储介质，其特征在于，所述计算机可读指令被处理器执行时还实现如下步骤：
    在对所述目标空白发票调用所述税控系统提供的税控回收接口之前，将所述目标空白发票的回收累计次数加1；
    若本次税控回收接口的返回结果为不成功，则判断所述目标空白发票的回收累计次数是否超过预设的阈值；
    若所述目标空白发票的回收累计次数不超过预设的阈值，则返回执行所述查询发票管理系统上是否存在关于所述目标空白发票的异常回收记录的步骤。
PCT/CN2018/082840 2017-07-24 2018-04-12 一种空白发票的回收处理方法、存储介质和服务器 WO2019019701A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710605534.0A CN107798570A (zh) 2017-07-24 2017-07-24 一种空白发票的回收处理方法、存储介质和服务器
CN201710605534.0 2017-07-24

Publications (1)

Publication Number Publication Date
WO2019019701A1 true WO2019019701A1 (zh) 2019-01-31

Family

ID=61530326

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082840 WO2019019701A1 (zh) 2017-07-24 2018-04-12 一种空白发票的回收处理方法、存储介质和服务器

Country Status (2)

Country Link
CN (1) CN107798570A (zh)
WO (1) WO2019019701A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107798570A (zh) * 2017-07-24 2018-03-13 平安科技（深圳）有限公司 一种空白发票的回收处理方法、存储介质和服务器
CN114118881B (zh) * 2022-01-26 2022-05-06 中国民航信息网络股份有限公司 处理民航空白票证的方法、装置、存储介质和设备
CN115471959B (zh) * 2022-09-19 2024-05-14 中国建设银行股份有限公司 信息管理方法与装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101118632A (zh) * 2007-09-13 2008-02-06 中商流通生产力促进中心有限公司 一种网络税控器断网的数据处理方法
US20150142648A1 (en) * 2012-04-26 2015-05-21 Chengdu Santai Electronic Industry Co., Ltd. Corporate Bill Self-service System with Blank Bill Vending and Temporary Bill Storage Functions
US20170076342A1 (en) * 2015-09-15 2017-03-16 Sap Se Duplicate check based on generated hash value
CN106530024A (zh) * 2016-11-09 2017-03-22 百望金赋科技有限公司 一种开票方法、开票系统及其税控服务器
CN106779988A (zh) * 2016-11-15 2017-05-31 百望金赋科技有限公司 一种税控服务器管理系统及方法
CN107798570A (zh) * 2017-07-24 2018-03-13 平安科技（深圳）有限公司 一种空白发票的回收处理方法、存储介质和服务器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103793990B (zh) * 2012-11-02 2016-06-29 航天信息股份有限公司 发票的验证方法和系统
CN104992505B (zh) * 2015-05-26 2017-05-10 成都金税电子技术有限公司 基于监控pos机打印端口采集商超销售数据的方法
CN106920135A (zh) * 2015-12-28 2017-07-04 航天信息股份有限公司 一种pos开票服务器离线交易的实现方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101118632A (zh) * 2007-09-13 2008-02-06 中商流通生产力促进中心有限公司 一种网络税控器断网的数据处理方法
US20150142648A1 (en) * 2012-04-26 2015-05-21 Chengdu Santai Electronic Industry Co., Ltd. Corporate Bill Self-service System with Blank Bill Vending and Temporary Bill Storage Functions
US20170076342A1 (en) * 2015-09-15 2017-03-16 Sap Se Duplicate check based on generated hash value
CN106530024A (zh) * 2016-11-09 2017-03-22 百望金赋科技有限公司 一种开票方法、开票系统及其税控服务器
CN106779988A (zh) * 2016-11-15 2017-05-31 百望金赋科技有限公司 一种税控服务器管理系统及方法
CN107798570A (zh) * 2017-07-24 2018-03-13 平安科技（深圳）有限公司 一种空白发票的回收处理方法、存储介质和服务器

Also Published As

Publication number Publication date
CN107798570A (zh) 2018-03-13

Similar Documents

Publication Publication Date Title
US8688634B2 (en) Asynchronous peer-to-peer data replication
AU2016352206B2 (en) Data processing method and device
KR102072726B1 (ko) 데이터베이스로의 미들-티어 트랜잭션 로그들의 인라인 위임을 지원하는 시스템들 및 방법들
CN109542980B (zh) 一种区块链的数据处理方法、装置、设备及介质
US20060200829A1 (en) Duplicate message elimination during recovery when multiple threads are delivering messages from a message store to a destination queue
CN108647357B (zh) 数据查询的方法及装置
WO2019019701A1 (zh) 一种空白发票的回收处理方法、存储介质和服务器
US11704302B2 (en) Method, system and apparatus for processing database updates
CN107766080B (zh) 事务消息处理方法、装置、设备及系统
CN109240854B (zh) 对误操作引起的更改进行数据恢复的方法及系统
CN106575251B (zh) 流数据的推测数据处理
TW200821863A (en) Work item event procession
WO2019136812A1 (zh) 电子装置、数据调用日志生成及查询方法及存储介质
US10585877B1 (en) System and method for achieving high quality data integrity
US20100146334A1 (en) Fault tolerant update propagation to views
US11816163B2 (en) Systems and methods for improved transactional mainframes
US11169984B2 (en) Data management system
CN112988812A (zh) 库存数据的处理方法、装置、设备及存储介质
WO2019019631A1 (zh) 空白发票的作废处理方法、可读存储介质、服务器及装置
CN111158960A (zh) 一种基于内存的分布式异常数据处理方法和设备
WO2019019712A1 (zh) 一种空白发票的分发处理方法、存储介质和服务器
CN112783972A (zh) 图像特征值数据的同步方法及系统
CN114371870A (zh) 代码扫描、提交方法及代码扫描服务器、客户端和服务端
JP2017167842A (ja) トランザクション制御システムおよびトランザクション制御方法
JP2009295050A (ja) 成果物管理サーバ、成果物管理方法及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18838222

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18838222

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FOR 1205A DATED 04.08.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18838222

Country of ref document: EP

Kind code of ref document: A1