Business support device, business support method, and business support program

Abstract

To facilitate reference of forms of related companies before and after transfer by a worker who has been transferred between the related companies constituting a group company.SOLUTION: A storage control section stores form data before and after transfer between related companies in each worker of each related company uploaded from a plurality of related companies constituting a group company in a reference area which is a storage area of a storage section accessible from the worker of each related company together with employee identification information unique to each worker used in each related company and company identification information unique to the related company to which each worker belongs. When receiving an output request for form data from a worker who has been transferred from a related company to another related company, an acquisition section acquires designated form data from the reference area among the form data before and after the transfer, which is associated with the employee identification information of the worker. An output control section controls the output of the acquired form data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a business support device, a business support method, and a business support program. [Background technology]

[0002] Patent Document 1 (JP 2007-122342 A) discloses a personnel information processing device. In this personnel information processing device, a shared basic personnel information input means stores input personnel information, including personnel information about employees employed at any one of the companies in a corporate group that adopts a group management system, related to individual attributes as shared basic personnel information in a shared basic personnel information database shared by some or all of the companies belonging to the corporate group. A company-specific personnel information input means stores, as company-specific personnel information, personnel information about employees related to company attributes in a company-specific personnel information database managed individually by some or all of the companies belonging to the corporate group.

[0003] This will enable the corporate group to make effective use of its human resources and streamline its administrative management. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-122342 Summary of the Invention [Problem to be solved by the invention]

[0005] Here, when there is a transfer between related companies that make up a group of companies, there is a problem in that it becomes difficult for workers to refer to document data such as pay slips from the related company before the transfer.

[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that make it easy for workers who have been transferred between related companies that make up a group of companies to refer to the documents of the related companies before and after the transfer. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the business support device of the present invention has a memory control unit that stores pre- and post-transfer report data for each worker of each related company uploaded from multiple related companies that make up a group of companies in a reference area, which is a memory area of ​​a memory unit that can be accessed by workers of each related company, along with each worker's unique employee identification information used at each related company and the unique company identification information of the related company to which each worker belongs; an acquisition unit that, when a worker who has been transferred from one related company to another requests the output of report data, acquires specified report data from the reference area from the pre- and post-transfer report data associated with the worker's employee identification information; and an output control unit that controls the output of the acquired report data.

[0008] In addition, in order to solve the above-mentioned problems and achieve the object, the business support method of the present invention includes a storage control step in which a memory control unit stores pre-transfer and post-transfer report data for each worker of each related company, which is uploaded from multiple related companies that make up a group of companies, in a reference area, which is a memory area of ​​the memory unit that can be accessed by workers of each related company, together with each worker's unique employee identification information used at each related company and the unique company identification information of the related company to which each worker belongs; an acquisition step in which an acquisition unit acquires specified report data from the reference area from the pre-transfer and post-transfer report data associated with the worker's employee identification information when a request to output report data is made by a worker who has been transferred from one related company to another related company; and an output control step in which an output control unit controls the output of the acquired report data.

[0009] In addition, in order to solve the above-mentioned problems and achieve the object, the business support program of the present invention causes a computer to function as a memory control unit that stores pre- and post-transfer report data for each worker of each related company uploaded from multiple related companies that make up a group of companies in a reference area, which is a memory area of ​​the memory unit that can be accessed by workers of each related company, along with each worker's unique employee identification information used at each related company and the unique company identification information of the related company to which each worker belongs; an acquisition unit that, when a worker who has been transferred from one related company to another requests the output of report data, acquires specified report data from the reference area from the pre- and post-transfer report data associated with the worker's employee identification information; and an output control unit that controls the output of the acquired report data. [Effects of the Invention]

[0010] The present invention makes it easy for workers who have been transferred between related companies that make up a group of companies to refer to the documents of the related companies before and after the transfer. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing the system configuration of a form reference system according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing the hardware configuration of a business support device provided in the form reference system according to the embodiment. [Figure 3] FIG. 3 is a diagram showing various master tables and various storage units provided in the business support device. [Figure 4] FIG. 4 is a diagram showing an example of an employee master table provided in the business support device. [Figure 5] FIG. 5 is a diagram illustrating an example of a form data storage unit provided in the business support device. [Figure 6] FIG. 6 is a diagram showing an example of a copy source / copy destination table provided in the task support device. [Figure 7]FIG. 7 is a diagram showing a form data copy screen for specifying form data to be uploaded to the business support device on the terminal device of the affiliated company side of the form reference system according to the embodiment. [Figure 8] FIG. 8 is a diagram showing an example of employee data that has been uploaded from a terminal device on the affiliated company side to the business support device and stored in the reference area of ​​the storage unit of the business support device. [Figure 9] FIG. 9 is a diagram showing an example of form data that is uploaded from a terminal device on the affiliated company side to the business support device and stored in a reference area of ​​the storage unit of the business support device. [Figure 10] FIG. 10 is a diagram showing an example of employee data of a logged-in user acquired from the reference area of ​​the storage unit of the business support device. [Figure 11] FIG. 11 is a diagram showing an example of form data of a logged-in user, which is acquired from the reference area of ​​the storage unit of the business support device based on the employee data of the logged-in user. [Figure 12] FIG. 12 is a diagram showing how the form data acquired from the reference area is displayed in a list on the worker's terminal device. [Figure 13] FIG. 13 is a diagram showing the flow up to the point where a job for displaying a list of form data of a user who has logged in to the business support device (a job for personal form inquiry) is determined. [Figure 14] FIG. 14 is a diagram showing the transition of the display screen until the form data of the user who has logged in to the business support device is displayed in a list. DETAILED DESCRIPTION OF THE INVENTION

[0012] A form reference system according to an embodiment of the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to the following embodiment.

[0013] (overview) In group companies that manage multiple corporations (affiliated companies), it is necessary to ensure the security of personal information by separating the accessible area for each affiliated company. For this reason, systems are generally built in a format that stores data in separate memory areas for each affiliated company. Human resources personnel at each affiliated company perform calculations such as monthly salaries, bonuses, social insurance, and year-end tax adjustments for employees employed at the affiliated companies they are responsible for.

[0014] Here, workers may be transferred between related companies within a group of companies due to transfers, company mergers or reorganizations, and the related company after the transfer may need documents such as pay slips from the related company before the transfer.

[0015] Although each affiliated company is part of the same corporate group, they are different companies and therefore often have different regulations and payroll items. This makes it difficult to transfer report data item by item between affiliated companies before and after a transfer. It also requires changing the system permission settings for transferred employees, which places a burden on human resources personnel or managers.

[0016] In addition, the services or systems of the affiliated company where the employee was employed before the transfer are often deemed unusable after the transfer, but documents such as withholding slips or pay slips from the previous affiliated company may be required by the affiliated company to which the employee is transferred. For this reason, it may be considered to keep the documents from the previous affiliated company in one's possession, but such personal management of documents is not recommended as it may lead to inconveniences such as loss.

[0017] For this reason, the form reference system of the embodiment consolidates and stores forms such as pay slips issued by each affiliated company in a dedicated area (reference area) for each specified period, such as each month. This allows each affiliated company to seamlessly transfer form data before and after a transfer to the dedicated area (reference area), reducing the tedious work of the person in charge at the affiliated company before the transfer having to provide form data from when the employee was employed at the affiliated company before the transfer every time a worker requests it.

[0018] In addition, workers can freely refer to their own document data before and after their transfer, which has been transferred to a dedicated area (reference area). This reduces the need for tedious tasks such as changing security settings for workers or systems.

[0019] (System Configuration) Fig. 1 is a diagram showing the system configuration of a form reference system according to an embodiment. As shown in Fig. 1, the form reference system according to the embodiment is configured by interconnecting a business support device 1, which is a terminal device of a form reference company that forms a group of companies, terminal devices 2 to 6 of companies A to E, and a terminal device 7 of an employee of each company, so that they can communicate with each other via a network 8. The network 8 may be, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0020] Terminal devices 2-6 of companies A to E store accounting data such as the salary, bonus, social insurance, and year-end tax adjustment of each worker. Each terminal device 2-6 of companies A to E uploads (copies) the accounting data to the reference area of ​​the business support device 1 via the network 8, for example, at a predetermined time every night or at predetermined intervals such as once a month.

[0021] The business support device 1 of the document reference company stores (copies) the document data uploaded from companies A to E in the reference area 20, which is a storage area common to all companies. As a result, even if a worker is transferred between related companies A to E, the document data of the worker before and after the transfer will be stored in the reference area 20.

[0022] This reference area 20 can be freely accessed by workers from companies A to E and the document reference company via the terminal device 7. Workers can obtain their own document data from the reference area 20. Therefore, even if a worker needs document data from the company where they were employed before the transfer after being transferred, the worker can obtain it from the reference area 20 and submit it to the company to which they have been transferred.

[0023] (Hardware configuration) FIG. 2 shows the hardware configuration of the business support device 1 of the document reference company. As shown in FIG. 2, the business support device 1 of this embodiment includes a memory unit 12, a control unit 13, a communication interface unit 14, and an input / output interface unit 15. An input device 16 and an output device 17 are connected to the input / output interface unit 15. The output device 17 may be a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to achieve a pointing device function. The communication interface unit 14 is communicatively connected to the terminal devices 2 to 6 of each company and the terminal device 7 of each worker via the above-mentioned network 8.

[0024] The storage unit 12 may be, for example, a storage device such as a ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive). The storage unit 12 stores a business support program that enables workers who have been transferred between companies A to E that make up a group of companies to easily refer to the document data of the company before and after the transfer. The storage unit 12 also has a reference area 20, which is a memory area shared by the companies.

[0025] The reference area 20 is provided with the following storage areas: an employee master table 21, a form data storage unit 22, a user master table 23, a user group master table 24, a copy source / copy destination table 25, a company authority master table 26, a company information storage unit 27, a job authority master table 28, and a job information storage unit 29. The employee master table 21 to the job information storage unit 29 store employee data, form data, security data, etc. uploaded from companies A to E.

[0026] Specifically, as shown in Figure 3(a), the employee master table 21 stores the company number, target year and month, employee code, name, gender, date of birth, date of retirement, affiliation, job title, user identification number (user ID), etc. for each worker at each company. The same employee code is used consistently regardless of which company, A to E, that the worker belongs to that makes up the group of companies. In other words, even if the worker is transferred to, for example, Company A or Company B, the employee code used by Company A before the transfer will continue to be used at Company B after the transfer.

[0027] As shown in Fig. 3(b), the document data storage unit 22 stores document header data and document entity data for each employee of each company. As document header data, the document identification number (document ID), company number, employee code, issue date, document type such as pay slip or withholding tax slip, and publication date and time, which is the date and time when this document header data and document entity data were stored in the reference area, are stored for each employee of each company. As document entity data, the document identification number (document ID) and entity data are stored for each employee of each company in a data format, for example, binary data.

[0028] 3(c), the user master table 23 stores the user ID, user name, password, expiration date, etc. of each worker of each company. This information is checked against the user ID, password, etc. entered when the worker logs in to the business support device 1 to obtain his / her own report data.

[0029] As shown in FIG. 3(d), the user group master table 24 stores, for each worker of each company, a user ID and a user group to which the user belongs in association with each other.

[0030] As shown in FIG. 3(i), the copy source / copy destination table 25 stores, in association with each other, a copy source company that uploads the form data and a copy destination company that stores the uploaded form data. In this example, the copy source companies are Companies A to E. In addition, in this example, the copy destination companies are the form reference companies of the business support device 1. That is, in the copy source / copy destination table 25, Companies A to E are all associated with one form reference company.

[0031] As shown in Figure 3(e), the company authority master table 26 stores the user group names and company numbers of users who are authorized to use the document reference system of the embodiment for each employee of each company.

[0032] As shown in FIG. 3(f), the company information storage unit 27 stores the company numbers, company names, etc. of companies that are permitted to use the form reference system of the embodiment.

[0033] As shown in Figure 3(g), the job authority master table 28 stores the names of user groups that are permitted to use the document reference system of the embodiment, and the processing contents (jobs) that are permitted to be executed.

[0034] As shown in FIG. 3(h), the job information storage unit 29 stores information indicating, for example, a job "inquiry of personal form" as a process content (job) that is permitted to be executed.

[0035] Among these, the employee master table 21, the user master table 23, and the job information storage unit 29 are mainly used to detect jobs for which user authentication and permission are to be performed. That is, when a user ID and a password are transmitted by a worker via the terminal device 7, the control unit 13 of the business support device 1 performs user authentication processing based on the user ID and password in the user master table 23.

[0036] When this user authentication process authenticates that the user is a legitimate user, the control unit 13 references the user group master table 24 based on the user ID to detect the user group to which the user belongs. The control unit 13 also references the company authority master table 26 based on the detected user group to detect the company number of the company that allows the user group to which the user belongs to query form data. The control unit 13 then references the company information storage unit 27 based on the detected company number to detect the company name of the company to which the user belongs.

[0037] On the other hand, the control unit 13 refers to the job authority master table 28 based on the user group detected by referring to the user group master table 24, and determines whether the user group to which the worker belongs is authorized to execute the job. The example in FIG. 3(g) is an example in which the user group to which the worker belongs is authorized to execute the job. If the job is authorized, the control unit 13 refers to the job information storage unit 29 and detects the job content (processing content). If the processing content of "personal form inquiry" is registered as the job content (processing content), this indicates that the worker is authorized to refer to his or her own form data, and the "personal form inquiry" is authenticated.

[0038] In this way, the employee master table 21, the user master table 23, and the job information storage unit 29 are mainly used for user authentication, company authentication, and authentication of jobs that require authorization (such as personal form inquiries).

[0039] An example of the employee master table 21 is shown in Fig. 4. As shown in Fig. 4, the employee master table 21 stores the company number, target year and month, employee code, name, joining date, leaving date, and user ID of each company, each of which is associated with the other information.

[0040] The company number is a unique number assigned to the above-mentioned companies A to E. The company number "100" is the company number of company A, the company number "200" is the company number of company B, and the company number "300" is the company number of company C. Furthermore, the company number "400" is the company number of company D, and the company number "500" is the company number of company E.

[0041] The target year and month is the year and month when the employee data was uploaded to the reference area 20. The example in Figure 4 shows that employee data for December 2022 and January 2023 was uploaded from Company A, whose company number is "100," and Company B, whose company number is "200," respectively.

[0042] The employee code is a number assigned uniquely to each worker at Companies A to E. This employee code is a number that is used consistently for that worker, even if the worker is transferred between Companies A to E that make up the group of companies. As an example, the employee code for employee M is "10001." Furthermore, the employee code for employee K is "10002," and the employee code for employee F is "10003."

[0043] The joining date is the date on which a worker joined the company. The leaving date is the date on which a worker left the company. The example in Figure 4 shows that for Company A, whose company number is "100", employee M, whose employee code is "10001", joined Company A, whose company number is "100", on April 1, 2010, and left Company A, whose company number is "100", on December 31, 2022. It also shows that employee M, whose employee code is "10001", joined (transferred to) Company B, whose company number is "200", on January 1, 2023.

[0044] The user ID is a unique number assigned to each worker in addition to the employee code. In the example of Figure 4, the user ID "User10001" is assigned to employee M, the user ID "User10002" is assigned to employee K, and the user ID "User10003" is assigned to employee F. This user ID is also a number that is used consistently for a worker even if the worker is transferred between companies A to E that make up the group of companies.

[0045] Next, as shown in Fig. 5, in the reference area 20 of the business support device 1, the form data uploaded from the terminal devices 2 to 6 of companies A to E is stored in the form data storage unit 22. This form data is stored in the form data storage unit 22 with the company number, employee code, issue date, form type, publication date and time, form ID, and entity data all associated with each other. The company number and employee code are each the unique numbers mentioned above.

[0046] The document type is information indicating the type of document, such as salary, bonus, withholding slip, or appointment letter. The issue date is the date on which the document was issued. The publication date and time is the date on which the document data of the document was uploaded (copied) to the reference area 20 of the business support device 1. The document ID is a unique identification number assigned to each document data. The entity data is the document data of each document, which is binary data.

[0047] In the example of Figure 5, a worker with employee code "10001" was paid a bonus on December 10, 2022 (issue date). The report data for this bonus was assigned a report ID of "ID0001" and uploaded to the reference area 20 on December 9, 2022. Similarly, a worker with employee code "10001" was paid a salary on December 25, 2022 (issue date). The report data for this salary was assigned a report ID of "ID0002" and uploaded to the reference area 20 on December 23, 2022. Furthermore, a withholding tax certificate was issued to the worker with employee code "10001" on December 28, 2022 (issue date). The report data for this withholding tax slip is assigned the report ID "ID0005" and was uploaded to the reference area 20 on December 28, 2022.

[0048] Furthermore, an appointment letter was issued to a worker with employee code "10001" on January 1, 2023. The document data for this appointment letter was assigned a document ID of "ID0008" and uploaded to the reference area 20 on January 1, 2023. Furthermore, with this appointment letter, the worker with employee code "10001" was transferred from Company A, whose company number is "100," to Company B, whose company number is "200," and an employment contract for Company B was issued to the worker on January 10, 2023. The document data for this employment contract was assigned a document ID of "ID0055" and uploaded to the reference area 20 on January 10, 2023. The worker with employee code "10001" was paid a salary on January 15, 2023, at the worker's new company, Company B. The report data for this salary's pay slip is assigned the report ID "ID0058" and was uploaded to the reference area 20 on January 13, 2023.

[0049] Next, in the business support device 1 of the embodiment, the company number of the form data uploaded to the reference area 20 from each company is changed to the company number "001", which is the company number of the form reference company, which is the company that manages this business support device 1. Then, the form data uploaded to the reference area 20 from each company is held in the reference area 20 with the original company number, and the form data changed to the company number "001" of the form reference company is stored in the reference area 20 and used for access by each worker.

[0050] The copy source / copy destination table 25 shown in Fig. 6 associates the company numbers before the change with the company numbers after the change. That is, in the example of Fig. 6, the company numbers of companies A to E, which are the copy source, "100," "200," "300," "400," and "500," are all changed to "001," which is the company number of the copy destination document reference company, and are stored in the reference area 20.

[0051] (Functional configuration of business support device) Next, the control unit 13 executes the business assistance program stored in the storage unit 12, thereby functioning as a storage control unit 31, an acquisition unit 32, an output control unit 33, and a display control unit 34, as shown in FIG.

[0052] In this example, the description will proceed assuming that the storage control unit 31 to the display control unit 34 are realized by software using a business assistance program, but some or all of the storage control unit 31 to the display control unit 34 may be realized by hardware. In either case, the same effects as those described below can be obtained.

[0053] The memory control unit 31 stores document data (pay slips, bonus slips, withholding tax slips, appointment orders, employment contracts, etc.) uploaded from multiple related companies (Company A to Company E) that make up a group of companies, for each worker (full-time workers, part-time workers, temporary workers, etc.) of each related company before and after transfer between related companies, in the reference area 20, which is a memory area of ​​the memory unit 12 that can be accessed by workers of each related company, together with each worker's unique employee identification information (employee code) used at each related company and the unique company identification information (company number) of the related company to which each worker belongs.

[0054] When a request for output of report data is received from a worker who has been transferred from one affiliated company to another affiliated company, the acquisition unit 32 acquires from the reference area 20 the specified report data from the report data before and after the transfer that is associated with the worker's employee identification information.

[0055] The output control unit 33 controls the output of the acquired form data. Applicable devices to be controlled include a monitor, a printer, an external memory device, and a communication unit. That is, if a monitor is provided as the output device 17 shown in FIG. 1, the form data can be displayed and output via the monitor. If a printer is provided as the output device 17 shown in FIG. 1, the form data can be printed and output via the printer. If an external memory device is provided as the output device 17 shown in FIG. 1, the form data can be supplied to the external memory device and stored therein.

[0056] The output control unit 33 may also control the communication unit (communication interface unit 14) to transmit the acquired form data to the worker's terminal device 7 via the network 8.

[0057] The display control unit 34 also controls the communication unit (communication interface unit 14) to display the acquired report data in a list on the worker's terminal device 7 (see FIG. 12). The output control unit 33 then controls the communication unit to transmit the report data selected by the worker from the list of displayed report data to the worker's terminal device 7.

[0058] Furthermore, the storage control unit 31 converts the company identification information (company numbers such as "100" and "200" of companies A to E) into unique managing company identification information (company number "001") assigned to the associated companies (document reference companies) that manage the business support device 1, and then stores this together with the document data and employee identification information (employee code) in the reference area 20. In this case, the acquisition unit 32 acquires the document data assigned with the managing company identification information (company number "001") from the reference area 20.

[0059] (Upload (copy) of report data to reference area) Next, the operation of uploading (copying) the form data of each company to the reference area 20 of the business support device 1 using the terminal devices 2 to 6 of companies A to E shown in FIG. 1 will be described.

[0060] In this case, the person in charge of each company's terminal devices 2 to 6 launches the document data copy screen shown in Fig. 7 and specifies the year and month (target year and month), document type, and issue date (issue period) of the document data to be uploaded. The example in Fig. 7 is an example in which document data for "December 2023" is specified as the target year and month, the document type of "1: Payslip" is specified, and document data generated during the period "December 1, 2023 to December 31, 2023" is specified.

[0061] After specifying the form data to be uploaded in this way, the person in charge presses the upload execution button. When the execution button is pressed, the control units of the terminal devices 2 to 6 of each company acquire the form data of the specified form type and employee data that occurred during the specified period from the form data of each form type stored in the memory unit by month of each year, and transmit the data to the business support device 1 via the network 8.

[0062] As a result, the employee data and report data uploaded from the terminal devices 2 to 6 of each company are stored in the reference area 20 of the business support device 1. FIG. 8(a) is an example of employee data uploaded from the terminal device 2 of company A. FIG. 8(b) is an example of employee data uploaded from the terminal device 3 of company B. FIG. 8(c) is a diagram showing an example of employee data of each company that has been uploaded to the business support device 1 and stored in the employee master table 21 of the reference area 20.

[0063] As shown in Figure 8(a), employee data for the specified December 2022 fiscal year, including Company A's company number ("100"), employee code, name, date of joining, date of leaving, and user ID for each worker, Employee M, Employee K, and Employee F, is uploaded from Company A's terminal device 2 to the business support device 1, and as shown in Figure 8(c), the memory control unit 31 of the business support device 1 stores the data in the employee master table 21 in the reference area 20.

[0064] Similarly, employee data for the specified December 2022 fiscal year, including Company B's company number ("200"), employee code, name, date of joining, date of leaving, and user ID for each worker, Employee G and Employee P, is uploaded from Company B's terminal device 3 to the business support device 1, and is stored in the employee master table 21 in the reference area 20 by the memory control unit 31 of the business support device 1, as shown in Figure 8(c).

[0065] Here, the employee data uploaded from each company's terminal device 2 to 6 is stored in the employee master table 21 in the reference area 20 of the business support device 1 as shown in Figure 8(c), and at this time the storage control unit 31 refers to the copy source / copy destination table 25 shown in Figure 6. The storage control unit 31 then changes all of the company numbers ("100", "200", "300", "400", "500") of the employee data of each company uploaded from each company to "001", which is the company number of the report reference company, and stores these in the employee master table 21 in the reference area 20 separately from the employee data whose company number has not been changed.

[0066] The employee data with the company number "001" shown in Figure 8(c) is the employee data stored after changing the company number of Company A, which was "100," to "001," which is the company number of the document reference company. In this way, the uploaded employee data of each company has the company number changed to "001," which is the company number of the document reference company, and is stored in the employee master table 21 in the reference area 20 separately from the original employee data, and is used to reference the document data, as will be described later.

[0067] 9(a) is an example of the form data uploaded from the terminal device 2 of company A. FIG. 9(b) is an example of the form data uploaded from the terminal device 3 of company B. FIG. 9(c) is a diagram showing an example of the form data of each company that has been uploaded to the business support device 1 and stored in the form data storage unit 22 of the reference area 20.

[0068] As shown in Figure 9(a), for the specified December 2022 fiscal year, the following document data, including Company A's company number ("100"), the employee codes of each worker, Employee M (Employee code 10001), Employee K (Employee code 10002), and Employee F (Employee code 10003), the document type, the document issue date, the publication date and time which is the date and time of upload to the reference area 20, the document ID, and the document entity data, are uploaded from Company A's terminal device 2 to the business support device 1. Then, as shown in Figure 9(c), the memory control unit 31 of the business support device 1 stores the document data in the document data memory unit 22 of the reference area 20.

[0069] Similarly, the specified company number ("200") of Company B, the employee codes of each worker, Employee G (employee code 20001) and Employee P (employee code 20002), the form type, the issuance date of the form, the publication date and time which is the date and time of upload to the reference area 20, the form ID, and the form data including the entity data of the form for December 2022 are uploaded from Company B's terminal device 3 to the business support device 1. Then, as shown in FIG. 9(c), the memory control unit 31 of the business support device 1 stores the data in the form data memory unit 22 of the reference area 20.

[0070] Here, the form data uploaded from the terminal devices 2 to 6 of each company is stored in the form data storage unit 22 of the reference area 20 of the business support device 1 as shown in Fig. 9(c), and at this time the storage control unit 31 refers to the copy source / copy destination table 25 shown in Fig. 6. Then the storage control unit 31 changes all of the company numbers ("100", "200", "300", "400", "500") of the form data of each company uploaded from each company to "001", which is the company number of the form reference company, and stores these in the form data storage unit 22 of the reference area 20 separately from the form data whose company number has not been changed.

[0071] Of the form data with company number "001" shown in Figure 9(c), the form data for employee codes "10001," "10002," and "10003" is form data that has been stored after changing the company number "100" of Company A to "001," which is the company number of the form-referencing company. Also, of the form data with company number "001" shown in Figure 9(c), the form data for employee codes "20001" and "20002" is form data that has been stored after changing the company number "200" of Company B to "001," which is the company number of the form-referencing company.

[0072] In this way, the uploaded report data of each company has the company number changed to "001" of the report reference company, and is stored separately from the original report data in the report data storage section 22 of the reference area 20, and is used to query the report data as described below.

[0073] (Inquiry of report data) In this way, once the employee data and report data of each company are uploaded (copied) to the reference area 20 of the business support device 1, workers of each company can access the business support device 1 at their desired time and download (obtain) their own report data.

[0074] Specifically, when a user ID and password are entered via the worker's terminal device and a login request is made to the business support device 1, the acquisition unit 32 refers to the user master table 23 based on the entered user ID and password, as described using Figure 3, and performs user authentication processing.

[0075] If this user authentication process authenticates that the user is a legitimate user, the acquisition unit 32 references the employee master table 21 based on the user ID. Then, as shown in Figure 10(a) or 10(b), the acquisition unit 32 acquires employee data corresponding to the login date and user ID from among the employee data whose company number has been changed to "001" of the document reference company.

[0076] Figure 10(a) shows the employee data that will be acquired when employee M, a worker, logs in in December 2022. In the example of employee data shown in Figure 4, as of December 2022, employee M joined company A on April 1, 2010, and is affiliated with company A with a company number of 100. Therefore, when logging in in December 2022, as shown in Figure 10(a), the following employee data will be acquired: company number "001 (the company number of the report reference company in the change process described above)", target year and month (year and month at the time of login) "December 2022", employee code "10001", name "Employee M", joining date "April 1, 2010", leaving date "blank (NULL data)", and user ID "User10001".

[0077] In contrast, as shown in Figure 4, employee M will be transferred to company B, which has a company number of "200," on January 1, 2023. Therefore, when employee M logs in in January 2023, as shown in Figure 10(b), the following employee data is obtained: company number "001 (the company number of the report reference company due to the change process described above)," target year and month (year and month at the time of login) "January 2023," employee code "10001," name "Employee M," joining date "January 1, 2023," leaving date "blank (NULL data)," and user ID "User10001."

[0078] Next, as described with reference to FIG. 3, the acquisition unit 32 references the user group master table 24 based on the user ID and detects the user group to which the user belongs. Furthermore, based on the detected user group, the acquisition unit 32 references the job authority master table 28 and determines whether the user group to which employee M belongs is authorized to execute the job. The example in FIG. 3(g) is an example in which the user group to which employee M belongs is authorized to execute the job. If execution of the job is authorized, the acquisition unit 32 references the job information storage unit 29 and detects the job content (processing content). If the processing content of "personal form inquiry" is registered as the job content (processing content), this indicates that employee M is authorized to reference his or her own form data. In this way, the acquisition unit 32 authenticates employee M's authorization to reference his or her own form data.

[0079] Next, after authenticating employee M's (employee M's) right to view his / her own (employee M's) form data, the display control unit 34 controls the communication of the communication interface unit 14 to send the personal form reference screen shown in FIG. 12 to employee M's terminal device 7. Employee M inputs the form type and the issue date of the form he / she wishes to inquire about on this personal form reference screen, and operates the display button 50. As a result, information indicating the selected form type, the selected issue date, and that the display button has been operated is transmitted from employee M's terminal device 7 to the business support device 1.

[0080] When receiving information indicating that the display button 50 has been operated, the acquisition unit 32 refers to the form data storage unit 22 based on the employee code of "10001" detected by referring to the employee master table 21 and the issue year and month selected on the personal form reference screen. Then, as shown in FIG. 11(a) or 11(b), the acquisition unit 32 acquires form data issued in the issue year selected on the personal form reference screen for employee M corresponding to the login date and the employee code of "10001" from the form data for which the company number of the form reference company has been changed to "001."

[0081] FIG. 11(a) shows the document data that is acquired when employee M logs in on December 31, 2022, and specifies the issue date for December 2022. The example in FIG. 11(a) shows that the documents, including a bonus statement, a pay statement, and a withholding tax slip, were issued to employee M (employee code "10001") in December 2022, which is the specified issue date. Therefore, the acquisition unit 32 acquires the document data for employee M from the document data storage unit 22, including the company number "001 (the company number of the document reference company in the above-mentioned change process)", employee code ("10001"), issue date (an issue date before December 31, 2022), document type, publication date and time, document ID, and document entity data corresponding to these documents.

[0082] In contrast, Figure 11(b) shows the report data that is acquired when employee M logs in on January 15, 2023 and specifies December 2022 and January 2023. In this example, as described above, employee M is transferred from company A to company B on January 1, 2023. However, the report data storage unit 22 stores report data for reports issued by company A before the transfer, and report data for reports issued by company B after the transfer during the period from the transfer to January 15, 2023, the date of login.

[0083] For this reason, as shown in Figure 11(b), the acquisition unit 32 acquires the document data of the above-mentioned bonus statement, salary statement, and withholding tax slip issued by company A before the transfer (December 2022), as well as the document data of the appointment order, employment contract, and salary statement issued by company B after the transfer (after January 1, 2023).

[0084] Next, the display control unit 34 transmits the acquired report data to employee M's terminal device 7. Then, as shown in FIG. 12, the display control unit 34 displays a list of the acquired report data for employee M on employee M's terminal device 7. FIG. 12 shows an example of a list display of report data for the bonus statement issued by company A on December 10, 2022, the pay statement issued by company A on December 25, 2022, and the withholding tax slip issued by company A on December 28, 2022, before employee M was transferred. FIG. 12 also shows an example of a list display of report data for the employment contract issued by company B on January 10, 2023, and the pay statement issued by company B on January 15, 2023, after employee M was transferred.

[0085] Note that this example is an example of displaying a list of report data for the publication month selected by the worker, but the display control unit 34 may also display a list of all report data issued up to the date of login without requiring the worker to select the publication month.

[0086] Next, as shown in FIG. 12, employee M selects the form data to be output from the list of displayed form data via the selection field for each form data, and operates the inquiry (download) button 51. FIG. 12 shows an example in which, from the list of displayed form data, the following form data has been selected: a bonus statement issued by company A on December 10, 2022, before the transfer; a pay statement issued by company A on December 25, 2022; and a withholding tax slip issued by company A on December 28, 2022. When the inquiry (download) button 51 is operated, employee M's terminal device 7 transmits information indicating the form data selected by employee M to the business support device 1.

[0087] Then, the output control unit 33 of the business support device 1 transmits each piece of report data selected by employee M (in this example, the report data issued by Company A before the transfer in December 2022) to employee M's terminal device 7 via the communication interface unit 14. In this way, the business support device 1 of the embodiment can freely obtain report data of individual worker reports.

[0088] (Job authentication behavior) Next, the authentication operation for jobs permitted for a worker will be described with reference to Figure 13. In Figure 13, when a user is authenticated as a legitimate user through the user authentication process at login described above, the acquisition unit 32 references the user group master table 24 based on the user ID and detects the user group to which the user belongs, as shown in Figures 13(a) and 13(b). In addition, the acquisition unit 32 references the company authority master table 26 based on the detected user group and detects the company number of the company that permits the user group to which the user belongs to inquire about report data, as shown in Figure 13(c).

[0089] In this example, the form data that can be referenced is limited to form data of form-referencing companies with a company number of "001." Therefore, by referencing the company authority master table 26, the company number of the form-referencing company, "001," is detected as the company number of the company for which the user group to which the user belongs is permitted to reference form data.

[0090] Then, as shown in Figure 13(d), the acquisition unit 32 refers to the company information storage unit 27 based on the detected company number "001" and recognizes the scope of the report data that can be queried (for example, "the entire group") corresponding to the company number "001".

[0091] On the other hand, the acquisition unit 32 refers to the job authority master table 28 shown in FIG. 13(e) based on the user group detected by referring to the user group master table 24, and determines whether the user group to which the worker belongs is authorized to execute the job. If the job is authorized, the control unit 13 refers to the job information storage unit 29 as shown in FIG. 13(f) to detect the job content (processing content). As the job content (processing content), the processing content of "personal form inquiry" is registered in the job information storage unit 29. As a result, the acquisition unit 32 authenticates that the worker is authorized to refer to his / her own form data.

[0092] (Flow of report inquiry operation) Finally, the flow of the form inquiry operation explained above will be explained with reference to FIG.

[0093] First, the worker operates the terminal device 7, inputs the user ID and password on the login screen, and sends it to the business support device 1. As a result, the personal form inquiry screen described with reference to FIG. 12 is sent to and displayed on the terminal device 7, and the worker selects the type of form to inquire about and the issuance date of the form, and operates the inquiry (download) button 51. As a result, the issuance date and type of form selected via the personal form inquiry screen are sent from the terminal device 7 to the business support device 1.

[0094] The acquisition unit 32 of the business support device 1 acquires the worker's form data corresponding to the issue date and type of form selected via the personal form inquiry screen from the form data storage unit 22 in the reference area 20. Then, the output control unit 33 transmits the acquired form data to the worker's terminal device 7. This allows the worker to inquire about forms of the desired period and type.

[0095] (Effects of the embodiment) As is clear from the above explanation, the document reference system of the embodiment consolidates and stores documents such as pay slips issued by each related company in a dedicated area (reference area) for a specified period, such as every month.

[0096] This allows each affiliated company to seamlessly transfer the accounting data before and after the transfer to a dedicated area (reference area), reducing the tedious task of the person in charge at the affiliated company before the transfer having to provide accounting data from the time the employee was employed at the affiliated company before the transfer every time a worker requests it.

[0097] In addition, workers can freely refer to their own document data before and after their transfer, which has been transferred to a dedicated area (reference area). This reduces the need for tedious work such as changing security settings for workers or systems when workers are transferred.

[0098] In other words, regardless of whether a worker has been transferred or not, they can freely access the document data issued by each company in the group without changing the security settings.

[0099] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of goals "8" and "9" of the SDGs.

[0100] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs goals 12, 13, and 15.

[0101] Furthermore, the present invention can contribute to strengthening control and governance, thereby contributing to the achievement of Goal 16 of the SDGs.

[0102] [Other embodiments] The present invention can be implemented in various different forms other than the above-described embodiments within the scope of the technical concept described in the claims.

[0103] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually, or all or part of the processes described as being performed manually may be performed automatically using a known method or the like.

[0104] Furthermore, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in the specification or drawings may be changed as desired unless otherwise specified.

[0105] Furthermore, the components of the business support device 1 shown in the figure are conceptual functional components and do not necessarily have to have the physical configuration shown in the figure. For example, all or any part of the processing functions of the business support device 1, particularly the processing functions performed by the control unit 13, may be realized by a program interpreted and executed by the control unit 13 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0106] The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in the embodiments, and is mechanically read by the business support device 1 as needed. That is, the storage unit 12, such as a ROM or HDD, stores a computer program for working with an OS (Operating System) to give instructions to the control unit 13 (CPU) and perform various processes. The computer program is loaded into RAM, expanded, and executed by the control unit 13 as appropriate.

[0107] In addition, the business support program of this business support device 1 may be stored in another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0108] Furthermore, the business support program for executing the processes described in the embodiments may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0109] Here, the "recording medium" can be 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.

[0110] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code.

[0111] It should be noted that a "program" is not necessarily limited to a single structure, but includes a structure that is distributed as multiple modules or libraries, and a structure that achieves its function by working together with other programs, such as an OS.

[0112] Furthermore, the specific configuration for reading the recording medium in the task support device 1 of the embodiment, the reading procedure, and the installation procedure after reading can be any known configuration or procedure.

[0113] The memory unit 12 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, web page files, etc. used for various processes or to provide websites.

[0114] The business support device 1 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may be implemented with software (including programs or data) that realizes the processes described in the embodiments.

[0115] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be selectively implemented by combining them in any way. [Industrial Applicability]

[0116] The present invention is suitable for application to the management of document data of related companies that make up a group of companies. [Explanation of symbols]

[0117] 1 Business support equipment 2. Company A's terminal equipment 3. Company B's terminal equipment 4 Company C's terminal equipment 5. Company D's terminal equipment 6. E Company's terminal equipment 7. Terminal devices of employees of each affiliated company 8 Network 12 Storage section 13 Control Unit 14 Communication interface section 15 Input / output interface section 16 Input Devices 17 Output Devices 20 Reference area 21 Employee Master Table 22 Report data storage unit 23 User Master Table 24 User Group Master Table 25 Source / Destination Tables 26 Company Authority Master Table 27 Company Information Storage Department 28 Job Authority Master Table 29 Job information storage unit 31 Memory control unit 32 Acquisition Department 33 Output control section 34 Display control unit

Claims

1. a storage control unit that stores the report data uploaded from a plurality of related companies that make up a group of companies, for each worker of the related companies, before and after transfer between the related companies, in a reference area, which is a storage area of ​​the storage unit that can be accessed by workers of each related company, together with the unique employee identification information of each worker used in each related company and the unique company identification information of the related company to which each worker belongs; an acquisition unit that acquires, from the reference area, designated form data from the form data before and after the transfer that is associated with the employee identification information of the worker when an output request for the form data is received from the worker who has been transferred from the related company to another related company; an output control unit that controls output of the acquired form data; A business support device having the above.

2. the output control unit controls a communication unit to transmit the acquired form data to the worker's terminal device via a network; 2. The business support device according to claim 1, wherein:

3. A display control unit that displays the acquired document data in a list on the terminal device of the worker, the output control unit controls the communication unit to transmit selected form data from the displayed list of form data to the terminal device of the worker; 3. The business support device according to claim 2, wherein:

4. the storage control unit converts the company identification information into unique managing company identification information assigned to an associated company that manages the business support device, and stores the converted information in the reference area together with the form data and the employee identification information; the acquiring unit acquires the form data to which the managing company identification information is attached from the reference area; 4. The business support device according to claim 1, wherein:

5. a storage control step in which the storage control unit stores the document data uploaded from a plurality of related companies constituting a group of companies, for each worker of the related companies, before and after transfer between the related companies, in a reference area, which is a storage area of ​​the storage unit accessible by workers of each related company, together with the unique employee identification information of each worker used in each related company and the unique company identification information of the related company to which each worker belongs; an acquisition step in which, when an output request for the form data is received from the worker who has been transferred from the related company to another related company, the acquisition unit acquires, from the reference area, designated form data from the form data before and after the transfer that is associated with the employee identification information of the worker; an output control step in which an output control unit controls output of the acquired form data; A business support method having the above.

6. Computer, a storage control unit that stores the report data uploaded from a plurality of related companies that make up a group of companies, for each worker of the related companies, before and after transfer between the related companies, in a reference area, which is a storage area of ​​the storage unit that can be accessed by workers of each related company, together with the unique employee identification information of each worker used in each related company and the unique company identification information of the related company to which each worker belongs; an acquisition unit that acquires, from the reference area, designated form data from the form data before and after the transfer that is associated with the employee identification information of the worker when an output request for the form data is received from the worker who has been transferred from the related company to another related company; functioning as an output control unit that controls output of the acquired form data; Business support programs.

Images