Labor management device, labor management method and labor management program

Abstract

To provide a labor management device, a labor management method, and a labor management program that reduce the workload of a person in charge of labor management operations.SOLUTION: Provided is a system comprising: an extraction part that refers to first settlement data that manages whether employees' working hours, payment amounts, and eligibility and disqualification requirements for social insurance and employment insurance are satisfied, and extracts the cumulative number of times that the eligibility requirements are satisfied; an alert determination part that refers to an alert determination master that manages alerts corresponding to the cumulative number of times the eligibility requirements for social insurance and employment insurance are satisfied, and determines alerts based on the cumulative number of times extracted by the extraction part; a first data generation part that stores the determination result of the alert determination part into the first settlement data and generates the first settlement data; and a function that displays, on an alert display screen, the alerts stored in the first settlement data.SELECTED DRAWING: Figure 16

Description

Technical Field

[0001] The present invention relates to a labor management device, a labor management method, and a labor management program.

Background Art

[0002] Patent Document 1 discloses a staff shift adjustment system and the like that reduces the labor of individual applicants to multiple employers while ensuring flexible working opportunities for candidate staff who wish to work in terms of time and work location, etc., and enables the employer stores to reduce the costs of advertising and the labor of handling inquiries.

[0003] Patent Document 1 also enables the use of this system for attendance management. Specifically, after securing the working hours of staff at the store-side terminal 4 of this system, if the staff works on time, the scheduled working hours are directly determined as the actual working hours, and if the staff does not work on time, the scheduled working hours can be corrected at the store-side terminal 4 to determine the actual working hours, thus enabling use for attendance management (paragraph 0062).

[0004] Also, when a request for working within the dependent limit is set from the staff terminal 3 to the shift management server 1, it is possible to notify the corresponding staff terminal 3 to that effect when the income amount calculated based on the cumulative time of the working hours and the hourly wage approaches the limit amount of the dependent deduction (paragraph 0064).

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] Here, in labor management operations, the workload of checking enrollments and cancellations in social insurance and employment insurance based on work performance and payment performance has been high, which has been a problem.

[0007] The present invention has been made in view of the above, and an object thereof is to provide a labor management device, a labor management method, and a labor management program that reduce the workload of a person in charge in labor management operations.

Means for Solving the Problems

[0008] In order to solve the above problems and achieve the object, a labor management device according to the present invention refers to first data that manages whether an employee's working hours, payment amount, social insurance and employment insurance enrollment requirements and loss requirements are met, and extracts the corresponding cumulative number of times that meets the enrollment requirements. An extraction unit; referring to an alert master that manages an alert according to the corresponding cumulative number of times that meets the social insurance and employment insurance enrollment requirements, and determining an alert based on the corresponding cumulative number of times extracted by the extraction unit; an alert determination unit; a first data generation unit that stores the determination result of the alert determination unit in the first data and generates the first data; and a display control unit that displays the alert stored in the first data on a work status confirmation screen for checking the work status of an employee.

[0009] In order to solve the above problems and achieve the object, a labor management device according to the present invention refers to second data that manages the cumulative payment amount of an employee, and obtains a cumulative payment amount at the end of the previous month corresponding to a predetermined year and month, which is the cumulative payment amount at the end of the previous month, and a cumulative payment amount at the end of the current month, which is the cumulative payment amount up to the end of the predetermined year and month. An acquisition unit; the display control unit is characterized in that it displays the cumulative payment amount at the end of the previous month and the cumulative payment amount at the end of the current month acquired by the acquisition unit on a work status confirmation screen.

[0010] In order to solve the above problems and achieve the object, the extraction unit of the labor management device according to the present invention further extracts the payment amount and working hours in the first data, the alert master stores an alert according to the payment amount or working hours in addition to the corresponding cumulative number of times, and the alert determination unit refers to the alert master and determines an alert based on the corresponding cumulative number of times, payment amount and working hours extracted by the extraction unit.

[0011] In order to solve the above problems and achieve the object, the working hours of the first data of the labor management device according to the present invention are obtained by aggregating the actual working hours actually worked, and when the actual working hours are not registered, the planned working hours, which are the planned working hours, are aggregated. The paid amounts of the first data and the second data are obtained by aggregating the actual paid amounts, and when the actual paid amounts are not registered, the planned paid amounts, which are the planned paid amounts, are aggregated.

[0012] In order to solve the above problems and achieve the object, the labor management method according to the present invention includes an extraction step in which an extraction unit refers to first data that manages whether a company employee's working hours, paid amount, social insurance, and employment insurance eligibility and loss requirements are met, and extracts the corresponding cumulative number of times that meet the eligibility requirements; an alert determination step in which an alert determination unit refers to an alert master that manages alerts according to the corresponding cumulative number of times that meet the social insurance and employment insurance eligibility requirements, and determines an alert based on the corresponding cumulative number of times extracted by the extraction unit; a first data generation step in which a first data generation unit stores the determination result of the alert determination unit in the first data and generates the first data; and a display control step in which a display control unit displays the alert stored in the first data on a work status confirmation screen for checking the work status of the company employee.

[0013] In order to solve the above problems and achieve the object, the labor management program according to the present invention causes a computer to function as an extraction unit that refers to first data that manages whether a company employee's working hours, paid amount, social insurance, and employment insurance eligibility and loss requirements are met, and extracts the corresponding cumulative number of times that meet the eligibility requirements; an alert determination unit that refers to an alert master that manages alerts according to the corresponding cumulative number of times that meet the social insurance and employment insurance eligibility requirements, and determines an alert based on the corresponding cumulative number of times extracted by the extraction unit; a first data generation unit that stores the determination result of the alert determination unit in the first data and generates the first data; and a display control unit that displays the alert stored in the first data on a work status confirmation screen for checking the work status of the company employee.

Advantages of the Invention

[0014] The present invention can reduce the workload of the person in charge in labor management operations.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Mode for Carrying Out the Invention

[0016] Hereinafter, embodiments of a labor management device, a labor management method, and a labor management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited by the present embodiment.

[0017] [1. Overview] In the case of companies with many part-time workers such as the food service industry and multi-store operations, it is necessary to check the enrollment and loss of social insurance and employment insurance based on work performance and payment performance. In the current system, when the requirements for enrollment (loss) are met continuously for two months, the person in charge needs to perform enrollment and loss procedures, so the workload of the person in charge for requirement checking is high.

[0018] Furthermore, part-time workers hope to work within the scope of health insurance dependents and tax dependents (income ceiling). Therefore, at the end of the year, they often calculate the working hours that can be worked within the scope of dependents manually and then adjust the shift, further increasing the workload of the person in charge.

[0019] The present invention calculates the current payment prediction amount according to the hourly wage and work shift (schedule / actual performance), and sets stepwise thresholds until the requirements for enrollment (loss) of social insurance and employment insurance are met, and displays an alert. Furthermore, the cumulative predicted annual income amount can be visualized and confirmed from the cumulative past salary payment performance, the work shift (schedule / actual performance) from the current month onward, and the hourly wage.

[0020] [2. Configuration] An example of the configuration of the business support device 100 (including the labor management device of the present invention) according to this embodiment will be described with reference to FIG. 1 and the like. FIG. 1 is a block diagram showing an example of the configuration of the business support device 100.

[0021] The business support device 100 is constructed based on a commercially available desktop personal computer. Note that the business support device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, and may be constructed based on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer.

[0022] The business support device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the business support device 100 is communicably connected via an arbitrary communication path.

[0023] The communication interface unit 104 communicably connects the business support device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of communicably connecting the business support device 100 and the server 200 to each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the storage unit 106 may be stored in the server 200, for example.

[0024] An input / output interface unit 108 is connected to an input device 112 and an output device 114. As the output device 114, in addition to a monitor (including a home TV), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Hereinafter, in some cases, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

[0025] The storage unit 106 stores various databases, tables, files, etc. A computer program for giving commands to the CPU (Central Processing Unit) to perform various processes in cooperation with the OS (Operating System) is recorded in the storage unit 106. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used.

[0026] The storage unit 106 stores a requirement master 106a, an employee master 106b, a closing date master 106c, an alert determination master 106d (corresponding to the alert master of the present invention), first daily data 106e, first closing data 106f (corresponding to the first data of the present invention), second daily data 106g, and second closing data 106h (corresponding to the second data of the present invention), etc.

[0027] The requirement master 106a is for managing the requirements for joining and losing social insurance and employment insurance. As shown in FIG. 2, the requirement master 106a stores the joining check requirements and losing check requirements for social insurance and employment insurance. When a law amendment or the like is made, the requirement master 106a is updated each time.

[0028] As shown in FIG. 3, the employee master 106b manages employee information. The employee master 106b stores employee identification information (e.g., employee code, etc.), a closing date classification for classifying the closing date of salary calculation, an hourly wage, a social insurance classification for classifying the enrollment / non-enrollment in social insurance, an employment insurance classification for classifying the enrollment / non-enrollment in employment insurance, and a part-time student classification for classifying whether it is subject to part-time student requirements, etc.

[0029] As shown in FIG. 4, the closing date master 106c is for managing the closing date information of salary calculation. The closing date master 106c stores the closing year and month, the closing date classification, the period start date, the attendance closing date, the salary payment month, and an initialization flag for determining whether to initialize the cumulative annual income of the previous month in the second closing calculation data, etc. When the initialization flag is "0", it indicates that the cumulative annual income of the previous month is not initialized, and when the initialization flag is "1", it indicates that the cumulative annual income of the previous month is initialized.

[0030] As shown in FIG. 5, the alert determination master 106d is for managing alert information related to social insurance enrollment requirements, etc. The alert determination master 106d stores a threshold value 1 (exceeded cumulative number of times), a threshold value 2 (predicted payment amount), a threshold value 2 (weekly working hours), and an alert type and remarks, etc.

[0031] As shown in FIG. 6, the first day calculation data 106e is for managing information related to working hours and payment amounts. The first day calculation data 106e stores employee identification information, working days, planned working hours, predicted payment amount (planned), actual working hours, and predicted payment amount (actual), etc.

[0032] The first summary data 106f is for managing the labor information aggregated by the closing date, as shown in FIG. 7. The first summary data 106f stores employee identification information, attendance closing date, total labor forecast, weekly labor forecast, payment amount forecast, item names "Requirement A" to "Requirement G" for storing whether they apply to Requirements A to G in the requirement master, a section for aggregating flags corresponding to Requirements A to C which are social insurance enrollment requirements (e.g., social insurance CHK cumulative, etc.), a section for aggregating flags corresponding to Requirements D and E which are employment insurance enrollment requirements (e.g., employment insurance CHK cumulative, etc.), a section for aggregating flags corresponding to Requirement F which is a social insurance loss requirement (e.g., social insurance loss CHK cumulative, etc.), a section for aggregating flags corresponding to Requirement G which is an employment insurance loss requirement (e.g., employment insurance loss CHK cumulative, etc.), the alert type for social insurance enrollment requirements which is the determination result of the alert determination section (e.g., social insurance alert, etc.) and the alert type for employment insurance enrollment requirements which is the determination result of the alert determination section (e.g., employment insurance alert, etc.), etc.

[0033] The second daily data 106g is for managing information regarding working hours and payment amounts, as shown in FIG. 8. The second daily data 106g stores employee identification information, working day, scheduled working hours, payment amount forecast (scheduled), actual working hours, and payment amount forecast (actual), etc.

[0034] The second summary data 106h is for managing the labor information aggregated by the closing date, as shown in FIG. 9. The second summary data 106h stores employee identification information, attendance closing date, salary payment month, payment amount forecast, cumulative annual income of the previous month-end, and cumulative annual income of the current month-end, etc.

[0035] Returning to FIG. 1, the control unit 102 is a CPU etc. that comprehensively controls the business support device 100. The control unit 102 has an internal memory for storing control programs such as the OS, programs defining various processing procedures, etc., and required data, and executes various information processes based on these stored programs.

[0036] Functionally conceptually, the control unit 102 includes a staff information registration unit 102a, a closing date master setting unit 102b, a work registration unit 102c (including the extraction unit, acquisition unit, and display control unit of the present invention), an alert determination unit 102d (including the alert determination unit, first data generation unit, and display control unit of the present invention), and the like. Note that the alert display screen MA and the cumulative annual income display screen MB correspond to the work status confirmation screen of the present invention.

[0037] The staff information registration unit 102a stores the staff information (staff code, closing date classification, hourly wage, social insurance classification, employment insurance classification, working student classification, etc.) set by the person in charge or the like in the staff master 106b and generates the staff master 106b.

[0038] The closing date master setting unit 102b stores the closing date information (closing year and month, closing date classification, period start date, attendance closing date, salary payment month, initialization flag, etc.) set by the person in charge or the like in the closing date master 106c and generates the closing date master 106c.

[0039] The work registration unit 102c performs the following processes (11) to (13) as the registration process of the work shift and work performance (generation process of the first daily work data 106e and the second daily work data 106g). Note that the process of the first daily work data 106e will be described, and the second daily work data 106g is also generated by the same process. (11) Refer to the staff master 106b and obtain the hourly wage associated with a predetermined staff code. (12) Refer to the shift management data (not shown), obtain the scheduled working hours based on a predetermined staff code and the work date, store it in the item "scheduled working hours" associated with the corresponding work date of the first daily work data 106e, calculate the scheduled payment amount by multiplying the hourly wage obtained in (11) by the obtained scheduled working hours, and store it in the item "predicted payment amount (scheduled)" associated with the corresponding work date of the first daily work data 106e. If there is no shift registration, store "no shift registration" in the item "scheduled working hours" associated with the corresponding work date of the first daily work data 106e, "0" in the item "predicted payment amount (scheduled)", "-" in the item "actual working hours", and "0" in the item "predicted payment amount (actual)". (13) Refer to the labor time management data (not shown), obtain the actual labor time based on a predetermined employee code and working day, store it in the item "Actual Labor Time" associated with the corresponding working day in the first daily summary data 106e, calculate the payment amount by multiplying the hourly wage obtained in (11) by the obtained actual labor time, and store it in the item "Predicted Payment (Actual)" associated with the corresponding working day in the first daily summary data 106e. Note that the item "Actual Labor Time" associated with the corresponding working day in the first daily summary data 106e does not store "-", and the item "Predicted Payment (Actual)" does not store "0". If the actual labor time is not stored in the labor time management data, store "(before actual registration)" in the item "Actual Labor Time" of the first daily summary data 106e and store "0" in the item "Predicted Payment (Actual)" of the first daily summary data 106e.

[0040] The attendance registration section 102c performs the following processes (21) to (27) as the closing process (generation of the first closing data 106f). (21) Refer to the closing date master 106c, obtain the period start date corresponding to a predetermined attendance closing date, and obtain the first daily summary data 106e from the period start date corresponding to the predetermined employee code to the attendance closing date. (22) Aggregate the actual labor time (if the actual labor time is not stored, the planned labor time) of the first daily summary data 106e obtained in (21), and store it in the item "Total Labor Prediction" associated with the predetermined employee code and the predetermined attendance closing date in the first closing data 106f. (23) Calculate the total labor prediction aggregated in (22) ÷ 4.3 to calculate the weekly labor prediction, and store it in the item "Weekly Labor Prediction" associated with the predetermined employee code and the predetermined attendance closing date in the first closing data 106f. (24) Aggregate the amount of the predicted payment (actual) (if the amount is not stored in the predicted payment (actual), the amount of the predicted payment (planned)) of the first daily summary data 106e obtained in (21), and store it in the item "Predicted Payment" associated with the predetermined employee code and the predetermined attendance closing date in the first closing data 106f. Refer to the requirement master 106a, check whether the items "total labor forecast", "weekly labor forecast", and "payment amount forecast" in the first summary data 106f correspond to requirements A to G. If they correspond, store "1" in the items "requirement A" to "requirement G" corresponding to the specified employee code and the specified attendance closing date in the first summary data 106f; if they do not correspond, store "0". In the case where the requirement is an average of 6 months (for example, requirement B, etc.), calculate the 6-month average from the weekly labor forecast and payment amount forecast of the past finalized data and the current month's data, make a judgment on whether the requirement corresponds or not, and store the judgment result in the first summary data 106f.

[0041] (26) In the first summary data, based on the flag stored in the process of (25), perform the following process to calculate the social insurance CHK cumulative and employment insurance CHK cumulative, and store the flag in the items "social insurance CHK cumulative" and "employment insurance CHK cumulative" of the first summary data 106f (see Figure 13). <No condition>... When there is no flag until the previous month Flag of requirement A or requirement B in the current month = 0... Social insurance CHK cumulative = 0 (initialization process) Flag of requirement D or requirement E in the current month = 0... Employment insurance CHK cumulative = 0 (initialization process) <When the previous month's social insurance CHK cumulative and employment insurance CHK cumulative = 0> Flag of requirement A or requirement B in the current month = 1... Social insurance CHK cumulative = 1 Flag of requirement D or requirement E in the current month = 1... Employment insurance CHK cumulative = 1 <When the previous month's social insurance CHK cumulative and employment insurance CHK cumulative = 1 or 2> Flag of requirement A or requirement B in the current month = 1... Social insurance CHK cumulative = 2 Flag of requirement D or requirement E in the current month = 1... Employment insurance CHK cumulative = 2

[0042] (27) In the first summary data, based on the flag stored in the process of (25), perform the following process to calculate the social insurance loss CHK cumulative and employment insurance loss CHK cumulative, and store the flag in the items "social insurance loss CHK cumulative" and "employment insurance loss CHK cumulative" of the first summary data 106f (see Figure 13). <No condition>... When there is no flag until the previous month When the flag of requirement F for the current month = 0... Social insurance loss CHK cumulative = 0 (Initialization process) When the flag of requirement G for the current month = 0... Employment insurance loss CHK cumulative = 0 (Initialization process) <When the cumulative social insurance loss CHK and cumulative employment insurance loss CHK for the previous month = 0> When the flag of requirement F for the current month = 1... Social insurance loss CHK cumulative = 1 When the flag of requirement G for the current month = 1... Employment insurance loss CHK cumulative = 1 <When the cumulative social insurance loss CHK and cumulative employment insurance loss CHK for the previous month = 1 or 2> When the flag of requirement F for the current month = 1... Social insurance loss CHK cumulative = 2 When the flag of requirement G for the current month = 1... Employment insurance loss CHK cumulative = 2

[0043] The work registration department 102c performs the following processes (31) to (34) as the closing process (generation of the second closing data 106h). (31) Refer to the closing date master 106c and obtain the "period start date", "attendance closing date", "salary payment month", and "initialization flag" associated with the specified closing year and month. (32) Store the specified employee code, the attendance closing date and the salary payment month obtained in (31) in the items "employee code", "attendance closing date", and "salary payment month" of the second closing data 106h. (33) Refer to the second daily data 106g, total the "predicted payment amount (actual)" from the "period start date" to the "attendance closing date" obtained in (31) (if there is no actual value in the "predicted payment amount (actual)", use the value of the "predicted payment amount (scheduled)"), and store it in the item "predicted payment amount" of the second closing data 106h. (34) Refer to the initialization flag obtained in (31), perform the following processes, calculate the cumulative annual income for the previous month and the cumulative annual income for the current month, and store them in the items "cumulative annual income for the previous month" and "cumulative annual income for the current month" of the second closing data 106h (see Figure 18). <When the closing date master. initialization flag = 1> Store "cumulative annual income for the previous month" of the second closing data 106h = 0 (Initialization process). The item "Cumulative Annual Income at the End of the Current Month" in the second closing data 106h stores the monthly payment prediction (the value calculated in (33)). <At other times> The item "Cumulative Annual Income at the End of the Previous Month" in the second closing data 106h stores the cumulative amount from the value of the item "Predicted Payment Amount" in the second closing data 106h for January of the "Salary Payment Month" to the value of the item "Predicted Payment Amount" in the second closing data 106h for the previous month. The item "Cumulative Annual Income at the End of the Current Month" in the second closing data 106h stores the value calculated as the value of the item "Cumulative Annual Income at the End of the Previous Month" in the second closing data 106h + the predicted monthly payment amount in the second closing data 106h for the current month (the value calculated in (33)).

[0044] The work registration unit 102c performs the following processes (41) to (45) as display processing. (41) Receive an instruction to specify a predetermined employee code and a predetermined closing month and display the cumulative annual income display screen MB. (42) Display the cumulative annual income display screen MB and display the predetermined employee code and the predetermined closing month in the "Closing Month" in the area MB1 and the "Employee Code" in the area MB2 of the cumulative annual income display screen MB. (43) Refer to the closing date master 106c and obtain the "Start Date of Work" and the "Attendance Closing Date" corresponding to the predetermined closing month. (44) Refer to the second timekeeping data 106g, obtain the "Working Day", the "Scheduled Working Hours" and the "Actual Working Hours" corresponding to the "Attendance Closing Date" from the "Start Date of Work" obtained in (43), and display them in the "Working Day" in the area MB31, the "Scheduled Working Hours" in the area MB32 and the "Actual Working Hours" in the area MB33 of the cumulative annual income display screen MB. (45) Refer to the second closing data 106h, obtain the "Predicted Payment Amount", the "Cumulative Annual Income at the End of the Previous Month" and the "Cumulative Annual Income at the End of the Current Month" corresponding to the attendance closing date obtained in (43), and display them in the "Predicted Payment Amount" in the area MB41, the "Cumulative Annual Income at the End of the Previous Month" in the area MB42 and the "Cumulative Annual Income at the End of the Current Month" in the area MB43 of the cumulative annual income display screen MB.

[0045] The alert determination unit 102d performs the following processes (51) to (53) as alert determination processing. Refer to the first consolidated data 106f and confirm that it is stored from the item "Employee Code" to the item "Unemployment Insurance Loss CHK Cumulative". Refer to the first consolidated data 106f and obtain the values of the social insurance CHK cumulative and unemployment insurance CHK cumulative of the previous month's first consolidated data 106f and the values of the payment performance prediction and weekly working hours prediction of the current month's first consolidated data 106f. Refer to the alert determination master 106d, determine the alert type based on the values obtained in (52), and store it in the items "Social Insurance Alert" and "Unemployment Insurance Alert" of the current month's first consolidated data 106f. Regarding the threshold value 2 (payment performance / weekly working hours) of the alert determination master 106d, it is the alert target if it meets any of the conditions.

[0046] The alert determination unit 102d performs the following processes (61) to (65) as alert display processing. (61) Receive an instruction to specify a predetermined employee code and a predetermined closing month and display the alert display screen MA. (62) Display the alert display screen MA and display the predetermined employee code and the predetermined closing month in the "Closing Month" of the area MA1 and the "Employee Code" of the area MA2 of the alert display screen MA. (63) Refer to the closing date master 106c and obtain the "Start Date of Work" and "Attendance Closing Date" corresponding to the predetermined closing month. (64) Refer to the first day count data 106e, obtain the "Working Days" from the "Start Date of Work" to the "Attendance Closing Date" obtained, the "Scheduled Working Hours" and "Actual Working Hours" corresponding to the working days, and display them in the "Working Days" of the area MA31, the "Scheduled Working Hours" of the area MA32, and the "Actual Working Hours" of the area MA33 of the alert display screen MA. (65) Refer to the first consolidated data 106f, obtain the "Total Labor Prediction", "Social Insurance Alert", and "Unemployment Insurance Alert" corresponding to the attendance closing date obtained in (63), and display them in the "Total Labor Prediction" of the area MA41, the "Social Insurance Alert" of the area MA42, and the "Unemployment Insurance Alert" of the area MA43 of the alert display screen MA.

[0047] [3. Specific Examples of Processing] A specific example of the processing executed by the business support apparatus 100 configured as described above will be described in detail with reference to FIGS. 10 to 19 and the like.

[0048] [Register Employee Information] The person in charge gives an instruction to display an employee information input screen (not shown).

[0049] The employee information registration unit 102a displays the employee information input screen. The employee information registration unit 102a causes the person in charge or the like to register employee information on the employee information input screen and generates an employee master 106b. For example, it stores an employee code "100001", a closing date classification "31", an hourly wage "1,000 yen", a social insurance classification "non-enrollment", an employment insurance classification "non-enrollment", and a part-time student classification "not applicable" and generates an employee master 106b (see step S1, FIG. 10).

[0050] [Set Closing Date Master] The person in charge gives an instruction to display a closing date master setting screen (not shown).

[0051] The closing date master setting unit 102b displays the closing date master setting screen. The closing date master setting unit 102b causes the person in charge or the like to register closing date information on the closing date master setting screen and generates a closing date master 106c. For example, it stores a closing year and month "2022 / 9", a closing date classification "31", a period start date "2022 / 9 / 1", a work attendance closing date "2022 / 9 / 30", a salary payment month "2022 / 10", and an initialization flag "0" and generates a closing date master 106c (see step S2, FIG. 11).

[0052] [Generate Daily Attendance Data] An example of a record of the employee code "100002" and the work date "2023 / 3 / 1" in the first daily attendance data 106e will be described.

[0053] The work registration unit 102c refers to the employee master 106b and acquires the hourly wage "1,000 yen" associated with a predetermined employee code "100002".

[0054] The work registration department 102c refers to the shift management data (not shown), obtains the scheduled working hours of "3 hours" based on the employee code "100002" and the working date "2023 / 3 / 1", stores the scheduled working hours of "3 hours" associated with the working date "2023 / 3 / 1" in the first-day summary data 106e, calculates the scheduled payment amount of "3,000 yen" by multiplying the hourly wage of "1,000 yen" by the scheduled working hours of "3 hours", and stores it in the item "Predicted Payment Amount (Scheduled)" associated with the working date "2023 / 3 / 1" in the first-day summary data 106e (see Figure 12).

[0055] The work registration department 102c refers to the working hours management data (not shown), obtains the actual working hours of "3 hours" based on the employee code "100002" and the working date "2023 / 3 / 1", stores the actual working hours of "3 hours" associated with the working date "2023 / 3 / 1" in the first-day summary data 106e, calculates the payment amount of "3,000 yen" by multiplying the hourly wage of "1,000 yen" by the actual working hours of "3 hours", and stores it in the item "Predicted Payment Amount (Actual)" associated with the working date "2023 / 3 / 1" in the first-day summary data 106e (see Figure 12). Note that since there is no work record registered in the working hours management data for the employee code "100002" and the working date "2023 / 3 / 3", "(before actual registration)" is stored in the actual working hours, and "0 yen" is stored in the predicted payment amount (actual).

[0056] The work registration department 102c performs the same processing for the second-day summary data 106g as for the first-day summary data 106e (see Figure 17).

[0057] The work registration department 102c generates the first-day summary data 106e and the second-day summary data 106g (see Figures 12 and 17).

[0058] (Check for enrollment and loss of social insurance and employment insurance) Taking the employee code "100002" and the work closing date "2023 / 3 / 31" as an example for explanation. Note that the requirements for working students (requirement C) are omitted.

[0059] Based on the closing date of work "2023 / 3 / 31", the work registration department 102c refers to the closing date master 106c and obtains the period start date "2023 / 3 / 1" and the work attendance closing date "2023 / 3 / 31". The work registration department 102c refers to the first day summary data 106e and obtains the records from the period start date "2023 / 3 / 1" to the work attendance closing date "2023 / 3 / 31" of the employee code "100002".

[0060] For the work dates "2023 / 3 / 1" and "2023 / 3 / 2" from the records of the first day summary data 106e of the obtained employee code "100002", since the actual working hours are stored, the work registration department 102c aggregates the actual working hours. For the days after "2023 / 3 / 3", since the actual working hours are not stored, the planned working hours are aggregated, and "93 hours" is stored in the total labor prediction associated with the employee code "100002" and the work attendance closing date "2023 / 3 / 31" in the first closing summary data 106f (see Figures 12 and 15).

[0061] The work registration department 102c calculates the total labor prediction "93 hours" in the first day summary data 106e divided by 4.3 to calculate the weekly labor prediction "21.6", and stores "21.6" in the weekly labor prediction associated with the employee code "100002" and the work attendance closing date "2023 / 3 / 31" in the first closing summary data 106f (see Figure 15).

[0062] For the work dates "2023 / 3 / 1" and "2023 / 3 / 2" from the records of the first day summary data 106e of the obtained employee code "100002", since the predicted payment amount (actual) is stored, the work registration department 102c aggregates the predicted payment amount (actual). For the days after "2023 / 3 / 3", since the predicted payment amount (actual) is not stored, the predicted payment amount (planned) is aggregated, and "93,000 yen" is stored in the predicted payment amount associated with the employee code "100002" and the work attendance closing date "2023 / 3 / 31" in the first closing summary data 106f (see Figures 12 and 15).

[0063] The work registration department 102c obtains the total labor forecast of "93 hours", the weekly labor forecast of "21.6", and the payment amount forecast of "93,000 yen" for the first consolidated data 106f of employee code "100002" (see Figure 15).

[0064] The work registration department 102c refers to the requirement master 106a and checks whether the records of the first consolidated data 106f of the obtained employee code "100002" meet the requirements of requirement A and requirement D, "monthly, the actual payment is 88,000 yen or more and 20H or more per week". Since it meets the requirements, "1" is stored in requirement A and requirement D of the first consolidated data 106f (see Figures 2 and 15).

[0065] The work registration department 102c calculates the average of the weekly labor forecast and the payment amount forecast for the six months before the work closing date of "2023 / 3 / 31" (work closing date from "2022 / 10 / 31" to "2023 / 3 / 31") for the first consolidated data 106f of employee code "100002" (see <Six-month average result> in Figure 15).

[0066] The work registration department 102c refers to the requirement master 106a and checks whether the calculated six-month average weekly labor forecast and payment amount forecast meet the requirements of requirement B and requirement E, "six-month average, the actual payment is 88,000 yen or more and 20H or more per week". Since it does not meet the requirements, "0" is stored in requirement B and requirement E of the first consolidated data 106f (see Figures 2 and 15).

[0067] The work registration department 102c refers to the requirement master 106a and checks whether the requirements of requirement F "monthly and six-month average, the actual payment is less than 88,000 yen" and requirement G "monthly and six-month average, the actual payment is less than 88,000 yen and less than 20H per week" are met based on the monthly weekly labor forecast and payment amount forecast on the work closing date of "2023 / 3 / 31" and the calculated six-month average weekly labor forecast and payment amount forecast. Since it does not meet the requirements, "0" is stored in requirement F and requirement G of the first consolidated data 106f (see Figures 2 and 15).

[0068] Since the work registration department 102c has a social insurance CHK cumulative total of "1" for the previous month (the work attendance closing date is "2023 / 2 / 28") and an employee code of "100002" in the first closing data 106f, and a flag of "1" for requirement A in the current month (the work attendance closing date is "2023 / 3 / 31"), it stores "2" in the "social insurance CHK cumulative total" for the current month (see Figures 13 and 15).

[0069] Since the work registration department 102c has an employment insurance CHK cumulative total of "1" for the previous month (the work attendance closing date is "2023 / 2 / 28") and an employee code of "100002" in the first closing data 106f, and a flag of "1" for requirement D in the current month (the work attendance closing date is "2023 / 3 / 31"), it stores "2" in the "employment insurance CHK cumulative total" for the current month (see Figures 13 and 15).

[0070] The work registration department 102c obtains a social insurance loss CHK cumulative total of "0" and an employment insurance loss CHK cumulative total of "0" for the work attendance closing date of "2023 / 2 / 28" and employee code of "100002" in the first closing data 106f. Since the flags for requirements F and G in the current month (the work attendance closing date is "2023 / 3 / 31") are "0", it stores a social insurance loss CHK cumulative total of "0" and an employment insurance loss CHK cumulative total of "0" for the current month (see Figures 13 and 15).

[0071] The alert determination department 102d refers to the first closing data 106f and confirms that the items from "total working hours" to "employment insurance loss CHK cumulative total" in the record with the employee code "100002" and work attendance closing date of "2023 / 3 / 31" are stored (see Figure 15).

[0072] The alert determination department 102d refers to the first closing data 106f and obtains the social insurance CHK cumulative total of "1" and the employment insurance CHK cumulative total of "1" in the record for the previous month (the work attendance closing date is "2023 / 2 / 28") with the employee code "100002", as well as the weekly work prediction of "21.6" and the payment performance prediction of "93,000 yen" in the first closing data 106f for the current month (see Figure 15).

[0073] The alert determination unit 102d refers to the alert determination master 106d and stores "Warning 3" in the "Social Insurance Alert" and "Employment Insurance Alert" of the first summary data 106f because it meets the conditions of the alert type "Warning 3" (threshold value 1 "1", threshold value 2 (predicted payment amount) "80,000 to 999,999" or threshold value 2 (weekly working hours) "16 to 999") (see FIGS. 14 and 15).

[0074] The person in charge etc. designates the employee code "100002" and the closing month and year "2023 / 3" and instructs to display the alert display screen MA.

[0075] Then, the alert determination unit 102d displays the alert display screen MA and displays "2023 / 3" in the closing month and year in the area MA1 of the alert display screen MA and "100002" in the employee code in the area MA2 (see FIG. 16).

[0076] The alert determination unit 102d refers to the closing date master 106c, obtains the period start date "2023 / 3 / 1" and the attendance closing date "2023 / 3 / 31" corresponding to the closing month and year "2023 / 3", refers to the first daily summary data 106e, and obtains the "working days", the "scheduled working hours" and the "actual working hours" corresponding to the working days from the period start date "2023 / 3 / 1" to the attendance closing date "2023 / 3 / 31", and displays them in the "working days" in the area MA31 of the alert display screen MA, the "scheduled working hours" in the area MA32 and the "actual working hours" in the area MA33 (see FIG. 16).

[0077] The alert determination unit 102d refers to the first summary data 106f, obtains the record of the obtained attendance closing date "2023 / 3 / 31", and displays the total labor prediction "93 hours" in the area MA41 of the alert display screen MA, the social insurance alert "Warning 3" in the area MA42 and the employment insurance alert "Warning 3" in the area MA43 (see FIG. 16).

[0078] (Calculation of annual income prediction from work shift and attendance record) Taking the employee code "100001" and the closing month and year "2023 / 11" as an example for explanation.

[0079] The work registration department 102c refers to the closing date master 106c and obtains the period start date "2023 / 11 / 1", the attendance closing date "2023 / 11 / 30", the salary payment month "2023 / 12", and the initialization flag "0" associated with the closing year and month "2023 / 11" (see Figure 11).

[0080] The work registration department 102c stores the employee code "100001", the obtained attendance closing date "2023 / 11 / 30", and the salary payment month "2023 / 12" in the second closing summary data 106h (see Figure 18).

[0081] The work registration department 102c refers to the second daily summary data 106g. Among the period from the period start date "2023 / 11 / 1" to the attendance closing date "2023 / 11 / 30" of the employee code "100001", for "2023 / 11 / 1" and "2023 / 11 / 2", since the actual values are entered in the "predicted payment amount (actual)", the actual values are used. For the period from "2023 / 11 / 3" to "2023 / 11 / 30", the values of the "predicted payment amount (planned)" are aggregated, and "90,000 yen" is stored in the "predicted payment amount" of the second closing summary data 106h (see Figures 17 and 18).

[0082] Since the obtained initialization flag is "0", the work registration department 102c aggregates the predicted payment amount values from the salary payment month "2023 / 1" to the predicted payment amount values of the previous month (salary payment month "2023 / 11"), and stores the aggregated value "965,000 yen" in the "cumulative previous year's annual income" of the second closing summary data 106h (see Figure 18). Note that for the record of the employee code "100001" and the salary payment month "2023 / 1" in the second closing summary data 106h in Figure 18, since the initialization flag of the closing date master 106c is "1", "0" (initialization process) is stored in the item "cumulative previous year's annual income" (see Figure 18).

[0083] The work registration department 102c stores "1,055,000 yen", which is calculated by adding the predicted payment amount "90,000 yen" for the current month (salary payment month "2023 / 12") of the second closing summary data 106h to the cumulative previous year's annual income "965,000 yen" of the second closing summary data 106h (see Figure 18).

[0084] The work registration department 102c generates the second summary data 106h by the above processing (see Fig. 18).

[0085] The person in charge designates the employee code "100001" and the closing month and year "2023 / 11", and instructs to display the cumulative annual income display screen MB.

[0086] Then, the work registration department 102c displays the cumulative annual income display screen MB, and displays "2023 / 11" in the closing month and year in area MB1 and "100001" in the employee code in area MB2 (see Fig. 19).

[0087] The work registration department 102c refers to the closing date master 106c and obtains the period start date "2023 / 11 / 1" corresponding to the closing month and year "2023 / 11" and the attendance closing date "2023 / 11 / 30" (see Fig. 11).

[0088] The work registration department 102c refers to the second daily summary data 106g, obtains the "working days" from the period start date "2023 / 11 / 1" to the attendance closing date "2023 / 11 / 30", the "scheduled working hours" and "actual working hours" corresponding to the working days, and displays them in the "working days" in area MB31, the "scheduled working hours" in area MB32, and the "actual working hours" in area MB33 of the cumulative annual income display screen MB (see Figs. 17 and 19).

[0089] The work registration department 102c refers to the second summary data 106h, obtains the predicted payment amount "90,000 yen" corresponding to the attendance closing date "2023 / 11 / 30", the cumulative annual income of the previous month-end "965,000 yen", and the cumulative annual income of the current month-end "1,055,000 yen", and displays the predicted payment amount "90,000 yen" in area MB41, the cumulative annual income of the previous month-end "965,000 yen" in area MB42, and the cumulative annual income of the current month-end "1,055,000 yen" in area MB43 of the cumulative annual income display screen MB (see Figs. 18 and 19).

[0090] (Effects of the Embodiment) It is common to use the payroll calculation results for checking the loss of social insurance enrollment, etc. For companies that employ many part-time workers, it was necessary to extract the target persons and conduct procedures within a short period after the payroll calculation.

[0091] With the alert display screen, it has become possible to discover target part-time workers at an early stage by utilizing work information for checking the loss of social insurance enrollment, etc. For companies, it helps prevent omission of social insurance enrollment procedures, and for workers, it makes it easier to make work schedules while being aware of the so-called "annual income threshold." Also, without relying solely on the payroll calculation results, it is possible to confirm the relevant persons from work schedules / actual performance, and preparations for social insurance enrollment procedures can be carried out at an early stage. It becomes possible to adjust the shift arrangement so that it does not become a non-social insurance enrollment target at the stage of making the shift.

[0092] With the cumulative annual income display screen, it is possible to predict the annual income using attendance information and send an alert notification on the work schedule, enabling the creation of work shifts while being aware of the annual income threshold.

[0093] Especially in the food service industry and the multi-store operation business format, since part-time workers account for most of the store operations, there may be a situation where the shift cannot be arranged due to the annual income threshold, which may disrupt the store operations. However, the person in charge, etc., can actually check the work status of part-time workers on the alert display screen and the cumulative annual income display screen, and create work shifts considering the busy periods of the store side, etc.

[0094] [4. Contribution to the Sustainable Development Goals (SDGs) Led by the United Nations] According to this embodiment, it can contribute to improving business efficiency and promoting appropriate business judgment of the company, so it can contribute to Goals 8 and 9 of the SDGs.

[0095] Also, according to this embodiment, it can contribute to reducing waste loss and promoting paperless and digitalization, so it can contribute to Goals 12, 13, and 15 of the SDGs.

[0096] In addition, according to this embodiment, since it can contribute to strengthening control and governance, it becomes possible to contribute to Goal 16 of the SDGs.

[0097] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0098] For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all or part of the processes described as being manually performed can be automatically performed by a known method.

[0099] In addition, regarding the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and the drawings, they can be arbitrarily changed unless otherwise specified.

[0100] Regarding the business support device 100, each of the illustrated components is a functional concept, and it is not necessarily physically configured as shown.

[0101] For example, regarding the processing functions provided by the business support device 100, particularly each processing function performed by the control unit, all or any part of them may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the business support device 100 as necessary. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes the control unit in cooperation with the CPU.

[0102] Further, this computer program may be stored in an application program server connected to the business support device 100 via an arbitrary network, and all or part of it can be downloaded as necessary.

[0103] Also, the program for executing the processing described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0104] Also, a "program" is a data processing method described in any language or description method, regardless of the form such as source code or binary code. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributedly configured as a plurality of modules or libraries, or those that achieve their functions in cooperation with separate programs typified by an OS. Note that for the specific configuration, reading procedure, and installation procedure after reading for reading a recording medium in each device shown in the embodiments, well-known configurations and procedures can be used.

[0105] The various databases and the like stored in the storage unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0106] Also, the business support device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Also, the business support device 100 may be realized by installing software (including programs or data, etc.) that realizes the processes described in this embodiment in the device.

[0107] Furthermore, the specific form of the distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or according to the function load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0108] The present invention is useful in enterprises that employ part-time workers.

Explanation of Symbols

[0109] 100 Business Support Device 102 Control Unit 102a Employee Information Registration Unit 102b Closing Date Master Setting Unit 102c Work Registration Unit 102d Alert Judgment Unit 104 Communication Interface Unit 106 Storage Unit 106a Requirement Master 106b Employee Master 106c Closing Date Master 106d Alert Judgment Master 106e First Day Total Data 106f First Closing Total Data 106g Second Day Total Data 106h Second Closing Total Data 108 Input / Output Interface Unit 112 Input Device 114 Output Device 200 Server 300 Network

Claims

1. An extraction unit that extracts the corresponding cumulative number of times that meets the eligibility requirements by referring to first data that manages whether an employee's working hours, payment amount, social insurance and employment insurance eligibility requirements and loss requirements are met; An alert determination unit that determines the alert based on the corresponding cumulative number of times extracted by the extraction unit by referring to an alert master that manages alerts according to the corresponding cumulative number of times that meets the social insurance and employment insurance eligibility requirements; A first data generation unit that stores the determination result of the alert determination unit in the first data and generates the first data; A display control unit that displays the alert stored in the first data on a work status confirmation screen for checking the work status of an employee; A labor management device characterized by comprising the above.

2. An acquisition unit that acquires the cumulative payment amount at the end of the previous month, which is the cumulative payment amount up to the end of the previous month corresponding to a predetermined year and month, and the cumulative payment amount at the end of the current month, which is the cumulative payment amount up to the end of the predetermined month, by referring to second data that manages the cumulative payment amount of an employee; The labor management device according to claim 1, wherein the display control unit displays the cumulative payment amount at the end of the previous month and the cumulative payment amount at the end of the current month acquired by the acquisition unit on the work status confirmation screen.

3. The extraction unit further extracts the payment amount and the working hours in the first data; The alert master stores the alert according to the payment amount or the working hours in addition to the corresponding cumulative number of times; The labor management device according to claim 1, wherein the alert determination unit refers to the alert master and determines the alert based on the corresponding cumulative number of times, the payment amount, and the working hours extracted by the extraction unit.

4. The working hours in the first data are the total of the actual working hours actually worked, and when the actual working hours are not registered, the total of the planned working hours, which are the planned working hours. The payment amount in the first data and the second data is the total of the actual payment amount, and when the actual payment amount is not registered, the total of the planned payment amount, which is the planned payment amount. The labor management device according to claim 2, characterized in that.

5. An extraction step in which an extraction unit extracts the corresponding cumulative number of times that meets the eligibility requirements by referring to first data that manages whether an employee's working hours, payment amount, social insurance and employment insurance eligibility requirements and loss requirements are met; An alert determination step in which an alert determination unit refers to an alert master that manages alerts according to the corresponding cumulative number of times that meet the requirements for social insurance and employment insurance, and determines the alert based on the corresponding cumulative number of times extracted by the extraction unit; A first data generation step in which a first data generation unit stores the determination result of the alert determination unit in first data and generates the first data; A display control step in which a display control unit displays the alert stored in the first data on a work status confirmation screen for checking the work status of employees; A labor management method having the above steps.

6. A computer, An extraction unit that refers to first data for managing an employee's working hours, payment amount, and whether they meet the requirements and loss requirements for social insurance and employment insurance, and extracts the corresponding cumulative number of times that meet the requirements; An alert determination unit that refers to an alert master that manages alerts according to the corresponding cumulative number of times that meet the requirements for social insurance and employment insurance, and determines the alert based on the corresponding cumulative number of times extracted by the extraction unit; A first data generation unit that stores the determination result of the alert determination unit in first data and generates the first data; A display control unit that displays the alert stored in the first data on a work status confirmation screen for checking the work status of employees; A labor management program for causing the computer to function as described above.

Images