Task pushing method and device, equipment and medium
By pushing payment bills online, the problem of cumbersome and errors in charging small fees within the organization is solved, and the timeliness and accuracy of payment is achieved, reducing labor and time costs.
Patent Information
- Application Number
- CN202411078581.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-07
- Publication Date
- 2024-11-12
AI Technical Summary
In the prior art, the method of charging small fees within the institution is cumbersome, prone to errors, high labor and time costs, and offline registration leads to difficulty in checking historical payment records and difficulty in statistical analysis of payment situations.
By pushing tasks online, in response to setting the payment cycle, the target object information is obtained, and the pending tasks are generated based on the payment strategy and historical payment information, and the payment bill is automatically pushed. The target object pays the fees required for the payment cycle online.
It improves the timeliness of fee collection, reduces the degree of manual participation and time cost, reduces the probability of errors, and ensures the accuracy of payment.
Smart Images

Figure CN118941284A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of Internet technology, and in particular to a task pushing method, device, equipment and medium. Background Art
[0002] Members of different institutions are obliged to pay management fees to the organization to which the institution belongs. In order to maintain the normal operation of the institution and provide services, the organization to which the institution belongs will regularly collect small management fees (hereinafter referred to as small fees) from the members of the institution. In related technologies, the collection of small fees within the organization mainly includes the following three methods:
[0003] The first one uses offline registration and charges a small fee from the institution members;
[0004] The second method is to collect small fees from members of the institution in cash;
[0005] The third method is to use private transfers to collect a small fee from members of the organization.
[0006] However, all of the above-mentioned collection methods have the following problems: the fee collection process is cumbersome, prone to errors, and has high labor and time costs. Summary of the invention
[0007] The present disclosure provides a task push method, device, equipment and medium to solve one of the technical problems in the related art at least to a certain extent. The technical solution of the present disclosure is as follows:
[0008] According to a first aspect of an embodiment of the present disclosure, a task pushing method is provided, including:
[0009] In response to reaching a set payment period associated with a target organization to which a target organization belongs, obtaining object information of at least one target object in the target organization;
[0010] For any target object, in response to the existence of historical payment information of any target object, determine the target payment amount that any target object needs to pay to the target organization in this payment cycle according to the payment strategy associated with the target organization, the object information of any target object and the historical payment information;
[0011] Generate a task to be processed for each target object according to the payment configuration associated with the target organization and the target payment amount of each target object;
[0012] The corresponding pending tasks are pushed to each of the target objects, so that each of the target objects executes the corresponding pending tasks and pays the target organization the target payment amount indicated by the payment slip in the corresponding pending tasks.
[0013] According to a second aspect of an embodiment of the present disclosure, there is provided a task pushing device, comprising:
[0014] A first acquisition module, configured to acquire object information of at least one target object in the target organization in response to reaching a set payment period associated with the target organization to which the target organization belongs;
[0015] A first determination module is used to determine, for any target object, in response to the existence of historical payment information of any target object, a target payment amount that any target object needs to pay to the target organization in this payment cycle according to a payment policy associated with the target organization, the object information of any target object, and the historical payment information;
[0016] A first generating module, configured to generate a to-be-processed task for each of the target objects according to the payment configuration associated with the target organization and the target payment amount of each of the target objects;
[0017] The first push module is used to push the corresponding pending tasks to each of the target objects, so that each of the target objects executes the corresponding pending tasks and pays the target payment amount indicated by the payment slip in the corresponding pending tasks to the target organization.
[0018] According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the task pushing method proposed in the above-mentioned first aspect of the present disclosure.
[0019] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can execute the task pushing method proposed in the first aspect of the present disclosure.
[0020] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, including: a computer program, which, when executed by a processor, implements the task pushing method as described in the above embodiment of the present disclosure.
[0021] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:
[0022] By pushing tasks online, payment slips are automatically pushed to the target objects in the target institutions, so that the target objects can pay the management fees required for this payment cycle online to the target organization to which the target institution belongs based on the payment slips. This can not only improve the timeliness of fee collection by the target organization, reduce the degree of manual participation, save labor and time costs, but also reduce the probability of errors in fee collection and ensure the accuracy of fee collection by the target organization.
[0023] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.
[0025] Figure 1 It is a flowchart of the task pushing method shown in the first embodiment of the present disclosure.
[0026] Figure 2 It is a flowchart of the task pushing method shown in the second embodiment of the present disclosure.
[0027] Figure 3 It is a flowchart of the task pushing method shown in the third embodiment of the present disclosure.
[0028] Figure 4 It is a flowchart of the task pushing method shown in the fourth embodiment of the present disclosure.
[0029] Figure 5 It is a flowchart of the task pushing method shown in the fifth embodiment of the present disclosure.
[0030] Figure 6 It is a flowchart of the task pushing method shown in the sixth embodiment of the present disclosure.
[0031] Figure 7 It is a flowchart of the task pushing method shown in the seventh embodiment of the present disclosure.
[0032] Figure 8 It is a structural diagram of a task pushing device shown in the eighth embodiment of the present disclosure.
[0033] Fig. 9 It is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION
[0034] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.
[0035] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0036] It should be noted that the acquisition, storage, use, and processing of data in the technical solution disclosed in this disclosure are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0037] It should also be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.
[0038] It should also be noted that in the embodiments of the present disclosure, certain software, components, models and other existing solutions in the industry may be mentioned, which should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present disclosure, but it does not mean that the applicant has or will necessarily use the solution.
[0039] At present, the collection method of small fees within an organization is often to collect them offline and then remit them to a designated bank account. This collection method has at least the following problems: the amount of money paid by each member of the organization is small and the number of times is high, which is prone to errors, and the fee summary is cumbersome, with high labor and time costs. In addition, the offline registration collection method makes it difficult to check the historical payment records of the members of the organization, and it is difficult to conduct statistical analysis of the payment situation at the organizational level, and it is not standardized.
[0040] In response to at least one of the above problems, the present disclosure proposes a task pushing method, device, equipment and medium.
[0041] The following describes the task push method, apparatus, device, and medium of the embodiments of the present disclosure with reference to the accompanying drawings.
[0042] Figure 1 It is a flowchart of the task pushing method shown in the first embodiment of the present disclosure.
[0043] The embodiment of the present disclosure takes the task pushing method configured in a task pushing device as an example. The task pushing device can be applied to any electronic device so that the electronic device can perform the task pushing function.
[0044] Among them, the electronic device can be any device with computing capabilities, such as a personal computer, a mobile terminal, a server, etc. The mobile terminal can be, for example, a vehicle-mounted device, a mobile phone, a tablet computer, a personal digital assistant, a wearable device, and other hardware devices with various operating systems, touch screens and / or display screens.
[0045] like Figure 1 As shown, the task pushing method may include the following steps S11 to S14.
[0046] In step S11 , in response to reaching a set payment period associated with a target organization to which the target organization belongs, object information of at least one target object in the target organization is obtained.
[0047] The target organization can be any organization.
[0048] Among them, the set payment cycle refers to the payment cycle pre-configured for the target organization to which the target institution belongs. It should be noted that in the embodiment of the present disclosure, there is no restriction on the period length of the set payment cycle. For example, the period length of the set payment cycle can be 1 week, 1 month, etc.
[0049] It should also be noted that for different target organizations, the associated set payment periods may be different. For example, the set payment period of organization 1 may be 1 week, the set payment period of organization 2 may be 1 month, and the set payment period of organization 3 may be 1 year.
[0050] Among them, the target object can be any member of the target organization, and the object information of the target object includes but is not limited to: object identification (such as object ID (Identity), object number, etc.), identity information (such as student, teacher, doctor, etc.), income information, etc.
[0051] In the embodiment of the present disclosure, when a set payment period associated with a target organization to which a target organization belongs is reached, object information of each target object in the target organization may be queried.
[0052] In step S12, for any target object, in response to the existence of historical payment information for any target object, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined based on the payment policy associated with the target organization, the object information of any target object and the historical payment information.
[0053] The historical payment information may include the fees that the target object needs to pay to the target organization in each historical payment period before the current payment period, and the fees that the target object actually paid to the target organization in each historical payment period.
[0054] In the disclosed embodiment, for any target object, it is possible to query whether the target object has historical payment information based on the object information of the target object. If the target object does not have historical payment information, it indicates that the target object is a new object joining the target organization (i.e., an institutional member). At this time, the target payment amount that the target object needs to pay to the target organization in this payment cycle can be calculated directly based on the object information of the target object and the payment policy associated with the target organization.
[0055] As an example, when the target organization is an enterprise and the target object is an employee of the enterprise, the payment standard adapted to the target object in the payment policy associated with the target organization can be obtained, and based on the income information in the target object's object information and the payment standard adapted to the target object, the target payment amount that the target object needs to pay to the target organization in this payment cycle can be calculated.
[0056] If the target object has historical payment information, the target payment amount that the target object needs to pay to the target organization in this payment cycle can be calculated by further combining the object information and historical payment information of the target object and the payment strategy associated with the target organization.
[0057] In step S13, a to-be-processed task for each target object is generated according to the payment configuration associated with the target organization and the target payment amount of each target object.
[0058] Among them, the payment configuration associated with the target organization refers to the configuration information pre-configured for the target organization and related to payment, which is used to indicate at least one collection account, payment method, currency, payment deadline and other information corresponding to the target organization.
[0059] In the disclosed embodiment, for any target object, a pending task for the target object in this payment cycle can be generated based on the target payment amount of the target object and the payment configuration associated with the target organization, wherein the pending task includes the payment slip of the target object, and the payment slip includes at least the target payment amount that the target object needs to pay to the target organization in this payment cycle.
[0060] In step S14, the corresponding pending tasks are pushed to each target object, so that each target object executes the corresponding pending tasks and pays the target payment amount indicated by the payment slip in the corresponding pending tasks to the target organization.
[0061] In an embodiment of the present disclosure, corresponding pending tasks can be pushed to each target object. In the present disclosure, after any target object receives a pending task, it can execute the pending task to pay the target organization the target payment amount indicated by the payment slip in the pending task.
[0062] The task pushing method of the disclosed embodiment automatically pushes payment slips to the target objects in the target organization by pushing tasks online, so that the target objects can pay the management fees required for this payment period to the target organization to which the target organization belongs online based on the payment slip. This can not only improve the timeliness of fee collection by the target organization, reduce the degree of manual participation, save labor and time costs, but also reduce the probability of errors in fee collection and ensure the accuracy of fee collection by the target organization.
[0063] The present disclosure provides another task pushing method. Figure 2 It is a flowchart of the task pushing method shown in the second embodiment of the present disclosure.
[0064] like Figure 2 As shown, in Figure 1 On the basis of the illustrated embodiment, after the task to be processed is pushed to any target object, the target object may perform the task to be processed by taking the following steps S21 to S24.
[0065] In step S21, in response to the payment status of the payment slip in the pending task being an unpaid state, a target payment method is determined from a plurality of candidate payment methods indicated by the payment slip.
[0066] Among them, the candidate payment methods can also be called candidate payment channels.
[0067] In the disclosed embodiment, in order to avoid repeated payments by the target object, it is possible to determine whether the payment status of the payment slip in the pending task is an unpaid status. If not, there is no need to execute subsequent steps. If so, it indicates that the target object has not paid the target payment amount indicated by the payment slip to the target organization. At this time, the target payment method can be determined from the multiple candidate payment methods indicated by the payment slip in the pending task.
[0068] As an example, the target object may manually select a target payment method from multiple candidate payment methods.
[0069] As another example, a default payment method among multiple candidate payment methods may be used as the target payment method.
[0070] In step S22, a target currency is determined from a plurality of candidate currencies indicated in the payment slip.
[0071] As an example, the target object may manually select the target currency from a plurality of candidate currencies indicated on the payment slip.
[0072] As another example, a default currency among multiple candidate currencies may be used as the target currency.
[0073] In step S23, before the payment deadline indicated in the payment slip is reached, the target payment amount indicated in the payment slip is transferred to the collection account of the target organization indicated in the payment slip based on the target payment method and target currency.
[0074] In the embodiment of the present disclosure, if the payment deadline indicated on the payment slip has not been reached at the current moment, the target payment amount indicated on the payment slip is transferred to the collection account of the target organization indicated on the payment slip based on the target payment method and target currency.
[0075] In step S24, in response to the target payment amount being transferred in successfully, the payment status of the payment slip is updated from an unpaid status to a paid status.
[0076] In the disclosed embodiment, when the target payment amount is transferred successfully, the payment status of the payment slip can be updated from an unpaid state to a paid state.
[0077] The task push method of the disclosed embodiment determines whether to transfer the target payment amount required to be paid by the target object to the collection account of the target organization indicated by the payment slip based on the payment status of the payment slip, which can avoid the target object from making repeated payments to the collection account of the target organization. In addition, only when the target payment amount is successfully transferred, the payment status of the payment slip is updated from the unpaid status to the paid status, which can avoid the target organization from missing fees, thereby improving the accuracy and rationality of fee collection.
[0078] The present disclosure provides another task pushing method. Figure 3 It is a flowchart of the task pushing method shown in the third embodiment of the present disclosure.
[0079] It should be noted that the task push method can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in the embodiment, or it can be executed in combination with any technical solution in the related technology, and the embodiments of the present disclosure are not limited to this.
[0080] like Figure 3 As shown, the task pushing method may include the following steps S301 to S310.
[0081] In step S301, in response to reaching a set payment period associated with a target organization to which a target organization belongs, object information of at least one target object in the target organization is obtained.
[0082] In step S302, for any target object, it is determined whether any target object has historical payment information. If so, step S303 is executed, and if not, step S304 is executed.
[0083] It should be noted that step S303 and step S304 are two parallel implementation methods. In actual application, only one needs to be executed.
[0084] The historical payment information may include the fees that the target object needs to pay to the target organization in each historical payment period before the current payment period, and the fees that the target object actually paid to the target organization in each historical payment period.
[0085] In step S303, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined based on the payment policy associated with the target organization, the object information and historical payment information of any target object.
[0086] For explanations of steps S301 to S303, reference may be made to the relevant descriptions in any embodiment of the present disclosure, and will not be repeated here.
[0087] In step S304, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined according to the payment policy associated with the target organization and the object information of any target object.
[0088] In the disclosed embodiment, for any target object, it is possible to query whether the target object has historical payment information based on the object information of the target object. If the target object does not have historical payment information, it indicates that the target object is a new object joining the target organization (i.e., an institutional member). At this time, the target payment amount that the target object needs to pay to the target organization in this payment cycle can be calculated directly based on the object information of the target object and the payment policy associated with the target organization.
[0089] As an example, the payment strategy associated with the target organization may include multiple payment standards. In the present disclosure, the payment standard adapted to the target object can be determined from multiple payment standards based on the object information of the target object, and the target payment amount that the target object needs to pay to the target organization in this payment cycle can be calculated based on the adapted payment standard and the object information of the target object.
[0090] For example, taking the target organization as an enterprise and the target object as the enterprise employees, the payment standard adapted to the target object may include a payment ratio. The target payment amount that the target object needs to pay to the target organization in this payment period can be calculated based on the income information in the target object's object information and the payment ratio.
[0091] In step S305, it is checked whether any target object has a first payment account for withholding, if so, step S306 is executed, if not, step S307 is executed.
[0092] In step S306, it is checked whether there is an available balance in the first payment account of any target object. If not, steps S307 to S308 are executed. If yes, steps S309 to S310 are executed.
[0093] In step S307, a to-be-processed task for any target object is generated according to the payment configuration associated with the target organization and the target payment amount of any target object.
[0094] As an example, for any target object, if the target object does not have a first payment account for withholding, or if the target object has a first payment account and there is no available balance in the first payment account, a pending task for the target object can be generated based on the target payment amount of the target object and the payment configuration associated with the target organization.
[0095] It is understandable that when the target object does not have a first payment account for withholding, or the target object has a first payment account but there is no available balance in the first payment account, the first payment account cannot be used for withholding. At this time, it is necessary to push a payment slip containing the entire target payment amount to the target object, which can improve the accuracy and effectiveness of the target institution's collection of fees.
[0096] As another example, for any target object, if the target object does not have a first payment account, or if the target object has a first payment account and there is no available balance in the first payment account, or if the target object has a first payment account and there is an available balance in the first payment account and the available balance is less than the target payment amount of the target object, then a pending task for the target object can be generated based on the target payment amount of the target object and the payment configuration associated with the target organization.
[0097] It is understandable that even if the target object has a first payment account for withholding and there is an available balance in the first payment account, since the available balance is less than the target payment amount of the target object (i.e., the available balance is insufficient), the available balance in the first payment account cannot be used for withholding. At this time, it is necessary to push a payment slip containing the full target payment amount to the target object, which can further improve the accuracy and effectiveness of the target institution's collection of fees.
[0098] In step S308, the corresponding pending tasks are pushed to each target object, so that each target object executes the corresponding pending tasks and pays the target payment amount indicated by the payment slip in the corresponding pending tasks to the target organization.
[0099] For explanations of steps S307 to S308, reference may be made to the relevant descriptions in any embodiment of the present disclosure, and will not be repeated here.
[0100] In step S309, it is determined whether the available balance is greater than or equal to the target payment amount of any target object. If so, step S310 is executed; if not, steps S307 to S308 are executed.
[0101] Step S310, deducting a target payment amount of any target object from the first payment account of any target object, and depositing the deducted target payment amount into a designated account associated with the target organization.
[0102] The designated account may be a pre-configured unified payment account associated with the target organization.
[0103] In an embodiment of the present disclosure, when the target object has a first payment account for withholding, and there is an available balance in the first payment account, and the available balance is greater than or equal to the target payment amount of the target object, the target payment amount of the target object can be directly deducted from the first payment account of the target object, and the deducted target payment amount can be deposited into a designated account associated with the target organization.
[0104] The task push method of the disclosed embodiment can utilize the funds deposited in advance by the target object into the withholding account to automatically collect the target payment amount that the target object needs to pay to the target organization in this payment cycle without the need for the target object to pay manually, which can reduce the target object's operations and improve the target object's usage experience.
[0105] The present disclosure provides another task pushing method. Figure 4 It is a flowchart of the task pushing method shown in the fourth embodiment of the present disclosure.
[0106] It should be noted that the task push method can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in the embodiment, or it can be executed in combination with any technical solution in the related technology, and the embodiments of the present disclosure are not limited to this.
[0107] like Figure 4 As shown, the task pushing method may include the following steps S401 to S413.
[0108] In step S401, in response to reaching a set payment period associated with a target organization to which a target organization belongs, object information of at least one target object in the target organization is obtained.
[0109] In step S402, for any target object, it is determined whether any target object has historical payment information. If so, step S403 is executed, and if not, step S404 is executed.
[0110] It should be noted that step S403 and step S404 are two parallel implementation methods. In actual application, only one needs to be executed.
[0111] In step S403, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined according to the payment policy associated with the target organization, the object information and historical payment information of any target object.
[0112] In step S404, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined according to the payment policy associated with the target organization and the object information of any target object.
[0113] In step S405, it is checked whether any target object has a first payment account for withholding, if so, step S406 is executed, if not, step S407 is executed.
[0114] In step S406, it is checked whether there is an available balance in the first payment account of any target object. If so, step S408 is executed; if not, step S407 is executed.
[0115] In step S407, based on the payment configuration associated with the target organization and the target payment amount of any target object, a to-be-processed task for any target object is generated, and the corresponding to-be-processed task is pushed to any target object.
[0116] Among them, the pending tasks are used by the target object to pay the target payment amount indicated on the payment slip to the target organization.
[0117] For explanation of step S407, reference may be made to the relevant description in any embodiment of the present disclosure, and will not be repeated here.
[0118] In step S408, it is determined whether the available balance is greater than or equal to the target payment amount of any target object. If so, step S409 is executed; if not, steps S410 to S413 are executed.
[0119] In step S409, a target payment amount of any target object is deducted from the first payment account of any target object, and the deducted target payment amount is deposited into a designated account associated with the target organization.
[0120] For explanations of steps S401 to S409, reference may be made to the relevant descriptions in any embodiment of the present disclosure, and will not be repeated here.
[0121] In any one embodiment of the present disclosure, for any one target object, when the available balance of the first payment account of the target object is greater than or equal to the target payment amount of the target object, and after the target payment amount of the target object is deducted from the first payment account of the target object, the following steps A to D may also be performed:
[0122] Step A: Determine a target financial product associated with the first payment account of the target object.
[0123] Among them, the target financial product can be an interest settlement product selected by the target object.
[0124] Step B: query the remaining amount in the first payment account of the target object; wherein the remaining amount is determined according to the difference between the available balance of the target object and the target payment amount.
[0125] Step C: In response to reaching the interest payment time, obtain the interest of the target object; wherein the interest is determined based on the interest rate of the target financial product and the remaining amount in step B.
[0126] Step D: Deposit the interest into the first payment account of the target object.
[0127] In this way, interest can be calculated on the remaining amount in the target object's withholding account, which can not only improve the target object's satisfaction and loyalty and encourage the target object to maintain pre-deposits, but also promote market competition and realize profit sharing.
[0128] In step S410, all available balances are deducted from the first payment account of any target object, and the deducted available balance is deposited into a designated account associated with the target organization.
[0129] In the embodiment of the present disclosure, for any target object, if the target object has a first payment account for withholding, and there is an available balance in the first payment account, and the available balance is less than the target payment amount of the target object, then all the available balance can be first deducted from the first payment account of the target object, and the deducted available balance can be deposited into a designated account associated with the target organization.
[0130] In step S411, the supplementary payment amount is determined according to the difference between the target payment amount and the available balance of any target object.
[0131] Furthermore, the target object's supplementary payment amount can be determined based on the difference between the target payment amount of the target object and the deducted available balance, that is, supplementary payment amount = target payment amount - available balance.
[0132] In step S412, based on the payment configuration and the supplementary payment amount associated with the target organization, a supplementary payment task to be paid for any target object is generated.
[0133] In the disclosed embodiment, a to-be-paid task of the target object can be generated according to the to-be-paid amount of the target object and the payment configuration associated with the target organization, wherein the to-be-paid task includes a to-be-paid form indicating the to-be-paid amount that the target object needs to pay to the target organization. The implementation principle is similar to step S13 and will not be described in detail here.
[0134] In step S413, the task to be supplemented is pushed to any target object, so that any target object executes the task to be supplemented and pays the supplementary payment amount in the supplementary payment form to the target organization.
[0135] In the disclosed embodiment, the to-be-paid task can be pushed to the target object, and accordingly, after receiving the to-be-paid task, the target object can execute the to-be-paid task to pay the target organization the to-be-paid amount indicated by the to-be-paid order in the to-be-paid task. The implementation principle is similar to steps S21 to S24, and will not be described in detail here.
[0136] The task push method of the disclosed embodiment automatically deducts the available balance in the first payment account when the available balance in the first payment account is insufficient, and then notifies the target object to make up the shortfall by pushing the task to be paid. This allows the target object to clearly see the amount deducted and the amount to be paid, thereby increasing the transparency of the operation. In addition, part of the amount is settled instantly, which speeds up the circulation of funds. Timely notification of the target object to make up the payment helps to reduce late payment fees or additional fees caused by overdue payments, and helps to optimize service processes and promote user loyalty.
[0137] The present disclosure provides another task pushing method. Figure 5It is a flowchart of the task pushing method shown in the fifth embodiment of the present disclosure.
[0138] It should be noted that the task push method can be executed alone, or it can be executed in combination with any embodiment of the present disclosure or a possible implementation method in the embodiment, or it can be executed in combination with any technical solution in the related technology, and the embodiments of the present disclosure are not limited to this.
[0139] like Figure 5 As shown, the task pushing method may include the following steps S51 to S58.
[0140] In step S51, in response to reaching a set payment period associated with a target organization to which a target organization belongs, object information of at least one target object in the target organization is obtained.
[0141] In step S52, for any target object, it is determined whether any target object has historical payment information. If so, step S53 is executed, and if not, step S54 is executed.
[0142] In step S53, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined based on the payment policy associated with the target organization, the object information and historical payment information of any target object.
[0143] In step S54, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined according to the payment policy associated with the target organization and the object information of any target object.
[0144] For explanations of steps S51 to S54, reference may be made to the relevant descriptions in any embodiment of the present disclosure and will not be repeated here.
[0145] In step S55, it is checked whether any target object applies for automatic deduction. If so, steps S57 to S58 are executed. If not, step S56 is executed.
[0146] In step S56, based on the payment configuration associated with the target organization and the target payment amount of any target object, a to-be-processed task for any target object is generated, and the to-be-processed task is pushed to any object.
[0147] In the embodiments of the present disclosure, for any target object, if the target object has not applied for automatic deduction, a pending task for the target object can be generated based on the target payment amount of the target object and the payment configuration associated with the target organization, and the pending task can be pushed to the object so that the target object executes the pending task and pays the target payment amount indicated on the payment slip in the pending task to the target organization.
[0148] For the explanation of step S56, please refer to the relevant description in any embodiment of the present disclosure, which will not be repeated here.
[0149] In step S57, a second payment account of any target object is determined.
[0150] In the embodiment of the present disclosure, for any target object, if the target object has applied for automatic deduction, the second payment account of the target object can be determined, wherein the second payment account is the payment account selected for automatic deduction when the target object applies for automatic deduction.
[0151] In step S58, the target payment amount of any target object is deducted from the second payment account, and the deducted target payment amount is deposited into a designated account associated with the target organization.
[0152] In the disclosed embodiment, the target payment amount of the target object may be automatically deducted from the second payment account, and the target payment amount deducted from the second payment account may be deposited into a designated account associated with the target organization.
[0153] The task push method of the disclosed embodiment, when the target object applies for automatic deduction, automatically deducts the target payment amount that the target object needs to pay to the target organization in this payment cycle from the target object's automatic deduction account, without the need for the target object to pay manually, which can reduce the target object's operations and improve the target object's user experience. If the target object does not apply for automatic deduction, based on the task push method, a payment slip containing the entire payment amount is pushed to the target object, which can improve the timeliness, effectiveness and accuracy of the target organization's fee collection.
[0154] The present disclosure provides another task pushing method. Figure 6 It is a flowchart of the task pushing method shown in the sixth embodiment of the present disclosure.
[0155] like Figure 6 As shown, in Figures 1 to 5 Based on any one of the embodiments, the task pushing method may further include the following steps S61 to S63.
[0156] In step S61, the payment status of the payment slip in the pending tasks of each target object is obtained.
[0157] Among them, the payment status includes unpaid status and paid status.
[0158] In the disclosed embodiment, the payment status of the payment slip in the pending tasks of each target object can be queried online.
[0159] In step S62, in response to the payment status corresponding to each target object being the paid status, the total amount transferred into the collection account in the payment slip corresponding to each target object is determined.
[0160] In the disclosed embodiment, when the payment status of each target object is paid, or when the payment deadline indicated on the payment slip is reached, the total amount transferred into the collection account in the payment slip corresponding to each target object can be counted.
[0161] In step S63, the total amount of each receiving account is transferred to a designated account associated with the target organization.
[0162] In the embodiment of the present disclosure, the total amount in each payment collection account may be transferred to a designated account associated with the target organization.
[0163] In any one of the embodiments of the present disclosure, the generation of payment statistics (paid, unpaid) reports in the organizational dimension can also be supported. That is, in the present disclosure, the payment status of the payment slips in the pending tasks of each target object can be obtained, and the payment statistics report can be generated according to the payment status corresponding to each target object.
[0164] The payment statistics report is used to indicate at least one of the following:
[0165] The first item is the object identifier of the target object for which payment has been made (such as object ID, object number, etc.).
[0166] The second item is the number of target objects that have paid.
[0167] The third item is the proportion of target objects that have paid, that is, the ratio of the number of target objects that have paid to the total number of target objects.
[0168] The fourth item is the object identifier of the target object that has not paid the fee.
[0169] Item 5: The number of target objects that have not paid.
[0170] The sixth item is the proportion of target objects that have not paid their fees, that is, the ratio of the number of target objects that have not paid their fees to the total number of target objects.
[0171] Item 7: The total amount of payment already paid by the target recipients.
[0172] Item 8: The total amount of contributions not paid by the target recipients.
[0173] In summary, it is possible to automatically count the real-time payment status of each target object and meet the actual statistical analysis needs in different application scenarios.
[0174] The task push method of the disclosed embodiment does not need to manually summarize the payment amounts in different collection accounts corresponding to the target organization, and aggregates the payment amounts in different collection accounts into a unified designated account, which can not only improve the efficiency of fee collection, but also reduce the probability of errors in fee collection.
[0175] The present disclosure provides another task pushing method. Figure 7 It is a flowchart of the task pushing method shown in the seventh embodiment of the present disclosure.
[0176] like Figure 7 As shown, in Figures 1 to 6 Based on any one of the embodiments, step S12 or step S303 or step S403 or step S53 may specifically include the following steps S71 to S74.
[0177] In step S71, for any target object, according to the object information of any target object, a target payment standard adapted to any target object is determined from a plurality of payment standards in the payment strategy associated with the target organization.
[0178] In the embodiment of the present disclosure, for any target object, a target payment standard adapted to the target object can be determined from multiple payment standards in the payment strategy associated with the target organization according to the object information of the target object.
[0179] For example, the target payment standard suitable for the target object can be determined based on the identity information and income information in the object information of the target object.
[0180] In step S72, based on the object information and target payment standard of any target object, the initial payment amount that any target object needs to pay to the target organization in this payment cycle is determined.
[0181] In the disclosed embodiment, the initial payment amount that the target object needs to pay to the target organization in this payment cycle can be calculated based on the target object information and the target charging standard adapted to the target object. The implementation principle is similar to step S303 and will not be repeated here.
[0182] In step S73, the historical payment information of any target object is queried to determine whether any target object has paid the historical payment amount to the target organization, and the query result is obtained.
[0183] Among them, the historical payment amount is the amount that any target object needs to pay to the target organization in the most recent payment cycle.
[0184] In the embodiment of the present disclosure, when the target object has historical payment information, it indicates that the target object is not a new object joining the target organization. At this time, the historical payment information of the target object can be further queried to determine whether the target object has paid the historical payment amount to the target organization to obtain the query result; wherein the historical payment amount is the amount that the target object needs to pay to the target organization in the most recent payment cycle.
[0185] In step S74, based on the query result and the initial payment amount, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined.
[0186] In the disclosed embodiment, the query result and the initial payment amount may be combined to calculate the target payment amount that the target object needs to pay to the target organization in this payment cycle.
[0187] As a possible implementation method, when the query result indicates that the target object has paid historical payment amounts to the target organization, the initial payment amount of the target object can be directly used as the target payment amount that the target object needs to pay to the target organization in this payment cycle.
[0188] As another possible implementation method, when the query result indicates that the target object has not paid the historical payment amount to the target organization, the target payment amount that the target object needs to pay to the target organization in this payment cycle can be further calculated based on the target object's initial payment amount and historical payment amount.
[0189] For example, target payment period = initial payment amount + historical payment amount.
[0190] As another possible implementation method, when the query result indicates that the target object has paid part of the historical payment amount to the target organization, the remaining amount (or the remaining amount) of the historical payment amount except the part can be calculated first, and then the target payment amount that the target object needs to pay to the target organization in this payment cycle can be calculated based on the remaining amount and the initial payment amount.
[0191] For example, target payment period = initial payment amount + remaining amount.
[0192] In summary, based on the query results, it is possible to specifically calculate the target payment amount that the target object needs to pay to the target organization in this payment cycle, which can improve the rationality and accuracy of the calculation of the target payment amount and avoid the situation where the target organization misses to collect fees that the target object has not paid in the historical payment cycle.
[0193] The task push method of the disclosed embodiment comprehensively considers the target payment standard adapted to each target object, the object information of the target object, and the query result of whether the target object has paid the historical payment amount to the target organization, to calculate the target payment amount that the target object needs to pay to the target organization in this payment cycle, thereby improving the rationality and accuracy of the calculation of the target payment amount.
[0194] In any embodiment of the present disclosure, in order to solve the problem that the existing method of collecting small fees within an organization has a complicated fee collection process and high labor and time costs, the present disclosure proposes an online payment method to improve the efficiency of fee collection and reduce labor and time costs.
[0195] As an example, payment slips can be automatically generated and pushed in batches according to the payment cycle, supporting online multi-channel payment, automatic payment collection, payment statistics, etc., mainly including the following parts:
[0196] Payment period management: support customized payment period, such as monthly or weekly collection;
[0197] Payment amount management: support customizing the payment amount of organization members; support batch import of payment amounts of organization members;
[0198] Payment slip management: support the creation of payment slips for organization members; support automatic batch generation of payment slips for organization members based on payment period and payment amount; support batch import of payment slips for organization members;
[0199] Payment of organization fees: Supports organization members to pay organization fees through multiple terminals (such as APP (Application), PC (Personal Computer), etc.), multiple payment channels, and multiple currencies. After the fees are paid, the payment status of the payment slip will be automatically updated;
[0200] Payment statistics analysis: support payment statistics (paid, unpaid) reports at the organizational level;
[0201] Collection: After payment is completed, payment aggregation is supported, and fees from different payment accounts are automatically collected into a unified designated account;
[0202] Automatic deduction: Automatically deduct fees according to the automatic deduction agreement and automatic deduction application. Furthermore, when the organization members are employees of the organization, the automatic deduction can be automatically lifted according to the resignation of the organization employees.
[0203] Withholding: Institutional members deposit the funds exceeding the required amount into the payment account first. When the funds are required to be deducted, the payment account will be directly deducted. When the funds in the payment account are insufficient, the payment slip or supplementary payment slip will be sent to the structural members;
[0204] Interest settlement of withheld funds: After withholding funds, institutional members select corresponding financial products and obtain returns from financial products on a regular basis.
[0205] In summary, it can replace the traditional offline registration, replace offline manual payment, automatically push payment slips, pay online, automatically count and analyze the payment situation of institution members, and ensure the timeliness and accuracy of small amount collection.
[0206] With the above Figures 1 to 7 Corresponding to the task push method provided in the embodiment, the present disclosure also provides a task push device. Figures 1 to 7 The task push method provided in the embodiment corresponds to the task push method, so the implementation method of the task push method is also applicable to the task push device provided in the embodiment of the present disclosure, and will not be described in detail in the embodiment of the present disclosure.
[0207] Figure 8 It is a structural diagram of a task pushing device shown in the eighth embodiment of the present disclosure.
[0208] Reference Figure 8 The task pushing device 800 may include: a first acquisition module 810 , a first determination module 820 , a first generation module 830 and a first pushing module 840 .
[0209] The first acquisition module 810 is used to acquire object information of at least one target object in the target organization in response to reaching a set payment period associated with the target organization to which the target organization belongs;
[0210] The first determination module 820 is used to determine, for any target object, in response to the existence of historical payment information for any target object, a target payment amount that any target object needs to pay to the target organization in this payment cycle according to the payment policy associated with the target organization, the object information of any target object, and the historical payment information;
[0211] A first generating module 830, configured to generate a to-be-processed task for each target object according to the payment configuration associated with the target organization and the target payment amount of each target object;
[0212] The first push module 840 is used to push the corresponding pending tasks to each target object, so that each target object executes the corresponding pending tasks and pays the target payment amount indicated by the payment slip in the corresponding pending tasks to the target organization.
[0213] In a possible implementation of the embodiment of the present disclosure, the payment strategy associated with the target organization includes multiple payment standards, and the first determination module 820 is specifically used to: for any target object, determine the target payment standard that is compatible with any target object from multiple payment standards based on the object information of any target object; determine the initial payment amount that any target object needs to pay to the target organization in this payment cycle based on the object information and the target payment standard of any target object; query the historical payment information of any target object to determine whether any target object has paid the historical payment amount to the target organization, and obtain the query result; wherein the historical payment amount is the amount that any target object needs to pay to the target organization in the most recent payment cycle; determine the target payment amount that any target object needs to pay to the target organization in this payment cycle based on the query result and the initial payment amount.
[0214] In a possible implementation of the embodiment of the present disclosure, the first determination module 820 is specifically used to: if the query result indicates that any target object has paid the historical payment amount, then the initial payment amount is used as the target payment amount that any target object needs to pay to the target organization in this payment cycle; if the query result indicates that any target object has not paid the historical payment amount, then the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined based on the initial payment amount and the historical payment amount; if the query result indicates that any target object has paid part of the historical payment amount, then the remaining amount of the historical payment amount other than the part is determined; based on the remaining amount and the initial payment amount, the target payment amount that any target object needs to pay to the target organization in this payment cycle is determined.
[0215] In a possible implementation of the embodiment of the present disclosure, the tasks to be processed are executed using the following modules:
[0216] A second determination module is used to determine a target payment method from a plurality of candidate payment methods indicated by the payment slip in response to the payment status of the payment slip in the pending task being an unpaid state;
[0217] A third determination module is used to determine the target currency from a plurality of candidate currencies indicated by the payment slip;
[0218] The first transfer module is used to transfer the target payment amount indicated in the payment slip to the collection account of the target organization indicated in the payment slip based on the target payment method and the target currency before the payment deadline indicated in the payment slip is reached;
[0219] The updating module is used to update the payment status of the payment slip from an unpaid state to a paid state in response to the target payment amount being transferred in successfully.
[0220] In a possible implementation of the embodiment of the present disclosure, the first generating module 830 is specifically used to: for any target object, query whether any target object has a first payment account for withholding;
[0221] If any target object has a first payment account, query whether there is an available balance in the first payment account of any target object;
[0222] When any target object does not have a first payment account, or when there is no available balance in the first payment account of any target object, a to-be-processed task for any target object is generated according to the payment configuration and the target payment amount of any target object.
[0223] In a possible implementation of the embodiment of the present disclosure, the first generating module 830 is specifically configured to: when there is an available balance in the first payment account of any target object, determine whether the available balance is greater than or equal to the target payment amount of any target object;
[0224] When any target object does not have a first payment account, or there is no available balance in the first payment account of any target object, or the available balance is less than the target payment amount of any target object, a pending task for any target object is generated based on the payment configuration and the target payment amount of any target object.
[0225] In a possible implementation of the embodiment of the present disclosure, the task pushing device 800 may further include:
[0226] A first deduction module is used to deduct the target payment amount of any target object from the first payment account of any target object if the available balance is greater than or equal to the target payment amount of any target object;
[0227] The first deposit module is used to deposit the deducted target payment amount into a designated account associated with the target organization.
[0228] In a possible implementation of the embodiment of the present disclosure, the task pushing device 800 may further include:
[0229] a processing module, configured to deduct all the available balance from the first payment account of any target object if there is an available balance in the first payment account of any target object, and the available balance is less than the target payment amount of any target object, and deposit the deducted available balance into a designated account associated with the target organization;
[0230] A fourth determination module is used to determine the supplementary payment amount according to the difference between the target payment amount and the available balance of any target object;
[0231] The second generation module is used to generate a task to be paid back for any target object according to the amount of the supplementary payment and the payment configuration; wherein the task to be paid back includes a supplementary payment form for indicating the amount of the supplementary payment that any target object needs to pay to the target organization;
[0232] The second push module is used to push the pending supplementary payment task to any target object, so that any target object can perform the pending supplementary payment task and pay the supplementary payment amount in the supplementary payment form to the target organization.
[0233] In a possible implementation of the embodiment of the present disclosure, the task pushing device 800 may further include:
[0234] A fifth determination module, configured to determine a target financial product associated with a first payment account of any target object;
[0235] A query module, used to query the remaining amount in the first payment account of any target object; wherein the remaining amount is determined according to the difference between the available balance of any target object and the target payment amount;
[0236] The second acquisition module is used to acquire the interest of any target object in response to reaching the interest payment time; wherein the interest is determined according to the interest rate and the remaining amount of the target financial product;
[0237] The second deposit module is used to deposit the interest into the first payment account of any target object.
[0238] In a possible implementation of the embodiment of the present disclosure, the first generating module 830 is specifically used to: for any target object, query whether any target object applies for automatic deduction;
[0239] In the case that any target object has not applied for automatic deduction, a pending task for any target object is generated according to the payment configuration and the target payment amount of any target object.
[0240] In a possible implementation of the embodiment of the present disclosure, the task pushing device 800 may further include:
[0241] A sixth determination module, used to determine a second payment account of any target object when any target object has applied for automatic deduction; wherein the second payment account is the payment account selected for automatic deduction when any target object applies for automatic deduction;
[0242] A second deduction module is used to deduct a target payment amount of any target object from the second payment account;
[0243] The third deposit module is used to deposit the deducted target payment amount into a designated account associated with the target organization.
[0244] In a possible implementation of the embodiment of the present disclosure, the task pushing device 800 may further include:
[0245] The third acquisition module is used to obtain the payment status of the payment slip in the pending task of each target object;
[0246] The third generation module is used to generate a payment statistics report according to the payment status corresponding to each target object;
[0247] Among them, the payment statistics report is used to indicate at least one of the following: the object identification of the target objects that have paid; the number of target objects that have paid; the proportion of target objects that have paid; the object identification of the target objects that have not paid; the number of target objects that have not paid; the proportion of target objects that have not paid; the total payment amount paid by the target objects that have paid; the total payment amount not paid by the target objects that have not paid.
[0248] In a possible implementation of the embodiment of the present disclosure, the task pushing device 800 may further include:
[0249] The fourth acquisition module is used to obtain the payment status of the payment slip in the pending task of each target object;
[0250] A seventh determination module, configured to determine the total amount transferred into the collection account in the payment slip corresponding to each target object in response to the payment status corresponding to each target object being the paid status;
[0251] The second transfer module is used to transfer the total amount of each receiving account to a designated account associated with the target organization.
[0252] The task pushing device of the disclosed embodiment automatically pushes payment slips to the target objects in the target organization by pushing tasks online, so that the target objects can pay the management fees required for this payment period to the target organization to which the target organization belongs online based on the payment slip. This can not only improve the timeliness of fee collection by the target organization, reduce the degree of manual participation, save labor and time costs, but also reduce the probability of errors in fee collection and ensure the accuracy of fee collection by the target organization.
[0253] In an exemplary embodiment, the present disclosure also provides an electronic device.
[0254] Among them, electronic equipment includes:
[0255] processor;
[0256] a memory for storing processor-executable instructions;
[0257] The processor is configured to execute instructions to implement the task pushing method proposed in any of the aforementioned embodiments of the present disclosure.
[0258] As an example, Fig. 9 is a schematic diagram of the structure of an electronic device 900 shown in an exemplary embodiment of the present disclosure, such as Fig. 9 As shown, the electronic device 900 may further include:
[0259] The memory 910 and the processor 920, a bus 930 connecting different components (including the memory 910 and the processor 920), the memory 910 stores a computer program, and when the processor 920 executes the program, the task pushing method described in any embodiment of the present disclosure is implemented.
[0260] Bus 930 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.
[0261] The electronic device 900 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by the electronic device 900, including volatile and non-volatile media, removable and non-removable media.
[0262] The memory 910 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 940 and / or cache memory 950. The server 900 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 960 may be used to read and write non-removable, non-volatile magnetic media ( Fig. 9 not shown, usually called a "hard drive"). Although Fig. 9 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 930 via one or more data medium interfaces. The memory 910 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.
[0263] A program / utility 980 having a set (at least one) of program modules 970 may be stored, for example, in the memory 910, such program modules 970 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 970 generally perform the functions and / or methods of the embodiments described in the present disclosure.
[0264] The electronic device 900 may also communicate with one or more external devices 990 (e.g., keyboard, pointing device, display 991, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 900, and / or communicate with any device that enables the electronic device 900 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 992. In addition, the electronic device 900 may also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN) and / or public network, such as the Internet) through a network adapter 993. As shown, the network adapter 993 communicates with other modules of the electronic device 900 through a bus 930. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0265] The processor 920 executes various functional applications and task push by running the programs stored in the memory 910 .
[0266] It should be noted that the implementation process and technical principles of the electronic device of this embodiment refer to the aforementioned explanation of the task push method of any embodiment of the present disclosure, and will not be repeated here.
[0267] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory including instructions, and the above instructions can be executed by a processor of an electronic device to complete the method proposed in any of the above embodiments. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0268] In an exemplary embodiment, a computer program product is also provided, including a computer program / instruction, wherein the computer program / instruction implements the method proposed in any of the above embodiments when executed by a processor.
[0269] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0270] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A task pushing method, characterized in that: include: In response to reaching a set payment period associated with a target organization to which a target organization belongs, obtaining object information of at least one target object in the target organization; For any target object, in response to the existence of historical payment information of any target object, determine the target payment amount that any target object needs to pay to the target organization in this payment cycle according to the payment strategy associated with the target organization, the object information of any target object and the historical payment information; Generate a task to be processed for each target object according to the payment configuration associated with the target organization and the target payment amount of each target object; The corresponding pending tasks are pushed to each of the target objects, so that each of the target objects executes the corresponding pending tasks and pays the target organization the target payment amount indicated by the payment slip in the corresponding pending tasks.
2. The method according to claim 1, characterized in that The payment strategy includes a plurality of payment standards. For any target object, in response to the existence of historical payment information of the any target object, according to the payment strategy associated with the target organization, the object information of the any target object and the historical payment information, determining a target payment amount that the any target object needs to pay to the target organization in this payment cycle includes: For any target object, according to the object information of any target object, determine a target payment standard adapted to any target object from the multiple payment standards; Determine, based on the object information of any target object and the target payment standard, the initial payment amount that any target object needs to pay to the target organization in the current payment cycle; Query the historical payment information of any target object to determine whether any target object has paid the historical payment amount to the target organization, and obtain the query result; wherein the historical payment amount is the amount that any target object needs to pay to the target organization in the most recent payment cycle; The target payment amount that any target object needs to pay to the target organization in the current payment cycle is determined based on the query result and the initial payment amount.
3. The method according to claim 2, characterized in that Determining the target payment amount that any target object needs to pay to the target organization in the current payment cycle according to the query result and the initial payment amount includes: If the query result indicates that any of the target objects has paid the historical payment amount, the initial payment amount is used as the target payment amount that any of the target objects needs to pay to the target organization in the current payment cycle; If the query result indicates that any of the target objects has not paid the historical payment amount, then determining the target payment amount that any of the target objects needs to pay to the target organization in the current payment cycle based on the initial payment amount and the historical payment amount; If the query result indicates that any target object has paid part of the historical payment amount, determining the remaining amount of the historical payment amount except the part; The target payment amount that any target object needs to pay to the target organization in this payment cycle is determined based on the remaining amount and the initial payment amount.
4. The method according to claim 1, characterized in that: The tasks to be processed are executed by the following steps: In response to the payment status of the payment slip in the pending task being an unpaid state, determining a target payment method from a plurality of candidate payment methods indicated by the payment slip; Determine a target currency from a plurality of candidate currencies indicated in the payment slip; Before the payment deadline indicated on the payment slip arrives, based on the target payment method and the target currency, the target payment amount indicated on the payment slip is transferred to the collection account of the target organization indicated on the payment slip; In response to the target payment amount being successfully transferred in, the payment status of the payment slip is updated from an unpaid status to a paid status.
5. The method according to claim 1, characterized in that The generating of the to-be-processed tasks for each target object according to the payment configuration associated with the target organization and the target payment amount of each target object includes: For any target object, query whether any target object has a first payment account for withholding; If any of the target objects has the first payment account, query whether there is an available balance in the first payment account of any of the target objects; When any of the target objects does not have a first payment account, or when no available balance exists in the first payment account of any of the target objects, a to-be-processed task for any of the target objects is generated according to the payment configuration and the target payment amount of any of the target objects.
6. The method according to claim 5, characterized in that In the case that any target object does not have a first payment account, or there is no available balance in the first payment account of any target object, generating a to-be-processed task for any target object according to the payment configuration and the target payment amount of any target object, including: In the case where there is an available balance in the first payment account of any target object, determining whether the available balance is greater than or equal to the target payment amount of any target object; When there is no first payment account for any of the target objects, or there is no available balance in the first payment account of any of the target objects, or the available balance is less than the target payment amount of any of the target objects, a pending task for any of the target objects is generated according to the payment configuration and the target payment amount of any of the target objects.
7. The method according to claim 6, characterized in that After determining whether the available balance is greater than or equal to the target payment amount of any target object, the method further includes: If the available balance is greater than or equal to the target payment amount of any target object, deducting the target payment amount of any target object from the first payment account of any target object; The deducted target payment amount is deposited into a designated account associated with the target organization.
8. The method according to claim 5, characterized in that After querying whether there is an available balance in the first payment account of any target object, the method further includes: If there is an available balance in the first payment account of any target object, and the available balance is less than the target payment amount of any target object, deduct all the available balance from the first payment account of any target object, and deposit the deducted available balance into a designated account associated with the target organization; Determine the amount of supplementary payment based on the difference between the target payment amount and the available balance of any target object; Generate a task to be paid for any target object according to the amount to be paid and the payment configuration; wherein the task to be paid for includes a payment slip for indicating the amount to be paid for any target object to pay to the target organization; The task to be supplemented is pushed to any of the target objects, so that any of the target objects executes the task to be supplemented and pays the supplementary payment amount in the supplementary payment form to the target organization.
9. The method according to claim 7, characterized in that: If the available balance is greater than or equal to the target payment amount of any target object, then after deducting the target payment amount of any target object from the first payment account of any target object, the method further includes: Determining a target financial product associated with a first payment account of any target object; Querying the remaining amount in the first payment account of any target object; wherein the remaining amount is determined according to the difference between the available balance of any target object and the target payment amount; In response to reaching the interest payment time, obtaining the interest of any target object; wherein the interest is determined according to the interest rate of the target financial product and the remaining amount; The interest is deposited into the first payment account of any target object.
10. The method according to claim 1, characterized in that The generating of the to-be-processed tasks for each target object according to the payment configuration associated with the target organization and the target payment amount of each target object includes: For any target object, query whether any target object applies for automatic deduction; In the case that any of the target objects has not applied for automatic deduction, a to-be-processed task for the any of the target objects is generated according to the payment configuration and the target payment amount of the any of the target objects.
11. The method according to claim 10, characterized in that After querying whether any target object applies for automatic deduction, the method further includes: In the case that any of the target objects has applied for automatic deduction, determining a second payment account of any of the target objects; wherein the second payment account is the payment account for automatic deduction selected by any of the target objects when applying for the automatic deduction; deducting the target payment amount of any target object from the second payment account; The deducted target payment amount is deposited into a designated account associated with the target organization.
12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: Obtaining the payment status of the payment slip in the pending tasks of each target object; Generate a payment statistics report according to the payment status corresponding to each target object; The payment statistics report is used to indicate at least one of the following: The object identifier of the target object for which the fee has been paid; The number of target subjects who have paid the fee; The percentage of target recipients who have paid; The object identifier of the target object that has not paid the fee; The number of target subjects who have not paid their dues; The percentage of target subjects who have not paid their fees; The total amount of payment paid by the target recipients who have paid; The total amount of payment that has not been paid by the target group.
13. The method according to any one of claims 1 to 11, characterized in that The method further comprises: Obtain the payment status of the payment slip in the pending tasks of each target object; In response to the payment status corresponding to each of the target objects being in the paid status, determining the total amount transferred into the collection account in the payment slip corresponding to each of the target objects; The total amount of each of the receiving accounts is transferred to a designated account associated with the target organization.
14. A task pushing device, characterized in that: include: A first acquisition module, configured to acquire object information of at least one target object in the target organization in response to reaching a set payment period associated with the target organization to which the target organization belongs; A first determination module is used to determine, for any target object, in response to the existence of historical payment information of any target object, a target payment amount that any target object needs to pay to the target organization in this payment cycle according to a payment policy associated with the target organization, the object information of any target object, and the historical payment information; A first generating module, configured to generate a to-be-processed task for each of the target objects according to the payment configuration associated with the target organization and the target payment amount of each of the target objects; The first push module is used to push the corresponding pending tasks to each of the target objects, so that each of the target objects executes the corresponding pending tasks and pays the target payment amount indicated by the payment slip in the corresponding pending tasks to the target organization.
15. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the task pushing method as described in any one of claims 1 to 13. 16 . A computer-readable storage medium, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the task pushing method according to any one of claims 1 to 13.
17. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the task pushing method according to any one of claims 1 to 13 is implemented.
