Fund processing method under combined billing scene

Abstract

The invention relates to a fund processing method in a combined billing scene, which comprises the following steps: creating a process control engine, and setting a process control sub-module based on a state machine; presetting each state in the combined billing fund processing flow; setting corresponding triggering conditions and conversion rules; and when a combined billing request is generated, if the trigger conditions of each state are met, automatically switching to the corresponding state, and continuing to execute subsequent operation until the combined billing and fund processing flow are completely completed. According to the invention, by means of the process control engine and the state machine-based sub-module, the process is comprehensively managed and optimized, participated receipts can be intelligently determined, and the business processing efficiency and the data accuracy are improved; during fund processing, relevant algorithms ensure that collection is feasible and accurate, risks are reduced, and the flexibility and reliability of the system are enhanced in cooperation with a cashier desk, refund processing, data updating, log recording and other mechanisms; and the exception handling module ensures the smooth flow and provides powerful support for enterprise finance and business development.

Description

Technical Field

[0001] This invention relates to the field of financial business process technology, specifically a method for processing funds in a combined order placement scenario. Background Technology

[0002] In existing ERP systems, the following application scenarios exist to improve data processing efficiency:

[0003] In the sales order module, the "create order" operation is a series of actions to create a new sales order. When creating a new sales order, you need to determine the document type, such as vehicle sales, visit sales, warehouse direct sales - self-pickup, warehouse direct sales - delivery, etc., and enter information such as customer, salesperson, and warehouse. The system will calculate data such as order amount, overall order discount, and accounts receivable based on the entered information.

[0004] In the return order module, the "create order" operation involves a series of actions to create a new return order. When creating a new return order, you need to determine the return type (return by item, return by order, vehicle sales, visit sales, etc.), select information such as customer, salesperson, and return warehouse, and the system will calculate data such as order amount, refundable discount, and refundable amount.

[0005] It may also include the "invoicing" operation of business documents such as exchange orders and return orders.

[0006] To improve efficiency, a combined order processing application scenario was designed. The "combined order processing" operation integrates multiple business documents (sales orders, return orders, return orders, etc.) into the same operation process for processing. This breaks the limitations of traditional single-document order processing and enables collaborative processing of multiple business documents through a single operation, meeting the needs of complex business scenarios and improving business processing efficiency and data accuracy.

[0007] From a business perspective, combined order processing can handle order requirements for multiple transactions, including sales, returns, and goods returns, in one go, avoiding the cumbersome process of creating separate orders and improving the convenience and efficiency of business operations. In business scenarios involving both sales and returns, combined order processing can handle these transactions centrally, reducing operational steps and time costs.

[0008] From a data processing perspective, combined billing ensures data consistency and accuracy. By uniformly calculating data such as overall order discounts and amounts receivable / refundable, it avoids data inconsistencies that may arise from separate billing, providing a reliable data foundation for subsequent financial accounting and business analysis.

[0009] Existing combined invoicing scenarios suffer from complex and error-prone fund processing flows, unintelligent document matching, and a lack of effective process control and anomaly interception mechanisms. Specifically, when combining multiple business documents for invoicing, fund calculation rules are cumbersome, such as the calculation and restrictions of overall order discounts and complex deduction logic for different document amounts; document matching relies on manual selection, which is inefficient and prone to errors; process control lacks unified management, resulting in poor operational continuity between stages; and anomaly handling is not timely, such as the inability to effectively intercept overdue payments, affecting system stability and fund security, leading to a poor user experience and hindering normal business operations.

[0010] 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

[0011] To address the shortcomings of existing technologies, the present invention aims to provide a fund processing method for combined order processing scenarios. By leveraging a process control engine and state machine-based sub-modules, the method comprehensively manages and optimizes the process, intelligently identifying participating documents and improving business processing efficiency and data accuracy. When processing funds, relevant algorithms ensure feasible and accurate receipt of payments, reducing risk. Combined with mechanisms such as cashier functions, refund processing, data updates, and log recording, the system's flexibility and reliability are enhanced. An exception handling module ensures smooth process flow, providing strong support for enterprise finance and business development.

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

[0013] A method for processing funds in a combined order placement scenario, characterized by comprising:

[0014] Create a process control engine and use it as the core module to control and execute the overall process;

[0015] In the process control engine, a state machine-based process control submodule is set up to manage the various states and their transitions in the combined order fund processing process.

[0016] Preset each state in the combined order fund processing flow;

[0017] Set corresponding trigger conditions and transition rules for each state;

[0018] Set the state machine maintenance trigger conditions and corresponding transition rules to ensure that the process can proceed smoothly according to the predetermined logic;

[0019] When a combined order request is generated, the system checks whether the trigger conditions for each state are met. If they are met, the process control engine automatically switches to the corresponding state based on the trigger conditions and conversion rules, and continues to execute subsequent operations until the combined order and fund processing processes are completed.

[0020] Based on the above technical solution, the various states in the combined order processing flow include:

[0021] Invoice initialization: When a combined invoice request is received, the relevant data and status are initialized;

[0022] Payment Confirmation: The user confirms the payment information and prepares to process the funds;

[0023] During payment collection: This involves actually executing payment collection operations, including accessing the cashier, processing mixed payments, and applying discounts and offers.

[0024] Refund Confirmation: The user confirms the refund information and prepares to process the refund.

[0025] Refund in progress: The actual execution of refund operations, including processing over-collection refunds, converting over-collection payments to prepayments, or issuing direct refunds;

[0026] Order completion: The entire process of order processing and fund handling is completed, and relevant documents and account status are updated.

[0027] Based on the above technical solution, after obtaining the combined invoice request, the following strategy is used to determine which documents need to be included in the request for processing:

[0028] User selection and confirmation strategy: Users select the documents to be combined through the interface. The documents include: sales order, return order, expense order, exchange order, and return order.

[0029] Business rules and logical judgment strategies: Based on preset business rules, determine which documents among the currently unprocessed documents can be processed together. The preset business rules are based on document type, document status, customer consistency, product relevance, and amount relationship as judgment conditions.

[0030] Amount and financial verification strategy: Pre-set verification rules for amount and financial aspects, including checking the total amount of documents, the amount receivable, and the amount received to determine whether the financial indicators meet the requirements for combined invoicing;

[0031] Assistance prompt strategy: Based on historical records and customer behavior pattern analysis, predict and recommend required documents for combined order processing and provide real-time prompts and feedback.

[0032] Based on the above technical solution, in the order initialization state, the data verification algorithm is used to verify the completeness and accuracy of the sales order, return order, and return order related documents involved in the combined order. If the verification fails, the user is prompted to correct the data.

[0033] Based on the above technical solution, in the payment confirmation state, the process control engine calls the debt amount judgment algorithm and the amount calculation algorithm, wherein the debt amount judgment algorithm is used to determine whether the customer's debt amount exceeds the preset limit. If it exceeds the limit, it will be processed according to the preset strategy.

[0034] Based on the above technical solution, when the cashier is invoked in the payment state, the cashier determines the payment account according to different business document types through a preset account matching algorithm. The cashier supports discounts and the mixed use of prepaid accounts and multiple fund accounts, and fills in the amount according to the preset default backfill amount rules.

[0035] Based on the above technical solution, in the refund process, when overpayment is involved, the system determines the refund account according to a preset refund account selection algorithm, does not support discounts or the mixed use of prepaid accounts and funds accounts, and fills in the amount according to the preset refund amount backfilling rules.

[0036] Based on the above technical solution, when updating relevant documents and account status in the order completion state, the settlement status and amount data of relevant documents such as sales orders, return orders, and return orders are updated simultaneously through a preset data update algorithm, as well as the balance data of customer accounts, funds accounts, and prepaid accounts.

[0037] Based on the above technical solution, the process control engine records log information for each state transition during the state transition process, including the state transition time, triggering conditions, and related document numbers, etc., through a log recording algorithm, for subsequent process tracing and problem investigation.

[0038] Based on the above technical solution, an exception handling module is also included. When an exception occurs during the combined order fund processing, such as payment system failure or network interruption, the exception handling module identifies the exception type according to the preset exception type matching algorithm and handles it according to the preset exception handling strategy, such as prompting the user, retrying the operation, or rolling back the process.

[0039] The fund processing method for combined order placement scenarios described in this invention has the following beneficial effects:

[0040] 1. By creating a process control engine and a state machine-based process control submodule, the combined order processing flow is automated and intelligent, reducing manual operation steps and improving the efficiency of fund processing.

[0041] 2. By using preset business rules and financial verification strategies, ensure the integrity and accuracy of document data during the combined invoicing process, avoid financial risks caused by data inconsistency or errors, and provide a reliable data foundation for financial accounting and business analysis;

[0042] 3. Through the exception handling module and log recording algorithm, abnormal situations in the combined order fund processing process can be detected and handled in a timely manner, such as payment system failures and network interruptions, to ensure the stable operation of the process and provide detailed records for subsequent process traceability and problem investigation.

[0043] 4. By employing user selection and confirmation strategies, as well as auxiliary prompt strategies, we provide more convenient and intelligent document selection and combination order creation operations, reducing the cumbersomeness of user operations and improving user satisfaction.

[0044] 5. By using the debt amount judgment algorithm and the amount calculation algorithm, the customer's debt amount is assessed during the payment confirmation stage, and situations exceeding the preset limit are promptly detected and handled, effectively reducing financial risk and ensuring fund security.

[0045] 6. During the order completion stage, relevant documents and account status are updated in real time through a preset data update algorithm to ensure the timeliness and accuracy of business data and provide timely and accurate information support for subsequent business operations. Attached Figure Description

[0046] The present invention includes the following figures:

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

[0048] Figure 1 The flowchart is a first embodiment of the fund processing method in a combined order scenario described in this invention. Detailed Implementation

[0049] 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.

[0050] like Figure 1As shown, the fund processing method in a combined order scenario according to the present invention includes:

[0051] Create a process control engine as the core module, responsible for the control and execution of the overall process; the process control engine controls every link of the entire process from start to finish, ensuring that each step is carried out in the predetermined order and rules, coordinating the work of each part, and ensuring the smooth operation of the entire process.

[0052] In the process control engine, a state machine-based process control submodule is set up to manage the various states and their transitions in the combined order fund processing process. The process control submodule is responsible for identifying the different states experienced in the combined order fund processing process and precisely controlling the transition process between these states.

[0053] Pre-set the various states in the combined order fund processing flow; clearly define the various states that may occur during the combined order fund processing process in advance, so that the whole process has a clear framework and direction, which facilitates subsequent management and control.

[0054] Set corresponding trigger conditions and transition rules for each state; by defining trigger conditions and transition rules for each state, the state machine will only transition from one state to another according to the predetermined transition rules when the specific trigger conditions are met. This ensures the controllability and determinism of the process transition.

[0055] Set state machine maintenance trigger conditions and corresponding transition rules to ensure that the process can proceed smoothly according to the predetermined logic; the state machine manages the maintenance work such as adding, deleting, modifying and querying trigger conditions and transition rules.

[0056] For example, a trigger condition refers to a condition or event that needs to be met in a specific state. These conditions or events will cause the state machine to transition from the current state to the next state. For example, if the trigger condition is "user confirms payment information", the state machine will transition from the "order initialization" state to the "payment confirmation" state only after the user confirms the payment information.

[0057] For example, transition rules refer to the specific rules that determine how a state machine transitions from one state to another after a triggering condition is met. These rules define the path and result of the state transition. For example, the transition rule is "After transitioning from the 'invoice initialization' state to the 'payment confirmation' state, execute the outstanding amount judgment algorithm and the amount calculation algorithm".

[0058] When a combined order request is generated, the system checks whether the trigger conditions for each state are met. If they are met, the process control engine automatically switches to the corresponding state based on the trigger conditions and conversion rules, and continues to execute subsequent operations until the combined order and fund processing processes are completed.

[0059] Based on the above technical solution, the various states in the combined order processing flow include:

[0060] Invoice initialization: When a combined invoice request is received, the relevant data and status are initialized;

[0061] Payment Confirmation: The user confirms the payment information and prepares to process the funds;

[0062] During payment collection: This involves actually executing payment collection operations, including accessing the cashier, processing mixed payments, and applying discounts and offers.

[0063] Refund Confirmation: The user confirms the refund information and prepares to process the refund.

[0064] Refund in progress: The actual execution of refund operations, including processing over-collection refunds, converting over-collection payments to prepayments, or issuing direct refunds;

[0065] Order completion: The entire process of order processing and fund handling is completed, and relevant documents and account status are updated.

[0066] Based on the above technical solution, after obtaining the combined invoice request, the following strategy is used to determine which documents need to be included in the request for processing:

[0067] User selection and confirmation strategy: Users select the documents to be combined through the interface. The documents include: sales order, return order, expense order, exchange order, and return order.

[0068] Business rules and logical judgment strategies: Based on preset business rules, determine which documents among the currently unprocessed documents can be processed together. The preset business rules are based on document type, document status, customer consistency, product relevance, and amount relationship as judgment conditions. For example, preset business rules are generated based on the status of "unapproved" or "approved but not settled" as judgment conditions, and then the unprocessed documents are filtered.

[0069] Amount and financial verification strategy: Pre-set verification rules for amount and financial aspects, including checking the total amount of documents, the amount receivable, and the amount received to determine whether the financial indicators meet the requirements for combined invoicing;

[0070] Assistance prompt strategy: Based on historical records and customer behavior pattern analysis, predict and recommend required documents for combined order processing and provide real-time prompts and feedback.

[0071] In this embodiment, the user selection and confirmation strategy grants users a high degree of autonomy. Different users may have different business needs and considerations when combining orders. Allowing users to freely select the sales orders, return orders, expense orders, exchange orders, and return orders to be combined through the interface can meet the diverse and personalized needs of users. This allows users to flexibly configure the documents involved in combining orders according to the actual business scenario, rather than being bound by fixed rules.

[0072] Business rules and logical judgment strategies are based on criteria such as document type, document status, customer consistency, product relevance, and monetary relationship. Pre-defined business rules are used to filter documents that can be combined for processing. This helps ensure that the combined invoicing process conforms to the company's business logic and standards, avoiding unreasonable or non-compliant document combinations. For example, filtering documents based on "unapproved" or "approved but not settled" ensures that the documents involved in the combination are in the appropriate business status, reducing business risk.

[0073] The amount and financial verification strategy pre-sets verification rules for amounts and financial aspects, checking financial indicators such as the total amount, accounts receivable, and amount received on documents to ensure that these indicators meet the requirements for combined invoicing. This helps prevent financial data errors caused by improper document combination, ensuring the accuracy and reliability of financial data.

[0074] The auxiliary suggestion strategy, based on historical data and customer behavior pattern analysis, can predict and recommend the necessary documents for combining orders, and provide real-time prompts and feedback. This helps users quickly find suitable documents to combine, reducing search and filtering time and improving business processing efficiency.

[0075] Based on the above technical solution, in the order initialization state, the data verification algorithm is used to verify the completeness and accuracy of the sales order, return order, and return order related documents involved in the combined order. If the verification fails, the user is prompted to correct the data.

[0076] Combination order processing involves various documents such as sales orders, return orders, and reimbursement orders. The data integrity of these documents is crucial for subsequent fund processing and business decisions. By checking the document data using data validation algorithms, it can be ensured that all necessary data items are filled in, avoiding process interruptions or errors due to missing data. For example, if a sales order lacks product quantity or unit price information, the amount receivable cannot be accurately calculated, thus affecting collection and settlement operations.

[0077] Verification algorithms can check the logical rationality and consistency of data, such as whether the amount calculation is correct and the date is reasonable. If data errors exist, it may lead to inaccurate financial statements and flawed business decisions. By promptly identifying and correcting data errors during the invoicing initialization phase, data quality can be improved, providing a reliable foundation for subsequent business operations.

[0078] Accurate and complete document data is a prerequisite for the smooth operation of combined invoicing and fund processing. Data errors during the process may lead to interruptions or prevent normal progress. Data validation can proactively eliminate these potential problems, ensuring the process proceeds smoothly according to predetermined logic and improving the consistency and stability of business operations.

[0079] Based on the above technical solution, in the payment confirmation state, the process control engine calls the debt amount judgment algorithm and the amount calculation algorithm, wherein the debt amount judgment algorithm is used to determine whether the customer's debt amount exceeds the preset limit. If it exceeds the limit, it will be processed according to the preset strategy.

[0080] In the scenario of combined order placement, the payment confirmation status calls the outstanding amount judgment algorithm and the amount calculation algorithm to verify the funds. Therefore, this status is a critical node in fund processing and is directly related to the feasibility and accuracy of subsequent payment operations.

[0081] The payment confirmation status marks a critical juncture, indicating the imminent actual payment collection. Calling the outstanding balance assessment algorithm allows for a pre-collection evaluation of the customer's debt risk. By comparing data such as the customer's cumulative outstanding balance, the current amount due, and uncollected amounts for unsigned orders with the maximum outstanding balance limit set in the customer's profile, it can be determined whether the customer has sufficient outstanding balance for the transaction. If the limit is exceeded, timely measures are taken, such as intercepting the transaction or prompting the customer to adjust their payment method, effectively reducing financial risk. The amount calculation algorithm, invoked in this status, ensures the accuracy of the collected amount. Combined invoicing involves multiple document types, such as sales orders, return orders, and reimbursement orders. The amounts of each document, as well as overall order discounts, influence each other. The amount calculation algorithm needs to comprehensively consider these factors to accurately calculate the amount due / refundable, providing a reliable basis for subsequent payment collection operations.

[0082] This embodiment, from the perspective of strengthening risk management, specifically includes:

[0083] Assessing Debt Risk: The debt limit assessment algorithm comprehensively evaluates a customer's debt risk before the actual collection process begins. It integrates multi-dimensional data, including the customer's cumulative debt amount, the current receivable amount, and outstanding amounts for unsigned orders, and meticulously compares this data with the pre-set maximum debt limit in the customer's file to accurately determine whether the customer has sufficient debt limit to proceed with the transaction. This process acts like a robust defense for the company's financial security, identifying potential risk factors in advance and effectively avoiding bad debt losses due to excessive customer debt.

[0084] Once the system determines that a customer's outstanding balance exceeds the preset limit, it can quickly take corresponding measures according to the preset strategy, such as decisively blocking the transaction or promptly prompting the customer to adjust the payment method. This rapid response mechanism can minimize the financial risks faced by enterprises, ensure the stability and health of the enterprise's cash flow, and guarantee the normal operation and development of the enterprise.

[0085] Accurate Calculation of Receivables: In scenarios involving combined invoicing, the calculation of receivables becomes complex and prone to errors due to the interplay and mutual influence of various document types, such as sales orders, return orders, and payment receipts, as well as factors like overall order discounts. The appropriate amount calculation algorithm comprehensively considers all these complex factors and uses scientifically sound calculation methods to accurately calculate the amount receivable or refundable. This provides a solid and reliable basis for subsequent payment operations, preventing financial disputes and business chaos caused by incorrect amount calculations.

[0086] Accurate calculation of payment amounts is not only fundamental to the smooth operation of payment collection, but also crucial to ensuring the accuracy of all transaction data. Only by ensuring the accuracy of amounts during the payment confirmation stage can the authenticity and reliability of subsequent financial statements be guaranteed, providing strong support for the company's financial management and decision-making.

[0087] Improve payment collection efficiency: By accurately calculating the customer's outstanding balance and the amount due in advance during the payment confirmation process, delays and repeated communications caused by outstanding balance issues or calculation errors can be avoided during the actual payment collection process. This allows for smoother and more efficient payment collection, reducing unnecessary time and labor costs, and improving the company's business processing efficiency.

[0088] The invocation of these two algorithms makes the payment confirmation status a critical control point in the fund processing flow. By effectively managing and monitoring this stage, businesses can ensure that the entire fund processing flow proceeds in an orderly manner according to predetermined rules and logic. In case of any anomalies, timely detection and appropriate adjustments can be made, enhancing the controllability and stability of the business process.

[0089] Based on the above technical solution, when the cashier is invoked in the payment state, the cashier determines the payment account according to different business document types through a preset account matching algorithm. The cashier supports discounts and the mixed use of prepaid accounts and multiple fund accounts, and fills in the amount according to the preset default backfill amount rules.

[0090] Different types of business documents often correspond to different payment requirements and financial rules. Through a pre-set account matching algorithm, the cashier can accurately determine the receiving account based on the specific business document type. This avoids errors that may occur due to manual account selection, ensuring that every payment is accurately deposited into the corresponding account, guaranteeing the accuracy and traceability of financial data. For example, sales orders and return orders may correspond to different receiving accounts; the algorithm can quickly and accurately distinguish and match them.

[0091] In practice, businesses may offer discounts or incentives to customers to boost sales, manage customer relationships, or respond to market competition. Cash register support for discounts allows businesses to flexibly handle these situations during the payment process, meeting the needs of different business scenarios. This helps businesses better conduct marketing activities, improve customer satisfaction and loyalty, and also allows for flexible adjustments to sales strategies and pricing systems based on actual circumstances.

[0092] The ability to combine advance payment accounts with multiple cash accounts provides businesses with greater choice and flexibility in payment methods. Customers can choose to combine various payment methods, such as advance payments, cash, bank cards, and electronic payments, based on their financial situation and business needs. For businesses, this approach better meets customer payment preferences, increases the success rate of payment collection, and also helps optimize the efficiency of corporate cash management and utilization.

[0093] Based on the above technical solution, in the refund process, when overpayment is involved, the system determines the refund account according to a preset refund account selection algorithm, does not support discounts or the mixed use of prepaid accounts and funds accounts, and fills in the amount according to the preset refund amount backfilling rules.

[0094] The pre-defined refund account selection algorithm can accurately determine the refund account based on specific rules. This effectively avoids refund errors, prevents funds from being mistakenly refunded to the wrong account, and protects the company's financial security. For example, in complex business scenarios, customers may have multiple associated accounts; the algorithm can accurately locate the correct refund account based on business logic and data records, reducing financial risk.

[0095] The restriction against discounts and the mixing of prepaid and cash accounts is designed to simplify the refund process and reduce potential loopholes in fund management due to complex operations. Mixing discounts and accounts can complicate the calculation and flow of refund amounts, increasing the difficulty and risk of fund management. This restriction ensures that the flow of refund funds is clear and traceable, guaranteeing the reasonable use and security of corporate funds.

[0096] The system fills in refund amounts according to preset rules, providing a unified standard and specification for refund operations. This ensures that different refund processes are handled systematically, avoiding operational discrepancies and confusion caused by human factors. Regardless of which employee handles a refund, they can operate according to the same rules, guaranteeing the consistency and standardization of the business process.

[0097] The preset refund amount filling rules can comprehensively consider various factors and accurately calculate the amount of overcharged refunds. This avoids errors that may occur due to manual calculation and ensures the accuracy of the refund amount.

[0098] Based on the above technical solution, when updating relevant documents and account status in the order completion state, the settlement status and amount data of relevant documents such as sales orders, return orders, and return orders are updated simultaneously through a preset data update algorithm, as well as the balance data of customer accounts, funds accounts, and prepaid accounts.

[0099] In this embodiment, the settlement status and amount data of related documents such as sales orders, return orders, and reimbursement orders are dynamically changing throughout the business process. Timely updating of this information upon completion of the order process ensures that document information is synchronized with actual business operations. For example, if the settlement status of a sales order is not updated to "settled" in a timely manner after the combined order processing and fund handling process is completed, subsequent business personnel may misjudge the status of the document and perform unnecessary processing again, leading to business chaos. Through a preset data update algorithm, the latest status of documents can be reflected quickly and accurately, providing reliable data support for the company's business operations.

[0100] Customer account, cash account, and advance payment account balances are crucial indicators for corporate financial management. Timely updates to these account balances after an order is placed ensure the company has a clear and accurate understanding of its financial situation. For example, if a customer pays part of the amount in a combined order, the advance payment account balance decreases accordingly, while the cash account balance increases. Failure to update this data promptly may lead to deviations in the company's financial planning and decision-making, impacting financial security and normal operations.

[0101] The order completion status is a crucial node in the combined order creation and fund processing workflow. Updating relevant documents and account status is the final step in this process and a key link connecting current and subsequent business operations. Automating these operations through data update algorithms makes the entire business process more seamless, avoiding interruptions caused by delays or errors in manual operations. For example, once the document settlement status is updated, subsequent steps such as financial statement generation and inventory management can be based on the latest data, ensuring close collaboration between various business processes.

[0102] Updating this data upon completion of invoices ensures that financial statements accurately reflect a company's financial condition and operating results. For example, items such as accounts receivable and advances from customers in the balance sheet, and sales revenue and cost of goods sold in the income statement, are closely related to the status of relevant documents and accounts. Accurate financial statements provide management with a basis for decision-making, helping them formulate reasonable business strategies and financial plans.

[0103] Based on the above technical solution, the process control engine records log information for each state transition during the state transition process, including the state transition time, triggering conditions, and related document numbers, etc., through a log recording algorithm, for subsequent process tracing and problem investigation.

[0104] The log information records the state transition time, triggering conditions, and involved document numbers, making the entire combined invoice processing flow visible. Managers can clearly understand the specific execution status of each step by reviewing the logs, including when a certain state is entered, the reason for the state transition, and which business documents are involved. This facilitates real-time monitoring of the business process, enabling timely detection of anomalies or potential problems, and allowing for appropriate adjustments and optimizations.

[0105] When issues arise during the processing of combined order funds, log records can help technical and business personnel quickly pinpoint the problem. By reviewing the status transition logs, the specific stage and time of the problem can be traced, revealing the triggering conditions and involved documents, thereby narrowing down the scope of troubleshooting and saving time and costs in problem resolution. For example, if an anomaly occurs in the payment collection process, the logs can be used to view information related to the transition from the payment confirmation status to the "payment in progress" status, determining whether the problem was caused by unmet triggering conditions or incorrect execution of the transition rules.

[0106] Based on the above technical solution, an exception handling module is also included. When an exception occurs during the combined order fund processing, such as payment system failure or network interruption, the exception handling module identifies the exception type according to the preset exception type matching algorithm and handles it according to the preset exception handling strategy, such as prompting the user, retrying the operation, or rolling back the process.

[0107] In the combined order processing flow, unforeseen circumstances such as payment system failures and network interruptions are difficult to avoid. The exception handling module can respond quickly to these emergencies, accurately identifying the problem based on a pre-defined exception type matching algorithm. For example, when a network interruption occurs, the system can quickly determine the exception type, preventing the process from completely stalling due to unexpected events.

[0108] When an abnormal situation occurs, the exception handling module will promptly notify the user, so that the user is clearly aware of the problem encountered in the current process; the user does not need to try to solve complex exception problems on their own, which reduces the user's operation cost and time cost.

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

[0110] 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 processing funds in a combined order placement scenario, characterized in that, include: Create a process control engine and use it as the core module to control and execute the overall process; In the process control engine, a state machine-based process control submodule is set up to manage the various states and their transitions in the combined order fund processing process. Preset each state in the combined order fund processing flow; Set corresponding trigger conditions and transition rules for each state; Set the state machine maintenance trigger conditions and corresponding transition rules to ensure that the process can proceed smoothly according to the predetermined logic; When a combined order request is generated, the system checks whether the trigger conditions for each state are met. If they are met, the process control engine automatically switches to the corresponding state based on the trigger conditions and conversion rules, and continues to execute subsequent operations until the combined order and fund processing processes are completed.

2. The fund processing method in a combined order placement scenario as described in claim 1, characterized in that, The various states in the combined order processing flow include: Invoice initialization: When a combined invoice request is received, the relevant data and status are initialized; Payment Confirmation: The user confirms the payment information and prepares to process the funds; During payment collection: This involves actually executing payment collection operations, including accessing the cashier, processing mixed payments, and applying discounts and offers. Refund Confirmation: The user confirms the refund information and prepares to process the refund. Refund in progress: The actual execution of refund operations, including processing over-collection refunds, converting over-collection payments to prepayments, or issuing direct refunds; Order completion: The entire process of order processing and fund handling is completed, and relevant documents and account status are updated.

3. The fund processing method in a combined order scenario as described in claim 1, characterized in that, After obtaining the combined invoice request, the following strategy is used to determine which documents need to be included in the request for processing: User selection and confirmation strategy: Users select the documents to be combined through the interface. The documents include: sales order, return order, expense order, exchange order, and return order. Business rules and logical judgment strategies: Based on preset business rules, determine which documents among the currently unprocessed documents can be processed together. The preset business rules are based on document type, document status, customer consistency, product relevance, and amount relationship as judgment conditions. Amount and financial verification strategy: Pre-set verification rules for amount and financial aspects, including checking the total amount of documents, the amount receivable, and the amount received to determine whether the financial indicators meet the requirements for combined invoicing; Assistance prompt strategy: Based on historical records and customer behavior pattern analysis, predict and recommend required documents for combined order processing and provide real-time prompts and feedback.

4. The fund processing method in a combined order scenario as described in claim 1, characterized in that, In the order initialization state, the data verification algorithm checks the completeness and accuracy of the relevant document data of the sales order, return order, and return order involved in the combined order. If the verification fails, the user is prompted to correct the data.

5. The fund processing method in a combined order scenario as described in claim 1, characterized in that, In the payment confirmation state, the process control engine calls the debt amount judgment algorithm and the amount calculation algorithm. The debt amount judgment algorithm is used to determine whether the customer's debt amount exceeds the preset limit. If it does, it is processed according to the preset strategy.

6. The fund processing method in a combined order scenario as described in claim 1, characterized in that, When the cashier is invoked during the payment process, the cashier determines the payment account based on different business document types using a preset account matching algorithm. The cashier supports discounts and the mixed use of prepaid accounts and multiple fund accounts, and fills in the amount according to the preset default amount filling rules.

7. The fund processing method in a combined order scenario as described in claim 1, characterized in that, In the refund process, when overpayment is involved, the system determines the refund account based on a preset refund account selection algorithm. It does not support discounts or the mixed use of prepaid accounts and funds accounts, and fills in the amount according to the preset refund amount backfilling rules.

8. The fund processing method in a combined order placement scenario as described in claim 1, characterized in that, When the order is completed, and the relevant documents and account status are updated, the settlement status and amount data of the sales order, return order, and return order are updated simultaneously using a preset data update algorithm, as well as the balance data of the customer account, fund account, and prepaid account.

9. The fund processing method in a combined order scenario as described in claim 1, characterized in that, During the state transition process, the process control engine records log information for each state transition, including the state transition time, triggering conditions, and the document number involved. This is achieved through a log recording algorithm and is used for subsequent process tracing and problem investigation.

10. The fund processing method in a combined order scenario as described in claim 1, characterized in that, It also includes an exception handling module. When an exception occurs during the processing of funds for combined order opening, the exception handling module identifies the exception type according to a preset exception type matching algorithm and handles it according to a preset exception handling strategy.

Images