Accounting method and device, computer device, readable storage medium and program product

Abstract

The application relates to a reconciliation method and device, a computer device, a computer readable storage medium and a computer program product. The method comprises the following steps: determining a supplier invoice associated with each system order; obtaining a reconciliation template; calculating data in the supplier invoice according to a calculation rule of a plurality of order fields to obtain invoice data corresponding to the plurality of order fields; determining a plurality of target fields to be matched according to a comparison option; matching the system order with the invoice data according to a matching rule of the target fields to obtain a matching result; outputting an error prompt if the matching result represents a matching failure; and determining a reconciliation result according to the matching result of the plurality of target fields. The method automatically matches and checks the cost information between the supplier, ensures the comprehensiveness and accuracy of the reconciliation, and reduces manual errors; the self-defined reconciliation template can meet the diversified needs of enterprises and improve the flexibility and efficiency of the reconciliation settlement.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, in particular to an account reconciliation method and device, a computer device, a computer readable storage medium and a computer program product. BACKGROUND

[0002] At present, in order to achieve better production and operation, more and more high-quality resource suppliers are introduced into enterprises, and service resources are optimized, resulting in heavier account reconciliation work. In addition, low collaboration efficiency on the supplier side is also one of the problems to be solved in current enterprise operation management. At present, a complete online collaboration mechanism has not yet been formed between suppliers and operators, and more reliance is placed on offline communication. This communication method is not only inefficient and prone to errors, but also may lead to information opacity and asymmetry, increasing the financial risk and operation cost of enterprises. The account reconciliation and settlement work is complex and tedious, and information opacity and asymmetry will greatly affect the efficiency of account reconciliation and settlement.

[0003] In recent years, with the rapid development of information technology and the widespread application of Internet technology, more and more operation companies have begun to realize the great potential of online automated tools in improving the efficiency and accuracy of account reconciliation. However, the current online account reconciliation tools have single functions and lack comprehensiveness and flexibility, and cannot meet the diversified needs of enterprises for account reconciliation. SUMMARY

[0004] Therefore, it is necessary to provide an account reconciliation method, device, computer device, computer readable storage medium and computer program product to automatically match and check the cost information between the supplier and generate accurate account reconciliation results.

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

[0006] determining a supplier invoice associated with each system order;

[0007] obtaining an account reconciliation template; the account reconciliation template includes configuration information of a plurality of 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] calculating the data in the supplier invoice according to the calculation rule of the plurality of order fields to obtain invoice data corresponding to the plurality of order fields;

[0009] determining a plurality of target fields to be matched according to the comparison option;

[0010] for each target field, matching the data of the system order under the target field with the invoice data corresponding to the target field according to the matching rule of 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] Determine the reconciliation results between system orders and supplier invoices 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] Perform a preliminary match between the found system order and 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 results and 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 records of abnormal system orders or abnormal supplier invoices. Abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and abnormal supplier invoices include supplier invoices that fail preliminary matching or have duplicate accounts. The exception handling buttons include a button to confirm discrepancies or a button to delay settlement.

[0023] Display the result page.

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

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

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

[0027] In one of the embodiments, the method further comprises:

[0028] receiving a manually imported supplier invoice;

[0029] checking the data in the received supplier invoice under preset key fields;

[0030] If the checking fails, an import failure prompt is issued, and the user is provided with error data.

[0031] In a second aspect, the application further provides an account checking device, comprising:

[0032] a determination module configured to determine a supplier invoice associated with each system order;

[0033] an acquisition module configured to acquire an account checking template; the account checking template comprises configuration information of a plurality of order fields, and the configuration information comprises at least one of a calculation rule, a comparison option, a matching rule, and an error prompt;

[0034] a calculation module configured to calculate the data in the supplier invoice according to the calculation rule of the plurality of order fields, to obtain invoice data corresponding to the plurality of order fields;

[0035] a matching module configured to determine a plurality of target fields to be matched according to the comparison option; for each target field, the data of the system order under the target field is matched with the invoice data corresponding to the target field according to the matching rule of the target field, to obtain a matching result; and if the matching result represents a matching failure, an error prompt of the target field is output;

[0036] an account checking module configured to determine an account checking result between the system order and the supplier invoice according to the matching results of the plurality of target fields.

[0037] In a third aspect, the application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method of the first aspect when executing the computer program.

[0038] In a fourth aspect, the application further provides a computer readable storage medium, which stores a computer program, and the computer program implements the steps of the method of the first aspect when executed by a processor.

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

[0040] The account checking method, device, computer device, computer readable storage medium and computer program product determine a supplier invoice associated with each system order, obtain an account checking template, the account checking template includes configuration information of a plurality of order fields, the configuration information includes at least one of a calculation rule, a comparison option, a matching rule and an error prompt, calculate data in the supplier invoice according to the calculation rule of the plurality of order fields to obtain invoice data corresponding to the plurality of order fields, determine a plurality of target fields to be matched according to the comparison option, for each target field, match data of the system order under the target field with invoice data corresponding to the target field according to the matching rule of the target field to obtain a matching result, if the matching result represents a matching failure, output an error prompt of the target field, and determine an account checking result between the system order and the supplier invoice according to the matching result of the plurality of target fields. In this way, based on the self-defined account checking template, the cost information between the supplier can be automatically matched and checked, and an accurate account checking result can be generated, so that the comprehensiveness and accuracy of the account checking are ensured, manual errors are reduced, the time cost of the enterprise for account checking is greatly reduced, and the operation efficiency of the enterprise is improved. The self-defined account checking template can meet diversified needs of the enterprise, and improve the flexibility and efficiency of the account checking and settlement. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description only some embodiments of the present application, and for those skilled in the art, other related drawings can be obtained without creative labor on the basis of these drawings.

[0042] Figure 1 An application environment diagram of the account checking method in an embodiment;

[0043] Figure 2 A flowchart of the account checking method in an embodiment;

[0044] Figure 3 A page diagram of a newly created account checking template in an embodiment;

[0045] Figure 4 A diagram of a supplier invoice in an embodiment;

[0046] Figure 5 A diagram of a result page in an embodiment;

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

[0048] Figure 7A structural block diagram of the reconciliation device in one embodiment;

[0049] Figure 8 An internal structural diagram of the computer device in one embodiment. DETAILED DESCRIPTION

[0050] In order to make the purposes, technical solutions and advantages of the present application clearer, the present application is further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and not to limit the present application.

[0051] The reconciliation method provided by the embodiments of the present application can be applied to an application environment as shown in Figure 1 . The terminal 102 communicates with the server 104 through a network. The terminal 102 logs in the platform corresponding to the server 104 through a browser or an application program, and shows a relevant page to a user; in response to an operation of the user, the terminal 102 completes functions such as user login, data import, reconciliation settlement, and bill cover download. The server 104 is connected with each supplier system 106 through an API interface, and realizes 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 bill data; the server 104 performs reconciliation processing based on the reconciliation method provided by any one of the embodiments of the present application, and sends the processed reconciliation result to the supplier system 106, so as to perform subsequent settlement operations. The server 104 interacts with a database, and stores and retrieves data and information generated in the reconciliation process. The terminal 102 can be, but is not limited to, various personal computers, notebook computers, smart phones, and tablet computers. The server 104 can be a stand-alone physical server, or a server cluster or distributed system formed by multiple physical servers, or a cloud server providing cloud computing services.

[0052] In one exemplary embodiment, as shown in Figure 2 , a reconciliation method is provided, and the method is described by taking the server 104 in Figure 1 as an example, and includes the following steps.

[0053] In step 202, a supplier bill associated with each system order is determined.

[0054] The server stores a plurality of system orders, and the system order refers to a transaction record and basis stored by an operator. The supplier bill refers to transaction information stored in a supplier system. Optionally, the system order and the supplier bill that need to be reconciled are quickly determined by bidirectional searching in the server and the supplier system.

[0055] In an optional implementation, the system order and the supplier invoice need to be pre-processed before being processed, including parsing of the invoice file, conversion of the data format, processing of abnormal data, etc., so as to improve the quality and availability of the data.

[0056] In step 204, an account template is obtained. The account template includes configuration information of a plurality of 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] The account template is configured by a user according to a business requirement and a supplier account rule on a server, and is used for account. The account template defines a corresponding relationship between the system order and the supplier invoice, a calculation rule, a comparison option, a matching rule, an error prompt, etc., and is used for guiding the system to automatically perform account processing.

[0058] In an optional implementation, the server manages the account templates corresponding to the systems of various suppliers. In the current processing flow, the corresponding account template is searched in the storage space according to the identification of the supplier that needs to be accounted.

[0059] In an optional implementation, the account template is searched according to the identification of the supplier that needs to be accounted. Figure 3 , Figure 3 A page schematic diagram for creating an account template is shown. A user can customize different account templates through the page. The user can add or delete customized information for each order field, define an account template column of each order field, a calculation rule, a comparison option, a matching rule, and an error reason based on the page. The merging processing of the account data is supported, and the flexibility and accuracy of the account are improved. The user can flexibly configure the account template according to the actual business requirement, so as to adapt to different account scenarios.

[0060] It can be understood that the calculation rule is used to define a calculation operation that needs to be performed in the account process, and indicates that the value under the A field and the value under the B field in the supplier invoice need to be calculated in a certain way. 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 invoice. The matching rule is used to indicate the comparison rule between the system order and the supplier invoice. For example, if the value under the order field is greater than the corresponding value in the supplier invoice, the matching is successful, otherwise the matching fails. The error prompt is used to show the specific error information to the user when a difference is found in the comparison process, so as to help the user find the error reason 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 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 based on 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] The matching rule determines how the target field's data is compared with the corresponding billing data. Examples include exact match (identical data), fuzzy match (using a predefined algorithm to calculate similarity), and so on. Based on the matching rule, the system order data in the target field is compared with the corresponding billing data, and which target fields successfully match 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 : Determine the reconciliation result between the system order and the supplier invoice based on the matching results of the multiple target fields.

[0070] The matching results for each target field between the system order and the supplier invoice are recorded. If all target fields match successfully, the reconciliation between the system order and the supplier invoice is considered a successful match. If any target field fails to match, the reconciliation between the system order and the supplier invoice is considered a failed match, and an error message indicating the failed match for the target field is added to the corresponding field.

[0071] As you can understand, the automatic reconciliation process supports bidirectional search and error detection. Bidirectional search means that the server searches both system orders for records that match supplier invoices and supplier invoices for records that match system orders. Error detection means that during the comparison process, the server determines whether there are any discrepancies based on the configured comparison options, matching rules, and calculation rules, and generates a discrepancy report. The discrepancy report includes the discrepancy type, detailed information, and the reason for the discrepancy.

[0072] In one optional implementation, during the reconciliation process, real-time recording of information such as reconciliation status, reconciled amounts, invoiced amounts, and collected amounts facilitates user monitoring and tracking of reconciliation progress. A real-time reconciliation data display function allows users to view reconciliation information between system orders and supplier invoices at any time. Reconciliation data is presented in a clear and intuitive tabular format, facilitating accurate analysis and decision-making. Reconciliation results are updated in real time to ensure data accuracy and consistency.

[0073] In an optional implementation, a one-click statement cover function 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, making it convenient for users to print, archive or send it.

[0074] In the above reconciliation method, the supplier bills associated with each system order are determined; a reconciliation template is obtained; the reconciliation template includes configuration information for multiple order fields, the configuration information including at least one of calculation rules, comparison options, matching rules, and error prompts; data in the supplier bill is calculated according to the calculation rules for the multiple order fields to obtain bill data corresponding to the multiple order fields; multiple target fields are determined based on the comparison options; for each target field, the system order data under the target field is matched with the bill data corresponding to the target field according to the matching rules for the target field to obtain a matching result; if the matching result indicates a match failure, an error prompt for the target field is output; and based on the matching results for the multiple target fields, a reconciliation result between the system order and the supplier bill is determined. Through the above method, based on a customized reconciliation template, expense information with suppliers can be automatically matched and verified, generating accurate reconciliation results. This ensures the comprehensiveness and accuracy of reconciliation, reduces manual errors, and thus significantly reduces the time and cost of enterprise reconciliation and improves the enterprise's operational efficiency. Supporting customized reconciliation templates can meet the diverse needs of enterprises and enhance the flexibility and efficiency of reconciliation and settlement.

[0075] In an exemplary embodiment, step 202 includes: 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.

[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 timed task, that is, the server supports a periodic reconciliation function. Figure 4 , Figure 4 This diagram shows a supplier bill in one embodiment. The server connects to the supplier's system via an API and automatically retrieves the supplier bill, including the order number, product information, and amount. After data acquisition is complete, the server preprocesses the data, including data cleaning and format conversion, to ensure data accuracy and consistency.

[0077] In an optional implementation, the server records the reconciliation time range based on 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 further includes: if the target system order cannot be matched to the associated supplier bill, determining the preliminary matching result of the target system order to be 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 to be 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 preliminarily 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 further 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 supplier bills 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] The preliminary matching and reconciliation results generated in the aforementioned steps are displayed, and an exception handling button is provided for the user to use. It is understood that if a system order that failed the preliminary matching is found in the aforementioned steps, the system order will be displayed on the results page; if no exception records are found in the aforementioned steps, only the reconciliation results may be displayed. The content displayed on the results page in this embodiment is related to the preliminary matching and reconciliation results. Methods such as manual discrepancy confirmation and delayed settlement are provided for handling reconciliation discrepancy data.

[0084] In an optional implementation, referring to Figure 5 , Figure 5 This is a schematic diagram of a results page in one embodiment. The results page displays billing and order information, along with the comparison results (i.e., reconciliation results). For system orders and supplier bills that fail the initial match, a prompt stating "System order not found" or "Supplier bill not found" appears in the comparison results. A page switching function is provided, allowing users to trigger actions to switch to pages such as discrepant orders, delayed settlement, or reconciled accounts.

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

[0086] After the results page is generated, users can process the discrepancies. The results page provides a button to confirm the discrepancies or a button to delay settlement. Users can choose the appropriate processing method based on their specific situation. For discrepancies that have been confirmed to be correct, users can mark them as processed and update the supplier reconciliation status. For discrepancies that require delayed settlement, users can mark them as pending and re-check and confirm them later. After confirming the reconciliation is correct, users can update the supplier reconciliation status to reconciled, ending 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] Among them, 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 Schematic diagram of an import failure prompt in an embodiment; the 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 rules; 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 verification 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 various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed 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 portion of steps or stages in other steps.

[0091] Based on the same inventive concept, embodiments of the present application also provide a reconciliation device for implementing the aforementioned reconciliation method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of one or more embodiments of the reconciliation device provided below can be found in the above-described limitations of the reconciliation method and will not be further elaborated here.

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

[0093] The determination module 702 is configured 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 calculation rules, comparison options, matching rules, and error prompts.

[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 bill data corresponding to the multiple order fields.

[0096] Matching module 708 is used to determine multiple target fields to be matched based on 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 for the target field is output.

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

[0098] The aforementioned reconciliation device, based on customizable reconciliation templates, can automatically match and verify expense information with suppliers, generating accurate reconciliation results. This ensures comprehensiveness and accuracy, reduces manual errors, and significantly reduces the time and cost of reconciliation for businesses, improving operational efficiency. Supporting customizable reconciliation templates can meet the diverse needs of businesses and enhance 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 with the associated supplier bill, the preliminary matching result of the target system order is a matching failure; if the target supplier bill cannot be matched with 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, abnormal system orders include system orders that fail preliminary matching or have duplicate accounts, and abnormal supplier bills include supplier bills 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 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 in 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 aforementioned reconciliation device may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of 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, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. 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 shown in the figure, or combine certain components, or have a different component arrangement.

[0107] In an exemplary embodiment, a computer device is provided, comprising 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 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; based on 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, it also implements the following steps: 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 a preliminary matching result; and determining the supplier bills associated with each system order based on the preliminary matching result.

[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 account marks 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, it also implements the following steps: 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 supplier bills 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.

[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, which, when executed by a processor, implements the following steps: determining a supplier bill associated with each system order; obtaining a reconciliation template; the reconciliation template includes configuration information of multiple order fields, the configuration information including at least one of calculation rules, comparison options, matching rules and error prompts; calculating 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; determining multiple target fields to be matched according to the comparison options; for each target field, matching the data of the system order under the target field with the bill data corresponding to the target field according to the matching rules of the target field to obtain a matching result; if the matching result indicates a matching failure, outputting an error prompt for the target field; and determining the reconciliation result between the system order and the supplier bill according to the matching results of the multiple target fields.

[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 an account duplication mark to generate a corresponding preliminary matching result.

[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 supplier bills 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 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, comprising a computer program, which, when executed by a processor, implements the following steps: determining a supplier bill associated with each system order; obtaining a reconciliation template; the reconciliation template includes configuration information of multiple order fields, the configuration information including at least one of calculation rules, comparison options, matching rules, and error prompts; calculating 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; determining multiple target fields to be matched according to the comparison options; for each target field, matching the data of the system order under the target field with the bill data corresponding to the target field according to the matching rules of the target field to obtain a matching result; if the matching result indicates a matching failure, outputting an error prompt for the target field; and determining the reconciliation result between the system order and the supplier bill according to the matching results of the multiple target fields.

[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 an account duplication mark to generate a corresponding preliminary matching result.

[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 supplier bills 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 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] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented 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 memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile memory and volatile memory. Non-volatile memory may 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 may include random access memory (RAM) or external cache memory, etc. By way of 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 the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, an artificial intelligence (AI) processor, and the like.

[0127] The technical features of the above embodiments can be combined arbitrarily. In order 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 merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended 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, the configuration information including calculation rules, comparison options, matching rules, and error prompts; Calculating 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; Determining 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 message 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 based on the reconciliation time range, and call the supplier system interface to obtain the supplier bill corresponding to the reconciliation time range from the supplier system; Perform a preliminary match between the found system order and 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 based on the preliminary matching result and the reconciliation result; the result page displays the reconciliation result of each system order, an exception record, and at least one exception handling button; the exception record includes record information of an abnormal system order or an abnormal supplier invoice, the abnormal system order includes a system order that fails preliminary matching or has duplicate accounts, and the abnormal supplier invoice includes a supplier invoice that fails preliminary matching or has duplicate accounts; the exception handling button includes 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 preset key fields of the received supplier bill; 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 is used to acquire a reconciliation template; the reconciliation template includes configuration information of multiple order fields, the configuration information including calculation rules, comparison options, matching rules and error prompts; a calculation module, configured to calculate the data in the supplier bill according to calculation rules for the multiple order fields to obtain bill data corresponding to the multiple order fields; a matching module configured to determine, based on the comparison options, a plurality of target fields to be matched; for each target field, matching the data of the system order under the target field with the bill data corresponding to the target field according to the matching rules of the target field to obtain a matching result; and outputting an error prompt for the target field if the matching result indicates a matching failure; A reconciliation module is used to determine a reconciliation result between the system order and the supplier bill based on 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