WO2024090292A1

WO2024090292A1 - Processing device, processing program, and processing method

Info

Publication number: WO2024090292A1
Application number: PCT/JP2023/037563
Authority: WO
Inventors: 寿充東川; 卓也小川
Original assignee: Ｕｎｉｆｏｒｃｅ株式会社
Priority date: 2022-10-26
Filing date: 2023-10-17
Publication date: 2024-05-02
Also published as: JP2024063313A

Abstract

[Problem] To facilitate an understanding of various processes and task statuses relating to account settlement tasks. [Solution] Upon receipt of a specified deadline relating to account settlement, a start deadline or an end deadline of a working period is set for each task by subtracting a preset offset value from the specified deadline, the working period is set for each task on the basis of the set start deadline or end deadline and a reference working period set for each task, and a plurality of tasks are output on a display on the basis of the working period set for the plurality of tasks.

Description

Processing device, processing program, and processing method

This disclosure relates to a processing device, processing program, and processing method related to accounting tasks.

　In the past, equipment maintenance support systems capable of automatically managing required tasks and their deadlines have been known in industries such as equipment maintenance work. For example, Patent Document 1 describes an equipment maintenance support system that includes a reception system, a mobile system, a network system, and a base system, in which the base system has a task management table in which multiple tasks are defined, and the reception system has a means for automatically transitioning the state of the reception system, the mobile system, and the network system to the next task, the second task, when the reception system receives a notification from the mobile system or the network system that a condition for transitioning to the next task, the second task, for any first task among the multiple tasks based on the task management table has been satisfied.

In cases such as facility maintenance work, each task can be clearly separated, and the number and variety of tasks themselves do not generally become enormous. Furthermore, the documents required for each task are not often related to each other, and it is generally easy to create the documents required for each task. For this reason, deadline management was easy to achieve for facility maintenance work. However, in work related to the disclosure of company financial statements, the required tasks and documents to be created were enormous and often related to each other, making deadline management complicated.

JP 2021-114098 A

The present disclosure has been made against the background described above, and provides a processing device, processing program, and processing method that can facilitate the understanding of various processes and task statuses related to accounting tasks.

According to one aspect of the present disclosure, there is provided a processing device having at least one processor that executes a process for creating a schedule for a plurality of tasks related to a settlement operation, the at least one processor being configured to execute a process for: upon receiving a specified deadline related to the settlement operation, subtracting a preset offset value from the specified deadline to set a start deadline or end deadline for a work period for each of the tasks; setting a work period for each of the tasks based on the set start deadline or end deadline and a standard work period set for each of the tasks; and outputting the plurality of tasks on a display based on the work periods set for the plurality of tasks.

According to one aspect of the present disclosure, there is provided a processing program that causes a computer having at least one processor to function as follows: when a specified deadline for accounting work is received, the at least one processor subtracts a preset offset value from the specified deadline to set a start deadline or end deadline for a work period for each task, sets a work period for each task based on the set start deadline or end deadline and a standard work period set for each task, sets a time interval, sets a second deadline from the work period set for each task, and outputs the multiple tasks on a display based on the work periods set for the multiple tasks.

According to one aspect of the present disclosure, there is provided a processing method executed by at least one processor in a computer having the at least one processor, the processing method including the steps of: when a specified deadline for accounting work is received, subtracting a preset offset value from the specified deadline to set a start deadline or end deadline for a work period for each task; setting a work period for each task based on the set start deadline or end deadline and a standard work period set for each task; setting a second deadline from the work period set for each task; and outputting the multiple tasks on a display based on the work periods set for the multiple tasks.

According to the present disclosure, it is possible to provide a processing device, processing program, and processing method that can facilitate the understanding of various processes and task statuses related to accounting tasks.

Note that the above effects are merely illustrative for the convenience of explanation and are not limiting. In addition to or instead of the above effects, any effect described in this disclosure or any effect that would be obvious to a person skilled in the art may be achieved.

FIG. 1 is a diagram illustrating an outline of a deadline management process in a processing system 1 according to an embodiment of the present disclosure. FIG. 2 is a conceptual diagram illustrating a schematic configuration of a processing system 1 according to an embodiment of the present disclosure. FIG. 3 is a block diagram illustrating an example of a configuration of the user terminal device 100 according to an embodiment of the present disclosure. FIG. 4 is a block diagram illustrating an example of a configuration of the server device 200 according to an embodiment of the present disclosure. FIG. 5A is a diagram conceptually illustrating a task management table stored in the server device 200 according to an embodiment of the present disclosure. FIG. 5B is a diagram conceptually illustrating a person in charge management table stored in the server device 200 according to an embodiment of the present disclosure. FIG. 6A is a diagram showing a processing sequence executed between the user terminal device 100 and the server device 200 according to an embodiment of the present disclosure. FIG. 6B is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. FIG. 6C is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. FIG. 6D is a diagram showing an example of a screen output to the user terminal device 100 according to an embodiment of the present disclosure. FIG. 7A is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure. FIG. 7B is a diagram illustrating an outline of an example of a schedule creation process executed in the server device 200 according to an embodiment of the present disclosure. FIG. 8 is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure.

Embodiments of the present disclosure will be described with reference to the accompanying drawings. Note that common components in the drawings are given the same reference numerals.

1. Overview of the processing system 1 according to the present disclosure The processing system 1 according to the present disclosure is used, for example, to set work periods for a plurality of tasks related to a company's accounting operations and to perform schedule management for each task. In particular, the processing system 1 is preferably used when providing an optimal schedule for each company by, for example, acquiring information on the company's internally designated deadline (designated deadline) set before the legal deadline automatically calculated from the accounting date from companies with different accounting dates. Specifically, the processing system 1 sets the start deadline (scheduled start date) or end deadline (scheduled end date) of the work period for each task by subtracting a preset offset value from the internally designated deadline, and sets the work period for each task based on the set start deadline or end deadline and the standard work period set for each task. In addition, when setting the work period, the processing system 1 also takes into account the processing order set for the plurality of tasks, optimizing task deadline management.

FIG. 1 is a diagram showing an outline of deadline management processing in a processing system 1 according to an embodiment of the present disclosure. Specifically, the example shows a case where users A and B have requested schedule management of tasks related to accounting work. According to FIG. 1, A and B have different accounting dates. For this reason, A and B need to manage the schedule of tasks in accordance with their accounting dates, and they request task schedule management with A's accounting date set to December 15th and B's accounting date set to March 31st. In this case, A and B will set an internally designated deadline before the statutory deadline that is automatically determined from the accounting date.

The accounting schedule creation server device (hereinafter simply referred to as the server device) constituting the processing system 1 creates schedules for multiple tasks related to accounting work based on the acquired accounting date and in-house specified deadline. According to FIG. 1, the server device creates a schedule specifically for Company A based on Company A's accounting date (December 15th) and in-house specified deadline (November 30th), and provides a task management table for Company A with a dashboard of task work periods. Meanwhile, the server device creates a schedule specifically for Company B, which is different from Company A, based on Company B's accounting date (March 31st) and in-house specified deadline (March 1st), and provides a task management table for Company B with a dashboard of task work periods. In particular, the processing system 1 according to the present disclosure makes it easier for users to grasp task deadline management based on dashboarded information, and makes deadline management itself easy to perform.

Furthermore, in this disclosure, "task" simply means work and operations related to accounting procedures. In particular, in this disclosure, "tasks" are subdivided based on specialized knowledge of accounting procedures, and an enormous number of over 400 tasks have been set. However, the content and quantity of "tasks" are not fixed, and the content and quantity can be set as appropriate. Accounting procedures include accounting disclosure procedures, and are a series of tasks related to accounting. For this reason, the embodiment of this disclosure is described assuming tasks related to accounting disclosure procedures, but the tasks in this disclosure are not limited to those related to accounting disclosure procedures, and can be broadly applied to accounting procedures.

In the embodiment of the present disclosure, the "designated deadline" is described by taking as an example a company-specified deadline set by the user, but the "designated deadline" is not limited to a date and may be set in weeks or hours. Similarly, in the embodiment of the present disclosure, the "offset value" is described by taking as an example a date that is set in advance for each task on the server device side, but the "offset value" is not limited to a date and may be set in weeks or hours. In the embodiment of the present disclosure, the end deadline of each task is described by taking as an example a date calculated by subtracting the offset value from the company-specified deadline, but the end deadline is not limited to a date and may be set in weeks or hours. Similarly, the start deadline of each task in the present disclosure is not limited to a start date and may be set in weeks or hours. In other words, in the present disclosure, the schedule of tasks related to accounting work can be managed on a daily, weekly, or hourly basis.

In addition, in the embodiment of the present disclosure, the "designated deadline" and "task end deadline" are described using internal company dates as examples, but are not limited to dates related to the inside of a company, etc. In other words, in the present disclosure, the "designated deadline", "task end deadline", and "task start deadline" are not limited to deadlines such as dates related inside or outside a company, and include dates related not only to general companies but also to certain organizations (e.g., professional services). In other words, the schedule management of tasks related to the accounting work of the present disclosure may also be carried out within certain organizations, such as offices other than a company, or corporations.

In this disclosure, the names given to each device are used merely to distinguish each device from others, and each device may be given a different name depending on its function.

Furthermore, even if the term "first" or "second" is used in this disclosure, this does not mean that it is limited to only the two elements to which it is attached. Naturally, it may include "third," "fourth," and more multiple elements.

2. Configuration of the Processing System 1 FIG. 2 is a conceptual diagram illustrating the configuration of the processing system 1 according to an embodiment of the present disclosure. As shown in FIG. 2, the processing system 1 includes a user terminal device 100 installed in a company that performs accounting operations, and a server device 200 that is a processing device that creates a task schedule based on a request from the user terminal device 100. Here, the user terminal device 100 and the server device 200 are connected to each other via a network 300 so that they can communicate in both directions. The network 300 is, for example, the Internet. That is, the user terminal device 100 and the server device 200 are connected to an Internet line by wire or wirelessly, and are capable of transmitting and receiving various information and the like.

In the example of FIG. 2, only one user terminal device 100 is shown, but since the user is a company that performs accounting procedures, multiple user terminal devices 100 are connected to each other so that they can communicate with each other via the network 300. Also, although the server device 200 is shown as a single device, it is also possible to distribute the components and processes of the server device 200 to multiple server devices or cloud server devices.

3. Configuration of the user terminal device 100 Fig. 3 is a block diagram showing an example of the configuration of the user terminal device 100 according to an embodiment of the present disclosure. The user terminal device 100 does not need to include all of the components shown in Fig. 3, and may have a configuration in which some components are omitted, or may include other components.

The user terminal device 100 is typically a terminal device capable of wireless communication, such as a laptop computer or desktop computer, but is of course not limited to such devices. For example, the user terminal device 100 can be suitably applied to any device capable of executing the program related to the present disclosure, such as a smartphone, feature phone, personal digital assistant, PDA, portable game machine, or stationary game machine. Also, as described above, when multiple user terminal devices 100 are capable of communicating with the server device 200, the user terminal devices 100 do not necessarily have to be the same type or the same terminal device, but may be different types of terminal devices.

As shown in FIG. 3, the user terminal device 100 includes an output interface 111, a processor 112, a memory 113 including RAM, ROM, or non-volatile memory (or HDD in some cases), a communication interface 114 including a communication processing circuit and an antenna, and an input interface 115 including a mouse 115a and a keyboard 115b. These components are electrically connected to each other via control lines and data lines.

The output interface 111 functions as an output unit that outputs display information received from the server device 200 to a device such as a display or a printer by executing a program according to the present disclosure in response to instructions from the processor 112. Such a display may be, for example, a liquid crystal display, an organic electroluminescence display, or electronic paper.

The processor 112 is composed of a CPU (microcomputer) and functions as a control unit that controls other connected components based on various programs stored in the memory 113. Specifically, the processor 112 reads out and executes programs for executing various applications and programs for executing the OS from the memory 113. In this disclosure, the processor 112 particularly executes a part of the processing described in the processing sequence described below. Details of the processing will be explained in detail in the explanation from FIG. 6A onwards. The processor 112 may be composed of a single CPU, or may be composed of a combination of multiple CPUs and GPUs.

Memory 113 is composed of ROM, RAM, non-volatile memory, HDD, etc., and functions as a storage unit. ROM stores instructions for executing the application and OS related to the present disclosure as a program. RAM is used to write and read data while the program stored in ROM is being processed by processor 112. Non-volatile memory is memory into which data is written and read by the execution of the program, and data written therein is saved even after the execution of the program has ended. In the present disclosure, memory 113 particularly stores a program that executes part of the processing described in the processing sequence described below. Details of the processing will be explained in detail when explaining FIG. 6B and subsequent figures.

The communication interface 114 functions as a communication unit that transmits and receives information to and from a remotely installed server device 200 via a communication processing circuit and an antenna. The communication processing circuit processes the programs and various information used in the processing system 1 to transmit and receive information from the server device 200 according to the progress of processing. In this disclosure, in particular, user information related to accounting operations (such as the company's designated deadline, and the department and position in charge of the task) and information related to the progress of the task are transmitted to the server device 200, and information related to the task schedule is transmitted from the server device 200.

The communication processing circuit processes based on a wideband wireless communication method such as the LTE method, but it is also possible to process based on a method related to narrowband wireless communication such as wireless LAN such as IEEE802.11 or Bluetooth (registered trademark) or a method related to contactless wireless communication. It is also possible to use wired communication instead of or in addition to wireless communication.

The input interface 115 is composed of, for example, a mouse 115a and a keyboard 115b, and functions as an input unit that accepts instruction inputs related to the execution of the program according to the present disclosure and operation inputs for registering various information. The mouse 115a and the keyboard 115b are connected wirelessly or by wire to a main body including the processor 112, etc. The configuration of the input interface 115 is not limited to this, and a touch panel or other hard keys, etc. may be used. For example, when a touch panel is used, the touch panel is arranged to cover the output interface 111, and information on position coordinates corresponding to the data of an image output from the output interface 111 to the display is transmitted to the processor 112. As a touch panel method, known methods such as a resistive film method, a capacitive coupling method, and an ultrasonic surface acoustic wave method can be used. In the present disclosure, the touch panel detects swipe operations and tap operations on each icon, etc. displayed on the output interface 111 by an indicator.

4. Configuration of the server device 200 Fig. 4 is a block diagram showing an example of the configuration of the server device 200 according to an embodiment of the present disclosure. The server device 200 does not need to include all of the components shown in Fig. 4, and may have a configuration in which some components are omitted, or other components may be added. In addition, the server device 200 does not need to include the components shown in Fig. 4 in a single housing, and each component and process of the server device 200 may be distributed to multiple server devices or cloud server devices.

As shown in FIG. 4, the server device 200 includes a memory 211 including RAM, ROM, non-volatile memory, HDD, etc., a processor 212 consisting of a CPU, etc., an input/output interface 213, and a communication interface 214. These components are electrically connected to each other via control lines and data lines.

Memory 211 includes RAM, ROM, non-volatile memory, and HDD, and functions as a storage unit. ROM stores instructions for executing the application and OS related to the present disclosure as a program. Such programs are loaded and executed by processor 212. RAM is used to write and read data while the program stored in ROM is being processed by processor 212. Non-volatile memory is memory into which data is written and read by the execution of the program, and data written here is retained even after execution of the program has ended.

In this disclosure, the memory 211 stores programs for "processing for subtracting a preset offset value from a specified deadline for settlement operations when the specified deadline is received to set a start deadline or end deadline for the work period for each task," "processing for setting a work period for each task based on the set start deadline or end deadline and the standard work period set for each task," and "processing for outputting multiple tasks to a display based on the work periods set for the multiple tasks." The memory 211 also stores information regarding users authorized to use the server device 200, information regarding the tasks of the settlement operations, general information regarding the settlement operations, and legal information regarding the settlement operations.

The processor 212 is composed of a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 211. Specifically, the processor 212 reads out from the memory 211 a program for executing an application related to the present disclosure and a program for executing an OS, and executes them. In the present disclosure, the processor 212 executes, in particular, "a process of subtracting a preset offset value from a designated deadline for settlement work received to set a start deadline or end deadline for a work period for each task," "a process of setting a work period for each task based on the set start deadline or end deadline and the standard work period set for each task," and "a process of outputting multiple tasks to a display based on the work periods set for the multiple tasks." The processor 212 may be composed of a single CPU, or multiple CPUs.

The input/output interface 213 functions as an output unit that executes the program according to the present disclosure in response to instructions from the processor 212, and outputs information received from the user terminal device 100 and information related to the accounting process to devices such as a display or printer. Such a display may be, for example, a liquid crystal display, an organic electroluminescence display, or electronic paper. The input/output interface 213 also functions as an input unit that accepts instruction inputs related to the execution of the program according to the present disclosure and operation inputs for registering various information. For example, a mouse and keyboard are connected wirelessly or by wire. The configuration of the input/output interface 213 is not limited to this, and a touch panel or other hard keys may be used. As the touch panel method, known methods such as a resistive film method, a capacitive coupling method, and an ultrasonic surface acoustic wave method may be used.

The communication interface 214 functions as a communication unit that transmits and receives information between the user terminal device 100 and other server devices installed remotely via a communication processing circuit and an antenna. The communication processing circuit processes the programs and various information used in the processing system 1 to transmit and receive information from the user terminal device 100 and other server devices according to the progress of processing. In this disclosure, in particular, information regarding users authorized to use the server device 200, information regarding the tasks of the settlement work, general information regarding the settlement work, and legal information regarding the settlement work are transmitted and received between the server device 200 and the user terminal device 100 via the communication interface 214.

Note that the input/output interface 213 and the communication interface 214 may be configured as a common interface when devices of the same standard are used. For example, when the input/output interface 213 is a connection device that performs wireless communication, the input/output interface 213 may be included in the communication interface 214.

5. Information stored in the memory 211 of the server device 200 FIG. 5A is a diagram conceptually illustrating a task management table stored in the server device 200 according to an embodiment of the present disclosure. Among the information stored in the task management table, the ID, upper task, middle task, lower task, related task ID, responsible department, available position, document name, standard work period, and offset value are information registered as initial states from the start of use of the processing system 1, regardless of whether or not a schedule management request is sent from the user terminal device 100. In addition, the person in charge, status, start date, and end date are information that are automatically input when a schedule management request is made from the user terminal device 100 to the server device 200, and are information that can be changed by additional information and update information received from the user terminal device 100. Furthermore, the work details, labor hours, and remarks are information that can be input or changed by update information received from the user terminal device 100 when schedule management is started and the actual task is progressing.

"ID" is an identification number given to each task related to the accounting process. As shown in FIG. 5A, there are two types of IDs, and the format of the ID given to the higher-level tasks described later is different from that given to the middle-level tasks and lower-level tasks described later. Specifically, the higher-level tasks are given a code such as "xx" or "yy". On the other hand, the middle-level tasks and lower-level tasks are given a hyphen and a serial number after the code of the higher-level task (for example, "xx-001", "yy-001"). This associates the higher-level task with its constituent middle-level tasks and lower-level tasks, making it easier to identify the tasks. The format of the ID is not limited to the above, and any format may be used as long as it is possible to identify each task. For example, numbers, letters, or other symbols may be added to the "xx" and "yy" parts.

Tasks related to accounting work are hierarchically divided into three stages: "high-level tasks," "mid-level tasks," and "low-level tasks" depending on the content of the accounting work. In other words, the content of accounting work is divided into parent tasks (high-level tasks), child tasks (middle-level tasks), and grandchild tasks (low-level tasks). As a result, there are multiple mid-level tasks within a high-level task, and multiple sub-tasks within each mid-level task. However, depending on the content of a mid-level task, there may be no sub-tasks. The task hierarchy is not limited to three stages, and may be set to two or four or more, and may be changed as appropriate to suit the accounting work of the industry to which the user belongs.

Here, the task management table stores the task names for each of the higher-level tasks, mid-level tasks, and lower-level tasks. In FIG. 5A, for convenience, the higher-level task names are listed as "A1" and "A2," the mid-level tasks as "B1," "B2," etc., and the lower-level tasks as "C1," "C2," etc., but in reality, task names related to the contents of the accounting work are stored in advance.

"Higher level tasks" are tasks that are set as a broad concept, taking into consideration the content and progress of the accounting procedures. For example, "financial results summary," "financial statements," "business reports," "securities reports," and "notice of meeting" are set as higher level tasks. Note that these tasks are typical tasks that are generally known in accounting procedures, but the types of higher level tasks are not limited to the above five.

"Mid-level tasks" are tasks that are set as intermediate tasks that are necessary to execute higher-level tasks, taking into consideration the content of the accounting work and their relationship with the higher-level tasks. In particular, "middle-level tasks" are defined as tasks related to preparation for higher-level tasks, preparation of necessary documents, audits, etc. For this reason, when all mid-level tasks are completed, the higher-level tasks that are located above the mid-level tasks will also be completed. Also, for each higher-level task, there may be mid-level tasks with the same name, but the content of the mid-level tasks themselves will differ depending on the content of the higher-level tasks. In other words, even if the task names of mid-level tasks are the same, the lower-level tasks included in the mid-level tasks will be different.

For example, if the higher-level task is "Financial results summary", "Preparation", "Create summary information", "Create attachments", "Internal review", "Check with printing company", "Correction", "Check with audit corporation", "Approval by meeting body", and "Disclosure" are set as mid-level tasks. If the higher-level task is "Financial statements", "Preparation", "Create financial statements", "Preparation of supplementary details", "Preparation of consolidated financial statements", "Audit by audit corporation", "Approval by meeting body", and "Disclosure" are set as mid-level tasks. If the higher-level task is "Business report", "Preparation" and "Create business report" are set as mid-level tasks. If the higher-level task is "Securities report", "Preparation", "Create securities report", "Audit by audit corporation", "Internal review", "Check with printing company", "Correction", "Audit by audit corporation", "Approval by meeting body", and "Disclosure" are set as mid-level tasks. If the higher-level task is "Convocation notice", "Preparation", "Create convocation notice", "Internal review", "Check with printing company", "Correction", "Audit by audit corporation", "Audit report", "Approval by meeting body", "Print request", and "Dispatch" are set as mid-level tasks. These tasks are also typical tasks that are commonly known in accounting procedures, but mid-level tasks are not limited to these.

"Lower-level tasks" are tasks that are set with detailed positioning necessary to execute the mid-level tasks, taking into consideration the content of the accounting work and their relationship to the mid-level tasks. In particular, "lower-level tasks" are set as tasks that indicate mid-level tasks in detail and specifically, and specify details about documents, responses to documents, various required materials, etc. For this reason, when all lower-level tasks are completed, the mid-level tasks that are located above the lower-level tasks will also be completed.

For example, if the higher-level task is "Financial results summary" and the mid-level task is "Preparation," then the lower-level tasks will be "Certificate of full historical matters," "Organization chart," "Budget documents," "Consolidated balance sheet, Consolidated reclassification table," "Dividend status documents," etc. If the higher-level task is "Financial statements" and the mid-level task is "Preparation," then the lower-level tasks will be "Financial results processing policy table," "Treasury stock ledger," "Accounting regulations," "Capital relationship diagram," "List of affiliated companies," etc. If the higher-level task is "Business report" and the mid-level task is "Preparation," then the lower-level tasks will be "List of affiliated companies," "Personnel list," "Loan ledger," "Shareholder list," "Articles of incorporation," etc. If the higher-level task is "Securities report" and the mid-level task is "Preparation," then the lower-level tasks will be "History documents," "Employee status documents," "Major shareholder list," "Business content documents," "Stock status documents," etc. If the upper task is "Convocation notice" and the mid-level task is "Preparation," then "List of resolutions" is set as the lower-level task, and if the mid-level task is "Create convocation notice," then "Resolutions," "Reports," and "Create convocation notice" are set as lower-level tasks. Note that the above lower-level tasks are merely representative examples, and in reality, a huge number of lower-level tasks, over 400, are set.

"Related task ID" is the ID of a related task when there is a relationship between the contents of lower level tasks. In other words, when there is a strong business relationship between the lower level tasks, there is common work or materials, or the work flows are similar, the "Related task ID" field stores the ID of other related tasks, and if there are no other related tasks, it is left blank. Note that for higher level tasks and mid-level tasks, the content of the tasks is set to be broad, so related task IDs are not stored.

As shown in Figure 5A, related task IDs may be stored when there is a common mid-level task. For example, the related task ID column for IDs "xx-006" and "xx-007" stores the other party's ID to indicate that the tasks are related. This makes it possible to confirm the relationship between tasks IDs "xx-006" and "xx-007", providing information for deciding whether to assign the same person in charge to both tasks, for example.

In addition, even if the higher-level task and the mid-level task do not have anything in common, the related task ID may be stored. For example, the ID of the other party is stored in the related task ID column for the IDs "xx-006" and "yy-002" to indicate that the tasks are related to each other. In other words, even if the work content is completely different or the documents to be created are completely different, the related task ID may be stored after a comprehensive judgment is made on the commonality of the work or documents. Even in such cases, it provides information for deciding whether to assign the same person to both tasks, and is extremely useful information in situations where the relationship is thought to be low just by checking the task names of the lower-level tasks.

"Responsible department" is information about the department that will actually perform each task. Since this is a settlement-related task, the "Responsible department" stores the name of the department that is expected to perform the settlement work, such as IR, accounting, or general affairs. However, depending on the documents or materials to be prepared, the technical department or manufacturing department may be in charge. Note that, since the actual department name may differ from the name stored in "Responsible department" depending on the user, or may not exist, the information stored as "Responsible department" can be changed as appropriate using user information, and may even be excluded from the initial settings. In addition, for higher-level tasks, the content of the task is set to be broad, and it is possible that multiple departments may handle the task, so the setting is such that the "Responsible department" is not stored.

"Possible Positions" is information about the positions required to actually perform each task. "Possible Positions" stores information that limits who can perform the task depending on the importance of the task, such as general position or above, chief or above, section manager or above, department manager or above, etc. Note that depending on the user, the actual position name may differ from the name stored in "Possible Positions" or may not exist, so the information stored as "Possible Positions" can be changed as appropriate using user information, and may even be excluded from the initial settings. In addition, for higher-level tasks, the content of the task is set to be broad, and it is possible that multiple people will be in charge of the task, so the setting is such that "Possible Positions" are not stored.

"Document name" is information about the document that will be created in whole or in part by executing each task. For convenience, "D1", "D2", "D3", "D4", and "D5" are listed in FIG. 5A, but in reality, document names related to the contents of the accounting work are pre-stored. For example, document names included in the names of higher-level tasks, mid-level tasks, or lower-level tasks are applicable. Specifically, "Certificate of all historical matters", "Organizational chart", "Accounting documents", "Business report", "Securities report", "Notice of meeting", etc. will be pre-stored.

"Standard work period" is information about the industry standard work hours required to perform each task. For this reason, the "standard work period" column stores the time (number of days) generally required to complete a task, rather than information that takes into account the ability or experience of the person performing the task. Here, since mid-level tasks are completed by performing all lower level tasks, the standard work period for a mid-level task is greater than the total standard work time for the lower level tasks contained in that mid-level task. Note that the content of higher level tasks is set to be broad, so the "standard work period" is not stored.

The "offset value" is set to set and manage the schedule for the execution of each task. The "offset value" is set in advance for each task, taking into account, for example, the standard work period of mid-level tasks and lower-level tasks. The setting is performed appropriately by the administrator of the server device 200, and the user is not involved. By using such an "offset value," when responding to a change in the company-specified deadline (first deadline), when generating a new schedule for the next year, or when duplicating a schedule, it is possible to easily set the work period, start date, and end date by taking into account holidays (non-working days) such as Saturdays and Sundays, unlike simply setting the work period.

"Person in Charge" is information about the name of the person who actually carries out each task. "Person in Charge" is information that is automatically set and stored when a schedule management request is made from the user terminal device 100 to the server device 200. However, depending on the user's situation, there may not be a suitable person when the request is made, in which case "not assigned" is stored. Furthermore, when the server device 200 receives additional information about the person in charge from the user terminal device 100, the "Person in Charge" is newly set or updated. Note that for higher-level tasks, the content of the task is set broadly, and the setting is such that the "Person in Charge" is not stored.

"Status" is progress information for each task. Either "Not started," "In progress," or "Completed" is stored in the "Status" column. When task schedule management begins, "Not started" is stored as the status of each task, but depending on progress reports received from the user terminal device 100, the stored information will change to "In progress" or even "Completed." Note that for higher-level tasks, the task content is set to be broad, and the setting is such that "status" is not stored.

The "start date" is information on the start date of each task, and the "end date" is information on the end date of each task. The "start date" and "end date" are information that are automatically set and stored when the user terminal device 100 requests the server device 200 to manage the schedule. Here, the "end date" that is automatically set is the planned end date, which is the deadline, and the "start date" that is automatically set is also the planned start date calculated from the planned end date and the work period. However, the dates of the "start date" and "end date" are updated according to the progress report received from the user terminal device 100. Here, since a mid-level task is completed by executing all lower level tasks, the start date of the mid-level task is the earliest date of the lower level tasks included in the mid-level task, and the end date of the mid-level task is the latest date of the lower level tasks included in the mid-level task. Note that the content of the upper level tasks is set broadly, and the "start date" and "end date" are not stored.

"Work details" is detailed information required for the work of executing each task. "Man-hours" is information on the actual time or number of days required to execute and complete each task. "Notes" is information on matters that require attention when executing each task, and information that accompanies task execution. In any of the information columns, when the server device 200 receives updated information on each task from the user terminal device 100, the received information is stored. Note that for higher-level tasks, the task content is set broadly, and "Work details", "Man-hours" and "Notes" are not stored.

5B is a diagram conceptually illustrating a person in charge management table stored in the server device 200 according to an embodiment of the present disclosure. The person in charge management table includes information on employees of the user company. Specifically, information on "person in charge," "job type," "position," and "past history of work" is stored. Here, "person in charge" is the same information as "person in charge" in the task management table of FIG. 5A, and is also information that links the task management table and the person in charge management table. "Job type" is information on the department name to which the person in charge of the task belongs, and department names such as "accounting," "general affairs," or "IR" are stored. In addition, "position" is information on the position of the person in charge of the task, and position names such as "department manager," "section manager," "supervisor," and "general" are stored. This information is updated when there is a personnel transfer or department change in the user company.

"Past history of work" refers to information about the IDs of tasks that each person in charge has been in charge of up until now. In other words, "past history of work" stores information about tasks that each person in charge has experience with. "Past history of work" is updated when the accounting procedures for each fiscal year or each period of each fiscal year are completed. This makes it possible to determine the most suitable person in charge of a task, either automatically or manually, by taking past performance into consideration. Even if there is no past performance of the same task, by combining this with the information on the related task ID described above, it becomes possible to automatically or manually assign someone with experience in related tasks as the person in charge, thereby expanding the range of people to choose from. In other words, "past history of work" is very useful information when assigning tasks.

In addition, the memory 211 may store a management table that combines the data of the two tables, rather than storing the above-mentioned task management table and person in charge management table separately. In this case, the processor 212 of the server device 200 may appropriately generate a table composed of necessary information from the one table.

In addition to the task management table and the person in charge management table described above, the memory 211 of the server device 200 stores the settlement date of each user and the legal deadline calculated from the settlement date. The settlement date of the user is set by the user when the user starts using the system (i.e., the initial setting stage). For example, information related to the settlement date may be sent from the user terminal device 100 to the server device 200 and automatically stored in the server device 200, or may be set in the server device 200 after the administrator of the server device 200 receives separate contact from the user. The legal deadline may be set, for example, as 45 days after the settlement date, but may vary depending on various conditions. Note that some users may specify the settlement month, and in such a case, the server device 200 may register, for example, the last day of the settlement month as the settlement date and calculate the legal deadline from the last day.

6. Processing sequence executed by the processing system 1 Fig. 6A is a diagram showing a processing sequence executed between the user terminal device 100 and the server device 200 according to an embodiment of the present disclosure. Figs. 6B, 6C, and 6D are diagrams showing examples of screens output to the user terminal device 100 according to an embodiment of the present disclosure. Below, the flow of processing and information provided to the user will be described with reference to each drawing.

As shown in FIG. 6A, the user terminal device 100 executes a startup process to start a request for task schedule management (S11). Specifically, the processor 112 of the user terminal device 100 displays a login screen on a display connected via the output interface 111. The processor 112 of the user terminal device 100 then receives a login ID and password (hereinafter, login information) entered by a terminal operator (user's employee) and transmits the received login information to the server device 200 via the communication interface 114. That is, the processor 112 of the user terminal device 100 makes a login request to the processing system 1 to the server device 200 (T11).

When the server device 200 receives login information via the communication interface 214, the processor 212 of the server device 200 executes authentication processing (S12). Specifically, the processor 212 of the server device 200 compares the received login information with the user information stored in the memory 211 to determine whether the two pieces of information match. The processor 212 of the server device 200 transmits the authentication result to the user terminal device 100 via the communication interface 114 (T12).

When the user terminal device 100 receives an authentication result approving the login request via the communication interface 114, a screen for entering the company-specified due date appears on the display of the user terminal device 100. On the other hand, when an authentication result stating that the login request is not approved is received via the communication interface 114, a screen requesting the user to re-enter login information appears on the display of the user terminal device 100. Here, we will naturally assume that the login request is approved.

After a screen requesting input of the in-house designated due date is displayed on the user terminal device 100, the terminal operator inputs the in-house designated due date that has been determined in advance within the company as user setting information (S13), and the processor 112 of the user terminal device 100 receives the in-house designated due date. The processor 112 of the user terminal device 100 then transmits the received in-house designated due date as setting information to the server device 200 via the communication interface 114 (T13). This means that a request for schedule management of tasks related to accounting work has been made from the user terminal device 100 to the server device 200.

When the server device 200 receives the setting information via the communication interface 214, the processor 212 of the server device 200 stores the setting information in the memory 211 (S14). The processor 212 of the server device 200 then reads the program stored in the memory 211, executes the schedule creation process using the setting information, and creates the schedule information by setting the work period for each task by counting backwards from the in-house specified due date (S15). The specific schedule creation process will be described later with reference to Figures 7 and 8. Here, the schedule information includes a schedule table of all tasks shown in Figure 6B, a list of tasks shown in Figure 6C, and detailed information on each task shown in Figure 6D, and the work period of the task is displayed in a dashboard format. The schedule information is displayed on the display of the user terminal device 100, and will be described later.

Then, the processor 212 of the server device 200 transmits the created schedule information to the user terminal device 100 via the communication interface 214 (T14). In other words, a response to the request for schedule management of the tasks related to the accounting work is sent from the server device 200 to the user terminal device 100.

The processor 112 of the user terminal device 100 displays the schedule information received via the communication interface 114 on a display unit such as a display via the output interface 111 (S16). Specifically, as shown in FIG. 6B, a schedule table is displayed in which the work period is displayed as a horizontal bar graph on a calendar for each task (higher-level task, middle-level task, lower-level task). The schedule table also displays the task name, start date, end date, status, and person in charge. Also, in FIG. 6B, the higher-level task "Convocation Notice" is selected, and each of the middle-level tasks of the "Convocation Notice" is also selected, and each of the lower-level tasks is also displayed. In other words, when the "higher-level task" and "middle-level task" displayed in the task name column are clicked with the mouse 115a, the tasks located below the clicked task are displayed.

In the schedule information received in S16, the start date and end date columns show the planned start date and planned end date that were automatically set in S15. In addition, in the person in charge column, the name of the person in charge is displayed for the parts that were automatically set in S15, and for parts that were not automatically set, "no applicable person" is displayed. Meanwhile, the status column is not automatically determined in S15, and the initial status of "not started" is uniformly displayed.

As mentioned above, for higher-level and mid-level tasks, the higher-level tasks are completed when all tasks in the lower layers are completed, so the bar graphs showing the work periods for higher-level and mid-level tasks are displayed with the bar graphs showing the work periods for the tasks in the lower layers connected together. This makes it easy to grasp the detailed work periods for each lower-level task, while also making it easy to grasp the work periods for comprehensive tasks that are higher-level and mid-level tasks positioned in the upper layers. In other words, it becomes possible to simultaneously and easily grasp not only the individual tasks that each person in charge should be aware of, but also the overall task schedule that managers and others should be aware of.

Information displayed on the display of the user terminal device 100 includes a task list as shown in FIG. 6C. For example, the display of FIG. 6B may be switched to the display of FIG. 6C by switching tabs, and the task list may be displayed alongside the schedule of FIG. 6B. As shown in FIG. 6C, the task list display can display all tasks, and it is also possible to display only some of the tasks by setting conditions. Specifically, the display allows selection of the fiscal year, person in charge, document name, accounting period, status, start date, end date, and update period. It is also possible to perform a keyword search for tasks by entering a keyword.

Then, below the display for selecting search conditions, a list of tasks is displayed as the search results. Display items for a task include, for example, the task name, status, person in charge, and document name, but are not limited to these, and the display items for a task can be selected and changed as appropriate by the terminal operator of the user terminal device 100. For example, the terminal operator of the user terminal device 100 can extract tasks that have not been assigned a person in charge or tasks that have not progressed (tasks that have not been started), making it easy to assign new people in charge and review schedules, etc.

Furthermore, the information displayed on the display of the user terminal device 100 includes task details as shown in FIG. 6D. For example, by selecting the name of each task in FIG. 6C, the task details screen of FIG. 6D may be displayed. Also, by switching tabs, the display of FIG. 6B or FIG. 6B may be switched to the display of FIG. 6D, and the task details may be displayed in addition to the displays of FIG. 6B and FIG. 6C. As shown in FIG. 6D, the display of task details includes the name of the selected task (audit report), and above the name of the task, a display of the hierarchy related to the task (return to list > prepare securities report > audit report) is included. This makes it easy to check the current task, and further makes it easy to transition from the selected task to other tasks and task lists.

Below the name of the selected task, the status, the person in charge, the start date, the end date, the work details, and the work tasks are displayed. The status, the person in charge, the start date, and the end date are linked to the entries in the schedule table in FIG. 6B, and each piece of information can be changed as appropriate. The work details and work tasks columns are fields that are entered by the terminal operator of the user terminal device 100 as the actual task progresses.

The task details information includes related task information, and the name, work period, person in charge, and status of the task related to the selected task are displayed. That is, information related to the related task ID shown in FIG. 5A (i.e., the content of the related task) is displayed as detailed information on the selected task. This makes it easy to grasp not only the status of the selected task, but also the status of related tasks, and the terminal operator of the user terminal device 100 can easily assign a new person in charge to a task that has not been assigned a person in charge or a task that has not progressed (a task that has not been started) and review the schedule, etc. In particular, it becomes possible to grasp the cross-sectional progress status of tasks, and schedule management of higher-level tasks and mid-level tasks can be achieved with high accuracy and ease.

When the terminal operator checks the schedule information displayed on the display of the user terminal device 100 and determines that there is content to be added or modified (additional setting information), the terminal operator inputs the additional setting information (S17), and the processor 112 of the user terminal device 100 receives the additional setting information. The additional setting information includes, for example, an unspecified person in charge and an automatically set start date and end date for a task. The processor 112 of the user terminal device 100 then transmits the received additional setting information to the server device 200 via the communication interface 114 (T15). As a result, a request to change the settings for the schedule management of tasks related to the accounting process is executed from the user terminal device 100 to the server device 200.

When the server device 200 receives the additional setting information via the communication interface 214, the processor 212 of the server device 200 stores the additional setting information in the memory 211 (S18). As a result, the request for changing the settings of the schedule management of the task related to the accounting work is approved, and the user starts schedule management. If there is no additional setting information, the schedule management of the task starts from the stage of S16. If the start date and end date of the task are modified, the processor 212 of the server device 200 may perform the schedule creation process again. That is, the processor 212 of the server device 200 may take into account the modified start date or end date of the task, determine the need to modify the work period for other tasks, and reset the work period for one or more tasks. In this case, the processor 212 of the server device 200 may compare the start date and end date before the modification with the modified start date and end date to modify the offset value.

After that, as the task processing progresses, update information for the task is input by the terminal operator (S19), and the processor 112 of the user terminal device 100 receives the update information. The update information includes, for example, information such as the date the task processing actually started and ended, and the newly assigned person in charge. The processor 112 of the user terminal device 100 then transmits the received update information to the server device 200 via the communication interface 114 (T16). As a result, a request to update the schedule management of the tasks related to the accounting work is executed from the user terminal device 100 to the server device 200.

When the server device 200 receives the update information via the communication interface 214, the processor 212 of the server device 200 stores the update information in the memory 211 (S20). This approves the request to update the schedule management of the tasks related to the accounting process, and the schedule management is updated to the latest state.

7. Processing Flow Executed in Server Device 200 The processing flow executed in server device 200 for the schedule creation process (S15) shown in FIG. 6A will now be described in detail.

FIG. 7A is a diagram showing a processing flow executed in the server device 200 according to an embodiment of the present disclosure. The processing flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211. FIG. 7B is a diagram showing a schematic overview of an example of a schedule creation process executed in the server device 200 according to an embodiment of the present disclosure.

As shown in FIG. 7A, the processor 212 determines whether or not it has received setting information including an internally designated deadline from the user terminal device 100 via the communication interface 214 (S31). If it has not received the setting information (S31: No), this processing flow ends. On the other hand, if it has received the setting information (S31: Yes), the processor 212 sets the internally designated deadline included in the setting information as the internally designated deadline and stores it in the memory 211 (S32). As shown in FIG. 7B, the following description assumes that March 31 is initially set as the settlement date, the legal deadline that is the deadline for the company from the settlement date is automatically set to May 15, and March 10 is set as the internally designated deadline (designated deadline) as an earlier date than the legal deadline.

Here, the external deadline is a date that is different from an internal deadline and is a legally required date or a date that is notified or announced externally. In other words, the processor 212 sets the external deadline as the final completion date for the accounting process, while setting the internally specified deadline as the internal deadline that must be observed within the company.

Next, the processor 212 subtracts an offset value set in advance for each task from the stored in-house specified due date, and calculates and sets the end date, which is the in-house deadline for each task, for each task (S33). Specifically, the processor 212 subtracts the offset value for each task stored in the memory 211 from the received in-house specified due date, and sets the end date of each task to be earlier than the in-house specified due date, so that all tasks are completed by the in-house specified due date. For example, as shown in FIG. 7B, for the task of receiving the audit report, the processor 212 subtracts the offset value of 10 days set from the in-house specified due date of March 10, and sets the end date, which is the deadline for the task, to February 24. Similarly, the processor 212 subtracts the offset value of 12 days set from the in-house specified due date of March 10, and sets the end date, which is the deadline for the task, to February 22 for the auditor's audit task. Here, the task of the auditor's audit cannot be executed unless it is completed before the audit report is received, but since the number of days considering the order of task completion is set as the offset value, an appropriate end date can be set simply by subtracting the offset value from the in-house designated due date. Here, since the offset value is set to include only actual working days (Monday to Friday), the end date to be set is set even earlier. Specifically, February 25th (Saturday) and February 26th (Sunday) are holidays, so both days are excluded from the offset, and the end date of the task of receiving the audit report is February 24th, 12 days before the in-house designated due date of March 10th. In order to include only the actual working days, general calendar information is stored in the memory 211, and the processor 212 uses the calendar information to set the work period.

Next, the processor 212 sets the planned work period (work period at the time of initial setting) for each task from the end date of each task set in S33 and the standard work period of each task stored in the memory 211, and stores it in the memory 211 (S34). Specifically, the processor 212 sets the work period for the audit report receipt task to 1 day, February 24th, based on the set end date of February 24th and the standard work period of 1 day stored in the memory 211. Similarly, the processor 212 sets the work period for the auditor audit task to 6 days, from February 17th to February 22nd, based on the set end date of February 22nd and the standard work period of 4 days stored in the memory 211. Here, the setting of the work period is set to target only actual working days, as in the case of the offset value, so that if a holiday is included in the work period, the work period is set to be longer than the standard work period. In an embodiment of the present disclosure, the end date calculated in the above process and the start date, which is the first day of the work period, are stored in the start date and end date columns of each task in FIG. 5A.

Next, the processor 212 generates dashboard information of the work period of each set task, and stores it in the memory 211 (S35). That is, in the stage of S34, the processor 212 sets only the numerical data of the work period of each chest, and generates information related to the graphical representation of the schedule as shown in FIG. 7B using the numerical data. The processor 212 also executes a process related to the automatic assignment of a person in charge of each task, and stores it in the memory 211 as schedule information (S36). For example, the processor 212 performs the automatic assignment based on the related task ID, responsible department, available position, and past assignment history information stored in the memory 211. This automatic assignment will be described later with reference to FIG. 8.

Then, the processor 212 transmits the schedule information with the person in charge automatically assigned to the user terminal device 100 via the communication interface 214 (S37).

Next, a detailed process flow for S36 will be described with reference to FIG. 8. FIG. 8 is a diagram showing a process flow executed in the server device 200 according to an embodiment of the present disclosure. This process flow is mainly performed by the processor 212 of the server device 200 reading and executing a program stored in the memory 211.

First, the processor 212 selects one task to which a person in charge is to be assigned from the tasks stored in the memory 211 (S301). The tasks to be selected are mid-level tasks and lower-level tasks, so for example, the processor 212 selects tasks in the order of ID, excluding higher-level tasks.

Then, the processor 212 calculates the number of people available to handle the selected task, taking into account the department and position (S302). Specifically, the processor 212 counts the target persons based on the information on the person in charge, the responsible department, and the corresponding available position stored in the memory 211. If the number of people available to handle the task is one, the processor 212 automatically assigns the relevant person as the person in charge (S307) and ends this processing flow. On the other hand, if the number of people available to handle the task is zero, the processor 212 selects no assignment (S308) as automatic assignment to the task is not possible, and ends this processing flow.

If there are multiple applicable persons calculated taking into consideration the department and position, the processor 212 determines whether the person with the most number of people in the past history of being in charge of the task selected in S301 is limited to one person (S303). Specifically, the processor 212 counts the number of target persons based on the information of the person in charge, including the past work history, stored in the memory 211. If there is only one applicable person, the processor 212 automatically assigns that person as the person in charge (S307), and ends this processing flow.

If the most frequent person in charge in the past history of responsibility is zero or more, the applicable person has not been narrowed down to one person, so the processor 212 judges whether a related task has been registered for the task selected in S301 (S304). Specifically, the processor 212 judges whether the ID of another task is stored in the memory 211 as a related task ID for the selected task. If a related task is registered, the processor 212 judges whether there is one person in charge of the related task (S305). Specifically, the processor 212 judges whether there is one applicable person based on the quantity of related tasks extracted in S304 and the information of the person in charge automatically assigned to each related task. Note that the processor 212 may execute this process for related tasks, including not only the person automatically assigned at the current stage, but also information on the past history of responsibility. If there is one applicable person, the processor 212 automatically assigns that person as the person in charge (S307) and ends this processing flow.

On the other hand, if no related tasks are registered for the selected task (S304: No), and if there are zero or multiple people in charge of the related tasks (S305: No), the number of applicable persons has not been narrowed down to one, so the processor 212 considers the job title, past history of work, and related tasks, and narrows down the number of applicable persons to one person based on a comprehensive judgment (S306). The processor 212 then automatically assigns the applicable person as the person in charge (S307), and ends this processing flow. For example, by setting weights in advance for the job title, past history of work, and related tasks, the processor 212 may extract the most suitable person as the applicable person based on the numerical value related to the weight, or may simply select an employee with a high job title. Furthermore, the accuracy of the comprehensive judgment may be improved using techniques such as machine learning or deep learning.

The above-mentioned automatic assignment flow of personnel is merely one example, and additional judgment items may be added, or some judgment items may be deleted. For example, automatic assignment of personnel may be performed based on a comprehensive judgment of department, position, and past history of work, without taking into account judgment regarding related tasks.

8. Summary of the embodiment of the present disclosure The server device 200 according to the embodiment of the present disclosure is a processing device that creates a schedule for a plurality of tasks related to the settlement work, and includes at least one processor 212 that executes a process for creating the schedule. Here, the processor 212 is configured to execute a process for executing ...

Furthermore, in the server device 200 according to an embodiment of the present disclosure, the processor 212 outputs detailed information for each task to the display, and the detailed information includes related task information that is set when the tasks are related to each other. Here, the related task information is also set for different documents related to the closing work. With this configuration, tasks related to the closing work are linked together, and when manually assigning a person in charge of a task, it is possible to extract a wide range of candidate persons and easily select the most suitable person in charge.

Furthermore, in the server device 200 according to an embodiment of the present disclosure, the processor 212 automatically sets a person in charge for each task. Here, the processor 212 may automatically assign a person in charge based on the person in charge's department, position, past person in charge information for the task, or related task information. With this configuration, it becomes possible to extract a wide range of candidate persons for each task and automatically select the most suitable person in charge.

When a processing program in the server device 200 according to an embodiment of the present disclosure receives a specified deadline for accounting work, it causes the processor 212 to function in such a way that, upon receiving the specified deadline for accounting work, it subtracts a preset offset value from the specified deadline to set an end date that is the completion deadline for each task, sets the work period for each task from the set end date and the standard work period set for each task, and outputs multiple tasks on the display based on the work periods set for the multiple tasks. Such a program allows the user to receive a task schedule optimized to suit the circumstances of his or her company, and easily performs processing related to the tasks for the company's accounting work. In particular, the user can easily grasp the tasks as a whole and each individual task.

The processing method by the server device 200 according to an embodiment of the present disclosure is executed by the processor 212, and includes the steps of, upon receiving a specified deadline for accounting work, subtracting a preset offset value from the specified deadline to set an end date that is the deadline for each task, setting a work period for each task from the set end date and a standard work period set for each task, and outputting multiple tasks on a display based on the work periods set for the multiple tasks. With this method, the user can receive a task schedule optimized to suit the situation of their company, and can easily carry out processing related to the tasks for the company's accounting work. In particular, the user can easily grasp the tasks as a whole and each task individually.

9. Modifications In the above-mentioned embodiment, it is assumed that the in-house specified due date is not changed, but the in-house specified due date may be changed during the work of each task. In this case, the specified in-house due date is reset and the schedule creation process is performed again. Even in such a case, since an offset value is set for each task, the end date of each task can be easily set by subtracting the offset value from the in-house specified due date, which is the specified deadline, and further, it is easy to recreate a schedule that takes into account holidays such as Saturdays and Sundays. In addition, at this time, the work period of the completed task may be taken into account and a schedule for the uncompleted task may be created.

In the above embodiment, the end date of each task is set by subtracting an offset value set for each task from the in-house specified due date, and the work period for each task is set from the end date and the standard work period for each task, but the method of setting the work period is not limited to this. Specifically, the start date, which is the deadline for starting each task, may be set by subtracting the offset number of days set for each task from the in-house specified due date, and the work period for each task may be set from the start date and the standard work period for each task. In other words, if a numerical value that includes the standard work period is set in the offset value, the work period for each task may be set after the planned start date for each task is set. In other words, the work period for a task may be set based on the start date, which is the deadline for starting the task. Even in such a case, since an offset value is set for each task, the end date of each task can be easily set by subtracting the offset value from the in-house specified due date, which is the specified deadline, and it is also easy to recreate a schedule that takes into account holidays such as Saturdays and Sundays.

The processes and procedures described in this specification can be realized not only by those explicitly described in this disclosure, but also by software, hardware, or a combination of these. Specifically, the processes and procedures described in this specification are realized by implementing logic equivalent to the processes in media such as integrated circuits, volatile memory, non-volatile memory, magnetic disks, optical storage, etc. In addition, the processes and procedures described in this specification can be implemented as computer programs and executed by various computers including terminal devices and server devices.

Even if it is described that the processes and procedures described in this specification are performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, multiple software, multiple components, and/or multiple modules. Furthermore, even if it is described that various information described in this specification is stored in a single memory or storage unit, such information may be stored in multiple memories provided in a single device or in multiple memories distributed across multiple devices. Furthermore, the software and hardware elements described in this specification may be realized by integrating them into fewer components or by breaking them down into more components.

100 User terminal device 200 Server device (processing device)

Claims

A processing device including at least one processor that executes a process for creating a schedule of a plurality of tasks related to a settlement operation,
The at least one processor:
When a designated deadline for the settlement work is received, a preset offset value is subtracted from the designated deadline to set a start deadline or an end deadline for the work period for each task;
setting a work period for each of the tasks based on the set start deadline or end deadline and a standard work period set for each of the tasks;

outputting the plurality of tasks on a display based on the work periods set for the plurality of tasks;
2. A processing device configured to perform processing for:
The at least one processor outputs detailed information for each of the tasks to the display;
The processing device according to claim 1 , wherein the detailed information includes related task information that is set when tasks are related to each other.
The processing device according to claim 2, wherein the related task information is also set for different documents related to the accounting process.
The processing device according to claim 3, wherein the at least one processor automatically assigns a person in charge to each of the tasks.
The processing device according to claim 4, wherein the at least one processor automatically assigns the person in charge based on the department and position of the person in charge.
The processing device according to claim 4 or 5, wherein the at least one processor automatically assigns tasks based on past information about the person in charge of the tasks.
The processing device according to claim 4 or 5, wherein the at least one processor automatically assigns tasks based on the related task information.
The processing device according to claim 1, wherein the at least one processor resets the start deadline or the end deadline for each task when the change in the specified deadline is received.
The processing device according to claim 1, wherein the offset value is set for each task.
In a computer having at least one processor, the at least one processor is
When a designated deadline for a settlement operation is received, a preset offset value is subtracted from the designated deadline to set a start deadline or an end deadline for the work period for each task;
setting a work period for each of the tasks based on the set start deadline or end deadline and a standard work period set for each of the tasks;
outputting the plurality of tasks on a display based on the work periods set for the plurality of tasks;
A processing program that makes it function as such.
A processing method executed by at least one processor in a computer having the at least one processor, comprising:
When a first deadline related to a settlement operation is received, a preset offset value is subtracted from the designated deadline to set a start deadline or an end deadline of a work period for each task;
setting a work period for each task based on the set start deadline or end deadline and a standard work period set for each task;

outputting the plurality of tasks on a display based on the work periods set for the plurality of tasks;
A processing method comprising: