Data processing method and device based on transaction link tracing, equipment and medium

Abstract

The invention relates to the technical field of artificial intelligence and management, and discloses a data processing method, device, equipment and medium based on transaction link traceability, and the method comprises the steps: obtaining a previous contract of a leasing customer, the previous contract being a historical contract that the leasing customer cooperates with a historical purchaser enterprise in the industry for a target leasing item; determining the enterprise classification of the historical purchaser enterprises according to the previous contract; determining an ownership file handover strategy of the target rental item according to the enterprise classification, and executing a flow set by the ownership file handover strategy; after the process is executed, obtaining an acceptance check result of the target rental item and a payment condition check result of the rental customer; and when the acceptance check result and the payment condition check result both pass the check, calling a payment service interface and completing a payment handover process. The method is applied to a financial science and technology business processing scene, a cooperation mechanism of ownership handover verification and loan approval is constructed, and the efficiency of a leasing loan process and the customer experience can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of artificial intelligence and management, and is applied to the financial technology business processing scene, and particularly relates to a data processing method and device based on transaction link tracing, equipment and medium. BACKGROUND

[0002] In the leaseback business mode of the financing lease industry, the customer sells the self-owned equipment to the financing lease company and then leases back for use, and the two parties negotiate to determine the transaction framework including core clauses such as lease period, rent payment method, interest rate structure, equipment ownership attribution, and maintenance responsibility. The mode has formed a standardized legal document signing process, but in the loan link after the contract is signed, the existing process exposes significant technical defects.

[0003] According to industry specifications, the transfer of the right of equipment ownership must be confirmed before the loan is made to ensure the legality of the transfer of the right of property. However, in the information verification link of the right of property certificate, the system cannot intelligently associate the right of property proof file, resulting in the need for manual intervention in key tasks such as the validity confirmation of the previous contract and the verification of the right of equipment ownership. This technical breakpoint forces the operator to repeatedly verify multiple source information, not only increasing additional steps and costs, but also leading to process fragmentation and significantly prolonging the loan approval time.

[0004] In summary, the existing technical system fails to build a coordination mechanism for the transfer of the right of property verification and loan approval, resulting in low efficiency of the loan process, which further affects the customer experience. SUMMARY

[0005] The present application provides a data processing method and device based on transaction link tracing, equipment and medium to solve the problem of low efficiency in the existing leaseback loan approval.

[0006] In a first aspect, a data processing method based on transaction link tracing is provided, comprising:

[0007] Obtaining a previous contract of a leaseback customer, wherein the previous contract is a historical contract between the leaseback customer and a historical purchaser in the industry for cooperation on a target lease object;

[0008] Determining the enterprise classification of the historical purchaser according to the previous contract;

[0009] Determining the right of property file transfer strategy of the target lease object according to the enterprise classification, and executing the process set by the right of property file transfer strategy;

[0010] After the process is executed, obtaining the acceptance result of the target lease object and the payment condition verification result of the leaseback customer;

[0011] When the acceptance result and the payment condition checking result are both checking passed, a payment service interface is called and a preset handover payment process is completed.

[0012] In a second aspect, a data processing device based on transaction link tracing is provided, comprising:

[0013] A contract obtaining module is configured to obtain a previous-hand contract of a return lease customer, the previous-hand contract being a historical contract between the return lease customer and a historical purchaser in the industry for cooperation on a target lease object;

[0014] A type determining module is configured to determine an enterprise classification of the historical purchaser according to the previous-hand contract;

[0015] A strategy determining module is configured to determine a title document handover strategy of the target lease object according to the enterprise classification, and execute a process set by the title document handover strategy;

[0016] A result obtaining module is configured to obtain an acceptance result of the target lease object and a payment condition checking result of the return lease customer after the process is executed;

[0017] A handover payment module is configured to call a payment service interface and complete a preset handover payment process when the acceptance result and the payment condition checking result are both checking passed.

[0018] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement the steps of the data processing method based on transaction link tracing.

[0019] In a fourth aspect, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the steps of the data processing method based on transaction link tracing.

[0020] The scheme realized by the data processing method and device based on transaction link tracing, the computer device, and the medium can establish traceability of the target rental transaction link by obtaining the previous-hand contract in the historical cooperation record of the rental customer; different enterprise classifications can be matched for the historical purchase enterprise based on the transaction experience of the target rental, and the ownership file handover strategy of the target rental is determined according to different enterprise classifications, so as to realize dynamic adaptation of the ownership file handover process; the process set by the ownership file handover strategy is automatically executed by the strategy engine, manual intervention in processing the ownership handover verification is reduced, and the process efficiency is significantly improved; after the ownership handover process is executed, the acceptance result of the target rental and the payment condition inspection result of the rental customer are automatically obtained, and when both the inspection results pass the inspection, the payment service interface is called to complete the preset handover payment process, so as to realize the cooperative mechanism of the ownership handover verification and the loan approval, and effectively improve the efficiency of the rental loan process and the customer experience. BRIEF DESCRIPTION OF DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the description of the embodiments of the present application. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0022] Figure 1 is an exemplary system architecture diagram of the data processing method based on transaction link tracing in an embodiment of the present application;

[0023] Figure 2 is a flowchart of the data processing method based on transaction link tracing in an embodiment of the present application;

[0024] Figure 3 is Figure 2 is a specific embodiment flowchart of step S30 in

[0025] Figure 4 is Figure 2 is a specific embodiment flowchart of step S40 in

[0026] Figure 5 is a structural schematic diagram of the data processing device based on transaction link tracing in an embodiment of the present application;

[0027] Figure 6 is a structural schematic diagram of the computer device in an embodiment of the present application. DETAILED DESCRIPTION

[0028] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terms used in the specification are intended to describe the particular embodiments and are not intended to limit the application; the terms "include" and "have" and their any variations used in the specification and the claims and the above description of drawings are intended to cover the non-exclusive inclusion; the terms "first", "second" and the like used in the specification and the claims and the above description of drawings are intended to distinguish different objects, not to describe a particular order.

[0029] Reference herein to "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily mutually exclusive of one another. It is expressly understood that the embodiments described herein are merely examples and are not intended to limit the scope of the application.

[0030] In order to make the person skilled in the art better understand the scheme of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the drawings below.

[0031] As shown in Figure 1 The system architecture 100 can include a terminal device 101, a network 102 and a server 103, and the terminal device 101 can be a notebook computer 1011, a tablet computer 1012 or a mobile phone 1013. The network 102 is a medium for providing a communication link between the terminal device 101 and the server 103. The network 102 can include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0032] The user can use the terminal device 101 to interact with the server 103 through the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0033] The terminal device 101 can be various electronic devices with a display screen and supporting web browsing, in addition to the notebook computer 1011, the tablet computer 1012 or the mobile phone 1013, the terminal device 101 can also be an electronic book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 player (Moving Picture Experts Group Audio Layer IV), a laptop computer and a desktop computer, etc.

[0034] The server 103 can be a server providing various services, for example, a background server providing support for a page displayed on the terminal device 101.

[0035] It should be noted that the data processing method based on transaction link tracing provided by the embodiments of the present application is generally executed by a server / terminal device, and accordingly, the data processing device based on transaction link tracing is generally arranged in the server / terminal device.

[0036] It should be understood that, Figure 1 The number of terminal devices, networks and servers in

[0037] Referring to Figure 2 , it is shown that Figure 2 a flowchart of the data processing method based on transaction link tracing provided by the embodiments of the present application, comprising the following steps:

[0038] S20: Obtain the previous contract of the return lease customer, wherein the previous contract refers to a historical contract between the return lease customer and a historical purchaser enterprise in the industry for cooperation on the target lease.

[0039] The data processing method based on transaction link tracing provided by the present application can be applied to an intelligent data processing engine in various application scenarios, and the intelligent data processing engine is usually realized by a server, the server is connected with a client through a network, and the server can obtain the previous contract of the return lease customer through the client. The client can include but is not limited to various personal computers, notebook computers, smart phones, tablet computers and portable wearable devices. The server can be realized by an independent server or a server cluster composed of multiple servers. The present application will be described in detail through specific embodiments.

[0040] Specifically, the process of obtaining the pre-hand contract of the leasing customer can be, for example, that a data processing application is pre-installed on the client of the enterprise, when the enterprise completes the electronic signing of the current leasing contract with the leasing customer and needs to lend money to the leasing customer, the application is used to collect the pre-hand contract of the target lease from the leasing customer. The pre-hand contract refers to the historical contract between the leasing customer and the historical buyer enterprise in the industry for the target lease. Leasing refers to the transaction process in which the leasing customer sells assets (i.e., target lease) to a financial leasing enterprise (i.e., buyer enterprise) and then rents back the assets for continued use. The leasing customer refers to the asset owner in the leasing transaction. The historical buyer enterprise refers to the enterprise that has ever purchased assets from the leasing customer in the financial leasing industry. The target lease refers to the lease asset in the leasing transaction, i.e., the asset sold by the leasing customer to the financial leasing enterprise and then rented back.

[0041] For example, in the financial industry, after a leasing customer completes the contract signing of the leasing transaction with a financial leasing enterprise for a numerical control machine (i.e., target lease), the leasing customer submits a loan application to the financial leasing enterprise through an application for leasing payment. After receiving the loan application, the financial leasing enterprise collects one or more pre-hand contracts of the target lease from the leasing customer. The pre-hand contract is a historical contract between the leasing customer and the historical buyer enterprise in the industry for the target lease.

[0042] S30: determining the enterprise classification of the historical buyer enterprise according to the pre-hand contract;

[0043] In the embodiment, the historical buyer enterprise can be the current financial leasing enterprise that signs a cooperation contract with the leasing customer, which has ever signed a cooperation contract with the leasing customer for the target lease; can be an enterprise that establishes a data sharing mechanism with the current financial leasing enterprise, which has ever signed a cooperation contract with the leasing customer for the target lease; or can be other enterprises that have ever signed a cooperation contract with the leasing customer for the target lease (i.e., the enterprise does not establish a data sharing mechanism with the current financial leasing enterprise).

[0044] Specifically, classification standards for classifying each enterprise are pre-established, for example, the current financial leasing enterprise that signs a cooperation contract with the leasing customer and the enterprise that establishes a data sharing mechanism with the current financial leasing enterprise are classified as target enterprises; and other enterprises that do not establish a data sharing mechanism with the current financial leasing enterprise are classified as non-target enterprises. For the obtained pre-hand contract, the historical buyer enterprise in the pre-hand contract is extracted, and the enterprise classification of the historical buyer enterprise is determined according to the pre-established classification standards.

[0045] In some embodiments, the historical buyer enterprise is determined by referring toFigure 3 , step S30, i.e. determining the enterprise classification of the historical buyer enterprise according to the previous contract, can include steps S301-S304 as follows:

[0046] S301: performing named entity recognition on the previous contract, and extracting the buyer enterprise name in the previous contract based on the recognition content;

[0047] Specifically, the named entity recognition is performed on the previous contract by using a pre-trained recognition model or a pre-set regular expression. For example, a BERT-wwm model is trained for financial field text to obtain a recognition model, and the recognition model is used to recognize the enterprise name, contract number and other entities in the previous contract to obtain the recognition content. Alternatively, a regular expression for matching entities such as “Party A” and “Party B / Buying Party” is pre-constructed, and the regular expression is used to match the entity content corresponding to “Party A” and “Party B / Buying Party” from the previous contract as the recognition content of the previous contract. The buyer enterprise name of the previous contract is extracted from all the recognition content.

[0048] S302: obtaining a preset target enterprise list, and sequentially matching each target enterprise name in the target enterprise list with the buyer enterprise name;

[0049] Specifically, a preset target enterprise list is obtained, and the target enterprise list includes one or more target enterprise names. For example, the target enterprise list can include the enterprise names of the financial leasing enterprises that currently sign cooperation with the leaseback client, or the enterprise names of the enterprises that establish a data sharing mechanism with the current financial leasing enterprise. Each target enterprise name in the target enterprise list is sequentially matched with the buyer enterprise name. For example, a similarity calculation algorithm can be used to sequentially calculate the similarity between each target enterprise name and the buyer enterprise name, so as to subsequently determine the target enterprise name that matches the buyer enterprise name based on the similarity.

[0050] S303: when there is a target enterprise name that matches the buyer enterprise name, the historical buyer enterprise is divided into a target enterprise;

[0051] Specifically, when there is a target enterprise name that matches the buyer enterprise name, i.e. when the similarity between the target enterprise name and the buyer enterprise name meets a preset threshold, it is determined that there is a target enterprise name that matches the buyer enterprise name, and at this time, the historical buyer enterprise is divided into a target enterprise. The preset threshold can be set according to the historical matching success rate of the enterprise name in the financial leasing industry.

[0052] S304: when there is no target enterprise name that matches the buyer enterprise name, the historical buyer enterprise is divided into a non-target enterprise.

[0053] Specifically, when there is no target enterprise name matching the buyer enterprise name, that is, when the similarity between all target enterprise names and the buyer enterprise name does not meet the preset threshold, it is determined that there is no target enterprise name matching the buyer enterprise name, at this time, the historical buyer enterprise is divided into a non-target enterprise.

[0054] In this embodiment, the name of the buyer enterprise is automatically extracted from the previous contract through named entity recognition, reducing the need for manual reading and analysis of the contract and improving processing efficiency. By accurately matching each target enterprise name in the target enterprise list with the name of the buyer enterprise extracted from the contract, the accuracy of enterprise classification is ensured. This embodiment realizes the rapid and accurate classification of historical buyer enterprises by automatically processing contract information, accurately matching enterprise names, and using an explicit and efficient classification method.

[0055] S40: According to the enterprise classification, determine the ownership file transfer strategy of the target lease, and execute the process set by the ownership file transfer strategy;

[0056] In this embodiment, the ownership file is the original ownership proof file of the lease, which is used to prove that the owner has the right to sell and lease the lease; the ownership file can include the purchase invoice, property certificate, non-mortgage certificate or other files that can prove the original ownership of the lease (such as equipment, machinery and other movable property). Different enterprise classifications correspond to different ownership file transfer strategies and processes, for example, when the historical buyer enterprise in the previous contract is the current financing leasing enterprise or an enterprise that establishes a data sharing mechanism with the current financing leasing enterprise, the historical transaction record of the target lease can be directly obtained, and the ownership state of the target lease is confirmed according to the historical transaction record, therefore, for this enterprise classification, the ownership file of the target lease can be transferred without the need to transfer the ownership file of the target lease. The ownership file transfer strategy and process are set to obtain the historical transaction record of the target lease; when the historical buyer enterprise in the previous contract is an enterprise that does not establish a data sharing mechanism with the current financing leasing enterprise, the historical electronic invoice of the target lease can be obtained, and the ownership state of the target lease is confirmed according to the identification content of the historical electronic invoice, therefore, for this enterprise classification, the ownership file of the target lease can also be transferred without the need to transfer the ownership file of the target lease. The ownership file transfer strategy and process are set to obtain the historical electronic invoice of the target lease.

[0057] Specifically, based on the pre-set correspondence between different enterprise classifications and ownership document handover strategies, and according to the enterprise classification of historical purchasing enterprises, the corresponding ownership document handover strategies for the target leased property are matched. Among them, the ownership document handover strategies may include no-handover-required strategies and handover-required strategies. No-handover-required strategies refer to strategies that do not require online and offline ownership document handovers; and handover-required strategies refer to strategies that require online or offline ownership document handovers. Optionally, the no-handover-required strategies can be further divided into historical transaction record acquisition strategies and historical electronic invoice acquisition strategies on the premise that no ownership document handovers are required. Specifically, different ownership document handover strategies are correspondingly set with relevant processes. According to the matched ownership document handover strategy, a policy engine is used to drive the automated execution of the processes set by the ownership document handover strategy.

[0058] In some embodiments, the enterprise classification includes a target enterprise. Step S40, i.e., determining a policy for handing over the ownership document of the target leased property based on the enterprise classification and executing the process set by the policy, may include the following steps:

[0059] If the historical purchaser is the target enterprise, the ownership document handover strategy for the target leased property is determined to be the first no-handover strategy;

[0060] Specifically, the classification criteria for target enterprises are pre-set. For example, the target enterprises may include the current financial leasing enterprise that has signed a cooperation agreement with the leaseback customer for the target leased item, and the enterprise that has established a data sharing mechanism with the current financial leasing enterprise, wherein the current financial leasing enterprise and the enterprise that has established a data sharing mechanism are both enterprises that have signed a cooperation agreement with the leaseback customer for the target leased item. If the historical purchasing enterprise is determined to be the target enterprise, that is, the historical purchasing enterprise is the current financial leasing enterprise or the enterprise that has established a data sharing mechanism with the current financial leasing enterprise, then the strategy for handing over the ownership documents of the target leased item is determined to be the first strategy that does not require handover. The process content of the first strategy that does not require handover is set to not require handover of the ownership documents of the target leased item, and the ownership status of the target leased item is determined by obtaining historical transaction data of the historical purchasing enterprise and the leaseback customer that have cooperated on the target leased item.

[0061] Based on the first no-handover-required strategy, obtaining historical transaction data of the historical purchasing enterprise and the leaseback customer regarding the target leased item;

[0062] Specifically, after the ownership file handover strategy of the target lease object is determined as the first no handover strategy, based on the process content set by the first no handover strategy, the historical transaction data of the historical purchaser enterprise and the lease-back client in cooperation with the target lease object is obtained. For example, when the historical purchaser enterprise is the current financial leasing enterprise, the historical transaction data of the current financial leasing enterprise and the lease-back client in cooperation with the target lease object is queried through the historical transaction platform in the enterprise according to the identification ID of the lease-back client. When the historical purchaser enterprise is an enterprise that has established a data sharing mechanism with the current financial leasing enterprise, the historical transaction data of the enterprise that has established the data sharing mechanism and the lease-back client is called through the data sharing API interface between enterprises according to the identification ID of the lease-back client.

[0063] It should be noted that the current financial leasing enterprise or the enterprise that has established a data sharing mechanism with the current financial leasing enterprise has historical transaction data of the lease-back client in cooperation with the target lease object, which can prove that the ownership status of the target lease object has been verified in the historical transaction process, and the original ownership of the target lease object belongs to the lease-back client.

[0064] The historical transaction data is pushed to the lease object acceptance node and the payment condition verification node.

[0065] Specifically, the obtained historical transaction data is pushed to the lease object acceptance node and the payment condition verification node to trigger the execution of the related processes of the lease object acceptance node and the payment condition verification node. The lease object acceptance node is used to verify the technical specifications, performance parameters, quality standards and the like of the target lease object; and the payment condition verification node is used to confirm whether the lease-back client meets the payment conditions required by the contract, which can include providing necessary payment vouchers, reaching a specific payment stage (such as clear ownership status of the lease object, qualified lease object acceptance and the like).

[0066] In the embodiment, when the historical purchaser enterprise is identified as the target enterprise, the ownership file handover strategy of the target lease object is directly determined as the first no handover strategy, unnecessary ownership file handover process is avoided, time and resources are saved, and overall efficiency is improved. By obtaining the historical transaction data of the historical purchaser enterprise and the lease-back client in cooperation with the target lease object, and pushing the historical transaction data to the lease object acceptance node and the payment condition verification node, the historical transaction data can be effectively utilized to simplify the ownership file handover process, so that when it is determined that the ownership status of the target lease object has been verified in the historical transaction process, the acceptance process of the lease object and the verification of the payment condition are directly triggered, and the completion of the loan process is further accelerated.

[0067] In some embodiments, with reference to Figure 4The enterprise classification includes a non-target enterprise, step S40, that is, determining the title document handover strategy of the target lease according to the enterprise classification, and executing the process set by the title document handover strategy can include the following steps S401-S405:

[0068] S401: If the historical purchaser enterprise is a non-target enterprise, historical electronic invoices of the historical purchaser enterprise cooperating with the lease customer on the target lease are obtained;

[0069] Specifically, the division standard of the target enterprise is set in advance, for example, the non-target enterprise can be an enterprise that does not establish a data sharing mechanism with the current financial leasing enterprise, wherein the enterprise that does not establish a data sharing mechanism is an enterprise that has ever signed a cooperation agreement with the lease customer on the target lease. If it is determined that the historical purchaser enterprise is a non-target enterprise, that is, the historical purchaser enterprise is an enterprise that does not establish a data sharing mechanism with the current financial leasing enterprise, historical electronic invoices of the historical purchaser enterprise cooperating with the lease customer on the target lease are obtained.

[0070] S402: The content of the historical electronic invoice is identified by using image recognition technology to obtain invoice identification data;

[0071] Specifically, the content of the obtained historical electronic invoice is identified by using image recognition technology, and the key information on the historical electronic invoice is extracted to form invoice identification data. The image recognition process can include preprocessing of the historical electronic invoice, such as denoising, binarization, etc.; the text information on the invoice is identified by using OCR (Optical Character Recognition) technology, and is stored as structured invoice identification data. The invoice identification data can include but is not limited to: invoice basic information (such as invoice number, invoice date, purchaser information, seller information, etc.), transaction details (such as lease description, transaction amount, tax information, etc.), anti-fake identification, etc.

[0072] In some embodiments, step S402, that is, the content of the historical electronic invoice is identified by using image recognition technology to obtain invoice identification data, can include the following steps:

[0073] The historical electronic invoice is identified by using image recognition technology, and the identified invoice core area is obtained;

[0074] Specifically, the historical electronic invoice is preprocessed by using image recognition technology, such as denoising, binarization, etc.; the preprocessed historical electronic invoice is identified by using edge detection, shape analysis and machine learning model, etc., and the identified invoice core area is obtained. The invoice core area can include the invoice frame, the title bar, the text information area, etc.

[0075] adjusting contrast and brightness of the invoice core area to enhance separation degree of text information and background in the invoice core area;

[0076] Specifically, the contrast and brightness of the invoice core area are identified, and an image enhancement algorithm is used to adjust the identified contrast and brightness to obtain an adjusted invoice core area and separation degree of text information and background in the area. It is determined whether the separation degree of text information and background meets a preset threshold. If yes, an enhanced invoice core area is generated.

[0077] A preset invoice template is obtained, and the invoice template is matched with the enhanced invoice core area to extract invoice element content in the invoice core area as invoice recognition data.

[0078] Specifically, a preset invoice template is obtained, which is obtained based on a standard format of an invoice and includes expected invoice element positions and formats. The enhanced invoice core area is matched with the invoice template, and an OCR technique is used to identify invoice element content in the invoice core area. The identified invoice element content is matched with invoice element positions and formats defined in the invoice template. If the matching is successful, corresponding invoice element content is extracted as invoice recognition data.

[0079] In this embodiment, image recognition technology is used to identify the invoice core area of a historical electronic invoice, and the contrast and brightness of the invoice core area are adjusted to enhance the separation degree of text information and background, which helps to more clearly identify text information on the invoice and improves the accuracy of identification. A preset invoice template is matched with the enhanced invoice core area to automatically extract invoice element content as invoice recognition data, effectively reducing the step of manually entering data and thus reducing the data entry error rate caused by human negligence or errors.

[0080] S403: performing invoice verification according to the invoice recognition data to obtain an invoice verification result;

[0081] Specifically, invoice verification is performed according to invoice recognition data to verify the authenticity and validity of a historical electronic invoice to obtain an invoice verification result. The process of invoice verification can include interfacing with an invoice verification platform such as a tax department or an invoice issuer to verify whether invoice number, invoice date, transaction amount, buyer / seller information, access identifier and other information of the historical electronic invoice are true and correct to obtain an invoice verification result.

[0082] In some embodiments, step S403, i.e., performing invoice verification according to the invoice recognition data to obtain an invoice verification result, can include the following steps:

[0083] acquire a preset invoice verification rule, the invoice verification rule being a rule for verifying one or more invoice identification data;

[0084] Specifically, the preset invoice verification rule is acquired, which is a rule for verifying one or more invoice identification data, which can include but is not limited to invoice format requirements, whether there is an invoice number, validity of the invoice date, whether the transaction amount is correct, whether the buyer / seller information matches the contract, whether there is a forgery identification, etc.

[0085] The invoice verification rule is used to sequentially verify the invoice identification data to obtain an invoice verification result.

[0086] Specifically, the preset invoice verification rule is used to sequentially verify the invoice identification data, for example, the invoice verification rule is used to sequentially verify the invoice number, invoice date, transaction amount, buyer / seller information, access identification, etc. in the invoice identification data, and the verification results of each information are recorded to form an invoice verification result. The invoice verification result can include verification pass, verification failure or further verification, etc.

[0087] Invoice verification parameters are extracted from the invoice identification data, an interface of an invoice verification platform is called and the invoice verification parameters are input, and an invoice verification result returned by the invoice verification platform according to the invoice verification parameters is acquired;

[0088] Specifically, invoice verification parameters are extracted from the invoice identification data, which are a series of key information used for invoice authenticity verification on the invoice verification platform. Different invoice verification platforms stipulate different invoice verification parameters, such as invoice number, buyer / seller information, lease description and verification code, etc. For the extracted invoice verification parameters, the interface of the invoice verification platform is called and the invoice verification parameters are input, so that the invoice verification platform retrieves the corresponding invoice verification result according to the invoice verification parameters and returns, and then the invoice verification result returned by the invoice verification platform according to the invoice verification parameters is acquired. The invoice verification result can be a status code or status information, indicating whether the historical electronic invoice is real and valid.

[0089] The invoice verification result is obtained by combining the invoice verification result and the invoice verification result.

[0090] Specifically, the invoice verification result is obtained by combining the invoice verification result and the invoice verification result. If the invoice verification result is verification pass and the invoice verification result indicates that the historical electronic invoice is real and valid, the invoice verification result is pass verification. Otherwise, if any result indicates that the historical electronic invoice has a problem, the invoice verification result is fail verification.

[0091] In this embodiment, the invoice recognition data is preliminarily checked by the preset invoice checking rule, which helps to identify possible errors or inconsistencies. Subsequently, the secondary verification is performed by calling the interface of the invoice checking platform and using professional invoice checking services, which can further improve the accuracy of invoice verification. The double verification process complements each other, reducing the misjudgment that may occur in a single verification method.

[0092] S404: If the invoice verification result is that the historical electronic invoice passes the verification, the ownership file transfer strategy of the target rental object is determined as a second no-transfer strategy;

[0093] Specifically, if the invoice verification result is that the historical electronic invoice passes the verification, the ownership file transfer strategy of the target rental object is determined as a second no-transfer strategy. The process content of the second no-transfer strategy is set as no need to transfer the ownership file of the target rental object, and the invoice verification result is pushed to the subsequent rental object acceptance node and payment condition checking node.

[0094] It should be noted that if the historical electronic invoice passes the verification, it can be indicated that the target rental object has passed the verification of the historical purchaser enterprise in the historical transaction process, and the original ownership of the target rental object belongs to the leaseback client.

[0095] S405: Based on the second no-transfer strategy, the invoice verification result is pushed to the rental object acceptance node and the payment condition checking node.

[0096] Specifically, based on the process content set by the second no-transfer strategy, the invoice verification result is pushed to the rental object acceptance node and the payment condition checking node to trigger the execution of the related processes of the rental object acceptance node and the payment condition checking node.

[0097] In this embodiment, when the historical purchaser enterprise is not the target enterprise, the historical electronic invoice of the historical purchaser enterprise and the leaseback client in cooperation with the target rental object is obtained, and the content of the invoice is identified and verified, which can indirectly prove the authenticity and legality of the target rental object in the historical transaction process. After confirming the ownership of the target rental object, the second no-transfer strategy is adopted, i.e., no additional ownership file transfer process is required, which effectively simplifies the procedures of rental object ownership transfer and improves the processing efficiency of leaseback loans.

[0098] In some embodiments, if the invoice verification result of the historical electronic invoice is not passed, the original ownership of the target rental object needs to be further confirmed. Specifically, after step S403, i.e., according to the invoice recognition data to perform invoice verification, the invoice verification result is obtained, the following steps can also be included:

[0099] if the invoice verification result is that the historical electronic invoice fails the verification, the ownership file handover strategy of the target rental object is determined as a required handover strategy;

[0100] Based on the required handover strategy, a preset online or offline ownership file handover process is performed.

[0101] Specifically, if the invoice verification result is that the historical electronic invoice fails the verification, the ownership file handover strategy of the target rental object is determined as a required handover strategy. The required handover strategy refers to a strategy that requires online or offline ownership file handover. According to the required handover strategy, a preset online or offline ownership file handover process is performed, such as performing file handover on a part of the ownership files through online handover and performing file handover on another part of the ownership files through offline handover according to preset ownership file handover requirements.

[0102] S50: After the process is completed, an acceptance result of the target rental object and a payment condition verification result of the return rental client are obtained;

[0103] In this embodiment, after the handover process of the ownership file handover strategy is completed, an acceptance result of the target rental object and a payment condition verification result of the return rental client are obtained. The acceptance result is a result obtained by verifying the technical specifications, performance parameters, quality standards, etc. of the target rental object in the rental object acceptance node. The payment condition verification result is a result obtained by verifying whether the return rental client meets the contract-required payment conditions in the payment condition verification node. For example, the credit record, financial situation, historical rental payment record, etc. of the return rental client are checked to determine whether the return rental client meets the contract-required payment conditions.

[0104] S60: When the acceptance result and the payment condition verification result are both verified, a payment service interface is called and a preset handover payment process is completed.

[0105] Specifically, when the acceptance result of the target rental object and the payment condition verification result of the return rental client are both verified, a loan request is sent to the payment service system, a corresponding payment service interface is called, and a preset handover payment process is completed according to the loan amount, payment method, payment account of the return rental client, etc. specified in the current return rental contract. For example, the payment service system returns a payment result to confirm whether the payment is successful; if the payment is successful, relevant records are updated, such as the transfer of ownership of the target rental object, the loan record of the return rental client, etc.

[0106] Optionally, when the acceptance result of the target rental object or the payment condition verification result of the return rental client is not verified, the payment delivery process is ended.

[0107] The data processing method based on transaction link tracing provided by the embodiment of the present application can establish traceability of a target lease transaction link by obtaining a previous contract in historical cooperation records of a lease customer, can match different enterprise categories for a historical purchase enterprise based on transaction experience of the target lease, can determine a property file handover strategy of the target lease according to different enterprise categories, and can realize dynamic adaptation of a property file handover process. The strategy engine can drive automatic execution of a process set by the property file handover strategy, reduce manual intervention in processing property handover verification, and significantly improve process efficiency. The method can automatically obtain acceptance results of the target lease and payment condition inspection results of the lease customer after the property handover process is completed, and can complete a preset handover payment process by calling a payment service interface when both inspection results pass the inspection, thereby realizing a collaborative mechanism of property handover verification and loan approval and effectively improving efficiency of a lease loan process and customer experience.

[0108] It should be understood that the size of the serial number of each step in the above embodiment does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0109] In an embodiment, a data processing device based on transaction link tracing is provided, which corresponds to the data processing method based on transaction link tracing in the above embodiment. As shown in the figure, the data processing device based on transaction link tracing includes a contract acquisition module 201, a type determination module 202, a strategy determination module 203, a result acquisition module 204, and a handover payment module 205. The functions of each module are described in detail as follows: Figure 5

[0110] The contract acquisition module 201 is configured to obtain a previous contract of a lease customer, wherein the previous contract is a historical contract between the lease customer and a historical purchase enterprise in the industry for cooperation on a target lease;

[0111] The type determination module 202 is configured to determine an enterprise category of the historical purchase enterprise according to the previous contract;

[0112] The strategy determination module 203 is configured to determine a property file handover strategy of the target lease according to the enterprise category, and execute a process set by the property file handover strategy;

[0113] The result acquisition module 204 is configured to obtain acceptance results of the target lease and payment condition inspection results of the lease customer after the process is completed;

[0114] ​The handover payment module 205 is configured to call a payment service interface and complete a preset handover payment process when the acceptance result and the payment condition checking result are both passed.

[0115] In an embodiment, the enterprise classification includes a target enterprise, and the strategy determination module 203 is specifically configured to:

[0116] If the historical buyer enterprise is a target enterprise, the ownership file handover strategy of the target lease object is determined as a first no-handover strategy.

[0117] Based on the first no-handover strategy, historical transaction data of the historical buyer enterprise cooperating with the lease customer on the target lease object is obtained.

[0118] The historical transaction data is pushed to the lease object acceptance node and the payment condition checking node.

[0119] In an embodiment, the enterprise classification includes a non-target enterprise, and the strategy determination module 203 is specifically configured to:

[0120] If the historical buyer enterprise is a non-target enterprise, historical electronic invoices of the historical buyer enterprise cooperating with the lease customer on the target lease object are obtained.

[0121] An image recognition technology is used to perform content recognition on the historical electronic invoices to obtain invoice recognition data.

[0122] Invoice verification is performed according to the invoice recognition data to obtain an invoice verification result.

[0123] If the invoice verification result is that the historical electronic invoices pass the verification, the ownership file handover strategy of the target lease object is determined as a second no-handover strategy.

[0124] Based on the second no-handover strategy, the invoice verification result is pushed to the lease object acceptance node and the payment condition checking node.

[0125] In an embodiment, the strategy determination module 203 is further configured to:

[0126] An image recognition technology is used to perform region recognition on the historical electronic invoices to obtain recognized invoice core regions.

[0127] The contrast and brightness of the invoice core regions are adjusted to enhance the separation degree of text information and background in the invoice core regions.

[0128] A preset invoice template is obtained, the invoice template is matched with the enhanced invoice core regions, and invoice element content in the invoice core regions is extracted as invoice recognition data.

[0129] In an embodiment, the policy determination module 203 is further configured to:

[0130] obtain a preset invoice verification rule, the invoice verification rule being a rule for verifying one or more invoice identification data;

[0131] verify the invoice identification data in sequence by using the invoice verification rule to obtain an invoice verification result;

[0132] extract an invoice verification parameter from the invoice identification data, call an interface of an invoice verification platform and input the invoice verification parameter, and obtain an invoice verification result returned by the invoice verification platform according to the invoice verification parameter;

[0133] combine the invoice verification result and the invoice verification result to perform result evaluation to obtain an invoice authenticity verification result.

[0134] In an embodiment, the policy determination module 203 is further configured to:

[0135] if the invoice authenticity verification result is that the historical electronic invoice fails the authenticity verification, determine a need-to-transfer policy as the ownership file transfer policy of the target lease object;

[0136] based on the need-to-transfer policy, perform a preset online or offline ownership file transfer process.

[0137] In an embodiment, the type determination module 202 is specifically configured to:

[0138] perform named entity recognition on the previous-hand contract, and extract a buyer enterprise name in the previous-hand contract based on the recognized content;

[0139] obtain a preset target enterprise list, and match each target enterprise name in the target enterprise list with the buyer enterprise name in sequence;

[0140] when there is a target enterprise name that matches the buyer enterprise name, divide the historical buyer enterprise into a target enterprise;

[0141] when there is no target enterprise name that matches the buyer enterprise name, divide the historical buyer enterprise into a non-target enterprise.

[0142] The application provides a data processing device based on transaction link tracing, which can establish traceability of a target lease transaction link by acquiring a previous contract in historical cooperation records of a lease customer; can match different enterprise classifications for a historical purchase enterprise based on transaction experience of the target lease according to the enterprise classification of the historical purchase enterprise in the previous contract, determine a property right file handover strategy of the target lease according to different enterprise classifications, and realize dynamic adaptation of a property right file handover process; can reduce manual intervention in processing property right handover verification by driving an automatic process set by the property right file handover strategy through a strategy engine, and significantly improve process efficiency; and can realize a collaborative mechanism of property right handover verification and loan approval by automatically acquiring acceptance results of the target lease and payment condition inspection results of the lease customer after the property right handover process is completed, and calling a payment service interface to complete a preset handover payment process when both inspection results pass the inspection, and effectively improve efficiency of a lease loan process and customer experience.

[0143] The specific limitation of the data processing device based on transaction link tracing can be referred to the limitation of the data processing method based on transaction link tracing in the above, and will not be repeated here. Each module in the above data processing device based on transaction link tracing can be realized by software, hardware and a combination thereof in whole or in part. The above modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory in the computer device in software form, so as to call and execute the operations corresponding to each module by the processor.

[0144] To solve the above technical problems, the embodiment of the application further provides a computer device, please refer to Figure 6 , Figure 6 The computer device is a basic structure block diagram of the embodiment.

[0145] The computer device 6 includes a memory 61, a processor 62 and a network interface 63 which are connected to each other through a system bus. It should be pointed out that only the computer device 6 with the memory 61, the processor 62 and the network interface 63 is shown in the figure, but it should be understood that it is not required to implement all the shown components, and more or less components can be alternatively implemented. Among them, the computer device herein is a device capable of automatically performing numerical calculation and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), digital signal processor (DSP), embedded device, etc.

[0146] The computer device can be a desktop computer, a notebook computer, a palm computer, a cloud server, or the like. The computer device can interact with a user through a keyboard, a mouse, a remote controller, a touchpad, a voice control device, or the like.

[0147] The memory 61 can include at least one type of readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., an SD or DX memory, or the like), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, or the like. In some embodiments, the memory 61 can be an internal storage unit of the computer device 6, such as a hard disk or a memory of the computer device 6. In other embodiments, the memory 61 can also be an external storage device of the computer device 6, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, or the like. Of course, the memory 61 can include both an internal storage unit and an external storage device of the computer device 6. In this embodiment, the memory 61 is generally used to store an operating system and various application software installed in the computer device 6, such as computer readable instructions of the data processing method based on transaction link tracing, or the like. In addition, the memory 61 can also be used to temporarily store various data that have been output or will be output.

[0148] The processor 62 can be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip in some embodiments. The processor 62 is generally used to control the overall operation of the computer device 6. In this embodiment, the processor 62 is used to run computer readable instructions or process data stored in the memory 61, such as computer readable instructions of the data processing method based on transaction link tracing.

[0149] The network interface 63 can include a wireless network interface or a wired network interface, and is generally used to establish a communication connection between the computer device 6 and other electronic devices.

[0150] The present application also provides another embodiment, namely, providing a computer-readable storage medium, which stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the data processing method based on transaction link tracing as described above.

[0151] The computer device, computer-readable storage medium and computer-readable instructions provided in the embodiments of the present application obtain the previous contract in the historical cooperation record of the leaseback customer through the processor execution, and establish the traceability of the transaction link of the target leased item; by determining the corporate classification of the historical purchasing enterprise in the previous contract, it is possible to match different corporate classifications for the historical purchasing enterprise based on the transaction experience of the target leased item, and determine the title document handover strategy of the target leased item according to the different corporate classifications, thereby realizing dynamic adaptation of the title document handover process; through the policy engine driving the automatic execution of the process set by the title document handover strategy, manual intervention in the title handover verification is reduced, and the process efficiency is significantly improved; by automatically obtaining the acceptance result of the target leased item and the payment condition inspection result of the leaseback customer after the title handover process is completed, and when both inspection results are passed, calling the payment service interface to complete the preset handover payment process, a collaborative mechanism of title handover verification and loan approval is realized, effectively improving the efficiency of the leaseback loan process and customer experience.

[0152] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0153] Obviously, the embodiments described above are only some of the embodiments of the present application, rather than all of the embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions described in the aforementioned specific embodiments, or to make equivalent replacements for some of the technical features therein. Any equivalent structure made using the contents of the present application specification and the accompanying drawings, directly or indirectly used in other related technical fields, is also within the scope of patent protection of the present application.

[0154] The non-Company software tools or components appearing in the embodiments of this application are merely examples and do not represent actual use.

Claims

1. A data processing method based on transaction link tracing, characterized in that: include: Obtain the previous contracts of the back-leasing customer, which refers to the historical contracts between the back-leasing customer and previous purchasing companies in the same industry for the target leased property; Determining the corporate classification of the historical purchasing enterprise based on the previous contract; Determine the ownership document handover strategy for the target leased property based on the enterprise classification, and execute the process set by the ownership document handover strategy; After the process is completed, the acceptance result of the target leased property and the payment condition verification result of the leaseback customer are obtained; When both the acceptance result and the payment condition inspection result are passed, the payment service interface is called and the preset handover payment process is completed.

2. The method according to claim 1, wherein The enterprise classification includes a target enterprise, and determining a policy for handing over ownership documents of the target leased property based on the enterprise classification and executing a process set by the policy for handing over ownership documents include: If the historical purchaser is the target enterprise, the ownership document handover strategy for the target leased property is determined to be the first no-handover strategy; Based on the first no-handover-required strategy, obtaining historical transaction data of the historical purchasing enterprise and the leaseback customer regarding the target leased item; The historical transaction data is pushed to the lease acceptance node and the payment condition verification node.

3. The method according to claim 1, wherein The enterprise classification includes non-target enterprises, and determining the ownership document handover strategy of the target leased property based on the enterprise classification and executing the process set by the ownership document handover strategy include: If the historical purchasing enterprise is not the target enterprise, obtaining historical electronic invoices of the historical purchasing enterprise and the leaseback customer in connection with the target leased property; Using image recognition technology to perform content recognition on the historical electronic invoice to obtain invoice recognition data; Perform invoice verification based on the invoice identification data to obtain an invoice verification result; If the invoice verification result is that the historical electronic invoice has passed the verification, the ownership document handover strategy of the target leased property is determined to be the second no-handover-required strategy; Based on the second no-handover-required strategy, the invoice verification result is pushed to the leased item acceptance node and the payment condition verification node.

4. The method according to claim 3, wherein The image recognition technology is used to perform content recognition on the historical electronic invoice to obtain invoice recognition data, including: Using image recognition technology, perform regional recognition on the historical electronic invoice to obtain the recognized core area of ​​the invoice; Adjusting the contrast and brightness of the core area of ​​the invoice to enhance the separation of text information and background in the core area of ​​the invoice; A preset invoice template is obtained, the invoice template is matched with the enhanced invoice core area, and the invoice element content in the invoice core area is extracted as invoice identification data.

5. The method according to claim 3, wherein The invoice verification is performed based on the invoice identification data to obtain an invoice verification result, including: Obtaining a preset invoice verification rule, wherein the invoice verification rule is a rule for verifying one or more invoice identification data; Using the invoice verification rules, verify the invoice identification data in sequence to obtain an invoice verification result; Extracting invoice verification parameters from the invoice identification data, calling an interface of an invoice verification platform and inputting the invoice verification parameters, and obtaining an invoice verification result returned by the invoice verification platform based on the invoice verification parameters; The invoice verification result and the invoice inspection result are combined to perform a result evaluation to obtain the invoice verification result.

6. The method according to claim 3, wherein After performing invoice verification based on the invoice identification data and obtaining the invoice verification result, the method further includes: If the invoice verification result is that the historical electronic invoice fails the verification, the ownership document handover strategy of the target leased property is determined as requiring a handover strategy; Based on the required handover strategy, execute the preset online or offline handover process of ownership documents.

7. The method according to claim 1, wherein The determination of the enterprise classification of the historical purchasing enterprise based on the previous contract includes: Performing named entity recognition on the previous contract, and extracting the name of the purchasing company in the previous contract based on the recognized content; Obtain a preset target enterprise list, and match each target enterprise name in the target enterprise list with the purchaser enterprise name in sequence; When there is a target enterprise name that matches the name of the purchasing enterprise, classifying the historical purchasing enterprise as the target enterprise; When there is no target enterprise name matching the purchasing enterprise name, the historical purchasing enterprise is classified as a non-target enterprise.

8. A data processing device based on transaction link tracing, characterized in that: include: A contract acquisition module is used to acquire the previous contracts of the leaseback customer, wherein the previous contracts refer to the historical contracts between the leaseback customer and the previous purchasing enterprises in the same industry for the target leased property; A type determination module, configured to determine the enterprise classification of the historical purchasing enterprise based on the previous contract; A strategy determination module, configured to determine a strategy for handing over ownership documents of the target leased property according to the enterprise classification, and execute a process set by the strategy for handing over ownership documents; A result acquisition module is used to obtain the acceptance result of the target leased item and the payment condition verification result of the leased customer after the process is completed; The handover payment module is used to call the payment service interface and complete the preset handover payment process when the acceptance result and the payment condition inspection result are both passed.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the data processing method based on transaction link tracing according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the data processing method based on transaction link tracing according to any one of claims 1 to 7 are implemented.

Images