Salary issuing method and device, electronic equipment and medium

Abstract

The invention provides a salary issuing method and device, electronic equipment, a medium and a computer program product. The method and the device can be used in the technical field of big data and financial science and technology. The salary issuing method comprises the steps that a first salary issuing template before editing is sent to a client side, in response to editing of a user on the first salary issuing template, a second salary issuing template after editing is obtained, and the second salary issuing template comprises necessary salary issuing information and user-defined demand information; m threads are called to analyze the necessary information and the demand information to a database, the necessary information in the database is uploaded to a dynamic account system, the dynamic account system carries out salary issuing according to the necessary information, and m is an integer larger than or equal to 1; and forming issuing details according to the necessary information, the demand information and the salary issuing state in the database after the salary is issued, and sending the issuing details to a client.

Description

Technical Field

[0001] The present disclosure relates to the field of big data and financial technology, and more specifically, to a wage payment method, device, electronic device, medium and computer program product. Background Art

[0002] Payroll payment by an enterprise refers to the payment of wages, subsidies or labor fees to employees of the enterprise by enterprise users through financial institutions. Financial institutions are generally commercial banks, and payroll payment by an enterprise is a basic business of the bank's public system. Currently, enterprise users operate through corresponding payroll products, download fixed templates on the enterprise online banking page, fill in the templates according to the requirements, and submit instructions to the enterprise online banking server for pre-analysis and verification of the submitted files. After verification, the subsequent processing links are carried out.

[0003] The existing steps for salary payment are as follows.

[0004] 1. The customer enters the product submission page, clicks the "Download Template" link on the page, and downloads different versions of templates according to their needs, including 1.0, 1.1, 1.2, 2.0, 3.0, etc. The fields contained in different templates are not all the same, but they include basic elements of agency payment (such as "payer name", "payer account", "recipient name", "recipient card number", "amount of agency payment", "purpose of agency payment" and "whether the payer has an account in another bank") and non-basic elements (such as "date", "currency", "account opening area", "receiving area", "opening bank", "receiving bank", "PBOC name", "PBOC number", "remarks", "recipient mobile phone number", "reimbursement number", "number of documents", "sequence number" and "details mark", etc.).

[0005] 2. Parse the template selected by the user. Templates of versions 1.0, 1.1 and 1.2 are parsed according to the scheduled parsing process. The element information of the template is extracted and registered in the batch table and instruction table of the server, and the dynamic account processing method is marked as scheduled processing; templates of versions 2.0 and 3.0 are processed in real time.

[0006] 3. After the analysis is completed, the subsequent dynamic account processing process is carried out. The scheduled template only processes 6 sessions a day, and the real-time template data is processed once every half an hour. Summary of the invention

[0007] In view of this, the present disclosure provides a salary payment method, device, electronic device, computer-readable storage medium and computer program product that saves resources, has high system cohesion and low user learning cost.

[0008] One aspect of the present disclosure provides a wage payment method, comprising: sending a first wage payment template before editing to a client, and in response to a user editing the first wage payment template, obtaining an edited second wage payment template, wherein the second wage payment template includes necessary information for wage payment and user-defined requirement information; calling m threads to parse the necessary information and the requirement information into a database, and sending the necessary information in the database to a dynamic account system, wherein the dynamic account system performs wage payment according to the necessary information, and m is an integer greater than or equal to 1; and after the wage is paid, forming payment details according to the necessary information, the requirement information and the wage payment status in the database, and sending the payment details to the client.

[0009] According to the wage payment method of the embodiment of the present disclosure, the necessary information and demand information of the acquired second wage payment template are parsed into the database by calling m threads, and the necessary information in the database is sent to the dynamic account system, so that the dynamic account system can perform wage payment according to the necessary information. After the wage is paid, payment details are formed according to the necessary information, demand information and wage payment status in the database, and the payment details are sent to the client. Compared with the prior art, the wage payment method of the present disclosure has only one first wage payment template for users to choose from, and users do not need to understand the advantages and disadvantages of many templates before making a choice, thereby reducing the user's learning cost for the template. Having only one first wage payment template will not cause compatibility issues. Having only one first wage payment template only requires the m threads originally designed to parse the template, and there is no need to increase threads during use, thereby reducing resource waste and making the system design highly cohesive.

[0010] In some embodiments, the necessary information includes fixed fields and fixed field values, the required information includes custom fields and custom field values, and the step of calling m threads to parse the necessary information and the required information into a database, and sending the necessary information in the database to the dynamic account system includes: calling a first thread to check the fixed fields and the fixed field values ​​according to a pre-established first verification rule, and when the fixed fields and the fixed field values ​​pass the verification, the first thread parses the fixed fields and the fixed field values ​​into the database; when the fixed fields and the fixed field values ​​pass the verification, calling a second thread to parse the custom fields and the custom field values ​​into the database; and when the fixed fields and the fixed field values ​​pass the verification, calling a third thread to send the fixed fields and the fixed field values ​​to the dynamic account system.

[0011] In some embodiments, the third thread uploads the fixed field and the fixed field value to the dynamic account system according to the real-time upload rule.

[0012] In some embodiments, when the fixed field and the fixed field value verification fail, a first error prompt is returned to the client.

[0013] In some embodiments, when the fixed field and the fixed field value are verified, before the step of calling the second thread to parse the custom field and the custom field value into the database, the method also includes: calling the second thread to verify the custom field and the custom field value according to a pre-established second verification rule, wherein, when the custom field and the custom field value are verified, calling the second thread to parse the custom field and the custom field value into the database; when the custom field and the custom field value are not verified, returning a second error prompt to the client, and calling the second thread to parse the custom field and the custom field value into the database.

[0014] In some embodiments, the step of the first thread parsing the fixed fields and the fixed field values ​​into a database includes: assigning an instruction sequence to the fixed fields and the corresponding fixed field values ​​and adding them to an instruction table; adding a link address of the instruction table to a batch table; and saving the instruction table and the batch table in a database.

[0015] In some embodiments, the step of calling a second thread to parse the custom field and the custom field value into a database includes: assigning an instruction sequence to the custom field and adding it to a first custom table; assigning an instruction sequence to the custom field value corresponding to the custom field and adding it to a second custom table; and saving the first custom table and the second custom table in the database.

[0016] Another aspect of the present disclosure provides a wage payment device, including: an acquisition module, the acquisition module is used to execute sending a first wage payment template before editing to a client, and in response to a user's editing of the first wage payment template, acquire a second wage payment template after editing, wherein the second wage payment template includes necessary information for wage payment and user-defined requirement information; a sending module, the sending module is used to execute calling m threads to parse the necessary information and the requirement information into a database, and send the necessary information in the database to a dynamic account system, wherein the dynamic account system performs wage payment according to the necessary information, and m is an integer greater than or equal to 1; and a feedback module, the feedback module is used to form payment details according to the necessary information, the requirement information and the wage payment status in the database after the salary is paid, and send the payment details to the client.

[0017] Another aspect of the present disclosure provides an electronic device, comprising one or more processors and one or more memories, wherein the memories are used to store executable instructions, and when the executable instructions are executed by the processors, the above-mentioned method is implemented.

[0018] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above method when executed.

[0019] Another aspect of the present disclosure provides a computer program product, comprising a computer program, wherein the computer program comprises computer executable instructions, and the instructions are used to implement the method as described above when executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0021] Figure 1 An exemplary system architecture to which the method and apparatus according to an embodiment of the present disclosure can be applied is schematically shown;

[0022] Figure 2 A flowchart of a salary payment method according to an embodiment of the present disclosure is schematically shown;

[0023] Figure 3 A flowchart schematically shows the steps of calling m threads to parse necessary information and required information into a database, and sending the necessary information in the database to the dynamic account system according to an embodiment of the present disclosure;

[0024] Figure 4 A flowchart schematically shows the steps of a first thread parsing fixed fields and fixed field values ​​into a database according to an embodiment of the present disclosure;

[0025] Figure 5 A flowchart schematically shows the steps of calling a second thread to parse a custom field and a custom field value into a database according to an embodiment of the present disclosure;

[0026] Figure 6 A block diagram of a salary payment device according to an embodiment of the present disclosure is schematically shown;

[0027] Figure 7 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0028] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0029] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0030] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0031] When using expressions such as "at least one of A, B or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). The terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, features defined as "first" and "second" may explicitly or implicitly include one or more of the said features.

[0032] Payroll payment by an enterprise refers to the payment of wages, subsidies or labor fees to employees of the enterprise by enterprise users through financial institutions. Financial institutions are generally commercial banks, and payroll payment by an enterprise is a basic business of the bank's public system. Currently, enterprise users operate through corresponding payroll products, download fixed templates on the enterprise online banking page, fill in the templates according to the requirements, and submit instructions to the enterprise online banking server for pre-analysis and verification of the submitted files. After verification, the subsequent processing links are carried out.

[0033] The existing steps for salary payment are as follows.

[0034] 1. The customer enters the product submission page, clicks the "Download Template" link on the page, and downloads different versions of templates according to their needs, including 1.0, 1.1, 1.2, 2.0, 3.0, etc. The fields contained in different templates are not all the same, but they include basic elements of agency payment (such as "payer name", "payer account", "recipient name", "recipient card number", "amount of agency payment", "purpose of agency payment" and "whether the payer has an account in another bank") and non-basic elements (such as "date", "currency", "account opening area", "receiving area", "opening bank", "receiving bank", "PBOC name", "PBOC number", "remarks", "recipient mobile phone number", "reimbursement number", "number of documents", "sequence number" and "details mark", etc.).

[0035] 2. Parse the template selected by the user. Templates of versions 1.0, 1.1 and 1.2 are parsed according to the scheduled parsing process. The element information of the template is extracted and registered in the batch table and instruction table of the server, and the dynamic account processing method is marked as scheduled processing; templates of versions 2.0 and 3.0 are processed in real time.

[0036] 3. After the analysis is completed, the subsequent dynamic account processing process is carried out. The scheduled template only processes 6 sessions a day, and the real-time template data is processed once every half an hour.

[0037] From the above process, it can be seen that users need to have personalized needs when submitting data, but many templates have limitations and cannot meet the real needs of users. The current problems are as follows:

[0038] ① There are many templates. As can be seen from the template version number, the templates are changed according to customer needs. Currently, there are 5 template versions, but they still cannot meet all customer needs. As a result, customers need to understand the advantages and disadvantages of many templates and then download and fill them out according to their own needs.

[0039] ② Poor compatibility. Except for the basic mandatory elements (involving dynamic account parsing), the non-mandatory elements of each template are not nearly the same, and the order of fields is inconsistent. Therefore, the new version of the template cannot replace the old version of the template, resulting in the inability to unify the template. In actual use, due to user usage habits, the template will not be changed actively, especially for old customers with relatively stable remittance.

[0040] ③ Low cohesion. Each template has a dedicated thread for pre-parsing and parsing according to the version number in the file. If the customer needs to update again, new templates and corresponding threads need to be added again, which greatly expands the thread design and file temporary storage of the file transfer process, resulting in resource waste and low system design cohesion.

[0041] ④High learning cost for customers. Different templates have different filling specifications. When customers initially choose a template, they need to inquire, learn, compare, and select each template. If customers want to change the template, they need to relearn the new template specifications. In addition, different templates may cause other detailed reconciliation issues after the account is changed, which may cause some trouble for customers.

[0042] The embodiments of the present disclosure provide a method, device, electronic device, computer-readable storage medium and computer program product for wage payment. The wage payment method includes: sending a first wage payment template before editing to a client, and in response to a user editing the first wage payment template, obtaining an edited second wage payment template, wherein the second wage payment template includes necessary information for wage payment and user-defined demand information; calling m threads to parse the necessary information and demand information into a database, and sending the necessary information in the database to a dynamic account system, wherein the dynamic account system performs wage payment according to the necessary information, and m is an integer greater than or equal to 1; and after the wage is paid, forming a payment detail according to the necessary information, demand information and wage payment status in the database, and sending the payment detail to the client.

[0043] It should be noted that the wage payment method, device, electronic device, computer-readable storage medium and computer program product disclosed in the present invention can be used in the field of big data technology, and can also be used in any field other than the field of big data technology, such as the field of financial technology. The field of the present invention is not limited here.

[0044] Figure 1 The exemplary system architecture 100 to which the wage payment method, apparatus, electronic device, computer-readable storage medium and computer program product according to the embodiments of the present disclosure can be applied is schematically shown. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0045] like Figure 1 As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0046] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0047] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0048] The server 105 may be a server that provides various services, such as a background management server (only an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0049] It should be noted that the wage payment method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the wage payment device provided in the embodiment of the present disclosure can generally be set in the server 105. The wage payment method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the wage payment device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0050] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0051] The following will be based on Figure 1 The scene described by Figure 2 to Figure 5 The salary payment method according to the embodiment of the present disclosure is described in detail.

[0052] Figure 2 The flowchart of the wage payment method according to the embodiment of the present disclosure is schematically shown.

[0053] like Figure 2 As shown, the salary payment method of this embodiment includes operations S210 to S230.

[0054] In operation S210, the first salary payment template before editing is sent to the client, and in response to the user editing the first salary payment template, the edited second salary payment template is obtained, wherein the second salary payment template includes necessary information for salary payment and user-defined requirement information.

[0055] In some examples, the first salary payment template may be as shown in Table 1.

[0056] Table 1

[0057]

[0058] It is understandable that the client can provide a link to download the first salary payment template. The link only provides one first salary payment template. The first salary payment template can be an xls template. The version number mark is cancelled in the template, and only the basic mandatory element header is retained, that is, the necessary information header for salary payment and the user-defined requirement information header, such as Table 1. The first row adds customer prompt information, and the fields under the necessary information need to be filled in according to the specifications. The custom fields under the requirement information need to modify the second row fields to the fields expressed by the user's wishes. In this way, the original templates with multiple version numbers can be integrated into one, which is convenient for the unification of the second salary payment template returned by the user after editing, and for subsequent unified processing, solving the problem of poor compatibility of multiple templates. At the same time, it allows users to fill in custom fields according to their own needs, without having to learn different filling methods according to different template versions, thereby reducing customer learning costs.

[0059] Of course, the fixed fields under the necessary information in Table 1 are only for illustration purposes, and the fixed fields can be adjusted according to actual needs and should not be construed as limitations on the present disclosure.

[0060] In operation S220, m threads are called to parse necessary information and demand information into a database, and the necessary information in the database is sent to the dynamic account system, wherein the dynamic account system performs salary payment according to the necessary information, and m is an integer greater than or equal to 1.

[0061] As an implementable approach, the necessary information includes fixed fields and fixed field values, and the required information includes custom fields and custom field values, such as Figure 3 As shown, operation S220 calls m threads to parse necessary information and required information into a database, and sends the necessary information in the database to the dynamic account system, including operations S221 to S223.

[0062] In operation S221, the first thread is called to check the fixed fields and the fixed field values ​​according to a pre-defined first check rule. When the fixed fields and the fixed field values ​​pass the check, the first thread parses the fixed fields and the fixed field values ​​into a database.

[0063] It can be understood that the first thread is used to parse and verify the necessary information required for the account dynamic system. The header fields under the necessary information, such as columns 1 to 5 in Table 1, are scanned and parsed according to the pre-set first verification rule. The first verification rule can be understood as a filling specification rule. When the fixed field and the fixed field value pass the verification, the first thread parses the fixed field and the fixed field value into the database. In some examples, a successful verification flag, such as flag A1, can be returned to the client.

[0064] As a possible way to achieve this, Figure 4 As shown, operation S221 is a step in which the first thread parses the fixed fields and the fixed field values ​​into a database, including operations S2211 to S2213.

[0065] In operation S2211, fixed fields and corresponding fixed field values ​​are assigned instruction sequences and added to an instruction table.

[0066] In operation S2212, a link address of the instruction table is added to the batch table.

[0067] In operation S2213, the instruction table and the batch table are saved in the database.

[0068] Operations S2211 to S2213 can facilitate the first thread to parse the fixed fields and the fixed field values ​​into the database.

[0069] According to some embodiments of the present disclosure, when the fixed field and the fixed field value verification fails, the first error prompt is returned to the client. It is understandable that when the client fills in the specification incorrectly, a mark of incorrect filling, such as mark A0, can be returned to the client, and the subsequent thread call is terminated at the same time. This can facilitate the user to understand that the information that he has filled in incorrectly, and terminating the subsequent thread call can save computing resources.

[0070] In some examples, if the client receives an A0 return flag, it can call an error translation program to return the actual non-standard errors (such as "the amount contains illegal characters") to the client for display. The client checks and modifies the filled-in second salary payment template according to the error prompt.

[0071] In operation S222, when the fixed field and the fixed field value are verified, the second thread is called to parse the custom field and the custom field value into the database. It can be understood that the second thread is used to parse the custom field that meets the user's personalized needs, thereby parsing the custom field and the custom field value into the database.

[0072] As a possible way to achieve this, Figure 5As shown, operation S222 calls the second thread to parse the custom field and the custom field value into the database, including operations S2221 to S2223.

[0073] In operation S2221, the custom fields are assigned an instruction sequence and then added to the first custom table.

[0074] In operation S2222, the custom field values ​​corresponding to the custom fields are assigned an instruction sequence and then added to the second custom table.

[0075] In operation S2223, the first custom table and the second custom table are saved in the database.

[0076] It should be noted that, relative to the instruction table and batch table in the database, the present disclosure adds non-essential information, that is, a header record table of demand information, which is defined as the first custom table. The present disclosure adds a value storage table of non-essential information, which is defined as the second custom table. The second thread can first cut the header fields of the demand information column by column, and enter the custom fields into the first custom table, so that the demand information in the second salary payment template can be split by column; then continue to scan row by row, and write the custom field values ​​in the second salary payment template into the value storage table. Through operations S2221 to S2223, it is easy to call the second thread to parse the custom fields and custom field values ​​into the database.

[0077] In some examples, the first custom table and the second custom table are mapped and associated using the "table header name" as a foreign key, and the instruction table is associated using the "instruction sequence number" as a primary key. In this way, the overall association of the required information and the necessary information can be achieved.

[0078] According to some embodiments of the present disclosure, when the fixed fields and the fixed field values pass the verification, before the step of calling the second thread to parse the custom fields and the custom field values into the database, the method further includes: calling the second thread to verify the custom fields and the custom field values according to a pre-established second verification rule, wherein when the custom fields and the custom field values pass the verification, calling the second thread to parse the custom fields and the custom field values into the database; when the custom fields and the custom field values do not pass the verification, returning a second error prompt to the client and calling the second thread to parse the custom fields and the custom field values into the database. Thus, it is possible to verify the fields customized by the user, facilitating the user to understand whether the self-filled custom fields and custom field values conform to the filling specifications. Since the custom fields and custom field values are not necessary fields for account transactions, the custom fields and custom field values can be parsed into the database regardless of whether the filling conforms to the specifications. However, when at least one of the custom fields and custom field values does not conform to the specifications, a second error prompt needs to be returned to the client, thereby prompting the user that there is an error. This can improve user satisfaction.

[0079] In some examples, semantic fuzzy matching is performed on the header names. For example, those containing the words "day" or "date" are defined as the date type, and this element is defined as the date type in the second custom table. If filled in as other types, parsing errors will occur; fields containing the word "quantity" are specified as the int type, the mobile phone number is 11 digits long and is of the int type, and so on. The second thread verifies whether the filled values of the elements in the second custom table are compliant (including length / partial Chinese-English conversion). Since it is non-essential information and does not affect the account transaction operation, and it is a custom value filled in by the customer according to their own needs, strong regulations and strong verifications on the content are not performed, and only pre-parsing of records and basic specifications (numeric type / length, etc.) is provided. Therefore, if non-compliant filling is found, the second thread returns a non-compliant flag to the client, such as flag B0. Then, an error translation program can be called to return the actual non-compliant filling error (such as "the mobile phone number must be 11 digits") to the client for display to the user, and the user can check and modify the submitted file according to the error prompt.

[0080] In operation S223, when the fixed fields and the fixed field values pass the verification, call the third thread to send the fixed fields and the fixed field values to the account transaction system. Thus, the account transaction system can perform salary disbursement based on the fixed fields and the fixed field values. By operating S221 to operation S223, it is convenient to call m threads to parse the necessary information and the required information into the database, and send the necessary information in the database to the account transaction system.

[0081] In some examples, the third thread uploads the fixed fields and fixed field values ​​to the dynamic account system according to the real-time upload rules. It can be understood that the third thread is used to upload the fixed fields and fixed field values ​​under the necessary information required for the dynamic account. Since the custom fields and custom field values ​​in the demand information are non-mandatory fields and do not involve dynamic account elements, there is no need to upload the custom fields and custom field values.

[0082] In some examples, in order to facilitate old users who use the existing wage payment method to switch smoothly to the method disclosed in the present invention, the third thread is called to register the necessary information in the batch table and instruction table (stock table) of the database. This part deletes the timed analysis process of the original process and only retains the real-time analysis program module of the original process. The third thread disassembles the branch number / area number / each analysis result / and other key information required for the account activation based on the necessary information data in the table, and sends the information to the package or calls the online service according to the original real-time process to ensure that all subsequent account activations follow the real-time account activation process. In this way, the analysis method is changed from the original two to one, and the timeliness is faster, which solves the problem that different templates of the original process have different analysis threads and solves the problem of low cohesion.

[0083] In operation S230, after the salary is paid, payment details are formed according to the necessary information, required information and salary payment status in the database, and the payment details are sent to the client.

[0084] According to the wage payment method of the embodiment of the present disclosure, the necessary information and demand information of the acquired second wage payment template are parsed into the database by calling m threads, and the necessary information in the database is sent to the dynamic account system, so that the dynamic account system can perform wage payment according to the necessary information. After the wage is paid, payment details are formed according to the necessary information, demand information and wage payment status in the database, and the payment details are sent to the client. Compared with the prior art, the wage payment method of the present disclosure has only one first wage payment template for users to choose from, and users do not need to understand the advantages and disadvantages of many templates before making a choice, thereby reducing the user's learning cost for the template. Having only one first wage payment template will not cause compatibility issues. Having only one first wage payment template only requires the m threads originally designed to parse the template, and there is no need to increase threads during use, thereby reducing resource waste and making the system design highly cohesive.

[0085] The following describes in detail the wage payment method according to the embodiment of the present disclosure. It is worth noting that the following description is only an exemplary description and is not a specific limitation of the present disclosure.

[0086] This disclosure integrates existing templates by adding background pre-analysis thread splitting and fuzzy matching and other file processing thread pools, and only provides a single template download link, which not only retains all the elements of traditional templates, but also allows customers to customize fields according to their own needs. It also provides unified pre-analysis and analysis threads in the background, unifies the dynamic account process, and makes all the details visible to customers on the front-end page of the enterprise network unified.

[0087] The implementation of the salary payment method disclosed in the present invention is as follows.

[0088] a. Corporate online banking front-end page: the template submission page visible to customers.

[0089] b. Corporate online banking server: used to complete the transmission and basic processing of templates, including the pre-parsing, parsing and return thread design in this disclosure.

[0090] c. Dynamic account processing system, used for dynamic account processing on behalf of others.

[0091] The above involves three parties, namely the corporate online banking front-end page, the corporate online banking server and the account dynamic processing end. The interaction process of each party is as follows.

[0092] 1. Corporate online banking front-end page: The template download link provided by the front desk changes the template list, only provides one xls template, cancels the version number mark in the template, and only retains the basic mandatory element header. The subsequent header is changed to user-defined, and customer prompt information is added. The mandatory fields must be filled in according to the specifications, and the custom fields must be modified to the real header in the second row. In this way, the original templates with multiple version numbers are integrated into one, the mandatory fields of the uploaded files are unified, and the subsequent unified processing solves the problem of poor compatibility. At the same time, customers are allowed to fill in the custom fields according to their own needs, and there is no need to learn different filling methods according to different template versions, which reduces the customer's learning cost.

[0093] 2. Add a file processing thread pool on the corporate online banking server. The thread design is as follows.

[0094] 1) Pre-analysis thread A: This thread is used to pre-analyze and verify the mandatory information required for account activation. The mandatory element header field AF column is scanned and pre-analyzed according to the original filling specification rules. If the verification fails, that is, the customer fills in the specification incorrectly, the flag A0 is returned and the subsequent thread is terminated; if the front end of the page receives the A0 return flag, the error translation program is called to return the actual non-standard filling error (for example, "the amount filled in contains illegal characters") to the front end page to display to the customer. The customer checks and modifies the submitted file according to the error prompt. If the verification result passes, the mandatory element is registered in the batch table and instruction table of the corporate online banking server, the flag A1 is returned, and the custom file pre-analysis thread B is called.

[0095] 2) Pre - parsing Thread B: This thread is used to perform pre - parsing verification on custom fields that meet the personalized needs of customers. In the database, a non - basic element header record table (defined as Table I) and a non - basic element value storage table (defined as Table II) are newly added. Thread B first cuts the non - mandatory header fields (after column G) column by column, enters the header names and writes them into the header record table (Table I), thus splitting the non - basic elements in the original file by column; then it scans row by row, enters the field values and writes them into the element value storage table (Table II). This step realizes the registration of all values of the non - mandatory elements in the uploaded file. The two tables are mapped and associated with the "header name" as the foreign key, and the "instruction serial number" is used as the primary key to associate with the basic element table. In this way, the overall association of custom elements and mandatory elements can be achieved.

[0096] 3) After splitting, perform semantic fuzzy matching on the header names. For example, those containing the words "day" or "date" are defined as the date type, and this element is defined as the date type in Table II. If it is filled in as other types, a pre - parsing error will be reported; fields containing the word "quantity" are specified as the int type, mobile phone numbers are 11 - digit length int type, etc. Thread B verifies whether the filled values of the elements in Table II are compliant (including length / partial Chinese - English conversion). Since they are non - basic elements, they do not affect the account - moving operation, and they are custom values filled in by customers according to their own needs. Therefore, no strict regulations and strong verifications on the content are carried out, only pre - parsing of records and basic specifications (numeric type / length, etc.) is provided. Therefore, if pre - parsing B finds non - compliant filling, the thread returns flag B0, calls the error translation program, and returns the actual non - compliant filling error (such as "mobile phone number must be 11 digits") to the front - end page for display to the customer. The customer checks and modifies the submitted file according to the error prompt. If the verification result passes, flag B1 is returned, and the file parsing Thread C is called.

[0097] 4) Modifying Parsing Thread C: This thread is used to disassemble and register the mandatory field elements required for account - moving. Since the non - mandatory fields in the custom template do not involve account - moving elements, there is no need to parse the custom elements. After all the element values of the payroll template are recorded and pre - parsed, when calling Parsing Thread C, the mandatory element information will be registered in the batch table and instruction table (stock table) of the corporate online banking server. This part deletes the timed parsing process of the original process and only retains the quasi - real - time parsing program module of the original process. This thread disassembles key information such as the branch number / area number / each parsing result required for account - moving according to the mandatory element data in the table, and performs information uploading, packing or calling online services according to the original quasi - real - time process, ensuring that all subsequent account - moving processes follow the quasi - real - time account - moving process. In this way, the parsing method changes from the original two to one, and the timeliness becomes faster, solving the problem that different templates in the original process have different parsing threads and the problem of low cohesion.

[0098] 3. The backend account movement system only needs to follow the quasi-real-time process to move accounts, and the account movement process remains unchanged.

[0099] 4. Newly added merge thread D on the corporate online banking server: This thread is divided into two blocks. Block 1 scans the dynamic account status of the batch table and instruction table (these records are all mandatory element records) and updates them to the front-end page. Block 2 scans Table I and Table II to return all customer custom field information. The two blocks are linked through the "instruction serial number" field shared by the batch table / instruction detail table / non-basic element header record table / non-basic element value record table to complete the scanning operation. After the thread scans, the dispatched file information is returned to the detail query thread and detail download thread for subsequent operations by the customer.

[0100] This disclosure integrates existing templates by adding file processing thread pools such as fuzzy matching and background splitting, which not only retains all the elements of traditional templates, but also allows customers to customize fields according to their own needs. It provides corporate banking customers with "thousands of faces" submission templates, and the background unified integration processing mode can meet the different needs of customers, reduce customer learning costs, improve customer experience, and at the same time improve the cohesion of the background design, greatly improving the enterprise's requirements for the ease of use of the payroll template.

[0101] Based on the above-mentioned wage payment method, the present disclosure also provides a wage payment device. Figure 6 The wage payment device is described in detail.

[0102] Figure 6 The structural block diagram of the salary payment device according to the embodiment of the present disclosure is schematically shown.

[0103] The wage payment device 10 comprises an acquisition module 1 , a sending module 2 and a feedback module 3 .

[0104] Acquisition module 1, acquisition module 1 is used to perform operation S210: sending the first salary payment template before editing to the client, and in response to the user's editing of the first salary payment template, acquiring the edited second salary payment template, wherein the second salary payment template includes necessary information for salary payment and user-defined requirement information.

[0105] The sending module 2 is used to perform operation S220: calling m threads to parse the necessary information and required information into the database, and sending the necessary information in the database to the dynamic account system, wherein the dynamic account system performs salary payment according to the necessary information, and m is an integer greater than or equal to 1.

[0106] Feedback module 3, feedback module 3 is used to perform operation S230: after the salary is paid, payment details are formed according to the necessary information, demand information and salary payment status in the database, and the payment details are sent to the client.

[0107] According to the wage payment device 10 of the embodiment of the present disclosure, the necessary information and demand information of the acquired second wage payment template are parsed into the database by calling m threads, and the necessary information in the database is sent to the dynamic account system, so that the dynamic account system can perform wage payment according to the necessary information. After the wage is paid, the payment details are formed according to the necessary information, demand information and wage payment status in the database, and the payment details are sent to the client. Compared with the prior art, the wage payment method disclosed in the present disclosure has only one first wage payment template for users to choose from, and users do not need to understand the advantages and disadvantages of many templates before making a choice, thereby reducing the user's learning cost for the template. Having only one first wage payment template will not cause compatibility issues. Having only one first wage payment template only requires the initially designed m threads to parse the template, and there is no need to increase threads during use, thereby reducing resource waste and making the system design highly cohesive.

[0108] In addition, according to an embodiment of the present disclosure, any multiple modules among the acquisition module 1, the upload module 2 and the feedback module 3 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module.

[0109] According to an embodiment of the present disclosure, at least one of the acquisition module 1, the upload module 2 and the feedback module 3 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or can be implemented in any one of the three implementation methods of software, hardware and firmware, or in an appropriate combination of any of them.

[0110] Alternatively, at least one of the acquisition module 1, the sending module 2 and the feedback module 3 may be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function may be executed.

[0111] Figure 7 A block diagram of an electronic device suitable for implementing the above method according to an embodiment of the present disclosure is schematically shown.

[0112] like Figure 7As shown, the electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage part 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include an onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0113] In RAM 903, various programs and data required for the operation of electronic device 900 are stored. Processor 901, ROM 902 and RAM 903 are connected to each other via bus 904. Processor 901 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 902 and / or RAM 903. It should be noted that the program can also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0114] According to an embodiment of the present disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to the bus 904. The electronic device 900 may further include one or more of the following components connected to the I / O interface 905: an input portion 906 including a keyboard, a mouse, etc.; an output portion 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 908 including a hard disk, etc.; and a communication portion 909 including a network interface card such as a LAN card, a modem, etc. The communication portion 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage portion 908 as needed.

[0115] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0116] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus, or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 902 and / or RAM 903 described above and / or one or more memories other than ROM 902 and RAM 903.

[0117] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method of the embodiment of the present disclosure.

[0118] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 901. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0119] In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of a signal on a network medium, and downloaded and installed through the communication part 909, and / or installed from a removable medium 911. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0120] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0121] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0122] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0123] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0124] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for paying wages on behalf of others, characterized in that: include: Sending the first salary payment template before editing to the client, and in response to the user editing the first salary payment template, obtaining the edited second salary payment template, wherein the second salary payment template includes necessary information for salary payment and user-defined requirement information; Calling m threads to parse the necessary information and the demand information into a database, and sending the necessary information in the database to the dynamic account system, wherein the dynamic account system performs salary payment according to the necessary information, and m is an integer greater than or equal to 1; and After the salary is paid, payment details are formed according to the necessary information, the demand information and the salary payment status in the database, and the payment details are sent to the client.

2. The wage payment method according to claim 1, characterized in that: The necessary information includes fixed fields and fixed field values, the demand information includes custom fields and custom field values, calling m threads to parse the necessary information and the demand information into a database, and sending the necessary information in the database to the dynamic account system, including: Calling a first thread to check the fixed field and the fixed field value according to a pre-defined first check rule, when the fixed field and the fixed field value pass the check, the first thread parses the fixed field and the fixed field value into a database; When the fixed field and the fixed field value pass the verification, calling the second thread to parse the custom field and the custom field value into a database; and When the fixed field and the fixed field value are verified, the third thread is called to send the fixed field and the fixed field value to the dynamic account system.

3. The wage payment method according to claim 2, characterized in that: The third thread sends the fixed field and the fixed field value to the dynamic account system according to the real-time sending rule.

4. The wage payment method according to claim 2, characterized in that: When the fixed field and the fixed field value verification fail, a first error prompt is returned to the client.

5. The wage payment method according to claim 2, characterized in that: When the fixed field and the fixed field value are verified, before calling the second thread to parse the custom field and the custom field value into a database, the method further includes: The second thread is called to check the custom field and the custom field value according to a pre-established second check rule, wherein when the custom field and the custom field value pass the check, the second thread is called to parse the custom field and the custom field value into a database; when the custom field and the custom field value fail the check, a second error prompt is returned to the client, and the second thread is called to parse the custom field and the custom field value into a database.

6. The wage payment method according to claim 2, characterized in that: The step of the first thread parsing the fixed field and the fixed field value into a database includes: Assigning an instruction sequence to the fixed fields and the corresponding fixed field values ​​and then adding them to the instruction table; Adding the link address of the instruction table to the batch table; and The instruction table and the batch table are stored in a database.

7. The wage payment method according to claim 2, characterized in that: The step of calling the second thread to parse the custom field and the custom field value into a database includes: Assigning an instruction sequence to the custom fields and then adding them to the first custom table; Assigning an instruction sequence to the custom field value corresponding to the custom field and adding it to the second custom table; and The first custom table and the second custom table are saved in a database.

8. A salary payment device, characterized in that: include: an acquisition module, the acquisition module being used to send the first salary payment template before editing to the client, and in response to the user editing the first salary payment template, acquire the edited second salary payment template, wherein the second salary payment template includes necessary information for salary payment and user-defined requirement information; a sending module, the sending module is used to execute and call m threads to parse the necessary information and the demand information into a database, and send the necessary information in the database to the dynamic account system, wherein the dynamic account system performs salary payment according to the necessary information, and m is an integer greater than or equal to 1; and A feedback module is used to generate payment details according to the necessary information, the demand information and the salary payment status in the database after executing salary payment, and send the payment details to the client.

9. An electronic device, characterized in that: include: one or more processors; One or more memories, used to store executable instructions, wherein when the executable instructions are executed by the processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The storage medium stores executable instructions, which, when executed by a processor, implement the method according to any one of claims 1 to 7.

Images