Processing method and device of market management bill and server

Abstract

The invention provides a market management bill processing method and device and a server, which can be used in the financial field. Based on the method, after a server receives a multi-bill merging processing request, bill information, payment time limit data and payment preferential data of a target market management bill, and attribute information and behavior data of a merchant can be firstly obtained, and two different dimensions of time limit and preferential of the market management bill are synthesized according to the bill information, the payment time limit data and the payment preferential data of the target market management bill; a bill processing scheme matched with the merchant is automatically determined as a recommendation scheme for the merchant to select; according to feedback data of the merchant for the recommendation scheme, determining a target processing rule for the multiple target market management bills; and thus, according to the target processing rule, a plurality of target market management bills can be processed through interaction with the merchant terminal. Therefore, the method can be well adapted to a market management payment scene, a merchant can select a matched processing mode to complete related bill payment according to own conditions, and the interaction experience of the merchant is improved.

Description

Technical Field

[0001] This specification belongs to the technical field of bill data processing, and in particular to a method, device and server for processing market management bills. Background Art

[0002] In the financial business field, for market management payment scenarios, according to relevant market regulations, merchants entering the market (for example, agricultural trade wholesale markets, etc.) usually need to pay a variety of related market management fees to the market management party.

[0003] However, based on the existing method, when a merchant receives a market management fee bill, he needs to make a one-time payment for the market management fee bill. In actual implementation, there are often problems such as rigid and inconvenient payment methods, cumbersome merchant operations, heavy financial pressure, and poor merchant interaction experience.

[0004] Currently, no effective solution has been proposed to the above problems. Summary of the invention

[0005] This specification provides a method, device and server for processing market management bills, which can be well adapted to market management payment scenarios, allowing merchants to flexibly choose and complete the payment of relevant market management fees through matching processing methods according to their own circumstances, thereby improving the merchant's interactive experience.

[0006] This manual provides a method for processing market management bills, including:

[0007] Receiving a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least the bill identifiers of multiple target market management bills selected by the merchant and the merchant identifier of the merchant;

[0008] According to the bill identifications of multiple target market management bills, the bill information, payment time limit data, and payment discount data of the target market management bills are obtained; and according to the merchant identifications of the merchants, the attribute information and behavior data of the merchants are obtained;

[0009] Based on the bill information, payment time limit data, payment discount data of bill management bills in multiple target markets, as well as the attribute information and behavior data of merchants, multiple bill processing solutions matching the merchants are generated as recommended solutions;

[0010] Sending the recommendation plan to the merchant terminal, and receiving merchant feedback data on the recommendation plan; wherein the merchant terminal is used to display the recommendation plan to the merchant;

[0011] According to the feedback data, target processing rules for managing bills in multiple target markets selected by the target merchant are determined; wherein the target processing rules at least include: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules;

[0012] Interact with merchant terminals to manage bills for multiple target markets based on target processing rules.

[0013] In one embodiment, according to the target processing rules, the system interacts with the merchant terminal to process multiple target market management bills, including:

[0014] According to the bill merging sub-rule, a first target market management bill among the multiple target market management bills is merged to obtain a corresponding first payment order; a second target market management bill among the multiple target market management bills is merged to obtain a corresponding second payment order; wherein the payment time limit data and / or payment discount data of the first target market management bill associated with the first payment order matches, and the payment time limit data and / or payment discount data of the second target market management bill associated with the second payment order matches;

[0015] Generate, according to the bill payment sub-rule, a plurality of first payment tasks regarding the first payment order and a plurality of second payment tasks regarding the second payment order;

[0016] According to the target processing rule, by interacting with the merchant terminal, multiple first payment tasks and multiple second payment tasks are executed in batches to obtain corresponding first payment resource data and second payment resource data;

[0017] According to the bill settlement allocation sub-rule, the first target market management bills are settled and written off in batches using the first payment resource data; the second target market management bills are settled and written off in batches using the second payment resource data.

[0018] In one embodiment, after merging a first target market management bill among multiple target market management bills to obtain a corresponding first payment order according to the bill merging sub-rule; and merging a second target market management bill among multiple target market management bills to obtain a corresponding second payment order, the method further includes:

[0019] The remaining third target market management bills in the multiple target market management bills are combined to obtain a corresponding third payment order.

[0020] In one embodiment, according to the bill merging sub-rule, merging the first target market management bill among the multiple target market management bills to obtain the corresponding first payment order includes:

[0021] According to the bill merging sub-rule and the payment time limit data of the target market management bill, the target market management bill whose time difference between the verification deadline and the current time is less than the first reference time is selected from multiple target market management bills as candidate target market management bills;

[0022] According to the bill merging sub-rule and the payment preferential data of the candidate market management bills, a candidate target market management bill without mutually exclusive preferential treatment is selected from multiple candidate target market management bills as the first target market management bill;

[0023] According to the bill merging sub-rule, the bill information of the multiple first target market management bills is used to merge the multiple first target market management bills to obtain the corresponding first payment order.

[0024] In one embodiment, according to the bill merging sub-rule, merging the second target market management bills in the plurality of target market management bills to obtain the corresponding second payment order includes:

[0025] Determining a first remaining bill among the plurality of target market management bills except the first target market management bill;

[0026] According to the bill merging sub-rule and the payment preferential data of the first remaining bills, bills with mutually exclusive preferential treatment are eliminated from the plurality of first remaining bills to obtain the second target market management bills;

[0027] According to the bill merging sub-rule, the bill information of the plurality of second target market management bills is used to merge the plurality of second target market management bills to obtain a corresponding second payment order.

[0028] In one embodiment, according to the bill settlement allocation sub-rule, the first payment resource data is used to settle and write off the first target market management bill in batches, including:

[0029] According to the bill settlement allocation sub-rule, the current batch of settlement and write-off of the first target market management bills is performed in the following manner using the current first payment resource data fed back by the merchant for the current first payment task:

[0030] Determine the current time difference between the current time and the write-off deadline of the first target market management bill, and the current remaining resource data value of the first target market management bill to be settled and written off;

[0031] Determine the priority weight of the first target market management bill according to the current time difference value and the current remaining resource data value of the first target market management bill;

[0032] According to the priority weight of the first target market management bill, the current first payment resource data is divided into a plurality of resource shares; wherein one resource share corresponds to one first target market management bill;

[0033] Utilize multiple resource shares to respectively perform settlement and write-off of the current batch of corresponding first target market management bills.

[0034] In one embodiment, the target market management bill includes at least one of the following: a market entry bill, a resource rental bill, a property management bill, a booth usage fee bill, and a loading and unloading service bill.

[0035] In one embodiment, after acquiring bill information, payment time limit data, and payment discount data of target market management bills according to bill identifiers of multiple target market management bills, and acquiring attribute information and behavior data of merchants according to merchant identifiers of merchants, the method further includes:

[0036] According to the preset verification rules, use the merchant information and billing information to verify the target market management bills;

[0037] When a target market management bill that fails verification is detected, an error message about the target market management bill is generated;

[0038] Send the error message to the merchant terminal.

[0039] In one embodiment, based on bill information, payment time limit data, payment discount data of multiple target market management bills, and attribute information and behavior data of merchants, multiple bill processing solutions matching the merchants are generated, including:

[0040] According to the bill information of the bills managed by the multiple target markets, a preset bill processing rule library is queried to determine multiple matching bill processing rules; wherein the preset bill processing rule library stores multiple preset bill processing rules, and one preset bill processing rule corresponds to at least one bill type;

[0041] Splice the bill information and bill processing rules of the corresponding target market management bill to obtain the spliced ​​bill processing rules; splice the merchant's attribute information and behavior data to obtain the merchant's associated data;

[0042] The preset decision model is used to process the spliced ​​bill processing rules and the merchant's associated data to determine multiple bill processing solutions that match the merchant.

[0043] In one embodiment, based on the feedback data, target processing rules for managing bills in multiple target markets selected by the target merchant are determined, including:

[0044] According to the feedback data, determine the recommendation plan selected by the merchant as the target recommendation plan;

[0045] Detect whether there is modified data for the target recommendation solution in the feedback data;

[0046] In the case where it is determined that there is modified data for the target recommended solution, detecting whether the modified data exceeds the authorized scope;

[0047] In the case where it is determined that the modified data exceeds the authorized scope, the modified data and the target recommendation scheme are sent to the market management terminal; wherein the market management terminal determines whether to accept the modified data for the target recommendation scheme;

[0048] Receive and respond to the confirmation acceptance instruction fed back by the market management terminal, and generate target processing rules for multiple target market management bills selected by the target merchants based on the modified data and the target recommendation plan.

[0049] In one embodiment, according to the target processing rule, by interacting with the merchant terminal, executing multiple first payment tasks and multiple second payment tasks in batches, and obtaining corresponding first payment resource data and second payment resource data, includes:

[0050] According to the target processing rules, interact with the merchant terminal in the following way to execute the first payment task of the current batch:

[0051] According to the target processing rules, monitor whether the execution conditions of the first payment task of the current batch are triggered;

[0052] In the case of determining the execution condition for triggering the first payment task of the current batch, calculating the current first payment resource data for the current first payment task according to the bill payment sub-rule and the first payment order;

[0053] Generate a current first sub-order to be paid for the current first payment task according to the current first payment resource data;

[0054] Sending the current first payment reminder information to the merchant terminal; wherein the current first payment reminder information carries at least the current first sub-order;

[0055] Receive the first payment resource data fed back by the merchant.

[0056] This specification also provides a market management bill processing device, including:

[0057] A receiving module, configured to receive a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least the bill identifiers of multiple target market management bills selected by the merchant, and the merchant identifier of the merchant;

[0058] An acquisition module, used to acquire bill information, payment time limit data, and payment discount data of target market management bills according to bill identifiers of multiple target market management bills; and to acquire attribute information and behavior data of merchants according to merchant identifiers of merchants;

[0059] A generation module, for generating multiple bill processing solutions matching the merchant as recommended solutions based on the bill information, payment time limit data, payment discount data, and merchant attribute information and behavior data of multiple target market management bills;

[0060] An interactive module, used to send the recommendation plan to the merchant terminal and receive merchant feedback data on the recommendation plan; wherein the merchant terminal is used to display the recommendation plan to the merchant;

[0061] A determination module, used to determine target processing rules for managing bills in multiple target markets selected by target merchants based on the feedback data; wherein the target processing rules at least include: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules;

[0062] The processing module is used to interact with the merchant terminal according to the target processing rules and process multiple target market management bills.

[0063] The present specification also provides a server, comprising a processor and a memory for storing processor executable instructions, wherein the processor implements relevant steps of the method for processing market management bills when executing the instructions.

[0064] The present specification also provides a computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the relevant steps of the method for processing the market management bill.

[0065] Based on the market management bill processing method, device and server provided in this specification, when merchants need to pay relevant market management fees to the market management party, they can select multiple target market management bills to be paid at the same time through the merchant terminal; and initiate a multi-bill merging processing request for multiple target market management bills. After receiving the multi-bill merging processing request, the server can first obtain and automatically determine multiple bill processing solutions that match the merchant and are more in line with the merchant's interests and habits based on the bill information, payment time limit data, payment discount data, and merchant attribute information and behavior data of the target market management bill, and the two different dimensions of time limit and discount of the market management bill, as recommended solutions for merchants to choose freely; then, based on the merchant's feedback data on the recommended solutions, determine the target processing rules for multiple target market management bills; and then, based on the target processing rules, multiple target market management bills can be processed by interacting with the merchant terminal. This makes it better adapted to market management payment scenarios, while taking into account payment time limits and payment discounts, enabling merchants to flexibly choose and use matching processing methods according to their own circumstances to efficiently and conveniently complete the payment of multiple market management bills, meet merchants' diverse payment needs, and improve merchants' interactive experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] In order to more clearly illustrate the embodiments of this specification, the drawings required for use in the embodiments will be briefly introduced below. The drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0067] Figure 1 It is a flowchart of a method for processing a market management bill provided by an embodiment of this specification;

[0068] Figure 2 It is a schematic diagram of an embodiment of a method for processing a market management bill provided by an embodiment of this specification, in a scenario example;

[0069] Figure 3 It is a schematic diagram of an embodiment of a method for processing a market management bill provided by an embodiment of this specification, in a scenario example;

[0070] Figure 4 It is a schematic diagram of an embodiment of a method for processing a market management bill provided by an embodiment of this specification, in a scenario example;

[0071] Figure 5 It is a schematic diagram of an embodiment of a method for processing a market management bill provided by an embodiment of this specification, in a scenario example;

[0072] Figure 6 It is a schematic diagram of an embodiment of a method for processing a market management bill provided by an embodiment of this specification, in a scenario example;

[0073] Figure 7 It is a schematic diagram of an embodiment of a method for processing a market management bill provided by an embodiment of this specification, in a scenario example;

[0074] Figure 8 It is a schematic diagram of the structure of a server provided by an embodiment of this specification;

[0075] Fig. 9 It is a schematic diagram of the structure of a device for processing market management bills provided by an embodiment of this specification;

[0076] Fig.10 It is a schematic diagram of an embodiment of a method for processing a market management bill provided by an embodiment of this specification, in a scenario example;

[0077] Fig.11 It is a schematic diagram of an embodiment of a method for processing a market management bill provided by an embodiment of this specification, in a scenario example;

[0078] Fig.12 It is a schematic diagram of an embodiment of a method for processing market management bills provided by an embodiment of this specification, in a scenario example. DETAILED DESCRIPTION

[0079] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0080] It should be noted that the user-related information and data involved in the embodiments of this specification are all information and data authorized by the user or fully authorized by relevant parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users or relevant parties to choose to authorize or refuse.

[0081] It should also be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0082] See also Figure 1 As shown, the embodiment of this specification provides a method for processing a market management bill. The method is specifically applied to the server side. When implemented specifically, the method may include the following contents:

[0083] S101: receiving a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least bill identifiers of multiple target market management bills selected by the merchant and a merchant identifier of the merchant;

[0084] S102: acquiring bill information, payment time limit data, and payment discount data of the target market management bill according to bill identifiers of the multiple target market management bills; and acquiring attribute information and behavior data of the merchant according to the merchant identifier of the merchant;

[0085] S103: generating multiple bill processing solutions matching the merchant as recommended solutions based on the bill information, payment time limit data, payment discount data, and merchant attribute information and behavior data of the multiple target market management bills;

[0086] S104: Sending the recommendation plan to the merchant terminal, and receiving merchant feedback data on the recommendation plan; wherein the merchant terminal is used to display the recommendation plan to the merchant;

[0087] S105: Determine target processing rules for managing bills in multiple target markets selected by the target merchant based on the feedback data; wherein the target processing rules at least include: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules;

[0088] S106: According to the target processing rules, interact with the merchant terminal to process multiple target market management bills.

[0089] The payment deadline data may specifically include payment deadline information for each market management bill. The payment deadline information may specifically be the time difference between the current time and the cancellation deadline of the market management bill.

[0090] Specifically, the market management party will set corresponding write-off deadlines for different types of market management bills according to the corresponding market management regulations. For example, the write-off deadline for property management bills is within one month of receiving the property management bill; that is, the merchant starts counting after receiving the property management bill, and needs to complete the payment of the bill within one month. Otherwise, if the write-off deadline is exceeded, the payment will not be completed in the normal way, and even overdue penalties will be incurred.

[0091] The above payment preferential data may specifically include payment preferential information for some market management bills and related payment preferential strategies. Among them, the payment preferential strategies may specifically include payment preferential conditions, preferential resource setting methods, preferential resource distribution methods, etc.

[0092] Specifically, in order to encourage merchants to pay relevant market management bills in a timely or early manner, market management parties sometimes set up and carry out corresponding payment preferential activities based on corresponding payment preferential strategies. For example, according to the first payment preferential strategy, merchants are encouraged to enjoy a 10 yuan discount if the cumulative payment settlement for the three types of bills, namely market entry bills, resource rental bills, and property management bills, reaches 100 yuan this month. For another example, according to the second payment preferential strategy, merchants are encouraged to enjoy a 15% discount if the cumulative payment settlement for the two types of bills, namely stall usage fee bills and loading and unloading service bills, reaches 200 yuan this week. It should be noted that based on different payment preferential strategies, different payment preferential activities can be mutually exclusive or can be superimposed on each other.

[0093] In specific implementation, according to the target bill processing, the server can merge multiple target market management bills selected by the merchant into one payment order, or two payment orders, or even three or more payment orders, to achieve the merging of multiple target market management bills; further, the server can also split the above payment order into multiple payments and settle them in a manner that takes into account the interests and personalized needs of the merchant and matches the merchant, to achieve the settlement of multiple target market management bills. In this way, the processing of multiple target market management bills can be completed better.

[0094] Based on the above embodiments, it can be better adapted to market management payment scenarios such as agricultural trade wholesale markets, while effectively taking into account merchant payment time limits and payment discounts, enabling merchants to flexibly choose matching processing methods according to their own circumstances to efficiently and conveniently complete the payment of multiple market management bills, thereby better meeting the merchants' diverse payment needs and improving the merchants' interactive experience.

[0095] In some embodiments, the server can be specifically understood as a server of a market payment management platform, wherein the server can be connected to a merchant terminal and a market management terminal via a wired or wireless method.

[0096] In this embodiment, the above-mentioned server may specifically include a background server applied to one side of the market payment management platform, which can realize functions such as data transmission and data processing. Specifically, the server may be, for example, an electronic device with data calculation, storage and network interaction functions. Alternatively, the server may also be a software program running in the electronic device to provide support for data processing, storage and network interaction. In this embodiment, the number of the servers is not specifically limited. The server may specifically be one server, or several servers, or a server cluster formed by several servers.

[0097] In this embodiment, the merchant terminal and the market management terminal may include front ends applied to the merchant and the market management side, respectively, which can realize functions such as data collection and data transmission. Specifically, the merchant terminal and the market management terminal may be electronic devices such as desktop computers, tablet computers, laptop computers, and smart phones. Alternatively, the merchant terminal and the market management terminal may also be software applications that can run in the above electronic devices. For example, it may be a market management payment APP running on a smart phone.

[0098] In specific implementation, the market management party can upload the market management bills to be paid by the merchants in the market it is responsible for to the market management payment platform. The market management payment platform can distribute the above market management bills to the merchant terminals held by the corresponding merchants based on the bill information of the market management bills.

[0099] The merchant terminal receives the above market management bill; and reminds and displays the above market management bill to the merchant.

[0100] For the market management bills reminded and displayed by the merchant terminal, merchants can pay each market management bill separately by performing corresponding operations on the merchant terminal according to their own circumstances and individual preferences; they can also perform corresponding operations on the merchant terminal to select multiple market management bills to merge, and then make statistics and payment on the merged market management bills; they can also perform corresponding operations on the merchant terminal to select multiple market management bills to merge, set up multiple installments, and then make multiple payments in batches.

[0101] This can better meet the diverse payment needs of merchants.

[0102] In some embodiments, the above-mentioned method for processing market management bills can be specifically applied to agricultural trade wholesale markets, building materials markets, home appliance markets, and the like.

[0103] Of course, it should be noted that the above-listed markets are only a schematic illustration. In specific implementation, according to specific circumstances and processing requirements, the above-mentioned market management bill processing method can be further promoted and applied to other types of markets involving market management payment. This specification does not limit this.

[0104] In some embodiments, the above-mentioned market management bill can be specifically understood as a payment bill involving market management that requires merchants to pay fees.

[0105] During specific implementation, the merchant terminal can display the current market management bill to be paid to the merchant through the market management payment interface.

[0106] Merchants can select multiple market management bills that they want to merge in the above market management payment interface according to their own circumstances; and initiate a merge operation for the selected multiple market management bills.

[0107] Correspondingly, the merchant terminal can receive and respond to the merchant's relevant operations through the above-mentioned market management payment interface, determine the market management bill selected by the merchant as the target market management bill; and obtain the bill identifier of the target market management bill (for example, the bill number, etc.), and the merchant identifier of the merchant (for example, the merchant name, the mobile phone number used by the merchant when registering, the merchant number, etc.); automatically generate a corresponding multi-bill merging processing request; and then send the multiple merging processing requests to the server to request merging of the multiple target market management bills selected by the merchant.

[0108] In some embodiments, the target market management bill may specifically include at least one of the following: a market entry bill, a resource rental bill, a property management bill, a booth usage fee bill, a loading and unloading service bill, and the like.

[0109] It should be noted that the target market management bills listed above are only a schematic illustration. In specific implementation, other types of market management bills such as health fee bills and heating fee bills may also be included according to the specific market and specific payment conditions. This specification does not limit this.

[0110] Based on the above embodiments, it can be better adapted to the market management payment scenario and comprehensively and effectively handle the payment of various market management bills in this scenario.

[0111] In some embodiments, after receiving a multi-bill merging processing request initiated by a merchant terminal, the server can first parse the multi-bill merging processing request, extract the billing identifiers of multiple target market management bills, and use the merchant identifier of the merchant; then query the bill database based on the bill identifier to obtain the billing information of the target market management bill; at the same time, query the merchant database and the merchant's historical behavior records based on the merchant identifier to obtain the merchant's attribute information and behavior data.

[0112] The bill information of the target market management bill may specifically include at least one of the following: bill identification, bill type, generation time, merchant identification, booth information, payment mode, etc.

[0113] Specifically, the stall information may be the location information or number of the stall (or counter) of the merchant in the market indicated by the target market management bill. The payment mode may be the fee period covered by the target market management bill, for example, one month's fee or one year's fee.

[0114] The above-mentioned merchant attribute information may specifically include at least one of the following: merchant identification, merchant preference, merchant tag, merchant business category, etc.

[0115] Specifically, the merchant preferences may include: the merchant's customary payment time, the merchant's customary merging method, the merchant's customary payment method, etc. In specific implementation, the server may regularly obtain and update the merchant preferences based on the merchant's historical payment records within the latest reference time period.

[0116] The above-mentioned merchant tags may include: merchant credit tags, etc. In specific implementation, the server may cooperate with financial institutions such as banks; regularly obtain the merchant's first credit evaluation information based on the financial transaction behavior of the financial institution; at the same time, the server may also obtain and calculate the merchant's second credit evaluation information based on market management payment according to the merchant's historical payment records within the latest reference time period; re-evaluate the merchant's creditworthiness by combining the first credit evaluation information and the second credit evaluation information; and update the merchant's credit tag according to the merchant's latest creditworthiness.

[0117] The above-mentioned merchant behavior data may specifically include at least one of the following: merchant historical payment records, merchant and market management interaction records, merchant historical business records, etc.

[0118] In some embodiments, after acquiring the bill information, payment time limit data, and payment discount data of the target market management bill according to the bill identifications of the multiple target market management bills, and acquiring the attribute information and behavior data of the merchant according to the merchant identification, refer to Figure 2 As shown, when the method is implemented specifically, it may also include the following contents:

[0119] S1: Verify the target market management bills using merchant information and bill information according to preset verification rules;

[0120] S2: when a target market management bill that fails verification is detected, an error message about the target market management bill is generated;

[0121] S3: Send the error message to the merchant terminal.

[0122] When conducting specific verification, the electronic account used for payment provided by the merchant when registering can be queried based solely on the merchant information; and the electronic account can be checked to see if it is in a frozen state; when it is determined that the electronic account is in a frozen state, it is determined that the verification has failed.

[0123] You can also use merchant information and billing information together. First, determine the relevant stall information based on the billing information; then, based on the stall information and merchant information, query the merchant database to check whether the stall indicated by the stall information is the stall used by the merchant; if not, it is determined that the verification has failed.

[0124] It is also possible to detect whether the target market management bill is overdue based on the payment time limit data of the target market management bill; when it is determined that at least one target market management bill is overdue, it is determined that the verification has failed.

[0125] In specific implementation, when it is determined that multiple target market management bills have been verified, subsequent data processing can be triggered. On the contrary, when a target market management bill that has not passed the verification is detected, subsequent data processing can be suspended, and an error message about the target market management bill can be generated. The error message at least carries the bill identifier of the target market management bill that has not passed the verification.

[0126] In specific implementation, the server may send the error prompt to the merchant terminal. The merchant terminal displays the error prompt to the merchant. Accordingly, the merchant may, according to the error prompt, remove the target market management bills that have not passed the verification from the previously selected multiple target market management bills through the market management payment interface to obtain the revised multiple target market management bills. Accordingly, the server may perform subsequent data processing on the revised multiple target market management bills.

[0127] For target market management bills that have not passed the verification, merchants can select the supplementary payment icon through the market management payment interface to trigger the supplementary payment processing for the target market management bill.

[0128] Based on the above embodiment, the target market management bills can be verified in advance according to preset verification rules using merchant information and bill information, so that data processing of multiple target market management bills can be completed relatively more accurately later.

[0129] In some embodiments, see Figure 3 As shown, the above-mentioned bill information, payment time limit data, payment discount data, and merchant attribute information and behavior data of multiple target market management bills are used to generate multiple bill processing solutions that match the merchant. When implemented specifically, the following contents may be included:

[0130] S1: According to bill information of multiple target market management bills, query a preset bill processing rule library to determine multiple matching bill processing rules; wherein the preset bill processing rule library stores multiple preset bill processing rules, and one preset bill processing rule corresponds to at least one bill type;

[0131] S2: splicing the bill information and bill processing rules of the corresponding target market management bill to obtain the spliced ​​bill processing rules; splicing the merchant's attribute information and behavior data to obtain the merchant's associated data;

[0132] S3: Use the preset decision model to process the spliced ​​bill processing rules and the merchant's associated data to determine multiple bill processing solutions that match the merchant.

[0133] Based on the above embodiments, factors in multiple dimensions such as payment time limit, payment discounts, and merchant behavior preferences can be comprehensively considered to automatically and accurately determine a bill processing solution that is likely to meet the merchant's needs as a recommended solution for the merchant to choose, thereby enabling the merchant to obtain a relatively better interactive experience.

[0134] The preset bill processing rule library may store a plurality of preset bill processing rules, and each preset bill processing rule corresponds to at least one bill type.

[0135] Before specific implementation, the market management party may set corresponding bill processing rules for each type of market management bill through the market management terminal according to relevant market management rules as corresponding preset bill processing rules.

[0136] The above-mentioned preset bill processing rules may specifically include limitations on merging operations, settlement operations, preferential operations, and time limit operations for bills of the corresponding type.

[0137] The above-mentioned preset decision model can be specifically understood as a neural network model that uses a large amount of sample data in advance and, through deep reinforcement learning, is trained to automatically combine and use multiple bill processing rules based on the input spliced ​​bill processing rules and the merchant's associated data to generate and output a bill processing solution that meets the merchant's requirements.

[0138] Specifically, when using the preset decision model to process the spliced ​​bill processing rules and the merchant's associated data, the model will combine the limited elements of the various types of bill processing rules involved based on the trained and mastered knowledge, and use the payment time limit data as a constraint condition to jointly perform the optimization solution of the preferential resource data value calculated based on the payment preferential data and the merchant satisfaction calculated based on the merchant's associated data, so as to converge to obtain multiple bill processing solutions as recommended solutions. Then the server can send the above recommended solutions to the merchant terminal, and the merchant terminal will display the recommended solutions to the merchant.

[0139] Accordingly, the merchant can select one of the recommended solutions that best meets his needs as the target recommended solution by operating the merchant terminal. Furthermore, the merchant can directly accept the target recommended solution; or modify it based on the target recommended solution according to his actual needs, and complete the feedback on the displayed recommended solution. The merchant terminal can receive the above feedback data; and send the above feedback data to the server.

[0140] In some embodiments, see Figure 4 As shown, the target processing rules for managing bills in multiple target markets selected by the target merchant are determined based on the feedback data. When implemented specifically, the following contents may be included:

[0141] S1: According to the feedback data, determine the recommendation plan selected by the merchant as the target recommendation plan;

[0142] S2: Detect whether there is modified data for the target recommendation solution in the feedback data;

[0143] S3: When it is determined that there is modified data for the target recommendation solution, detecting whether the modified data exceeds the authorization scope;

[0144] S4: When it is determined that the modified data exceeds the authorized scope, the modified data and the target recommendation scheme are sent to the market management terminal; wherein the market management terminal determines whether to accept the modified data for the target recommendation scheme;

[0145] S5: Receive and respond to the confirmation acceptance instruction fed back by the market management terminal, and generate target processing rules for multiple target market management bills selected by the target merchants based on the modified data and the target recommendation plan.

[0146] Among them, the above-mentioned modification data may specifically include at least one of the following: modification data for payment channels, modification data for the total number of batches of payments in batches, modification data for the interval time between adjacent batches of payments in batches, modification data for the merging combination method of bill merging, modification data for resource data of a single batch payment, modification data for the allocation ratio of resource data when settling and writing off different bills of the same batch, etc.

[0147] Based on the above embodiments, the server can accurately determine target processing rules for managing bills for multiple target markets based on the feedback data from the merchants, so as to better meet the diversified business needs of the merchants.

[0148] In specific implementation, after determining a target recommendation plan based on feedback data, if no modification data for the target recommendation plan is detected, the server can directly call the rule engine to automatically generate corresponding target processing rules based on the target recommendation plan.

[0149] The rule engine can be specifically understood as a component that can be embedded in an application. Before implementation, the processing rules can be separated from the code program, and the processing rules can be written using predefined semantic modules. It will parse the specific plan and form the processing rules, without the need to write code to implement rule control. During implementation, the rule engine will load the configured processing rules into memory, allowing the system to perform corresponding data processing on multiple target market management bills according to the established processing rules.

[0150] In specific implementation, when the server detects the existence of modified data for the target recommendation plan, it can first detect whether the modified data exceeds the authorization scope based on the preset modification permission scope; if it is determined that it does not exceed the authorization scope, it can modify the target recommendation plan based on the modified data to obtain a modified recommendation plan; and then call the rule engine to automatically generate the corresponding target processing rules based on the modified recommendation plan.

[0151] On the contrary, if it is determined that the authorization scope is exceeded, the modified data and the target recommendation plan can be sent to the market management terminal for specific review. While sending the modified data and the target recommendation plan to the market management terminal, the merchant's merchant ID and the merchant's contact information can also be sent to the market management terminal. The market management party can manually review and determine whether to accept the merchant's modified data based on the merchant's modified data displayed by the market management terminal and the target recommendation plan selected by the merchant; alternatively, the market management party can also contact the merchant for further negotiation and discussion to determine the final target recommendation plan. The market management terminal returns the final target recommendation plan to the server so that the server can generate corresponding target processing rules based on the final target recommendation plan.

[0152] In some embodiments, see Figure 5 As shown, the above interacts with the merchant terminal according to the target processing rules to process multiple target market management bills. When implemented specifically, the following contents may be included:

[0153] S1: According to the bill merging sub-rule, a first target market management bill among multiple target market management bills is merged to obtain a corresponding first payment order; a second target market management bill among multiple target market management bills is merged to obtain a corresponding second payment order; wherein the payment time limit data and / or payment discount data of the first target market management bill associated with the first payment order matches, and the payment time limit data and / or payment discount data of the second target market management bill associated with the second payment order matches;

[0154] S2: generating, according to the bill payment sub-rule, a plurality of first payment tasks regarding the first payment order and a plurality of second payment tasks regarding the second payment order;

[0155] S3: According to the target processing rule, by interacting with the merchant terminal, multiple first payment tasks and multiple second payment tasks are executed in batches to obtain corresponding first payment resource data and second payment resource data;

[0156] S4: According to the bill settlement allocation sub-rule, the first target market management bills are settled and written off in batches using the first payment resource data; and the second target market management bills are settled and written off in batches using the second payment resource data.

[0157] Among them, the first reference time can be set by the market management party through the market management terminal.

[0158] Based on the above embodiment, the server can automatically complete operations such as bill merging, batch payment, batch settlement and write-off according to the target processing rules by interacting with the merchant terminal, thereby assisting the merchant to complete the data processing of multiple bills efficiently and conveniently.

[0159] In some embodiments, the above-mentioned target processing rules may specifically include: bill merging sub-rules, bill payment sub-rules, bill settlement allocation sub-rules, etc.

[0160] During specific implementation, according to different scenarios and based on the bill merging sub-rules, multiple target management bills can be merged into one payment order (for example, the first payment order); they can also be merged into two payment orders (for example, the first payment order and the second payment order); they can also be merged into three payment orders (for example, the first payment order, the second payment order, and the third payment order), etc.

[0161] The payment time limit data and / or payment discount data of different target market management bills belonging to the same payment order are matched with each other. For the target market management bills included in the same payment order, a unified payment settlement can be performed.

[0162] Specifically, for example, when all target market management bills are far away from the settlement deadline (for example, the time difference between the current time and its settlement deadline is greater than or equal to the first reference time), that is, there is no target market management bill that needs to be settled and written off within a short time (for example, within 1 week); and there is no payment preferential activity, or there is only one payment preferential activity, or there are multiple non-mutually exclusive payment preferential activities, all target market management bills can be merged into one payment order, recorded as the first payment order.

[0163] For another example, when some target market management bills are closer to the deadline for verification (for example, the time difference between the current time and the deadline for verification is less than the first reference time); and there is no payment preferential activity, or there is only one payment preferential activity, or there are multiple non-mutually exclusive payment preferential activities, all target market management bills can be merged into two payment orders, namely: the first payment order and the second payment order. The target market management bills included in the first payment order can be bills closer to the deadline for verification, that is, bills whose payment time limit data match each other and whose payment preferential data match each other; the target market management bills included in the second payment order can be bills closer to the deadline for verification, that is, bills whose payment time limit data match each other and whose payment preferential data match each other.

[0164] For another example, when some target market management bills have a shorter deadline to be written off; and there are multiple payment preferential activities, some of which are mutually exclusive, all target market management bills can be combined into three payment orders, namely: the first payment order, the second payment order, and the third payment order. Among them, the target market management bills included in the first payment order can be bills with a shorter deadline to be written off; the target market management bills included in the second payment order can be bills with a longer deadline to be written off and participate in mutually exclusive first-category payment preferential activities or do not participate in preferential activities; the target market management bills included in the third payment order can be the remaining bills with a longer deadline to be written off and participate in mutually exclusive second-category payment preferential activities.

[0165] According to the above idea, for more complicated situations, four payment orders or even more payment orders can be merged according to the bill merging sub-rules.

[0166] In specific implementation, for different payment orders, corresponding multiple payment tasks can be generated and established according to the bill payment sub-rules, and the corresponding task execution time can be set. Then, the corresponding payment tasks can be automatically triggered in batches according to the task execution time, so that merchants can pay the corresponding payment resource data in batches on time according to the finalized plan and complete the batch payment.

[0167] The above-mentioned payment resource data may specifically be fund data, points data, coupon data, etc.

[0168] In addition, according to relevant rules, the execution status of payment tasks in each batch can be automatically followed up, and merchants can be reminded in a timely manner to avoid losses caused by merchants' negligence in missing a batch of payments.

[0169] During specific implementation, for each batch of payment resource data received, the bill characteristics of bills managed by different target markets in the same payment order can be distinguished based on the bill settlement allocation sub-rules, and the corresponding payment resource data can be automatically and reasonably allocated to complete specific bill settlement and write-off, thereby avoiding losses to merchants' interests.

[0170] In some embodiments, after merging the first target market management bill among the multiple target market management bills according to the bill merging sub-rule to obtain the corresponding first payment order; and merging the second target market management bill among the multiple target market management bills to obtain the corresponding second payment order, the method may further include:

[0171] The remaining third target market management bills in the multiple target market management bills are combined to obtain a corresponding third payment order.

[0172] Based on the above embodiment, multiple target market management bills can be accurately merged into three different payment orders according to the bill merging sub-rules, so that corresponding payment tasks and settlement verification can be performed for different payment orders separately, thereby obtaining relatively better processing results.

[0173] In some embodiments, according to the bill merging sub-rule, merging the first target market management bill in the multiple target market management bills to obtain the corresponding first payment order may include the following contents during specific implementation:

[0174] S1: According to the bill merging sub-rule and the payment time limit data of the target market management bill, the target market management bill whose time difference between the verification deadline and the current time is less than the first reference time is selected from multiple target market management bills as candidate target market management bills;

[0175] S2: According to the bill merging sub-rule and the payment preferential data of the candidate market management bills, a candidate target market management bill without mutually exclusive preferential treatment is selected from multiple candidate target market management bills as the first target market management bill;

[0176] S3: According to the bill merging sub-rule, the bill information of the multiple first target market management bills is used to merge the multiple first target market management bills to obtain the corresponding first payment order.

[0177] During the specific screening, on the premise that candidate target market management bills with no mutually exclusive preferential treatment are screened out from multiple candidate target market management bills, candidate target market management bills with a total number of resources that meet preferential conditions can be screened out as much as possible as the first target market management bill. For example, M candidate target market management bills with a total number of resources that just reaches 100 can be screened out as a group of first target market management bills to establish the first first payment order. Then, N candidate target market management bills with a total number of resources that just reaches 100 can be screened out from the remaining bills as another group of second target market management bills to establish the second first payment order, etc. And so on, finally the remaining bills are divided into a group to establish the last first payment order.

[0178] Based on the above embodiment, the first target market management bill that meets the requirements can be more accurately determined from multiple target market management bills according to the bill merging sub-rule, and then combined to obtain a first payment order with better effect.

[0179] In some embodiments, according to the bill merging sub-rule, merging the second target market management bills in the multiple target market management bills to obtain the corresponding second payment order may include the following contents during specific implementation:

[0180] S1: determining a first remaining bill other than a first target market management bill from among a plurality of target market management bills;

[0181] S2: according to the bill merging sub-rule and the payment preferential data of the first remaining bills, bills with mutually exclusive preferential treatment are eliminated from the plurality of first remaining bills to obtain a second target market management bill;

[0182] S3: According to the bill merging sub-rule, the bill information of the plurality of second target market management bills is used to merge the plurality of second target market management bills to obtain a corresponding second payment order.

[0183] Based on the above embodiment, according to the bill merging sub-rule, the second target market management bill that meets the requirements can be more accurately determined from multiple target market management bills for combination, and the second payment order with better effect can be obtained by merging.

[0184] In some embodiments, according to the target processing rule, by interacting with the merchant terminal, multiple first payment tasks and multiple second payment tasks are executed in batches to obtain corresponding first payment resource data and second payment resource data. For specific implementation, refer to Figure 6 As shown, it may include: according to the target processing rule, interacting with the merchant terminal in the following manner to execute the first payment task of the current batch:

[0185] S1: monitor whether the execution condition of the first payment task of the current batch is triggered according to the target processing rule;

[0186] S2: when determining the execution condition for triggering the first payment task of the current batch, calculate the current first payment resource data for the current first payment task according to the bill payment sub-rule and the first payment order;

[0187] S3: generating a current first sub-order to be paid for the current first payment task according to the current first payment resource data;

[0188] S4: Sending the current first payment reminder information to the merchant terminal; wherein the current first payment reminder information carries at least the current first sub-order;

[0189] S5: Receive the first payment resource data fed back by the merchant.

[0190] Based on the above embodiment, for different payment orders, the corresponding payment tasks can be automatically executed in batches according to the above method and target processing rules, and the payment resource data fed back by the merchant can be received to smoothly complete the payment tasks of the corresponding batches, thereby fully completing the payment for the payment order.

[0191] During specific implementation, the server can monitor in real time according to the target processing rules whether the time interval from the start time of the first payment task of the previous batch to the current time reaches the trigger duration (for example, 1 month); if it is monitored that the time interval reaches the trigger duration, the execution conditions for triggering the first payment task of the current batch are determined.

[0192] The server may also determine the execution plan schedule for each batch of first payment tasks for the first payment order according to the processing rules; and determine the execution plan time for the first payment task of the current batch according to the execution plan schedule; and then monitor whether the current time is the execution plan time for the first payment task of the current batch; if so, determine the execution conditions for triggering the first payment task of the current batch.

[0193] In specific implementation, after sending the current first payment reminder information to the merchant terminal, the first payment resource data fed back by the merchant within the second reference time corresponding to the merchant may also be monitored.

[0194] The second reference time may be determined in the following manner: obtaining and determining the payment cycle of the merchant after being reminded based on the merchant's behavior data; and determining the second reference time for the merchant based on the payment cycle.

[0195] When it is detected that the first payment resource data is not received within the second reference time, a secondary reminder message regarding the first payment reminder message can be generated; and multiple contact methods of the merchant (including email, mobile phone number, social media, etc.) are determined; based on multiple contact methods, a secondary reminder message is sent to the merchant at the same time to more effectively reach and remind the merchant.

[0196] If the first payment resource data is not received two days before the specified deadline, a reminder can be sent to the market management terminal so that the market management party can arrange market management personnel to go to the merchant's booth to remind the merchant in time, thereby effectively avoiding losses caused by the merchant's forgetfulness.

[0197] In some embodiments, the first payment resource data is used to settle and write off the first target market management bills in batches according to the bill settlement allocation sub-rule. Figure 7 As shown, according to the bill settlement allocation sub-rule, the current batch of settlement and write-off of the first target market management bills can be performed in the following manner using the current first payment resource data fed back by the merchant for the current first payment task:

[0198] S1: Determine the current time difference between the current time and the write-off deadline of the first target market management bill, and the current remaining resource data value to be settled and written off of the first target market management bill;

[0199] S2: determining the priority weight of the first target market management bill according to the current time difference value and the current remaining resource data value of the first target market management bill;

[0200] S3: dividing the current first payment resource data into a plurality of resource shares according to the priority weight of the first target market management bill; wherein one resource share corresponds to one first target market management bill;

[0201] S4: Use multiple resource shares to respectively perform settlement and write-off of the current batch of corresponding first target market management bills.

[0202] Based on the above embodiment, for different target market management bills to be settled and written off in the same batch and the same payment order, the payment resource data of the current batch can be finely and accurately allocated according to the bill settlement allocation sub-rules to intelligently and reasonably complete the settlement and writing off of related bills.

[0203] During specific implementation, according to the bill settlement allocation sub-rules, for bills that are relatively close to the write-off deadline and have relatively large remaining resource data values, a relatively large priority weight can be set so that they can be allocated a relatively larger share of resources in the settlement and write-off of the current batch, thereby completing the complete settlement and write-off of the bill relatively faster and avoiding damage to the rights and interests of merchants due to exceeding the write-off deadline.

[0204] In addition, during the specific implementation, according to the bill settlement allocation sub-rules, it is also possible to simultaneously obtain and use information such as the bill type and importance of the target market management bill as an auxiliary reference to more accurately determine the priority weight of each target market management bill.

[0205] In some embodiments, during specific implementation, the target processing rules finally determined by the merchant and the market management party, as well as the payment orders merged based on the target processing rules, and the batch processing results of the payment tasks for each payment order can be stored separately in the corresponding blocks in the blockchain for subsequent backtracking queries.

[0206] As can be seen from the above, based on the method for processing market management bills provided in the embodiments of this specification, when merchants need to pay relevant market management fees to the market management party, they can select multiple target market management bills to be paid through the merchant terminal at the same time, and initiate a multi-bill merging processing request for multiple target market management bills. After receiving the multi-bill merging processing request, the server can first obtain and automatically determine multiple bill processing solutions that match the merchant based on the bill information, payment time limit data, payment discount data, and merchant attribute information and behavior data of the target market management bill, and the two different dimensions of time limit and discount of the market management bill as recommended solutions for the merchant to choose; then, based on the merchant's feedback data on the recommended solutions, determine the target processing rules for multiple target market management bills; and then, according to the target processing rules, interact with the merchant terminal to process multiple target market management bills. This makes it better adapted to market management payment scenarios. While effectively taking into account merchant payment time limits and payment discounts, it enables merchants to flexibly choose and use matching processing methods according to their own circumstances to efficiently and conveniently complete the payment of multiple market management bills, meet merchants' diverse payment needs, and improve merchants' interactive experience.

[0207] This specification embodiment provides a server, referring to Figure 8 The server includes a network communication port 801, a processor 802 and a memory 803, and the above structures are connected through internal cables so that each structure can perform specific data interaction.

[0208] Among them, the network communication port 801 can be specifically used to receive a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least the bill identifiers of multiple target market management bills selected by the merchant, and the merchant identifier of the merchant.

[0209] The processor 802 can be specifically used to obtain bill information, payment time limit data, and payment discount data of target market management bills based on bill identifiers of multiple target market management bills; and obtain attribute information and behavior data of the merchant based on the merchant identifier of the merchant; generate multiple bill processing solutions matching the merchant as recommended solutions based on the bill information, payment time limit data, payment discount data of multiple target market management bills, and attribute information and behavior data of the merchant; send the recommended solutions to the merchant terminal, and receive feedback data from the merchant on the recommended solutions; wherein the merchant terminal is used to display the recommended solutions to the merchant; determine target processing rules for multiple target market management bills selected for the target merchant based on the feedback data; wherein the target processing rules include at least: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules; interact with the merchant terminal based on the target processing rules to process multiple target market management bills.

[0210] The memory 803 may be specifically used to store corresponding instruction programs, target processing rules and other related data.

[0211] Based on the above method, the relevant structural performance of the server can be effectively utilized, the data processing speed of the electronic equipment can be improved, and the data processing of the market management bill can be efficiently realized.

[0212] In this embodiment, the network communication port 801 can be a virtual port that is bound to different communication protocols so that different data can be sent or received. For example, the network communication port can be a port responsible for web data communication, a port responsible for FTP data communication, or a port responsible for email data communication. In addition, the network communication port can also be a physical communication interface or communication chip. For example, it can be a wireless mobile network communication chip, such as GSM, CDMA, etc.; it can also be a Wifi chip; it can also be a Bluetooth chip.

[0213] In this embodiment, the processor 802 may be implemented in any appropriate manner. For example, the processor may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) executable by the (micro)processor, a logic gate, a switch, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, etc. This specification does not limit this.

[0214] In this embodiment, the memory 803 may include multiple levels. In a digital system, anything that can store binary data can be a memory; in an integrated circuit, a circuit with a storage function but no physical form is also called a memory, such as RAM, FIFO, etc.; in a system, a storage device with a physical form is also called a memory, such as a memory stick, TF card, etc.

[0215] The embodiment of the present specification also provides a computer-readable storage medium based on the above-mentioned market management bill processing method, wherein the computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed, the following are achieved: receiving a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least the bill identifiers of multiple target market management bills selected by the merchant, and the merchant identifier of the merchant; obtaining the bill information, payment time limit data, and payment discount data of the target market management bills according to the bill identifiers of the multiple target market management bills; and obtaining the attribute information and behavior data of the merchant according to the merchant identifier of the merchant; and obtaining the multi-bill merging processing request according to the multiple target market management bills. The method comprises the following steps: generating a plurality of bill processing schemes matching the merchant based on the bill information of the market management bill, payment time limit data, payment discount data, and attribute information and behavior data of the merchant, as recommended schemes; sending the recommended schemes to the merchant terminal, and receiving feedback data from the merchant on the recommended schemes; wherein the merchant terminal is used to display the recommended schemes to the merchant; determining target processing rules for multiple target market management bills selected for the target merchant based on the feedback data; wherein the target processing rules include at least: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules; and interacting with the merchant terminal based on the target processing rules to process multiple target market management bills.

[0216] In this embodiment, the storage medium includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), a cache, a hard disk (HDD), or a memory card. The memory may be used to store computer program instructions. The network communication unit may be an interface for network connection communication set in accordance with the standard specified by the communication protocol.

[0217] In this embodiment, the functions and effects specifically implemented by the program instructions stored in the computer-readable storage medium can be explained in comparison with other implementations and will not be described in detail here.

[0218] The embodiment of the present specification also provides a computer program product, which at least includes a computer program, and when the computer program is executed by a processor, the following method steps are implemented: receiving a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least the bill identifiers of multiple target market management bills selected by the merchant, and the merchant identifier of the merchant; obtaining the bill information, payment time limit data, and payment discount data of the target market management bills according to the bill identifiers of the multiple target market management bills; and obtaining the attribute information and behavior data of the merchant according to the merchant identifier of the merchant; obtaining the attribute information and behavior data of the merchant according to the bill information, payment time limit data, and payment discount data of the multiple target market management bills; and obtaining the attribute information and behavior data of the merchant according to the merchant identifier of the merchant; obtaining the attribute information and behavior data of the multiple target market management bills according to the bill information, payment time limit data, and payment discount data of the multiple target market management bills; and obtaining the attribute information and behavior data of the merchant according to the bill information, payment time limit data, and payment discount data of the multiple target market management bills. The method comprises the following steps: generating a plurality of bill processing schemes matching the merchant based on the payment time limit data, payment discount data, and the attribute information and behavior data of the merchant, as recommended schemes; sending the recommended schemes to the merchant terminal, and receiving the merchant's feedback data on the recommended schemes; wherein the merchant terminal is used to display the recommended schemes to the merchant; determining target processing rules for managing bills of multiple target markets selected for the target merchant based on the feedback data; wherein the target processing rules include at least: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules; and interacting with the merchant terminal based on the target processing rules to process multiple target market management bills.

[0219] See also Fig. 9 As shown, the embodiment of this specification also provides a device for processing market management bills, which may specifically include the following structural modules:

[0220] The receiving module 901 may be specifically configured to receive a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least the bill identifiers of the multiple target market management bills selected by the merchant, and the merchant identifier of the merchant;

[0221] The acquisition module 902 may be specifically used to acquire bill information, payment time limit data, and payment discount data of the target market management bill according to bill identifiers of multiple target market management bills; and acquire attribute information and behavior data of the merchant according to the merchant identifier of the merchant;

[0222] The generating module 903 may be used to generate multiple bill processing solutions matching the merchant as recommended solutions based on the bill information, payment time limit data, payment discount data, and merchant attribute information and behavior data of multiple target market management bills;

[0223] The interaction module 904 may be specifically used to send the recommendation plan to the merchant terminal and receive the merchant's feedback data on the recommendation plan; wherein the merchant terminal is used to display the recommendation plan to the merchant;

[0224] The determination module 905 may be specifically used to determine target processing rules for managing bills in multiple target markets selected by the target merchant based on the feedback data; wherein the target processing rules at least include: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules;

[0225] The processing module 906 may be specifically configured to interact with the merchant terminal according to the target processing rules to process multiple target market management bills.

[0226] In some embodiments, when the above-mentioned processing module 906 is specifically implemented, it can interact with the merchant terminal according to the target processing rules in the following manner to process multiple target market management bills: according to the bill merging sub-rule, merge the first target market management bill in the multiple target market management bills to obtain the corresponding first payment order; merge the second target market management bill in the multiple target market management bills to obtain the corresponding second payment order; wherein the payment time limit data and / or payment discount data of the first target market management bill associated with the first payment order match, and the payment time limit data and / or payment discount data of the second target market management bill associated with the second payment order match; according to the bill payment sub-rule, generate multiple first payment tasks for the first payment order and multiple second payment tasks for the second payment order; according to the target processing rules, by interacting with the merchant terminal, execute multiple first payment tasks and multiple second payment tasks in batches to obtain corresponding first payment resource data and second payment resource data; according to the bill settlement allocation sub-rule, use the first payment resource data to settle and write off the first target market management bill in batches; use the second payment resource data to settle and write off the second target market management bill in batches.

[0227] In some embodiments, after the first target market management bill among multiple target market management bills is merged to obtain a corresponding first payment order according to the bill merging sub-rule; and the second target market management bills among multiple target market management bills are merged to obtain a corresponding second payment order, when the device is specifically implemented, it can also be used to: merge the remaining third target market management bills among the multiple target market management bills to obtain a corresponding third payment order.

[0228] In some embodiments, when the above-mentioned processing module 906 is implemented, the first target market management bill among multiple target market management bills can be merged according to the bill merging sub-rule to obtain the corresponding first payment order in the following manner: according to the bill merging sub-rule and the payment time limit data of the target market management bill, the target market management bill whose time difference between the verification deadline and the current time is less than the first reference time is screened out from the multiple target market management bills as the candidate target market management bills; according to the bill merging sub-rule and the payment discount data of the candidate market management bills, the candidate target market management bills without mutually exclusive discounts are screened out from the multiple candidate target market management bills as the first target market management bill; according to the bill merging sub-rule, the bill information of multiple first target market management bills is used to merge the multiple first target market management bills to obtain the corresponding first payment order.

[0229] In some embodiments, when the above-mentioned processing module 906 is implemented, the second target market management bills in multiple target market management bills can be merged according to the bill merging sub-rule to obtain the corresponding second payment order, including: determining the first remaining bills other than the first target market management bill in the multiple target market management bills; according to the bill merging sub-rule and the payment discount data of the first remaining bills, eliminating the bills with mutually exclusive discounts from the multiple first remaining bills to obtain the second target market management bill; according to the bill merging sub-rule, using the bill information of multiple second target market management bills, merging the multiple second target market management bills to obtain the corresponding second payment order.

[0230] In some embodiments, when the above-mentioned processing module 906 is implemented, the current batch of settlement and write-off of the first target market management bills can be performed according to the bill settlement allocation sub-rules and in the following manner using the current first payment resource data fed back by the merchant for the current first payment task: determine the current time difference between the current time and the write-off deadline of the first target market management bill, and the current remaining resource data value of the first target market management bill to be settled and written off; determine the priority weight of the first target market management bill according to the current time difference and the current remaining resource data value of the first target market management bill; divide the current first payment resource data into multiple resource shares according to the priority weight of the first target market management bill; wherein one resource share corresponds to one first target market management bill; and use multiple resource shares to respectively perform settlement and write-off of the current batch of corresponding first target market management bills.

[0231] In some embodiments, the target market management bill may specifically include at least one of the following: a market entry bill, a resource rental bill, a property management bill, a booth usage fee bill, a loading and unloading service bill, etc.

[0232] In some embodiments, after obtaining the bill information, payment time limit data, and payment discount data of the target market management bill based on the bill identifiers of multiple target market management bills; and obtaining the attribute information and behavior data of the merchant based on the merchant identifier of the merchant, the device, when implemented specifically, can also be used to: verify the target market management bill using merchant information and bill information according to preset verification rules; when a target market management bill that fails the verification is detected, generate an error prompt about the target market management bill; and send the error prompt to the merchant terminal.

[0233] In some embodiments, when the above-mentioned generation module 903 is implemented, it can generate multiple bill processing solutions matching the merchant according to the bill information, payment time limit data, payment discount data, and attribute information and behavior data of multiple target market management bills in the following manner: query the preset bill processing rule library according to the bill information of multiple target market management bills, and determine multiple matching bill processing rules; wherein the preset bill processing rule library stores multiple preset bill processing rules, and one preset bill processing rule corresponds to at least one bill type; splice the bill information and bill processing rules of the corresponding target market management bills to obtain the spliced ​​bill processing rules; splice the attribute information and behavior data of the merchant to obtain the merchant's associated data; use the preset decision model to process the spliced ​​bill processing rules and the merchant's associated data to determine multiple bill processing solutions matching the merchant.

[0234] In some embodiments, when the above-mentioned determination module 905 is implemented, the target processing rules for multiple target market management bills selected by the target merchant can be determined according to the feedback data in the following manner: according to the feedback data, the recommendation plan selected by the merchant is determined as the target recommendation plan; whether there is modification data for the target recommendation plan in the feedback data; if it is determined that there is modification data for the target recommendation plan, whether the modification data exceeds the authorization scope; if it is determined that the modification data exceeds the authorization scope, the modification data and the target recommendation plan are sent to the market management terminal; wherein the market management terminal determines whether to accept the modification data for the target recommendation plan; receives and responds to the confirmation acceptance instruction fed back by the market management terminal, and generates target processing rules for multiple target market management bills selected by the target merchant according to the modification data and the target recommendation plan.

[0235] In some embodiments, when the above-mentioned processing module 906 is implemented, it can interact with the merchant terminal in the following manner according to the target processing rules to execute the first payment task of the current batch: according to the target processing rules, monitor whether the execution conditions of the first payment task of the current batch are triggered; when determining the execution conditions that trigger the first payment task of the current batch, calculate the current first payment resource data for the current first payment task according to the bill payment sub-rules and the first payment order; based on the current first payment resource data, generate the current first sub-order to be paid for the current first payment task; send the current first payment reminder information to the merchant terminal; wherein the current first payment reminder information carries at least the current first sub-order; receive the first payment resource data fed back by the merchant.

[0236] It should be noted that the units, devices or modules described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. For the convenience of description, the above devices are described separately by functions divided into various modules. Of course, when implementing this specification, the functions of each module can be implemented in the same or more software and / or hardware, or the modules that implement the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0237] It can be seen from the above that the market management bill processing device provided based on the embodiment of this specification can be well adapted to the market management payment scenario. While effectively taking into account the merchant payment time limit and payment discount, it enables merchants to flexibly choose and complete the payment of multiple market management bills efficiently and conveniently through matching processing methods according to their own circumstances, thereby meeting the merchants' diverse payment needs and improving the merchants' interactive experience.

[0238] In a specific scenario example, the market management bill processing method provided in this specification can be applied to implement configurable support for bill consolidation and multiple payments for the agricultural wholesale market. The specific implementation process can be found in the following content.

[0239] In this scenario example, it is considered that in the agricultural wholesale market, the payment interaction scenarios between the market management and the merchants are often relatively frequent, such as entry and exit scenarios (corresponding to the market entry bill), resource leasing scenarios (corresponding to the resource leasing bill), etc. However, the most common payment mode in the agricultural wholesale market is that one bill must be paid in full at one time, and multiple bills must be paid in multiple times; this payment mode sometimes puts pressure on merchants in terms of capital turnover, and also increases the merchant's operation time, reducing the merchant experience. Specifically. The existing party has the following shortcomings: (1) does not support multiple payments for a single bill; (2) does not support the combined payment of multiple bills; (3) does not support multiple payments after the multiple bills are combined. This leads to pressure on the merchant's funds and affects the merchant experience.

[0240] In order to ease the financial pressure of merchants and improve the merchant experience, merchants can meet similar installment payments and bill consolidation payments, make merchants more active, and promote a healthier and more sustainable agricultural wholesale market. Consider proposing a bill that is convenient and flexible, can better meet the needs of merchants, supports multiple bills to be combined and can make multiple payments. In addition to supporting the previous payment mode, this solution also provides a single account for multiple payments (twice or more), multiple bills after the merger of one or more payments. The payment mode is more flexible, allowing merchants to customize the payment method according to their needs. At the same time, in order to promote the payment enthusiasm of merchants, early renewal can obtain a certain amount of discounts, such as a 500 yuan discount for a payment of 10,000 yuan or more. Users need to consider reducing the amount of the discount when paying.

[0241] Since multiple payments and combined payments, as well as multiple payments after combined payments, require many business rules to control various possible billing situations, a rule engine is introduced to complete the analysis of business rules and the final business decision; a flexible payment rule configuration page (for example, the market management payment interface) is introduced to achieve the flexible support of the business system for multiple payment methods. The application of new rules can be completed without changing the code and system release, improving the efficiency of the business system and user experience.

[0242] Since payment is a very serious scenario that does not tolerate any mistakes, it is necessary to introduce a payment verification mechanism on the payment platform (for example, the market payment management platform) to help complete the verification functions such as the legitimacy of the payment account and whether it has been frozen (for example, verifying the target market management bill); other aspects, such as the cache mechanism, can achieve fast data retrieval. For details, see Fig.10 As shown, the following structure can be introduced and used to build the overall architecture of the bill payment business system:

[0243] (1) Introducing the rule engine

[0244] The rule engine is a component that can be embedded in an application. It can separate business decisions from code programs and use predefined semantic modules to complete the writing of business decisions. It parses business rules and makes business decisions without having to write code to implement rule control. When the system starts, the rule engine will load the configured business rules into memory, allowing the system to process business according to the established business rules.

[0245] (2) Configurable rules

[0246] Payment rules (e.g., target processing rules) can be configured on the business system management side, and the configured rules can provide data input for the rule engine; at the same time, it can respond to changes in payment requirements or customized bill payment methods for different merchants, and provide bill payment methods that suit their needs for different merchants. The main elements of this configuration include merchant number, bill payment method, bill payment channel, preferential method, bill type mutual exclusion, notification method, etc.

[0247] Among them, merchant number: unique identifier, one merchant number can only be configured with one bill payment method;

[0248] Bill payment method: The bill payment method is first fully configured by the market administrator, and each merchant can choose the payment method that suits them according to their own situation. If you choose "Multiple bills combined for multiple payments", multiple bills can be combined and paid multiple times. If the total amount of multiple bills exceeds the full discount standard, a full discount will be made, and this combination will only be fully discounted once, and another bill cannot be combined with other bills for payment again; choose to pay a single bill once or multiple times; the default method is to pay one bill in one payment; if a merchant wants to modify his payment method, he needs to apply to the market administrator to update and modify it.

[0249] Bill payment channel: The payment channel is set by the market administrator and is usually the default. The default main payment channels are: bank card, WeChat Pay, Alipay, UnionPay, etc.

[0250] Discount method: This rule configuration must be completed by the market administrator, and the rule applies to all merchants. Different types of fees have different discount methods. For example, if the fee type is booth rental, it can be configured to give a discount of 500 yuan for a payment of 10,000 yuan. This payment method is calculated based on the amount paid by the merchant (such as the previous 10,000 yuan is the final amount paid by the merchant); if the fee type is loading and unloading fees, it is paid as a percentage, such as a 10% discount. This configuration can be used regardless of whether it is paid multiple times or once. If three bills are combined and paid at 50%, each bill will have a 10% discount.

[0251] Mutually exclusive rules for bill types: For multiple bills combined payment, due to their different preferential methods, in order to better control the payment method of bills, different bills adopt mutually exclusive rules for merging. For example, the bill with the fee type of booth rental usually adopts the preferential method of full discount, and cannot be combined with the bill with the fee type of loading and unloading fee that is paid by percentage.

[0252] Notification method: Provide merchants with a notification method after the payment action is completed. It can be an immediate notification or a specific time point can be set, such as 09:00, which is the default method. The payment notification result text mainly includes payment success and payment failure (including the failure reason and the corresponding error code).

[0253] (3) Payment Verification Mechanism

[0254] The rule engine solves the business rules for bill payment, mainly to complete the allocation of each bill and whether it involves the allocation of an amount exceeding the amount. For example, there are five bills to be paid together, one of which is a bill of 500 yuan, and the merchant uses a 20% payment percentage when paying 5,000 yuan, that is, 1,000 yuan per bill. It is found that there will be 500 yuan left when paying the bill with a total amount of 500 yuan, so the remaining 500 yuan needs to be allocated to the other four bills. In addition, before payment, it is necessary to verify whether the counter numbers corresponding to multiple bills are consistent and whether the account is frozen. The relevant verification work is completed by the payment verification mechanism.

[0255] (4) Bill payment progress notification

[0256] After the bill payment is successful, in addition to notifying the merchant of the successful payment, the merchant must also be informed of the bill payment status of this payment, such as paid, partially paid, unpaid, etc., so that the merchant can know their payment status and progress, which is convenient for them to make financial plans.

[0257] (5) Others

[0258] The cache mechanism is used in many business systems. It can significantly improve retrieval efficiency, enhance user experience, reduce database access pressure, and improve business processing performance.

[0259] Based on the above bill payment business system, when merchants make bill payments, the specific bill payment business flow process can be referred to Fig.11 As shown, including the following.

[0260] (1) The market operation administrator first configures the merchant's payment rules based on the merchant's payment preferences and preferential rules through the add / modify bill payment method configuration information function in the business system management terminal. The management terminal (e.g., the market management terminal) will load the configuration rules (e.g., the preset bill processing rules) into the rule engine.

[0261] (2) The merchant selects the bill to be paid (possibly multiple bills) and the payment method, verifies whether the discount item is effective, and clicks Pay (to determine the final target processing rules);

[0262] (3) The rule engine makes a payment decision based on the bill information in (2) combined with the payment rules (e.g., target processing rules). The payment platform further verifies the legitimacy of the account, how to allocate the excess amount, and whether the bill payment has timed out (15 minutes).

[0263] (4) After the payment is completed, the payment platform records the payment flow and sends a payment notification to the business system application. The business system application completes the bill status update and sends the payment notification to the merchant;

[0264] Specifically, if the payment is successful, the payment process ends; if the payment fails, the user can initiate the payment process again and repeat the operation process after (2).

[0265] Combination Fig.11 It can be seen that the bill payment business flow process is divided into two stages. The first stage is to complete the configuration of bill payment rules, preferential rules, and mutually exclusive rules; the second stage is for merchants to select bills and payment channels, and complete bill payment in combination with the payment rules and preferential rules (maybe without preferential rules) configured in the first stage. The specific implementation details can be found in the following content.

[0266] (1) Bill payment rule configuration

[0267] In order to better and uniformly manage the configuration of bill payment rules, this function can only be operated by authorized market administrators (for example, market management parties). Administrators can configure payment-related rules, such as preferential rules, mutually exclusive rules, optional payment channels, and optional payment methods (full payment methods). And store the configuration information in the domestic database TiDB. After the configuration is completed, the scheduled task scans the newly added, updated or deleted bill payment rules every 10 minutes (time period 09:00-18:00) and configures the information, and pushes it to the rule engine in the payment platform for subsequent business processing.

[0268] (2) Merchant bill payment method settings

[0269] Merchants can select bills according to their preferences and actual needs and then choose payment methods. The payment methods that can be selected must be those configured by the market administrator in (1). For example, if you select multiple bills to combine multiple payments, the rule verification will be triggered, and the expense type of the bill will be used as the judgment standard to see if they are mutually exclusive. If the verification is passed, he needs to fill in the total amount for this payment first, and then set a certain amount or percentage for each bill. In fact, the total amount of this payment is allocated to the selected bills to achieve flexible on-demand payment. At the same time, the merchant's preference settings will be verified with the business rules in (1). If the verification fails, the order to be paid and subsequent operations will be reselected.

[0270] (3) Rule Engine and Business Rules

[0271] Specifically, we can use the AviatorScript open source lightweight rule engine, where programmers can combine the bill payment rules configured in (1) with regular expressions to form an overall business logic judgment. The more complex and core part here is the judgment logic. Here is a judgment flow chart, which can be referred to Fig.12 When implemented specifically, the following steps may be included:

[0272] 1) After the rule engine obtains the configured bill payment business rules, it waits for the user to initiate a bill payment application;

[0273] 2) The rule engine makes a rule judgment based on the bill information, and terminates the payment process directly if it does not meet the business rules;

[0274] 3) If it meets the requirements, it is necessary to determine whether the bill is multiple or single. If it is a single bill, a payment order is directly constructed; if it is multiple bills, multiple bills need to be merged according to business rules, and whether there is a discount amount must also be considered. If there is a discount, the discount amount is deducted, and then a payment order is constructed to complete the payment.

[0275] (4) Payment verification

[0276] The payment verification process is one of the core functions of the payment platform. It mainly completes the verification of whether the order payment status has timed out, whether the account information is abnormal, etc. Only orders that have passed the verification (note that they are not bills) can be paid, otherwise the prompt text will be directly returned to the merchant.

[0277] (5) Payment completion and notification

[0278] The two most common states of payment results are success or failure. Regardless of the state, the merchant must be informed clearly to let them know the payment progress and results. In particular, if the payment fails, the merchant should be informed of the reason for the payment failure as much as possible to guide the merchant to the next step and prevent them from making the same mistake next time. At the same time, the payment flow should be recorded after the payment is completed for reconciliation.

[0279] Through the above scenario examples, it is verified that the method for processing market management bills provided in this manual has the following advantages: (1) supports more payment methods; (2) is applicable to more and richer payment scenarios, and has greater market potential; (3) the rule configuration is flexible and convenient, and easier to promote; it helps the agricultural wholesale market to operate more smoothly.

[0280] Although the present specification provides method operation steps as described in the embodiments or flow charts, more or less operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiments is only one way of executing the order of many steps, and does not represent a unique execution order. When the device or client product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment). The term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, product or device. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or device including the elements. The first, second, etc. words are used to represent the name, and do not represent any particular order.

[0281] Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

[0282] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, classes, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer-readable storage media including storage devices.

[0283] Through the description of the above embodiments, it can be known that those skilled in the art can clearly understand that the present specification can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present specification can essentially be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a mobile terminal, a server, or a network device, etc.) to execute the methods described in each embodiment of the present specification or some parts of the embodiments.

[0284] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. This specification can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0285] Although the present specification is described through embodiments, those skilled in the art will appreciate that there are many modifications and changes to the present specification without departing from the spirit of the present specification, and it is intended that the appended claims include these modifications and changes without departing from the spirit of the present specification.

Claims

1. A method for processing a market management bill, characterized in that: include: Receiving a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least the bill identifiers of multiple target market management bills selected by the merchant and the merchant identifier of the merchant; According to the bill identifications of multiple target market management bills, the bill information, payment time limit data, and payment discount data of the target market management bills are obtained; and according to the merchant identifications of the merchants, the attribute information and behavior data of the merchants are obtained; Based on the bill information, payment time limit data, payment discount data of bill management bills in multiple target markets, as well as the attribute information and behavior data of merchants, multiple bill processing solutions matching the merchants are generated as recommended solutions; Sending the recommendation plan to the merchant terminal, and receiving merchant feedback data on the recommendation plan; wherein the merchant terminal is used to display the recommendation plan to the merchant; According to the feedback data, target processing rules for managing bills in multiple target markets selected by the target merchant are determined; wherein the target processing rules at least include: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules; Interact with merchant terminals to manage bills for multiple target markets based on target processing rules.

2. The method according to claim 1, characterized in that Interact with merchant terminals according to target processing rules to process multiple target market management bills, including: According to the bill merging sub-rule, a first target market management bill among the multiple target market management bills is merged to obtain a corresponding first payment order; a second target market management bill among the multiple target market management bills is merged to obtain a corresponding second payment order; wherein the payment time limit data and / or payment discount data of the first target market management bill associated with the first payment order matches, and the payment time limit data and / or payment discount data of the second target market management bill associated with the second payment order matches; Generate, according to the bill payment sub-rule, a plurality of first payment tasks regarding the first payment order and a plurality of second payment tasks regarding the second payment order; According to the target processing rule, by interacting with the merchant terminal, multiple first payment tasks and multiple second payment tasks are executed in batches to obtain corresponding first payment resource data and second payment resource data; According to the bill settlement allocation sub-rule, the first target market management bills are settled and written off in batches using the first payment resource data; the second target market management bills are settled and written off in batches using the second payment resource data.

3. The method according to claim 2, characterized in that According to the bill merging sub-rule, a first target market management bill among the multiple target market management bills is merged to obtain a corresponding first payment order; After merging the second target market management bills among the multiple target market management bills to obtain a corresponding second payment order, the method further includes: The remaining third target market management bills in the multiple target market management bills are combined to obtain a corresponding third payment order.

4. The method according to claim 2, characterized in that: According to the bill merging sub-rule, the first target market management bill in the multiple target market management bills is merged to obtain the corresponding first payment order, including: According to the bill merging sub-rule and the payment time limit data of the target market management bill, the target market management bill whose time difference between the verification deadline and the current time is less than the first reference time is selected from multiple target market management bills as candidate target market management bills; According to the bill merging sub-rule and the payment preferential data of the candidate market management bills, a candidate target market management bill without mutually exclusive preferential treatment is selected from multiple candidate target market management bills as the first target market management bill; According to the bill merging sub-rule, the bill information of the multiple first target market management bills is used to merge the multiple first target market management bills to obtain the corresponding first payment order.

5. The method according to claim 4, characterized in that According to the bill merging sub-rule, the second target market management bills in the multiple target market management bills are merged to obtain the corresponding second payment order, including: Determining a first remaining bill among the plurality of target market management bills except the first target market management bill; According to the bill merging sub-rule and the payment preferential data of the first remaining bills, bills with mutually exclusive preferential treatment are eliminated from the plurality of first remaining bills to obtain the second target market management bills; According to the bill merging sub-rule, the bill information of the plurality of second target market management bills is used to merge the plurality of second target market management bills to obtain a corresponding second payment order.

6. The method according to claim 2, characterized in that According to the bill settlement allocation sub-rule, the first payment resource data is used to settle and write off the first target market management bills in batches, including: According to the bill settlement allocation sub-rule, the current batch of settlement and write-off of the first target market management bills is performed in the following manner using the current first payment resource data fed back by the merchant for the current first payment task: Determine the current time difference between the current time and the write-off deadline of the first target market management bill, and the current remaining resource data value of the first target market management bill to be settled and written off; Determine the priority weight of the first target market management bill according to the current time difference value and the current remaining resource data value of the first target market management bill; According to the priority weight of the first target market management bill, the current first payment resource data is divided into a plurality of resource shares; wherein one resource share corresponds to one first target market management bill; Utilize multiple resource shares to respectively perform settlement and write-off of the current batch of corresponding first target market management bills.

7. The method according to claim 1, characterized in that The target market management bill includes at least one of the following: a market entry bill, a resource rental bill, a property management bill, a stall usage fee bill, and a loading and unloading service bill.

8. The method according to claim 1, characterized in that According to the bill identifiers of multiple target market management bills, the bill information, payment time limit data, and payment discount data of the target market management bills are obtained; After obtaining the attribute information and behavior data of the merchant according to the merchant identification of the merchant, the method further includes: According to the preset verification rules, use the merchant information and billing information to verify the target market management bills; When a target market management bill that fails verification is detected, an error message about the target market management bill is generated; Send the error message to the merchant terminal.

9. The method according to claim 1, characterized in that: Based on the bill information, payment time limit data, payment discount data of multiple target market management bills, as well as the attribute information and behavior data of the merchant, multiple bill processing solutions matching the merchant are generated, including: According to the bill information of the bills managed by the multiple target markets, a preset bill processing rule library is queried to determine multiple matching bill processing rules; wherein the preset bill processing rule library stores multiple preset bill processing rules, and one preset bill processing rule corresponds to at least one bill type; Splice the bill information and bill processing rules of the corresponding target market management bill to obtain the spliced ​​bill processing rules; splice the merchant's attribute information and behavior data to obtain the merchant's associated data; The preset decision model is used to process the spliced ​​bill processing rules and the merchant's associated data to determine multiple bill processing solutions that match the merchant.

10. The method according to claim 1, characterized in that Based on the feedback data, target processing rules for managing bills in multiple target markets selected by target merchants are determined, including: According to the feedback data, determine the recommendation plan selected by the merchant as the target recommendation plan; Detect whether there is modified data for the target recommendation solution in the feedback data; In the case where it is determined that there is modified data for the target recommended solution, detecting whether the modified data exceeds the authorized scope; In the case where it is determined that the modified data exceeds the authorized scope, the modified data and the target recommendation scheme are sent to the market management terminal; wherein the market management terminal determines whether to accept the modified data for the target recommendation scheme; Receive and respond to the confirmation acceptance instruction fed back by the market management terminal, and generate target processing rules for multiple target market management bills selected by the target merchants based on the modified data and the target recommendation plan.

11. The method according to claim 2, characterized in that According to the target processing rule, by interacting with the merchant terminal, multiple first payment tasks and multiple second payment tasks are executed in batches to obtain corresponding first payment resource data and second payment resource data, including: According to the target processing rules, interact with the merchant terminal in the following way to execute the first payment task of the current batch: According to the target processing rules, monitor whether the execution conditions of the first payment task of the current batch are triggered; In the case of determining the execution condition for triggering the first payment task of the current batch, calculating the current first payment resource data for the current first payment task according to the bill payment sub-rule and the first payment order; Generate a current first sub-order to be paid for the current first payment task according to the current first payment resource data; Sending the current first payment reminder information to the merchant terminal; wherein the current first payment reminder information carries at least the current first sub-order; Receive the first payment resource data fed back by the merchant.

12. A device for processing market management bills, characterized in that: include: A receiving module, configured to receive a multi-bill merging processing request initiated by a merchant terminal; wherein the multi-bill merging processing request carries at least the bill identifiers of multiple target market management bills selected by the merchant, and the merchant identifier of the merchant; An acquisition module, used to acquire bill information, payment time limit data, and payment discount data of target market management bills according to bill identifiers of multiple target market management bills; and to acquire attribute information and behavior data of merchants according to merchant identifiers of merchants; A generation module, for generating multiple bill processing solutions matching the merchant as recommended solutions based on the bill information, payment time limit data, payment discount data, and merchant attribute information and behavior data of multiple target market management bills; An interactive module, used to send the recommendation plan to the merchant terminal and receive merchant feedback data on the recommendation plan; wherein the merchant terminal is used to display the recommendation plan to the merchant; A determination module, used to determine target processing rules for managing bills in multiple target markets selected by target merchants based on the feedback data; wherein the target processing rules at least include: bill merging sub-rules, bill payment sub-rules, and bill settlement allocation sub-rules; The processing module is used to interact with the merchant terminal according to the target processing rules and process multiple target market management bills.

13. A server, characterized in that: The method comprises a processor and a memory for storing processor-executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 11 when executing the instructions.

14. A computer-readable storage medium, characterized in that: Computer instructions are stored thereon, and when the instructions are executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

15. A computer program product, characterized in that The invention comprises a computer program, which implements the steps of the method according to any one of claims 1 to 11 when being executed by a processor.

Images