WO2019019750A1 - 年金管理系统、方法、服务器和存储介质 - Google Patents

年金管理系统、方法、服务器和存储介质 Download PDF

Info

Publication number
WO2019019750A1
WO2019019750A1 PCT/CN2018/085042 CN2018085042W WO2019019750A1 WO 2019019750 A1 WO2019019750 A1 WO 2019019750A1 CN 2018085042 W CN2018085042 W CN 2018085042W WO 2019019750 A1 WO2019019750 A1 WO 2019019750A1
Authority
WO
WIPO (PCT)
Prior art keywords
annuity
employee
receiving
information
enterprise
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/085042
Other languages
English (en)
French (fr)
Inventor
黄海亮
徐凌青
胡伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2019019750A1 publication Critical patent/WO2019019750A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • the application relates to an annuity management system, method, server and storage medium.
  • the annuity refers to the supplementary pension insurance that the enterprise and its employees voluntarily establish on the basis of participating in the basic endowment insurance according to law. Annuities include corporate contributions and individual employee contributions. An annuity is also a good investment arrangement, and more and more companies are participating in the annuity plan. However, the inventors realized that there is currently no system that can effectively and comprehensively manage the annuity business. If there are more employees participating in the enterprise annuity plan, the enterprise needs to invest a large amount of manpower, which is long, time-consuming and labor-intensive.
  • an annuity management system a method, server, and storage medium are provided.
  • An annuity management system that includes:
  • the annuity receiving system is configured to receive an annuity business processing request sent by the enterprise terminal; the annuity processing request carries an annuity plan identifier, enterprise information and employee information;
  • An annuity trustee system for opening an annuity business based on the annuity plan logo and corporate information
  • the annuity receiving system is further configured to receive an annuity payment request sent by the enterprise terminal;
  • An account management system for performing an annuity payment accounting operation for a plurality of employees according to the annuity payment request
  • the annuity trustee system is further configured to obtain an annuity income corresponding to the annuity business, and the account management system is further configured to perform an annuity income allocation accounting operation for a plurality of employees according to the annuity income;
  • the annuity receiving system is further configured to receive an annuity receiving request sent by the employee terminal, where the annuity receiving request carries a receiving account; the annuity trusting system is further configured to calculate a corresponding annuity receiving amount according to the annuity receiving request, according to The annuity receiving amount and the receiving account generate an annuity payment request, and send the annuity payment request to the hosting terminal, so that the hosting terminal transfers the annuity receiving amount to the receiving account.
  • An annuity management method that includes:
  • annuity processing request sent by the enterprise terminal;
  • the annuity processing request carries an annuity plan identifier and enterprise information; and annuity business corresponding to the enterprise is opened according to the annuity plan identifier and the enterprise information;
  • annuity payment request sent by the enterprise terminal, where the annuity payment request carries a plurality of employee identifications; and adding an annuity payment record corresponding to the plurality of employee identifications according to the annuity payment request;
  • the annuity receiving request When receiving the annuity receiving request sent by the employee terminal, the annuity receiving request carries the employee identification and the receiving account; obtaining the corresponding annuity payment record and the income distribution record according to the employee identification, and paying the record and the income according to the annuity
  • the distribution record calculates a corresponding annuity payment amount, and sends the annuity payment request to the escrow terminal according to the annuity collection amount and the collection account generating annuity payment request, so that the escrow terminal transfers the annuity payment amount to the collection account.
  • a computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executable by the processor to cause the one or more processors to execute The following steps:
  • annuity processing request sent by the enterprise terminal;
  • the annuity processing request carries an annuity plan identifier and enterprise information; and annuity business corresponding to the enterprise is opened according to the annuity plan identifier and the enterprise information;
  • annuity payment request sent by the enterprise terminal, where the annuity payment request carries a plurality of employee identifications; and adding an annuity payment record corresponding to the plurality of employee identifications according to the annuity payment request;
  • the annuity receiving request When receiving the annuity receiving request sent by the employee terminal, the annuity receiving request carries the employee identification and the receiving account; obtaining the corresponding annuity payment record and the income distribution record according to the employee identification, and paying the record and the income according to the annuity
  • the distribution record calculates a corresponding annuity payment amount, and sends the annuity payment request to the escrow terminal according to the annuity collection amount and the collection account generating annuity payment request, so that the escrow terminal transfers the annuity payment amount to the collection account.
  • One or more non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the following steps:
  • annuity processing request sent by the enterprise terminal;
  • the annuity processing request carries an annuity plan identifier and enterprise information; and annuity business corresponding to the enterprise is opened according to the annuity plan identifier and the enterprise information;
  • annuity payment request sent by the enterprise terminal, where the annuity payment request carries a plurality of employee identifications; and adding an annuity payment record corresponding to the plurality of employee identifications according to the annuity payment request;
  • the annuity receiving request When receiving the annuity receiving request sent by the employee terminal, the annuity receiving request carries the employee identification and the receiving account; obtaining the corresponding annuity payment record and the income distribution record according to the employee identification, and paying the record and the income according to the annuity
  • the distribution record calculates a corresponding annuity payment amount, and sends the annuity payment request to the escrow terminal according to the annuity collection amount and the collection account generating annuity payment request, so that the escrow terminal transfers the annuity payment amount to the collection account.
  • FIG 1 is an application environment diagram of an annuity management system in accordance with one or more embodiments.
  • FIG. 2 is a block diagram showing the structure of an annuity management system in accordance with one or more embodiments.
  • FIG. 3 is a schematic structural diagram of a server according to one or more embodiments.
  • FIG. 4 is a block diagram showing the flow of an annuity management method in accordance with one or more embodiments.
  • first may be referred to as a second client
  • second client may be referred to as a first client, without departing from the scope of the present application.
  • Both the first client and the second client are clients, but they are not the same client.
  • the annuity management system provided in the embodiment of the present application can be applied to an application environment as shown in FIG. 1.
  • a plurality of enterprise terminals 102 are connected to the server 104 via a network, and a plurality of employee terminals 106 are connected to the server 104 via a network, and the managed terminal 108 is connected to the server 104 via a network.
  • the enterprise manager can initiate an annuity service request to the server 104 through the enterprise terminal 102.
  • the annuity business registration request carries the annuity plan logo, company information and employee information.
  • the server 104 activates the corresponding annuity business based on the annuity plan identifier and the company information.
  • the server 104 obtains the corresponding annuity information according to the annuity plan identifier, and counts the employees who choose to participate in the annuity plan according to the annuity information and the employee information, and obtains the statistical result of the employee participation.
  • the statistical results include a list of employees who are confirmed to participate in the annuity plan.
  • the enterprise manager can initiate an annuity payment request to the server 104 through the enterprise terminal 102.
  • the server 104 generates a bill to be completed according to the annuity payment request, and queries whether the corresponding annuity account has an account matching the bill to be completed according to the enterprise information, and if so, uses the account to perform an annuity payment accounting operation for the plurality of employees.
  • an employee needs to receive an annuity
  • the employee can initiate an annuity claim to the server 104 via the employee terminal 106.
  • the collection request is carried in the annuity request.
  • the server 104 calculates a corresponding annuity receiving amount according to the annuity receiving request, and generates an annuity payment request according to the annuity receiving amount and the receiving account to generate an annuity payment request, and sends the annuity payment request to the custody terminal 108 corresponding to the third party bank worker.
  • the escrow terminal 108 transfers the account corresponding to the annuity payment amount to the collection account according to the annuity payment request. This enables effective and integrated management of the annuity business.
  • an annuity management system including: an annuity acceptance system 202, an annuity trustee system 204, and an account management system 206, wherein:
  • the annuity receiving system 202 is configured to receive an annuity business processing request sent by the enterprise terminal; the annuity processing request carries an annuity plan identifier, enterprise information, and employee information.
  • the annuity trustee system 204 is used to open an annuity business based on the annuity plan logo and company information.
  • the annuity receiving system 202 is further configured to receive an annuity payment request sent by the enterprise terminal.
  • the account management system 206 is configured to perform an annuity payment accounting operation for a plurality of employees according to the annuity payment request.
  • the annuity trustee system 204 is also used to obtain the annuity income corresponding to the annuity business, and the account management system is also used to perform an annuity income allocation accounting operation for a plurality of employees based on the annuity income.
  • the annuity receiving system 202 is also used for the annuity receiving request sent by the employee terminal, and the annuity receiving request includes the receiving account; the annuity trusting system 204 is also used to calculate the corresponding annuity receiving amount according to the annuity receiving request, and generate according to the annuity receiving amount and the receiving account.
  • the annuity payment request sends an annuity payment request to the escrow terminal, so that the escrow terminal transfers the annuity payment amount to the receiving account.
  • the annuity management system can run on the server.
  • the annuity management system can comprehensively manage the annuity business. Specifically, when the enterprise chooses to participate in an annuity plan, the management personnel of the enterprise can send an annuity business processing request to the annuity receiving system 202 through the enterprise terminal.
  • Each annuity plan has a corresponding annuity plan logo and annuity information.
  • the annuity business registration request carries the annuity plan logo, company information and employee information.
  • the annuity plan logo can be an annuity plan registration number, etc.
  • Corporate information includes corporate identity.
  • Employee information includes basic information about multiple employees, such as employee name, gender, contact number, and email address.
  • the annuity receiving system 202 sends the annuity plan identification, company information, and employee information to the annuity trustee system 204.
  • the annuity trustee system 204 activates the corresponding annuity task based on the annuity plan logo and company information.
  • Multiple companies can participate in the same annuity plan, and the insurance company creates a corresponding annuity account for each annuity plan.
  • Each company can transfer one or more accounts from the corporate account to the annuity account through the corporate terminal on a monthly, quarterly or yearly basis when an annuity is required for the employee participating in the annuity plan.
  • Multiple accounts in an annuity account include used and/or unused accounts. For accounts that are initially transferred to an annuity account, the server marks the account as unused.
  • the annuity trustee system 204 obtains the corresponding annuity information according to the annuity plan identifier, and generates the first file by using the annuity information.
  • the first document is a document that employees need to confirm when they choose to participate in an annuity plan.
  • the annuity trustee system 204 transmits the first file and corresponding annuity information to a plurality of employee terminals based on employee information (contact phone or email).
  • Annuity information includes annuity plan and annuity knowledge. Employees can understand the annuity knowledge and annuity plan through the employee terminal to determine whether to participate in the company's annuity plan.
  • the employee can download the first file through the employee terminal, and input the confirmation information corresponding to the first file.
  • the confirmation information may include a digital signature, fingerprint information, a face image, or an answer to a random question.
  • the random problem is that the annuity trustee system 204 randomly generates according to the first file and has a corresponding default answer.
  • the employee terminal sends a confirmation message to the annuity trustee system 204.
  • the annuity trustee system 204 verifies the confirmation information according to a preset verification rule.
  • the annuity trustee system 204 obtains the pre-stored signature handwriting corresponding to the employee, and matches the signature signature of the digital signature with the pre-stored signature handwriting; if the matching degree reaches the first threshold And the answer to the random question is consistent with the default answer, then the verification is passed.
  • the verification of the confirmation information returned by the employee terminal can prevent other people from maliciously replacing the employee to confirm the first file, improve the real validity of the employee participation statistics, and reduce the cumbersomeness of the enterprise management personnel to manually identify the authenticity of the confirmation information. In turn, the burden on the enterprise manager to manually verify the confirmation information can be reduced.
  • the annuity trustee system 204 counts the currently received confirmation information, and obtains the statistical result of the employee participation.
  • the statistical results of employee participation include a list of employees who have participated in the annuity plan, along with the first document and corresponding confirmation information.
  • the annuity trustee system 204 returns the statistical results of employee participation to the corporate terminal.
  • the enterprise management personnel can download the first file and the corresponding confirmation information through the enterprise terminal to archive the first file and the corresponding confirmation information.
  • Business managers can pay annuities to employees who participate in the annuity plan through the corporate terminal.
  • the business manager can send an annuity payment request to the annuity receiving system 202 through the enterprise terminal.
  • the annuity payment request carries the corporate identity.
  • the annuity receiving system 202 sends an annuity payment request to the annuity trustee system 204.
  • the annuity trustee system 204 reads the employee list based on the annuity payment request.
  • the employee list includes employee IDs and payment amounts for multiple employees.
  • the employee ID is used to uniquely identify an employee, which can be an employee number or an ID number.
  • the annuity trustee system 204 generates a pending bill based on the company identification and the employee list.
  • the pending bill has corresponding billing information.
  • the billing information includes the billing title and billing amount.
  • the billing title is used to indicate the purpose of the pending bill, including the company logo and the annuity payment time, such as “A company’s September 2016 annuity bill”. It is easy to understand that the bill amount is equal to the sum of the payment amounts corresponding to multiple employees.
  • the annuity trustee system 204 obtains the corresponding annuity account according to the company logo, and queries the annuity account for the existence of unused accounts. If yes, the annuity trustee system 204 monitors the batch task execution status and resource consumption status in the database during the non-working time period, and selects the ability according to the execution time and resource consumption time of the batch task in the non-working time period. Avoid the resource consumption time of multiple batch task execution time as the idle time of the database. Batch tasks include pending billing and unused accounts, and annuity billing. The annuity trustee system 204 obtains the account information of the unused accounts during the idle time of the database, and matches the completed bills with the unused accounts according to the billing information and the account information.
  • the annuity trustee system 204 reads the employee list, assigns the unused accounts matching the pending bills to the plurality of employees based on the payment amount of the plurality of employees, and transmits the distribution result to the account management system 206.
  • the account management system 206 adds a corresponding annuity payment record to each employee identification according to the distribution result, thereby completing the annuity payment accounting operation of the plurality of employees.
  • the annuity payment record can be used as the basis for an employee to receive an annuity.
  • the employee can apply for an annuity from the employee through the employee terminal.
  • the employee can send an annuity claim to the annuity receiving system 202 through the employee terminal.
  • the annuity claim carries the employee identification information and the application information.
  • Receiving application information includes receiving information such as receiving an account, receiving type, receiving period, number of receiving periods, and/or amount of each period. Among them, the types of collection include regular, fixed and fixed quotas.
  • the collection cycle includes one-time collection, monthly collection, quarterly collection and annual collection. Employees can choose the type of collection at the employee terminal.
  • the annuity receiving system 202 sends an annuity claim to the annuity trustee system 204.
  • the annuity acceptance system 202 and the annuity trustee system 204 verify employee identity information.
  • the annuity receiving system 202 and the annuity trustee system 204 can verify employee identity information via a video call.
  • the annuity receiving system 202 receives a video call request initiated by the employee through the employee terminal, and the annuity trusting system 204 establishes a video call between the employee terminal and the management terminal according to the video call request, and receives the employee uploading through the employee terminal during the video call.
  • the identity information is used to obtain the pre-stored identity information corresponding to the employee, and the uploaded identity information is matched with the pre-stored identity information; if the matching degree reaches a preset threshold, the verification is passed.
  • the annuity trustee system 204 If the verification is passed, the annuity trustee system 204 generates the payment record inquiry task using the employee identity information, and sends the payment record inquiry task to the account management system 206.
  • the account management system 206 queries whether there is a corresponding annuity payment record based on the employee identification information, and returns the inquiry result to the annuity trustee system 204. If the result of the inquiry is that the employee's annuity payment record exists, the annuity trustee system 204 calculates the corresponding annuity payment amount and/or tax amount based on the employee's annuity payment record and the application information.
  • the annuity trustee system 204 generates a receipt file based on the receipt application information and the calculated annuity receipt amount and/or tax amount, and stores the receipt file in a database. Before the current collection file is stored in the database, the recipient files corresponding to multiple employees may already be stored in the database.
  • the annuity trustee system 204 counts the number of documents collected in the statistical database, and compares whether the statistical quantity of the received files reaches the second threshold. If so, the annuity trustee system 204 sends the plurality of receipt files stored in the database to the enterprise terminal in batches.
  • the enterprise management personnel can conduct a unified review of the plurality of documents received through the enterprise terminal, and if the approval is passed, send the receiving response to the annuity receiving system 202.
  • the annuity receiving system 202 sends a receipt response to the annuity trustee system 204. If the receipt response is a confirmation payment, the annuity trustee system 204 generates an annuity payment request based on the receipt document, and sends the annuity payment request to the escrow terminal.
  • the bank staff can transfer the account corresponding to the annuity payment amount from the annuity account to the collection account through the escrow terminal.
  • the annuity management system may include at least an annuity acceptance system, an annuity trustee system, and an account management system.
  • the annuity acceptance system and the annuity trustee system can open the corresponding annuity business according to the request for the annuity business initiated by the enterprise terminal.
  • the account management system can perform an annuity payment accounting operation for multiple employees.
  • the annuity trustee system and the account management system can also allocate annuity income to multiple employees of the company based on the annuity income corresponding to the annuity business.
  • the annuity receiving system and the annuity trustee system can calculate the corresponding annuity receiving amount according to the employee's annuity receiving request, and can transfer the amount directly to the employee's receiving account through the bank's custody terminal.
  • the annuity management system can not only open an annuity business for enterprises, but also pay an annuity payment, and can also carry out various business such as annuity income distribution and annuity collection, thereby realizing effective comprehensive management of the annuity business.
  • the annuity acceptance system is further configured to receive an annuity transfer reservation request sent by the enterprise terminal, and the annuity transfer retention request carries the information of the resigned employee;
  • the annuity trustee system is further configured to generate a second file according to the information of the resigned employee, The second file is sent to the employee terminal corresponding to the departing employee, receives the confirmation information corresponding to the second file returned by the employee terminal, and sends the confirmation information to the enterprise terminal, so that the enterprise terminal handles the annuity transfer to the departing employee according to the confirmation information.
  • the company can deal with the annuity of the departing employee, such as transfer retention.
  • the enterprise management personnel can initiate an annuity transfer request to the annuity acceptance system 202 through the enterprise terminal.
  • the annuity transfer request carries the information of the departing employee.
  • the information of the retired employees includes basic information and annuity payment information of a number of retired employees, such as an annuity payment account and the specific proportion of ownership.
  • the annuity receiving system 202 sends an annuity transfer request to the annuity trustee system 204.
  • the annuity trustee system 204 generates an annuity balance inquiry request based on the resigned employee information, and sends an annuity balance inquiry request to the account management system 206. Based on the annuity balance inquiry request, the account management system 206 queries the current total amount of the annuity payment accounts corresponding to the plurality of departing employees. The annuity trustee system 204 generates a second document for each departing employee based on the basic information of the departing employee and the current total amount of the annuity payment account.
  • the annuity trustee system 204 generates notification information, obtains the contact information of each employee based on the information of the resigned employee, and sends the second file and the notification information to the employee terminal corresponding to the resigned employee according to the obtained contact information, so as to prompt the retired employee to promptly contact the second employee.
  • the file is confirmed.
  • the employee terminal may return the problem item corresponding to the second file to the server, such as “the ID number is incorrect” or “the attribution ratio is incorrect”.
  • the employee terminal sends the question item to the annuity receiving system 202.
  • the annuity receiving system 202 sends the question item to the enterprise terminal.
  • the enterprise management personnel can modify the information of the departing employees according to the problem item through the enterprise terminal.
  • the enterprise terminal regenerates the annuity transfer reservation request using the modified resigned employee information, and transmits the regenerated annuity transfer reservation request to the annuity acceptance system 202.
  • the employee terminal may return the confirmation information corresponding to the second file to the annuity trustee system 204.
  • the confirmation information may be a digital signature, a fingerprint information or a face image, or may be an answer to a random question. The random problem is randomly generated by the server according to the first file and has a corresponding default answer.
  • the server can verify the confirmation information returned by the employee terminal in the manner provided in the foregoing embodiment. If the confirmation information verification is passed, the annuity trustee system 204 transmits the second file and the corresponding confirmation information to the enterprise terminal. According to the second document and the corresponding confirmation information, the enterprise management personnel can transfer the annuity to the departing employees through the enterprise terminal.
  • the enterprise management personnel may initiate an annuity transfer request at the enterprise terminal, generate a second file according to the annuity transfer request, and send the second file to the employee terminal, so that the retired employee can confirm the second file at the employee terminal. Or raise an objection; when the employee has objection to the second file, the employee can send the problem item to the enterprise terminal through the employee terminal; the enterprise management personnel can re-initiate the annuity transfer request in the enterprise terminal according to the problem item, thereby ensuring The correctness of the annuity transfer request can reduce the cumbersomeness of the enterprise management personnel to manually confirm the information of the departing employees, and thus can effectively reduce the workload of the enterprise management personnel in handling the annuity business.
  • the annuity trustee system is further configured to query whether the annuity account has an annuity income when the preset income distribution period is reached, and if so, calculate a corresponding income distribution amount of the plurality of employees of the enterprise; The system is also used to perform an annuity income allocation accounting operation for multiple employees based on the amount of revenue distribution.
  • the insurance company uses the account in the corresponding annuity account for investment, and the income generated by the investment is distributed to the employees participating in the annuity plan according to the company regulations. Therefore, the annuity includes not only corporate contributions and individual employee contributions, but also annuity income, which has the problem of income distribution among multiple employees of the enterprise.
  • the annuity trustee system 204 presets a revenue distribution period.
  • the revenue distribution period includes multiple time nodes. The length of the income distribution cycle can be set by the insurance company's management personnel according to the duration of different investment projects.
  • the annuity trustee system 204 performs a revenue distribution at the end of each income distribution period.
  • the annuity trustee system 204 queries whether the annuity account has an annuity income, and if so, calculates an annuity income corresponding to each employee of the enterprise.
  • the account system 206 performs an annuity income allocation accounting operation for the corresponding employee based on the annuity income corresponding to each employee.
  • the annuity trustee system is further configured to obtain the annuity data, the first distribution model, and the second distribution model, and calculate the annuity income corresponding to the enterprise identifier by using the annuity data and the first distribution model; and use the annuity income corresponding to the enterprise logo.
  • the second distribution model calculates the annuity income corresponding to multiple employees.
  • the annuity trustee system 204 Upon reaching the preset revenue distribution period, the annuity trustee system 204 queries whether the annuity account has an annuity income, and if so, the annuity trustee system 204 obtains the annuity data of the plurality of enterprises corresponding to the annuity account.
  • the revenue distribution period includes multiple time nodes.
  • the annuity data corresponding to an enterprise includes the initial annuity amount of the enterprise before the start of the income distribution period and the amount of annuity change at each time node.
  • the annuity trustee system 204 obtains the first model, inputs the annuity income and the annuity data into the first model, and calculates the annuity income corresponding to each enterprise.
  • the annuity data corresponding to a company also includes the initial annuity amount of multiple employees of the enterprise before the start of the income distribution cycle and the amount of annuity change at each time node.
  • the annuity trustee system 204 obtains the second model, inputs the annuity income corresponding to the enterprise and the annuity data of the enterprise into the second model, and calculates the annuity income corresponding to the plurality of employees of the enterprise.
  • the annuity trustee system 204 sends the calculated annuity income corresponding to each employee to the account management system 206.
  • the account management system 206 performs an annuity income allocation accounting operation for the corresponding employee according to the annuity income corresponding to each employee.
  • the income distribution can be automatically performed, and the workload of the insurance company manager for artificially distributing the income is reduced; and each enterprise is calculated by inputting the annuity income and the annuity data into the first model.
  • Corresponding annuity income by inputting the corresponding annuity income and annuity data of the enterprise into the second model to calculate the annuity income corresponding to the plurality of employees of the enterprise, the accuracy of the calculation of the annuity income can be improved, and the distribution efficiency of the annuity income can also be improved.
  • the annuity receiving system is further configured to receive an employee new request sent by the enterprise terminal, and the employee new request carries the newly added employee list, and the newly added employee list includes the receiving field name corresponding to the plurality of newly added employees;
  • the annuity trustee system is also used to obtain the docking configuration table.
  • the docking configuration table records the trusted field name and the corresponding receiving field name, and queries the corresponding receiving field name in the newly added employee list according to the trusted field name; obtains the employee list, according to the query The callee field name adds the employee's corresponding trusted field name to the employee list.
  • the annuity receiving system 202 receives data provided by the customer through the enterprise terminal or the employee terminal.
  • the data provided by the customer can be called the acceptance data. If the recording method of the acceptance data is different from the recording method required by the insurance company, the insurance company cannot directly use the acceptance data provided by the customer for business processing, and also needs to perform the docking processing on the acceptance data provided by the customer, so that the docked data is easy to be insured.
  • the company conducts business processing.
  • the annuity receiving system 202 transmits the acceptance data to the annuity trustee system 204.
  • the annuity trustee system 204 pre-stores the entry configuration table and the docking configuration table in the database.
  • the entry configuration table records the names of multiple call fields provided by the customer.
  • the business field name and the call field name are recorded in the docking configuration table. There is a mapping relationship between the business field name and one or more call field names.
  • the business field name may be extracted from the above employee list by the annuity trustee system 204.
  • the acceptance field name may be extracted from the entry configuration table by the annuity trustee system 204.
  • the enterprise manager can initiate an employee new request to the annuity receiving system 202 through the enterprise terminal.
  • the employee new request carries a list of new employees.
  • the new employee list includes the names of the receiving fields corresponding to multiple new employees, such as name, gender, ID number, mobile phone, etc.
  • the annuity receiving system 202 sends an employee addition request to the annuity trustee system 204.
  • the annuity trustee system 204 obtains a list of employees. Multiple business field names are recorded in the employee list, such as employee name, employee gender, ID number, contact number, and so on.
  • the annuity trustee system 204 obtains the docking configuration table, and queries the docking configuration table for the call field name corresponding to the business field name in the employee list, and uses the call field name to query the same call field name in the call data. Based on the queried call field name, the annuity trustee system 204 adds the business data field name of the acceptance data to the employee list.
  • the mapping relationship between the service field name and the call field name is recorded in the docking configuration table.
  • the call field name corresponding to the service field name can be queried in the acceptance data, so that the service field name corresponding to the call data can be recorded in the service data table according to the queried call field name, thereby realizing the acceptance data and
  • the accurate docking between the business data enables the docked data to facilitate the insurance company to conduct business processing.
  • the annuity trustee system is further configured to generate a corresponding annuity task according to each annuity business processing request, process the annuity task, monitor whether the annuity task has an abnormality, and if so, obtain the annuity task in the process of processing
  • the recorded log is sent to the management terminal.
  • the annuity receiving system 202 can receive an annuity business processing request sent by a plurality of enterprise terminals.
  • the annuity receiving system 202 sends a plurality of annuity business processing requests to the annuity trustee system 204.
  • the annuity trustee system 204 generates a corresponding annuity task according to each annuity business processing request, calls multiple threads, processes a plurality of annuity tasks in batches, and monitors whether an annuity task has an abnormality. If yes, the annuity trustee system 204 obtains the log recorded during the processing of the corresponding annuity task, and sends the log to the management terminal. According to the log, the management personnel can manually process the annuity task that has abnormal processing through the management terminal to ensure that each annuity task can be effectively processed.
  • a server is provided, as shown in FIG. 3, which includes a processor, a storage device, and a network interface connected by a system bus.
  • the processor of the server is used to provide computing and control capabilities.
  • the storage device of the server includes one or more non-volatile storage media, one or more internal storage devices.
  • the server's non-volatile storage medium stores an operating system, computer readable instructions, and a database, the computer readable instructions being executed by the processor to implement the functionality of an annuity management system that stores the receipt of multiple employees Documents, etc.
  • the internal storage of the server provides an environment for the operation of the operating system and computer readable instructions in the non-volatile storage medium.
  • the network interface of the server is used for communicating with an external terminal through a network connection, for example, receiving an annuity service request sent by the terminal.
  • the server can be implemented as a standalone server; it can also be implemented as a server cluster consisting of multiple servers.
  • FIG. 3 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied.
  • the specific server may include a ratio. More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.
  • an annuity management method is provided, which is applied to the server as an example, and specifically includes the following steps:
  • Step 402 Receive an annuity business processing request sent by the enterprise terminal; the annuity processing request carries the annuity plan identifier and the enterprise information; and the annuity business corresponding to the enterprise is opened according to the annuity plan identifier and the enterprise information;
  • Step 404 Receive an annuity payment request sent by the enterprise terminal, where the annuity payment request carries multiple employee identifiers; and add an annuity payment record corresponding to the plurality of employee identifiers according to the annuity payment request;
  • Step 406 Acquire an annuity income corresponding to the annuity business according to a preset time frequency, and add a revenue allocation record corresponding to the plurality of employee identifiers according to the annuity income;
  • Step 408 When receiving the annuity receiving request sent by the employee terminal, the annuity receiving request carries the employee identification and the receiving account; and the corresponding annuity payment record and the income distribution record are obtained according to the employee identification, and are calculated according to the annuity payment record and the income distribution record.
  • the corresponding annuity payment amount is sent to the escrow terminal according to the annuity payment amount and the account payment annuity payment request, so that the escrow terminal transfers the annuity payment amount to the receiving account.
  • the server can open the corresponding annuity business according to the request for the annuity business initiated by the enterprise terminal.
  • the server can add a corresponding annuity payment record for multiple employee IDs.
  • the server can also periodically add corresponding annuity income allocation records to multiple employee IDs according to the annuity income corresponding to the annuity business.
  • the server can obtain the corresponding annuity payment record and the income distribution record according to the employee's annuity receiving request, calculate the corresponding annuity receiving amount according to the annuity payment record and the income distribution record, and can directly report to the bank's custody terminal.
  • the employee's collection account is transferred to this amount.
  • the server opens an annuity service for the enterprise, adds a corresponding annuity payment record and a revenue distribution record for the plurality of employee identifications, and when the employee needs to receive the annuity, the server can send an annuity receiving request to the server through the employee terminal, and the server can The annuity payment amount of the employee is calculated by using the annuity payment record and the income distribution record, and the amount of the annuity received can be directly transferred to the employee's collection account through the bank's custody terminal.
  • the employee can receive an annuity.
  • the method further comprises: obtaining an annuity information according to the annuity plan identifier, generating the first file by using the annuity information; sending the first file to the plurality of employee terminals; and agreeing to participate in the annuity plan when the employee agrees within the preset time period Receiving, by the employee terminal, the confirmation information corresponding to the first file returned by the employee terminal; the first file has a corresponding random problem; if the confirmation information includes the digital signature and the answer to the random question; and verifying the confirmation information by using the digital signature and the answer of the random question If the verification is passed, the confirmation information is counted, the statistical result of the employee participation is obtained, and the statistical result is sent to the enterprise terminal.
  • the server can automatically count the employees participating in the annuity plan according to the request for the annuity business of the enterprise terminal.
  • the server verifies the confirmation information returned by the employee terminal, which can prevent others from maliciously replacing the employee to confirm the first file, improve the real validity of the employee participation statistics, and reduce the need for the enterprise management personnel to manually identify the confirmation information.
  • the cumbersomeness of authenticity can further reduce the burden on business managers to manually verify the confirmation information.
  • the method further comprises: generating a bill to be completed according to the annuity payment request, the bill to be completed has corresponding billing information; and querying whether the corresponding annuity account has unused accounts according to the enterprise information, the unused account has Corresponding account information; if present, obtain the idle time of the database, and match the completed bill and the unused account according to the billing information and the account information during the idle time of the database; if the matching is successful, the employee list is read, the employee The list includes multiple employees; annuity payment accounting operations are performed on multiple employees with unused accounts.
  • the server can automatically match the completed bill and the unused account according to the enterprise terminal's annuity payment request, so that the accounting operation can be paid for the annuity of multiple employees. More importantly, the matching of the bills to be completed and the unused accounts and the operation of the accounting and annuity accounting are all performed in the idle time of the database, which can reduce the occupation of server resources.
  • the method further includes: receiving an employee new request sent by the enterprise terminal, the employee new request carrying the newly added employee list, and the newly added employee list including the receiving field name corresponding to the plurality of newly added employees;
  • the docking configuration table In the docking configuration table, the trusted field name and the corresponding receiving field name are recorded in the docking configuration table, and the corresponding receiving field name is queried in the newly added employee list according to the trusted field name; the employee list is obtained, and the employee is added according to the queryed receiving field name.
  • the corresponding trusted field name is added to the employee list.
  • the mapping relationship between the service field name and the call field name is recorded in the docking configuration table.
  • the call field name corresponding to the service field name can be queried in the acceptance data, so that the service field name corresponding to the call data can be recorded in the service data table according to the queried call field name, thereby realizing the acceptance data and
  • the accurate docking between the business data enables the docked data to facilitate the insurance company to conduct business processing.
  • steps in the flowchart of FIG. 4 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIG. 4 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, and the execution of these sub-steps or stages The order is also not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.
  • a computer device comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to perform the step of: receiving the transmission by the enterprise terminal
  • the annuity business processing request carries the annuity plan logo and the enterprise information
  • the annuity business corresponding to the enterprise is opened according to the annuity plan logo and the enterprise information
  • the annuity payment request sent by the enterprise terminal is received, and the annuity payment request carries a plurality of employee identifications
  • the annuity payment record corresponding to the employee identification is added
  • the annuity income corresponding to the annuity business is obtained according to the preset time frequency
  • the income distribution record corresponding to the plurality of employee identifications is added according to the annuity income
  • the employee's identification and the account are carried in the annuity claim
  • the corresponding annuity payment record and income distribution record are obtained according to the employee
  • the processor when executing the computer readable instructions, further performs the steps of: obtaining an annuity information according to the annuity plan identifier, generating the first file using the annuity information; transmitting the first file to the plurality of employee terminals; and when the employee is pre
  • the confirmation information corresponding to the first file returned by the employee terminal is received; the first file has a corresponding random problem; if the confirmation information includes the digital signature and the answer to the random question; the digital signature and the random problem are utilized The answer is to verify the confirmation information; if the verification is passed, the confirmation information is counted, the statistical result of the employee participation is obtained, and the statistical result is sent to the enterprise terminal.
  • the processor further executes the following steps: generating a bill to be completed according to the annuity payment request, the bill to be completed has corresponding billing information; and querying whether the corresponding annuity account is not used according to the enterprise information.
  • Accounts, unused accounts have corresponding account information; if they exist, obtain the idle time of the database, and match the completed bills and unused accounts according to the bill information and the account information during the idle time of the database; if the matching is successful , the employee list is read, the employee list includes multiple employees, and the annuity payment accounting operation is performed on multiple employees by using the unused accounts.
  • the method further includes the steps of: receiving an employee new request sent by the enterprise terminal, the employee new request carrying the new employee list, and the newly added employee list including multiple new The corresponding field name of the employee; obtain the docking configuration table, record the trusted field name and the corresponding receiving field name in the docking configuration table, query the corresponding receiving field name in the newly added employee list according to the trusted field name; obtain the employee list, according to the query The name of the accepted field will be added to the employee list by adding the employee's corresponding trusted field name.
  • One or more non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of: receiving an annuity service sent by the enterprise terminal The request is processed; the annuity processing request carries the annuity plan logo and the enterprise information; the annuity business corresponding to the enterprise is opened according to the annuity plan logo and the enterprise information; and the annuity payment request sent by the enterprise terminal is received, and the annuity payment request carries a plurality of employee identifications; The annuity payment request adds an annuity payment record corresponding to the plurality of employee identifications; acquires an annuity income corresponding to the annuity business according to a preset time frequency, adds a revenue distribution record corresponding to the plurality of employee identifications according to the annuity income; and receives an annuity sent by the employee terminal When receiving the request, the annuity collection request carries the employee identification and the collection account; the corresponding annuity payment record and the income distribution record are obtained according
  • the computer readable instructions are further executed by the processor to: obtain an annuity information according to the annuity plan identifier, generate a first file using the annuity information; send the first file to the plurality of employee terminals; Receiving the confirmation information corresponding to the first file returned by the employee terminal when agreeing to participate in the annuity plan within the preset time period; the first file has a corresponding random problem; if the confirmation information includes the digital signature and the answer to the random question; using the digital signature and the random The answer to the question verifies the confirmation information; if the verification is passed, the confirmation information is counted, the statistical result of the employee participation is obtained, and the statistical result is sent to the enterprise terminal.
  • the computer readable instructions are further executed by the processor to: generate a bill to be completed according to the annuity payment request, the bill to be completed has corresponding billing information; and query whether the corresponding annuity account exists according to the enterprise information Using the account, the unused account has the corresponding account information; if it exists, the idle time of the database is obtained, and the completed bill and the unused account are matched according to the bill information and the account information during the idle time of the database; If successful, the employee list is read, the employee list includes multiple employees, and the annuity payment accounting operation is performed for multiple employees using the unused accounts.
  • the computer readable instructions are further executed by the processor to: receive an employee new request sent by the enterprise terminal, the employee new request carries a new employee list, and the newly added employee list includes multiple new Add the corresponding call field name of the employee; obtain the docking configuration table, record the trusted field name and the corresponding call field name in the docking configuration table, query the corresponding call field name in the newly added employee list according to the trusted field name; obtain the employee list, according to The name of the received call field will be added to the employee list.
  • Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory can include random access memory (RAM) or external cache memory.
  • RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • Synchlink DRAM SLDRAM
  • Memory Bus Radbus
  • RDRAM Direct RAM
  • DRAM Direct Memory Bus Dynamic RAM
  • RDRAM Memory Bus Dynamic RAM

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种年金管理系统，包括：年金受理系统，用于接收企业终端发送的年金业务办理请求；年金办理请求中携带了年金计划标识、企业信息和员工信息；年金受托系统，用于根据年金计划标识和企业信息开通年金业务；年金受理系统还用于接收企业终端发送的年金缴纳请求；账管系统，用于根据年金缴纳请求为多个员工进行年金缴纳记账操作；年金受托系统还用于获取年金业务对应的年金收益，账管系统还用于根据年金收益为多个员工进行年金收益分配记账操作；年金受理系统还用于员工终端发送的年金领取请求；年金受托系统还用于根据年金领取请求生成年金支付请求，将年金支付请求发送至托管终端。

Description

年金管理系统、方法、服务器和存储介质
本申请要求于2017年7月25日提交中国专利局，申请号为2017106129823，申请名称为“年金管理系统、方法、服务器和存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及一种年金管理系统、方法、服务器和存储介质。
背景技术
年金是指企业及其员工在依法参加基本养老保险的基础上，自愿建立的补充养老保险。年金包括企业缴费和员工个人缴费。年金也是一种较好的投资安排，越来越多的企业参与年金计划。但发明人意识到，目前缺乏可以对年金业务进行有效综合管理的系统，如果有较多的员工参与企业的年金计划，需要企业投入大量的人力，周期长，耗时又耗力。
发明内容
根据本申请公开的各种实施例，提供一种年金管理系统、方法、服务器和存储介质。
一种年金管理系统，包括：
年金受理系统，用于接收企业终端发送的年金业务办理请求；所述年金办理请求中携带了年金计划标识、企业信息和员工信息；
年金受托系统，用于根据所述年金计划标识和企业信息开通年金业务；
所述年金受理系统还用于接收企业终端发送的年金缴纳请求；
账管系统，用于根据所述年金缴纳请求为多个员工进行年金缴纳记账操作；
所述年金受托系统还用于获取所述年金业务对应的年金收益，所述账管系统还用于根据所述年金收益为多个员工进行年金收益分配记账操作；及
所述年金受理系统还用于接收员工终端发送的年金领取请求，所述年金领取请求中携带了领取账户；所述年金受托系统还用于根据所述年金领取请求计算相应的年金领取金额，根据所述年金领取金额和领取账户生成年金支付请求，将所述年金支付请求发送至托管终端，以使得托管终端向所述领取账户转入所述年金领取金额。
一种年金管理方法，包括：
接收企业终端发送的年金业务办理请求；所述年金办理请求中携带了年金计划标识和企业信息；根据所述年金计划标识和企业信息开通企业对应的年金业务；
接收企业终端发送的年金缴纳请求，所述年金缴纳请求携带了多个员工标识；根据所述年金缴纳请求添加多个员工标识对应的年金缴纳记录；
按照预设的时间频率获取所述年金业务对应的年金收益，根据所述年金收益添加多个 员工标识对应的收益分配记录；及
当接收到员工终端发送的年金领取请求时，所述年金领取请求中携带了员工标识和领取账户；根据所述员工标识获取对应的年金缴纳记录和收益分配记录，根据所述年金缴纳记录和收益分配记录计算相应的年金领取金额，根据所述年金领取金额和领取账户生成年金支付请求，将所述年金支付请求发送至托管终端，以使得托管终端向所述领取账户转入所述年金领取金额。
一种计算机设备，包括存储器和一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器执行以下步骤：
接收企业终端发送的年金业务办理请求；所述年金办理请求中携带了年金计划标识和企业信息；根据所述年金计划标识和企业信息开通企业对应的年金业务；
接收企业终端发送的年金缴纳请求，所述年金缴纳请求携带了多个员工标识；根据所述年金缴纳请求添加多个员工标识对应的年金缴纳记录；
按照预设的时间频率获取所述年金业务对应的年金收益，根据所述年金收益添加多个员工标识对应的收益分配记录；及
当接收到员工终端发送的年金领取请求时，所述年金领取请求中携带了员工标识和领取账户；根据所述员工标识获取对应的年金缴纳记录和收益分配记录，根据所述年金缴纳记录和收益分配记录计算相应的年金领取金额，根据所述年金领取金额和领取账户生成年金支付请求，将所述年金支付请求发送至托管终端，以使得托管终端向所述领取账户转入所述年金领取金额。
一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
接收企业终端发送的年金业务办理请求；所述年金办理请求中携带了年金计划标识和企业信息；根据所述年金计划标识和企业信息开通企业对应的年金业务；
接收企业终端发送的年金缴纳请求，所述年金缴纳请求携带了多个员工标识；根据所述年金缴纳请求添加多个员工标识对应的年金缴纳记录；
按照预设的时间频率获取所述年金业务对应的年金收益，根据所述年金收益添加多个员工标识对应的收益分配记录；及
当接收到员工终端发送的年金领取请求时，所述年金领取请求中携带了员工标识和领取账户；根据所述员工标识获取对应的年金缴纳记录和收益分配记录，根据所述年金缴纳记录和收益分配记录计算相应的年金领取金额，根据所述年金领取金额和领取账户生成年金支付请求，将所述年金支付请求发送至托管终端，以使得托管终端向所述领取账户转入所述年金领取金额。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为根据一个或多个实施例中的年金管理系统的应用环境图。
图2为根据一个或多个实施例中年金管理系统的结构示意图。
图3为根据一个或多个实施例中服务器的结构示意图。
图4为根据一个或多个实施例中年金管理方法的流程示意图框图。
具体实施方式
为了使本申请的技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
可以理解，本申请所使用的术语“第一”、“第二”等可在本文中用于描述各种元件，但这些元件不受这些术语限制。这些术语仅用于将第一个元件与另一个元件区分。举例来说，在不脱离本申请的范围的情况下，可以将第一客户端称为第二客户端，且类似地，可将第二客户端称为第一客户端。第一客户端和第二客户端两者都是客户端，但其不是同一客户端。
本申请实施例中所提供的年金管理系统可以应用于如图1所示的应用环境中。多个企业终端102通过网络与服务器104连接，多个员工终端106通过网络与服务器104连接，托管终端108通过网路与服务器104连接。当企业选择参与年金计划时，企业的管理人员可以通过企业终端102向服务器104发起年金业务办理请求。年金业务办理请求中携带了年金计划标识、企业信息和员工信息。服务器104根据年金计划标识和企业信息开通相应的年金业务。服务器104根据年金计划标识获取对应的年金信息，根据年金信息和员工信息对选择参加年金计划的员工进行统计，得到员工参与的统计结果。统计结果包括确认参与年金计划的员工清单。当企业需要给员工清单内的员工缴纳年金时，企业的管理人员可以通过企业终端102向服务器104发起年金缴纳请求。服务器104根据年金缴纳请求生成待完成账单，根据企业信息查询对应的年金账户是否存在与待完成账单匹配的账款，若存在，利用该笔账款对多个员工进行年金缴纳记账操作。当员工需要领取年金时，员工可以通过员工终端106向服务器104发起年金领取请求。年金领取请求中携带了领取账户。服务器104根据年金领取请求计算相应的年金领取金额，根据年金领取金额和领取账户生成年金支付请求，将年金支付请求发送至第三方银行工作人员对应的托管终端108。托管终端108根据年金支付请求将年金领取金额对应的账款转入领取账户。由此可以实现对年金业务的有效综合管理。
在其中一个实施例中，如图2所示，提供了一种年金管理系统，包括：年金受理系统202、年金受托系统204和账管系统206，其中：
年金受理系统202，用于接收企业终端发送的年金业务办理请求；年金办理请求中携带了年金计划标识、企业信息和员工信息。
年金受托系统204，用于根据年金计划标识和企业信息开通年金业务。年金受理系统202还用于接收企业终端发送的年金缴纳请求。
账管系统206，用于根据年金缴纳请求为多个员工进行年金缴纳记账操作。年金受托系统204还用于获取年金业务对应的年金收益，账管系统还用于根据年金收益为多个员工进行年金收益分配记账操作。年金受理系统202还用于员工终端发送的年金领取请求，年金领取请求中包括了领取账户；年金受托系统204还用于根据年金领取请求计算相应的年金领取金额，根据年金领取金额和领取账户生成年金支付请求，将年金支付请求发送至托管终端，以使得托管终端向领取账户转入年金领取金额。
年金管理系统可以运行在服务器上。年金管理系统可以对年金业务进行综合管理。具体的，当企业选择参加一项年金计划时，企业的管理人员可以通过企业终端向年金受理系统202发送年金业务办理请求。每项年金计划具有对应年金计划标识和年金信息。年金业务办理请求中携带了年金计划标识、企业信息和员工信息。年金计划标识可以是年金计划登记号等。企业信息包括企业标识。员工信息包括多个员工的基本信息，如员工姓名、性别、联系电话、电子邮箱等。
年金受理系统202将年金计划标识、企业信息和员工信息发送至年金受托系统204。年金受托系统204根据年金计划标识和企业信息开通相应的年金任务。多个企业可以参加同一项年金计划，保险公司给每项年金计划建立对应的年金账户。每个企业在需要给参与年金计划的员工缴纳年金时，可以按月、按季度或者按年通过企业终端将一笔或多笔账款从企业账户转入年金账户。年金账户中的多笔账款包括已使用账款和/或未使用账款。对于初始转入到年金账户中的账款，服务器将该账款标记为未使用账款。
年金受托系统204根据年金计划标识获取对应的年金信息，利用年金信息生成第一文件。第一文件为员工选择参与年金计划时需要进行确认的文件。年金受托系统204根据员工信息(联系电话或电子邮箱)将第一文件和对应的年金信息发送至多个员工终端。年金信息包括年金方案和年金知识等。员工可以通过员工终端对年金知识和年金方案进行了解，进而判断是否参与企业的年金计划。当员工在预设时间段内选择参与企业的年金计划时，员工可以通过员工终端对第一文件进行下载，输入第一文件对应的确认信息。确认信息可以包括数字签名、指纹信息、人脸图像或随机问题的答案等。随机问题是年金受托系统204根据第一文件随机生成的，具有对应的预设答案。员工终端将确认信息发送至年金受托系统204。年金受托系统204按照预设的校验规则对确认信息进行校验。例如，若确认信息包括数字签名和随机问题的答案，年金受托系统204获取员工对应的预存储的签名笔迹，将数字签名的签名笔迹与预存储的签名笔迹进行匹配；若匹配度达到第一阈值，且 随机问题的答案与预设答案一致，则校验通过。对员工终端返回的确认信息进行校验，可以避免他人恶意代替员工对第一文件进行确认，提高员工参与统计的真实有效性，可以减少企业管理人员需要对确认信息进行人工识别真伪的繁琐，进而可以减少企业管理人员对确认信息进行人工校验的负担。
若确认信息校验通过，则年金受托系统204对当前接收到的确认信息进行统计，得到员工参与的统计结果。员工参与的统计结果包括确认参与年金计划的员工清单、以及第一文件和对应的确认信息。年金受托系统204将员工参与的统计结果返回至企业终端。企业管理人员可以通过企业终端对第一文件和对应的确认信息进行下载，以对第一文件和对应的确认信息进行存档。企业管理人员可以通过企业终端给确认参与年金计划的员工缴纳年金。
当企业需要给参与企业计划的员工缴纳年金时，企业管理人员可以通过企业终端向年金受理系统202发送年金缴纳请求。年金缴纳请求携带了企业标识。年金受理系统202将年金缴纳请求发送至年金受托系统204。年金受托系统204根据年金缴纳请求读取员工清单。员工清单包括多个员工对应的员工标识和缴纳金额。员工标识用于唯一识别一个员工，可以是员工编号或身份证件号等。年金受托系统204根据企业标识和员工清单生成待完成账单。待完成账单具有对应的账单信息。账单信息包括账单标题和账单金额。账单标题用于标注该笔待完成账单的用途，包括企业标识和年金缴纳时间，如“A企业2016年9月份应缴年金账单”等。容易理解，账单金额等于多个员工对应的缴纳金额之和。
年金受托系统204根据企业标识获取对应的年金账户，在年金账户中查询是否存在未使用账款。若存在，则年金受托系统204对非工作时间段内数据库中的批处理任务执行状况和资源消耗状况进行监控，根据在非工作时间段内批处理任务的执行时间和资源消耗时间，筛选出能够避开多个批处理任务执行时间的资源消耗时间作为数据库的空闲时间。批处理任务包括待完成账单与未使用账款匹配以及年金缴纳记账等。年金受托系统204在数据库的空闲时间获取未使用账款的账款信息，根据账单信息和账款信息对待完成账单与未使用账款进行匹配。若匹配成功，则年金受托系统204读取员工清单，根据多个员工的缴纳金额将与待完成账单匹配的未使用账款分配给多个员工，将分配结果发送至账管系统206。账管系统206根据分配结果给每个员工标识添加对应的年金缴纳记录，从而完成多个员工的年金缴纳记账操作。年金缴纳记录可以作为员工领取年金的依据。
当员工达到国家规定的退休年龄或出境定居时，员工可以通过员工终端向企业申请领取年金。当员工需要领取年金时，员工可以通过员工终端向年金受理系统202发送年金领取请求。年金领取请求携带了员工身份信息和领取申请信息。领取申请信息包括领取信息，如领取账户、领取类型、领取周期、领取期数和/或每期领取金额等。其中，领取类型包括定期、定额和定期定额。领取周期包括一次性领取、按月领取、按季领取和按年领取等。员工可以在员工终端选择领取类型。年金受理系统202将年金领取请求发送至年金受托系统204。
年金受理系统202和年金受托系统204对员工身份信息进行验证。年金受理系统202和年金受托系统204可以通过视屏通话对员工身份信息进行验证。具体的，年金受理系统202接收员工通过员工终端发起的视屏通话请求，年金受托系统204根据视屏通话请求建立员工终端与管理终端之间的视频通话，接收员工在视频通话过程中通过员工终端上传的身份信息，获取员工对应的预存储的身份信息，将上传的身份信息与预存储的身份信息进行匹配；若匹配度达到预设阈值，则验证通过。若验证通过，年金受托系统204利用员工身份信息生成缴费记录查询任务，将缴费记录查询任务发送至账管系统206。账管系统206根据员工身份信息查询是否存在对应的年金缴纳记录，将查询结果返回至年金受托系统204。若查询结果为存在该员工的年金缴纳记录，年金受托系统204根据该员工的年金缴纳记录和领取申请信息，计算对应的年金领取金额和/或纳税金额。
年金受托系统204根据领取申请信息以及计算得到的年金领取金额和/或纳税金额，生成领取文件，将领取文件存储至数据库。在将当前的领取文件存储至数据库之前，数据库中可能已经存储了多个员工对应的领取文件。年金受托系统204统计数据库中存储的领取文件的数量，比较领取文件的统计数量是否达到第二阈值。若是，则年金受托系统204将数据库中存储的多个领取文件批量发送至企业终端。企业管理人员可以通过企业终端对多份领取文件进行统一审核，若审核通过，向年金受理系统202发送领取应答。年金受理系统202将领取应答发送至年金受托系统204。若领取应答为确认支付，年金受托系统204根据领取文件生成年金支付请求，将年金支付请求发送至托管终端。银行的工作人员可以通过托管终端将年金领取金额对应的账款从年金账户转入领取账户。
本实施例中，年金管理系统至少可以包括年金受理系统、年金受托系统和账管系统。年金受理系统和年金受托系统可以根据企业终端发起的年金业务办理请求为其开通相应的年金业务。企业通过企业终端为员工缴纳年金时，账管系统可以为多个员工进行年金缴纳记账操作。年金受托系统以及账管系统还可以根据年金业务对应的年金收益为企业的多个员工进行年金收益分配。当员工需要领取年金时，年金受理系统和年金受托系统可以根据员工的年金领取请求计算相应的年金领取金额，并且可以通过银行的托管终端直接向员工的领取账户转入该金额。该年金管理系统既可以为企业开通年金业务，又可以进行年金缴费，还可以进行年金收益分配以及年金领取等多种业务，由此实现了对年金业务的有效综合管理。
在其中一个实施例中，年金受理系统还用于接收企业终端发送的年金转保留请求，年金转保留请求携带了离职员工信息；年金受托系统还用于根据离职员工信息生成第二文件，将第二文件发送至离职员工对应的员工终端，接收员工终端返回的第二文件对应的确认信息，将确认信息发送至企业终端，以使得企业终端根据确认信息对离职员工办理年金转保留。
在员工离职后，企业可以对离职员工的年金作相应处理，如作转保留处理。当企业需要为离职员工办理年金转保留业务时，企业管理人员可以通过企业终端向年金受理系统 202发起年金转保留请求。年金转保留请求携带了离职员工信息。离职员工信息包括多位离职员工的基本信息和年金缴纳信息，如年金缴费账户，具体归属比例等。年金受理系统202将年金转保留请求发送至年金受托系统204。年金受托系统204根据离职员工信息生成年金余额查询请求，将年金余额查询请求发送至账管系统206。根据年金余额查询请求，账管系统206查询多个离职员工对应的年金缴费账户的当前总额。年金受托系统204根据离职员工的基本信息及其年金缴费账户的当前总额，针对每位离职员工生成一份第二文件。年金受托系统204生成通知信息，根据离职员工信息获取每位离职员工的联系方式，根据获取的联系方式将第二文件和通知信息发送至对应离职员工的员工终端，以提示离职员工及时对第二文件进行确认。
若离职员工在指定时间段内对第二文件中的内容有异议，可以通过员工终端向服务器返回第二文件对应的问题项，如“证件号码有误”或“归属比例有误”等。员工终端将问题项发送至年金受理系统202。年金受理系统202将问题项发送至企业终端。企业管理人员可以通过企业终端根据问题项修改离职员工信息。企业终端利用修改后的离职员工信息重新生成年金转保留请求，将重新生成的年金转保留请求发送至年金受理系统202。
若离职员工在指定时间段内对第二文件无异议，可以通过员工终端向年金受托系统204返回第二文件对应的确认信息。确认信息可以是数字签名、指纹信息或者人脸图像等，也可以是随机问题的答案。随机问题是服务器根据第一文件随机生成的，具有对应的预设答案。服务器可以采用上述实施例中提供的方式，对员工终端返回的确认信息进行校验。若确认信息校验通过，则年金受托系统204将第二文件和对应的确认信息发送至企业终端。根据第二文件和对应的确认信息，企业管理人员可以通过企业终端对离职员工办理年金转保留。
本实施例中，企业管理人员可以在企业终端发起年金转保留请求，根据年金转保留请求生成第二文件，将第二文件发送至员工终端，使得离职员工可以在员工终端对第二文件进行确认或者提出异议；当员工对第二文件存在异议时，可以通过员工终端发送问题项，将问题项反馈至企业终端；企业管理人员可以根据问题项在企业终端重新发起年金转保留请求，进而可以保证年金转保留请求的正确性，可以减少企业管理人员对离职员工信息进行人工确认的繁琐，进而可以有效减少企业管理人员在办理年金业务时的工作负担。
在其中一个实施例中，年金受托系统还用于在到达预设的收益分配周期时，查询年金账户是否存在年金收益，若存在，则计算企业的多个员工分别对应的收益分配金额；账款系统还用于根据收益分配金额为多个员工进行年金收益分配记账操作。
企业给员工缴纳年金后，保险公司将对应的年金账户中的账款用于投资，投资产生的收益按照企业规定分配给参与年金计划的员工。故年金不仅包括企业缴费和员工个人缴费，还包括年金收益，这就在企业的多个员工之间存在收益分配的问题。年金受托系统204预设了收益分配周期。收益分配周期包括多个时间节点。收益分配周期的时间长度可以是保险公司的管理人员根据不同的投资项目的持续时间设定的。年金受托系统204在每 个收益分配周期结束时进行一次收益分配。具体的，在到达预设的收益分配周期到达时，年金受托系统204查询年金账户是否存在年金收益，若存在，计算该企业的多个员工分别对应的年金收益。账款系统206根据每个员工对应的年金收益为相应员工进行年金收益分配记账操作。
在其中一个实施例中，年金受托系统还用于获取年金数据、第一分配模型和第二分配模型，利用年金数据和第一分配模型计算企业标识对应的年金收益；利用企业标识对应的年金收益和第二分配模型计算多个员工对应的年金收益。
在到达预设的收益分配周期时，年金受托系统204查询年金账户是否存在年金收益，若存在，年金受托系统204获取年金账户对应的多个企业的年金数据。收益分配周期包括多个时间节点。一个企业对应的年金数据包括该企业在收益分配周期开始前的初始年金金额以及在每个时间节点的年金变动金额。年金受托系统204获取第一模型，将年金收益和年金数据输入第一模型，计算得到每个企业对应的年金收益。一个企业对应的年金数据还包括该企业的多个员工在收益分配周期开始前的初始年金金额以及在每个时间节点的年金变动金额。年金受托系统204获取第二模型，将一个企业对应的年金收益和该企业的年金数据输入第二模型，计算得到该企业的多个员工对应的年金收益。年金受托系统204将计算得到的每个员工对应的年金收益发送至账管系统206。账管系统206根据每个员工对应的年金收益为对应的员工进行年金收益分配记账操作。
本实施例中，在预设的收益分配周期到达时，可以自动进行收益分配，减少保险公司管理人员需要人为进行收益分配的工作负担；通过将年金收益和年金数据输入第一模型计算每个企业对应的年金收益，通过将企业对应的年金收益和年金数据输入第二模型计算企业的多个员工对应的年金收益，可以提高年金收益计算的准确率，也可以提高年金收益的分配效率。
在其中一个实施例中，年金受理系统还用于接收企业终端发送的员工新增请求，员工新增请求携带了新增员工清单，新增员工清单包括多个新增员工对应的受理字段名；年金受托系统还用于获取对接配置表，对接配置表中记录了受托字段名和对应的受理字段名，根据受托字段名在新增员工清单中查询对应的受理字段名；获取员工清单，根据查询到的受理字段名将新增员工对应受托字段名添加至员工清单中。
保险公司为客户(企业或员工)办理不同的业务时，需要客户提供不同的数据。年金受理系统202接收客户通过企业终端或者员工终端提供的数据。客户提供的数据可以称为受理数据。受理数据的记录方式如果与保险公司所需的记录方式不同，保险公司无法直接使用客户提供的受理数据进行业务处理，还需要对客户提供的受理数据进行对接处理，以使得对接后的数据便于保险公司进行业务处理。年金受理系统202将受理数据发送至年金受托系统204。年金受托系统204在数据库中预先存储了录入配置表和对接配置表。录入配置表中记录了客户提供的多个受理字段名。对接配置表中记录了业务字段名和受理字段名。其中，业务字段名和一个或多个受理字段名之间具有映射关系。业务字段名可以是年 金受托系统204从上述员工清单中提取得到的。受理字段名可以是年金受托系统204从录入配置表中提取得到的。
当企业新增员工时，企业管理人员可以通过企业终端向年金受理系统202发起员工新增请求。员工新增请求携带了新增员工清单，新增员工清单包括多个新增员工对应的受理字段名，如名字、性别、身份证号、移动电话等。年金受理系统202将员工新增请求发送至年金受托系统204。年金受托系统204获取员工清单。员工清单中记录了多个业务字段名，如员工姓名、员工性别、证件号码、联系电话等。年金受托系统204获取对接配置表，在对接配置表中查询与员工清单中的业务字段名对应的受理字段名，利用该受理字段名在受理数据中查询相同的受理字段名。根据查询到的受理字段名，年金受托系统204将受理数据对应业务字段名添加至员工清单中。
本实施例中，由于对接配置表中记录了业务字段名与受理字段名之间的映射关系。利用该映射关系，可以在受理数据中查询与业务字段名对应的受理字段名，由此可以根据查询到的受理字段名将受理数据对应业务字段名记录至业务数据表中，从而实现了受理数据与业务数据之间的准确对接，能够使得对接后的数据便于保险公司进行业务处理。
在其中一个实施例中，年金受托系统还用于根据每个年金业务办理请求生成对应的年金任务，对年金任务进行处理，监测年金任务是否发生处理异常，若是，则获取年金任务在处理过程中记录的日志，将日志发送至管理终端。
年金受理系统202可以接收多个企业终端发送的年金业务办理请求。年金受理系统202将多个年金业务办理请求发送至年金受托系统204。年金受托系统204根据每个年金业务办理请求生成对应的年金任务，调用多个线程，批量处理多个年金任务，监测年金任务是否发生处理异常。若是，则年金受托系统204获取对应的年金任务在处理过程中记录的日志，将日志发送至管理终端。根据该日志，管理人员可以通过管理终端对发生处理异常的年金任务作人工处理，以保证每个年金任务可以得到有效的处理。
在一个实施例中，提供了一种服务器，如图3所示，该服务器包括通过系统总线连接的处理器、存储装置和网络接口。其中，该服务器的处理器用于提供计算和控制能力。该服务器的存储装置包括一个或多个非易失性存储介质、一个或多个内存储装置。该服务器的非易失性存储介质存储有操作系统、计算机可读指令和数据库，该计算机可读指令被处理器执行时以实现一种年金管理系统的功能，该数据库存储了多个员工的领取文件等。该服务器的内存储装置为非易失性存储介质中的操作系统和计算机可读指令的运行提供环境。该服务器的网络接口用于与外部的终端通过网络连接通信，比如，接收终端发送的年金业务办理请求等。
该服务器可以用独立的服务器来实现；也可以用多个服务器组成的服务器集群来实现。本领域技术人员可以理解，图3中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的服务器的限定，具体的服务器可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在其中一个实施例中，如图4所示，提供了一种年金管理方法，以该方法应用于服务器为例进行说明，具体包括以下步骤：
步骤402，接收企业终端发送的年金业务办理请求；年金办理请求中携带了年金计划标识和企业信息；根据年金计划标识和企业信息开通企业对应的年金业务；
步骤404，接收企业终端发送的年金缴纳请求，年金缴纳请求携带了多个员工标识；根据年金缴纳请求添加多个员工标识对应的年金缴纳记录；
步骤406，按照预设的时间频率获取年金业务对应的年金收益，根据年金收益添加多个员工标识对应的收益分配记录；
步骤408，当接收到员工终端发送的年金领取请求时，年金领取请求中携带了员工标识和领取账户；根据员工标识获取对应的年金缴纳记录和收益分配记录，根据年金缴纳记录和收益分配记录计算相应的年金领取金额，根据年金领取金额和领取账户生成年金支付请求，将年金支付请求发送至托管终端，以使得托管终端向领取账户转入年金领取金额。
服务器可以根据企业终端发起的年金业务办理请求为其开通相应的年金业务。企业通过企业终端为员工缴纳年金时，服务器可以为多个员工标识添加对应的年金缴纳记录。服务器还可以周期性根据年金业务对应的年金收益为多个员工标识添加对应的年金收益分配记录。当员工需要领取年金时，服务器可以根据员工的年金领取请求获取对应的年金缴纳记录和收益分配记录，根据年金缴纳记录和收益分配记录计算相应的年金领取金额，并且可以通过银行的托管终端直接向员工的领取账户转入该金额。
本实施例中，服务器通过为企业开通年金业务，为多个员工标识添加对应的年金缴纳记录以及收益分配记录，进而当员工需要领取年金时，可以通过员工终端向服务器发送年金领取请求，服务器可以利用年金缴纳记录和收益分配记录计算该员工的年金领取金额，通过银行的托管终端可以直接向员工的领取账户转入该年金领取金额。由此，不仅可以实现对年金业务的有效综合管理，还可以为员工领取年金提供方便。
在其中一个实施例中，该方法还包括：根据年金计划标识获取年金信息，利用年金信息生成第一文件；将第一文件发送至多个员工终端；当员工在预设时间段内同意参与年金计划时，接收员工终端返回的第一文件对应的确认信息；第一文件具有对应的随机问题；若确认信息包括数字签名和随机问题的答案；利用数字签名和随机问题的答案对确认信息进行校验；若校验通过，对确认信息进行统计，得到员工参与的统计结果，将统计结果发送至企业终端。
服务器可以根据企业终端的年金业务办理请求，自动对参与年金计划的员工进行统计。统计过程中，服务器对员工终端返回的确认信息进行校验，可以避免他人恶意代替员工对第一文件进行确认，提高员工参与统计的真实有效性，可以减少企业管理人员需要对确认信息进行人工识别真伪的繁琐，进而可以减少企业管理人员对确认信息进行人工校验的负担。
在其中一个实施例中，该方法还包括：根据年金缴纳请求生成待完成账单，待完成账 单具有对应的账单信息；根据企业信息查询对应的年金账户是否存在未使用账款，未使用账款具有对应的账款信息；若存在，获取数据库的空闲时间，在数据库的空闲时间内根据账单信息和账款信息对待完成账单和未使用账款进行匹配；若匹配成功，则读取员工清单，员工清单中包括多个员工；利用未使用账款对多个员工进行年金缴纳记账操作。
服务器可以根据企业终端的年金缴纳请求，自动对待完成账单和未使用账款进行匹配，从而可以为多个员工的年金缴纳记账操作。更重要的是，待完成账单和未使用账款的匹配以及程年金缴纳记账操作均是在数据库的空闲时间进行，可以减少服务器资源的占用。
在其中一个实施例中，该方法还包括：接收企业终端发送的员工新增请求，员工新增请求携带了新增员工清单，新增员工清单包括多个新增员工对应的受理字段名；获取对接配置表，对接配置表中记录了受托字段名和对应的受理字段名，根据受托字段名在新增员工清单中查询对应的受理字段名；获取员工清单，根据查询到的受理字段名将新增员工对应受托字段名添加至员工清单中。
本实施例中，由于对接配置表中记录了业务字段名与受理字段名之间的映射关系。利用该映射关系，可以在受理数据中查询与业务字段名对应的受理字段名，由此可以根据查询到的受理字段名将受理数据对应业务字段名记录至业务数据表中，从而实现了受理数据与业务数据之间的准确对接，能够使得对接后的数据便于保险公司进行业务处理。
应该理解的是，虽然图4的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图4中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
一种计算机设备，包括存储器和一个或多个处理器，存储器中储存有计算机可读指令，计算机可读指令被处理器执行时，使得一个或多个处理器执行以下步骤：接收企业终端发送的年金业务办理请求；年金办理请求中携带了年金计划标识和企业信息；根据年金计划标识和企业信息开通企业对应的年金业务；接收企业终端发送的年金缴纳请求，年金缴纳请求携带了多个员工标识；根据年金缴纳请求添加多个员工标识对应的年金缴纳记录；按照预设的时间频率获取年金业务对应的年金收益，根据年金收益添加多个员工标识对应的收益分配记录；当接收到员工终端发送的年金领取请求时，年金领取请求中携带了员工标识和领取账户；根据员工标识获取对应的年金缴纳记录和收益分配记录，根据年金缴纳记录和收益分配记录计算相应的年金领取金额，根据年金领取金额和领取账户生成年金支付请求，将年金支付请求发送至托管终端，以使得托管终端向领取账户转入年金领取金额。
在其中一个实施例中，处理器执行计算机可读指令时还执行以下步骤：根据年金计划 标识获取年金信息，利用年金信息生成第一文件；将第一文件发送至多个员工终端；当员工在预设时间段内同意参与年金计划时，接收员工终端返回的第一文件对应的确认信息；第一文件具有对应的随机问题；若确认信息包括数字签名和随机问题的答案；利用数字签名和随机问题的答案对确认信息进行校验；若校验通过，对确认信息进行统计，得到员工参与的统计结果，将统计结果发送至企业终端。
在其中一个实施例中，处理器执行计算机可读指令时还执行以下步骤：根据年金缴纳请求生成待完成账单，待完成账单具有对应的账单信息；根据企业信息查询对应的年金账户是否存在未使用账款，未使用账款具有对应的账款信息；若存在，获取数据库的空闲时间，在数据库的空闲时间内根据账单信息和账款信息对待完成账单和未使用账款进行匹配；若匹配成功，则读取员工清单，员工清单中包括多个员工；利用未使用账款对多个员工进行年金缴纳记账操作。
在其中一个实施例中，处理器执行计算机可读指令时还执行以下步骤：接收企业终端发送的员工新增请求，员工新增请求携带了新增员工清单，新增员工清单包括多个新增员工对应的受理字段名；获取对接配置表，对接配置表中记录了受托字段名和对应的受理字段名，根据受托字段名在新增员工清单中查询对应的受理字段名；获取员工清单，根据查询到的受理字段名将新增员工对应受托字段名添加至员工清单中。
一个或多个存储有计算机可读指令的非易失性存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：接收企业终端发送的年金业务办理请求；年金办理请求中携带了年金计划标识和企业信息；根据年金计划标识和企业信息开通企业对应的年金业务；接收企业终端发送的年金缴纳请求，年金缴纳请求携带了多个员工标识；根据年金缴纳请求添加多个员工标识对应的年金缴纳记录；按照预设的时间频率获取年金业务对应的年金收益，根据年金收益添加多个员工标识对应的收益分配记录；当接收到员工终端发送的年金领取请求时，年金领取请求中携带了员工标识和领取账户；根据员工标识获取对应的年金缴纳记录和收益分配记录，根据年金缴纳记录和收益分配记录计算相应的年金领取金额，根据年金领取金额和领取账户生成年金支付请求，将年金支付请求发送至托管终端，以使得托管终端向领取账户转入年金领取金额。
在其中一个实施例中，计算机可读指令被处理器执行时还执行以下步骤：根据年金计划标识获取年金信息，利用年金信息生成第一文件；将第一文件发送至多个员工终端；当员工在预设时间段内同意参与年金计划时，接收员工终端返回的第一文件对应的确认信息；第一文件具有对应的随机问题；若确认信息包括数字签名和随机问题的答案；利用数字签名和随机问题的答案对确认信息进行校验；若校验通过，对确认信息进行统计，得到员工参与的统计结果，将统计结果发送至企业终端。
在其中一个实施例中，计算机可读指令被处理器执行时还执行以下步骤：根据年金缴纳请求生成待完成账单，待完成账单具有对应的账单信息；根据企业信息查询对应的年金账户是否存在未使用账款，未使用账款具有对应的账款信息；若存在，获取数据库的空闲 时间，在数据库的空闲时间内根据账单信息和账款信息对待完成账单和未使用账款进行匹配；若匹配成功，则读取员工清单，员工清单中包括多个员工；利用未使用账款对多个员工进行年金缴纳记账操作。
在其中一个实施例中，计算机可读指令被处理器执行时还执行以下步骤：接收企业终端发送的员工新增请求，员工新增请求携带了新增员工清单，新增员工清单包括多个新增员工对应的受理字段名；获取对接配置表，对接配置表中记录了受托字段名和对应的受理字段名，根据受托字段名在新增员工清单中查询对应的受理字段名；获取员工清单，根据查询到的受理字段名将新增员工对应受托字段名添加至员工清单中。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种年金管理系统，包括：
    年金受理系统，用于接收企业终端发送的年金业务办理请求；所述年金办理请求中携带了年金计划标识、企业信息和员工信息；
    年金受托系统，用于根据所述年金计划标识和企业信息开通年金业务；
    所述年金受理系统还用于接收企业终端发送的年金缴纳请求；
    账管系统，用于根据所述年金缴纳请求为多个员工进行年金缴纳记账操作；
    所述年金受托系统还用于获取所述年金业务对应的年金收益，所述账管系统还用于根据所述年金收益为多个员工进行年金收益分配记账操作；及
    所述年金受理系统还用于接收员工终端发送的年金领取请求，所述年金领取请求中携带了领取账户；所述年金受托系统还用于根据所述年金领取请求计算相应的年金领取金额，根据所述年金领取金额和领取账户生成年金支付请求，将所述年金支付请求发送至托管终端，以使得托管终端向所述领取账户转入所述年金领取金额。
  2. 根据权利要求1所述的系统，其特征在于，所述年金受托系统还用于根据所述年金计划标识获取年金信息，利用年金信息生成第一文件；所述年金受理系统还用于将所述第一文件发送至多个员工终端，当员工在预设时间段内同意参与年金计划时，接收员工终端返回的第一文件对应的确认信息；第一文件具有对应的随机问题；若确认信息包括数字签名和所述随机问题的答案，所述年金受托系统还用于利用所述数字签名和所述随机问题的答案对所述确认信息进行校验，若校验通过，对确认信息进行统计，得到员工参与的统计结果，将所述统计结果发送至企业终端。
  3. 根据权利要求1所述的系统，其特征在于，所述年金受托系统还用于根据所述年金缴纳请求生成待完成账单，所述待完成账单具有对应的账单信息；根据企业信息查询对应的年金账户是否存在未使用账款，所述未使用账款具有对应的账款信息；若存在，获取数据库的空闲时间，在所述数据库的空闲时间内根据账单信息和账款信息对待完成账单和未使用账款进行匹配，若匹配成功，则读取员工清单，所述员工清单中包括多个员工；所述账管系统还用于利用未使用账款对多个员工进行年金缴纳记账操作。
  4. 根据权利要求1所述的系统，其特征在于，所述企业信息包括企业标识；所述年金受托系统还用于在到达预设的收益分配周期时，查询年金账户是否存在年金收益，若存在，则获取年金数据、第一分配模型和第二分配模型，利用所述年金数据和第一分配模型计算企业标识对应的年金收益；利用企业标识对应的年金收益和第二分配模型计算多个员工对应的年金收益；所述账款系统还用于根据年金收益为多个员工进行年金收益分配记账操作。
  5. 根据权利要求1所述的系统，其特征在于，所述年金受理系统还用于接收企业终端发送的员工新增请求，所述员工新增请求携带了新增员工清单，所述新增员工清单包括多个新增员工对应的受理字段名；所述年金受托系统还用于获取对接配置表，所述对接配 置表中记录了受托字段名和对应的受理字段名，根据受托字段名在新增员工清单中查询对应的受理字段名；获取员工清单，根据查询到的受理字段名将新增员工对应受托字段名添加至所述员工清单中。
  6. 根据权利要求1所述的系统，其特征在于，所述年金受托系统还用于根据年金业务办理请求生成对应的年金任务，对年金任务进行处理，监测年金任务是否发生处理异常，若是，则获取年金任务在处理过程中记录的日志，将所述日志发送至管理终端。
  7. 一种年金管理方法，包括：
    接收企业终端发送的年金业务办理请求；所述年金办理请求中携带了年金计划标识和企业信息；根据所述年金计划标识和企业信息开通企业对应的年金业务；
    接收企业终端发送的年金缴纳请求，所述年金缴纳请求携带了多个员工标识；根据所述年金缴纳请求添加多个员工标识对应的年金缴纳记录；
    按照预设的时间频率获取所述年金业务对应的年金收益，根据所述年金收益添加多个员工标识对应的收益分配记录；
    当接收到员工终端发送的年金领取请求时，所述年金领取请求中携带了员工标识和领取账户；根据所述员工标识获取对应的年金缴纳记录和收益分配记录，根据所述年金缴纳记录和收益分配记录计算相应的年金领取金额，根据所述年金领取金额和领取账户生成年金支付请求，将所述年金支付请求发送至托管终端，以使得托管终端向所述领取账户转入所述年金领取金额。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    根据所述年金计划标识获取年金信息，利用年金信息生成第一文件；
    将所述第一文件发送至多个员工终端；当员工在预设时间段内同意参与年金计划时，接收员工终端返回的第一文件对应的确认信息；第一文件具有对应的随机问题；若确认信息包括数字签名和所述随机问题的答案；
    利用所述数字签名和所述随机问题的答案对所述确认信息进行校验；
    若校验通过，对确认信息进行统计，得到员工参与的统计结果，将所述统计结果发送至企业终端。
  9. 一种服务器，包括存储器及一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：
    接收企业终端发送的年金业务办理请求；所述年金办理请求中携带了年金计划标识、企业信息和员工信息；根据所述年金计划标识和企业信息开通年金业务；
    接收企业终端发送的年金缴纳请求，根据所述年金缴纳请求为多个员工进行年金缴纳记账操作；
    获取所述年金业务对应的年金收益，所述账管系统还用于根据所述年金收益为多个员工进行年金收益分配记账操作；及
    接收员工终端发送的年金领取请求，所述年金领取请求中携带了领取账户；所述年金受托系统还用于根据所述年金领取请求计算相应的年金领取金额，根据所述年金领取金额和领取账户生成年金支付请求，将所述年金支付请求发送至托管终端，以使得托管终端向所述领取账户转入所述年金领取金额。
  10. 根据权利要求9所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：根据所述年金计划标识获取年金信息，利用年金信息生成第一文件；将所述第一文件发送至多个员工终端，当员工在预设时间段内同意参与年金计划时，接收员工终端返回的第一文件对应的确认信息；第一文件具有对应的随机问题；若确认信息包括数字签名和所述随机问题的答案，利用所述数字签名和所述随机问题的答案对所述确认信息进行校验，若校验通过，对确认信息进行统计，得到员工参与的统计结果，将所述统计结果发送至企业终端。
  11. 根据权利要求9所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：根据所述年金缴纳请求生成待完成账单，所述待完成账单具有对应的账单信息；根据企业信息查询对应的年金账户是否存在未使用账款，所述未使用账款具有对应的账款信息；若存在，获取数据库的空闲时间，在所述数据库的空闲时间内根据账单信息和账款信息对待完成账单和未使用账款进行匹配，若匹配成功，则读取员工清单，所述员工清单中包括多个员工；及利用未使用账款对多个员工进行年金缴纳记账操作。
  12. 根据权利要求9所述的服务器，其特征在于，所述企业信息包括企业标识；所述处理器执行所述计算机可读指令时还执行以下步骤：在到达预设的收益分配周期时，查询年金账户是否存在年金收益，若存在，则获取年金数据、第一分配模型和第二分配模型，利用所述年金数据和第一分配模型计算企业标识对应的年金收益；利用企业标识对应的年金收益和第二分配模型计算多个员工对应的年金收益；及根据年金收益为多个员工进行年金收益分配记账操作。
  13. 根据权利要求9所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：接收企业终端发送的员工新增请求，所述员工新增请求携带了新增员工清单，所述新增员工清单包括多个新增员工对应的受理字段名；获取对接配置表，所述对接配置表中记录了受托字段名和对应的受理字段名，根据受托字段名在新增员工清单中查询对应的受理字段名；及获取员工清单，根据查询到的受理字段名将新增员工对应受托字段名添加至所述员工清单中。
  14. 根据权利要求9所述的服务器，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：根据年金业务办理请求生成对应的年金任务，对年金任务进行处理，监测年金任务是否发生处理异常，若是，则获取年金任务在处理过程中记录的日志，将所述日志发送至管理终端。
  15. 一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：
    接收企业终端发送的年金业务办理请求；所述年金办理请求中携带了年金计划标识、企业信息和员工信息；根据所述年金计划标识和企业信息开通年金业务；
    接收企业终端发送的年金缴纳请求，根据所述年金缴纳请求为多个员工进行年金缴纳记账操作；
    获取所述年金业务对应的年金收益，所述账管系统还用于根据所述年金收益为多个员工进行年金收益分配记账操作；及
    接收员工终端发送的年金领取请求，所述年金领取请求中携带了领取账户；所述年金受托系统还用于根据所述年金领取请求计算相应的年金领取金额，根据所述年金领取金额和领取账户生成年金支付请求，将所述年金支付请求发送至托管终端，以使得托管终端向所述领取账户转入所述年金领取金额。
  16. 根据权利要求15所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：根据所述年金计划标识获取年金信息，利用年金信息生成第一文件；将所述第一文件发送至多个员工终端，当员工在预设时间段内同意参与年金计划时，接收员工终端返回的第一文件对应的确认信息；第一文件具有对应的随机问题；若确认信息包括数字签名和所述随机问题的答案，利用所述数字签名和所述随机问题的答案对所述确认信息进行校验，若校验通过，对确认信息进行统计，得到员工参与的统计结果，将所述统计结果发送至企业终端。
  17. 根据权利要求15所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：根据所述年金缴纳请求生成待完成账单，所述待完成账单具有对应的账单信息；根据企业信息查询对应的年金账户是否存在未使用账款，所述未使用账款具有对应的账款信息；若存在，获取数据库的空闲时间，在所述数据库的空闲时间内根据账单信息和账款信息对待完成账单和未使用账款进行匹配，若匹配成功，则读取员工清单，所述员工清单中包括多个员工；及利用未使用账款对多个员工进行年金缴纳记账操作。
  18. 根据权利要求15所述的存储介质，其特征在于，所述企业信息包括企业标识；所述计算机可读指令被所述处理器执行时还执行以下步骤：在到达预设的收益分配周期时，查询年金账户是否存在年金收益，若存在，则获取年金数据、第一分配模型和第二分配模型，利用所述年金数据和第一分配模型计算企业标识对应的年金收益；利用企业标识对应的年金收益和第二分配模型计算多个员工对应的年金收益；及根据年金收益为多个员工进行年金收益分配记账操作。
  19. 根据权利要求15所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：接收企业终端发送的员工新增请求，所述员工新增请求携带了新增员工清单，所述新增员工清单包括多个新增员工对应的受理字段名；获取对接配置表，所述对接配置表中记录了受托字段名和对应的受理字段名，根据受托字段名在新增员工清单中查询对应的受理字段名；及获取员工清单，根据查询到的受理字段名将新增员工 对应受托字段名添加至所述员工清单中。
  20. 根据权利要求15所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：根据年金业务办理请求生成对应的年金任务，对年金任务进行处理，监测年金任务是否发生处理异常，若是，则获取年金任务在处理过程中记录的日志，将所述日志发送至管理终端。
PCT/CN2018/085042 2017-07-25 2018-04-28 年金管理系统、方法、服务器和存储介质 Ceased WO2019019750A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710612982.3A CN108510397A (zh) 2017-07-25 2017-07-25 年金管理系统、方法、服务器和存储介质
CN201710612982.3 2017-07-25

Publications (1)

Publication Number Publication Date
WO2019019750A1 true WO2019019750A1 (zh) 2019-01-31

Family

ID=63374262

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085042 Ceased WO2019019750A1 (zh) 2017-07-25 2018-04-28 年金管理系统、方法、服务器和存储介质

Country Status (2)

Country Link
CN (1) CN108510397A (zh)
WO (1) WO2019019750A1 (zh)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109818962B (zh) * 2019-01-31 2021-07-09 泰康保险集团股份有限公司 业务数据处理方法及装置、电子设备、存储介质
CN109816176A (zh) * 2019-02-22 2019-05-28 泰康保险集团股份有限公司 年金数据处理方法、装置、介质及电子设备
CN109886692B (zh) * 2019-03-08 2021-05-07 泰康保险集团股份有限公司 基于区块链的数据传输方法、装置、介质及电子设备
CN109934695B (zh) * 2019-03-14 2021-08-06 泰康保险集团股份有限公司 年金业务中自动生成到账凭证的方法、系统、设备及介质
CN110111209A (zh) * 2019-05-05 2019-08-09 泰康保险集团股份有限公司 支付通知业务的处理方法、装置及可读存储介质
CN110796437A (zh) * 2019-11-04 2020-02-14 泰康保险集团股份有限公司 业务处理方法、装置、设备及存储介质
KR102105553B1 (ko) * 2019-11-06 2020-04-28 김창훈 스마트 연금 운영 시스템 및 그 구동방법
CN111192148B (zh) * 2019-11-25 2023-07-07 泰康保险集团股份有限公司 一种跨平台的数据处理方法及装置、电子设备、存储介质
CN111680064B (zh) * 2020-05-25 2023-09-08 泰康保险集团股份有限公司 年金余额信息的查询方法及装置
CN111681117B (zh) * 2020-05-25 2023-09-12 泰康保险集团股份有限公司 一种待遇支付系统、方法及装置
CN111626882B (zh) * 2020-05-28 2022-07-19 泰康保险集团股份有限公司 数据检测方法、装置、计算机可读介质及电子设备
CN111859041B (zh) * 2020-07-24 2023-07-18 中国工商银行股份有限公司 数据报送方法及装置
CN112085601A (zh) * 2020-09-04 2020-12-15 泰康保险集团股份有限公司 年金数据处理方法、装置、介质及电子设备
CN112163846A (zh) * 2020-10-19 2021-01-01 泰康保险集团股份有限公司 基于区块链的支付方案确定方法及装置、系统
CN112163959A (zh) * 2020-10-19 2021-01-01 泰康保险集团股份有限公司 基于区块链的年金投资方案确定方法及装置、系统、设备
CN112926971B (zh) * 2021-03-23 2023-03-21 支付宝（中国）网络技术有限公司 基于储值卡的支付方法及装置
CN113706108B (zh) * 2021-08-27 2025-05-13 中国建设银行股份有限公司 公积金缴存方法、装置、电子设备及计算机可读介质
CN114529418A (zh) * 2022-01-14 2022-05-24 富途网络科技(深圳)有限公司 基于esop系统的数据处理方法、装置、介质及设备
CN115114978B (zh) * 2022-06-20 2025-03-25 泰康保险集团股份有限公司 企业分类方法、装置、电子设备及可读介质
CN115719280B (zh) * 2022-11-30 2025-10-31 泰康保险集团股份有限公司 基于年金账户的返点确定方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040153390A1 (en) * 2003-01-30 2004-08-05 Saulys Vincent V. Automated financial instrument exchange apparatus and systems
CN101551893A (zh) * 2008-03-31 2009-10-07 乔美国际网路股份有限公司 年金契约的系统与由年金契约的系统所执行的方法
CN102629362A (zh) * 2012-03-02 2012-08-08 浪潮集团山东通用软件有限公司 一种企业年金账户管理系统中实现灵活账户结构的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040153390A1 (en) * 2003-01-30 2004-08-05 Saulys Vincent V. Automated financial instrument exchange apparatus and systems
CN101551893A (zh) * 2008-03-31 2009-10-07 乔美国际网路股份有限公司 年金契约的系统与由年金契约的系统所执行的方法
CN102629362A (zh) * 2012-03-02 2012-08-08 浪潮集团山东通用软件有限公司 一种企业年金账户管理系统中实现灵活账户结构的方法

Also Published As

Publication number Publication date
CN108510397A (zh) 2018-09-07

Similar Documents

Publication Publication Date Title
WO2019019750A1 (zh) 年金管理系统、方法、服务器和存储介质
US10564936B2 (en) Data processing systems for identity validation of data subject access requests and related methods
CN109472678B (zh) 一种基于区块链的会计账本管理方法、电子装置及可读存储介质
WO2019019744A1 (zh) 理赔流程识别方法、装置、服务器和存储介质
WO2019019447A1 (zh) 年金数据处理方法、装置、服务器和存储介质
CN109636558B (zh) 基于区块链的员工数据处理方法、装置及系统
WO2019019748A1 (zh) 年金业务处理方法、系统、服务器和存储介质
US12413599B2 (en) Systems, methods, apparatuses and computer program products for executing data verification operations between independent computing resources
WO2020233310A1 (zh) 实时处理数据的异步补偿方法、装置、设备及存储介质
US20210012355A1 (en) Systems and methods for vendor onboarding
US20170024695A1 (en) System and method for systematic presentation and ordering of documents based on triggers
CN111368327A (zh) 数据共享方法、装置、电子设备及可读存储介质
CN115115443A (zh) 保单补录方法、装置、电子设备和存储介质
CN113449497A (zh) 业务申请表填写方法及装置
CN110602215A (zh) 基于联盟区块链的资源处理方法及联盟区块链系统
CN108242021B (zh) 一种账务数据的处理系统、方法及装置
US10970741B2 (en) Method and system for integrating audience data with a social media site
CN113421053A (zh) 业务管理方法、系统、及计算机可读存储介质
CN114842479B (zh) 账单的管理方法及其装置、电子设备及存储介质
US20190266675A1 (en) Methods, system, application for medical mileage transportation tracking and reimbursement
CN117808440B (zh) 基于云服务的协同价格作业分配和编排方法及装置
US20240311908A1 (en) Systems and methods for providing digital trusted data
US20220335385A1 (en) System and method for systematic presentation and ordering of documents based on triggers
CN113869886B (zh) 数据处理方法、装置、电子设备、介质和计算机程序
RU2718736C1 (ru) Система электронного документооборота и способ управления системой электронного документооборота

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18837657

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18837657

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC , EPO FORM 1205A DATED 04.08.2020.

122 Ep: pct application non-entry in european phase

Ref document number: 18837657

Country of ref document: EP

Kind code of ref document: A1