JP7121362B2 - Business management support system, business management support method, and business management support program - Google Patents

Description

The present invention relates to a business management support system, a business management support method, and a business management support program.

As a system to support business management, a company has a human resources management system that manages employee schedules, work performance, personnel expenses, etc., a salary system that manages employee salaries, an accounting system that manages corporate accounting, an employee There are various computer management systems such as an employment system that manages the attendance of employees. In the accounting department of a company, data on management from various viewpoints are required from managers, financial managers, department heads, and the like. For example, a manager may request production and sales data related to production and sales management, such as sales and production volume, for each segment, such as the type of business, location of business establishment, and region. Further, for example, the person in charge of finance may request the total amount of personnel expenses and forecast data of personnel expenses. Persons in charge such as the accounting department process data from multiple support systems to create data that meets requests from various departments.

Further, Patent Literature 1 describes a labor cost simulation system for predicting future labor cost data.

Japanese Patent No. 5917785

Although the labor cost simulation system of Patent Document 1 can predict future labor costs, it does not suggest the idea of associating labor cost data with production and sales data. In the field of business management, the relationship between sales, production, and personnel costs is an important factor in business management. .

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems. It is to provide a method and a business management support program.

A business management support system that solves the above problems comprises a storage unit that stores labor cost data related to labor costs for each employee and production and sales data related to production and sales management; and an aggregating unit for aggregating the labor cost data and the production and sales data. The personnel cost data includes first personnel cost data in a first period that serves as a reference on the time axis of personnel costs, and a second period that is data calculated based on the first personnel cost data and that is different from the first period. and second labor cost data in . Then, the aggregating unit is based on at least one personnel cost data of the production and sales data, the first personnel cost data and the second personnel cost data, according to the conditions of the segment element and the aggregating period. Outputs labor cost summary data.

According to the above configuration, since personnel expenses and production/sales management data for a predetermined period are output in one form, it is possible to easily grasp the relationship between the total personnel expenses data and the production/sales data.

In the business management support system described above, it is preferable that the personnel expense data is associated with an item code indicating a sorted item in accounting with a detailed item of salary.
According to the above configuration, since the personnel expense data is associated with the item code, it is possible to easily tabulate the personnel expenses by accounting month.

In the business management support system described above, when the conditions of the segment elements are aggregated, it is preferable that the aggregation unit generates the personnel expense aggregation data by stored procedure processing.
According to the above configuration, desired data can be quickly calculated by stored procedure processing.

In the business management support system described above, it is preferable that the totalization unit calculates the labor cost data by adding expenses borne by the business owner to the total amount paid to the employee.
According to the above configuration, since the expenses borne by the business owner are added to the total amount paid to the employee, it can be calculated accurately.

In the business management support system described above, it is preferable that the first period is a period of one month, and the second period is a period of hours, days, or weeks.
According to the above configuration, by calculating daily personnel expenses from monthly data, it is possible to accurately calculate personnel expenses for a set period regardless of the length of the period. .

In the above business management support system, the storage unit further stores data relating to work schedules, and the totalizing unit calculates personnel expenses based on personnel cost data in accordance with the data relating to work schedules for periods of non-employment. Data are preferably calculated.
According to the above configuration, it is possible to accurately calculate personnel expenses according to employment performance and employment schedule.

Further, the present invention is a business management support method executed by the business management support system.
Furthermore, the present invention is a business management program used in a business management support system, and is executed by being installed in a computer such as a server device.

According to the above configuration, it is possible to easily grasp the relationship between labor cost data and production/sales data.

1 is a block diagram showing an outline of a system according to this embodiment; FIG. 4A and 4B are diagrams showing tables for managing work schedules stored in a work schedule storage unit; FIG. The figure which shows the table which manages the employment record stored in the employment record memory|storage part. The figure which shows the table which manages the salary payment performance stored in the salary payment performance memory|storage part. The figure explaining the function of a business management support system. A conceptual diagram for explaining a first personnel/salary organization that collects the same roles in managing and controlling a company, and a second employment organization that includes workplaces and working together. 4A and 4B are diagrams showing an example of management of departments of a first organization and workplaces of a second organization; FIG. (a) is a diagram for explaining conventional processing, and (b) is a diagram for explaining stored procedure processing. (a) is a diagram explaining the subject code of personnel expenses, (b) is a diagram summed up by department CD and subject CD, and (c) is a diagram summed up by a specific subject. FIG. 10 is a diagram for explaining a shift in periods when calculating labor costs; The figure explaining the calculation method of personnel expenses. The figure explaining the setting box of a vertical axis|shaft and a horizontal axis. FIG. 12A is a diagram showing a form output based on the settings in FIG. 12, where (a) is a list with sales, cost, personnel expenses, and expenses on the vertical axis and stores on the horizontal axis, and (b) is a graph.

An embodiment of a business management support system, a business management support method, and a business management support program will be described below with reference to FIGS. 1 to 13. FIG. In this embodiment, a business management support system will be described that allows managers and employees in various positions within a company to easily obtain labor cost data and production and sales cost data.

As shown in FIG. 1, a management server 10 used in the management support system is connected to a plurality of client terminals 2 via a network 1 . The client terminal 2 is a terminal managed by a manager, a terminal managed by a financial manager, or a terminal managed by a department head or an employee. These client terminals 2 are configured by hardware such as a CPU, ROM, RAM, and hard disk, and have an output section and an input section. The output unit is means for outputting various information, and is configured by a display, a printer, and the like. Also, the input unit is means for inputting various information, and includes a keyboard, a pointing device, a communication interface, and the like. The client terminal 2 is an information processing device such as a desktop or notebook computer terminal, a smartphone terminal, or the like, which can display various data on a monitor or print and check the data with a printer.

Also, the management server 10 is connected to another system 3 via the network 1 . The other system 3 is a personnel management system that manages schedules, work records, personnel expenses, etc. of managers and employees, and a labor cost management system that manages personnel expenses in detailed units such as department units. Other systems 3 include a business electronic approval system for managing expenses such as travel expenses and accommodation expenses for business trips, an accounting system for managing accounting, and the like. Various data accumulated in the other systems 3 are taken into the database of the management server 10 in a format such as CSV (Comma-Separated Values) as needed or periodically. This importing process may be performed according to an operation, or may be automatically performed according to a program.

The management server 10 to which the devices as described above are connected via the network 1 is a normal server, and is a computer system composed of hardware such as a CPU, ROM, RAM, and hard disk. The management server 10 is an integrated database that integrates and collectively manages human resources management data such as input schedules, work records, personnel expenses, labor cost data such as department units, expense data, and accounting data. Yes, and as an example, it consists of a relational database.

Specifically, the management server 10 includes a storage unit 11 , an input unit 12 , an output unit 13 and an aggregation unit 14 . The storage unit 11 is composed of a large-capacity hard disk or the like, and the above-described database is constructed. The input unit 12 is an input device such as a keyboard and a mouse, and is an input interface for data supplied from another system 3 or other equipment such as a time recorder. It is also an input interface to which a portable recording medium such as an optical disk, USB memory, or memory card is connected and data is input. The output unit 13 is an interface that outputs data to a display unit or the like, and is a communication interface that transmits data to the client terminal 2 . Also, the output unit 13 outputs data to a portable recording medium. Aggregation unit 14 aggregates the data in the database according to the segment element and aggregation period conditions. The management server 10 outputs the aggregated data aggregated by the aggregation unit 14 from the output unit 13 and displays it on a printer, a display unit of the client terminal 2, or the like.

The storage unit 11 includes a work schedule storage unit 21, a work performance storage unit 22, a salary payment storage unit 23, a bonus payment storage unit 24, an expense storage unit 25, a production and sales management storage unit 26, an accounting A storage unit 27 and a non-accounting storage unit 28 are provided.

FIG. 2( a ) shows an example of a table for managing work schedules stored in the work schedule storage unit 21 . The work schedule management table 21a manages an employee's personal schedule on a daily basis. Specifically, the work schedule management table 21a includes a company CD that uniquely identifies a company, an individual ID that uniquely identifies an individual such as an employee, a date, and a workplace to which the employee belongs in the company organization. , a workplace name indicated by the workplace CD, a shift CD that is a code indicating a work shift, a start time to start work, an end time to end work, and working hours. . Note that the start time, end time, and working hours are managed in minutes. The end item "1080" indicates "18:00". Also, "-1" indicates no attendance. Also, in the duty CD, "1" indicates normal duty, and "2" indicates holiday.

FIG. 2(b) shows the work schedule management table 21b by project stored in the work schedule storage unit 21. As shown in FIG. The work schedule management table by project 21b manages how much time an employee allocates to which project during working hours. It stores the work CD1 that uniquely identifies the work, working hours, and overtime hours.

The work schedule storage unit 21 may store a monthly work schedule management table and a project-based work schedule management table 21b. When creating the monthly work schedule management table and the project-based work schedule management table 21b, they can be created by totalizing the daily work schedule management table and the project-based work schedule management table 21b.
In addition, the work schedule management table 21a and the work schedule management table by project 21b may also store break time, vacation time, extra time, and the like.

FIG. 3 shows an example of a table for managing work records stored in the work record storage unit 22. As shown in FIG. The work record management table 22a manages individual work records of employees on a monthly basis. Specifically, the employment record management table 22a includes company CD, personal ID, date, workplace CD, and workplace name, as well as monthly working hours, monthly working days, and paid usage. stored. The work record storage unit 22 stores a daily work record management table corresponding to the work schedule management table 21a shown in FIG. , may also store the work record management table by project. The daily work performance management table and the project-based work performance management table can be generated by disassembling the monthly work performance management table and the project-based work performance management table. In addition, the various tables stored in the work record storage unit 22 may also store time to go out early and early, the number of remaining paid holidays, the number of lunch boxes ordered, the amount of money, and the like.

FIG. 4 shows an example of a table for managing salary payment performance stored in the salary payment performance storage unit 23. As shown in FIG. The salary payment record management table 23a manages the salary payment record of employees on a monthly basis. Specifically, the salary payment record management table 23a includes company CD, personal ID, date, workplace CD, and workplace name, as well as item CD, which is an item of salary, and amount corresponding to item CD. , and attendance items corresponding to item CD are stored. As for the attendance item, when the item CD indicates the basic salary, the number of working days is stored; when the item CD indicates the overtime allowance, the overtime hours are stored; when the item CD indicates the number of working days, the number of days is stored. In addition, deduction items, insurance premiums, transportation expenses, and the like may be stored in the salary payment record management table 23a. The salary payment record storage unit 23 may store a table for managing the employee's salary payment record on a daily basis. The daily wage payment record management table can manage daily labor costs based on the daily work record specified by the work record management table 22a. In addition, regarding unpaid salaries, labor costs can be calculated and predicted based on the daily work schedule specified by the work schedule management table 21a. For example, employee salary data on a monthly basis is the first personnel cost data, and hourly or daily salary data with finer granularity is the second personnel cost data.
Note that the bonus payment record storage unit 24 also stores a bonus payment record management table having almost the same items as the salary payment record management table 23a.
This salary payment record management table 23a is associated with an item code indicating an item for sorting in accounting, as will be described later.

The expense storage unit 25 stores a table for managing expenses such as travel expenses and accommodation expenses for business trips. The expense management table is a table for each day, and each item code such as transportation expenses and accommodation expenses during a business trip is given. The expense storage unit 25 may store a monthly expense management table. The monthly expense management table can be calculated by aggregating the daily expense management table.

The production/sales management storage unit 26 stores a table for managing production numbers and sales numbers for each factory and store. The production management table for managing production and sales is a daily table, and a code is assigned to each item. The production management table manages, for example, production numbers, sales numbers, production targets, sales targets (number, price, etc.). In addition, the production management table may manage raw material costs for purchasing and manufacturing, advertising costs, land rent, and the like. The production/sales management storage unit 26 may store a monthly production management table. The monthly production control table can be calculated by aggregating the daily production control table. The number of production and the number of sales may be managed for each individual employee.

The accounting storage unit 27 stores an accounting table for managing accounting data. Accounting data includes annual and monthly sales, cost of sales, selling, general and administrative expenses, and various financial data related to financial statements such as non-operating income.Accounting data including these data is stored. be done.

Data arbitrarily set by the user is input to the non-accounting storage unit 28 . For example, various data such as rental housing costs, employee training costs, and the number of calls received at the service center are stored.

FIG. 5 is a diagram showing functions of the management server 10. As shown in FIG.
Part (1) in FIG. 5 indicates that the employee's personal schedule is managed in units of days in the work schedule management table 21a in the work schedule storage unit 21. FIG. Part (2) in FIG. 5 indicates that the employee's personal schedule is managed on a daily basis in the project-by-project work schedule management table 21b in the work schedule storage unit 21. FIG.

The tabulation unit 14 tabulates working hours, scheduled overtime hours, etc. for a given accounting month (from the beginning to the end of the month) according to the data recorded in the work schedule management table 21a and the work schedule management table by project 21b. store in In addition, the working hours, overtime hours, etc. for a month or a plurality of months from the day after the closing date of the previous month in terms of accounting to the closing date of the current month are totaled and stored in the work schedule storage unit 21 . These data can be used when calculating personnel expenses for the future. It can also be used to understand how much time employees spend on which projects. In addition, the aggregation unit 14 can also decompose the day-based work schedule management table 21a or the project-based work schedule management table 21b into time units.

Regarding the work schedule, the aggregating unit 14 performs a query 15 for aggregating the monthly working hours from the day after the accounting closing date of the previous month to the accounting closing date of the current month, the scheduled overtime hours, etc. for each workplace, the daily working hours, the scheduled overtime hours, etc. etc., and a query 15 for aggregating hourly working hours, scheduled overtime hours, and the like. The query 15 saves the aggregated data in the work schedule storage unit 21 .

The part (3) in FIG. 5 indicates that the personal schedule of the employee is managed on a day-by-day basis in the work record management table 22a in the work record storage unit 22. FIG. Part (4) in FIG. 5 indicates that the work record of the employee is managed in units of days in the work record management table 21b by project in the work record storage unit 22. FIG.

Aggregating unit 14 aggregates working hours, overtime hours, etc. for a given accounting month (from the beginning to the end of the month) according to the record data of work record management table 22a and work schedule management table by project 21b, and stores them in work record storage unit 22. Store. In addition, the working hours, overtime hours, etc. for a month or a plurality of months from the day after the closing date of the previous month in terms of accounting to the closing date of the current month are totaled and stored in the work record storage unit 22 . These data can be used when calculating past labor costs and the like. It can also be used to understand how much time an employee has spent on which project. Note that the aggregation unit 14 can also decompose the daily work record management table 22a or the project-specific work record management table into time units.

Regarding the actual work performance, the aggregating unit 14 performs a query 16 for aggregating monthly working hours, overtime hours, etc. from the day after the closing date of the previous month in terms of accounting to the closing date of the current month for each workplace, and a query 16 for aggregating daily working hours, overtime hours, etc. A query 16 for totaling, a query 16 for totaling working hours, overtime hours, etc. for a given accounting month (from the beginning to the end of the month), a query 16 for totaling working hours, overtime hours, etc. for multiple months in accounting, etc. . In addition, for each project, a query 16 is provided for aggregating working hours, overtime hours, etc. according to the day or accounting month for each project in the company or the entire group company. In addition, the personal attribute includes a query 16 for totaling hourly working hours, overtime hours, and the like. The query 16 saves the aggregated data in the work record storage unit 22 .

Part (5) in FIG. 5 indicates that the salary payment record of the employee is managed on a monthly basis in the salary payment record management table 23a in the salary payment record storage unit 23. FIG. The counting unit 14 calculates daily salary data according to the data recorded in the salary payment record management table 23a, and aggregates the daily salary data to obtain the salary data for a predetermined accounting month (from the beginning to the end of the month). calculate. In addition, according to the data recorded in the salary payment record management table 23a, the data is broken down into hourly salary data.

Part (6) in FIG. 5 indicates that the bonus payment record of the employee over a plurality of months is managed on a monthly basis in the bonus payment record management table in the bonus payment record storage unit 24 . The tabulation unit 14 decomposes the data into salary data for a predetermined accounting month (from the beginning to the end of the month) and bonus data on a daily or hourly basis according to the recorded data in the bonus payment record management table.

Regarding salaries and bonuses, the tallying unit 14 has a query 17 for tallying monthly salaries and bonuses for each workplace from the day after the accounting closing date of the previous month to the accounting closing date of the current month. It also has a query 17 for aggregating salaries and bonuses for the entire company and group companies. The query 17 stores the aggregated data in the salary payment record storage unit 23 and the bonus payment record storage unit 24 .

The part (7) in FIG. 5 indicates that the production/sales management storage unit 26 manages daily production numbers and sales numbers in the production management table. Aggregating unit 14 aggregates production and sales data for a given accounting month (from the beginning of the month to the end of the month) according to the data recorded in the production management table, and stores the data in production and sales management storage unit 26 . In addition, monthly production and sales data from the day after the accounting closing date of the previous month to the accounting closing date of the current month are aggregated and stored in the production and sales management storage unit 26 . Furthermore, production and sales data for a plurality of months in terms of accounting are aggregated and stored in the production and sales management storage unit 26 . In addition, the production/sales data and the like are aggregated by accounting hours, days, and accounting months, and stored in the production/sales management storage unit 26 .

The portion (8) in FIG. 5 indicates that the expense storage unit 25 manages daily expense data in the expense management table. The tabulation unit 14 tabulates the expense data for a given accounting month (from the beginning to the end of the month) according to the data recorded in the expense management table, and stores the data in the expense storage unit 25 . The tallying unit 14 has a query 18 for tallying expenses for a predetermined accounting month (from the beginning of the month to the end of the month) for each individual. . It also has a query 18 for aggregating expenses for the entire company or group companies. The query 18 saves the aggregated data in the expense storage unit 25 .

Queries 15, 16, 17, and 18 as described above can be quickly processed by stored procedure processing, for example. It should be noted that other queries may be provided.

By the way, as shown in FIG. 6, a company consists of a first personnel/salary organization 41 that collects the same roles in management and control of the company, and a first organization 41 in terms of work place and cooperation in working together. There are two organizations 42 . The former first organization 41 is, for example, an organization such as a service department, marketing department, development department, management department, and sales department, and the latter second organization 42 is, for example, workplaces and stores located all over the country. Employees often work in a second organization 42 while belonging to a first organization 41 . In corporate accounting, financial statements such as PL are created according to the first organization 41 . Financial statements such as PL for each store can be created by executing the above-described query, for example.

For example, as shown in FIG. 7A, the departments of the first organization 41 and the workplaces of the second organization 42 are managed by department code (1) and internal hierarchy code (2). For example, for "nationwide", the department code (1) is "ALL01" and the internal hierarchy code (2) is "001 000 000 000". In the lower middle part, the department code (1) is "CH01" and the internal layer code (2) is "001 001 000 000". In Kanto, the department code (1) is "KT09" and the internal layer code (2) is "001 002 000 000". Aichi in the lower layer of the central part has the department code (1) of "AI01" and the internal layer code (2) of "001 001 001 000". The lower level Sakae store in Aichi has a department code (1) of "SKE001" and an internal layer code (2) of "001 001 001 001".

Further, as shown in FIG. 7(b), in the employee salary payment record management table 23a, only the department code (1) is stored in the workplace CD. In such a case, for example, if you want to know the labor cost of Chubu "CH01", you have conventionally done as follows. That is, as shown in FIG. 8A, the client terminal 2 requests a department list associated with "CH01" (step S1). Specifically, the first and second layers of the internal layer code (2) of the middle part "CH01" are "001 001", and the first and second layers of the internal layer code (2) are is "001 001" (step S2). After that, the labor cost is requested for each acquired department code (1) (step S3), and the result is acquired (step S4).

On the other hand, as shown in FIG. 8(b), according to the stored procedure processing, the central part "CH01" labor cost is requested (step S11), and then the central part "CH01" personnel cost is obtained. (step S12). As a result, the process can be performed in two steps, and work efficiency can be improved.

By the way, the salary payment record management table 23a stores, for each employee, an item code which is an item of salary and indicates an item for sorting in accounting. Specifically, as shown in FIG. 9(a), in the salary payment record management table 23a, an item code that associates each item CD with accounting information is inserted into each employee's pay statement data. For example, the item CD "basic salary" is associated with the subject code "BASE", and the item CD "overtime pay" is associated with the subject code "OVERTIME". As a result, for example, as shown in FIG. 9B, the tallying unit 14 can tally the department CD and the subject CD in cooperation with accounting. In addition, as shown in FIG. 9C, it is possible to link with accounting and output for a specific subject.

By the way, there are cases where the accounting month is handled from the beginning to the end of the month, and cases where it is handled according to the accounting closing date. As shown in FIG. 10, for example, from an accounting point of view, the working period in March is from February 16th to March 15th, and April is from March 16th to April 15th. On the other hand, March in the accounting period is from 3/1 to 3/31. For example, between March 16th and April 15th, when trying to figure out the personnel expenses for March in accounting, wages from March 1st to March 15th have already been paid, but from March 16th Wages until 3/31 are unpaid. Between 3/16 and 3/31, there are working periods and non-working periods. In this state, the wages already paid from 3/1 to 3/15 access the work record management table 22a and calculate the wages according to the work record from 3/1 to 3/15. The unpaid period for which work has been completed after 3/16 is also calculated in the same manner. As for the wages for the non-working period, the work schedule management table 21a is accessed to calculate the wages according to the work schedule from 3/16 to 3/31. As a result, it is possible to accurately calculate the personnel expenses according to the employment record and the employment schedule.

FIG. 11 is a diagram for explaining a specific method of calculating an accurate daily labor cost. As shown in (a), in the case of paid leave, the labor cost per day is the amount obtained by multiplying the prescribed working hours by the individual hourly wage. Further, as shown in (b), in the case of working on weekdays, the amount obtained by multiplying the total working hours per day by the individual hourly wage unit price is the labor cost per day. Furthermore, as shown in (c), in the case of working on a holiday, the amount obtained by multiplying the overtime hours by the individual hourly wage rate and the premium rate is the labor cost per day. Furthermore, as shown in (d), the daily allowance is the daily payment amount. Labor costs per day are from (a) to (d), but here, as shown in (e) and (f), social insurance costs (health insurance, welfare pension and fund, long-term care insurance, child Child care contribution, industrial accident insurance, employment insurance, etc.) are added, and transportation expenses (gasoline charges, commuter charges) are added as shown in (g) and (h). Furthermore, as shown in (i), (j) and (k), allowances (bonuses, retirement allowances, etc.), executive compensation (executive compensation, directors' training costs), etc. Whether to calculate accurate personnel expenses on a daily basis based on work performance or on a daily basis based on work schedule, the above method is used. By doing so, it is possible to accurately calculate the labor cost per day.

Next, a case where the client terminal 2 accesses the management server 10 and performs profit analysis will be described with reference to FIG. The setting screen displayed on the client terminal 2 includes a period setting box 30 for setting the aggregation time axis as a segment, a vertical axis setting box 31 for setting the vertical axis as the segment, and a horizontal axis setting box 31 for setting the horizontal axis as the segment. An axis setting box 32 is displayed on the setting screen. In the vertical axis setting box 31, it is possible to set, for example, production sales management data such as sales and costs, and scheduled working hours and working hours as employment data. In addition, non-accounting data (various types of data such as rented housing costs, employee training costs, and the number of calls received at service centers) can be set. In the vertical axis setting box 31, a preset standard table can be selected, and "Profit analysis 1" is set here. In the horizontal axis setting box 32, it is possible to set the area and store for the organization. A store is the smallest unit. In addition, regarding products, it is possible to set types, items, and products. A product is the smallest unit.

"Profit analysis 1" set in the vertical axis setting box 31 automatically displays sales (sales budget, actual sales), costs (actual costs), and labor costs (total working hours, actual labor costs) on the vertical axis. ), and expenses (actual expenses) are selected. Sales budget, actual sales, actual costs, actual personnel expenses, and actual expenses are taken out from the salary payment performance management table 23a, bonus payment performance management table, production management table, expense management table, and accounting table. Also, the total working hours are taken out from the working schedule management table 21a and the working performance management table 22a. The fixed form of the vertical axis setting box 31 is prepared in addition to "profit analysis 1", and can be selected.

When the data is aggregated according to the settings in the period setting box 30, the vertical axis setting box 31, and the horizontal axis setting box 32, as shown in FIG. , expenses and stores on the horizontal axis (see FIG. 13(a)) and graphs (see FIG. 13(b)) are displayed and printed.

According to the business management support system, the following effects can be obtained.
(1) As shown in the examples of FIGS. 12 and 13, labor costs and production/sales management data for a store during a predetermined period are output in one form, so that the relationship between total labor costs data and production/sales data can be checked. can be easily grasped.

(2) In the examples of FIGS. 12 and 13, the aggregation time axis is set from 2014.03.01 to 2014.03.31 in terms of accounting. This set period is different from the period of 2/16 to 3/15 in March of the work period. The counting unit 14 accurately calculates the exact personnel expenses for each day according to the personnel expenses calculation method based on FIG. be able to.

(3) For personnel expenses, item codes are associated with item CD. Therefore, in conjunction with accounting, it is possible to output specific items in salary.
(4) Desired data regarding labor costs for each store can be quickly calculated by stored procedure processing.

(5) Personnel cost data can be made accurate because it is calculated by adding the expenses borne by the employer to the total amount paid to the employees.
(6) By calculating daily labor costs from monthly salary data, it is possible to accurately calculate labor costs for a set period regardless of the length of the period.
(7) It is possible to accurately calculate personnel expenses according to employment records and employment schedules.

Note that the business management support system described above can also be implemented with appropriate modifications as follows.
As for labor cost data, in addition to generating hourly data from monthly data, weekly data or yearly data may be generated from monthly data. These data can be queried and computed with stored procedure processing. Further, the calculated data may be stored in the storage unit. As a result, it is possible to omit the process of calculating the data next time, and to that extent it is possible to quickly calculate the desired data.

・In calculating accurate personnel expenses per day, it is not necessary to consider all of social insurance expenses, transportation expenses, allowances, executive compensation, and educational expenses, and any one or more of these There may be, and costs may include costs other than those listed here.
・Not all queries need to be stored procedure processing.

・Actual salary payment on a daily basis, actual salary payment on an hourly basis, etc. may be automatically calculated from the actual salary payment on a monthly basis and stored in the salary payment performance storage unit 23. However, it may be calculated by executing a query according to the user's operation, and stored in the salary payment record storage unit 23 . By storing these data in the salary payment record storage unit 23, it is only necessary to read them from the next time, and the time required to obtain the desired data can be shortened. In addition, hourly labor cost data may be obtained and saved on a daily basis.

・The business management support system can support the business management of companies such as service industries such as restaurants and production industries.

DESCRIPTION OF SYMBOLS 1... Network 2... Client terminal 3... System 10... Management server 11... Storage part 12... Input part 13... Output part 14... Aggregation part 15... Query 16... Query 17... Query 18 Query 21 Work schedule storage unit 21a Work schedule management table 21b Work schedule management table by project 22 Work record storage unit 22a Work record management table 23 Salary payment record storage unit 23a Salary payment record management table 24 Bonus payment record storage unit 25 Expense storage unit 26 Production/sales management storage unit 27 Accounting storage unit 28 Non-accounting storage unit 30 Period setting box 31 Vertical axis setting box 32... Horizontal axis setting box 41... First structure 42... Second structure.

Claims (4)

a work schedule storage unit that stores data related to the work schedule of the employee;
a work record storage unit that stores data related to the work record of the employee;
a salary payment record storage unit that stores labor cost data related to labor costs for each employee;
a bonus payment record storage unit that stores data related to bonuses for each employee;
an expense storage unit that manages expense data;
a production and sales management storage unit that stores production and sales data related to production and sales management;
an accounting storage unit that stores accounting data;
a non-accounting storage unit that stores non-accounting data;
The employment schedule storage unit, the employment performance storage unit, the salary payment performance storage unit, the bonus payment performance storage unit, the expense storage unit, the production and sales management storage unit, the accounting storage unit, and the non-accounting storage unit an aggregating unit for aggregating the data stored in the aggregating unit for aggregating the labor cost data and the production and sales data according to the input segment element and aggregation period conditions;
In the personnel cost data, item codes indicating item classifications in accounting are associated with salary detail items, and the totaling unit calculates the total amount paid to employees, social security expenses, transportation expenses, Calculated by adding provision, executive remuneration, and educational expenses.
First personnel cost data in a first period that serves as a reference on the time axis of personnel costs, and second personnel cost data in a second period that is data calculated based on the first personnel cost data and is different from the first period. and
The aggregating unit outputs aggregated labor cost data based on the production and sales data, the first personnel cost data and the second personnel cost data , according to the conditions of the segment element and the aggregation period ,
For the non-employment period, the labor cost summary data is calculated based on the labor cost data according to the data on the work schedule.
Business management support system. The first period is a period of one month,
2. The business management support system according to claim 1 , wherein the second period is an hourly period, a daily period, or a weekly period. storing data relating to the employee's work schedule in a work schedule storage unit;
storing data relating to the employment record of the employee in the employment record storage unit;
storing labor cost data related to labor costs for each employee in a salary payment performance storage unit;
storing data relating to bonuses for each employee in a bonus payment record storage unit;
storing the expense data in the expense storage unit;
storing production and sales data related to production and sales management in the production and sales management storage unit;
storing the accounting data in the accounting storage unit;
storing non-accounting data in the non-accounting storage;
The work schedule storage unit, the work performance storage unit, the salary payment performance storage unit, the bonus payment performance storage unit, the expense storage unit, the production and sales management storage unit, the accounting storage unit, and the non-accounting storage unit. Aggregate the data stored in the accounting storage unit, and aggregate the labor cost data and the production and sales data according to the inputted segment element and aggregation period conditions,
In the personnel cost data, item codes indicating item classifications in accounting are associated with itemized items of salary, and the totalizing unit includes the total amount paid to employees, social security expenses, transportation expenses, Calculated by adding provision, executive remuneration, and educational expenses.
First personnel cost data in a first period that serves as a reference on the time axis of personnel costs, and second personnel cost data in a second period that is data calculated based on the first personnel cost data and is different from the first period. and
The aggregation unit outputs aggregated personnel cost data based on the production and sales data, the first personnel cost data and the second personnel cost data , according to the conditions of the segment element and the aggregation period ,
For the non-employment period, the labor cost summary data is calculated based on the labor cost data according to the data on the work schedule.
Business management support method. Business management support system,
a procedure for storing data relating to an employee's work schedule in a work schedule storage unit;
a procedure for storing data relating to the employment record of the employee in an employment record storage unit;
a procedure for storing personnel cost data related to the personnel cost for each employee in a salary payment performance storage unit;
a procedure for storing data relating to bonuses for each employee in a bonus payment record storage unit;
a procedure for storing expense data in an expense storage unit;
a procedure for storing production/sales data relating to production/sales management in a production/sales management storage unit;
a procedure for storing accounting data in an accounting storage unit;
a procedure for storing non-accounting data in the non-accounting storage;
The work schedule storage unit, the work performance storage unit, the salary payment performance storage unit, the bonus payment performance storage unit, the expense storage unit, the production and sales management storage unit, the accounting storage unit, and the non-accounting storage unit. Aggregating the data stored in the accounting storage unit and aggregating the labor cost data and the production and sales data according to the input segment element and aggregation period conditions;
In the personnel cost data, item codes indicating item classifications in accounting are associated with itemized items of salary, and the totalizing unit includes the total amount paid to employees, social security expenses, transportation expenses, Calculated by adding provision, executive remuneration, and educational expenses.
First personnel cost data in a first period that serves as a reference on the time axis of personnel costs, and second personnel cost data in a second period that is data calculated based on the first personnel cost data and is different from the first period. and
Further, the aggregation unit outputs aggregated labor cost data based on the production/sales data, the first labor cost data, and the second labor cost data , according to the conditions of the segment element and the aggregation period. and a business management support program for executing a procedure for calculating the labor cost summary data based on the labor cost data in accordance with the work schedule data for the non-employment period .

Images