Financial data processing method for leasing business management

Abstract

The invention relates to the technical field of data processing, is suitable for the financial field, and provides a financial data processing method for lease business management, and the method comprises the steps: obtaining a revocation request for a lease business contract; in response to the acquisition of the revocation request, determining whether the type of the lease business contract is a revocable type; if the type of the lease service contract is the revocable type, determining revocation associated information of the lease service contract based on the revocation request; determining a target version matched with the revocation association information in a plurality of historical versions of the rental business contract; and rolling back contract associated data of the leasing business contract to the target version. According to the technical scheme, the accuracy of revocation processing of the rental business contract is remarkably improved.

Description

Financial data processing methods for leasing business management Technical Field

[0001] This application relates to the field of data processing technology, specifically to the financial sector, and particularly to a financial data processing method for leasing business management. Background Technology

[0002] In leasing business management, leasing contracts often face issues such as early settlement or cancellation. For example, if a vehicle leasing contract is settled early, the financial system or a dedicated leasing business management system needs to automatically complete financial processing procedures such as interest calculation, rent waiver, and cost allocation.

[0003] However, when faced with changes to lease agreements due to force majeure, or reversals due to legal disputes or unforeseen circumstances, the complex and ever-changing financial processes often rely on manual, item-by-item verification and ledger corrections. This manual approach is not only inefficient but also carries risks of inaccuracy and non-compliance, including but not limited to errors such as incorrect tax rates or misclassification of accounts, resulting in a persistently high rate of accounting discrepancies. Furthermore, the lack of electronic record-keeping and automated audit trails makes it difficult to meet the demands of internal and external compliance monitoring.

[0004] Therefore, how to improve the accuracy of lease contract cancellation operations while ensuring high efficiency has become an urgent technical problem to be solved. Summary of the Invention

[0005] This application provides a financial data processing method for leasing business management, aiming to solve the technical problems of low efficiency and insufficient accuracy in processing lease contract cancellation operations in related technologies.

[0006] In a first aspect, embodiments of this application provide a financial data processing method for leasing business management, comprising: obtaining a cancellation request for a leasing business contract; in response to obtaining the cancellation request, determining whether the type of the leasing business contract is a revocable type; if the type of the leasing business contract is the revocable type, determining cancellation association information of the leasing business contract based on the cancellation request, wherein the cancellation association information is used to reflect the characteristics of the historical state to which the cancellation request requires the leasing business contract to be rolled back; determining a target version that matches the cancellation association information among multiple historical versions of the leasing business contract; and rolling back the contract association data of the leasing business contract to the target version.

[0007] In one embodiment of this application, optionally, obtaining a rescission request for the lease agreement includes: obtaining a rescission request for the lease agreement from the business party; or obtaining a rescission request for the lease agreement from the finance party.

[0008] In one embodiment of this application, optionally, the method further includes: if the type of the lease business contract is not the revocable type, rejecting the revocation request and writing the rejected revocation request into a security log.

[0009] Optionally, in one embodiment of this application, determining the revocation association information of the lease business contract based on the revocation request includes: parsing the time parameters in the revocation request, wherein the time parameters include one or more of the occurrence time identifier of the revocation triggering behavior, the relevant business time identifier of the revocation triggering behavior, and the time identifier of the target version to which the revocation is required to return; and determining the business type of the lease business contract, the revocation triggering behavior, and the time parameters as the revocation association information of the lease business contract.

[0010] Optionally, in one embodiment of this application, determining the target version matching the revocation association information among multiple historical versions of the lease business contract includes: based on the time identifier and business content of each of the multiple historical versions of the lease business contract, and the rollback permission corresponding to the business type of the lease business contract, determining the versions with rollback permission for the business type among the multiple historical versions, as a first historical version set; for each historical version in the first historical version set, if the available revocation triggering behavior set of the historical version has the revocation triggering behavior shown in the revocation request, adding the historical version to a second historical version set; and determining, in the second historical version set, a historical version whose time parameter matches the time parameter in the revocation request, as the target version matching the revocation association information.

[0011] In one embodiment of this application, the method may optionally further include: after rolling back to the target version, setting the contract status label of the leasing business contract to the contract status label corresponding to the target version.

[0012] In one embodiment of this application, the method may optionally further include: after rolling back to the target version, determining first result data based on the rolled-back credential information, and determining second result data based on the business data of the lease business contract; determining whether the first result data and the second result data have a discrepancy; if the first result data and the second result data have a discrepancy, determining the cause category of the discrepancy based on a predetermined business rule base; and repairing the first result data based on the repair method corresponding to the cause category, so that the first result data is consistent with the second result data.

[0013] In one embodiment of this application, optionally, before determining the cause category of the deviation based on a predetermined business rule base, the method further includes: determining whether the difference between the first result data and the second result data is less than or equal to a specified security threshold; if the difference is less than or equal to the specified security threshold, proceeding to the step of determining the cause category of the deviation based on the predetermined business rule base; if the difference is greater than the specified security threshold, executing a predetermined information push warning strategy, and reporting the rollback operation to the target version to a specified object.

[0014] Secondly, embodiments of this application provide a financial data processing apparatus for leasing business management, comprising: a revocation request acquisition unit, configured to acquire a revocation request for a leasing business contract; a contract type determination unit, configured to determine, in response to the acquisition of the revocation request, whether the type of the leasing business contract is a revocable type; a revocation association information determination unit, configured to, if the type of the leasing business contract is the revocable type, determine the revocation association information of the leasing business contract based on the revocation request, wherein the revocation association information is used to reflect the characteristics of the historical state to which the revocation request requires the leasing business contract to be rolled back; a target version determination unit, configured to determine, among multiple historical versions of the leasing business contract, a target version matching the revocation association information; and a rollback execution unit, configured to roll back the contract association data of the leasing business contract to the target version.

[0015] In one embodiment of this application, optionally, the revocation request acquisition unit is used to: acquire a revocation request for the lease business contract from the business party; or acquire a revocation request for the lease business contract from the finance party.

[0016] Optionally, in one embodiment of this application, the apparatus further includes: a revocation request rejection unit, configured to reject the revocation request if the type of the lease business contract is not the revocable type, and write the rejected revocation request into a security log.

[0017] Optionally, in one embodiment of this application, the revocation association information determination unit includes: a time parameter parsing unit, configured to parse the time parameters in the revocation request, wherein the time parameters include one or more of the occurrence time identifier of the revocation triggering behavior, the relevant business time identifier of the revocation triggering behavior, and the time identifier of the target version to which the revocation is required to return; and a first execution unit, configured to determine the business type of the lease business contract, the revocation triggering behavior, and the time parameters as the revocation association information of the lease business contract.

[0018] Optionally, in one embodiment of this application, the target version determination unit includes: a first version set determination unit, configured to determine, based on the time identifier and business content of each of the multiple historical versions of the lease business contract, and the rollback permission corresponding to the business type of the lease business contract, the versions with rollback permission for the business type among the multiple historical versions, as a first historical version set; a second version set determination unit, configured to, for each historical version in the first historical version set, if the available revocation triggering behavior set of the historical version has the revocation triggering behavior shown in the revocation request, add the historical version to the second historical version set; and a second execution unit, configured to determine, in the second historical version set, a historical version whose time parameter matches the time parameter in the revocation request, as a target version matching the revocation association information.

[0019] In one embodiment of this application, the apparatus may optionally further include: a contract label updating unit, configured to set the contract status label of the lease business contract to the contract status label corresponding to the target version after rolling back to the target version.

[0020] In one embodiment of this application, the apparatus optionally further includes: a rollback verification unit, configured to, after rolling back to the target version, determine first result data based on the rolled-back credential information, and determine second result data based on the business data of the lease business contract; determine whether the first result data and the second result data have a deviation; if the first result data and the second result data have a deviation, determine the cause category of the deviation based on a predetermined business rule base; and a rollback repair unit, configured to repair the first result data based on the repair method corresponding to the cause category, so that the first result data is consistent with the second result data.

[0021] Optionally, in one embodiment of this application, the apparatus further includes: a deviation degree judgment unit, configured to determine whether the difference between the first result data and the second result data is less than or equal to a specified security threshold before the rollback verification unit determines the cause category of the deviation; a third execution unit, configured to enter the step of determining the cause category of the deviation based on a predetermined business rule base if the difference is less than or equal to the specified security threshold; the apparatus further includes: a rollback error reporting unit, configured to execute a predetermined information push warning strategy if the difference is greater than the specified security threshold, and report the rollback operation to the target version to a specified object.

[0022] Thirdly, embodiments of this application provide a computer device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being configured to perform the method described in the first aspect above.

[0023] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions for performing the method described in the first aspect above.

[0024] The above technical solution addresses the technical problems of low efficiency and insufficient accuracy in processing lease contract cancellations in related technologies. It establishes an automated contract cancellation process for lease contracts, encompassing the acquisition of cancellation requests, verification of cancellation eligibility, selection of rollback versions, and even version rollback. This solves the problems of low efficiency and insufficient accuracy associated with traditional manual operations. Through a precise contract version matching mechanism, this solution ensures that the rollback operation complies with both business rules and timing requirements, significantly improving the accuracy of lease contract cancellation processing. Attached Figure Description

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

[0026] Figure 1 shows a flowchart of a financial data processing method for leasing business management according to an embodiment of the present application; Figure 2 shows a flowchart of a verification and problem repair method after contract rollback according to an embodiment of the present application; Figure 3 shows a block diagram of a computer device according to an embodiment of the present application; Figure 4 shows a block diagram of a computer device according to another embodiment of the present application. Detailed Implementation

[0027] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0028] Figure 1 shows a flowchart of a financial data processing method for leasing business management according to an embodiment of this application.

[0029] As shown in Figure 1, the flow of a financial data processing method for leasing business management according to an embodiment of this application includes: step 102, obtaining a revocation request for a leasing business contract.

[0030] The leasing business contracts include, but are not limited to, lease agreements for the subject matter, sale-leaseback agreements for the subject matter, insurance service agreements related to the lease of the subject matter, and maintenance service agreements for the subject matter, as well as any other contracts related to the subject matter and involving financial transactions. Here, the subject matter includes, but is not limited to, vehicles, cameras, power banks, sleeping pods, and any other items that can be rented out as shared objects, without being limited to the examples given in this application.

[0031] The circumstances under which a lease agreement may be rescinded include, but are not limited to: the lessee defaulting on payments due to financial problems; total loss or scrapping of the leased property; the user overpaying the lease loan and requesting a refund; and the contract being unable to be performed due to force majeure or changes in laws and policies.

[0032] Optionally, when the financial system or a dedicated leasing business management system detects that any of these situations have occurred in the business corresponding to any leasing business contract, a cancellation request for the leasing business contract can be automatically generated.

[0033] Optionally, when any of these situations occur in the business corresponding to any lease business contract, the relevant staff can manually trigger a cancellation request for the lease business contract in the lease business management system.

[0034] In one possible design, step 102 includes obtaining a cancellation request for the lease agreement from the business party. In another possible design, step 102 includes obtaining a cancellation request for the lease agreement from the finance party.

[0035] The business side includes asset leasing business administrators or sales operations personnel, while the finance side encompasses financial personnel involved in all aspects of the leasing business contract. This application supports contract rollback from both the business and finance sides, thus accommodating the management needs of both sides in their respective work scenarios. This enhances the flexibility of contract cancellation operations and allows for multi-party collaboration, enabling business personnel to initiate rollbacks promptly based on actual operational conditions, and allowing finance personnel to independently reverse-process financial data according to accounting compliance requirements. This two-way operation reduces inter-departmental coordination costs, avoids business disruptions, and improves the convenience of leasing business contract cancellation operations.

[0036] Step 104: In response to the receipt of the revocation request, determine whether the type of the lease business contract is revocable.

[0037] Voidable types refer to contract types that are eligible for rescission. For example, a lease contract that stipulates that the contract can be rescinded or rolled back to a previous version of the contract if certain conditions are met is a voidable type of lease contract.

[0038] If the lease agreement is of the voidable type, the request to cancel the lease agreement can be accepted, and the cancellation process for the lease agreement can then proceed.

[0039] Conversely, if the type of the lease agreement is not the revocable type, the revocation request is rejected, and the rejected revocation request is written to the security log.

[0040] In this way, the system can promptly block illegal operations on non-revocable contract types, preventing abnormal data changes caused by erroneous or malicious requests. Simultaneously, all rejected revocation requests are recorded in the security log, forming a complete operation trail for subsequent compliance reviews, facilitating accountability and enhancing the overall security of the system.

[0041] Step 106: If the type of the lease business contract is the revocable type, determine the revocation association information of the lease business contract based on the revocation request.

[0042] If the lease agreement is of the voidable type, the cancellation process for that lease agreement can be initiated. In the cancellation process, firstly, it is necessary to determine the characteristics of the historical state to which the cancellation request requires the lease agreement to be rolled back, so that the rollback can be accurately performed to the contract state desired by the cancellation request. Specifically, the cancellation-related information determined based on the cancellation request reflects the characteristics of the historical state to which the cancellation request requires the lease agreement to be rolled back.

[0043] Specifically, the time parameters in the revocation request can be parsed, wherein the time parameters include one or more of the following: the occurrence time identifier of the revocation triggering action, the relevant business time identifier of the revocation triggering action, and the time identifier of the target version to which the revocation is required; the business type of the lease business contract, the revocation triggering action, and the time parameters are determined as the revocation association information of the lease business contract.

[0044] Time parameters refer to key time markers extracted from the revocation request. These key time markers accurately reflect the historical moment or version range to which the rollback operation points. Specifically, the occurrence time marker of the revocation triggering action reflects the specific moment when the action related to the lease contract that caused the user or system to initiate the revocation operation, such as the date of loan termination or the date of damage to the leased property. The relevant business time markers of the revocation triggering action reflect the actual occurrence time of the original business events such as repayment and settlement in the lease contract that triggered the revocation, reflecting the time portion of each execution stage of the lease contract. The time marker of the target version to which the revocation request is to revert reflects the time node corresponding to the contract's historical state to which the revocation request is expected to return, clarifying the specific time target for version retrieval. Therefore, by parsing one or more time parameters, the system can accurately locate the required contract state, avoiding rollback deviations caused by missing time dimensions.

[0045] Different business types have different permissions regarding contract cancellation. For example, vehicle rental contracts with early repayment clauses can be cancelled due to early repayment, while those with total loss insurance clauses can be cancelled due to total loss or scrapping of the vehicle. Furthermore, vehicle maintenance service contracts that have been fully performed and for which all payments have been settled no longer have cancellation permissions because their business cycle has naturally ended and there are no outstanding rights or obligations; the system will automatically reject all rollback requests for such contracts.

[0046] Therefore, it can be said that the business type of a lease contract reflects whether the lease contract has the authority to be revoked, thus providing a basis for authority verification for rollback operations.

[0047] In addition, the cancellation trigger behavior reflects the specific business event that triggers the cancellation request, clarifies the business scenario that triggers the rollback operation, and the time parameter reflects the key time node or version range targeted by the rollback operation, providing one-dimensional or multi-dimensional time sequence basis for accurately locating the target contract status.

[0048] By combining the business type of the lease contract, the cancellation triggering behavior, and the time parameter, the system achieves feature fusion across three dimensions: business type, triggering behavior, and time. This enables the system to construct cancellation association information that fully describes the rollback intention or the feature requirements that need to be met for rollback, which helps to accurately locate the rollback position and improve the accuracy of lease contract cancellation or rollback.

[0049] Step 108: Among multiple historical versions of the lease agreement, identify the target version that matches the cancellation association information.

[0050] By accurately matching revocation-related information with historical versions, the system can automatically filter out target versions that match the revocation intent, avoiding errors and delays that may occur with manual operations. Simultaneously, this version rollback matching mechanism makes the rollback process simple and transparent, enabling convenient data reverse recovery in complex business scenarios, significantly improving the automation level and accuracy of the lease contract revocation process.

[0051] In one possible design, firstly, based on the time stamps and business content of multiple historical versions of the lease business contract, and the rollback permissions corresponding to the business type of the lease business contract, the version with rollback permissions for the business type can be determined from the multiple historical versions and used as the first historical version set.

[0052] The time stamp of a historical version refers to a time-series certificate marking the moment a historical version was generated. The business content of a historical version includes specific data such as the terms and amounts of the lease contracts under that historical version, and the contract term. Rollback permissions represent the scope of revocable operations available for contracts of different business types. Based on this, by combining the above multi-dimensional information, historical versions with rollback permissions are prioritized and processed in the initial screening.

[0053] Next, for each historical version in the first historical version set, if the available undo trigger behavior set of the historical version has the undo trigger behavior shown in the undo request, the historical version is added to the second historical version set.

[0054] Each historical version has its own set of available undo trigger actions. For a single historical version, only if the current undo trigger action is within that set of available undo trigger actions is that historical version eligible to be selected as a rollback result. This further narrows down the matching scope for rollback.

[0055] Furthermore, in the second set of historical versions, historical versions whose time parameters match the time parameters in the revocation request are identified as target versions that match the revocation association information.

[0056] At this point, by combining time parameters with precise matching of historical versions in the second historical version set, target versions that meet both rollback permission constraints and revocation trigger behavior and time requirements are gradually selected. This significantly improves the accuracy of version retrieval and avoids the risks associated with unauthorized rollbacks.

[0057] Step 110: Roll back the contract association data of the lease business contract to the target version.

[0058] The contract-related data of the lease agreement refers to the data that needs to be changed during the rollback process of the lease agreement. At this point, the contract-related data of the lease agreement can be rolled back to the target version, completing the cancellation of the lease agreement.

[0059] Of course, after rolling back to the target version, the contract status label of the lease business contract is set to the contract status label corresponding to the target version, so as to indicate that the current contract data after the rollback has been successfully restored to the business status under the specified historical version, which can provide accurate status basis for subsequent business processes.

[0060] The above technical solution establishes an automated contract cancellation process for leasing contracts, encompassing the acquisition of cancellation requests, verification of cancellation eligibility, selection of rollback versions, and even version rollback. This solves the technical problems of low efficiency and insufficient accuracy associated with traditional manual operations. Through a precise contract version matching mechanism, this solution ensures that the rollback operation complies with both business rules and timing requirements, significantly improving the accuracy of leasing contract cancellation processing.

[0061] In addition, this solution can also record the entire operation trajectory to meet subsequent audit requirements, thereby comprehensively improving the security of reverse operation of leasing business contracts while ensuring processing efficiency and accuracy.

[0062] In an exemplary real-world scenario, a customer and a lessor sign a three-year vehicle rental installment contract, stipulating that if the customer fails to pay rent for three consecutive months, the lessor has the right to cancel the contract and reclaim the vehicle.

[0063] First, if a customer has defaulted on payments for more than three consecutive months, the lessor's business system automatically detects this breach and generates a cancellation request for the vehicle rental contract. Next, the lessor's business system responds to the request and determines the contract type. Since the contract explicitly states that cancellation is possible after three consecutive months of non-payment, the lessor's business system confirms that the contract is revocable. At this point, the system parses the cancellation request, determining the business type to be a vehicle rental installment contract, the cancellation trigger to be the lessee's non-payment, the time parameter to be the last successful payment date, and the desired rollback state after the contract's initial effective date but before the first payment as the target version's time marker. These elements together constitute the relevant information for this cancellation. The system then matches and filters all historical versions of the contract based on this relevant information to obtain the target version. Next, the system rolls back all relevant data for the vehicle rental contract to the target version, i.e., the state when the contract first took effect, and the contract status label is updated to "Cancelled - Vehicle Awaiting Recovery." The contract cancellation process is now complete.

[0064] In another exemplary real-world scenario, a user rents a shared power bank. According to the power bank rental agreement, if the power bank is determined to be lost by the system during the rental period, the power bank rental order will be automatically canceled, and the compensation process will be initiated.

[0065] First, if a user rents a power bank and fails to return it for an extended period, the platform managing the power bank rental business determines that the power bank is lost by locating it and monitoring its usage status. The platform then automatically generates a cancellation request for the power bank rental order. At this point, the platform first determines the type of contract: the power bank rental order, being an immediate contract. According to the power bank rental contract, loss of the power bank is a clear condition for cancellation; therefore, the platform confirms that the order is revocable. Next, the platform analyzes the cancellation request, determining the business type as a "power bank rental order," the cancellation trigger as "power bank loss," and the time parameter as the "last online time of the power bank," serving as the time of the triggering action. The desired rollback state before the user's rental operation is also used as the target version's time identifier. This information constitutes the cancellation association information. Based on this cancellation association information, the platform matches the target version in the order's historical versions and executes a rollback operation, restoring all data, including the order status, the user's deposit or credit status, and the power bank's inventory status, to the state before the user rented the power bank. Simultaneously, the platform triggered the deduction and compensation process, and the contract status label for the power bank rental order was updated to "Cancelled - Compensation Processed." This allows for rapid processing of financial data for power bank rental orders, ensuring the platform's asset security.

[0066] Figure 2 shows a flowchart of a method for verifying and fixing problems after contract rollback according to an embodiment of this application.

[0067] As shown in Figure 2, a method for verifying and fixing problems after contract rollback according to an embodiment of this application includes: step 202, after rolling back to the target version, determining first result data based on the rolled-back credential information, and determining second result data based on the business data of the lease business contract.

[0068] Voucher information refers to the set of financial vouchers involved after the rollback operation, while business data covers core business information such as contract terms and execution status. If the rollback is successful and no data errors occur, the results calculated from the voucher information and business data will be consistent. Therefore, the first result data corresponding to the rolled-back voucher information can be compared with the second result data calculated from the business data of the lease business contract to determine whether the rolled-back data is correct.

[0069] Step 204: Determine whether there is a deviation between the first result data and the second result data.

[0070] If the first and second result data deviate, it indicates that the rollback operation caused a problem with the data, and the current rollback result is invalid and requires further correction. Conversely, if they are in agreement, it indicates that the rollback operation did not cause a problem with the data, and the current rollback result is valid.

[0071] Step 206: If there is a deviation between the first result data and the second result data, determine the category of the cause of the deviation based on a predetermined business rule base.

[0072] When the current rollback result is invalid and requires further correction, matching the numerical differences with specific rules in the business rule base, such as tax regulations and contract terms, can accurately infer the underlying business root cause of the deviation. For example, it can identify deviations caused by misuse of tax rate policy versions or by incorrect configuration of accrual formulas under specific contract terms. This provides a valid basis for data repair, thereby improving the accuracy of deviation handling.

[0073] Step 208: Based on the repair method corresponding to the cause category, repair the first result data to make the first result data consistent with the second result data.

[0074] The repair method is a standardized correction strategy bound to the cause category. For example, for tax rate misuse, the latest tax rate table is automatically called to recalculate the tax amount. For example, for accrual formula errors, the formula engine is triggered to dynamically correct the calculation logic.

[0075] By using this precise classification and repair method, the system can quickly eliminate the differences between the rolled-back data and the actual data in the historical version. This not only ensures the real-time consistency between financial vouchers and business data, but also significantly improves the automation of data correction, avoids secondary errors that may be introduced by manual intervention, and ultimately ensures the integrity and validity of the data after the rollback operation.

[0076] The above technical solutions perform timely data verification and repair after rollback. Based on the rollback of the contract version, they automatically compare the consistency between financial voucher data and business logic data, and use a business rule base to classify and repair any discrepancies. This effectively ensures the accuracy of the data after the rollback operation, avoids the risk of secondary errors caused by manual intervention, ensures the effectiveness of the lease contract rollback, and comprehensively enhances the stability of the financial system or lease business management system.

[0077] In addition, this application embodiment also provides a financial data processing device for leasing business management, including: a cancellation request acquisition unit, used to acquire a cancellation request for a leasing business contract; a contract type determination unit, used to determine whether the type of the leasing business contract is a revocable type in response to the acquisition of the cancellation request; a cancellation association information determination unit, used to determine the cancellation association information of the leasing business contract based on the cancellation request if the type of the leasing business contract is the revocable type, wherein the cancellation association information is used to reflect the characteristics of the historical state to which the cancellation request requires the leasing business contract to be rolled back; a target version determination unit, used to determine a target version that matches the cancellation association information among multiple historical versions of the leasing business contract; and a rollback execution unit, used to roll back the contract association data of the leasing business contract to the target version.

[0078] In one embodiment of this application, optionally, the revocation request acquisition unit is used to: acquire a revocation request for the lease business contract from the business party; or acquire a revocation request for the lease business contract from the finance party.

[0079] Optionally, in one embodiment of this application, the apparatus further includes: a revocation request rejection unit, configured to reject the revocation request if the type of the lease business contract is not the revocable type, and write the rejected revocation request into a security log.

[0080] Optionally, in one embodiment of this application, the revocation association information determination unit includes: a time parameter parsing unit, configured to parse the time parameters in the revocation request, wherein the time parameters include one or more of the occurrence time identifier of the revocation triggering behavior, the relevant business time identifier of the revocation triggering behavior, and the time identifier of the target version to which the revocation is required to return; and a first execution unit, configured to determine the business type of the lease business contract, the revocation triggering behavior, and the time parameters as the revocation association information of the lease business contract.

[0081] Optionally, in one embodiment of this application, the target version determination unit includes: a first version set determination unit, configured to determine, based on the time identifier and business content of each of the multiple historical versions of the lease business contract, and the rollback permission corresponding to the business type of the lease business contract, the versions with rollback permission for the business type among the multiple historical versions, as a first historical version set; a second version set determination unit, configured to, for each historical version in the first historical version set, if the available revocation triggering behavior set of the historical version has the revocation triggering behavior shown in the revocation request, add the historical version to the second historical version set; and a second execution unit, configured to determine, in the second historical version set, a historical version whose time parameter matches the time parameter in the revocation request, as a target version matching the revocation association information.

[0082] In one embodiment of this application, the apparatus may optionally further include: a contract label updating unit, configured to set the contract status label of the lease business contract to the contract status label corresponding to the target version after rolling back to the target version.

[0083] In one embodiment of this application, the apparatus optionally further includes: a rollback verification unit, configured to, after rolling back to the target version, determine first result data based on the rolled-back credential information, and determine second result data based on the business data of the lease business contract; determine whether the first result data and the second result data have a deviation; if the first result data and the second result data have a deviation, determine the cause category of the deviation based on a predetermined business rule base; and a rollback repair unit, configured to repair the first result data based on the repair method corresponding to the cause category, so that the first result data is consistent with the second result data.

[0084] Optionally, in one embodiment of this application, the apparatus further includes: a deviation degree judgment unit, configured to determine whether the difference between the first result data and the second result data is less than or equal to a specified security threshold before the rollback verification unit determines the cause category of the deviation; a third execution unit, configured to enter the step of determining the cause category of the deviation based on a predetermined business rule base if the difference is less than or equal to the specified security threshold; the apparatus further includes: a rollback error reporting unit, configured to execute a predetermined information push warning strategy if the difference is greater than the specified security threshold, and report the rollback operation to the target version to a specified object.

[0085] The device uses the solution described in any one of the above embodiments, and therefore has all the above-mentioned technical effects, which will not be repeated here.

[0086] In another embodiment, this application provides a computer device, which can be a server, and its internal structure diagram is shown in Figure 3. The computer device includes a processor, memory, network interface, and database connected via a system bus. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used to communicate with external clients via a network connection. When the computer program is executed by the processor, it can implement the methods described in any of the above embodiments.

[0087] In one embodiment, this application also provides a computer device, which can be a client, and its internal structure diagram can be as shown in Figure 4. The computer device includes a processor, memory, network interface, display screen, and input device connected via a system bus. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it can implement the methods described in any of the above embodiments.

[0088] The computer devices described in the embodiments of this application exist in various forms, including but not limited to: (1) mobile communication devices: These devices are characterized by having mobile communication functions and are primarily designed to provide voice and data communication. These terminals include: smartphones (e.g., iPhones), multimedia phones, feature phones, and low-end phones, etc.

[0089] (2) Ultra-mobile personal computer devices: These devices fall under the category of personal computers, possessing computing and processing capabilities, and generally also have mobile internet access features. These terminals include PDAs, MIDs, and UMPCs, such as the iPad.

[0090] (3) Portable entertainment devices: These devices can display and play multimedia content. This category includes: audio and video players (such as iPods), handheld game consoles, e-books, as well as smart toys, wearable devices, and portable car navigation devices.

[0091] (4) Server: A device that provides computing services. The components of a server include a processor, hard disk, memory, system bus, etc. Servers are similar to general computer architectures, but because they need to provide highly reliable services, they have higher requirements in terms of processing power, stability, reliability, security, scalability, and manageability.

[0092] (5) Other electronic devices with data interaction functions.

[0093] Additionally, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions for performing the following steps: obtaining a revocation request for a lease agreement; in response to obtaining the revocation request, determining whether the lease agreement is a revocable type; if the lease agreement is a revocable type, determining revocation association information for the lease agreement based on the revocation request, wherein the revocation association information reflects the characteristics of the historical state to which the revocation request requires the lease agreement to be rolled back; determining a target version matching the revocation association information among multiple historical versions of the lease agreement; and rolling back the contract association data of the lease agreement to the target version.

[0094] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or computer device described above can be referred to the relevant descriptions in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0095] The technical solution of this application has been described in detail above with reference to the accompanying drawings. This technical solution establishes an automated contract cancellation process for lease contracts, encompassing the acquisition of cancellation requests, verification of cancellation eligibility, selection of rollback versions, and even version rollback. This solves the technical problems of low efficiency and insufficient accuracy associated with traditional manual operations. Through a precise contract version matching mechanism, this technical solution ensures that the rollback operation complies with both business rules and timing requirements, significantly improving the accuracy of lease contract cancellation processing.

[0096] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0097] It should be understood that although the terms "first," "second," etc., may be used to describe the result data in the embodiments of this application, the result data should not be limited to these terms. These terms are only used to distinguish the result data from one another. For example, without departing from the scope of the embodiments of this application, the first result data may also be referred to as the second result data, and similarly, the second result data may also be referred to as the first result data.

[0098] Depending on the context, the word "if" as used here can be interpreted as "when," "when," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrase "if determination" or "if detection (of the stated condition or event)" can be interpreted as "when determination," "in response to determination," "when detection (of the stated condition or event)," or "in response to detection (of the stated condition or event)."

[0099] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0100] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and 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. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0101] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0102] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0103] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A financial data processing method for leasing business management, characterized in that, include: Obtain a request to cancel the lease agreement; In response to receiving the revocation request, determine whether the type of the lease agreement is revocable; If the lease agreement is of the revocable type, based on the revocation request, the revocation association information of the lease agreement is determined, wherein the revocation association information is used to reflect the characteristics of the historical state to which the revocation request requires the lease agreement to be rolled back; among the multiple historical versions of the lease agreement, a target version that matches the revocation association information is determined; and the contract association data of the lease agreement is rolled back to the target version.

2. The method according to claim 1, characterized in that, The process of obtaining a rescission request for a lease agreement includes: obtaining a rescission request for a lease agreement from the business party; or obtaining a rescission request for a lease agreement from the finance party.

3. The method according to claim 1, characterized in that, Also includes: If the type of the lease agreement is not the revocable type, the revocation request is rejected, and the rejected revocation request is written to the security log.

4. The method according to claim 1, characterized in that, The step of determining the revocation association information of the lease business contract based on the revocation request includes: parsing the time parameters in the revocation request, wherein the time parameters include one or more of the following: the occurrence time identifier of the revocation triggering behavior, the relevant business time identifier of the revocation triggering behavior, and the time identifier of the target version to which the revocation is required; and determining the business type of the lease business contract, the revocation triggering behavior, and the time parameters as the revocation association information of the lease business contract.

5. The method according to claim 4, characterized in that, The step of determining the target version matching the revocation association information among multiple historical versions of the lease business contract includes: based on the time identifier and business content of each of the multiple historical versions of the lease business contract, and the rollback permission corresponding to the business type of the lease business contract, determining the version with rollback permission for the business type among the multiple historical versions, as a first historical version set; for each historical version in the first historical version set, if the available revocation triggering behavior set of the historical version has the revocation triggering behavior shown in the revocation request, adding the historical version to a second historical version set; and determining the historical version in the second historical version set whose time parameter matches the time parameter in the revocation request, as the target version matching the revocation association information.

6. The method according to claim 1, characterized in that, Also includes: After rolling back to the target version, the contract status label of the lease business contract will be set to the contract status label corresponding to the target version.

7. The method according to any one of claims 1 to 6, characterized in that, Also includes: After rolling back to the target version, the first result data is determined based on the rolled-back credential information, and the second result data is determined based on the business data of the lease business contract; Determine whether there is a discrepancy between the first result data and the second result data; If the first result data and the second result data deviate, the cause category of the deviation is determined based on a predetermined business rule base; Based on the repair method corresponding to the cause category, the first result data is repaired to make the first result data consistent with the second result data.

8. The method according to claim 7, characterized in that, Before determining the cause category of the deviation based on the predetermined business rule base, the method further includes: determining whether the difference between the first result data and the second result data is less than or equal to a specified security threshold; if the difference is less than or equal to the specified security threshold, entering the step of determining the cause category of the deviation based on the predetermined business rule base; the method further includes: if the difference is greater than the specified security threshold, executing a predetermined information push warning strategy, and reporting the rollback operation to the target version to a specified object.

9. A computer device, characterized in that, include: At least one processor; And a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being configured to cause the processor to perform the method of any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The device stores computer-executable instructions configured to perform the method as described in any one of claims 1 to 8.

Images