CN110889771A - Account processing method and device, electronic equipment and computer readable medium - Google Patents
Account processing method and device, electronic equipment and computer readable medium Download PDFInfo
- Publication number
- CN110889771A CN110889771A CN201911047353.6A CN201911047353A CN110889771A CN 110889771 A CN110889771 A CN 110889771A CN 201911047353 A CN201911047353 A CN 201911047353A CN 110889771 A CN110889771 A CN 110889771A
- Authority
- CN
- China
- Prior art keywords
- enterprise
- annuity
- target member
- account
- information
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 21
- 238000012545 processing Methods 0.000 claims abstract description 120
- 238000000034 method Methods 0.000 claims abstract description 46
- 230000008569 process Effects 0.000 claims abstract description 25
- 230000008859 change Effects 0.000 claims description 13
- 238000012546 transfer Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 9
- 230000008520 organization Effects 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
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)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application discloses an account processing method and device, electronic equipment and a computer readable medium. An embodiment of the method comprises: receiving a service processing request for enterprise annuity service, wherein the service processing request comprises target member information and enterprise information of an enterprise to which a target member belongs; determining the business type of the enterprise annuity business; and determining an account processing strategy based on the service type, the target member information and the enterprise information, and processing the enterprise annuity account of the target member in the annuity management system based on the account processing strategy when the enterprise annuity service is processed. This embodiment reduces the risk of errors in the data processing process.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to an account processing method, an account processing device, electronic equipment and a computer readable medium.
Background
The enterprise annuity refers to a supplementary endowment insurance system which is voluntarily established by enterprises and workers on the basis of taking part in basic endowment insurance according to law. Enterprise annuity business operations often involve the following four-party organization: the system comprises a receiving mechanism, a trusteeship mechanism, an account management mechanism and a cast management mechanism. The trusted organization is an organization that accepts entrustment of an enterprise (i.e., a trusted person) and manages an annual account of the enterprise. The trusted authority may maintain an annuity management system to manage enterprise annuity accounts for each member of each enterprise. Before enterprise annuity policy changes, the same member can establish enterprise annuity accounts in different enterprises or different branches of the same enterprise respectively, and different enterprises can carry out enterprise annuity payment on the same enterprise respectively. After the enterprise annuity policy is changed, the same member is not allowed to establish enterprise annuity accounts in different enterprises or different branches of the same enterprise, so that data (such as information in the enterprise annuity accounts and accounts) in the annuity management system needs to be processed to meet policy requirements.
In the existing mode, repeated enterprise annuity accounts in an annuity management system are required to be inquired usually, and then the repeated enterprise annuity accounts are directly merged, deleted and the like. However, in this way, the processing of the enterprise annuity business needs to be suspended in the process of processing the annuity account, and the risk of error of the account data is high.
Disclosure of Invention
The embodiment of the application provides an account processing method and device, electronic equipment and a computer readable medium, so that the annual fund account of an enterprise is processed in the process of processing the annual fund business of the enterprise, and the risk of error of account data is reduced.
In a first aspect, an embodiment of the present application provides an account processing method, where the method includes: receiving a service processing request for enterprise annuity service, wherein the service processing request comprises target member information and enterprise information of an enterprise to which a target member belongs; determining the business type of the enterprise annuity business; and determining an account processing strategy based on the service type, the target member information and the enterprise information, and processing the enterprise annuity account of the target member in the annuity management system based on the account processing strategy when the enterprise annuity service is processed.
In a second aspect, an embodiment of the present application provides an account processing apparatus, including: the system comprises a receiving unit and a processing unit, wherein the receiving unit is configured to receive a business processing request for an enterprise annuity business, and the business processing request comprises target member information and enterprise information of an enterprise to which a target member belongs; a determining unit configured to determine a service type of an enterprise annuity service; and the processing unit is configured to determine an account processing strategy based on the service type, the target member information and the enterprise information, and process the enterprise annuity account of the target member in the annuity management system based on the account processing strategy when the enterprise annuity service is processed.
In a third aspect, an embodiment of the present application provides an electronic device, including: one or more processors; storage means having one or more programs stored thereon which, when executed by one or more processors, cause the one or more processors to carry out the method as described in the first aspect above.
In a fourth aspect, embodiments of the present application provide a computer-readable medium on which a computer program is stored, which when executed by a processor, implements the method as described in the first aspect above.
According to the account processing method, the account processing device, the electronic equipment and the computer readable medium, the business processing request of the enterprise annuity business is received, then the business type of the enterprise annuity business is determined, finally the account processing strategy of the target member is determined based on the business type, the target member information in the business processing request and the enterprise information of the enterprise to which the target member belongs, and the enterprise annuity account of the target member in the annuity management system is processed by using the account processing strategy when the enterprise annuity business is processed. Therefore, the related enterprise annuity accounts in the annuity management system can be processed in the normal processing process of the enterprise annuity business, the data in the annuity management system can be gradually updated, and the error risk in the data processing process is reduced.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is a flow diagram of one embodiment of an account processing method according to the present application;
FIG. 2 is a flow diagram of yet another embodiment of an account processing method according to the present application;
FIG. 3 is a flow diagram of yet another embodiment of an account processing method according to the present application;
FIG. 4 is a schematic block diagram of one embodiment of an account processing apparatus according to the present application;
FIG. 5 is a schematic block diagram of a computer system suitable for use in implementing an electronic device according to embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Referring to FIG. 1, a flow 100 of one embodiment of an account processing method according to the present application is shown.
The account processing method can be applied to various electronic devices such as a server, a desktop computer and the like. The electronic device may be deployed at a trusted authority. The trusted authority is an authority that accepts entrustment of an enterprise (i.e., a trusted person) and manages an annual account of the enterprise.
The electronic device may be operated with an annuity management system. The trusted authority may maintain an annuity management system to manage enterprise annuity accounts for each member of each enterprise.
Before enterprise annuity policy changes, the same member can establish enterprise annuity accounts in different enterprises or different branches of the same enterprise respectively, and different enterprises can carry out enterprise annuity payment on the same enterprise respectively. For example, if a company is affiliated with group a, a1 subsidiary under the group a, and a group B company, the group a1 subsidiary, and the group B company may each establish account information for the company and pay an annual fee for the company. At this time, an enterprise annuity account exists in the annuity management system at one of the three institutions.
However, after the enterprise annuity policy is changed, the same member is not allowed to establish enterprise annuity accounts in different enterprises or different branches of the same enterprise. Continuing with the above example, there is only one organization in group a, group a1 subsidiary and group B enterprises that can establish account information and pay annuity fees for Zhang. In this case, it is necessary to perform processing such as merging of the corporate annuity accounts of three institutions in one annuity management system.
The account processing method in the embodiment comprises the following steps:
In this embodiment, an executing entity (e.g., an electronic device such as a server) of the account processing method may receive a business processing request for the enterprise annuity business. The business processing request may include information of the target member and enterprise information of an enterprise to which the target member belongs.
Here, the target member is the enterprise personnel currently waiting to process the enterprise annuity account. The target member information may include various information related to the target member. For example, may include, but is not limited to: name, age, certificate type, certificate number, gender, etc. In addition, the enterprise information may include various information related to the enterprise to which the target member belongs. For example, may include, but is not limited to: enterprise name, enterprise address, enterprise legal name, enterprise account name, etc.
For example, if the business processing request indicates to process an annual account of a certain enterprise among the employees in the group a enterprise, the certain enterprise is a target member, and the business processing request may include information such as a name and an identification number of the certain enterprise, and may further include information such as a name and an address of the certain enterprise (i.e., the group a enterprise).
The specific content in the target member information and the enterprise information may be preset as needed, and is not limited herein.
In this embodiment, the execution subject may process various types of enterprise annuity services. For example, may include, but may not be limited to, may include, but is not limited to: newly adding enterprise annuity account service, changing service of the enterprise to which the target member belongs, transferring service of the enterprise annuity account of the target member, account data query service and the like.
In this embodiment, the executing entity may determine the service type of the enterprise annuity service requested to be processed by the service processing request received in step 101. In practice, the service processing request may include an identifier indicating the service type. The execution body can determine the service type by identifying the identifier. For example, if the identifier is 1, it may indicate that the service type requested to be processed is a new enterprise annuity account service; if the identifier is 2, it may indicate that the service type requested to be processed is a modified service for the enterprise to which the target member belongs. The writing mode of the identifier and the corresponding relationship between the identifier and the service type may be preset, and is not limited herein.
And 103, determining an account processing strategy based on the service type, the target member information and the enterprise information, and processing the enterprise annuity account of the target member in the annuity management system based on the account processing strategy when the enterprise annuity service is processed.
In this embodiment, for a certain member, since there may be multiple enterprise annuity accounts of the member in multiple institutions in the annuity management system, the enterprise annuity accounts of the member in the annuity management system may be processed (for example, processing such as querying and merging) in the process of processing the annuity business of the member.
Here, different business types may correspond to different account processing policies, and the account processing policies are used to clean the enterprise annuity accounts of the target members in the annuity management system, so that the enterprise annuity accounts of the target members in the annuity management system are not greater than two.
As an example, if the service type is to query the annuity amount of the target member, the enterprise annuity account of the target member may be queried in the annuity management system first, and when there is only one enterprise annuity account of the target member, the annuity amount query task may be directly performed. If two or more than two enterprise annuity accounts exist in the target member, the annuity amount of each enterprise annuity account can be inquired respectively, and the user is prompted to carry out treatment such as combination of the enterprise annuity accounts while the annuity amount is returned.
As another example, if the business type is a change business to the enterprise to which the target member belongs (from the original enterprise to the target enterprise), the enterprise annuity account of the target member may be queried in the annuity management system during the business execution. If there is only one, the enterprise annuity account can be directly transferred to the target enterprise. If there are at least two, the content in each account can be merged and transferred to the target enterprise.
As another example, if the service type is a transfer service to the enterprise annuity account of the target member (for example, a transfer service from an original enterprise to a target enterprise), the enterprise annuity account of the target member may be queried in the annuity management system during the service execution process. If there is only one, the enterprise annuity account can be directly transferred to the target enterprise. If there are at least two, the content in each account can be merged and transferred to the target enterprise.
The business type of the enterprise annuity business and the account processing policy corresponding to each business type may be set in advance as needed, and are not limited to the above list.
In some optional implementation manners of this embodiment, if the service type is a new enterprise annuity account service, the following steps may be performed:
the method comprises the first step of determining the number of enterprises to which target members belong based on enterprise information of the enterprises to which the target members belong. For example, in the business process request, if a target member is an enterprise to which the target member belongs, and includes both enterprise a and enterprise a1, the number of enterprises to which the target member belongs is 2.
And a second step of determining whether the target member information is stored in the annuity management system if the number is equal to a preset number (e.g., 1). Here, the query of the target member may be performed in the annuity management system using the above target member information. If the annual fund information is inquired, the target member information stored in the annual fund management system can be determined; if the information is not inquired, it can be determined that the target member information is not stored in the annuity management system.
Optionally, the target member information may include a name, a certificate type, and a certificate number. At this time, it may be determined whether member information including the name, the certificate type, and the certificate number is stored in the annuity management system. If yes, the target member information stored in the determined annuity management system can be determined; if not, the target member information is not stored in the determined annuity management system.
And thirdly, if the target member information is not stored, adding an enterprise annuity account of the target member in the enterprise to which the target member belongs in the annuity management system.
Therefore, in the process of processing the annuity business, the enterprise annuity account of the target member in the annuity management system is inquired and processed. When the enterprise annuity account does not exist, the enterprise annuity account of the member is added, so that the condition that two or more enterprise annuity accounts of the member exist in the annuity management system at the same time is avoided.
In the above-described embodiment, if the number is greater than a preset number (for example, 1) or the annuity management system stores the target member information, it is prohibited that the enterprise annuity account of the target member is added to the annuity management system. Thus, when a business processing request for adding a plurality of (two or more) enterprise annuity accounts for a certain member is received, or when the enterprise annuity accounts of the member already exist in the annuity management system, the operation of adding the accounts is not executed, and the condition that two or more enterprise annuity accounts of the member simultaneously exist in the annuity management system is avoided.
In some optional implementations of this embodiment, the executing entity may further receive a request for a duplication checking of the enterprise annuity account. Wherein, the query request can be initiated by the annuity operation and maintenance personnel. After receiving the duplication checking request, repeated enterprise annuity accounts can be inquired from the annuity management system and combined.
The method provided by the embodiment of the application determines the service type of the enterprise annuity service by receiving the service processing request of the enterprise annuity service, determines the account processing strategy of the target member based on the service type, the target member information in the service processing request and the enterprise information of the enterprise to which the target member belongs, and processes the enterprise annuity account of the target member in the annuity management system by using the account processing strategy when the enterprise annuity service is processed. Therefore, the related enterprise annuity accounts in the annuity management system can be processed in the normal processing process of the enterprise annuity business, the data in the annuity management system can be gradually updated, and the error risk in the data processing process is reduced.
With further reference to FIG. 2, a flow 200 of yet another embodiment of an account processing method is shown. The process 200 of the account processing method includes the following steps:
In this embodiment, if the service type is a modified service for the enterprise to which the target member belongs, the enterprise to which the target member currently belongs may be regarded as an original enterprise, the enterprise to which the target member belongs may be regarded as a target enterprise, and whether an enterprise annuity account of the target enterprise is stored in the annuity management system is determined. As an example, if a business annuity account exists at both a group business and a1 subsidiary. Now, a group a enterprise initiates a "change of affiliated enterprise" service, which means that a certain affiliated enterprise is changed from a group a enterprise to a1 subsidiary company. In this case, it is possible to inquire whether or not an account of the annual fee of the company at the a1 subsidiary exists in the annual fee management system, with the a group company as the original company and the a1 subsidiary as the target company.
And 204, if the enterprise annuity account exists, returning prompt information, wherein the prompt information is used for prompting that the enterprise annuity account of the target member in the original enterprise is merged into the enterprise annuity account of the target member in the target enterprise.
In this embodiment, if an enterprise annuity account of the target member in the target enterprise already exists in the annuity management system, the prompt message may be returned. The prompt information is used for prompting that the enterprise annuity account of the target member in the original enterprise is merged into the enterprise annuity account of the target member in the target enterprise.
Continuing with the above example, if a corporate annuity account at the a1 subsidiary is located in the annuity management system, a prompt may be returned suggesting that the user select automatic reconciliation. Here, the result of the reconciliation is that an enterprise annuity account exists in a1 subsidiary, and an enterprise annuity account does not exist in a group a enterprise.
And step 205, if the account does not exist, transferring the annual account of the target member in the original enterprise to the target enterprise.
In this embodiment, if the annual fee management system does not have the enterprise annual fee account of the target member in the target enterprise, the enterprise annual fee account of the target member in the original enterprise may be transferred to the target enterprise.
Continuing with the above example, if Zhang A1 subsidiary enterprise annuity account is not queried in the annuity management system, then Zhang A clique enterprise annual annuity account may be transferred to the A1 subsidiary name.
Therefore, under the condition that the enterprise change business is normally processed, the repeated accounts in the annuity management system can be cleaned, and the condition that two or more enterprise annuity accounts of the member exist in the annuity management system at the same time is avoided.
As can be seen from fig. 2, compared with the embodiment corresponding to fig. 1, the flow 200 of the account processing method in this embodiment relates to a processing step of an enterprise annuity account of a target member in the annuity management system when processing the change business of the affiliated institution. Therefore, according to the scheme described in the embodiment, the repeated accounts in the annuity management system can be cleaned under the condition that the enterprise change business is normally processed, so that the condition that two or more enterprise annuity accounts of the member exist in the annuity management system at the same time is avoided.
With further reference to FIG. 3, a flow 300 of yet another embodiment of an account processing method is shown. The process 300 of the account processing method includes the following steps:
Step 301 to step 302 in this embodiment can refer to step 101 to step 102 in the embodiment shown in fig. 1, and are not described herein again.
In this embodiment, if the service type is a transfer service to the enterprise annuity account of the target member, the execution subject may determine whether the enterprise annuity account of the target member exists in other enterprises of the organizational structure where the target enterprise is located, by taking the enterprise to which the target member currently belongs as an original enterprise and taking the enterprise to which the target member belongs as a target enterprise. As an example, if zhang san calendar history is stored in both group B business and group a business's a1 subsidiary. Now the group B enterprise initiates a "member roll out" service, meaning that a job is rolled out from the group B to a2 subsidiary. In this case, it is possible to inquire whether or not there is any enterprise annuity account of the remaining subsidiaries (i.e., the companies other than the a2 subsidiaries) in the annuity management system, with the B group enterprise as the original enterprise and the a2 subsidiary as the target enterprise.
And step 304, if the enterprise annuity account exists, deleting the enterprise annuity account of the target member in the original enterprise, and creating a change service of the enterprise to which the target member belongs so as to transfer the enterprise annuity account of the target member in other enterprises to the target enterprise.
In this embodiment, if the enterprise annuity account of the target member exists in another enterprise of the organizational structure where the target enterprise is located, the execution main body may delete the enterprise annuity account of the target member in the original enterprise, and create a change service for the enterprise to which the target member belongs, so as to transfer the enterprise annuity account of the target member in the another enterprise to the target enterprise. For the processing procedure of the changed service, refer to step 203-step 205 in the embodiment shown in fig. 2, which is not described herein again.
Continuing with the above example, when querying finds that a certain annual account of the enterprise exists in the a1 sub-company, the annual account of the enterprise in the B group enterprise may be deleted, and at the same time, a "business change belonging" service is initiated, so that the annual account of the certain enterprise is automatically changed from the a1 sub-company to the a2 sub-company. As a result, zhangzhi has an enterprise annuity account only in company a2, and does not set an enterprise annuity account in group B enterprises and company a 1.
And 305, if the account does not exist, transferring the target member to the target enterprise from the enterprise annuity account of the original enterprise.
In this embodiment, if the enterprise annuity account of the target member does not exist in other enterprises of the organizational structure where the target enterprise is located, the execution subject may transfer the enterprise annuity account of the target member in the original enterprise to the target enterprise.
Therefore, the repeated accounts in the annuity management system can be cleaned under the condition that the member roll-out service is normally processed, and the condition that two or more enterprise annuity accounts of the member exist in the annuity management system at the same time is avoided.
As can be seen from fig. 3, compared with the embodiment corresponding to fig. 1, the flow 300 of the account processing method in this embodiment relates to a processing step of an enterprise annuity account of a target member in the annuity management system when the member roll-out service is processed. Therefore, according to the scheme described in the embodiment, the repeated accounts in the annuity management system can be cleaned under the condition that the member roll-out service is normally processed, so that the condition that two or more enterprise annuity accounts of the member exist in the annuity management system at the same time is avoided.
With further reference to fig. 4, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of an account processing apparatus, which corresponds to the embodiment of the method shown in fig. 1, and which can be applied to various electronic devices.
As shown in fig. 4, the account processing apparatus 400 according to the present embodiment includes: a receiving unit 401, configured to receive a service processing request for an enterprise annuity service, where the service processing request includes target member information and enterprise information of an enterprise to which the target member belongs; a determining unit 402 configured to determine a service type of the enterprise annuity service; a processing unit 403, configured to determine an account processing policy of the target member based on the service type, the target member information, and the enterprise information, and process an enterprise annuity account of the target member in an annuity management system by using the account processing policy.
In some optional implementations of this embodiment, the processing unit 403 may be further configured to: determining an account processing policy based on the service type, the target member information and the enterprise information, and processing an enterprise annuity account of the target member in an annuity management system based on the account processing policy when the enterprise annuity service is processed, wherein the account processing policy comprises: if the service type is a newly added enterprise annuity account service, determining the number of enterprises to which the target members belong based on the enterprise information; if the number is equal to a preset number, determining whether the target member information is stored in the annuity management system; and if the target member information is not stored, adding an enterprise annuity account of the target member in the enterprise to which the target member belongs in the annuity management system.
In some optional implementations of this embodiment, the processing unit 403 may be further configured to: and if the number is larger than the preset number or the annual fund management system stores the target member information, forbidding adding the enterprise annual fund account of the target member in the annual fund management system.
In some optional implementations of this embodiment, the processing unit 403 may be further configured to: determining whether member information including the name, the certificate type and the certificate number is stored in the annuity management system; if yes, determining that the target member information is stored in the determined annuity management system; if not, determining that the target member information is not stored in the determined annuity management system.
In some optional implementations of this embodiment, the processing unit 403 may be further configured to: if the business type is a change business of the enterprise to which the target member belongs, taking the enterprise to which the target member currently belongs as an original enterprise, taking the enterprise to which the target member belongs as a target enterprise, and determining whether an enterprise annuity account of the target member in the target enterprise is stored in the annuity management system; if yes, returning prompt information, wherein the prompt information is used for prompting that the enterprise annuity account of the target member in the original enterprise is merged to the enterprise annuity account of the target member in the target enterprise; and if the target member does not exist, transferring the enterprise annuity account of the target member in the original enterprise to the target enterprise.
In some optional implementations of this embodiment, the processing unit 403 may be further configured to: if the service type is a transfer service of the enterprise annuity account of the target member, taking the enterprise to which the target member currently belongs as an original enterprise, taking the enterprise to which the target member belongs as a target enterprise, and determining whether the enterprise annuity account of the target member exists in other enterprises of an organizational structure in which the target enterprise is located; if yes, deleting the enterprise annuity account of the target member in the original enterprise, and creating a change business of the enterprise to which the target member belongs so as to transfer the enterprise annuity account of the target member in the other enterprises to the target enterprise; and if not, transferring the target member to the target enterprise from the enterprise annuity account of the original enterprise.
In some optional implementations of this embodiment, the processing unit 403 may be further configured to: receiving a duplication checking request for an enterprise annuity account; querying repeated enterprise annuity accounts from an annuity management system; and merging the repeated annual fund accounts of the enterprises.
The device provided by the above embodiment of the present application determines the service type of the enterprise annuity service by receiving a service processing request for the enterprise annuity service, and finally determines an account processing policy of the target member based on the service type, target member information in the service processing request, and enterprise information of an enterprise to which the target member belongs, and processes an enterprise annuity account of the target member in the annuity management system by using the account processing policy when processing the enterprise annuity service. Therefore, the related enterprise annuity accounts in the annuity management system can be processed in the normal processing process of the enterprise annuity business, the data in the annuity management system can be gradually updated, and the error risk in the data processing process is reduced.
Referring now to FIG. 5, shown is a block diagram of a computer system 500 suitable for use in implementing the electronic device of an embodiment of the present application. The electronic device shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU)501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the system 500 are also stored. The CPU501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Liquid Crystal Display (LCD) and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program performs the above-described functions defined in the method of the present application when executed by the Central Processing Unit (CPU) 501. It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a preprocessing unit, a differential operation unit, and a determination unit. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be present separately and not assembled into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: receiving a service processing request for enterprise annuity service, wherein the service processing request comprises target member information and enterprise information of an enterprise to which a target member belongs; determining the business type of the enterprise annuity business; and determining an account processing strategy based on the service type, the target member information and the enterprise information, and processing the enterprise annuity account of the target member in the annuity management system based on the account processing strategy when the enterprise annuity service is processed.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (10)
1. An account processing method, characterized in that the method comprises:
receiving a service processing request for enterprise annuity service, wherein the service processing request comprises target member information and enterprise information of an enterprise to which a target member belongs;
determining the business type of the enterprise annuity business;
and determining an account processing strategy based on the service type, the target member information and the enterprise information, and processing the enterprise annuity account of the target member in an annuity management system based on the account processing strategy when the enterprise annuity service is processed.
2. The method of claim 1, wherein determining an account processing policy based on the business type, the target member information, and the enterprise information, and processing the enterprise annuity account of the target member in an annuity management system based on the account processing policy when processing the enterprise annuity business comprises:
if the service type is a newly added enterprise annuity account service, determining the number of enterprises to which the target member belongs based on the enterprise information;
if the number is equal to a preset number, determining whether the target member information is stored in the annuity management system;
and if the target member information is not stored, adding an enterprise annuity account of the target member in the enterprise in the annuity management system.
3. The method of claim 2, wherein determining an account processing policy based on the business type, the target member information, and the enterprise information, and processing the enterprise annuity account of the target member in an annuity management system based on the account processing policy when processing the enterprise annuity business, further comprises:
and if the number is larger than the preset number or the annuity management system stores the target member information, forbidding adding the enterprise annuity account of the target member in the annuity management system.
4. The method of claim 2, wherein the target member information includes a name, a certificate type, and a certificate number; and
the determining whether the target member information is stored in the annuity management system comprises:
determining whether member information including the name, the certificate type, and the certificate number has been stored in the annuity management system;
if yes, determining that the target member information is stored in the determined annuity management system;
if not, determining that the target member information is not stored in the determined annuity management system.
5. The method of claim 1, wherein determining an account processing policy based on the business type, the target member information, and the enterprise information, and processing the enterprise annuity account of the target member in an annuity management system based on the account processing policy when processing the enterprise annuity business comprises:
if the business type is a change business of the enterprise to which the target member belongs, taking the enterprise to which the target member currently belongs as an original enterprise, taking the enterprise to which the target member belongs as a target enterprise, and determining whether an enterprise annuity account of the target member in the target enterprise exists in the annuity management system;
if the target member annual account exists, returning prompt information, wherein the prompt information is used for prompting that the enterprise annual account of the target member in the original enterprise is merged into the enterprise annual account of the target member in the target enterprise;
and if not, transferring the target member to the target enterprise from the enterprise annuity account of the original enterprise.
6. The method of claim 1, wherein determining an account processing policy based on the business type, the target member information, and the enterprise information, and processing the enterprise annuity account of the target member in an annuity management system based on the account processing policy when processing the enterprise annuity business comprises:
if the service type is a transfer-out service of the enterprise annuity account of the target member, taking the enterprise to which the target member currently belongs as an original enterprise, taking the enterprise to which the target member belongs as a target enterprise, and determining whether the enterprise annuity account of the target member exists in other enterprises of an organization framework where the target enterprise is located;
if yes, deleting the enterprise annuity account of the target member in the original enterprise, and creating a change service of the enterprise to which the target member belongs so as to transfer the enterprise annuity account of the target member in the other enterprises to the target enterprise;
and if not, transferring the target member to the target enterprise from the enterprise annuity account of the original enterprise.
7. The method of claim 1, further comprising:
receiving a duplication checking request for an enterprise annuity account;
querying repeated enterprise annuity accounts from an annuity management system;
and merging the repeated annual fund accounts of the enterprises.
8. An enterprise annuity account processing apparatus, the apparatus comprising:
the system comprises a receiving unit and a processing unit, wherein the receiving unit is configured to receive a business processing request of an enterprise annuity business, and the business processing request comprises target member information and enterprise information of an enterprise to which a target member belongs;
a determining unit configured to determine a business type of the enterprise annuity business;
the processing unit is configured to determine an account processing strategy of the target member based on the service type, the target member information and the enterprise information, and process an enterprise annuity account of the target member in an annuity management system by using the account processing strategy.
9. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911047353.6A CN110889771A (en) | 2019-10-30 | 2019-10-30 | Account processing method and device, electronic equipment and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911047353.6A CN110889771A (en) | 2019-10-30 | 2019-10-30 | Account processing method and device, electronic equipment and computer readable medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110889771A true CN110889771A (en) | 2020-03-17 |
Family
ID=69746710
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911047353.6A Pending CN110889771A (en) | 2019-10-30 | 2019-10-30 | Account processing method and device, electronic equipment and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110889771A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268639A (en) * | 2021-06-09 | 2021-08-17 | 新奥数能科技有限公司 | Energy enterprise information processing method and device, computer equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101477671A (en) * | 2009-01-19 | 2009-07-08 | 招商银行股份有限公司 | System and method for pension account management |
| US20090292563A1 (en) * | 2008-05-20 | 2009-11-26 | Hartford Fire Insurance Company | System and method for administering variable annuities |
| CN108446976A (en) * | 2018-02-07 | 2018-08-24 | 平安科技（深圳）有限公司 | A kind of common reserve fund transfer method, computer readable storage medium and terminal device |
| CN108564339A (en) * | 2018-03-29 | 2018-09-21 | 平安科技（深圳）有限公司 | A kind of account management method, device, terminal device and storage medium |
| CN109118373A (en) * | 2017-06-26 | 2019-01-01 | 平安科技（深圳）有限公司 | Supplementary pension method of commerce, device and computer readable storage medium |
-
2019
- 2019-10-30 CN CN201911047353.6A patent/CN110889771A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090292563A1 (en) * | 2008-05-20 | 2009-11-26 | Hartford Fire Insurance Company | System and method for administering variable annuities |
| CN101477671A (en) * | 2009-01-19 | 2009-07-08 | 招商银行股份有限公司 | System and method for pension account management |
| CN109118373A (en) * | 2017-06-26 | 2019-01-01 | 平安科技（深圳）有限公司 | Supplementary pension method of commerce, device and computer readable storage medium |
| CN108446976A (en) * | 2018-02-07 | 2018-08-24 | 平安科技（深圳）有限公司 | A kind of common reserve fund transfer method, computer readable storage medium and terminal device |
| CN108564339A (en) * | 2018-03-29 | 2018-09-21 | 平安科技（深圳）有限公司 | A kind of account management method, device, terminal device and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 吴书卿: "基于工作流的企业年金账户管理系统的研究与设计", 《中国优秀博硕士学位论文全文数据库(电子期刊)信息科技辑》 * |
| 王卫东, 武汉大学出版社 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268639A (en) * | 2021-06-09 | 2021-08-17 | 新奥数能科技有限公司 | Energy enterprise information processing method and device, computer equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10114854B2 (en) | Validation rule management across entities | |
| US20160267587A1 (en) | Systems and methods for online guarantorship of loans | |
| US9633069B2 (en) | Data subscription management system | |
| CN114626698A (en) | Incentive asset allocation method, incentive asset allocation device, electronic equipment and storage medium | |
| US20130080301A1 (en) | One-step posting for approval-based ledger transactions | |
| US20230153446A1 (en) | System for improving the resource event device removal process | |
| CN112581179B (en) | Electronic coupon generation method and generation device | |
| CN110889771A (en) | Account processing method and device, electronic equipment and computer readable medium | |
| US20190034905A1 (en) | Ride sharing benefit administration platform | |
| CN111859049B (en) | Method for realizing differential display of enterprise salary information and message generation method | |
| US20240037647A1 (en) | Reconciliation for enabling accelerated access to contribution funded accounts | |
| CN111179054A (en) | Request information processing method, server, client and system | |
| CN111383098A (en) | Resource distribution method and device | |
| CN115564415A (en) | Order payment and settlement method and device | |
| JPWO2017021998A1 (en) | Method and system for updating electronic approval document | |
| JP2016095686A (en) | Collateral management service system and method of electronic recording credit | |
| CN113361733A (en) | Processing method and device for reserved service | |
| RU2656720C2 (en) | Asset inventory system | |
| US20150294404A1 (en) | Method and system for legal processing for debt collection | |
| CN113128595A (en) | Method, apparatus, device and computer readable medium for integrating customer information | |
| US8732041B2 (en) | Replicating data in financial systems | |
| JP6263288B1 (en) | Bank system, method and program executed by bank system | |
| CN115456802B (en) | Insurance event processing system based on digital currency | |
| CN115829753B (en) | Cross-border securities business exchange method and system based on blockchain | |
| CN115496581A (en) | Account amount transferring method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200317 |