WO2021135742A1 - 对账清算方法及装置 - Google Patents

对账清算方法及装置 Download PDF

Info

Publication number
WO2021135742A1
WO2021135742A1 PCT/CN2020/131563 CN2020131563W WO2021135742A1 WO 2021135742 A1 WO2021135742 A1 WO 2021135742A1 CN 2020131563 W CN2020131563 W CN 2020131563W WO 2021135742 A1 WO2021135742 A1 WO 2021135742A1
Authority
WO
WIPO (PCT)
Prior art keywords
reconciliation
batch
task
executed
task table
Prior art date
Application number
PCT/CN2020/131563
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 WO2021135742A1 publication Critical patent/WO2021135742A1/zh

Links

Images

Classifications

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

Definitions

  • the present disclosure relates to the technical field of data processing, and in particular to a method and device for reconciliation and settlement.
  • the purpose of the present disclosure is to solve one of the above technical problems at least to a certain extent.
  • the first purpose of the present disclosure is to propose a method for reconciliation and settlement, which can clearly know whether the reconciliation task is completed through the execution status of the task in the task table, which improves the operability and maintenance, and can check the future.
  • the completed transaction batches are retried, which improves the success rate of reconciliation tasks and reduces labor costs.
  • the second purpose of the present disclosure is to provide a reconciliation and clearing device.
  • the third purpose of the present disclosure is to provide another reconciliation and clearing device.
  • the fourth purpose of the present disclosure is to provide a non-transitory computer-readable storage medium.
  • the first aspect of the present disclosure provides an account reconciliation method, including: obtaining a reconciliation task table, the reconciliation task table contains the batch information of each batch of reconciliation tasks and the corresponding Execution status; in the case of obtaining the reconciliation task table, determine the batch reconciliation task to be executed according to the reconciliation task table, and the batch reconciliation task to be executed includes at least one of the following: current Batch reconciliation tasks, as well as batch reconciliation tasks whose execution status is not executed and earlier than the current batch; in the case where the execution status of the batch reconciliation task to be executed changes, update the reconciliation The execution status of the batch reconciliation task to be executed in the task table.
  • a reconciliation task table is obtained, and the reconciliation task table contains batch information of each batch reconciliation task and the corresponding execution status; after obtaining the reconciliation task table
  • the batch reconciliation task to be executed is determined according to the reconciliation task table, and the batch reconciliation task to be executed includes at least one of the following: the current batch reconciliation task, and the execution status is unexecuted and A batch reconciliation task that is earlier than the current batch; in the case of a change in the execution status of the batch reconciliation task to be executed, update the batch reconciliation task to be executed in the reconciliation task table The execution status.
  • This method can clearly know whether the reconciliation task is completed through the execution status of the task in the task table, which improves the operation and maintenance, and can retry the batch of uncompleted transactions, which improves the success rate of the reconciliation task and reduces Labor cost.
  • an embodiment of the second aspect of the present disclosure proposes a reconciliation and clearing device, including: an acquisition module to obtain a reconciliation task table, the reconciliation task table contains batch information of each batch of reconciliation tasks And the corresponding execution status; the determining module is configured to determine the batch reconciliation task to be executed according to the reconciliation task table in the case of obtaining the reconciliation task table, and the batch reconciliation to be executed
  • the tasks include at least one of the following: the current batch reconciliation task, and the batch reconciliation task whose execution status is not executed and is earlier than the current batch; the update module is used for the batch reconciliation task to be executed When the execution status changes, the execution status corresponding to the batch reconciliation task to be executed in the reconciliation task table is updated.
  • the reconciliation and clearing device of the embodiment of the present disclosure obtains a reconciliation task table, the reconciliation task table contains the batch information of each batch of reconciliation tasks and the corresponding execution status; when the reconciliation task table is obtained
  • the batch reconciliation task to be executed is determined according to the reconciliation task table, and the batch reconciliation task to be executed includes at least one of the following: the current batch reconciliation task, and the execution status is unexecuted and A batch reconciliation task that is earlier than the current batch; in the case of a change in the execution status of the batch reconciliation task to be executed, update the batch reconciliation task to be executed in the reconciliation task table The execution status.
  • the device can clearly know whether the reconciliation task is completed through the execution status of the task in the task table, which improves the operability and maintenance, and can retry uncompleted transaction batches, which improves the success rate of the reconciliation task. Reduce labor costs.
  • the third aspect of the present disclosure provides another reconciliation and clearing device, including: a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor executes all When the program is described, the above-mentioned reconciliation and settlement method is realized.
  • an embodiment of the fourth aspect of the present disclosure proposes a non-transitory computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the reconciliation and settlement method as described above is realized.
  • Fig. 1 is a schematic flow chart of a method for reconciliation and settlement according to an embodiment of the present disclosure
  • Fig. 2 is a schematic diagram of obtaining a reconciliation task table according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a method for reconciliation and settlement according to another embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of a method for reconciliation and settlement according to another embodiment of the present disclosure.
  • Fig. 5 is a schematic structural diagram of an account reconciliation and clearing device according to an embodiment of the present disclosure.
  • Fig. 6 is a schematic structural diagram of an account reconciliation and clearing device according to another embodiment of the present disclosure.
  • Fig. 7 is a schematic structural diagram of an account reconciliation and clearing device according to another embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an account reconciliation and clearing device according to still another embodiment of the present disclosure.
  • Fig. 9 is a schematic structural diagram of another reconciliation and clearing device according to an embodiment of the present disclosure.
  • the execution subject of the reconciliation and settlement method provided in the present disclosure is a reconciliation and settlement device, and the reconciliation and settlement device may be hardware devices such as terminal devices and servers, or software installed on the hardware devices.
  • FIG. 1 is a schematic flowchart of a method for reconciliation and settlement provided by an embodiment of the disclosure. As shown in Figure 1, the reconciliation and settlement method includes the following steps:
  • Step 101 Obtain a reconciliation task table.
  • the reconciliation task table contains batch information and corresponding execution status of each batch of reconciliation tasks.
  • the reconciliation and clearing device sends a query request to the task table server, the task table server returns the reconciliation task table to be queried to the reconciliation and clearing device, and the account reconciliation device receives the reconciliation task table returned by the task table server.
  • the reconciliation task table contains batch information of each batch of reconciliation tasks and the corresponding execution status.
  • the query request may include, but is not limited to, the identification of the reconciliation task table to be queried.
  • the execution status of the task table may include, but is not limited to, the task has been executed, the task has not been executed, and so on. It should be noted that the identifier of the reconciliation task table is used to determine the reconciliation task table to be queried.
  • the scheduling system at 0 o’clock every day initiates a reconciliation task generation instruction to the reconciliation and clearing device, and the task generation module in the reconciliation and clearing device processes the instruction to generate corresponding tasks for all reconciliation batches of the day.
  • the task table server writes all batch reconciliation tasks into the reconciliation task table.
  • the reconciliation and clearing device sends a query request to the task table server every hour, and the task table server returns the reconciliation task table to be queried to the reconciliation and clearing device, and the reconciliation and clearing device can obtain the corresponding reconciliation task table.
  • Step 103 When the reconciliation task table is obtained, determine the batch reconciliation task to be executed according to the reconciliation task table, and the batch reconciliation task to be executed includes at least one of the following: the current batch reconciliation task, And the batch reconciliation task whose execution status is not executed and is earlier than the current batch.
  • the batch reconciliation tasks to be executed can be determined according to the reconciliation task table.
  • the batch reconciliation tasks whose task execution status is not executed are regarded as pending Batch reconciliation tasks.
  • the current reconciliation time point is 2 o'clock
  • the batch reconciliation tasks whose task execution status is not executed are regarded as pending Batch reconciliation tasks.
  • the determination of the reconciliation time point can be set as required. As an example, you can set reconciliation time points that comply with different rules, or you can set to skip certain reconciliation time points. For example, from 0 to 7 o’clock, from 22 to 24 o’clock, there are fewer expected transactions and can be reconciled every 2 hours. In other time periods, there are more expected transactions and can be reconciled every 1 hour.
  • Step 105 When the execution status of the batch reconciliation task to be executed changes, update the execution status of the batch reconciliation task to be executed in the reconciliation task table.
  • the batch reconciliation task to be executed in the reconciliation task table will be executed The status is updated, and the updated reconciliation task table is sent to the task table server to realize the update of the reconciliation task table in the task table server.
  • the reconciliation and clearing device can receive the reconciliation task table update request, update the reconciliation task table according to the reconciliation task table update request, and send the updated reconciliation task table to the task table server to check the task table server
  • the reconciliation task table is updated. Therefore, when reconciliation and clearing are to be performed again, the reconciliation and clearing device will, according to the updated reconciliation task table, take the batch reconciliation task for the user to reconcile the reconciliation as the batch reconciliation task to be executed, and perform the reconciliation task again. Reconciliation and settlement.
  • the update request may include, but is not limited to: batch reconciliation tasks whose execution status is to be changed, and the changed execution status of batch reconciliation tasks. For example, if the user wants to perform reconciliation and clearing of the batch reconciliation task corresponding to 2 o'clock, he can change the execution status of the batch reconciliation task corresponding to 2 o'clock from executed to not executed.
  • a reconciliation task table is obtained, and the reconciliation task table contains batch information of each batch reconciliation task and the corresponding execution status; in the case of obtaining the reconciliation task table, according to The reconciliation task table determines the batch reconciliation tasks to be executed.
  • the batch reconciliation tasks to be executed include at least one of the following: the current batch reconciliation task, and the batch whose execution status is not executed and is earlier than the current batch Reconciliation task; in the case of a change in the execution status of the batch reconciliation task to be executed, update the execution status of the batch reconciliation task to be executed in the reconciliation task table.
  • the method can clearly know whether the reconciliation task is completed through the task status in the task table, which improves the operation and maintenance, and can retry the uncompleted transaction batches, improves the success rate of the reconciliation task, and reduces labor costs.
  • FIG. 3 is a schematic flowchart of a method for reconciliation and clearing according to another embodiment of the present disclosure, and the specific implementation process is as follows:
  • Step 301 Every day at 0 o’clock, the scheduling system initiates a reconciliation task generation instruction to the reconciliation and clearing device.
  • the task generation module in the reconciliation and clearing device processes the instruction, generates corresponding tasks for all reconciliation batches that day, and writes them into the pair in the database. Account task table.
  • Step 303 The scheduling system initiates a reconciliation processing instruction to the reconciliation and clearing device every hour, and the task processing module in the reconciliation and clearing device processes the instruction, and queries all the batch reconciliation tasks to be executed from the database task table.
  • step 305 after the task processing module of the reconciliation clearing device reads the batch reconciliation task to be executed, it reconciles the transactions of the batch of that date according to the bill date and task batch in the task information.
  • Step 307 If the batch reconciliation task is executed successfully, set the execution status of the batch reconciliation task in the reconciliation task table to be executed, and continue to execute the next batch reconciliation task to be executed; if executed If it fails, skip the batch reconciliation task and continue to execute the next batch reconciliation task.
  • a reconciliation task table is obtained, and the reconciliation task table contains batch information of each batch reconciliation task and the corresponding execution status; in the case of obtaining the reconciliation task table, according to The reconciliation task table determines the batch reconciliation tasks to be executed.
  • the batch reconciliation tasks to be executed include at least one of the following: the current batch reconciliation task, and the batch whose execution status is not executed and is earlier than the current batch Reconciliation task; in the case of a change in the execution status of the batch reconciliation task to be executed, update the execution status of the batch reconciliation task to be executed in the reconciliation task table.
  • This method can clearly know whether the reconciliation task is completed through the task status in the task table, which improves the operation and maintenance, and judges whether there is a reconciliation task to be executed according to the task table, and executes it when there is a reconciliation task to be executed.
  • the reconciliation task to be executed before the reconciliation time point realizes the automatic retry of unfinished reconciliation tasks, improves the success rate of reconciliation tasks, and reduces labor costs.
  • Fig. 4 is a schematic flowchart of a method for reconciliation and settlement according to another embodiment of the present disclosure. As shown in Figure 4, the reconciliation and settlement method includes the following steps:
  • Step 401 Obtain a reconciliation task table.
  • the reconciliation task table contains batch information and corresponding execution status of each batch of reconciliation tasks; if the reconciliation task table is obtained, step 403 is executed; if no reconciliation is obtained For the task table, step 407 is executed.
  • Step 403 When the reconciliation task table is obtained, determine the batch reconciliation task to be executed according to the reconciliation task table.
  • the batch reconciliation task to be executed includes at least one of the following: the current batch reconciliation task, And the batch reconciliation task whose execution status is not executed and is earlier than the current batch.
  • Step 405 When the execution status of the batch reconciliation task to be executed changes, update the execution status of the batch reconciliation task to be executed in the reconciliation task table, and send the updated reconciliation task table to Task table server.
  • Step 407 in the case that the reconciliation task table is not obtained, query each task completion file stored locally; each task completion file stored locally is generated based on the execution result of the batch reconciliation task to be executed and the batch Each reconciliation task corresponds to the task completion file one by one.
  • Step 409 Determine the batch reconciliation task to be executed according to the task completion file.
  • the batch reconciliation task to be executed includes the batch reconciliation task whose execution status is not executed and is earlier than the current batch.
  • the task completion file includes the completion status of the corresponding batch reconciliation task, for example, the task has been executed, the task has not been executed, and so on.
  • the completion status of the batch of reconciliation tasks is still the task not executed. If a batch reconciliation task has not been executed, the completion status of the batch reconciliation task can also be empty, which also means that the task has not been executed.
  • the batch reconciliation task to be executed after the batch reconciliation task to be executed is determined, the batch reconciliation task to be executed performs a clearing operation, and the execution result is obtained.
  • Step 411 When the execution status of the batch reconciliation task to be executed changes, update the execution status of the batch reconciliation task to be executed in the reconciliation task table, and send the updated reconciliation task table to Task table server.
  • a reconciliation task table is obtained, and the reconciliation task table contains batch information of each batch reconciliation task and the corresponding execution status; in the case of obtaining the reconciliation task table, according to The reconciliation task table determines the batch reconciliation tasks to be executed.
  • the batch reconciliation tasks to be executed include at least one of the following: the current batch reconciliation task, and the batch whose execution status is not executed and is earlier than the current batch Reconciliation tasks; in the case that the reconciliation task table is not obtained, query the locally stored task completion files to determine the batch reconciliation tasks to be executed; the execution status of the batch reconciliation tasks to be executed changes In this case, update the execution status of the batch reconciliation tasks to be executed in the reconciliation task table.
  • This method can clearly know whether the reconciliation task is completed through the task status in the task table or locally stored task completion files, which improves the operability and maintenance, and can retry uncompleted transaction batches, which improves the The success rate of account tasks reduces labor costs.
  • an embodiment of the present disclosure also provides a reconciliation and clearing device, because the reconciliation and clearing device provided by the embodiments of the present disclosure is different from that provided by the foregoing several embodiments.
  • the reconciliation and clearing methods are corresponding, so the implementation of the foregoing reconciliation and clearing methods is also applicable to the reconciliation and clearing device provided in this embodiment, and will not be described in detail in this embodiment.
  • Fig. 5 is a schematic structural diagram of an account reconciliation and clearing device according to an embodiment of the present disclosure. As shown in FIG. 5, the reconciliation and settlement device includes: an acquisition module 510, a determination module 520, and an update module 530.
  • the obtaining module 510 is used to obtain the reconciliation task table, and the reconciliation task table contains the batch information of each batch of reconciliation tasks and the corresponding execution status; the determining module 520 is used to obtain the reconciliation task.
  • the batch reconciliation task to be executed is determined according to the reconciliation task table, and the batch reconciliation task to be executed includes at least one of the following: the current batch reconciliation task, and the execution status is not yet The batch reconciliation task that is executed and is earlier than the current batch; the execution module 530 is used to update the batch pair to be executed in the reconciliation task table when the execution status of the batch reconciliation task to be executed changes The execution status corresponding to the account task.
  • the reconciliation and clearing apparatus further includes a storage module 540.
  • the obtaining module 510 is also used to obtain the execution results of the batch reconciliation tasks to be executed; the storage module 540 is used to generate task completion files corresponding to each of the batch reconciliation tasks according to the execution results. And perform local storage; the obtaining module 510 is also used to query each task completion file stored locally when the reconciliation task table is not obtained; the determining module 520 is also used to determine the task completion file to be executed according to the task completion file Batch reconciliation tasks, batch reconciliation tasks to be executed include batch reconciliation tasks whose execution status is not executed and is earlier than the current batch.
  • the obtaining module 510 is specifically configured to send a query request to the task table server, the query request includes: the identification of the reconciliation task table to be queried; and receives the reconciliation returned by the task table server Task table.
  • the reconciliation and clearing apparatus further includes: a receiving module 550.
  • the receiving module 550 is used to receive a reconciliation task table update request, the update request includes: batch reconciliation tasks whose execution status is to be changed, and the changed execution status of the batch reconciliation task; the update module 530 is also used to According to the reconciliation task table update request, the reconciliation task table is updated.
  • the reconciliation and clearing apparatus further includes: a sending module 560.
  • the sending module 560 is configured to send the updated reconciliation task table to the task table server to update the reconciliation task table on the task table server.
  • the reconciliation and clearing device of the embodiment of the present disclosure obtains the reconciliation task table, and the reconciliation task table contains the batch information of each batch reconciliation task and the corresponding execution status; in the case of obtaining the reconciliation task table, according to The reconciliation task table determines the batch reconciliation tasks to be executed.
  • the batch reconciliation tasks to be executed include at least one of the following: the current batch reconciliation task, and the batch whose execution status is not executed and is earlier than the current batch Reconciliation task; in the case of a change in the execution status of the batch reconciliation task to be executed, update the execution status of the batch reconciliation task to be executed in the reconciliation task table.
  • the device can clearly know whether the reconciliation task is completed through the task status in the task table, which improves the operation and maintenance, and judges whether there is a reconciliation task to be performed according to the task table, and when there is a reconciliation task to be performed , Execute the reconciliation task to be executed before the reconciliation time point, realize the automatic retry of the unfinished reconciliation task, improve the success rate of the reconciliation task, and reduce labor costs.
  • the task table can be updated and managed. Repeat the reconciliation of the specified batch without changing the code, which improves the flexibility of the reconciliation business.
  • FIG. 9 is a schematic structural diagram of another reconciliation and clearing device provided by an embodiment of the disclosure.
  • the reconciliation and settlement device includes:
  • the processor 1002 implements the reconciliation and settlement method provided in the foregoing embodiment when executing the program.
  • the reconciliation and settlement device further includes:
  • the communication interface 1003 is used for communication between the memory 1001 and the processor 1002.
  • the memory 1001 is used for storing computer programs that can run on the processor 1002.
  • the memory 1001 may include a high-speed random access memory (Random Access Memory, referred to as RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
  • RAM Random Access Memory
  • non-volatile memory such as at least one disk memory.
  • the processor 1002 is configured to implement the reconciliation and settlement method described in the foregoing embodiment when executing the program.
  • the bus may be an Industry Standard Architecture (ISA) bus, Peripheral Component Interconnect (PCI) bus, or Extended Industry Standard Architecture (EISA) bus Wait.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • the memory 1001, the processor 1002, and the communication interface 1003 are integrated on a single chip, the memory 1001, the processor 1002, and the communication interface 1003 can communicate with each other through internal interfaces.
  • the processor 1002 may be a central processing unit (Central Processing Unit, referred to as CPU), or a specific integrated circuit (Application Specific Integrated Circuit, referred to as ASIC), or configured to implement one or more of the embodiments of the present disclosure integrated circuit.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • the embodiment of the present disclosure also proposes a non-transitory computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the reconciliation and settlement method as in the above-mentioned embodiment is implemented.
  • first and second are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined with “first” and “second” may explicitly or implicitly include at least one of the features. In the description of the present disclosure, “plurality” means at least two, such as two, three, etc., unless otherwise specifically defined.
  • a "computer-readable medium” can be any device that can contain, store, communicate, propagate, or transmit a program for use by an instruction execution system, device, or device or in combination with these instruction execution systems, devices, or devices.
  • computer readable media include the following: electrical connections (electronic devices) with one or more wiring, portable computer disk cases (magnetic devices), random access memory (RAM), Read-Only Memory (Read-Only Memory, ROM for short), Erasable Programmable Read-Only Memory (EPROM or Flash Memory for short), optical fiber devices, and portable CD-ROM read-only memory (Compact Disc Read-Only Memory, referred to as CDROM).
  • the computer-readable medium may even be paper or other suitable medium on which the program can be printed, because it can be used, for example, by optically scanning the paper or other medium, followed by editing, interpretation, or other suitable media if necessary. The program is processed in a manner to obtain the program electronically, and then stored in the computer memory.
  • each part of the present disclosure can be implemented by hardware, software, firmware, or a combination thereof.
  • multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system.
  • Discrete logic gate circuits with logic functions for data signals Logic circuits, dedicated integrated circuits with suitable combinational logic gate circuits, Programmable Gate Array (PGA), Field Programmable Gate Array (Field Programmable Gate Array, FPGA), etc.
  • a person of ordinary skill in the art can understand that all or part of the steps carried in the method of the foregoing embodiments can be implemented by a program instructing relevant hardware to complete.
  • the program can be stored in a computer-readable storage medium. When executed, it includes one of the steps of the method embodiment or a combination thereof.
  • the functional units in the various embodiments of the present disclosure may be integrated into one processing module, or each unit may exist alone physically, or two or more units may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer readable storage medium.
  • the aforementioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种对账清算方法及装置，其中方法包括：获取对账任务表，对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态（101）；在获取到对账任务表的情况下，根据对账任务表确定待执行的批次对账任务，待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务（103）；在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务的执行状态（105）。该方法通过任务表中的任务的执行状态可以明确知道对账任务是否完成，提高了可运维性，且能够对未完成的交易批次进行重试，提高了对账任务成功率，降低人工成本。

Description

对账清算方法及装置
相关申请的交叉引用
本申请要求网联清算有限公司于2019年12月31日提交的、发明名称为“对账清算方法及装置”的、中国专利申请号“201911423926.0”的优先权。
技术领域
本公开涉及数据处理技术领域，尤其涉及一种对账清算方法及装置。
背景技术
随着网络技术和移动通信技术的普及，近年来我国的互联网金融发展迅速，市场规模也在持续扩大，网上交易也越来越普及，因此对交易处理数据的清算需求也日益渐增。
相关技术中，在对交易数据进行清算时，基于时间段进行批次对账，即每一个批次只对上一个时间段的交易进行对账。但是，一个交易批次是否完整的完成了对账却无法获知，可运维性差，并且不能自动对未成功完成的交易批次进行重试，对账任务成功率低，人工成本较高。
发明内容
本公开的目的旨在至少在一定程度上解决上述技术问题之一。
为此，本公开的第一个目的在于提出一种对账清算方法，该方法通过任务表中的任务的执行状态可以明确知道对账任务是否完成，提高了可运维性，且能够对未完成的交易批次进行重试，提高了对账任务成功率，降低了人工成本。
本公开的第二个目的在于提出一种对账清算装置。
本公开的第三个目的在于提出另一种对账清算装置。
本公开的第四个目的在于提出一种非临时性计算机可读存储介质。
为达上述目的，本公开第一方面实施例提出了一种对账清算方法，包括：获取对账任务表，所述对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；在获取到所述对账任务表的情况下，根据所述对账任务表确定待执行的批次对账任务，所述待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；在所述待执行的批次对账任务的执行状态发生变化的情况下，更新所述对账任务表中所述待执行的批次对账任务的执行状态。
本公开实施例的对账清算方法，获取对账任务表，所述对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；在获取到所述对账任务表的情况下，根据所述对账任务表确定待执行的批次对账任务，所述待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；在所述待执行的批次对账任务的执行状态发生变化的情况下，更新所述对账任务表中所述待执行的批次对账任务的执行状态。该方法通过任务表中的任务的执行状态可以明确知道对账任务是否完成，提高了可运维性，且能够对未完成的交易批次进行重试，提高了对账任务成功率，降低了人工成本。
为达上述目的，本公开第二方面实施例提出了一种对账清算装置，包括：获取模块，获取对账任务表，所述对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；确定模块，用于在获取到所述对账任务表的情况下，根据所述对账任务表确定待执行的批次对账任务，所述待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；更新模块，用于在所述待执行的批次对账任务的执行状态发生变化的情况下，更新所述对账任务表中所述待执行的批次对账任务对应的执行状态。
本公开实施例的对账清算装置，获取对账任务表，所述对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；在获取到所述对账任务表 的情况下，根据所述对账任务表确定待执行的批次对账任务，所述待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；在所述待执行的批次对账任务的执行状态发生变化的情况下，更新所述对账任务表中所述待执行的批次对账任务的执行状态。该装置可实现通过任务表中的任务的执行状态可以明确知道对账任务是否完成，提高了可运维性，且能够对未完成的交易批次进行重试，提高了对账任务成功率，降低了人工成本。
为达上述目的，本公开第三方面实施例提出了另一种对账清算装置，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现如上所述的对账清算方法。
为了实现上述目的，本公开第四方面实施例提出了一种非临时性计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如上所述的对账清算方法。
本公开附加的方面和优点将在下面的描述中部分给出，部分将从下面的描述中变得明显，或通过本公开的实践了解到。
附图说明
本公开上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中：
图1为根据本公开一个实施例的对账清算方法的流程示意图；
图2为根据本公开一个实施例的对账任务表获取示意图；
图3为根据本公开另一个实施例的对账清算方法的流程示意图；
图4为根据本公开又一个实施例的对账清算方法的流程示意图；
图5为根据本公开一个实施例的对账清算装置的结构示意图；
图6为根据本公开另一个实施例的对账清算装置的结构示意图；
图7为根据本公开又一个实施例的对账清算装置的结构示意图；
图8为根据本公开再一个实施例的对账清算装置的结构示意图；
图9为根据本公开一个实施例的另一种对账清算装置的结构示意图。
具体实施方式
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。
下面参考附图描述本公开实施例的对账清算方法及装置。本公开提供的对账清算方法的执行主体为对账清算装置，对账清算装置可以为终端设备、服务器等硬件设备，或者为硬件设备上安装的软件。
图1为本公开实施例提供的一种对账清算方法的流程示意图。如图1所示，该对账清算方法包括以下步骤：
步骤101，获取对账任务表，对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态。
可选地，对账清算装置向任务表服务器发送查询请求，任务表服务器向对账清算装置返回待查询的对账任务表，对账清算装置接收任务表服务器返回的对账任务表。所述对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态。其中，查询请求可包括但不限于待查询的对账任务表的标识。任务表的执行状态可包括但不限于任务已执行、任务未执行等。需要说明的是，对账任务表的标识用于确定待查询的对账任务表。
举例而言，如图2所示，每天0点调度系统向对账清算装置发起对账任务生成指令，对账清算装置中任务生成模块处理该指令，将当天所有对账批次生成对应任务，任务表服务器将所有批次对账任务写入对账任务表。对账清算装置每小时向任务表服务器发送查询请求，任务表服务器向对账清算装置返回待查询的对账任务表，对账清算装置可获取对应的对账任务表。
步骤103，在获取到对账任务表的情况下，根据对账任务表确定待执行的批次对账任务，待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务。
举例而言，假设在1天内，以每小时为基准划分时间段，进行对账清算，每次进行对账清算时，可根据对账任务表确定待执行的批次对账任务。作为一种示例，当前时间点对应的批次对账任务、以及早于当前时间点的时间点对应的批次对账任务中，任务执行状态为未执行的批次对账任务，作为待执行的批次对账任务。比如，当前对账时间点为2点，将2点对应的批次对账任务、以及2点之前对应的批次对账任务中，任务执行状态为未执行的批次对账任务作为待执行的批次对账任务。其中，需要说明的是，对账时间点的确定，可以根据需要进行设置。作为一种示例，可以设置符合不同的规律的对账时间点，也可以设置跳过某些对账时间点。比如，0点-7点，22-24点，预期交易较少，可以2小时对一次账，其他时间段，预期交易较多，可以1小时对一次账。
步骤105，在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务的执行状态。
为了通过对账任务表中的执行状态可以明确知道批次对账任务是否完成，每次执行待执行的批次对账任务后，将对账任务表中待执行的批次对账任务的执行状态进行更新，并将更新后的对账任务表发送至任务表服务器，以实现对任务表服务器中对账任务表的更新。
另外，当用户根据需求要对某个批次对账任务重新进行对账清算时，可以向对账清算装置发起对账任务表更新请求。对账清算装置可接收对账任务表更新请求，根据对账任务表更新请求，对对账任务表进行更新，并将更新后的对账任务表发送给任务表服务器，以对任务表服务器上的对账任务表进行更新。从而在再次要进行对账清算时，对账清算装置根据更新后的对账任务表，会将用户要重新进行对账清算的批次对账任务作为待执行的批次对账任务，重新进行对账清算。
其中，更新请求可包括但不限于：待更改执行状态的批次对账任务，以及批次对账任务的更改后执行状态。比如，用户想要对2点钟对应的批次对账任务重新进行对账清算，则可以将2点钟对应的批次对账任务的执行状态从已执行更改为未执行。
本公开实施例的对账清算方法，获取对账任务表，对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；在获取到对账任务表的情况下，根据对账任务表确定待执行的批次对账任务，待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务的执行状态。该方法通过任务表中的任务状态可以明确知道对账任务是否完成，提高了可运维性，且能够对未完成的交易批次进行重试，提高了对账任务成功率，降低人工成本。
为了更好地说明上述实施例，现举例进行说明。
举例而言，如图3所示，图3为根据本公开另一个实施例的对账清算的方法流程示意图，具体的实现过程如下：
步骤301，每天0点调度系统向对账清算装置发起对账任务生成指令，对账清算装置中任务生成模块处理该指令，将当天所有对账批次生成对应任务，并写入数据库中的对账任务表。
步骤303，调度系统每小时向对账清算装置发起对账处理指令，对账清算装置中任务处理模块处理该指令，从数据库任务表中查询所有待执行的批次对账任务。
步骤305，对账清算装置任务处理模块读取到待执行的批次对账任务后，根据任务信息中账单日期和任务批次对该日期批次的交易进行对账。
步骤307，如果该批次对账任务执行成功，则将对账任务表中该批次对账任务的执行状态设置为执行完毕，并继续执行下一个待执行的批次对账任务；如果执行失败，则直接跳过该批次对账任务，继续执行下一个批次对账任务。
当前调度周期执行失败的批次对账任务由于状态未改变，因此在下一个调度周期仍然会被任务处理模块获取到并执行。如果需要对已完成的批次对账任务进行重复清算，只需要将对账任务表中该批次对账任务的状态重置为待执行，则任务处理模块将在下一个调度周期中获取到该批次对账任务并执行。
本公开实施例的对账清算方法，获取对账任务表，对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；在获取到对账任务表的情况下，根据对账任务表确定待执行的批次对账任务，待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务的执行状态。该方法通过任务表中的任务状态可以明确知道对账任务是否完成，提高了可运维性，并根据任务表判断是否存在待执行的对账任务，在存在待执行的对账任务时，执行对账时间点之前的待执行的对账任务，实现了自动对未完成对账任务进行重试，提高了对账任务成功率，降低人工成本，另外，通过对任务表的更新管理可以在不改变代码的情况下对指定批次重复对账，提高了对账业务的灵活性。
图4为根据本公开又一个实施例的对账清算方法的流程示意图。如图4所示，该对账清算方法包括以下步骤：
步骤401，获取对账任务表，对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；若获取到对账任务表，则执行步骤403；若未获取到对账任务表，则执行步骤407。
步骤403，在获取到对账任务表的情况下，根据对账任务表确定待执行的批次对账任务，待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务。
步骤405，在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务的执行状态，并将更新后的对账任务表发送给任务表服务器。
步骤407，在未获取到对账任务表的情况下，查询本地存储的各个任务完成文件；本地存储的各个任务完成文件，为根据待执行的批次对账任务的执行结果生成的与各批次对账任务分别一一对应的任务完成文件。
步骤409，根据任务完成文件确定待执行的批次对账任务，待执行的批次对账任务包括执行状态为未执行且早于当前批次的批次对账任务。
本公开中，任务完成文件中包括有对应的批次对账任务的完成状态，例如，任务已执行、任务未执行等。另外，若某个批次对账任务执行过但未执行成功，则该批次对账任务的完成状态还是任务未执行。若某个批次对账任务未执行过，则该批次对账任务的完成状态也可以为空，为空也表示任务未执行。
本公开中，确定待执行的批次对账任务之后，对待执行的批次对账任务执行清算操作，获取执行结果。
步骤411，在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务的执行状态，并将更新后的对账任务表发送给任务表服务器。
本公开实施例的对账清算方法，获取对账任务表，对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；在获取到对账任务表的情况下，根据对账任务表确定待执行的批次对账任务，待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；在未获取到对账任务表的情况下，查询本地存储的各个任务完成文件，确定待执行的批次对账任务；在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务的执行状态。该方法通过任务表中的任务状态或者本地存储的各个任务完成文件，可以明确知道对账任务是否完成，提高了可运维性，且能够对未完成的交易批次进行重试，提高了对账任务成功率，降低人工成本。
与上述几种实施例提供的对账清算方法相对应，本公开的一种实施例还提供一种对账清算装置，由于本公开实施例提供的对账清算装置与上述几种实施 例提供的对账清算方法相对应，因此在前述对账清算方法的实施方式也适用于本实施例提供的对账清算装置，在本实施例中不再详细描述。图5为根据本公开一个实施例的对账清算装置的结构示意图。如图5所示，该对账清算装置包括：获取模块510、确定模块520、更新模块530。
其中，获取模块510，用于获取对账任务表，对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；确定模块520，用于在获取到所述对账任务表的情况下，根据所述对账任务表确定待执行的批次对账任务，所述待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；执行模块530，用于在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务对应的执行状态。
作为本公开实施例的一种可能的实现方式，如图6所示，在图5所示基础上，对账清算装置还包括：存储模块540。
其中，获取模块510，还用于获取待执行的批次对账任务的执行结果；存储模块540，用于根据执行结果，生成与各所述批次对账任务分别一一对应的任务完成文件并进行本地存储；获取模块510，还用于在未获取到所述对账任务表的情况下，查询本地存储的各个任务完成文件；确定模块520，还用于根据任务完成文件确定待执行的批次对账任务，待执行的批次对账任务包括执行状态为未执行且早于当前批次的批次对账任务。
作为本公开实施例的一种可能的实现方式，获取模块510具体用于，向任务表服务器发送查询请求，查询请求包括：待查询的对账任务表的标识；接收任务表服务器返回的对账任务表。
作为本公开实施例的一种可能的实现方式，如图7所示，在图5所示基础上，对账清算装置还包括：接收模块550。
其中，接收模块550，用于接收对账任务表更新请求，更新请求包括：待更改执行状态的批次对账任务，以及批次对账任务的更改后执行状态；更新模 块530，还用于根据对账任务表更新请求，对对账任务表进行更新。作为本公开实施例的一种可能的实现方式，如图8所示，在图7所示基础上，对账清算装置还包括：发送模块560。
其中，发送模块560，用于将更新后的对账任务表发送给任务表服务器，以对任务表服务器上的对账任务表进行更新。
本公开实施例的对账清算装置，获取对账任务表，对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；在获取到对账任务表的情况下，根据对账任务表确定待执行的批次对账任务，待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；在待执行的批次对账任务的执行状态发生变化的情况下，更新对账任务表中待执行的批次对账任务的执行状态。该装置可实现通过任务表中的任务状态可以明确知道对账任务是否完成，提高了可运维性，并根据任务表判断是否存在待执行的对账任务，在存在待执行的对账任务时，执行对账时间点之前的待执行的对账任务，实现了自动对未完成对账任务进行重试，提高了对账任务成功率，降低人工成本，另外，通过对任务表的更新管理可以在不改变代码的情况下对指定批次重复对账，提高了对账业务的灵活性。
为了实现上述实施例，本公开还提出另一种对账清算装置，图9为本公开实施例提供的另一种对账清算装置的结构示意图。该对账清算装置包括：
存储器1001、处理器1002及存储在存储器1001上并可在处理器1002上运行的计算机程序。
处理器1002执行所述程序时实现上述实施例中提供的对账清算方法。
进一步地，对账清算装置还包括：
通信接口1003，用于存储器1001和处理器1002之间的通信。
存储器1001，用于存放可在处理器1002上运行的计算机程序。
存储器1001可能包含高速随机存取存储器(Random Access Memory，简称为RAM)，也可能还包括非易失性存储器(non-volatile memory)，例如至少 一个磁盘存储器。
处理器1002，用于执行所述程序时实现上述实施例所述的对账清算方法。
如果存储器1001、处理器1002和通信接口1003独立实现，则通信接口1003、存储器1001和处理器1002可以通过总线相互连接并完成相互间的通信。所述总线可以是工业标准体系结构(Industry Standard Architecture，简称为ISA)总线、外部设备互连(Peripheral ComponentInterconnect，简称为PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，简称为EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可选的，在具体实现上，如果存储器1001、处理器1002及通信接口1003，集成在一块芯片上实现，则存储器1001、处理器1002及通信接口1003可以通过内部接口完成相互间的通信。
处理器1002可能是一个中央处理器(Central Processing Unit，简称为CPU)，或者是特定集成电路(Application Specific Integrated Circuit，简称为ASIC)，或者是被配置成实施本公开实施例的一个或多个集成电路。
为了实现上述实施例，本公开实施例还提出一种非临时性计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如上述实施例的对账清算方法。
在本说明书的描述中，参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构、材料或者特点包含于本公开的至少一个实施例或示例中。在本说明书中，对上述术语的示意性表述不必须针对的是相同的实施例或示例。而且，描述的具体特征、结构、材料或者特点可以在任一个或多个实施例或示例中以合适的方式结合。此外，在不相互矛盾的情况下，本领域的技术人员可以将本说明书中描述的不同实施例或示例以及不同实施例或示例的特征进行结合和组合。
此外，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相 对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。在本公开的描述中，“多个”的含义是至少两个，例如两个，三个等，除非另有明确具体的限定。
流程图中或在此以其他方式描述的任何过程或方法描述可以被理解为，表示包括一个或更多个用于实现定制逻辑功能或过程的步骤的可执行指令的代码的模块、片段或部分，并且本公开的优选实施方式的范围包括另外的实现，其中可以不按所示出或讨论的顺序，包括根据所涉及的功能按基本同时的方式或按相反的顺序，来执行功能，这应被本公开的实施例所属技术领域的技术人员所理解。
在流程图中表示或在此以其他方式描述的逻辑和/或步骤，例如，可以被认为是用于实现逻辑功能的可执行指令的定序列表，可以具体实现在任何计算机可读介质中，以供指令执行系统、装置或设备(如基于计算机的系统、包括处理器的系统或其他可以从指令执行系统、装置或设备取指令并执行指令的系统)使用，或结合这些指令执行系统、装置或设备而使用。就本说明书而言，"计算机可读介质"可以是任何可以包含、存储、通信、传播或传输程序以供指令执行系统、装置或设备或结合这些指令执行系统、装置或设备而使用的装置。计算机可读介质的更具体的示例(非穷尽性列表)包括以下：具有一个或多个布线的电连接部(电子装置)，便携式计算机盘盒(磁装置)，随机存取存储器(RAM)，只读存储器(Read-Only Memory，简称为ROM)，可擦除可编辑只读存储器(Erasable Programmable Read-Only Memory，简称为EPROM或闪速存储器)，光纤装置，以及便携式光盘只读存储器(Compact Disc Read-Only Memory，简称为CDROM)。另外，计算机可读介质甚至可以是可在其上打印所述程序的纸或其他合适的介质，因为可以例如通过对纸或其他介质进行光学扫描，接着进行编辑、解译或必要时以其他合适方式进行处理来以电子方式获得所述程序，然后将其存储在计算机存储器中。
应当理解，本公开的各部分可以用硬件、软件、固件或它们的组合来实现。 在上述实施方式中，多个步骤或方法可以用存储在存储器中且由合适的指令执行系统执行的软件或固件来实现。如，如果用硬件来实现和在另一实施方式中一样，可用本领域公知的下列技术中的任一项或他们的组合来实现：具有用于对数据信号实现逻辑功能的逻辑门电路的离散逻辑电路，具有合适的组合逻辑门电路的专用集成电路，可编程门阵列(Programmable Gate Array，简称为PGA)，现场可编程门阵列(Field Programmable Gate Array，简称为FPGA)等。
本技术领域的普通技术人员可以理解实现上述实施例方法携带的全部或部分步骤是可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，该程序在执行时，包括方法实施例的步骤之一或其组合。
此外，在本公开各个实施例中的各功能单元可以集成在一个处理模块中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。
上述提到的存储介质可以是只读存储器，磁盘或光盘等。尽管上面已经示出和描述了本公开的实施例，可以理解的是，上述实施例是示例性的，不能理解为对本公开的限制，本领域的普通技术人员在本公开的范围内可以对上述实施例进行变化、修改、替换和变型。

Claims (12)

  1. 一种对账清算方法，其中，包括：
    获取对账任务表，所述对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；
    在获取到所述对账任务表的情况下，根据所述对账任务表确定待执行的批次对账任务，所述待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；
    在所述待执行的批次对账任务的执行状态发生变化的情况下，更新所述对账任务表中所述待执行的批次对账任务的执行状态。
  2. 根据权利要求1所述的方法，其中，还包括：
    获取所述待执行的批次对账任务的执行结果；
    根据所述执行结果，生成与各所述批次对账任务分别一一对应的任务完成文件并进行本地存储；
    则在获取对账任务表之后，所述方法还包括：
    在未获取到所述对账任务表的情况下，查询本地存储的各个任务完成文件；
    根据所述任务完成文件确定待执行的批次对账任务，所述待执行的批次对账任务包括执行状态为未执行且早于当前批次的批次对账任务。
  3. 根据权利要求1所述的方法，其中，所述获取对账任务表，包括：
    向任务表服务器发送查询请求，所述查询请求包括：待查询的对账任务表的标识；
    接收所述任务表服务器返回的所述对账任务表。
  4. 根据权利要求1-3任一项所述的方法，其中，还包括：
    接收对账任务表更新请求，所述更新请求包括：待更改执行状态的批次对账任务，以及所述批次对账任务的更改后执行状态；
    根据所述对账任务表更新请求，对所述对账任务表进行更新。
  5. 根据权利要求1或4所述的方法，其中，还包括：
    将更新后的对账任务表发送给任务表服务器，以对所述任务表服务器上的对账任务表进行更新。
  6. 一种对账清算装置，其中，包括：
    获取模块，用于获取对账任务表，所述对账任务表中包含各个批次对账任务的批次信息以及对应的执行状态；
    确定模块，用于在获取到所述对账任务表的情况下，根据所述对账任务表确定待执行的批次对账任务，所述待执行的批次对账任务包括以下至少一项：当前批次对账任务，以及执行状态为未执行且早于当前批次的批次对账任务；
    更新模块，用于在所述待执行的批次对账任务的执行状态发生变化的情况下，更新所述对账任务表中所述待执行的批次对账任务对应的执行状态。
  7. 根据权利要求6所述的装置，其中，还包括：存储模块；
    所述获取模块，还用于获取所述待执行的批次对账任务的执行结果；
    所述存储模块，用于根据所述执行结果，生成与各所述批次对账任务分别一一对应的任务完成文件并进行本地存储；
    所述获取模块，还用于在未获取到所述对账任务表的情况下，查询本地存储的各个任务完成文件；
    所述确定模块，还用于根据所述任务完成文件确定待执行的批次对账任务，所述待执行的批次对账任务包括执行状态为未执行且早于当前批次的批次对账任务。
  8. 根据权利要求6所述的装置，其中，所述获取模块具体用于，
    向任务表服务器发送查询请求，所述查询请求包括：待查询的对账任务表的标识；
    接收所述任务表服务器返回的所述对账任务表。
  9. 根据权利要求6-8任一项所述的装置，其中，还包括：接收模块；
    所述接收模块，用于接收对账任务表更新请求，所述更新请求包括：待更改执行状态的批次对账任务，以及所述批次对账任务的更改后执行状态；
    所述更新模块，还用于根据所述对账任务表更新请求，对所述对账任务表进行更新。
  10. 根据权利要求6或9所述的装置，其中，还包括：发送模块，用于将更新后的对账任务表发送给任务表服务器，以对所述任务表服务器上的对账任务表进行更新。
  11. 一种对账清算装置，其中，包括：
    存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求1-5中任一所述的对账清算方法。
  12. 一种非临时性计算机可读存储介质，其上存储有计算机程序，其中，该程序被处理器执行时实现如权利要求1-5中任一所述的对账清算方法。
PCT/CN2020/131563 2019-12-31 2020-11-25 对账清算方法及装置 WO2021135742A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911423926.0A CN111222972A (zh) 2019-12-31 2019-12-31 对账清算方法及装置
CN201911423926.0 2019-12-31

Publications (1)

Publication Number Publication Date
WO2021135742A1 true WO2021135742A1 (zh) 2021-07-08

Family

ID=70829225

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/131563 WO2021135742A1 (zh) 2019-12-31 2020-11-25 对账清算方法及装置

Country Status (2)

Country Link
CN (1) CN111222972A (zh)
WO (1) WO2021135742A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111222972A (zh) * 2019-12-31 2020-06-02 网联清算有限公司 对账清算方法及装置
CN113076340B (zh) * 2021-03-22 2024-01-16 北京同邦卓益科技有限公司 账务数据的处理方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160078532A1 (en) * 2014-09-11 2016-03-17 International Business Machines Corporation Aggregation engine for real-time counterparty credit risk scoring
CN106097092A (zh) * 2016-06-07 2016-11-09 中国建设银行股份有限公司 用于对账的数据处理方法和装置
CN107169749A (zh) * 2017-04-01 2017-09-15 北京波若科技有限公司 网络支付对账方法及系统
CN107392762A (zh) * 2017-04-14 2017-11-24 阿里巴巴集团控股有限公司 清算文件处理的方法、装置及设备
CN111222972A (zh) * 2019-12-31 2020-06-02 网联清算有限公司 对账清算方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010282485A (ja) * 2009-06-05 2010-12-16 Nec System Technologies Ltd 監査リスト生成装置、監査リスト生成方法およびプログラム
CN106339937A (zh) * 2016-11-21 2017-01-18 中国农业银行股份有限公司 一种托管核算对账方法及系统
CN107888672A (zh) * 2017-11-02 2018-04-06 深圳市牛鼎丰科技有限公司 账单数据处理方法、装置、存储介质和计算机设备
CN108182632A (zh) * 2017-12-29 2018-06-19 山大地纬软件股份有限公司 支持业务自动对账的装置
CN108961026A (zh) * 2018-07-04 2018-12-07 中国建设银行股份有限公司 账务核算处理方法、装置及电子设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160078532A1 (en) * 2014-09-11 2016-03-17 International Business Machines Corporation Aggregation engine for real-time counterparty credit risk scoring
CN106097092A (zh) * 2016-06-07 2016-11-09 中国建设银行股份有限公司 用于对账的数据处理方法和装置
CN107169749A (zh) * 2017-04-01 2017-09-15 北京波若科技有限公司 网络支付对账方法及系统
CN107392762A (zh) * 2017-04-14 2017-11-24 阿里巴巴集团控股有限公司 清算文件处理的方法、装置及设备
CN111222972A (zh) * 2019-12-31 2020-06-02 网联清算有限公司 对账清算方法及装置

Also Published As

Publication number Publication date
CN111222972A (zh) 2020-06-02

Similar Documents

Publication Publication Date Title
US20230273937A1 (en) Conditional master election in distributed databases
US8285872B2 (en) Affinity-based transaction processing
WO2021135742A1 (zh) 对账清算方法及装置
CN110806933B (zh) 一种批量任务处理方法、装置、设备和存储介质
CN102971711A (zh) 用于处理批工作单元的设备
US9088537B2 (en) Apparatus and method for executing agent
CN107436799B (zh) 分布式事务一致性实现方法及装置
US7712096B2 (en) Method, system, and storage medium for dynamically reordering resource participation in two-phase commit to heuristically optimize for last-agent optimization
US9514170B1 (en) Priority queue using two differently-indexed single-index tables
CN109446225A (zh) 数据缓存方法、装置、计算机设备及存储介质
US20140067904A1 (en) Selection of transaction managers based on runtime data
CN115984022B (zh) 分布式支付系统统一对账方法和装置
CN109101350A (zh) 一种数据处理方法及其相关设备
CN112783954B (zh) 数据访问方法、装置及服务器
US9298517B2 (en) Exclusive control request allocation method and system
CN112817533A (zh) Ssd管理方法、装置计算机设备及存储介质
CN111367694A (zh) 事件处理方法、服务器及计算机存储介质
CN114338390B (zh) 一种服务器配置方法、计算设备及存储介质
JP7458512B2 (ja) 分散トランザクション処理方法、端末およびコンピュータ読み取り可能な記憶媒体
WO2024119930A1 (zh) 调度方法、装置、计算机设备和存储介质
CN116955342B (zh) 业务数据一致率校验方法和装置
CN116051003B (zh) 库存处理方法、装置、电子设备及存储介质
CN108763247B (zh) 在数据迁移过程中处理用户请求的方法及装置
CN116405533A (zh) 请求发送方法、装置、电子设备及存储介质
CN117076503A (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: 20909078

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

Country of ref document: EP

Kind code of ref document: A1