Enterprise annuity service automatic receiving platform and control method

Abstract

The application relates to an enterprise annuity business automatic receiving platform and a control method, which comprises the following steps: step S1, based on a constructed unified rule database, individualized configuration of rule data sets of a trust end is carried out, and the rule data sets are encapsulated into a verification set according to business types; step S2, after the receiving platform receives an instruction package, the encapsulated verification set is called to analyze data in the instruction package and to carry out step-by-step verification; after verification, step S3 is entered to receive business according to business types, otherwise, an abnormal processing process is entered; step S3, an adaptive business process node is automatically generated according to analyzed instruction package data, and account management is interacted to process business; if an account management feedback exception occurs in the interaction process, the abnormal processing process is entered. Compared with the prior art, the application has the advantages of high universality and high business processing efficiency.

Description

Technical Field

[0001] This invention relates to the field of enterprise annuity business acceptance technology, and in particular to an automatic enterprise annuity business acceptance platform and control method. Background Technology

[0002] Currently, corporate annuity services cover over 100,000 enterprises and 27.17 million individuals. Account management institutions primarily handle the management of enterprise and individual accounts, involving a series of accounting processes such as account setup, contribution, payment, subscription, and redemption. The existing corporate annuity service processing has the following problems:

[0003] 1) Low code reusability;

[0004] 2) The interface is prone to change and difficult to maintain:

[0005] 3) The verification rules are scattered, the interaction is frequently interrupted, and the business processing efficiency is low;

[0006] 4) The processes are fragmented, resulting in a large workload for operations. Summary of the Invention

[0007] The purpose of this invention is to overcome the shortcomings of the existing technology and provide a highly versatile and efficient automatic acceptance platform and control method for enterprise annuity business.

[0008] The objective of this invention can be achieved through the following technical solutions:

[0009] According to a first aspect of the present invention, a control method for an automated enterprise annuity business processing platform is provided, the method comprising the following steps:

[0010] Step S1: Based on the constructed unified rule database, configure the rule dataset of the entrusted end in a personalized way, and encapsulate it into a verification set according to the business type;

[0011] Step S2: After receiving the instruction packet, the acceptance platform calls the encapsulated verification set to parse and verify the data in the instruction packet level by level; if the verification is successful, proceed to step S3 to accept the business according to the business type; otherwise, enter the exception handling process.

[0012] Step S3: Automatically generate suitable business process nodes based on the parsed instruction package data, and interact with the accounting management system to process business; if the accounting management system reports an abnormality during the interaction process, the abnormality handling process will be initiated.

[0013] Preferably, the unified rule database in step S1 includes an interface rule database, a file verification rule database, and a data verification rule database;

[0014] The data verification rules, through parameterized verification attributes and verification levels, are used to control the flow of abnormal information and divide the information levels when data verification fails.

[0015] Preferably, the step S2, in which the acceptance platform receives the instruction packet, further includes: a mechanism in which an empty packet is sent by a third-party platform jointly accessed by the acceptance platform and the entrusted end at set intervals, and the acceptance platform provides corresponding feedback.

[0016] Preferably, the step S2 of parsing and verifying the data in the instruction packet specifically involves: parsing the data packet and performing step-by-step verification on the data in the instruction packet in batches according to the predefined verification attributes and verification levels of the verification rules; the step-by-step verification is in the order of file verification and data verification.

[0017] Preferably, the exception handling includes file verification exceptions, data verification exceptions, and account management feedback processing exceptions;

[0018] The document verification is a strong control verification. When an anomaly occurs, the anomaly information is directly fed back to the entrusted end, and the instruction processing ends.

[0019] Preferably, the data verification anomalies include control verification anomalies, prompt verification anomalies, and prompt-acceptable verification anomalies, and the specific processing procedures are as follows:

[0020] Control verification anomaly handling: The anomaly information is directly fed back to the entrusted party, and the instruction acceptance ends;

[0021] Prompt verification exception handling: Push the exception to the to-do workbench according to the permissions, and manually handle the exception. After the exception is handled, re-verify the rule until the verification passes; if the manual confirms that the exception cannot be handled, the exception can be fed back to the entrusted end, and the instruction processing ends.

[0022] Prompt-based - Acceptable verification exception handling: Push the verification to the to-do workbench according to permissions. If the manual reviewer can ignore the exception and continue to configure and advance according to the preset process, or if the manual reviewer confirms that the exception cannot be ignored, the exception can be reported back to the entrusted end, and the instruction processing ends.

[0023] Preferably, the specific processing procedure for the abnormal account management feedback is as follows: 1) If the acceptance option is "accept", the sub-transaction is resent for its splitting request; 2) If the acceptance option is "abandon", the instruction is accepted and abandoned, and the account management transaction is rolled back offline. After the problem is resolved, the instruction package can be re-accepted and re-processed through the abandonment and resending function.

[0024] 8. The control method for an automated enterprise annuity business processing platform, as described above, is characterized in that the interaction with the account management system in step S3 includes three interactions, specifically:

[0025] First interaction: The platform sends a request to split the sub-transaction;

[0026] The second interaction: The entrusted end creates a business transaction number and sends the business transaction number back to the acceptance platform, which then records the business transaction number;

[0027] The third interaction: The entrusted end continues to process the sub-transaction. After processing, it sends the processing result back to the acceptor. If there is an error, the error information must be sent back at the same time. If the current node is the last sub-transaction node in the business processing stage, the account manager must send back the processing result of successful acceptance after successful processing, and at the same time organize the feedback document.

[0028] According to a second aspect of the present invention, a corporate annuity business processing platform is provided, employing any one of the methods described above, the platform comprising:

[0029] The rules database module is used to verify the incoming standard data packets and provide a data interface;

[0030] The verification module is used to perform batch and step-by-step file verification before business acceptance, data verification during business acceptance, and verification of accounting and management interaction results after business processing in the instruction package.

[0031] The business acceptance module is used to automatically generate appropriate business process nodes based on the data of the instruction package that has passed the verification module, and interact with the account management.

[0032] The exception handling module is used to handle exceptions for instruction packets that fail the verification module.

[0033] Preferably, the information flow between the modules in the platform is carried out through a full-chain business management system based on Robotic Process Automation (RPA) technology.

[0034] Compared with the prior art, the present invention has the following advantages:

[0035] 1) High maintainability: The system adopts a modular encapsulation concept. When business adjustments lead to interface adjustments or validation rule adjustments, there is no need to adjust the processing flow. Only the newly added interface elements or validation rules in the encapsulated rule database need to be called in the processing flow, resulting in a small overall impact.

[0036] 2) High reusability / versatility: Although there are differences in the same business across different entrusted ends, there are a large number of common business rules. By establishing a unified rule base, different entrusted ends can parameterize and configure business rules, improving code reusability and reducing workload; unified process design, through unified connection between business processing links and the accounting management backend, establishes a unified interaction interface, reducing the need for adjustments to the accounting management logic due to changes in external interfaces, and making the system more versatile;

[0037] 3) Simplified and clear processes: By adopting Robotic Process Automation (RPA) technology, processes are automatically integrated, which greatly reduces the number of operation steps and makes the business processing flow clearer and the processing process more explicit. At the same time, the simplification of processes does not affect the rigor of the original business processing. The process-driven automation improves business efficiency.

[0038] 4) More complete information monitoring: Full-process monitoring ensures that information is not fragmented or lost, providing a necessary prerequisite for subsequent statistical services with more dimensions. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the method flow of the present invention;

[0040] Figure 2 This is a schematic diagram of the standard treatment payment business processing flow in the embodiment. Detailed Implementation

[0041] 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 should fall within the scope of protection of the present invention.

[0042] Example

[0043] This embodiment provides a control method for the aforementioned automated enterprise annuity business processing platform, the method comprising the following steps:

[0044] Step S1: Based on the constructed unified rule database, including the interface rule database, file verification rule database and data verification rule database, configure the rule dataset of the entrusted end in a personalized way and encapsulate it into a verification set according to the business type;

[0045] The data verification rules, through parameterized verification attributes and verification levels, are used to control the flow of abnormal information and divide the information levels when data verification fails.

[0046] Step S2: After receiving the instruction packet, the acceptance platform calls the encapsulated verification set to parse and verify the data in the instruction packet level by level; if the verification is successful, proceed to step S3 to accept the business according to the business type; otherwise, enter the exception handling process.

[0047] In this embodiment, both the acceptance platform and the entrusted end use the Shenzhen Stock Exchange Platform (SZSE) as a third-party platform for interaction. To prevent data loss and disruption to normal business operations caused by SZSE sending data but the acceptance platform not receiving it, or by the acceptance platform providing feedback but SZSE not receiving it, this invention employs a data polling mechanism: SZSE sends empty packets every hour, and the acceptance platform provides corresponding feedback. This mechanism allows for timely detection of instability on the SZSE platform, reducing business risks.

[0048] The step S2 of parsing and verifying the data in the instruction packet specifically involves: parsing the data packet and performing step-by-step verification on the data in the instruction packet in batches according to the predefined verification attributes and verification levels of the verification rules; the step-by-step verification is in the order of file verification and data verification.

[0049] The exception handling includes file verification exceptions, data verification exceptions, and account management feedback processing exceptions.

[0050] 1) File verification error: File verification is a strong control verification. When an error occurs, the error information is directly fed back to the entrusted end in the form of a .fail file, and the instruction processing ends.

[0051] 2) Data validation anomalies: These include control validation anomalies, warning validation anomalies, and warning-acceptable validation anomalies. The specific handling procedures are as follows:

[0052] Control check exception handling: The exception information is directly fed back to the entrusted party in the form of an .er file, and the instruction acceptance ends;

[0053] Prompt verification exception handling: Push the exception to the to-do workbench according to the permissions, and manually handle the exception. After the exception is handled, the rule is re-verified until the verification passes; if the manual confirmation is that the exception cannot be handled, the exception is fed back to the entrusted end in the form of a .er file, and the instruction acceptance ends.

[0054] Prompt-based - Acceptable verification exception handling: Push the verification to the to-do workbench according to permissions. If the manual reviewer can ignore the exception and continue to configure and advance according to the preset process, or if the manual reviewer confirms that the exception cannot be ignored, report the exception to the entrusted end in the form of an .er file, and the instruction processing ends.

[0055] 3) Account Management Feedback Processing Abnormalities: If the acceptance option is "Accept", the sub-transaction will be resubmitted for splitting; if the acceptance option is "Abandon", the instruction will be abandoned and the account management transaction will be rolled back offline. After the problem is resolved, the instruction package can be re-accepted and resubmitted through the abandonment and resending function.

[0056] Step S3: Automatically generate adapted business process nodes based on the parsed instruction package data, and interact with the accounting management system to process business; if an abnormality is detected by the accounting management system during the interaction process, the abnormality handling process will be initiated.

[0057] During business processing, the normal interaction with the accounting system occurs in three parts:

[0058] First interaction: The receiving platform sends a request to split the sub-transaction (including the splitting file);

[0059] The second interaction: The entrusted end creates a business transaction number and sends the business transaction number back to the acceptance platform, which then records the business transaction number;

[0060] The third interaction: The entrusted end continues to process the sub-transaction. After processing, it sends the processing result back to the acceptor. If there is an error, the error information must be sent back at the same time. If the current node is the last sub-transaction node in the business processing stage, the account manager must send back the processing result of successful acceptance after successful processing, and at the same time organize the feedback document.

[0061] This embodiment uses the processing of standard benefit payment transactions on an automated enterprise annuity business processing platform as an example to provide a detailed description of the method of the present invention. Figure 2 As shown, the specific steps include:

[0062] 1. Data packet files are accessed through the acceptance platform;

[0063] 2. After data access, the receiving platform verifies the documents;

[0064] 3. After the file verification is successful, a succ file is sent. Based on the relevant regulations of Bank of Communications and the Ministry of Human Resources and Social Security, relevant risk control and monitoring settings are designed for the payment business process.

[0065] 4. If file verification fails, a fail file will be sent.

[0066] 5. Once the file verification passes, proceed to the data verification stage;

[0067] 6. If the document verification fails, the process ends.

[0068] 7. After data verification is completed, proceed to personal information change. In accordance with the relevant regulations of Bank of Communications and the Ministry of Human Resources and Social Security, design relevant risk control and monitoring settings for the payment business process;

[0069] 8. If data validation fails, proceed to exception handling;

[0070] 9. After personal information is changed, the beneficiary change process will be initiated, and the account manager will handle the corresponding procedures.

[0071] 10. After the beneficiary changes, the payment rules will be changed, and the account manager will make the corresponding processing.

[0072] 11. After the payment rules are changed, the system will be assigned to a batch account, and the account manager will process the changes accordingly.

[0073] 12. After batch allocation, a payment application is submitted, and the accounting department processes it accordingly;

[0074] 13. If the exception handling during data verification is not accepted, the process is complete.

[0075] 14. If the exception handling during data verification is accepted, the normal process for personal information change will begin;

[0076] 15. If an exception is rejected, feedback should be sent to the er file;

[0077] 16. Payment application complete, data monitoring begins;

[0078] 17. After monitoring the data, determine whether D00228 needs to be paid.

[0079] 18. When making supplementary payments for D00228, the periodic fixed amount parameters should be changed;

[0080] 19. D00228 Send tr feedback file during non-supplementary payment;

[0081] 20. Send 0214 file while monitoring data;

[0082] 21. The application for change of periodic quota parameters is completed;

[0083] 22. Any abnormalities occurring during the personal information change, beneficiary change, payment rule change, batch attribution, or payment application process will trigger an exception handling process.

[0084] 23. If the exception handling is accepted, the sub-process continues;

[0085] 24. If exception handling is discarded, the instruction is discarded.

[0086] Next, an automated enterprise annuity business processing platform is presented, employing the above method. The platform includes:

[0087] The rules database module is used to verify the incoming standard data packets and provide a data interface;

[0088] The verification module is used to perform batch and step-by-step file verification before business acceptance, data verification during business acceptance, and verification of accounting and management interaction results after business processing in the instruction package.

[0089] The business acceptance module is used to automatically generate appropriate business process nodes based on the data of the instruction package that has passed the verification module, and interact with the account management.

[0090] The exception handling module is used to handle exceptions for instruction packets that fail the verification module.

[0091] In this embodiment, the verification rule base module is a pre-verification rule base module, specifically:

[0092] To address issues such as differing standard business designs, data dictionaries, and risk control problems among entrusted institutions, this invention innovatively places the verification rule base at the forefront. This proactively manages business risks through pre-event business rule setting, in-event processing and risk verification, and post-event business validation. Data cleaning is performed during the pre-event document verification stage to ensure the integrity of data entering the business process and reduce rework rates. The in-event data verification stage consists of three parts: First, control verification; if control verification fails, the application fails and the process is returned. Second, prompt verification; if the error in the prompt message is not corrected offline, the application re-enters the exception process after "Exception Handling - Acceptance"; if the error in the prompt message has been corrected offline, the application process continues after "Exception Handling - Acceptance". Third, prompt verification - Acceptable; regardless of whether the error in the prompt message has been corrected offline, the application process continues after "Exception Handling - Acceptance". Currently, the system has 419 mandatory verifications, 34 prompt verifications, and 48 prompt verifications - acceptable, totaling 501 rules. Verification rules can also be categorized into access verification and feedback verification. Access verification mainly includes file verification and data verification; feedback verification primarily verifies the required fields and data in files from other systems to confirm correct processing. This design registers risk points accumulated during accounting business processing, forming business rules. Risks are pre-registered, and then qualitative and quantitative analysis is used to determine risk response strategies and make corresponding adjustments to the system. When the system identifies business processing risks, it can mitigate these risks through anomaly handling functions, including alert messages, warning icons, anomaly handling, data auditing, and daily settlement statistics.

[0093] The acceptance platform in this embodiment also includes a visualization module, specifically:

[0094] The processing platform collects business data from the processing platform, analyzes task execution status, and displays a business volume chart on its homepage. Through data statistics, bar charts, pie charts, and other formats, the platform visually displays the current workload of each employee to the administrator. By comparing and analyzing the charts, administrators can allocate tasks from staff with heavy workloads to those with lighter workloads, balancing workloads and preventing unnecessary disruptions to operations, thus improving processing efficiency. Functions include staff substitution, workflow allocation, workflow initiation and termination, access control (substitution), and business volume statistics.

[0095] In this embodiment, the various modules in the acceptance platform employ Robotic Process Automation (RPA) technology for end-to-end business information flow management, specifically:

[0096] First, Shenzhen Stock Exchange Data Center verifies the data packets by checking the files and data. The verification results are then fed back to the acceptance platform. Data that passes the file and data verification enters the business acceptance stage, is sent to the corresponding system for business processing, and the data is monitored until the acceptance is completed. Under normal circumstances, the system processes the data automatically according to the process. When an anomaly occurs or the data requires manual review, the task is automatically pushed to the operations personnel for manual intervention.

[0097] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A control method for an automated enterprise annuity business processing platform, characterized in that, The method includes the following steps: Step S1: Based on the constructed unified rule database, configure the rule dataset of the entrusted end in a personalized way, and encapsulate it into a verification set according to the business type; Step S2: After receiving the instruction packet, the acceptance platform calls the encapsulated verification set to parse and verify the data in the instruction packet level by level; if the verification is successful, proceed to step S3 to accept the business according to the business type; otherwise, enter the exception handling process. Step S3: Automatically generate adapted business process nodes based on the parsed instruction package data, and interact with the accounting management system to process business; if an abnormality is detected by the accounting management system during the interaction process, the abnormality handling process will be initiated. The unified rule database in step S1 includes an interface rule database, a file verification rule database, and a data verification rule database. The data verification rules, through parameterized verification attributes and verification levels, are used to control the flow of abnormal information and divide the information levels when data verification fails.

2. The control method for an automated enterprise annuity business acceptance platform according to claim 1, characterized in that, The step S2, in which the acceptance platform receives the instruction packet, also includes a mechanism whereby an empty packet is sent by a third-party platform jointly accessed by the acceptance platform and the entrusted end at set intervals, and the acceptance platform provides corresponding feedback.

3. The control method for an automated enterprise annuity business acceptance platform according to claim 1, characterized in that, The step S2 of parsing and verifying the data in the instruction packet specifically involves: parsing the data packet and performing step-by-step verification on the data in the instruction packet in batches according to the predefined verification attributes and verification levels of the verification rules; the step-by-step verification is in the order of file verification and data verification.

4. The control method for an automated enterprise annuity business acceptance platform according to claim 1, characterized in that, The exception handling includes file verification exceptions, data verification exceptions, and account management feedback processing exceptions. The document verification is a strong control verification. When an anomaly occurs, the anomaly information is directly fed back to the entrusted end, and the instruction processing ends.

5. The control method for an automated enterprise annuity business acceptance platform according to claim 4, characterized in that, The data validation anomalies include control validation anomalies, prompt validation anomalies, and prompt-acceptable validation anomalies, and the specific handling procedures are as follows: Control verification anomaly handling: The anomaly information is directly fed back to the entrusted party, and the instruction acceptance ends; Prompt verification exception handling: Push the exception to the to-do workbench according to the permissions, and manually handle the exception. After the exception is handled, re-verify the rule until the verification passes; if the manual confirms that the exception cannot be handled, the exception can be fed back to the entrusted end, and the instruction processing ends. Prompt-based - Acceptable verification exception handling: Push the verification to the to-do workbench according to permissions. If the manual reviewer can ignore the exception and continue to configure and advance according to the preset process, or if the manual reviewer confirms that the exception cannot be ignored, the exception can be reported back to the entrusted end, and the instruction processing ends.

6. The control method for an automated enterprise annuity business acceptance platform according to claim 4, characterized in that, The specific handling process for the abnormal account management feedback is as follows: 1) If the acceptance option is "Accept", the sub-transaction will be resent for splitting; 2) If the acceptance option is "Abandon", the instruction will be abandoned, and the account management transaction will be rolled back offline. After the problem is resolved, the instruction package can be reprocessed through the abandon and resend function.

7. The control method for an automated enterprise annuity business acceptance platform according to claim 1, characterized in that, The interaction with the account management system in step S3 includes three interactions, specifically: First interaction: The platform sends a request to split the sub-transaction; The second interaction: The entrusted end creates a business transaction number and sends the business transaction number back to the acceptance platform, which then records the business transaction number; The third interaction: The entrusted end continues to process the sub-transaction. After processing, it sends the processing result back to the acceptor. If there is an error, the error information must be sent back at the same time. If the current node is the last sub-transaction node in the business processing stage, the account manager must send back the processing result of successful acceptance after successful processing, and at the same time organize the feedback document.

8. A platform for accepting enterprise annuity business, characterized in that, The platform comprising the method according to any one of claims 1 to 7, wherein the platform includes: The rules database module is used to verify the incoming standard data packets and provide a data interface; The verification module is used to perform batch and step-by-step file verification before business acceptance, data verification during business acceptance, and verification of accounting and management interaction results after business processing in the instruction package. The business acceptance module is used to automatically generate appropriate business process nodes based on the data of the instruction package that has passed the verification module, and interact with the account management. The exception handling module is used to handle exceptions for instruction packets that fail the verification module.

9. A corporate annuity business acceptance platform according to claim 8, characterized in that, The platform employs Robotic Process Automation (RPA) technology for full-chain business information flow between its various modules.

Images