CN115063242A

CN115063242A - Account checking method, account checking device, account checking equipment, account checking medium and program product for business transaction

Info

Publication number: CN115063242A
Application number: CN202210732096.5A
Authority: CN
Inventors: 李泽云; 王斌; 王旭超; 王毅
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2022-06-17
Filing date: 2022-06-17
Publication date: 2022-09-16

Abstract

The utility model provides a reconciliation method, a reconciliation device, a reconciliation medium and a program product for business transaction, which relate to the technical field of data processing and can be applied to the technical field of finance, wherein the reconciliation method comprises the following steps: acquiring transaction data to be checked; in response to the transaction data to be checked out is transaction data of real-time check out, checking out the transaction data to be checked out based on a pre-configured key field, wherein the key field is used for representing key transaction information in the transaction data to be checked out; in response to the account checking transaction data being daily and final account checking transaction data, performing account checking on the account checking transaction data based on a full-amount field of the account checking transaction data; and the transaction data of the daily final account checking comprises the transaction data of the real-time account checking. The account checking method divides the account checking into real-time account checking and daily final account checking, greatly shortens the account checking time, improves the timeliness of the account checking, and improves the accuracy of the account checking through a double account checking mechanism.

Description

Account checking method, account checking device, account checking equipment, account checking medium and program product for business transaction

Technical Field

The disclosure relates to the technical field of data processing, can be applied to the field of financial science and technology, and particularly relates to a reconciliation method, device, equipment, medium and program product for business transactions.

Background

With the gradual expansion of the escrow business, the business interaction between the escrow system and the industrial and silver financing and subsidiary companies is increased greatly, so that the requirements on the safety and the accuracy of the transaction are higher and higher. In order to ensure the security and accuracy of the lecture, account checking needs to be performed on transaction data generated by business transactions.

In the prior art, account checking generally adopts a manual account checking mode, and in the process of implementing the concept of the present disclosure, the applicant finds that the existing account checking technology at least includes the following defects: the correctness of the transaction depends on manual review, so that the account checking efficiency is low and the time consumption is high. With the expansion of services, manual review has gradually failed to meet the timeliness of supervision. Partial bottom layer transaction data are not displayed on a foreground interface, the data are relatively complex to obtain manually, and the risk of data leakage may exist.

BRIEF SUMMARY OF THE PRESENT DISCLOSURE

In order to at least partially solve the technical problem, an aspect of the present disclosure provides a reconciliation method for a business transaction, including: acquiring transaction data to be checked; in response to the transaction data to be checked out is transaction data of real-time check out, checking out the transaction data to be checked out based on a pre-configured key field, wherein the key field is used for representing key transaction information in the transaction data to be checked out; in response to the account checking transaction data being daily and final account checking transaction data, performing account checking on the account checking transaction data based on a full-amount field of the account checking transaction data; and the transaction data of the daily final account checking comprises the transaction data of the real-time account checking.

According to the embodiment of the disclosure, the reconciliation method further comprises the following steps: configuring the key field, including: extracting all first service types contained in the service transaction; setting a corresponding key field for each first service type; and storing the key field corresponding to each first service type in a configuration table by taking the first interface identifier corresponding to the first service type as an index.

According to an embodiment of the present disclosure, the reconciling the transaction data to be reconciled based on a pre-configured key field in response to the transaction data to be reconciled being the transaction data for real-time reconciliation specifically includes: extracting a second interface identifier corresponding to a second service type of the transaction data of the real-time account checking; matching the first interface identifier which is the same as the second interface identifier in the configuration table; inquiring corresponding keywords according to the first interface identification obtained by matching; and checking the transaction data of the real-time account according to the corresponding keywords obtained by the query.

According to an embodiment of the present disclosure, the reconciling the to-be-reconciled transaction data based on the full-amount field of the to-be-reconciled transaction data in response to the to-be-reconciled transaction data being daily-to-reconciled transaction data specifically includes: and comparing the to-be-checked transaction data acquired in the daytime with the full-amount field contained in the to-be-checked transaction data acquired in the nighttime.

According to the embodiment of the disclosure, the reconciliation method further comprises the following steps: and sending alarm information to a provider of the transaction data to be checked under the condition that the check-out is not passed, wherein the alarm information is used for reminding the provider of the transaction data to be checked to perform manual check-out on the transaction data to be checked.

According to the embodiment of the disclosure, the condition that the account is not passed comprises that information contained in the transaction data to be checked is inconsistent or data provided by the provider is missing; under the condition that the information contained in the transaction data to be checked is inconsistent, directly sending alarm information to the provider; and sending reminding information for re-providing the to-be-checked transaction data to the provider under the condition that the to-be-checked transaction data provided by the provider is missing, and sending warning information to the provider under the condition that the re-provided to-be-checked transaction data is missing.

According to an embodiment of the present disclosure, the acquiring the transaction data to be reconciled includes: and acquiring the transaction data to be checked in a message format through a java program.

According to an embodiment of the present disclosure, the acquiring the transaction data to be reconciled includes: and acquiring the transaction data to be reconciled in a point-to-point transmission mode based on a general data transmission platform.

Another aspect of the present disclosure provides an account checking device for business transaction, including: the acquisition module is used for acquiring the transaction data to be checked; the first reconciliation module is used for reconciling the transaction data to be reconciled based on a pre-configured key field in response to the transaction data to be reconciled being real-time reconciliation transaction data, wherein the key field is used for representing key transaction information in the transaction data to be reconciled; the second account checking module is used for responding to the transaction data to be checked for account daily and final account checking, and checking the transaction data to be checked for account based on the full-amount field of the transaction data to be checked for account; and the transaction data of the daily final account checking comprises the transaction data of the real-time account checking.

Another aspect of the present disclosure provides an electronic device including: one or more processors; 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 implement the method as described above.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.

Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.

According to the reconciliation method, the reconciliation device, the reconciliation equipment, the reconciliation medium and the reconciliation program product of the business transaction provided by the embodiment of the disclosure, at least the following technical effects are achieved:

the account checking is divided into real-time account checking and daily final account checking, the most key transaction information is checked through the real-time account checking, the account checking time is greatly shortened, the timeliness of the account checking is improved, the account checking is performed again through the full amount of data contained in the daily final account checking transaction data, the daily final account checking transaction data comprise the transaction data of the real-time account checking, and the accuracy of the account checking is improved through the dual account checking and auditing mechanism.

Further, the key words corresponding to the key information of the real-time account checking are stored and indexed based on the interface identification corresponding to the service type contained in the service transaction data, when the service type of the service transaction changes (such as increases or decreases), the corresponding message can be generated only by adding or deleting the interface identification of the service type and the corresponding key field directly in the configuration table, the original logic does not need to be changed, and the key configuration is not mutually invaded with other interfaces, so that the one-click configuration is realized, and the account checking range can be flexibly expanded.

Furthermore, when the account checking is inconsistent, warning information is sent to the provider of the transaction data to be checked in time to remind the provider of manual account checking, and the accuracy and the timeliness of the account checking are further improved.

Drawings

Fig. 1 schematically illustrates a system architecture 100 of a reconciliation method and system for business transactions according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a reconciliation method for a business transaction according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow chart of a reconciliation method for a business transaction according to another embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow diagram of a real-time reconciliation method according to an embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow chart of a day end reconciliation method according to an embodiment of the present disclosure;

FIG. 6 schematically shows a flow chart of a business transaction reconciliation method according to yet another embodiment of the present disclosure;

FIG. 7 schematically illustrates a block diagram of a reconciliation apparatus for a business transaction according to an embodiment of the present disclosure;

FIG. 8 schematically illustrates a block diagram of a reconciliation apparatus for a business transaction according to another embodiment of the present disclosure;

FIG. 9 schematically illustrates a block diagram of a reconciliation apparatus for a business transaction according to yet another embodiment of the present disclosure;

FIG. 10 schematically illustrates a block diagram of a configuration module according to an embodiment of the present disclosure;

FIG. 11 schematically illustrates a block diagram of a first reconciliation module according to an embodiment of the present disclosure;

FIG. 12 schematically illustrates a block diagram of an alarm unit according to an embodiment of the present disclosure;

fig. 13 schematically illustrates a block diagram of an electronic device suitable for implementing the above-described method according to an embodiment of the present 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 illustrative only 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 disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not 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 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 is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have 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.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have 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.).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.

In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure, application and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations, necessary confidentiality measures are taken, and the customs of the public order is not violated.

In the technical scheme of the disclosure, before the personal information of the user is acquired or collected, the authorization or the consent of the user is acquired.

For the technical problems existing in the related art, the embodiment of the present disclosure provides a reconciliation method for business transactions, including: and taking the transaction data to be reconciled. And in response to the account checking transaction data being the transaction data of real-time account checking, performing account checking on the account checking transaction data based on a pre-configured key field, wherein the key field is used for representing key transaction information in the account checking transaction data. And in response to the account checking transaction data being the daily final account checking transaction data, performing account checking on the account checking transaction data based on the full-size field of the account checking transaction data. The transaction data of daily final account checking comprises transaction data of real-time account checking.

Fig. 1 schematically illustrates a system architecture 100 of a reconciliation method and system for business transactions according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, a system architecture 100 according to this embodiment may include a storage module 101, a network 102, and a server 103. Network 102 is used to provide a communication link between storage module 101 and server 103.

The storage module 101 may include, for example, a Read Only Memory (ROM), a Random Access Memory (RAM), a database, a distributed cache, or the like, and the storage module 101 is used for storing transaction data generated by a business transaction. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others. The wired mode may be, for example, a connection using a cable and any one of the following interfaces: the wireless communication system comprises a fiber channel, an Infrared interface, a D-Type data interface, a serial interface, a USB Type-C interface or a Dock interface, and the wireless communication mode can be connected by adopting a wireless communication mode, wherein the wireless communication mode can adopt any one of a plurality of wireless technology standards such as Bluetooth, Wi-Fi, infra, ZigBee and the like. The server 103 is configured to obtain the business transaction data stored in the storage module 101 through the network 102, match the transaction data that needs to be reconciled in real time by using preset keywords, so as to quickly obtain a current reconciliation result, and compare, for all transaction data of the current day, each transaction data obtained during the day with the total transaction data obtained during the night through the library, so as to obtain an overall reconciliation result.

It should be noted that the reconciliation method for business transaction provided by the embodiment of the present disclosure may be executed by the server 103. Accordingly, the reconciliation device for business transaction provided by the embodiment of the present disclosure may be disposed in the server 103. Alternatively, the reconciliation method for the business transaction provided by the embodiment of the present disclosure may also be performed by a server or a server cluster that is different from the server 103 and can communicate with the storage module 101 and/or the server 103. Correspondingly, the reconciliation device for the business transaction provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster that is different from the server 103 and can communicate with the storage module 101 and/or the server 103. Alternatively, the reconciliation method for business transaction provided by the embodiment of the present disclosure may also be partially executed by the server 103 and partially executed by the storage module 101. Correspondingly, the reconciliation device for the business transaction provided by the embodiment of the present disclosure may also be partially disposed in the server 103 and partially disposed in the storage module 101.

It should be understood that the number of storage modules, networks, and servers in FIG. 1 are illustrative only. There may be any number of storage modules, networks, and servers, as desired for an implementation.

The reconciliation method for the business transaction provided by the embodiment of the disclosure can be applied to the field of financial science and technology. For example, for banks, within a preset time period, multiple transfer transactions may exist between banks or between banks and a payment platform, for bank I and bank J, it is necessary to check whether the amounts of money transferred to bank J by N customers of bank I are consistent with the amounts of money received by bank J, at this time, a manual account checking mode is adopted, one-time check is required, time consumption is long, efficiency is low, and accuracy cannot be fully guaranteed.

It should be understood that the reconciliation method for business transactions provided by the embodiment of the present disclosure is not limited to be applied to the field of financial technology, the above description is only exemplary, and the reconciliation method for business transactions of the embodiment of the present disclosure can be applied to other technical fields related to reconciliation of business transactions.

Fig. 2 schematically shows a flow chart of a reconciliation method for a business transaction according to an embodiment of the present disclosure.

As shown in fig. 2, the reconciliation method for the business transaction may include operations S201 to S203, for example.

In operation S201, to-be-reconciled transaction data is acquired.

In operation S202, in response to that the to-be-reconciled transaction data is transaction data for real-time reconciliation, reconciling the to-be-reconciled transaction data based on a pre-configured key field, where the key field is used to represent key transaction information in the to-be-reconciled transaction data.

In operation S203, in response to the to-be-reconciled transaction data being daily-end-reconciled transaction data, reconciling the to-be-reconciled transaction data based on the full-size field of the to-be-reconciled transaction data. The transaction data of daily final account checking comprises transaction data of real-time account checking.

In some embodiments of the present disclosure, the most critical information in the business transaction data, such as the amount, date, account, etc., is generally the object that needs to be focused on, and the checking needs to be performed in real time, so as to avoid finding errors in time, performing correction, and avoiding loss. Therefore, in order to quickly and timely check the most critical transaction information, a real-time reconciliation strategy for reconciling based on the key field can be adopted, namely, the key field is set to be the amount, the date, the account and the like.

Illustratively, in the real-time reconciliation process, a data receiving party obtains the to-be-reconciled transaction data provided by a data providing party, the to-be-reconciled transaction data is generally a transaction settlement order of each service type, the data receiving party performs data processing according to different service types, and then a corresponding instruction is generated to complete the actual reconciliation operation. The most common reconciliation may include, for example, equivalence matching, that is, checking whether the amount of money in a transaction settlement list uploaded by a data provider is equal to the amount of money corresponding to the transaction pre-stored by a data receiver, and the reconciliation means may also include simple addition and subtraction operation, comparison whether the amount of money is within an interval, and the like. The specific reconciliation means is set according to the actual application scene, and the disclosure is not limited.

In an embodiment of the present disclosure, after all transactions on the current day are completed, a more comprehensive reconciliation, called a daily final reconciliation, can be performed on all transaction statements on the current day. The daily terminal account checking can carry out account checking on the full data of the transaction settlement list, namely, the field for account checking can be more than that for real-time account checking, and the checking method of partial non-key fields can be properly relaxed. Such as: the number of bits in the check field, the type of check field, etc. Because the objects of daily final account checking are all transaction data, the transaction data generally comprises the transaction data for performing real-time account checking in the daytime, and a double account checking mechanism is further realized.

According to the reconciliation method for the business transaction provided by the embodiment of the disclosure, the reconciliation is divided into the real-time reconciliation and the daily final reconciliation, the most key transaction information is reconciled through the real-time reconciliation, the reconciliation time is greatly shortened, the timeliness of the reconciliation is improved, the re-reconciliation is carried out through the full amount of data contained in the daily final reconciliation transaction data, the transaction data of the daily final reconciliation comprises the transaction data of the real-time reconciliation, and the accuracy of the reconciliation is improved through the dual reconciliation auditing mechanism. For example, daily transaction data passes through a real-time account checking key field, a night account checking total field and two-layer auditing, so that errors of the key field can be found within 5 minutes, and various errors can be found within 24 hours.

Fig. 3 schematically shows a flow chart of a reconciliation method for a business transaction according to an embodiment of the present disclosure.

As shown in fig. 3, the reconciliation method for the business transaction may further include, for example, a configuration key field, and the configuration key field may include, for example, operations S301 to S303.

In operation S301, all first traffic types included in the traffic transaction are extracted.

In operation S302, a corresponding key field is set for each first service type.

In operation S303, a key field corresponding to each first service type is stored in a configuration table by using the first interface identifier corresponding to the first service type as an index.

In an embodiment of the present disclosure, the data providing method generally provides transaction issue lists of each service type, so that the service type of the service transaction can be directly obtained based on the transaction issue lists. In general, for each service type, the corresponding key transaction information may be different, and the corresponding key fields are also different. For example, for type i of service, the corresponding key fields may be, for example, an amount and a date, and for type j of service, the corresponding key fields may be, for example, an account.

In an embodiment of the present disclosure, each service type generally corresponds to an interface, the interface is used for service transaction of the service type, and an interface identifier (interface number) of the interface is generally fixed, so that for each service type, the interface identifier can be used as an index of a key field, the key field corresponding to each service type is stored in a configuration table, and when performing subsequent real-time reconciliation, the key field can be directly and quickly obtained from the configuration table according to the interface identifier of the service type included in the current transaction data to be reconciled to perform reconciliation, which is convenient and fast.

Further, the service type of the service transaction is not the same, and sometimes changes, and when a service type is added or deleted, only the interface identifier of the service type and the corresponding key field need to be added in the configuration table in a manner of storing the key field corresponding to each service type in the configuration table by using the interface identifier as the index of the key field.

Further, in order to optimize the one-click configuration, the data receiver may obtain the to-be-reconciled transaction data in a message format through a java program, for example. And during real-time account checking, receiving and sending messages through a java program, generating a common basic format of the messages in the java program, and inquiring corresponding key fields in a configuration table of the database according to a specific interface identifier. When a new service type is needed, only the interface number of the service type and the corresponding key field need to be newly added in the configuration table, so that the corresponding message can be generated without changing the original logic and without mutual intrusion with other interfaces.

Illustratively, the data receiver acquires a bond transaction order from the data provider, the corresponding interface is identified as 1101, and the transaction amount and the clearing date are determined by inquiring 1101 or preset key fields of real-time reconciliation. On 2/1/2022, the data receiving side obtains a 1101 (bond transaction) invoice message with a number of a06053202201310027 from the data providing method, and after receiving the message from the data providing side, the service data are as follows, as shown in table 1.

TABLE 1

The 1101 transaction list with the number a06053202201310027 is shown in the following table 2, and key data to be checked are recorded in the corresponding service table.

TABLE 2

As can be seen from tables 1 and 2, after the account checking is performed based on the numbers and the interface identifiers, if the two amount fields (balance _ account and track _ account) and the two date fields (clear _ date and track _ date) are consistent, the real-time account checking can be considered to be successful, and the information of successful account checking is returned to the data providing party.

According to the reconciliation method for the business transaction provided by the embodiment of the disclosure, the key words corresponding to the key information of the real-time reconciliation are stored and indexed based on the interface identification corresponding to the business type contained in the business transaction data, when the business type of the business transaction changes (such as increase or decrease), only the interface identification of the business type and the corresponding key field need to be added or deleted directly in the configuration table, the original logic does not need to be changed, and the method and the device do not mutually invade other interfaces, so that one-click configuration is realized, and the scope of reconciliation can be flexibly expanded.

Fig. 4 schematically shows a flow chart of a real-time reconciliation method according to an embodiment of the present disclosure.

As shown in fig. 4, the real-time reconciliation method may include, for example, operations S401 to S403.

In operation S401, a second interface identifier corresponding to a second service type of the transaction data for real-time reconciliation is extracted.

In operation S402, a first interface identifier identical to a second interface identifier is matched in a configuration table.

In operation S403, a corresponding keyword is queried according to the first interface identifier obtained by matching.

In operation S404, reconciliation is performed on the transaction data of the real-time reconciliation according to the corresponding keyword obtained by the query.

Illustratively, the business transaction includes A, B, C as all the first business types, the corresponding interface identifiers are a, b and c, and the corresponding key fields are clearing date, amount and account. And if the second service type of the currently extracted transaction data for real-time reconciliation is B and the corresponding interface identifier is B, directly acquiring the amount of the key field from the configuration table according to the interface identifier B for reconciliation. The real-time account checking can be performed on a five-minute total inner wall ring, namely, if an error occurs, the real-time account checking can be timely found within five minutes, so that the time effectiveness of the account checking is guaranteed.

According to the real-time account checking method corresponding to the embodiment of the disclosure, the key fields can be quickly acquired from the configuration table through the interface identification to perform real-time account checking, so that the real-time account checking efficiency can be further improved, and the timeliness of the real-time account checking is ensured.

Fig. 5 schematically shows a flowchart of a day end reconciliation method according to an embodiment of the present disclosure.

As shown in fig. 5, the daily end reconciliation method may include, for example, operations S501 to S502.

In operation S501, night to-be-reconciled data is acquired.

In operation S502, the to-be-checked transaction data acquired in the daytime and the to-be-checked transaction data acquired in the nighttime are compared with each other.

In an embodiment of the present disclosure, in the course of real-time daily reconciliation, every time the real-time daily reconciliation is performed, the transaction data will fall to the transaction order information table as a record, for example, for a bond transaction order, after the data receiving party obtains the bond transaction order, the data receiving party will fall to the "finance direct bank bond transaction order information table" as a record, and then a corresponding bond-present buy/sell instruction (buy/sell is determined according to specific data) is generated. That is, through a real-time reconciliation of a day, the database of the data recipient may already have stored all of the transaction statements of the day.

And when the daily account is checked, the data providing method provides an integral transaction statement again, and although the transaction statements are provided by the data providing method, the transaction statements can be provided by different users of the data providing method. For example, every real-time reconciliation transaction statement in the daytime is provided by the respective operated staff, while the whole transaction statement provided at night is provided by the supervisor after being summarized from the system, and the sources of the two transaction statements are different. Comparing the same transaction data acquired through different channels can further verify the correctness of the transaction data. Therefore, a scheme for checking the daily transaction data and the night transaction data is further added on the basis of real-time checking, and a double-checking mechanism is realized.

Further, the data receiver can obtain the transaction data to be checked through a point-to-point transmission mode based on a general data transmission platform (GTP). After the data receiver obtains the transaction data to be checked, the transaction data to be checked can be landed to the structured query language database.

For example, nine nights a day, the data receiver obtains the service transaction data provided by the data provider, and the format of the service transaction data may be, for example, PPM _ TRADE _ INFO _ CHECK _ yyymmdd. Meanwhile, the checking result is recorded at 3 points in the morning of the next day to ensure that the business is normally traded on the second day. And, the result of the collation is returned to the counterpart as a file PPM _ TRADE _ INFO _ check _ result _ yyymmdd. The sending mode can also be transmitted in a point-to-point mode based on GTP.

It should be noted that the daily final reconciliation can also flexibly extend the reconciliation range in a one-key configuration similar to the real-time reconciliation.

According to the daytime reconciliation method provided by the embodiment of the disclosure, the accuracy of the reconciliation of the transaction data can be further improved.

Fig. 6 schematically shows a flow chart of a business transaction reconciliation method according to a further embodiment of the present disclosure.

As shown in fig. 6, the business transaction reconciliation method may include operations S601 to S603, for example.

In operation S601, reconciliation is performed on the data to be transacted.

In operation S602, in a case that the reconciliation does not pass, sending alarm information to a provider of the to-be-reconciled transaction data, where the alarm information is used to remind the provider of the to-be-reconciled transaction data to perform manual reconciliation on the to-be-reconciled transaction data.

In the embodiment of the disclosure, the real-time account checking and the daily final account checking both include two conditions of account checking passing and account checking not passing. The situation of account checking failure can include two situations, for example, that the information contained in the transaction data to be checked is inconsistent or the data provided by the provider is missing.

And under the condition that the information contained in the transaction data to be checked is inconsistent, namely the checking caused by the actual data is inconsistent, directly sending alarm information to the provider. For example, the account checking failure information can be sent in an email form, and after receiving the account checking failure information, the data receiving party and the data providing party perform account checking on the data to be checked in a manual account checking mode.

And sending reminding information for re-providing the to-be-checked transaction data to the data provider under the condition that the to-be-checked transaction data provided by the data provider is missing, and sending alarm information to the provider under the condition that the re-provided to-be-checked transaction data is missing. For example, if the data provider fails to report the transaction data or the uploaded transaction data is incomplete, the transaction data is automatically retransmitted within 1 minute, if the data is lost for the second time, the alarm information is directly transmitted to the provider, and after the information of account checking failure is received, the data receiver and the data provider check the account of the data to be checked in a manual account checking mode.

According to the business transaction reconciliation method provided by the embodiment of the disclosure, when the reconciliation is inconsistent, the alarm information is sent to the provider of the transaction data to be reconciled in time to remind the provider of manual reconciliation, so that the reconciliation accuracy and timeliness are further improved.

It should be noted that the real-time reconciliation may be performed based on the data receiving party, or a third-party application may be introduced, and the reconciliation may be performed on the transaction data provided by the data receiving party and the data providing party by the third-party application. The matching can be performed through the unique identifier in the XML messages sent by the two parties under the condition of not contacting the related service by the third party application, and then the key information carried in the messages of the two parties is checked. And the daily final account checking can be directly carried out in the structured language database without the third application.

In summary, the method for business transaction provided by the embodiment of the present disclosure changes the traditional manual reconciliation into automatic reconciliation, and greatly improves efficiency while releasing manpower. The machine replaces manpower, potential errors are avoided, secondary rechecking can be performed manually, and accuracy is improved. And alarming is carried out immediately when the inconsistency is inconsistent, and errors are found in the first time, so that the timeliness of account checking is improved.

Fig. 7 schematically illustrates a block diagram of a reconciliation apparatus for a business transaction according to an embodiment of the present disclosure.

As shown in fig. 7, the reconciliation apparatus 700 for business transaction may include an obtaining module 710, a first reconciliation module 720 and a second prediction module 730.

The obtaining module 710 is configured to obtain the transaction data to be checked.

The first reconciliation module 720 is configured to reconcile the reconciliation transaction data based on a pre-configured key field in response to the reconciliation transaction data being transaction data for real-time reconciliation, where the key field is used to represent key transaction information in the reconciliation transaction data.

The second reconciliation module 730 is configured to, in response to that the to-be-reconciled transaction data is daily-final-reconciled transaction data, reconcile the to-be-reconciled transaction data based on the full-size field of the to-be-reconciled transaction data. And the transaction data of daily final account checking comprises the transaction data of real-time account checking.

Fig. 8 schematically shows a block diagram of a reconciliation apparatus for a business transaction according to another embodiment of the present disclosure.

As shown in fig. 8, the reconciliation apparatus 700 for business transaction may further include a configuration module 740 in addition to the acquisition module 710, the first reconciliation module 720 and the second prediction module 730.

A configuration module 740 for configuring key fields for real-time reconciliation.

Fig. 9 schematically shows a block diagram of a reconciliation apparatus for a business transaction according to yet another embodiment of the present disclosure.

As shown in fig. 9, the reconciliation apparatus 700 for business transaction may further include an alarm module 750, in addition to the obtaining module 710, the first reconciliation module 720, the second prediction module 730 and the configuration module 740.

And the warning module 750 is configured to send warning information to a provider of the to-be-reconciled transaction data when the reconciled transaction data does not pass, where the warning information is used to remind the provider of the to-be-reconciled transaction data of performing manual reconciled on the to-be-reconciled transaction data.

FIG. 10 schematically shows a block diagram of a configuration module according to an embodiment of the disclosure.

As shown in fig. 10, the configuration module 740 may include, for example, a first extraction unit 741, a configuration unit 742, and an index unit 743.

The first extracting unit 741 is configured to extract all the first service types included in the service transaction.

A configuration unit 742 is configured to configure a corresponding key field for each first service type.

An indexing unit 743, configured to store the key field corresponding to each first service type in the configuration table by using the first interface identifier corresponding to the first service type as an index.

Fig. 11 schematically illustrates a block diagram of a first reconciliation module according to an embodiment of the present disclosure.

As shown in fig. 11, the first reconciliation module 720 can include, for example, a second extraction unit 721, a matching unit 722, a query unit 723 and a reconciliation unit 724.

The second extracting unit 721 extracts a second interface identifier corresponding to a second service type of the transaction data for real-time reconciliation.

The matching unit 722 matches the first interface identifier identical to the second interface identifier in the configuration table.

The query unit 723 queries a corresponding keyword according to the first interface identifier obtained through matching.

The reconciliation unit 724 is used for reconciling the transaction data of the real-time reconciliation according to the corresponding keywords obtained by the query.

FIG. 12 schematically illustrates a block diagram of an alarm unit according to an embodiment of the present disclosure.

As shown in FIG. 12, the alert module 750 may include, for example, a first alert element 751 and a second alert element 752.

The first warning unit 751 is used for directly sending warning information to the provider when the information contained in the to-be-reconciled transaction data is inconsistent.

And a second warning unit 752, configured to send, to the provider, a reminder for resupplying the to-be-reconciled transaction data when the to-be-reconciled transaction data provided by the provider is missing, and send, to the provider, a warning message when the to-be-reconciled transaction data provided by the provider is missing.

According to the reconciliation device for business transaction provided by the embodiment of the disclosure, the reconciliation is divided into the real-time reconciliation and the daily final reconciliation, the most key transaction information is reconciled through the real-time reconciliation, the reconciliation time is greatly shortened, the timeliness of the reconciliation is improved, the re-reconciliation is carried out on the full amount of data contained in the daily final reconciliation transaction data, the transaction data of the daily final reconciliation comprises the transaction data of the real-time reconciliation, and the accuracy of the reconciliation is improved through the dual reconciliation auditing mechanism. Further, the key words corresponding to the key information of the real-time account checking are stored and indexed based on the interface identification corresponding to the service type contained in the service transaction data, when the service type of the service transaction changes (such as increases or decreases), the corresponding message can be generated only by adding or deleting the interface identification of the service type and the corresponding key field directly in the configuration table, the original logic does not need to be changed, and the key configuration is not mutually invaded with other interfaces, so that the one-click configuration is realized, and the account checking range can be flexibly expanded. Furthermore, when the account checking is inconsistent, warning information is sent to the provider of the transaction data to be checked in time to remind the provider of manual account checking, and the accuracy and timeliness of the account checking are further improved.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, 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 any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any plurality of the obtaining module 710, the first reconciliation module 720, the second prediction module 730, the configuration module 740, and the alarm module 750 may be combined in one module/unit/sub-unit to be implemented, or any one of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the disclosure, at least one of the obtaining module 710, the first reconciliation module 720, the second prediction module 730, the configuration module 740 and the alarm module 750 may be implemented at least in part as a hardware circuit, 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 by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or may be implemented by any one of three implementations of software, hardware and firmware, or any suitable combination of any of them. Alternatively, at least one of the obtaining module 710, the first reconciliation module 720, the second prediction module 730, the configuration module 740 and the alert module 750 may be at least partially implemented as a computer program module that, when executed, may perform a corresponding function.

It should be noted that, the reconciliation device portion of the business transaction in the embodiment of the present disclosure corresponds to the reconciliation method portion of the business transaction in the embodiment of the present disclosure, and the specific implementation details thereof are also the same.

Fig. 13 schematically shows a block diagram of an electronic device adapted to implement the above described method according to an embodiment of the present disclosure. The electronic device shown in fig. 13 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 13, an electronic device 1300 according to an embodiment of the present disclosure includes a processor 1301 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1302 or a program loaded from a storage section 1308 into a Random Access Memory (RAM) 1303. The processor 1301 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1301 may also include onboard memory for caching purposes. Processor 1301 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 RAM1303, various programs and data necessary for the operation of the electronic apparatus 1300 are stored. The processor 1301, the ROM1302, and the RAM1303 are connected to each other via a bus 1304. The processor 1301 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM1302 and/or the RAM 1303. Note that the programs may also be stored in one or more memories other than the ROM1302 and RAM 1303. The processor 1301 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 1300 may also include input/output (I/O) interface 1305, which is also connected to bus 1304, according to an embodiment of the present disclosure. The electronic device 1300 may also include one or more of the following components connected to the I/O interface 1305: an input portion 1306 including a keyboard, a mouse, and the like; an output section 1307 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1308 including a hard disk and the like; and a communication section 1309 including a network interface card such as a LAN card, a modem, or the like. The communication section 1309 performs communication processing via a network such as the internet. A drive 1310 is also connected to the I/O interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1310 as necessary, so that a computer program read out therefrom is mounted into the storage portion 1308 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via communications component 1309 and/or installed from removable media 1311. The computer program, when executed by the processor 1301, performs the functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are 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 present 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, a computer-readable storage medium may include one or more memories other than the ROM1302 and/or the RAM1303 and/or the ROM1302 and the RAM1303 described above.

The flowchart 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 various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

Claims

1. A reconciliation method for a business transaction, comprising:

acquiring transaction data to be checked;

in response to the transaction data to be checked out is transaction data of real-time check out, checking out the transaction data to be checked out based on a pre-configured key field, wherein the key field is used for representing key transaction information in the transaction data to be checked out;

in response to the account checking transaction data being daily and final account checking transaction data, performing account checking on the account checking transaction data based on a full-amount field of the account checking transaction data;

and the transaction data of the daily final account checking comprises the transaction data of the real-time account checking.

2. The reconciliation method of claim 1, wherein the reconciliation method further comprises:

configuring the key field, including:

extracting all first service types contained in the service transaction;

configuring a corresponding key field for each first service type;

and storing the key field corresponding to each first service type in a configuration table by taking the first interface identifier corresponding to the first service type as an index.

3. The reconciliation method of claim 2, wherein the reconciling the transaction data to be reconciled based on the pre-configured key field in response to the transaction data to be reconciled being the transaction data for real-time reconciliation specifically comprises:

extracting a second interface identifier corresponding to a second service type of the transaction data of the real-time account checking;

matching the first interface identifier which is the same as the second interface identifier in the configuration table;

inquiring corresponding keywords according to the first interface identifier obtained by matching;

and checking the transaction data of the real-time account according to the corresponding keywords obtained by the query.

4. The reconciliation method of claim 1, wherein the reconciling the to-be-reconciled transaction data based on the full-volume field of the to-be-reconciled transaction data in response to the to-be-reconciled transaction data being daily-final-reconciled transaction data specifically comprises:

and comparing the to-be-checked transaction data acquired in the daytime with the full-amount field contained in the to-be-checked transaction data acquired in the nighttime.

5. The reconciliation method of claim 1, wherein the reconciliation method further comprises:

and sending alarm information to a provider of the transaction data to be checked under the condition that the check-out is not passed, wherein the alarm information is used for reminding the provider of the transaction data to be checked to perform manual check-out on the transaction data to be checked.

6. The reconciliation method of claim 5, wherein the condition of the failure in reconciliation comprises inconsistency of information contained in the transaction data to be reconciled or missing of data provided by the provider;

under the condition that the information contained in the transaction data to be checked is inconsistent, directly sending alarm information to the provider;

and sending reminding information for re-providing the to-be-checked transaction data to the provider under the condition that the to-be-checked transaction data provided by the provider is missing, and sending warning information to the provider under the condition that the re-provided to-be-checked transaction data is missing.

7. The reconciliation method of claim 1, wherein the obtaining the transaction data to be reconciled comprises:

and acquiring the transaction data to be checked in a message format through a java program.

8. The reconciliation method of claim 1, wherein the obtaining the transaction data to be reconciled comprises:

and acquiring the transaction data to be reconciled in a point-to-point transmission mode based on a general data transmission platform.

9. A reconciliation device for a business transaction, comprising:

the acquisition module is used for acquiring the transaction data to be checked;

the first reconciliation module is used for reconciling the transaction data to be reconciled based on a pre-configured key field in response to the transaction data to be reconciled being real-time reconciliation transaction data, wherein the key field is used for representing key transaction information in the transaction data to be reconciled;

the second account checking module is used for responding to the transaction data to be checked for account daily and final account checking, and checking the transaction data to be checked for account based on the full-amount field of the transaction data to be checked for account;

10. An electronic device, comprising:

one or more processors;

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 implement the method of any of claims 1-8.

11. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 8.

12. 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 8.