CN116934508A

CN116934508A - Account checking method, account checking device, computer equipment and storage medium

Info

Publication number: CN116934508A
Application number: CN202310774136.7A
Authority: CN
Inventors: 王扬
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2023-06-27
Filing date: 2023-06-27
Publication date: 2023-10-24

Abstract

The application relates to the technical field of data processing, and particularly discloses a checking method, a checking device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: acquiring stream data generated by a service provider for transferring resources to the service provider according to a bill which is generated by a service receiver and is supposed to be received by the resources; for the same transaction event, the resource bill to be received and the running water data carry the same transaction description information; based on the transaction description information, matching the outstanding bill in the bill receivable by the resource with outstanding bill in the flow data; in the case that there are unsettled running water and unsettled bills that fail to match, identifying a bill running water combination from the unsettled running water and unsettled bills that fail to match; at least one part of the transaction description information of each of the non-reconciled running water and the non-reconciled bill contained in the bill flow combination has the same content; and sending the bill flow combination to the checking end. The method can rapidly and accurately meet the reconciliation requirement.

Description

Account checking method, account checking device, computer equipment and storage medium

Technical Field

The present application relates to the field of data processing technology, and in particular, to a reconciliation method, apparatus, computer device, storage medium and computer program product.

Background

In the conventional technology, when corresponding accounts receivables and flow data are checked, a receiver is generally required to acquire the authorization of a paying party, the flow data of the paying party is acquired and derived, and then a staff of the receiver checks the accounts receivables with the flow data one by one.

However, the checking method in the conventional technology requires manual checking by a worker, and has high labor cost and long time consumption. Especially in complex scenes, if the reconciliation data are more, the staff is required to screen out the data needing the reconciliation one by one from the derived massive running water data. In addition, because the receiver and the payer usually name the data generated by the transaction according to their habits, the staff also needs to spend time checking and eliminating the interference caused by different naming, and even if the staff derives the flow data of the payer, it is difficult to quickly and accurately correspond the flow data of the payer with the accounts receivable of the receiver, which results in more complicated checking steps of the staff and easy occurrence of checking errors.

Therefore, the checking method in the prior art has low efficiency and is easy to make mistakes, and the checking cannot be performed quickly and accurately.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a reconciliation method, apparatus, computer device, computer-readable storage medium, and computer program product that can quickly and accurately meet the reconciliation requirements.

In a first aspect, the present application provides a reconciliation method. The method comprises the following steps:

acquiring a bill which the service provider should receive for resources generated by the service receiver and stream data generated by transferring the resources to the service provider by the service receiver; for the same transaction event, the resource bill receivable and the stream data carry the same transaction description information;

matching the unreliaison running water in the running water data with the unreliaison bill in the bill receivable by the resource based on the transaction description information;

in the case that the matching failure of the outstanding running water and outstanding bill exists, identifying bill running water combination from the matching failure of the outstanding running water and outstanding bill; at least one part of the transaction description information of each of the non-reconciled running water and the non-reconciled bill contained in the bill running water combination has the same content;

and sending the bill flow combination to the checking and rechecking end so that the checking and rechecking end performs checking and rechecking processing on the bill flow combination.

In one embodiment, the process of obtaining the pipeline data includes:

under the condition that a resource transfer requirement exists between a service receiver and a service provider, acquiring a resource account provided by the service receiver; the resource account is carrier information of the resource stored in the resource storage party by the service receiver;

under the condition that a service receiver allows a service provider to inquire the stream data, a request for distributing an inquiry interface is sent to a resource storage party based on a resource account;

and acquiring the stream data generated by transferring the resources from the service receiving party to the service provider from the resource storage party based on the query interface distributed by the resource storage party.

In one embodiment, the process of generating the resource accounts receivable and the streaming data includes:

determining a transaction event of the service provider for the service recipient;

acquiring transaction description information corresponding to a transaction event;

generating a resource receivable bill for the transaction event based on the transaction description information;

transmitting the resource bill to be received carrying the transaction description information to a resource storage party of the service provider under the condition that the service receiver confirms that the resource bill to be received carrying the transaction description information;

after a service receiver transfers resources according to a resource accounts receivable one-way service provider, acquiring stream data which is generated by a resource storage party and carries transaction description information of the resource accounts receivable.

In one embodiment, the acquisition process of the unsecure pipeline includes:

acquiring stream data generated by transferring resources from a service receiving party to a service provider from a resource storage party based on a query interface distributed by the resource storage party of the service provider; each piece of running water data has a running water number;

and carrying out data filtering processing on the running water data based on the recorded running water number of the running water data with the checking completed, so as to obtain the running water without checking.

In one embodiment, the method further comprises:

if the non-reconciliation bill with the same transaction description information as the non-reconciliation running water does not exist, the non-reconciliation running water is used as the non-reconciliation running water with failed matching;

and if the non-reconciliation flowing water with the same transaction description information as the non-reconciliation bill does not exist, the non-reconciliation bill is taken as the non-reconciliation bill with failed matching.

In one embodiment, identifying a bill flowing combination from the unsecure flowing water and the unsecure bill that fail to match includes:

taking the unqualified aggregate and the unqualified bill which fail to be matched as a first reconciliation object and a second reconciliation object respectively, and determining a first resource amount of the first reconciliation object and a second resource amount of the second reconciliation object;

And under the condition that the first resource amount is equal to the second resource amount and at least one part of the same content exists in transaction description information corresponding to each of the first reconciliation object and the second reconciliation object, constructing a bill flow combination based on the first reconciliation object and the second reconciliation object.

In a second aspect, the application further provides a reconciliation device. The device comprises:

the bill flow obtaining module is used for obtaining bill receivable by the service provider for the resource generated by the service receiver and flow data generated by transferring the resource to the service provider by the service receiver; for the same transaction event, the resource bill receivable and the stream data carry the same transaction description information;

the bill flow matching module is used for matching the unreliaison flow in the flow data with the unreliaison bill in the resource bill receivable based on the transaction description information;

the bill flow combination identification module is used for identifying bill flow combination from the non-reconciled flow and the non-reconciled bill which are failed in matching under the condition that the non-reconciled flow and the non-reconciled bill which are failed in matching exist; at least one part of the transaction description information of each of the non-reconciled running water and the non-reconciled bill contained in the bill running water combination has the same content;

And the bill flow combination sending module is used for sending the bill flow combination to the checking and checking terminal so that the checking and checking terminal performs checking and checking processing on the bill flow combination.

In one embodiment, the apparatus further comprises:

the flow data acquisition module is used for acquiring a resource account provided by the service receiver under the condition that a resource transfer requirement exists between the service receiver and the service provider; the resource account is carrier information of the resource stored in the resource storage party by the service receiver; under the condition that a service receiver allows a service provider to inquire the stream data, a request for distributing an inquiry interface is sent to a resource storage party based on a resource account; and acquiring the stream data generated by transferring the resources from the service receiving party to the service provider from the resource storage party based on the query interface distributed by the resource storage party.

In one embodiment, the apparatus further comprises:

the bill flow generating module is used for determining transaction events of the service provider for the service receiver; acquiring transaction description information corresponding to a transaction event; generating a resource receivable bill for the transaction event based on the transaction description information; transmitting the resource bill to be received carrying the transaction description information to a resource storage party of the service provider under the condition that the service receiver confirms that the resource bill to be received carrying the transaction description information; after a service receiver transfers resources according to a resource accounts receivable one-way service provider, acquiring stream data which is generated by a resource storage party and carries transaction description information of the resource accounts receivable.

In one embodiment, the apparatus further comprises:

the unsettled running water obtaining module is used for obtaining running data generated by transferring resources from a service receiving party to a service provider from a resource storage party based on a query interface distributed by the resource storage party of the service provider; each piece of running water data has a running water number; and carrying out data filtering processing on the running water data based on the recorded running water number of the running water data with the checking completed, so as to obtain the running water without checking.

In one embodiment, the apparatus further comprises:

the matching failure data determining module is used for taking the non-reconciliation running water as the non-reconciliation running water with the matching failure if the non-reconciliation bill with the same transaction description information as the non-reconciliation running water does not exist; and if the non-reconciliation flowing water with the same transaction description information as the non-reconciliation bill does not exist, the non-reconciliation bill is taken as the non-reconciliation bill with failed matching.

In one embodiment, the bill-by-water combination identification module is further configured to: taking the unqualified aggregate and the unqualified bill which fail to be matched as a first reconciliation object and a second reconciliation object respectively, and determining a first resource amount of the first reconciliation object and a second resource amount of the second reconciliation object; and under the condition that the first resource amount is equal to the second resource amount and at least one part of the same content exists in transaction description information corresponding to each of the first reconciliation object and the second reconciliation object, constructing a bill flow combination based on the first reconciliation object and the second reconciliation object.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:

In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

In a fifth aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:

According to the method, the device, the computer equipment, the storage medium and the computer program product for checking account, the resource corresponding bill generated by a service provider for a service receiver is obtained, and the service receiver transfers the flow data generated by the resource, wherein the resource corresponding bill and the flow data carry the same transaction description information for the same transaction event, namely, the flow data generated for the same transaction event and the transaction description information carried in the resource corresponding bill are guaranteed to have consistency in advance, so that in the checking account process, the time consumption is not required to eliminate the interference caused by the inconsistent transaction description information due to the same transaction event, the efficiency and the accuracy of matching corresponding bill and the flow data can be improved, then, based on the transaction description information, the non-checking account in the flow data and the non-checking account in the resource corresponding bill are matched, and in the case that the matching fails, the matching fails and the non-checking account is combined, the flow data and the non-checking account are identified, and the flow data contained in the flow data and the non-checking account are at least partially matched, and the corresponding account is matched, and the flow information and the corresponding account is matched and the flow information is matched and the flow is well, and the checking is matched and the flow is well and the combined and the flow is well. In the whole process, the account checking efficiency and the accuracy are improved by improving the efficiency and the accuracy of matching accounts receivable and flow data, and in addition, the account checking efficiency can be further improved by sending account checking data with matching possibility to an account checking and checking end in a combined mode. Therefore, the check-out can be performed quickly and accurately.

Drawings

FIG. 1 is an application environment diagram of a reconciliation method in one embodiment;

FIG. 2 is a flow diagram of a reconciliation method in one embodiment;

FIG. 3 is a flow diagram of acquiring pipeline data in one embodiment;

FIG. 4 is a flow diagram of generating resource accounts receivable and pipeline data in one embodiment;

FIG. 5 is a flow diagram of obtaining a reconciliation process flow in one embodiment;

FIG. 6 is a flow diagram of a reconciliation process flow and a reconciliation bill for determining a match failure in one embodiment;

FIG. 7 is a flow diagram of identifying a bill pipeline combination in one embodiment;

FIG. 8 is a flow chart of one-to-one matching of a non-reconciled running water and a non-reconciled bill in one embodiment;

FIG. 9 is a flow diagram of one-to-many matching of a outstanding reconciliation process line and outstanding reconciliation bill in one embodiment;

FIG. 10 is a flow diagram of a many-to-one matching of a outstanding reconciliation process line and outstanding reconciliation bill in one embodiment;

FIG. 11 is a flow diagram of a many-to-many matching of outstanding flows and outstanding bills in one embodiment;

figure 12 is a block diagram of a campus management system, in one embodiment;

FIG. 13 is a block diagram of a reconciliation apparatus in one embodiment;

Fig. 14 is an internal structural diagram of a computer device in one embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

It should be noted that, the user information or the information of each party (including, but not limited to, service provider information, service provider device information, service receiver device information, resource storage party device information, etc.) and the data (including, but not limited to, data for analysis, stored data, presented data, etc. related to the reconciliation process) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to comply with the related laws and regulations and standards of the related countries and regions.

The reconciliation method provided by the embodiment of the application can be applied to a reconciliation system as shown in fig. 1. The reconciliation system includes a service provider 102, a server 1021 of the service provider, a reconciliation review terminal 1022 of the service provider, a service receiver 104, and a server 1041 of the service receiver, where the server 1021 of the service provider communicates with the server 1041 of the service receiver and the reconciliation review terminal 1022 of the service provider, respectively. The data storage system may be integrated on the server 1021 of the service provider or may be placed on the cloud or other network server. The server 1021 of the service provider may obtain authorization by communicating with the server 1041 of the service receiver, so as to obtain, based on the authorization, a resource to be received by the service provider 102 for the service receiver 104, and transfer, by the service receiver 104, aggregate data generated by the resource to the service provider 102, where, for the same transaction event, the resource to be received carries the same transaction description information with the aggregate data, then, based on the transaction description information, the server 1021 of the service provider may match the non-reconciled aggregate in the aggregate data with the non-reconciled aggregate in the resource to be received, and in the case that there is a matching failure of the non-reconciled aggregate and the non-reconciled aggregate, identify a bill aggregate combination from the matching failure of the non-reconciled aggregate and the non-reconciled aggregate, where, in the transaction description information of each of the non-reconciled aggregate and the non-reconciled aggregate contained by the bill aggregate, at least a portion of the same content exists, and finally, the server 1021 of the service provider may send the aggregate combination to the reconciled aggregate of the reconciled bills 1022 of the service provider to enable the reconciled end 1022 of the service provider to reconcile.

Wherein the service provider 102 may be, but is not limited to, various individuals or organizations that may provide services including, but not limited to, rental services, property services, and the like. The server 1021 of the service provider may be implemented as a stand-alone server or as a server cluster composed of a plurality of servers. The checking and checking end 1022 of the service provider may be a terminal corresponding to a staff responsible for checking and checking in the service provider 102, and the terminal may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and the like. The service recipient 104 may be, but is not limited to, an individual or organization receiving the service provided by the service provider 102, and a resource transfer relationship exists between the service provider 102 and the service recipient 104. The server 1041 of the service receiver may be implemented as a separate server or a server cluster composed of a plurality of servers.

In one embodiment, as shown in fig. 2, a reconciliation method is provided, which is illustrated by way of example as applied to the server of the service provider in fig. 1, and includes the following steps:

step 202, obtaining the bill which the service provider should receive for the resource generated by the service receiver and the flow data generated by the service receiver transferring the resource to the service provider; for the same transaction event, the resource accounts receivable and the streaming data carry the same transaction description information.

Wherein, the transaction descriptive information of the transaction event includes, but is not limited to: the name of the transaction event, the type of the transaction event, the amount of resources that need to be transferred to execute the transaction event, notes for the transaction event, the actual execution time of the transaction event, the names of the parties that have occurred the transaction event, and the like. The bill and stream data of the resource should be received all carry transaction description information. Each transaction event is executed to generate resource bill-receiving and flow data corresponding to the transaction information, wherein the resource bill-receiving and flow data carries transaction description information for the transaction event.

Optionally, the server of the service provider may obtain, from the data storage system of the service provider, a bill receivable by the service provider for the resource generated by the service receiver based on the name of the service provider, and the server of the service provider may further obtain, by communicating with the server of the service receiver, a query and derive an authorization of the service receiver, so as to obtain, based on the authorization, the aggregate data generated by transferring the resource from the service receiver to the service provider.

For example, in the process of acquiring the resource bill and the stream data, the service provider may further define a time period to which the acquired resource bill and stream data respectively belong in response to an operation instruction of an operator of the service provider, so as to reconcile the resource bill and stream data within a specific time period.

Step 204, matching the outstanding bill in the bill receivable by the resource with the outstanding bill in the flow data based on the transaction description information.

Optionally, after acquiring the account receivable by the service provider for the resource generated by the service receiver and transferring the flow data generated by the resource to the service provider by the service receiver, the server of the service provider may first screen out the non-reconciliation flow in the flow data and the non-reconciliation bill in the account receivable by the resource, and then match the non-reconciliation flow with the non-reconciliation bill based on the transaction description information carried by the non-reconciliation flow and the non-reconciliation bill.

For example, for the non-reconciled bill and the non-reconciled running water carrying the same transaction description information, the server of the service provider may determine a matching manner of the non-reconciled bill and the non-reconciled running water carrying the same transaction description information based on the respective numbers of the non-reconciled bill and the non-reconciled running water carrying the same transaction description information, so as to match the non-reconciled bill and the non-reconciled running water carrying the same transaction description information according to the determined matching manner. The matching mode specifically may be: one-to-one matching, one-to-many matching, many-to-one matching, many-to-many matching.

Optionally, if there is no outstanding running water and outstanding bill that fail to match, that is, all outstanding running water corresponds to outstanding bill carrying the same transaction description information, and all outstanding bill corresponds to outstanding running water carrying the same transaction description information, the server of the service provider may execute step 206 to determine that all outstanding running water and outstanding bill match successfully, otherwise, execute step 208.

Step 208, in the case that there are unsettled running water and unsettled bills that fail to match, identifying a bill running water combination from the unsettled running water and unsettled bills that fail to match; at least a part of the transaction description information of each of the unsecure running water and the unsecure bill contained in the bill flow combination is the same.

Wherein, at least one part of the same content characterization exists in the transaction description information of each of the unsent running water and the unsent bill contained in the bill running water combination: there is a correlation between the transaction description information of each of the non-reconciled running water and the non-reconciled bill in the bill flow combination, i.e. there is a possibility that the matching of the non-reconciled running water and the non-reconciled bill in the bill flow combination is successful.

Optionally, in the case that there is a non-reconciled running water and a non-reconciled bill that fail to match, the server of the service provider may identify respective transaction description information of the non-reconciled running water and the non-reconciled bill that fail to match, determine that at least a portion of non-reconciled running water and the non-reconciled bill with the same content exist in the respective transaction description information, and construct a bill running water combination based on that at least a portion of non-reconciled running water and the non-reconciled bill with the same content exist in the respective transaction description information.

Step 210, send the bill flow combination to the checking and checking terminal, so that the checking and checking terminal performs checking and checking processing on the bill flow combination.

Wherein the number of bill flow combinations is at least one group.

Optionally, the server of the service provider may send the constructed bill flow combination to the checking and checking terminal, so that the checking and checking terminal performs checking and checking processing on the bill flow combination.

For each bill flow combination, if the checking end determines that the non-checking flow and the non-checking bill in the bill flow combination are the non-checking flow and the non-checking bill corresponding to the same transaction event, the server of the service provider may confirm the non-checking flow in the bill flow combination as checked-out flow, confirm the non-checking bill in the bill flow combination as checked-out bill, and record the flow number of the non-checking flow in the bill flow combination, and the bill number of the non-checking bill in the bill flow combination, so that the non-checking flow and the non-checking bill may be screened out based on the recorded flow number and the bill number when checking next time.

For example, if there is a check-out running water that is still not successfully matched after being checked by the check-out checking terminal, the server of the service provider may identify and determine the running water number of the check-out running water, send the check-out running water to the server of the service receiver, and send a prompting message of "running water number XXXXX is abnormal to the server of the service receiver, and please perform manual check".

For example, if there is a check that the check-out bill is still not successfully matched after the check-out end checks out, the server of the service provider may identify and determine the bill number of the check-out bill first, and send a reminding message of "the resource with the bill number of XXXXX should receive the bill abnormally" to the terminal of the operator responsible for creating the check-out bill in the service provider, and please perform the manual check. When the server of the service provider stores the bill to be received created by the operator of the service provider, the server of the service provider also stores the operator work number corresponding to the bill to be received by the resource, so that when the bill to be received by the resource is abnormal, the corresponding operator can be timely determined, and the reason of the abnormal account checking is determined.

In the reconciliation method, the service provider obtains the resource corresponding bill generated by the service receiver and the flow data generated by transferring the resource to the service provider, wherein the resource corresponding bill carries the same transaction description information with the flow data for the same transaction event, namely, the flow data generated by the same transaction event and the transaction description information carried in the resource corresponding bill are guaranteed to have consistency in advance, so that in the reconciliation process, the time consumption is not required to eliminate the interference caused by inconsistent transaction description information of the same transaction event, the efficiency and the accuracy of the matched corresponding bill and the flow data can be improved, then, based on the transaction description information, the flow of the flow data and the non-reconciliation bill in the resource corresponding bill are matched, and in the case of the fact that the reconciliation bill and the non-reconciliation bill fail in matching, a reconciliation bill combination is identified, wherein at least a part of the same content exists in the respective description information of the reconciliation flow water and the non-reconciliation bill, the reconciliation bill is checked to be relatively high in the form, and the reconciliation bill is checked to be relatively and the reconciled, and the reconciliation bill is accordingly, the reconciled is sent to the reconciliation efficiency and the reconciliation bill is improved. In the whole process, the account checking efficiency and the accuracy are improved by improving the efficiency and the accuracy of matching accounts receivable and flow data, and in addition, the account checking efficiency can be further improved by sending account checking data with matching possibility to an account checking and checking end in a combined mode. Therefore, the check-out can be performed quickly and accurately.

In one embodiment, as shown in fig. 3, the process of obtaining the pipeline data includes:

step 302, obtaining a resource account provided by a service receiver under the condition that a resource transfer requirement exists between the service receiver and a service provider; the resource account is carrier information for the service recipient to store the resource in the resource store.

The resource storage party may specifically be: and the compliance certification authority is provided with resource storage qualification.

Alternatively, the server of the service provider may obtain the resource account provided by the service receiver in the case that there is a resource transfer requirement between the service receiver and the service provider, and send the resource account of the service provider to the server of the service receiver, so that the service receiver may transfer the resource from the resource account of the service receiver to the resource account of the service provider.

For example, when the server of the service provider obtains the resource account provided by the service receiver, the server of the service provider may send a request for allocating the query authority to the server of the service receiver, for example, "whether the service provider is allowed to query the resource account yyyyyyy to transfer the flow data generated by the resource to the service provider", and if the message fed back by the server of the service receiver is allowed by the message characterization of the service receiver, the message fed back by the server of the service receiver is stored for later forwarding to the resource storage of the service receiver for auditing.

Optionally, after the resource account is obtained, the server of the service receiver may execute step 304, and send an authorization request to the server of the service receiver, where the service receiver does not grant authorization (the service provider is not allowed to query the running water data in the resource account), and the server of the service receiver returns to step 304.

In step 306, in the case where the service receiver allows the service provider to query the aggregate data, a request to allocate a query interface is sent to the resource repository based on the resource account.

Optionally, in the case that the service receiver allows the service provider to query the aggregate data, the server of the service provider may forward both the resource account that the server receiver allows to query and the message that characterizes the aggregate data in the resource account that the server receiver is allowed to query to the resource repository, and send a request to allocate the query interface to the resource repository.

Step 308, obtaining, from the resource repository, the streaming data generated by the transfer of the resource from the service receiver to the service provider based on the query interface allocated by the resource repository.

Optionally, after the server of the service provider obtains the query interface for the resource account allocated by the resource storage, the server of the service provider may obtain, from the historical running data of the resource account stored in the resource storage, running data generated by transferring the resource from the service receiving direction to the service provider.

For example, if there is a missing, failed storage, or missing situation of the exported stream data within the validity period of the query interface, the server of the service receiver may query again and export the stream data generated by transferring the resource to the service provider based on the query interface for the resource account allocated by the resource storage party.

In this embodiment, the running data generated by transferring the resources from the service receiving party to the service provider can be directly and quickly obtained from the resource storage party based on the actual query requirement in a compliance range through the query interface distributed by the resource storage party, without the need for the service receiving party to download and forward the running data to the service provider by itself. On one hand, the efficiency of acquiring the flow data can be improved, so that the checking efficiency is improved, on the other hand, the flow data can be ensured not to be tampered, the authenticity of the flow data can be ensured, and the checking accuracy is improved.

In one embodiment, as shown in FIG. 4, the process of generating the resource accounts receivable and the pipeline data includes:

step 402, a transaction event is determined for a service provider for a service recipient.

Alternatively, the server of the service provider may first obtain the transaction event created by the operator of the service provider, and identify the name of another transaction party of the transaction event, and determine the service provider in the transaction time, so as to determine the transaction event of the service provider for the service receiver.

Step 404, obtaining transaction description information corresponding to the transaction event.

Optionally, the server of the service provider may identify the transaction event created by the operator of the service provider, and determine the transaction description information corresponding to the transaction event. In the process of creating a transaction event by an operator, the operator needs to input the name of the transaction event, the type of the transaction event, the amount of resources needed to be transferred for executing the transaction event, notes of the transaction event, the limit term of the transaction event, the names of both parties for generating the transaction event, and the like.

Step 406, generating a resource accounts receivable for the transaction event based on the transaction description information.

Alternatively, the server of the service provider may generate a resource bill to be received for the transaction event based on the transaction description information, such that the generated resource bill to be received carries the transaction description information.

Illustratively, the server of the service provider may send the generated resource bill to the server of the service receiver to confirm whether the service receiver has a modification opinion for the resource bill, and if so, execute step 408 to re-acquire the transaction description information for the transaction event, which is confirmed by negotiation between the service provider and the service receiver, so as to generate a new resource bill based on the new transaction description information; if there is no modification opinion, step 410 is performed.

In step 410, in case the service recipient has confirmed that the resource carrying the transaction description information should be billed, the resource carrying the transaction description information should be billed is sent to the resource repository of the service provider.

Alternatively, in the event that the service recipient has acknowledged that the resource carrying the transaction description information should be billed, the server of the service provider may send the resource carrying the transaction description information to the resource store of the service provider.

Step 412, after the service receiver transfers the resource according to the resource accounts receivable one-way service provider, obtaining the stream data carrying the transaction description information of the resource accounts receivable generated by the resource storage.

Optionally, after the service receiver transfers the resource from the resource account of the service receiver to the resource account of the service provider according to the resource bill to be received, that is, after the service receiver has executed the transaction event corresponding to the resource bill to be received, the resource storage party generates the stream data carrying the transaction description information of the resource bill to be received, so that the server of the service provider can acquire the stream data based on the query interface provided by the resource storage party.

In this embodiment, by determining transaction description information corresponding to a transaction event and forwarding a resource bill to be received carrying the transaction description information to a resource storage party, it is possible to ensure that the transaction description information in the aggregate data for the transaction event generated by the resource storage party is consistent with the transaction description information in the resource bill to be received corresponding to the same transaction event, that is, it is possible to ensure in advance that the aggregate data generated for the same transaction event and the transaction description information carried in the resource bill to be received have consistency, so that when checking accounts later, it is unnecessary to take time to eliminate interference caused by inconsistent transaction description information existing in the same transaction event, and efficiency and accuracy of matching the bill to be received and the aggregate data can be improved, thereby improving efficiency and accuracy of checking accounts.

In one embodiment, as shown in fig. 5, the acquisition process of the unpaid running water includes:

step 502, acquiring stream data generated by transferring resources from a service receiving party to a service provider from a resource storage party based on a query interface distributed by the resource storage party of the service provider; each of the stream data has a respective stream number.

Optionally, the server of the service provider may obtain, from the resource storage, the aggregate data generated by transferring the resources from the service receiving party to the service provider in the resource account based on the query interface allocated by the resource storage of the service provider and the resource account corresponding to the query interface.

Step 504, based on the recorded serial number of the stream data with the checking completed, performing data filtering processing on the stream data to obtain a stream with no checking.

Optionally, the server of the service provider may first identify the serial number of each piece of the acquired serial data, determine the serial number of each piece of the serial data, and obtain, from the data storage system, the serial number of the serial data with the checking completed recorded in the previous checking process, and perform data filtering processing on the serial data based on the serial number of the serial data with the checking completed and the serial number of each piece of the acquired serial data, to obtain the serial data without checking.

In this embodiment, the obtained running data is filtered through the recorded running number of the running data after checking, so that it is not necessary to manually compare whether the running data is the running data without checking one by one, repeated checking of the checked running data with time consumption can be avoided, and the checking efficiency is facilitated.

In one embodiment, in performing step 204, in matching the outstanding data in the aggregate data with the outstanding bill in the resource accounts receivable based on the transaction description information, the server of the service provider may determine the outstanding aggregate and outstanding bill that failed to match through the steps as shown in fig. 6:

for each outstanding flow, if there is an outstanding bill with the same transaction description information as the outstanding flow, step 2041 is performed to determine that the outstanding flow has completed checking. If there is no outstanding bill with the same transaction description information as the outstanding running water, step 2042 is executed to take the outstanding running water as the outstanding running water with failed matching.

For each outstanding bill, if there is an outstanding bill having the same transaction description information as the outstanding bill, step 2043 is performed to determine that the outstanding bill has completed checking. If there is no outstanding flow with the same transaction description information as the outstanding bill, step 2044 is executed to take the outstanding bill as the outstanding bill that fails to match.

In this embodiment, by determining the non-reconciliation running water and the non-reconciliation bill which fail to match, the non-reconciliation running water and the non-reconciliation bill which fail to match can be forwarded to the reconciliation review terminal for review, so that the reconciliation accuracy can be improved.

In one embodiment, as shown in fig. 7, identifying a bill flow combination from the unsecure flow and the unsecure bill that fail to match includes:

step 702, taking the unset running water and the unset bill which fail to be matched as a first reconciliation object and a second reconciliation object respectively, and determining a first resource amount of the first reconciliation object and a second resource amount of the second reconciliation object.

The method comprises the steps that in transaction description information carried by non-reconciliation running water, the first resource quantity of a first reconciliation object represents the resource quantity which needs to be transferred for a transaction event corresponding to the transaction description information, and when the number of the first reconciliation objects is multiple, the first resource quantity of the first reconciliation object represents the total resource quantity which needs to be transferred for the transaction event corresponding to the multiple first reconciliation objects. And in the transaction description information carried by the non-reconciliation bill, the second resource quantity of the second reconciliation object represents the resource quantity which needs to be transferred for the transaction event corresponding to the transaction description information, and when the number of the second reconciliation objects is multiple, the second resource quantity of the second reconciliation object represents the total resource quantity which needs to be transferred for the transaction event corresponding to the multiple second reconciliation objects.

Optionally, the server of the service provider may respectively use the unqualified aggregate and the unqualified bill that fail to be matched as the first reconciliation object and the second reconciliation object, and respectively identify transaction description information carried by the first reconciliation object and the second reconciliation object, so as to determine a first resource amount of the first reconciliation object and a second resource amount of the second reconciliation object.

Step 704, when the first resource amount is equal to the second resource amount and at least a part of the same content exists in the transaction description information corresponding to each of the first reconciliation object and the second reconciliation object, constructing a bill flow combination based on the first reconciliation object and the second reconciliation object.

The number of the first reconciliation objects and the number of the second reconciliation objects may be at least one.

Optionally, if the first resource amount of the first reconciliation object is equal to the second resource amount of the second reconciliation object, and at least a portion of the same content exists in the transaction description information corresponding to each of the first reconciliation object and the second reconciliation object, the server of the service provider may determine that there is a match possibility for the first reconciliation object and the second reconciliation object, thereby constructing the bill running water combination based on the first reconciliation object and the second reconciliation object.

Illustratively, the description will be given by taking as an example the uncork flow X1 (carrying the transaction description information r1, r1 with the amount of the resources a), the uncork flow X2 (carrying the transaction description information r1, r1 with the amount of the resources a), and the uncork bill Y (carrying the transaction description information r2, r2 with the amount of the resources B) with the failure of the matching: if 2a=b is satisfied and at least a portion of the same content exists in r1 and r2, the server of the service provider may determine that there is a many-to-one match between X1 and X2 and Y, and may further use X1 and X2 together as a first reconciliation object in the billing pipeline combination and Y as a second reconciliation object in the billing pipeline combination.

Illustratively, description will be given of a reconciliation-failure flow X1 (carrying the transaction description information r1, r1 with the amount of the resources being a), a reconciliation-failure flow X2 (carrying the transaction description information s1, s1 with the amount of the resources being B), a reconciliation-failure bill Y1 (carrying the transaction description information r2, r2 with the amount of the resources being a), and a reconciliation-failure bill Y2 (carrying the transaction description information s2, s2 with the amount of the resources being B) with the failure of the matching. If at least a part of the same content exists in r1 and r2, the server of the service provider can determine that the possibility of one-to-one matching exists between X1 and Y1, so that a bill flow combination is built based on X1 and Y1; if at least a portion of the same content exists in s1 and s2, the server of the service provider may determine that there is a one-to-one match between X2 and Y2, thereby constructing a billing pipeline combination based on X2 and Y2.

In this embodiment, at least a part of the same content exists in the respective transaction description information, and the unset running water and the unset bill which are failed in matching and correspond to the same resource amount are used as the running water and the unset bill which are failed in matching and correspond to the possible successful matching are used as the combination, and the combination is sent to the checking and checking terminal, namely, the unset running water and the unset bill which are failed in matching are fed back to the checking and checking terminal in an intelligent recommendation mode, so that the checking workload of the checking and checking terminal in the early stage can be reduced, the checking and checking efficiency of the checking and checking terminal can be improved, and the overall checking efficiency is further improved.

In one embodiment, the server of the service provider may determine the service receiver needing to be checked in response to an operation instruction issued by an operator of the service provider, and screen the running data and the resource to be billed according to one-to-one, one-to-many, many-to-one, and many-to-many matching, and may display the number of running data successfully matched and the number of running data failed matched to the operator of the service provider.

Taking an example of checking the service provider Z and the service receiver a, if the service provider Z provides the rental service to the service receiver a, and checking the flow data and the resource bill to be received related to the rental service, as shown in fig. 8, a schematic diagram of one-to-one matching of the unpaid running water and the unpaid bill carrying the same transaction description information is provided. In fig. 8, the number of the successfully matched stream data and the number of the resource accounts receivable are 1. The same transaction matching information carried in the successfully matched aggregate data, resource accounts receivable in fig. 8 includes, but is not limited to: the same aggregate resource amount, service offering content, transaction event name, month to which transaction time belongs, and so forth.

Taking an example of checking the service provider Z and the service receiver a, if the service provider Z provides the rental service to the service receiver a and checks the flow data and the resource bill to be received related to the rental service, as shown in fig. 9, a schematic diagram of one-to-many matching of the unpaid running water and the unpaid bill carrying the same transaction description information is provided. In fig. 9, the number of the successfully matched stream data is 1, and the number of the resource billable is a plurality. The same transaction matching information carried in the successfully matched aggregate data, resource accounts receivable in fig. 9 includes, but is not limited to: the same aggregate resource amount, service offering content, transaction event name, month to which transaction time belongs, and so forth.

Taking an example of checking the service provider Z and the service receiver a, if the service provider Z provides the rental service to the service receiver a and checks the flow data and the resource bill to be received related to the rental service, as shown in fig. 10, a schematic diagram of matching the unpaid running water and the unpaid bill carrying the same transaction description information in many-to-one manner is provided. The number of the successfully matched stream data in fig. 10 is a plurality of the stream data, and the number of the resource billable is 1. The same transaction matching information carried in the successfully matched aggregate data, resource accounts receivable in fig. 10 includes, but is not limited to: the same aggregate resource amount, service offering content, transaction event name, month to which transaction time belongs, and so forth.

Taking an example of checking the service provider Z and the service receiver a, if the service provider Z provides the rental service to the service receiver a and checks the flow data and the resource bill to be received related to the rental service, as shown in fig. 11, a schematic diagram of many-to-many matching of the unpaid running water and the unpaid bill carrying the same transaction description information is provided. The number of the successfully matched stream data in fig. 11 is a plurality of the stream data, and the number of the resource billable is a plurality of the stream data. The same transaction matching information carried in the successfully matched aggregate data, resource accounts receivable in fig. 11 includes, but is not limited to: the same aggregate resource amount, service offering content, transaction event name, month to which transaction time belongs, and so forth.

The server of the service provider may automatically confirm that the successfully matched aggregate data and the resource should be billed, or may respond to the operation that the operator of the service provider clicks the "confirm reconciled" option in fig. 8 to 11, to confirm that the successfully matched aggregate data and the resource should be billed.

The server of the service provider may automatically send the running data of failed matching and the bill running combination of the bill to be received by the resource to the checking end, or may respond to the operation that the operator of the service provider clicks the "manual matching" option in fig. 8 to 11 to combine the running data of failed matching and the bill running combination of the bill to be received by the resource to the checking end.

In this embodiment, according to the actual account checking situation, different modes of flexible matching can be performed on the flow data of the account which is not checked and the accounts receivable of the resource which is not checked, so that the account checking efficiency can be improved.

In one embodiment, taking the service provider as a campus and the service receiver as a person or organization renting the assets in the campus as an example, the above-mentioned reconciliation method can be applied to a campus management cloud platform to assist the campus in completing daily reconciliation business. As shown in fig. 12, a schematic block diagram of a campus management cloud platform is provided, where the campus management cloud platform mainly includes: asset management module, transaction management module, lease management module, user management module, and cockpit management module, wherein:

the asset management module can realize the functions of area management, asset ownership management, current unit management, history unit management and the like. The asset management module may be used to manage assets in various areas of the campus, including but not limited to, the cell building within the campus for providing rental services. If the park needs to combine and manage a plurality of unit buildings, each unit building before combining is a history unit, and the unit building after combining is a current unit.

The transaction management module can realize the functions of transaction event management, temporary transaction event management, bill receivable management, reconciliation and the like. The transaction event management function may be used to configure the campus to service recipients' common, periodic transaction events, and transaction descriptive information of the transaction events, among other things. Temporary transaction event management may be used to configure the campus for some sporadic, aperiodic transaction events, as well as transaction description information of the transaction events for the service recipient. The bill due management function may be used to manage resource bill due generated based on the transaction event, and transaction description information of the transaction event. The reconciliation function may be used to effect a reconciliation between the resources of the campus and the aggregate data of the service receiver based on the authorization of the service receiver.

And the lease management module can realize functions of lease management, contract management, lease audit management and the like, and is mainly used for auditing lease qualification of a service receiver and lease contract between a management park and the service receiver.

The user management module can realize the functions of mechanism management, department management, user management, authorization management and the like, can be used for managing the operation authorities of various users accessing the park management cloud platform, and can manage the operation authorities of different users in the park management cloud platform in a separated mechanism and a separated department.

The cockpit management module can realize the functions of index overview, asset flash report, operation analysis, operation early warning, park map guidance and the like, can be used for analyzing and displaying park operation data and asset data and monitoring and early warning the park operation data, for example, analyzing and displaying the revenue data of services provided by the park. The cockpit management module can also display map guidance of each building in the park to the user accessing the park management cloud platform.

As shown in fig. 12, the service receiver may access the campus management cloud platform through the applet port of the campus management cloud platform based on the respective terminals, and may send a transaction request to the campus management cloud platform based on the applet port of the campus management cloud platform, and view the transaction result at the applet port. The staff of the park can log in the park management cloud platform from the webpage end to operate based on the terminals of the staff.

By taking the above checking method as an example, the operator of the park can uniformly and clearly define the transaction event of the park for the service receiver and the transaction description information of the transaction event based on the transaction event management function in the park management cloud platform or the temporary transaction event management function, so that the park management cloud platform does not need to consume time to eliminate the interference caused by inconsistent transaction description information of the same transaction event when checking the account based on the checking method, and the efficiency and the accuracy of matching the to-be-checked bill and the flow data can be improved, thereby improving the checking efficiency and the accuracy.

Further, as shown in fig. 12, the campus management cloud platform may also interact with the resource storage party of the service receiver to obtain authorization of the resource storage party, so as to obtain the flow data generated when the service receiver transfers the resource to the campus for subsequent reconciliation. After the flow data of the service receiver is obtained, the campus management cloud platform can derive the resource accounts receivable of the non-reconciliation based on the account receivable management function, and intelligently match the flow data of the non-reconciliation with the resource accounts receivable of the non-reconciliation, such as one-to-one matching, one-to-many matching, many-to-one matching and many-to-many matching.

Then, the park management cloud platform can count the unqualified running water and the unqualified bills which are failed to be matched, identify the bill running water combination from the unqualified running water and the unqualified bills which are failed to be matched according to the checking method, send the bill running water combination to the checking and checking end of the park for checking, so that the checking and checking efficiency of the checking and checking end is improved, and the overall checking efficiency is further improved.

According to the method for checking accounts, the checking account business of the park management cloud platform is executed, the transaction description information of each transaction event can be uniformly and clearly defined in the park management cloud platform in advance, the efficiency and the accuracy of follow-up matching of running data and accounts receivable by resources are improved, the efficiency and the accuracy of checking accounts of the park are further improved, and the checking account efficiency can be further improved by identifying the running combination of the bills from the unqualified running water and the unqualified checking account and sending the running combination of the bills to the checking account checking end of the park for checking. Therefore, the method for checking accounts is applied to the checking accounts of the parks, and the requirements of checking accounts of the parks can be met rapidly and accurately.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a checking device for realizing the checking method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in one or more embodiments of the reconciliation device provided below may be referred to the limitation of the reconciliation method hereinabove, and will not be repeated here.

In one embodiment, as shown in fig. 13, there is provided a reconciliation apparatus comprising: a billing pipeline acquisition module 1302, a billing pipeline matching module 1304, a billing pipeline combination identification module 1306, and a billing pipeline combination transmission module 1308, wherein:

In the reconciliation device, the service provider obtains the resource corresponding bill generated by the service receiver and the flow data generated by transferring the resource to the service provider, wherein the resource corresponding bill carries the same transaction description information with the flow data for the same transaction event, namely, the flow data generated by the same transaction event and the transaction description information carried in the resource corresponding bill are guaranteed to have consistency in advance, so that in the reconciliation process, the time consumption is not required to eliminate the interference caused by inconsistent transaction description information of the same transaction event, the efficiency and the accuracy of the matched corresponding bill and the flow data can be improved, then, based on the transaction description information, the flow of the flow data and the non-reconciliation bill in the resource corresponding bill are matched, and in the case of the fact that the reconciliation bill and the non-reconciliation bill fail in matching, a reconciliation bill combination is identified, wherein at least a part of the same content exists in the respective description information of the reconciliation flow water and the non-reconciliation bill, the reconciliation bill is checked to be relatively high in the form, and the reconciliation bill is correspondingly checked to be sent to the reconciliation end, and the reconciliation efficiency is improved. In the whole process, the account checking efficiency and the accuracy are improved by improving the efficiency and the accuracy of matching accounts receivable and flow data, and in addition, the account checking efficiency can be further improved by sending account checking data with matching possibility to an account checking and checking end in a combined mode. Therefore, the check-out can be performed quickly and accurately.

In one embodiment, the apparatus further comprises: the flow data acquisition module is used for acquiring a resource account provided by the service receiver under the condition that a resource transfer requirement exists between the service receiver and the service provider; the resource account is carrier information of the resource stored in the resource storage party by the service receiver; under the condition that a service receiver allows a service provider to inquire the stream data, a request for distributing an inquiry interface is sent to a resource storage party based on a resource account; and acquiring the stream data generated by transferring the resources from the service receiving party to the service provider from the resource storage party based on the query interface distributed by the resource storage party.

In one embodiment, the apparatus further comprises: the bill flow generating module is used for determining transaction events of the service provider for the service receiver; acquiring transaction description information corresponding to a transaction event; generating a resource receivable bill for the transaction event based on the transaction description information; transmitting the resource bill to be received carrying the transaction description information to a resource storage party of the service provider under the condition that the service receiver confirms that the resource bill to be received carrying the transaction description information; after a service receiver transfers resources according to a resource accounts receivable one-way service provider, acquiring stream data which is generated by a resource storage party and carries transaction description information of the resource accounts receivable.

In one embodiment, the apparatus further comprises: the unsettled running water obtaining module is used for obtaining running data generated by transferring resources from a service receiving party to a service provider from a resource storage party based on a query interface distributed by the resource storage party of the service provider; each piece of running water data has a running water number; and carrying out data filtering processing on the running water data based on the recorded running water number of the running water data with the checking completed, so as to obtain the running water without checking.

In one embodiment, the apparatus further comprises: the matching failure data determining module is used for taking the non-reconciliation running water as the non-reconciliation running water with the matching failure if the non-reconciliation bill with the same transaction description information as the non-reconciliation running water does not exist; and if the non-reconciliation flowing water with the same transaction description information as the non-reconciliation bill does not exist, the non-reconciliation bill is taken as the non-reconciliation bill with failed matching.

The various modules in the reconciliation apparatus described above may be implemented in whole or in part in software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 14. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is for storing reconciliation data. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a reconciliation method.

It will be appreciated by those skilled in the art that the structure shown in fig. 14 is merely a block diagram of a portion of the structure associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements are applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, implements the steps of the method embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims

1. A method of reconciliation, the method comprising:

acquiring a bill which a service provider should receive for resources generated by a service receiver and stream data generated by transferring the resources to the service provider by the service receiver; for the same transaction event, the resource bill to be received and the flow data carry the same transaction description information;

Matching the unpaid running water in the running water data with the unpaid bill in the resource bill receivable based on the transaction description information;

identifying bill flow combination from the non-reconciled running water and the non-reconciled bill which fail to match under the condition that the non-reconciled running water and the non-reconciled bill which fail to match exist; at least one part of the transaction description information of each of the non-reconciled running water and the non-reconciled bill contained in the bill running water combination has the same content;

and sending the bill flow combination to a checking and checking terminal so that the checking and checking terminal performs checking and checking processing on the bill flow combination.

2. The method of claim 1, wherein the process of obtaining the pipeline data comprises:

acquiring a resource account provided by the service receiver under the condition that a resource transfer requirement exists between the service receiver and the service provider; the resource account is carrier information of the resource stored in the resource storage party by the service receiver;

sending a request to allocate a query interface to the resource repository based on the resource account if the service recipient allows the service provider to query the aggregate data;

And acquiring the flow data generated by transferring resources from the service receiving party to the service provider from the resource storage party based on the query interface distributed by the resource storage party.

3. The method of claim 2, wherein the process of billing the resource and generating the pipeline data comprises:

determining a transaction event for the service provider for the service recipient;

acquiring transaction description information corresponding to the transaction event;

generating a resource accounts receivable for the transaction event based on the transaction description information;

transmitting the resource bill to be received carrying the transaction description information to a resource storage side of the service provider under the condition that the service receiver confirms that the resource bill to be received carrying the transaction description information;

and after the service receiver transfers the resources to the service provider according to the resource accounts receivable, acquiring stream data which is generated by the resource storage party and carries transaction description information of the resource accounts receivable.

4. The method of claim 2, wherein the acquiring of the unpaid running water includes:

acquiring stream data generated by transferring resources from the service receiving party to the service provider from the resource storage party based on a query interface distributed by the resource storage party of the service provider; each piece of the flow data is provided with a flow number;

5. The method according to claim 1, wherein the method further comprises:

if the non-reconciliation bill with the same transaction description information as the non-reconciliation running water does not exist, taking the non-reconciliation running water as the non-reconciliation running water with failed matching;

and if the non-reconciliation flowing water with the same transaction description information as the non-reconciliation bill does not exist, the non-reconciliation bill is used as the non-reconciliation bill with failed matching.

6. The method of claim 1, wherein identifying a bill flow combination from the unsecure flow and the unsecure bill that failed to match comprises:

taking the unqualified running water and the unqualified bill which fail to be matched as a first reconciliation object and a second reconciliation object respectively, and determining a first resource amount of the first reconciliation object and a second resource amount of the second reconciliation object;

7. A reconciliation apparatus, the apparatus comprising:

the bill flow obtaining module is used for obtaining bill receivable by a service provider for resources generated by a service receiver and flow data generated by transferring the resources to the service provider by the service receiver; for the same transaction event, the resource bill to be received and the flow data carry the same transaction description information;

the bill flow matching module is used for matching the non-reconciliation flow in the flow data with the non-reconciliation bill in the resource accounts receivable based on the transaction description information;

the bill flow combination identification module is used for identifying bill flow combination from the non-reconciled flow and the non-reconciled bill which fail to match under the condition that the non-reconciled flow and the non-reconciled bill which fail to match exist; at least one part of the transaction description information of each of the non-reconciled running water and the non-reconciled bill contained in the bill running water combination has the same content;

and the bill flow combination sending module is used for sending the bill flow combination to a checking and checking terminal so that the checking and checking terminal performs checking and checking processing on the bill flow combination.

8. The apparatus of claim 7, wherein the apparatus further comprises:

the stream data acquisition module is used for acquiring a resource account provided by the service receiver under the condition that a resource transfer requirement exists between the service receiver and the service provider; the resource account is carrier information of the resource stored in the resource storage party by the service receiver; sending a request to allocate a query interface to the resource repository based on the resource account if the service recipient allows the service provider to query the aggregate data; and acquiring the flow data generated by transferring resources from the service receiving party to the service provider from the resource storage party based on the query interface distributed by the resource storage party.

9. The apparatus of claim 8, wherein the apparatus further comprises:

a bill flow generating module for determining transaction events of the service provider for the service receiver; acquiring transaction description information corresponding to the transaction event; generating a resource accounts receivable for the transaction event based on the transaction description information; transmitting the resource bill to be received carrying the transaction description information to a resource storage side of the service provider under the condition that the service receiver confirms that the resource bill to be received carrying the transaction description information; and after the service receiver transfers the resources to the service provider according to the resource accounts receivable, acquiring stream data which is generated by the resource storage party and carries transaction description information of the resource accounts receivable.

10. The apparatus of claim 8, wherein the apparatus further comprises:

the unsettled running water obtaining module is used for obtaining running data generated by transferring resources from the service receiving party to the service provider from the resource storage party based on a query interface distributed by the resource storage party of the service provider; each piece of the flow data is provided with a flow number; and carrying out data filtering processing on the running water data based on the recorded running water number of the running water data with the checking completed, so as to obtain the running water without checking.

11. The apparatus of claim 7, wherein the apparatus further comprises:

the matching failure data determining module is used for taking the non-reconciliation running water as the non-reconciliation running water with the matching failure if the non-reconciliation bill with the same transaction description information as the non-reconciliation running water does not exist; and if the non-reconciliation flowing water with the same transaction description information as the non-reconciliation bill does not exist, the non-reconciliation bill is used as the non-reconciliation bill with failed matching.

12. The apparatus of claim 7, wherein the billing pipeline combination identification module is further configured to: taking the unqualified running water and the unqualified bill which fail to be matched as a first reconciliation object and a second reconciliation object respectively, and determining a first resource amount of the first reconciliation object and a second resource amount of the second reconciliation object; and under the condition that the first resource amount is equal to the second resource amount and at least one part of the same content exists in transaction description information corresponding to each of the first reconciliation object and the second reconciliation object, constructing a bill flow combination based on the first reconciliation object and the second reconciliation object.

13. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.

14. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.

15. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.