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

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

Info

Publication number
WO2019019712A1
WO2019019712A1 PCT/CN2018/083553 CN2018083553W WO2019019712A1 WO 2019019712 A1 WO2019019712 A1 WO 2019019712A1 CN 2018083553 W CN2018083553 W CN 2018083553W WO 2019019712 A1 WO2019019712 A1 WO 2019019712A1
Authority
WO
WIPO (PCT)
Prior art keywords
invoice
tax control
distribution
target blank
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/083553
Other languages
English (en)
French (fr)
Inventor
熊俊超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
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 Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2019019712A1 publication Critical patent/WO2019019712A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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

Definitions

  • the present application relates to the field of financial technology, and in particular, to a method for distributing 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 process of distributing blank invoices mainly refers to the process of distributing blank invoices from the core board to the billing terminal.
  • the enterprise's invoice management system needs to call the distribution interface (referred to as the tax control distribution interface) of the dedicated tax control server (for example, the tax control server), which is provided externally through the browser plug-in. Javascript interface to achieve.
  • the invoice management system often calls the tax control distribution 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 is unable to know the return result of the tax control distribution interface in time and accurately, so that it is difficult to determine whether the result of distributing 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 distributing a blank invoice including:
  • invoice management table records invoice information of a blank invoice currently available on the core board
  • the distribution information sheet records the invoice information of the blank invoice that has been distributed
  • the target blank invoice is deleted from the blank invoice inventory
  • the preset invoice distribution operation includes the following steps:
  • the target blank invoice is deleted from the blank invoice inventory.
  • 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 blank processing method of a blank invoice .
  • 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 distribution processing method for the blank invoice.
  • the present application determines whether the target blank invoice is distributed by querying the invoice management table and the distribution information table of the tax control system before invoking the tax control distribution interface to distribute the target blank invoice. If the target blank invoice is in the invoice management table, it indicates that it has not completed the distribution, thus calling the tax control distribution interface; if the target blank invoice is not in the invoice management table and in the distribution information table, it indicates that it has completed the distribution and Blank invoice inventory is deleted; if the target blank invoice is not in the invoice management table and is not in the distribution information table, although it is not possible to determine whether the target blank invoice is distributed, but the scheme directly calls the tax control distribution interface again, the target blank invoice can be ensured. The distribution is completed and the returned result is deleted from the blank invoice inventory after success. It can be seen that regardless of whether the tax distribution interface returns a specific distribution result, the solution can ensure the distribution of the target blank invoice to be distributed, and ensure that the undistributed blank invoice inventory stored by the invoice management system is consistent with that in the tax control system.
  • FIG. 1 is a flow chart of an embodiment of a blank invoice distribution processing method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of step 105 of a blank invoice distribution processing method in an application scenario according to an embodiment of the present application;
  • FIG. 3 is a schematic flowchart of step 105 of a blank invoice distribution processing method in another application scenario according to an embodiment of the present application;
  • FIG. 4 is a structural diagram of an embodiment of a blank invoice distribution processing apparatus 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 blank invoice distribution processing method 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 blank invoices are available in the undistributed blank invoice inventory, and determine the target blank invoice to be distributed currently.
  • the above step 101 may include: querying and displaying a blank invoice in the blank invoice inventory not distributed by the invoice management system, and then determining the blank invoice selected by the current user as the target blank invoice to be distributed. That is, after the invoice management system queries the blank invoice in the blank invoice inventory, the available blank invoices can be displayed to the user through the display interface, and the user can select the blank invoices to be distributed and the number of invoices on the display interface. After the user clicks the "Distribute" button, it indicates that the user selects the completion, and the blank invoice selected by the user is determined as the above-mentioned target blank invoice.
  • the user may also input to which billing terminal the blank invoices are to be distributed, and after the user inputs the billing terminal and clicks the "OK" button, the invoice management system may obtain the target blank invoice.
  • the billing terminal to be distributed to, and a corresponding distribution instruction may be generated, and the invoice management system performs subsequent steps on the target blank invoice according to the distribution instruction to complete the distribution operation.
  • step 102 Query whether the invoice information of the target blank invoice is recorded in the invoice management table of the tax control system. If yes, execute step 105. If no, execute step 103, where the invoice management table records that the core board is currently available. Invoice information for blank invoices;
  • the tax control system (the system of the dedicated tax control server) stores two forms, which are the invoice management table and the distribution information table.
  • the invoice management table is used to record the invoice information of the blank invoice currently available on the core board
  • the distribution information table is used to record the invoice information of the blank invoice that has been distributed. It can be understood that when the invoice information of a blank invoice is recorded in the invoice management table, it indicates that the blank invoice is not distributed; when the invoice information of a blank invoice is recorded in the distribution information table, it indicates This blank invoice has been distributed.
  • step 105 is executed to invoke the tax control distribution interface to perform the target blank invoice.
  • step 105 is executed to invoke the tax control distribution interface to perform the target blank invoice.
  • Distribute if not, it means that the target blank invoice may have been distributed, but it is not sure whether the distribution has been successful, so step 103 needs to be performed for further confirmation.
  • the distribution information table of the tax control system can be queried, and if the invoice information of the target blank invoice is recorded on the distribution information table, the target blank invoice is indicated. Has been successfully distributed.
  • the target blank invoice is a blank invoice inventory that is not distributed in the invoice management system
  • the record in the blank invoice inventory is inconsistent with the record information on the tax control system, in order to maintain inventory information between the invoice management system and the tax control system.
  • the consistency of the record, and based on the record information of the tax control system, should be performed in step 104 to delete the target blank invoice from the blank invoice inventory.
  • the invoice management system may perform step 105 to perform the target blank invoice. Once again, distribute the operation to ensure its distribution is successful.
  • the invoice information of the target blank invoice in the blank invoice inventory may be deleted from the inventory, or may be marked as “distributed” in the invoice information of the target blank invoice, and accordingly, These invoices are automatically filtered when the invoice management system queries these blank invoices marked as "distributed”, which is equivalent to removing the target blank invoice from the blank invoice inventory.
  • step 105 may specifically include the following steps:
  • the target blank invoice is deleted from the blank invoice inventory.
  • step 201 in order to complete the distribution of the target blank invoice, or to ensure the successful distribution of the target blank invoice, the tax control distribution interface provided by the tax control system may be invoked on the target blank invoice to perform the distribution operation.
  • the step 201 is specifically: invoking the tax control distribution interface provided by the tax control system to distribute the target blank invoice to the billing terminal. .
  • the tax distribution interface After the tax distribution interface is invoked, the tax distribution interface generally reports the success or failure of the distribution. If the “distribution success” information fed back by the tax distribution interface is received, it can be determined. The target blank invoice has been distributed, thereby performing the above step 202, deleting the target blank invoice from the blank invoice inventory. If the information of the tax control distribution interface is not received, the result of the tax control distribution interface is unsuccessful. In this case, the preset processing mode can be used for processing. For example, feedback can be performed. Relevant alarm information is sent to the designated administrator, or the distribution operation can be directly ended, or the above steps 102-105 can be performed again, the target blank invoice can be re-tried, and so on.
  • the embodiment may also add relevant identifiers during the execution process. Specifically, before step 201, 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 distribution interface is successful, the preset is The flag information is modified to be normal; otherwise, if the return result of the tax control distribution interface is unsuccessful, the information about the unsuccessful distribution 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 distribution interface is invoked, if the tax control is performed.
  • the result of the distribution interface is unsuccessful (as opposed to the success of the distribution, that is, as long as the distribution is successful, the return result of this tax control distribution interface is considered unsuccessful), the target blank invoice always exists in the distribution 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 distributed can be distinguished from the blank invoice that is abnormally distributed.
  • step 105 may specifically include the following steps:
  • step 303 determine whether the return result of the current tax control distribution interface is successful, and if so, proceed to step 304, and if not, proceed to step 305;
  • step 305 Determine whether the cumulative number of times the target blank invoice is distributed exceeds a preset threshold, and if yes, end the current distribution operation, and if no, return to step 102.
  • the above steps 302-304 are similar to the above steps 201-202, and are not described herein again.
  • step 301 in this application scenario, for each same invoice, the tax distribution distribution interface is called once, and the cumulative number of distributions of the blank invoice is incremented by one, and the tax distribution distribution that has been called for the blank invoice is counted by distributing the cumulative number of times. The number of times the interface. Therefore, if it is determined in step 303 that the return result of the tax control distribution interface is unsuccessful, step 305 may be performed to determine whether the cumulative number of distributions of the target blank invoice exceeds a preset threshold, and if so, the blank invoice for the target is known. After the tax control distribution interface has been called repeatedly, the distribution cannot be successfully distributed. It can be determined that the target blank invoice is abnormal.
  • the distribution operation is ended, and the information about the unsuccessful distribution of the target blank invoice can be fed back to the designated administrator; Otherwise, you can go back to step 102, re-inquire the target blank invoice again and call the tax control distribution interface to ensure the successful distribution of the target blank invoice, and keep the blank invoice inventory of the invoice management system as much as possible. Consistent with the tax control system. In practical applications, generally speaking, after the tax control distribution interface is called twice for the same blank invoice, the distribution success rate of the blank invoice can reach 99.99%, so the above steps 301 ⁇ 305 can basically ensure the target blank invoice to be distributed. Complete the distribution operation.
  • the invoice management system may further insert the invoice related information distributed by the target blank invoice into the invoice database of the invoice management system. If the return result of the tax control distribution interface is unsuccessful, the invoice related information of the current distribution is deleted from the invoice database.
  • the above-mentioned 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 can be used in the invoice database to store the basic information and detailed information.
  • the invoice management table and the distribution information table of the tax control system are queried to determine whether the target blank invoice is distributed. If the target blank invoice is in the invoice management table, it indicates that it has not completed the distribution, thus calling the tax control distribution interface; if the target blank invoice is not in the invoice management table and in the distribution information table, it indicates that it has completed the distribution and Blank invoice inventory is deleted; if the target blank invoice is not in the invoice management table and is not in the distribution information table, although it is not possible to determine whether the target blank invoice is distributed, but the scheme directly calls the tax control distribution interface again, the target blank invoice can be ensured. The distribution is completed and the returned result is deleted from the blank invoice inventory after success. It can be seen that regardless of whether the tax distribution interface returns a specific distribution result, the solution can ensure the distribution of the target blank invoice to be distributed, and ensure that the undistributed blank invoice inventory stored by the invoice management system is consistent with that in the tax control system.
  • 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.
  • the distribution processing method of a blank invoice is mainly described above, and a distribution processing apparatus of a blank invoice will be described in detail below.
  • FIG. 4 is a structural diagram showing an embodiment of a blank processing system for distributing a blank invoice in the embodiment of the present application.
  • a distribution processing device for a blank invoice includes:
  • the target invoice determination module 401 is configured to determine a target blank invoice to be distributed in the blank invoice inventory that is not distributed by the invoice management system;
  • the first query module 402 is configured to query whether the invoice information of the target blank invoice is recorded in an invoice management table of the tax control system, where the invoice management table records invoice information of a blank invoice currently available on the core board;
  • the first distribution triggering module 403 is configured to trigger the distribution operation module 407 if the query result of the first query module 402 is YES;
  • the second query module 404 is configured to: if the query result of the first query module 402 is negative, query whether the invoice information of the target blank invoice is recorded in a distribution information table of the tax control system, the distribution information The table records the invoice information of the blank invoice that has been distributed;
  • the second distribution triggering module 406 is configured to trigger the distribution operation module 407 if the query result of the second query module 404 is negative;
  • the distribution operation module 407 includes:
  • a distribution interface invoking unit 4071 configured to invoke the tax control distribution interface provided by the tax control system on the target blank invoice;
  • the invoice inventory deleting unit 4072 is configured to delete the target blank invoice from the blank invoice inventory if the return result of the current tax control distribution interface is successful.
  • the distribution operation module may further include:
  • a first flag information modifying unit configured to: in the invoice management system, correspond to the target blank invoice before the distribution interface calling unit invokes the tax control distribution interface provided by the tax control system on the target blank invoice
  • the preset flag information is modified to be abnormal
  • a second flag information modification unit configured to modify the preset flag information to be normal if the return result of the tax control distribution interface is successful
  • the information feedback unit is configured to: if the return result of the tax control distribution interface is unsuccessful, feed back information about the unsuccessful distribution of the target blank invoice to the designated administrator.
  • the distribution processing device of the blank invoice may further include:
  • An information insertion module configured to insert the target blank invoice book into an invoice database of the invoice management system before the distribution interface calling unit invokes the tax control distribution interface provided by the tax control system on the target blank invoice Sub-distributed invoice related information;
  • the information deletion module is configured to delete the invoice related information of the current distribution from the invoice database if the return result of the tax control distribution interface is unsuccessful.
  • the target invoice determination module may include:
  • An inventory inquiry unit for querying and displaying a blank invoice in a blank invoice inventory not distributed by the invoice management system
  • An invoice determining unit configured to determine a blank invoice selected by the current user as a target blank invoice to be distributed
  • the distribution processing device of the blank invoice may further include:
  • a billing terminal obtaining module configured to acquire a billing terminal to which the target blank invoice is to be distributed
  • the distribution interface calling unit is specifically configured to: invoke the tax control distribution interface provided by the tax control system to distribute the target blank invoice to the billing terminal.
  • the distribution processing device of the blank invoice may further include:
  • a distribution accumulating module configured to increase the cumulative number of distributions of the target blank invoice by one before the distribution interface calling unit invokes the tax control distribution interface provided by the tax control system on the target blank invoice;
  • the cumulative number judging module is configured to determine whether the cumulative number of distributions of the target blank invoice exceeds a preset threshold if the return result of the tax control distribution interface is unsuccessful;
  • the query triggering module is configured to trigger the first query module if the judgment result of the cumulative number determining 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 processor 50 executes the computer readable instructions 52, the steps in the embodiment of the method for distributing the blank invoices described above are implemented, such as steps 101 to 105 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.
  • the computer readable instructions 52 may be partitioned into one or more modules/units that are stored in the memory 51 and executed by the processor 50, To complete this application.
  • the one or more modules/units may be a series of computer readable instruction instruction segments capable of performing a particular function, the instruction segments being used to describe the execution of the computer readable instructions 52 in the server 5.
  • the server 5 can be a computing device such as a local server or a cloud server.
  • the server may include, but is not limited to, a processor 50, a memory 51. It will be understood by those skilled in the art that FIG. 5 is merely an example of the server 5 and does not constitute a limitation of the server 5, and may include more or less components than those illustrated, or combine some components, or different components, such as
  • the server may also include an input and output device, a network access device, a bus, and the like.
  • the processor 50 can be a central processing unit (Central Processing Unit, CPU), can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 51 may be an internal storage unit of the server 5, such as a hard disk or a memory of the server 5.
  • the memory 51 may also be an external storage device of the server 5, such as a plug-in hard disk, a smart memory card (SMC), and a secure digital (SD) card provided on the server 5. Flash card (Flash Card) and so on.
  • the memory 51 may also include both an internal storage unit of the server 5 and an external storage device.
  • the memory 51 is for storing the computer readable instructions and other programs and data required by the server.
  • the memory 51 can also be used to temporarily store data that has been output or is about to be output.

Landscapes

  • Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Finance (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本申请公开了一种空白发票的分发处理方法，用于解决无法获知税控分发接口的返回结果时，容易导致发票管理系统存储的空白发票的库存与税控系统中的不一致的问题。本申请提供的方法包括：在发票管理系统未分发的空白发票库存中确定当前待分发的目标空白发票；查询目标空白发票的发票信息是否记录在税控系统的发票管理表中，若是，则执行预设的发票分发操作，若否，则查询目标空白发票的发票信息是否记录在税控系统的分发信息表中；若在分发信息表中，则将目标空白发票从空白发票库存中删除；若不在分发信息表中，则执行预设的发票分发操作；预设的发票分发操作包括：调用税控分发接口；若的返回结果为成功，则将目标空白发票从空白发票库存中删除。

Description

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

Claims (20)

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

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710605522.8A CN107784531A (zh) 2017-07-24 2017-07-24 一种空白发票的分发处理方法、存储介质和服务器
CN201710605522.8 2017-07-24

Publications (1)

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

Family

ID=61437500

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083553 Ceased WO2019019712A1 (zh) 2017-07-24 2018-04-18 一种空白发票的分发处理方法、存储介质和服务器

Country Status (2)

Country Link
CN (1) CN107784531A (zh)
WO (1) WO2019019712A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107784531A (zh) * 2017-07-24 2018-03-09 平安科技（深圳）有限公司 一种空白发票的分发处理方法、存储介质和服务器

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106504044A (zh) * 2016-11-09 2017-03-15 百望金赋科技有限公司 一种开票方法及系统
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 百望金赋科技有限公司 一种开票方法、开票系统及其税控服务器
CN106530022A (zh) * 2016-11-09 2017-03-22 百望金赋科技有限公司 一种税控核心板 、使用方法及税控服务器
CN107784531A (zh) * 2017-07-24 2018-03-09 平安科技（深圳）有限公司 一种空白发票的分发处理方法、存储介质和服务器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101320444A (zh) * 2007-06-07 2008-12-10 华为技术有限公司 一种实现电子票据的方法、系统及装置
CN106920135A (zh) * 2015-12-28 2017-07-04 航天信息股份有限公司 一种pos开票服务器离线交易的实现方法及系统
CN106779988A (zh) * 2016-11-15 2017-05-31 百望金赋科技有限公司 一种税控服务器管理系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170076342A1 (en) * 2015-09-15 2017-03-16 Sap Se Duplicate check based on generated hash value
CN106504044A (zh) * 2016-11-09 2017-03-15 百望金赋科技有限公司 一种开票方法及系统
CN106530024A (zh) * 2016-11-09 2017-03-22 百望金赋科技有限公司 一种开票方法、开票系统及其税控服务器
CN106530022A (zh) * 2016-11-09 2017-03-22 百望金赋科技有限公司 一种税控核心板 、使用方法及税控服务器
CN107784531A (zh) * 2017-07-24 2018-03-09 平安科技（深圳）有限公司 一种空白发票的分发处理方法、存储介质和服务器

Also Published As

Publication number Publication date
CN107784531A (zh) 2018-03-09

Similar Documents

Publication Publication Date Title
US20220309052A1 (en) Data Consistency In Master Data Integration
CN109815291B (zh) 数据同步方法、装置、电子设备及存储介质
US20220075900A1 (en) Tracing objects across different parties
US10824602B2 (en) System for determining the impact to databases, tables and views by batch processing
CN107766080B (zh) 事务消息处理方法、装置、设备及系统
US10585877B1 (en) System and method for achieving high quality data integrity
US11157247B2 (en) Cryptographic digital twin segregation system for development operations
WO2019136812A1 (zh) 电子装置、数据调用日志生成及查询方法及存储介质
WO2019140739A1 (zh) 客户回访的判断方法、电子装置及计算机可读存储介质
US12174820B2 (en) Data management system with tamper-evidence
WO2019019701A1 (zh) 一种空白发票的回收处理方法、存储介质和服务器
CN109240854B (zh) 对误操作引起的更改进行数据恢复的方法及系统
US11816163B2 (en) Systems and methods for improved transactional mainframes
US20210133179A1 (en) Method, system and apparatus for processing database updates
CN109324959B (zh) 一种自动转移数据的方法、服务器及计算机可读存储介质
WO2019169771A1 (zh) 电子装置、访问指令信息获取方法及存储介质
CN109284331B (zh) 基于业务数据资源的制证信息获取方法、终端设备及介质
CN116993523A (zh) 配置化对账方法、装置、设备及存储介质
WO2019019631A1 (zh) 空白发票的作废处理方法、可读存储介质、服务器及装置
WO2019019712A1 (zh) 一种空白发票的分发处理方法、存储介质和服务器
US9977726B2 (en) System and method for smart framework for network backup software debugging
CN110781142B (zh) 数据导入方法及装置、服务端及存储介质
CN105760283B (zh) 一种日志输出方法和装置
CN106845263A (zh) 一种访问数据库的方法、装置及电子设备
CN114710333B (zh) 数据传输及校验的方法、系统、计算机设备及存储介质

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: 18837836

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: 18837836

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 FORM 1205A DATED 04.08.2020.

122 Ep: pct application non-entry in european phase

Ref document number: 18837836

Country of ref document: EP

Kind code of ref document: A1