Reconciliation method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to an account checking method and device, computer equipment, a computer readable storage medium and a computer program product. Comprising the following steps: determining supplier bills associated with each system order; obtaining an account checking template; according to the calculation rules of the plurality of order fields, calculating data in the supplier bill to obtain bill data corresponding to the plurality of order fields; determining a plurality of target fields to be matched according to the comparison options; according to the matching rule of the target field, matching the system order with the bill data to obtain a matching result; if the matching result shows that the matching fails, an error prompt is output; and determining an account checking result according to a matching result of the plurality of target fields. By adopting the method, the cost information between suppliers is automatically matched and checked, the comprehensiveness and accuracy of account checking are ensured, and manual errors are reduced; the self-defined reconciliation template is supported, the diversified requirements of enterprises can be met, and the flexibility and efficiency of reconciliation settlement are improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a reconciliation method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] At present, in order to achieve better production and operation, enterprises have introduced more and more high-quality resource suppliers and optimized service resources, which has led to an increasingly heavy workload for reconciliation. Secondly, the low efficiency of collaboration on the supplier side is also one of the problems that need to be urgently solved in the current enterprise operation and management. At present, there is no complete online collaboration mechanism between suppliers and operators, and they rely more on offline communication. This communication method is not only inefficient and prone to errors, but may also lead to information opacity and asymmetry, increasing the financial risks and operating costs of enterprises. The reconciliation and settlement work is complex and cumbersome, and the opacity and asymmetry of information will greatly affect the efficiency of reconciliation and settlement.

[0003] In recent years, with the rapid development of information technology and the widespread application of Internet technology, more and more operating companies have begun to realize the huge potential of online automation tools in improving reconciliation efficiency and accuracy. However, the current online reconciliation tools have single functions, lack comprehensiveness and flexibility, and cannot meet the diverse needs of corporate reconciliation. Summary of the invention

[0004] Based on this, it is necessary to provide a reconciliation method, apparatus, computer equipment, computer-readable storage medium and computer program product to address the above technical problems, which can automatically match and verify expense information with suppliers and generate accurate reconciliation results.

[0005] In a first aspect, the present application provides a reconciliation method, comprising:

[0006] Determine the vendor bills associated with each system order;

[0007] Obtaining a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of a calculation rule, a comparison option, a matching rule, and an error prompt;

[0008] According to the calculation rules of multiple order fields, the data in the supplier bill is calculated to obtain the bill data corresponding to the multiple order fields;

[0009] According to the comparison options, multiple target fields to be matched are determined;

[0010] For each target field, according to the matching rule of the target field, the system order data under the target field is matched with the bill data corresponding to the target field to obtain a matching result;

[0011] If the matching result indicates a matching failure, an error message for the target field is output;

[0012] The reconciliation results between system orders and supplier bills are determined based on the matching results of multiple target fields.

[0013] In one embodiment, determining a vendor bill associated with each system order includes:

[0014] Automatically search for system orders based on the reconciliation time range, call the supplier system interface, and obtain the supplier bill corresponding to the reconciliation time range from the supplier system;

[0015] Preliminarily match the found system order with the obtained supplier bill to obtain a preliminary matching result;

[0016] Based on the preliminary matching results, determine the supplier bills associated with each system order.

[0017] In one embodiment, the method further comprises:

[0018] If the target system order cannot be matched to the associated supplier bill, the preliminary matching result of the target system order is determined to be a matching failure;

[0019] If the target supplier bill cannot be matched to the associated system order, the preliminary matching result of the target supplier bill is determined to be a matching failure;

[0020] Mark duplicate system orders or supplier bills with duplicate accounting marks and generate corresponding preliminary matching results.

[0021] In one embodiment, the method further comprises:

[0022] A result page is generated based on the preliminary matching result and the reconciliation result; the result page displays the reconciliation result of each system order, abnormal records and at least one abnormal handling button; the abnormal records include the record information of abnormal system orders or abnormal supplier bills, the abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and the abnormal supplier bills include abnormal suppliers that fail preliminary matching or have duplicate accounts; the abnormal handling buttons include a difference data confirmation button or a delayed settlement option button;

[0023] The result page is displayed.

[0024] In one embodiment, the method further comprises:

[0025] In response to a triggering operation of a confirmation button for difference data on a result page, marking the selected system order and / or supplier bill as confirmed;

[0026] In response to a triggering operation on a delayed settlement option button on a result page, the selected system order and / or supplier bill is marked as pending.

[0027] In one embodiment, the method further comprises:

[0028] Receive manually imported vendor bills;

[0029] Verify the data in the received supplier bill under the preset key fields;

[0030] If the verification fails, an import failure prompt will be issued and incorrect data will be provided to the user.

[0031] In a second aspect, the present application also provides a reconciliation device, including:

[0032] A determination module for determining the supplier bill associated with each system order;

[0033] An acquisition module, used to acquire a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of a calculation rule, a comparison option, a matching rule, and an error prompt;

[0034] A calculation module, used to calculate the data in the supplier bill according to the calculation rules of multiple order fields to obtain bill data corresponding to the multiple order fields;

[0035] The matching module is used to determine multiple target fields to be matched according to the comparison options; for each target field, according to the matching rule of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result; if the matching result indicates a matching failure, an error prompt of the target field is output;

[0036] The reconciliation module is used to determine the reconciliation results between system orders and supplier bills based on the matching results of multiple target fields.

[0037] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the method described in the first aspect above are implemented.

[0038] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method described in the first aspect above are implemented.

[0039] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the method described in the first aspect above.

[0040] The above-mentioned reconciliation method, device, computer equipment, computer-readable storage medium and computer program product determine the supplier bill associated with each system order; obtain a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of calculation rules, comparison options, matching rules and error prompts; according to the calculation rules of multiple order fields, the data in the supplier bill is calculated to obtain the bill data corresponding to the multiple order fields; according to the comparison options, multiple target fields to be matched are determined; for each target field, according to the matching rules of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result; if the matching result indicates that the matching fails, an error prompt of the target field is output; according to the matching results of multiple target fields, the reconciliation result between the system order and the supplier bill is determined. In the above manner, based on the customized reconciliation template, the expense information between the supplier and the supplier can be automatically matched and checked to generate accurate reconciliation results, ensuring the comprehensiveness and accuracy of the reconciliation, reducing manual errors, thereby greatly reducing the time cost of enterprise reconciliation and improving the operational efficiency of the enterprise. Supports custom reconciliation templates to meet the diverse needs of enterprises and improve the flexibility and efficiency of reconciliation and settlement. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0042] Figure 1 An application environment diagram of a reconciliation method in an embodiment;

[0043] Figure 2 A schematic diagram of a flow chart of a reconciliation method in one embodiment;

[0044] Figure 3 A schematic diagram of a page for creating a new reconciliation template in an embodiment;

[0045] Figure 4 A schematic diagram of a supplier bill in one embodiment;

[0046] Figure 5 is a schematic diagram of a result page in one embodiment;

[0047] Figure 6 A schematic diagram of an import failure prompt in an embodiment;

[0048] Figure 7is a structural block diagram of an account reconciliation device in an embodiment;

[0049] Figure 8 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0051] The reconciliation method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The terminal 102 logs in to the platform corresponding to the server 104 through a browser or application program, and displays relevant pages to the user; in response to the user's operation, completes functions such as user login, data import, reconciliation settlement, and bill cover download. The server 104 is connected to each supplier system 106 through an API interface to achieve real-time transmission and synchronization of data. The server 104 sends a reconciliation request to the supplier system 106, and the supplier system 106 returns the bill data; the server 104 performs reconciliation processing based on the reconciliation method provided in any embodiment of the present application, and sends the processed reconciliation result to the supplier system 106 for subsequent settlement operations. The server 104 interacts with the database to store and retrieve data and information generated during the reconciliation process. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, and tablet computers. The server 104 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0052] In an exemplary embodiment, Figure 2 As shown, a reconciliation method is provided, which is applied to Figure 1 The server 104 in FIG. 1 is used as an example to illustrate, including:

[0053] Step 202, determine the supplier bill associated with each system order.

[0054] Among them, there are several system orders stored on the server. The system order refers to the transaction record and basis for the operation fee storage, and the supplier bill is the transaction information stored in the supplier system. Optionally, by searching in both directions on the server and the supplier system, the system order and supplier bill that need to be reconciled can be quickly determined.

[0055] In an optional implementation, before processing system orders and supplier bills, data preprocessing is required for system orders and supplier bills, including parsing of bill files, conversion of data formats, abnormal data processing, etc., to improve data quality and availability.

[0056] Step 204, obtaining a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of a calculation rule, a comparison option, a matching rule, and an error prompt.

[0057] Among them, the reconciliation template is the rules and parameters for reconciliation configured on the server by the user according to business needs and supplier reconciliation rules. The reconciliation template defines the correspondence between system orders and supplier bills, calculation rules, comparison options, matching rules, error prompts, etc., and is used to guide the system to automatically perform reconciliation processing.

[0058] In an optional implementation, the server manages the reconciliation templates corresponding to each supplier system, and in the current processing flow, searches for the corresponding reconciliation template in the storage space according to the identifier of the supplier that needs to be reconciled.

[0059] In an optional implementation, refer to Figure 3 , Figure 3 A schematic diagram of a new reconciliation template page is shown. Through this page, users can customize different reconciliation templates. Among them, users can add or delete customized information for each order field, and define the reconciliation template columns, calculation rules, comparison options, matching rules and error reasons for each order field based on this page. It supports the merging of reconciliation data to improve the flexibility and accuracy of reconciliation. Users can flexibly configure reconciliation templates according to actual business needs to adapt to different reconciliation scenarios.

[0060] It can be understood that the calculation rules are used to define the calculation operations that need to be performed during the reconciliation process, indicating how the bill fields corresponding to the order fields need to be calculated. For example, the calculation rule corresponding to a certain order field is: the sum of the value under field A and the value under field B in the supplier's bill. The comparison option is used to indicate whether the order field needs to be compared. Some system-fixed fields do not need to be compared with the supplier's bill. The matching rule is used to indicate the comparison rules between the system order and the supplier's bill. For example, the matching rule corresponding to a certain order field is: if the value under the order field is greater than the corresponding value in the supplier's bill, the match is successful, otherwise the match fails. The error prompt is used to display specific error information to the user when differences are found during the comparison process, so that the user can find the cause of the error and perform subsequent processing.

[0061] Step 206, calculate the data in the supplier's bill according to the calculation rules of the multiple order fields to obtain the bill data corresponding to the multiple order fields.

[0062] For each order field, based on the calculation rules of the order field, relevant data is obtained from the supplier bill, and the obtained data is calculated using the calculation rules to obtain the bill data corresponding to the order field.

[0063] Step 208: Determine multiple target fields to be matched according to the comparison options.

[0064] Among them, according to the comparison option of each bill field, multiple target fields that need to be compared are determined.

[0065] Step 210, for each target field, according to the matching rule of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result.

[0066] Among them, the matching rule determines how to compare the data under the target field with the billing data corresponding to the target field, for example, complete matching (the data is exactly the same), fuzzy matching (using a set algorithm to calculate the similarity), etc. Based on the matching rule, the system order data under the target field is compared with the billing data corresponding to the target field, and which target fields are successfully matched and which target fields fail to match are recorded.

[0067] Step 212: If the matching result indicates a matching failure, an error prompt of the target field is output.

[0068] If the matching result of any target field is a matching failure, the error prompt corresponding to the target field will be recorded.

[0069] Step 214, determining the reconciliation result between the system order and the supplier bill according to the matching results of the multiple target fields.

[0070] Among them, the matching results of each target field between the system order and the supplier bill are recorded. If the matching results of all target fields are successful, the reconciliation result between the system order and the supplier bill is determined to be a successful match. If the matching result of a target field is a match failure, the reconciliation result between the system order and the supplier bill is determined to be a match failure, and an error prompt of the target field that failed to match is added in the corresponding field.

[0071] It is understandable that the automatic reconciliation process supports two-way search and error identification. Two-way search means that the server will search for records that match the supplier bill from the system order, and will also search for records that match the system order from the supplier bill. Error identification means that during the comparison process, the server will determine whether there is a difference based on the configured comparison options, matching rules, and calculation rules, and generate a difference report. The difference report includes the type of difference, the specific information of the difference, and the reason for the difference.

[0072] In an optional implementation, during the reconciliation process, information such as the reconciliation status, reconciled amount, invoiced amount, and received amount are recorded in real time, making it easy for users to monitor and track the progress of the reconciliation. A real-time reconciliation data display function is provided, so that users can view the reconciliation information of system orders and supplier bills at any time. The reconciliation data is displayed in a list format, which is intuitive and clear, making it easy for users to make accurate analysis and decisions. The reconciliation results are updated in real time to ensure the accuracy and consistency of the data.

[0073] In an optional implementation, a function of generating a statement cover with one click is provided. The statement cover is generated based on key reconciliation information. The statement cover can be optionally displayed in a list format. The statement cover can be exported to PDF to facilitate users to print, archive or send.

[0074] In the above reconciliation method, the supplier bill associated with each system order is determined; a reconciliation template is obtained; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of calculation rules, comparison options, matching rules and error prompts; according to the calculation rules of multiple order fields, the data in the supplier bill is calculated to obtain the bill data corresponding to the multiple order fields; according to the comparison options, multiple target fields to be matched are determined; for each target field, according to the matching rules of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result; if the matching result indicates that the matching fails, an error prompt of the target field is output; according to the matching results of multiple target fields, the reconciliation result between the system order and the supplier bill is determined. In the above manner, based on the customized reconciliation template, the expense information between the supplier and the supplier can be automatically matched and checked, and accurate reconciliation results can be generated, which ensures the comprehensiveness and accuracy of the reconciliation, reduces manual errors, and thus greatly reduces the time cost of enterprise reconciliation and improves the operational efficiency of the enterprise. Supporting customized reconciliation templates can meet the diversified needs of enterprises and improve the flexibility and efficiency of reconciliation settlement.

[0075] In an exemplary embodiment, step 202 includes: automatically searching for system orders according to the reconciliation time range, and calling the interface of the supplier system to obtain the supplier bill corresponding to the reconciliation time range from the supplier system; preliminarily matching the found system orders with the obtained supplier bills to obtain preliminary matching results; and determining the supplier bills associated with each system order based on the preliminary matching results.

[0076] The reconciliation time range can be manually input by the user, set by each supplier, or determined by the server based on a pre-configured scheduled task, that is, the server supports the periodic reconciliation function. Figure 4 , Figure 4 The following is a schematic diagram of a supplier bill in an embodiment; the server connects to the supplier system through an API interface and automatically obtains the supplier bill, including order number, product information, amount, etc. After the data is obtained, the server will pre-process the obtained data, including data cleaning, format conversion, etc., to ensure the accuracy and consistency of the data.

[0077] In an optional implementation, the server records the reconciliation time range according to the reconciliation time dimension set by each supplier, and automatically matches and searches for system order details based on the reconciliation time range, supplier bill details, etc.; it also supports querying all unreconciled system order details according to the reconciliation time range, supplier, and billing cycle. After automatic comparison, it displays the reasons for the differences based on the reconciliation template and updates the bill statistics in real time.

[0078] In this embodiment, supplier bills are automatically obtained from the supplier system, which can reduce manual operation processes and improve reconciliation efficiency.

[0079] In an exemplary embodiment, the method also includes: if the target system order cannot be matched to the associated supplier bill, determining the preliminary matching result of the target system order is a matching failure; if the target supplier bill cannot be matched to the associated system order, determining the preliminary matching result of the target supplier bill is a matching failure; marking duplicate accounts for duplicate system orders or supplier bills to generate corresponding preliminary matching results.

[0080] Among them, the server supports automatic marking of missing system orders, missing supplier bills, duplicate system orders or duplicate supplier bills, and provides abnormal account display and processing functions, which makes it easy for users to quickly identify abnormal accounts, increase the transparency of order processing, and reduce misunderstandings caused by information asymmetry.

[0081] Optionally, during the preliminary matching process, the system order and the supplier bill are matched according to the order number. The system order and the supplier bill that are successfully initially matched are further matched according to steps 202 to 214 provided in this application. The data that fails the preliminary matching is recorded and displayed synchronously on the result page.

[0082] In an exemplary embodiment, the method also includes: generating a result page based on the preliminary matching results and the reconciliation results; displaying the reconciliation results of each system order, exception records and at least one exception handling button on the result page; the exception records include record information of abnormal system orders or abnormal supplier bills, abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and abnormal supplier bills include abnormal suppliers that fail preliminary matching or have duplicate accounts; the exception handling buttons include a difference data confirmation button or a delayed settlement option button; and displaying the result page.

[0083] Among them, the preliminary matching results and reconciliation results generated in the above steps are displayed, and an exception handling button is provided for users to use. It is understandable that if a system order that fails the preliminary matching is found in the above steps, the system order will be displayed on the result page; if no abnormal record is found in the above steps, only the reconciliation result can be displayed; the content displayed on the result page of this embodiment is related to the above preliminary matching results and reconciliation results. Manual difference confirmation, delayed settlement and other methods are provided to handle reconciliation difference data.

[0084] In an optional implementation, refer to Figure 5 , Figure 5 This is a schematic diagram of a result page in an embodiment; the result page displays bill information and order information, and displays comparison results (i.e., reconciliation results). For system orders and supplier bills that fail to be initially matched, "system order not found" or "supplier bill not found" is prompted in the comparison results. A page switching function is provided, and in response to a user's trigger operation, it can switch to a difference order page, a delayed settlement page, or a reconciled page, etc.

[0085] In an exemplary embodiment, the method further includes: in response to a trigger operation for a difference data confirmation button on a result page, marking the selected system order and / or supplier bill as confirmed; in response to a trigger operation for a delayed settlement option button on the result page, marking the selected system order and / or supplier bill as pending.

[0086] Among them, after the result page is generated, the user can process the difference data. The result page provides a difference data confirmation button or a delayed settlement option button, and the user can choose the corresponding processing method according to the actual situation. For the difference data that has been confirmed to be correct, the user can mark it as processed and update the supplier reconciliation status. For the difference data that needs to be delayed for settlement, the user can mark it as pending and check and confirm it again in the subsequent processing. After confirming that the reconciliation is correct, the user can update the supplier reconciliation status to reconciled and end the reconciliation process.

[0087] In an exemplary embodiment, the method further includes: receiving a manually imported supplier bill; verifying the data in the received supplier bill under preset key fields; if the verification fails, issuing an import failure prompt and providing erroneous data to the user.

[0088] The manual import of bills function is supported to ensure the continuity of reconciliation work when the API interface of the supplier system is unavailable or the supplier system is upgraded. Users can upload the bill files provided by the supplier to the server, which will parse and import them. Figure 6 , Figure 6 A schematic diagram of an import failure prompt in an embodiment; a user manually uploads a supplier bill file through the user interface displayed on the terminal, and the server automatically parses the bill file and extracts the data therein; the server presets key fields that need to be verified according to business needs, such as supplier name, bill date, transaction amount, product or service details, etc.; the server verifies the data related to the preset key fields in the parsed bill data to check whether it conforms to the expected format, range or rule; if the bill data fails to verify any key field, a prompt message of import failure is issued, and specific error data is displayed to the user for the user to export and view which fields failed to verify and the reasons for the failure.

[0089] In this embodiment, a manual bill import function is provided, and the manually imported supplier bills are verified, which can ensure the accuracy of the supplier bill data, thereby improving the accuracy of the reconciliation results and the efficiency of reconciliation management.

[0090] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0091] Based on the same inventive concept, the embodiment of the present application also provides a reconciliation device for implementing the reconciliation method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more embodiments of the reconciliation device provided below can refer to the limitations on the reconciliation method above, and will not be repeated here.

[0092] In an exemplary embodiment, Figure 7 As shown, a reconciliation device is provided, comprising:

[0093] The determination module 702 is used to determine the supplier bill associated with each system order.

[0094] The acquisition module 704 is used to acquire a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of a calculation rule, a comparison option, a matching rule, and an error prompt.

[0095] The calculation module 706 is used to calculate the data in the supplier bill according to the calculation rules of multiple order fields to obtain the bill data corresponding to the multiple order fields.

[0096] The matching module 708 is used to determine multiple target fields to be matched according to the comparison options; for each target field, according to the matching rules of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result; if the matching result indicates a matching failure, an error prompt of the target field is output.

[0097] The reconciliation module 710 is used to determine the reconciliation result between the system order and the supplier bill according to the matching results of multiple target fields.

[0098] In the above reconciliation device, based on the customized reconciliation template, it can automatically match and check the expense information with the supplier, generate accurate reconciliation results, ensure the comprehensiveness and accuracy of the reconciliation, reduce manual errors, and thus greatly reduce the time cost of enterprise reconciliation and improve the operational efficiency of the enterprise. Supporting customized reconciliation templates can meet the diverse needs of enterprises and improve the flexibility and efficiency of reconciliation and settlement.

[0099] In an exemplary embodiment, the determination module 702 is also used to automatically search for system orders based on the reconciliation time range, and call the interface of the supplier system to obtain the supplier bill corresponding to the reconciliation time range from the supplier system; preliminarily match the found system orders with the obtained supplier bills to obtain preliminary matching results; and determine the supplier bills associated with each system order based on the preliminary matching results.

[0100] In an exemplary embodiment, the determination module 702 is also used to determine that if the target system order cannot be matched to the associated supplier bill, the preliminary matching result of the target system order is determined to be a matching failure; if the target supplier bill cannot be matched to the associated system order, the preliminary matching result of the target supplier bill is determined to be a matching failure; and to mark duplicate accounts for duplicate system orders or supplier bills to generate corresponding preliminary matching results.

[0101] In an exemplary embodiment, the reconciliation device also includes a result display module, which is used to generate a result page based on the preliminary matching results and the reconciliation results; the result page displays the reconciliation results of each system order, exception records and at least one exception handling button; the exception records include record information of abnormal system orders or abnormal supplier bills, the abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and the abnormal supplier bills include abnormal suppliers that fail preliminary matching or have duplicate accounts; the exception handling buttons include difference data confirmation buttons or delayed settlement option buttons; the result page is displayed.

[0102] In an exemplary embodiment, the result display module is also used to mark the selected system order and / or supplier bill as confirmed in response to the triggering operation of the difference data confirmation button on the result page; and to mark the selected system order and / or supplier bill as pending in response to the triggering operation of the delayed settlement option button on the result page.

[0103] In an exemplary embodiment, the reconciliation device also includes an import module, which is used to receive manually imported supplier bills; verify the data of the received supplier bills under preset key fields; if the verification fails, issue an import failure prompt and provide erroneous data to the user.

[0104] Each module in the above-mentioned reconciliation device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0105] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 8 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a reconciliation method is implemented.

[0106] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0107] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: determining the supplier bill associated with each system order; obtaining a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of calculation rules, comparison options, matching rules and error prompts; according to the calculation rules of the multiple order fields, the data in the supplier bill is calculated to obtain the bill data corresponding to the multiple order fields; according to the comparison options, multiple target fields to be matched are determined; for each target field, according to the matching rules of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result; if the matching result indicates a matching failure, an error prompt for the target field is output; according to the matching results of the multiple target fields, the reconciliation result between the system order and the supplier bill is determined.

[0108] In one embodiment, when the processor executes the computer program, the following steps are also implemented: automatically searching for system orders according to the reconciliation time range, and calling the interface of the supplier system to obtain the supplier bill corresponding to the reconciliation time range from the supplier system; preliminarily matching the found system orders with the obtained supplier bills to obtain preliminary matching results; and determining the supplier bills associated with each system order based on the preliminary matching results.

[0109] In one embodiment, when the processor executes the computer program, the following steps are also implemented: if the target system order cannot be matched to the associated supplier bill, the preliminary matching result of the target system order is determined to be a matching failure; if the target supplier bill cannot be matched to the associated system order, the preliminary matching result of the target supplier bill is determined to be a matching failure; and duplicate accounts are marked for duplicate system orders or supplier bills to generate corresponding preliminary matching results.

[0110] In one embodiment, when the processor executes the computer program, the following steps are also implemented: a result page is generated based on the preliminary matching results and the reconciliation results; the reconciliation results of each system order, exception records and at least one exception handling button are displayed on the result page; the exception records include record information of abnormal system orders or abnormal supplier bills, abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and abnormal supplier bills include abnormal suppliers that fail preliminary matching or have duplicate accounts; the exception handling buttons include difference data confirmation buttons or delayed settlement option buttons; and the result page is displayed.

[0111] In one embodiment, when the processor executes the computer program, the following steps are also implemented: in response to the triggering operation of the difference data confirmation button on the result page, the selected system order and / or supplier bill is marked as confirmed; in response to the triggering operation of the delayed settlement option button on the result page, the selected system order and / or supplier bill is marked as pending.

[0112] In one embodiment, when the processor executes the computer program, it also implements the following steps: receiving a manually imported supplier bill; verifying the data in the received supplier bill under preset key fields; if the verification fails, issuing an import failure prompt and providing erroneous data to the user.

[0113] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: determining the supplier bill associated with each system order; obtaining a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of calculation rules, comparison options, matching rules and error prompts; according to the calculation rules of the multiple order fields, the data in the supplier bill is calculated to obtain the bill data corresponding to the multiple order fields; according to the comparison options, multiple target fields to be matched are determined; for each target field, according to the matching rules of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result; if the matching result indicates a matching failure, an error prompt for the target field is output; according to the matching results of the multiple target fields, the reconciliation result between the system order and the supplier bill is determined.

[0114] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: automatically searching for system orders based on the reconciliation time range, and calling the interface of the supplier system to obtain the supplier bill corresponding to the reconciliation time range from the supplier system; preliminarily matching the found system orders with the obtained supplier bills to obtain preliminary matching results; and determining the supplier bills associated with each system order based on the preliminary matching results.

[0115] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the target system order cannot be matched to the associated supplier bill, the preliminary matching result of the target system order is determined to be a matching failure; if the target supplier bill cannot be matched to the associated system order, the preliminary matching result of the target supplier bill is determined to be a matching failure; duplicate system orders or supplier bills are marked with account duplications to generate corresponding preliminary matching results.

[0116] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: a result page is generated based on the preliminary matching results and the reconciliation results; the reconciliation results of each system order, exception records and at least one exception handling button are displayed on the result page; the exception records include record information of abnormal system orders or abnormal supplier bills, abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and abnormal supplier bills include abnormal suppliers that fail preliminary matching or have duplicate accounts; the exception handling buttons include difference data confirmation buttons or delayed settlement option buttons; and the result page is displayed.

[0117] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to the triggering operation of the difference data confirmation button on the result page, the selected system order and / or supplier bill is marked as confirmed; in response to the triggering operation of the delayed settlement option button on the result page, the selected system order and / or supplier bill is marked as pending.

[0118] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented: receiving a manually imported supplier bill; verifying the data in the received supplier bill under preset key fields; if the verification fails, issuing an import failure prompt and providing erroneous data to the user.

[0119] In one embodiment, a computer program product is provided, including a computer program, which implements the following steps when executed by a processor: determining a supplier bill associated with each system order; obtaining a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of calculation rules, comparison options, matching rules and error prompts; according to the calculation rules of the multiple order fields, the data in the supplier bill is calculated to obtain bill data corresponding to the multiple order fields; according to the comparison options, multiple target fields to be matched are determined; for each target field, according to the matching rules of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result; if the matching result indicates a matching failure, an error prompt for the target field is output; according to the matching results of the multiple target fields, the reconciliation result between the system order and the supplier bill is determined.

[0120] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: automatically searching for system orders based on the reconciliation time range, and calling the interface of the supplier system to obtain the supplier bill corresponding to the reconciliation time range from the supplier system; preliminarily matching the found system orders with the obtained supplier bills to obtain preliminary matching results; and determining the supplier bills associated with each system order based on the preliminary matching results.

[0121] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the target system order cannot be matched to the associated supplier bill, the preliminary matching result of the target system order is determined to be a matching failure; if the target supplier bill cannot be matched to the associated system order, the preliminary matching result of the target supplier bill is determined to be a matching failure; duplicate system orders or supplier bills are marked with account duplications to generate corresponding preliminary matching results.

[0122] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: a result page is generated based on the preliminary matching results and the reconciliation results; the reconciliation results of each system order, exception records and at least one exception handling button are displayed on the result page; the exception records include record information of abnormal system orders or abnormal supplier bills, abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and abnormal supplier bills include abnormal suppliers that fail preliminary matching or have duplicate accounts; the exception handling buttons include difference data confirmation buttons or delayed settlement option buttons; and the result page is displayed.

[0123] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to the triggering operation of the difference data confirmation button on the result page, the selected system order and / or supplier bill is marked as confirmed; in response to the triggering operation of the delayed settlement option button on the result page, the selected system order and / or supplier bill is marked as pending.

[0124] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented: receiving a manually imported supplier bill; verifying the data in the received supplier bill under preset key fields; if the verification fails, issuing an import failure prompt and providing erroneous data to the user.

[0125] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0126] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0127] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0128] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A reconciliation method, characterized in that: The method comprises: Determine the vendor bills associated with each system order; Obtaining a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of a calculation rule, a comparison option, a matching rule, and an error prompt; Calculate the data in the supplier bill according to the calculation rules of the multiple order fields to obtain bill data corresponding to the multiple order fields; According to the comparison options, determining multiple target fields to be matched; For each target field, according to the matching rule of the target field, the data of the system order under the target field is matched with the bill data corresponding to the target field to obtain a matching result; If the matching result indicates a matching failure, an error prompt for the target field is output; A reconciliation result between the system order and the supplier bill is determined based on the matching results of the multiple target fields.

2. The method according to claim 1, characterized in that Determining the supplier bill associated with each system order includes: Automatically search for system orders according to the reconciliation time range, and call the interface of the supplier system to obtain the supplier bill corresponding to the reconciliation time range from the supplier system; Preliminarily match the found system order with the obtained supplier bill to obtain a preliminary matching result; Based on the preliminary matching results, the supplier bill associated with each system order is determined.

3. The method according to claim 2, characterized in that The method further comprises: If the target system order cannot be matched to the associated supplier bill, determining the preliminary matching result of the target system order as a matching failure; If the target supplier bill cannot be matched to the associated system order, determining the preliminary matching result of the target supplier bill as a matching failure; Mark duplicate system orders or supplier bills with duplicate accounting marks and generate corresponding preliminary matching results.

4. The method according to claim 3, characterized in that The method further comprises: A result page is generated according to the preliminary matching result and the reconciliation result; the result page displays the reconciliation result of each system order, an abnormal record and at least one abnormal processing button; the abnormal record includes the record information of abnormal system orders or abnormal supplier bills, the abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and the abnormal supplier bills include abnormal suppliers that fail preliminary matching or have duplicate accounts; the abnormal processing buttons include a difference data confirmation button or a delayed settlement option button; The result page is displayed.

5. The method according to claim 4, characterized in that The method further comprises: In response to a triggering operation on the difference data confirmation button on the result page, marking the selected system order and / or supplier bill as confirmed; In response to a triggering operation on the delayed settlement option button on the result page, the selected system order and / or supplier bill is marked as pending.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Receive manually imported vendor bills; Verify the data in the received supplier bill under the preset key fields; If the verification fails, an import failure prompt will be issued and incorrect data will be provided to the user.

7. A reconciliation device, characterized in that: The device comprises: A determination module for determining the supplier bill associated with each system order; An acquisition module, used to acquire a reconciliation template; the reconciliation template includes configuration information of multiple order fields, and the configuration information includes at least one of a calculation rule, a comparison option, a matching rule, and an error prompt; A calculation module, used to calculate the data in the supplier bill according to the calculation rules of the multiple order fields to obtain bill data corresponding to the multiple order fields; A matching module, used for determining a plurality of target fields to be matched according to the comparison options; for each target field, according to the matching rule of the target field, matching the data of the system order under the target field with the bill data corresponding to the target field to obtain a matching result; if the matching result indicates a matching failure, an error prompt of the target field is output; A reconciliation module is used to determine the reconciliation result between the system order and the supplier bill according to the matching results of the multiple target fields.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images