A salary payment system and method based on data security management

Abstract

This invention discloses a payroll distribution system and method based on data security management, relating to the fields of enterprise payroll management and data security technology. It includes a data acquisition and encryption module that encrypts basic payroll data using AES-256 and transmits it via SSL / TLS, verifying data integrity; a payroll calculation module that decrypts the data and calculates according to preset logic, initiating triple verification; an access control module that assigns permissions based on four roles according to the RBAC model; a secure storage module that stores data with double encryption, requiring multi-factor authentication for access; a payroll execution module that supports three payroll channels and sends payroll notifications; an audit and traceability module that records operation logs using blockchain; and a central control module that coordinates the various modules, manages keys, and issues warnings. This invention ensures data security through multi-layer encryption and dynamic desensitization, improves efficiency through automated calculation, and ensures business continuity through disaster recovery backup. It is adaptable to enterprises of different sizes, improving the security and efficiency of payroll management.

Description

Technical Field

[0001] This invention relates to the field of enterprise payroll management and data security technology, and in particular to a payroll distribution system and method based on data security management. Background Technology

[0002] Current enterprise payroll systems suffer from multiple shortcomings in data security management, with the core issue being insufficient security protection during data collection and transmission. Most systems use only a single encryption algorithm to process basic payroll data, lacking a data integrity verification mechanism. During transmission from attendance systems and performance platforms to the payroll calculation module, data is vulnerable to tampering and loss due to network attacks or transmission interruptions, and such tampering is difficult to detect in a timely manner. For example, some small and medium-sized enterprises' payroll systems directly transmit unencrypted employee bank account information and payroll details via HTTP, posing a risk of data interception and leakage. Furthermore, the lack of abnormal transmission monitoring prevents the identification of high-frequency, unusual IP address data access requests, further amplifying data security risks.

[0003] Insufficient granularity in access control and sensitive data protection is another core deficiency in existing systems. Traditional payroll systems often employ a simple "account-password" authentication model, failing to clearly define access boundaries based on roles. In some scenarios, payroll clerks can overstep their authority to view complete payroll details for employees in other departments, and finance disbursement clerks can modify confirmed payroll calculations, posing a high risk of access abuse. Furthermore, the methods for desensitizing sensitive data are rigid, such as using fixed character replacement rules for employee ID numbers and bank account numbers, without dynamically adjusting the desensitization level based on the access role. Employees themselves still need to apply separately to access their personal information, impacting user experience. External auditors, however, may encounter insufficiently desensitized sensitive information, leading to uncontrolled data exposure. In addition, the lack of a full-process record of access changes makes it difficult to trace responsibility after access abuse occurs, further reducing system security and controllability.

[0004] Weak audit traceability and business continuity assurance capabilities constrain the reliability of existing systems. Most systems' operation logs only record basic operator and time information, lacking data access traces and operation result verification information. Furthermore, logs are stored on a single local server, making them susceptible to deletion and tampering, thus failing to establish an immutable audit trail. Regarding data storage and disaster recovery, some systems lack off-site backup mechanisms, relying solely on local hard drives for payroll data storage. In the event of hardware failures, natural disasters, or other emergencies, data loss cannot be quickly recovered, leading to interruptions in payroll processing. Even the few systems that do deploy backups suffer from excessively long backup cycles and lack of backup data integrity verification, compromising backup data availability and consequently affecting the timeliness of payroll payments, harming employee rights and the company's reputation. Summary of the Invention

[0005] This invention proposes a payroll system and method based on data security management to solve the problems mentioned in the prior art.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: a payroll system based on data security management, comprising the following modules:

[0007] The data acquisition and encryption module collects the basic data required for salary calculation. The original data is encrypted using the AES-256 encryption algorithm during the acquisition process. The encrypted data is then transmitted to subsequent modules via the SSL / TLS protocol. At the same time, the integrity of the collected data is verified by comparing hash values.

[0008] The payroll calculation module receives encrypted basic data, requests a decryption key from the central control module and completes the decryption, performs payroll calculation according to the preset payroll calculation logic, generates preliminary payroll details and then starts a triple verification mechanism. If the verification fails, it returns an error message and pauses the calculation process.

[0009] The access control module divides system users into four core roles: administrator, payroll clerk, financial disbursement clerk, and employee query clerk. Each role has exclusive operation permissions, and the permission allocation adopts a role-based access control model, which synchronously records permission change logs.

[0010] The secure storage module is used to store encrypted basic data, salary calculation results, permission configuration information and audit logs. The storage medium is an encrypted hard disk. Data is double-encrypted when stored. At the same time, access control policies are set so that only authorized roles can access the corresponding data after passing multi-factor authentication. Unauthorized access will trigger an alarm.

[0011] The payroll disbursement module is used to perform payroll disbursement operations. It supports three disbursement channels: bank transfer, e-wallet payment, and paper check. Before disbursement, the central control module verifies the financial disbursement staff's permissions. During the disbursement process, it sends a notification to employees containing the disbursement amount, disbursement time, and query link. After disbursement, it receives feedback results from the payment channels. The feedback results are encrypted and stored in the secure storage module.

[0012] The audit traceability module is used to record all operations within the system. The records are stored using blockchain technology and support querying logs by operator, operation time, and operation type. The query results are only visible to administrators and auditors, and the query process is recorded in the logs simultaneously.

[0013] The central control module receives status feedback from each module, issues early warnings for abnormal states, manages system keys, and maintains basic system parameters.

[0014] Furthermore, it also includes a data anonymization module. Sensitive data includes employee ID numbers, bank account numbers, and complete salary details that are not viewed by the individual. The anonymization rules cover partial character replacement, data format conversion, and dynamic anonymization. At the same time, the anonymization strategy is dynamically adjusted according to the type of sensitive data and the access scenario. When abnormal access frequency of sensitive data is detected, the anonymization level is dynamically increased to control the scope of sensitive data exposure.

[0015] Furthermore, it also includes an anomaly monitoring module, used to monitor data operation anomalies and salary payment anomalies within the system. During the anomaly monitoring process, the anomaly risk value is quantified using the formula R=α×D+β×T+γ×F, where R is the anomaly risk value, α is the weight of the data operation anomaly, D is the degree of the data operation anomaly, β is the weight of the salary payment anomaly, T is the degree of the salary payment anomaly, γ is the weight of the historical anomaly correlation, and F is the degree of the historical anomaly correlation. The anomaly level is determined by this quantification result, and corresponding handling measures are triggered according to the level.

[0016] Furthermore, the access control module also supports dynamic access control adjustment. When the system detects a change in user operation scenario, the administrator initiates a temporary access control adjustment request. After the request is submitted and approved by the auditors, it takes effect. The validity period of temporary access control is no more than 72 hours. After the validity period expires, the original access control will be automatically restored. The entire process of application, review, activation and expiration of temporary access control is recorded in the audit log. In addition, the access control module regularly performs compliance checks on all user access control. Non-compliant access control is automatically frozen and the administrator is notified.

[0017] Furthermore, the secure storage module adopts a dual-storage architecture of "local encrypted storage + off-site disaster recovery backup". Local storage is used for daily data access and uses a RAID5 disk array to achieve hardware-level data reliability. Off-site disaster recovery backup is deployed in a backup center. Backup data is synchronized with local storage data in real time. The synchronization process uses IPsec protocol for encrypted transmission. The off-site backup center uses the same access control policy as the local one. In addition, the secure storage module performs lifecycle management on stored data. The basic data retention period is 3 years, and the salary calculation results and payment records are retained for 10 years. Data exceeding the retention period is shredded and deleted after being reviewed by the administrator and supervised by the auditor. The deletion process is recorded in the audit log.

[0018] Furthermore, the payroll execution module also has a secondary verification function for payroll results. After the payroll is completed, the system automatically sends a confirmation notification containing a random verification code to the employee. The employee must enter the verification code through the system query interface to complete the payroll confirmation within 24 hours. For employees who fail to confirm on time, the system will send a reminder notification again after 12 hours. If the employee still fails to confirm after 48 hours, the payroll execution module will trigger an abnormal warning and suspend the employee's next payroll payment until confirmation is completed. In addition, the payroll execution module also supports a payroll cancellation function. If a payroll error is found and the payment channel supports cancellation, the finance payroll clerk will initiate a cancellation request. The cancellation operation will be executed within 2 hours after the payroll is completed. If it exceeds 2 hours, manual intervention is required. The cancellation process and results are recorded in the audit log.

[0019] Furthermore, the audit traceability module also has log analysis and risk warning functions. It performs multi-dimensional analysis on audit logs and generates audit reports based on the analysis results. The reports identify high-frequency operation roles, periods of concentrated abnormal operations, and high-risk operation types, providing data support for administrators to optimize permission configurations and adjust security policies. In addition, the audit logs adopt tamper-proof storage technology, so administrators and auditors can only view the logs and cannot modify or delete them.

[0020] Furthermore, this includes the following steps:

[0021] The data collection and encryption steps involve collecting employee attendance data, performance data, social security and housing provident fund payment standards, individual income tax deduction rules, and employee salary structure data. All collected raw data is encrypted using the AES-256 encryption algorithm, and the hash value of the raw data is calculated. The encrypted data and hash value are transmitted to the payroll calculation module via the SSL / TLS protocol. After receiving the data, the payroll calculation module verifies the hash value to complete the data integrity verification.

[0022] The salary calculation process involves the salary calculation module requesting a decryption key from the central control module, decrypting the received encrypted basic data, performing salary calculations according to the preset salary calculation logic, generating individual employee salary details, and initiating a triple verification mechanism: logical verification, historical data comparison verification, and cross-data verification. If the verification passes, the final salary details are generated; if the verification fails, an error message is returned to the central control module, and the calculation process is paused.

[0023] In the permission verification process, when a payroll clerk initiates a payroll details submission request, a finance disbursement clerk initiates a disbursement execution request, or an employee initiates a payroll query request, the permission management module receives the request and obtains the identity information of the requesting user. Based on the RBAC model, it verifies the permissions corresponding to the user role. If the verification passes, the operation is allowed to continue; if the verification fails, the operation is rejected and the abnormal access log is recorded to the audit traceability module.

[0024] In the secure storage process, the payroll calculation module transmits the final payroll details and encrypted basic data to the secure storage module. The secure storage module uses the SM4 algorithm to encrypt the data and the RSA-2048 algorithm to perform file-level encryption. The encrypted data is then stored in the local RAID5 disk array and synchronized to the off-site disaster recovery backup center. After storage is completed, a storage record is generated and sent to the central control module and the audit traceability module.

[0025] In the payroll execution process, after the financial payroll clerk passes the authorization verification, they select the payroll channel through the payroll execution module and enter the account information required for payroll. The payroll execution module calls the final payroll details in the secure storage module and compares the payroll account with the employee's account. If the consistency is successful, a payroll request is initiated to the corresponding payment channel. The payroll execution module encrypts and stores the result in the secure storage module and sends a notification with a query link to the employee. After receiving the notification, the employee completes the payroll confirmation through the system.

[0026] The audit logging process involves the audit traceability module receiving operational data from each module in real time, organizing the data into audit log entries, generating a unique hash value for each log entry and linking it to the blockchain distributed ledger, and storing the audit logs in a designated area of ​​the secure storage module for administrators and auditors to query.

[0027] Furthermore, it also includes a dynamic permission adjustment step. When the system detects a change in the user's operation scenario, the user initiates a temporary permission adjustment request. If approved, the administrator configures the temporary permissions. The priority of the temporary permissions is determined by the formula P=λ×S+μ×I+ν×U, where P is the temporary permission priority, λ is the business urgency weight, S is the business urgency, μ is the data sensitivity weight, I is the data sensitivity level, ν is the historical permission record weight, and U is the historical permission compliance record. After the temporary permission configuration is completed according to the priority, the permission management module records the configuration process to the audit log. The temporary permission expires automatically and the original permission is restored after the expiration of the validity period. The expiration process is also recorded in the log.

[0028] Furthermore, it includes data disaster recovery backup and recovery steps. In this step, the secure storage module performs local full backup and off-site incremental backup according to a preset cycle. The local backup is stored with ZIP compression and SM4 encryption, and its integrity is verified by hash value comparison. The off-site backup only synchronizes newly added or modified data, which is transmitted with IPsec encryption. After hash verification at the off-site backup center, the version is updated or resynchronized. When local data is damaged / lost, the administrator initiates a recovery request after multi-factor authentication by the auditor. Data is extracted from the local full backup first. If the local backup is unavailable, off-site data is retrieved. After decryption, its integrity and accuracy are verified by comparison with historical logs. The recovery result is recorded in the audit traceability module and the administrator is notified. The secure storage module conducts disaster recovery drills every quarter to simulate the scenario of complete loss of local data, records indicators and generates reports.

[0029] Compared with existing technologies, the beneficial effects of this invention are:

[0030] In the data acquisition and transmission stages, the AES-256 encryption algorithm combined with hash value comparison is used to achieve dual verification of raw data encryption and integrity. Coupled with SSL / TLS protocol transmission, this effectively blocks data tampering and intercepts risks. The data anonymization module supports dynamic anonymization strategies based on access roles, ensuring that employees can view their complete personal information while restricting other roles' access to sensitive data, balancing data security and ease of use. Simultaneously, the anomaly monitoring module can identify unauthorized access, high-frequency queries, and other risky behaviors in real time, triggering corresponding handling measures through risk quantification and grading to proactively prevent data security threats.

[0031] The refined design of the access control system significantly enhances the rigor and traceability of system access control. Based on the RBAC model, four core roles are defined and access boundaries are clearly defined to prevent unauthorized operations. The dynamic access control function supports the entire process of temporary access application, review, activation, and expiration, and combined with regular access control compliance checks, it not only meets the needs of temporary access control for cross-departmental collaboration, but also prevents long-term abuse of access control. Access control changes can be traced back to the specific operator and time of operation, and the responsible party can be quickly identified in case of problems.

[0032] Audit traceability and disaster recovery backup design enhance system reliability and business continuity. The audit traceability module uses blockchain technology to store operation logs, recording comprehensive information including operator, operation trajectory, and result verification. The logs are tamper-proof and support multi-dimensional queries, forming a complete audit chain and providing reliable evidence for security audits and problem tracing. The secure storage module's "local encrypted storage + off-site disaster recovery backup" architecture, combined with real-time synchronization and regular backup strategies, ensures data is not lost in scenarios such as hardware failures and natural disasters. The data recovery process includes integrity and availability verification, ensuring that recovered data can be directly used for payroll calculation and disbursement, avoiding payroll interruptions due to data loss and maintaining the timeliness of payroll disbursements and protecting employee rights. Simultaneously, functions such as secondary verification of disbursement results and disbursement revocation review improve the accuracy of payroll disbursements, reduce disputes caused by disbursement errors, and enhance employee trust in the company's payroll management. Attached Figure Description

[0033] Figure 1 This is a schematic block diagram of the payroll system based on data security management proposed in this invention;

[0034] Figure 2 This is a schematic block diagram of the payroll distribution method based on data security management proposed in this invention;

[0035] Figure 3A line graph comparing the time taken to calculate salaries for different employee sizes;

[0036] Figure 4 A bar chart comparing the approval cycles for different permission operation types;

[0037] Figure 5 Line chart comparing response times for different anomaly types. Detailed Implementation

[0038] 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 embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0039] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," and "counterclockwise," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention.

[0040] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified. Furthermore, the terms "installed," "connected," and "linked" should be interpreted broadly; for example, they may refer to a fixed connection, a detachable connection, or an integral connection; they may refer to a mechanical connection or an electrical connection; they may refer to a direct connection or an indirect connection through an intermediate medium; and they may refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances. The invention will now be described in further detail with reference to the accompanying drawings.

[0041] Reference Figures 1 to 5 A payroll system based on data security management, comprising the following modules:

[0042] The data acquisition and encryption module is used to collect the basic data required for salary calculation. The basic data includes employee attendance data, performance data, social security and housing provident fund payment standards, individual income tax deduction rules and salary structure data. The original data is encrypted using the AES-256 encryption algorithm during the acquisition process. The encrypted data is transmitted to subsequent modules through the SSL / TLS protocol. At the same time, the integrity of the collected data is verified by hash value comparison to ensure that the data is not tampered with during the data transmission process.

[0043] The payroll calculation module connects to the data acquisition and encryption module. After receiving encrypted basic data, it requests a decryption key from the central control module and completes the decryption. It then performs payroll calculations according to the preset payroll calculation logic, which includes basic salary calculation, performance bonus calculation, social security and housing fund deduction, individual income tax calculation, and other allowance and subsidy addition and subtraction rules. After generating preliminary payroll details, it initiates a triple verification mechanism, namely logical verification, historical data comparison verification, and cross-data verification. If the verification fails, it returns an error message and pauses the calculation process.

[0044] The access control module is used to allocate system operation permissions, dividing system users into four core roles: administrator, payroll clerk, financial disbursement clerk, and employee query clerk. Each role has exclusive operation permissions. Administrators have full module operation permissions, payroll clerks only have data viewing and payroll calculation permissions, financial disbursement clerks only have disbursement execution and disbursement result viewing permissions, and employee query clerks only have personal payroll details query permissions. Permission allocation adopts a role-based access control (RBAC) model and records permission change logs synchronously.

[0045] The secure storage module, connected to the payroll calculation module and the access control module, is used to store encrypted basic data, payroll calculation results, access configuration information, and audit logs. The storage medium is an encrypted hard drive, and double encryption is performed when storing data. The storage encryption algorithm is SM4, and the file-level encryption is RSA-2048. Access control policies are also set, allowing only authorized roles to access the corresponding data after passing multi-factor authentication (including at least two of the following: password, dynamic token, and biometrics). Unauthorized access triggers an alarm.

[0046] The payroll execution module, connected to the payroll calculation module and the secure storage module, is used to perform payroll payroll operations. It supports three payroll channels: bank transfer, e-wallet payment, and paper check. Before payroll payroll payroll payroll payroll payroll payroll payroll clerks’ permissions are verified by the central control module. During payroll ...

[0047] The audit traceability module connects to all modules in the system and is used to record all operations within the system. The operation log includes the operator, operation time, operation module, operation content, operation result, and data access trajectory. The records are stored using blockchain technology and support querying logs by operator, operation time, and operation type. The query results can only be viewed by administrators and auditors, and the query process is recorded synchronously in the log.

[0048] The central control module, as the core coordination unit of the system, connects with the data acquisition and encryption module, salary calculation module, access control module, secure storage module, payment execution module, and audit traceability module. It coordinates the data interaction and function execution of each module, receives status feedback from each module, including data processing progress, abnormal information, and operation results, and issues early warnings for abnormal states through system pop-ups and administrator SMS notifications. It also manages system keys, which are rotated periodically with a configurable rotation cycle, and maintains basic system parameters, including updating salary calculation rules, adjusting access control templates, and configuring storage strategies.

[0049] This invention also includes a data anonymization module, which is connected to the data acquisition and encryption module and the secure storage module. This module is used to perform anonymization processing on sensitive data stored and transmitted within the system. The sensitive data specifically includes employee ID numbers, bank account numbers, and complete salary details that are not viewed by the employee themselves. The anonymization rules specifically include partial character replacement, data format conversion, and dynamic anonymization. Dynamic anonymization adjusts the anonymization level according to the access role. When the employee views the data, the complete data is displayed, while when other authorized roles view the data, the anonymized data is displayed. At the same time, the anonymization strategy can be dynamically adjusted according to the type of sensitive data and the access scenario. When abnormal access frequency of sensitive data is detected, the anonymization level is dynamically increased to control the scope of sensitive data exposure.

[0050] This invention also includes an anomaly monitoring module, which is connected to the central control module and the audit traceability module. It is used to monitor data operation anomalies and salary payment anomalies within the system. Data operation anomalies specifically include unauthorized access attempts, high-frequency data queries, abnormal IP address logins, and abnormal permission changes. Salary payment anomalies specifically include discrepancies between the payment amount and the calculation result, mismatch between the payment account and the employee account, and excessively high frequency of payment channel failures. During anomaly monitoring, the anomaly risk value is quantified using the formula R=α×D+β×T+γ×F, where R is the anomaly risk value, ranging from 0 to 100. R≥80 is considered high risk, 60≤R<80 is considered medium risk, and R<60 is considered low risk; α is the weight of data operation anomalies, ranging from 0.3 to 0.5; D is the degree of data operation anomalies, ranging from 0 to 100, quantified based on the number of anomalies and the scope of impact; β is the weight of salary payment anomalies, ranging from 0.3 to 0.5; T is the degree of salary payment anomalies, ranging from 0 to 100, quantified based on the amount of deviation and the frequency of failures; γ is the weight of historical anomaly correlation, ranging from 0.1 to 0.2; and F is the correlation degree of historical anomalies, ranging from 0 to 100, quantified based on the similarity between the current anomaly and historical high-risk anomalies. The quantitative results are used to accurately determine the level of anomalies and trigger corresponding handling measures based on the level. High-risk operations are immediately suspended and the administrator is notified; medium-risk operations are restricted and an alert is issued; and low-risk operations are logged and continuously monitored.

[0051] In this invention, the permission management module also supports dynamic permission adjustment. When the system detects a change in the user's operation scenario, the administrator can initiate a temporary permission adjustment application. The application must include the reason for the adjustment, the scope of the adjusted permission, and the validity period. The application will only take effect after being reviewed and approved by the auditors. The validity period of the temporary permission shall not exceed 72 hours. After the validity period expires, the original permission will be automatically restored. The entire process of application, review, activation, and expiration of temporary permissions is recorded in the audit log, enabling traceability of permission changes. In addition, the permission management module regularly performs compliance checks on all user permissions. The checks include the matching of permissions with roles, whether there are long-term unused permissions, and whether there are permissions beyond the scope. The check results generate a compliance report, and non-compliant permissions are automatically frozen and the administrator is notified.

[0052] In this invention, the secure storage module adopts a dual storage architecture of "local encrypted storage + off-site disaster recovery backup". The local storage is used for daily data access and uses a RAID5 disk array to achieve hardware-level data reliability. The off-site disaster recovery backup is deployed in a backup center at least 50 kilometers away from the local storage. The backup data is synchronized with the local storage data in real time (synchronization delay does not exceed 10 seconds). The synchronization process uses IPsec protocol for encrypted transmission. The off-site backup center adopts the same access control policy as the local one to ensure that the backup data is not leaked. In addition, the secure storage module performs lifecycle management on the stored data. The retention period for basic data (attendance, performance, etc.) is 3 years, and the retention period for salary calculation results and payment records is 10 years. Data exceeding the retention period is shredded and deleted after being reviewed by the administrator and supervised by the auditor. The deletion process is recorded in the audit log.

[0053] In this invention, the payroll execution module also has a secondary verification function for the payroll result. After the payroll is completed and the payment channel reports a successful payment, the system automatically sends a confirmation notification containing a random verification code to the employee. The employee must enter the verification code through the system query interface within 24 hours to complete the payroll confirmation. For employees who fail to confirm on time, the system will send a reminder notification again after 12 hours. If the employee still fails to confirm after 48 hours, the payroll execution module will trigger an abnormal warning and suspend the employee's next payroll payment until confirmation is completed. In addition, the payroll execution module also supports a payroll cancellation function. If a payroll error is found and the payment channel supports cancellation, the finance payroll clerk can initiate a cancellation application. The application must be approved by the administrator. The cancellation operation can be executed within 2 hours after the payroll is completed. If it exceeds 2 hours, manual intervention is required. The cancellation process and result are recorded in the audit log.

[0054] In this invention, the audit traceability module also features log analysis and risk warning functions. It can perform multi-dimensional analysis on audit logs, specifically including operation frequency analysis, permission usage analysis, and abnormal operation trend analysis. The analysis cycle is configurable, defaulting to once per day. The analysis results generate an audit report, which identifies high-frequency operation roles, peak periods of abnormal operations, and high-risk operation types, providing data support for administrators to optimize permission configurations and adjust security policies. Furthermore, the audit logs employ immutable storage technology, specifically a blockchain-based distributed ledger. Each log entry generates a unique hash value and links to the previous entry; modifying any entry will break the hash chain. Administrators and auditors can only view the logs, not modify or delete them. Log queries require multi-factor authentication, and query records are also stored as part of the audit logs, ensuring traceability of the audit process.

[0055] This invention includes the following steps:

[0056] The data collection and encryption module obtains employee attendance data, performance data, social security and housing provident fund payment standards, and individual income tax deduction rules from the enterprise attendance system, performance evaluation system, social security and housing provident fund management platform, and individual income tax declaration system. At the same time, it obtains employee salary structure data from the human resources system. All collected raw data is encrypted using the AES-256 encryption algorithm, and the hash value of the raw data is calculated. The encrypted data and hash value are transmitted to the payroll calculation module via SSL / TLS protocol. After receiving the data, the payroll calculation module verifies the hash value and completes the data integrity verification.

[0057] The salary calculation process involves the salary calculation module requesting a decryption key from the central control module, decrypting the received encrypted basic data, and performing salary calculations according to the preset salary calculation logic (basic salary = position salary + job grade salary, performance bonus = performance coefficient × performance base, social security and housing fund deductions = contribution base × contribution rate, individual income tax = (gross salary - tax threshold - special additional deductions) × tax rate - quick calculation deduction, net salary = gross salary - social security and housing fund deductions - individual income tax - other deductions). This generates individual salary details for each employee and initiates a triple verification mechanism: logic verification: checks the accuracy of the calculation formula parameters; historical data comparison verification: compares the deviation between the current salary and the previous month's salary to see if it is within a preset threshold; cross-data verification: checks the consistency between the social security and housing fund deduction amount and the data on the social security platform. If the verification passes, the final salary details are generated; if the verification fails, an error message is returned to the central control module, and the calculation process is paused.

[0058] In the permission verification process, when a payroll clerk initiates a payroll details submission request, a finance disbursement clerk initiates a disbursement execution request, or an employee initiates a payroll inquiry request, the permission management module receives the request and obtains the identity information of the requesting user. Based on the RBAC model, it verifies the permissions corresponding to the user role. The verification content includes whether the user has the permission to perform the operation and whether the scope of the operation is within the authorized range. If the verification passes, the user is allowed to continue the operation. If the verification fails, the user is denied the operation and an abnormal access log is recorded in the audit traceability module.

[0059] In the secure storage process, the payroll calculation module transmits the final payroll details and encrypted basic data to the secure storage module. The secure storage module uses the SM4 algorithm to perform storage encryption on the data and the RSA-2048 algorithm to perform file-level encryption. The encrypted data is then stored in the local RAID5 disk array. At the same time, the data is synchronized to the off-site disaster recovery backup center via the IPsec protocol. After storage is completed, a storage record is generated, which includes the storage time, storage location, and access permissions. The storage record is then sent to the central control module and the audit and traceability module.

[0060] The payroll disbursement process involves the following steps: After the financial disbursement clerk's permissions are verified, they select the payroll disbursement channel through the disbursement execution module and enter the required account information. The disbursement execution module then retrieves the final payroll details from the secure storage module and compares the disbursement account with the employee's account. If the consistency is verified, a disbursement request is initiated to the corresponding payment channel. After the payment channel reports the disbursement result, the disbursement execution module encrypts and stores the result in the secure storage module. Simultaneously, it sends a notification to the employee containing the disbursement amount, disbursement time, and query link. The notification method is preset by the employee, and after receiving the notification, the employee completes the disbursement confirmation through the system.

[0061] The audit log process involves the audit traceability module receiving operational data from each module in real time. This data includes the data source for data collection, the encryption process, parameter calls and results for salary calculation, permission verification requests and results, secure storage operations and synchronization, and channel selection and results for payout execution. The operational data is then organized into audit log entries, which include the operator, operation time, operation module, operation content, operation result, IP address, and authentication method. A unique hash value is generated for each log entry and linked to the blockchain distributed ledger. Simultaneously, the audit logs are stored in a designated area of ​​the secure storage module for administrators and auditors to query.

[0062] This invention also includes a dynamic permission adjustment step. When the system detects a change in the user's operation scenario, the user initiates a temporary permission adjustment request. The request content specifically includes the requesting role, the type of permission to be adjusted, the scope of adjustment, the reason for adjustment, and the validity period of adjustment. After the request is submitted, the permission management module sends the request to the auditor for review. The auditor reviews the rationality of the request, specifically including whether there is indeed a need for cross-departmental collaboration and whether the scope of adjustment is necessary. If the review is approved, the administrator configures the temporary permissions. Temporary permissions are prioritized using the formula P = λ × S + μ × I + ν × U, where P is the temporary permission priority (range 0-10, higher P indicates higher priority); λ is the business urgency weight (range 0.4-0.6); S is the business urgency (range 0-10, quantified based on project deadlines and collaboration needs); μ is the data sensitivity weight (range 0.2-0.3); I is the data sensitivity (range 0-10, with cross-departmental salary data sensitivity at 8-10 and single-department non-core data at 3-7); ν is the historical permission record weight (range 0.1-0.2); and U is the historical permission compliance record weight (range 0-10, with unauthorized abuse records at 10, minor violations at 5-9, and serious violations at 0-4). After configuring temporary permissions according to priority, the permission management module records the configuration process in the audit log. Temporary permissions automatically expire and the original permissions are restored after the expiration period, with the expiration process also recorded in the log.

[0063] This invention also includes a data disaster recovery backup and restoration step. In this step, the secure storage module triggers a full local data backup and an incremental off-site data backup according to a preset period (the period is configurable, defaulting to 2-4 AM daily to avoid peak business hours). The full local backup uses ZIP compression and SM4 encryption algorithms for compressed and encrypted storage. After the backup is completed, the hash value of the backup file is calculated and compared with the hash value of the original data to complete the integrity verification of the backup data. The incremental off-site backup only synchronizes the data added or modified in the local storage. The synchronization process uses IPsec protocol for encrypted transmission to ensure the security of data during off-site transmission. After synchronization is completed, the off-site backup center performs hash value verification on the incremental data. If the verification passes, the backup data version in the off-site storage is updated; if the verification fails, a new synchronization request is initiated. When data is corrupted or lost in the local storage, the administrator initiates a data recovery request through the central control module. The request requires multi-factor authentication and confirmation by auditors. After confirmation, the secure storage module prioritizes extracting the corresponding data from the local full backup. If the local backup is unavailable, the data is retrieved from the off-site disaster recovery backup center. During the recovery process, the backup data is decrypted using the same decryption algorithm (SM4, RSA-2048) as when it was stored. After the recovery is completed, the recovered data is compared with the data records in the historical operation log to verify the data integrity and accuracy. The recovery result is synchronously recorded to the audit traceability module, and a recovery completion notification is sent to the administrator. In addition, the secure storage module performs a disaster recovery drill every quarter to simulate a scenario of complete loss of local data. The full data is recovered from the off-site backup center, and drill indicators such as recovery time and data integrity compliance rate are recorded. A disaster recovery drill report is generated, which analyzes the problems in the drill process and proposes optimization solutions to ensure the effectiveness of the disaster recovery backup mechanism and guarantee the recoverability of system data under extreme conditions.

[0064] The following two examples further illustrate specific embodiments of the present invention:

[0065] Example 1: Application of a Payroll System in a Large Manufacturing Enterprise

[0066] This embodiment is applied to a large manufacturing enterprise with 5,000 employees, including 12 production workshops and 8 functional departments. It needs to handle the differentiated salary structure of multiple departments (piece-rate wages for production positions, fixed salaries for functional positions, and project bonuses for technical positions). The system module deployment and operation details are as follows.

[0067] I. System Module Deployment and Parameter Configuration

[0068] Data Acquisition and Encryption Module: This module integrates with the enterprise's fingerprint attendance system, performance evaluation system, social security and housing provident fund management platform, individual income tax declaration system, and human resources system. It collects 120,000 attendance records daily, calculates output and pass rates by work group, updates contribution bases monthly, synchronizes special additional deduction information, and stores data on position wages, job level wages, and seniority subsidies. The original data is encrypted using the AES-256 encryption algorithm, with SHA-256 hash calculation. Encrypted data is transmitted via SSL / TLS 1.3 protocol, with transmission latency controlled within 500ms.

[0069] The salary calculation module includes three pre-defined salary calculation logics: Production staff net pay = (piece rate × output × pass rate) + seniority allowance - (social security base × 16% + housing provident fund base × 12%) - individual income tax - food and accommodation deductions; Functional staff net pay = (position salary + job grade salary) × attendance coefficient + performance bonus - (social security + housing provident fund) - individual income tax; Technical staff net pay = fixed salary + project bonus × contribution coefficient - (social security + housing provident fund) - individual income tax. The triple verification mechanism includes: logic verification checking the accuracy of parameter calls, such as whether output data is associated with the corresponding workshop; a historical data comparison threshold set at ±15%; and cross-verification connecting to the social security platform API to verify deducted amounts in real time.

[0070] The access control module is divided into four roles: 10 administrators (headquarters HR director and IT manager), 20 payroll clerks (assigned by department, each responsible for 1-2 departments), 5 finance disbursement clerks (divided into bank liaison groups), and 5000 employee query clerks (all employee accounts). In the RBAC access template, payroll clerks can only view attendance and performance data for their assigned departments and cannot modify individual income tax rules; finance disbursement clerks can only initiate transfers and cannot view payroll calculation details. The key rotation cycle is set to the 1st of each month and is automatically triggered by the central control module.

[0071] Secure storage module: The local system uses a 6-bay RAID5 disk array with a total storage capacity of 20TB. The SM4 storage encryption key is 128 bits long, and the RSA-2048 file-level encryption key is jointly kept by the administrator and the auditor. The off-site disaster recovery backup center is deployed in a city disaster recovery data center 60 kilometers away from the factory area. The synchronization delay is set to 8 seconds, and the backup cycle is a full backup at 3:00 AM every day + an incremental backup every 2 hours.

[0072] Anomaly monitoring module: Deploy 10 anomaly detection nodes, with a monitoring frequency of once per second, an unauthorized access attempt threshold of 5 times / minute, anomaly IP judgment criteria of non-enterprise intranet IP (enterprise intranet segment 192.168.0.0 / 16), a disbursement amount deviation threshold of ±500 yuan, and a disbursement failure frequency threshold of 3 times / employee.

[0073] The disbursement execution module integrates with the APIs of six major banks (supporting batch transfers), WeChat Work e-wallet (for small subsidy disbursements), and a check printing system (for paper disbursements to retired employees). Disbursement notifications are primarily sent via WeChat Work, achieving a 98% reach rate; unread SMS messages are resent after two hours. The disbursement confirmation verification code is valid for 24 hours; failure to confirm within this timeframe triggers a financial review.

[0074] Audit traceability module: Adopting a consortium blockchain architecture, the three accounting nodes are deployed in the HR, finance and IT departments respectively. The log entries include the operator's account, MAC address, operation duration, and comparison values ​​before and after data modification. The query supports filtering by combination of "department + month + operation type". The log retention period is 10 years.

[0075] Central control module: adopts industrial-grade PLC, supports 500 data interfaces, and a 15-inch touch screen displays real-time data processing progress, such as "Attendance data encryption completed 98%". Anomaly warnings are pushed through the administrator's WeChat robot and trigger system pop-ups. Key storage uses a hardware encryption machine (to prevent physical tampering).

[0076] II. Control Flow and Formula Application

[0077] Data collection and encryption steps: At 18:00 on the 25th of each month, the module automatically pulls data from various data sources. After deduplication of attendance data (removing duplicate clock-ins), it is encrypted and a hash value is generated. For example, the hash value of attendance data is "a3f2d4e5...". This hash value is transmitted to the payroll calculation module along with the encrypted data. The latter receives the data after verifying that the hash value is consistent.

[0078] Salary calculation steps: At 9:00 AM on the 26th, the salary calculation module requests a decryption key from the central control module (the key is dynamically generated through a hardware encryption machine). After decryption, the corresponding calculation logic is called according to the department to generate preliminary details. For example, if employee Zhang San in production workshop A has a piece-rate wage of 8,500 yuan and a seniority allowance of 300 yuan, a triple check is initiated. The logic check finds that "the project bonus of technical staff Li Si is not associated with the project number" and returns an error message. After the accountant supplements the project information, the calculation is recalculated, and the check passes to generate the final details.

[0079] Access Control Verification and Dynamic Adjustment Steps: At 10:00 AM on the 27th, the payroll clerk of Workshop B requested to view the performance data of Workshop C (due to the need to verify output during collaborative production). A temporary access request was initiated, citing "cross-workshop collaborative output verification" as the reason, valid for 24 hours. After the auditor approved the request, the administrator configured the access using the abnormal risk value formula R=α×D+β×T+γ×F, taking α=0.4 (data operation abnormality weight), D=60 (the clerk has had no abnormal operations in the past 30 days, abnormality level 60); β=0.4 (payroll payment abnormality weight), T=50 (Workshop C has no abnormal payments this month, abnormality level 50); γ=0.2 (historical association weight), F=70 (no historical high-risk associations, association degree 70). The calculated R=0.4×60+0.4×50+0.2×70=24+20+14=58 (low risk). Temporary viewing access was granted, and the access was recorded in the audit log after it took effect.

[0080] Distribution Execution and Audit Steps: At 3 PM on the 28th, the finance distribution clerk selected the bank transfer channel and entered 1200 employee bank account numbers. After the module verified that the accounts matched the employee information database, a batch transfer request was initiated. 30 minutes later, feedback was received from the bank (1198 successful transfers, 2 failed transfers). The reason for the failures was "account frozen," triggering an anomaly warning in the system. Finance personnel contacted the employees to update their accounts and then reissued the funds. Simultaneously, a WeChat notification was sent to the employees, who clicked the link, entered the verification code, and completed the confirmation. The confirmation record was encrypted and stored in a secure storage module. The audit traceability module recorded the entire process in real time: "Distributor Wang Wu initiates transfer - 1198 successful transfers - 2 failed transfers - reissue," generating blockchain log entries.

[0081] III. Data Representation and Interpretation

[0082] Table 1. Comparison of key indicators between the traditional salary system and this system in large manufacturing enterprises.

[0083] Comparison indicators Traditional system This invention system Data breach incidence 1.2 times / year 0 times / year Number of complaints about abuse of power 8 times / year 0 times / year Salary calculation error rate 2.5% 0.1% Exception handling response time 4 hours 15 minutes Data recovery success rate 75% 100%

[0084] Table 1 shows that traditional systems, due to their simplistic encryption mechanisms and loose access control, experience an average of 1.2 data breaches and 8 complaints of access abuse annually. Salary calculations rely on manual verification, resulting in a 2.5% error rate. Anomaly handling takes 4 hours (manual log review), and the lack of off-site backups for local storage leads to a data recovery success rate of only 75%. This system, through AES-256 encryption, RBAC access control model, and blockchain auditing, achieves zero data breaches and zero access abuse. Triple verification reduces the calculation error rate to 0.1%. The anomaly monitoring module locates and resolves issues within 15 minutes. Dual storage (local + off-site) ensures a 100% data recovery success rate, fully meeting the secure salary management needs of large manufacturing enterprises with multiple departments and high data volumes.

[0085] Example 2: Application of a Payroll System in a Small and Medium-Sized Internet Company

[0086] This embodiment is applied to a small to medium-sized internet company (including three core departments: product, R&D, and operations) with 300 employees and a project-based system. It needs to support remote work permission application and real-time calculation of project bonuses. The system modules are adapted to be lightweight as follows.

[0087] I. System Module Deployment and Parameter Configuration

[0088] Data Acquisition and Encryption Module: Integrates with WeChat Work remote attendance system, Jira project management system, third-party social security payment platform, individual income tax app, and Lark HR system. It collects 300 daily attendance records, calculates R&D staff task completion rates, pushes monthly payment details, synchronizes employee special additional deductions, and stores basic salary and job-level subsidies. Data is encrypted with AES-256 and transmitted via SSL / TLS 1.3 protocol, with transmission latency controlled within 300ms. Hash value verification uses SHA-256.

[0089] Salary calculation module: Two pre-defined calculation logics are used: For R&D positions, net salary = base salary + (task completion rate × project bonus base) - (social security + housing fund) - individual income tax; For operations positions, net salary = base salary + (KPI score × performance coefficient) - (social security + housing fund) - individual income tax. In the triple verification process, the historical data comparison threshold is set at ±20%, and cross-validation is performed using JiraAPI to verify task completion rates.

[0090] The access control module is divided into four roles: 3 administrators (CEO, HR manager, and IT specialist), 2 payroll clerks (responsible for company-wide payroll), 1 finance disbursement clerk, and 300 employee query clerks. In the RBAC template, payroll clerks can view company-wide data but cannot modify project bonus bases, while finance disbursement clerks can only operate e-wallets and bank transfers. The key rotation cycle is set to once every two weeks, manually triggered by the central control module.

[0091] Secure storage module: The local storage uses a 4-bay RAID5 disk array with a total storage capacity of 5TB. The SM4 encryption key is 128 bits, and the RSA-2048 key is jointly kept by the HR manager and the finance manager. The off-site disaster recovery backup center is deployed on a cloud server 30 kilometers away from the company, with a synchronization delay of 10 seconds. The backup cycle is a full backup at 2:00 AM every day plus an incremental backup every 4 hours.

[0092] Anomaly monitoring module: Deploy 3 anomaly detection nodes, monitor once per second, unauthorized access threshold 3 times / minute, abnormal IP is non-company VPN sIP (VPN segment 10.0.0.0 / 8), disbursement amount deviation threshold ±200 yuan, failure frequency threshold 2 times / employee.

[0093] The disbursement execution module integrates with two bank APIs (supporting small-amount batch transfers) and WeChat Work e-wallet (the primary disbursement channel, with 100% reach). Disbursement notifications prioritize WeChat Work, and unread emails are resent within one hour. Verification codes are valid for 12 hours; exceeding this time triggers HR review.

[0094] Audit traceability module: It adopts a lightweight consortium blockchain, with two accounting nodes deployed in the HR and finance departments respectively. The logs include the operator's account, login device model, and operation content summary. The query supports filtering by "project + employee". The log retention period is 5 years.

[0095] Central control module: Uses commercial PLC, supports 100 data interfaces, 10-inch touch screen displays real-time progress, anomaly warnings are pushed to the administrator via WeChat and SMS, and key storage uses software encrypted container (bound to the company's intranet IP).

[0096] II. Control Flow and Formula Application

[0097] Data collection and encryption steps: At 12:00 on the 20th of each month, the module automatically pulls data (Jira task data is grouped by project), encrypts it to generate a hash value, and transmits it to the salary calculation module, which receives the data after verifying that the hash is consistent.

[0098] Salary calculation steps: At 10:00 on the 21st, the module applies for a decryption key. After decryption, the logic is called according to the job position. For example, if Li Si, a research and development position, has a task completion rate of 95% and a project bonus base of 8,000 yuan, the bonus is calculated to be 7,600 yuan. The triple verification finds that "Wang Wu, an operations position, has not had his KPI score reviewed" and returns an exception. After the operations supervisor reviews it, the calculation is recalculated and the final details are generated.

[0099] Dynamic permission adjustment steps: At 9:00 AM on the 22nd, R&D staff member Zhao Liu requested to view the product department's project bonus data (valid for 12 hours) due to cross-project collaboration. After the request was submitted, the auditor approved it. When configuring permissions, the administrator used the temporary permission priority formula P=λ×S+μ×I+ν×U, taking λ=0.5 (business urgency weight), S=8 (3 days until project launch, urgency 8); μ=0.3 (data sensitivity weight), I=9 (product department bonus data sensitivity 9); ν=0.2 (historical record weight), U=10 (Zhao Liu has no permission violation record, compliance record 10), and calculated P=0.5×8+0.3×9+0.2×10=4+2.7+2=8.7 (high priority). The permission configuration was completed within 10 minutes and recorded in the audit log.

[0100] Payroll Disbursement and Disaster Recovery Procedures: At 2 PM on the 23rd, the finance payroll clerk disbursed salaries via WeChat e-wallet. 298 transactions were successful, and 2 failed (reason: "account not bound"). After a system alert, HR contacted employees to bind their accounts and re-disburse salaries. Simultaneously, an off-site backup was triggered, and the cloud server synchronized the latest disbursement records. At 10 AM the following day, a local storage hard drive failed. The central control module automatically restored data from the off-site backup. After restoration, the consistency between salary details and disbursement records was verified, and the system returned to normal operation within 15 minutes.

[0101] III. Data Representation and Interpretation

[0102] Table 2 Comparison of key indicators between traditional payroll systems and this system in small and medium-sized internet companies.

[0103] Comparison indicators Traditional system This invention system Salary calculation time 8 hours 1.5 hours Remote access request cycle 24 hours 30 minutes Notification reach rate 85% 100% Data backup time 2 hours 10 minutes Employee satisfaction survey 65% 98%

[0104] Table 2 shows that the traditional system relies on manual data entry and Excel calculations, taking 8 hours to calculate salaries; remote access requests require cross-departmental signatures, taking 24 hours; notifications are sent via SMS, with a reach rate of only 85%; data backups are performed manually, taking 2 hours; and employees need to contact HR to inquire about their salaries, resulting in a satisfaction rate of only 65%. This system reduces the processing time to 1.5 hours through automated calculations; dynamic permissions are configured within 30 minutes; enterprise WeChat notifications achieve 100% reach; automatic backups are completed in 10 minutes; and employees can self-service query details, increasing satisfaction to 98%. It is well-suited to the "lightweight, efficient, and remote collaboration" business characteristics of small and medium-sized internet companies, improving salary management efficiency while ensuring data security.

[0105] Reference Figure 3 This line graph visually illustrates the impact of employee growth on payroll calculation efficiency. Traditional systems rely on manual data entry and Excel calculations, with time increasing linearly with the number of employees. For a scale of 5000 employees, the process takes up to 10 hours, and scaling up directly leads to a precipitous drop in efficiency. The system of this invention, relying on automated data collection, batch calculation logic, and module collaboration, takes only 0.5 hours for 500 employees, and even for a scale of 5000 employees, it only takes 1.5 hours, with a time increase of less than 200%. This difference demonstrates that the automated architecture of this invention is adaptable to enterprises of different sizes, especially for large enterprises with multiple departments and high data volumes in payroll calculation scenarios. Through algorithm optimization, it avoids the efficiency bottleneck of manual operation, ensuring the timeliness of large-scale payroll calculations.

[0106] Reference Figure 4The bar chart clearly illustrates the efficiency differences in access control processes. Traditional systems rely on offline manual signature approvals for access control, with temporary cross-departmental access taking 24 hours and abnormal access unblocking taking up to 36 hours, resulting in cumbersome processes and potential business delays. This invention's system, through automated access control verification, online review processes, and quantitative evaluation using a temporary access priority formula, reduces temporary cross-departmental access to just 0.5 hours and abnormal access unblocking to 4 hours. While improving approval efficiency, the system also records audit logs for the entire access control process, meeting the business needs of enterprises to flexibly adjust permissions while avoiding compliance risks associated with simplified processes.

[0107] Reference Figure 5 This line chart illustrates the core difference in anomaly handling efficiency. Traditional systems rely on manual log checks to locate anomalies, with log tampering anomalies requiring 300 minutes to respond and data tampering requiring 240 minutes, leading to inefficient handling and potential for increased losses. The system of this invention quantifies anomaly levels using a risk value formula from the anomaly monitoring module, quickly pinpointing the root cause. Account error anomalies can be responded to in just 5 minutes, and log tampering can be quickly traced thanks to blockchain evidence, completing processing within 20 minutes. The anomaly monitoring module scans the system status in real time, automatically suspending related operations and sending alerts for high-risk anomalies, minimizing the impact of anomalies on the payroll process.

[0108] The above are merely preferred embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.

Claims

1. A salary payment system based on data security management, characterized by, Includes the following modules: The data acquisition and encryption module collects the basic data required for salary calculation. During the acquisition process, the original data is encrypted using the AES-256 encryption algorithm. After encryption, the data is transmitted to the salary calculation module via the SSL / TLS protocol. At the same time, the integrity of the collected data is verified by comparing hash values. The payroll calculation module receives encrypted basic data, requests a decryption key from the central control module, and completes decryption. It then performs payroll calculations according to preset payroll calculation logic, generates preliminary payroll details, and initiates a triple verification mechanism: logical verification, historical data comparison verification, and cross-data verification. If the verification passes, the final payroll details are generated; if the verification fails, an error message is returned to the central control module, and the calculation process is paused. The logical verification checks the accuracy of the calculation formula parameters; the historical data comparison verification compares the current payroll with the previous month's payroll to see if the deviation is within a preset threshold; and the cross-data verification checks the consistency between the social security and housing provident fund deductions and the data on the social security platform. The access control module divides system users into four core roles: administrator, payroll clerk, financial disbursement clerk, and employee query clerk. Each role has exclusive operation permissions, and the permission allocation adopts a role-based access control model, which synchronously records permission change logs. The secure storage module, connected to the payroll calculation module and the access control module, is used to store encrypted basic data, payroll calculation results, access configuration information and audit logs. The storage medium is an encrypted hard disk, and double encryption is performed when storing data. The storage encryption algorithm is SM4, and the file-level encryption is RSA-2048. Access control policies are also set so that only authorized roles can access the corresponding data after passing multi-factor authentication. Unauthorized access will trigger an alarm. The payroll execution module, connected to the payroll calculation module and the secure storage module, is used to perform payroll payroll operations. It supports three payroll channels: bank transfer, e-wallet payment, and paper check. Before payroll ... The audit traceability module connects to all modules of the system and is used to record all operations within the system. The operation log includes the operator, operation time, operation module, operation content, operation result and data access trajectory. The record uses blockchain technology for evidence storage and supports querying logs by operator, operation time and operation type. The query results can only be viewed by administrators and auditors, and the query process is recorded in the logs simultaneously. The central control module connects to the data acquisition and encryption module, salary calculation module, access control module, secure storage module, payment execution module, and audit traceability module. It receives status feedback from each module, issues warnings for abnormal states, manages system keys, and maintains basic system parameters.

2. The salary payment system based on data security management according to claim 1, characterized in that, It also includes a data anonymization module. Sensitive data includes employee ID numbers, bank account numbers, and complete salary details that are not viewed by the individual. The anonymization rules cover partial character replacement, data format conversion, and dynamic anonymization. At the same time, the anonymization strategy is dynamically adjusted according to the type of sensitive data and the access scenario. When abnormal access frequency of sensitive data is detected, the anonymization level is dynamically increased to control the scope of sensitive data exposure.

3. The salary payment system based on data security management according to claim 1, characterized in that, It also includes an anomaly monitoring module, which is used to monitor data operation anomalies and salary payment anomalies within the system. During the anomaly monitoring process, the anomaly risk value is quantified using the formula R=α×D+β×T+γ×F, where R is the anomaly risk value, α is the weight of the data operation anomaly, D is the degree of the data operation anomaly, β is the weight of the salary payment anomaly, T is the degree of the salary payment anomaly, γ is the weight of the historical anomaly correlation, and F is the degree of the historical anomaly correlation. The anomaly level is determined by this anomaly risk value, and corresponding handling measures are triggered according to the anomaly level.

4. The salary payment system based on data security management according to claim 1, characterized in that, The access control module also supports dynamic access control adjustment. When the system detects a change in user operation scenario, the administrator initiates a temporary access control adjustment request. After the request is submitted and approved by the auditors, it takes effect. The validity period of temporary access control is no more than 72 hours. After the validity period expires, the original access control will be automatically restored. The entire process of application, review, activation and expiration of temporary access control is recorded in the audit log. The access control module regularly performs compliance checks on all user access control. Non-compliant access control is automatically frozen and the administrator is notified.

5. The payroll system based on data security management according to claim 1, wherein, The secure storage module adopts a dual-storage architecture of "local encrypted storage + off-site disaster recovery backup". Local storage is used for daily data access and uses a RAID5 disk array to achieve hardware-level data reliability. Off-site disaster recovery backup is deployed in the backup center. Backup data is synchronized with local storage data in real time. The synchronization process uses IPsec protocol for encrypted transmission. The off-site backup center uses the same access control policy as the local data. The secure storage module performs lifecycle management on the stored data. The basic data retention period is 3 years, and the salary calculation results and payment records are retained for 10 years. Data exceeding the retention period is shredded and deleted after being reviewed by the administrator and supervised by the auditor. The deletion process is recorded in the audit log.

6. The salary payment system based on data security management according to claim 1, wherein, The payroll execution module also has a secondary verification function for payroll results. After payroll is completed, the system automatically sends a confirmation notification containing a random verification code to the employee. The employee must enter the verification code through the system query interface to complete the payroll confirmation within 24 hours. For employees who fail to confirm on time, the system will send a reminder notification again after 12 hours. If the employee still fails to confirm after 48 hours, the payroll execution module will trigger an abnormal warning and suspend the employee's next payroll payment until confirmation is completed. The payroll execution module also supports a payroll cancellation function. If a payroll error is found and the payment channel supports cancellation, the finance payroll clerk will initiate a cancellation request. The cancellation operation will be executed within 2 hours after the payroll is completed. If it exceeds 2 hours, manual intervention is required. The cancellation process and results are recorded in the audit log.

7. The payroll system based on data security management according to claim 1, wherein, The audit traceability module also has log analysis and risk warning functions. It performs multi-dimensional analysis on audit logs and generates audit reports based on the analysis results. The reports identify high-frequency operation roles, periods of concentrated abnormal operations, and high-risk operation types, providing data support for administrators to optimize permission configurations and adjust security policies. The audit logs use tamper-proof storage technology, so administrators and auditors can only view the logs and cannot modify or delete them.

8. A salary payment method based on data security management, characterized by, A payroll system based on data security management, as described in any one of claims 1-7, includes the following steps: The data collection and encryption steps involve collecting the basic data required for salary calculation, including employee attendance data, performance data, social security and housing provident fund contribution standards, individual income tax deduction rules, and employee salary structure data. All collected raw data is encrypted using the AES-256 encryption algorithm, and the hash value of the raw data is calculated. The encrypted data and hash value are transmitted to the salary calculation module via the SSL / TLS protocol. After receiving the data, the salary calculation module verifies the hash value to complete the data integrity verification. The salary calculation process involves the salary calculation module requesting a decryption key from the central control module, decrypting the received encrypted basic data, performing salary calculations according to preset salary calculation logic, generating individual employee salary details, and initiating a triple verification mechanism: logical verification, historical data comparison verification, and cross-data verification. If the verification passes, the final salary details are generated; if the verification fails, an error message is returned to the central control module, and the calculation process is paused. The logical verification checks the accuracy of the calculation formula parameters; the historical data comparison verification compares the deviation between the current salary and the previous month's salary to see if it is within a preset threshold; and the cross-data verification checks the consistency between the social security and housing provident fund deductions and the data on the social security platform. In the permission verification process, when a payroll clerk initiates a payroll details submission request, a finance disbursement clerk initiates a disbursement execution request, or an employee initiates a payroll query request, the permission management module receives the request and obtains the identity information of the requesting user. Based on the RBAC model, it verifies the permissions corresponding to the user role. If the verification passes, the operation is allowed to continue; if the verification fails, the operation is rejected and the abnormal access log is recorded to the audit traceability module. In the secure storage process, the payroll calculation module transmits the final payroll details and encrypted basic data to the secure storage module. The secure storage module uses the SM4 algorithm to encrypt the data and the RSA-2048 algorithm to perform file-level encryption. The encrypted data is then stored in the local RAID5 disk array and synchronized to the off-site disaster recovery backup center. After storage is completed, a storage record is generated and sent to the central control module and the audit traceability module. In the payroll execution process, after the financial payroll clerk passes the authorization verification, they select the payroll channel through the payroll execution module and enter the account information required for payroll. The payroll execution module calls the final payroll details in the secure storage module and compares the payroll account with the employee's account. If the consistency is successful, a payroll request is initiated to the corresponding payment channel. The payroll execution module encrypts and stores the result in the secure storage module and sends a notification with a query link to the employee. After receiving the notification, the employee completes the payroll confirmation through the system. The audit logging process involves the audit traceability module receiving operational data from each module in real time, organizing the data into audit log entries, generating a unique hash value for each log entry and linking it to the blockchain distributed ledger, and storing the audit logs in a designated area of ​​the secure storage module for administrators and auditors to query.

9. The salary payment method based on data security management according to claim 8, wherein, It also includes a dynamic permission adjustment step. When the system detects a change in the user's operation scenario, the user initiates a temporary permission adjustment request. If approved, the administrator configures the temporary permissions. The priority of the temporary permissions is determined by the formula P=λ×S+μ×I+ν×U, where P is the temporary permission priority, λ is the business urgency weight, S is the business urgency, μ is the data sensitivity weight, I is the data sensitivity level, ν is the historical permission record weight, and U is the historical permission compliance record. After the temporary permission is configured according to the priority, the permission management module records the configuration process to the audit log. The temporary permission expires automatically and the original permission is restored after the expiration of the validity period. The expiration process is also recorded in the log.

10. The payroll disbursement method based on data security management according to claim 8, wherein, It also includes data disaster recovery backup and recovery steps. In this step, the secure storage module performs local full backup and off-site incremental backup according to a preset cycle. The local backup is compressed with ZIP and encrypted with SM4. The integrity is verified by comparing hash values. Off-site backups only synchronize newly added or modified data, transmitted with IPsec encryption. The off-site backup center updates the version or resynchronizes after hash verification. When local data is damaged or lost, the administrator initiates a recovery request after multi-factor authentication by auditors. Data is extracted from the local full backup. If the local backup is unavailable, off-site data is retrieved. After decryption, the integrity and accuracy are verified by comparing with historical logs. The recovery result is recorded in the audit traceability module and the administrator is notified. The secure storage module conducts disaster recovery drills every quarter, simulating the scenario of complete loss of local data, recording indicators and generating reports.

Images