Reconciliation difference processing method and device, equipment and medium

Abstract

The invention relates to the technical field of data processing, in particular to a reconciliation difference processing method and device, equipment and a medium, and is used for improving the efficiency and accuracy of reconciliation difference processing. The method comprises the following steps: in response to an account checking query condition input by a user on an interactive interface, displaying account checking difference data which is not successfully checked; and in response to a selection operation of the user on the account checking difference data, at least one type of account checking processing is performed on the account checking difference data selected by the user, and the types of the account checking processing comprise an account keeping type and a non-account keeping type.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, device, equipment and medium for processing reconciliation differences. Background Art

[0002] With the development of the financial era, business transactions between banks are becoming more and more frequent, and more and more areas involve reconciliation. The reconciliation results may be different, and the data with differences needs to be processed. At present, when processing reconciliation difference data, it is usually more focused on analyzing the causes of reconciliation differences, and more dependent on manual experience when processing difference data. When encountering complex accounts, such as a difference data involving both customer account accounting and internal account accounting, or involving a large number of accounts, relying on manual experience to process difference data has a greater risk of causing wrong accounts, and the same type of account adjustments require manual repetitive operations, and the overall efficiency of solving difference data is low. Summary of the invention

[0003] Embodiments of the present application provide a method, device, equipment and medium for processing reconciliation differences, which are used to improve the efficiency and accuracy of reconciliation difference processing.

[0004] In a first aspect, the present application provides a method for processing reconciliation differences, the method comprising:

[0005] In response to the reconciliation query conditions input by the user in the interactive interface, displaying the reconciliation difference data that has not been successfully reconciled;

[0006] In response to a user's selection operation on the reconciliation difference data, at least one type of reconciliation processing is performed on the reconciliation difference data selected by the user, wherein the types of the reconciliation processing include an accounting type and a non-accounting type.

[0007] The reconciliation difference processing method provided in this embodiment queries the reconciliation difference data by inputting the reconciliation query conditions, which is convenient for business personnel to query and analyze the reconciliation difference data and then perform subsequent reconciliation processing operations. The reconciliation difference can be queried and processed through simple selection operations, which reduces the reliance on manual experience, improves the reconciliation efficiency, and reduces the possibility of accounting errors.

[0008] In a possible embodiment, in response to the reconciliation query condition input by the user in the interactive interface, the reconciliation difference data that has not been successfully reconciled is displayed, including:

[0009] In response to a reconciliation query condition input by a user on an interactive interface, obtaining first account data and second account data that meet the reconciliation query condition;

[0010] Reconciliation processing is performed on the first accounting data and the second accounting data, and reconciliation difference data that has not been successfully reconciled is displayed.

[0011] In a possible embodiment, performing accounting type reconciliation processing on the reconciliation difference data selected by the user includes:

[0012] Query the accounting rule table according to the reconciliation group and currency corresponding to the reconciliation difference data;

[0013] If the bill details under the reconciliation group and currency match the accounting rules in the accounting rule table, accounting processing is performed according to the bill details under the reconciliation group and currency.

[0014] In a possible embodiment, if the bill details data under the reconciliation group and currency match the accounting rules in the accounting rule table, then accounting processing is performed according to the bill details data under the reconciliation group and currency, including:

[0015] Traversing the accounting rules in the accounting rule table, if the bill detail data under the reconciliation group and currency matches the accounting rule, storing the successfully matched bill detail data in the accounting detail table;

[0016] According to the accounting rules, perform accounting operations on the data in the accounting details table to generate accounting flow information;

[0017] Use the accounting engine to automatically record accounting flow information.

[0018] In a possible embodiment, the method further includes:

[0019] If the reconciliation difference data of multiple accounts correspond to the same reconciliation group and currency, the bill detail data of the multiple accounts under the reconciliation group and currency are merged, and the merged bill detail data is determined as the bill detail data under the reconciliation group and currency.

[0020] In a possible embodiment, performing non-bookkeeping reconciliation processing on the reconciliation difference data selected by the user includes:

[0021] Obtain the third accounting data and the fourth accounting data corresponding to the reconciliation difference data;

[0022] In response to a user's reconciliation operation on the third account data and the fourth account data, a reconciliation process is performed on the reconciliation difference data.

[0023] In a possible embodiment, the method further includes:

[0024] In response to a user's selection operation on the plurality of reconciliation difference data, at least one type of batch reconciliation processing is performed on the plurality of reconciliation difference data selected by the user.

[0025] In a second aspect, the present application provides a reconciliation difference processing device, the device comprising:

[0026] A query module, configured to display unreconciled reconciliation difference data in response to reconciliation query conditions input by a user in an interactive interface;

[0027] The reconciliation module is used to perform at least one type of reconciliation processing on the reconciliation difference data selected by the user in response to the user's selection operation on the reconciliation difference data, wherein the types of reconciliation processing include accounting type and non-accounting type.

[0028] As an optional implementation manner, the query module is specifically used for:

[0029] In response to a reconciliation query condition input by a user on an interactive interface, obtaining first account data and second account data that meet the reconciliation query condition;

[0030] Reconciliation processing is performed on the first accounting data and the second accounting data, and reconciliation difference data that has not been successfully reconciled is displayed.

[0031] As an optional implementation, the reconciliation module is specifically used for:

[0032] Query the accounting rule table according to the reconciliation group and currency corresponding to the reconciliation difference data;

[0033] If the bill details under the reconciliation group and currency match the accounting rules in the accounting rule table, accounting processing is performed according to the bill details under the reconciliation group and currency.

[0034] As an optional implementation, the reconciliation module is specifically used for:

[0035] Traversing the accounting rules in the accounting rule table, if the bill detail data under the reconciliation group and currency matches the accounting rule, storing the successfully matched bill detail data in the accounting detail table;

[0036] According to the accounting rules, perform accounting operations on the data in the accounting details table to generate accounting flow information;

[0037] Use the accounting engine to automatically record accounting flow information.

[0038] As an optional implementation, the reconciliation module is further configured to:

[0039] If the reconciliation difference data of multiple accounts correspond to the same reconciliation group and currency, the bill detail data of the multiple accounts under the reconciliation group and currency are merged, and the merged bill detail data is determined as the bill detail data under the reconciliation group and currency.

[0040] As an optional implementation, the reconciliation module is specifically used for:

[0041] Obtain the third accounting data and the fourth accounting data corresponding to the reconciliation difference data;

[0042] In response to a user's reconciliation operation on the third account data and the fourth account data, a reconciliation process is performed on the reconciliation difference data.

[0043] As an optional implementation, the reconciliation module is further configured to:

[0044] In response to a user's selection operation on the plurality of reconciliation difference data, at least one type of batch reconciliation processing is performed on the plurality of reconciliation difference data selected by the user.

[0045] In a third aspect, the present application provides an electronic device, including:

[0046] A memory for storing program instructions;

[0047] The processor is used to call the program instructions stored in the memory, and execute the steps included in any one of the methods in the first aspect according to the obtained program instructions.

[0048] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes any one of the methods described in the first aspect.

[0049] In a fifth aspect, the present application provides a computer program product, comprising: a computer program code, when the computer program code is run on a computer, the computer executes any one of the methods described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 A flowchart of a method for handling reconciliation differences provided in an embodiment of the present application;

[0051] Figure 2 An implementation flow chart of automatic accounting provided in an embodiment of the present application;

[0052] Figure 3 A workflow template configuration diagram provided for an embodiment of the present application;

[0053] Figure 4 A structural diagram of a device for processing reconciliation differences provided in an embodiment of the present application;

[0054] Figure 5 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

[0056] The terms "first" and "second" in the specification and claims of the present application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive protection. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. "Multiple" in the present application can mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.

[0057] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0058] In the technical solution of this application, the acquisition, transmission, storage, and use of data are in compliance with the requirements of relevant national laws and regulations.

[0059] Before introducing the reconciliation difference processing method provided in the embodiment of the present application, in order to facilitate understanding, the technical background of the embodiment of the present application is first introduced in detail below.

[0060] With the development of the financial era, business transactions between banks are becoming more and more frequent, and more and more areas involve reconciliation. The reconciliation results may be different, and the data with differences needs to be processed. At present, when processing reconciliation difference data, it is usually more focused on analyzing the causes of reconciliation differences, and more dependent on manual experience when processing difference data. When encountering complex accounts, such as a difference data involving both customer account accounting and internal account accounting, or involving a large number of accounts, relying on manual experience to process difference data has a greater risk of causing wrong accounts, and the same type of account adjustments require manual repetitive operations, and the overall efficiency of solving difference data is low.

[0061] In order to solve the above technical problems, this embodiment provides a query and processing function for reconciliation difference processing. By entering the reconciliation query conditions, the reconciliation difference data is queried, which is convenient for business personnel to query and analyze the reconciliation difference data and then perform subsequent reconciliation processing operations. The reconciliation difference can be queried and processed through simple selection operations, reducing reliance on manual experience, improving reconciliation efficiency, and reducing the possibility of accounting errors.

[0062] Reference Figure 1 The implementation process of a method for processing reconciliation differences provided in this embodiment is as follows:

[0063] Step 100: In response to the reconciliation query condition input by the user in the interactive interface, display the reconciliation difference data that has not been successfully reconciled;

[0064] In practice, this embodiment provides an interactive interface, providing the functions of querying, exporting and initiating the reconciliation processing flow of reconciliation difference data. Users can freely enter query conditions (entry date, value date, currency, amount, business number, account number, etc.) in the interactive interface to query the reconciliation difference data that has not been successfully reconciled.

[0065] In some embodiments, this embodiment displays the unreconciled reconciliation difference data in the following manner, including:

[0066] In response to the reconciliation query condition input by the user in the interactive interface, the first account data and the second account data satisfying the reconciliation query condition are obtained; the first account data and the second account data are reconciled, and the reconciliation difference data that has not been successfully reconciled is displayed.

[0067] During implementation, the corresponding first account data (understood as our data) and second account data (understood as the other party's data) are obtained based on the reconciliation query conditions input by the user, such as the entry date, interest accrual date, currency, amount, business number, account number and other information; the first account data and the second account data can be reconciled by automatically comparing the first account data and the second account data. When unsuccessfully reconciled data is queried, the unreconciled reconciliation difference data is displayed on the display interface.

[0068] Among them, our data refers to the statement data generated by local system transactions; other party data refers to the statement data provided by the external system.

[0069] Step 101: In response to a user's selection operation on the reconciliation difference data, at least one type of reconciliation processing is performed on the reconciliation difference data selected by the user, wherein the types of reconciliation processing include accounting type and non-accounting type.

[0070] Optionally, the reconciliation difference data may be displayed in a list format, wherein the reconciliation difference data includes the third account data (equivalent to our data that has not been reconciled successfully) and the fourth account data (equivalent to the other party's data that has not been reconciled successfully). The third account data and the fourth account data are displayed in two lists respectively.

[0071] Optionally, the user can continue to check the data that needs to be processed in the interface of the displayed reconciliation difference data, select the transfer position, select the reason for the difference, and initiate the reconciliation process (accounting can be done); or the user can check the data on our side and the data on the other side of the balance of debits and credits for manual reconciliation.

[0072] Optionally, the query results (reconciliation difference data) can also be exported to Excel and subsequently uploaded to the "Batch Accounting Processing to be Reconciled" page for difference processing with the same processing method (transferred to the same position for the same operation), or uploaded to "Batch Cancellation of Reconciliation Data" for reconciliation cancellation operations.

[0073] The interactive interface of this embodiment also provides the functions of querying, exporting and maintaining "reasons for reconciliation differences". When the business personnel conduct reconciliation processing, they select from the maintained "reasons for reconciliation differences" and initiate the reconciliation processing process. If a new reason for reconciliation difference appears, it must be maintained first and then displayed in the interactive interface for the user to select.

[0074] Optionally, the types of reconciliation processing in this embodiment include accounting type and non-accounting type. The user can select the accounting type of reconciliation processing to execute the automatic accounting process, and the user can also select the non-accounting type of reconciliation processing to reconcile the reconciliation difference data.

[0075] Method 1: Accounting type reconciliation process.

[0076] In some embodiments, this embodiment may also perform accounting type reconciliation processing on the reconciliation difference data selected by the user in the following manner:

[0077] 1a) querying the accounting rule table according to the reconciliation group and currency corresponding to the reconciliation difference data;

[0078] Optionally, the accounting rule table in this embodiment is pre-configured, and the pre-configured accounting rules are initialized to the accounting rule table. One or more rules are stored in the accounting rule table. As long as the reconciliation difference data matches a rule, the bill detail data corresponding to the fourth account data (the other party's reconciliation difference data) in the reconciliation difference data will be read, and the bill detail data will be automatically accounted for.

[0079] In implementation, in response to the user's touch operation on the automatic accounting button in the interactive interface, the reconciliation group and currency corresponding to the reconciliation difference data selected by the user are triggered. The reconciliation group of each account is pre-configured. When the reconciliation difference data is queried, the reconciliation group of the account corresponding to the third account data and the fourth account data corresponding to the reconciliation difference data are determined. After the reconciliation group and currency corresponding to the reconciliation difference data are determined, the pre-configured accounting rule table is queried to determine whether the reconciliation difference data matches the accounting rules in the accounting rule table.

[0080] 1b) If the bill details under the reconciliation group and currency match the accounting rules in the accounting rule table, accounting processing is performed according to the bill details under the reconciliation group and currency.

[0081] Optionally, the accounting rules in this embodiment include, but are not limited to, reconciliation group, account line code, account number, rule type, rule details, accounting type, accounting scenario, accounting scenario, difference processing reason, whether to merge accounting, and other information. Optionally, the rule type includes the method of rule verification, such as reconciliation statement notes (which can be understood as a field in the database table), MPS (Max Payload Size) message processing queue (which can be understood as the return result of a query service), etc. Optionally, the accounting type is used to indicate the type of account involved in the accounting, such as customer account, internal account, accounting event, position transfer, position interest, and others. Optionally, there are different accounting scenarios under different accounting types, such as collection, payment, automatic investment principal, automatic investment recovery, collection branch transactions, payment branch transactions, etc. Optionally, whether to merge accounting is used to distinguish between merging one-note accounting and detailed multiple-note accounting.

[0082] Each accounting scenario in this embodiment corresponds to the overall business meaning of an accounting behavior. An accounting behavior with a business meaning including an accounting type number is configured through an accounting scenario number, an accounting type, and a conditional variable. The conditional variables include a debit and credit identifier, a domestic and foreign identifier, etc. The accounting scenario number is the unique identifier of the accounting scenario. After the final accounting behavior registration is completed, it is reflected as a contract. Each accounting scenario in this embodiment corresponds to an atomic algorithm for recording an accounting entry. An accounting entry including an accounting type number, an atomic action number, an amount type number, a balance type number, and a debit and credit identifier is configured through an accounting scenario number. The accounting scenario number is the unique identifier of the accounting scenario. After the final accounting behavior registration is completed, it is reflected as a contract detail. In this embodiment, the accounting scenario configuration and the accounting scenario configuration can be centrally configured in a configuration file. By associating them through the accounting scenario number, a complete set of accounting behavior actions can be obtained, which is convenient for development and later maintenance.

[0083] During implementation, after the user selects the reconciliation difference data that needs to be reconciled, the reconciliation group and currency corresponding to the fourth account data (other party data) in the reconciliation difference data are obtained, and the bill detail data of the fourth account data that cannot be reconciled successfully under the reconciliation group and currency are queried. If the bill detail data of the fourth account data matches the accounting rules, the matching bill detail data is automatically accounted for.

[0084] In some embodiments, the primary key of the accounting rule table in this embodiment is a multi-entity identifier, a third-party account number, an account line number, a currency, and a condition sequence number. Other fields include, but are not limited to: reconciliation group, rule type (such as XXX query, XXX field), rule details (such as fixed summary of message), entry parameters (for example: interbank difference accounting type, accounting scenario number, scenario name, debit accounting scenario number, debit accounting classification, debit account number, debit reconciliation mark, debit institution number, credit accounting scenario number, credit accounting classification, credit account number, credit reconciliation mark, credit institution number, automatic accounting description (reason for reconciliation difference)), maintenance time, maintenance employee number, remarks, merged accounting mark, etc.

[0085] In some embodiments, accounting processing is performed according to the bill details data under the reconciliation group and currency in the following manner:

[0086] Step b1, traversing the accounting rules in the accounting rule table, if the bill detail data under the reconciliation group and currency matches the accounting rules, storing the successfully matched bill detail data in the accounting detail table;

[0087] In implementation, when matching the reconciliation difference data with the accounting rules, the bill details of the other party's data under the reconciliation group and currency can be selected to match with the accounting rules, so as to automatically account for the data in the successfully matched bill details. In implementation, the accounting rule table is traversed, and the bill details list of the other party's data in the reconciliation group, other party account number, account line, currency, and multi-entity information query processing of a single accounting rule is traversed to match the accounting rule one by one.

[0088] Among them, the accounting rule matching logic is as follows:

[0089] If the rule type is statement remark, that is, use the expression to directly match the remark field of the other party's bill detail data and the rule details of this rule; if the rule type is MPS message processing queue, that is, query the outbound call interface, and judge whether the match is successful according to the returned information. You can query a third party and carry account information, so as to use the third party to judge whether the match is successful, and judge whether the match is successful according to the information returned by the third party. When the match is successful, the successfully matched bill detail data will be automatically added to the accounting detail table under the current accounting rule.

[0090] Step b2: perform accounting operations on the data in the accounting details table according to the accounting rules to generate accounting flow information;

[0091] During implementation, after traversing the bill details under a single accounting rule, first add the successfully matched bill details to the accounting details table, and then perform accounting operations on the data in the accounting details table according to the accounting scenario in the accounting rule to generate accounting flow information (such as an accounting flow table). If the accounting scenario is to merge one note into one account, then register one record into the accounting flow table, and net the difference amount of the other party's bill details in the accounting details table according to the credit plus debit minus, and take the absolute value of the amount, and take the latest record for the interest date and entry date. If the accounting scenario is to account for multiple notes in detail, then register the other party's bill details into the accounting flow table one by one.

[0092] Optionally, each accounting scenario in this embodiment corresponds to an atomic algorithm for recording an accounting entry. An accounting entry including an accounting type number, an atomic action number, an amount type number, a balance type number, and a debit and credit mark is configured by the accounting scenario number. The accounting scenario number is a unique identifier for the accounting scenario. After the final accounting behavior registration is completed, it is reflected in the contract details.

[0093] Step b3: Use the accounting engine to automatically record the accounting flow information.

[0094] In implementation, after the automatic accounting is successful, the accounting flow table is scanned asynchronously, and the accounting engine (accounting service) is called out for automatic accounting. The accounting process of the accounting engine and the generation of accounting flow information are asynchronous, that is, the threads used are different.

[0095] In some embodiments, this embodiment can also perform batch accounting of the same group reconciliation group, as shown below:

[0096] If the reconciliation difference data of multiple accounts correspond to the same reconciliation group and currency, the bill detail data of the multiple accounts under the reconciliation group and currency are merged, and the merged bill detail data is determined as the bill detail data under the reconciliation group and currency.

[0097] Optionally, the accounting details table in this embodiment is used to register the details of automatic accounting. The primary key is the multi-entity identifier, the primary key of the other party's bill details table (other party's bill details sequence number). Other fields are the primary key of the automatic accounting rule parameters (other party account number, account line number, currency, condition sequence number), summary accounting flag, remarks, outbound call response code, outbound call response description, global event tracking number, sub-transaction sequence number, and other fields of the other party's bill details table.

[0098] Optionally, the accounting flow information (such as the accounting flow table) in this embodiment is used to register the flow of automatic accounting, and one flow can correspond to multiple details. The primary key is the multi-entity identifier, the global event tracking number, and the sub-transaction sequence number. Other fields include the other party's bill detail sequence number, the automatic accounting rule parameter primary key (the other party's account number, account line number, currency, condition sequence number), reconciliation group, accounting amount, accounting parameters (interbank difference accounting type, accounting scenario number, scenario name, debit accounting scenario number, debit accounting classification, debit account number, debit reconciliation mark, debit institution number, credit accounting scenario number, credit accounting classification, credit account number, credit reconciliation mark, credit institution number, automatic accounting description (reason for reconciliation difference)), remarks, outbound call response code, outbound call response description, processing status (pending, pending, processing completed), accounting status, interest date, entry date, our business number, other party's business number, teller number.

[0099] In some embodiments, this embodiment also designs an online batch processing control table, which relies on the scanning mechanism to asynchronously process online transactions initiated by the page, and the primary key is the multi-entity identifier, the global event tracking number, and the sub-transaction sequence number. Other fields include transaction date, task submission time, transaction agency, task status, record lock flag, transaction service code, entry teller, transaction context, and timestamp.

[0100] like Figure 2 As shown, this embodiment provides an implementation process of automatic accounting, as shown below:

[0101] Step 200: Initialize the accounting rules to the accounting rules table;

[0102] Step 201: In response to the automatic accounting instruction triggered by the user in the interactive interface, the reconciliation group and currency of the reconciliation difference data selected by the user are obtained, and the reconciliation group and currency are registered in the online batch processing control table;

[0103] Step 202, asynchronously scanning the online batch processing control table, querying the online batch processing control table records whose task status is unprocessed and whose record lock flag is unlocked for processing;

[0104] Step 203: Update the other party's bill details under the reconciliation group and currency to a status to be recorded;

[0105] Step 204: query the accounting rule table by reconciliation group and currency to determine whether the accounting rule table exists. If so, execute step 205; otherwise, execute step 210;

[0106] Step 205: Match the bill details under the reconciliation group and currency with the accounting rules in the accounting rule table;

[0107] Step 206: Add the successfully matched bill details to the accounting details table;

[0108] Step 207: Add the bill details in the accounting details table to the accounting flow table according to the accounting scenario;

[0109] Step 208: Update the status of the other party's bill details data under the reconciliation group and currency;

[0110] Step 209: Asynchronously scan the accounting flow table, query the records to be processed, and call the outbound accounting service to perform accounting;

[0111] The accounting service includes the accounting engine.

[0112] Step 210: Update the other party's bill details data back to the state of waiting for the first billing.

[0113] During implementation, this embodiment can obtain the accounting scenario number of each contract detail according to the accounting type and the accounting scenario number, and obtain the accounting scenario according to the accounting scenario number, that is, obtain an atomic algorithm for recording accounting entries to complete the registration of accounting entries.

[0114] Method 2: Non-bookkeeping reconciliation process.

[0115] In some embodiments, this embodiment may perform non-bookkeeping reconciliation processing on the reconciliation difference data selected by the user in the following manner:

[0116] 2a) Obtaining the third accounting data and the fourth accounting data corresponding to the reconciliation difference data;

[0117] The third accounting data in this embodiment represents data in our data that has not been successfully reconciled, and the fourth accounting data represents data in the other party's data that has not been successfully reconciled.

[0118] 2b) In response to the user's reconciliation operation on the third account data and the fourth account data, reconciliation processing is performed on the reconciliation difference data.

[0119] In some embodiments, this embodiment can also perform batch processing on multiple reconciliation difference data, as shown below:

[0120] In response to a user's selection operation on the plurality of reconciliation difference data, at least one type of batch reconciliation processing is performed on the plurality of reconciliation difference data selected by the user.

[0121] In some embodiments, this embodiment may also perform any one or more of the following operations on the unreconciled reconciliation difference data:

[0122] (1) Reconciliation difference accounting correction, used to provide the function of reversing difference accounting.

[0123] (2) Reconciliation data query and single cancellation, used to provide the functions of reconciliation data query and single cancellation.

[0124] (3) Batch cancellation of reconciliation data, used to provide the function of batch cancellation of reconciliation data.

[0125] (4) Reconciliation data supplement, used to provide the function of manual entry of reconciliation data.

[0126] This embodiment also provides an interactive page design for reconciliation differences, including the following functions:

[0127] Function 1: Reconciliation difference data maintenance, providing "reconciliation difference reason" query, export and maintenance functions.

[0128] During implementation, business personnel need to select from the maintained "Reconciliation Difference Reasons" when handling differences before initiating the difference handling process. If a new reconciliation difference reason appears, it needs to be maintained first.

[0129] Function 2: Processing of accounts to be reconciled, providing functions for querying and exporting reconciliation difference data and initiating the reconciliation difference processing process.

[0130] During implementation, business personnel can freely enter query conditions (entry date, interest date, currency, amount, business number, account number, etc.) to query the reconciliation difference data that has not been successfully reconciled. The query results are displayed in two lists: our data and other party's data. Business personnel check the reconciliation difference data to be processed, select the transfer position, select the difference reason, and initiate the difference processing process (which can be recorded); they can also check the debit and credit balance of our data and other party's data for manual reconciliation. The query results can also be exported to Excel, and then uploaded to the "Batch Accounts to be Reconciled" page for difference processing in the same processing method (transfer to the same position for the same operation), or uploaded to the "Batch Cancellation of Reconciliation Data" for reconciliation cancellation.

[0131] Optionally, the transfer positions in this embodiment are divided into two categories: accounting positions and non-accounting positions. The accounting position is used to enter the reconciliation process of the accounting type. Users can manually fill in the accounting information or automatically obtain the accounting information. Accounting information includes but is not limited to accounting types (such as others, investment policy transfers, investment policy interest, each type includes multiple accounting scenarios, and different scenarios have different accounting methods and natures), accounting scenarios, account information, reasons for differences, amounts, accounting notes, consolidated accounting, interest accrual dates, etc. Users can select different accounting scenarios, and the page will reflect the corresponding transfer-out accounts and transfer-in accounts specified by the business rules. The amount will also be reflected after calculation based on the selected data, which is convenient for business operations, and business personnel do not need to enter the account information again. The non-accounting position is used to enter the reconciliation process of the non-accounting type. Users can fill in the "reasons for reconciliation differences" and "circulation opinions" (select from the menu item).

[0132] Function 3: Batch processing of accounts to be reconciled, used to provide the process initiation function for processing the same type of reconciliation difference data.

[0133] During implementation, users can first download our data and other party's data on the "Account Processing to be Reconciled" page; fill in "Remarks" (that is, data with the same remarks are grouped as a difference process) and "Reason for Difference" in the bill details of our data and other party's data. The difference reasons for the same remarks are the same. Users upload their bill details and other party's bill details, click "Start Transfer", and a pop-up window will pop up to select the transfer position to initiate the difference processing process.

[0134] Function 4, reconciliation difference details, is used to provide detailed information and processing functions of the current difference processing process.

[0135] Among them, users can check the difference processing record to be processed by the current position through the "Personal To-Do" or "Difference Processing" page, and jump to the "Reconciliation Difference Details" page. The page displays the difference number, initiation time, difference process status, our data list, other party's data list, difference processing process list and the authority functions of the current position (circulation, end, reconciliation, return to the previous level, return to the initiator, authorization, handling, review).

[0136] like Figure 3 As shown, this embodiment also provides a workflow template configuration diagram, in which the workflow is managed and executed through the workflow engine, the flow nodes are not fixed, and the processing positions and processors are parameterized and configured, and can be infinitely circulated before the process ends and is reviewed. The workflow scene is centrally configured as an enumeration class, and the attributes are template number, scene description, node direction (0-new, 1-one-way node flow, 2-terminate, 3-rollback, 4-two-way node flow), and routing line number (i.e., the arrow in the workflow template). The difference processing type (flow, end, reconciliation, return to the previous level, return to the initiator, authorization, handling, review) and position number are used to control the difference processing operation authority of the current business personnel. Each step of the difference processing process is registered and queried through the difference processing process table, including information such as the processor, processing position, reconciliation difference reason, flow opinion, accounting scene, accounting notes, amount, receiving time, completion time, etc. The current difference processing information is stored in the difference processing table. The accounting process for difference processing is: the reconciliation post transfers to the accounting post to initiate the transfer -> the supervisor post authorizes -> the accounting processing post handles it -> the accounting processing post reviews it.

[0137] During implementation, the transfer function is used to transfer the difference processing process to the next position for processing, call the submission method of the workflow engine, assign the processing position of the next node, and the data status in the transfer is that the transfer has been locked. The operation position is generally the reconciliation position. It can be transferred to a non-accounting position, that is, the current position not only transfers but also does not process. It can also be transferred to an accounting position, that is, fill in the accounting parameter information and initiate the difference processing accounting. The end function is used to end the current difference processing process, call the workflow engine, terminate the entire workflow, and update the data status to non-first reconciliation. The reconciliation function is used to select the difference processing data for manual reconciliation. The manual reconciliation remarks need to be filled in. Manual reconciliation only focuses on the amount, that is, the balance of debits and credits (the total amount calculated by obtaining each data of our party and the other party is 0), and does not pay attention to other reconciliation conditions. When the reconciliation is successful, the data status is updated to manual reconciliation success. The return to previous level function is used to return the current difference processing process to the previous processing position, call the workflow engine, query the processing position of the previous node through the difference processing process table, and assign it to the processing position of the next node. The data status is locked for transfer. The return to initiator function is used to return the current difference processing process to the process initiator, call the workflow engine, query the processing position of the first node of the process through the difference processing process table, and assign it to the processing position of the next node. The data status is locked for transfer. The authorization function is used to review the authorization operation for initiating difference processing accounting. Call the workflow engine and assign the processing position of the next node to the accounting processing position. The data status is locked for transfer. The handling function is used to conduct the initial review of the difference processing accounting. At this time, the accounting information can also be modified. Call the workflow engine and assign the processing position of the next node to the accounting processing position. The data status is locked for transfer. The review function is used to conduct a final review of the difference processing accounting. At this time, you can only view but not modify the information. If the review is passed, the accounting element information is obtained from the request, the contract and contract details are assembled, and the accounting interface is called for accounting processing; when the accounting is successful, the data status is updated to the difference reconciliation success. During the review, a difference processing accounting is a contract, and the borrowing and lending parties in an accounting scenario are a group of contract details. The number of contract details is determined by the request parameter "merge accounting". If one accounting is merged, there is only one group of contract details, and the amount is the total absolute value of our data after the other party's data is calculated (the total debit amount of our data-the total credit amount of our data-the total debit amount of the other party's data + the total credit amount of the other party's data); if there are multiple records in the details, the amount is the amount of each reconciliation data, and the contract details are multiple groups.

[0138] This embodiment provides the function of querying and processing reconciliation difference data. By entering conditions such as date and currency, our data and the other party's data can be queried. The interface is divided into two lists for clear display, and it also supports excel download to local viewing. Based on manual experience, the reasons for reconciliation differences are parameterized and maintained. After the business personnel query and analyze the reconciliation difference data, they match the reasons for the reconciliation differences and can perform corresponding subsequent operations. The difference processing function is comprehensive and complete. Based on business rules and accounting rules, the accounting logic is configured into an accounting scenario. When accounting adjustments are required, business personnel only need to select the correct accounting scenario and simply fill in the accounting information to complete the difference processing accounting of a single or multiple accounting scenarios. The difference processing accounting process is circulated and reviewed by multiple positions, reducing the possibility of accounting errors.

[0139] On the one hand, this embodiment can provide an automatic accounting process for initializing automatic accounting rule parameters, initiating automatic accounting for difference processing, matching automatic accounting rules, and outbound accounting. When the reconciliation difference data is queried, automatic accounting can be achieved through the automatic accounting process to improve the efficiency of reconciliation processing. On the other hand, this embodiment can also parameterize and maintain the reasons for reconciliation differences. When business personnel handle differences, they can match the reasons for reconciliation differences and perform corresponding processing, making difference processing more efficient and convenient. This embodiment configures the accounting logic into an accounting scenario to reduce manual input elements. Even for complex accounting processing logic, business personnel only need to initiate simple difference processing accounting, which improves work efficiency and reduces error rate. This embodiment has low development difficulty, and the reconciliation difference processing function is complete. Business personnel can use the present invention to perform difference processing operations.

[0140] Based on the same inventive concept, the present application embodiment provides a reconciliation difference processing device, please refer to Figure 4 , the device comprises:

[0141] The query module 400 is used to display the reconciliation difference data that has not been successfully reconciled in response to the reconciliation query conditions entered by the user in the interactive interface;

[0142] The reconciliation module 401 is used for performing at least one type of reconciliation processing on the reconciliation difference data selected by the user in response to the user's selection operation on the reconciliation difference data, wherein the types of reconciliation processing include accounting type and non-accounting type.

[0143] As an optional implementation, the query module 400 is specifically used for:

[0144] In response to a reconciliation query condition input by a user on an interactive interface, obtaining first account data and second account data that meet the reconciliation query condition;

[0145] Reconciliation processing is performed on the first accounting data and the second accounting data, and reconciliation difference data that has not been successfully reconciled is displayed.

[0146] As an optional implementation, the reconciliation module 401 is specifically used for:

[0147] Query the accounting rule table according to the reconciliation group and currency corresponding to the reconciliation difference data;

[0148] If the bill details under the reconciliation group and currency match the accounting rules in the accounting rule table, accounting processing is performed according to the bill details under the reconciliation group and currency.

[0149] As an optional implementation, the reconciliation module 401 is specifically used for:

[0150] Traversing the accounting rules in the accounting rule table, if the bill detail data under the reconciliation group and currency matches the accounting rule, storing the successfully matched bill detail data in the accounting detail table;

[0151] According to the accounting rules, perform accounting operations on the data in the accounting details table to generate accounting flow information;

[0152] Use the accounting engine to automatically record accounting flow information.

[0153] As an optional implementation, the reconciliation module 401 is further configured to:

[0154] If the reconciliation difference data of multiple accounts correspond to the same reconciliation group and currency, the bill detail data of the multiple accounts under the reconciliation group and currency are merged, and the merged bill detail data is determined as the bill detail data under the reconciliation group and currency.

[0155] As an optional implementation, the reconciliation module 401 is specifically used for:

[0156] Obtain the third accounting data and the fourth accounting data corresponding to the reconciliation difference data;

[0157] In response to a user's reconciliation operation on the third account data and the fourth account data, a reconciliation process is performed on the reconciliation difference data.

[0158] As an optional implementation, the reconciliation module 401 is further configured to:

[0159] In response to a user's selection operation on the plurality of reconciliation difference data, at least one type of batch reconciliation processing is performed on the plurality of reconciliation difference data selected by the user.

[0160] Based on the same inventive concept, the present application embodiment provides an electronic device, which can implement the reconciliation difference processing function discussed above, please refer to Figure 5, the device comprises a processor 501 and a memory 502, wherein:

[0161] Memory 502, used for storing program instructions;

[0162] The processor 501 is used to call the program instructions stored in the memory, and execute the following steps according to the obtained program instructions:

[0163] In response to the reconciliation query conditions input by the user in the interactive interface, displaying the reconciliation difference data that has not been successfully reconciled;

[0164] In response to a user's selection operation on the reconciliation difference data, at least one type of reconciliation processing is performed on the reconciliation difference data selected by the user, wherein the types of the reconciliation processing include an accounting type and a non-accounting type.

[0165] As an optional implementation manner, the processor 501 is specifically configured to execute:

[0166] In response to a reconciliation query condition input by a user on an interactive interface, obtaining first account data and second account data that meet the reconciliation query condition;

[0167] Reconciliation processing is performed on the first accounting data and the second accounting data, and reconciliation difference data that has not been successfully reconciled is displayed.

[0168] As an optional implementation manner, the processor 501 is specifically configured to execute:

[0169] Query the accounting rule table according to the reconciliation group and currency corresponding to the reconciliation difference data;

[0170] If the bill details under the reconciliation group and currency match the accounting rules in the accounting rule table, accounting processing is performed according to the bill details under the reconciliation group and currency.

[0171] As an optional implementation manner, the processor 501 is specifically configured to execute:

[0172] Traversing the accounting rules in the accounting rule table, if the bill detail data under the reconciliation group and currency matches the accounting rule, storing the successfully matched bill detail data in the accounting detail table;

[0173] According to the accounting rules, perform accounting operations on the data in the accounting details table to generate accounting flow information;

[0174] Use the accounting engine to automatically record accounting flow information.

[0175] As an optional implementation manner, the processor 501 is further configured to execute:

[0176] If the reconciliation difference data of multiple accounts correspond to the same reconciliation group and currency, the bill detail data of the multiple accounts under the reconciliation group and currency are merged, and the merged bill detail data is determined as the bill detail data under the reconciliation group and currency.

[0177] As an optional implementation manner, the processor 501 is specifically configured to execute:

[0178] Obtain the third accounting data and the fourth accounting data corresponding to the reconciliation difference data;

[0179] In response to a user's reconciliation operation on the third account data and the fourth account data, a reconciliation process is performed on the reconciliation difference data.

[0180] As an optional implementation manner, the processor 501 is further configured to execute:

[0181] In response to a user's selection operation on the plurality of reconciliation difference data, at least one type of batch reconciliation processing is performed on the plurality of reconciliation difference data selected by the user.

[0182] Based on the same inventive concept, the embodiment of the present application provides a computer-readable storage medium, and the computer program product includes: computer program code, when the computer program code is executed on a computer, the computer executes any of the above-mentioned methods for handling account reconciliation differences. Since the principle of solving the problem by the above-mentioned computer-readable storage medium is similar to that of the method for handling account reconciliation differences, the implementation of the above-mentioned computer-readable storage medium can refer to the implementation of the method, and the repeated parts will not be repeated.

[0183] Based on the same inventive concept, the embodiment of the present application also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, the computer executes any of the above-mentioned methods for handling account reconciliation differences. Since the principle of solving the problem by the above-mentioned computer program product is similar to that of the method for handling account reconciliation differences, the implementation of the above-mentioned computer program product can refer to the implementation of the method, and the repeated parts will not be repeated.

[0184] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0185] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0186] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0187] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of user-operated steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0188] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for processing reconciliation differences, characterized in that: The method includes: In response to the reconciliation query conditions input by the user in the interactive interface, displaying the reconciliation difference data that has not been successfully reconciled; In response to a user's selection operation on the reconciliation difference data, at least one type of reconciliation processing is performed on the reconciliation difference data selected by the user, wherein the types of the reconciliation processing include an accounting type and a non-accounting type.

2. The method according to claim 1, characterized in that In response to the reconciliation query conditions entered by the user in the interactive interface, the reconciliation difference data that failed to be reconciled is displayed, including: In response to a reconciliation query condition input by a user on an interactive interface, obtaining first account data and second account data that meet the reconciliation query condition; Reconciliation processing is performed on the first accounting data and the second accounting data, and reconciliation difference data that has not been successfully reconciled is displayed.

3. The method according to claim 1, characterized in that Perform accounting type reconciliation processing on the reconciliation difference data selected by the user, including: Query the accounting rule table according to the reconciliation group and currency corresponding to the reconciliation difference data; If the bill details under the reconciliation group and currency match the accounting rules in the accounting rule table, accounting processing is performed according to the bill details under the reconciliation group and currency.

4. The method according to claim 3, characterized in that If the bill details data under the reconciliation group and currency match the accounting rules in the accounting rule table, then accounting processing is performed according to the bill details data under the reconciliation group and currency, including: Traversing the accounting rules in the accounting rule table, if the bill detail data under the reconciliation group and currency matches the accounting rule, storing the successfully matched bill detail data in the accounting detail table; According to the accounting rules, perform accounting operations on the data in the accounting details table to generate accounting flow information; Use the accounting engine to automatically record accounting flow information.

5. The method according to claim 3, characterized in that: The method further comprises: If the reconciliation difference data of multiple accounts correspond to the same reconciliation group and currency, the bill detail data of the multiple accounts under the reconciliation group and currency are merged, and the merged bill detail data is determined as the bill detail data under the reconciliation group and currency.

6. The method according to claim 1, characterized in that Perform non-bookkeeping reconciliation processing on the reconciliation difference data selected by the user, including: Obtain the third accounting data and the fourth accounting data corresponding to the reconciliation difference data; In response to a user's reconciliation operation on the third account data and the fourth account data, a reconciliation process is performed on the reconciliation difference data.

7. The method according to claim 1, characterized in that The method further comprises: In response to a user's selection operation on the plurality of reconciliation difference data, at least one type of batch reconciliation processing is performed on the plurality of reconciliation difference data selected by the user.

8. A device for processing reconciliation differences, characterized in that: The device includes: A query module, configured to display unreconciled reconciliation difference data in response to reconciliation query conditions input by a user in an interactive interface; The reconciliation module is used to perform at least one type of reconciliation processing on the reconciliation difference data selected by the user in response to the user's selection operation on the reconciliation difference data, wherein the types of reconciliation processing include accounting type and non-accounting type.

9. The device according to claim 8, characterized in that The query module is specifically used for: In response to a reconciliation query condition input by a user on an interactive interface, obtaining first account data and second account data that meet the reconciliation query condition; Reconciliation processing is performed on the first accounting data and the second accounting data, and reconciliation difference data that has not been successfully reconciled is displayed.

10. The device according to claim 8, characterized in that The reconciliation module is specifically used for: Query the accounting rule table according to the reconciliation group and currency corresponding to the reconciliation difference data; If the bill details under the reconciliation group and currency match the accounting rules in the accounting rule table, accounting processing is performed according to the bill details under the reconciliation group and currency.

11. The device according to claim 10, characterized in that The reconciliation module is specifically used for: Traversing the accounting rules in the accounting rule table, if the bill detail data under the reconciliation group and currency matches the accounting rule, storing the successfully matched bill detail data in the accounting detail table; According to the accounting rules, perform accounting operations on the data in the accounting details table to generate accounting flow information; Use the accounting engine to automatically record accounting flow information.

12. The device according to claim 10, characterized in that The reconciliation module is also specifically used for: If the reconciliation difference data of multiple accounts correspond to the same reconciliation group and currency, the bill detail data of the multiple accounts under the reconciliation group and currency are merged, and the merged bill detail data is determined as the bill detail data under the reconciliation group and currency.

13. The device according to claim 8, characterized in that The reconciliation module is specifically used for: Obtain the third accounting data and the fourth accounting data corresponding to the reconciliation difference data; In response to a user's reconciliation operation on the third account data and the fourth account data, a reconciliation process is performed on the reconciliation difference data.

14. The device according to claim 8, characterized in that The reconciliation module is also specifically used for: In response to a user's selection operation on the plurality of reconciliation difference data, at least one type of batch reconciliation processing is performed on the plurality of reconciliation difference data selected by the user.

15. An electronic device, characterized in that: include: A memory for storing program instructions; A processor is used to call the program instructions stored in the memory, and execute the steps included in any one of claims 1-7 according to the obtained program instructions.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method according to any one of claims 1 to 7.

17. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is enabled to execute the method according to any one of claims 1 to 7.

Images