Property payment reminder method, device, electronic device, and medium

Abstract

This application discloses a property payment reminder method, device, electronic device, and medium. The method includes: determining a first account associated with a first project and a corresponding first user; sending a first payment notification to the first account; when the first account fails to pay within a preset time period, determining a second project corresponding to the first user based on a payment mapping table, and determining a second account associated with the second project, wherein the second project is a non-overdue payment project, and the second account is different from the first account but bound to the second project; when the second project reaches its corresponding payment reminder time, sending a second payment notification carrying the target bills associated with the first and second projects to the second account based on the first user's credit score. This application improves the delivery rate of payment notifications by determining another second account corresponding to the first user associated with the overdue payment project through a mapping table when the overdue payment project remains unpaid for a long period.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of communication technology, and in particular to a property fee payment reminder method, device, electronic device, and medium. Background Technology

[0002] Traditionally, residents pay property management fees offline at the property management office. To improve the convenience of payment, existing systems allow residents to pay online through a property management fee payment module. However, the payment reminder methods of these modules are rather limited. For overdue payments, they only notify the logged-in user account associated with the payment item via the property management app. This inadequate reminder strategy results in a low delivery rate for payment notifications. Furthermore, residents often forget to pay proactively. When the property management app detects that a payment has not been made within a preset time period, it suspends the corresponding property services, leading to a poor user experience. Summary of the Invention

[0003] This application provides a property fee payment reminder method, device, electronic device, and medium, which can improve the delivery rate of payment notifications and thus enhance user experience.

[0004] In a first aspect, embodiments of this application provide a property fee payment reminder method, applied to a property management system, including:

[0005] Identify the first account associated with the first project and identify the first user corresponding to the first account, wherein the first account is used to indicate the payment contact account bound to the first project, and the first project is an overdue payment project;

[0006] Within a preset time period, a preset number of first payment notifications are sent to the first account. If the first account fails to pay within the preset time period, a second item corresponding to the first user is determined based on a preset payment mapping table, and a second account associated with the second item is determined. The payment mapping table is used to indicate the mapping relationship between payment items, payment contact accounts, and corresponding users. The second item is a payment item that is not overdue. The second account is used to indicate the payment contact account bound to the second item. Both the first account and the second account are bound to the first user, and the first account and the second account are different from each other.

[0007] The first credit score level of the first user is determined based on the first user's historical payment records, wherein the historical payment records are used to indicate the historical payment records of all payment items associated with the first user in the payment mapping table;

[0008] When the second item reaches the corresponding collection time, a target bill is generated based on the first bill of the first item and the second bill of the second item, and a second payment notification carrying the target bill is sent to the second account based on the first credit score.

[0009] In some embodiments, each payment item in the payment mapping table corresponds to a property identifier. Based on a preset payment mapping table, a second item corresponding to the first user is determined, and a second account associated with the second item is determined, including:

[0010] Determine the target property identifier associated with the first user from the payment mapping table;

[0011] The items other than the first item in the payment items corresponding to the target property identifier are identified as candidate items;

[0012] Determine the user account corresponding to the candidate item, and determine the user identifier corresponding to the user account;

[0013] The user account that corresponds to the first user and is different from the first user is identified as the second user;

[0014] The candidate item corresponding to the second account is determined as the second item.

[0015] In some embodiments, the property management system is associated with at least a first platform, a second platform, and a third platform. The first user logs into the first platform, the second platform, and the third platform through a second account, and sends a second payment notification carrying the target bill to the second account based on the first credit score, including:

[0016] When the first credit score is higher than the preset level, the second payment notification is sent to the first platform, and the first time difference and the first operation are determined as the first conditions. The first time difference is the time difference between two consecutive sending of the second payment notification, and the first operation is the payment operation of the first user on the first platform.

[0017] If the reference time difference does not reach the first time difference and the first operation is not completed, the first condition is updated based on the first user's payment behavior on the first platform. The reference time difference is the time difference between the last time the second payment notification was sent and the current time.

[0018] The second payment notification is sent to the second platform based on the updated first condition. The second time difference and the second operation are determined as the second condition. The second time difference is the time difference between two consecutive sending of the second payment notification. The second operation is the payment operation on the first platform or the second platform.

[0019] If the reference time difference does not reach the second time difference and the second operation is not completed, the second condition is updated based on the first user's payment behavior on the first platform or the second platform, and the second payment notification is sent to the third platform based on the updated second condition.

[0020] When it is detected that the first user has completed the payment operation corresponding to the second payment notification on any platform, the sending of the second payment notification to the remaining platforms will be stopped;

[0021] or,

[0022] When the first credit score is lower than the preset level, the second payment notification is sent to the first platform, the second platform, and the third platform.

[0023] In some embodiments, updating the first condition based on the first user's payment behavior on the first platform includes:

[0024] Determine the first operating state of the first platform;

[0025] When the first running state characterizes the operation, if it is detected that the first user enters the payment page on the first platform but has not completed the payment, the first time difference is extended.

[0026] or,

[0027] If the first operating state representation is closed, determine the first user's reference payment behavior on the first platform before the first platform was closed, and update the first condition based on the reference payment behavior.

[0028] In some embodiments, updating the first condition based on the reference payment behavior includes:

[0029] The startup time of the first platform is used as the sending time of the last sending of the second payment notification to re-time and determine the third time difference, wherein the third time difference represents the time difference between the startup time and the next sending of the second payment notification;

[0030] When the first reference payment behavior indicates that the first user enters the payment page, the third time difference is extended, and the extended third time difference and the first operation are determined as the updated first condition.

[0031] or,

[0032] When the first reference payment behavior indicates that the first user has not entered the payment page, the third time difference and the first operation are determined as the updated first condition.

[0033] In some embodiments, if the first credit score is lower than a preset level, the method further includes:

[0034] Identify multiple third accounts associated with the first project and multiple fourth accounts associated with the second project, wherein the payment priority of the third accounts is lower than that of the first accounts, the payment priority of the fourth accounts is lower than that of the second accounts, and the users corresponding to the third accounts and the fourth accounts are different from the first user;

[0035] Each second credit score level is determined based on the historical payment records of the users corresponding to each of the third accounts in the business system, and each third credit score level is determined based on the historical payment records of the users corresponding to each of the fourth accounts in the business system.

[0036] Based on the preset level conditions and all the second credit score levels, a first target account is determined from the third account, and a new payment priority is assigned to the first target account, wherein the new payment priority of the first target account is higher than the payment priority of the first account.

[0037] Based on the preset level conditions and all of the third credit score levels, a second target account is determined from the fourth account, and a new payment priority is assigned to the second target account, wherein the new payment priority of the second target account is higher than the payment priority of the second account.

[0038] When the user corresponding to the first target account is the same as the user corresponding to the second target account, the second payment notification is sent to the first target account or the second target account.

[0039] When the user corresponding to the first target account is different from the user corresponding to the second target account, the second payment notification is sent to the first target account and the second target account at the same time.

[0040] In some embodiments, the first platform, the second platform, and the third platform are all configured with weight values. After sending a second payment notification carrying the target bill to the second account based on the first credit score, the method further includes:

[0041] If the first credit score is higher than the preset score, when it is detected that the first user completes the payment operation corresponding to the second payment notification on the second platform or the third platform, the platform corresponding to the completed payment operation is identified as the target platform, and the weight value of the target platform is increased, and the weight value of the target platform is higher than the weight value of the remaining platforms.

[0042] When the third item associated with the first user reaches the corresponding payment reminder time, a new second payment notification is sent to the target platform, wherein the third item is a payment item that is not overdue.

[0043] Secondly, embodiments of this application provide a control device, including at least one control processor and a memory for communicatively connecting to the at least one control processor; the memory stores instructions executable by the at least one control processor, which, when executed by the at least one control processor, enable the at least one control processor to perform the property payment reminder method as described in the first aspect.

[0044] Thirdly, embodiments of this application also provide an electronic device, including the control device of the second aspect.

[0045] Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for performing the property fee payment reminder method as described in the first aspect.

[0046] This application provides a property payment reminder method, device, electronic device, and medium. The method includes: determining a first account associated with a first item and determining a first user corresponding to the first account, wherein the first account is used to indicate a payment contact account bound to the first item, and the first item is an overdue payment item; sending a preset number of first payment notifications to the first account within a preset time period; when the first account fails to pay within the preset time period, determining a second item corresponding to the first user based on a preset payment mapping table and determining a second account associated with the second item, wherein the payment mapping table is used to indicate the mapping relationship between payment items, payment contact accounts, and corresponding users, and the second... The project is a payment project that is not overdue. The second account is used to indicate the payment contact account bound to the second project. Both the first account and the second account are bound to the first user, and the first account and the second account are different from each other. Based on the first user's historical payment records, the first user's first credit score level is determined. The historical payment records are used to indicate the historical payment records of all payment projects associated with the first user in the payment mapping table. When the second project reaches the corresponding due date, a target bill is generated based on the first bill of the first project and the second bill of the second project. Based on the first credit score level, a second payment notification carrying the target bill is sent to the second account. According to the solution provided in this application embodiment, when an overdue payment project has not been completed for a long time, another second account corresponding to the first user associated with the overdue payment project is determined through the mapping table. A second payment notification carrying the associated bills of the two projects is sent to the second account, improving the delivery rate of payment notifications and thus improving user experience. Attached Figure Description

[0047] Figure 1 This is a flowchart illustrating the steps of a property fee payment reminder method provided in one embodiment of this application;

[0048] Figure 2 This is a structural diagram of a control device provided in another embodiment of this application. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0050] It is understandable that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, or the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0051] Traditionally, residents pay property management fees offline at the property management office. To improve the convenience of payment, existing systems allow residents to pay online through a property management fee payment module. However, the payment reminder methods of these modules are rather limited. For overdue payments, they only notify the logged-in user account associated with the payment item via the property management app. This inadequate reminder strategy results in a low delivery rate for payment notifications. Furthermore, residents often forget to pay proactively. When the property management app detects that a payment has not been made within a preset time period, it suspends the corresponding property services, leading to a poor user experience.

[0052] To address the aforementioned problems, this application provides a property payment reminder method, device, electronic device, and medium. The method includes: determining a first account associated with a first item and determining a first user corresponding to the first account, wherein the first account is used to indicate a payment contact account bound to the first item, and the first item is an overdue payment item; sending a preset number of first payment notifications to the first account within a preset time period; if the first account fails to pay within the preset time period, determining a second item corresponding to the first user based on a preset payment mapping table and determining a second account associated with the second item, wherein the payment mapping table is used to indicate the mapping relationship between payment items, payment contact accounts, and corresponding users. The second item is a payment item that is not overdue. The second account is used to indicate the payment contact account bound to the second item. Both the first account and the second account are bound to the first user, and the first account and the second account are different from each other. A first credit score level for the first user is determined based on the first user's historical payment records, wherein the historical payment records are used to indicate the historical payment records of all payment items associated with the first user in the payment mapping table. When the second item reaches its corresponding due date, a target bill is generated based on the first bill of the first item and the second bill of the second item. A second payment notification carrying the target bill is sent to the second account based on the first credit score level. According to the solution provided in this application embodiment, when an overdue payment item remains unpaid for a long period, another second account corresponding to the first user associated with the overdue payment item is determined through the mapping table, and a second payment notification carrying the associated bills of both items is sent to the second account, improving the delivery rate of payment notifications and thus improving user experience.

[0053] The embodiments of this application will be further described below with reference to the accompanying drawings.

[0054] refer to Figure 1 , Figure 1 This is a flowchart illustrating the steps of a property fee payment reminder method according to an embodiment of this application. This application provides a property fee payment reminder method applied to a property management system, and the method includes, but is not limited to, the following steps:

[0055] Step S10: Determine the first account associated with the first project and determine the first user corresponding to the first account. The first account is used to indicate the payment contact account bound to the first project, and the first project is an overdue payment project.

[0056] Specifically, users bind their payment contact accounts to the payment items in advance in the property management system's associated property management APP. This allows the identification of the first account and the first user corresponding to the first item, thus providing a valid data foundation for sending the first and second payment notifications.

[0057] Step S20: Send a preset number of first payment notifications to the first account within a preset time period. If the first account fails to pay within the preset time period, determine the second item corresponding to the first user based on a preset payment mapping table, and determine the second account associated with the second item. The payment mapping table is used to indicate the mapping relationship between payment items, payment contact accounts, and corresponding users. The second item is a payment item that is not overdue. The second account is used to indicate the payment contact account bound to the second item. Both the first account and the second account are bound to the first user, and the first account and the second account are different from each other.

[0058] Specifically, the preset time period can be within one month or 45 days from the overdue date of the payment item. Those skilled in the art can determine it according to the actual situation. In this embodiment, the preset number of times the first payment notification is sent is determined by the preset time period. For example, if the preset time period is within one month from the overdue date of the payment item, the first payment notification is sent to the first account every week, and the preset number of times is 4.

[0059] Specifically, in this embodiment, the payment contact account is a mobile phone number or a social media account. As those skilled in the art know, the same user may have one or more payment contact accounts.

[0060] Specifically, when users bind payment items and payment contact accounts in the property management system, they can select accounts and payment items to bind according to different transaction habits. Therefore, there may be situations where different payment items for the same user are bound to different payment contact accounts. If multiple first payment notices have been sent to the first account within a preset time period, such as within one month, and the first account has not made any payments within this month, if the payment notices are only sent based on the original binding relationship of the payment items, it is easy to cause a low notification delivery rate and the payment matters cannot be completed.

[0061] Specifically, in some embodiments, each payment item in the payment mapping table corresponds to a property identifier. Figure 1 Step S20 includes, but is not limited to, the following steps:

[0062] Step S21: Determine the target property identifier associated with the first user from the payment mapping table;

[0063] Step S22: Select the items other than the first item from the payment items corresponding to the target property identifier as candidate items;

[0064] Step S23: Determine the user account corresponding to the candidate item and determine the user identifier corresponding to the user account;

[0065] Step S24: Identify the user account that corresponds to the first user and is different from the first user as the second user;

[0066] Step S25: The candidate item corresponding to the second account is determined as the second item.

[0067] Specifically, the property management system in this embodiment can also be connected to the power supply system, water supply system, or gas supply system. In this case, the payment items corresponding to the same property identifier include multiple types, such as property management fee-related payment items, as well as water fee items, electricity fee items, gas fee items, etc. Therefore, the specific number of candidate items in this embodiment depends on the actual situation.

[0068] Specifically, the same user may have one or more target property identifiers. Therefore, the second item may be a payment item of a different type than the first item corresponding to the same property identifier of the same user. For example, the first item may be the property management fee corresponding to property identifier A, and the second item may be the water fee corresponding to property identifier A. Alternatively, the second item may be the same type of payment item or different type of payment item corresponding to different property identifiers of the same user. For example, the first item may be the property management fee corresponding to property identifier B, and the second item may be the property management fee corresponding to property identifier C, or the first item may be the property management fee corresponding to property identifier B, and the second item may be the gas fee corresponding to property identifier C.

[0069] It is understood that the property management system in this embodiment maintains a payment mapping table to indicate the mapping relationship between payment items, payment contact accounts, and corresponding users. Based on this payment mapping table, it is possible to query and determine all payment items associated with the same user in the property management system, as well as the payment contact accounts corresponding to each payment item. Based on this, it is possible to find the payment contact account (i.e., the second account) other than the first account corresponding to the target user (i.e., the first user) associated with the first item. This provides an effective data foundation for the subsequent deployment of payment notification sending methods that improve the notification delivery rate.

[0070] Step S30: Determine the first credit score level of the first user based on the first user's historical payment records, wherein the historical payment records are used to indicate the historical payment records of all payment items associated with the first user in the payment mapping table.

[0071] Specifically, the historical payment records in this embodiment include payment time information (payment time, payment deadline, etc.), overdue status, early payment status, payment item information, and feedback on payment amount disputes.

[0072] Specifically, the method for determining the first user's first credit score level based on historical payment records in this embodiment may include: setting a basic credit score; periodically acquiring each payment record corresponding to the first user stored in the current property system; adding points when the first user makes an early payment; deducting points when the overdue payment exceeds a preset time; detecting the sending time of the payment amount objection feedback when the overdue payment exceeds a preset time and the payment amount objection feedback information is detected; deducting points when the sending time is detected to be overdue and adding points when the sending time is detected to be within the early payment time range; accumulating the added and deducted points of all current payment records, combining them with the basic credit score to obtain a target score, and determining the first credit score level based on the target score and the preset credit score level range.

[0073] It is understood that this embodiment uses different methods to send second payment notices for different first credit score levels. For example, for users with low credit scores, the second payment notice is sent more frequently, while for users with high credit scores, the second payment notice is sent less frequently. This can improve the delivery rate of the second payment notice while ensuring the user experience of users with high credit scores.

[0074] Step S40: When the second item reaches the corresponding collection time, a target bill is generated based on the first bill of the first item and the second bill of the second item, and a second payment notice carrying the target bill is sent to the second account based on the first credit score.

[0075] Specifically, in this embodiment, the collection reminder time is the time when the second bill corresponding to the second item is generated.

[0076] Specifically, the target bill in this embodiment includes target details and target amount. The target bill is generated by merging the bill details corresponding to the first bill and the second bill to obtain the target details, and adding the amounts corresponding to the first bill and the second bill to obtain the target amount.

[0077] It is understood that in this embodiment, after determining the second item, the second payment notification carrying the target bill is sent to the second account only after the second item reaches the corresponding payment reminder time. This can realize the completion of the second payment notification for two payment items in one reminder, saving the number of times the property system generates and sends the second payment notification, thereby saving system resources.

[0078] Specifically, in some embodiments, the property management system is associated with at least a first platform, a second platform, and a third platform, and a first user logs into the first platform, the second platform, and the third platform using a second account. Figure 1Step S40 involves sending a second payment notification carrying the target bill to the second account based on the first credit score, including but not limited to the following steps:

[0079] Step S41: When the first credit score is higher than the preset level condition, a second payment notification is sent to the first platform, and the first time difference and the first operation are determined as the first condition. The first time difference is the time difference between two consecutive second payment notifications, and the first operation is the payment operation of the first user on the first platform.

[0080] Step S42: When the reference time difference does not reach the first time difference and the first operation is not completed, the first condition is updated based on the first user's payment behavior on the first platform. The reference time difference is the time difference between the last time the second payment notification was sent and the current time.

[0081] Step S43: Send a second payment notification to the second platform based on the updated first condition, and determine the second time difference and the second operation as the second condition. The second time difference is the time difference between two consecutive sending of the second payment notification, and the second operation is the payment operation on the first platform or the second platform.

[0082] Step S44: When the reference time difference does not reach the second time difference and the second operation is not completed, update the second condition based on the first user's payment behavior on the first or second platform, and send a second payment notification to the third platform based on the updated second condition.

[0083] Step S45: When it is detected that the first user has completed the payment operation corresponding to the second payment notification on any platform, stop sending the second payment notification to the remaining platforms;

[0084] or,

[0085] Step S46: When the first credit score is lower than the preset level, a second payment notification is sent to the first platform, the second platform, and the third platform.

[0086] Specifically, referring to the description of the above embodiments, the collection methods are adjusted according to credit rating, which can improve the delivery rate and enhance the user experience of users with good credit.

[0087] Specifically, the first platform, the second platform, and the third platform in this embodiment are platforms that can provide property-related payment services to the first user. They can be property management apps, mobile communication platforms, or social software (such as WeChat). The first user can log in to the first platform, the second platform, and the third platform using their mobile phone number.

[0088] Specifically, in this embodiment, after sending the second payment notification to the first platform, the timing of the first condition is triggered, and it is determined whether the timing duration reaches the first time difference, and whether the first user completes the payment operation on the first platform (i.e. whether the first operation is completed) within the time period of the timing, so as to provide an effective basis for determining the timing of sending the second payment notification next time.

[0089] Specifically, the criterion for determining whether the first operation in this embodiment is completed is that the first user enters the payment page on the first platform and completes the payment, and then the corresponding payment record can be sent to the property management system through the first platform.

[0090] Specifically, in this embodiment, the reference time difference is calculated by timing the first condition after the second payment notification is sent to the first platform, and the time difference between the last time the second payment notification was sent and the current time is calculated, and then compared with the first time difference.

[0091] Specifically, in this embodiment, when the reference time difference does not reach the first time difference and the first operation is not completed, the system detects the first user's payment behavior 1 on the first platform (for example, the first platform is a property management APP, the first user opens the property management APP and performs an operation unrelated to project payment, or opens the property management APP, clicks on the payment page but does not complete the payment operation, etc.). Based on this payment behavior 1, the system adjusts the default basic first condition 1 to obtain the updated first condition 2, so as to adjust the timing of sending the second payment notification (i.e., sending the second payment notification 2) to the target user. The timing of sending the second payment notification is determined according to the two progressively adjustable conditions, so as to avoid the first user with a high credit score receiving frequent payment notification reminders when they are paying or have the intention to pay, which would affect the user experience.

[0092] Specifically, when the first credit score is lower than the preset level, a second payment notification is sent simultaneously to each platform logged in by the second account corresponding to the first user, in order to improve the delivery rate of the second payment notification.

[0093] It is understood that, in this embodiment, after detecting that the target user has completed the payment operation corresponding to the second payment notification on any of the first, second, or third platforms, the payment status of the corresponding first and second items is determined to be paid, and the second payment notification is stopped from being sent to the remaining platforms. This avoids the first user from receiving the payment notification corresponding to the paid service again after completing the payment operation, thus avoiding affecting the user experience.

[0094] In addition, after the second payment notification is sent to the third platform, when the reference time difference reaches the preset fifth time difference and the target user has not completed the payment operation on the first platform, the second platform or the third platform, the operation of steps S41 to S44 is repeated until the second project is in the overdue payment state, and the property-related services corresponding to the first project and the second project are suspended.

[0095] Specifically, the step of updating the first condition based on the first user's payment behavior on the first platform in step S43 includes, but is not limited to, the following steps:

[0096] Step S431: Determine the first operating state of the first platform;

[0097] Step S432: When the first running state indicates that the system is running, if it is detected that the first user enters the payment page on the first platform but has not completed the payment, the first time difference is extended.

[0098] or,

[0099] Step S433: If the first running state is closed, determine the first user's reference payment behavior on the first platform before the first platform is closed, and update the first condition based on the reference payment behavior.

[0100] Specifically, during the period when the reference time difference has not reached the first time difference, the first platform may be either closed or running. If the first platform is running, this embodiment determines whether the first user intends to pay by detecting whether the first user enters the payment page. This can be obtained by acquiring the operation log information corresponding to the first user on the first platform. Whether the user enters the payment interface is used as the criterion for adjusting the first time difference. In this embodiment, if the first user is detected entering the payment page on the first platform but has not submitted a payment, the first time difference is extended. If the user is not detected entering the payment page, it indicates that the first user does not intend to pay, and the first condition is not adjusted. If the first platform is detected to be closed, the user's payment behavior before the platform closed needs to be determined to update the first condition. Thus, in this embodiment, if one of the sub-conditions of the first condition is triggered but the conditions for sending a second payment notification to the second platform are not met, the first condition is dynamically adjusted and updated by monitoring the first user's payment behavior under various conditions on the first platform. This allows the timing of sending the second payment notification to the second platform to be adjusted according to the changes in the first condition, making the second payment notification more aligned with the first user's operating habits and ensuring a better user experience.

[0101] Specifically, the step of updating the first condition based on the reference payment behavior in step S433 includes, but is not limited to, the following steps:

[0102] The startup time of the first platform is used as the sending time of the last second payment notification to re-time and determine the third time difference, where the third time difference represents the time difference between the startup time and the next sending of the second payment notification;

[0103] When the first reference payment behavior indicates that the first user enters the payment page, the third time difference is extended, and the extended third time difference and the first operation are determined as the updated first condition.

[0104] or,

[0105] When the first reference payment behavior indicates that the first user has not entered the payment page, the third time difference and the first operation are determined as the updated first condition.

[0106] Understandably, to avoid the first user terminal receiving multiple second payment notifications simultaneously upon logging into the first platform when the first platform restarts and the first and second conditions are already met, thus affecting user experience, this embodiment uses the startup time of the first platform as the sending time of the last second payment notification to recalculate the time, determines the third time difference, and updates the first condition based on the user's first reference payment behavior before the first platform closes and the third time difference. Specifically, when the first reference payment behavior indicates that the first user has entered the payment page, the third time difference is extended, and the extended third time difference and the first operation are determined as the updated first condition; or, when the first reference payment behavior indicates that the first user has not entered the payment page, the third time difference and the first operation are determined as the updated first condition, thereby effectively improving user experience.

[0107] In addition, the process of updating the second condition based on the first user's payment behavior on the first or second platform also requires determining the operating status of the first and second platforms. When they are closed, it is necessary to determine the first user's reference payment behavior before the closure, and then combine the platform's operating status and the reference payment behavior to update the second condition to adjust the timing of sending the second payment notification next time, so that the sending of the second payment notification is more in line with the first user's usage habits and ensures user experience.

[0108] In addition, in some embodiments, when the first credit score is lower than a preset level, the property payment reminder method provided in this application embodiment also includes, but is not limited to, the following steps:

[0109] Step S51: Determine multiple third accounts associated with the first project and multiple fourth accounts associated with the second project, wherein the payment priority of the third accounts is lower than that of the first accounts, the payment priority of the fourth accounts is lower than that of the second accounts, and the users corresponding to the third and fourth accounts are different from the first user.

[0110] Step S52: Determine each second credit score level based on the historical payment records of the users corresponding to each third account in the business system, and determine each third credit score level based on the historical payment records of the users corresponding to each fourth account in the business system.

[0111] Step S53: Based on the preset level conditions and all second credit score levels, determine the first target account from the third accounts, and assign a new payment priority to the first target account. The new payment priority of the first target account is higher than the payment priority of the first account.

[0112] Step S54: Based on the preset level conditions and all third credit score levels, determine the second target account from the fourth account, assign a new payment priority to the second target account, and the new payment priority of the second target account is higher than the payment priority of the second account.

[0113] Step S55: When the user corresponding to the first target account is the same as the user corresponding to the second target account, send a second payment notification to the first target account or the second target account.

[0114] Step S56: When the user corresponding to the first target account is different from the user corresponding to the second target account, a second payment notification is sent to the first target account and at the same time to the second target account.

[0115] Specifically, users first bind their payment contact accounts to the payment items in the property management system's associated property management APP. In this embodiment, one payment item corresponds to multiple payment contact accounts. Each payment contact account can correspond to the same user or different users (for example, when renting out a house and binding the tenant's payment contact account, or using a family account). This ensures that the payment item can find the payment recipient in a timely manner and avoids the service corresponding to the payment item being suspended.

[0116] It is understood that the first and second projects in this embodiment correspond to the same property identifier. When the first credit score of the first user is lower than the preset level, the credit score of each payment object (i.e., the third and fourth accounts) corresponding to the first and second projects is determined, and the payment priority of each payment object corresponding to the first and second projects is adjusted according to the determined credit score. The payment object with the higher credit score has a higher payment priority. Adjusting the payment priority means adjusting the recipients of the second payment notification, thereby enabling the second payment notification to be sent to the objects corresponding to the first and second target accounts that have a higher willingness to respond to the second payment notification and complete the payment, which greatly increases the probability of completing the payment operation and improves the notification delivery rate.

[0117] In addition, in some embodiments, after step S40 is executed, the first platform, the second platform, and the third platform are all configured with weight values. The property payment reminder method provided in this application embodiment also includes, but is not limited to, the following steps:

[0118] Step S61: If the first credit score is higher than the preset score, when it is detected that the first user completes the payment operation corresponding to the second payment notification on the second platform or the third platform, the platform corresponding to the completed payment operation is identified as the target platform, and the weight value of the target platform is increased. The weight value of the target platform is higher than the weight value of the remaining platforms.

[0119] Step S62: When the third item associated with the first user reaches the corresponding overdue payment time, a new second payment notification is sent to the target platform, wherein the third item is a payment item that is not overdue.

[0120] Specifically, in this embodiment, the weight values ​​assigned to the first platform, the second platform, and the third platform are used to determine the sending order of the second payment notification to these three platforms, with higher weight values ​​indicating earlier sending order.

[0121] As can be understood, referring to the description of the above embodiments, when the first credit score is higher than the preset level, a multi-platform progressive method of sending the second payment notification is used to remind users to pay. During the multi-platform progressive payment reminder operation, when it is detected that the first user has completed the payment operation corresponding to the second payment notification on the second or third platform, the platform corresponding to the completed payment operation is identified as the target platform. This indicates that the first user is accustomed to making payments on the target platform, even though the first user has also logged into other platforms associated with the property system that provide payment services. Based on this, this embodiment increases the weight value of the target platform, making the weight value of the target platform higher than the weight values ​​of the remaining platforms. Thus, when the third item associated with the first user reaches the corresponding reminder time, a new second payment notification is sent to the target platform first, which can better match the first user's operating habits, ensure user experience, and increase the probability of completing the payment operation compared to completing the payment operation on the remaining platforms.

[0122] like Figure 2 As shown, Figure 2 This is a structural diagram of a control device provided in one embodiment of this application. The present invention also provides a control device 200, comprising:

[0123] The processor 210 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0124] The memory 220 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 220 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 220 and called by the processor 210 to execute the property payment reminder method of the embodiments of this application.

[0125] Input / output interface 230 is used to implement information input and output;

[0126] The communication interface 240 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0127] Bus 250 transmits information between various components of the device (e.g., processor 210, memory 220, input / output interface 230, and communication interface 240);

[0128] The processor 210, memory 220, input / output interface 230 and communication interface 240 are connected to each other within the device via bus 250.

[0129] In addition, this application also provides an electronic device, including the control device 200 described in the above embodiments.

[0130] In addition, this application embodiment also provides a storage medium, which is a computer-readable storage medium, storing a computer program that, when executed by a processor, implements the above-mentioned property fee payment reminder method.

[0131] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof. The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate, and may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0132] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically include computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0133] The above provides a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of the present invention.

Claims

1. A property fee payment reminder method, characterized in that, Applied to property management systems, including: Identify the first account associated with the first project and identify the first user corresponding to the first account, wherein the first account is used to indicate the payment contact account bound to the first project, and the first project is an overdue payment project; Within a preset time period, a preset number of first payment notifications are sent to the first account. If the first account fails to pay within the preset time period, a second item corresponding to the first user is determined based on a preset payment mapping table, and a second account associated with the second item is determined. The payment mapping table is used to indicate the mapping relationship between payment items, payment contact accounts, and corresponding users. The second item is a payment item that is not overdue. The second account is used to indicate the payment contact account bound to the second item. Both the first account and the second account are bound to the first user, and the first account and the second account are different from each other. The first credit score level of the first user is determined based on the first user's historical payment records, wherein the historical payment records are used to indicate the historical payment records of all payment items associated with the first user in the payment mapping table; When the second item reaches the corresponding collection time, a target bill is generated based on the first bill of the first item and the second bill of the second item, and a second payment notification carrying the target bill is sent to the second account based on the first credit score level. The property management system is associated with at least a first platform, a second platform, and a third platform. The first user logs into the first platform, the second platform, and the third platform through a second account, and sends a second payment notification carrying the target bill to the second account based on the first credit score, including: When the first credit score is higher than the preset level, the second payment notification is sent to the first platform, and the first time difference and the first operation are determined as the first conditions. The first time difference is the time difference between two consecutive sending of the second payment notification, and the first operation is the payment operation of the first user on the first platform. If the reference time difference does not reach the first time difference and the first operation is not completed, the first condition is updated based on the first user's payment behavior on the first platform. The reference time difference is the time difference between the last time the second payment notification was sent and the current time. The second payment notification is sent to the second platform based on the updated first condition. The second time difference and the second operation are determined as the second condition. The second time difference is the time difference between two consecutive sending of the second payment notification. The second operation is the payment operation on the first platform or the second platform. If the reference time difference does not reach the second time difference and the second operation is not completed, the second condition is updated based on the first user's payment behavior on the first platform or the second platform, and the second payment notification is sent to the third platform based on the updated second condition. When it is detected that the first user has completed the payment operation corresponding to the second payment notification on any platform, the sending of the second payment notification to the remaining platforms will be stopped; or, When the first credit score is lower than the preset level, the second payment notification is sent to the first platform, the second platform, and the third platform.

2. The property fee payment reminder method according to claim 1, characterized in that, Each payment item in the payment mapping table corresponds to a property identifier. Based on the preset payment mapping table, a second item corresponding to the first user is determined, and a second account associated with the second item is determined, including: Determine the target property identifier associated with the first user from the payment mapping table; The items other than the first item in the payment items corresponding to the target property identifier are identified as candidate items; Determine the user account corresponding to the candidate item, and determine the user identifier corresponding to the user account; The user account that corresponds to the first user and is different from the first user account is identified as the second user account; The candidate item corresponding to the second account is determined as the second item.

3. The property fee payment reminder method according to claim 1, characterized in that, The first condition is updated based on the first user's payment behavior on the first platform, including: Determine the first operating state of the first platform; When the first running state characterizes the operation, if it is detected that the first user enters the payment page on the first platform but has not completed the payment, the first time difference is extended. or, If the first operating state representation is closed, determine the first user's reference payment behavior on the first platform before the first platform was closed, and update the first condition based on the reference payment behavior.

4. The property fee payment reminder method according to claim 3, characterized in that, Updating the first condition based on the reference payment behavior includes: The startup time of the first platform is used as the sending time of the last sending of the second payment notification to re-time and determine the third time difference, wherein the third time difference represents the time difference between the startup time and the next sending of the second payment notification; When the first reference payment behavior indicates that the first user enters the payment page, the third time difference is extended, and the extended third time difference and the first operation are determined as the updated first condition. or, When the first reference payment behavior indicates that the first user has not entered the payment page, the third time difference and the first operation are determined as the updated first condition.

5. The property fee payment reminder method according to claim 2, characterized in that, If the first credit score is lower than a preset level, the method further includes: Identify multiple third accounts associated with the first project and multiple fourth accounts associated with the second project, wherein the payment priority of the third accounts is lower than that of the first accounts, the payment priority of the fourth accounts is lower than that of the second accounts, and the users corresponding to the third accounts and the fourth accounts are different from the first user; Each second credit score level is determined based on the historical payment records of the users corresponding to each third account in the business system, and each third credit score level is determined based on the historical payment records of the users corresponding to each fourth account in the business system. Based on the preset level conditions and all the second credit score levels, a first target account is determined from the third account, and a new payment priority is assigned to the first target account, wherein the new payment priority of the first target account is higher than the payment priority of the first account. Based on the preset level conditions and all of the third credit score levels, a second target account is determined from the fourth account, and a new payment priority is assigned to the second target account, wherein the new payment priority of the second target account is higher than the payment priority of the second account. When the user corresponding to the first target account is the same as the user corresponding to the second target account, the second payment notification is sent to the first target account or the second target account. When the user corresponding to the first target account is different from the user corresponding to the second target account, the second payment notification is sent to the first target account and the second target account at the same time.

6. The property fee payment reminder method according to claim 1, characterized in that, The first platform, the second platform, and the third platform are all configured with weight values. After sending a second payment notification carrying the target bill to the second account based on the first credit score, the method further includes: If the first credit score is higher than the preset score, when it is detected that the first user completes the payment operation corresponding to the second payment notification on the second platform or the third platform, the platform corresponding to the completed payment operation is identified as the target platform, and the weight value of the target platform is increased, and the weight value of the target platform is higher than the weight value of the remaining platforms. When the third item associated with the first user reaches the corresponding payment reminder time, a new second payment notification is sent to the target platform, wherein the third item is a payment item that is not overdue.

7. A control device, characterized in that, It includes at least one control processor and a memory for communicatively connecting to the at least one control processor; the memory stores instructions executable by the at least one control processor, which, when executed by the at least one control processor, enable the at least one control processor to perform the property fee payment reminder method as described in any one of claims 1 to 6.

8. An electronic device, characterized in that, Includes the control device as described in claim 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to perform the property fee payment reminder method as described in any one of claims 1 to 6.

Images