Contract payment reminding method and device, equipment and storage medium

Abstract

The invention discloses a contract payment reminding method, device and equipment and a storage medium, relates to the technical field of data processing, and discloses a contract payment reminding method which comprises the following steps: receiving a payment strategy created by a collection user based on a transaction mode in a contract; according to the payment strategy, dividing different transaction modes for contract information input by a collection user based on a contract, and obtaining periodic sub-contracts representing different transaction modes; and performing task division on the period sub-contract based on a preset payment period, and generating a payment task for reminding a payment user recorded in the contract to perform payment. Namely, the contract is divided according to the transaction mode according to the payment strategy so as to reduce the contract management complexity, and then task division is performed on the divided period sub-contracts according to the preset payment period so as to generate the reminding task for reminding the payment user, so that the payment user can be timely and actively reminded of payment through the payment task. And the timeliness of reminding the payment user is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a contract payment reminder method, device, equipment and storage medium. Background Art

[0002] In order to protect one's own rights, when reaching a monetary agreement with others, a rental contract is usually signed to constrain it.

[0003] Due to the differences in payment cycles and payment methods, contracts can be divided into different types of rental contracts, and there can be multiple payment cycles or payment methods in a contract. When managing the contract, it is necessary to remind the payee in the contract to pay on time during each payment cycle to ensure that the agreement continues. However, due to the rich and complex types of contracts, each contract requires the payee in the contract to spend a lot of energy and manpower costs to manage in order to remind the payee to pay the rent on time. When the contract that the payee needs to handle is too complicated, it is easy to miss or misread the reminder time for the payee, resulting in untimely reminders to the payee, which in turn leads to reduced timeliness of reminders to the payee.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a contract payment reminder method, which aims to solve the technical problem that it is easy to cause untimely reminders to users who make payments, thereby reducing the timeliness of reminders to users who make payments.

[0006] To achieve the above purpose, this application proposes a contract payment reminder method, which includes:

[0007] Receive the payment strategy created by the recipient based on the transaction method in the contract;

[0008] According to the payment strategy, the contract information input by the payment recipient based on the contract is divided into different transaction modes to obtain periodic sub-contracts representing different transaction modes;

[0009] The periodic sub-contract is divided into tasks based on a preset payment cycle, and a payment task is generated for reminding the payment user recorded in the contract to make the payment.

[0010] In one embodiment, the step of dividing the contract information input by the payee based on the contract into different transaction modes according to the payment strategy, and obtaining periodic sub-contracts representing different transaction modes includes:

[0011] Identify the period fields for dividing the contract information from the payment strategy, the contract information being the information input by the payment recipient according to the corresponding period fields;

[0012] Based on the period field, identifying the billing method and payment method of the corresponding period from the contract information;

[0013] A contract transaction method based on the billing method and the payment method forming a corresponding cycle;

[0014] According to the contract transaction mode and the payment strategy, the contract information is divided into different transaction modes according to the period field to obtain periodic sub-contracts representing different transaction modes.

[0015] In one embodiment, the step of identifying the billing method and payment method of the corresponding period from the contract information based on the period field includes:

[0016] identifying a corresponding time field in the contract information based on the period field;

[0017] Based on a preset first position relationship, identifying a billing character representing a billing method in each period from the contract information, the preset first position relationship being a position relationship between the time character and the billing character;

[0018] Based on a preset second position relationship, identifying the payment characters representing the payment method in each period from the contract information, the preset second position relationship being the position relationship between the time field and the payment characters;

[0019] The billing method selected in the corresponding period is filtered from the contract information based on the billing characters, and the payment method selected in the corresponding period is filtered from the contract information based on the payment characters.

[0020] In one embodiment, the step of identifying the period fields for dividing the contract information from the payment strategy includes:

[0021] Identify time characters from the payment strategy and read context information of each time character;

[0022] Based on the context information, selecting a period node representing a period from the time characters;

[0023] Based on the periodic nodes, periodic fields for dividing the contract information are identified.

[0024] In one embodiment, the step of dividing the periodic sub-contract into tasks based on the preset payment cycle and generating a payment task for reminding the payment user recorded in the contract to make payment includes:

[0025] Identifying the start time of the corresponding period from the periodic sub-contract;

[0026] Taking the preset payment time as the time interval, dividing the periodic sub-contract into tasks according to the start time, and determining the time frame of each payment task to be generated;

[0027] Based on the time frame, read the target billing method and target payment method corresponding to the current period from the periodic sub-contract, and obtain the target payment amount within the time frame;

[0028] Based on the time frame, the target billing method, the target payment method and the target payment amount, a payment task is generated to remind the payment user recorded in the contract to make the payment.

[0029] In one embodiment, the step of obtaining the target payment amount within each time frame includes:

[0030] Determine the target billing method for each payment task within the time frame at the corresponding reminder time point;

[0031] Based on the target billing method, a target payment amount within the preset payment time is determined.

[0032] In addition, to achieve the above purpose, the present application also proposes a contract payment reminder device, which includes:

[0033] The receiving module is used to receive the payment strategy created by the payee based on the transaction method in the contract;

[0034] A contract division module, used to divide the contract information input by the payment recipient based on the contract into different transaction modes according to the payment strategy, and obtain periodic sub-contracts representing different transaction modes;

[0035] The task generation module is used to divide the tasks of the periodic sub-contract based on the preset payment cycle, and generate payment tasks for reminding the payment users recorded in the contract to make payments.

[0036] In addition, to achieve the above-mentioned purpose, the present application also proposes a contract payment reminder device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the contract payment reminder method as described above.

[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the contract payment reminder method described above are implemented.

[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the contract payment reminder method as described above.

[0039] One or more technical solutions proposed in this application have at least the following technical effects:

[0040] Since a contract may contain multiple transaction methods, the payee can create a payment strategy based on the transaction methods in the contract. In order to reduce the complexity of the contract information input by the payee based on the contract, after the operating platform receives the payment strategy uploaded by the payee, it can divide the contract information into different transaction methods according to the payment strategy, obtain periodic sub-contracts representing different transaction methods, and further manage the periodic sub-contracts of the same transaction method, thereby reducing the complexity of contract management and the error rate of contract management. By dividing the periodic sub-contracts into different payment tasks according to the preset payment cycle, the payee recorded in the contract is actively reminded to pay within each preset payment cycle through the payment task, thereby avoiding the failure to remind the payee to pay rent in time due to the large number of contracts that the payee needs to handle or the relatively complex contracts, thereby improving the timeliness of reminders to the payee. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0042] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0043] Figure 1 A flowchart of the first embodiment of the method for reminding payment of a contract application;

[0044] Figure 2 A brief flowchart of the contract payment reminder method provided in Example 1 of the present application;

[0045] Figure 3 A flowchart of the second embodiment of the method for reminding the payment of a contract for this application;

[0046] Figure 4 A schematic diagram of a brief flow of the payment strategy configuration provided in Example 2 of the present application;

[0047] Figure 5 A flowchart of the third embodiment of the method for reminding payment of a contract for this application;

[0048] Figure 6 A schematic diagram of a brief process for automatically generating a payment task provided in Example 3 of the present application;

[0049] Figure 7 This is a schematic diagram of the module structure of the contract payment reminder device according to an embodiment of the present application;

[0050] Figure 8 This is a schematic diagram of the device structure of the hardware operating environment involved in the contract payment reminder method in the embodiment of the present application.

[0051] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0052] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0053] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0054] The main solution of the embodiment of the present application is: the contract management operation platform receives the payment strategy created by the payment user based on the transaction method in the contract; according to the payment strategy, the contract information input by the payment user based on the contract is divided into different transaction methods to obtain periodic sub-contracts representing different transaction methods; the periodic sub-contracts are divided into tasks based on the preset payment cycle, and a payment task is generated to remind the payment user recorded in the contract to make the payment.

[0055] In this embodiment, for ease of description, the following description is made with the contract management operation platform as the execution entity.

[0056] Due to the differences in payment cycles and payment methods in the prior art, contracts can be divided into different types of rental contracts, and there can be multiple payment cycles or payment methods in a contract. When managing the contract, it is necessary to remind the payee in the contract to pay on time during each payment cycle to ensure that the agreement continues. However, due to the rich and complex types of contracts, each contract requires the payee in the contract to spend a lot of energy and manpower costs to manage in order to remind the payee to pay the rent on time. When the contract that the payee needs to handle is too complicated, it is easy to miss or misread the reminder time for the payee, resulting in untimely reminders to the payee, which in turn reduces the timeliness of reminders to the payee.

[0057] The present application provides a solution. Since a contract may contain multiple transaction methods, the payee can create a payment strategy based on the transaction methods in the contract. In order to reduce the complexity of the contract information input by the payee based on the contract, after the operation platform receives the payment strategy uploaded by the payee, the contract information can be divided into different transaction methods according to the payment strategy, and periodic sub-contracts representing different transaction methods can be obtained. The periodic sub-contracts of the same transaction method are further managed, thereby reducing the complexity of contract management and the error rate of contract management. By dividing the periodic sub-contracts into different payment tasks according to the preset payment cycle, the payee recorded in the contract is actively reminded to pay the money through the payment tasks within each preset payment cycle, thereby avoiding the failure to remind the payee to pay the rent in time because the payee needs to handle more contracts or the contracts are more complicated, thereby improving the timeliness of reminding the payee.

[0058] It should be noted that the execution subject of this embodiment may be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, an operating platform for contract management, etc. The following takes the operating platform for contract management as an example to illustrate this embodiment and the following embodiments.

[0059] Based on this, the present application embodiment provides a contract payment reminder method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the contract payment reminder method for this application.

[0060] In this embodiment, the contract payment reminder method includes steps S10 to S30:

[0061] Step S10, receiving a payment strategy created by the payee based on the transaction method in the contract;

[0062] It should be noted that the payment recipient may be the user recorded in the contract for receiving payment. For example, if the contract is a rental contract, the landlord recorded in the rental contract is the payment recipient. If the contract is a venue rental contract, the lessor user in the venue rental contract is the payment recipient. The payment strategy may be a specific transaction method determined based on the information in the contract and the period of the sub-contracts that divide the contract. The transaction method may be a combination of the billing method and the payment method in each periodic sub-contract.

[0063] It is understandable that since the transaction method in the contract may be more complicated, in order to simplify the difficulty of contract management, the receiving user determines the payment strategy for dividing the received contract information based on the content of the contract, so as to simplify the contract according to the payment strategy and reduce the difficulty of contract management.

[0064] In the specific implementation, the payment receiving user can upload the contract to be managed through the OA (Office Automation) system connected to the contract management operation platform, so that the contract management operation platform can obtain the contract information in the contract. The payment receiving user can also create a payment strategy through the OA system, and the OA system uploads the payment strategy to the contract management operation platform. The payment receiving user can also upload the payment strategy to the contract management operation platform to avoid errors during the transmission process.

[0065] Step S20, according to the payment strategy, the contract information input by the payment recipient based on the contract is divided into different transaction modes to obtain periodic sub-contracts representing different transaction modes;

[0066] It should be noted that the periodic sub-contract can be a sub-contract divided according to different transaction methods and in chronological order, that is, the transaction method in each periodic sub-contract is the same.

[0067] It is understandable that due to different times within the contract, the billing method and payment method of the collection may be different. When managing such a contract, it is necessary to determine the billing method and payment method within the current time period each time, and frequently change the management method of the contract, which in turn causes labor costs for managing such contracts. If the contract is to be managed automatically, it is necessary to increase the computing power required for management, and as the computing power increases, it will also lead to errors in the final management. In order to reduce labor costs and the difficulty of managing the contract, the contract can be divided into multiple periodic sub-contracts according to different transaction methods based on the payment strategy, and the transaction method in each period of the contract is the same. When managing each periodic sub-contract, there is no need to frequently change the reminder task for the payment user according to the transaction method, and the difficulty of managing the contract is reduced.

[0068] Step S30, dividing the periodic sub-contract into tasks based on the preset payment cycle, and generating a payment task for reminding the payment user recorded in the contract to make payment.

[0069] It should be noted that the preset payment cycle can be the time difference between two consecutive payments. Since payments are collected at an agreed period, there is generally a fixed time difference between adjacent payments, such as one month, three months or six months. A payment task can be a reminder instruction to remind the payment user to make a payment. The payment task should include the specific billing method, payment method, payment amount and details of the payment amount.

[0070] It is understandable that in order to realize automatic and regular reminders to the user who is making payment, it is necessary to remind the user of the required payment task each time, so as to remind the user to make payment regularly according to the payment task. This avoids the situation where the user who receives payment forgets to remind the user who makes payment, causing the user who makes payment to delay the payment and cause the user to breach the contract. Therefore, the timeliness of reminders to the user who makes payment is improved.

[0071] In the specific implementation, the time required for each payment is calculated based on the filled-in contract information, and the payee is reminded to confirm the operation. The current payment task is also generated based on the payment strategy. The payee can also open the task to recheck the converted payment amount and other data, and can also supplement some information to generate a payment task based on the payment amount verified by the payee and the supplemented information, so that the payee can clearly know the details of the payment required.

[0072] This embodiment provides a contract payment reminder method. Since a contract may contain multiple transaction methods, the payee can create a payment strategy based on the transaction methods in the contract. In order to reduce the complexity of the contract information input by the payee based on the contract, after the operation platform receives the payment strategy uploaded by the payee, the contract information can be divided into different transaction methods according to the payment strategy to obtain periodic sub-contracts representing different transaction methods, and then the periodic sub-contracts with the same transaction method are further managed, thereby reducing the complexity of contract management and the error rate of contract management. By dividing the periodic sub-contracts into different payment tasks according to the preset payment cycle, the payee recorded in the contract is actively reminded to pay within each preset payment cycle through the payment task, thereby avoiding the failure to remind the payee to pay rent in time because the payee needs to handle more contracts or the contracts are more complicated, thereby improving the timeliness of reminding the payee.

[0073] For example, in order to help understand the implementation process of the contract payment reminder method obtained by combining this embodiment with the above-mentioned embodiment 1, the leasing of a charging pile station is used as an example for explanation. Please refer to Figure 2 , Figure 2 A brief flowchart of a contract payment reminder method is provided, specifically:

[0074] The station manager (payee) creates a lease contract for the station through the OA system. After the lease contract is approved, it is stored in the OA system. Since the lease contract is only stored in the OA system and not classified, in order to enable the back-end operation system (contract management operation platform) to remind the payee according to the contract content, the station manager is also required to create a rent payment strategy based on the transaction method in the contract, and send the payment strategy to the back-end operation system to facilitate the back-end operation system to obtain the contract information of the lease contract from the OA system according to the payment strategy, divide the contract information according to different transaction methods according to the payment strategy, obtain the periodic sub-contracts representing different transaction methods, and then classify them according to the periodic sub-contracts. The sub-contract creates payment tasks according to the cycle rules (preset payment cycle), and the contract information can also be displayed through the OA system. The site manager confirms the amount of this payment and can also supplement the bidding information. After the back-end operation system receives the confirmation instructions and supplementary information from the site manager, it reminds the payment user to make the payment according to the payment task. After the payment is completed, the task status of the payment task is changed from payment to payment completion. Similarly, there is no need for manual self-reminders for each subsequent task. The task will be automatically generated and the message center will actively remind and inform. After the notification, the manual confirmation and supplement will be carried out. After the task is submitted, the OA work order will be generated and sent to the OA. There is no need for manual intervention by the site manager thereafter.

[0075] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 3 , step S20 also includes steps S21 to S24:

[0076] Step S21, identifying the period fields for dividing the contract information from the payment strategy, the contract information being the information input by the payment recipient according to the corresponding period fields;

[0077] It should be noted that the period field can be a simple field set through a survey of the payee and a survey of the OA system on the content required for a payment, so that both the payee and the OA system can identify the content of the payment strategy.

[0078] It is understandable that although the existing intelligent model structure or AI technology is already very sophisticated, errors will occur more or less during use, and some template information in the contract will also interfere with the accurate identification of useful information from the contract. Therefore, the information of the period field in the corresponding payment strategy in the contract can be filtered out by the receiving user, thereby improving the completeness and accuracy of the contract information obtained.

[0079] In the specific implementation, the corresponding information in the contract can be filled into the OA system through the prompt of useful information in the OA system. After the contract information of the contract is uploaded through the OA system, the contract information can be divided according to the period field.

[0080] Step S22, based on the period field, identifying the billing method and payment method of the corresponding period from the contract information;

[0081] It should be noted that the billing method can be a fixed monthly rent or a proportional share of the station service fee, etc. The payment method can be prepayment, invoice first and payment later, etc.

[0082] It is understandable that since all transaction methods are based on a combination of billing methods and payment methods, the periods to be divided are determined from the contract information based on the period field, and then the billing method and payment method of the period are identified from the contract information corresponding to each period, so as to simplify the complexity of contract management based on the billing method and payment method, so that there is only one payment method in each period sub-contract, and there is only one corresponding billing method.

[0083] It is understandable that by dividing the contract information within the same billing method and payment method period into the same period sub-contract according to the period field, the difficulty of calculating the payment amount can be reduced, thereby improving the accuracy of the payment amount in the payment task and speeding up the calculation of the payment amount.

[0084] Step S23, forming a contract transaction method of a corresponding period based on the billing method and the payment method;

[0085] It should be noted that the contract transaction method can be a transaction method consisting of a billing method and a payment method identified from the contract information.

[0086] It can be immediately noted that, since recognition errors may occur when dividing the contract information according to the cycle field in the payment strategy, and the payment strategy also includes the transaction method, that is, the strategic transaction method, in order to avoid errors in the billing method and charging method identified from the contract information, it is necessary to compare the contract transaction method with the strategic transaction method in the payment strategy to improve the accuracy of the billing method and payment method.

[0087] Step S24, according to the contract transaction mode and the payment strategy, the contract information is divided into different transaction modes according to the period field to obtain period sub-contracts representing different transaction modes.

[0088] It can be understood that by dividing the contract information according to the transaction method, a periodic sub-contract containing only one transaction method is obtained, thereby reducing the difficulty of calculating the amount of payment each time the payment is collected, thereby reducing the error caused by complex calculations, and thus improving the accuracy of the amount of payment recorded in the payment task each time the payment is collected.

[0089] Furthermore, step S22 may also include:

[0090] identifying a corresponding time field in the contract information based on the period field;

[0091] Based on a preset first position relationship, identifying a billing character representing a billing method in each period from the contract information, the preset first position relationship being a position relationship between the time character and the billing character;

[0092] Based on a preset second position relationship, identifying the payment characters representing the payment method in each period from the contract information, the preset second position relationship being the position relationship between the time field and the payment characters;

[0093] The billing method selected in the corresponding period is filtered from the contract information based on the billing characters, and the payment method selected in the corresponding period is filtered from the contract information based on the payment characters.

[0094] It should be noted that the time field can be a character representing time, which is used to accurately obtain time information from a large number of data characters through this character. The first positional relationship can be the positional relationship between the time character in the contract information and the character for the user to identify the billing method, so that after determining the time character, the billing method in the contract information can be quickly determined from the contract information. The second positional relationship can be the positional relationship between the time character in the contract information and the character for the user to identify the payment method, so that after determining the time character, the payment method in the contract information can be quickly determined from the contract information.

[0095] It is understandable that since there are a large number of character strings in the contract information, in order to quickly extract the data required to generate the payment task from the contract information, and the positional relationship between the character strings of each information in the contract information is also within a certain range, therefore, after identifying the time field corresponding to the time point of the period field from the corresponding time field in the contract information, the billing characters and the payment characters are obtained respectively according to the corresponding positional relationship, which can shorten the time for identifying the billing characters and the payment characters, thereby improving the efficiency of determining the payment task, avoiding the untimely reminder of the payment user in an emergency, and thereby improving the timeliness of the reminder to the payment user.

[0096] Furthermore, step S21 further includes:

[0097] Identify time characters from the payment strategy and read context information of each time character;

[0098] Based on the context information, selecting a period node representing a period from the time characters;

[0099] Based on the periodic nodes, periodic fields for dividing the contract information are identified.

[0100] It should be noted that the context information can be information represented by the context characters of the time characters, wherein the context information of the time characters can be read by a neural network model or a large model that can analyze the context information, or a machine learning model to improve the accuracy of obtaining the context information. The cycle node can be the starting time point and the ending time point of a cycle, so that a cycle is formed by the starting time point and the ending time point.

[0101] It is understandable that since the payment strategy may contain other time characters, such as the creation date of the payment strategy, in order to avoid the impact of such time on the division of contract information, it is necessary to identify the time characters in the payment strategy and read the context information of each time character from the payment strategy, so as to accurately determine the start and end time points of the representation period through the context information, thereby improving the accuracy of contract information division and accurately identifying the periodic sub-contracts corresponding to each transaction method.

[0102] For example, in order to help understand the implementation process of the contract payment reminder method obtained by combining this embodiment with the above embodiments, please refer to Figure 4 , Figure 4 A brief flowchart of payment strategy configuration is provided, specifically:

[0103] The contract period is generally long, 5-10 years. When signing a contract, different rents may be charged in different periods. Therefore, when configuring a new payment strategy, you can select the start and end time in the period field to divide the contract into periods. The division of the contract periods can be based on the time sequence and the billing method. For example, the billing method corresponding to period one is fixed rent, the billing method corresponding to period two is service fee sharing, and so on. The billing method corresponding to period N is configured for all periods of the entire payment strategy, such as invoice first and payment later and prepayment. In order to receive the rental payment from the payment user on time, it is also necessary to determine the settlement period (preset payment period) according to the period rules in the contract. In order to remind the payment user to pay on time and avoid default by the payment user, it is also necessary to configure the time of each payment, that is, the number of days in advance for each period, and other required fields.

[0104] Among them, the fixed rent is similar to renting a parking space in life, and the number and unit price of charging parking spaces and equipment parking spaces can be filled in. The service fee sharing is calculated by calculating the total service fee of the station revenue within the settlement period, and allocating it to the station in proportion. Ticket first, then payment means consumption first and then payment. The venue is rented first. After the venue provides the bill to the person in charge of the station, the person in charge will make the payment. The advance payment means prepaying the rent for the next task before using the station. The settlement cycle can be monthly, quarterly, annual payment, etc. The number of days in advance for each period is to generate and remind the person in charge of the station that the next period of tasks has been generated in advance, and some information needs to be prepared in advance, and it can also allow OA work orders to be submitted in time to avoid breach of contract.

[0105] Based on the first and second embodiments of the present application, in the third embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be described in detail later. Figure 5 , step S30 also includes steps S1 to S4:

[0106] Step S1, identifying the start time of the corresponding period from the periodic sub-contract;

[0107] Step S2, taking the preset payment time as the time interval, dividing the periodic sub-contract into tasks according to the start time, and determining the time frame of each payment task to be generated;

[0108] Step S3, based on the time frame, read the target billing method and target payment method corresponding to the current period from the periodic sub-contract, and obtain the target payment amount within the time frame;

[0109] Step S4, based on the time frame, the target billing method, the target payment method and the target payment amount, generating a payment task for reminding the payment user recorded in the contract to make payment.

[0110] It should be noted that the preset payment time can be the time interval for executing the payment task, that is, the time interval for reminding the payment user to make the payment. The start time can be the start time of the periodic sub-contract. Since the contents of adjacent periodic sub-contracts are the same, the start time of the current periodic sub-contract is the end time of the previous periodic sub-contract, and the end time of the current periodic sub-contract is the start time of the next periodic sub-contract. The time frame can be the time point when each payment task needs to be executed after the periodic sub-contract is divided into tasks. The target billing method can be the billing method recorded in the previous periodic sub-contract. The target payment method can be the payment method recorded in the current periodic sub-contract. The target payment amount can be the payment amount that the user needs to be reminded to make the payment in the current period.

[0111] It can be understood that by determining the time frame of each payment task, the target payment amount that the paying user needs to pay to the receiving user can be accurately determined before each time point when the paying user needs to be reminded to make the payment, and the paying user can be reminded on time at the time point when the paying user needs to be reminded to make the payment, thereby avoiding the need for manual intervention to complete the timely payment of rent, and thus solving the technical problem of untimely submission of payment applications due to manual rent management. That is, the technical effect of improving the timeliness of reminders to paying users is achieved.

[0112] It is understandable that by automatically generating payment tasks and reminding users to pay on time at the corresponding time points, it can also avoid overdue payments caused by abnormal payment management and negative online user experience, thereby reducing asset losses and lowering the rate of manual errors.

[0113] Furthermore, step S30 may also include:

[0114] Determine the target billing method for each payment task within the time frame at the corresponding reminder time point;

[0115] Based on the target billing method, a target payment amount within the preset payment time is determined.

[0116] It can be understood that by determining the target billing method in each periodic sub-contract in the time frame, and then selecting the target billing method when calculating the target payment amount, it is possible to flexibly calculate the target payment amount that the user who needs to pay the payee needs to pay during the corresponding periodic sub-contract according to the billing method in the periodic sub-contract.

[0117] For example, in order to help understand the implementation process of the contract payment reminder method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 6 , Figure 6 A brief flowchart of the automatic generation of payment tasks is provided, specifically:

[0118] According to the time field of cycle m divided according to the payment method in the payment strategy, and the payment cycle (settlement cycle X months), a payment task is generated, that is, task one (cycle m start time ~ cycle m start time + X months), task two (task one end time + 1 day ~ task one end time + X months + 1 day), ..., task n (task n-1 end time + 1 day ~ task n-1 end time + X months + 1 day). After the execution time period of each payment task determined above, the billing method of each payment task is determined according to the payment method in the payment strategy, so as to calculate the amount involved in each payment task according to the billing method. For example, if the billing method is fixed rent, the calculation method of the amount involved in the corresponding payment task is: charging parking space * single Price (yuan / month)*X+equipment parking space*unit price (yuan / month)*X; if the billing method is service fee sharing, the calculation method of the amount involved in the corresponding payment task is: the total service fee earned by the station during the task time period*sharing ratio, and then determine the payment method of each payment task, and determine the sending time of the payment task based on the number of days y in advance for each period in the payment strategy. Due to different payment methods, the sending time of the payment task is also different. Among them, the sending time of the ticket first and the payment later is calculated as follows: the end time of each task - y days to generate the current task of the past month; the sending time of the advance payment is calculated as follows: the start time of each task - y days to generate the current task of the future month, and finally, according to the logic of each payment task, the rent and other information are automatically filled in to generate a reminder message for the payment.

[0119] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the contract payment reminder method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0120] This application also provides a contract payment reminder device, please refer to Figure 7 The contract payment reminder device includes:

[0121] Receiving module 10, used for receiving the payment strategy created by the payment recipient based on the transaction method in the contract;

[0122] The contract division module 20 is used to divide the contract information input by the payment user based on the contract into different transaction modes according to the payment strategy, and obtain periodic sub-contracts representing different transaction modes;

[0123] The task generation module 30 is used to divide the periodic sub-contract into tasks based on a preset payment cycle, and generate a payment task for reminding the payment user recorded in the contract to make payment.

[0124] Optionally, the contract division module 20 is further used to identify the period field for dividing the contract information from the payment strategy, the contract information being the information input by the payee according to the corresponding period field; based on the period field, identifying the billing method and payment method of the corresponding period from the contract information; forming a contract transaction method of the corresponding period based on the billing method and the payment method; and according to the contract transaction method and the payment strategy, dividing the contract information into different transaction methods according to the period field to obtain period sub-contracts representing different transaction methods.

[0125] Optionally, the contract division module 20 is also used to identify the corresponding time field in the contract information based on the period field; based on a preset first position relationship, identify the billing characters representing the billing method in each period from the contract information, and the preset first position relationship is the position relationship between the time character and the billing character; based on a preset second position relationship, identify the payment characters representing the payment method in each period from the contract information, and the preset second position relationship is the position relationship between the time field and the payment character; based on the billing character, filter the billing method selected in the corresponding period from the contract information, and based on the payment character, filter the payment method selected in the corresponding period from the contract information.

[0126] Optionally, the contract division module 20 is also used to identify time characters from the payment strategy and read the context information of each time character; based on the context information, filter the period nodes representing the period from the time characters; based on the period nodes, identify the period fields for dividing the contract information.

[0127] Optionally, the task generation module 30 is further used to identify the start time of the corresponding cycle from the periodic sub-contract; divide the tasks of the periodic sub-contract according to the start time with the preset payment time as the time interval, and determine the time frame of each payment task to be generated; based on the time frame, read the target billing method and target payment method corresponding to the current cycle from the periodic sub-contract, and obtain the target payment amount within the time frame; based on the time frame, the target billing method, the target payment method and the target payment amount, generate a payment task for reminding the payment user recorded in the contract to make the payment.

[0128] Optionally, the task generation module 30 is also used to determine the target billing method at the reminder time point corresponding to each payment task within the time frame; based on the target billing method, determine the target payment amount within the preset payment time.

[0129] The contract payment reminder device provided by the present application adopts the contract payment reminder method in the above embodiment, which can solve the technical problem that it is easy to cause the reminder of the payment user to be delayed, thereby reducing the timeliness of the reminder to the payment user. Compared with the prior art, the beneficial effects of the contract payment reminder device provided by the present application are the same as the beneficial effects of the contract payment reminder method provided by the above embodiment, and the other technical features of the contract payment reminder device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0130] The present application provides a contract payment reminder device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the contract payment reminder method in the above-mentioned embodiment one.

[0131] Reference below Figure 8 , which shows a schematic diagram of the structure of a contract payment reminder device suitable for implementing the embodiment of the present application. The contract payment reminder device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The contract payment reminder device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0132] like Figure 8As shown, the contract payment reminder device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the contract payment reminder device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the contract payment reminder device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a contract payment reminder device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0133] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0134] The contract payment reminder device provided by the present application adopts the contract payment reminder method in the above embodiment, which can solve the technical problem that it is easy to cause the reminder of the payment user to be delayed, thereby reducing the timeliness of the reminder to the payment user. Compared with the prior art, the beneficial effects of the contract payment reminder device provided by the present application are the same as the beneficial effects of the contract payment reminder method provided by the above embodiment, and the other technical features of the contract payment reminder device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0135] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0136] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0137] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the contract payment reminder method in the above-mentioned embodiment.

[0138] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0139] The above-mentioned computer-readable storage medium may be included in the contract payment reminder device; or it may exist independently without being assembled into the contract payment reminder device.

[0140] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the contract payment reminder device, the contract payment reminder device: receives a payment strategy created by the payee based on the transaction method in the contract; according to the payment strategy, divides the contract information input by the payee based on the contract into different transaction methods, and obtains periodic sub-contracts representing different transaction methods; divides the periodic sub-contracts into tasks based on a preset payment cycle, and generates a payment task for reminding the payee recorded in the contract to make payments.

[0141] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0142] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0143] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0144] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned contract payment reminder method, and can solve the technical problem that it is easy to cause untimely reminders to payment users, thereby reducing the timeliness of reminders to payment users. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the contract payment reminder method provided by the above-mentioned embodiment, and will not be repeated here.

[0145] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned contract payment reminder method when executed by a processor.

[0146] The computer program product provided by this application can solve the technical problem that it is easy to cause the reminder of the payment user to be delayed, which in turn leads to the reduction of the timeliness of the reminder of the payment user. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the contract payment reminder method provided by the above embodiment, which will not be repeated here.

[0147] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A contract payment reminder method, characterized in that: The method includes: Receive the payment strategy created by the recipient based on the transaction method in the contract; According to the payment strategy, the contract information input by the payment recipient based on the contract is divided into different transaction modes to obtain periodic sub-contracts representing different transaction modes; The periodic sub-contract is divided into tasks based on a preset payment cycle, and a payment task is generated for reminding the payment user recorded in the contract to make the payment.

2. The method according to claim 1, characterized in that The step of dividing the contract information input by the payment recipient based on the contract into different transaction modes according to the payment strategy to obtain periodic sub-contracts representing different transaction modes includes: Identify the period fields for dividing the contract information from the payment strategy, the contract information being the information input by the payment recipient according to the corresponding period fields; Based on the period field, identifying the billing method and payment method of the corresponding period from the contract information; A contract transaction method based on the billing method and the payment method forming a corresponding cycle; According to the contract transaction mode and the payment strategy, the contract information is divided into different transaction modes according to the period field to obtain periodic sub-contracts representing different transaction modes.

3. The method according to claim 2, characterized in that The step of identifying the billing method and payment method of the corresponding period from the contract information based on the period field includes: identifying a corresponding time field in the contract information based on the period field; Based on a preset first position relationship, identifying the billing characters representing the billing method in each period from the contract information, the preset first position relationship being the position relationship between the time character and the billing character; Based on a preset second position relationship, identifying the payment characters representing the payment method in each period from the contract information, the preset second position relationship being the position relationship between the time field and the payment characters; The billing method selected in the corresponding period is filtered from the contract information based on the billing characters, and the payment method selected in the corresponding period is filtered from the contract information based on the payment characters.

4. The method according to claim 2, characterized in that The step of identifying the period fields for dividing the contract information from the payment strategy comprises: Identify time characters from the payment strategy and read context information of each time character; Based on the context information, selecting a period node representing a period from the time characters; Based on the periodic nodes, periodic fields for dividing the contract information are identified.

5. The method according to any one of claims 1 to 4, characterized in that The step of dividing the periodic sub-contract into tasks based on the preset payment cycle and generating a payment task for reminding the payment user recorded in the contract to make payment includes: Identifying the start time of the corresponding period from the periodic sub-contract; Taking the preset payment time as the time interval, dividing the periodic sub-contract into tasks according to the start time, and determining the time frame of each payment task to be generated; Based on the time frame, read the target billing method and target payment method corresponding to the current period from the periodic sub-contract, and obtain the target payment amount within the time frame; Based on the time frame, the target billing method, the target payment method and the target payment amount, a payment task is generated to remind the payment user recorded in the contract to make the payment.

6. The method according to claim 5, characterized in that The step of obtaining the target payment amount within each time frame includes: Determine the target billing method for each payment task within the time frame at the corresponding reminder time point; Based on the target billing method, a target payment amount within the preset payment time is determined.

7. A contract payment reminder device, characterized in that: The device comprises: The receiving module is used to receive the payment strategy created by the payee based on the transaction method in the contract; A contract division module, used to divide the contract information input by the payment recipient based on the contract into different transaction modes according to the payment strategy, and obtain periodic sub-contracts representing different transaction modes; The task generation module is used to divide the tasks of the periodic sub-contract based on the preset payment cycle, and generate payment tasks for reminding the payment users recorded in the contract to make payments.

8. A contract payment reminder device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the contract payment reminder method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the contract payment reminder method as described in any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the contract payment reminder method as described in any one of claims 1 to 6 are implemented.

Images