CN116843335A - Multiparty reconciliation method, apparatus, device, medium and program product - Google Patents

Abstract

The disclosure provides a multiparty account checking method which can be applied to the technical field of financial account checking. The multiparty account checking method comprises the following steps: generating a plurality of sub-reconciliation files of the platform system and the network system according to the records to be reconciled; generating a first reconciliation error table according to the plurality of sub-reconciliation files; and performing error check on the first reconciliation error table and a second reconciliation error table of the accounting system to generate a reconciliation result. The present disclosure also provides a multiparty reconciliation apparatus, device, storage medium and program product.

Description

Multiparty reconciliation method, apparatus, device, medium and program product

Technical Field

The present disclosure relates to the field of financial reconciliation, and in particular, to a multi-party reconciliation method, apparatus, device, medium and program product.

Background

Based on the information provided, existing payment systems include accounting systems and platform systems. Prior to 2017, the bank was docked directly with the payment mechanism for payment transactions, and the platform system was reconciled with the accounting system at the end of the day. However, since 2017, the online payment transaction must access the network clearing platform system, which results in the bank interfacing with the network, and the network interfacing with the payment mechanism, as required by the central office. The account checking scheme of the platform system is changed into the day-end account checking of the platform system and the accounting system, and the day-end account checking of the accounting system and the internet. The proposal needs a newly added daytime account checking file of the accounting system, and the newly added daytime account checking file of the accounting system and the internet in the platform system, namely end-to-end account checking.

However, in the newly added daytime account checking file of the accounting system, the improvement of the accounting system is involved, and redundant data on the side of the accounting system needs to be received and stored, so that a large amount of storage space is occupied. At the same time, there is a risk of inconsistent reconciliation source data.

Disclosure of Invention

In view of the foregoing, the present disclosure provides a multiparty reconciliation method, apparatus, device, medium and program product.

According to a first aspect of the present disclosure, there is provided a multiparty reconciliation method comprising: generating a plurality of sub-reconciliation files of the platform system and the network system according to the records to be reconciled; generating a first reconciliation error table according to the plurality of sub-reconciliation files; performing error check on the first checking error table and the second checking error table to generate checking results; the first reconciliation error table comprises a plurality of first reconciliation error records, wherein error information of a single transaction bill in the reconciliation of the platform system and the network system is recorded in the first reconciliation error records; the second reconciliation error table comprises a plurality of second reconciliation error records, and error information of a single transaction bill in the reconciliation of the platform system and the accounting system is recorded in the second reconciliation error records.

According to an embodiment of the present disclosure, error checking the first reconciliation error table with the second reconciliation error table, generating a reconciliation result includes: executing a first circulation process until a preset first circulation stop condition is met, wherein the preset first circulation stop condition is that states of a plurality of first reconciliation error records are checked, and the first circulation process is used for performing error check on the first reconciliation error records with the states of unchecked in a first reconciliation error table to generate a first check result; executing a second circulation process until a preset second circulation stop condition is met, wherein the preset second circulation stop condition is that states of a plurality of second reconciliation error records are checked, and the second circulation process is used for performing error check on the second reconciliation error records with the states of unchecked in a second reconciliation error table to generate a second check result; and generating a reconciliation result according to the first check result and the second check result.

According to an embodiment of the present disclosure, the first cyclic process includes: acquiring a first reconciliation error record with a non-checked state in the first reconciliation error records; judging whether the first account checking error record with the state of non-checking meets a first preset condition or not; and executing a first reconciliation process for generating a first check result when the first reconciliation error record whose status is unchecked satisfies a first preset condition.

According to an embodiment of the present disclosure, a first reconciliation process comprises: searching a second reconciliation error record which is the same as the transaction serial number and the organization number of the first reconciliation error record with the unchecked state from the plurality of second reconciliation error records; generating a first checking result according to a first checking error record, a second checking error record and a preset error comparison rule, wherein the first checking error record and the second checking error record are in an uncore state; updating the status of the second reconciliation error record to checked; the status of the first reconciliation error record whose status is unchecked is updated to checked.

According to an embodiment of the present disclosure, the second cyclic process includes: acquiring a second reconciliation error record with a non-checked state in the plurality of second reconciliation error records; judging whether the second checking error record with the state of non-checking meets a second preset condition or not; and executing a second reconciliation process for generating a second check result in the case that the second reconciliation error record whose status is unchecked satisfies a second preset condition.

According to an embodiment of the present disclosure, the second reconciliation process comprises: searching a first reconciliation error record which is the same as the transaction serial number and the institution number of a second reconciliation error record with the unchecked state from the plurality of first reconciliation error records; generating a second checking result according to the second checking error record, the first checking error record and a preset error checking rule, wherein the second checking error record is in an uncore state; updating the status of the first reconciliation error record to checked; and updating the state of the second reconciliation error record with the state of unchecked to checked.

According to an embodiment of the present disclosure, the first preset condition includes: the first checking error record with the state of non-checking is provided with a completion identification of checking the platform system and the accounting system, and the first checking error record with the state of non-checking is provided with a completion identification of checking the platform system and the network system.

According to an embodiment of the present disclosure, the second preset condition includes: the second reconciliation error record with the status of unchecked has a completion identification of the platform system reconciliation with the network system.

According to an embodiment of the present disclosure, generating a plurality of sub-reconciliation files for a platform system and a network system from a record to be reconciled includes: acquiring a reconciliation detail file of the network system according to the record to be reconciled; dividing the account checking detail file into a plurality of sub account checking detail files according to the transaction serial number; dividing a transaction detail file of a platform system into a plurality of sub-transaction detail files according to a transaction serial number; and merging the sub-reconciliation statement files with the same transaction serial numbers with the sub-transaction statement files to generate a plurality of sub-reconciliation files.

According to an embodiment of the present disclosure, generating a first reconciliation error table from a plurality of sub-reconciliation documents comprises: all sub reconciliation documents are checked in parallel to generate a check result; and generating a first reconciliation error table according to the order of the transaction serial numbers according to the check result.

A second aspect of the present disclosure provides a multiparty reconciliation apparatus comprising: the first generation module is used for generating a plurality of sub reconciliation files of the platform system and the network system according to the records to be reconciled; the second generation module is used for generating a first reconciliation error table according to the plurality of sub reconciliation files; and the error checking module is used for checking the first checking error table with the second checking error table of the accounting system in error to generate a checking result.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the multiparty reconciliation method described above.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described multiparty reconciliation method.

A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the multiparty reconciliation method described above.

According to the multiparty account checking method provided by the disclosure, on one hand, the transformation cost and the workload are reduced, and the accounting system does not need to be transformed, so that the transformation range and the transformation workload are greatly reduced, and the implementation cost is reduced. On the other hand, the storage space and the data cleaning cost are reduced, and only one accounting system account checking file is needed, so that the storage space requirement is reduced, and the storage and data cleaning cost is reduced. In still another aspect, in the method provided by the present disclosure, only one account checking file of the accounting system is used, so that the risk of inconsistent account checking source data is avoided. In yet another aspect, the present disclosure provides a new reconciliation solution for systems that do not have end-to-end reconciliation conditions.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be more apparent from the following description of embodiments of the disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram of multiparty reconciliation in accordance with an embodiment of the disclosure;

FIG. 2 schematically illustrates a flow diagram of a multiparty reconciliation method in accordance with an embodiment of the disclosure;

FIG. 3 schematically illustrates a flow diagram of generating a plurality of sub-reconciliation files in accordance with an embodiment of the disclosure;

FIG. 4 schematically illustrates a flow chart of performing error checking to generate reconciliation results in accordance with an embodiment of the disclosure;

FIG. 5 schematically illustrates a flow chart of a first cyclical process in accordance with an embodiment of the disclosure;

FIG. 6 schematically illustrates a flow chart of a second cyclical process in accordance with an embodiment of the disclosure;

fig. 7 schematically illustrates a block diagram of multiparty error check in accordance with an embodiment of the present disclosure;

FIG. 8 schematically illustrates a block diagram of a multi-party reconciliation apparatus in accordance with an embodiment of the disclosure; and

fig. 9 schematically illustrates a block diagram of an electronic device adapted to implement a multiparty reconciliation method in accordance with an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Fig. 1 schematically illustrates an application scenario diagram of multiparty reconciliation in accordance with an embodiment of the disclosure.

As shown in fig. 1, an application scenario 100 according to this embodiment may include a platform system 101, an accounting system 102, and a networking system 103.

The platform system 101 is part of the payment system of the bank, which is responsible for processing and tracking the various stages of the transaction. This system may include user interfaces, databases, servers, and other components to support various payment and transaction activities. In some embodiments, the number of platform systems 101 may be multiple. The platform system 101 may be, for example, a unified payment system, a credit system, an acquirer system, a coupon system, a points system, or the like.

Accounting system 102 is a financial system for processing and recording financial transactions for an organization, including all check-in and check-out transactions. These systems are commonly used in banks, financial institutions, large businesses, government institutions, etc. for processing large amounts of transaction data. Accounting system 102 is responsible for processing all transactions associated with the bank account and recording these transactions in a database. It may interact with other systems (e.g., platform system 101 and network system 103) to accomplish reconciliation tasks.

The internet connection system 103 is an internet connection clearing platform of the Chinese Unionpay. The China Union is a bank card organization in China for processing bank card transactions across rows and regions. In order to meet the requirements of China people's bank (i.e. central office), all online payment transactions require an access network linked computing platform. The internet system 103 is a large electronic payment system responsible for processing and clearing all transactions conducted over the internet of silver. This platform connects all banks and payment institutions, handling a large number of transactions per day.

Network 104 is the medium used to provide communication links between multi-party systems 101, 102, 103 and server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

Server 105 may be a server that provides various services, such as a background management server (by way of example only) that provides support for reconciliation data generated by systems 101, 102, 103. The background management server can analyze and process the received data such as the user request and the like, and feed back the processing result to the multiparty system. In some embodiments, server 105 may be configured in platform system 101.

It should be noted that, the multiparty accounting method provided by the embodiments of the present disclosure may be generally executed by the server 105. Accordingly, the multiparty reconciliation apparatus provided by the embodiments of the present disclosure may be generally provided in the server 105. The multiparty reconciliation method provided by the embodiments of the present disclosure may also be performed by a server or cluster of servers other than server 105 and capable of communicating with multiparty systems 101, 102, 103 and/or server 105. Accordingly, the multiparty reconciliation apparatus provided by embodiments of the present disclosure may also be provided in a server or server cluster that is different from server 105 and is capable of communicating with multiparty systems 101, 102, 103 and/or server 105.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of systems, networks, and servers, as desired for implementation.

The multiparty reconciliation method of the disclosed embodiments will be described in detail below with reference to fig. 2-6 based on the scenario described in fig. 1.

Fig. 2 schematically illustrates a flow chart of a multiparty reconciliation method in accordance with an embodiment of the disclosure.

As shown in fig. 2, the multiparty reconciliation of this embodiment includes steps S210 to S230.

In operation S210, generating a plurality of sub-reconciliation files of the platform system and the network system according to the record to be reconciled;

it should be noted that, the online system interfaces all banks and payment institutions, and daily transaction amount is very large, so that the online system generates a reconciliation file of the transaction in the last hour every hour, and in order to improve the reconciliation efficiency, the reconciliation of the platform system and the online system is designed as a process, and the reconciliation is performed once every hour. To complete the reconciliation, the reconciliation file is pulled from the online platform to the platform system every hour, converted into a reconciliation format, then the transaction detail file is obtained from the platform system according to the record to be reconciled, the reconciliation detail file (i.e., the file generated by converting the pulled reconciliation file into the format described in this paragraph) is obtained from the online system, and the transaction detail file and the reconciliation detail file are integrated into a plurality of sub-reconciliation files.

In operation S220, a first reconciliation error table is generated from the plurality of sub-reconciliation files;

according to the embodiment of the disclosure, a plurality of sub-reconciliation files are distributed to a plurality of processing units (such as a plurality of CPU cores or a plurality of servers) for concurrent processing, each record is checked one by one in each sub-reconciliation file, and if errors exist, the errors are recorded in a first reconciliation error table in the order of transaction serial numbers.

In operation S230, performing error checking on the first reconciliation error table and the second reconciliation error table to generate a reconciliation result;

it should be noted that the first reconciliation error table includes a plurality of first reconciliation error records, in which error information of a single transaction bill in the reconciliation of the platform system and the internet system is recorded, and the second reconciliation error table includes a plurality of second reconciliation error records, in which error information of a single transaction bill in the reconciliation of the platform system and the accounting system is recorded.

The second reconciliation error table is generated by the platform system and the accounting system, specifically, after the trade of one day is finished, the accounting system generates a reconciliation file containing all trade details. This file typically includes details of each transaction, such as transaction time, transaction amount, transaction type, etc. The generated reconciliation file may be transmitted to the platform system. This may be accomplished in various ways, such as by the Secure File Transfer Protocol (SFTP). The platform system will compare the received accounting system accounting file with its own recorded transaction details. This is typically done by an automated process that compares the data in the two files line by line to check if the details of each transaction are consistent. If any inconsistencies are found during the alignment, these inconsistencies are recorded in the second reconciliation error table.

In some embodiments, after steps S210 to S220 are performed, a preset time may be waited, and steps S210 to S220 may be repeated after waiting. Waiting for a period of time is to ensure that the data synchronization between the system and the network is complete. After checking, the system needs a certain time to transmit data to the internet to process and compare, so as to ensure the accuracy of accounting. After waiting for a period of time, checking out is performed again, so that the data synchronization between the system and the internet connection can be ensured to be complete, and possible differences or abnormal conditions can be found in time, so that the accuracy and efficiency of checking out are improved.

Fig. 3 schematically illustrates a flow chart of generating a plurality of sub-reconciliation files in accordance with an embodiment of the disclosure.

As shown in fig. 3, step 210 may include steps 310-340.

In operation S310, a reconciliation detail file of the network system is obtained according to the record to be reconciled; it should be noted that before obtaining the record to be checked, whether the platform system has the record to be checked is required to be judged, if yes, the checking detail file of the network system is obtained according to the record to be checked. The records to be reconciled are typically those that have not been reconciled yet, which may be marked as "not reconciled" or determined from their time stamps. Typically, the record to be reconciled will be stored in a relational database (e.g., mySQL, oracle, etc.), or a file system (e.g., HDFS, S3, etc.).

In operation S320, the reconciliation statement file is split into a plurality of sub-reconciliation statements files per transaction flow number. A transaction serial number, also commonly referred to as a transaction ID or transaction reference number, is a unique identifier that is used to track and record a particular financial transaction. Each transaction (whether deposit, withdrawal, transfer, or payment) is assigned a unique transaction serial number when processed. This number may be used to query transaction details, check out, resolve transaction disputes, etc. Transaction serial numbers are typically automatically generated by the system to ensure that each transaction has a unique identification.

According to the embodiment of the disclosure, the reconciliation statement file is split according to the specified two digits (required to uniformly distribute transactions) in the transaction serial number, and 100 sub-reconciliation statement files are generated. The "evenly distributed transaction" requirement herein means that the two digits in the transaction stream number (which may be any two digits, such as the last two digits, or two digits in other positions as well) should be evenly distributed among all possible digits (00-99), that is, each of the possible digits has approximately the same probability of occurrence. For example, if we choose the last two digits of the serial number to split, then all transactions ending in 00 will be placed in one file, all transactions ending in 01 will be placed in another file, and so on, up to 99. If the two digits of the transaction stream number are evenly distributed, we can get 100 small files of approximately equal size. Thus, the sizes of the split small files are ensured to be approximately equal, and no certain file is particularly large or particularly small, so that the processing efficiency and the possibility of parallel processing are improved. When the amount of data to be processed is very large, splitting the data into multiple small files can make it easier for the data processing tasks to be distributed to multiple processing units (e.g., multiple CPU cores or multiple servers) for parallel processing, thereby greatly increasing the processing speed. At the same time, handling small files is generally easier to manage and less prone to error than handling one large file.

In operation S330, the transaction detail file of the platform system is split into a plurality of sub-transaction detail files according to the transaction serial number.

According to the embodiment of the disclosure, according to the transaction detail file corresponding to the record to be checked, the transaction detail file is split into 100 sub-transaction detail files according to the method for splitting the check detail file.

In operation S340, merging the sub-reconciliation documents with the same transaction serial numbers with the sub-transaction documents to generate a plurality of sub-reconciliation documents;

according to the embodiment of the disclosure, the split 100 groups of sub transaction detail files are combined with the files with the same transaction serial number paragraphs in the 100 groups of sub reconciliation detail files, and the 100 sub reconciliation files are generated according to the ordering of the transaction serial numbers. The merging method may, for example, read the records in the two subfiles line by a program, match according to the transaction serial number, and merge the matched records together.

In some embodiments, if a matching transaction serial number is not found in the reconciliation file, then this record may be marked as an error and recorded in an error table.

Fig. 4 schematically illustrates a flow chart of performing error checking to generate reconciliation results in accordance with an embodiment of the disclosure.

As shown in fig. 4, step S230 may include steps S410 to S430.

In operation S410, a first loop process is performed until a preset first loop stop condition is satisfied, where the preset first loop stop condition is that states of a plurality of first reconciliation error records are checked, and the first loop process is used for performing error check on the first reconciliation error records whose states are unchecked in the first reconciliation error table, so as to generate a first check result.

In operation S420, a second loop process is performed until a preset second loop stop condition is satisfied, where the preset second loop stop condition is that states of a plurality of second reconciliation error records are checked, and the second loop process is used for performing error check on the second reconciliation error records whose states are unchecked in the second reconciliation error table, so as to generate a second check result.

In operation S430, a reconciliation result is generated based on the first reconciliation result and the second reconciliation result.

The cyclic process in the embodiment of the present disclosure will be described in detail with reference to fig. 5 to 6 based on the two cyclic processes described in fig. 4;

fig. 5 schematically shows a flow chart of a first cyclic process according to an embodiment of the disclosure.

As shown in fig. 5, the first cyclic process includes steps S510 to S530;

In operation S510, a first reconciliation error record whose status is unchecked among the plurality of first reconciliation error records is acquired.

In operation S520, it is determined whether the first reconciliation error record, which is in the unverified state, satisfies a first preset condition.

According to an embodiment of the present disclosure, the first preset condition is: the first checking error record with the state of non-checking is provided with a completion identification of checking the platform system and the accounting system, and the first checking error record with the state of non-checking is provided with a completion identification of checking the platform system and the network system. Various problems may occur during the reconciliation process, such as data loss, data errors, etc. By judging whether the current record is checked out or not, all transactions can be ensured to be checked out, and the problem caused by missing checking out is avoided.

In the case where the first reconciliation error record whose status is unchecked satisfies the first preset condition, a first reconciliation process S530 is performed.

According to an embodiment of the present disclosure, the second reconciliation process S530 may include steps S531-S534.

In operation S531, a first reconciliation error record identical to the transaction serial number and the institution number of the second reconciliation error record whose status is unchecked is searched for from the plurality of first reconciliation error records. The institution number is a unique number used to identify a particular financial institution for identifying and verifying the source or destination of the transaction.

In operation S532, a first check result is generated according to the first reconciliation error record, the second reconciliation error record, and the preset error comparison rule, the status of which is unchecked;

according to an embodiment of the present disclosure, the preset error control rule may be as shown in table 1.

Table 1 error lookup table

In operation S533, the status of the second reconciliation error record is updated to checked; the second reconciliation error record here is the same transaction serial number and institution number as the first reconciliation error record whose status was not checked in step S531.

In operation S534, the status of the first reconciliation error record whose status is unchecked is updated to checked.

Fig. 6 schematically shows a flow chart of a second cyclic process according to an embodiment of the disclosure.

As shown in fig. 6, the second cycle includes steps S610 to S630;

in operation S610, a second reconciliation error record whose status is unchecked among the plurality of second reconciliation error records is acquired.

In operation S620, it is determined whether the second reconciliation error record, which is in the unverified state, satisfies a second predetermined condition.

According to an embodiment of the present disclosure, the second preset condition is: the second reconciliation error record with the status of unchecked has a completion identification of the platform system reconciliation with the network system. Since the checking of the first reconciliation error table has been completed at this time, it is not necessary to re-verify whether the record has a completion identification of the reconciliation of the platform system with the reconciliation system.

In the case where the second reconciliation error record whose status is unchecked satisfies the second preset condition, a second reconciliation process S630 is performed.

According to an embodiment of the present disclosure, the second reconciliation process S630 may include steps S631-S634.

In operation S631, a first reconciliation error record identical to the transaction serial number and the institution number of the second reconciliation error record whose status is unchecked is searched for from the plurality of first reconciliation error records.

In operation S632, a second checking result is generated according to the second checking error record, the first checking error record, and the preset error checking rule, the status of which is unchecked; in the embodiment of the present disclosure, the preset error comparison rule refers to table 1 above.

In operation S633, the status of the first reconciliation error record is updated to checked; the first reconciliation error record here is the same transaction serial number and institution number as the second reconciliation error record whose status was not checked in step S631.

In operation S634, the status of the second reconciliation error record whose status is unchecked is updated to checked.

According to the embodiment of the disclosure, when the first cycle process and the second cycle process are the cycle processes shown in fig. 5 and 6, all the uncore records in the first reconciliation error table are checked in the first cycle process, and at the same time, part of the records in the second reconciliation error table (i.e., the second reconciliation error records with the same transaction serial number and organization number as the uncore first reconciliation error records in the first cycle process) are checked and marked as checked. The recording collation amount in performing the second cycle is reduced, and collation efficiency is improved. And in the second cycle process, all the uncore records in the second reconciliation error table are completely checked, and meanwhile, part of the records in the second reconciliation error table (namely, the first reconciliation error records with the same transaction serial numbers and the same organization numbers as the uncore second reconciliation error records in the second cycle process) are checked, so that on one hand, the record check omission caused by factors such as external program interruption in the first cycle process is avoided, and on the other hand, the check accuracy is improved, and on the other hand, the check is equivalent to the detection of part of the check records in the first cycle process.

Fig. 7 schematically illustrates a block diagram of multiparty error check in accordance with an embodiment of the present disclosure.

Based on the multiparty account checking method, the end-to-end account checking between two systems which are not directly checked is realized, and the method is also suitable for realizing end-to-end account checking between multiple systems. As shown in fig. 7, for example, there is a system A, B, C, D, to implement end-to-end reconciliation of a and D, based on a and B, B and C, C and D, a and C reconciliation errors are generated based on a and B reconciliation errors and B and C reconciliation errors, and a and D reconciliation errors are generated using a and C reconciliation errors and C and D reconciliation errors, to implement end-to-end reconciliation of a and D.

According to the multiparty account checking method provided by the disclosure, on one hand, the transformation cost and the workload are reduced, and the accounting system does not need to be transformed, so that the transformation range and the transformation workload are greatly reduced, and the implementation cost is reduced. On the other hand, the storage space and the data cleaning cost are reduced, and only one accounting system account checking file is needed, so that the storage space requirement is reduced, and the storage and data cleaning cost is reduced. In still another aspect, in the method provided by the present disclosure, only one account checking file of the accounting system is used, so that the risk of inconsistent account checking source data is avoided. In yet another aspect, the present disclosure provides a new reconciliation solution for systems that do not have end-to-end reconciliation conditions. In still another aspect, a new reconciliation method is added, and the accounting check can be implemented on the basis of a small amount of error data.

Based on the multiparty reconciliation method, the disclosure also provides a multiparty reconciliation device. The device will be described in detail below in connection with fig. 8.

Fig. 8 schematically illustrates a block diagram of a multiparty reconciliation apparatus in accordance with an embodiment of the disclosure.

As shown in fig. 8, the multiparty reconciliation apparatus 800 of this embodiment includes a first generation module 810, a second generation module 820, and an error checking module 830.

The first generating module 810 is configured to generate a plurality of sub-reconciliation documents of the platform system and the internet system according to the record to be reconciled. In an embodiment, the first generating module 810 may be used to perform the operation S210 described above, which is not described herein.

The second generation module 820 is configured to generate a first reconciliation error table according to the plurality of sub-reconciliation documents. In an embodiment, the second generating module 820 may be used to perform the operation S220 described above, which is not described herein.

The error checking module 830 is configured to perform error checking on the first reconciliation error table and the second reconciliation error table of the accounting system, and generate a reconciliation result. In an embodiment, the error checking module 830 may be configured to perform the operation S230 described above, which is not described herein.

Any of the first generation module 810, the second generation module 820, and the error checking module 830 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules according to an embodiment of the present disclosure. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the first generation module 810, the second generation module 820, and the error checking module 830 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the first generation module 810, the second generation module 820, and the error checking module 830 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.

Fig. 9 schematically illustrates a block diagram of an electronic device adapted to implement a multiparty reconciliation method in accordance with an embodiment of the disclosure.

As shown in fig. 9, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage portion 908 into a Random Access Memory (RAM) 903. The processor 901 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 901 may also include on-board memory for caching purposes. Processor 901 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 903, various programs and data necessary for the operation of the electronic device 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other by a bus 904. The processor 901 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 902 and/or the RAM 903. Note that the program may be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the disclosure, the electronic device 900 may also include an input/output (I/O) interface 905, the input/output (I/O) interface 905 also being connected to the bus 904. The electronic device 900 may also include one or more of the following components connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 902 and/or RAM 903 and/or one or more memories other than ROM 902 and RAM 903 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to implement the item recommendation method provided by embodiments of the present disclosure.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 901. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed, and downloaded and installed in the form of a signal on a network medium, via communication portion 909, and/or installed from removable medium 911. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 901. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims (14)

1. A multi-party reconciliation method comprising:

generating a plurality of sub-reconciliation files of the platform system and the network system according to the records to be reconciled;

Generating a first reconciliation error table according to the plurality of sub-reconciliation files;

performing error check on the first reconciliation error table and the second reconciliation error table to generate a reconciliation result;

the first reconciliation error table comprises a plurality of first reconciliation error records, wherein error information of a single transaction bill in a reconciliation of a platform system and a network system is recorded in the first reconciliation error records;

the second reconciliation error table comprises a plurality of second reconciliation error records, wherein error information of a single transaction bill in the reconciliation of the platform system and the accounting system is recorded in the second reconciliation error records.

2. The multiparty reconciliation method of claim 1, wherein error checking the first reconciliation error table with the second reconciliation error table to generate a reconciliation result comprises:

executing a first circulation process until a preset first circulation stop condition is met, wherein the preset first circulation stop condition is that states of the plurality of first reconciliation error records are checked, and the first circulation process is used for performing error check on the first reconciliation error records with the states of unchecked in the first reconciliation error table to generate a first check result;

Executing a second circulation process until a preset second circulation stop condition is met, wherein the preset second circulation stop condition is that states of the plurality of second reconciliation error records are checked, and the second circulation process is used for performing error check on the second reconciliation error records with the states of unchecked in the second reconciliation error table to generate a second check result;

and generating the reconciliation result according to the first check result and the second check result.

3. The multiparty reconciliation method of claim 2, wherein the first loop process comprises:

acquiring a first reconciliation error record with a non-checked state in the plurality of first reconciliation error records;

judging whether the first checking error record which is not checked in the state meets a first preset condition or not;

and executing a first reconciliation process for generating the first check result under the condition that the first reconciliation error record with the status of unchecked meets the first preset condition.

4. The multiparty reconciliation method of claim 3, wherein the first reconciliation process comprises:

searching a second reconciliation error record which is the same as the transaction serial number and the institution number of the first reconciliation error record with the unchecked state from the plurality of second reconciliation error records;

Generating a first checking result according to the first checking error record, the second checking error record and a preset error checking rule, wherein the first checking error record and the second checking error record are not checked;

updating the status of the second reconciliation error record to checked;

and updating the state of the first reconciliation error record with the state of unchecked to checked.

5. The multiparty reconciliation method of claim 2, wherein the second loop process comprises:

acquiring a second reconciliation error record with a non-checked state in the plurality of second reconciliation error records;

judging whether the second checking error record which is not checked in the state meets a second preset condition or not;

and executing a second reconciliation process for generating the second check result when the second reconciliation error record whose status is unchecked satisfies the second preset condition.

6. The multiparty reconciliation method of claim 5, wherein the second reconciliation process comprises:

searching a first reconciliation error record which is the same as the transaction serial number and the institution number of a second reconciliation error record with the unchecked state from the plurality of first reconciliation error records;

Generating a second checking result according to the second checking error record, the first checking error record and a preset error checking rule, wherein the second checking error record is not checked in the state;

updating the status of the first reconciliation error record to checked;

and updating the state of the second reconciliation error record with the state of unchecked to checked.

7. The multiparty reconciliation method of claim 3, wherein the first preset condition comprises:

the first reconciliation error record with the status of unchecked has a completion identification of the platform system reconciliation with the accounting system, and

and the status is that the first checking error record which is not checked has a finishing identification of checking the platform system and the network system.

8. The multiparty reconciliation method of claim 5, wherein the second preset condition comprises:

and the status is that the second checking error record which is not checked has a finishing identification of checking the platform system and the network system.

9. The multiparty reconciliation method of claim 1, wherein generating the plurality of sub-reconciliation files for the platform system and the network system from the records to be reconciled comprises:

Acquiring a reconciliation detail file of the network system according to the record to be reconciled;

dividing the account checking detail file into a plurality of sub account checking detail files according to a transaction serial number;

splitting the transaction detail file of the platform system into a plurality of sub-transaction detail files according to the transaction serial number;

and merging the sub-reconciliation documents with the same transaction serial numbers with the sub-transaction detail documents to generate a plurality of sub-reconciliation documents.

10. The multi-party reconciliation method of claim 1, wherein generating a first reconciliation error table from the plurality of sub-reconciliation files comprises:

all the sub reconciliation documents are checked in parallel to generate a check result;

and generating the first reconciliation error table according to the check result and the transaction serial number sequence.

11. A multiparty reconciliation apparatus, comprising:

the first generation module is used for generating a plurality of sub reconciliation files of the platform system and the network system according to the records to be reconciled;

the second generation module is used for generating a first reconciliation error table according to the plurality of sub reconciliation files; and

and the error checking module is used for checking the first checking error table with a second checking error table of the accounting system in error to generate a checking result.

12. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-10.

13. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1-10.

14. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 10.