Method and apparatus for handling prepayment of funds

Abstract

The embodiment of the specification provides a fund prepayment processing method and device, wherein the fund prepayment processing method comprises the following steps: in the process of fund prepayment processing between a payer and a payee, a prepayment order is created according to a fund prepayment request submitted by the payer to the payee, a prepayment deduction dimension set by the payer for the prepayment order is obtained, a prepayment voucher submitted by the payee for the prepayment order is further obtained, and fund prepayment is performed on a prepayment account based on the prepayment voucher, and in the case that a prepayment deduction record submitted by the payee is detected, a target prepayment order matched with the prepayment deduction record is determined, and fund deduction processing is performed, so that fund prepayment and prepayment deduction are realized between the payer and the payee participating in a credit investigation service agreement.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a method and apparatus for prepayment processing. Background Technology

[0002] With the continuous development of internet technology, users are paying more and more attention to credit reporting, and the credit reporting system is being established and improved. Under these circumstances, credit reporting platforms that provide various credit reporting services to users have emerged. As more and more institutions cooperate with credit reporting platforms to provide credit reporting services or credit-related services to users, higher requirements are being placed on credit reporting platforms. Summary of the Invention

[0003] This specification provides one or more embodiments of a prepayment processing method applied to a prepayment management system. The method includes: creating a prepayment order from the payer to the payee based on a prepayment request submitted by the payer to the payee in connection with a credit reporting service agreement; obtaining the prepayment deduction dimension set by the payer for the prepayment order based on the service agreement information with the payee; obtaining the prepayment voucher submitted by the payee for the prepayment order and making a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher; if a prepayment deduction record submitted by the payee is detected, determining a target prepayment order matching the prepayment deduction record based on the prepayment deduction dimension of each prepayment order from the payer to the payee, and performing fund deduction processing on the target prepayment order.

[0004] This specification provides one or more embodiments of a prepayment processing device, operating within a prepayment management system. The device includes: a prepayment order creation module configured to create a prepayment order from the payer to the payee based on a prepayment request submitted by the payer to the payee in connection with a credit reporting service agreement; a deduction dimension setting module configured to obtain a prepayment deduction dimension set by the payer for the prepayment order based on service agreement information with the payee; a prepayment module configured to obtain a prepayment voucher submitted by the payee for the prepayment order and make a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher; and a deduction processing module configured to, if a prepayment deduction record submitted by the payee is detected, determine a target prepayment order matching the prepayment deduction record based on the prepayment deduction dimensions of each prepayment order from the payer to the payee, and perform fund deduction processing on the target prepayment order.

[0005] This specification provides one or more embodiments of a prepayment processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: create a prepayment order from the payer to the payee based on a prepayment request submitted by the payer to the payee in connection with a credit reporting service agreement; obtain a prepayment deduction dimension set by the payer for the prepayment order based on service agreement information with the payee; obtain a prepayment voucher submitted by the payee for the prepayment order and make a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher; if a prepayment deduction record submitted by the payee is detected, determine a target prepayment order matching the prepayment deduction record based on the prepayment deduction dimension of each prepayment order from the payer to the payee, and perform prepayment deduction processing for the target prepayment order.

[0006] This specification provides one or more embodiments of a computer-readable storage medium for storing computer-executable instructions that, when executed, implement the following process: Based on a prepayment request submitted by a payer to a payee under a credit reporting service agreement, create a prepayment order from the payer to the payee. Obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service agreement information with the payee. Obtain the prepayment voucher submitted by the payee for the prepayment order and prepay funds to the prepayment account associated with the prepayment order based on the prepayment voucher. If a prepayment deduction record submitted by the payee is detected, determine a target prepayment order matching the prepayment deduction record based on the prepayment deduction dimension of each prepayment order from the payer to the payee, and perform fund deduction processing for the target prepayment order. Attached Figure Description

[0007] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0008] Figure 1 A schematic diagram illustrating the implementation environment of a prepayment processing method provided in one or more embodiments of this specification;

[0009] Figure 2 A flowchart illustrating a method for prepayment processing provided in one or more embodiments of this specification;

[0010] Figure 3A flowchart illustrating a prepayment processing method for a credit access scenario, provided for one or more embodiments of this specification.

[0011] Figure 4 A flowchart illustrating a prepayment processing method for credit data collection scenarios, provided by one or more embodiments of this specification.

[0012] Figure 5 A schematic diagram of an embodiment of a prepayment processing device provided in one or more embodiments of this specification;

[0013] Figure 6 This is a schematic diagram of the structure of a prepayment processing device provided for one or more embodiments of this specification. Detailed Implementation

[0014] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0015] The fund prepayment processing method provided in one or more embodiments of this specification can be applied to the implementation environment of a prepayment management system. (Refer to...) Figure 1 The implementation environment includes at least:

[0016] Prepayment management system 101, payer's access terminal 102, payee's access terminal 103;

[0017] Among them, the prepayment management system 101 is used to manage the prepayment of funds from the payer to the payee when the payer participates in the signing of the credit reporting service agreement. Specifically, it includes creating prepayment orders, setting prepayment deduction dimensions and processing prepayment of funds in the prepayment stage, and making decisions on prepayment deduction and processing the deduction of prepayment funds in the prepayment deduction stage.

[0018] The payer's access terminal 102 refers to the terminal device of the payer who has signed the credit reporting service agreement to access the prepayment management system 101. The payer uses the access terminal 102 to access the prepayment management system 101 to apply for prepayment of funds to the payee.

[0019] The payee's access terminal 103 refers to the terminal device of the payee who has signed the credit reporting service agreement to access the prepayment management system 101. The payee uses the access terminal 103 to access the prepayment management system 101 to cooperate with the payee in making prepayments and to deduct prepayment funds by submitting prepayment deduction records to the prepayment management system 101.

[0020] In this implementation environment, during the prepayment process, the payer first submits a prepayment request to the payee through the prepayment management system 101 via the payer's access terminal 102. The prepayment management system 101 creates a prepayment order from the payer to the payee based on the prepayment request and obtains the prepayment deduction dimension set by the payer's access terminal 102 based on the service contract information with the payee. Further, based on the prepayment voucher submitted by the payee through the access terminal 103 for the prepayment order, the system prepays funds to the prepayment account associated with the prepayment order based on the prepayment voucher. Subsequently, upon detecting the prepayment deduction record submitted by the payee through the access terminal 103, the system determines the target prepayment order matching the prepayment deduction record based on the prepayment deduction dimension of each prepayment order from the payer to the payee, and performs the fund deduction processing for the target prepayment order. This achieves prepayment and prepayment fund deduction between the payer and the payee who participated in the credit reporting service agreement.

[0021] This specification provides one or more embodiments of a prepayment processing method for funds, as follows:

[0022] Reference Figure 2 The prepayment processing method provided in this embodiment can be applied to a prepayment management system. The method specifically includes steps S202 to S208.

[0023] Step S202: Based on the prepayment request submitted by the payer to the payee in accordance with the prepayment request submitted by the payer in connection with the signing of the credit reporting service agreement, create a prepayment order from the payer to the payee.

[0024] In this embodiment, the signing of a credit reporting service agreement refers to the signing of an agreement by the parties involved in the credit reporting service for or related services. After signing the credit reporting service agreement, the corresponding service signing information is obtained. For example, a credit reporting agency providing credit reporting services and a financial institution accessing the credit reporting service (credit reporting access agency / credit reporting inquiry agency) sign an agreement for the credit reporting service. After the credit reporting agency and the financial institution sign a credit reporting access agreement for the credit reporting service, the credit reporting access signing information is obtained. Another example is a data source agency providing data collection and a credit reporting agency that wants to collect data sign an agreement for data collection. After the data source agency and the credit reporting agency sign an agreement for data collection, the credit data signing information is obtained.

[0025] The payer refers to the party that needs to make payment among the parties involved in signing the credit reporting service agreement, while the payee refers to the party that receives payment from the payer. For example, in a scenario where a credit reporting agency and a financial institution sign a credit access agreement for credit reporting services, the payer is the financial institution that uses the credit reporting services provided by the credit reporting agency, that is, the financial institution that accesses the credit information (credit inquiry) from the credit reporting agency, and the payee is the credit reporting agency. As another example, in a scenario where a data source institution and a credit reporting agency sign an agreement for data collection, the payer is the credit reporting agency that requests data collection from the data source institution, and the payee is the data source institution that provides the data collection.

[0026] The aforementioned prepayment request refers to a payment request made by the payee to the payee in advance before using the credit reporting services specified in the agreement, after the payee and payer have signed a credit reporting service agreement. Alternatively, it can refer to a payment request made by the payee to the payee in advance before any fees are incurred during the service's operation. A prepayment order refers to a payment slip or invoice created by the payer to the payee in advance. Specifically, a prepayment order can be a credit reporting access prepayment order from a financial institution to a credit reporting agency for credit reporting access, or a data collection prepayment order from a credit reporting agency to a data source institution for data collection.

[0027] In practice, based on the signing of a credit information service agreement between the payer and the payee, during the process of the payer making advance payments to the payee, the payer submits an advance payment request to the advance payment management system. The advance payment management system then creates an advance payment order based on the advance payment request, specifically an advance payment order for the payer to make advance payments to the payee. The advance payment request may include payer information, payee information, and / or the amount of advance payments. The advance payment management system can then create an advance payment order based on the payer information, payee information, and / or the amount of advance payments included in the advance payment request.

[0028] Step S204: Obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee.

[0029] In practice, after creating a prepayment order where the payer makes advance payments to the payee, the payer can configure the prepayment settings. Specifically, this involves setting prepayment deduction dimensions for the prepayment order to determine the subsequent configuration for prepayment deduction. In particular, during the prepayment settings process, the payer can set prepayment deduction dimensions based on the service agreement information with the payee. Correspondingly, the prepayment management system obtains the prepayment deduction dimensions set by the payer for the prepayment order, specifically the prepayment deduction dimensions set by the payer based on the service agreement information with the payee.

[0030] The aforementioned prepayment deduction dimension refers to the configuration set by the payer for subsequent prepayment deduction of the prepayment funds for the prepayment order; specifically, the prepayment deduction dimension can be determined based on at least one service contracting object selected by the payer from the service contracting information obtained when signing the credit service agreement with the payee.

[0031] In this context, the service contracting party in the service contracting information obtained by the payer when signing a credit investigation service agreement with the payee can be the payer as a whole, or it can be an offline contract signed by the payer and the payee (or an electronic contract signed online), or it can be a contracted service product signed by the payer with the payee, or it can be a service contract signed by the payer with the payee.

[0032] Based on this, when the payer sets the prepayment deduction dimension for the prepayment order, it can set the prepayment deduction dimension at the level of the institution as a whole. In this case, the prepayment deduction dimension is specifically the institution deduction dimension where the payer deducts the prepayment funds from the payee.

[0033] It is also possible to set up a prepayment deduction dimension where the payer deducts the prepayment funds from the signed contract between the two parties. In this case, the prepayment deduction dimension is specifically a contract deduction dimension where the payer deducts the prepayment funds from the signed contract with the payee.

[0034] Alternatively, a prepayment deduction dimension can be set up where the payer deducts prepayment funds for the contracted service products signed with the payee. In this case, the prepayment deduction dimension is specifically the product deduction dimension where the payer deducts prepayment funds for the contracted service products signed with the payee.

[0035] Alternatively, a prepayment deduction dimension can be set up where the payer deducts prepayment funds based on the service contract signed with the payee. In this case, the prepayment deduction dimension is specifically a contract deduction dimension where the payer deducts prepayment funds based on the service contract signed with the payee.

[0036] Optionally, the prepayment deduction dimension includes at least one of the following: institutional deduction dimension where the payer deducts funds from the payee's prepayment; contract deduction dimension where the payer deducts funds from the prepayment of a contract signed with the payee; product deduction dimension where the payer deducts funds from the prepayment of a contracted service product signed with the payee; and contract deduction dimension where the payer deducts funds from the prepayment of a service contract signed with the payee.

[0037] In practical applications, to improve the efficiency of payers setting prepayment deduction dimensions for prepayment orders, a large language model can be used to set these dimensions. Specifically, the prepayment order, the service agreement information between the payer and payee, and the task setting text can be input into the large language model to set the prepayment deduction dimensions, thus obtaining the prepayment deduction dimensions for the prepayment order. In this case, obtaining the prepayment deduction dimensions set by the payer for the prepayment order based on the service agreement information with the payee can be replaced by inputting the prepayment order, service agreement information, and / or task setting text into the large language model to make a prepayment deduction dimension decision, thus obtaining the prepayment deduction dimensions for the prepayment order.

[0038] To better align the prepayment deduction dimension set by the large language model with the actual scenario of fee settlement for credit investigation services using prepayment and prepayment deduction methods between payers and payees, the following can be input into the large language model: historically valid prepayment orders created by the payer and payee in the previous prepayment process, along with the prepayment order, the service contract information between the payer and payee, and the task setting text. This input will determine the prepayment deduction dimension for the prepayment order. In this case, obtaining the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee can be replaced by: inputting the prepayment order, historical prepayment orders, service contract information, and / or task setting text into the large language model to determine the prepayment deduction dimension.

[0039] Step S206: Obtain the prepayment voucher submitted by the payee for the prepayment order, and make a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher.

[0040] In practice, based on the prepayment deduction dimension set by the payer for the prepayment order, the prepayment management system can synchronize the prepayment order with the prepayment deduction dimension set to the payee. After receiving the prepayment order, the payee can generate a prepayment voucher for the prepayment order and submit the prepayment voucher to the prepayment management system. The prepayment voucher can be an electronic invoice obtained by applying for an electronic invoice for the prepayment order, or it can be an image of an uploaded physical invoice.

[0041] Accordingly, after the prepayment management system obtains the prepayment voucher submitted by the payee for the prepayment order, it makes a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher. Specifically, in one optional implementation of this embodiment, making a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher includes: transferring funds from the payer's funds account based on the amount of funds carried by the prepayment voucher, and transferring the transferred funds to the prepayment account created for the prepayment order.

[0042] It should be noted that during the process of making advance payments to the prepayment account associated with the prepayment order based on the prepayment voucher, a prepayment account for the prepayment order can also be created. A prepayment account is a fund account used to store and manage the advance funds made by the payer to the payee. The account belongs to the payer. Specifically, based on the agreement between the payer and the prepayment management system, the prepayment management system can help the payer create a prepayment account for the current prepayment order. It can also help the payer manage the prepayment account and the advance funds within it. In this case, there is a one-to-one correspondence between the prepayment order and the prepayment account. After creating the prepayment account, funds are transferred from the payer's fund account based on the amount carried by the prepayment voucher, and the transferred funds are then transferred to the prepayment account created for the prepayment order. Alternatively, after creating a prepayment order from the payer to the payee, the prepayment management system can create a prepayment account for the prepayment order. Here, funds are transferred from the payer's fund account based on the amount carried by the prepayment voucher, and the transferred funds are then transferred to the prepayment account created for the prepayment order.

[0043] In addition to the above-mentioned implementation method of creating a one-to-one prepayment account for prepayment orders, in the scenario where the payer makes prepayments to the payee, multiple prepayment orders for which the payer makes prepayments to the payee can share a single prepayment account. In this case, during the process of making prepayments to the prepayment account associated with the prepayment order based on the prepayment voucher, one prepayment account can be selected as the target prepayment account from among the multiple prepayment accounts created by the payer for making prepayments to the payee. The prepayment order is then associated with the target prepayment account, and funds are transferred out from the payer's funds account based on the amount of funds carried by the prepayment voucher, and the transferred funds are then transferred into the target prepayment account associated with the prepayment order.

[0044] Step S208: If a prepayment deduction record submitted by the payee is detected, the target prepayment order matching the prepayment deduction record is determined according to the prepayment deduction dimension of each prepayment order from the payer to the payee, and the fund deduction processing of the target prepayment order is performed.

[0045] In practice, after making a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher, the payee can initiate a prepayment deduction by submitting a prepayment deduction record to the prepayment management system. Accordingly, when the prepayment management system detects the prepayment deduction record submitted by the payee, it determines the target prepayment order that matches the prepayment deduction record based on the prepayment deduction dimension of each prepayment order from the payer to the payee, and performs the fund deduction processing for the target prepayment order.

[0046] In determining the target prepayment order for matching prepayment deduction records, the target prepayment order can be determined based on the prepayment deduction dimensions of each prepayment order from the payer to the payee. In one optional implementation of this embodiment, determining the target prepayment order based on the prepayment deduction dimensions of each prepayment order from the payer to the payee includes:

[0047] Match the prepayment deduction records with the service contract information to determine the payment recipient;

[0048] Prepayment decision processing is performed based on the prepayment deduction dimension of each prepayment order associated with the prepayment deduction record and the payment recipient, to obtain at least one prepayment order as the target prepayment order.

[0049] In the specific execution process, when matching prepayment deduction records with service contract information, prepayment keywords can be extracted from the prepayment deduction records and contract keywords can be extracted from the service contract information. The prepayment keywords and contract keywords are matched to obtain the payment object. Furthermore, based on the prepayment deduction dimension of each prepayment order associated with the prepayment deduction records and payment objects, prepayment decision processing is performed to obtain at least one prepayment order as the target prepayment order.

[0050] Specifically, in the prepayment decision-making process based on prepayment deduction records and the prepayment deduction dimensions of each prepayment order, in order to ensure that each prepayment order of the payer and payee can be deducted, and to avoid situations where prepayment order deduction fails or the prepayment funds corresponding to the prepayment order cannot be deducted for a long time, this embodiment provides an optional implementation method, which performs prepayment decision-making based on prepayment deduction records and the prepayment deduction dimensions of each prepayment order associated with the payment object, to obtain at least one prepayment order as the target prepayment order, including:

[0051] Each prepayment order is tested based on the prepayment decision rules, and the prepayment priority of each prepayment order is determined based on the test results and the prepayment deduction dimension of each prepayment order.

[0052] Based on the prepayment deduction record and prepayment priority, at least one prepayment order is selected as the target prepayment order from among the prepayment orders.

[0053] In the specific execution process, each prepayment order is detected based on the pre-configured prepayment decision rules. For example, the prepayment decision rules can be detection rules used to detect whether the prepayment order has been prepaid and deducted within a preset time interval. If the detection result is negative, it indicates that the prepayment order has not been deducted within a specific period of time, which can increase the prepayment priority of the prepayment order, thereby increasing the probability of the prepayment order being prepaid and deducted.

[0054] For example, the prepayment decision rule could be a detection rule used to check whether the service contract object corresponding to the prepayment deduction dimension set in the prepayment order is in a valid state. If the detection result is negative, it means that the service contract object corresponding to the prepayment deduction dimension set in the prepayment order may be unable to be prepaid due to contract changes, contract expiration, or contract invalidation. This can increase the prepayment priority of the prepayment order, thereby increasing the probability that the prepayment order will be prepaid.

[0055] Based on the above determination of the target prepayment order matching the prepayment deduction record according to the prepayment deduction dimension of each prepayment order from the payer to the payee, the fund deduction processing of the target prepayment order is carried out. Specifically, in the process of processing the fund deduction of the target prepayment order, the deduction parameters of the target prepayment order can be determined, and the deduction mode of the target prepayment order can be determined according to the deduction parameters, and the fund deduction processing of the target prepayment order can be carried out according to the deduction mode.

[0056] The deduction parameter can be the amount to be deducted; the deduction mode includes: the write-off deduction mode and / or the apportionment deduction mode; the write-off deduction mode refers to deducting the prepaid funds by writing off the prepaid funds corresponding to the prepaid bill, and the apportionment deduction mode refers to the situation where the prepaid funds corresponding to the prepaid bill are insufficient to deduct the prepaid funds, that is, the amount to be deducted in the prepaid deduction record is greater than the remaining write-off amount of the prepaid bill. In this case, part of the funds corresponding to the amount to be deducted are deducted by the prepaid funds corresponding to the prepaid bill, and the other part of the funds corresponding to the amount to be deducted needs to be paid by the payer.

[0057] Specifically, in one optional implementation of this embodiment, the processing of fund deduction for the target prepayment includes:

[0058] The amount to be deducted for the target prepayment is determined based on the prepayment deduction records;

[0059] If the amount to be deducted is less than or equal to the remaining write-off amount of the target prepayment, the funds will be transferred from the prepayment account associated with the target prepayment to the receiving account according to the amount to be deducted.

[0060] In addition, if the amount to be deducted is greater than the remaining write-off amount of the target prepayment, an accounts payable invoice is created based on the amount to be deducted and the remaining write-off amount; for example, the accounts payable amount is calculated based on the amount to be deducted and the remaining write-off amount, and an accounts payable invoice corresponding to the accounts payable amount is created; furthermore, funds are transferred from the prepayment account associated with the target prepayment to the receiving account according to the remaining write-off amount, and the accounts payable invoice is paid to the payee by the payer.

[0061] In this embodiment, to improve the accuracy and success rate of prepayment deduction in determining the target prepayment order matching the prepayment deduction record, a large language model can also be used to determine the target prepayment order matching the prepayment deduction record. Specifically, in an optional implementation method provided in this embodiment, the target prepayment order matching the prepayment deduction record is determined according to the prepayment deduction dimension of each prepayment order from the payer to the payee, including:

[0062] The prepayment deduction records and the prepayment deduction dimensions of each prepayment order are input into a large language model to perform prepayment order matching decisions and obtain the target prepayment order;

[0063] The prepayment matching decision includes: performing anomaly detection on each prepayment based on the prepayment deduction dimension to obtain abnormal prepayment, and determining the prepayment level of abnormal and normal prepayment; and determining at least one abnormal prepayment and / or normal prepayment as the target prepayment based on the prepayment level and prepayment deduction record.

[0064] Furthermore, in the process of determining the target prepayment order matching the prepayment deduction record based on the prepayment deduction dimension of each prepayment order from the payer to the payee, in an optional implementation of this embodiment, the process of deducting funds from the target prepayment order includes: determining the deduction parameters of the target prepayment order, determining the deduction mode of the target prepayment order based on the deduction parameters, and performing the fund deduction process of the target prepayment order according to the deduction mode.

[0065] Specifically, in the process of determining the deduction mode of the target prepayment based on the deduction parameters, it can be determined by checking whether the deduction parameters are greater than the remaining write-off amount of the target prepayment. If so, the deduction mode of the target prepayment is determined to be the apportionment deduction mode; if not, the deduction mode of the target prepayment is determined to be the write-off deduction mode.

[0066] Based on this, in the process of processing the deduction of funds for target prepayment orders according to the deduction model, the following methods can be used:

[0067] If the deduction mode is the apportionment deduction mode, an accounts payable invoice is created based on the amount to be deducted and the remaining write-off amount. Funds are transferred from the prepayment account associated with the target prepayment invoice to the collection account according to the remaining write-off amount, and the accounts payable invoice is paid to the payee in the direction of the payer.

[0068] If the deduction mode is the write-off deduction mode, the funds will be transferred from the prepayment account associated with the target prepayment to the receiving account according to the amount to be deducted.

[0069] In practical applications, there may be situations where changes to the service contract information between the payer and the payee may require changes to the prepayment deduction dimension set by the payer for the prepayment order. To ensure that the prepayment order can be prepaid normally after the service contract information is changed, in an optional implementation of this embodiment, if a dimension change request for any prepayment order is detected, the change deduction dimension submitted by the payer is obtained, the prepayment deduction dimension of any prepayment order is updated based on the change deduction dimension, and the association between any prepayment order and the prepayment account is updated.

[0070] Furthermore, in practical applications, the payer or the prepayment management system can also manage the prepayment accounts associated with the prepayment order. Specifically, if the payer submits account update information for the prepayment account, the prepayment management system will update the prepayment account based on the updated information. In addition, the prepayment account update can be synchronized to the corresponding prepayment order. Moreover, if the prepayment management system detects that a prepayment account has triggered an account update condition, it will update the prepayment account accordingly. This update can involve changing or deleting the prepayment account. Similarly, the prepayment account update can be synchronized to the corresponding prepayment order.

[0071] For example, if the payer submits a request to change the prepaid account, the prepaid management system will change the corresponding prepaid account according to the request. After the prepaid account is changed, the system can also make corresponding changes to the prepaid orders associated with the changed prepaid account. As another example, if the payer submits a request to delete the prepaid account, the system will delete the corresponding prepaid account according to the request. After the prepaid account is deleted, the system will associate the prepaid orders associated with the deleted prepaid account with the prepaid account specified by the payer or with a prepaid account determined or recommended by the system.

[0072] In summary, the prepayment processing method provided in this embodiment, during the prepayment and prepayment deduction process between the payer and payee participating in the credit reporting service agreement signing, creates a prepayment order for the payer to prepay the payee based on the prepayment request submitted by the payer, obtains the prepayment deduction dimension set by the payer for the prepayment order based on the service agreement information with the payee, and, upon obtaining the prepayment voucher submitted by the payee for the prepayment order, prepays funds to the prepayment account associated with the prepayment order based on the prepayment voucher. Payment; Subsequently, upon detecting the prepayment deduction record submitted by the payee, the target prepayment order matching the prepayment deduction record is determined based on the prepayment deduction dimension of each prepayment order from the payer to the payee, and the funds deduction processing of the target prepayment order is carried out. In this way, based on the prepayment of funds from the payer to the payee through prepayment orders, the prepayment deduction of prepayment funds in the prepayment account associated with the prepayment order is carried out according to the prepayment deduction record submitted by the payee, thereby improving the settlement efficiency and accuracy of credit service fund settlement between payers;

[0073] Furthermore, during the process of deducting funds from the target prepayment, the deduction parameters of the target prepayment can be determined, and the deduction mode of the target prepayment can be determined based on the deduction parameters. The funds of the target prepayment can be deducted according to the deduction mode. Different deduction modes can better adapt to the actual settlement scenario and also help improve the effectiveness and success rate of the prepayment being deducted.

[0074] The following example uses a prepayment processing method provided in this embodiment in a credit access scenario as an example, combined with... Figure 3 The method for prepayment processing provided in this embodiment will be further explained below. Figure 3 The method for prepaying funds in credit reporting scenarios includes the following steps.

[0075] Step S302: Based on the prepayment request submitted by the financial institution to the credit reporting agency, create a prepayment order from the financial institution to the credit reporting agency.

[0076] Step S304: Obtain the prepayment deduction dimensions set by the financial institution for the prepayment order.

[0077] Step S306: Obtain the electronic invoice submitted by the credit reporting agency for the prepaid bill.

[0078] Step S308: Transfer funds from the financial institution's fund account based on the amount of funds carried by the electronic invoice, and transfer the transferred funds to the prepaid account created for the prepaid order.

[0079] Step S310: If a prepayment deduction record submitted by a credit reporting agency is detected, the prepayment deduction record is matched with the credit access contract information to determine the payment recipient.

[0080] Step S312: Based on the prepayment deduction records and the prepayment deduction dimensions of each prepayment order associated with the payment recipient, perform prepayment decision processing to obtain the target prepayment order.

[0081] Step S314: Determine the amount to be deducted for the target prepayment based on the prepayment deduction record.

[0082] Step S316: If the amount to be deducted is less than or equal to the remaining write-off amount of the target prepayment, the funds are transferred from the prepayment account associated with the target prepayment to the receiving account according to the amount to be deducted.

[0083] Step S318: If the amount to be deducted is greater than the remaining write-off amount of the target prepayment, create an accounts payable invoice based on the amount to be deducted and the remaining write-off amount.

[0084] Step S320: Transfer funds from the prepayment account associated with the target prepayment to the receiving account according to the remaining write-off amount, and make payment to the credit reporting agency by the financial institution.

[0085] It should be noted that any one or more steps in steps S302 to S320 can be combined with any one or more steps in steps S202 to S208 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features in steps S302 to S320 can be selected and combined with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S302 to S320 can be replaced with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0086] The following example uses a prepayment processing method provided in this embodiment in a credit data collection scenario as an example, combined with... Figure 4 The method for prepayment processing provided in this embodiment will be further explained below. Figure 4 The method for prepaying funds in credit data collection scenarios includes the following steps.

[0087] Step S402: Based on the prepayment request submitted by the credit reporting agency to the data source agency, create a prepayment order from the credit reporting agency to the data source agency.

[0088] Step S404: Obtain the prepayment deduction dimensions set by the credit reporting agency for the prepayment.

[0089] Step S406: Obtain the electronic invoice submitted by the data source institution for the prepaid order.

[0090] Step S408: Based on the amount of funds carried by the electronic invoice, transfer funds from the credit reporting agency's fund account and transfer the transferred funds to the prepayment account created for the prepayment.

[0091] Step S410: If a prepayment deduction record submitted by a credit reporting agency is detected, the prepayment deduction record and the prepayment deduction dimension of each prepayment order are input into the big language model to make a prepayment order matching decision and obtain the target prepayment order.

[0092] Step S412: Determine the deduction parameters of the target prepayment and determine the deduction mode of the target prepayment based on the deduction parameters.

[0093] Step S414: Process the fund deduction for the target prepayment in accordance with the deduction mode.

[0094] It should be noted that any one or more steps in steps S402 to S414 can be combined with any one or more steps in steps S202 to S208 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features in steps S402 to S414 can be selected and combined with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S402 to S414 can be replaced with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0095] This specification provides an embodiment of a prepayment processing device as follows:

[0096] In the above embodiments, a method for prepaying funds is provided, and correspondingly, a device for prepaying funds is also provided, which will be described below with reference to the accompanying drawings.

[0097] Reference Figure 5 The diagram shows a schematic representation of an embodiment of a prepayment processing device provided in this embodiment.

[0098] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0099] This embodiment provides a fund prepayment processing device, the device comprising:

[0100] The prepayment order creation module 502 is configured to create a prepayment order from the payer to the payee based on the prepayment request submitted by the payee in response to the prepayment request submitted by the payer in connection with the signing of the credit reporting service agreement.

[0101] The deduction dimension setting module 504 is configured to obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee;

[0102] The prepayment module 506 is configured to obtain the prepayment voucher submitted by the payee for the prepayment order, and make prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher;

[0103] The deduction processing module 508 is configured to, if a prepayment deduction record submitted by the payee is detected, determine the target prepayment order matching the prepayment deduction record according to the prepayment deduction dimension of each prepayment order from the payer to the payee, and perform fund deduction processing on the target prepayment order.

[0104] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0105] The following is an example of a prepayment processing device provided in this manual:

[0106] Corresponding to the fund prepayment processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a fund prepayment processing device, which is used to execute the fund prepayment processing method provided above. Figure 6 This is a schematic diagram of the structure of a prepayment processing device provided for one or more embodiments of this specification.

[0107] This embodiment provides a prepayment processing device, comprising:

[0108] like Figure 6As shown, device 600 mainly consists of a communication interface 602, a user interface 604, a processor 606, and a data storage 608. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 610. Communication interface 602 enables device 600 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, communication interface 602 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, communication interface 602 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide area wireless interface (e.g., WiMAX or LTE). Of course, communication interface 602 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. Communication interface 602 may also include multiple physical communication interfaces, such as Wi-Fi, Bluetooth, and wide area wireless interfaces. User interface 604 includes receiving operator input and providing output to operators. Therefore, the user interface 604 may include input components such as a keypad, keyboard, touch-sensitive or presence-sensitive panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with a touch-sensitive panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. The user interface 604 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, the user interface 604 may include software, circuitry, or other forms of logic capable of transmitting and receiving data to and from external operator input / output devices. Additionally or alternatively, the device 600 may support remote access from other devices via communication interface 602 or another physical interface (not shown). The user interface 604 may be configured to receive operator input, the position and movement of which may be indicated by indicators or cursors described herein. The user interface 604 may also be configured as a display device for rendering or displaying text fragments.

[0109] Processor 606 may include one or more general-purpose processors and / or special-purpose processors. Data storage 608 may include one or more volatile and / or non-volatile storage components and may be integrated wholly or partially with processor 606. Data storage 608 may include removable and non-removable components.

[0110] Processor 606 is capable of executing program instructions 618 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 608 to perform the various functions described herein. Data storage 608 may comprise a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 600, enable device 600 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 618 by processor 606 may result in processor 606 using data 612. For example, program instructions 618 may include an operating system 622 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 600 and one or more application programs 620 (e.g., a browser, social application, or game application). Similarly, data 612 may include operating system data 616 and application data 614. Operating system data 616 is primarily accessible to operating system 622, while application data 614 is primarily accessible to one or more application programs 620. Application data 614 may reside in a file system visible or hidden by operators of device 600. Application 620 can communicate with operating system 622 through one or more application programming interfaces (APIs). These APIs facilitate application 620 in reading and / or writing application data 614, transmitting or receiving information via communication interface 602, and receiving or displaying information on user interface 604. In some terms, application 620 may be simply referred to as "app". Furthermore, application 620 can be downloaded to device 600 through one or more online app stores or app markets. However, applications can also be installed on device 600 in other ways, such as through a web browser or a physical interface on device 600 (e.g., a USB port).

[0111] In one specific embodiment, the prepayment processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the prepayment processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0112] Based on the prepayment request submitted by the payer to the payee in accordance with the credit reporting service agreement, a prepayment order is created from the payer to the payee.

[0113] Obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee;

[0114] Obtain the prepayment voucher submitted by the payee for the prepayment order, and make a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher;

[0115] If a prepayment deduction record submitted by the payee is detected, the target prepayment order matching the prepayment deduction record is determined according to the prepayment deduction dimension of each prepayment order from the payer to the payee, and the funds deduction processing of the target prepayment order is performed.

[0116] This specification provides an embodiment of a computer-readable storage medium as follows:

[0117] Corresponding to the above-described method for prepayment of funds, based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0118] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0119] Based on the prepayment request submitted by the payer to the payee in accordance with the credit reporting service agreement, a prepayment order is created from the payer to the payee.

[0120] Obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee;

[0121] Obtain the prepayment voucher submitted by the payee for the prepayment order, and make a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher;

[0122] If a prepayment deduction record submitted by the payee is detected, the target prepayment order matching the prepayment deduction record is determined according to the prepayment deduction dimension of each prepayment order from the payer to the payee, and the funds deduction processing of the target prepayment order is performed.

[0123] It should be noted that the embodiments of a computer-readable storage medium described in this specification and the embodiments of a prepayment processing method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0124] This specification provides an example of a computer program product as follows:

[0125] Corresponding to the above-described method for prepayment processing, based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0126] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps:

[0127] Based on the prepayment request submitted by the payer to the payee in accordance with the credit reporting service agreement, a prepayment order is created from the payer to the payee.

[0128] Obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee;

[0129] Obtain the prepayment voucher submitted by the payee for the prepayment order, and make a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher;

[0130] If a prepayment deduction record submitted by the payee is detected, the target prepayment order matching the prepayment deduction record is determined according to the prepayment deduction dimension of each prepayment order from the payer to the payee, and the funds deduction processing of the target prepayment order is performed.

[0131] It should be noted that the embodiments of a computer program product described in this specification and the embodiments of a prepayment processing method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0132] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments. For example, the device embodiment, equipment embodiment and computer-readable storage medium embodiment are all similar to the method embodiment, so the description is relatively simple. When reading the relevant content of the device embodiment, equipment embodiment and computer-readable storage medium embodiment, please refer to the description of the method embodiment.

[0133] While one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is merely one possible execution order among many steps, and does not represent the only execution order. Therefore, when the claims involve method steps, any changes or adjustments to the order of such steps, or the parallelism between steps, are also within the scope of protection of the claims. This specification uses specific terms to describe embodiments of this specification. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0134] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0135] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0136] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 525D, Atmel AT91SAM, Microchip PIC18F25K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0137] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0138] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0139] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0140] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0141] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0142] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0143] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0144] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0145] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0146] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising at least one…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0147] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0148] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A method for processing prepayments, characterized in that, Applied to a prepayment management system, the method includes: Based on the prepayment request submitted by the payer to the payee in accordance with the credit reporting service agreement, a prepayment order is created from the payer to the payee. Obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee; Obtain the prepayment voucher submitted by the payee for the prepayment order, and make a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher; If a prepayment deduction record submitted by the payee is detected, the prepayment deduction record and the prepayment deduction dimension of each prepayment order from the payer to the payee are input into a large language model to perform prepayment order matching decision to obtain the target prepayment order matching the prepayment deduction record, and the funds deduction processing of the target prepayment order is performed. The prepayment matching decision includes: performing anomaly detection on each prepayment based on the prepayment deduction dimension to obtain abnormal prepayment, and determining the prepayment level of the abnormal prepayment and normal prepayment; and determining at least one abnormal prepayment and / or normal prepayment as the target prepayment based on the prepayment level and the prepayment deduction record.

2. The method for prepayment processing according to claim 1, characterized in that, The prepayment deduction dimension is determined based on at least one service contracting object selected by the payer from the service contracting information obtained when signing a credit reporting service agreement with the payee.

3. The method for prepayment processing according to claim 2, characterized in that, The prepayment deduction dimensions include at least one of the following: The payment method includes institutional deductions for prepayments made by the payer to the payee, contract deductions for prepayments made by the payer to the payee, product deductions for prepayments made by the payer to the payee for contracted service products, and contract deductions for prepayments made by the payer to the payee for service contracts.

4. The method for prepayment processing according to claim 1, characterized in that, The step of making advance payments to the prepayment account associated with the prepayment order based on the prepayment voucher includes: Based on the amount of funds carried by the prepayment voucher, funds are transferred out from the payer's funds account and then transferred to the prepayment account created for the prepayment voucher.

5. The method for prepayment processing according to claim 1, characterized in that, The process of deducting funds from the target prepayment includes: The amount to be deducted for the target prepayment is determined based on the prepayment deduction record; If the amount to be deducted is less than or equal to the remaining write-off amount of the target prepayment, the funds will be transferred from the prepayment account associated with the target prepayment to the receiving account according to the amount to be deducted.

6. The method for prepayment processing according to claim 5, characterized in that, The process of deducting funds from the target prepayment also includes: If the amount to be deducted is greater than the remaining write-off amount of the target prepayment, an accounts payable invoice is created based on the amount to be deducted and the remaining write-off amount; The remaining amount to be reimbursed is transferred from the prepayment account associated with the target prepayment to the receiving account, and the payer makes payment to the payee's payable bill.

7. The method for prepayment processing according to claim 1, characterized in that, The process of deducting funds from the target prepayment includes: Determine the deduction parameters of the target prepayment, and determine the deduction mode of the target prepayment based on the deduction parameters; The funds for the target prepayment will be deducted according to the deduction model described above.

8. The method for prepaying funds according to claim 1, characterized in that, Also includes: If a dimension change request is detected for any of the prepaid orders, the change deduction dimension submitted by the payer is obtained, the prepayment deduction dimension of any prepaid order is updated based on the change deduction dimension, and the association between any prepaid order and the prepayment account is updated.

9. The method for prepaying funds according to claim 1, characterized in that, The service contract information includes: Credit access agreement information obtained by credit reporting agencies and credit access agencies signing credit access agreements; credit data agreement information obtained by data source agencies and credit reporting agencies signing data agreements.

10. A prepayment processing device, characterized in that, The device, which operates within the prepayment management system, includes: The prepayment order creation module is configured to create a prepayment order from the payer to the payee based on the prepayment request submitted by the payee in response to the prepayment request signed by the payer participating in the credit reporting service agreement. The deduction dimension setting module is configured to obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee; The prepayment module is configured to obtain the prepayment voucher submitted by the payee for the prepayment order, and make prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher; The deduction processing module is configured to, if a prepayment deduction record submitted by the payee is detected, input the prepayment deduction record and the prepayment deduction dimension of each prepayment order from the payer to the payee into a large language model to perform prepayment order matching decision to obtain the target prepayment order matching the prepayment deduction record, and perform fund deduction processing on the target prepayment order; The prepayment matching decision includes: performing anomaly detection on each prepayment based on the prepayment deduction dimension to obtain abnormal prepayment, and determining the prepayment level of the abnormal prepayment and normal prepayment; and determining at least one abnormal prepayment and / or normal prepayment as the target prepayment based on the prepayment level and the prepayment deduction record.

11. A prepayment processing device, characterized in that, The device includes: A processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Based on the prepayment request submitted by the payer to the payee in accordance with the credit reporting service agreement, a prepayment order is created from the payer to the payee. Obtain the prepayment deduction dimension set by the payer for the prepayment order based on the service contract information with the payee; Obtain the prepayment voucher submitted by the payee for the prepayment order, and make a prepayment to the prepayment account associated with the prepayment order based on the prepayment voucher; If a prepayment deduction record submitted by the payee is detected, the prepayment deduction record and the prepayment deduction dimension of each prepayment order from the payer to the payee are input into a large language model to perform prepayment order matching decision to obtain the target prepayment order matching the prepayment deduction record, and the funds deduction processing of the target prepayment order is performed. The prepayment matching decision includes: performing anomaly detection on each prepayment based on the prepayment deduction dimension to obtain abnormal prepayment, and determining the prepayment level of the abnormal prepayment and normal prepayment; and determining at least one abnormal prepayment and / or normal prepayment as the target prepayment based on the prepayment level and the prepayment deduction record.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store computer-executable instructions that, when executed, implement the steps of the method of claim 1.

Images