CN114187116A - Method and apparatus for managing account information - Google Patents
Method and apparatus for managing account information Download PDFInfo
- Publication number
- CN114187116A CN114187116A CN202111525734.8A CN202111525734A CN114187116A CN 114187116 A CN114187116 A CN 114187116A CN 202111525734 A CN202111525734 A CN 202111525734A CN 114187116 A CN114187116 A CN 114187116A
- Authority
- CN
- China
- Prior art keywords
- account
- target
- field
- product
- type
- 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
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/06—Asset management; Financial planning or analysis
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- 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/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Human Resources & Organizations (AREA)
- General Business, Economics & Management (AREA)
- Development Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Physics & Mathematics (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Operations Research (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Game Theory and Decision Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application provides a method and a device for managing account information, which can be used in the field of data verification, wherein the method comprises the following steps: determining a target account type of a target account; selecting a target account template from a plurality of account templates included in an account template management library based on the target account type, wherein the target account template corresponds to the target account type; acquiring account information of a target account based on a target account template; judging whether the target account meets the business verification rule or not based on the business verification rule in the account business rule base, the product identification, the product type, the account identification and the financial institution identification of the target account; and under the condition that the target account meets the service verification rule, establishing a corresponding relation between the product corresponding to the product identifier and the account corresponding to the account identifier, and recording account information of the target account. The method can acquire various types of account information so as to facilitate the subsequent management and maintenance of the account information.
Description
Technical Field
The present application relates to the field of data verification, and in particular, to a method and an apparatus for managing account information.
Background
The financial financing product refers to a standardized financial product, such as a financing product and a futures product, which is a financial institution having a qualification to collect funds from a specific client or to receive a property of the specific client to entrust to act as an asset manager and invest by using the entrusted property.
Financial management products such as financial products and futures products need to open different types of accounts in the collection, investment, stock management and inventory business, for example, the collected accounts need to be used for receiving collected funds of an affiliate in the collection stage, and the accounts of holders of clearing houses need to be opened for inter-bank transactions in the investment stage. The current system for managing account information can only acquire accounts of specific account types, but cannot acquire account information of various different types, so that the subsequent account management is not facilitated.
Therefore, a method for managing account information is needed, which can obtain various types of account information to facilitate subsequent management and maintenance of account information.
Disclosure of Invention
The application provides a method and a device for managing account information, which can acquire account information of different types, improve the flexibility of account information input and facilitate the follow-up management and maintenance of the account information.
In a first aspect, the present application provides a method for managing account information, the method comprising: determining a target account type of a target account; selecting a target account template from a plurality of account templates included in an account template management library based on the target account type, wherein the target account template corresponds to the target account type; acquiring account information of a target account based on a target account template, wherein the account information comprises a product identifier, a product type, an account identifier and a financial institution identifier; judging whether the target account meets the business verification rule or not based on the business verification rule in the account business rule base, the product identification, the product type, the account identification and the financial institution identification of the target account; and under the condition that the target account meets the service verification rule, establishing a corresponding relation between the product corresponding to the product identifier and the account corresponding to the account identifier, and recording account information of the target account.
According to the method for managing the account information, the account information of different types can be input by a customer through the preset of the plurality of account templates and the service inspection rule, so that the account information of different types can be obtained, the flexibility of inputting the account information is improved, and the account information can be managed and maintained subsequently.
With reference to the first aspect, in some implementations of the first aspect, the target account template includes an account type field, a virtual-real account flag field, an account name field, an account full name field, an account short name field, and an account opening mechanism field.
With reference to the first aspect, in certain implementations of the first aspect, the target account type is a fund account or a security account; the account template corresponding to the fund account also comprises a public field of the fund account and a personalized field of the fund account, wherein the public field of the fund account comprises a payment system line number field, an account opening bank code field and an account opening bank name field; the account template corresponding to the security account further comprises a public field of the security account and a personalized field of the security account, and the public field of the security account comprises a security code field.
With reference to the first aspect, in certain implementations of the first aspect, the service check rule includes at least one of the following rules: whether the account type is contained within a range of account types required for a particular product type; whether the same product allows for the addition of multiple accounts of the same account type; whether a particular account is allowed to be shared between different products; whether a particular account is allowed to be shared between different financial institutions for different products; alternatively, the same account can be shared by multiple financial institutions participating in the same product.
With reference to the first aspect, in certain implementations of the first aspect, the method further includes: and under the condition that the target account does not meet the service verification rule, displaying a prompt message, wherein the prompt message is used for prompting that the account is not verified to be passed and account information cannot be input.
The specific content in the prompt message is not limited, and the content incapable of inputting the account information is within the protection scope of the application as long as the content can be used for prompting that the account verification is not passed.
In a second aspect, the present application provides an apparatus for managing account information, the apparatus comprising a processing module and an obtaining module. The processing module is used for: determining a target account type of a target account; selecting a target account template from a plurality of account templates included in an account template management library based on the target account type, wherein the target account template corresponds to the target account type; the acquisition module is used for: acquiring account information of a target account based on a target account template, wherein the account information comprises a product identifier, a product type, an account identifier and a financial institution identifier; the processing module is further configured to: judging whether the target account meets the business verification rule or not based on the business verification rule in the account business rule base, the product identification, the product type, the account identification and the financial institution identification of the target account; and under the condition that the target account meets the service verification rule, establishing a corresponding relation between the product corresponding to the product identifier and the account corresponding to the account identifier, and recording account information of the target account.
With reference to the second aspect, in some implementations of the second aspect, the target account template includes an account type field, a virtual-real account flag field, an account name field, an account full name field, an account short name field, and an account opening mechanism field.
With reference to the second aspect, in some implementations of the second aspect, the target account type is a fund account or a security account; the account template corresponding to the fund account also comprises a public field of the fund account and a personalized field of the fund account, wherein the public field of the fund account comprises a payment system line number field, an account opening bank code field and an account opening bank name field; the account template corresponding to the security account further comprises a public field of the security account and a personalized field of the security account, and the public field of the security account comprises a security code field.
With reference to the second aspect, in some implementations of the second aspect, the service check rule includes at least one of the following rules: whether the account type is contained within a range of account types required for a particular product type; whether the same product allows for the addition of multiple accounts of the same account type; whether a particular account is allowed to be shared between different products; whether a particular account is allowed to be shared between different financial institutions for different products; alternatively, the same account can be shared by multiple financial institutions participating in the same product.
With reference to the second aspect, in some implementations of the second aspect, the apparatus further includes a display module; the display module is used for: and under the condition that the target account does not meet the service verification rule, displaying a prompt message, wherein the prompt message is used for prompting that the account is not verified to be passed and account information cannot be input.
In a third aspect, the present application provides an apparatus for managing account information, comprising a processor and a memory. The processor is configured to read instructions stored in the memory to perform the method of any one of the possible implementations of the first aspect.
Optionally, there are one or more processors and one or more memories.
Alternatively, the memory may be integrated with the processor, or provided separately from the processor.
In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.
The apparatus in the third aspect may be a chip, and the processor may be implemented by hardware or by software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.
In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program (which may also be referred to as code or instructions) which, when run on a computer, causes the computer to perform the method of any one of the possible implementations of the first aspect described above.
In a fifth aspect, the present application provides a computer program product comprising: computer program (also called code, or instructions), which when executed, causes a computer to perform the method of any of the possible implementations of the first aspect described above.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
FIG. 1 is a diagram illustrating a system architecture suitable for use in embodiments of the present application;
FIG. 2 is a schematic flow chart diagram of a method for managing account information provided by an embodiment of the present application;
FIG. 3 is a schematic flow chart diagram of another method for managing account information provided by an embodiment of the present application;
FIG. 4 is a schematic block diagram of an apparatus for managing account information according to an embodiment of the present disclosure;
fig. 5 is a schematic block diagram of another apparatus for managing account information according to an embodiment of the present disclosure.
With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
In the technical scheme of the application, the collection, storage, use, processing, transmission, provision, disclosure and other processing of the related information such as financial data or user data and the like all accord with the regulations of related laws and regulations and do not violate the good custom of the public order. For the convenience of understanding the embodiments of the present application, the related terms in the embodiments of the present application will be described first.
1. Gold financing tube product
The financial financing product refers to a standardized financial product, such as a financing product and a futures product, which is a financial institution having a qualification to collect funds from a specific client or to receive a property of the specific client to entrust to act as an asset manager and invest by using the entrusted property.
2. Fund account
The fund account is an account for recording fund flow, is used in the settlement of funds in the business of the liability end and the asset end of the financial resource management product, and is used in various stages of recruitment, investment, storage period management and the like of the financial resource management product.
3. Security account
The stock account is an account which is opened at a stock register and settlement institution, a stock company or other stock business participation institutions and records position holding information, and can be used for recording position holding of stocks, deposit positions, bond positions, fund positions, future positions, position holding of other investment targets and the like.
Generally, different types of investment varieties may have different security accounts.
4. Business verification rules
The business validation rules may include the validation rules of the account itself and the business rules of the account associated with the product. The verification rule of the account itself refers to that the account itself is verified through the mandatory item of the account. For example, the requisite items for an account are the full account name, the account type, and the opening institution, and the account is not passed if at least one of the information in the full account name, the account type, and the opening institution is unknown.
Before describing the method and apparatus for managing account information provided by the embodiments of the present application, the following description is made.
In the embodiments of the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, and c, may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, wherein a, b and c can be single or multiple.
Financial management products such as financial products and futures products need to open different types of accounts in the collection, investment, stock management and inventory business, for example, the collected accounts need to be used for receiving collected funds of an affiliate in the collection stage, and the accounts of holders of clearing houses need to be opened for inter-bank transactions in the investment stage. The current system for managing account information can only provide an operation interface for an account of a specific account type to further acquire account information, cannot adapt to accounts of different types, cannot acquire account information of different types, and is not beneficial to subsequent account management. If different operation interfaces are provided for different types of accounts, the problem of high development cost exists.
Illustratively, FIG. 1 shows a schematic diagram of a system architecture 100. As shown in fig. 1, the system architecture 100 includes a client 101 and a server 102. It should be understood that the number of the clients and the servers in fig. 1 is only an example, and the embodiment of the present application is not limited thereto.
After the customer opens the account, the account information needs to be entered into the client 101, and the client 101 can provide an account information entry interface for the customer to enter the account information. The client can fill in account information through an account information entry interface of the client 101, the client 101 responds to the operation of the client to acquire the account information and send the account information to the server 102, correspondingly, the server 102 can receive the account information and establish a corresponding relationship between a product and an account according to the account information, so that subsequent account management is facilitated.
It should be understood that the system architecture 100 is only an example, and in other possible implementations, the client may also establish a correspondence between the product and the account according to the account information, and store the account information and the correspondence locally, which is not limited in this embodiment of the present application.
The above-mentioned method for inputting account information has a drawback that, because the operation interfaces corresponding to different types of accounts are different, the client 101 can only provide an operation interface for a specific account, and cannot adapt to different types of accounts, and cannot acquire different types of account information, thereby being not favorable for subsequent account management. In view of this, embodiments of the present application provide a method and an apparatus for managing account information, which can acquire account information of different types, and improve flexibility of account information entry, so as to facilitate subsequent management and maintenance of account information.
Fig. 2 is a schematic flow chart of a method 200 for managing account information according to an embodiment of the present disclosure, where the method 200 may be implemented by a data processing device, and the data processing device may be any device having a data processing function. The method 200 may also be applied to the system shown in fig. 1, in which case the method 200 may be executed by the client 101 shown in fig. 1, but the embodiment of the present application is not limited thereto.
As shown in fig. 2, the method 200 may include the steps of:
s201, determining the target account type of the target account.
The target account is an account opened by a customer, and after the customer opens the account, account information of the account needs to be input into the data processing equipment, so that the subsequent data processing equipment can manage and maintain the account.
The target account type is an account type of the target account. The data processing apparatus may provide the customer with a human-machine interface that may include an account type selection interface that may display various account types for the customer to select. The customer may select an account type from the various account types based on the target account via the account type selection interface, and the data processing device may determine the target account type in response to the operation.
For example, the account type selection interface may display a funding account and a security account. After the customer opens the fund account (i.e., the target account), the customer may select the fund account from the fund account and the security account through the account type selection interface, and the data processing device may determine the target account type as the fund account in response to the operation.
S202, selecting a target account template from a plurality of account templates included in the account template management base based on the target account type, wherein the target account template corresponds to the target account type.
The plurality of account templates in the account template management library are preset, and the plurality of account templates can be summarized according to a large number of different types of account information. The number of the account templates is not limited in the embodiment of the application.
It should be understood that the account template management library may be stored in a local memory of the data processing device, or may be stored in the server and obtained from the server by the data processing device (or the client), which is not limited in this embodiment of the present application.
Alternatively, the different types of accounts may include a fund account and a security account, and the data processing device may summarize an account template corresponding to the fund account and an account template corresponding to the security account according to account information of a large number of fund accounts and account information of security accounts.
The data processing device may select an account template corresponding to the target account type from a plurality of account templates as the target account module.
Illustratively, the plurality of account templates include an account template corresponding to a fund account and an account template corresponding to a security account, and if the target account type is a security account, the target account module selected by the data processing device from the plurality of account templates is the account template corresponding to the security account.
Optionally, the target account module may include an account type field, a virtual account flag field, an account name field, an account full name field, an account short name field, and an account opening institution field.
Optionally, if the target account type is a fund account or a security account, the target account type may be an account template corresponding to the fund account or an account template corresponding to the target account.
The account template corresponding to the fund account can comprise an account type field, a virtual and real account mark field, an account name field, an account full name field, an account short name field and an account opening mechanism field, and can also comprise a public field of the fund account and a personalized field of the fund account, wherein the public field of the fund account can comprise a payment system line number field, an account opening bank code field and an account opening bank name field;
the account template corresponding to the security account may include an account type field, a virtual-real account mark field, an account name field, an account full name field, an account short name field, and an account opening mechanism field, and may further include a public field of the security account and a personalized field of the security account, where the public field of the security account includes a security code field.
Alternatively, the personalized field for the financial account and the personalized field for the security account may be deposited by JSON Object Notation (JSON) strings.
Optionally, a field included in the target account module corresponding to the target account type may be understood as an account attribute, and the data processing device may store the account attribute through an account attribute configuration table, where the account attribute configuration table may include basic information of the field, display control information of the field, and other additional information of the field.
S203, acquiring account information of the target account based on the target account template, wherein the account information comprises a product identifier, a product type, an account identifier and a financial institution identifier.
The data processing device may provide an account information interface for the customer based on the target account template, the account information interface including fields included with the target account template. The customer may obtain account information for the target account based on fields included in the target account template in the account information interface.
There are many realizable ways for the data processing device to obtain account information for the target account.
In one possible implementation, the customer may manually fill in the account information interface, that is, manually fill in the account information in an input box corresponding to a field displayed in the account information interface. The data processing device acquires account information of the target account in response to an operation of the customer.
In another possible implementation manner, after the customer opens the account (i.e., the target account), the data processing device may store an electronic version account opening notice of the account, where the account opening notice includes account information. Therefore, the account information interface may further include a file uploading control, the client may trigger a response of uploading the file by clicking the file uploading control, and upload the account opening notice, and after receiving the account opening notice, the data processing device may parse the account opening notice to obtain the account information, and input the account information to the corresponding field, thereby obtaining the account information of the target account.
In another possible implementation manner, the account opening notice of the account is paper, the account information interface may further include a file scanning control, the client may trigger a response of scanning the file by clicking the file scanning control, the data processing device may scan the account opening notice, analyze the account opening notice, obtain the account information, and input the account information to the corresponding field, thereby obtaining the account information of the target account.
The account information may include a product identifier, a product type, an account identifier, and a financial institution identifier, where the product identifier may be used to distinguish different products, the product type may classify products, the account identifier may be used to distinguish different accounts, and the financial institution identifier is used to distinguish institutions to which the customer belongs.
The account identifier and the product identifier may be identified by numbers, letters, or data plus letters, which is not limited in this application. The identification modes of the account identification and the product identification may be the same or different, and this is not limited in this application embodiment.
The financial institution identification may be a financial institution number, which is not limited in this embodiment of the present application.
Alternatively, the product type may be obtained together with the target account type in S201 described above. It should be understood that the embodiments of the present application are not limited thereto.
The human-machine interface provided by the data processing device for the customer may also include a product type selection interface that may display various product types for the customer to select. The product types may include financial products, futures products, stock products, and the like. It should be understood that the type of product of the embodiments of the present application is not limited thereto.
In particular, the product type selection interface may display various product types for selection by the customer. The customer may select a product type from the various product types based on the target account via the product type selection interface, and the data processing device may determine the product type in response to the operation.
It should be understood that the account opened by the customer is for processing a certain transaction of the product, so the customer may select the product type when the data processing device enters the account information.
Illustratively, the product type selection interface may display product types such as financial products, futures products, and stock products. After a client opens a collecting account (namely a target account) in the collecting stage of the financing products, the financing products can be selected from the financing products, the futures products and the stock products through the product type selection interface, and the data processing equipment responds to the operation to determine that the product type is the financing product.
Optionally, the product type may further include a sub-product, so the product type selection interface may further include a sub-product selection interface, and the sub-product selection interface may display sub-products that can be supported by the product type, so as to facilitate selection by the customer.
Illustratively, the sub-products that the financing product can support include a rights product, a solid income product, a mixed product and the like.
S204, judging whether the target account meets the business verification rule or not based on the business verification rule in the account business rule base, the product identification, the product type, the account identification and the financial institution identification of the target account.
The service verification rules in the account service rule base may be preset, and the service verification rules may include service rules associated with products and accounts, service rules associated with products, accounts and financial institutions, and the like, and the embodiments of the present application are not limited thereto.
It should be understood that the account service rule base may be stored in a local memory of the data processing device, or may be stored in the server, and is obtained from the server by the data processing device (or the client), which is not limited in this embodiment of the present application.
The data processing device can judge whether the target account meets the business verification rule or not according to the product identification, the product type, the account identification and the financial institution identification of the target account.
S205, under the condition that the target account meets the service verification rule, establishing a corresponding relation between the product corresponding to the product identification and the account corresponding to the account identification, and recording account information of the target account.
According to the method for managing the account information, the account information of different types can be input by a customer through the preset of the plurality of account templates and the service inspection rule, so that the account information of different types can be obtained, the flexibility of inputting the account information is improved, and the account information can be managed and maintained subsequently.
Optionally, the service check rule may include at least one of the following rules: whether the account type is contained within a range of account types required for a particular product type; whether the same product allows for the addition of multiple accounts of the same account type; whether a particular account is allowed to be shared between different products; whether a particular account is allowed to be shared between different financial institutions for different products; alternatively, the same account can be shared by multiple financial institutions participating in the same product.
The business verification rules may include whether the account type is contained within a range of account types required for a particular product type. The data processing device can judge whether the target account meets the business verification rule or not according to the product type and the account type of the target account.
Illustratively, financing class products (i.e., specific product types) may include funding accounts and recruitment accounts (i.e., a range of account types). If the target account is a recruitment account and the customer wants to use the target account for the financial product, the data processing device may determine that the recruitment account is included in the account type range required by the financial product, and then the target account satisfies the business verification rule.
The business verification rules may include whether the same product allows for the addition of multiple accounts of the same account type. The data processing device can judge whether the target account meets the business verification rule or not according to the product identification and the account type of the target account.
Illustratively, the financial product does not allow for adding a plurality of security accounts, and if the target account is a security account and the customer has entered the security account for the financial product in the data processing device, the data processing device may determine that the security account does not satisfy the business verification rules.
The business verification rules may include whether a particular account is allowed to be shared among different products. The data processing device can judge whether the target account meets the business verification rule or not according to the product identifier and the account identifier of the target account.
For example, the collection account may allow for sharing between financial and stock products. If the target account is a collection account, the collection account is used for financing products, and the customer already inputs a security account for the stock products in the data processing device, the data processing device can judge that the security account meets the business verification rule.
The business verification rules may include whether a particular account is allowed to be shared between different financial institutions for different products. The data processing device can judge whether the target account meets the business verification rule or not according to the product identification, the account identification and the financial institution identification of the target account.
Illustratively, the financial institution 1 opens a position holding account of the financial products, the financial institution 2 opens a position holding account of the stock products, and the position holding account may be one account, that is, the position holding account may be allowed to be shared between different financial institutions corresponding to different products. If the target account is a position-holding account, the position-holding account is used for financial products set by the financial institution 1, and the client has already input the position-holding account for stock products set by the financial institution 2 in the data processing device, the data processing device can judge that the stock account meets the business check rule.
The business verification rules may include whether the same account can be shared by multiple financial institutions participating in the same product. The data processing device can judge whether the target account meets the business verification rule or not according to the product identification, the account identification and the financial institution identification of the target account.
Illustratively, the financial institution 1 opens a transaction account of the financial product, and the financial institution 2 opens a transaction account of the financial product, which may not be a single account, i.e. the transaction account is not allowed to be shared by multiple financial institutions participating in the same product. If the target account is a trading account, the trading account is used for financial products set by the financial institution 1, and the customer already inputs the trading account for financial products set by the financial institution 2 in the data processing equipment, the data processing equipment can judge that the security account does not meet the business verification rule.
Optionally, the business verification rules may also include business rules associated with accounts, products, financial institutions, and business types. The data processing device can judge whether the target account meets the business verification rule or not according to the product identification, the product type, the account identification, the financial institution identification and the business type of the target account.
The service types may include recruitment services, investment services, and clearing services, etc., and it should be understood that embodiments of the present application should not be limited thereto.
For example, the business verification rules may include whether a particular account is allowed to be shared between different financial institutions for different businesses for different products. The data processing device can judge whether the target account meets the business verification rule or not according to the product identification, the account identification, the financial institution identification and the business type of the target account.
As an alternative embodiment, the method 200 further includes: and under the condition that the target account does not meet the service verification rule, displaying a prompt message, wherein the prompt message is used for prompting that the account is not verified to be passed and account information cannot be input.
And under the condition that the target account does not meet the service verification rule, the data processing equipment can display a prompt message on the man-machine interaction interface. The prompt information may be displayed in the form of a message box, but the embodiment of the present application is not limited thereto.
The specific content in the prompt message is not limited in the embodiment of the present application, and as long as the content can be used for prompting that the account verification is not passed, the content that the account information cannot be entered is within the protection scope of the embodiment of the present application.
Alternatively, the display event of the prompt message may be preset, for example, the prompt message may disappear after being displayed for a period of time, or the prompt message may be displayed until the message prompt box is closed by the client.
According to the method for managing the account information, under the condition that the target account does not meet the service verification rule, the prompt message can be displayed to prompt the client to operate wrongly, so that the client can know that the operation of the client is wrong, and the client can conveniently change the operation subsequently.
Optionally, the account type selection interface in the human-computer interaction interface provided by the data processing device may further include a control for adding an account type, the usage right of the control may be used by a developer, and when the account type displayed on the account type selection interface does not meet the requirements of the customer, the developer may trigger a response for adding the account type through the control for adding the account type, so that account type configurability is achieved, and account type selection may be provided for the customer more flexibly.
Optionally, the data processing device may display the target account template through a human-computer interaction interface, the target account template interface may include a field addition control, the use permission of the control may be used by a developer, and when the field information displayed on the target account template interface does not meet the customer requirements, the developer may trigger a field addition response through the field addition control, so that template information is configurable, and the target account template may be provided for the customer more flexibly.
Fig. 3 shows a schematic flow chart of another method 300 for managing account information, which may be applied to the system shown in fig. 1, but the embodiment of the present application is not limited thereto.
As shown in fig. 3, the method 300 may include the steps of:
s301, the client determines the target account type of the target account.
The method for determining the target account type of the target account by the client may refer to S201 in the method 200, which is not described herein again.
S302, the client sends the target account type to the server, and correspondingly, the server receives the target account type.
S303, the server selects a target account template from a plurality of account templates contained in the account template management base based on the target account type, wherein the target account template corresponds to the target account type.
The method for selecting the target account template from the plurality of account templates included in the account template management library by the server may refer to S202 in the method 200, and details are not described here.
S304, the server sends the target account template to the client, and correspondingly, the client receives the target account template.
S305, the client side obtains account information of the target account based on the target account template, wherein the account information comprises a product identifier, a product type, an account identifier and a financial institution identifier.
The method for the client to obtain the account information of the target account may refer to S203 in the method 200, which is not described herein again.
S306, the client sends the account information to the server, and correspondingly, the server receives the account information.
S307, the server judges whether the target account meets the business verification rule or not based on the business verification rule in the account business rule base, the product identification, the product type, the account identification and the financial institution identification (namely account information).
The method for the server to determine whether the target account satisfies the service verification rule may refer to S204 in the method 200, which is not described herein again.
S308, under the condition that the target account meets the service verification rule, the server establishes the corresponding relation between the product corresponding to the product identifier and the account corresponding to the account identifier, and records the account information of the target account.
The method for the server to establish the correspondence between the product corresponding to the product identifier and the account corresponding to the account identifier may refer to S205 in the method 200, which is not described herein again.
Optionally, the server may also send a prompt message to the client, the prompt message being used to prompt the client to successfully generate the account information. After receiving the prompt message, the client may display the prompt message.
According to the method for managing the account information, the server can preset a plurality of account templates and service inspection rules to provide the account templates and the service inspection rules for the client, so that the client can be supported to input different types of account information at the client, and further different types of account information can be acquired, and the subsequent management and maintenance of the account information can be facilitated.
As an alternative embodiment, the method 300 may further include: and under the condition that the target account does not meet the service verification rule, the server sends a prompt message to the client, wherein the prompt message is used for prompting that the account is not verified and account information cannot be input, and the client can display the prompt message after receiving the prompt message.
The sequence numbers of the above processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not be limited in any way to the implementation process of the embodiments of the present application.
The method for managing account information provided by the embodiment of the present application is described in detail above with reference to fig. 1 to 3, and the apparatus for managing account information provided by the embodiment of the present application is described in detail below with reference to fig. 4 and 5.
Fig. 4 illustrates an apparatus 400 for managing account information according to an embodiment of the present disclosure. The apparatus 400 comprises: a processing module 410 and an acquisition module 420. Wherein the processing module 410 is configured to: determining a target account type of a target account; selecting a target account template from a plurality of account templates included in an account template management library based on the target account type, wherein the target account template corresponds to the target account type; the obtaining module 420 is configured to: acquiring account information of a target account based on a target account template, wherein the account information comprises a product identifier, a product type, an account identifier and a financial institution identifier; the processing module 410 is further configured to: judging whether the target account meets the business verification rule or not based on the business verification rule in the account business rule base, the product identification, the product type, the account identification and the financial institution identification of the target account; and under the condition that the target account meets the service verification rule, establishing a corresponding relation between the product corresponding to the product identifier and the account corresponding to the account identifier, and recording account information of the target account.
Optionally, the target account template includes an account type field, a virtual-real account flag field, an account name field, an account full name field, an account short name field, and an account opening mechanism field.
Optionally, the target account type is a fund account or a security account; the account template corresponding to the fund account also comprises a public field of the fund account and a personalized field of the fund account, wherein the public field of the fund account comprises a payment system line number field, an account opening bank code field and an account opening bank name field; the account template corresponding to the security account further comprises a public field of the security account and a personalized field of the security account, and the public field of the security account comprises a security code field.
Optionally, the service verification rule includes at least one of the following rules: whether the account type is contained within a range of account types required for a particular product type; whether the same product allows for the addition of multiple accounts of the same account type; whether a particular account is allowed to be shared between different products; whether a particular account is allowed to be shared between different financial institutions for different products; alternatively, the same account can be shared by multiple financial institutions participating in the same product.
Optionally, the apparatus 400 further comprises a display module; the display module is used for: and under the condition that the target account does not meet the service verification rule, displaying a prompt message, wherein the prompt message is used for prompting that the account is not verified to be passed and account information cannot be input.
It should be appreciated that the apparatus 400 herein is embodied in the form of functional modules. The term module herein may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an optional example, as can be understood by those skilled in the art, the apparatus 400 may be specifically a data processing device in the foregoing embodiment, or functions of the data processing device in the foregoing embodiment may be integrated in the apparatus 400, and the apparatus 400 may be configured to execute each procedure and/or step corresponding to the data processing device in the foregoing method embodiment, and details are not described here again to avoid repetition.
The device 400 has functions of implementing corresponding steps executed by the data processing apparatus in the method 200; the above functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.
Fig. 5 illustrates another apparatus 500 for managing account information according to an embodiment of the present disclosure. The apparatus 500 comprises: a processor 510, a communication interface 520, and a memory 530. Wherein the processor 510, the communication interface 520 and the memory 530 are in communication with each other via an internal connection path, the memory 530 is configured to store instructions, and the processor 510 is configured to execute the instructions stored in the memory 530 to control the communication interface to transmit and/or receive signals.
It should be understood that the apparatus 500 may be used for executing each step and/or flow corresponding to the data processing device in the above method embodiments. Alternatively, the memory 530 may include a read-only memory and a random access memory, and provides instructions and data to the processor 510. A portion of memory 530 may also include non-volatile random access memory. For example, memory 530 may also store device type information. The processor 510 may be configured to execute instructions stored in the memory 530, and when the processor 510 executes the instructions stored in the memory 530, the processor 510 is configured to perform the various steps and/or processes of the method embodiments described above in relation to the data processing apparatus.
It should be understood that, in the embodiment of the present application, the processor 510 of the apparatus 500 may be a Central Processing Unit (CPU), and the processor 510 may also be other general processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software elements in a processor. The software elements may be located in ram, flash, rom, prom, or eprom, registers, among other storage media that are well known in the art. The storage medium is located in a memory, and a processor executes instructions in the memory, in combination with hardware thereof, to perform the steps of the above-described method. To avoid repetition, it is not described in detail here.
The present application provides a readable computer storage medium for storing a computer program for implementing the method corresponding to the data processing apparatus in the above-described embodiments.
The present application provides a computer program product comprising a computer program (also referred to as code, or instructions) which, when run on a computer, can carry out the method corresponding to the data processing device in the above-described embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (13)
1. A method for managing account information, comprising:
determining a target account type of a target account;
selecting a target account template from a plurality of account templates included in an account template management library based on the target account type, wherein the target account template corresponds to the target account type;
acquiring account information of the target account based on the target account template, wherein the account information comprises a product identifier, a product type, an account identifier and a financial institution identifier;
judging whether the target account meets the business verification rule or not based on a business verification rule in an account business rule base, the product identification, the product type, the account identification and the financial institution identification of the target account;
and under the condition that the target account meets the service verification rule, establishing a corresponding relation between the product corresponding to the product identifier and the account corresponding to the account identifier, and recording account information of the target account.
2. The method of claim 1, wherein the target account template comprises an account type field, a virtual-real account flag field, an account name field, an account full name field, an account short name field, and an account opening institution field.
3. The method of claim 2, wherein the target account type is a funding account or a security account;
the account template corresponding to the fund account also comprises a public field of the fund account and a personalized field of the fund account, wherein the public field of the fund account comprises a payment system line number field, an account opening bank code field and an account opening bank name field;
the account template corresponding to the security account further comprises a public field of the security account and a personalized field of the security account, and the public field of the security account comprises a security code field.
4. The method of claim 1, wherein the traffic verification rule comprises at least one of the following rules:
whether the account type is contained within a range of account types required for a particular product type;
whether the same product allows for the addition of multiple accounts of the same account type;
whether a particular account is allowed to be shared between different products;
whether a particular account is allowed to be shared between different financial institutions for different products; alternatively, the first and second electrodes may be,
the same account can be shared by multiple financial institutions participating in the same product.
5. The method according to any one of claims 1 to 4, further comprising:
and under the condition that the target account does not meet the service verification rule, displaying a prompt message, wherein the prompt message is used for prompting that the account verification fails and account information cannot be input.
6. An apparatus for managing account information, comprising:
the processing module is used for determining the target account type of the target account; selecting a target account template from a plurality of account templates included in an account template management library based on the target account type, wherein the target account template corresponds to the target account type;
the acquisition module is used for acquiring account information of the target account based on the target account template, wherein the account information comprises a product identifier, a product type, an account identifier and a financial institution identifier;
the processing module is further configured to: judging whether the target account meets the business verification rule or not based on a business verification rule in an account business rule base, the product identification, the product type, the account identification and the financial institution identification of the target account; and under the condition that the target account meets the service verification rule, establishing a corresponding relation between the product corresponding to the product identifier and the account corresponding to the account identifier, and recording account information of the target account.
7. The apparatus of claim 6, wherein the target account template comprises an account type field, a virtual-real account flag field, an account name field, an account full name field, an account short name field, and an account opening institution field.
8. The apparatus of claim 7, wherein the target account type is a funding account or a security account;
the account template corresponding to the fund account also comprises a public field of the fund account and a personalized field of the fund account, wherein the public field of the fund account comprises a payment system line number field, an account opening bank code field and an account opening bank name field;
the account template corresponding to the security account further comprises a public field of the security account and a personalized field of the security account, and the public field of the security account comprises a security code field.
9. The apparatus of claim 6, wherein the traffic verification rule comprises at least one of the following rules:
whether the account type is contained within a range of account types required for a particular product type;
whether the same product allows for the addition of multiple accounts of the same account type;
whether a particular account is allowed to be shared between different products;
whether a particular account is allowed to be shared between different financial institutions for different products; alternatively, the first and second electrodes may be,
the same account can be shared by multiple financial institutions participating in the same product.
10. The apparatus of any one of claims 6 to 9, further comprising a display module;
the display module is used for:
and under the condition that the target account does not meet the service verification rule, displaying a prompt message, wherein the prompt message is used for prompting that the account verification fails and account information cannot be input.
11. An apparatus for managing account information, comprising: a processor coupled to a memory for storing a computer program that, when invoked by the processor, causes the apparatus to perform the method of any of claims 1 to 5.
12. A computer-readable storage medium for storing a computer program comprising instructions for implementing the method of any one of claims 1 to 5.
13. A computer program product, characterized in that it comprises a computer program which, when executed by a processor, implements the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111525734.8A CN114187116A (en) | 2021-12-14 | 2021-12-14 | Method and apparatus for managing account information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111525734.8A CN114187116A (en) | 2021-12-14 | 2021-12-14 | Method and apparatus for managing account information |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114187116A true CN114187116A (en) | 2022-03-15 |
Family
ID=80543697
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111525734.8A Pending CN114187116A (en) | 2021-12-14 | 2021-12-14 | Method and apparatus for managing account information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114187116A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115828322A (en) * | 2022-11-25 | 2023-03-21 | 中电金信软件(上海)有限公司 | Method and device for verifying integrity of data storage, electronic equipment and storage medium |
-
2021
- 2021-12-14 CN CN202111525734.8A patent/CN114187116A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115828322A (en) * | 2022-11-25 | 2023-03-21 | 中电金信软件(上海)有限公司 | Method and device for verifying integrity of data storage, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7805369B2 (en) | Anti-financial crimes business network | |
| Lo et al. | Assets on the blockchain: An empirical study of Tokenomics | |
| US10733674B2 (en) | System and method for pattern-recognition based monitoring and controlled processing of data objects based on conformity measurements | |
| CN113034274A (en) | Supply chain financial service system and method based on block chain and terminal equipment | |
| CN112381645A (en) | Information processing method and device for bill transaction | |
| CN113205402A (en) | Account checking method and device, electronic equipment and computer readable medium | |
| US20140324703A1 (en) | Money services system | |
| KR20200019455A (en) | Apparatus for tracking cryptographic transaction using scraper and method of the same | |
| CN115063228A (en) | Anti-money laundering management platform and anti-money laundering method | |
| US20150066750A1 (en) | Payments Perfection and Processing System | |
| CN114187116A (en) | Method and apparatus for managing account information | |
| WO2016131084A1 (en) | Bill payment system | |
| CN112767107A (en) | Method, apparatus, device, medium and program product for detecting blacklist | |
| CN113034275A (en) | Management system and method based on block chain network and terminal equipment | |
| US20210027365A1 (en) | Method and system for using test deposits to detect unlisted accounts associated with users of a data management system | |
| CN111242779A (en) | Financial data characteristic selection and prediction method, device, equipment and storage medium | |
| CN115983995A (en) | Transaction service supervision method, device, equipment and storage medium | |
| US11557000B1 (en) | Systems and methods for automated teller drawer counting and balancing | |
| TWI618013B (en) | Automatic deposit cheque system and method of perfomring the same | |
| CN115062079A (en) | Transaction flow processing method, device, equipment and storage medium | |
| CN111784422A (en) | Data management method, device, storage medium and electronic equipment | |
| EP3847608A1 (en) | A system and process for the verification of data | |
| RU215982U1 (en) | A device for the remote provision of insurance services using the recognition of an electronic passport of the Russian Federation on a plastic card | |
| CN111292051B (en) | Foreign exchange business processing method, device, equipment and medium | |
| CN112785406B (en) | Account checking method, device, equipment and storage medium |
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 |