Generation method and device of payment bill information, equipment, storage medium and product

Abstract

The embodiment of the invention provides a payment bill information generation method and device, equipment, a storage medium and a product. The method comprises the following steps: for each payment item, determining whether the login time of an enterprise user login request is within a payment time period corresponding to the payment item, and if the login time is within the payment time period corresponding to the payment item, selecting target payment form information which is the same as the payment item from multiple pieces of historical payment form information; according to a payment item, a payment city and an enterprise payment account number in the target payment bill making information, generating and displaying a payment bill making link corresponding to the payment item; and in response to a triggering operation of the payment bill making link corresponding to any payment item, obtaining the payment item, the enterprise payment account number and the payment city associated with the payment bill making link, and generating payment bill making information corresponding to the payment item according to the payment bill information, the payment item, the enterprise payment account number and the payment city. According to the method, the efficiency of generating the payment bill making information is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of financial technology, and in particular to a method and device for generating payment order information, a storage medium and a product. BACKGROUND

[0002] In the daily operation of modern enterprises, the payment of public utility fees such as water, electricity and gas is a high-frequency and necessary operation. Enterprise users usually complete such payments through an enterprise online banking system.

[0003] In related technologies, an enterprise user needs to manually find a "payment on behalf of" menu after logging in to the online banking system, select a city and a payment item (such as water or electricity), input a household number and other query information, and perform an order search operation before being able to generate an order.

[0004] However, since the entire process involves multiple steps of interaction, and the user needs to repeatedly input key information (such as the household number), the repeated operations not only consume time but also lead to a low payment efficiency due to the input of incorrect information, thereby reducing the user experience. SUMMARY

[0005] The embodiments of the present application provide a method and device for generating payment order information, a storage medium and a product to improve the efficiency of generating payment order information.

[0006] In a first aspect, the embodiments of the present application provide a method for generating payment order information, comprising:

[0007] In response to a login request of an enterprise user, a plurality of historical payment order information of the enterprise user is obtained, and the historical payment order information at least includes a payment time, a payment item, a payment city and an enterprise payment household number;

[0008] According to the payment time and the payment item in the plurality of historical payment order information, a weighted average algorithm is used to predict a payment time period corresponding to each payment item of the enterprise payment household number;

[0009] For each payment item, it is determined whether the login time of the login request is within the payment time period corresponding to the payment item. If the login time of the login request is within the payment time period corresponding to the payment item, a target payment order information identical to the payment item is selected from the plurality of historical payment order information;

[0010] According to the payment item, the payment city and the enterprise payment household number in the target payment order information, a payment order link corresponding to the payment item is generated and displayed;

[0011] In response to a triggering operation of the payment order link corresponding to any payment item, the payment item, the enterprise payment household number and the payment city associated with the payment order link are obtained, and according to the enterprise payment household number, the payment bill information corresponding to the payment item is queried.

[0012] According to the payment bill information corresponding to the payment item, the payment item, the enterprise payment account number and the payment city associated with the payment bill link, the payment bill information corresponding to the payment item is generated.

[0013] In a possible implementation, according to the payment time and the payment item in the plurality of historical payment bill information, the weighted average algorithm is used to predict the payment time period corresponding to each payment item of the enterprise payment account number, comprising: for each payment item, obtaining a plurality of payment times corresponding to the payment item from the plurality of historical payment bill information; selecting a plurality of target payment times from the plurality of payment times corresponding to the payment item according to the time difference between the payment time and the current time; determining the weighted average time corresponding to the plurality of target payment times; taking the weighted average time as the end point of the time period, and taking the weighted average time minus the preset time length as the start point of the time period, to obtain the payment time period corresponding to the payment item.

[0014] In a possible implementation, selecting a plurality of target payment times from the plurality of payment times corresponding to the payment item according to the time difference between the payment time and the current time, comprising: selecting a plurality of target payment times in a preset number from the plurality of payment times corresponding to the payment item in the order of the time difference between the payment time and the current time from small to large; or, selecting a plurality of target payment times with a time difference less than a preset time difference threshold from the plurality of payment times corresponding to the payment item according to the time difference between the payment time and the current time.

[0015] In a possible implementation, according to the payment item, the payment city and the enterprise payment account number in the target payment bill information, a payment bill link corresponding to the payment item is generated and displayed, comprising: associating the payment item, the payment city and the enterprise payment account number in the target payment bill information with the payment bill link to generate and display the payment bill link corresponding to the payment item, the payment bill link carrying the payment item, the payment city and the enterprise payment account number.

[0016] In a possible implementation, associating the payment item, the payment city and the enterprise payment account number in the target payment bill information with the payment bill link, comprising: encrypting the enterprise payment account number in the target payment bill information by using a hash algorithm to obtain an encrypted enterprise payment account number; and associating the payment item, the payment city and the encrypted enterprise payment account number in the target payment bill information with the payment bill link.

[0017] In a possible implementation, the method further comprises: displaying a confirmation option corresponding to the payment bill information in the payment bill interface; in response to the triggering operation of the confirmation option, jumping the payment bill information to a payment review node, the payment review node being configured to review the payment bill information, and performing payment on the payment item after the review is passed.

[0018] In a second aspect, an embodiment of the present application provides a payment bill information generation device, comprising:

[0019] An acquisition module is configured to acquire a plurality of historical payment bill information of an enterprise user in response to a login request of the enterprise user, wherein the historical payment bill information comprises at least a payment time, a payment item, a payment city and an enterprise payment account number.

[0020] A prediction module is configured to predict a payment time period corresponding to each payment item of the enterprise payment account number by using a weighted average algorithm according to the payment time and the payment item in the plurality of historical payment bill information.

[0021] A determination module is configured to determine whether a login time of the login request is within the payment time period corresponding to each payment item, and select target payment bill information same as the payment item from the plurality of historical payment bill information if the login time of the login request is within the payment time period corresponding to the payment item.

[0022] A display module is configured to generate and display a payment bill link corresponding to the payment item according to the payment item, the payment city and the enterprise payment account number in the target payment bill information.

[0023] A query module is configured to acquire the payment item, the enterprise payment account number and the payment city associated with the payment bill link in response to a triggering operation of the payment bill link corresponding to any payment item, and query payment bill information corresponding to the payment item according to the enterprise payment account number.

[0024] A generation module is configured to generate payment bill information corresponding to the payment item according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number and the payment city associated with the payment bill link.

[0025] In a third aspect, an embodiment of the present application provides an electronic device, comprising a memory and a processor.

[0026] The memory stores computer execution instructions.

[0027] The processor executes the computer execution instructions stored in the memory, so that the processor executes the first aspect and / or various possible implementation manners of the first aspect.

[0028] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, wherein the computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed by the processor to implement the first aspect and / or various possible implementation manners of the first aspect.

[0029] In a fifth aspect, an embodiment of the present application provides a computer program product, comprising a computer program which, when executed by a processor, implements the first aspect and / or various possible implementation manners of the first aspect.

[0030] The method provided by the embodiment of the present application comprises: in response to a login request of an enterprise user, obtaining a plurality of historical payment invoice information of the enterprise user, the historical payment invoice information at least comprising a payment time, a payment item, a payment city and an enterprise payment account number; according to the payment time and the payment item in the plurality of historical payment invoice information, predicting a payment time period corresponding to each payment item of the enterprise payment account number by using a weighted average algorithm; for each payment item, determining whether a login time of the login request is within the payment time period corresponding to the payment item, if the login time of the login request is within the payment time period corresponding to the payment item, selecting target payment invoice information same as the payment item from the plurality of historical payment invoice information; according to the payment item, the payment city and the enterprise payment account number in the target payment invoice information, generating and displaying a payment invoice link corresponding to the payment item; in response to a triggering operation of the payment invoice link corresponding to any payment item, obtaining the payment item, the enterprise payment account number and the payment city associated with the payment invoice link, and querying payment bill information corresponding to the payment item according to the enterprise payment account number; and generating payment invoice information corresponding to the payment item according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number and the payment city associated with the payment invoice link. In the embodiment of the present application, the payment time period corresponding to each payment item of the enterprise payment account number is predicted by using the payment time and the payment item, if the login time of the login request is within the payment time period of the payment item, the user can directly query the payment bill information corresponding to the enterprise payment account number through the recommended payment invoice link, and obtain the payment item, the payment city and the enterprise payment account number in the target payment invoice information, to automatically generate the payment invoice information corresponding to the payment item, thereby reducing the complexity of the user payment operation, solving the problem of cumbersome process when the enterprise user performs the payment operation, and thus improving the efficiency of generating the payment invoice information. BRIEF DESCRIPTION OF DRAWINGS

[0031] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0032] Figure 1 A scene schematic diagram of the payment invoice information generation method provided by the present application;

[0033] Figure 2 A flowchart of the payment invoice information generation method provided by the embodiment of the present application;

[0034] Figure 3A schematic diagram of the structure of the device for generating payment invoice information provided in an embodiment of this application;

[0035] Figure 4 A schematic diagram of the structure of the electronic device provided in this application.

[0036] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0037] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0038] In the daily operations of modern enterprises, paying utility bills such as water, electricity, and gas is a frequent and necessary operation. Corporate users typically complete these payments through their corporate online banking systems.

[0039] In related technologies, corporate users need to log in to online banking, manually find the "Payment on Behalf" menu, select the city and payment item (such as water or electricity), enter their account number and other query information, and perform the bill inquiry operation before they can generate a bill. However, because the entire process involves multiple interactive steps, and users need to repeatedly enter key information (such as their account number), the repetitive operation is not only time-consuming but also prone to bill inquiry failure due to incorrect information, resulting in low payment efficiency and thus reducing user experience.

[0040] To address the aforementioned technical challenges, the inventors propose the following technical concept: Based on intelligent analysis of historical payment behavior data of enterprise users, an automated recommendation and execution mechanism for the payment process is constructed. Through data-driven predictive models and user behavior feature extraction, precise push notifications to payment entry points, automatic filling of key information, and seamless integration of the order inquiry and creation processes are achieved. By mining common patterns in users' high-frequency payment scenarios, the traditional payment process, which relies on manual operation, is transformed into a closed-loop system of data prediction, intelligent recommendation, and automatic execution, significantly reducing user operational complexity and improving process efficiency.

[0041] Correspondingly, the specific steps can comprise: in response to a login request of the enterprise user, obtaining a plurality of historical payment order information of the enterprise user, the historical payment order information at least comprising a payment time, a payment item, a payment city and an enterprise payment account number; according to the payment time and the payment item in the plurality of historical payment order information, predicting a payment time period corresponding to each payment item of the enterprise payment account number by using a weighted average algorithm; for each payment item, determining whether the login time of the login request is within the payment time period corresponding to the payment item, if the login time of the login request is within the payment time period corresponding to the payment item, selecting target payment order information same as the payment item from the plurality of historical payment order information; according to the payment item, the payment city and the enterprise payment account number in the target payment order information, generating and displaying a payment order link corresponding to the payment item; in response to a triggering operation of the payment order link corresponding to any payment item, obtaining the payment item, the enterprise payment account number and the payment city associated with the payment order link, and querying the payment bill information corresponding to the payment item according to the enterprise payment account number; and generating the payment order information corresponding to the payment item according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number and the payment city associated with the payment order link.

[0042] In the embodiments of the present disclosure, by predicting the payment time period corresponding to each payment item of the enterprise payment account number through the payment time and the payment item, if the user can directly query the payment bill information corresponding to the enterprise payment account number through the recommended payment order link within the payment time period of the payment item, and obtain the payment item, the payment city and the enterprise payment account number in the target payment order information, the payment order information corresponding to the payment item is automatically generated, which reduces the complexity of the user payment operation, solves the problem of cumbersome process when the enterprise user performs the payment operation, and thus improves the efficiency of generating the payment order information.

[0043] In the technical solutions of the present application, the collection, storage, use, processing, transmission, provision and disclosure of the financial data or user data and other information involved in the technical solutions comply with the relevant legal regulations and do not violate public order and good customs.

[0044] It should be noted that in the embodiments of the present application, some existing industry solutions such as software, components, models, etc. may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the implementation of the technical solutions of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0045] Figure 1 The scene schematic diagram of the payment order information generation method provided in the present application is shown in FIG. Figure 1 In this scene, it includes a server 101 and a terminal 102.

[0046] In the implementation process, the server 101 and the terminal 102 can be implemented by using one server or a cluster of multiple servers with more powerful processing capability and higher security, and in the case of possibility, a computer, a notebook computer or the like with stronger computing capability can also be used for replacement.

[0047] The connection mode between the server 101 and the terminal 102 can be wired connection or wireless connection. The enterprise user can log in to the enterprise online banking system through the terminal 102. The server 101 corresponding to the enterprise online banking system determines whether the login time of the login request is within the payment time period corresponding to each payment item; if it is within the payment time period corresponding to each payment item, the server 101 generates a payment order link corresponding to the payment item according to the payment item, the payment city and the enterprise payment account number, and displays the payment order link in the enterprise online banking system. The enterprise user triggers the payment order link through the terminal 102, and the server 101 automatically generates the payment order information corresponding to the payment item, thereby solving the problem of complicated process when the enterprise user performs the payment operation.

[0048] It can be understood that the scenario illustrated in the embodiment of the present application does not constitute a specific limitation on the method for generating payment order information. In another possible implementation of the present application, the above-mentioned scenario can include more or fewer components than the illustration, or combine certain components, or split certain components, or different component arrangement, and the specific determination can be made according to the actual application scenario, which is not limited herein. Figure 1 The illustrated scenario can be implemented by hardware, software, or a combination of software and hardware.

[0049] The technical solutions of the present application and how the technical solutions of the present application solve the above-mentioned technical problems will be described in detail in the following specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described in detail in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0050] Figure 2 The flowchart of the method for generating payment order information provided by the embodiment of the present application is shown. The execution subject of the embodiment of the present application can be the server 101 in Figure 1 , or a computer and / or a mobile phone, etc., and the embodiment does not particularly limit this. As Figure 2 shown, the method comprises:

[0051] S201, in response to a login request of an enterprise user, obtaining a plurality of historical payment order information of the enterprise user, the historical payment order information at least comprising payment time, payment item, payment city and enterprise payment account number.

[0052] In the embodiments of the present disclosure, the plurality of historical payment invoice information can be payment invoice information in a historical preset time length. For example, payment data in the last one month. The plurality of historical payment invoice information can also be a preset number of historical payment invoice information. The numerical value of the historical preset time length and the preset number is not specifically limited in the embodiments of the present disclosure.

[0053] For example, the preset number is 3; the plurality of historical payment invoice information includes payment invoice information of the last 3 electricity bills, payment invoice information of the last 3 water bills, and the like.

[0054] Optionally, when the enterprise user logs in the enterprise online bank, the system can call the historical payment data storage module to extract the payment records of the last 3 similar projects of the user.

[0055] S202, according to the payment time and the payment project in the plurality of historical payment invoice information, the weighted average algorithm is used to predict the payment time period corresponding to each payment project of the enterprise payment account number.

[0056] In a possible implementation, according to the payment time and the payment project in the plurality of historical payment invoice information, the weighted average algorithm is used to predict the payment time period corresponding to each payment project of the enterprise payment account number, including: for each payment project, obtaining a plurality of payment times corresponding to the payment project from the plurality of historical payment invoice information; selecting a plurality of target payment times from the plurality of payment times corresponding to the payment project according to the time difference between the payment time and the current time; determining a weighted average time corresponding to the plurality of target payment times, wherein the weight of the target payment time increases as the time difference decreases; taking the weighted average time as the end point of the time period, and taking the weighted average time minus the preset time length as the start point of the time period, to obtain the payment time period corresponding to the payment project.

[0057] Optionally, the target payment time can be the last N payment times, or the N payment times in a preset time (such as in the current quarter). Correspondingly, selecting a plurality of target payment times from the plurality of payment times corresponding to the payment project according to the time difference between the payment time and the current time includes: selecting a preset number of plurality of target payment times from the plurality of payment times corresponding to the payment project in the order of the time difference between the payment time and the current time from small to large; or selecting a plurality of target payment times with a time difference less than a preset time difference threshold from the plurality of payment times corresponding to the payment project according to the time difference between the payment time and the current time.

[0058] In the embodiments of the present disclosure, the numerical value of the preset time length is not specifically limited. For example, the preset time length is 7 days; the weighted average time is the 12th day of the month, the end point of the time period of the payment time period is the 12th day of the month, and the start point of the time period of the payment time period is the 5th day of the month. The payment time period is "from the 5th day of the month to the 12th day of the month".

[0059] In some embodiments, the weighted average time is obtained by weighted summation of a preset number of target payment times. Each target payment time can correspond to the same weight or different weights. Optionally, different weights are assigned according to the time difference between the target payment time and the current time. For example, the weight of the most recent payment time is 0.5, the weight of the intermediate payment time is 0.3, and the weight of the farthest payment time is 0.2.

[0060] For example, the enterprise user's electricity payment times in the past three months are January 15 (the 15th day of the month), February 20 (the 20th day of the month), and March 16 (the 16th day of the month). The weighted average time is: (the first order date x weight 1) + (the second order date x weight 2) + (the third order date x weight 3) = (15 x 0.2) + (20 x 0.3) + (16 x 0.5) = 17, and the weighted average time is the 17th day of the month.

[0061] In the embodiments of the present disclosure, the weighted average algorithm and the preset time period passing technique are used to accurately generate the prediction payment time interval. By dynamically adjusting the weight distribution strategy, the prediction result is more in line with the actual payment habits of the user. At the same time, by setting the preset time period, sufficient operation preparation time is provided for the user, effectively reducing the invalidation of the recommendation caused by the time prediction deviation, thereby improving the user experience.

[0062] S203, for each payment item, determine whether the login time of the login request is within the payment time period corresponding to the payment item. If the login time of the login request is within the payment time period corresponding to the payment item, select the target payment order information same as the payment item from the plurality of historical payment order information.

[0063] In the embodiments of the present disclosure, whether the login time of the login request is within the payment time period corresponding to each payment item can be determined one by one.

[0064] S204, according to the payment item, the payment city and the enterprise payment account number in the target payment order information, generate and display the payment order link corresponding to the payment item.

[0065] In one possible implementation, according to the payment item, the payment city and the enterprise payment account number, the payment order link corresponding to the payment item is generated and displayed, which includes: associating the payment item, the payment city and the enterprise payment account number in the target payment order information with the payment order link, generating and displaying the payment order link corresponding to the payment item, wherein the payment order link carries the payment item, the payment city and the enterprise payment account number.

[0066] Optionally, the payment item, the payment city and the enterprise payment account number in the target payment bill information are associated with the payment bill link, specifically including: extracting the payment city field, the payment item field and the enterprise payment account number field in the target payment bill information, encapsulating the extracted fields into link parameters in a unified format, and associating the link parameters with the payment bill link.

[0067] The city field refers to the payment city identifier associated in the user historical payment bill information. The payment item field refers to the specific payment type involved in the user historical payment bill information, such as "electricity fee" or "water fee". The account number field refers to the number used to uniquely identify the payment account in the user historical payment bill information, such as "123456" or "789012".

[0068] The link parameter in a unified format refers to a URL (Uniform Resource Locator) parameter encoded according to a predefined rule.

[0069] In a possible implementation, the city, the payment item and the account number field can be extracted from the user historical payment bill information by a data parsing module, and the fields are encoded into link parameters by a parameter encapsulation module according to a predefined format. The encoded link parameters are combined into a payment bill link by a link generation module.

[0070] In the embodiments of the present disclosure, the standardization generation of the quick payment bill link is realized through field extraction and parameter encapsulation technology. The parameter encoding in a predefined format ensures that the user historical payment bill information (city, item, account number) carried by the link can be directly parsed by the system and used in the subsequent payment process, avoiding the parsing failure problem caused by the non-uniform field format, and improving the compatibility and reusability of the link.

[0071] It should be noted that, in order to improve the security of the payment bill information, the enterprise payment account number can be encrypted. Correspondingly, the association of the payment item, the payment city and the enterprise payment account number in the target payment bill information with the payment bill link includes: encrypting the enterprise payment account number in the target payment bill information by using a hash algorithm to obtain an encrypted enterprise payment account number; and associating the payment item, the payment city and the encrypted enterprise payment account number in the target payment bill information with the payment bill link. At this time, the payment bill link carries the encrypted enterprise payment account number.

[0072] In the embodiments of the present disclosure, the payment bill links can be displayed in a user-friendly manner in a designated area of the homepage of the enterprise online banking. Optionally, after the payment bill links corresponding to the payment items are generated, the method further includes: displaying the payment bill links in a preset display manner at a preset information recommendation position; wherein the preset display manner includes one or more of preset display highlighting, preset display color, and preset display frequency. The preset information recommendation position can be any designated area of the homepage.

[0073] Here, since the real-time display of the links is realized through the interface element dynamic loading technology, the user can intuitively identify and quickly access the recommended payment bill entry, so that the user can discover the payment bill entry without actively searching, and the interactive consistency is enhanced through the fixed display position of the designated area, thereby improving the user experience.

[0074] In a possible implementation, before displaying the payment bill links, the system verifies the validity of the account number field in the payment bill links by calling the API interface of the third-party payment system. The verification process includes sending the account number field to the third-party payment system for verification and receiving the verification result, and if the verification is passed, the payment bill links are displayed. In this way, it can be ensured that the account number field carried by the payment bill links is consistent with the data of the third-party payment system. For example, the third-party payment system can be a power company payment system, a gas company payment system, etc.

[0075] S205, in response to the triggering operation of any payment bill link corresponding to a payment item, obtaining the payment item, the enterprise payment account number, and the payment city associated with the payment bill link, and querying the payment bill information corresponding to the payment item according to the enterprise payment account number.

[0076] The payment bill information corresponding to the enterprise payment account number can be the payment amount that the enterprise payment account number needs to pay.

[0077] In the embodiments of the present disclosure, since the payment bill information corresponding to the enterprise payment account number can be actively triggered when the payment bill information is generated, the operation complexity of the user is reduced, and thus the user experience is improved.

[0078] S206, generating payment bill information corresponding to the payment item according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number, and the payment city associated with the payment bill link.

[0079] In some embodiments, the payment order information corresponding to the payment item is generated according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number and the payment city associated with the payment order link, including: automatically filling the payment bill information field, the payment item field, the enterprise payment account number field and the payment city field in the payment order information according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number and the payment city associated with the payment order link, and generating the payment order information corresponding to the payment item.

[0080] In the embodiments of the present disclosure, since the payment order information can be pre-filled according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number and the payment city associated with the payment order link when generating the payment order information, the operation complexity of the user is significantly reduced, and thus the user experience is improved.

[0081] The method for generating payment order information provided by the embodiments of the present application: in response to a login request of an enterprise user, a plurality of historical payment order information of the enterprise user is obtained, and the historical payment order information at least includes payment time, payment item, payment city and enterprise payment account number; according to the payment time and the payment item in the plurality of historical payment order information, the weighted average algorithm is used to predict the payment time period corresponding to each payment item of the enterprise payment account number; for each payment item, it is determined whether the login time of the login request is within the payment time period corresponding to the payment item, if the login time of the login request is within the payment time period corresponding to the payment item, the target payment order information same as the payment item is selected from the plurality of historical payment order information; according to the payment item, the payment city and the enterprise payment account number in the target payment order information, the payment order link corresponding to the payment item is generated and displayed; in response to the triggering operation of the payment order link corresponding to any payment item, the payment item, the enterprise payment account number and the payment city associated with the payment order link are obtained, and the payment bill information corresponding to the payment item is queried according to the enterprise payment account number; according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number and the payment city associated with the payment order link, the payment order information corresponding to the payment item is generated. In the embodiments of the present disclosure, since the payment time and the payment item are used to predict the payment time period corresponding to each payment item of the enterprise payment account number, if the user is within the payment time period of the payment item, the user can directly query the payment bill information corresponding to the enterprise payment account number through the recommended payment order link, and obtain the payment item, the payment city and the enterprise payment account number in the target payment order information, and automatically generate the payment order information corresponding to the payment item, which reduces the complexity of the user's payment operation, solves the problem of complicated process when the enterprise user performs the payment operation, and thus improves the efficiency of generating the payment order information.

[0082] In some embodiments, the method comprises: displaying a confirmation option corresponding to the payment invoice information in the payment invoice interface; and in response to triggering of the confirmation option, jumping the payment invoice information to a payment review node.

[0083] Optionally, the payment review node is configured to review the payment invoice information by a reviewer, and perform payment on the payment item after confirming that the review is passed.

[0084] Figure 3 A structural schematic diagram of a payment invoice information generation apparatus provided by an embodiment of the present application is shown in FIG. 1. As shown in FIG. 1, the payment invoice information generation apparatus comprises: Figure 3

[0085] The obtaining module 301 is configured to obtain a plurality of historical payment invoice information of an enterprise user in response to a login request of the enterprise user, wherein the historical payment invoice information at least comprises a payment time, a payment item, a payment city, and an enterprise payment account number.

[0086] The prediction module 302 is configured to predict a payment time period corresponding to each payment item of the enterprise payment account number by using a weighted average algorithm according to the payment time and the payment item in the plurality of historical payment invoice information.

[0087] The determination module 303 is configured to determine whether a login time of the login request is within the payment time period corresponding to each payment item, and if the login time of the login request is within the payment time period corresponding to the payment item, select a target payment invoice information same as the payment item from the plurality of historical payment invoice information.

[0088] The display module 304 is configured to generate and display a payment invoice link corresponding to the payment item according to the payment item, the payment city, and the enterprise payment account number in the target payment invoice information.

[0089] The query module 305 is configured to obtain the payment item, the enterprise payment account number, and the payment city associated with the payment invoice link in response to triggering of the payment invoice link corresponding to any payment item, and query payment bill information corresponding to the payment item according to the enterprise payment account number.

[0090] The generation module 306 is configured to generate payment invoice information corresponding to the payment item according to the payment bill information corresponding to the payment item and the payment item, the enterprise payment account number, and the payment city associated with the payment invoice link.

[0091] ​In a possible implementation, the prediction module 302 predicts the payment time period corresponding to each payment item of the enterprise payment account number according to the payment time and the payment item in the plurality of historical payment receipt information by using a weighted average algorithm, including: for each payment item, obtaining a plurality of payment times corresponding to the payment item from the plurality of historical payment receipt information; selecting a plurality of target payment times from the plurality of payment times corresponding to the payment item according to the time difference between the payment time and the current time; determining a weighted average time corresponding to the plurality of target payment times; taking the weighted average time as the end point of the time period, and taking the weighted average time minus a preset time length as the start point of the time period to obtain the payment time period corresponding to the payment item.

[0092] In a possible implementation, the prediction module 302 selects a plurality of target payment times from the plurality of payment times corresponding to the payment item according to the time difference between the payment time and the current time, including: selecting a preset number of the plurality of target payment times from the plurality of payment times corresponding to the payment item in the order from small to large of the time difference between the payment time and the current time; or selecting the plurality of target payment times with the time difference less than a preset time difference threshold from the plurality of payment times corresponding to the payment item according to the time difference between the payment time and the current time.

[0093] In a possible implementation, the display module 304 generates and displays the payment receipt link corresponding to the payment item according to the payment item, the payment city and the enterprise payment account number in the target payment receipt information, including: associating the payment item, the payment city and the enterprise payment account number in the target payment receipt information with the payment receipt link to generate and display the payment receipt link corresponding to the payment item, and the payment receipt link carries the payment item, the payment city and the enterprise payment account number.

[0094] In a possible implementation, the display module 304 associates the payment item, the payment city and the enterprise payment account number in the target payment receipt information with the payment receipt link, including: performing encryption processing on the enterprise payment account number in the target payment receipt information by using a hash algorithm to obtain an encrypted enterprise payment account number; and associating the payment item, the payment city and the encrypted enterprise payment account number in the target payment receipt information with the payment receipt link.

[0095] In a possible implementation, the apparatus further includes a review module, and the review module is configured to display a confirmation option corresponding to the payment receipt information in the payment receipt interface; and in response to a triggering operation of the confirmation option, jump the payment receipt information to a payment review node, and the payment review node is configured to review the payment receipt information, and perform payment on the payment item after the review is passed.

[0096] The payment bill information generation device provided in the embodiment of the application can predict the payment time period corresponding to each payment item of the enterprise payment account number through the payment time and the payment item, and if the payment time period of the payment item is within the payment time period, the user can directly query the payment bill information corresponding to the enterprise payment account number through the recommended payment bill link, and obtain the payment item, the payment city and the enterprise payment account number in the target payment bill information, so as to automatically generate the payment bill information corresponding to the payment item, reduce the complexity of the user payment operation, solve the problem of complicated process when the enterprise user performs the payment operation, and therefore improve the efficiency of generating the payment bill information.

[0097] The payment bill information generation device provided in the embodiment of the application can execute the method provided in the method embodiment, and has similar implementation principles and technical effects, which will not be described here.

[0098] Figure 4 The structure schematic diagram of the electronic device provided in the application is shown in FIG. 1. Figure 4 As shown in FIG. 1, the electronic device 40 provided in the embodiment of the application includes at least one processor 401 and a memory 402. Optionally, the electronic device 40 further includes a communication component 403. The processor 401, the memory 402 and the communication component 403 are connected through a bus.

[0099] In the specific implementation process, the at least one processor 401 executes the computer execution instruction stored in the memory 402, so that the at least one processor 401 executes the method described above.

[0100] The specific implementation process of the processor 401 can refer to the method embodiment described above, and has similar implementation principles and technical effects, which will not be described here.

[0101] In the above embodiment, it should be understood that the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC) and the like. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor and the like. The steps of the method disclosed in the application can be directly embodied as the execution of the hardware processor, or executed by the combination of the hardware and software modules in the processor.

[0102] The memory can include a Random Access Memory (RAM) and can also include a Non-volatile Memory (NVM), such as at least one disk memory.

[0103] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application does not limit to only one bus or one type of bus.

[0104] The present application also provides a computer program product, comprising a computer program, which, when executed by a processor, implements the above method.

[0105] The present application also provides a computer readable storage medium, which stores computer execution instructions, and when a processor executes the computer execution instructions, the above method is implemented.

[0106] The above readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0107] An exemplary readable storage medium is coupled to the processor, so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an Application Specific Integrated Circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the device.

[0108] The division of units is only a logical function division, and actual implementation can have another division manner, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0109] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, can be located in one place, or can be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0110] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit.

[0111] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the part of the present application that essentially contributes to the prior art or the part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method of each embodiment of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0112] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware. The aforementioned program can be stored in a computer readable storage medium. The program executes to perform the steps of the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, and various program code storage media.

[0113] It should be understood that many of the materials and devices exemplified in this disclosure are articles of manufacture (i.e., articles of manufacture) according to this disclosure. The articles of manufacture can be employed as such to provide advantageous results. The articles of manufacture can also be employed in the practice or testing of the present disclosure. The articles of manufacture can also be employed in the practice or testing of other examples of the present disclosure. The articles of manufacture employed as such for practicing the present disclosure: include those devices and those manufacturing techniques that are known to those of skill in the art in this field. The articles of manufacture employed as such for practicing the present disclosure: include those devices and those manufacturing techniques that are analogous to those devices and those manufacturing techniques that are known to those of skill in the art in this field. The articles of manufacture employed as such for practicing the present disclosure: include those devices and those manufacturing techniques that are later developed by those of skill in the art in this field and are equivalent to those devices and those manufacturing techniques that are known to those of skill in the art in this field.

Claims

1. A method for generating payment invoice information, characterized in that, include: In response to a login request from an enterprise user, the system obtains multiple historical payment record information for that enterprise user. The historical payment record information includes at least the payment time, payment item, payment city, and enterprise payment account number. Based on the payment time and payment items in the multiple historical payment bills, a weighted average algorithm is used to predict the payment time period corresponding to each payment item of the enterprise's payment account number. For each payment item, determine whether the login time of the login request is within the payment time period corresponding to the payment item. If the login time of the login request is within the payment time period corresponding to the payment item, then select the target payment document information that is the same as the payment item from the multiple historical payment document information. Based on the payment item, payment city, and enterprise payment account number in the target payment bill information, generate and display the payment bill link corresponding to the payment item; In response to the triggering operation of the payment invoice link corresponding to any of the payment items, the payment item, corporate payment account number and payment city associated with the payment invoice link are obtained, and the payment bill information corresponding to the payment item is queried based on the corporate payment account number. Based on the payment bill information corresponding to the payment item and the payment item, enterprise payment account number and payment city associated with the payment document link, the payment document information corresponding to the payment item is generated.

2. The method according to claim 1, characterized in that, The step of predicting the payment period corresponding to each payment item of the enterprise payment account number using a weighted average algorithm based on the payment time and payment items in the multiple historical payment invoices includes: For each payment item, obtain multiple payment times corresponding to the payment item from the multiple historical payment invoice information; Based on the time difference between the payment time and the current time, select multiple target payment times from the multiple payment times corresponding to the payment item; Determine the weighted average time corresponding to the plurality of target payment times, wherein the weight of the target payment time increases as the time difference decreases; The payment period corresponding to the payment item is obtained by taking the weighted average time as the end point of the time period and taking the weighted average time minus the preset duration as the start point of the time period.

3. The method according to claim 2, characterized in that, The step of selecting multiple target payment times from multiple payment times corresponding to the payment item based on the time difference between the payment time and the current time includes: Select a preset number of target payment times from the multiple payment times corresponding to the payment item, in ascending order of the time difference between the payment time and the current time; or... Based on the time difference between the payment time and the current time, select multiple target payment times from the multiple payment times corresponding to the payment item, where the time difference is less than a preset time difference threshold.

4. The method according to claim 1, characterized in that, The step of generating and displaying the payment slip link corresponding to the payment item based on the payment item, payment city, and enterprise payment account number in the target payment slip information includes: The payment item, payment city, and corporate payment account number in the target payment bill information are associated with the payment bill link to generate and display the payment bill link corresponding to the payment item, wherein the payment bill link carries the payment item, payment city, and corporate payment account number.

5. The method according to claim 4, characterized in that, The step of associating the payment item, payment city, and corporate payment account number in the target payment document information with the payment document link includes: The enterprise payment account number in the target payment document information is encrypted using a hash algorithm to obtain the encrypted enterprise payment account number; Associate the payment item, payment city, and encrypted corporate payment account number in the target payment document information with the payment document link.

6. The method according to claim 1, characterized in that, The method further includes: The payment form interface displays the confirmation options corresponding to the payment form information. In response to the confirmation option, the payment order information is redirected to the payment review node, which reviews the payment order information and processes the payment for the item after the review is passed.

7. A device for generating payment invoice information, characterized in that, include: The acquisition module is used to respond to the login request of the enterprise user and acquire multiple historical payment bill information of the enterprise user. The historical payment bill information includes at least the payment time, payment item, payment city and enterprise payment account number. The prediction module is used to predict the payment time period corresponding to each payment item of the enterprise payment account number based on the payment time and payment items in the multiple historical payment bill information, using a weighted average algorithm. The determination module is used to determine whether the login time of the login request is within the payment time period corresponding to the payment item for each payment item. If the login time of the login request is within the payment time period corresponding to the payment item, then the target payment order information that is the same as the payment item is selected from the multiple historical payment order information. The display module is used to generate and display the payment document link corresponding to the payment item based on the payment item, payment city and enterprise payment account number in the target payment document information; The query module is used to respond to the triggering operation of the payment bill link corresponding to any of the payment items, obtain the payment item, enterprise payment account number and payment city associated with the payment bill link, and query the payment bill information corresponding to the payment item based on the enterprise payment account number. The generation module is used to generate payment invoice information corresponding to the payment item based on the payment bill information corresponding to the payment item and the payment item, enterprise payment account number and payment city associated with the payment invoice link.

8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1 to 6.

Images