Account period determination method and device, equipment, storage medium and program product
By receiving user-configured start date, settlement date, and payment date parameters from the ERP system, and combining them with preset rules and a list of prohibited payment dates, the payment period is dynamically calculated, solving the problem of inflexible payment period management in existing technologies and achieving effectiveness and efficiency in payment period management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2026-03-31
AI Technical Summary
Existing ERP systems lack flexibility in determining payment terms, making it difficult to match customers' actual needs and leading to chaotic payment term management.
A method for determining payment terms is provided. By receiving parameters such as the start date, settlement date, and payment date entered by the user in the configuration interface, and combining them with preset rules and a list of prohibited payment dates, the final payment terms are dynamically calculated to suit the customer's actual situation.
It enables dynamic calculation of payment terms based on customer needs, ensuring the effectiveness and efficiency of payment term management and reducing the chaos in payment term management.
Smart Images
Figure CN121767115A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of system management, and in particular to a method, apparatus, device, storage medium, and program product for determining payment terms. Background Technology
[0002] Enterprise Resource Planning (ERP) management systems include the management of payment terms in financial documents for receivables and payables, such as start dates, closing dates, payment cycles, and payment dates. In particular, the management of payment dates has a significant impact on a company's cash flow and risk control.
[0003] Currently, ERP systems often determine payment terms such as settlement dates and payment dates directly based on the start date and preset date calculation rules. This method of determining payment terms is relatively simplistic and difficult to match with the actual needs of customers. As a result, it is difficult for both parties to complete the corresponding payment terms within the determined payment period, which can easily lead to problems of chaotic payment term management for enterprises. Summary of the Invention
[0004] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a method, apparatus, equipment, storage medium and program product for determining payment terms, which can take into account the actual situation of the customer when determining the payment terms related to transactions, incorporate the payment term parameters configured by the customer when calculating the payment terms, and ensure the effectiveness of the enterprise's payment term management by the final calculated payment terms.
[0005] Firstly, this application provides a method for determining payment terms. The method includes: Receive user operations on the billing period configuration interface and obtain billing period configuration parameters; billing period configuration parameters include the user-selected start date, settlement configuration parameters, and payment configuration parameters; settlement configuration parameters are used to characterize the settlement date and / or settlement date rules, and payment configuration parameters are used to characterize the payment date and / or payment date rules; The user's start date, settlement date, and payment date are determined based on the start date, settlement configuration parameters, and payment configuration parameters.
[0006] In conjunction with the first aspect, in one possible implementation, determining the user's start date, settlement date, and payment date based on the start date, settlement configuration parameters, and payment configuration parameters includes: determining the settlement date represented by the settlement configuration parameters that is after the start date and has the shortest interval with the start date as the user's settlement date; determining the initial payment date based on the settlement date and payment cycle; and determining the payment date represented by the payment configuration parameters that is after the initial payment date and has the shortest interval with the initial payment date as the user's payment date.
[0007] In conjunction with the first aspect, in one possible implementation, the method for determining the payment period also includes: determining the settlement date represented by the settlement configuration parameters based on the settlement date rules and the start date; and determining the payment date represented by the payment configuration parameters based on the payment date rules and the initial payment date.
[0008] In conjunction with the first aspect, in one possible implementation, determining the settlement date represented by the settlement configuration parameters based on the settlement date rule and the start date includes: converting the start date according to the time unit corresponding to the settlement date rule; the time unit includes at least one of weekday and date; determining the time interval between the start date and the settlement date based on the start date after the time unit conversion; and determining the settlement date represented by the settlement configuration parameters based on the start date and the time interval between the start date and the settlement date.
[0009] In conjunction with the first aspect, in one possible implementation, determining the payment date represented by the payment configuration parameters based on the payment date rule and the initial payment date includes: converting the initial payment date according to the time unit corresponding to the payment date rule; the time unit includes at least one of weekday and date; determining the time interval between the initial payment date and the payment date based on the initial payment date after the time unit conversion; and determining the payment date represented by the payment configuration parameters based on the initial payment date and the time interval between the initial payment date and the payment date.
[0010] In conjunction with the first aspect, in one possible implementation, the payment period determination method further includes: matching the user's payment date with a preset list of prohibited payment dates; if there is a preset prohibited payment date in the list that matches the user's payment date, then the user's payment date is corrected.
[0011] In conjunction with the first aspect, one possible implementation method for determining the payment period also includes managing the user's transactions based on the user's start date, settlement date, and payment date.
[0012] In conjunction with the first aspect, in one possible implementation, the payment period configuration interface includes a start date configuration item, a settlement date configuration item, a payment cycle configuration item, and a payment date configuration item; the start date configuration item includes a start date configuration item and a start date type configuration item, the settlement date configuration item includes a settlement date configuration item and a settlement date rule configuration item, and the payment date configuration item includes a payment date configuration item and a payment date rule configuration item.
[0013] Secondly, this application also provides a payment term determination device. The device includes: The receiving module is used to receive user operations on the billing period configuration interface and obtain billing period configuration parameters. The billing period configuration parameters include the user-selected start date, settlement configuration parameters, and payment configuration parameters. The settlement configuration parameters are used to represent the settlement date and / or settlement date rules, and the payment configuration parameters are used to represent the payment date and / or payment date rules. The determination module is used to determine the user's start date, settlement date, and payment date based on the start date, settlement configuration parameters, and payment configuration parameters.
[0014] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method described in the first aspect.
[0015] Fourthly, this application also provides a computer-readable storage medium. This computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the method described in the first aspect.
[0016] Fifthly, this application also provides a computer program product. This computer program product includes a computer program that, when executed by a processor, implements the method described in the first aspect.
[0017] This application provides a method, apparatus, device, storage medium, and program product for determining payment terms. It provides customers with a configuration interface for transaction-related payment terms, allowing them to configure these terms according to their needs or actual circumstances. Upon receiving the payment term parameters configured by the customer in the configuration interface, the final payment term is determined based on these parameters. This application takes into account the customer's actual situation when determining transaction-related payment terms, incorporating the customer-configured payment term parameters into the calculation, thus ensuring the effectiveness of enterprise payment term management. Attached Figure Description
[0018] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is a flowchart illustrating a method for determining payment terms in one embodiment; Figure 2 This is a schematic diagram of the payment period configuration interface for a payment period determination method in one embodiment; Figure 3 This is a schematic diagram of another payment period configuration interface for a payment period determination method in one embodiment; Figure 4 This is another flowchart illustrating the payment period determination method in one embodiment; Figure 5This is another flowchart illustrating the payment period determination method in one embodiment; Figure 6 This is a schematic diagram of another payment period configuration interface for a payment period determination method in one embodiment; Figure 7 This is a schematic diagram of another payment period configuration interface for a payment period determination method in one embodiment; Figure 8 This is another flowchart illustrating the payment period determination method in one embodiment; Figure 9 Here is a calendar chart showing the payment period in one embodiment; Figure 10 This is a schematic diagram of another payment period configuration interface for a payment period determination method in one embodiment; Figure 11 This is a calendar chart for another billing period in one embodiment; Figure 12 This is a calendar chart for another billing period in one embodiment; Figure 13 This is a calendar chart for another billing period in one embodiment; Figure 14 This is another flowchart illustrating the payment period determination method in one embodiment; Figure 15 This is a schematic diagram illustrating a preset no-payment date in one embodiment; Figure 16 This is a schematic diagram of another preset no-payment date in one embodiment; Figure 17 Here is a flowchart of the payment period determination process in one embodiment; Figure 18 This is a schematic diagram of the transaction process in one embodiment; Figure 19 This is a schematic diagram of an accounting voucher in one embodiment; Figure 20 This is a schematic diagram of the payment period management interface in one embodiment; Figure 21 This is a schematic diagram of a modification approval form for the starting date in one embodiment; Figure 22 This is a structural block diagram of a payment period determination device in one embodiment; Figure 23 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation
[0019] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.
[0020] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. The present application will now be described in detail with reference to the accompanying drawings and embodiments. Furthermore, the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The terms "first" and "second," etc., in the specification and claims of the embodiments of this application are used to distinguish different objects, not to describe a specific order of objects.
[0021] In one embodiment, such as Figure 1 As shown, a method for determining payment terms is provided. This embodiment illustrates the application of this method to a terminal. It is understood that this method can also be applied to a server, and further to a system including both a terminal and a server, and implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps: Step 101: Receive user operations on the billing period configuration interface and obtain billing period configuration parameters.
[0022] In this embodiment of the application, a configuration interface for transaction-related billing periods can be provided to customers so that they can configure transaction-related billing periods according to their own needs or actual circumstances.
[0023] like Figure 2 As shown, the payment period configuration interface can include the start date configuration item (i.e., the payment basis in the figure), the settlement date configuration item (i.e., the customer's fixed settlement date in the figure), the payment cycle configuration item (i.e., the number of days in the figure), and the payment date configuration item (i.e., the customer's fixed payment date in the figure).
[0024] Accordingly, the payment period configuration parameters can include the user-selected start date, settlement configuration parameters, and payment configuration parameters. The system receives user input on the start date configuration item in the payment period configuration interface and retrieves the user-selected start date; it receives user input on the settlement date configuration item in the payment period configuration interface and retrieves the settlement configuration parameters; and it receives user input on the payment date configuration item in the payment period configuration interface and retrieves the payment configuration parameters.
[0025] The start date configuration item can include a start date configuration item and a start date type configuration item. When configuring the start date, users can directly enter the desired start date in the start date configuration item, or as follows: Figure 3 As shown, in the Start Date Type configuration item, select the date corresponding to the transaction-related date node type as the start date. The transaction-related date node types are shown in Table 1 below: Table 1
[0026] The settlement date configuration items can include the settlement date configuration item (i.e., the fixed date of each month in the figure) and the settlement date rule configuration item (i.e., the fixed date of each week in the figure). When configuring the settlement date, users can directly select or enter the desired settlement date in the settlement date configuration item, such as entering the 12th, 13th, or 15th, or checking the end of the month.
[0027] It should be noted that the settlement date configured by the user in the settlement date configuration item does not include the month, but only the specific date within the month, such as the 12th, 13th, 15th, the end of the month, etc. The settlement date configured by the user indicates that the customer, considering their own needs, can or expects to settle transactions on the aforementioned dates within a certain month.
[0028] Alternatively, users can select or enter settlement date rules in the settlement date rules configuration section. Settlement date rules can be weekdays; for example, users can enter or select Wednesday, Thursday, or Friday. These settlement date rules indicate that the customer, considering their needs, can or expects to settle transactions on the aforementioned weekdays.
[0029] The settlement date configuration item indicates that the customer configures the desired settlement date on a monthly basis, while the settlement date rule configuration item indicates that the customer configures the desired settlement date on a weekly basis. Therefore, the settlement configuration parameters include at least one desired settlement date or at least one desired number of weeks for settlement.
[0030] The payment date configuration options can include the payment date configuration option (i.e., a fixed date each month in the diagram) and the payment date rule configuration option (i.e., a fixed date each week in the diagram). When configuring the payment date, users can directly select or enter the desired payment date in the payment date configuration option, such as entering the 25th, 26th, or 27th, or checking the end of the month option.
[0031] It should be noted that the payment date configured by the user in the payment date configuration section does not include the month, but only the specific date within the month, such as the 25th, 26th, 27th, or the end of the month. This payment date configured by the user indicates that the customer, considering their own needs, can or expects to make payment on the aforementioned date within a certain month.
[0032] Alternatively, users can select or enter payment date rules in the payment date rules configuration section. Payment date rules can be weekdays; for example, users can enter or check Monday or Friday. This payment date rule indicates that the customer, considering their needs, can or expects to make payment on the specified weekday.
[0033] The payment date configuration item allows customers to configure their expected payment dates monthly, while the payment date rule configuration item allows customers to configure their expected payment dates weekly. Therefore, payment configuration parameters include at least one expected payment date or at least one expected number of weeks for payment.
[0034] Step 102: Determine the user's start date, settlement date, and payment date based on the start date, settlement configuration parameters, and payment configuration parameters.
[0035] In this embodiment of the application, after receiving the start date, settlement configuration parameters and payment configuration parameters configured by the user, the user-configured billing period is not directly used as the final billing period. Instead, the user-configured billing period is used as the basis to determine the final billing period in combination with pre-set rules.
[0036] Regarding the start date, if the user directly enters at least one expected start date in the start date configuration field, then any expected start date can be selected from the at least one expected start date as the start date, or the first expected start date entered by the user can be selected as the start date, or an expected start date that is beneficial to management can be selected from the at least one expected start date as the start date.
[0037] If the user enters at least one expected start date in the start date configuration field and selects a start date type in the start date type configuration field, the expected start date entered by the user shall prevail.
[0038] If a user selects a specific start date type in the start date type configuration item, the date corresponding to that start date type can be used as the start date; or the highest priority base date among the base dates corresponding to that start date type can be used as the start date.
[0039] The base date can include the types listed in Table 2 below: Table 2
[0040] Among them, "Manual Base Date - Approval" indicates the start date that the system has approved and that the customer has actively modified; "Manual Base Date - Update" indicates the start date determined based on the updated rules.
[0041] The priority of the base date for each start date type is shown in Table 3 below: Table 3
[0042] As shown in Table 3, the priority of the base date corresponding to the shipping date, from highest to lowest, is: manual base date - approval, transfer date, and shipping posting date. Distribution channel 10 can be for domestic sales, and channel 20 can be for international sales.
[0043] This priority mapping table can be obtained from the configuration table shown in Table 4 below: Table 4
[0044] If the user has not configured the settlement date in the settlement date configuration item, the start date can be used as the settlement date.
[0045] If the user enters or selects at least one expected settlement date in the settlement date configuration item, then at least one expected settlement date after the start date is determined, and one of them is selected as the settlement date; or, among at least one expected settlement date after the start date, the expected settlement date with the shortest time interval from the start date is selected as the settlement date.
[0046] Once the settlement date is determined, the initial payment date is the settlement date plus the payment cycle. The payment cycle can be configured by the customer or preset in the system. The preset payment cycles can be found in the configuration table shown in Table 5 below: Table 5
[0047] The initial payment date is the calculated date on which the customer should pay. However, this date may not reflect the customer's actual situation. Therefore, it is necessary to consider the payment configuration parameters configured by the customer in the payment date configuration item.
[0048] If the user has not configured the payment date in the payment date configuration item, the initial payment date can be used as the payment date.
[0049] If the user enters or selects at least one expected payment date in the payment date configuration item, then at least one expected payment date after the initial payment date is determined, and one of these dates is selected as the payment date; or, among at least one expected payment date after the initial payment date, the expected payment date with the shortest time interval from the initial payment date is selected as the payment date.
[0050] In one possible implementation, the payment period configuration interface may also include payment methods, such as wire transfer prepayment, for customers to select or enter a payment method that suits their actual situation.
[0051] In one possible implementation, the system determines the final start date, settlement date, and payment date based on the transaction-related billing periods configured by the customer in the billing period configuration interface. Then, it manages the user's transactions based on these dates. For example, it monitors whether both parties complete transaction settlement on the settlement date; it also monitors whether the customer completes payment on the payment date. If the customer fails to complete payment on the payment date, the system can control the subsequent transaction process through methods such as freezing the transaction.
[0052] The method provided in this application embodiment offers a configuration interface for transaction-related payment terms, allowing customers to configure these terms according to their needs or actual circumstances. Upon receiving the payment term parameters configured by the customer in the interface, the final payment terms are determined based on these parameters. This application embodiment considers the customer's actual situation when determining transaction-related payment terms, incorporating the customer-configured parameters into the calculation, thus ensuring the effectiveness of enterprise payment term management.
[0053] The embodiments described above illustrate a scheme for determining the final payment period based on customer-configured payment period parameters. In another embodiment of this application, the final payment period can be determined based on the principle of minimizing the time interval. That is, the aforementioned "determining the user's start date, settlement date, and payment date based on the start date, settlement configuration parameters, and payment configuration parameters" includes, for example: Figure 4 The steps shown are as follows: Step 201: Determine the settlement date of the user that is after the start date and has the shortest interval from the start date among the settlement dates represented by the settlement configuration parameters.
[0054] Step 202: Determine the initial payment date based on the settlement date and payment cycle.
[0055] Step 203: Determine the payment date that is after the initial payment date and has the shortest interval with the initial payment date among the payment dates represented by the payment configuration parameters.
[0056] In this embodiment, the settlement date represented by the settlement configuration parameter is first determined based on the specific date or weekday within the month configured by the customer in the settlement date configuration item. This settlement date represented by the settlement configuration parameter is a specific date including the year, month, and day. Then, at least one candidate settlement date that is after the start date is selected from at least one settlement date represented by the settlement configuration parameter. Finally, the candidate settlement date with the shortest time interval from the start date is determined as the user's settlement date, i.e., the final settlement date.
[0057] Once the settlement date is determined, the initial payment date is the settlement date plus the payment cycle.
[0058] Next, based on the specific date or weekday within the month configured by the customer in the payment date configuration item, the payment date represented by the payment configuration parameter is determined. This payment date represented by the payment configuration parameter is a specific date including the year, month, and day. Then, at least one candidate payment date that is after the initial payment date is selected from at least one payment date represented by the payment configuration parameter. Finally, the candidate payment date with the shortest time interval from the initial payment date is determined as the user's payment date, i.e., the final payment date.
[0059] The method provided in this application selects the settlement date that is after the start date and has the shortest interval with the start date from the settlement date represented by the settlement configuration parameters configured by the customer as the user's settlement date, and selects the payment date that is after the initial payment date and has the shortest interval with the initial payment date from the payment configuration parameters configured by the customer as the user's payment date. Taking into account the actual needs of customers, this shortens the transaction's billing cycle and improves the efficiency of transaction billing.
[0060] The embodiments described above introduce a scheme for determining the specific date represented by the payment term parameters configured by the customer. In another embodiment of this application, the specific date represented by the payment term parameters can be determined based on a specific date with year, month, and day (e.g., start date, initial payment date). This embodiment includes, as follows: Figure 5 The steps shown are as follows: Step 301: Determine the settlement date represented by the settlement configuration parameters based on the settlement date rules and the start date.
[0061] In this embodiment of the application, the year and month of the starting date are first determined. For example, the starting date is May 20, 2024.
[0062] For customers in such Figure 6 The settlement date configuration item shows the settlement parameters configured as follows: If a customer configures only one parameter in the settlement date configuration item, it means that the customer only checked the end of the month and did not fill in a date; or, the customer did not check the end of the month and only filled in a date.
[0063] If the customer only selects the end of the month and does not fill in the date, the end of the month in which the calculation begins will be the settlement date, which is May 31, 2024.
[0064] If the customer does not select the end of the month and only enters a date, the settlement date is compared with the number of days in the start date (i.e., the day in the year-month-day formula). If the number of days in the start date is less than or equal to the date entered by the customer, the month of the settlement date is the month of the start date. For example, if the customer enters the 26th, the settlement date is May 26th. If the number of days in the start date is greater than the date entered by the customer, the month of the settlement date is the month following the month of the start date. For example, if the customer enters the 16th, considering that the settlement date should be after the start date, the settlement date is June 16th.
[0065] If the customer does not select the end of the month and only enters one date, two dates can be generated based on the date entered by the customer, the month in which the calculation date falls, and the month following the month in which the calculation date falls. Then, the date that is after the calculation date and has the shortest time interval from the calculation date is selected as the settlement date. For example, if the customer enters the date 26, then May 26 and June 26 will be generated. Both dates are after the calculation date, but May 26 is the closest to the calculation date, so the settlement date is May 26. Similarly, if the customer enters the date 16, then May 16 and June 16 will be generated. Only June 16 is after the calculation date, so the settlement date is June 26.
[0066] If a customer has configured multiple parameters in the settlement date configuration item, it means that the customer has selected the end of the month and filled in at least one date; or, the customer has not selected the end of the month but has filled in multiple dates.
[0067] Multiple dates are generated based on the date entered or selected by the customer, the month of the start date, and the month following the start date. Specifically, the customer-entered or selected dates are prefixed with the month of the start date and the month following it. Understandably, the number of generated dates is twice the number of dates entered or selected by the customer. Then, the date generated that is after the start date and has the shortest time interval from it is selected as the settlement date. For example, if the customer enters the dates 16th and 17th and selects the end of the month, the generated dates are May 16th, May 17th, May 31st, June 16th, June 17th, and June 30th. Of these, May 31st, June 16th, June 17th, and June 30th are after the start date, but May 31st is the closest to the start date; therefore, May 31st is the settlement date.
[0068] For customers in such Figure 7 The settlement date rule configuration item shown illustrates the configuration of settlement parameters. The settlement configuration parameters represent the methods for determining the settlement date, including, for example... Figure 8 The steps shown are as follows: Step 401: Convert the starting date according to the time unit corresponding to the settlement date rule; the time unit includes at least one of weekday and date.
[0069] Step 402: Determine the time interval between the start date and the settlement date based on the start date after the time unit conversion.
[0070] Step 403: Determine the settlement date represented by the settlement configuration parameters based on the start date and the time interval between the start date and the settlement date.
[0071] First, the time units for the start date and the settlement parameters configured by the customer are standardized. Preferably, the start date is converted to a weekday, and the corresponding week sequence is determined. For example, ... Figure 9 As shown, if the starting date is the Monday of the fourth week of May, then the week number of the starting date is 1, and the week number is 4.
[0072] Then, determine the target week number from the customer's configured week number, which is greater than or equal to the week number of the start date and has the smallest time interval between it and the week number of the start date. Finally, the settlement date is the time interval corresponding to the target week number plus the start date. For example, if the customer configures week numbers 3 and 4, both greater than the week number 1 of the start date, and the time interval between Wednesday and Monday is the smallest, which is two days, then the settlement date is the start date plus two days, which is May 22nd.
[0073] If all the week numbers configured by the customer are less than the week number of the start date, then the target week number is determined by the week number with the smallest time interval between the customer's configured week numbers and the week number of the start date in the next week sorting corresponding to the start date. Finally, the time interval between the start date and the target week number is the settlement date. For example, if the start date is May 24th, which is the Friday of the fourth week, and the customer has configured week numbers 3 and 4, then the time interval between the fifth week's Wednesday and the start date is the smallest, which is five days. Therefore, the settlement date is the start date plus five days, which is May 29th.
[0074] One possible implementation is, such as Figure 10 As shown, the settlement date rule configuration item can also include a weekly sorting configuration item and a weekly sorting method configuration item. The weekly sorting method includes ascending and descending order. Based on the customer-configured weekly sorting, sorting method, and weekday number, the system determines the date within the month corresponding to the weekday number of the starting date, and the date within the following month of the month corresponding to the weekday number of the starting date. Then, the date with the shortest time interval from the starting date among the multiple dates corresponding to the weekday number is selected as the settlement date.
[0075] For example, such as Figure 9 and Figure 11 As shown, the starting date is May 20th, which is the Monday of the fourth week. The customer's configured week sort is 3, the sorting method is sequential, and the week number is 1 or 2. Therefore, the customer's configured week numbers correspond to May 13th, May 14th, June 10th, and June 11th. Among these, June 10th and June 11th are after the starting date, and June 10th has the shortest time interval with the starting date; therefore, the settlement date is June 10th.
[0076] For example, such as Figure 12 and Figure 13As shown, the start date is May 20th, which is the Monday of the fourth week. The customer's configured week order is 4, sorted in reverse order, with weekday numbers 2 and 5. Therefore, the customer's configured weekday numbers correspond to May 7th, May 10th, June 4th, and June 7th. Among these, June 4th and June 7th are after the start date, and June 7th has the shortest time interval with the start date; therefore, the settlement date is June 7th.
[0077] Step 302: Determine the payment date represented by the payment configuration parameters based on the payment date rules and the initial payment date.
[0078] In this embodiment of the application, the year and month of the initial payment date are first determined. For example, the initial payment date is May 20, 2024.
[0079] Regarding the above-mentioned customers Figure 6 The payment date configuration item shows the settlement parameters as follows: If a customer configures only one parameter in the payment date configuration item, it means that the customer only checked the end of the month and did not fill in a date; or, the customer did not check the end of the month and only filled in a date.
[0080] If the customer only selects the end of the month and does not fill in the date, the end of the month in which the initial payment date is located will be the payment date, which is May 31, 2024.
[0081] If the customer does not select the end of the month and only enters a date, the date entered by the customer is compared with the number of days in the initial payment date (i.e., the day in the year-month-day formula). If the number of days in the initial payment date is less than or equal to the date entered by the customer, the month of the payment date is the same as the month of the initial payment date. For example, if the customer enters the 26th, the payment date is May 26th. If the number of days in the initial payment date is greater than the date entered by the customer, the month of the payment date is the month following the month of the initial payment date. For example, if the customer enters the 16th, considering that the payment date should be after the initial payment date, the payment date is June 16th.
[0082] If the customer does not select the end of the month and only enters one date, two dates can be generated based on the date entered by the customer, the month of the initial payment date, and the month following the month of the initial payment date. Then, the date that is after the initial payment date and has the shortest time interval from it is determined as the payment date. For example, if the customer enters the 26th, then May 26th and June 26th are generated. Both dates are after the initial payment date, but May 26th is the closest, so the payment date is May 26th. Similarly, if the customer enters the 16th, then May 16th and June 16th are generated. Only June 16th is after the initial payment date, so the payment date is June 26th.
[0083] If a customer has configured multiple parameters in the payment date configuration item, it means that the customer has selected the end of the month and filled in at least one date; or, the customer has not selected the end of the month but has filled in multiple dates.
[0084] Multiple dates are generated based on the date entered or selected by the customer, the month of the initial payment date, and the month following the initial payment date. Specifically, the dates entered or selected by the customer are prefixed with the month of the initial payment date and the month following the initial payment date. Understandably, the number of generated dates is twice the number of dates entered or selected by the customer. Then, the date generated that is after the initial payment date and has the shortest time interval from the initial payment date is selected as the payment date. For example, if the customer enters the dates 16th and 17th and selects the end of the month, the generated dates are May 16th, May 17th, May 31st, June 16th, June 17th, and June 30th. Of these, May 31st, June 16th, June 17th, and June 30th are after the initial payment date, but May 31st is the closest to the initial payment date, so the payment date is May 31st.
[0085] Regarding the above-mentioned customers Figure 7 The payment date rule configuration item shown illustrates the settlement parameter configuration. The settlement configuration parameters represent the methods for determining the payment date, including, for example... Figure 14 The steps shown are as follows: Step 501: Convert the initial payment date according to the time unit corresponding to the payment date rule. The time unit includes at least one of weekdays and dates.
[0086] Step 502: Determine the time interval between the initial payment date and the payment date based on the initial payment date after time unit conversion.
[0087] Step 503: Determine the payment date represented by the payment configuration parameters based on the initial payment date and the time interval between the initial payment date and the payment date.
[0088] First, the time units for the initial payment date and the settlement parameters configured by the customer are standardized. Preferably, the initial payment date is converted into a weekday, and the corresponding week sequence is determined. For example, as shown above. Figure 9 As shown, if the initial payment date is the Monday of the fourth week of May, then the week number of the initial payment date is 1, and the week number is 4.
[0089] Then, among the weekdays configured by the customer, the target weekday is the one with the smallest time interval between the weekday of the initial payment date and the weekday of the initial payment date. Finally, the payment date is the initial payment date plus the corresponding time interval of the target weekday. For example, if the customer configures weekdays 3 and 4, both greater than the weekday of the initial payment date (1), and the time interval between Wednesday and Monday is the smallest (two days), then the payment date is the initial payment date plus two days, which is May 22nd.
[0090] If all the week numbers configured by the customer are less than the week number of the initial payment date, then the target week number is determined in the next week's week order following the initial payment date, based on the smallest time interval between the customer's configured week numbers and the week number of the initial payment date. Finally, the initial payment date plus the corresponding time interval of the target week number equals the payment date. For example, if the initial payment date is May 24th, which is the Friday of the fourth week, and the customer has configured week numbers 3 and 4, then the Wednesday of the fifth week has the smallest time interval with the initial payment date, which is five days. Therefore, the payment date is the initial payment date plus five days, which is May 29th.
[0091] One possible implementation is as described above. Figure 10 As shown, the payment date rule configuration item can also include a weekly sorting configuration item and a weekly sorting method configuration item. The weekly sorting method includes ascending and descending order. Based on the customer's configured weekly sorting, sorting method, and weekday number, the system determines the date within the month corresponding to the initial payment date, and the date within the following month. Then, the date with the shortest time interval from the initial payment date among the multiple dates corresponding to the weekday number is selected as the payment date.
[0092] For example, as above Figure 9 and above Figure 11 As shown, the initial payment date is May 20th, which is the Monday of the fourth week. The customer's configured week order is 3, the sorting method is sequential, and the week number is 1 or 2. Therefore, the customer's configured week numbers correspond to May 13th, May 14th, June 10th, and June 11th. Among these, June 10th and June 11th are after the initial payment date, and June 10th has the shortest time interval from the initial payment date; therefore, the payment date is June 10th.
[0093] For example, as above Figure 12 and above Figure 13 As shown, the initial payment date is May 20th, which is the Monday of the fourth week. The customer's configured week order is 4, sorted in reverse order, with weekdays being 2 and 5. Therefore, the customer's configured weekdays correspond to May 7th, May 10th, June 4th, and June 7th. Among these, June 4th and June 7th are after the initial payment date, and June 7th has the shortest time interval from the initial payment date; therefore, the payment date is June 7th.
[0094] The method provided in this application unifies the time units of the customer-configured payment period parameters and the start date or initial payment date, thereby determining the specific date corresponding to the customer-configured payment period parameters and ultimately determining the final payment period. This application embodiment takes into account the customer's actual situation when determining transaction-related payment periods, incorporating the customer-configured payment period parameters into the calculation, ensuring the effectiveness of the enterprise's payment period management.
[0095] In one embodiment, the payment term parameter configuration interface may further include a "prohibit payment date postponement" configuration item, which the customer can configure by checking "Yes" or "No". If the user checks "Yes", it indicates that the determined payment date needs to be postponed from the prohibited payment date; if the user does not check "Yes", it indicates that the determined payment date does not need to be postponed from the prohibited payment date. When the user checks "Yes", the final payment date is determined using methods such as... Figure 14 The steps shown are as follows: Step 601: Match the user's payment date with the preset list of prohibited payment dates.
[0096] Step 602: If there is a preset prohibited payment date in the preset prohibited payment date list that matches the user's payment date, then the user's payment date is corrected.
[0097] like Figure 15 As shown, the default payment prohibition date can be a statutory holiday. Figure 16 The image shows the statutory holidays in 2024.
[0098] The statutory holidays can be found in the configuration table shown in Table 6 below: Table 6
[0099] The system matches the user's payment date with a list of preset prohibited payment dates. If a date in the list of preset prohibited payment dates matches the user's payment date, the system iterates through each date after the payment date and matches it against the list of preset prohibited payment dates until a date does not match the list of preset prohibited payment dates. In this case, the user's payment date is replaced with that date.
[0100] For example, if a user's payment date falls on a statutory holiday, the first working day after the statutory holiday will be used to replace the user's payment date.
[0101] The method provided in this application embodiment can also modify the determined payment date based on a preset list of prohibited payment dates, so that the modified payment date is more reasonable and in line with the actual situation of the customer, and facilitates the company's payment period management.
[0102] In summary, the process for determining the payment terms related to a transaction is as follows: Figure 17 As shown, the start date for a transaction is determined based on the start date configured by the customer, the settlement date is determined based on the start date and settlement configuration parameters, the initial payment date is determined based on the settlement date and payment cycle, and the payment date is determined based on the initial payment date and payment configuration parameters. If the payment date falls on a statutory holiday, it will be postponed to the first working day after the statutory holiday.
[0103] like Figure 18 As shown, the transaction process is illustrated using an ERP system as an example: First, an interface for configuring payment terms is provided to the customer, receiving the payment term configuration parameters configured by the customer (i.e., maintaining configurations such as payment base type, base date, and priority in the diagram, creating a customer program, and maintaining customer payment term rules); then, a delivery note is generated based on the payment term configuration parameters (i.e., a delivery note program is created using the payment term rules of the customer to whom the sales order is delivered in the diagram); subsequently, as shown... Figure 19 The accounting voucher shown (i.e., the procedure for creating an invoice voucher in the diagram) displays the starting date; finally, the settlement date and payment date are calculated sequentially based on the starting date in the voucher (i.e., the due date is calculated based on the base date and payment period rules in the diagram).
[0104] like Figure 20 As shown, the system provides a payment terms management interface. During a transaction, after the ERP system generates accounting vouchers, the customer can modify the payment terms configuration parameters in the "Update Delivery Note Payment Rules" window of the payment terms management interface. For example, the weekly payment configuration parameter can be changed to a monthly configuration. The ERP system will update the payment terms configuration parameters to the delivery note, recalculate the payment terms based on the modified parameters, and update the accounting vouchers accordingly. Figure 18 In the process of modifying the customer program and the payment terms rules, the payment terms management program will synchronize and update the customer's payment terms rules to the delivery note payment rules and update the payment base date of the accounting vouchers.
[0105] Customers can also directly modify the start date in the application and approval window of the payment period management interface, and fill in the following information: Figure 21 The baseline date anomaly maintenance application approval form shown is processed by the ERP system. After approval, the settlement date and payment date are re-determined based on the modified start date and updated to the accounting voucher (i.e., ...). Figure 18 The mid-term accounting management program includes manual modification of the base date, application and approval forms for base date anomalies, and updating of the payment base date on accounting vouchers.
[0106] It should be noted that although the operations of the method of the present invention are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. On the contrary, the steps depicted in the flowchart may be performed in a different order. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.
[0107] In one embodiment, such as Figure 22 As shown, a payment term determination device is provided, which includes: a receiving module 701 and a determining module 702, wherein: The receiving module 701 is used to receive the user's operation on the billing period configuration interface and obtain the billing period configuration parameters. The billing period configuration parameters include the start date selected by the user, settlement configuration parameters, and payment configuration parameters. The settlement configuration parameters are used to represent the settlement date and / or settlement date rules, and the payment configuration parameters are used to represent the payment date and / or payment date rules.
[0108] The determination module 702 is used to determine the user's start date, settlement date, and payment date based on the start date, settlement configuration parameters, and payment configuration parameters.
[0109] In one embodiment, the determining module 702 is specifically used to determine the settlement date represented by the settlement configuration parameters that is after the start date and has the shortest interval with the start date as the user's settlement date; determine the initial payment date based on the settlement date and payment cycle; and determine the payment date represented by the payment configuration parameters that is after the initial payment date and has the shortest interval with the initial payment date as the user's payment date.
[0110] In one embodiment, the payment period determination device further includes a configuration parameter determination module 703, which is used to determine the settlement date represented by the settlement configuration parameters based on the settlement date rules and the start date represented by the settlement configuration parameters; and to determine the payment date represented by the payment configuration parameters based on the payment date rules and the initial payment date represented by the payment configuration parameters.
[0111] In one embodiment, the configuration parameter determination module 703 is specifically used to convert the start date according to the time unit corresponding to the settlement date rule; the time unit includes at least one of weekday and date; determine the time interval between the start date and the settlement date according to the start date after the time unit conversion; and determine the settlement date represented by the settlement configuration parameter according to the start date and the time interval between the start date and the settlement date.
[0112] In one embodiment, the configuration parameter determination module 703 is specifically used to convert the initial payment date according to the time unit corresponding to the payment date rule; the time unit includes at least one of weekday and date; determine the time interval between the initial payment date and the payment date according to the initial payment date after the time unit conversion; and determine the payment date represented by the payment configuration parameter according to the initial payment date and the time interval between the initial payment date and the payment date.
[0113] In one embodiment, the payment period determination device further includes a matching module 704, which is used to match the user's payment date with a preset list of prohibited payment dates; if there is a preset prohibited payment date in the list of prohibited payment dates that matches the user's payment date, then the user's payment date is corrected.
[0114] In one embodiment, the payment period determination device further includes a management module 705 that manages the user's transactions based on the user's start date, settlement date, and payment date.
[0115] In one embodiment, the payment period configuration interface includes a start date configuration item, a settlement date configuration item, a payment cycle configuration item, and a payment date configuration item; the start date configuration item includes a start date configuration item and a start date type configuration item, the settlement date configuration item includes a settlement date configuration item and a settlement date rule configuration item, and the payment date configuration item includes a payment date configuration item and a payment date rule configuration item.
[0116] It should be understood that the units or modules recorded in the payment term determination device are related to the reference. Figure 1 The steps in the described method correspond to each other. Therefore, the operations and features described above for the method also apply to the payment term determination device and the units contained therein, and will not be repeated here. The payment term determination device can be pre-implemented in the browser or other security applications of an electronic device, or it can be loaded into the browser or other security applications of an electronic device through download or other means. The corresponding units in the payment term determination device can cooperate with the units in the electronic device to implement the solutions of the embodiments of this application.
[0117] The following is for reference. Figure 23 It shows a schematic diagram of the structure of a computer system 800 suitable for implementing terminal devices or servers in the embodiments of this application.
[0118] like Figure 23As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 802 or programs loaded from storage section 808 into random access memory (RAM) 803. The RAM 803 also stores various programs and data required for the operation of the system 800. The CPU 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.
[0119] The following components are connected to I / O interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to I / O interface 805 as needed. A removable medium 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 810 as needed so that computer programs read from it can be installed into storage section 808 as needed.
[0120] In particular, according to embodiments of this disclosure, the above references Figure 1 The described process can be implemented as a computer software program. For example, embodiments of this disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program containing instructions for performing... Figure 1 The program code for the method. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 809, and / or installed from removable media 811.
[0121] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0122] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0123] The units or modules described in the embodiments of this application can be implemented in software or hardware. The described units or modules can also be located in a processor. The names of these units or modules do not, in certain circumstances, constitute a limitation on the unit or module itself.
[0124] On the other hand, this application also provides a computer-readable storage medium, which may be included in the computer device described in the above embodiments, or may exist independently and not assembled into the computer device. The aforementioned computer-readable storage medium stores one or more programs that, when used by one or more processors, execute the methods described in this application. For example, it may execute... Figure 1 The steps of the method shown.
[0125] This application provides a computer program product including instructions that, when executed, cause the method described in this application to be performed. For example, it can execute... Figure 1 The steps of the method shown are as follows.
[0126] Those skilled in the art will understand that all or part of the processes in 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 described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0127] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the inventive concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.
Claims
1. A method of determining a billing period, characterized by, The method comprises: receiving user operation on a billing period configuration interface to obtain billing period configuration parameters; the billing period configuration parameters comprise a selected starting date, settlement configuration parameters and payment configuration parameters by the user; the settlement configuration parameters are used to represent a settlement date and / or a settlement date rule, and the payment configuration parameters are used to represent a payment date and / or a payment date rule; determining the starting date, settlement date and payment date of the user according to the starting date, settlement configuration parameters and payment configuration parameters.
2. The method of claim 1, wherein, The determination of the starting date, settlement date and payment date of the user according to the starting date, settlement configuration parameters and payment configuration parameters comprises: determining the settlement date that is the shortest interval from the starting date among the settlement dates represented by the settlement configuration parameters as the settlement date of the user; determining an initial payment date based on the settlement date and a payment period; determining the payment date that is the shortest interval from the initial payment date among the payment dates represented by the payment configuration parameters as the payment date of the user.
3. The method of claim 2, wherein, The method further comprises: determining the settlement dates represented by the settlement configuration parameters based on the settlement date rule represented by the settlement configuration parameters and the starting date; determining the payment dates represented by the payment configuration parameters based on the payment date rule represented by the payment configuration parameters and the initial payment date.
4. The method of claim 3, wherein, The determination of the settlement dates represented by the settlement configuration parameters based on the settlement date rule represented by the settlement configuration parameters and the starting date comprises: converting the starting date according to a time unit corresponding to the settlement date rule; the time unit comprises at least one of a week and a date; determining a time interval between the starting date and the settlement date after the conversion of the starting date according to the time unit; determining the settlement dates represented by the settlement configuration parameters according to the starting date and the time interval between the starting date and the settlement date.
5. The method of claim 3, wherein, The determination of the payment dates represented by the payment configuration parameters based on the payment date rule represented by the payment configuration parameters and the initial payment date comprises: converting the initial payment date according to a time unit corresponding to the payment date rule; the time unit comprises at least one of a week and a date; determining a time interval between the initial payment date and the payment date after the conversion of the initial payment date according to the time unit; determining the payment dates represented by the payment configuration parameters according to the initial payment date and the time interval between the initial payment date and the payment date.
6. The method of claim 1, wherein, The method further comprises: matching the payment date of the user with a preset prohibited payment date list; if there is a preset prohibited payment date in the preset prohibited payment date list that matches the payment date of the user, the payment date of the user is corrected.
7. The method of claim 1, wherein, The method further comprises: managing the transaction of the user based on the starting date, settlement date and payment date of the user.
8. The method of claim 1, wherein, The account period configuration interface comprises a starting date configuration item, a settlement date configuration item, a payment period configuration item and a payment date configuration item; the starting date configuration item comprises a starting date configuration item and a starting date type configuration item, the settlement date configuration item comprises a settlement date configuration item and a settlement date rule configuration item, and the payment date configuration item comprises a payment date configuration item and a payment date rule configuration item.
9. An accounting period determination apparatus characterized by comprising: The device comprises: a receiving module configured to receive an operation of a user on an account period configuration interface and acquire account period configuration parameters; the account period configuration parameters comprise a starting date selected by the user, settlement configuration parameters and payment configuration parameters; the settlement configuration parameters are used to represent a settlement date and / or a settlement date rule, and the payment configuration parameters are used to represent a payment date and / or a payment date rule; a determining module configured to determine a starting date, a settlement date and a payment date of the user according to the starting date, the settlement configuration parameters and the payment configuration parameters. 10.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-9. The processor executes the computer program to implement the steps of the method in any one of claims 1 to 8.
11. A computer readable storage medium having stored thereon a computer program, characterized in that The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 8.
12. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 8.