JP2015179546A - Wrong salary payment detection system, method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To detect wrong payment of salary with high precision by a wrong salary payment detection system.SOLUTION: A wrong salary payment detection program includes: acquiring personnel event information applied to a detection object person in a detection object month; acquiring personnel event increase/decrease information representing an increase/decrease direction of the amount of money related to a salary item corresponding to the acquired personnel event information by using an increase/decrease table in which the increase/decrease direction of the amount of money related to the salary item is made to correspond to the personnel event information; acquiring salary detail information of the detection object month of the detection object person and salary detail information of the last month of the detection object month from a salary information database; acquiring salary detail increase/decrease information representing the increase/decrease direction of the amount of money related to the salary item corresponding to the acquired personnel event information from the last month to the detection object month by comparing the acquired salary detail information of the detection object month with the salary detail information of the last month; and comparing the increase/decrease direction of the personnel event increase/decrease information with the increase/decrease direction of the salary detail increase/decrease information and outputting notice information when the increase/decrease directions do not match each other.

Description

  Some embodiments according to the present invention relate to an erroneous salary detection system, method, and program.

  In companies and public institutions, there are often cases where a department (HR department or the like) that performs personnel-related processing and a department (Accounting Department or General Affairs Department) that calculate salary are set up separately. In departments that handle personnel-related processing, personnel systems that manage personnel information (such as career and address) of employees of companies and public institutions (hereinafter collectively referred to as companies) are widely used. In addition, in a department that calculates salary, a salary system that calculates salary of company employees is widely used. The personnel information managed by this personnel system and the salary information managed by the salary system (basic salary amount, various allowance amounts, etc.) may be related to each other. For example, with changes in personnel information such as promotion of employee's job title, it has often become necessary to change the basic salary and allowance of employees.

  However, for example, personnel information such as promotion and relocation is information related to personal privacy, so the number of people who are allowed to enter data may be limited, and general employees are not in a situation where they can see personnel information. There was a thing. For this reason, for example, a general employee of the accounting department cannot see the personnel information of the employee who performed the salary calculation, and it is difficult to detect an error in the salary calculation due to an error in data input.

  In addition, the human resources department that manages personnel information and the accounting department that manages salary information are often operated as different organizations, and there is often a situation in which mutual information does not circulate sufficiently due to the walls between the organizations. I was born. For example, when there is a change in personnel information related to a change in basic salary or allowance for a certain employee, the personnel information corresponding to the employee is transferred from the personnel system to a USB memory or the like. Read it to a storage medium and hand it to the accounting department. In the accounting department, work such as manually updating the information of the payroll system based on the received personnel data of the recording medium is performed.

In this regard, there has been known a technique that enables employee salary calculation to be performed in accordance with the time of change when information changes on the personnel side occur in the company. (For example, Patent Document 1)
A technique for recognizing an error in salary information accompanying an error in data input is also known. (For example, Patent Document 2)

JP 2000-207448 A JP 2005-84852 A

  However, the work to update the salary information registered in the payroll system increases the amount of work and the work becomes complicated, for example, when the number of employees increases or the number of allowance items increases. There was a situation where errors such as input mistakes were likely to occur. In addition, the task of detecting whether there is an error in the salary information registered in the salary calculation system also increases the amount of work and the work becomes complicated as the number of employees increases or the number of allowance items increases, for example. Therefore, there was a situation where detection was difficult.

  Therefore, there has been a demand for a method that can easily detect an erroneous payment of salary with high accuracy.

The erroneous salary supply detection program according to one aspect of the present invention is applied to a detection target month for a detection target person who detects the presence or absence of erroneous salary supply from a personnel event database storing personnel event information representing personnel events. Salary corresponding to the acquired personnel event information by using the increase / decrease table that acquires the personnel event information and stores the increase / decrease direction of the salary item payment amount for the personnel event information stored in the storage unit Acquire personnel event increase / decrease information indicating the direction of increase / decrease in the payment amount for the item, acquire salary detail information of the detection target person's detection target month and salary detail information of the previous month of the detection target month from the salary information database, Amount of payment from the previous month to the detection target month for the salary item corresponding to the acquired personnel event information by comparing the acquired salary detail information of the detection target month with the salary detail information of the previous month Get the pay stubs decrease information indicating the direction of increase or decrease, notify me of comparing the direction of increase or decrease of personnel events increase or decrease information, the direction of increase or decrease of the pay slip up, down information, the direction of increase or decrease is not matched Outputs information and causes the computer to execute processing.

The salary error supply detection system according to one aspect of the present invention is applied to a detection target month for a detection target person who detects the presence or absence of incorrect salary payment from a personnel event database storing personnel event information representing personnel events. HR events acquired using the HR event acquisition unit that acquires HR event information and the increase / decrease table that correlates the direction of increase / decrease of the salary item payment amount with the HR event information stored in the storage unit Increase / decrease information acquisition unit for acquiring personnel event increase / decrease information indicating the direction of increase / decrease in the payment amount of the salary item corresponding to the information, salary detail information of the detection target month of the detection target person, and salary detail information of the previous month of the detection target month To the salary item corresponding to the acquired personnel event information by comparing the salary detail information acquisition section that retrieves the salary information from the salary information database with the salary detail information of the acquired detection target month and the salary detail information of the previous month. A payroll calculation unit that acquires pay slips decrease information from the previous month had been representative of the direction of increase or decrease of payment amounts over the detected month, the direction of increase or decrease of personnel events decrease information, the direction of increase or decrease of the pay slip up, down information And a notification unit that outputs notification information when the increase / decrease directions do not match.

The salary error supply detection method according to one aspect of the present invention is applied to a detection target month for a detection target person who detects the presence or absence of incorrect salary payment from a personnel event database storing personnel event information representing a personnel event. Salary corresponding to the acquired personnel event information by using the increase / decrease table that acquires the personnel event information and stores the increase / decrease direction of the salary item payment amount for the personnel event information stored in the storage unit Acquires the increase / decrease information of personnel events that indicate the direction of increase / decrease in the payment amount of the item, and acquires the salary details information of the detection target person's detection target month and the salary detail information of the previous month of the detection target month from the salary information database By comparing the payroll details for the detected month and the payroll information for the previous month, the direction of increase or decrease in the amount of payment from the previous month to the detected month for the payroll item corresponding to the acquired personnel event information Acquires to pay slip increase or decrease information, compares the direction of increase or decrease of personnel events increase or decrease information, the direction of increase or decrease of the pay slip up, down information, outputs the notification information when the direction of increase or decrease is not matched , Including that.

  According to the above aspect, it is possible to detect an erroneous supply of salary with high accuracy.

It is a figure which shows the function structure relevant to the salary incorrect payment detection system based on one Embodiment. FIG. 6 illustrates a personnel event database, according to one embodiment. It is a figure which illustrates the increase / decrease table | surface which matches personnel event information and increase / decrease in the supply amount of a salary item based on one Embodiment. It is a figure which illustrates the supply salary item information stored in the salary information database based on one Embodiment. It is a figure which illustrates the salary details information stored in the salary information database according to one embodiment. It is a figure which illustrates the operation | movement flow of the salary mistake supply detection process performed by the salary mistake supply detection system based on 1st Embodiment. It is a figure which illustrates the operation | movement flow of the salary mistake supply detection process performed by the salary mistake supply detection system based on 2nd Embodiment. It is a figure which illustrates the computer by which the salary incorrect payment detection program based on one Embodiment is mounted. It is a figure which illustrates the server computer by which the salary incorrect payment detection program based on one Embodiment is mounted, and the computer which receives a service.

Hereinafter, some embodiments will be described in detail with reference to the drawings. In addition, the same code | symbol was attached | subjected to the corresponding element in several drawing.
FIG. 1 is a diagram showing a functional configuration related to an erroneous salary detection system 3 according to an embodiment. FIG. 1 shows a personnel system 1, a salary system 2, and an erroneous salary detection system 3 according to an embodiment.

  The personnel system 1 includes a personnel information database 4. The personnel system 1 may include other elements (not shown) such as an input / output unit. The personnel information database 4 is a database that stores employee personnel information. The personnel information is information relating to personnel applied to employees. Personnel information includes, for example, ID, staff number, name, address, address update date, presence / absence of spouse, number of dependents, dependent family renewal date, holding unit number, holding unit renewal date, working department, transfer date, job title, Includes various information related to gender, age, salary class, leave period, information on acquisition of reduced working hours for childcare, retirement date, disposal, and other personnel. There are items in personnel information that are directly related to changes in the amount of salary paid, and other items that are not directly related. The personnel information database 4 stores these personnel information in association with employees.

  The salary system 2 includes a salary information database 5. The salary system 2 may include other elements such as an input / output unit. The salary information database 5 stores, for example, detailed information on salary paid to each employee every month (hereinafter, detailed salary information 31). For example, as shown in FIG. 5, the salary detail information 31 includes the total amount of salary paid to a certain employee in a certain month and the amount for each salary item 25. The salary item 25 is various items to which money that can be included in salary is paid, and includes salary and various allowances. Various allowances include, for example, adjustments, teaching adjustments, dependent allowances, child allowances, adjustment allowances, regional allowances, housing allowances, starting salary adjustment allowances, commuting allowances, single employee allowances, managerial allowances, special land allowances, monthly special work Includes allowance, daily allowance, teacher special allowance, overtime allowance, transfer allowance, holiday allowance, night allowance, managerial special pay allowance, overnight stay allowance, end of term allowance, diligence allowance, etc. Further, in one embodiment, the salary information database 5 also stores salary item information 30 indicating which allowance is paid to each employee, as shown in FIG. 4, for example. Yes.

  The salary error supply detection system 3 includes a personnel information change unit 6, a personnel event database 7, a personnel event acquisition unit 8, an increase / decrease table 9, an increase / decrease information acquisition unit 10, a salary item determination unit 12, a salary detail acquisition unit 11, and a salary calculation. Section 13, comparison determination section 14, and notification section 15. The erroneous salary supply detection system 3 may include elements (not shown) such as an input / output unit.

  The personnel information changing unit 6 receives the input from the user, for example, and updates the personnel information database 4 by changing the personnel information stored in the personnel information database 4 using the received information. In one embodiment, the personnel information changing unit 6 requests the user to input personnel event information 18 representing the personnel event that caused the change made to the personnel information. The personnel information change unit 6 writes, for example, a personnel event record 23 as shown in FIG. 2 in the personnel event database 7 based on the input personnel event information 18. In another embodiment, the personnel information change unit 6 may be configured to write the personnel event record 23 in the personnel event database 7 based on the updated data in the personnel information database 4.

  An example of the personnel event database 7 and each personnel event record 23 stored therein is shown in FIG. The personnel event information 18 is information representing a personnel event. The personnel event is an event that causes the necessity to change personnel information. Personnel events include, for example, an increase in employee dependents due to childbirth, a change in the employee's job title or grade, and the employee's absence, disposition, short working hours, and retirement .

  One embodiment of the increase / decrease table 9 of FIG. 1 is shown in FIG. The increase / decrease table 9 includes personnel event information 18, salary items 25 that are salary items that need to be changed due to the personnel events indicated in the personnel event information 18, and salary items 25. It is a table | surface which matches the direction of increase / decrease in the amount of payment. In some embodiments, for example, the increase / decrease table 9 may include other information such as an allowable amount range for increase / decrease in the amount of payment. The personnel event information 18 includes, for example, a personnel event item 21 indicating the type of personnel event such as a change in the number of dependents, leave, disposal, short working hours, retirement, promotion, salary table change, and the personnel event item 21. Status information 22 which is information indicating the state of a personnel event to be performed.

  The personnel event acquisition unit 8 acquires personnel event information 18 from the personnel event database 7. The increase / decrease information acquisition unit 10 has a salary item 25 in which the amount of payment needs to be changed due to the personnel event shown in the acquired personnel event information 18 and a personnel representing the direction of increase / decrease in the amount of payment of the salary item 25 The event increase / decrease information is acquired by referring to the increase / decrease table 9.

  The salary item determination unit 12 determines whether the salary item 25 that needs to be changed due to personnel events acquired by the increase / decrease information acquisition unit 10 is subject to detection of erroneous salary payments. It is determined whether or not it is a supply target in the detection target month.

  The salary detail acquisition unit 11 acquires salary detail information 31 for the employee in a certain month and salary detail information 31 for the previous month of the certain month from the salary information database 5. Among the salary items 25 that need to change the amount of payment acquired by the increase / decrease information acquisition unit 10, the salary calculation unit 13 receives payment in the detection target month by the salary item determination unit 12 The salary item information is compared for the salary item 25 determined as. The salary calculation unit 13 acquires salary details increase / decrease information indicating the direction of increase / decrease in the difference indicating whether the amount of salary item 25 for a certain month has been increased or decreased as compared with the previous month.

  The comparison determination unit 14 determines the increase / decrease direction indicated in the personnel event increase / decrease information and the increase / decrease direction indicated in the salary detail increase / decrease information for the salary item 25 whose payment amount acquired by the increase / decrease information acquisition unit 10 is to be changed. It is determined whether or not they match.

  The notification unit 15 outputs notification information when the comparison determination unit 14 determines that the increase / decrease directions do not match. The notification information output from the notification unit 15 is used for notification, for example, displaying a warning on the display screen of the input / output unit 107 of the salary error supply detection system 3 or generating a warning sound. It is done.

  In FIG. 1, some elements of the erroneous salary detection system 3 are included in the personnel system 1 and other elements are included in the salary system 2, but the configuration of the erroneous salary detection system 3 is limited to this. Is not to be done. For example, all elements of the erroneous salary detection system 3 may be included in either the personnel system 1 or the salary system 2, or the erroneous salary detection system 3 is independent of the personnel system 1 and the salary system 2. May be provided.

  FIG. 2 is a diagram illustrating a personnel event database 7 that stores personnel event records 23 according to an embodiment. Registration of the personnel event record 23 in the personnel event database 7 is performed by the personnel information change unit 6. The personnel event database 7 includes a personnel event record 23. Each personnel event record 23 includes staff number 16, name 17, personnel event information 18, application date 19, and remarks 20.

  The staff number 16 is a number assigned to identify the employee. Therefore, for example, the personnel information change unit 6, the personnel event acquisition unit 8 and the salary detail acquisition unit 11 are information on which employee each record registered in the personnel information database 4, salary information database 5 and personnel event database 7 is. The staff number 16 can be used to identify whether

  Name 17 is the name of the employee. The personnel event information 18 is information representing a personnel event that is an event that causes the personnel information in the personnel information database 4 to be changed. The personnel event information 18 includes a personnel event item 21 and status information 22 of the personnel event item 21. Further details regarding the personnel event information 18 will be described later.

  In the present embodiment, the application date 19 is a date on which a change in personnel information required by a personnel event shown in the personnel event information 18 is actually applied. For example, in the personnel event database 7 of FIG. 2, personnel information indicating that “Kazuko Tanaka” of the staff number “0011” “takes leave” is registered in one personnel event record 23. Accordingly, the date when “Kazuko Tanaka” actually applies the leave and starts to take a leave of absence is registered as “February 1, 2011” on the application date 19, and thus is from February 1, 2011.

  However, there is a situation where the date when the change of personnel information is applied and the date when the change is reflected in the amount of payment of the salary item 25 are different. Therefore, in another embodiment, the application date 19 is changed when the amount of payment of the salary item 25 is changed due to the change of the personnel information required by the personnel event shown in the personnel event information 18. The date when the change is applied to the payment amount of the salary item 25. An example of this case will be described below.

  For example, in the personnel event database 7 of FIG. 2, it is registered that “Makoto Tagami” of the staff number “0060” is “promoted” from the section manager to the section manager. Here, it is assumed that the date on which the change of personnel information is applied (here, the date on which the change of position from the section manager to the general manager is applied) is February 1, 2011 as shown in Remarks 20. In this case, for example, since the payment amount of the salary item 25 such as management allowance increases simultaneously with the promotion, the application date 19 is registered as February 1, 2011, which is the same date as the promotion is applied. On the other hand, for example, assume that an employee has been born two years ago but has forgotten to report to the company to which he belongs and reports that this month the child was born. In this case, since the date on which the change of personnel information should be applied is two years ago, the date when the dependents increased in the personnel information is two years ago. However, since the dependent allowance that has not been paid so far cannot be paid retroactively two years ago, the payment of the dependent allowance accumulated from the previous two years may be settled with the salary of this month, for example. To do. In such a case, the date (for example, the first day of the current month) included in the calculation of the current salary for which the liquidation is performed is registered as the application date 19. In the following description, that a certain date is included in the salary calculation for a certain month is expressed as a certain date belonging to a certain month.

  As described above, when the change in the personnel information is different from the date on which the change is applied to the payment amount of the salary item 25 due to the change, the payment amount of the salary item 25 is changed. The applied date may be registered as the applied date 19. In yet another embodiment, the application date 19 does not include date information, and may be only information on the month in which the change is applied to the payment amount of the salary item 25.

  A remark 20 shown in FIG. 2 is a column in which a user can freely enter a memo or the like. In FIG. 2, the remark 20 describes what kind of personnel event has occurred. The personnel event database 7 does not necessarily include the name 17 or the staff number 16 and the remarks 20.

  Next, each personnel event record 23 will be briefly described. For example, looking at the personnel event record 23 in the second row, it is shown that “Takeshi Gonda” with the staff number “0024” is going to work for a short time from “January 13, 2011”. ing. Looking at Personnel Event Record 23 in the third row, “Taro Kinoshita” with staff number “0013” has been disposed of from December to January, and may be discontinued from “February 1, 2011”. It is shown. In this way, the personnel event database 7 stores information related to personnel events. In FIG. 2, several personnel event records 23 are shown as an example. However, even if more personnel event records 23 are included in the personnel event database 7, or fewer personnel event records 23 are included. It does not have to be included.

  FIG. 3 is a diagram illustrating an increase / decrease table 9 that correlates personnel event information 18 and increase / decrease in the amount of payment of the salary item 25 according to an embodiment. In the increase / decrease table 9, personnel event items 21, salary items 25, additions 26 and deletions 27, allowable ranges 28, and remarks 29 are associated with each other.

  The personnel event item 21 in the increase / decrease table 9 corresponds to the personnel event item 21 of the personnel event information 18 shown in FIG. The salary item 25 shown in the increase / decrease table 9 needs to change the amount of payment due to the change in personnel information required by the personnel event shown in the personnel event item 21 associated in the increase / decrease table 9 Salary item 25. Therefore, when a personnel event occurs, a salary item that requires a change in the amount to be paid by the personnel event by referring to the increase / decrease table 9 using the personnel event item 21 of the personnel event information 18 representing the personnel event. 25 can be specified.

  Correspondence between the personnel event information 18 and the salary item 25 in the increase / decrease table 9 is determined by the rules of salary supply in each company. For example, in the case of a company that stipulates a convention for paying a dependent allowance per dependent, the amount of dependent allowance increases and decreases with the increase or decrease in the number of dependents. In this case, salary item 25: “dependence allowance” is associated with personnel event item 21: “change in the number of dependents” in increase / decrease table 9. In addition, if the number of dependents of employees who are hired as a single employee increases, if the company has a policy that increases the allowance for a single employee per dependent, the allowance for single employees as the number of dependents increases or decreases. The amount of money will increase or decrease. In this case, the salary item 25: “single appointment allowance” is associated with the personnel event item 21: “change in the number of dependents” in the increase / decrease table 9.

  The addition 26 and deletion 27 of the increase / decrease table 9 correspond to the status information 22 of the personnel event information 18 of FIG. The addition 26 and the deletion 27 indicate whether the salary item 25 is increased or decreased depending on whether the status information 22 included in the personnel event information 18 of FIG. 2 is an addition or deletion. Therefore, by using the increase / decrease table 9, the salary item 25 whose amount of payment changes depending on the personnel event shown in the personnel event information 18 of the personnel event record 23 of the personnel event database 7, and the increase / decrease of the amount of salary of the salary item 25 And get directions.

  Note that the addition and deletion of the status information 22 shown in FIG. 2 and the addition 26 and deletion 27 of FIG. 3 do not necessarily represent adding or deleting something. These “addition” and “deletion” simply indicate that a personnel event has two states corresponding to “addition” and “deletion”. For example, “Change in the number of dependents” shown as the personnel event item 21 in FIG. 2 and FIG. 3 is “addition” means that the number of dependents has increased due to reasons such as childbirth, marriage, and retirement of a spouse. Conversely, “deleted” indicates a state in which the number of dependents has decreased. The remark 29 in FIG. 3 shows the state of “addition” and “deletion” of each personnel event item 21 shown in FIG. 2 and FIG. These “addition” and “deletion” in FIG. 2 and FIG. 3 indicate the personnel event shown in the personnel event information 18 of the personnel event record 23 in FIG. 2 and the payment of the salary item 25 in the increase / decrease table 9 in FIG. It is also information used to link the increase and decrease of the amount.

  The allowable range 28 is information representing an allowable amount range of increase / decrease in the payment amount of the salary item 25 associated in the increase / decrease table 9. The information set as the permissible range 28 can be determined that if the increase or decrease in the payment amount of the corresponding salary item 25 exceeds the range, the payment amount of the salary item 25 has some error (false payment). Is set to a range. The range set in the allowable range 28 is determined according to the amount of payment for the salary item 25 determined by each company. For example, assume a company that stipulates a contract for paying a dependent allowance of ¥ 4,000 per dependent. In this case, it is considered that the number of dependents of one employee will increase or decrease by 6 or more at the same time, so it is considered that it does not usually happen so much, so the maximum increase / decrease number of dependents is 5 people (5 people x 4) 20,000 yen is set as the allowable range 28 at 000 (yen). In addition, for example, if a company is set to provide 1,000 yen per dependent for a single employee, the increase or decrease in the amount of single employee allowance for one employee will be 5,000 yen. Exceeding is usually not likely to occur. Therefore, 5,000 yen is set as an allowable range of the increase / decrease amount of the single employee allowance for the personnel event item 21 of “change in the number of dependents”.

  By using the allowable range 28 set in this way, for example, the comparison / determination unit 14 determines that the amount of increase or decrease in the salary item 25 shown in the increase / decrease table 9 exceeds the corresponding allowable range 28. Therefore, it can be determined that there is some error in the salary detail information 31.

  A remark 29 in FIG. 3 is a column in which a user can freely enter a memo or the like. In FIG. 3, the remark 29 describes what state of “HR” represents “addition” and “deletion” for each personnel event item 21.

  Here, the personnel event item 21 that is particularly suitable for being put on the increase / decrease table 9 will be described. The personnel event item 21 is information representing the type of personnel event included in the personnel event information 18 as described above. As described above, the personnel event is an event that causes the need to change personnel information as described above. Therefore, the personnel event includes those other than the personnel event shown in the personnel event item 21 in FIG. Other types of events such as transfers are also included. For example, taking this transfer as an example, the transfer may increase or decrease a salary item 25 such as a single allowance paid to a person who has been assigned alone or a remote allowance paid to a person working in a remote area. However, it is often related to other factors such as the family composition of the employee and the consent of the family as to whether or not to be transferred to the transferee as a single person. It is difficult to directly relate to the increase or decrease in benefits. Similarly, since whether or not the transfer destination is a remote location varies depending on the composition of the company's work location, it is generally difficult to directly link the personnel event of transfer to the result of an increase or decrease in remote allowance. However, if, for example, a company is transferred only to remote areas, and the remote area allowance is paid whenever the company is transferred, and the remote area allowance increases, the personnel event of relocation is directly related to the increase or decrease in remote area allowance. Can be tied. In this case, the personnel event item 21 of transfer is particularly suitable for putting the salary item 25 of remote area allowance in association with the increase / decrease table 9.

  As described above, when the personnel event indicated in the personnel event item 21 can be directly linked to the result of the increase or decrease of the at least one salary item 25, the personnel event item 21 is associated with the associated salary. It is suitable to be put on the increase / decrease table 9 in association with the item 25.

  Note that the personnel event item 21 can be listed in the increase / decrease table 9 even when the personnel event indicated by the personnel event item 21 cannot be directly linked to the result of the increase or decrease of at least one salary item 25. For example, when it is possible to finally link the personnel event item 21 to the result of the increase or decrease of at least one salary item 25 by referring to other information, the personnel event item 21 and the salary item 25 are increased or decreased. May be stored. An example of referring to the supply salary item information 30 will be described later as an example of finally linking the personnel event item 21 with an increase or decrease of at least one salary item 25 by referring to this other information.

  FIG. 4 is a diagram illustrating paid salary item information 30 stored in the salary information database 5 according to an embodiment. In this embodiment, the salary information database 5 stores salary item information 30 representing salary items 25 that are paid for each employee. Each salary item information 30 includes staff number 16, name 17, and various salary items 25. Each salary item 25 also includes information on whether or not the salary item 25 is being paid. ing. In FIG. 4, “Yes” indicates that the salary item 25 is received, and “No” indicates that the salary item 25 is not received. For example, the information of the paid salary item information 30 is updated by an employee belonging to a department (such as the accounting department or the general affairs department) that calculates salary.

  The salary item information 30 illustrated in FIG. 4 is the salary item 25 representing the salary item 25 that was paid in February 2011 to “Taro Okada” registered in the personnel event database 7 of FIG. This is item information 30. Looking at the salary item information 30 for February 2011 of “Taro Okada” as an example, “Taro Okada” is provided with a dependent allowance and a single allowance allowance as of February 2011. I understand that

  FIG. 5 is a diagram illustrating salary detail information 31 stored in the salary information database 5 according to an embodiment. The salary detail information 31 illustrated in FIG. 5 is the salary detail information 31 for January and February 2011 of the staff number “0501” and the name “Taro Okada” registered in the personnel event database 7 of FIG. is there. In this embodiment, the salary information database 5 stores salary detail information 31 representing the details of salary paid monthly for each employee. Each salary detail information 31 includes a staff number 16, a name 17, a total salary payment, and various salary items 25. The salary item 25 includes the amount of payment of the salary item 25 when the salary item 25 is paid. Comparing the salary details 31 in January and February 2011 of “Taro Okada” as an example, the dependent allowance was not paid in January (ie 0 yen), but in February It is 4,000 yen, and you can see that it has increased by 4,000 yen. In addition, the single allowance was 3,000 yen in January, but it was 4,000 yen in February, increasing by 1,000 yen. In this way, whether the payment amount of the salary item 25 is increased by comparing the payment amount for each salary item 25 of the salary detail information 31 of a certain month and the salary detail information 31 of the previous month of the certain month, Alternatively, it is possible to obtain information on the increase / decrease in the difference indicating whether the amount has been reduced.

  FIG. 6 is a diagram illustrating an operational flow of an erroneous salary detection process executed by the erroneous salary detection system 3 according to the first embodiment. With reference to FIG. 6, detection of erroneous salary payment according to the first embodiment will be described below. Note that a target month for detecting whether or not there is an incorrect salary payment by the erroneous salary supply detection process is referred to as a detection target month. Further, an employee who is to detect the presence or absence of incorrect salary payment by the erroneous salary detection processing is referred to as a detection target person, and a personnel event record 23 to be detected is referred to as a detection target personnel event record 23.

  The operation flow shown in FIG. 6 starts when, for example, the user executes a salary error supply detection process from the input / output unit or the like. When the operation is started, the personnel event acquisition unit 8 refers to the personnel event database 7 in step S1. The personnel event acquisition unit 8 acquires one personnel event record 23 in which the month to which the application date 19 belongs coincides with the month to be detected from among the personnel event records 23 as the personnel event record 23 to be detected for incorrect salary payment. For example, assuming that the detection target month is February 2011, the personnel event acquisition unit 8 acquires a personnel event record 23 whose application date 19 is February from the personnel event database 7 shown in FIG. In FIG. 2, the personnel event record 23 between the personnel event record 23 of the staff number “0013” “Taro Kinoshita” and the personnel number “0024” of “Kazuaki Akiyama” is registered as the personnel event record 23 of February. Has been. The personnel event acquisition unit 8 acquires one of these personnel event records 23, for example, the personnel event record 23 of “Taro Okada” as the personnel event record 23 to be detected, To do.

  In step S <b> 2, the increase / decrease information acquisition unit 10 refers to the increase / decrease table 9 using the personnel event item 21 included in the personnel event information 18 of the acquired personnel event record 23 to be detected and the status information 22. As a result, the increase / decrease information acquisition unit 10 includes the salary item 25 whose amount of payment is changed by the personnel event shown in the personnel event information 18 from the increase / decrease table 9, and the personnel event increase / decrease information indicating the direction of increase / decrease of the amount of payment. To get. For example, an example of referring to the increase / decrease table 9 using the personnel event record 23 of “Taro Okada” with the staff number “0501” in FIG. 2 will be described. The increase / decrease information acquisition unit 10 sets “dependent family number change” as the personnel event item 21 of the personnel event information 18 and “add” as the status information 22 from the personnel event record 23 of “Taro Okada” with the staff number “0501”. get. The increase / decrease information acquisition unit 10 refers to the increase / decrease table 9 using the acquired personnel event item 21 “change in the number of dependents” and status information 22 “add”. The increase / decrease table 9 shows “dependent family allowance” and “single employee allowance” as salary items 25 related to personnel event item 21 “change in the number of dependents”. In the “addition” column, both “dependent allowance” and “single allowance” are indicated as “↑ increase”. Therefore, “Taro Okada” with the staff number “0501” has the salary item 25: “Dependent Allowance” and “Single Person Allowance” due to “Addition” of Personnel Event Information 18: “Change in Number of Dependents” in February. It can be seen that both increase "↑". The increase / decrease information acquisition unit 10 refers to the increase / decrease table 9 by using the “change in the number of dependents” in the personnel event item 21 and the “addition” in the status information 22, thereby increasing the “↑ increase in the“ dependent family allowance ”. And “↑ Increase” information can be acquired.

  In step S <b> 3, the salary item determination unit 12 obtains salary item information 30 for the employee whose staff number 16 is indicated in the personnel event record 23 to be detected from the salary information database 5. The salary item determination unit 12 refers to the acquired salary item information 30, and the employee indicated by the personnel event record 23 to be detected in the detection month is the salary item acquired by the increase / decrease information acquisition unit 10 in step S 2. It is determined whether or not it is a target of 25 supply. For example, in the case of the personnel event record 23 of the staff number “0501” and the name “Taro Okada” in FIG. 2, the increase / decrease information acquisition unit 10 reads “upward increase” and “single allowance” for “dependent family allowance” from the increase / decrease table 9. "↑ Increase" information is acquired. The salary item determination unit 12 obtains the salary item information 30 of the staff number “0501” and the name “Taro Okada” from the salary information database 5, and this salary item 25: “Dependent Allowance” and “ For “single employee allowance”, it is determined whether employee: “Taro Okada” is eligible for payment. FIG. 4 exemplifies the salary item information 30 for the employee number “0501” and the name “Taro Okada”. As shown in FIG. 4, the staff number “0501” and the name “Taro Okada” have “Dependent Allowance” and “Single Person Allowance” as “Yes”, so the employee “Taro Okada” The salary item 25 is subject to payment.

  In step S4, the salary statement acquisition unit 11 uses the employee number 16 of the employee shown in the personnel event record 23 to be detected acquired by the personnel event acquisition unit 8, and detects the employee's detection target month and the detection target. The salary detail information 31 of the previous month of the month is acquired from the salary information database 5. In step S <b> 5, the salary calculation unit 13 obtains the acquired detection target month and the salary detail information 31 of the previous month of the detection target month for the salary item 25 determined to be the supply target by the supply salary item determination unit 12. Make a comparison. The salary calculation unit 13 increased or decreased the salary item 25 for the salary item 25 determined by the salary item determination unit 12 to be paid from the previous month to the month to be detected by this comparison. Get the information. For example, in the case of the personnel event record 23 of the staff number “0501” and the name “Taro Okada” in FIG. 2, the increase / decrease information acquisition unit 10 reads “upward increase” and “single allowance” for “dependent family allowance” from the increase / decrease table 9. "↑ Increase" information is acquired. Then, the salary item determination unit 12 is subject to the payment of the salary item 25 “dependent family allowance” and “single employee allowance” by the employee “Taro Okada” from the salary item information 30 of FIG. It is determined. Accordingly, the salary calculation unit 13 compares the salary detail information 31 of the detection target month with the salary detail information 31 of the previous month for the salary item 25 “dependent family allowance” and “single allowance allowance”. FIG. 5 illustrates the detection target month (here, February) of the staff number “0501” and the name “Taro Okada” and the salary detail information 31 of the previous month (here, January). Comparing these two salary details information 31, the salary item 25 “Dependent Allowance” is increased by 4,000 yen from January to February. In addition, “single appointment allowance” increased by 1,000 yen from January to February. Accordingly, the salary calculation unit 13 acquires, as a result of the comparison, salary item increase / decrease information indicating the direction of increase as the direction of increase / decrease in the difference between the salary items 25 “support allowance” and “single allowance”. .

  In step S <b> 6, the comparison determination unit 14 indicates the increase / decrease direction indicated in the personnel event increase / decrease information and the salary detail increase / decrease information regarding the pay item 25 determined to be the supply target by the supply salary item determination unit 12. It is determined whether or not the direction of increase / decrease matches. If the comparison / determination unit 14 determines that they match, the process proceeds to Yes, and the operation flow ends. On the other hand, if the comparison determination unit 14 determines that they do not match, the process proceeds to No, and the flow proceeds to step S7. For example, when the personnel event record 23 of the staff number “0501” and the name “Taro Okada” in FIG. 2 is to be detected, the increase / decrease information acquisition unit 10 reads salary items 25 “dependent family allowance” and “single appointment” from the increase / decrease table 9. Acquired when both allowances are increased. Further, the salary item determination unit 12 determines that the employee number “0501” to be detected and the name “Taro Okada” from the salary item information 30 in FIG. "Is determined to be eligible for payment. The salary calculation unit 13 compares the detection target month with the salary detail information 31 of the previous month, as the direction of increase / decrease in the difference between the salary items 25 “support allowance” and “single allowance”. Acquire salary details increase / decrease information indicating the direction of increase. Therefore, regarding the personnel event record 23 of “Taro Okada” to be detected, the direction of increase / decrease in the amount of payment for “support allowance” and “single employee allowance” indicated in the personnel event increase / decrease information, and “ The direction of increase / decrease in “support allowance” and “single employee allowance” is the same. In this case, the comparison determination unit 14 determines Yes because the increase / decrease direction indicated in the personnel event increase / decrease information matches the increase / decrease direction indicated in the salary detail increase / decrease information, and the operation flow ends. However, for example, when the user inputs a change in the amount of “support allowance” and “single employee allowance” in the salary details information 31 of the salary information database 5, the amount is incorrectly entered as an increase (increase) and a decrease (decrease). Suppose you have. In such a case, the comparison determination unit 14 determines No because the increase / decrease direction indicated in the personnel event increase / decrease information does not match the increase / decrease direction indicated in the salary detail increase / decrease information, and the flow proceeds to step S7. Proceed to

  In step S7, the notification unit 15 outputs notification information. The notification information output from the notification unit 15 is, for example, for performing a notification such as displaying a warning on the display screen of the input / output unit 107 provided in the salary error supply detection system 3 or generating a warning sound. Used. When the notification unit 15 outputs the notification information, this flow ends. The notification output from the notification unit 15 is, for example, information that can identify the salary item 25 in which the increase / decrease directions indicated in the personnel event increase / decrease information and the salary detail increase / decrease information do not match with the employee to be detected ( For example, the staff number 16 and the name 17 may be included.

  The above-described processing of step S1 to step S7 is executed for all records whose application date 19 belongs to the detection target month in the personnel event database 7 shown in FIG. This completes the erroneous salary detection process.

  Note that the above step S3 is not necessarily executed. For example, the salary item 25 associated with the increase / decrease table 9 is only the salary item 25 provided to all employees, such as salary. If there is, the process of step S3 may not be executed.

  In the example illustrated in FIG. 6, when the increase / decrease direction indicated in the personnel event increase / decrease information matches the increase / decrease direction indicated in the salary details increase / decrease information, the notification unit 15 does not output the notification information. Stated. However, the embodiment is not limited to this. For example, when the increase / decrease direction indicated in the personnel event increase / decrease information matches the increase / decrease direction indicated in the salary detail increase / decrease information, the notification unit 15 outputs notification information indicating that no incorrect salary payment has been detected. May be.

  As described above, personnel event increase / decrease information representing the direction of increase / decrease of salary item 25 obtained from personnel event record 23 using increase / decrease table 9, and salary indicating the direction of increase / decrease of salary item 25 obtained by salary calculation unit 13. When the detailed increase / decrease information does not match, the notification unit 15 outputs the notification information. Accordingly, when any personnel event occurs, the salary error supply detection system 3 can detect whether or not the payment amount of the salary item 25 required by the personnel event has been changed. Further, when the payment amount of the salary item 25 required due to the personnel event is not changed, a notification is output from the notification unit 15, so that the user has an error in the amount of the salary detail information 31. I can know that.

  In the above embodiment, the personnel event increase / decrease information indicating the direction of increase / decrease of the salary item 25 acquired from the personnel event record 23 using the increase / decrease table 9 and the increase / decrease of the salary item 25 acquired by the salary calculation unit 13 are also described. It compares the pay detail change information indicating the direction. For example, when the salary item 25 that needs to be changed due to the personnel event shown in the personnel event record 23 is specified, and the salary item 25 is not changed in the salary item information 31 in the month to be detected and the previous month's salary details information 31 Suppose that it is determined that the salary is incorrect. In this case, for example, when the salary details information 31 is updated, the amount to be paid should be increased due to a user input error or the like. Not. Similarly, if the place where the amount of money to be paid should be reduced is mistakenly increased, the amount has changed, so that it is not determined that the payment is incorrect.

  However, in the above embodiment, the personnel event increase / decrease information indicating the direction of increase / decrease in the amount of payment acquired using the increase / decrease table 9 and the salary detail increase / decrease information indicating the direction of increase / decrease in the amount of salary in the salary detail information 31 match. It is also confirmed whether or not (that is, the direction of increase / decrease is also confirmed). For this reason, for example, when the pay amount information 31 should be increased due to a user input mistake or the like when updating the pay statement information 31, the direction does not match if the pay amount is reduced by mistake. The detail increase / decrease information does not match, and an erroneous supply of salary can be detected. Similarly, since the direction does not match even when the amount of money to be paid is increased by mistake, the personnel event increase / decrease information and the salary details increase / decrease information do not match, and it is possible to detect an erroneous supply of salary.

  Next, a second embodiment will be described with reference to FIG. FIG. 7 is a diagram illustrating an operational flow of an erroneous salary detection process executed by the erroneous salary detection system according to an embodiment, as in FIG. 6. In the second embodiment, processes similar to those in the first embodiment are executed from step ST1 to step ST4.

  In the second embodiment, in step ST5, the salary calculation unit 13 increases or decreases the payment amount of the salary item 25 to be changed by the personnel event record 23 to be detected, as in the first embodiment. Acquire salary details increase / decrease information indicating the direction. Furthermore, in the second embodiment, the salary item 25 to be changed by the personnel event record 23 to be detected also acquires the amount of money increased or decreased in the detection target month compared to the previous month of the detection target month. For example, for the personnel event record 23 of the staff number “0501” and the name “Taro Okada” in FIG. 2, the salary calculation unit 13 says that the salary item 25 “support allowance” is increased from January to February. Acquire information and the increased amount of 4,000 yen. The salary calculation unit 13 acquires information that the “single appointment allowance” is increased from January to February and the increased amount of 1,000 yen.

  Subsequently, in step ST6, as in the first embodiment, the comparison / determination unit 14 determines whether the increase / decrease direction indicated in the personnel event increase / decrease information matches the increase / decrease direction indicated in the salary details increase / decrease information. Determine. If the direction of increase / decrease indicated in the personnel event increase / decrease information and the salary detail increase / decrease information does not match, it is determined No, and the process proceeds to ST7. In step ST7, the notification unit 15 outputs notification information. The notification information output from the notification unit 15 is, for example, for performing a notification such as displaying a warning on the display screen of the input / output unit 107 provided in the salary error supply detection system 3 or generating a warning sound. Used. When the notification unit 15 outputs the notification information, this flow ends. The notification information output from the notification unit 15 may include, for example, information (for example, staff number 16, name 17, etc.) that can identify the salary item 25 whose direction does not match and the employee to be detected. Good.

  In step ST6, when the increase / decrease directions match, it is determined Yes and the process proceeds to step ST8. In step ST <b> 8, it is determined whether or not the increased / decreased amount of the salary item 25 having the same increase / decrease direction is within the range indicated by the allowable range 28. In the present embodiment, in step ST5, the salary calculation unit 13 adds the increase / decrease amount together with the salary detail increase / decrease information indicating the direction of increase / decrease of the amount from the salary detail information 31 of the detection target month and the previous month of the detection target month. Have also acquired. Therefore, it is possible to determine whether the amount is within the range indicated by the allowable range 28 shown in the increase / decrease table 9 by using the increased / decreased amount of the salary item 25 acquired by the salary calculation unit 13.

  As in the first embodiment, the personnel event record 23 of the name “Taro Okada” of the staff number “0501” in FIG. 2 is taken as an example. In this case, in step ST5, the salary calculation unit 13 increases the amount of money in addition to the information that the amount of payment is increased from January to February for the salary items 25 "sustainable allowance" and "single allowance allowance". Also get about. In other words, as described above, the salary calculation unit 13 has acquired an amount of 4,000 yen that has increased from January to February with respect to the “dependent family allowance”. In addition, with regard to “single employee allowance”, the amount of money increased from January to February was 1,000 yen. In step ST6, the comparison / determination unit 14 determines whether the increase / decrease direction indicated in the personnel event increase / decrease information and the increase / decrease direction indicated in the salary detail increase / decrease information for the salary items 25 “dependent family allowance” and “single employee allowance”. It is determined that they match.

  In this case, the comparison and determination unit 14 determines that the amount 4,000 yen increased from January to February in the salary details information 31 is within the allowable range 28 of the increase / decrease table 9 for the “dependent allowance” with the same increase / decrease direction. It is determined whether it is within the range. Personnel event item 21: “Dependent allowance” has a range of “−20,000 to +20,000” as an allowable range in the increase / decrease table 9. Therefore, the comparison / determination unit 14 determines that the increased amount of 4,000 yen is within the allowable range. Similarly, whether or not the amount of 1,000 yen increased from January to February in the salary details information 31 is within the allowable range 28 of the increase / decrease table 9 for the “single appointment allowance” with the same increase / decrease direction Determine. Personnel event item 21: “Personal appointment allowance” has a range of “−55,000 to +55,000” as an allowable range in the increase / decrease table 9. Therefore, the comparison determination unit 14 determines that the increased amount of 1,000 yen is within the allowable range.

  As a result of the above determination, the amount of increase / decrease is within the allowable range for both “dependent family allowance” and “single employee allowance” whose directions of increase / decrease were the same. In this case, it is determined Yes in step ST8, and this flow ends.

  On the other hand, even if the direction of increase / decrease is the same, if the increase / decrease amount of “Dependent allowance” or “Single employee allowance” is out of the allowable range 28, it is considered that there is some input error, etc. . In this case, it is determined No in step ST8, the flow proceeds to step ST7, and this flow ends after the notification unit 15 outputs the notification information.

  As described above, in the second embodiment, even if the increase / decrease directions coincide, the amount of money increased / decreased from the previous month of the detection target month of the salary detail information 31 to the detection target month is When the range shown in the allowable range 28 is exceeded, notification is performed. Therefore, for example, when the user makes an input error when changing the salary detail information 31, for example, when a large numerical value is input, even if the increase / decrease directions match, the range indicated by the allowable range 28 is not changed. If the increased or decreased amount is exceeded, a notification is given. Or, for example, if the program ends with an error without outputting a normal value and outputs a value of 0, the increased or decreased amount exceeds the range shown in the allowable range 28 of the increase / decrease table 9 Notification will be made if there is. From the above, it is possible to detect erroneous salary payments with higher accuracy.

  In the example illustrated in FIG. 7, the notification unit 15 does not output notification information when the amount increased or decreased in the verification target month is within the range indicated by the allowable range 28 compared to the previous month of the verification target month. An example was given. However, the embodiment is not limited to this. For example, when the amount of money increased or decreased in the verification target month compared with the previous month of the verification target month is within the range indicated by the allowable range 28, the notification unit 15 outputs notification information indicating that no incorrect salary payment has been detected. May be.

  Next, a third embodiment will be described. For example, two or more personnel events may occur for one employee in the same month. This is the case, for example, when the number of dependents changes due to childbirth (additional) and at the same time the child enters parental leave and takes leave (additional). In such a case, referring to the increase / decrease table 9 in FIG. 3, it is shown that “dependence allowance” and “single allowance allowance” are increased in the personnel event of “addition of dependent family number change”. However, it is shown that “addition” of “leave” reduces “sustainable allowance” and “single allowance”.

  In such a case, in order to finally determine whether the “support allowance” and the “single employee allowance” should be increased or decreased, in the personnel event item 21 of the increase / decrease table 9 as a third embodiment, A priority order may be set for this. For example, in the case of a company that stipulates that a person who does not take a leave of absence will not be paid, a decrease in the amount of payment due to a leave will be greater than an increase in the amount of payment due to a change in the number of dependents. In such a case, setting “work leave” is given priority over “change in the number of dependents” in the personnel event item 21. In the salary error supply detection system 3, since “work leave” is prioritized over “change in the number of dependents”, the salary error supply detection processing shown in FIGS. 6 and 7 using only the “absence” personnel event record 23. Execute.

  For example, for each of the personnel event items 21 shown in the increase / decrease table 9, the priority order information specifying the upper personnel event item 21 and the lower personnel event item 21 for the personnel event item 21 is added to the increase / decrease table 9. You may set by adding to. Here, it is assumed that the higher-order personnel event item 21 has priority over the lower-order personnel event item 21. When the personnel event acquisition unit 8 acquires the personnel event record 23, the personnel event acquisition unit 8 sets the application date 19 belonging to the detection target month to the employee (detection target person) indicated by the staff number 16 of the acquired personnel event record 23. It is determined whether there are a plurality of personnel event records 23 possessed. When there is no plurality of personnel event records 23 having the application date 19 belonging to the detection target month for the detection target person, the subsequent processing performs, for example, steps S2 to S7 of the first embodiment. However, when there are a plurality of personnel event records 23 having the application date 19 belonging to the detection target month for the detection target person, the priority event information 23 in the increase / decrease table 9 is used to determine the highest priority personnel event record 23. . For example, when a plurality of personnel event records 23 having an application date 19 belonging to the detection target month are registered in the personnel event database 7 for one employee, the personnel event acquisition unit 8 has a plurality of personnel events. The priority order information in the increase / decrease table 9 is referred to for each event record 23. The personnel event acquisition unit 8 determines which personnel event record 23 has the highest priority according to the priority order information in the increase / decrease table 9. For example, the processing of step S2 to step S7 of the first embodiment is performed on the one priority personnel event record 23 thus determined.

  As described above, even if two or more personnel events occur in the same month for one employee, whether or not the salary item 25 should be increased or decreased by setting a priority order Can be determined.

  FIG. 8 is a diagram illustrating a hardware configuration of the computer system 100 for realizing the erroneous salary detection system 3 according to an embodiment. As shown in FIG. 8, the computer system 100 includes a CPU 101, a memory 102, a storage unit 103, a reading unit 104, a communication interface 106, and an input / output unit 107. The CPU 101, the memory 102, the storage unit 103, the reading unit 104, the communication interface 106, and the input / output unit 107 are connected to each other via a bus 108, for example.

  The program describing the procedure of the operation flow shown in FIG. 6 and FIG. 7 may be stored in the memory 102 and the storage unit 103, for example. For example, the CPU 101 reads and executes the program describing the procedure of the operation flow shown in FIG. 6 and FIG. 7 using the memory 102, so that the personnel information change unit 6, the personnel event acquisition unit 8, and the increase / decrease A part or all of the functions of the information acquisition unit 10, the salary item determination unit 12, the salary details acquisition unit 11, the salary calculation unit 13, the comparison determination unit 14, and the notification unit 15 are provided.

  The memory 102 is a semiconductor memory, for example, and includes a RAM area and a ROM area. The storage unit 103 is a hard disk, for example, and stores a salary error supply detection program according to the embodiment. Note that the storage unit 103 may be a semiconductor memory such as a flash memory. The storage unit 103 may be an external recording device.

  The reading unit 104 accesses the removable recording medium 105 according to an instruction from the CPU 101. The detachable recording medium 105 includes, for example, a semiconductor device (USB memory or the like), a medium to / from which information is input / output by a magnetic action (magnetic disk or the like), a medium to / from which information is input / output by an optical action (CD-ROM, For example, a DVD). The communication interface 106 transmits / receives data via a network according to instructions from the CPU 101. The input / output unit 107 functions as, for example, an interface between a device that receives an instruction from a user, a display device, a speaker, and the like.

The salary error supply detection program of the embodiment is provided to the computer system 100 in the following form, for example.
(1) Installed in advance in the storage unit 103.
(2) Provided by the removable recording medium 105.
(3) Provided from the program server 109.

  In addition, the salary error supply detection method of the embodiment may provide the processing of the above-described operation flow using a plurality of computers. In this case, a certain computer may request a part of the processing of the above-described operation flow to another computer via a network and receive the processing result.

  Furthermore, a part of the salary error supply detection system of the embodiment may be realized by hardware. Alternatively, the salary error supply detection system may be realized by a combination of software and hardware.

  Further, the erroneous salary detection system of the embodiment may be implemented on the cloud. FIG. 9 is a diagram illustrating a server computer 110 on which an erroneous salary payment detection program according to an embodiment is installed and a computer 111 that receives a service. For example, the server computer 110 receives request information for detection of erroneous salary payment from the computer 111 via the network, and returns a result of executing the erroneous salary payment detection program to the computer 111.

  Several embodiments have been described. By using the above-described erroneous salary payment detection system 3, for example, the salary item 25 that needs to be changed due to a personnel event is identified from the increase / decrease table 9, and the identified salary item 25 is the salary detail information 31 of the verification month. By checking whether the amount has been changed, it is possible to detect erroneous payment of salary. Since the salary item 25 that needs to be changed can be specified by using the increase / decrease table 9, the salary item 25 in which a change that easily causes an error due to an input error or the like is extracted, and the erroneous salary detection processing is executed. be able to. Accordingly, the amount of processing necessary for the erroneous salary supply detection processing is reduced, so that the processing load on the computer is small and fast processing is possible.

  Further, since the increase / decrease direction of the amount of the salary item 25 that needs to be changed due to a personnel event is specified by the increase / decrease table 9, even if the amount of the salary item 25 that needs to be changed is changed in the salary detail information 31 If the increase / decrease direction does not match, it is possible to detect an erroneous payment of salary.

  Furthermore, since the allowable range of the change amount of the payment amount is defined in the increase / decrease table 9, even if the direction of increase / decrease in the payment amount is the same, if the changed amount exceeds the allowable range, the salary Can be detected.

  In addition, the above-described embodiment can be applied to detection of erroneous salary payments for a plurality of salary items 25. For example, even when there is only one salary item 25 (for example, only salary), erroneous salary payments are detected. Can be applied to.

  In addition, the above-described salary error supply detection process does not require complicated processing, and the direction of increase / decrease obtained by referring to the increase / decrease table 9 and the increase / decrease obtained by comparing the salary details of the detection target month and the previous month. The simple process of simply comparing the direction can reduce the missed detection of incorrect salary payments. Therefore, even when the number of employees and the number of salary items are very large, the processing load on the computer is small and fast processing is possible, and the salary error supply detection processing can be effectively performed. Therefore, for example, in a site where there are a large number of salary items, such as a public institution, the salary error supply detection process can be used effectively.

  According to some embodiments, the direction of increase / decrease in the amount of salary items obtained based on personnel events in the month subject to detection of incorrect salary payments, and the difference between the salary items in the salary details of the month subject to detection and the previous month It is possible to warn when the direction of increase / decrease does not match, and to reduce the missed detection of incorrect salary payment.

  In the above, several embodiments have been described. However, the embodiments according to the present invention are not limited to the above-described embodiments, but should be understood as including various modifications and alternative forms of the above-described embodiments. For example, it will be understood that various embodiments can be embodied by modifying the components without departing from the spirit and scope thereof. Further, it will be understood that various embodiments according to the present invention can be formed by appropriately combining a plurality of constituent elements disclosed in the above-described embodiments. Alternatively, various implementations according to the present invention may be made by deleting or replacing some components from all the components shown in the embodiment, or adding some components to the components shown in the embodiment. One skilled in the art will appreciate that the form may be implemented.

1 Personnel system 2 Salary system 3 Salary error supply detection system 4 Personnel information database 5 Salary information database 6 Personnel information change section 7 Personnel event database 8 Personnel event acquisition section 9 Increase / decrease table 10 Increase / decrease information acquisition section 11 Salary details acquisition section 12 Salary payment Item determination unit 13 Salary calculation unit 14 Comparison determination unit 15 Notification unit 100 Computer system 101 CPU
102 Memory 103 Storage Unit 104 Reading Unit 105 Removable Recording Medium 106 Communication Interface 107 Input / Output Unit 108 Bus 109 Program Server 110 Server Computer 111 Computer

Claims (1)

From the personnel event database that stores personnel event information that represents personnel events, obtain personnel event information that applies to the detection target month for the detection target person to detect the presence or absence of incorrect salary payments,
Increase / decrease in the amount of salary for salary items corresponding to the acquired personnel event information using the increase / decrease table that correlates the direction of increase / decrease in the salary item's amount of payment for the personnel event information stored in the storage unit HR event change information representing the direction of
Obtaining the salary detail information of the detection target month of the detection target person and the salary detail information of the previous month of the detection target month from the salary information database;
By comparing the acquired salary detail information of the detected month and the salary detail information of the previous month, the amount of payment from the previous month to the detected month of the salary item corresponding to the acquired personnel event information Get salary details increase / decrease information indicating the direction of increase / decrease,
Compare the increase / decrease direction of the personnel event increase / decrease information with the increase / decrease direction of the salary details increase / decrease information,
If the increase / decrease direction does not match, output notification information.
An incorrect pay detection program for causing a computer to execute processing.