Information processing system and method

Abstract

The embodiment of the present application provides an information processing system and method, including: an information item attribution subsystem, a business subsystem and a general ledger subsystem, the information item attribution subsystem and the business subsystem are communicatively connected, and the business subsystem and the general ledger subsystem are communicatively connected; the information item attribution subsystem, the business subsystem and the general ledger subsystem are all installed with a scheduling tool, the scheduling tool is used to trigger the subsystem on which the scheduling tool is installed to execute a target operation when a target file or a target message is monitored, thereby realizing automatic carry-forward processing of accounting information when an information item in the information item attribution subsystem changes, which not only avoids the problems of high error rate and high cost due to manual participation, but also improves the processing efficiency of accounting information.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data processing technology, and in particular, to an information processing system and method. Background Art

[0002] The chart of accounts (COA) refers to a collection of accounting accounts that classify and account for the specific contents of accounting elements according to the content of economic activities and the requirements of economic management. Each COA includes a series of fields. The selection of fields is determined by the accounting dimension, and the value of each field is limited by the corresponding value range.

[0003] Due to business statistics needs or financial external reporting needs, the values ​​of certain COA fields in the accounts will be changed in daily business activities. In the prior art, the account information is changed in a semi-automatic manner. Specifically, the information item attribution subsystem pushes the change information to the business subsystem and the general ledger subsystem, and the business subsystem and the general ledger subsystem manually implement the account transfer processing of the COA segment value change.

[0004] However, due to the high degree of manual involvement in the prior art, there are problems of high error rate and low efficiency. Summary of the invention

[0005] The embodiments of the present application provide an information processing system and method to solve the problems of high error rate and low efficiency in the prior art.

[0006] In a first aspect, an embodiment of the present application provides an information processing system, including: an information item attribution subsystem, a business subsystem, and a general ledger subsystem;

[0007] The information item attribution subsystem is communicatively connected with the business subsystem, and the business subsystem is communicatively connected with the general ledger subsystem; the information item attribution subsystem, the business subsystem and the general ledger subsystem are all installed with a scheduling tool, and the scheduling tool is used to trigger the subsystem on which the scheduling tool is installed to perform a target operation when a target file or target message is monitored.

[0008] Optionally, a first scheduling tool is installed on the information item attribution subsystem, and the first scheduling tool is used to:

[0009] When a list of information item changes is monitored, triggering the information item belonging subsystem to perform a first target operation;

[0010] Wherein, the information item change list includes the name of the target information item and the change content;

[0011] The first target operation includes:

[0012] According to the information item change list, changing the target information item in the subsystem to which the information item belongs;

[0013] Determining the business subsystem including the target information item according to the pre-stored correspondence between the information item and the business subsystem;

[0014] The information item change list is sent to the business subsystem including the target information item.

[0015] Optionally, a second scheduling tool is installed on the business subsystem, and the second scheduling tool is used to:

[0016] When the list of changes to the information items is monitored, triggering the business subsystem to perform a second target operation;

[0017] Wherein, the second target operation includes:

[0018] storing the information item change list;

[0019] On the next day, the target information item in the business subsystem is changed according to the information item change list;

[0020] The account transfer flow generated during the change of the target information item is sent to the general ledger subsystem.

[0021] Optionally, a third scheduling tool is installed on the general ledger subsystem, and the third scheduling tool is used to:

[0022] When the account carry-over flow is detected, the general ledger subsystem is triggered to perform the third target operation;

[0023] Wherein, the third target operation includes:

[0024] According to the received account carry-over flow, the account information in the general ledger subsystem is carried forward to obtain the general ledger balance of the general ledger subsystem.

[0025] Optionally, the third scheduling tool is further used to:

[0026] When it is monitored that the general ledger subsystem has completed the execution of the third target operation, triggering the general ledger subsystem to execute the fourth target operation;

[0027] Among them, the fourth target operation includes:

[0028] Obtain the total balance of the sub-accounts of the business subsystem that generates the account carry-forward flow;

[0029] Checking the total balance of the sub-accounts with the general ledger balance of the general ledger subsystem;

[0030] The verification result is fed back to the business subsystem that generates the account transfer flow.

[0031] Optionally, the information item belongs to a subsystem that is a customer information system, and the target information item is a customer type.

[0032] In a second aspect, an embodiment of the present application provides an information processing method, which is applied to an information item attribution subsystem, and the method includes:

[0033] Obtaining an information item change list, wherein the information item change list includes a name of a target information item and a change content;

[0034] According to the information item change list, the target information item in the system is changed;

[0035] Determining the business subsystem including the target information item according to the pre-stored correspondence between the information item and the business subsystem;

[0036] The information item change list is sent to the business subsystem including the target information item.

[0037] Optionally, sending the information item change list to a business subsystem including the target information item includes:

[0038] The information item change list is sent to the business subsystem including the target information item in the form of a message or a file.

[0039] Optionally, the changed content is the value range of the target information item.

[0040] In a third aspect, an embodiment of the present application provides an information processing method, which is applied to a business subsystem, and the method includes:

[0041] storing the received information item change list, wherein the information item change list includes the name of the target information item and the change content;

[0042] On the next day, the target information item in the system is changed according to the information item change list;

[0043] The account transfer flow generated during the change of the target information item is sent to the general ledger subsystem.

[0044] Optionally, sending the account transfer flow generated during the change of the target information item to the general ledger subsystem includes:

[0045] The account transfer flow generated during the change of the target information item is sent to the general ledger subsystem through the accounting engine.

[0046] Optionally, sending the account transfer flow generated during the change of the target information item to the general ledger subsystem includes:

[0047] The account transfer flow generated during the change of the target information item is sent to the general ledger subsystem in the form of a message or a file.

[0048] Optionally, the changed content is the value range of the target information item.

[0049] In a fourth aspect, an embodiment of the present application provides an information processing method, which is applied to a general ledger subsystem, and the method includes:

[0050] According to the received account carry-over flow, the account information in the system is carried forward to obtain the general ledger balance of the general ledger subsystem;

[0051] Obtain the total balance of the sub-accounts of the business subsystem that generates the account carry-forward flow;

[0052] Checking the total balance of the sub-accounts with the general ledger balance of the general ledger subsystem;

[0053] The verification result is fed back to the business subsystem that generates the account transfer flow.

[0054] The information processing system provided by the embodiment of the present application includes: an information item attribution subsystem, a business subsystem and a general ledger subsystem, the information item attribution subsystem and the business subsystem are communicatively connected, and the business subsystem and the general ledger subsystem are communicatively connected; the information item attribution subsystem, the business subsystem and the general ledger subsystem are all installed with scheduling tools, the scheduling tools are used to trigger the subsystem on which the scheduling tools are installed to perform the target operation when the target file or target message is monitored, and when the information item in the information item attribution subsystem changes, the automatic carry-over processing of the accounting information is realized, which not only avoids the problems of high error rate and high cost caused by manual participation, but also improves the processing efficiency of the accounting information, and because the business subsystem and the general ledger subsystem can complete the change of the accounting information on the same day, a series of problems caused by the inconsistency between the general ledger information and the sub-ledger information are reduced, and the coordination cost is reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 A schematic diagram of the structure of the information processing system provided in Example 1 of the present application;

[0056] Figure 2 A flowchart of an information processing method provided in Embodiment 2 of the present application;

[0057] Figure 3 A flowchart of the information processing method provided in Example 3 of the present application;

[0058] Figure 4 A flowchart of an information processing method provided in Embodiment 4 of the present application;

[0059] Figure 5 A schematic diagram of the overall processing logic of the information processing system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only the parts related to the present application, rather than all structures, are shown in the accompanying drawings.

[0061] Taking customer information changes as an example, in the prior art, the changes to the sub-account data in the business subsystem (or contract system) and the general ledger data in the general ledger system are realized in a semi-automatic manner. Specifically, the business subsystem or the general ledger system automatically receives the change file of the customer information system, selects the related sub-account data (or general ledger data) after manual verification, and makes changes to the customer information segment at the sub-account level (or general ledger level). It can be seen that the semi-automatic method used in the prior art has a large degree of manual intervention. On the one hand, it is difficult to ensure that the sub-account and the general ledger complete their respective modifications on the same day, and the coordination cost is very high. On the other hand, there are problems of high error rate and low processing efficiency.

[0062] The main idea of ​​the technical solution of the present application: Based on the problems existing in the prior art, the technical solution provided by the embodiment of the present application, by deploying scheduling tools in each system, each scheduling tool is triggered by an external file (or message), and when the target external file (or message) is received, the trigger system performs a pre-set operation, thereby ensuring the automatic connection between the information item attribution subsystem, the business subsystem and the general ledger subsystem, and realizing the automatic transfer of account information when the information item changes. Compared with the prior art, it not only reduces the error rate, improves the efficiency of information change, and saves costs, but also because the business subsystem and the general ledger subsystem can complete the change of account information on the same day, it also reduces a series of problems caused by the inconsistency between the general ledger information and the sub-ledger information, and reduces the coordination cost.

[0063] Embodiment 1

[0064] Figure 1 This is a schematic diagram of the structure of the information processing system provided in Example 1 of the present application, such as Figure 1 As shown, the information processing system 10 of this embodiment includes: multiple information item attribution subsystems 11, multiple business subsystems 12 and a general ledger subsystem 13.

[0065] Among them, the information item belonging subsystem 11 refers to the source system of each information item in the general ledger subsystem 13. For example, the general ledger subsystem 13 includes information items including customer type and institution number, and the customer type belongs to the customer information system, and the institution number field belongs to the institution employee system. Then the customer information subsystem and the institution employee subsystem are the two information item belonging subsystems 11 corresponding to the general ledger subsystem 13.

[0066] In this embodiment, the information item, namely the COA field, corresponds to different accounting dimensions of account information.

[0067] The business subsystem 12 is a system for implementing specific business processing, such as a deposit system for processing deposit business, a tax system for processing tax business, etc.

[0068] The general ledger subsystem 13 is a system that summarizes the accounts of each business subsystem.

[0069] In this embodiment, scheduling tools are installed on the information item attribution subsystem 11, the business subsystem 12 and the general ledger subsystem 13. The scheduling tools are used to trigger the subsystem on which the scheduling tools are installed to perform the target operation when the target file or target message is monitored, thereby realizing the automatic connection of the information item attribution subsystem 11, the business subsystem 12 and the general ledger subsystem 13, ensuring that when the information item in the information item attribution subsystem 11 changes, the business subsystem 12 and the general ledger subsystem 13 can automatically perform corresponding operations under the triggering of the scheduling tool to complete the automatic transfer processing of the account information. Since no human participation is required, the error rate is reduced, the efficiency of changing the account information is improved, and the cost is saved.

[0070] The scheduling tool is a software tool developed in advance and deployed in the corresponding subsystem, which is responsible for scheduling related tasks in the corresponding subsystem, so that the subsystem can do specified things at a specified time. Optionally, the scheduling tool used in the embodiment of the present application can be one of Quartz, Airflow, Azkaban, Oozie, Hamake, Cascading, etc. For the convenience of distinction, in this embodiment, the scheduling tool installed in the information item attribution subsystem 11 is called the first scheduling tool, the scheduling tool installed on the business subsystem 12 is called the second scheduling tool, and the scheduling tool installed on the general ledger subsystem 13 is called the third scheduling tool. The first scheduling tool, the second scheduling tool and the third scheduling tool are all scheduling tools triggered by files / messages.

[0071] Optionally, in this embodiment, the automated processing of the information item attribution subsystem 11 is triggered by an information item change list, wherein the information item change list includes the name of the target information item to be changed and the change content. In a possible implementation, the change content is the value range of the target information item; accordingly, the first scheduling tool is used to:

[0072] When the information item change list is monitored, the information item attribution subsystem 11 is triggered to execute the first target operation.

[0073] It is understandable that when a user has a need to change an information item, the user interface of the information item attribution subsystem 11 provides an information item change list upload interface or inputs a text document to upload the information item change list or input a memory address for storing the information item change list. The information item attribution subsystem 11 obtains the information item change list according to the user's upload operation or the input memory address. Accordingly, when the first scheduling tool detects that a new information item change list appears on the system, the information item attribution system is triggered to execute the first target operation, thereby realizing the automated processing of the information item attribution system. Exemplarily, the first target operation includes:

[0074] (1.1) According to the information item change list, change the target information item in the subsystem to which the information item belongs.

[0075] In this step, according to the name and change content of at least one target information item in the information item change list, the corresponding target information item in the information item attribution subsystem 11 is changed. For example, if the information item attribution subsystem 11 is a customer information system, the target information item is the customer type, and the original value range of the customer type is: (individual business owners, government customers). If the change content is (individual business owners, government customers, community social organizations, party and mass organizations at or above the provincial level), the result of executing this step is to change the value range of the customer type from (individual business owners, government customers) to (individual business owners, government customers, community social organizations, party and mass organizations at or above the provincial level).

[0076] When there are multiple information items that need to be changed, batch processing of the information items can be achieved through the information item change list, which is conducive to improving the efficiency of information item change processing.

[0077] (1.2) Determine the business subsystem including the target information item based on the pre-stored correspondence between the information item and the business subsystem.

[0078] The information item belonging subsystem 11 pre-stores the correspondence between each information item and the business subsystem. The correspondence may exist in the form of a first data table, which may be pre-configured by the user and stored in a designated location in the information item belonging subsystem 11 .

[0079] It should be noted that when the information items belong to different subsystems 11, the content of the first data table may also be different. For example, since the customer information system and the institutional employee system have different statistical objects, it is only necessary to have a correspondence between the information items included in their respective systems and the business subsystem 12. That is, the customer information system only needs to store the correspondence between the relevant information items in the customer information system and the business subsystem, such as the first correspondence between the customer type and the first business subsystem (the business subsystem that uses the customer type as the information item), and the institutional employee system only needs to store the correspondence between the relevant information items in the institutional employee system and the business subsystem, such as the second correspondence between the institution number and the second business subsystem (the business subsystem that uses the institution number as the information item).

[0080] Accordingly, in this step, the business subsystem 12 including the target information item is determined according to the correspondence between the information item and the business subsystem stored in the information item change list and the first data table. Exemplarily, if the target information item is a customer type, in this step, all business subsystems 12 including the customer type need to be determined.

[0081] (1.3) Send the information item change list to the business subsystem including the target information item.

[0082] In this step, after determining the business subsystem 12 including the target information item, the first scheduling tool triggers the information item attribution system to send the information item change list to the business subsystem 12 including the target information item in a set manner, so that the business subsystem 12 including the target information item performs further operations according to the information item change list.

[0083] In one possible implementation, the first scheduling tool triggers the information item attribution subsystem 11 to send the information item change list to the business subsystem 12 including the target information item in the form of a message, such as with the help of a message middleware. Specifically, the information item attribution system 11 first sends the message including the information item change list to the message middleware, and then the message middleware notifies the business subsystem 12 including the target information item that has subscribed to the message to the message middleware to obtain relevant messages, thereby sending the information item change list to the business subsystem 12 including the target information item in the form of a message.

[0084] In another possible implementation, the first scheduling tool triggers the information item attribution subsystem 11 to send the information item change list in the form of a file to the business subsystem 12 including the target information item, such as by using a file transfer protocol, through email or the like, to send the information item change list in the form of a file to the business subsystem 12 including the target information item.

[0085] Optionally, in this embodiment, the automated processing of the business subsystem 12 is also triggered by the information item change list. Accordingly, the second scheduling tool is used to:

[0086] When the list of information item changes is monitored, the business subsystem 12 is triggered to execute the second target operation.

[0087] Similar to the first scheduling tool, the second scheduling tool is not only used to schedule tasks for the business subsystem 12, but also used to monitor the business subsystem 12. When the system receives a message or file including a list of information item changes, the business subsystem 12 is triggered to automatically perform the second target operation. Exemplarily, the second target operation includes:

[0088] (2.1) List of changes to storage information items.

[0089] In order to ensure that the account information of the business subsystem 12 and the account information of the general ledger subsystem 13 are changed on the same day, and to avoid a series of problems caused by the inconsistency of the account information of the general ledger and the sub-ledger, in this step, when the information item change list is monitored, the second scheduling tool does not immediately trigger the business subsystem 12 to perform corresponding operations according to the information item change list, but first stores the information item change list according to a pre-set storage path.

[0090] (2.2) On the next day, according to the information item change list, the target information item in the business subsystem 12 is changed.

[0091] Assuming that the business subsystem 12 obtains the information item change list and the time for the information item change list is T day, then in this step, the business subsystem 12 obtains the stored information item change list on T+1 day, and performs change processing on the target information item in the business subsystem 12 according to the information item change list, so that the value range of the target information item in the business subsystem 12 is consistent with the value range of the target information item in the information item to which the subsystem 11 to which the information item belongs is consistent.

[0092] (2.3) Send the account transfer flow generated during the change of the target information item to the general ledger subsystem.

[0093] Since the change of the target information item may cause the account information of the corresponding sub-account in the business subsystem 12 to change, the change of the account information occurs together with the change of the target information item, and generates an account transfer flow. For example, when the value range of an information item changes from multiple fields to one field, the balances corresponding to the original multiple fields under the information item need to be merged to obtain the balance corresponding to the new field. Accordingly, if there is a change in the account information, the business subsystem 12 will send the generated account transfer flow to the general ledger subsystem 13 during the change of the target information item, so that the general ledger subsystem 13 can make corresponding adjustments to the account information in the general ledger subsystem 13 according to the account transfer flow, thereby ensuring the consistency of the account information of the general ledger and the sub-account.

[0094] In a possible implementation, in this step, the business subsystem 12 sends the account transfer flow generated in the process of changing the target information item to the general ledger subsystem 13 through the accounting engine. Similar to the sending method of the information item change list, the sending method of the account transfer flow can also be a message or a file. The specific sending method can be selected according to the actual situation, and no specific limitation is made here.

[0095] Optionally, after executing the above (2.2)-(2.3), the second scheduling tool may also trigger the business subsystem 12 to perform the following operations:

[0096] (2.4) Delete the list of changes to the information item.

[0097] In this step, by deleting the information item change list after the business subsystem 12 has executed the relevant change processing, unnecessary memory occupation in the business subsystem 12 is reduced. In the long run, it can effectively avoid a series of problems caused by excessive memory consumption, such as freezing and slow operation of the business subsystem 12.

[0098] Optionally, in this embodiment, the automated processing of the general ledger subsystem 13 is triggered by the account transfer flow. Accordingly, the third scheduling tool is used to monitor the messages or files received by the general ledger subsystem 13, and when the messages or files including the account transfer flow are monitored, the general ledger subsystem 13 is triggered to perform the third target operation. Exemplarily, the third target operation includes:

[0099] (3.1) Based on the received account transfer flow, the account information in the general ledger subsystem is transferred to obtain the general ledger balance of the general ledger subsystem.

[0100] In this step, the general ledger subsystem 13 performs automatic carry-over processing on the account information in the general ledger subsystem 13 on T+1 day according to the received account carry-over flow. It is understandable that in this step, the general ledger subsystem 13 can carry-over the corresponding account information every time it receives an account carry-over flow, or it can carry-over the account information in the general ledger subsystem 13 at a specific time on T+1 day (such as the end of T+1 day, every n hours), according to all account carry-over flows received on that day or within a period of time (such as 5 hours) (which may come from the same business subsystem 12 or from different business subsystems 12), to obtain the general ledger balance of the general ledger subsystem. Among them, the account information includes information items and balances.

[0101] Optionally, after executing the operation corresponding to (3.1), the third scheduling tool can also be used to trigger the general ledger subsystem 13 to perform the following operation (fourth target operation), thereby realizing the verification of the general ledger balance and the sub-ledger balance, and further ensuring the consistency and accuracy of the accounting information.

[0102] (3.2) Obtain the total balance of the sub-accounts in the business subsystem that generates the account transfer flow.

[0103] In this step, according to the account transfer flow, the total balance of the sub-accounts of the business subsystem 12 that generates the account transfer flow is obtained, wherein the total balance of the sub-accounts is obtained by summing the balances corresponding to the target information items in each business subsystem 12 that generates the account transfer flow. Accordingly, this step may specifically include: first obtaining the balance corresponding to the same target information item in each business subsystem that generates the account transfer flow, and then summing the obtained balances to obtain the sub-account balance corresponding to the target information item in the business subsystem that generates the account transfer flow.

[0104] It should be noted that when there are multiple target information items, in the fourth target operation, the total balance of the sub-accounts can be checked with the balance of the general ledger under each target information item dimension in units of target information items to ensure the orderliness and accuracy of the check.

[0105] (3.3) Check the total balance of the sub-ledger with the general ledger balance of the general ledger subsystem.

[0106] In this step, by comparing the total balance of the sub-accounts of the account information in the business subsystem 12 that generates the account transfer flow under the same target information item dimension with the general ledger balance recorded in the account information in the general ledger subsystem 13 to see if they are consistent, the total and the parts are reconciled to avoid a series of problems caused by the imbalance of the total and the parts.

[0107] (3.4) Feedback the verification results to the business subsystem that generates the account transfer flow.

[0108] In this step, after executing (3.3), the general ledger subsystem 13 feeds back the verification result to the business subsystem 12 that generates the account transfer flow, so that each business subsystem 12 that generates the account transfer flow performs corresponding operations. Specifically, if the total balance of the sub-account is inconsistent with the general ledger balance of the general ledger subsystem 13, the verification result is fed back to each business subsystem 12 that generates the account transfer flow, so that each business subsystem 12 that generates the account transfer flow verifies the account information to ensure the accuracy of the account information in each business subsystem 12 that generates the account transfer flow, thereby ensuring that the total balance of the sub-account is consistent with the general ledger balance of the general ledger subsystem 13.

[0109] In this embodiment, the information processing system is set up to include: an information item attribution subsystem, a business subsystem and a general ledger subsystem. The information item attribution subsystem and the business subsystem are communicated with each other, and the business subsystem and the general ledger subsystem are communicated with each other. The information item attribution subsystem, the business subsystem and the general ledger subsystem are all installed with scheduling tools. The scheduling tool is used to trigger the subsystem where the scheduling tool is installed to perform the target operation when the target file or target message is monitored. When the information item in the information item attribution subsystem changes, the automatic carry-over processing of the accounting information is realized, which not only avoids the problems of high error rate and high cost caused by manual participation, but also improves the processing efficiency of the accounting information. In addition, since the business subsystem and the general ledger subsystem can complete the change of the accounting information on the same day, it also reduces a series of problems caused by the inconsistency between the general ledger information and the sub-ledger information, and reduces the coordination cost.

[0110] Embodiment 2

[0111] Figure 2 This is a flow chart of the information processing method provided in Example 2 of the present application. The information processing method provided in this embodiment can be applied to Figure 1 The information items shown belong to the subsystem, such as Figure 2 As shown, the method of this embodiment includes:

[0112] S101. Obtain a list of information item changes.

[0113] Exemplarily, in this step, when the user uploads the information item change list or inputs the memory address storing the information item change list through the information item change list upload interface or input text document provided by the user interface of the information item attribution subsystem, the information item attribution subsystem obtains the information item change list, and the information item change list includes the name of the target information item and the change content. Optionally, the change content is the value domain of the target information item.

[0114] S102. Change the target information item in the system according to the information item change list.

[0115] In this step, after S101, the corresponding target information item in the system is changed according to the name and change content of the target information item in the acquired information item change list. The specific implementation method is similar to the specific implementation method of (1.1) in Example 1 and will not be repeated here.

[0116] The target information item is an information item included in the information item change list.

[0117] Optionally, the changed content is the value range of the target information item.

[0118] S103: Determine the business subsystem including the target information item according to the pre-stored correspondence between the information item and the business subsystem.

[0119] Exemplarily, in this step, the information item attribution subsystem determines one or more business subsystems including the target information item from multiple business subsystems through keyword query based on the correspondence between the information items and business subsystems pre-stored in the system and the name of the target information.

[0120] S104: Send the information item change list to the business subsystem including the target information item.

[0121] In this step, the acquired information change list is sent to the business subsystem including the target information item determined in S103.

[0122] Optionally, in this step, the information item change list is sent to the business subsystem including the target information item in the form of a message or a file. The specific implementation method is similar to the specific implementation method of (1.3) in Example 1 and will not be repeated here.

[0123] In this embodiment, by obtaining an information item change list, the target information item in the system is changed according to the information item change list, and the business subsystem including the target information item is determined according to the pre-stored correspondence between the information item and the business subsystem, and the information item change list is sent to the business subsystem including the target information item. Through the information item change list, automatic change processing of the information item by the subsystem to which the information item belongs is realized, thereby improving the efficiency of changing the information item, reducing the error rate, and saving costs.

[0124] Embodiment 3

[0125] Figure 3 This is a flow chart of the information processing method provided in Example 3 of the present application. The information processing method provided in this embodiment can be applied to Figure 1 The business subsystems shown are as follows: Figure 3 As shown, the method of this embodiment includes:

[0126] S201. Store the received information item change list.

[0127] In the steps, in order to ensure that the account information of the business subsystem and the account information of the general ledger subsystem are changed on the same day, and to avoid a series of problems caused by the inconsistency of the account information of the general ledger and the sub-ledger, the business subsystem that receives the information item change list does not immediately change the information item, but first stores the information item change list, wherein the information item change list includes the name of the target information item and the change content. Optionally, the change content is the value range of the target information item.

[0128] S202. On the next day, according to the information item change list, change the target information item in the system.

[0129] In this step, on the day after receiving the information item change list, the target information item in the business subsystem is changed according to the information item change list. The specific implementation method is similar to the specific implementation method of (2.2) in Example 1 and will not be repeated here.

[0130] S203: Send the account transfer flow generated during the change of the target information item to the general ledger subsystem.

[0131] In this step, the account transfer flow generated in the target information change process in S202 is sent to the general ledger subsystem, so that the general ledger subsystem can perform collaborative changes to the account information.

[0132] Optionally, in this step, the account transfer flow generated during the change of the target information item is sent to the general ledger subsystem through the accounting engine.

[0133] Optionally, in this step, the account transfer flow generated during the change of the target information item is sent to the general ledger subsystem in the form of a message or a file. The specific implementation method is similar to the specific implementation method of sending the information item change list to the business subsystem including the target information item in S104, and will not be repeated here.

[0134] Optionally, after S203, the method of this embodiment further includes: deleting the information item change list.

[0135] In this embodiment, by storing the received information item change list, the target information items in this system are changed on the next day according to the information item change list, and the account transfer flow generated during the change of the target information item is sent to the general ledger subsystem, thereby realizing automatic change processing of the information items by the business subsystem, improving the efficiency of changing the information items, reducing the error rate, and saving costs.

[0136] Embodiment 4

[0137] Figure 4This is a flow chart of the information processing method provided in Example 4 of the present application. The information processing method provided in this embodiment can be applied to Figure 1 In the general ledger subsystem shown in the figure, Figure 4 As shown, the method of this embodiment includes:

[0138] S301. Carry forward the account information in the system according to the received account carry-forward flow to obtain the general ledger balance of the general ledger subsystem.

[0139] In this step, the general ledger subsystem carries out a carry-over process on the account information in the system according to the received account carry-over flow to obtain the general ledger balance of the general ledger subsystem. The specific implementation method is similar to the specific implementation method of (3.1) in Example 1 and will not be described again here.

[0140] S302: Obtain the total balance of the sub-accounts of the business subsystem that generates the account transfer flow.

[0141] In this step, after S302, the total balance of the sub-accounts of the business subsystem that generates the account transfer flow is obtained based on the account transfer flow. The specific implementation method is similar to the specific implementation method (3.2) in Example 1 and will not be repeated here.

[0142] S303. Check the total balance of the sub-accounts with the general ledger balance of the general ledger subsystem.

[0143] In this step, different target information items are used as verification dimensions to verify the total balance of the sub-accounts and the general ledger balance of the general ledger subsystem. The specific implementation method is similar to the specific implementation method of (3.3) in Implementation Example 1, and will not be repeated here.

[0144] S304: Feedback the verification results to the business subsystem that generates the account transfer flow.

[0145] In this step, after S303, the verification result is fed back to the business subsystem that generates the account transfer flow, and its specific implementation method is similar to the specific implementation method of (3.4) in Example 1, which will not be repeated here. It can be understood that, similarly, in this step, the verification result can also be fed back to the business subsystem that generates the account transfer flow in the form of a message or a file.

[0146] In this embodiment, by carrying out carry-over processing on the account information in this system according to the received account carry-over flow, the general ledger balance of the general ledger subsystem is obtained, the total balance of the sub-accounts of the business subsystem that generates the account carry-over flow is obtained, the total balance of the sub-accounts is compared with the general ledger balance of the general ledger subsystem, and the comparison result is fed back to the business subsystem that generates the account carry-over flow, thereby realizing automatic carry-over processing of the accounting subsystem to the accounting system, improving the efficiency of changing information items, reducing the error rate, and saving costs. In addition, by adopting the method of this embodiment, the general ledger subsystem can complete the change of account information on the same day as the business subsystem, reducing a series of problems caused by the inconsistency between the general ledger information and the sub-account information.

[0147] For example, Figure 5 The overall processing logic diagram of the information processing system provided in the embodiment of the present application is as follows: Figure 5 As shown, the overall implementation logic of the embodiment of the present application is: when the business subsystem 12 obtains the change information provided by the information item attribution subsystem, the information item corresponding to the change information is changed in the business subsystem 12, and the account transfer flow generated during the information item change process is sent to the general ledger subsystem 13. The general ledger system 13 performs transfer processing on the account information according to the account transfer flow, and performs a total-specific check on the account information in the general ledger system 13 and the account information in the business subsystem 12. After the check is completed, the check result is fed back to the business subsystem 12 to meet the business needs of the total-specific check. By splitting these execution logics, the execution logics of the information attribution subsystem 11, the business subsystem 12 and the general ledger subsystem 13 are obtained respectively, and the corresponding execution logics are solidified in the corresponding subsystems, and through the deployment of scheduling tools, the automatic transfer processing of the account information is realized when the information item changes.

[0148] Optionally, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a computer processor, it is used to execute the execution logic of the aforementioned information item attribution subsystem or business subsystem or general ledger subsystem.

[0149] It is worth noting that the various subsystems included in the above-mentioned information processing system are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the subsystems are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application.

[0150] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims

1. An information processing system, characterized in that: include: Information items belong to the subsystem, business subsystem and general ledger subsystem; The information item attribution subsystem is in communication with the business subsystem, and the business subsystem is in communication with the general ledger subsystem; the information item attribution subsystem, the business subsystem and the general ledger subsystem are all installed with a scheduling tool, and the scheduling tool is used to trigger the subsystem installed with the scheduling tool to perform a target operation when a target file or target message is monitored; The information item attribution subsystem is installed with a first scheduling tool, and the first scheduling tool is used to: When a list of information item changes is monitored, triggering the information item belonging subsystem to perform a first target operation; Wherein, the information item change list includes the name of the target information item and the change content; Wherein, the first target operation includes: According to the information item change list, changing the target information item in the subsystem to which the information item belongs; Determining the business subsystem including the target information item according to the pre-stored correspondence between the information item and the business subsystem; Sending the information item change list to the business subsystem including the target information item; Wherein, a second scheduling tool is installed on the business subsystem, and the second scheduling tool is used to: When the list of changes to the information items is monitored, triggering the business subsystem to perform a second target operation; Wherein, the second target operation includes: storing the information item change list; On the next day, the target information item in the business subsystem is changed according to the information item change list; Sending the account transfer flow generated during the change of the target information item to the general ledger subsystem; Wherein, a third scheduling tool is installed on the general ledger subsystem, and the third scheduling tool is used to: When the account carry-over flow is detected, the general ledger subsystem is triggered to perform the third target operation; Wherein, the third target operation includes: According to the received account carry-over flow, the account information in the general ledger subsystem is carried forward to obtain the general ledger balance of the general ledger subsystem.

2. The system according to claim 1, characterized in that The third scheduling tool is also used to: When it is monitored that the general ledger subsystem has completed the execution of the third target operation, triggering the general ledger subsystem to execute the fourth target operation; Among them, the fourth target operation includes: Obtain the total balance of the sub-accounts of the business subsystem that generates the account carry-forward flow; Checking the total balance of the sub-accounts with the general ledger balance of the general ledger subsystem; The verification result is fed back to the business subsystem that generates the account transfer flow.

3. The system according to any one of claims 1 to 2, characterized in that: The information item belongs to the customer information system, and the target information item is the customer type.

4. An information processing method, characterized in that: Applied to an information processing system, the information processing system includes an information item attribution subsystem, a business subsystem and a general ledger subsystem, and the method includes: The information item belonging subsystem obtains an information item change list, the information item change list includes the name of the target information item and the change content; according to the information item change list, the target information item in the system is changed; according to the pre-stored correspondence between the information item and the business subsystem, the business subsystem including the target information item is determined; and the information item change list is sent to the business subsystem including the target information item; The business subsystem stores the received information item change list, which includes the name of the target information item and the change content; on the next day, the target information item in the system is changed according to the information item change list; and the account transfer flow generated during the change of the target information item is sent to the general ledger subsystem; The general ledger subsystem carries out carry-over processing on the account information in the system according to the received account carry-over flow to obtain the general ledger balance of the general ledger subsystem; obtains the total balance of the sub-accounts of the business subsystem that generates the account carry-over flow; verifies the total balance of the sub-accounts with the general ledger balance of the general ledger subsystem; and feeds back the verification result to the business subsystem that generates the account carry-over flow.

5. The method according to claim 4, characterized in that The sending of the information item change list to the business subsystem including the target information item comprises: The information item change list is sent to the business subsystem including the target information item in the form of a message or a file.

6. The method according to claim 4 or 5, characterized in that: The changed content is the value range of the target information item.

7. The method according to claim 4, characterized in that The sending of the account transfer flow generated during the change of the target information item to the general ledger subsystem includes: The account transfer flow generated during the change of the target information item is sent to the general ledger subsystem through the accounting engine.

8. The method according to claim 4, characterized in that The sending of the account transfer flow generated during the change of the target information item to the general ledger subsystem includes: The account transfer flow generated during the change of the target information item is sent to the general ledger subsystem in the form of a message or a file.

9. The method according to any one of claims 4, 7-8, characterized in that: The changed content is the value range of the target information item.

Images