Internal account-based reconciliation method and device, electronic device and storage medium

Abstract

The application discloses a kind of based on internal account reconciliation method and its device, electronic equipment and storage medium, it is related to the field of financial technology or other related fields, wherein, the reconciliation method includes: obtaining the account information of each internal account, and based on account information, generate the reconciliation file corresponding to internal account, based on preset business scenario, determine target internal account set, determine any one internal account in each two internal accounts in target internal account set as main internal account, another internal account is determined as slave internal account, based on key field, traverse the reconciliation data corresponding to main internal account and the reconciliation data corresponding to slave internal account, generate reconciliation result.The present application solves the technical problem that the reconciliation between internal accounts cannot be automatically performed in related art, resulting in low reconciliation efficiency and high labor cost.

Description

Technical Field

[0001] This invention relates to the field of financial technology, and more specifically, to a reconciliation method, apparatus, electronic device, and storage medium based on internal accounts. Background Technology

[0002] With the rapid development of the internet finance industry, the number of credit cards issued has also increased year by year. This continuous growth in credit card issuance has led to the booming development of related businesses such as chargebacks and order reconciliation. Chargebacks and order reconciliation often involve the reconciliation of accounts between different internal accounts within financial institutions. Technically, this is typically done manually. However, when transaction volumes are huge and business rules are complex, adjusting internal account accounts becomes cumbersome, and manual processing of internal account reconciliation is inefficient and consumes significant manpower.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This invention provides a reconciliation method, apparatus, electronic device, and storage medium based on internal accounts, to at least solve the technical problem in related technologies that the inability to automatically reconcile internal accounts leads to low reconciliation efficiency and high labor costs.

[0005] According to one aspect of the present invention, a reconciliation method based on internal accounts is provided, comprising: obtaining account information for each internal account, and generating a reconciliation file corresponding to the internal account based on the account information, wherein the reconciliation file includes at least: reconciliation data; determining a target set of internal accounts based on a preset business scenario; determining one of every two internal accounts in the target set as a primary internal account and the other internal account as a secondary internal account; and generating a reconciliation result by traversing the reconciliation data corresponding to the primary internal account and the reconciliation data corresponding to the secondary internal account based on key fields.

[0006] Optionally, the step of generating a reconciliation file corresponding to the internal account based on the account information includes: determining the reconciliation time range and the reconciliation method; determining the target account information within the reconciliation time range based on the account information; and processing the target account information based on the reconciliation method to generate the reconciliation file corresponding to the internal account.

[0007] Optionally, after generating a reconciliation file corresponding to the internal account based on the account information, the method further includes: determining a file identifier for each reconciliation file, wherein the file identifier includes at least: date and internal account identifier; establishing an index for each reconciliation file based on the file identifier, and storing each reconciliation file in a preset file system.

[0008] Optionally, after generating a reconciliation file corresponding to the internal account based on the account information, the method further includes: processing the reconciliation data of each reconciliation file based on a preset standard strategy; determining the key fields of the processed reconciliation data, wherein the key fields include at least: transaction date, transaction amount, and loan / debit flag; retaining the data records corresponding to the key fields and storing them in a preset database.

[0009] Optionally, before generating a reconciliation result by traversing the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account based on the key field, the method further includes: determining the master data record corresponding to the key field based on the reconciliation data corresponding to the master internal account; and determining the slave data record corresponding to the key field based on the reconciliation data corresponding to the slave internal account.

[0010] Optionally, the step of generating a reconciliation result by traversing the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account based on key fields includes: traversing the key fields in the reconciliation data corresponding to the master internal account, querying the slave data records in the reconciliation data corresponding to the slave internal account, and obtaining query results; based on the query results, determining a first slave data record set and a second slave data record set, wherein each first slave data record in the first slave data record set contains slave data records not found in the reconciliation data corresponding to the slave internal account, and each second slave data record in the second slave data record set contains slave data records found in the reconciliation data corresponding to the slave internal account; determining the target key fields corresponding to each first slave data record, obtaining a target key field set, and matching each target key field in the target key field set with the target key field set. The master data record corresponding to the key field is marked as a one-sided record; based on the second set of slave data records, a first master data record and a third slave data record with different business elements are determined, and the first master data record and the third slave data record are marked as error records respectively, wherein the business elements include at least: transaction amount; based on the second set of slave data records, a second master data record and a fourth slave data record with the same business elements are determined, and the second master data record and the fourth slave data record are marked as reconciliation records respectively; based on the first set of slave data records and the second set of slave data records, the reconciliation data corresponding to the slave internal account is checked to obtain the check result, and if the check result indicates that there is a fifth slave data record that has not been reconciled, the fifth slave data record is marked as the one-sided record; based on the one-sided record, the error record, and the reconciliation record, the reconciliation result is generated.

[0011] Optionally, after generating a reconciliation result by traversing the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account based on key fields, the method further includes: matching business rules from a pre-configured business rule engine based on the reconciliation result to obtain a matching result; if the matching result indicates that a first pending record matches a corresponding target business rule, processing the corresponding first pending record based on the target business rule to obtain a processing result, wherein the first pending record is the unilateral record or the erroneous record; adjusting the account information of the internal account corresponding to the first pending record based on the processing result, and generating an adjustment list report; if the matching result indicates that a second pending record does not match a corresponding target business rule, sending the second pending record to a target terminal for processing, wherein the second pending record is the unilateral record or the erroneous record.

[0012] According to another aspect of the present invention, a reconciliation device based on internal accounts is also provided, comprising: a first generation unit, configured to acquire account information for each internal account and generate a reconciliation file corresponding to the internal account based on the account information, wherein the reconciliation file includes at least: reconciliation data; a first determination unit, configured to determine a target set of internal accounts based on a preset business scenario; a second determination unit, configured to determine one of every two internal accounts in the target set as a primary internal account and the other internal account as a secondary internal account; and a second generation unit, configured to generate a reconciliation result by traversing the reconciliation data corresponding to the primary internal account and the reconciliation data corresponding to the secondary internal account based on key fields.

[0013] Optionally, the first generation unit includes: a first determining module, configured to determine the reconciliation time range and the reconciliation method; a second determining module, configured to determine target account information within the reconciliation time range based on the account information; and a first generation module, configured to process the target account information based on the reconciliation method and generate the reconciliation file corresponding to the internal account.

[0014] Optionally, the reconciliation device further includes: a third determining module, used to determine a file identifier for each reconciliation file after generating a reconciliation file corresponding to the internal account based on the account information, wherein the file identifier includes at least: date and internal account identifier; and a first establishing module, used to establish an index for each reconciliation file based on the file identifier and store each reconciliation file in a preset file system.

[0015] Optionally, the reconciliation device further includes: a first processing module, configured to process the reconciliation data of each reconciliation file based on a preset standard strategy after generating a reconciliation file corresponding to the internal account based on the account information; a fourth determining module, configured to determine the key fields of the processed reconciliation data, wherein the key fields include at least: transaction date, transaction amount, and loan / debit flag; and a first retaining module, configured to retain the data records corresponding to the key fields and store them in a preset database.

[0016] Optionally, the reconciliation device further includes: a fifth determining module, used to determine the master data record corresponding to the key field based on the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account before generating a reconciliation result by traversing the reconciliation data corresponding to the master internal account and the slave internal account based on the key field; and a sixth determining module, used to determine the slave data record corresponding to the key field based on the reconciliation data corresponding to the slave internal account.

[0017] Optionally, the second generation unit includes: a first query module, configured to traverse the key fields in the reconciliation data corresponding to the master internal account, query the slave data records in the reconciliation data corresponding to the slave internal account, and obtain query results; a seventh determination module, configured to determine a first slave data record set and a second slave data record set based on the query results, wherein each first slave data record in the first slave data record set contains slave data records not found in the reconciliation data corresponding to the slave internal account, and each second slave data record in the second slave data record set contains slave data records found in the reconciliation data corresponding to the slave internal account; a first marking module, configured to determine the target key field corresponding to each first slave data record, obtain a target key field set, and mark the master data record corresponding to each target key field in the target key field set as a one-sided record; a second marking module; A module is used to determine, based on the second set of secondary data records, a first master data record and a third secondary data record with different business elements, and to mark the first master data record and the third secondary data record as error records, wherein the business elements include at least: transaction amount; a third marking module is used to determine, based on the second set of secondary data records, a second master data record and a fourth secondary data record with the same business elements, and to mark the second master data record and the fourth secondary data record as reconciliation records; a fourth marking module is used to check the reconciliation data corresponding to the internal accounts based on the first set of secondary data records and the second set of secondary data records, obtain the check result, and, if the check result indicates the existence of a fifth secondary data record that has not been reconciled, mark the fifth secondary data record as the unilateral record; a second generation module is used to generate the reconciliation result based on the unilateral record, the error record, and the reconciliation record.

[0018] Optionally, the reconciliation device further includes: a first matching module, configured to, after generating a reconciliation result by traversing the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account based on key fields, match business rules from a pre-configured business rule engine based on the reconciliation result to obtain a matching result; a second processing module, configured to, when the matching result indicates that a first pending record matches a corresponding target business rule, process the corresponding first pending record based on the target business rule to obtain a processing result, wherein the first pending record is the unilateral record or the erroneous record; a first adjustment module, configured to, based on the processing result, adjust the account information of the internal account corresponding to the first pending record and generate an adjustment list report; and a first sending module, configured to, when the matching result indicates that a second pending record does not match a corresponding target business rule, send the second pending record to a target terminal for processing, wherein the second pending record is the unilateral record or the erroneous record.

[0019] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the above-described internal account-based reconciliation method.

[0020] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the reconciliation method based on internal accounts described above.

[0021] In this disclosure, account information for each internal account is obtained, and a reconciliation file corresponding to the internal account is generated based on the account information. Based on a preset business scenario, a target set of internal accounts is determined. For every two internal accounts in the target set, one is designated as the primary internal account, and the other as the secondary internal account. Based on key fields, the reconciliation data corresponding to the primary and secondary internal accounts is traversed to generate a reconciliation result. In this application, a reconciliation file is first generated for each internal account. Then, based on a preset business scenario, a target set of internal accounts to be reconciled is determined. For every two target internal accounts, one is designated as the primary internal account, and the other as the secondary internal account. Then, by traversing the reconciliation data of the primary and secondary internal accounts based on key fields, a reconciliation result is generated. This enables automatic reconciliation between internal accounts, improving reconciliation efficiency, reducing manual processing costs, and thus solving the technical problem in related technologies where automatic reconciliation between internal accounts is impossible, resulting in low reconciliation efficiency and high labor costs. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0023] Figure 1 This is a flowchart of an optional reconciliation method based on internal accounts according to an embodiment of the present invention;

[0024] Figure 2 This is a schematic diagram of an optional internal account-based reconciliation device according to an embodiment of the present invention;

[0025] Figure 3 This is a hardware structure block diagram of an electronic device (or mobile device) for an internal account-based reconciliation method according to an embodiment of the present invention. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] It should be noted that the reconciliation method and apparatus based on internal accounts in this disclosure can be used in the context of reconciliation between internal accounts in the fintech field, or in any field other than fintech for the purpose of reconciliation between internal accounts. This disclosure does not limit the application areas of the reconciliation method and apparatus based on internal accounts.

[0029] It should be noted that all information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) involved in this disclosure are information and data authorized by the user or fully authorized by all parties. For example, this system has an interface with relevant users or organizations. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain the relevant information after receiving consent information from the aforementioned user or organization.

[0030] The following embodiments of the present invention can be applied to various systems / applications / devices for reconciling internal accounts. In this invention, the lending relationships between internal accounts involved in chargeback and billing reconciliation are clear, for example, the chargeback temporary collection internal account and the card issuance clearing internal account. Therefore, a reconciliation method similar to that between two organizations can be adopted for reconciling internal accounts. Based on this, the present invention proposes an internal account reconciliation method that can achieve automatic reconciliation between internal accounts. By connecting to a business rule engine, relevant business rules can be flexibly configured, realizing automatic processing of error accounts, reducing manual processing costs, and after the system goes live, no modifications to the existing system are required to meet business needs.

[0031] The present invention will now be described in detail with reference to various embodiments.

[0032] Example 1

[0033] According to an embodiment of the present invention, an embodiment of a reconciliation method based on internal accounts is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0034] Figure 1 This is a flowchart of an optional internal account-based reconciliation method according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0035] Step S101: Obtain account information for each internal account, and generate a reconciliation file corresponding to the internal account based on the account information. The reconciliation file shall include at least the reconciliation data.

[0036] Step S102: Based on the preset business scenario, determine the target set of internal accounts.

[0037] Step S103: Determine one of any two internal accounts in the target internal account set as the primary internal account and the other internal account as the secondary internal account.

[0038] Step S104: Based on the key fields, traverse the reconciliation data corresponding to the main internal account and the reconciliation data corresponding to the secondary internal account to generate the reconciliation results.

[0039] Through the above steps, account information for each internal account can be obtained, and a reconciliation file corresponding to the internal account can be generated based on the account information. Based on a preset business scenario, a target set of internal accounts is determined. For every two internal accounts in the target set, one is designated as the primary internal account, and the other as the secondary internal account. Based on key fields, the reconciliation data corresponding to the primary and secondary internal accounts is traversed to generate a reconciliation result. In this embodiment of the invention, a reconciliation file can be generated for each internal account first. Then, based on a preset business scenario, a target set of internal accounts to be reconciled is determined. For every two target internal accounts, one is designated as the primary internal account, and the other as the secondary internal account. Then, by traversing the reconciliation data in the primary and secondary internal accounts based on key fields, a reconciliation result is generated. This enables automatic reconciliation between internal accounts, improving reconciliation efficiency, reducing manual processing costs, and thus solving the technical problem in related technologies where automatic reconciliation between internal accounts is impossible, resulting in low reconciliation efficiency and high labor costs.

[0040] The embodiments of the present invention will now be described in detail with reference to the steps described above.

[0041] Step S101: Obtain account information for each internal account, and generate a reconciliation file corresponding to the internal account based on the account information. The reconciliation file shall include at least the reconciliation data.

[0042] Optionally, the step of generating reconciliation files corresponding to internal accounts based on account information includes: determining the reconciliation time range and reconciliation method; determining the target account information within the reconciliation time range based on account information; and processing the target account information based on the reconciliation method to generate reconciliation files corresponding to internal accounts.

[0043] In this embodiment of the invention, account information (e.g., some transaction information) of each internal account can be obtained first, and a reconciliation file corresponding to the internal account can be generated based on the account information for subsequent reconciliation. Specifically, the reconciliation time range and reconciliation method between internal accounts can be determined first (e.g., the reconciliation file is processed into a file with the same message format or the same file format to facilitate reconciliation). Then, the target account information within the reconciliation time range can be determined based on the account information, and the target account information is processed through the determined reconciliation method to generate a reconciliation file corresponding to the internal account (the reconciliation file may include reconciliation data and other data).

[0044] Optionally, after generating reconciliation files corresponding to internal accounts based on account information, the method further includes: determining a file identifier for each reconciliation file, wherein the file identifier includes at least: date and internal account identifier; indexing each reconciliation file based on the file identifier, and storing each reconciliation file in a preset file system.

[0045] In this embodiment of the invention, after generating a corresponding reconciliation file for each internal account, the reconciliation file can be standardized and normalized, and the standardized and normalized reconciliation file can be persisted. Specifically, the reconciliation files generated by different internal accounts can be named and normalized (i.e., the file identifier of each reconciliation file is determined, which includes at least: date and internal account identifier), and stored in a preset file system (e.g., HDFS (Hadoop Distributed File System) distributed file system). An index is built for the stored reconciliation files according to the file identifier of each reconciliation file, so as to facilitate the quick search and use of the reconciliation files in the future.

[0046] Optionally, after generating reconciliation files corresponding to internal accounts based on account information, the method further includes: processing the reconciliation data of each reconciliation file based on a preset standard strategy; determining the key fields of the processed reconciliation data, wherein the key fields include at least: transaction date, transaction amount, and debit / credit flag; retaining the data records corresponding to the key fields and storing them in a preset database.

[0047] In this embodiment of the invention, the reconciliation data in the reconciliation file can be standardized (i.e., the reconciliation data of each reconciliation file is processed based on a preset standardization strategy). For example, preset standardization strategies such as the format of the transaction date and time, the amount format, the currency format, and the lending / borrowing flag can be determined. By setting the data format of each type of data through the preset standardization strategy, the reconciliation data in the reconciliation file is standardized. Then, the standardized reconciliation data is persisted. To reduce the storage capacity occupied by persistence, the key fields of the processed reconciliation data can be determined first (the key fields include at least: transaction date, transaction amount, lending / borrowing flag, etc.). Data records corresponding to the key fields related to reconciliation are retained, while data records corresponding to non-key fields can be discarded. Then, the reconciliation data is stored in a preset database (e.g., a relational database).

[0048] Step S102: Based on the preset business scenario, determine the target set of internal accounts.

[0049] In this embodiment of the invention, the internal accounts that need to be reconciled in the specific business scenario (e.g., a chargeback call business scenario) can be determined to obtain a target set of internal accounts.

[0050] Step S103: Determine one of any two internal accounts in the target internal account set as the primary internal account and the other internal account as the secondary internal account.

[0051] In this embodiment of the invention, any two internal accounts in the target set of internal accounts can be selected for reconciliation, and one of the selected internal accounts can be designated as the primary internal account, and the other internal account can be designated as the secondary internal account.

[0052] Optionally, before generating the reconciliation results by traversing the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account based on the key field, the method further includes: determining the master data record corresponding to the key field based on the reconciliation data corresponding to the master internal account; and determining the slave data record corresponding to the key field based on the reconciliation data corresponding to the slave internal account.

[0053] In this embodiment of the invention, the master data record corresponding to the key field can be determined based on the reconciliation data (i.e., master data) corresponding to the master internal account, and the slave data record corresponding to the key field can be determined based on the reconciliation data (i.e., slave data) corresponding to the slave internal account.

[0054] Step S104: Based on the key fields, traverse the reconciliation data corresponding to the main internal account and the reconciliation data corresponding to the secondary internal account to generate the reconciliation results.

[0055] Optionally, the step of generating reconciliation results by traversing the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account based on key fields includes: traversing the key fields in the reconciliation data corresponding to the master internal account, querying slave data records in the reconciliation data corresponding to the slave internal account, and obtaining query results; based on the query results, determining a first slave data record set and a second slave data record set, wherein each first slave data record in the first slave data record set contains slave data records not found in the reconciliation data corresponding to the slave internal account, and each second slave data record in the second slave data record set contains slave data records found in the reconciliation data corresponding to the slave internal account; determining the target key fields corresponding to each first slave data record, obtaining a target key field set, and matching each target key field in the target key field set with the target key field set. The master data record corresponding to the key field is marked as a one-sided record; based on the second set of slave data records, the first and third master data records with different business elements are identified, and the first and third master data records are marked as error records respectively, wherein the business elements include at least: transaction amount; based on the second set of slave data records, the second and fourth master data records with the same business elements are identified, and the second and fourth master data records are marked as reconciliation records respectively; based on the first and second sets of slave data records, the reconciliation data corresponding to the internal accounts is checked to obtain the check results, and if the check results indicate the existence of a fifth slave data record that has not been reconciled, the fifth slave data record is marked as a one-sided record; based on the one-sided records, error records, and reconciliation records, a reconciliation result is generated.

[0056] In this embodiment of the invention, the master data can be traversed in a loop, and the key fields in the master data can be used to query the slave data records in the slave data (that is, the key fields in the reconciliation data corresponding to the master internal account can be used to query the slave data records in the reconciliation data corresponding to the slave internal account to obtain the query results).

[0057] If the corresponding record cannot be found in the data, the record in the master data is marked as a one-sided record (that is, the target key field corresponding to each first data record is determined, the target key field set is obtained, and the master data record corresponding to each target key field in the target key field set is marked as a one-sided record, wherein the first data record is the data record in the first data record set determined according to the query results, and the first data record set records the data records that were not found in the reconciliation data corresponding to the internal account).

[0058] If a corresponding record is found, but the business element is inconsistent with the data record in the master data (e.g., the amount is inconsistent), then the record in the master data and the sub-data is marked as an error (that is, based on the second sub-data record set, the first master data record and the third sub-data record with different business elements are determined, and the first master data record and the third sub-data record are marked as error records respectively, wherein the second sub-data record set records the sub-data records queried in the reconciliation data corresponding to the sub-internal account, and the third sub-data record is a sub-data record in the second sub-data record set).

[0059] If a corresponding record is found, and the business element matches the data record in the master data, then that record in both the master and slave data is marked as reconciled (i.e., based on the second slave data record set, the second master data record and the fourth slave data record with the same business element are identified, and the second master data record and the fourth slave data record are marked as reconciled records, where the fourth slave data record is a slave data record in the second slave data record set). Afterwards, it can be checked whether there are any unreconciled records in the auxiliary data. If so, they are marked as one-sided (i.e., based on the first and second slave data record sets, the reconciliation data corresponding to the internal accounts is checked to obtain the check results, and if the check results indicate the existence of an unreconciled fifth slave data record, the fifth slave data record is marked as a one-sided record).

[0060] Then, reconciliation results can be generated based on unilateral records, erroneous records, and reconciliation records, and the reconciliation results can be notified to business personnel.

[0061] Optionally, after generating reconciliation results by traversing the reconciliation data corresponding to the main internal account based on key fields and from the reconciliation data corresponding to the internal account, the method further includes: matching business rules from a pre-configured business rule engine based on the reconciliation results to obtain matching results; if the matching results indicate that a first pending record matches the corresponding target business rule, processing the corresponding first pending record based on the target business rule to obtain processing results, wherein the first pending record is a one-sided record or an erroneous record; adjusting the account information of the internal account corresponding to the first pending record based on the processing results and generating an adjustment list report; if the matching results indicate that a second pending record does not match the corresponding target business rule, sending the second pending record to the target terminal for processing, wherein the second pending record is a one-sided record or an erroneous record.

[0062] In this embodiment of the invention, error processing can be performed on unilateral records and erroneous records in the reconciliation results. Specifically, a business rule engine can be accessed, and business rules can be flexibly configured in the business rule engine to process unilateral records or erroneous records. Then, based on the reconciliation results, business rules can be matched from the pre-configured business rule engine to obtain matching results. If the matching results indicate that a first pending record (i.e., a unilateral record or erroneous record) matches the corresponding target business rule (i.e., a unilateral record or erroneous record hits a certain business rule in the business rule engine), then the corresponding first pending record can be processed based on the target business rule to obtain processing results. Based on the processing results, the accounting relationship of the corresponding internal account can be adjusted (i.e., the account information of the internal account corresponding to the first pending record can be adjusted), and an adjustment list report can be generated for relevant business personnel to review. If the matching result indicates that there is a second pending record (i.e., a one-sided record or an incorrect record) that does not match the corresponding target business rule (i.e., a one-sided record or an incorrect record does not match a certain business rule in the business rule engine), then the second pending record will be sent to the target terminal to notify the business personnel to perform manual processing.

[0063] The following describes in detail another optional implementation method.

[0064] This embodiment provides an internal account reconciliation system for chargeback requests based on a business rule engine. The following example illustrates the reconciliation process between two internal accounts:

[0065] (1) After the two internal accounts are moved, the corresponding reconciliation files are generated and the two reconciliation files are obtained for subsequent reconciliation.

[0066] a. Determine the timeframe and reconciliation document format for the two internal accounts.

[0067] b. At the end of the day, based on the daily action data of the two internal accounts, and according to the determined reconciliation time range and document format, the corresponding reconciliation documents can be generated.

[0068] (2) Standardize and normalize the reconciliation documents and persist them.

[0069] a. Standardize the naming of the original reconciliation files generated by different internal accounts and store them in a file storage system, such as the HDFS distributed file system, and create an index for the stored reconciliation files to facilitate quick retrieval and use of the original reconciliation files in the future.

[0070] b. Standardize the reconciliation data in the reconciliation file, for example, standardizing the format of transaction dates and times, amount formats, currency formats, and debit / credit indicators. After standardization, persist the reconciliation data. To reduce the storage capacity required for persistence, key reconciliation-related fields can be retained, while non-key fields can be discarded. The reconciliation data is then stored in a database (such as a relational database).

[0071] (3) Perform automatic reconciliation based on persistent reconciliation data.

[0072] a. Based on the specific business scenario, select the reconciliation data of one internal account as the primary data and the reconciliation data of the other internal account as the secondary data.

[0073] b. Loop through the master data and use the key element fields of the master data to search for data records in the auxiliary data. If the corresponding record is not found in the auxiliary data, mark the record in the master data as one-sided. If the corresponding record is found, but the business elements are inconsistent, such as the amount, mark the record in both the master data and the auxiliary data as an error. If the corresponding record is found and the business elements are consistent, mark the record in both the master data and the auxiliary data as balanced.

[0074] c. Check if there are any unreconciled records in the auxiliary data; if so, mark them as one-sided.

[0075] d. Generate reconciliation results and notify business personnel of the results.

[0076] (4) Handling reconciliation errors.

[0077] a. Integrate with the business rules engine and flexibly configure business rules within the engine to handle unilateral or erroneous transactions.

[0078] b. If a unilateral or erroneous transaction hits a business rule deployed in the business rule engine, the unilateral or erroneous transaction record will be processed, the accounting relationship of the corresponding internal account will be adjusted, and an adjustment list report will be generated for relevant business personnel to review.

[0079] c. If a unilateral or erroneous transaction does not match any of the business rules deployed in the business rule engine, the relevant business personnel will be notified through the messaging system to handle the unilateral or erroneous transaction record that does not match any business rules manually.

[0080] This invention proposes an internal account reconciliation method that can solve the problems of cumbersome internal account adjustments and high labor costs in business processes such as chargeback calls, and can achieve the following beneficial effects:

[0081] (1) It can realize automatic reconciliation and automatic error handling between internal accounts within the system;

[0082] (2) By introducing a business rule engine, business rules can be flexibly configured to automatically process one-sided or erroneous records, reducing manual intervention and lowering business operation costs. Furthermore, it can cope with rapidly changing error processing needs without modifying the system; only new one-sided or erroneous record processing business rules need to be redeployed.

[0083] The following is a detailed description with reference to another embodiment.

[0084] Example 2

[0085] The reconciliation device based on internal accounts provided in this embodiment includes multiple implementation units, each of which corresponds to a specific implementation step in Embodiment 1 above.

[0086] Figure 2 This is a schematic diagram of an optional internal account-based reconciliation device according to an embodiment of the present invention, such as... Figure 2 As shown, the reconciliation device may include: a first generation unit 20, a first determination unit 21, a second determination unit 22, and a second generation unit 23, wherein,

[0087] The first generation unit 20 is used to obtain the account information of each internal account and generate a reconciliation file corresponding to the internal account based on the account information. The reconciliation file includes at least: reconciliation data.

[0088] The first determining unit 21 is used to determine the target set of internal accounts based on a preset business scenario;

[0089] The second determining unit 22 is used to determine one of any two internal accounts in the target internal account set as the master internal account and the other internal account as the slave internal account.

[0090] The second generation unit 23 is used to generate reconciliation results by traversing the reconciliation data corresponding to the main internal account and the reconciliation data corresponding to the internal account based on key fields.

[0091] The aforementioned reconciliation device can obtain account information for each internal account through the first generation unit 20, and generate a reconciliation file corresponding to the internal account based on the account information. The first determination unit 21 determines a target set of internal accounts based on a preset business scenario. The second determination unit 22 determines one of every two internal accounts in the target set as the primary internal account and the other as the secondary internal account. The second generation unit 23 iterates through the reconciliation data corresponding to the primary and secondary internal accounts based on key fields to generate a reconciliation result. In this embodiment of the invention, a reconciliation file can be generated for each internal account first. Then, based on a preset business scenario, a target set of internal accounts to be reconciled can be determined, and one of every two target internal accounts can be determined as the primary internal account and the other as the secondary internal account. Then, by iterating through the reconciliation data in the primary and secondary internal accounts based on key fields, a reconciliation result can be generated. This enables automatic reconciliation between internal accounts, improving reconciliation efficiency, reducing manual processing costs, and thus solving the technical problem in related technologies where automatic reconciliation between internal accounts is impossible, resulting in low reconciliation efficiency and high labor costs.

[0092] Optionally, the first generation unit includes: a first determining module for determining the reconciliation time range and the reconciliation method; a second determining module for determining the target account information within the reconciliation time range based on the account information; and a first generation module for processing the target account information based on the reconciliation method to generate a reconciliation file corresponding to the internal account.

[0093] Optionally, the reconciliation device further includes: a third determining module, used to determine the file identifier of each reconciliation file after generating reconciliation files corresponding to internal accounts based on account information, wherein the file identifier includes at least: date and internal account identifier; and a first establishing module, used to establish an index for each reconciliation file based on the file identifier and store each reconciliation file in a preset file system.

[0094] Optionally, the reconciliation device further includes: a first processing module, used to process the reconciliation data of each reconciliation file based on a preset standard strategy after generating reconciliation files corresponding to internal accounts based on account information; a fourth determining module, used to determine the key fields of the processed reconciliation data, wherein the key fields include at least: transaction date, transaction amount, and debit / credit flag; and a first retaining module, used to retain the data records corresponding to the key fields and store them in a preset database.

[0095] Optionally, the reconciliation device further includes: a fifth determining module, used to determine the master data record corresponding to the key field based on the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account before generating the reconciliation result based on the key field; and a sixth determining module, used to determine the slave data record corresponding to the key field based on the reconciliation data corresponding to the slave internal account.

[0096] Optionally, the second generation unit includes: a first query module, used to traverse the key fields in the reconciliation data corresponding to the master internal account, query the slave data records in the reconciliation data corresponding to the slave internal account, and obtain query results; a seventh determination module, used to determine a first slave data record set and a second slave data record set based on the query results, wherein each first slave data record in the first slave data record set contains slave data records not found in the reconciliation data corresponding to the master internal account, and each second slave data record in the second slave data record set contains slave data records found in the reconciliation data corresponding to the master internal account; a first marking module, used to determine the target key field corresponding to each first slave data record, obtain a target key field set, and mark the master data record corresponding to each target key field in the target key field set as a one-sided record; a second marking module; The first module is used to identify first and third master data records with different business elements based on the second set of slave data records, and to mark the first and third master data records as error records respectively. The business elements include at least the transaction amount. The second module is used to identify second and fourth master data records with the same business elements based on the second set of slave data records, and to mark the second and fourth master data records as reconciliation records respectively. The third module is used to check the reconciliation data corresponding to the internal accounts based on the first and second sets of slave data records, obtain the check results, and mark the fifth slave data record as a one-sided record if the check results indicate that there is an unreconciled fifth slave data record. The fourth module is used to generate a reconciliation result based on the one-sided record, the error record, and the reconciliation record.

[0097] Optionally, the reconciliation device further includes: a first matching module, used to generate a reconciliation result by traversing the reconciliation data corresponding to the main internal account and the reconciliation data corresponding to the internal account based on key fields, and then matching business rules from a pre-configured business rule engine based on the reconciliation result to obtain a matching result; a second processing module, used to process the corresponding first pending record based on the target business rule when the matching result indicates that there is a first pending record that matches the corresponding target business rule to obtain a processing result, wherein the first pending record is a one-sided record or an erroneous record; a first adjustment module, used to adjust the account information of the internal account corresponding to the first pending record based on the processing result and generate an adjustment list report; and a first sending module, used to send the second pending record to the target terminal for processing when the matching result indicates that there is a second pending record that does not match the corresponding target business rule, wherein the second pending record is a one-sided record or an erroneous record.

[0098] The aforementioned reconciliation device may also include a processor and a memory. The first generation unit 20, the first determination unit 21, the second determination unit 22, the second generation unit 23, etc., are all stored in the memory as program units, and the processor executes the aforementioned program units stored in the memory to realize the corresponding functions.

[0099] The aforementioned processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and by adjusting kernel parameters, reconciliation results are generated by traversing reconciliation data corresponding to the main internal account and the sub-internal account, based on key fields.

[0100] The aforementioned memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0101] This application also provides a computer program product that, when executed on a data processing device, is suitable for executing an initialization program with the following method steps: obtaining account information for each internal account, generating a reconciliation file corresponding to the internal account based on the account information, determining a target set of internal accounts based on a preset business scenario, determining one of every two internal accounts in the target set as the primary internal account and the other as the secondary internal account, and traversing the reconciliation data corresponding to the primary internal account and the secondary internal account based on key fields to generate a reconciliation result.

[0102] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the above-described internal account-based reconciliation method.

[0103] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the above-described internal account-based reconciliation method.

[0104] Figure 3 This is a hardware structure block diagram of an electronic device (or mobile device) for an internal account-based reconciliation method according to an embodiment of the present invention. Figure 3 As shown, the electronic device may include one or more processors 302 (shown as 302a, 302b, ..., 302n in the figure) 302 (processor 302 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 304 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 3 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device may also include components that are more... Figure 3 The more or fewer components shown, or having the same Figure 3 The different configurations shown.

[0105] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0106] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0107] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0108] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0109] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0110] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0111] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A reconciliation method based on internal accounts, characterized in that, include: Obtain account information for each internal account, and generate a reconciliation file corresponding to the internal account based on the account information, wherein the reconciliation file includes at least: reconciliation data; Based on a preset standard strategy, the reconciliation data of each reconciliation file is processed; key fields of the processed reconciliation data are determined, wherein the key fields include at least: transaction date, transaction amount, and loan / debit flag; data records corresponding to the key fields are retained and stored in a preset database; data records corresponding to non-key fields in the processed reconciliation data are discarded. Based on a pre-defined business scenario, determine the target set of internal accounts; In the target set of internal accounts, one of the two internal accounts is designated as the primary internal account, and the other internal account is designated as the secondary internal account. Based on key fields, the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account are traversed to generate reconciliation results. Specifically, the key fields in the reconciliation data corresponding to the master internal account are traversed, and slave data records are queried in the reconciliation data corresponding to the slave internal account to obtain query results. Based on the query results, a first slave data record set and a second slave data record set are determined. Each first slave data record in the first slave data record set contains slave data records not found in the reconciliation data corresponding to the slave internal account, and each second slave data record in the second slave data record set contains slave data records found in the reconciliation data corresponding to the slave internal account. Target key fields corresponding to each first slave data record are determined to obtain a target key field set, and each target key field in the target key field set is compared with... The master data record corresponding to the field is marked as a one-sided record; based on the second set of slave data records, a first master data record and a third slave data record with different business elements are determined, and the first master data record and the third slave data record are marked as error records respectively, wherein the business elements include at least: transaction amount; based on the second set of slave data records, a second master data record and a fourth slave data record with the same business elements are determined, and the second master data record and the fourth slave data record are marked as reconciliation records respectively; based on the first set of slave data records and the second set of slave data records, the reconciliation data corresponding to the slave internal account is checked to obtain the check result, and if the check result indicates that there is a fifth slave data record that has not been reconciled, the fifth slave data record is marked as the one-sided record; based on the one-sided record, the error record, and the reconciliation record, the reconciliation result is generated; Based on the reconciliation results, business rules are matched from the pre-configured business rule engine to obtain a matching result; if the matching result indicates that a first pending record matches the corresponding target business rule, the first pending record is processed based on the target business rule to obtain a processing result, wherein the first pending record is the unilateral record or the erroneous record; based on the processing result, the account information of the internal account corresponding to the first pending record is adjusted, and an adjustment list report is generated; if the matching result indicates that a second pending record does not match the corresponding target business rule, the second pending record is sent to the target terminal for processing, wherein the second pending record is the unilateral record or the erroneous record.

2. The reconciliation method according to claim 1, characterized in that, The step of generating a reconciliation file corresponding to the internal account based on the account information includes: Determine the timeframe and method for reconciliation; Based on the account information, the target account information within the reconciliation time range is determined; Based on the reconciliation method, the target account information is processed to generate the reconciliation file corresponding to the internal account.

3. The reconciliation method according to claim 1, characterized in that, After generating a reconciliation file corresponding to the internal account based on the account information, the process further includes: Determine a file identifier for each of the reconciliation documents, wherein the file identifier includes at least: date and internal account identifier; Based on the file identifier, an index is created for each reconciliation file, and each reconciliation file is stored in a preset file system.

4. The reconciliation method according to claim 1, characterized in that, Before generating the reconciliation result by iterating through the reconciliation data corresponding to the primary internal account and the reconciliation data corresponding to the secondary internal account based on key fields, the process also includes: Based on the reconciliation data corresponding to the main internal account, determine the master data record corresponding to the key field; Based on the reconciliation data corresponding to the internal account, determine the data record corresponding to the key field.

5. A reconciliation device based on an internal account, characterized in that, include: The first generation unit is used to obtain account information for each internal account and generate a reconciliation file corresponding to the internal account based on the account information, wherein the reconciliation file includes at least: reconciliation data; The first processing module is used to process the reconciliation data of each reconciliation file based on a preset standard strategy; determine the key fields of the processed reconciliation data, wherein the key fields include at least: transaction date, transaction amount, and loan / debit flag; retain the data records corresponding to the key fields and store them in a preset database; and discard the data records corresponding to non-key fields in the processed reconciliation data. The first determining unit is used to determine the target set of internal accounts based on a preset business scenario; The second determining unit is configured to determine one of any two internal accounts in the target internal account set as the primary internal account and the other internal account as the secondary internal account. The second generation unit is used to generate a reconciliation result by traversing the reconciliation data corresponding to the master internal account and the reconciliation data corresponding to the slave internal account based on key fields. Specifically, it traverses the key fields in the reconciliation data corresponding to the master internal account, queries slave data records in the reconciliation data corresponding to the slave internal account, and obtains query results. Based on the query results, it determines a first slave data record set and a second slave data record set. Each first slave data record in the first slave data record set contains slave data records not found in the reconciliation data corresponding to the slave internal account, and each second slave data record in the second slave data record set contains slave data records found in the reconciliation data corresponding to the slave internal account. It determines a target key field corresponding to each first slave data record, obtains a target key field set, and assigns a target key field to each of the target key field sets. The master data record corresponding to the target key field is marked as a one-sided record; based on the second set of slave data records, a first master data record and a third slave data record with different business elements are determined, and the first master data record and the third slave data record are marked as error records respectively, wherein the business elements include at least: transaction amount; based on the second set of slave data records, a second master data record and a fourth slave data record with the same business elements are determined, and the second master data record and the fourth slave data record are marked as reconciliation records respectively; based on the first set of slave data records and the second set of slave data records, the reconciliation data corresponding to the slave internal account is checked to obtain the check result, and if the check result indicates that there is a fifth slave data record that has not been reconciled, the fifth slave data record is marked as the one-sided record; based on the one-sided record, the error record, and the reconciliation record, the reconciliation result is generated; The first matching module is used to match business rules from a pre-configured business rule engine based on the reconciliation results to obtain a matching result; if the matching result indicates that a first pending record matches a corresponding target business rule, the module processes the corresponding first pending record based on the target business rule to obtain a processing result, wherein the first pending record is either the unilateral record or the erroneous record; based on the processing result, the module adjusts the account information of the internal account corresponding to the first pending record and generates an adjustment list report; if the matching result indicates that a second pending record does not match a corresponding target business rule, the module sends the second pending record to a target terminal for processing, wherein the second pending record is either the unilateral record or the erroneous record.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the reconciliation method based on any one of claims 1 to 4.

7. An electronic device, characterized in that, It includes one or more processors and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the internal account-based reconciliation method according to any one of claims 1 to 4.

Images