Reconciliation method, device and equipment based on car purchase staged business, medium and product

Abstract

The invention provides an account checking method, device and equipment based on car purchase staged business, a medium and a product. Relates to the technical field of data processing. The method comprises the steps of obtaining bill detail data of an automobile manufacturer in response to an account checking request automatically triggered for any automobile manufacturer; generating to-be-reconciliated data according to the protocol rule of the automobile manufacturer and the bill detail data; performing basic verification and business rule verification on the to-be-reconciliated data to obtain a verification result; if the verification is passed, sending the to-be-reconciliated data to a client of an automobile manufacturer, and generating a reconciliation result by the client; if the account checking result is that the bill is normal, account checking processing is completed; if the account checking result is that the bill is abnormal, bill detail data is modified according to the bill abnormal information; according to a protocol rule of an automobile manufacturer and the modified bill detail data, regenerating to-be-reconciliated data; and the client generates a new account checking result until the new account checking result is that the bill is normal. According to the method, the account checking efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a reconciliation method, apparatus, equipment, medium and product based on car purchase installment business. Background Technology

[0002] Car installment payment services are a typical example of the integration between finance and automakers. The core logic is that banks or financial institutions provide financial support to car buyers, while automakers collaborate with banks to offer interest subsidies to lower the barrier to entry for customers. During the allocation of these subsidies, manufacturers and banks need to reconcile accounts to ensure the accuracy of cost allocation.

[0003] Currently, the relevant technology requires banks and car manufacturers to transfer data via Excel files, paper documents, or emails, with manual reconciliation required. However, this method reduces reconciliation efficiency. Summary of the Invention

[0004] This application provides a method, apparatus, equipment, medium, and product for reconciliation based on car purchase installment business, in order to improve reconciliation efficiency.

[0005] In a first aspect, embodiments of this application provide a reconciliation method based on car purchase installment business, comprising: in response to an automatically triggered reconciliation request for any car manufacturer, obtaining the car manufacturer's billing details data; generating reconciliation data to be generated for the car manufacturer based on the agreement rules with the car manufacturer and the billing details data; performing basic verification and business rule verification on the reconciliation data to be generated, and obtaining verification results; if the verification result is successful, sending the reconciliation data to be generated to the car manufacturer's client, so that the car manufacturer's client can generate a reconciliation result based on the reconciliation data; receiving the reconciliation result sent by the car manufacturer's client; if the reconciliation result is successful... If the bill is normal, the reconciliation process with the car manufacturer is completed. If the reconciliation result shows an abnormal bill, the following operations are performed iteratively until the reconciliation result shows a normal bill. The operations include: obtaining the abnormal bill information from the reconciliation result; modifying the bill details data based on the abnormal bill information; regenerating the car manufacturer's reconciliation data according to the agreement rules with the car manufacturer and the modified bill details data; sending the newly generated reconciliation data to the car manufacturer's client so that the car manufacturer's client can perform reconciliation based on the reconciliation data and generate a new reconciliation result; and receiving the new reconciliation result sent by the car manufacturer's client.

[0006] In one possible implementation, generating reconciliation data for the car manufacturer based on the agreement rules and billing details includes: extracting reconciliation fields, calculation rules, and format rules from the agreement rules with the car manufacturer; filtering out data related to the reconciliation fields from the billing details; calculating derived data based on the calculation rules and the data related to the reconciliation fields; and converting the data related to the reconciliation fields and the derived data according to the format rules to generate the reconciliation data for the car manufacturer.

[0007] In one possible implementation, the reconciliation data is sent to the car manufacturer's client, enabling the car manufacturer's client to generate a reconciliation result based on the reconciliation data. This includes: performing a hash calculation on the reconciliation data to generate a first hash value; encrypting the first hash value to generate a digital signature; initiating a session key negotiation process with the car manufacturer's client to obtain a session key; encrypting the reconciliation data and the digital signature using the session key to obtain an encrypted reconciliation data packet; sending the encrypted reconciliation data packet to the car manufacturer's client, whereby the car manufacturer's client uses the session key to decrypt the encrypted reconciliation data packet to obtain the reconciliation data and the digital signature; decrypting the digital signature to obtain the original first hash value; performing a hash calculation on the reconciliation data to generate a second hash value; and generating a reconciliation result based on the reconciliation data if the second hash value matches the first hash value.

[0008] In one possible implementation, the data to be reconciled is subjected to basic verification and business rule verification to obtain verification results, including: verifying whether the fields in the data to be reconciled are complete, whether the data type is correct, and whether the data format is correct through basic verification to obtain basic verification results; verifying whether the data in the data to be reconciled is reasonable through business rule verification to obtain business rule verification results; and determining the basic verification results and business rule verification results as the verification results.

[0009] In one possible implementation, prior to responding to a timed reconciliation request automatically triggered for any vehicle manufacturer, the process includes: obtaining vehicle manufacturer identifiers for multiple vehicle manufacturers; obtaining the reconciliation timed period corresponding to the reconciliation timed period field from the agreement rules with each vehicle manufacturer; and generating a reconciliation request for each vehicle manufacturer using a timed task scheduler, based on the vehicle manufacturer identifier and the reconciliation timed period.

[0010] In one possible implementation, the method further includes: setting a reconciliation status; the reconciliation status indicating the reconciliation progress with the car manufacturer; updating the reconciliation status to "pending verification" when no bill detail data is detected; updating the reconciliation status to "preparing to generate reconciliation data" when bill detail data is detected but no reconciliation data is generated; updating the reconciliation status to "pending sending" when reconciliation data is detected but not sent to the car manufacturer's client; updating the reconciliation status to "pending processing" when reconciliation data is detected being sent to the car manufacturer's client but no reconciliation result is received from the car manufacturer's client; updating the reconciliation status to "verification successful" when reconciliation with the car manufacturer is detected; updating the reconciliation status to "return to modification" when the reconciliation result is detected as an abnormal bill; and updating the reconciliation status to "modified and reviewed" when bill detail data is detected being modified and the car manufacturer's reconciliation data is regenerated.

[0011] In one possible implementation, after obtaining the reconciliation data from the car manufacturer, the method further includes: if it is detected that the car manufacturer's client does not have a reconciliation function, calling the report export interface; exporting the reconciliation data in report format through the report export interface; wherein the exported reconciliation data is used for offline reconciliation with the car manufacturer; and obtaining the reconciliation results in response to the reconciliation result upload operation performed on the reconciliation result page.

[0012] Secondly, embodiments of this application provide a reconciliation device based on car purchase installment business, comprising: a response module, used to respond to an automatically triggered reconciliation request for any car manufacturer and obtain the car manufacturer's billing details data; a first generation module, used to generate reconciliation data to be generated for the car manufacturer according to the agreement rules with the car manufacturer and the billing details data; a verification module, used to perform basic verification and business rule verification on the reconciliation data to be generated and obtain a verification result; a second generation module, used to send the reconciliation data to the car manufacturer's client if the verification result is successful, so that the car manufacturer's client can generate a reconciliation result based on the reconciliation data; and a receiving module, used to receive the reconciliation data sent by the car manufacturer's client. The reconciliation process consists of two modules: a first reconciliation completion module, which completes the reconciliation with the car manufacturer if the reconciliation result is normal; and a second reconciliation completion module, which iteratively performs the following operations if the reconciliation result is abnormal, until the reconciliation result is normal. These operations include: obtaining abnormal bill information from the reconciliation result; modifying the bill details based on the abnormal bill information; regenerating the car manufacturer's reconciliation data according to the agreement rules with the car manufacturer and the modified bill details; sending the newly generated reconciliation data to the car manufacturer's client so that the car manufacturer's client can perform reconciliation based on the reconciliation data and generate a new reconciliation result; and receiving the new reconciliation result sent by the car manufacturer's client.

[0013] Thirdly, embodiments of this application provide a computer device, including: a memory and a processor;

[0014] The memory stores computer-executed instructions;

[0015] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0016] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0017] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0018] The reconciliation method, apparatus, equipment, medium, and product based on car purchase installment business provided in this application initiate the reconciliation process in response to an automatically triggered reconciliation request from any car manufacturer. Based on the agreement rules with the car manufacturer and billing details, it can automatically generate reconciliation data. Through basic verification and business rule verification, the accuracy and efficiency of reconciliation are improved. The reconciliation data is sent to the car manufacturer's client for reconciliation, and a reconciliation result is automatically generated. From automatically responding to the reconciliation request, obtaining billing details, generating reconciliation data, and sending the reconciliation data to the car manufacturer's client, where the car manufacturer's client generates a reconciliation result based on the reconciliation data, the entire process requires no manual intervention, reducing human error and improving reconciliation efficiency. If the reconciliation result indicates a bill anomaly, the data is modified according to the bill anomaly information, regenerated for reconciliation, and sent to the car manufacturer's client again for reconciliation, automatically generating a reconciliation result until the reconciliation result is normal, forming a closed loop and further improving reconciliation efficiency. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] Figure 1 A schematic diagram illustrating a scenario for a reconciliation method based on car purchase installment business provided in an embodiment of this application;

[0021] Figure 2 A flowchart illustrating the reconciliation method based on car purchase installment business provided in this application embodiment. Figure 1 ;

[0022] Figure 3 A flowchart illustrating the reconciliation method based on car purchase installment business provided in this application embodiment. Figure 2 ;

[0023] Figure 4 A flowchart illustrating the reconciliation method based on car purchase installment business provided in this application embodiment. Figure 3 ;

[0024] Figure 5 A schematic diagram of the structure of the reconciliation device based on car purchase installment business provided in this application embodiment;

[0025] Figure 6 A schematic diagram of the structure of a computer device provided in an embodiment of this application.

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

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

[0028] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0029] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0030] Figure 1 This is a schematic diagram illustrating a scenario of a reconciliation method based on car purchase installment business provided in an embodiment of this application, such as... Figure 1 As shown, it includes computer equipment 101 and a client 102 from an automobile manufacturer.

[0031] In this embodiment, in response to an automatically triggered reconciliation request for any car manufacturer, computer device 101 obtains the car manufacturer's billing details; generates reconciliation data for the car manufacturer based on the agreement rules with the car manufacturer and the billing details; performs basic verification and business rule verification on the reconciliation data to obtain a verification result; if the verification result is successful, computer device 101 sends the reconciliation data to the car manufacturer's client 102, so that the car manufacturer's client 102 generates a reconciliation result based on the reconciliation data; computer device 101 receives the reconciliation result sent by the car manufacturer's client 102; if the reconciliation result is a positive billing statement... If the reconciliation result is normal, the reconciliation with the car manufacturer is completed. If the reconciliation result is an abnormal bill, the following operations are performed iteratively until the reconciliation result is normal. The operations include: obtaining the abnormal bill information from the reconciliation result; modifying the bill details data according to the abnormal bill information; regenerating the car manufacturer's reconciliation data according to the agreement rules with the car manufacturer and the modified bill details data; sending the newly generated reconciliation data to the car manufacturer's client 102 so that the car manufacturer's client 102 can perform reconciliation based on the reconciliation data and generate a new reconciliation result; and the computer device 101 receiving the new reconciliation result sent by the car manufacturer's client 102.

[0032] Car installment financing is a typical example of the integration between finance and automakers. Its core logic involves banks or financial institutions providing financial support to car buyers, while automakers collaborate with banks to offer interest subsidies to lower the barrier to entry for car purchases. During the allocation of these subsidies, manufacturers and banks need to reconcile accounts to ensure the accuracy of cost allocation. Currently, the relevant technology requires banks and automakers to transmit data via Excel files, paper documents, or emails, necessitating manual reconciliation. However, this method reduces reconciliation efficiency.

[0033] To address the technical problems in related technologies, this application proposes the following technical concept: Considering that data reconciliation via Excel files, paper documents, or email, and manual reconciliation, leads to reduced efficiency, the inventors devised an automated reconciliation process. In response to an automatically triggered reconciliation request from any car manufacturer, the reconciliation process is initiated; based on the agreement rules with the car manufacturer and invoice details, reconciliation data is automatically generated. Basic verification and business rule verification improve the accuracy and efficiency of reconciliation. The reconciliation data is sent to the car manufacturer's client for reconciliation, and the reconciliation result is automatically generated. From automatically responding to reconciliation requests, obtaining invoice details, generating reconciliation data, verifying the reconciliation data, to sending the reconciliation data to the car manufacturer's client, where the client generates the reconciliation result based on the reconciliation data, the entire process requires no manual intervention, reducing human error and improving reconciliation efficiency. If the reconciliation result shows that the bill is abnormal, the abnormal bill information is modified, the reconciliation data is regenerated, and the data is sent to the car manufacturer's client again for reconciliation. The reconciliation result is generated until the reconciliation result is normal, forming a closed loop, which further improves the reconciliation efficiency.

[0034] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0035] Figure 2 A flowchart illustrating the reconciliation method based on car purchase installment business provided in this application embodiment. Figure 1 ,like Figure 2 As shown, the method includes:

[0036] S201: In response to an automatically triggered reconciliation request for any vehicle manufacturer, obtain the vehicle manufacturer's billing details.

[0037] In this embodiment, the automatically triggered reconciliation request is automatically triggered by a pre-set timed task scheduler.

[0038] In this embodiment, the reconciliation request carries the identifier of the car manufacturer to be reconciled, and the billing details of the car manufacturer are obtained based on the car manufacturer identifier.

[0039] The detailed billing data of car manufacturers is stored in the "Car Manufacturer Reconciliation Details" table in the database. By calling the interface to query manufacturer reconciliation information, the detailed billing data of car manufacturers can be obtained from the "Car Manufacturer Reconciliation Details" table. The detailed billing data of car manufacturers includes the car buyer's identity information, application information, manufacturer information, approval information, loan disbursement information, and installment information.

[0040] S202: Generate reconciliation data for the car manufacturer based on the agreement rules and billing details with the car manufacturer.

[0041] Specifically, the reconciliation fields, calculation rules, and format rules are extracted from the agreement rules with the car manufacturers; data related to the reconciliation fields is filtered out from the bill details; derived data is calculated based on the calculation rules and the data related to the reconciliation fields; and the data related to the reconciliation fields and the derived data are converted according to the format rules to generate the reconciliation data for the car manufacturers.

[0042] In this embodiment, the agreement rules with the car manufacturer are retrieved from the database table storing the agreement rules by calling the query interface. The agreement rules with the car manufacturer are read, including reconciliation fields, calculation rules, and format rules. The reconciliation fields are those fields that need to be reconciled during the reconciliation process with the car manufacturer; data related to these fields is filtered out. The calculation rules refer to the formulas or logic agreed upon with the car manufacturer for calculations, such as interest subsidy amount = installment principal × agreed interest subsidy ratio, surcharge sharing amount = total surcharge × manufacturer's share ratio, etc., used to generate the derived data required for reconciliation. The format rules refer to the presentation format requirements of the reconciliation data.

[0043] Optionally, the bill details can be checked before generating the reconciliation data, and if errors are found, they can be automatically corrected.

[0044] S203: Perform basic verification and business rule verification on the data to be reconciled to obtain the verification results.

[0045] Specifically, the basic verification checks whether the fields in the data to be reconciled are complete, whether the data type is correct, and whether the data format is correct, thus obtaining the basic verification result; the business rule verification checks whether the data in the data to be reconciled is reasonable, thus obtaining the business rule verification result; the basic verification result and the business rule verification result are combined to determine the verification result.

[0046] In this embodiment, whether a field is complete refers to verifying whether the required fields in the data to be reconciled are complete, such as the car manufacturer identifier. Missing fields need to be marked and the completion mechanism should be triggered to automatically fill in the default value or prompt for manual supplementation.

[0047] In this embodiment, whether the data type is correct refers to verifying whether the data type of each field conforms to the agreement, such as the amount field needing to be numeric; whether the data format is correct refers to verifying whether the data format of each field conforms to the agreement, such as the date field needing to conform to the YYYY-MM-DD format, and the mobile phone number field needing to be 11 digits, etc.

[0048] In this embodiment, business rule verification refers to verifying the reasonableness of the data values, such as the amount range. If the car manufacturer's agreement stipulates that the amount of a single installment payment shall not exceed 500,000 yuan, and the amount in the data to be reconciled is 600,000 yuan, then the business verification will fail.

[0049] S204: If the verification result is successful, the reconciliation data will be sent to the car manufacturer's client so that the car manufacturer's client can generate the reconciliation result based on the reconciliation data.

[0050] In this embodiment, when sending reconciliation data, an external interface with the car manufacturer is invoked to send the data to the car manufacturer's client. This external interface is a dedicated connection channel for data interaction with external organizations, specifically designed to enable information transfer and communication between different computer devices.

[0051] Optionally, the sending time and data identifier of the data to be reconciled can be saved to the car manufacturer reconciliation log in the database to ensure that the data transmission trajectory is traceable.

[0052] Specifically, the process involves hashing the reconciliation data to generate a first hash value; encrypting the first hash value to generate a digital signature; initiating a session key negotiation process with the car manufacturer's client to obtain a session key; encrypting the reconciliation data and digital signature using the session key to obtain an encrypted reconciliation data packet; sending the encrypted reconciliation data packet to the car manufacturer's client, where the client uses the session key to decrypt the encrypted reconciliation data packet to obtain the reconciliation data and digital signature; decrypting the digital signature to obtain the original first hash value; hashing the reconciliation data to generate a second hash value; and generating a reconciliation result based on the reconciliation data if the second hash value matches the first hash value.

[0053] In this embodiment, the first hash value is encrypted using the bank system's private key. After receiving the encrypted reconciliation data packet, the car manufacturer's client decrypts it using the session key to obtain the digital signature and the data to be reconciled. The digital signature is then decrypted using the bank system's public key to obtain the original first hash value. A hash calculation is performed on the data to be reconciled to generate a second hash value. If the second hash value matches the first hash value, it indicates that the data to be reconciled originates from the bank system and has not been tampered with; otherwise, it indicates that the data to be reconciled is abnormal.

[0054] S205: Receive reconciliation results sent by the car manufacturer's client.

[0055] Optionally, if it is detected that the car manufacturer's client does not have a reconciliation function, the report export interface is called; the data to be reconciled is exported in report format through the report export interface; the exported data to be reconciled is used for offline reconciliation with the car manufacturer; and the reconciliation results are obtained in response to the reconciliation result upload operation performed on the reconciliation result page.

[0056] In this embodiment, when it is detected that the car manufacturer's client does not have reconciliation functionality, an asynchronous operation will automatically call the report export interface to export the data to be reconciled into a report. After offline reconciliation is completed, the reconciliation results are uploaded on the reconciliation results page. Responding to this operation, the system receives and parses the uploaded reconciliation results, ensuring closed-loop management of the offline reconciliation process. This requires saving the task of calling the report export interface to export the data to be reconciled into a report to the asynchronous download task table for car installment manufacturer reconciliation data in the database.

[0057] S206: If the reconciliation result shows that the bill is normal, the reconciliation process with the car manufacturer is completed.

[0058] S207: If the reconciliation result is that the bill is abnormal, then perform the following operations iteratively until the reconciliation result is that the bill is normal.

[0059] The operation includes: obtaining bill anomaly information from the reconciliation results; modifying the bill details data based on the bill anomaly information; regenerating the reconciliation data for the car manufacturer based on the agreement rules with the car manufacturer and the modified bill details data; sending the newly generated reconciliation data to the car manufacturer's client so that the car manufacturer's client can perform reconciliation based on the reconciliation data and generate a new reconciliation result; and receiving the new reconciliation result sent by the car manufacturer's client.

[0060] In this embodiment, bill anomaly information, such as incorrect VIN format and installment principal calculation deviation, is extracted from the reconciliation results. The bill detail data is modified by calling the submit bill modification request interface. After the request is approved, the update bill detail data interface is called to modify the car manufacturer reconciliation detail table in the database according to the bill anomaly information and re-obtain the modified bill detail data.

[0061] In this embodiment, the modification record is saved to the vehicle manufacturer reconciliation modification record table in the database to ensure that the modification is traceable. Optionally, the modification can be to change a single bill data entry in the bill details data, or to modify a file within the bill details data. If a single bill data entry is modified, the modified bill details data is saved to the vehicle manufacturer reconciliation pending review table in the database. The data in the vehicle manufacturer reconciliation pending review table is used to review the modified data. Specifically, the review is performed by calling the review reconciliation modification application interface. If a file is modified, the modified file needs to be saved to the reconciliation file submission review table in the database. The data in the reconciliation file submission review table is used to review the modified file. Optionally, the database also contains a reconciliation file failure information table to save records of failed file submissions.

[0062] Optionally, automatic reconciliation for return scenarios is supported. Automatic reconciliation for return scenarios means that when a customer returns a car, the reconciliation process for the return business is automatically triggered: without manual intervention, it automatically acquires return-related data, generates corresponding return reconciliation data according to the return reconciliation rules in the agreement with the car manufacturer, and sends the return reconciliation data to the car manufacturer's client, so that the car manufacturer's client can generate return reconciliation results. If the return reconciliation result shows an abnormal bill, the abnormal bill information is saved to the car manufacturer's reconciliation return abnormality table in the database.

[0063] Optionally, the database also contains a vendor reconciliation query permission table, which is used for access control and stores the roles that can view reconciliation-related data.

[0064] Optionally, it also includes interfaces for uploading manufacturer reconciliation information, receiving reconciliation discrepancy data, querying manufacturer reconciliation statements through banks, updating reconciliation statement status, updating reconciliation statement details, querying reconciliation statement data, batch updating reconciliation statement data, querying manufacturer file upload process information, reviewing manufacturer reconciliation file upload process, querying reconciliation statement list, accessing reconciliation statement details, submitting reconciliation statement modification requests, reviewing reconciliation statement modification requests, maintaining reconciliation statements, querying reconciliation statement modification records, querying reconciliation statement process flow, exporting manufacturer reconciliation data, querying manufacturer reconciliation data, querying and exporting manufacturer reconciliation data, and maintaining vehicle installment return data, etc., to implement different functions in the reconciliation process.

[0065] In summary, the system automatically initiates a reconciliation process in response to any reconciliation request triggered by a car manufacturer. Based on the agreement rules and billing details with the car manufacturer, it automatically generates reconciliation data. Basic and business rule validations are performed on this data to obtain validation results. If the validation passes, the data is sent to the car manufacturer's client for reconciliation, automatically generating a reconciliation result. From automatically responding to reconciliation requests, obtaining billing details, generating reconciliation data, validating the data, and sending it to the car manufacturer's client (which then generates the reconciliation result), the entire process requires no manual intervention, reducing human error and improving efficiency. If the reconciliation result indicates an anomaly in the billing details, the data is modified based on the anomaly information, regenerated, and sent back to the car manufacturer's client for reconciliation, automatically generating a reconciliation result until the result is correct, forming a closed loop and further improving reconciliation efficiency. Furthermore, by encrypting the reconciliation data and digital signatures using session keys, it is ensured that even if intercepted during transmission, the original information cannot be decrypted and obtained, thus preventing data leakage. By comparing the first hash value with the second hash value, it is possible to detect whether the reconciliation data has been tampered with during transmission or storage. If they do not match, the data will be rejected, thus eliminating the risk of the reconciliation data being forged or modified from a technical perspective.

[0066] refer to Figure 3 , Figure 3 A flowchart illustrating the reconciliation method based on car purchase installment business provided in this application embodiment. Figure 2 Based on the above embodiments, this embodiment introduces a pre-configured timed task scheduler, detailed as follows:

[0067] S301: Obtain the vehicle manufacturer identifiers of multiple vehicle manufacturers.

[0068] S302: Obtain the reconciliation period corresponding to the reconciliation period field from the agreement rules with each car manufacturer.

[0069] The agreements with each automaker are documents signed between the two companies to regulate the reconciliation process. These agreements typically revolve around rules and requirements related to reconciliation to ensure its smooth operation. These agreements are stored in a database; for example, database tables might be named "Automaker Reconciliation Parameter Table" and "Automaker Additional Fee Breakdown Reconciliation Table."

[0070] S303: Based on the vehicle manufacturer identification and reconciliation schedule of each vehicle manufacturer, use a scheduled task scheduler to generate reconciliation requests for each vehicle manufacturer.

[0071] In this embodiment, the manufacturer identifiers and reconciliation schedules of each automaker are stored to form the basic data for scheduled tasks. During initialization, the scheduled task scheduler periodically queries the basic data for all automakers' manufacturer identifiers and reconciliation schedules. The scheduler compares the current date with the reconciliation schedules of each automaker, filters out the automakers that require reconciliation, and for each filtered automaker, generates a corresponding reconciliation request based on the manufacturer identifier, automatically triggering the reconciliation request to ensure that the reconciliation request for each automaker is accurately generated according to the reconciliation schedule.

[0072] For example, the car manufacturer is identified as A, and the reconciliation period is the 25th of each month. On the 25th of each month, the scheduled task automatically triggers the reconciliation request.

[0073] In this embodiment, if multiple car manufacturers have the same reconciliation period, all reconciliation requests triggered on the same day will be included in the task queue and sorted according to the priority of the car manufacturers or a preset order to avoid concurrent conflicts.

[0074] In summary, by pre-setting a scheduled task scheduler, the scheduler automatically generates reconciliation requests according to the reconciliation schedules of each automaker, thus triggering the reconciliation requests without manual intervention and avoiding omissions or delays in reconciliation due to human error. Furthermore, by obtaining the reconciliation schedules from the agreement rules with each automaker, it is ensured that each automaker's reconciliation process is triggered only for that automaker.

[0075] refer to Figure 4 , Figure 4 A flowchart illustrating the reconciliation method based on car purchase installment business provided in this application embodiment. Figure 3 Based on the above embodiments, this embodiment sets a reconciliation status to indicate the progress of reconciliation with the car manufacturer, as detailed below:

[0076] S401: Set reconciliation status; reconciliation status indicates the progress of reconciliation with the car manufacturer.

[0077] S402: When it is detected that no billing details data has been obtained, update the reconciliation status to pending verification.

[0078] In this embodiment, the "pending verification" status indicates that the reconciliation progress with the car manufacturer is in the stage of waiting to obtain detailed billing data.

[0079] S403: When it is detected that bill detail data has been obtained, but no reconciliation data has been generated, the reconciliation status is updated to the status of preparing to generate reconciliation data.

[0080] In this embodiment, the status of preparing to generate reconciliation data indicates that the reconciliation progress with the car manufacturer is in the stage where bill details have been obtained, but reconciliation data needs to be generated based on the bill details.

[0081] S404: When it is detected that reconciliation data has been generated but has not been sent to the car manufacturer's client, the reconciliation status is updated to pending sending status.

[0082] In this embodiment, the "pending send" status indicates the progress of reconciliation with the car manufacturer, specifically the stage where the reconciliation data has been generated but has not yet been sent to the car manufacturer's client via an external interface call.

[0083] S405: After detecting that the reconciliation data to be sent to the car manufacturer's client, but not detecting that the reconciliation result sent by the car manufacturer's client has been received, the reconciliation status is updated to pending status.

[0084] In this embodiment, the pending status indicates the progress of reconciliation with the car manufacturer, which is in the stage where reconciliation data has been sent but the reconciliation results have not been received from the car manufacturer's client.

[0085] S406: When it is detected that the reconciliation process with the car manufacturer has been completed, update the reconciliation status to "reconciliation successful".

[0086] In this embodiment, the successful verification status indicates that the reconciliation with the car manufacturer is in progress and the reconciliation is complete.

[0087] S407: When an abnormal bill is detected in the reconciliation result, the reconciliation status will be updated to "return to be modified".

[0088] In this embodiment, the "return to pending modification" status indicates that the reconciliation progress with the car manufacturer is in the stage where the reconciliation result is an abnormal bill, and the bill details data needs to be modified based on the abnormal bill information in the abnormal bill.

[0089] S408: When it is detected that the bill details data has been modified and the car manufacturer's reconciliation data has been regenerated, the reconciliation status will be updated to "Modified and Reviewed".

[0090] In this embodiment, the "modified and reviewed" status indicates that the reconciliation progress with the car manufacturer has been completed, and the review of the modified bill details data has been completed.

[0091] In this embodiment, the database also includes a reconciliation status table for car manufacturers. This table records the reconciliation status.

[0092] In summary, by setting reconciliation status and updating it according to different reconciliation progresses with car manufacturers, the reconciliation progress can be quickly understood. This reduces manual intervention and allows the reconciliation process to proceed automatically according to preset logic, further improving reconciliation efficiency.

[0093] In the above embodiments, the reconciliation method based on car purchase installment business is applicable to reconciliation scenarios between the head office and the car manufacturer, as well as reconciliation scenarios between branch banks and the car manufacturer.

[0094] Figure 5 This is a schematic diagram of the structure of the reconciliation device based on car purchase installment business provided in the embodiments of this application, as shown below. Figure 5 As shown, the reconciliation device based on car purchase installment business provided in this embodiment includes: a response module 501, a first generation module 502, a verification module 503, a second generation module 504, a receiving module 505, a first reconciliation completion module 506, and a second reconciliation completion module 507.

[0095] The response module 501 is used to respond to an automatically triggered reconciliation request for any car manufacturer and obtain the car manufacturer's billing details data.

[0096] The first generation module 502 is used to generate the reconciliation data of the car manufacturer based on the agreement rules and billing details with the car manufacturer.

[0097] The verification module 503 is used to perform basic verification and business rule verification on the data to be reconciled, and obtain the verification results.

[0098] The second generation module 504 is used to send the reconciliation data to the car manufacturer's client if the verification result is successful, so that the car manufacturer's client can generate the reconciliation result based on the reconciliation data.

[0099] The receiving module 505 is used to receive the reconciliation results sent by the car manufacturer's client.

[0100] The first reconciliation completion module 506 is used to complete the reconciliation process with the car manufacturer if the reconciliation result shows that the bill is normal.

[0101] The second reconciliation completion module 507 is used to iteratively perform the following operations if the reconciliation result is that the bill is abnormal, until the reconciliation result is that the bill is normal.

[0102] The operation includes: obtaining bill anomaly information from the reconciliation results; modifying the bill details data based on the bill anomaly information; regenerating the reconciliation data for the car manufacturer based on the agreement rules with the car manufacturer and the modified bill details data; sending the newly generated reconciliation data to the car manufacturer's client so that the car manufacturer's client can perform reconciliation based on the reconciliation data and generate a new reconciliation result; and receiving the new reconciliation result sent by the car manufacturer's client.

[0103] In one possible implementation, the first generation module 502 is specifically used to: extract reconciliation fields, calculation rules, and format rules from the agreement rules with the car manufacturer; filter out data related to the reconciliation fields from the bill detail data; calculate derived data according to the calculation rules and the data related to the reconciliation fields; and convert the data related to the reconciliation fields and the derived data according to the format rules to generate the reconciliation data to be generated for the car manufacturer.

[0104] In one possible implementation, the second generation module 504 is specifically configured to: perform a hash calculation on the reconciliation data to generate a first hash value; encrypt the first hash value to generate a digital signature; initiate a session key negotiation process with the car manufacturer's client to obtain a session key; encrypt the reconciliation data and the digital signature using the session key to obtain an encrypted reconciliation data packet; send the encrypted reconciliation data packet to the car manufacturer's client, whereby the car manufacturer's client uses the session key to decrypt the encrypted reconciliation data packet to obtain the reconciliation data and the digital signature; decrypt the digital signature to obtain the original first hash value; perform a hash calculation on the reconciliation data to generate a second hash value; and if the second hash value matches the first hash value, generate a reconciliation result based on the reconciliation data.

[0105] In one possible implementation, the verification module 503 is specifically used to: verify whether the fields in the data to be reconciled are complete, whether the data type is correct, and whether the data format is correct through basic verification, and obtain the basic verification result; verify whether the data in the data to be reconciled is reasonable through business rule verification, and obtain the business rule verification result; and determine the basic verification result and the business rule verification result as the verification result.

[0106] In one possible implementation, the reconciliation device based on car purchase installment business further includes: a setting module, which is specifically used to obtain the car manufacturer identifiers of multiple car manufacturers; obtain the reconciliation timing period corresponding to the reconciliation timing period field from the agreement rules with each car manufacturer; and generate reconciliation requests for each car manufacturer using a timed task scheduler according to the car manufacturer identifier and the reconciliation timing period of each car manufacturer.

[0107] In one possible implementation, the reconciliation device based on car purchase installment business further includes: a setting module, specifically used to set the reconciliation status; the reconciliation status represents the reconciliation progress with the car manufacturer; when it is detected that no bill detail data has been obtained, the reconciliation status is updated to a pending verification status; when it is detected that bill detail data has been obtained, but no reconciliation data has been generated, the reconciliation status is updated to a state of preparing to generate reconciliation data; when it is detected that reconciliation data has been generated, but the reconciliation data has not been sent to the car manufacturer's client, the reconciliation status is updated to a state of preparing to generate reconciliation data. The reconciliation status is initially set to "Pending Send". If, after detecting that the reconciliation data has been sent to the car manufacturer's client, but no reconciliation result has been received from the car manufacturer's client, the reconciliation status is updated to "Pending Processing". If the reconciliation process with the car manufacturer is completed, the reconciliation status is updated to "Verification Successful". If the reconciliation result indicates an abnormal bill, the reconciliation status is updated to "Returned for Modification". If the bill details have been modified and the car manufacturer's reconciliation data has been regenerated, the reconciliation status is updated to "Modified and Reviewed".

[0108] In one possible implementation, the reconciliation device based on car purchase installment business further includes: an export module, specifically used to call a report export interface if it is detected that the car manufacturer's client does not have a reconciliation function; export the data to be reconciled in report format through the report export interface; wherein the exported data to be reconciled is used for offline reconciliation with the car manufacturer; and obtain the reconciliation result in response to the reconciliation result upload operation performed on the reconciliation result page.

[0109] The reconciliation device based on car purchase installment business provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0110] Figure 6 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 6 As shown, the computer device provided in this embodiment includes at least one processor 601 and a memory 602. Optionally, the computer device further includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus.

[0111] In a specific implementation, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to perform the above-described method.

[0112] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0113] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0114] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0115] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0116] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0117] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0118] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0119] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0120] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0121] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0122] In addition, the functional units in the various embodiments of the present invention 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.

[0123] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0124] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0125] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A reconciliation method based on car purchase installment business, characterized in that, Applied to computer equipment, including: In response to an automatically triggered reconciliation request for any car manufacturer, obtain the billing details data of that car manufacturer; Based on the agreement rules with the car manufacturer and the billing details, generate the car manufacturer's pending reconciliation data; Perform basic verification and business rule verification on the data to be reconciled to obtain the verification results; If the verification result is successful, the reconciliation data is sent to the car manufacturer's client so that the car manufacturer's client can generate a reconciliation result based on the reconciliation data. Receive the reconciliation results sent by the car manufacturer's client; If the reconciliation result shows that the bill is normal, the reconciliation process with the car manufacturer is completed. If the reconciliation result indicates that the bill is abnormal, then perform the following operations iteratively until the reconciliation result indicates that the bill is normal; The operation includes: obtaining bill anomaly information from the reconciliation results; modifying the bill detail data based on the bill anomaly information; regenerating the car manufacturer's reconciliation data according to the agreement rules with the car manufacturer and the modified bill detail data; sending the newly generated reconciliation data to the car manufacturer's client so that the car manufacturer's client can perform reconciliation based on the reconciliation data and generate a new reconciliation result; and receiving the new reconciliation result sent by the car manufacturer's client.

2. The method according to claim 1, characterized in that, The step of generating the car manufacturer's pending reconciliation data based on the agreement rules with the car manufacturer and the billing details includes: Extract the reconciliation fields, calculation rules, and format rules from the agreement rules with the aforementioned car manufacturers; Filter out the data related to the reconciliation field from the bill details data; Based on the calculation rules and the data related to the reconciliation fields, derived data is calculated; The data related to the reconciliation fields and the derived data are converted according to the format rules to generate the reconciliation data for the car manufacturer.

3. The method according to claim 1, characterized in that, The step of sending the reconciliation data to the car manufacturer's client, so that the car manufacturer's client can generate a reconciliation result based on the reconciliation data, includes: Perform a hash calculation on the data to be reconciled to generate a first hash value; The first hash value is encrypted to generate a digital signature; Initiate a session key negotiation process with the car manufacturer's client to obtain the session key; The session key is used to encrypt the reconciliation data and the digital signature to obtain an encrypted reconciliation data packet; The encrypted reconciliation data packet is sent to the car manufacturer's client. The car manufacturer's client uses the session key to decrypt the encrypted reconciliation data packet to obtain the data to be reconciled and the digital signature. The digital signature is decrypted to obtain the original first hash value. The data to be reconciled is hashed to generate a second hash value. If the second hash value and the first hash value are consistent, a reconciliation result is generated based on the data to be reconciled.

4. The method according to claim 1, characterized in that, The basic verification and business rule verification of the data to be reconciled are performed to obtain the verification results, including: The basic verification process verifies whether the fields in the data to be reconciled are complete, whether the data type is correct, and whether the data format is correct, thus obtaining the basic verification result. The business rule verification is used to check whether the data in the reconciliation data is reasonable, and the business rule verification result is obtained. The basic verification result and the business rule verification result are determined as the verification result.

5. The method according to claim 1, characterized in that, The response prior to an automatically triggered periodic reconciliation request for any car manufacturer includes: Obtain the vehicle manufacturer identifiers from multiple car manufacturers; Obtain the reconciliation period corresponding to the reconciliation period field from the agreement rules with each car manufacturer; Based on the vehicle manufacturer identifier and the reconciliation period of each vehicle manufacturer, a scheduled task scheduler is used to generate reconciliation requests for each vehicle manufacturer.

6. The method according to claim 1, characterized in that, Also includes: Set the reconciliation status; the reconciliation status indicates the progress of reconciliation with the car manufacturer. If the bill details data is not obtained, the reconciliation status will be updated to pending verification. When it is detected that the bill details data has been obtained, but the reconciliation data has not been generated, the reconciliation status is updated to the status of preparing to generate reconciliation data. When it is detected that the reconciliation data has been generated, but the reconciliation data has not been sent to the car manufacturer's client, the reconciliation status is updated to the pending sending status. If the reconciliation status is updated to pending status after the data to be reconciled is detected to be sent to the car manufacturer's client, but no reconciliation result is received from the car manufacturer's client; When it is detected that the reconciliation process with the car manufacturer has been completed, the reconciliation status is updated to a successful reconciliation status. When the reconciliation result is detected as an abnormal bill, the reconciliation status will be updated to a state of being returned for modification. When it is detected that the bill details data has been modified and the car manufacturer's reconciliation data has been regenerated, the reconciliation status is updated to "Modification Reviewed".

7. The method according to any one of claims 1-6, characterized in that, After obtaining the reconciliation data from the car manufacturer, the process also includes: If it is detected that the car manufacturer's client does not have a reconciliation function, the report export interface is called; The data to be reconciled is exported in report format through the report export interface; the exported data to be reconciled is used for offline reconciliation with the car manufacturer. Retrieve reconciliation results in response to the reconciliation results upload operation performed on the reconciliation results page.

8. A reconciliation device based on car purchase installment business, characterized in that, Applied to computer equipment, including: The response module is used to respond to an automatically triggered reconciliation request for any car manufacturer and obtain the billing details data of that car manufacturer. The first generation module is used to generate the reconciliation data of the car manufacturer based on the agreement rules with the car manufacturer and the billing details data. The verification module is used to perform basic verification and business rule verification on the data to be reconciled, and obtain the verification results; The second generation module is used to send the reconciliation data to the car manufacturer's client if the verification result is successful, so that the car manufacturer's client can generate a reconciliation result based on the reconciliation data. A receiving module is used to receive the reconciliation results sent by the car manufacturer's client. The first reconciliation completion module is used to complete the reconciliation process with the car manufacturer if the reconciliation result is that the bill is normal. The second reconciliation completion module is used to iteratively perform the following operations if the reconciliation result is that the bill is abnormal, until the reconciliation result is that the bill is normal. The operation includes: obtaining bill anomaly information from the reconciliation results; modifying the bill detail data based on the bill anomaly information; regenerating the car manufacturer's reconciliation data according to the agreement rules with the car manufacturer and the modified bill detail data; sending the newly generated reconciliation data to the car manufacturer's client so that the car manufacturer's client can perform reconciliation based on the reconciliation data and generate a new reconciliation result; and receiving the new reconciliation result sent by the car manufacturer's client.

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

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

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

Images