Intelligent allocation method for combined settlement funds

Abstract

The invention relates to an intelligent allocation method for combined settlement funds. The method comprises the following steps: collecting key data from various business receipts and storing the key data; extracting the sorted key data, and judging a specific business scene to which the business belongs; according to the business scene, calling a corresponding fund allocation priority algorithm, and calculating a settlement amount, a settled amount, an unsettled amount and a verification amount of each business document; and feeding back a calculation result to a business document system and a financial system, and updating amount data of related documents. According to the invention, dynamic adjustment can be carried out according to the characteristics, the time sequence and the amount weight of the business document, so that the rationality and accuracy of fund allocation are ensured; the allocation efficiency is improved, and the complexity and the error rate of manual operation are reduced, so that the fund flow management is optimized; the flexibility and adaptability of the system are enhanced, and individual requirements of enterprises in different business scenes can be better met.

Description

Technical Field

[0001] This invention relates to the field of accounts receivable management technology in enterprise resource planning (ERP) systems, specifically a method for intelligent allocation of consolidated settlement funds. Background Technology

[0002] In Enterprise Resource Planning (ERP) systems, the processing of various business documents, such as sales orders, return orders, return orders, and expense orders, involves the statistics and settlement of funds. These documents have corresponding operation functions on both PC and mobile app platforms, forming the basic source of business data.

[0003] In the existing system, due to the complexity and diversity of enterprise business, multiple business scenarios trigger consolidated settlement. This is because the need for fund interaction between different business documents prompts consolidated settlement. For example:

[0004] In combined sales visits or mobile sales scenarios, both sales orders and return orders are involved. Sales orders represent the sale of goods, while return orders represent the return of goods; their cash flows are opposite. To accurately calculate the accounts receivable, received, and outstanding cash in this scenario, the cash from sales orders and return orders needs to be consolidated. This process requires consolidating the cash from sales orders and return orders to determine the pre-receipt amount, outstanding amount, settled amount, and outstanding amount for each order, clearly presenting the cash situation of this business.

[0005] Accounts Receivable Reconciliation and Settlement: Accounts receivable reconciliation optimizes customer settlement statements, generating settlement statements from sales orders (including orders for free gifts), return orders, return slips, customer expense slips, and customer accounts receivable initialization slips. These documents generate different cash flow changes during the business process. To ensure distributors have a clear understanding of their accounts receivable and accurately grasp the overall situation of accounts receivable, consolidated settlement is necessary. Signed sales orders, returned orders, signed return slips, approved customer expense slips (excluding full-order discounts and allowances), and approved customer accounts receivable initialization slips will participate in accounts receivable reconciliation and settlement. Through consolidated settlement, the settlement status of all accounts receivable documents can be viewed, and outstanding or partially settled settlement statements can be settled individually or in batches.

[0006] Overdue Payment Collection: Overdue payment collection involves the processing of funds from various business documents. In scenarios such as combined vehicle sales invoicing, accounts receivable reconciliation, overdue payment collection, driver settlement, and creating payment receipts (manually selecting documents), there may be outstanding amounts from various documents such as sales orders, return orders, and expense orders. To manage and settle these outstanding amounts uniformly, consolidated settlement is required. In this case, consolidated settlement is necessary to allocate the collected amount to each document according to certain rules, calculating the settlement amount, settled amount, and outstanding amount for each document, thus completing the fund processing for overdue payment collection.

[0007] Driver Settlement: After the driver signs for the delivery, outstanding amounts related to sales orders and return orders need to be processed. When settling accounts with the driver, it's necessary to calculate the total outstanding amounts for all sales orders and all return orders within that delivery order, and then settle them collectively. This is because a driver's delivery business may involve both sales and returns. To clearly account for the driver's income and the company's financial transactions, these outstanding amounts need to be consolidated for settlement, ensuring the accuracy of financial data and the integrity of the business process.

[0008] In practice, the following problems were found in the existing consolidated settlement operation:

[0009] Existing consolidated settlement systems have complex rules and lack unified standards for fund allocation. In scenarios involving advance payments, receipts are only associated with sales orders, and refunds are only associated with return orders. Outstanding amounts are recorded as outstanding payments after receipt / recovery and then settled. However, in practice, differences in receipt / recovery times complicate fund allocation and are prone to errors. When collecting outstanding payments, the different allocation logics for "sales > refund + expenses" and "sales < refund + expenses" increase operational difficulty. The distinction between manual and automatic order matching scenarios further complicates the allocation rules.

[0010] The existing consolidated settlement system cannot intelligently identify business scenarios and adaptively adjust the fund allocation method. It cannot adjust the time sequence and amount weight in real time according to business changes. When factors such as the number, amount, and time of business documents change, it is difficult to respond flexibly, resulting in unreasonable fund allocation and affecting the accuracy and timeliness of financial data.

[0011] Consolidated settlement involves financial information from various business documents, but this information is displayed in a scattered manner within the system. On the PC and mobile app platforms, financial data from documents such as sales orders, return orders, and receipts are distributed across different pages and modules. This requires finance personnel to frequently switch between these pages for verification and management, resulting in low efficiency and the risk of overlooking important information, which hinders an accurate grasp of the overall consolidated settlement situation.

[0012] The consolidated settlement process is cumbersome and lacks coherence. Data exchange between different business documents and financial processes is not smooth. From the occurrence of a business to the final settlement, the links are not tightly connected. For example, there are gaps in the process between sales order issuance, return order processing and subsequent collection of payments and settlement statement generation, which affects business processing efficiency and the speed of fund recovery.

[0013] The information disclosed in this background section is intended only to enhance the understanding of the general background of the invention and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0014] To address the shortcomings of existing technologies, the present invention aims to provide a method for intelligent allocation of consolidated settlement funds. This method can dynamically adjust the allocation based on the characteristics, time sequence, and amount weight of business documents, ensuring the rationality and accuracy of fund allocation. It improves allocation efficiency, reduces the complexity and error rate of manual operations, thereby optimizing fund flow management. It also enhances the flexibility and adaptability of the system, better meeting the personalized needs of enterprises in different business scenarios.

[0015] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0016] A method for intelligent allocation of consolidated settlement funds, characterized by comprising:

[0017] Key data is collected from various business documents, and the key data is initially sorted and verified to ensure the accuracy and integrity of the data before being stored in the system database.

[0018] The business documents include sales orders, return orders, expense orders, and customer accounts receivable initialization orders;

[0019] The key data includes order amount, total order discount, amount received, and amount refunded;

[0020] After extracting and organizing the data from the database, the specific business scenario to which the business belongs is determined based on the preset recognition rules;

[0021] The business scenarios include: prepayment collection business scenarios and overdue payment collection business scenarios.

[0022] Based on the identified business scenario, the corresponding fund allocation priority algorithm is called from the algorithm library to calculate the settlement amount, settled amount, outstanding amount and write-off amount for each business document;

[0023] The calculation results are fed back to the business document system and financial system through the system interface to update the amount data of the relevant documents;

[0024] The relevant documents include settlement statements, receipts, and advance payment receipts.

[0025] Based on the above technical solution, the preliminary processing and verification of key data specifically includes:

[0026] Perform data format standardization checks to ensure that numerical data such as order amount and amount received are in the correct format, and avoid data processing anomalies caused by incorrect format;

[0027] Perform data logic validation. If logical errors are found, promptly prompt the operators to correct or supplement the data.

[0028] Based on the above technical solution, when storing in the system database, during the initialization of tables and table items, a "Document Type" field is added to the table to identify the type of each document with a fixed code or string;

[0029] By adding a "timestamp" field to the table, the creation time and update time of each document can be identified;

[0030] Combining document types with timestamps provides a more flexible way to store and retrieve data.

[0031] Based on the above technical solution, if it is detected that the payment is only associated with the sales order, the refund is only associated with the return order, and the outstanding amount is recorded as a debt after the receipt / recovery, then it is determined to be a prepayment business scenario;

[0032] The system checks whether the transactions involve vehicle sales combination order creation, accounts receivable reconciliation settlement, collection of outstanding payments, driver settlement, and creation of payment receipts with manual document selection. If these operations exist and there are outstanding business documents, then the system is identified as a collection of outstanding payments business scenario.

[0033] Based on the above technical solutions, when determining business scenarios, the system can further obtain the source port of the documents and the order of business operations to achieve accurate identification of business scenarios.

[0034] Based on the above technical solutions, the determination of the document source port specifically includes:

[0035] For scenarios involving advance payment collection: When the system obtains the source port information of a business document, if it is from the APP and the document source is a sales representative or a mobile sales representative (including sales display redemption and mobile sales display redemption), the system will check for combined order creation. If so, it will further confirm that the payment is only associated with the sales order and the refund is only associated with the return order. If these conditions are met, the relevant information will be recorded and the process will proceed to the business operation sequence judgment. If these conditions are not met, the scenario will be directly excluded as an advance payment collection scenario, and the process will proceed to other scenario judgment procedures. If the document source port is from the PC, cloud platform, B2B platform, WMS, etc., the system will check the association between the payment and refund and the sales order and return order according to the specific business rules of the corresponding platform or port. If the association characteristics of advance payment collection are met, the relevant information will be recorded and the process will proceed to other scenario judgment procedures. Otherwise, the scenario will be excluded as an advance payment collection scenario, and the process will proceed to other scenario judgment procedures.

[0036] For overdue payment collection scenarios, the system obtains the source port information of the business documents. If the process involves operations such as vehicle sales combination order creation, accounts receivable reconciliation settlement, overdue payment collection, driver settlement, or creating a payment collection order and manually selecting documents, the system will check whether there are any outstanding business documents (sales orders, return orders, expense orders, etc.). If there are outstanding documents, the relevant information is recorded and entered into the business operation sequence for judgment. If all documents have been settled, the scenario is excluded as an overdue payment collection scenario, and the process moves to other scenario judgment procedures.

[0037] Based on the above technical solution, the determination of the business operation sequence specifically includes:

[0038] For scenarios involving advance payment collection: The system obtains the order of business operations based on timestamps. If an order is placed first, and the initial payment collection is associated with the sales order, the system will continuously monitor subsequent refund operations. If subsequent refund operations are only associated with return orders, and the outstanding amount is recorded as an arrears after receipt / recovery, the system determines that this is a scenario involving advance payment collection. If the payment is not associated with the sales order, or the refund is not associated with the return order, or the handling of the outstanding amount does not conform to the rules for advance payment collection, the scenario is excluded from the advance payment collection process, and the system proceeds to other scenario judgment procedures. If the operation order is disordered, such as refunding before payment collection, or the operation order does not conform to the logic of advance payment collection, the system directly excludes the scenario from the advance payment collection process and proceeds to other scenario judgment procedures.

[0039] For overdue payment collection scenarios, the system uses timestamps to obtain the order of business operations and checks if sales orders, return orders, expense orders, etc., were generated first. If this condition is met, and there is a manual selection of documents for payment collection, the system checks whether the payment collection operation conforms to the overdue payment collection business logic, such as whether it is processed according to the overdue payment collection fund allocation rules. If it does, the system determines that the business scenario is an overdue payment collection scenario. If it does not conform to the overdue payment collection business logic, such as abnormal association between the payment collection operation and the documents or non-compliance with the fund allocation rules, the scenario is excluded from the overdue payment collection business logic, and the process moves to other scenario judgment procedures. If the operation order does not conform to the overdue payment collection business logic, such as payment being collected before the business documents are generated, the system directly excludes the scenario from the overdue payment collection business logic and moves to other scenario judgment procedures.

[0040] Based on the above technical solution, in the scenario of receiving advance payments, the algorithm strictly follows the principle that payments are only associated with sales orders and refunds are only associated with return orders. After signing for / recovering the goods, the outstanding amount is treated as an arrears and then combined for settlement.

[0041] In the scenario of collecting outstanding payments, if sales exceed refunds plus expenses, the algorithm prioritizes writing off the negative amount and then distributes it in the order of sales order generation time from earliest to latest; if sales are less than refunds plus expenses, the algorithm prioritizes writing off the sales order amount and then distributes it in the order of negative document generation time from earliest to latest.

[0042] Based on the above technical solution, when the generation time is the same, the document with the smaller amount will be deducted first.

[0043] Based on the above technical solution, after the fund allocation calculation is completed, the calculation results are fed back to the business document system and the financial system by calling the preset system interface;

[0044] It automatically updates the amount data of relevant documents such as settlement statements, receipts, and advance payment receipts; and strictly follows the transaction processing principle during the update process.

[0045] When updating the settlement amount and settled amount of the settlement statement, the corresponding amounts of the relevant receipts and advance receipts are also updated simultaneously.

[0046] If any error occurs during the update process, the system will immediately initiate a rollback mechanism to undo the partially executed update operations, ensuring that the data is free of errors or inconsistencies.

[0047] The intelligent allocation method for consolidated settlement funds described in this invention has the following beneficial effects:

[0048] 1. It can dynamically adjust the allocation of funds based on the characteristics of business documents, combined with time sequence and amount weight, to ensure the rationality and accuracy of fund allocation;

[0049] 2. In different business scenarios such as collecting advance payments and collecting outstanding payments, this method can quickly match the corresponding fund allocation priority algorithm with its intelligent scenario recognition capability;

[0050] For example, when collecting outstanding payments and sales exceed refunds plus expenses, negative amounts are written off first, and then allocated according to the order in which the sales orders were generated; in scenarios involving collecting advance payments, sales orders are accurately linked to payments, and return orders are linked to refunds, making fund allocation more reasonable.

[0051] 3. Through an intelligent allocation calculation engine, the system can quickly process a large number of business documents, reduce manual intervention, avoid errors that are prone to occur in the processing of complex business data, and thus optimize cash flow management.

[0052] 4. This method enhances the system's flexibility and adaptability, allowing for flexible adjustment of the time sequence and monetary weights based on actual business changes, thus meeting the personalized needs of enterprises in different business scenarios.

[0053] This method integrates financial information scattered across various business documents, optimizes operational processes, and enhances the continuity of business operations, enabling financial personnel to more conveniently obtain and manage financial data, thereby comprehensively improving the efficiency and quality of financial settlement. Attached Figure Description

[0054] The present invention includes the following figures:

[0055] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0056] Figure 1 The flowchart of Embodiment 1 of the intelligent allocation method for consolidated settlement funds described in this invention. Detailed Implementation

[0057] The present invention will be further described in detail below with reference to the accompanying drawings. This detailed description is an illustration in conjunction with exemplary embodiments of the invention, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0058] The present invention discloses a method for intelligent allocation of consolidated settlement funds. The consolidated settlement refers to the unified settlement processing of funds involved in various business documents such as sales orders, return orders, expense orders, and customer accounts receivable initialization orders. In actual business scenarios, such as vehicle sales combined invoicing, driver settlement, accounts receivable reconciliation settlement, and collection of overdue payments, multiple business documents may be involved in fund interactions. Consolidated settlement can integrate and calculate these complex fund transactions, clearly presenting the company's accounts receivable, received, and outstanding funds, which facilitates financial management.

[0059] The aforementioned intelligent fund allocation is an operation that distributes funds involved in the consolidated settlement process to various relevant business documents according to certain rules. Since there are multiple document types in the business, and the amounts and statuses of each document are different, such as the order amount and whole-order discount of a sales order, and the refundable amount and already refunded amount of a return order, it is necessary to reasonably allocate the received or paid funds among these documents in order to accurately calculate the settlement amount, settled amount, outstanding amount and write-off amount of each document, and ensure the accuracy and consistency of financial data.

[0060] like Figure 1 As shown, the intelligent allocation method for consolidated settlement funds according to the present invention includes:

[0061] Key data is collected from various business documents, and the key data is initially sorted and verified to ensure the accuracy and integrity of the data before being stored in the system database.

[0062] The business documents include sales orders, return orders, expense orders, and customer accounts receivable initialization orders;

[0063] The key data includes order amount, total order discount, amount received, and amount refunded;

[0064] After extracting and organizing the data from the database, the specific business scenario to which the business belongs is determined based on the preset recognition rules;

[0065] The business scenarios include: prepayment collection business scenarios and overdue payment collection business scenarios.

[0066] Based on the identified business scenario, the corresponding fund allocation priority algorithm is called from the algorithm library to calculate the settlement amount, settled amount, outstanding amount and write-off amount for each business document;

[0067] The calculation results are fed back to the business document system and financial system through the system interface to update the amount data of the relevant documents;

[0068] The relevant documents include settlement statements, receipts, and advance payment receipts.

[0069] Based on the above technical solution, the preliminary processing and verification of key data specifically includes:

[0070] Perform data format standardization checks to ensure that numerical data such as order amount and amount received are in the correct format, and avoid data processing anomalies caused by incorrect format;

[0071] Perform data logic rationality verification. If logical errors are found in the data, promptly prompt the operators to correct or supplement it; for example, check whether the amount received is greater than the order amount (assuming no over-collection) and whether the overall order discount is positive, etc.

[0072] Based on the above technical solution, when storing in the system database, during the initialization of tables and table items, a "Document Type" field is added to the table to identify the type of each document with a fixed code or string;

[0073] By adding a "timestamp" field to the table, the creation time and update time of each document can be identified;

[0074] Combining document types with timestamps provides a more flexible way to store and retrieve data.

[0075] For example, different data tables are created in the database to store various business document data, such as sales order tables, return order tables, expense order tables, and customer receivable initialization order tables. Each table has fields designed according to the document characteristics. The sales order table sets fields such as order amount, overall order discount, customer information, salesperson, and warehouse; the return order table sets fields such as order amount, refundable discount, return reason, and returned goods warehouse. By adding a "Document Type" field to the tables, each document is identified by a fixed code or string, facilitating subsequent data querying and processing based on document type. For example, when querying all sales order data, the "Document Type" field value can be filtered to "Sales Order".

[0076] Taking a sales order as an example, when a new sales order is created, the system automatically retrieves the current time and writes it to the creation time field; subsequent changes to the order status and adjustments to the amount are synchronized with the updated time. During storage, the timestamp data uses a uniform format, such as "YYYY-MM-DD HH:MM:SS", ensuring accurate and consistent time records. Using the timestamp field, order data can be sorted chronologically, enabling order queries within a time range, such as querying sales orders within a specific time period, for analyzing business trends and changes in financial data.

[0077] When querying a database, data can be filtered using both document type and timestamp based on business needs to analyze data on a specific type of document within a particular time period. To improve query efficiency, a composite index can be created on the document type and timestamp fields. This allows the database system to locate and retrieve data faster, reducing query response time and improving system performance. For example, when analyzing sales trends for a quarter, a composite index can quickly retrieve the relevant data for statistical analysis.

[0078] Based on the above technical solution, if it is detected that the payment is only associated with the sales order, the refund is only associated with the return order, and the outstanding amount is recorded as a debt after the receipt / recovery, then it is determined to be a prepayment business scenario;

[0079] The system checks whether the transactions involve vehicle sales combination order creation, accounts receivable reconciliation settlement, collection of outstanding payments, driver settlement, and creation of payment receipts with manual document selection. If these operations exist and there are outstanding business documents, then the system is identified as a collection of outstanding payments business scenario.

[0080] Based on the above technical solutions, when determining business scenarios, the accurate identification of business scenarios can be achieved by further obtaining the document source port and business operation sequence;

[0081] The determination of the document source port specifically includes:

[0082] For scenarios involving advance payment collection: When the system obtains the source port information of a business document, if it is from the APP and the document source is a sales representative or a mobile sales representative (including sales display redemption and mobile sales display redemption), the system will check for combined order creation. If so, it will further confirm that the payment is only associated with the sales order and the refund is only associated with the return order. If these conditions are met, the relevant information will be recorded and the process will proceed to the business operation sequence judgment. If these conditions are not met, the scenario will be directly excluded as an advance payment collection scenario, and the process will proceed to other scenario judgment procedures. If the document source port is from the PC, cloud platform, B2B platform, WMS, etc., the system will check the association between the payment and refund and the sales order and return order according to the specific business rules of the corresponding platform or port. If the association characteristics of advance payment collection are met, the relevant information will be recorded and the process will proceed to other scenario judgment procedures. Otherwise, the scenario will be excluded as an advance payment collection scenario, and the process will proceed to other scenario judgment procedures.

[0083] For overdue payment collection scenarios, the system obtains the source port information of the business documents. If operations such as vehicle sales combination order creation, accounts receivable reconciliation settlement, overdue payment collection, driver settlement, and creating a payment collection order - manually selecting documents are involved, the system will check whether there are any outstanding business documents (sales orders, return orders, expense orders, etc.). If there are outstanding documents, the relevant information is recorded and entered into the business operation sequence for judgment. If all documents have been settled, the scenario is excluded as an overdue payment collection scenario, and the process moves to other scenario judgment procedures.

[0084] The specific steps for determining the order of business operations include:

[0085] For scenarios involving advance payment collection: The system obtains the order of business operations based on timestamps. If an order creation operation occurs first (the sales order and return order are generated before the payment collection and refund operations), and the initial payment collection operation is associated with the sales order, the system will continuously monitor subsequent refund operations. If subsequent refund operations are only associated with the return order, and the outstanding amount is recorded as an arrears after receipt / recovery, the system determines that this business scenario is a scenario involving advance payment collection. If the payment collection is not associated with the sales order, or the refund is not associated with the return order, or the handling of the outstanding amount does not conform to the rules for advance payment collection, then this scenario is excluded from the advance payment collection process, and the system proceeds to other scenario judgment procedures. If the operation order is disordered, such as refunding before payment collection, or the operation order does not conform to the logic of advance payment collection, the system directly excludes this scenario from the advance payment collection process and proceeds to other scenario judgment procedures.

[0086] For overdue payment collection scenarios, the system uses timestamps to obtain the order of business operations and checks if sales orders, return orders, expense orders, etc., were generated before the payment collection operation. If this condition is met, and there is a manual selection of documents for payment collection, the system checks if the payment collection operation conforms to the overdue payment collection logic, such as whether it is processed according to the overdue payment collection fund allocation rules. If it does, the system determines that the business scenario is an overdue payment collection scenario. If it does not conform to the overdue payment collection logic, such as abnormal association between the payment collection operation and the documents or non-compliance with the fund allocation rules, the scenario is excluded from the overdue payment collection scenario, and the process moves to other scenario judgment procedures. If the operation order does not conform to the overdue payment collection logic, such as payment collection before the creation of business documents, the system directly excludes the scenario from the overdue payment collection scenario and moves to other scenario judgment procedures.

[0087] When determining the nature of advance payment transactions, if the document source involves sales representatives (either through field visits or mobile sales), and the business operations involve combined order processing, the system will focus on payment collection and refund operations. This is because combined order processing for field visits or mobile sales is relatively complex, potentially involving both sales and returns, resulting in diverse fund flows. When payment is only associated with a sales order and refunds are only associated with a return order, this document source information, combined with the specific fund association method, becomes a crucial basis for determining the advance payment scenario. If the document source is a cloud commerce platform or B2B platform, although advance payments may still occur, the business rules differ from those for field visits or mobile sales. The system will further determine whether it meets the characteristics of an advance payment scenario based on the platform's specific rules and document association information. In advance payment scenarios, the order sequence follows a certain logic. Generally, order processing begins, generating sales and return orders, followed by payment collection or refund operations. If payment is performed first and associated with a sales order, the system will continue to monitor subsequent operations. If a subsequent refund is processed and only associated with a return order, and the outstanding amount is recorded as an arrears after receipt / return, conforming to the order of the advance payment business process, the system will classify it as an advance payment business scenario. If the order of operations is disordered, such as refunding before receiving payment, and the refund is associated with a sales order, the system will exclude this scenario from the advance payment scenario according to the rules and reassess whether it belongs to other business scenarios.

[0088] When determining the nature of outstanding payments, if the document source port involves operations such as vehicle sales combined invoicing, accounts receivable reconciliation settlement, outstanding payments collection, driver settlement, and creating a payment receipt (manually selecting documents), the system will focus on the financial status of these documents. In vehicle sales combined invoicing and driver settlement scenarios, the document source port indicates that the business is related to vehicle sales. The financial settlement of vehicle sales has its own characteristics, involving the financial transactions of various documents such as sales orders, return orders, and expense orders. The system will determine whether there are any outstanding business documents based on this document source port information, combined with data such as document amount, received and refunded amounts, etc. If so, the document source port information becomes an important clue for determining the outstanding payments collection scenario. In the outstanding payments collection scenario, the order of business operations is also crucial. In operations such as accounts receivable reconciliation settlement, outstanding payments collection, and creating a payment receipt (manually selecting documents), business documents are usually generated first, accumulating outstanding amounts, and then the payment collection operation is performed. If the system detects that there are outstanding amounts from sales orders, return orders, expense orders, etc., followed by a manual selection of documents for payment collection, and the order of operations conforms to the logic of debt collection, the system will further determine whether the scenario meets other characteristics of debt collection business scenarios, such as fund allocation rules. If the order of operations does not conform, such as payment being collected before business documents are generated, the system will re-determine the business scenario type.

[0089] Based on the above technical solution, in the scenario of receiving advance payments, the algorithm strictly follows the principle that payments are only associated with sales orders and refunds are only associated with return orders. After signing for / recovering the goods, the outstanding amount is treated as an arrears and then combined for settlement.

[0090] In the scenario of collecting outstanding payments, if sales > refunds + expenses, the algorithm prioritizes writing off the negative amount, and then allocates it in order of sales order generation time from earliest to latest; if sales < refunds + expenses, the algorithm prioritizes writing off the sales order amount, and then allocates it in order of negative document generation time from earliest to latest (when the generation time is the same, the document with the smaller amount is deducted first).

[0091] Through these algorithms, the system can accurately calculate the settlement amount, settled amount, outstanding amount, and write-off amount for each business document. During the calculation process, the system performs data operations and processing in real time to ensure the accuracy and reliability of the calculation results.

[0092] Based on the above technical solution, after the fund allocation calculation is completed, the calculation results are fed back to the business document system and the financial system by calling the preset system interface;

[0093] It automatically updates the amount data of relevant documents such as settlement statements, receipts, and advance payment receipts; and strictly follows the transaction processing principle during the update process.

[0094] When updating the settlement amount and settled amount of the settlement statement, the corresponding amounts of the relevant receipts and advance receipts are also updated simultaneously.

[0095] If any error occurs during the update process, the system will immediately initiate a rollback mechanism to undo the partially executed update operations, ensuring that the data is free of errors or inconsistencies.

[0096] The contents not described in detail in this specification are existing technologies known to those skilled in the art.

[0097] The above description is only a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiments. Any equivalent modifications or changes made by those skilled in the art based on the content disclosed in the present invention should be included in the scope of protection set forth in the claims.

Claims

1. A method for intelligent allocation of consolidated settlement funds, characterized in that, include: Key data is collected from various business documents, and the key data is initially sorted and verified to ensure the accuracy and integrity of the data before being stored in the system database. The business documents include sales orders, return orders, expense orders, and customer accounts receivable initialization orders; The key data includes order amount, total order discount, amount received, and amount refunded; After extracting and organizing the data from the database, the specific business scenario to which the business belongs is determined based on the preset recognition rules; The business scenarios include: prepayment collection business scenarios and overdue payment collection business scenarios. Based on the identified business scenario, the corresponding fund allocation priority algorithm is called from the algorithm library to calculate the settlement amount, settled amount, outstanding amount and write-off amount for each business document; The calculation results are fed back to the business document system and financial system through the system interface to update the amount data of the relevant documents; The relevant documents include settlement statements, receipts, and advance payment receipts.

2. The intelligent allocation method for consolidated settlement funds as described in claim 1, characterized in that, The preliminary sorting and verification of key data specifically includes: Perform data format standardization checks to ensure that order amounts and received amounts are formatted correctly, and avoid data processing anomalies caused by incorrect formats; Perform data logic validation. If logical errors are found, promptly prompt the operators to correct or supplement the data.

3. The intelligent allocation method for consolidated settlement funds as described in claim 1, characterized in that, When storing data in the system database, during the initialization of tables and table items, a "Document Type" field is added to the table to identify the type of each document using a fixed code or string; By adding a "timestamp" field to the table, the creation time and update time of each document can be identified; Combining document types with timestamps provides a more flexible way to store and retrieve data.

4. The intelligent allocation method for consolidated settlement funds as described in claim 1, characterized in that, If it is detected that the payment is only associated with the sales order, the refund is only associated with the return order, and the outstanding amount is recorded as an arrears after the goods are signed for / recovered, then it is determined to be a prepayment business scenario. The system checks whether the transactions involve vehicle sales combination order creation, accounts receivable reconciliation settlement, collection of outstanding payments, driver settlement, and creation of payment receipts with manual document selection. If these operations exist and there are outstanding business documents, then the system is identified as a collection of outstanding payments business scenario.

5. The intelligent allocation method for consolidated settlement funds as described in claim 1, characterized in that, When determining the business scenario, the system can accurately identify the business scenario by further obtaining the source port of the document and the sequence of business operations.

6. The intelligent allocation method for consolidated settlement funds as described in claim 5, characterized in that, The determination of the document source port specifically includes: For scenarios involving advance payment collection: After the system obtains the source port information of the business document, if it is from the APP and the document source is a salesperson or a mobile salesperson, the system will check whether there is a combined order. If so, it will further confirm that the payment is only associated with the sales order and the refund is only associated with the return order. If these conditions are met, the relevant information will be recorded and the process will proceed to the business operation sequence judgment. If these conditions are not met, the scenario will be directly excluded as an advance payment collection scenario and the process will proceed to other scenario judgment procedures. If the document source port is from the PC, cloud platform, B2B platform, or WMS, the system will check the association between the payment and refund and the sales order and return order according to the specific business rules of the corresponding platform or port. If the association characteristics of advance payment collection are met, the relevant information will be recorded and the process will proceed to other scenario judgment procedures. Otherwise, the scenario will be excluded as an advance payment collection scenario and the process will proceed to other scenario judgment procedures. For overdue payment collection scenarios, the system obtains the source port information of the business documents. If the operation involves vehicle sales combination order creation, accounts receivable reconciliation settlement, overdue payment collection, driver settlement, or creating a payment collection order - manually selecting documents, the system will check whether there are any outstanding business documents. If there are outstanding documents, the relevant information is recorded and entered into the business operation sequence judgment. If all documents have been settled, the scenario is excluded as an overdue payment collection scenario, and the process is transferred to other scenario judgment procedures.

7. The intelligent allocation method for consolidated settlement funds as described in claim 5, characterized in that, The specific steps for determining the order of business operations include: For scenarios involving advance payment collection: The system obtains the order of business operations based on timestamps. If an order is placed first, and the initial payment collection is associated with the sales order, the system will continuously monitor subsequent refund operations. If subsequent refund operations are only associated with return orders, and the outstanding amount is recorded as an arrears after receipt / recovery, the system determines that this is a scenario involving advance payment collection. If the payment is not associated with the sales order, or the refund is not associated with the return order, or the handling of the outstanding amount does not conform to the rules for advance payment collection, the scenario is excluded from the advance payment collection process, and the system proceeds to other scenario judgment procedures. If the operation order is disordered, such as refunding before payment collection, or the operation order does not conform to the logic of advance payment collection, the system directly excludes the scenario from the advance payment collection process and proceeds to other scenario judgment procedures. For overdue payment collection scenarios, the system uses timestamps to obtain the order of business operations and checks if sales orders, return orders, and expense orders were generated first. If this condition is met, and there is a manual selection of documents for payment collection, the system checks whether the payment collection operation conforms to the overdue payment collection business logic, such as whether it is processed according to the overdue payment collection fund allocation rules. If it does, the system determines that the business scenario is an overdue payment collection scenario. If it does not conform to the overdue payment collection business logic, such as abnormal association between the payment collection operation and the documents or non-compliance with the fund allocation rules, the scenario is excluded from the overdue payment collection business logic, and the process moves to other scenario judgment procedures. If the operation order does not conform to the overdue payment collection business logic, such as payment being collected before the business documents are generated, the system directly excludes the scenario from the overdue payment collection business logic and moves to other scenario judgment procedures.

8. The intelligent allocation method for consolidated settlement funds as described in claim 1, characterized in that, In the scenario of receiving advance payments, the algorithm strictly follows the principle that payments are only associated with sales orders and refunds are only associated with return orders. After signing for / recovering the goods, the outstanding amount is treated as an arrears and then combined for settlement. In the scenario of collecting outstanding payments, if sales exceed refunds plus expenses, the algorithm prioritizes writing off the negative amount and then distributes it in the order of sales order generation time from earliest to latest; if sales are less than refunds plus expenses, the algorithm prioritizes writing off the sales order amount and then distributes it in the order of negative document generation time from earliest to latest.

9. The intelligent allocation method for consolidated settlement funds as described in claim 8, characterized in that, When the generation times are the same, the document with the smaller amount will be deducted first.

10. The intelligent allocation method for consolidated settlement funds as described in claim 1, characterized in that, After completing the fund allocation calculation, the calculation results are fed back to the business document system and the financial system by calling the preset system interface; It automatically updates the amount data of settlement statements, receipts, and advance receipts; and strictly follows transaction processing principles during the update process. When updating the settlement amount and settled amount of the settlement statement, the corresponding amounts of the relevant receipts and advance receipts are also updated simultaneously. If any error occurs during the update process, the system will immediately initiate a rollback mechanism to undo the partially executed update operations, ensuring that the data is free of errors or inconsistencies.

Images