An account reconciliation intelligent processing method and system, a terminal device, and a storage medium

Abstract

The present application relates to the technical field of text classification, in particular to a kind of reconciliation intelligent processing method, system and terminal equipment and storage medium.The present application first identifies the unsettled order that platform is not settled to merchant from all orders, then filters the order object of this period from the unsettled order.Then the present application removes the order object of this period from all unsettled orders to obtain the unsettled historical order, then filters the historical backfill order object from the unsettled historical order, the historical backfill order object is the order missing due to unsettled in its belonging reconciliation period, finally the historical backfill order object and the order object of this period are attributed to the order reconciliation statement of current period, so that the historical backfill order object and the order object of this period are settled in time in current reconciliation.Due to the present application will automatically backfill the previous unsettled historical order in current reconciliation, so that the unsettled order can be settled in time in current reconciliation.

Description

Technical Field

[0001] This invention relates to the field of text classification technology, specifically to an intelligent reconciliation processing method, system, terminal device, and storage medium. Background Technology

[0002] The platform provides a transaction channel for merchants and users. Users place orders and pay for them on the platform. The platform then ships the ordered goods to the user through a third party. After the user receives the goods, the third party uploads the confirmation of receipt time to the platform. The platform receives the confirmation of receipt time. If this confirmation of receipt time is within the current reconciliation period, the platform will include the order in the current order reconciliation statement. For orders belonging to the current order reconciliation statement, the platform will transfer the corresponding order payment to the merchant within the current settlement period agreed upon with the merchant. However, if the third party fails to upload the confirmation of receipt time to the platform in a timely manner, confirmation of receipt times that originally belonged to the previous reconciliation period (that reconciliation period's time is earlier than the current reconciliation period's time) will not be included in the previous reconciliation period. Existing technology manually rewrites the delayed confirmation of receipt time to a receipt time that belongs to the current reconciliation period, so that the platform can include orders with delayed confirmation of receipt times in the current order reconciliation statement. Manually rewriting orders can easily lead to the omission of some orders during the current reconciliation, causing the platform to delay settling orders with merchants, or even miss settling the order altogether.

[0003] In summary, existing technologies are prone to missing some unsettled orders during the current reconciliation process.

[0004] Therefore, existing technologies still need to be improved and enhanced. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides an intelligent reconciliation processing method, system, terminal device, and storage medium, which solves the problem that existing technologies often omit some unsettled orders during the current reconciliation process.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: In a first aspect, the present invention provides an intelligent reconciliation processing method, comprising: Extract the confirmation receipt time from the unsettled orders, obtain the current reconciliation period, and based on the confirmation receipt time and the current reconciliation period, filter out the order objects for the current period from the unsettled orders; Identify unsettled historical orders, extract the confirmation receipt lag time on the unsettled historical orders, and based on the confirmation receipt lag time and the current reconciliation period, filter out historical replenishment order objects from the unsettled historical orders; Based on the current period order object and the historical replenishment order object, a current period order reconciliation statement to be processed is obtained.

[0007] In one implementation, unsettled orders are identified from all orders, including: Retrieve the data table for all orders, read the statement number from the order data table, and identify the value of the statement number; Based on the statement number, identify unsettled orders from all orders.

[0008] In one implementation, based on the confirmed receipt time and the current reconciliation period, the order objects for the current period are filtered from the unsettled orders, including: From the unsettled orders, select those whose confirmed receipt time falls within the current reconciliation period and are in a state where settlement is allowed, and use the selected orders as the order objects for this period.

[0009] In one implementation, based on the confirmed receipt lag time and the current reconciliation period, historical replenishment order objects are selected from the unsettled historical orders, including: From the unsettled historical orders, select those unsettled orders whose confirmation of receipt lag time is earlier than the current reconciliation period and are in the settlement allowed state, and use the selected unsettled orders as historical replenishment order objects.

[0010] In one implementation, the method for determining the unsettled historical orders includes: removing the current period order object from all the unsettled orders to obtain the unsettled historical orders.

[0011] One implementation also includes: Identify unsettled refund orders from all refund orders, indicating that no refund has been paid to the merchant. Obtain the refund time of the unsettled refund order from the feedback of the third party, and obtain the preset refund reconciliation deadline. Based on the refund time and the refund reconciliation deadline, filter out the refund recipients for this period from the unsettled refund orders. Remove the current refund recipients from all refund orders to obtain historical refund orders; obtain the refund lag time of the historical refund orders as reported by a third party, and based on the refund lag time and the refund reconciliation deadline, filter out the historical refund recipients from the historical refund orders who have not yet settled refunds with the merchants; Based on the current refund recipients and the historical refund recipients, a current refund statement that needs to be processed is obtained.

[0012] One implementation also includes: Determine the original order corresponding to the recipient of the refund for this period; Determine whether the original order belongs to the current period's order statement, and based on the determination of the attribution relationship, mark the refund path for the refund recipient in this period.

[0013] In one implementation, the refund path includes a current period refund path and a red-ink refund path.

[0014] In one implementation, the method for setting the refund reconciliation deadline includes: Obtain the refund period and determine the reserved deadline based on the refund period; Set the refund reconciliation deadline based on the reserved deadline and the current reconciliation period.

[0015] Secondly, embodiments of the present invention also provide an intelligent reconciliation processing system, the system comprising: The first filtering module is used to extract the confirmation receipt time on unsettled orders, obtain the current reconciliation period, and filter out the current period's order objects from the unsettled orders based on the confirmation receipt time and the current reconciliation period. The second filtering module identifies unsettled historical orders, extracts the confirmation receipt lag time from the unsettled historical orders, and filters out historical replenishment order objects from the unsettled historical orders based on the confirmation receipt lag time and the current reconciliation period. The order aggregation module is used to obtain the pending orders based on the current period's order objects and the historical replenishment order objects. Current period order statement.

[0016] Thirdly, embodiments of the present invention also provide a terminal device, wherein the terminal device includes a memory, a processor, and an intelligent reconciliation processing program stored in the memory and executable on the processor, wherein when the processor executes the intelligent reconciliation processing program, it implements the steps of the intelligent reconciliation processing method described above.

[0017] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing an intelligent reconciliation processing program, wherein when the intelligent reconciliation processing program is executed by a processor, it implements the steps of the intelligent reconciliation processing method described above.

[0018] Beneficial Effects: This invention first identifies unsettled orders from all orders that the platform has not yet settled with the merchants. Based on the confirmation receipt time of these unsettled orders and the current reconciliation period, it filters out current period orders from the unsettled orders. Then, it removes current period orders from all unsettled orders to obtain unsettled historical orders. Next, by comparing the confirmation receipt delay time of these unsettled historical orders with the current reconciliation period, it filters out historical supplementary orders from the unsettled historical orders. These historical supplementary orders are orders that were missed due to non-settlement within their respective reconciliation periods. Finally, these historical supplementary orders and current period orders are included together in the current period's order reconciliation statement, ensuring timely settlement of both during the current period's reconciliation. Because this invention automatically supplements previous unsettled historical orders during the current period's reconciliation, it enables timely settlement of unsettled orders within the current period's reconciliation. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating the order reconciliation process in an embodiment of the present invention. Figure 2 This is a flowchart illustrating the reconciliation process for a refund order in an embodiment of the present invention. Figure 3 This is a structural diagram of the intelligent reconciliation processing system provided by the present invention; Figure 4 This is a block diagram illustrating the internal structure of a terminal device provided in an embodiment of the present invention. Detailed Implementation

[0020] The technical solutions of the present invention will be clearly and completely described below with reference to the embodiments and accompanying drawings. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0021] Research revealed that the platform provides a transaction channel for merchants and users. Users place orders and pay on the platform, which then uses a third party to ship the ordered goods to the user. After the user receives the goods, the third party uploads the confirmation of receipt time to the platform. The platform receives the confirmation of receipt time, and if it falls within the current reconciliation period, the platform will include the order in the current order reconciliation statement. For orders belonging to the current order reconciliation statement, the platform will transfer the corresponding order payment to the merchant within the agreed settlement period. However, if the third party fails to upload the confirmation of receipt time to the platform in a timely manner, confirmation of receipt times that originally fell within the previous reconciliation period (which is earlier than the current reconciliation period) will not be included in the previous reconciliation period. Existing technology manually rewrites the delayed confirmation of receipt time to fall within the current reconciliation period, enabling the platform to include orders with delayed confirmation of receipt times in the current order reconciliation statement. Manually rewriting orders can easily lead to the omission of some orders during the current reconciliation, causing the platform to delay settling orders with merchants, or even miss settling the order altogether.

[0022] To address the aforementioned technical problems, this invention provides an intelligent reconciliation processing method, system, terminal device, and storage medium, resolving the issue of existing technologies easily missing some unsettled orders in the current reconciliation. In specific implementation, the computer records all orders placed by the user on the platform. The computer not only filters out unsettled orders for the current period from all orders but also filters out historical back-off orders that should be settled in the current reconciliation from the unsettled historical orders, ensuring that historical back-off orders are settled promptly in the current reconciliation.

[0023] For example, the current reconciliation period is September 2025 (start time: 2025-09-01 00:00:00, end time: 2025-09-30 23:59:59), and the current order reconciliation statement is generated on October 5, 2025 (i.e., the time when the current reconciliation is completed).

[0024] The previous reconciliation period was August 2025 (start time: 2025-08-01 00:00:00, end time: 2025-08-31 23:59:59), and the previous order reconciliation statement was generated on September 5, 2025.

[0025] Unsettled orders (i.e., orders for which the platform has not yet transferred the payment from the user to the merchant) include Order 1 and Order 2. The confirmation date for Order 1 is September 3, 2025, and the third-party courier uploaded this confirmation date to the platform before October 5, 2025. The confirmation date for Order 2 is August 30, 2025, but the third-party courier uploaded this confirmation date to the platform after September 5, 2025, making August 30, 2025 a delayed confirmation date. Therefore, Order 2 was not included in the previous order statement.

[0026] Both Order 1 and Order 2 meet the settlement requirements. Since September 3, 2025, falls between the start and end dates of the current reconciliation period, Order 1 is classified as a current period order. August 30, 2025, falls at the start of the current reconciliation period, therefore Order 2 is classified as a historical replenishment order. Both current period orders and historical replenishment orders are grouped into the current period's order reconciliation statement. For any order classified as a current period order, the system will prompt the platform to pay the merchant the amount paid by the user to the platform during the current period's reconciliation. The distinction between current period orders and historical replenishment orders is to prioritize unsettled orders. Historical replenishment orders have a higher priority than current period orders; that is, the platform will prioritize processing historical replenishment orders during the current period's reconciliation process with the merchant.

[0027] Example 1: This example provides an intelligent reconciliation processing method for orders. This intelligent reconciliation processing method for orders can be applied to terminal devices, which can be terminal products with text processing capabilities (in this example, the order format is text), such as computers. In this example, as... Figure 1 As shown, the intelligent reconciliation processing method specifically includes the following steps: S11, extract the confirmation receipt time from the unsettled orders, obtain the current reconciliation period, and based on the confirmation receipt time and the current reconciliation period, filter out the order objects for the current period from the unsettled orders; S12, remove the current period order object from all the unsettled orders to obtain unsettled historical orders, extract the confirmation receipt lag time on the unsettled historical orders, and based on the confirmation receipt lag time and the current reconciliation period, filter out the historical replenishment order object from the unsettled historical orders; S13. Based on the current order object and the historical replenishment order object, obtain the current order statement to be processed.

[0028] The unsettled orders in step S11 are orders for which the transaction platform has not paid the merchant. In this embodiment, the unsettled orders are identified from all orders, including: obtaining a data table of all orders, obtaining the statement number on the data table, and identifying the value of the statement number; and identifying the unsettled orders from all orders based on the value of the statement number.

[0029] Create a data table for orders on the computer. This table sets up a field (represented by `bill_no`) for each order to store the invoice number. When the value of the `bill_no` field is empty, it indicates that the order is unsettled. Empty values ​​include database NULL, an empty string, or no valid number written (i.e., an invalid number was written). Database NULL means that the `bill_no` field has no data records, and the database internally marks it as NULL. An empty string is simply "", meaning the `bill_no` field stores a blank string of length 0; the cell contains data, but no valid characters. A fixed-length number is considered a valid number. If the `bill_no` field contains a number, but the length of that number is not equal to the set fixed length, then that number is considered invalid.

[0030] When bill_no is null, a settlement flag field settling_flag=unsettled is generated for the order in the data table. When it is necessary to identify unsettled orders in the future, it is only necessary to filter whether the order data table has "unsettled". Identifying "unsettled" is faster than identifying whether bill_no is null.

[0031] S11, based on the confirmed receipt time and the current reconciliation period, filters out the current period's order objects from the unsettled orders, including: filtering out orders whose confirmed receipt time falls within the current reconciliation period and are in a settlement-allowed state from the unsettled orders, and using the filtered orders as the current period's order objects.

[0032] In other words, the order in this period must meet the following conditions: Condition 1, the order is not associated with a statement number (i.e., the statement number field bill_no is empty and the settlement flag field settle_flag is unsettled); Condition 2, the order confirmation of receipt time falls within the current reconciliation period, which is [the start time of reconciliation and the end time of reconciliation]; Condition 3, the order status meets the settlement conditions, where the settlement conditions are either successful order transaction or closed order transaction.

[0033] The first condition is to filter out orders that have already been settled, preventing duplicate accounting and reducing the computational burden caused by redundant orders. The second condition is to identify orders generated within the current reconciliation period and pinpoint their creation time.

[0034] For orders that include after-sales service, in addition to meeting conditions one and two above, a third condition must also be met. The fact that a third party has uploaded a confirmation of receipt time does not necessarily mean the transaction between the merchant and the user is successful. Some orders include after-sales service; uploading the confirmation of receipt time only indicates that the user has received the goods, not that the merchant has provided after-sales service. Therefore, the platform will not settle the order payment with the merchant before the transaction is confirmed as successful, in order to urge the merchant to complete all transactions related to the order.

[0035] Once the merchant has provided after-sales service and the user has settled the remaining payment with the platform, it means that the merchant and the user have completed all the transactions included in the order. Therefore, the platform closes the order, i.e., the order transaction is closed.

[0036] For any order, if the order data is modified, including but not limited to the confirmation of receipt time, order status, and statement of account number fields, it is necessary to verify whether the order meets the above three conditions to confirm whether the order belongs to the current period's order objects.

[0037] For example, the current reconciliation period is September 2025 (start time: 2025-09-01 00:00:00, end time: 2025-09-30 23:59:59).

[0038] Order O-202509-001: The third party supplemented the confirmation of receipt time on September 28, 2025. The confirmation of receipt update time is 15:20:00 on 2025-09-28. The order status is successful transaction. bill_no is empty (meaning that the platform has not settled the order amount for order O-202509-001 with the merchant).

[0039] The confirmed receipt date of September 28, 2025 is within the current reconciliation period. The bill_no value is null. The order status meets the settlement conditions (i.e., the transaction is successful). Therefore, order O-202509-001 belongs to the order objects of this period.

[0040] In step S12, the current period order object is removed from all the unsettled orders to obtain the unsettled historical orders. The specific steps include: marking the order corresponding to the settlement flag field sett_flag=unsettled on the data table as an unsettled order; removing the orders marked as current period order objects from the unsettled orders; and the remaining ones are the unsettled historical orders.

[0041] Step S12, based on the confirmed receipt lag time and the current reconciliation period, filters historical replenishment order objects from the unsettled historical orders, including: filtering unsettled orders whose confirmed receipt lag time is earlier than the current reconciliation period and are in the settlement allowed state, and using the filtered unsettled orders as historical replenishment order objects.

[0042] Unsettled historical orders are due to third parties delaying the uploading of user confirmation of receipt times to the platform. This prevents the platform from settling order payments to merchants within the reconciliation period corresponding to the actual confirmation of receipt time. For example, if a user confirmed receipt in August, but the third party did not upload the confirmation time in August (this confirmation time is marked as a delayed confirmation time), but only uploaded it in September, the platform and merchant did not settle the order payment in the August reconciliation, making the order an unsettled historical order. This embodiment, after identifying unsettled historical orders, will settle the order payment to the merchant in the September reconciliation as long as the order meets the conditions.

[0043] Historical order recovery objects must meet the following conditions: Condition 1, the order is not associated with a statement number (i.e., the statement number field bill_no of the order is empty and the settlement flag field settle_flag = unsettled); Condition 2, the order's confirmation of receipt lag time is earlier than the current reconciliation period, i.e., the confirmation of receipt time is earlier than the start time of the reconciliation for the current reconciliation period; Condition 3, the order status meets the settlement conditions, where the settlement conditions are either order transaction successful or order transaction closed.

[0044] In this embodiment, the order of determining the above three conditions is as follows: first, orders that meet condition one are filtered from historical orders; then, orders that meet condition two are filtered from the orders filtered based on condition one; and finally, orders that meet condition three are filtered from the orders filtered based on condition two, so as to obtain historical replenishment order objects.

[0045] The order of the three conditions in this embodiment has the following technical effects: bill_no is a high-frequency index field. The first step quickly prunes the entire order pool, directly filtering out a large number of settled and reconciled orders. The number of orders that need to be looped / compared in subsequent conditions two and three is greatly reduced, the reconciliation scheduled task takes the shortest time, and there will be no slow SQL queries or system timeouts during peak periods of the billing period.

[0046] The first step is to directly exclude orders that have already been billed and paid, thus preventing duplicate settlement calculations from the source. Even if there are abnormalities in the time or status logic later, duplicate payment documents will not be detected, making the risk control more tolerant.

[0047] By incorporating historical order backlogs into the order processing set of the current reconciliation statement, the platform achieves automatic identification and inclusion of previously unsettled orders without altering the main process of "checking historical orders when generating a statement." Specifically, it identifies unsettled orders by checking the statement number field of historical orders and includes them in the current reconciliation, enabling the platform to settle order payments to merchants promptly.

[0048] For example, the current reconciliation period is September 2025 (start time: 2025-09-01 00:00:00, end time: 2025-09-30 23:59:59).

[0049] Order O-202508-017: The user completed the purchase in August, but due to network delays, the confirmation of receipt was not updated until September 2, 2025. The confirmation of receipt update time was 09:00:00 on September 2, 2025 (earlier than the start time of the current reconciliation period: 00:00:00 on September 1, 2025). The transaction status was successful. When the September bill was generated, bill_no was still empty (meaning that the platform had not settled the order amount for order O-202508-017 with the merchant). Therefore, order O-202508-017 meets the three above-mentioned criteria for historical order supplementation objects. So, order O-202508-017 is classified as a historical order supplementation object for the September 2025 bill, and the order amount will be settled with the merchant in the September reconciliation.

[0050] Example 2: This example provides an intelligent reconciliation processing method for refund orders. In this example, as follows... Figure 2 As shown, the intelligent reconciliation processing method for refund orders specifically includes the following steps: S21, Identify unsettled refund orders from all refund orders that have not been settled with the merchant.

[0051] S22, obtain the refund time of the unsettled refund order from the feedback of the third party, and obtain the preset refund reconciliation deadline, and based on the refund time and the refund reconciliation deadline, filter out the refund recipients for this period from the unsettled refund orders.

[0052] S23, remove the current refund recipient from all refund orders to obtain historical refund orders; obtain the refund lag time of the historical refund orders as reported by a third party, and based on the refund lag time and the refund reconciliation deadline, filter out the historical refund recipients who have not settled refunds with the merchant from the historical refund orders.

[0053] S24. Based on the refund recipients for the current period and the historical refund recipients, obtain the current period refund statement that needs to be processed.

[0054] The specific process for identifying unsettled refund orders in step S21 is as follows: The refund data table maintains a field called refund_bill_no for each refund order. When the value of refund_bill_no is empty, it means that the platform has not settled the refund order with the merchant, that is, the platform has not deducted the refund requested by the user from the merchant.

[0055] Null values ​​include database NULL, empty strings, or no valid number written (i.e., an invalid number was written). Database NULL means that the bill_no field has no data records, and the database underlying system marks it as NULL; an empty string is "", meaning that the bill_no field stores a blank string of length 0. The cell contains data, but no valid characters; a fixed-length number is set as a valid number. Although the bill_no field also has a number, if the length of the number is not equal to the set fixed length, then the number is considered invalid.

[0056] The refund data table and the order data table in Example 1 are two independent tables stored in different locations. To check if an order has been settled, only the order data table needs to be searched, without needing to search the refund data table, thus improving the speed of finding unsettled orders. Similarly, to find unsettled refund orders, only the refund data table needs to be searched, without needing to search the order data table, further improving the speed of finding unsettled refund orders.

[0057] The refund time for the unsettled refund order reported by the third party in S22 can be either the time when the user applies for a refund through the third party to the platform, or the time when the platform entrusts the third party to refund the user after receiving the user's refund request. Whether it is the time of applying for a refund or the time of actually paying the refund, it belongs to the refund time reported by the third party.

[0058] The refund reconciliation deadline in step S22 is not set arbitrarily. Instead, it is first calculated based on the historical refund cycle of each order and the average duration of the refund process is calculated statistically. This average duration is used as the refund cycle. Then, based on the current reconciliation period, a refund reconciliation deadline that is later than the current reconciliation period is set.

[0059] In other words, a reserved deadline is set based on the refund cycle. The refund reconciliation deadline is obtained by delaying the reserved deadline from the current reconciliation period, so that the refund reconciliation deadline is later than the current reconciliation period.

[0060] When the refund period for an order is longer than the preset time threshold, the deadline is set to 10 days. When the refund period for an order is shorter than the preset time threshold, the deadline is set to 4 days.

[0061] For example, if the current reconciliation period is September 2025 (start time: 2025-09-01 00:00:00, end time: 2025-09-30 23:59:59), and the refund cycle is 2 days, which is less than the preset 3 days (i.e., the preset duration threshold), then the reserved deadline can be set to 4 days. That is, the refund reconciliation deadline can be October 4, 2025, at 23:59:59, so that the refund reconciliation deadline is later than the current reconciliation period.

[0062] When the refund period is 5 days, which is longer than the preset 3 days (i.e. the preset duration threshold), the reserved deadline can be set to 10 days. That is, the refund reconciliation deadline can be 23:59:59 on October 10, 2025, so that the refund reconciliation deadline is later than the current reconciliation period.

[0063] The reason for setting the refund reconciliation deadline later than the current reconciliation period is due to the inherent lag in after-sales refunds. This lag is caused by the long refund cycle, which consists of the user applying for a refund, the merchant's review, the platform's verification, and the refund being issued to the user. If the refund reconciliation deadline coincides with or is earlier than the current reconciliation period's end, the refund cannot be settled in the current reconciliation and will only be available in the next reconciliation period. This embodiment, by setting the refund reconciliation deadline later than the current reconciliation period, mitigates the drawbacks caused by the lag in refunds.

[0064] The process of selecting the refund recipients from the unsettled refund orders in step S22 is as follows: Identify whether the refund status is successful; identify whether the successful refund time falls within the allowed time range for aggregation; identify whether the refund settlement status is unassociated with the statement number (refund_bill_no is empty).

[0065] The specific implementation method of the above identification process is the same as the implementation method of filtering out the current period's order objects from the unsettled orders in step 11, and will not be described in detail here.

[0066] In step S23, historical refund objects that have not been settled with the merchant are filtered out from the historical refund orders. That is, it is determined whether the refund order belongs to the historical refund object. The determination conditions include: the refund status is successful; the successful refund time is earlier than or equal to the current period's refund reconciliation deadline; the refund object is not associated with any reconciliation statement number; the original order object status can be identified as settled or can enter the current processing path.

[0067] In step S24, based on the refund objects of the current period and the refund objects of the past period, a refund statement for the current period that needs to be processed is obtained. That is, both the refund objects of the current period and the refund objects of the past period are treated as refund statements for the current period that need to be processed. In the current reconciliation, the refund orders contained in the refund objects of the current period and the refund objects of the past period will be processed with the merchant.

[0068] In this embodiment, a refund path is also defined for the refund recipients in the current period, including: determining the original order corresponding to the refund recipients in the current period; determining whether the original order belongs to the current period's order statement, and marking the refund path for the refund recipients in the current period based on the determination result of the attribution relationship.

[0069] The refund for this period refers to the original order for which the user applied for a refund. If the original order belongs to the current period's order statement, the current period's order statement includes the current period's order objects and historical replenishment order objects. Regardless of whether it is the current period's order object or the historical replenishment order object, the orders contained in these two order objects are all unsettled orders waiting to be settled in the current period's statement. Therefore, the refund path for this current period's refund object is marked as the current period's refund path, which means that the refund is directly deducted from the order amount that needs to be settled with the merchant.

[0070] If the original order is not included in the current period's order statement, since the current period's order statement includes unsettled orders, the original order not being included in the current period's order statement means that the original order is a settled order. Therefore, the refund cannot be deducted in the current period's statement. So, the refund path of this refund object in the current period is marked as a "red-reversal refund path". A red-reversal refund path means that the refund will be marked as a red-reversal refund path in a later refund statement so that the refund can be deducted in subsequent statements.

[0071] For example, the current reconciliation period is September 2025 (start time: 2025-09-01 00:00:00, end time: 2025-09-30 23:59:59), and the deadline for refund reconciliation is October 4, 2025 at 23:59:59.

[0072] Refund order R-202509-031 was successfully refunded on September 25, 2025, and refund_bill_no is empty (indicating that the refund has not been settled). Therefore, this refund order is identified as a refund target for this period. The order O-202507-022 (the original order) corresponding to refund order R-202509-031 has already been written into the August statement with bill_no=LS202508-xx, which means it has been settled. In other words, the original order does not belong to the unsettled current period's order statement. Therefore, the refund path of the refund order can only be marked as a reverse refund path, that is, the refund order will be reflected as a reverse detail in the September order statement, rather than being a duplicate positive entry.

[0073] For example, refund order R-202510-008 was successfully refunded on October 3, 2025. The refund_bill_no is empty, and the successful refund time is no greater than T_cutoff (i.e., the refund reconciliation deadline). The original order O-202509-003 corresponding to refund order R-202510-008 belongs to the current order reconciliation statement for September (i.e., the original order is an unsettled order, meaning that the original order has not yet completed a valid settlement association in this batch or before). Therefore, the refund path of the refund order can be marked as the current refund path.

[0074] This embodiment associates refund orders with orders, allowing one order to be associated with N refund orders (1:N). For example, an order for whole-house renovation, including flooring, appliances, and furniture, might generate a refund order if the user is dissatisfied with the appliances after placing the order and requests a refund. If the user then discovers quality issues with the furniture and requests a refund, another refund order is generated. Both refund orders are associated with the user's whole-house renovation order. If the whole-house renovation order is not yet settled, the refund paths for both refund orders are marked as current refund paths, and the refunds are directly deducted from the original order's statement.

[0075] The deduction process in this embodiment is as follows: A unique identifier for the target order is written into the refund order to establish a one-to-many association between the target order and multiple refund orders; the settlement status of the target order is queried. If the target order is unsettled, the refund path of the current refund order is marked as the current period refund path; if the target order is settled, the current refund order is marked as the cross-period refund path; during the financial settlement stage, all refund orders marked with the current period refund path and successfully refunded are queried in batches based on the unique identifier of the target order. The total amount of all current period refunds is summarized, and the total amount of current period refunds is deducted from the original statement of account corresponding to the target order in one go, generating the actual settlement amount and completing the single deduction settlement; after settlement, the target order is updated to a settled status, and subsequent new refund orders are locked to only go through the cross-period reversal process; a timed compensation verification task is configured to match the total amount of refund orders with the amount deducted from the statement of account daily based on the order identifier, automatically correcting data differences; database transactions are enabled when performing refund creation and statement amount update operations to ensure the consistency of associated data; the amounts of all refund orders under the same target order are cumulatively verified to limit the total refund amount from not exceeding the original actual payment amount of the target order.

[0076] This embodiment associates multiple refund orders with an order, reducing the number of deductions and streamlining financial processes. One order can be bound to N refund orders, supporting multiple refunds for a single order, categorized by product type, demonstrating strong business adaptability. Multiple refunds for the same order are deducted in a unified manner, with only one settlement deduction executed, significantly reducing the number of deductions. There's no need to generate separate invoices or undergo separate financial audits for each refund, simplifying the entire reconciliation and settlement process. It allows for one-click access to all refund details for the order, providing clear traceability for reconciliation and after-sales issues.

[0077] Example 3: Based on Examples 1 and 2, in the current reconciliation, after the current period's order objects and historical replenishment order objects are settled, a reconciliation statement number is written to the current period's order objects and historical replenishment order objects. Writing the reconciliation statement number means that after reconciliation, the orders contained in these two reconciliation statement objects are settled.

[0078] Write the statement number and path type identifier to the current period refund path and the red-ink refund path object.

[0079] In scenarios involving multiple refunds for a single order, each refund order is written with a separate statement number instead of using a single order-level identifier to replace the refund order-level identifier, thus clarifying in which reconciliation period each refund order should be settled.

[0080] This embodiment uses an object-level write-back (i.e., writing the statement number) mechanism to ensure that the platform not only retains the final aggregation result, but also retains the reason and processing type of the object entering the processing path, which facilitates subsequent querying and tracing.

[0081] Example 4, based on Examples 1 and 2, summarizes the current period's order objects, historical replenishment order objects, current period's refund objects, and historical refund objects. This summary is displayed on the platform, operations, and merchant's reconciliation query, refund query, details page, and export page. The displayed content includes the reconciliation statement number, whether the order and refund order are in a certain stage, the object's source status, the refund path type (i.e., the current period's refund path and the red-ink refund path), and the association between the original order number and the refund order number.

[0082] For example, if O-202509-001 is the order object for this period, the confirmation of receipt update time is within the billing period and bill_no is empty, after reconciliation, write bill_no back (that is, change from empty value to non-empty value, indicating that the order has been settled after reconciliation).

[0083] O-202508-017 is a historical order that was updated after the confirmation of receipt. The confirmation of receipt was earlier than T_start (i.e., the start time of the billing period) and bill_no was empty. After reconciliation, bill_no was written back.

[0084] R-202510-008 and R-202509-031 are the recipients of this period's refund. After being split into the current period's refund path and the red-ink refund path, respectively, after reconciliation, refund_bill_no (that is, the value of refund_bill_no changes from null to non-null, indicating that the payment order has been processed after reconciliation) and path type are written back.

[0085] R-202507-004 represents a historical refund recipient. After reconciliation, write back the refund_bill_no.

[0086] If the same order O-202509-010 has two successful refund records, Ra (e.g., the recipient of the refund in this period) and Rb (e.g., the recipient of the refund in the past period), each record will be written back to refund_bill_no, reflecting a 1:N granular relationship.

[0087] In summary, this invention establishes a multi-dimensional state model for order objects and refund objects, and uses fields such as bill_no and refund_bill_no to automatically identify settlement status. This allows the system to move from single-field judgment to status-related judgment, improving the intelligence of reconciliation object identification. By classifying objects into four categories—current period order objects, historical replenishment order objects, current period refund objects, and historical refund objects—and using the diversion method shown in the embodiments, the platform can more stably differentiate between naturally settled items within the billing period, historical inflows, current period refunds and reversals, and historical pending refunds, improving processing accuracy and interpretability.

[0088] This invention reduces reliance on manual verification of missed historical settlement orders and refunds through an intelligent replenishment and rescanning mechanism for historical objects.

[0089] This invention enhances the traceability and result interpretation capabilities in scenarios with multiple refunds for a single order by using object-level path routing and numbered write-back mechanisms.

[0090] This invention improves the consistency of results and processing efficiency in multiple generation scenarios by controlling repeated aggregation and regeneration.

[0091] This invention reduces the discrepancy in results when different users view the same bill through a consistent multi-device display mechanism.

[0092] Example 5: This example also provides an intelligent reconciliation processing system, such as... Figure 3 As shown, the system includes: The first filtering module 01 is used to extract the confirmation of receipt time on unsettled orders, obtain the current reconciliation period, and filter out the order objects of the current period from the unsettled orders based on the confirmation of receipt time and the current reconciliation period; The second filtering module 02 determines unsettled historical orders, extracts the confirmation receipt lag time on the unsettled historical orders, and filters out historical replenishment order objects from the unsettled historical orders based on the confirmation receipt lag time and the current reconciliation period; Order aggregation module 03 is used to obtain pending orders based on the current period's order objects and the historical replenishment order objects. The current order statement.

[0093] Based on the above embodiments, the present invention also provides a terminal device, the principle block diagram of which can be as follows: Figure 4 As shown, the terminal device includes a processor, memory, network interface, and display screen connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements an intelligent reconciliation processing method. The display screen can be an LCD screen or an e-ink screen.

[0094] Those skilled in the art will understand that Figure 4 The schematic diagram shown is only a partial structural diagram related to the present invention and does not constitute a limitation on the terminal device to which the present invention is applied. The specific terminal device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0095] In one embodiment, a terminal device is provided, comprising a memory, a processor, and an intelligent reconciliation processing program stored in the memory and executable on the processor. When the processor executes the intelligent reconciliation processing program, it implements the following operation instructions: Extract the confirmation receipt time from the unsettled orders, obtain the current reconciliation period, and based on the confirmation receipt time and the current reconciliation period, filter out the order objects for the current period from the unsettled orders; Identify unsettled historical orders, extract the confirmation receipt lag time on the unsettled historical orders, and based on the confirmation receipt lag time and the current reconciliation period, filter out historical replenishment order objects from the unsettled historical orders; Based on the current period order object and the historical replenishment order object, a current period order reconciliation statement to be processed is obtained.

[0096] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0097] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for intelligent reconciliation processing, characterized in that, include: Extract the confirmation receipt time from the unsettled orders, obtain the current reconciliation period, and based on the confirmation receipt time and the current reconciliation period, filter out the order objects for the current period from the unsettled orders; Identify unsettled historical orders, extract the confirmation receipt lag time on the unsettled historical orders, and based on the confirmation receipt lag time and the current reconciliation period, filter out historical replenishment order objects from the unsettled historical orders; Based on the current period order object and the historical replenishment order object, a current period order reconciliation statement to be processed is obtained.

2. The intelligent reconciliation processing method as described in claim 1, characterized in that, The methods for determining the unsettled orders include: Retrieve the data table for all orders, obtain the statement number from the data table, and identify the value of the statement number; Based on the value of the statement number, unsettled orders are identified from all orders.

3. The intelligent reconciliation processing method as described in claim 1, characterized in that, Based on the confirmed receipt time and the current reconciliation period, the orders for the current period are filtered from the unsettled orders, including: From the unsettled orders, select those whose confirmed receipt time falls within the current reconciliation period and are in a state where settlement is allowed, and use the selected orders as the order objects for this period.

4. The intelligent reconciliation processing method as described in claim 1, characterized in that, Based on the confirmed receipt lag time and the current reconciliation period, historical replenishment orders are selected from the unsettled historical orders, including: From the unsettled historical orders, select those unsettled orders whose confirmation of receipt lag time is earlier than the current reconciliation period and are in the settlement allowed state, and use the selected unsettled orders as historical replenishment order objects.

5. The intelligent reconciliation processing method as described in claim 1, characterized in that, The method for determining the unsettled historical orders includes: removing the current period's order object from all the unsettled orders to obtain the unsettled historical orders.

6. The intelligent reconciliation processing method as described in any one of claims 1-5, characterized in that, Also includes: Identify unsettled refund orders from all refund orders, indicating that no refund has been paid to the merchant. Obtain the refund time of the unsettled refund order from the feedback of the third party, and obtain the preset refund reconciliation deadline. Based on the refund time and the refund reconciliation deadline, filter out the refund recipients for this period from the unsettled refund orders. Remove the current refund recipients from all refund orders to obtain historical refund orders. Obtain the refund lag time of the historical refund orders as reported by a third party. Based on the refund lag time and the refund reconciliation deadline, filter out the historical refund recipients from the historical refund orders who have not yet settled refunds with the merchants. Based on the current refund recipients and the historical refund recipients, a current refund statement that needs to be processed is obtained.

7. The intelligent reconciliation processing method as described in claim 6, characterized in that, Also includes: Determine the original order corresponding to the recipient of the refund for this period; Determine whether the original order belongs to the current period's order statement, and based on the determination of the attribution relationship, mark the refund path for the refund recipient in this period.

8. The intelligent reconciliation processing method as described in claim 7, characterized in that, The refund path includes the current period refund path and the red-ink refund path.

9. The intelligent reconciliation processing method as described in claim 6, characterized in that, The method for setting the refund reconciliation deadline includes: Obtain the refund period and determine the reserved deadline based on the refund period; Set the refund reconciliation deadline based on the reserved deadline and the current reconciliation period.

10. An intelligent reconciliation processing system, characterized in that, The system includes: The first filtering module is used to extract the confirmation receipt time on unsettled orders, obtain the current reconciliation period, and filter out the current period's order objects from the unsettled orders based on the confirmation receipt time and the current reconciliation period. The second filtering module identifies unsettled historical orders, extracts the confirmation receipt lag time from the unsettled historical orders, and filters out historical replenishment order objects from the unsettled historical orders based on the confirmation receipt lag time and the current reconciliation period. The order aggregation module is used to obtain the pending orders based on the current period's order objects and the historical replenishment order objects. Current period order statement.

11. A terminal device, characterized in that, The terminal device includes a memory, a processor, and an intelligent reconciliation processing program stored in the memory and executable on the processor. When the processor executes the intelligent reconciliation processing program, it implements the steps of the intelligent reconciliation processing method as described in any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an intelligent reconciliation processing program, which, when executed by a processor, implements the steps of the intelligent reconciliation processing method as described in any one of claims 1-9.

Images