Administrative management system, administrative management method, and computer program

Abstract

To provide a new technique for supporting administrative activities.SOLUTION: An administrative management system, wherein an administrative object holds a budget item and a budget amount for each stage of budget compilation, the administrative object being registered in association with another administrative object related to the same administrative activity along a chain, the administrative management system comprising: Referring to the budget amount and the budget subject of a registered administrative object related to a settled budget specified based on the budget compilation stage, displaying the registered administrative object as a candidate for data of the new administrative object, and registering the new administrative object in association with the registered administrative object related to the same administrative activity along the same line.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an administrative management system, an administrative management method, and a computer program for supporting administrative projects. [Background technology]

[0002] Administrative organizations, including local governments, set policy systems such as policies, measures, and administrative projects, and execute administrative projects within the budgets secured for those systems. Policies and projects are evaluated item by item every year, and review meetings are held to determine next year's budget and whether the project will continue in the following year. In this way, information on policies, measures, and projects is used to make decisions in administrative activities.

[0003] Patent Document 1 discloses technology that aims to resolve the problem of local government financial planning being conducted from a macro perspective, while budget assessments for individual administrative projects are conducted from a micro perspective, and that the two are not linked. This technology makes it possible to maintain consistency between individual plans and overall strategies by establishing rules, making the creation of revenue and expenditure plans for individual administrative projects more detailed and computerizing them, and by linking the financial planning of the local government as a whole with the management and evaluation of administrative projects, thereby enabling long-term financial estimates based on project accumulation. [Prior art documents] [Patent documents]

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

[0005] In the execution of budgets in administrative activities, when budgets become necessary due to unexpected circumstances such as the occurrence of a sudden natural disaster, it becomes necessary to register new administrative objects such as supplementary budgets. In such cases, there has been no support available to easily register administrative objects.

[0006] In view of the above-mentioned problems, an object of the present invention is to provide a novel technology for supporting administrative activities. [Means for solving the problem]

[0007] [1] An administrative management system comprising: Administrative objects relating to continuing administrative activities are registered in a series associated with other corresponding administrative objects relating to the same administrative activity; When a request for the creation of a new administrative object corresponding to an already registered administrative object but at a different position in the series is received for a continuing administrative activity, registering the new administrative object based on the registered administrative object in association with the registered administrative object along the series; Administrative management system. [2] The series is related to budget type and / or execution year, [1] The administrative management system described in [1]. [3] When a request for generating the new administrative object is received, an input screen for data items of the new administrative object is displayed in which one or more data items are preset in the input field based on the registered data items included in the registered administrative object. [1] The administrative management system described in [1]. [4] Administrative objects contain information about the people who carry out administrative activities. When a request for generating a new administrative object is received for an ongoing administrative activity, a person in charge of the new administrative object is registered based on the registered administrative object. [1] The administrative management system described in [1]. [5] The administrative objects are registered in association with each other so as to be aligned along the series; the new administrative object is registered in direct association with the previously registered administrative object in the previous position in the sequence; [1] The administrative management system described in [1]. [6] An administrative management system for managing budget information related to administrative activities, For each project in administrative activities, a system item including a subject and the amount related to the system item are registered in association with each other; When making a new supplementary budget request for the project for which the items and amounts related to the initial budget or the initial budget and the supplementary budget have been registered, display candidates for items for which the supplementary budget request will be made based on the registered items, An administrative management system that registers the amount related to the supplementary budget request in association with the subject selected from the candidates. [7] The above system items include budget item system items, settlement item system items, and public accounting item system items. [6] The administrative management system described in [8] For the business, one or more individual expenditure items are registered as the system items, each of which is uniquely associated with a budget item system item, a settlement item system item, and a financial source; In displaying candidates in the supplementary budget request, candidates for the subject are displayed for each individual expense item. [6] or [7], the administrative management system. [9] Based on the individual expenditure items related to the registered approved budget, the individual expenditure items are displayed in a list as candidates for the budget items for which the supplementary budget request is made. [8] The administrative management system described in [8].

[10] Regarding the supplementary budget request, accept the registration of new items and register them in association with the amounts related to the new items. [8] The administrative management system described in [8].

[11] The subjects to be registered are budget subjects, The amount to be registered includes the requested amount, the assessed amount, and the estimated amount. Based on the registered items and amounts, the requested amount, assessed amount, and provisional amount are displayed for each specific item. [8] The administrative management system described in [8].

[12] When making a supplementary budget request for a project for which budget information relating to the initial budget and supplementary budget has been registered, the registered subjects for the same fiscal year are displayed as candidates for the budget subject for which the supplementary budget request is made, based on the registered subjects for the same fiscal year. An administrative management system according to any one of [6] to

[11] .

[13] For the project, one or more individual expenditure items indicating the expenditure destination of the budget are registered, and the subject and amount are registered for each individual expenditure item. The individual expenditure items are items related to budget expenditures in administrative activities, When the supplementary budget request is made, if the designation of a project is accepted, the candidate subjects are determined by referring to the registered subjects related to the individual expenditure items under the designated project. An administrative management system according to any one of [6] to

[12] .

[14] The individual expenditure items are registered in association with the breakdown of financial resources, Based on the financial resource breakdown registered in association with the individual expense items, a financial resource breakdown related to the supplementary budget request is newly generated, and the financial resource breakdown is registered in association with the account and amount related to the individual expense items related to the supplementary budget request.

[13] The administrative management system described in

[13] .

[10] A computer-implemented administrative management method, comprising: Administrative objects relating to continuing administrative activities are registered in a series associated with other corresponding administrative objects relating to the same administrative activity; When a request for the creation of a new administrative object corresponding to an already registered administrative object but at a different position in the series is received for a continuing administrative activity, registering the new administrative object based on the registered administrative object by associating it with the registered administrative object along the series; Administrative management methods.

[11]

[15] A computer program that causes the computer to execute the administrative management method described above.

[0008] According to the invention of [1], administrative objects registered in administrative activities can be managed in accordance with the series, and further, when registering a new administrative object, data already registered in accordance with the series can be used to register it.

[0009] The invention of [2] makes it possible to manage data registered for each execution year and / or budget type in administrative activities and to register new administrative objects using data already registered in a series.

[0010] The invention according to [3] makes it possible to register administrative objects with minimal effort by using a data input screen with preset data items.

[0011] The invention according to [4] makes it possible to easily register a person in charge corresponding to the flow of administrative activities when registering a new administrative object relating to ongoing administrative activities.

[0012] The invention of [5] allows administrative data to be registered serially along a series.

[0013] [6] The invention of the present invention makes it possible to easily register new items and amounts when registering a supplementary budget by using registered items related to the initial budget or supplementary budget.

[0014] The invention of [7] allows the registration of items and amounts for budget item system items, settlement item system items, and public accounting item system items.

[0015] [8] The invention of the present invention allows for the display and registration of candidates for budget item system items or settlement item system items for each individual expenditure item when registering a supplementary budget.

[0016] According to the invention of [9], a list of candidate subjects for the supplementary budget can be displayed, and the supplementary budget can be easily registered based on the subjects selected from the list.

[0017]

[10] The invention of the present invention allows for the registration of items related to expenditures such as individual expenditure items and the registration of associated items and amounts when compiling a budget.

[0018]

[11] The invention of the present invention allows the registration of requested amounts, assessed amounts, and provisional amounts for budget items, and displays multiple amounts associated with each item.

[0019]

[12] The invention of the present invention allows registered items to be displayed as candidates for supplementary budget items in cases where the same expenses continue within a fiscal year, making it easy to register a supplementary budget.

[0020] The invention in

[13] makes it easy to check the relevant items and amounts for each business.

[0021]

[14] The invention of the present invention makes it possible to easily register not only the items but also the financial sources of budget-related expenditure items using information on the registered budget. [Effects of the Invention]

[0022] According to the present invention, it is possible to provide a technology for supporting administrative activities. [Brief explanation of the drawings]

[0023] [Figure 1] Block diagram of the system of this embodiment [Figure 2] Hardware configuration diagram of this embodiment [Figure 3] An image diagram of the tree structure and data structure of the policy system of this embodiment. [Figure 4] Display example of the screen of this embodiment [Figure 5] Display example of the screen of this embodiment DETAILED DESCRIPTION OF THE INVENTION

[0024] The following describes an administrative management system, an administrative management method, and an administrative management program according to an embodiment of the present invention, with reference to the accompanying drawings. Note that the embodiment shown below is an example of the present invention, and the present invention is not limited to the following embodiment, and various configurations can be adopted.

[0025] In this embodiment, we will explain an example of when an administrative management system registers a new supplementary budget for a project (administrative project, minor project) for which the initial budget, or items related to the initial budget and supplementary budget and the amounts related to those items, have been registered.

[0026] In this embodiment, the configuration, operation, etc. of an administrative management system and an administrative management device are described, but similarly configured administrative management methods, computer programs, and program recording media on which the programs are recorded also achieve the same effects. For example, by using a program recording media, the program can be installed on a computer. The series of processes according to this embodiment described below is provided as a computer-executable program, and can be provided via a non-transitory computer-readable recording medium such as a CD-ROM or a flexible disk, or even via a communication line.

[0027] <Terminology> An administrative organization is an organization that manages administration, including government agencies, ministries, and public organizations such as national and local governments, and in this embodiment, a local government is used as an example. The administrative management system according to the present invention is used in administrative organizations to support decision-making in administrative activities.

[0028] A policy system is a system of issues divided into three levels: policy, measures, and administrative projects. In this embodiment, measures are assumed to include multiple levels (two levels) of divisions, including measures and their subordinate measures (referred to as sub-measures), and an example is given of a case where administrative projects are managed using an issue system divided into four levels: policy, measures, sub-measures, and administrative projects, as shown in Figure 3(a). For example, the issue system may be divided into three or five or more levels, and administrative projects may be managed. Furthermore, policies and / or administrative projects may include divisions at two or more levels. A policy is a large set of administrative activities aimed at realizing basic guidelines for addressing specific administrative issues, and indicates the direction and objectives of urban development in the established administrative division (city, ward, town, village, etc.). A policy is a set of administrative activities based on the basic principles of a policy, with the aim of realizing a specific policy, and indicates the measures and countermeasures for realizing the policy. In addition, detailed measures are further sub-divided into the measures and countermeasures for each policy. Administrative projects are administrative tasks and projects that are individual administrative means for realizing specific policies in policies (sub-policies). Administrative projects are implemented by each bureau within an administrative division based on its budget.

[0029] An administrative object refers to an object handled in administrative activities. In this embodiment, administrative objects are managed as system items such as individual policy system items (policies, measures, sub-measures, administrative projects) and breakdown items (individual expenditure items, estimated items). However, for example, answers to questions from assembly members prepared by executive agencies such as administrative agencies in plenary sessions and committee responses, the planning, execution, and evaluation stages of administrative projects, and issues collected by assemblies, committees, etc. and serving as the basis for formulating administrative issues for the next term and beyond may also be treated as administrative objects. Administrative objects are managed as administrative data in a database (DB). In this embodiment, administrative objects, which are data items divided into hierarchies, are configured so that lower-level administrative objects are included within higher-level administrative objects, for example, individual expenditure items are included within administrative projects. Furthermore, an administrative object may include multiple lower-level administrative objects.

[0030] Furthermore, as shown in FIG. 3(b), administrative objects are registered for each position (time point / stage) in a series (e.g., a series related to a time series or a stage in administrative activities). In this embodiment, administrative objects are data registered by execution year and / or budget type, such as by execution year in the task and project hierarchy and by execution year and budget type in the individual expense item hierarchy. However, they may also be data registered as comprehensive data including data from multiple positions in the series (e.g., data such as "task and project A" including task and project A for fiscal year 2023 and task and project A for fiscal year 2024). In this embodiment, administrative objects are registered in association with each other based on a system such as a policy system and based on a series related to continuing tasks and projects, as shown in FIG. 3. This allows data related to administrative activities to be managed based on the system of issues for administrative activities and their chronological position or budget type in continuing administrative activities. In this embodiment, administrative objects are registered in association with each other based on identification information such as an execution year ID and a budget type ID. Furthermore, when a policy system item, such as an administrative project, is newly registered as an administrative object, it is linked to the corresponding administrative project from the previous year (or the year before in chronological order). For example, data for administrative project A for fiscal year 2024 is linked to data for administrative project A for fiscal year 2023. In this embodiment, administrative objects related to policy system items are linked to other administrative objects so as to form a straight line along the timeline, which facilitates the management and display of data along a timeline, such as a chronological difference display comparing data for administrative projects for fiscal years 2023 and 2024. In this embodiment, for example, if data for administrative project A for fiscal year 2022 is registered linked to data for administrative project A for fiscal year 2021 because its abolition has not yet been decided, but its contents do not have any data items registered, when it is decided to revive administrative project A in fiscal year 2024, the newly registered data for administrative project A for fiscal year 2024 is linked to data for administrative project A for fiscal year 2022, not data for administrative project A for fiscal year 2021.In this way, when a new administrative object is registered for a business that will continue after a period of time, such as when a business that was temporarily suspended or abolished and not carried out in the previous year is revived and new business information is registered, the new administrative object is linked to the administrative object that was last registered at the time of suspension or abolition and registered.

[0031] An example of an individual expense item A1 related to ongoing expenses for an administrative project A, as shown in Figure 3(b), will be described. The individual expense item A1 relates to the budget continuing into fiscal years 2023 and 2024. In this embodiment, the individual expense items A1 for fiscal year 2023, including the individual expense items A1 (initial), A1 (June correction), and A1 (September correction), are associated via the higher-level administrative project A in this embodiment, but they may also be directly associated and registered. A series refers to a time series in ongoing administrative activities or a series related to the workflow of administrative activities. In this embodiment, the time series includes a series related to the execution year and a series related to the workflow of administrative activities. In this invention, such series-related associations are used to obtain data related to administrative objects corresponding to ongoing administrative activities and are used in the processing described below.

[0032] A topic refers to a gradual division of administrative activities carried out with an administrative object as the objective. One or more topics can be defined for each type of administrative object. In this embodiment, for example, when an administrative project is the objective, multiple divisions arranged chronologically, such as "budget preparation > request," "budget preparation > assessment," "budget preparation > preliminary announcement," "budget preparation > resolution," "budget execution," "settlement," and "administrative evaluation," are defined as topics. The above is just one example, and different divisions, abstract divisions, detailed divisions, etc. may also be defined. Furthermore, topics may be subdivided by hierarchizing them into multiple layers. For example, instead of the topic "Budget Preparation > XX," categories such as "Initial Budget Preparation (hereinafter referred to as "Initial") > XX" and "Supplementary Budget Preparation (hereinafter referred to as "Supplementary") > XX" may be defined. In this embodiment, the administrative business information described below is set to budget type (e.g., initial budget, supplementary budget number, carryover, current total) and budget preparation status (e.g., "Request," "Adjusting," "Assessment," "Unofficial Notice / Resolution"), allowing topics related to budget preparation to be distinguished.

[0033] <Outline of administrative activities> Here is an example of the flow of administrative activities in a local government. Administrative activities are carried out in succession on a fiscal year basis through stages (topics) such as the budget preparation stage, budget execution stage, and administrative evaluation stage. At the budget preparation stage, the implementation details of the policy system are planned, including deciding on the administrative projects to be implemented in the next execution year, and the budget is compiled after budget requests, assessments, internal announcements, and resolutions are made for the planned policy system. At the budget execution stage, the compiled budget is used to implement the policy system, including administrative projects. At the administrative evaluation stage, the performance of the implemented policy system is evaluated.

[0034] <System configuration> Figure 1 shows a system configuration diagram of an administrative management system 1. The administrative management system 1 comprises an administrative management device 2, a user terminal 3, and a database DB, and each component is connected to a communication network NW. For example, the communication network NW includes a comprehensive administrative network (LGWAN: Local Government Wide Area Network), and the administrative management device 2 and the database DB, and the administrative management device 2 and the user terminal 3 are connected via the comprehensive administrative network.

[0035] The administrative management system 1 (administrative management device 2) provides a platform for operating and managing administrative activities related to business operations. The administrative management device 2 comprises, as functional components, a registration unit 21 and a display processing unit 22.

[0036] The user terminal 3 is a terminal device used by a user belonging to an administrative organization, etc. A plurality of user terminals 3 are installed at least within the administrative organization.

[0037] In this embodiment, users include special officials (such as mayors) within administrative organizations, users of the secretariat department (such as the finance department), section chiefs, department heads, the Civil Engineering Department (bureau / section) and the Agriculture, Forestry and Fisheries Department (bureau / section), and users and supervisors (such as section chiefs and department heads) of the original bureaus and original sections. For example, original section users perform tasks such as creating project documents such as business plans, creating budget requests, executing budgets, and creating administrative evaluation reports. Secretariat users perform tasks such as requesting original section users to create budget requests and evaluating budget requests. Section chiefs, department heads, and special officials perform tasks such as reviewing user deliverables, selecting and prioritizing priority projects based on plans, and assessing budget requests approved by the finance department users. In this embodiment, each user is assigned a specific operational authority, and the permission and restriction of certain functions are controlled according to the operational authority.

[0038] <Hardware configuration> FIG. 2(a) shows a hardware configuration diagram of the administrative management device 2. The administrative management device 2 includes, as its hardware configuration, a control unit 201, a storage unit 202, and a communication unit 203. In this embodiment, the administrative management device 2 can be a computer device such as a server device or a personal computer. Note that the administrative management device 2 may be configured with multiple computer devices, and is not limited to the configuration shown in FIG. 2(a) as long as it can realize the above-described functional components (21-22) as a whole.

[0039] The control unit 201 is configured with one or more processors such as a CPU (Central Processing Unit) or GPU (Graphics Processing Unit), and controls the overall processing of the administrative management device 2 by executing an administrative management program, an OS (Operating System), and other applications. The storage unit 202 is a hard disk drive (HDD), solid state drive (SSD), flash memory, RAM (Random Access Memory), etc., and stores the administrative management program and various data. The communication unit 203 controls communication with the communication network NW, and realizes data communication with the user terminal 3 and the database DB. By executing the administrative management program, the control unit 201 causes the computer to function as the administrative management device 2 and execute the administrative management method.

[0040] In the illustrated example, the database DB is a database server accessible via a communication network NW including LGWAN, etc., but it may also be realized using, for example, the control unit 201 and memory unit 202 that constitute the administrative management device 2, or it may be connected to the administrative management device 2 via a LAN, etc.

[0041] 2(b) shows a hardware configuration diagram of the user terminal 3. The user terminal 3 includes, as its hardware configuration, a control unit 301, a storage unit 302, a communication unit 303, an input unit 304, and an output unit 305. In this embodiment, the user terminal 3 may be a smartphone, a personal computer, a tablet terminal, or the like.

[0042] The control unit 301 is composed of one or more processors such as a CPU, and controls the overall processing of the user terminal 3 by executing an OS, other applications, etc. The storage unit 302 is an HDD, SSD, flash memory, RAM, etc., and stores a browser application and various data. The communication unit 303 controls communication with the communication network and realizes data communication with at least the administrative management system 1. The input unit 304 is an input interface that accepts input operations by the user, and is composed of a microphone, touch panel, mouse, keyboard, etc. The output unit 305 is composed of a display that displays output, etc.

[0043] <Data structure> First, we will explain the data configuration in the administrative management system 1 according to this embodiment. The database DB stores an organization master, a user master, a policy / measure master, a budget item master, an administrative indicator master, and administrative business information (administrative data) for each execution year.

[0044] The organizational master stores organizational structure items that represent a tree-structured organizational structure by linking data items as master data for data items related to organizations within or outside the administrative organization. In this embodiment, the organizational master stores organization information and department information as organizational structure items. The organization information stores identification information (organization ID) of the organization and the organization name. The department information stores identification information (department ID) of the department (division, section, office, etc.) in the organization, identification information (organization ID) of the organization to which the department belongs, identification information (department ID) of the higher-level department to which the department belongs, and the department name. The department to which the user belongs, which will be described later, and the department in charge of policies, measures, and administrative projects, etc., are registered in an identifiable manner in various information based on the organizational structure items.

[0045] The user master stores user information within an organization. The user information includes the user's identification information (user ID), name, department (organizational structure item), etc. It may also be possible to define a user group, which is a collection of one or more users. For example, a user group may be defined by user group information including the user group's identification information (user group ID) and the identification information of users belonging to the user group, the group name, etc., or users having a common attribute such as an organizational structure item may be treated as a user group. Users to be included in a predefined user group may be arbitrarily selected, or may be selectable from user groups having a common attribute. A user group is specified by an arbitrarily set group name or an attribute name that represents the characteristics of the group.

[0046] The policy and program master stores policy and program system items that represent a tree-structured policy and program system by linking data items as master data for data items related to policies and programs. In this embodiment, the policy and program master stores policy information and program information as policy and program system items. The policy information / program information includes identification information for the policy / program (policy ID / program ID), policy number / program number, policy name / program name, responsible department (department, section, office, etc.), policy purpose / program purpose, and policy summary / program summary. Furthermore, the program information includes identification information for the corresponding main policy (policy ID).

[0047] The subject master stores master data for data items that indicate the budget subject system, settlement subject system, and public accounting subject system, including budget subject system items that represent the budget subject system in a tree structure by linking data items, settlement subject system items that represent the settlement subject system, and public accounting subject system items that represent the public accounting subject system. In this embodiment, the budget item master stores budget item information as a budget item system item. The budget item information includes budget item identification information (budget item ID), identification information (budget item ID) of the higher-level budget item to which the budget item belongs, budget item type (either subitem, section, or subsection), and budget item name. The financial statement subject master stores expenditure breakdown purpose information and budget property information as financial statement subject system items. Expenditure breakdown purpose indicates the purpose of expenditure linked to an administrative project, and is used for financial statement statistics in the financial statement topic. Expenditure breakdown purpose information includes identification information of the expenditure breakdown purpose (expenditure breakdown purpose ID), identification information of the higher-level expenditure breakdown purpose to which the expenditure breakdown purpose belongs (expenditure breakdown purpose ID), identification information of the corresponding budget subject (section, item, or item) (budget subject ID), type of expenditure breakdown purpose (in this embodiment, there are three types: major classification, medium classification, and minor classification), and expenditure breakdown purpose name. The budget property indicates the property of the budget set under a section or subsection, and the budget property information includes identification information of the budget property (budget property ID), identification information of the budget item (section or subsection) to which the budget property belongs (budget item ID), or identification information of the higher-level budget property (budget property ID), the type of budget property (in this embodiment, there are four types: major classification, medium classification, minor classification, and detailed classification), and the budget property name. The public accounting item master stores public accounting item information as a public accounting item system item. The public accounting item information includes identification information for the public accounting item, identification information for the higher-level public accounting item to which the public accounting item belongs (public accounting item ID), and the public accounting item name.

[0048] In this embodiment, the policy system tree structure and administrative indicator tree structure shown in FIG. 3 are in a corresponding relationship. The policy system tree structure has a policy level T11, a policy level T12, a sub-policy level T13, and an administrative / business level T14. The administrative indicator tree structure has a long-term indicator level T21, a long-term indicator level T22, a long-term indicator level T23, and a medium-term indicator / progress indicator level T24. The policy level T11 and the long-term indicator level T21, the policy level T12 and the long-term indicator level T22, the sub-policy level T13 and the long-term indicator level T23, and the administrative / business level T14 and the medium-term indicator / progress indicator level T24 are respectively associated with each other. Corresponding administrative indicator information can be referenced for policies, programs, sub-policies, and administrative projects. Information related to the policy system and administrative indicator information can be referenced by both parties by having the identification information of the corresponding party (IDs such as policy IDs or program IDs related to the policy system, or administrative indicator IDs). The administrative management device 2 accepts the specification of the policy information, measure information, or business / operation information to be associated, as well as the administrative indicator information (administrative indicator system items), and associates the administrative indicator with the specified policy, measure, or business / operation and stores it in the memory unit 202.

[0049] Each task and project is set with breakdown items, which are elements that can be decomposed and are contained within it. In this embodiment, one or more sub-projects are linked to each task and project as breakdown items, and each sub-project is linked to individual expense items that indicate the purpose and destination of the budget expenditure. The individual expense items include an accumulation item that indicates the budget amount, etc., and a financial source breakdown that indicates the source of funds.

[0050] Furthermore, individual tasks and projects or subprojects are linked to organizational system items, policy and program system items, budget item system items, and administrative indicator system items. In this embodiment, a data structure is adopted in which tasks and projects are linked to one or more organizational system items, one or more policy and program system items, one or more administrative indicator system items, and budget item system items related to sub-items, and subprojects are linked to budget item system items related to sub-items. Furthermore, in any topic, labels indicating their contents may be assigned to individual tasks and projects, subprojects, or individual expense items. In this embodiment, a label indicating that a task and project is a priority project is assigned to a task and project, and a label indicating that a project is a mandatory expense or a label indicating an increase or decrease in the budget amount for an ongoing project, etc. is assigned to an individual expense item.

[0051] The business and project information is administrative data related to each business and project, and is registered for each execution year. In this embodiment, the business and project information includes basic information related to the business and project (basic business information), administrative indicator information, budget information, financial resource information, and expenditure and income information related to the business and project. Basic information on business operations (basic business information) is information on the contents of business operations, and includes basic information (i.e., business operation information) identification information (business operation ID), related administrative data, business operation name, major policies and measures to which the business operation belongs (policy and measure system item), business start year, execution (planned) year, budget type (e.g., initial budget, supplementary budget number, carryover, current total), topic, budget amount of business operation, revenue amount of business operation, budget name, affiliated department / agency (organization system item), responsible department (organization system item), accounting classification, business operation status (e.g., "new", "expansion", "reduction", "suspended", "abolished"), budget compilation status (e.g., "request", "under adjustment", "assessment", "preliminary notice / resolution"), item item (budget item system item), major classification, medium classification, minor classification of expenditure breakdown purpose (settlement item system item), expense classification, budget amount of business operation, etc., as well as optional items such as business operation purpose, business operation summary, It includes various information related to the project, such as the underlying laws and regulations, related plans and notifications, the current situation and issues, the (planned) fiscal year in which the project will end, remarks, and priority issues (administrative indicator system items). Attachments such as PR materials and forms may also be linked to the administrative project information. In addition, if a budget is compiled multiple times within a fiscal year, such as when a supplementary budget is compiled midway through the fiscal year, multiple pieces of administrative project information may be registered in association with each budget type for the same administrative project.

[0052] Budget information includes, for example, budget amounts (expenditures) for each topic (e.g., "Budget Preparation > Request," "Budget Preparation > Assessment," "Budget Preparation > Preliminary Notification / Resolution"), individual expense item names, and system items including subjects. In this embodiment, budget information includes, as system items, expenditure subdivisions (budget item system items), major, medium, minor, and detailed budget classifications (settlement item system items), and public accounting item system items. Budget amounts include the requested amount, which is the budget amount estimated at the "request" stage of budget preparation, the assessed amount, which is the budget amount adjusted as necessary from the requested amount at the "assessment" stage, the preliminarily announced budget amount, etc. In this embodiment, each piece of business information is configured to be able to hold the budget amounts for each stage for each individual expense item it contains.

[0053] The funding information indicates one or more funding sources for each budget amount, and includes, for example, the name of the funding source, the amount of revenue appropriated for the budget information, and details (budget item system items). For example, like the budget amount, the revenue amount is also linked to each topic, and is configured to be able to hold, for example, the revenue request amount, which is the amount of revenue estimated at the "request" stage of budget preparation, the revenue assessment amount, which is the amount of revenue adjusted as necessary from the revenue request amount at the "assessment" stage, and the revenue forecast amount, which is the amount of revenue forecast.

[0054] In this embodiment, policy information, program information, and task and project information are registered for each implementation year, and policies and programs implemented over several years, and related tasks and projects in different implementation years that are continued or integrated, etc., are associated with each other. Tasks and projects are further subdivided into a four-level tree structure (tasks > subprojects > individual expenditure items > estimated items) based on their breakdown items, and these breakdown items are also registered for each implementation year. Tasks and projects are structured to include one or more subprojects, and subprojects include one or more individual expenditure items. Task and project information includes basic task information, which is a data item in the task and project layer that represents the content of the task and project; subproject information, which is a data item in the subproject layer that represents the content of the subproject; and individual expenditure item layer data items that represent the content of the individual expenditure items. Individual expenditure items are breakdown items of task and project (subprojects in this embodiment) that indicate the purpose and destination of budget expenditures, and are associated with subsections (budget account system items) and budget amounts by budget type (estimation items). Preferably, the budget amount is also associated with the corresponding revenue amount (breakdown of financial resources). In this embodiment, three items are registered in association with each individual expense item: budget item system item, budget characteristics (financial statement item system item), and revenue breakdown. One or more accumulation items are included in each individual expense item, and are registered using accumulation item information that indicates the budget amount of the business or higher-level breakdown item by being accumulated. The revenue breakdown is included as 0 or 1 for each individual expense item, and is registered using revenue breakdown information that indicates the revenue amount of the business or higher-level breakdown item.

[0055] The sub-project information includes various information related to the sub-project, such as the identification information of the sub-project (sub-project ID), the identification information of the related administrative information (administrative project ID), the name of the sub-project, an overview of the sub-project, the status of the sub-project (e.g., "new," "expansion," "reduction," "suspended," "cancelled"), and the budget amount of the sub-project.

[0056] Individual expense items indicate expense items required for administrative activities related to the corresponding subprojects, and refer to expense items among budget information that are uniquely registered in each of the budget item system items, settlement item system items, and public accounting item system items. Individual expense item information includes identification information for the individual expense item (individual expense item ID), identification information for the related subproject (subproject ID), individual expense item name, budget amount for the individual expense item, individual expense item group label, individual expense item summary, subsection (budget item system item), and nature (budget nature: budget item system item). An accumulation item is a specific individual expense item included in an individual expense item, and accumulation item information includes identification information of the accumulation item (accumulation item ID), identification information of the related individual expense item (individual expense item ID), accumulation item name, budget amount for each topic, planned execution quarter, accumulation item overview, and accumulation basis (formula, etc.). The funding breakdown indicates the funding source for each individual expenditure item, and the funding information includes the identification information of the funding source (funding source ID), the identification information of the related individual expenditure item (individual expenditure item ID), the name of the funding source, the amount of revenue for each topic, the funding allocation rate, the funding classification (general funding, specific funding), item item subsections (budget subject system items), responsible organization / department (organization system items), the basis for allocation, and the reason for allocation.

[0057] In this embodiment, the administrative business is subdivided into a four-level tree structure, and the budget amount for an administrative business is given by the total budget amount of the sub-businesses under the administrative business, the budget amount for a sub-business is given by the total budget amount of the individual expense items under the sub-business, and the budget amount for an individual expense item is given by the total budget amount of the accumulated items under the individual expense items. In other words, when registering administrative business information, the registration unit 21 registers the budget amount for the accumulated items, thereby also registering the budget amounts for the individual expense items, sub-businesses, and administrative business. The same applies to revenue amounts.

[0058] The expenditure and income information is information related to expenditures and / or incomes that is registered as needed for budget execution during the execution period. The expenditure and income information includes identification information for expenditures and incomes (expense and income ID), identification numbers for itemized items of the budget to be executed, names of expenditure and income items, expenditure and income amounts, and sub-items (budget subject system items). In this embodiment, individual expenditure items are linked to the expenditure and income information as the budget to be executed, but it is also possible to link estimated items.

[0059] In this embodiment, an example is described in which individual expense items are linked to a budget item system and a settlement item system (subsections). Furthermore, public accounting items, which are public accounting items, may be linked one-to-one to the subsections of individual expense items as an item system. Public accounting items are multi-entry items used in accounting for organizations that provide public services, such as national and local governments, including financial documents such as general account balance sheets, general account administrative cost statements, net asset change plans, and general account cash flow statements. These items are systematically stored in a database at one or more levels. Local public accounting refers to a government accounting system established as a unified standard by local governments, which aims to enhance administrative financial transparency, fulfill accountability to residents, and promote financial efficiency and rationalization. The system complements the current cash-basis, single-entry budget and settlement systems used by local governments. In the process of tabulation described below, the tabulation unit 23 may search for revenues and / or expenditures that meet the search criteria using these accounting items as the axis, and tabulate the revenue and / or expenditure amounts. Individual expense items linked to public accounting items are used to create financial documents such as balance sheets.

[0060] <Functional configuration> The following describes the functional configuration of the administrative management system 1. In this embodiment, a new supplementary budget request is made for a project (administrative project, minor project) for which items and amounts related to those items have been registered for the initial budget or the initial budget and supplementary budget. In the example shown below, individual expense items are replicated as administrative objects, and data items such as items and amounts included in the replicated individual expense items are replicated. However, similar processing to that described below may be performed for administrative objects at other levels. Furthermore, the "new supplementary budget request" for a project (administrative project, minor project) for which items and amounts related to those items have been registered for the initial budget or the initial budget and supplementary budget refers to the time when the display processing unit 22 receives a request from the user terminal 3 to display a budget registration screen (in this embodiment, a project details screen) for registering a supplementary budget for a project (administrative project, minor project) for which items and amounts related to the initial budget or the initial budget and supplementary budget have been registered. In this embodiment, the process for registering a new supplementary budget is performed by referring to information about already approved budgets, such as budgets that have already been approved (budgets with a budget compilation status of approved), but registration may also be performed by referring to information about budgets with other statuses. Corresponding budgets are budgets related to corresponding administrative objects (administrative projects, minor projects, individual expenditure items, estimated items, etc.) that are related along a series, such as budgets related to individual expenditure items under the same administrative project, but which differ in one or more of the execution year, budget type, and budget compilation status (for example, "travel expenses" in the FY2024 initial budget under the administrative project "next payroll system development project expenses" and "travel expenses" in the FY2024 September supplementary budget).

[0061] In systems for managing administrative activities in general, information on the budget is registered for each budget type (initial, supplementary, etc.), including information on administrative projects such as costs for each project. However, in the administrative management system 1 of this embodiment, by registering data on individual expenditure items such as estimated items and breakdowns of funding sources, which have different budget types for each project, it is possible to register and display information according to budget type for each project in administrative activities.

[0062] In addition, in this embodiment, an example is described in which the items and amounts (budget amounts) of the supplementary budget are registered by duplicating individual expense items and duplicating or newly registering the accumulated items under them, but for example, data items may be duplicated for data items of other hierarchical levels, such as minor projects or accumulated items, and processing related to budget registration, such as registering items and amounts related to the supplementary budget, may be performed. In addition, in this embodiment, the granularity of information is consistent by associating budget item system items, settlement item system items, and financial resource breakdowns with individual expense items and registering them, and individual expense items are used for budget compilation, settlement statistics, etc.

[0063] <Registration Department 21> The registration unit 21 accepts input of administrative data such as organizational information, department information, user information, policy information, measure information, business and project information, budget item information, performance indicator information, and progress indicator information via the user terminal 3, and stores the data in the database DB. For example, the registration unit 21 accepts organizational information, department information, user information, policy information, measure information, and budget item information in advance and stores them in the database DB, and at the budget compilation stage, it accepts business and project information and stores it in the database DB. Furthermore, at the execution stage, the registration unit 21 accepts registration of progress performance information and expenditure and income information, and at the administrative evaluation or settlement stage, it accepts registration of performance performance information, etc.

[0064] Furthermore, the registration unit 21 registers the budget by accepting system items including items and amounts in the budget compilation stage and storing them in the database DB. System items are administrative objects organized using a tree structure or the like, and in this embodiment, include items such as budget items. In this embodiment, the registration unit 21 registers breakdown items (individual expense items, estimated items, etc.) as system items for each project when registering the budget, but may also register a breakdown of financial resources as system items. In this embodiment, the registered items are items (budget items) related to budget item system items, but may also be items (settlement items) related to settlement item system items or items (public accounting items) related to public accounting item system items. The registration unit 21 accepts amounts such as budget amounts along with items such as budget items for individual expense items under the project (administrative project, minor project) specified by the user, and registers them in the database DB in association with each other. In addition, in this embodiment, the registration unit 21 registers the budget by accepting the registration of amounts (budget amounts) for subjects (budget subjects) corresponding to individual expense items and for accumulated items under the individual expense items, but the budget may also be registered by accepting the registration of subjects and amounts for items at any level (administrative business, minor business, individual expense item, accumulated item) for administrative business.

[0065] The registration unit 21 copies data items other than amounts (individual expense item name, expenditure item (subsection: budget item system item), nature (budget nature: settlement item system item), account name to which transfer is to be made (accounting category: general account / special account), etc.) based on information (individual expense item information, etc.) related to the initial budget or supplementary budget for registered individual expense items or items linked to individual expense items (accumulation items, etc.), and stores the copied data together with amounts (budget amounts, etc.) received from users in the database DB, thereby registering system items (individual expense items in this embodiment) related to a new supplementary budget. Furthermore, when registering individual expense items related to the supplementary budget, the registration unit 21 may copy information related to the accumulation items registered in association with the individual expense items (budget type, budget amount) and information related to the financial resource breakdown (financial resource category, revenue amount), and register the copied data as new accumulation items / financial resource breakdowns related to the supplementary budget in association with the individual expense items related to the newly generated supplementary budget. In this embodiment, new individual expense items related to the supplementary budget are stored in the database DB in association with the same or corresponding higher-level item (business project, minor project) as the original individual expense item. However, they may also be registered in association with the original individual expense item. Corresponding items here refer to items (individual expense items in this embodiment) at the same level in the tree structure that are stored in association with different execution years and / or budget types, such as items related to similar expenses in the same business project (e.g., individual expense item names) but with different execution years or budget types (initial budget, supplementary budget number, etc.). Furthermore, when registering individual expense items for a supplementary budget using a duplicated item, new accumulation items may be generated that duplicate data other than the amounts for the accumulation items under the original individual expense item, and the new items may be registered in association with the new individual expense items related to the supplementary budget. Amounts, such as budget amounts, may also be duplicated, or amounts related to the items or items may be pre-registered. The amounts duplicated and registered are the unofficial amounts, but may also be amounts in other budget preparation statuses (e.g., requested amounts, assessed amounts, etc.). In addition, in this embodiment, an amount that has a different budget preparation status from the registered column is copied and registered, such as an amount copied from the tentative amount being registered in the requested amount column when requesting a budget.

[0066] The registration unit 21 associates and registers the duplicated items and the amounts entered by the user based on information about the registered budget. In this embodiment, the registration unit 21 registers new individual expense items for the supplementary budget in which other data items such as items are duplicated from the registered budget based on individual expense item information for the registered budget related to the initial budget and / or supplementary budget and the amounts (budget amounts, etc.) entered by the user. In addition, in this embodiment, the registration unit 21 generates a new breakdown of financial resources for the supplementary budget based on the breakdown of financial resources linked to the individual expense items for the registered budget, and registers the breakdown of financial resources in association with the new individual expense items for the supplementary budget.

[0067] In this embodiment, the registration unit 21 performs processing related to the registration of the supplementary budget by generating and storing new individual expense item information based on the amount input on the user terminal 3 and information related to individual expense items in the registered budget (individual expense item information, etc.). Furthermore, the registration unit 21 may generate individual expense item information in which the amount is blank or 0 yen in advance for individual expense items that are candidates for items in the supplementary budget based on the information related to the registered budget, and upon receiving the designation of an individual expense item and input of the amount from the user terminal 3, change the amount of the generated individual expense item information to register the supplementary budget, including the registration of the amount and item.

[0068] <Display processing unit 22> The display processing unit 22 processes the display of various pages including a business details screen based on the data stored in the database DB. The business details screen is a screen for displaying detailed information about a specified business, and is displayed on the user terminal 3. When a business to check details about is specified on the user terminal 3, the display processing unit 22 processes the display of the business details screen.

[0069] In this embodiment, when the registration of a supplementary budget is selected for a project (administrative project or minor project) to be registered, the display processing unit 22 references the items related to the registered initial budget or supplementary budget and displays a project details screen on which candidate items to be registered are displayed. At this time, the display processing unit 22 displays the project details screen on which candidate items are displayed based on the data related to the initial budget or the initial budget and supplementary budget already registered for the same project.

[0070] <Screen display example> 4 and 5 are used below to show examples of screens displayed by the display processing unit 22. In addition, the example described in this embodiment will be a case where a supplementary budget is input and displayed at the stage of compiling the supplementary budget, but the input and display of the initial budget may also be performed in the same manner.

[0071] When the designation of the project for which the budget is to be registered is accepted from the user terminal 3, the display processing unit 22 processes the display of project detail screens W1 and W2 for the designated administrative project, which display details of the designated project as shown in Figures 4 and 5. When "initial" is selected as the budget type, the display processing unit 22 displays the project detail screen W1 as shown in Figure 4, and when "June correction" is selected as the budget type, the display processing unit 22 displays the project detail screen W2 as shown in Figure 5. The screens shown in Figures 4 and 5 display a specific individual expense item ("contract fee") associated with the designated project ("next payroll system development project cost"), but it is also possible to aggregate and display information on individual expense items of the same category or nature, for example.

[0072] 4 shows an example of the screen display of the project details screen W1, which functions as an input screen for the initial budget for a specified administrative project on the user terminal 3 and a display screen. Regarding the process for registering a supplementary budget, which will be explained using FIG. 5, an example will be explained in which the supplementary budget for an administrative project ("Next Payroll System Development Project Costs") displayed on the project details screen W1 shown in FIG. 4 is registered and displayed. In this embodiment, when compiling a supplementary budget, the supplementary budget is registered using the items of the initial budget and / or supplementary budget registered for the same project in the same fiscal year. However, for example, when compiling an initial budget, information about the budget may be registered using the items of the initial budget and / or supplementary budget for the same administrative project in the previous fiscal year.

[0073] The project details screen W1 shown in FIG. 4 is a screen for displaying information about a specified project regarding expenditures and budgets for the project, and displays one or more sub-projects, individual expense items, and accumulated items under the project. The display processing unit 22 displays a screen such as that shown in FIG. 4 based on information about the project selected by the user (project information, individual expense item information, etc.). At this time, the display processing unit 22 may display a screen such as that shown in FIG. 4 using any information about items (sub-projects, individual expense items, accumulated items, etc.) associated with the selected project through a tree structure or the like. In the example shown in FIG. 4, information about a sub-project called "Next Payroll System Development Project Cost" under the project called "Next Payroll System Development Project Cost" is displayed, and information about an individual expense item called "Contract Fee" under the sub-project called "Next Payroll System Development Project Cost" is also displayed. In addition, in the example shown in FIG. 4, an accumulated item ("Contract Fee") under the individual expense item called "Contract Fee" is also displayed. As shown in Figure 4, in this embodiment, each item is displayed in association with related items based on a tree structure relating to administrative projects and detailed items such as minor projects, individual expense items, and estimating items, so that estimated items under the same administrative project are arranged side by side.

[0074] In addition, by pressing the "-" mark to the left of the item name, the items subordinate to that item (for example, if it is an individual expense item, the items subordinate to that item will be hidden. In this embodiment, the business details screen W1 displays, for individual expense items, budget item system items (items below the section), budget characteristics (financial statement item system items), and details of funding sources (revenue amounts for each funding source category and each budget preparation status). In addition, the business details screen W1 displays, for each budget item, the budget type, the planned execution quarter (the planned time of execution), and the budget amount (requested amount, assessed amount, and forecast amount) for each budget preparation status. In addition, for the breakdown of funding sources, the business details screen W1 displays the revenue amount (requested amount, assessed amount, and forecast amount) for each budget type, responsible organization (or responsible department), and budget preparation status. Furthermore, for each item, a screen for inputting or changing the specified item is displayed by pressing the pencil mark (edit button) or three-dot leader displayed on the right side of the screen, and the user may enter input via the displayed screen to correct data items that have already been registered. Furthermore, for data items that are preferably not editable, such as the initial budget that has already been assessed or the initial budget at the registration stage of a supplementary budget, a detail confirmation button for checking details may be provided instead of an edit button, and the data may be configured to be non-editable. Furthermore, in this embodiment, the person who made the final assessment ("Governor" or "Deputy Governor" in FIG. 4) is displayed above the assessed amount.

[0075] Figure 5 shows a business details screen W2 that functions as an input screen and display screen when a supplementary budget (June supplementary budget in the example shown in Figure 5) is selected as the budget type. The business details screen W2 shown in Figure 5 is a screen for displaying and registering information about the supplementary budget for the June supplementary budget for the same fiscal year (2024) as the same administrative business ("Next Payroll System Development Project Costs") as the administrative business shown in Figure 4, and is a screen that displays candidate subjects for the supplementary budget based on data such as subjects for individual expense items in the initial budget shown in Figure 4.

[0076] The project details screen W2 shown in Fig. 5 is a screen displayed when "June correction" is selected as the budget type for the registered budget shown on the project details screen W1. When the display processing unit 22 receives a project details screen display request for the initial budget or the supplementary budget from the user terminal 3 for an administrative project for which an initial budget or supplementary budget has been registered, the display processing unit 22 displays the project details screen W2, as shown in Fig. 5, displaying candidate items for the supplementary budget based on the registered information (administrative project information, detailed project information, individual expense item information, and accumulated item information) for the initial budget or supplementary budget of the specified project. Furthermore, if the registration unit 21 has previously registered candidate breakdown items (individual expense items, etc.) for the supplementary budget, the display processing unit 22 may perform display processing based on candidate information for the registered supplementary budget (for example, individual expense item information with a budget amount of 0 yen, etc.).

[0077] In the example shown in Fig. 5, the display processing unit 22 performs display processing based on the registered initial budget shown in Fig. 4, and therefore individual expense items registered in the initial budget, including "commission fee," are displayed as candidate individual expense items for the supplementary budget. At this time, for each individual expense item, the same subjects (subsections) as those in the initial budget are displayed as candidates, but for other data items included in the business information, such as characteristics (accounting subject system items) and accounting classifications, the same (characteristics, accounting classifications, etc.) as those in the initial budget may also be displayed as candidates. In addition, for the accumulation items subordinate to the candidate individual expense items in the supplementary budget, accumulation items similar to those in the initial budget (for example, "commission fee" as an accumulation item) may be displayed as candidates in the supplementary budget, and amounts for these items may be registered. Furthermore, the display processing unit 22 displays the names of data items (for example, commission fees as individual expense items) that are candidates for the supplementary budget based on the data items of the registered initial budget, but may also display a screen (business details screen W2) that includes input fields with preset data items (for example, with budget amounts corresponding to individual expense items already entered) based on the data items of the registered initial budget.

[0078] On the screen shown in FIG. 5, when one of the individual expense items displayed as candidates for the supplementary budget based on the individual expense items related to the registered initial budget is designated as the individual expense item for which the budget is to be registered, and an amount (budget amount) is input from the user terminal 3, the registration unit 21 registers the input amount and the items, etc. related to the designated individual expense item in association with each other, thereby registering the supplementary budget. For example, when "commission fee" is selected as the individual expense item for which the user inputs an amount from the candidates displayed on the business details screen W2, the registration unit 21 registers the items and amounts for the individual expense item "commission fee" in the supplementary budget. In this embodiment, the items (or items) and amounts are registered in association with each other by receiving the registration of amounts, such as the budget amount, for the accumulation items under the designated individual expense item; however, amounts and items may also be registered in association with each other at the individual expense item level. Furthermore, when a request to register a new individual expense item with a budget type of supplementary budget is received for an administrative project for which an individual expense item has already been registered, the person in charge and / or the organization in charge of the individual expense item in the new supplementary budget may be registered based on information regarding the person in charge of the registered individual expense item. For example, the person in charge / organization in charge from the initial budget may be registered as the person in charge of the new individual expense item. Furthermore, the information regarding the person in charge includes user information regarding the user who will be in charge of the administrative object as the person in charge, and one or more organizational structure items regarding the organization in charge and the department in charge. In this embodiment, the person in charge / organization in charge / department in charge, and their superiors or members of the superior organization can input / modify data for the administrative object. The person or organization in charge of the administrative object may change depending on the flow of administrative activity.

[0079] Furthermore, when the individual expense item registration button labeled "+Individual Expense Item" is pressed, an instruction to create a new individual expense item is sent from the user terminal 3, and an individual expense item input screen for entering information about the new individual expense item is displayed by the display processing unit 22 so that it is superimposed on the right side of the business details screen W2.

[0080] The individual expense item input screen is a screen display for inputting various information regarding individual expense items, including the individual expense item name, expenditure item (subdivision), nature (budget nature: budget item accounting item), and accounting classification, and is displayed when the user selects to create a new individual expense item. When the display processing unit 22 receives an instruction to create a new individual expense item from the user terminal 3, it performs display processing so that the individual expense item input screen is superimposed on the business details screen W2. The registration unit 21 registers information regarding the new individual expense item input from the user terminal 3 via the individual expense item input screen (individual expense item information) in association with higher-level administrative business information and / or detailed business information.

[0081] Furthermore, when a user selects creation of a new sub-project under an administrative project, the display processing unit 22 may display a screen display (sub-project information input screen) for accepting input of information about the sub-project. At this time, the display processing unit 22 displays the sub-project information input screen for accepting information about the sub-project, such as the sub-project name, summary, and sub-project status (e.g., "expansion," "reduction," "suspended," or "cancelled"). The registration unit 21 accepts the sub-project information entered via the sub-project information input unit, associates it with the administrative project information about the higher-level administrative project, and stores it in the database DB for registration. Furthermore, when an accumulating item registration button labeled "+ accumulating item" or a funding breakdown registration button labeled "+ funding breakdown" is pressed, an accumulating item registration screen or funding breakdown registration screen for registering the accumulating item or funding breakdown may be displayed. At this time, the registration unit 21 associates the information about the accumulating item or funding breakdown received with the individual expense item ("commission fee" in the example shown in FIG. 5) displayed in the same column of the table and registers it in the database DB.

[0082] The registration unit 21 registers various information relating to individual expense items received via the individual expense item input screen.

[0083] Furthermore, in this embodiment, an example at the stage of compiling a supplementary budget has been described. However, when compiling the initial budget, the previous year's initial budget may be referenced to display and register candidate items for the current year's initial budget. At this time, the registration unit 21 and the display processing unit 22 perform processing related to display and budget registration by referencing the previous year's data (task and business information) for a specific task and business stored in the database DB. Also, for tasks and businesses that are not performed annually but are performed every other year, or that have periods of abolition or suspension, administrative objects do not need to be registered every year. A newly registered administrative object for a task that has been suspended or resumed after being abolished is registered in association with the administrative object closest in the series (for example, the administrative object last registered before or after the abolition).

[0084] Furthermore, in this embodiment, an example has been described in which a supplementary budget is registered by duplicating individual expense items and registering them in association with the amount received from the user terminal 3, but for items (administrative objects) at a different level from individual expense items, such as administrative projects, minor projects, and estimated items, it is also possible to register new administrative objects based on registered administrative objects, duplicate system items (items, etc.), and register items and amounts using the duplicated system items. In this case, processing may be performed by mutually utilizing data related to items at different levels that are registered in association with a tree structure related to administrative objects and / or policy systems and breakdown items that are related by a series.

[0085] In the above example, we have explained the case where each individual administrative object is duplicated and registered. However, it is also possible to collectively register a specified range of administrative objects based on already registered administrative objects, such as registering data for this year's administrative projects based on data for the previous year's administrative projects. In this case, administrative projects with a status of "abolished" or "suspended" may not be duplicated when newly registering, and administrative objects to be duplicated and not duplicated may be determined based on the status of the administrative project (such as administrative project status or subproject status), and new administrative objects may be registered in bulk by duplicating administrative objects with other statuses. Furthermore, administrative objects and other data items at lower levels of the new administrative object may be duplicated and registered based on administrative objects at lower levels (e.g., individual expenditure items at lower levels of administrative projects) of already registered administrative objects associated based on a system (policy system or system related to breakdown items). For example, when duplicating data for 2023 administrative business A, in which 2023 individual expense item A1 and 2023 individual expense item A2 are registered at a lower level, new data for 2024 administrative business A is registered, and 2024 administrative business A is registered with 2024 individual expense item A1 and 2024 individual expense item A2 linked to it.The new administrative object generated and registered by duplication is registered in association with the registered administrative object from which it was copied, based on the system of the registered administrative object, in the same system as the original registered administrative object. [Explanation of symbols]

[0086] 1. Administrative Management System 2 Administrative management device 21 Registration Department 22 Display processing section 3. User terminal

Claims

1. An administrative management system, The administrative object holds budget items and budget amounts for each stage of budget preparation, and is registered in a series associated with other administrative objects related to the same administrative activity. When a request for creating a new administrative object relating to the same administrative activity is received, and displaying the budget amounts and budget items of registered administrative objects relating to the approved budgets identified based on the stage of budget compilation as candidates for data of the new administrative object; registering the new administrative object in association with the registered administrative object relating to the same administrative activity along the same line; Administrative management system.

2. The candidates are displayed based on the registered administrative objects related to the current budget. The administrative management system according to claim 1 .

3. The administrative object relating to the current budget is an administrative object based on a plurality of registered administrative objects including initial and correctional administrative objects, The budget amount displayed as a candidate is the total amount of the initial budget and the supplementary budget. The administrative management system according to claim 2 .

4. the candidates are displayed based on the most recent administrative object in the sequence; The administrative management system according to claim 1 .

5. The administrative object includes one or more financial resource breakdowns associated with each of the budget items; Displaying the breakdown of financial resources linked to each budget item based on one or more financial resource breakdowns included in the registered administrative object, The administrative management system according to claim 1 .

6. The series is based on budget type and execution year. The candidates are displayed based on the registered administrative objects that have the same budget type in the series as the new administrative object and that have different execution years. The administrative management system according to claim 1 .

7. The new administrative object is registered in association with the registered administrative object used to display the candidate. The administrative management system according to claim 1 .

8. For each project in administrative activities, system items including subjects and budget amounts related to the system items are registered in association with each other; Once the designation of a project for which a new budget request is made is accepted, Display subject candidates based on registered subjects related to the specified business, Accepting registration of a budget amount related to the specified project, and registering the accepted budget amount and the items displayed as candidates in association with the registered administrative object related to the specified project. The administrative management system according to claim 1 .

9. Administrative objects are registered in association with administrative objects at higher and / or lower levels in a tree structure; The new administrative object is an individual expense item related to expenses required for administrative activities, and is registered in association with higher-level administrative business information of the registered administrative object or with administrative business information corresponding to the higher-level administrative business information. The administrative management system according to claim 1 .

10. Administrative objects are individual expenditure items related to expenditures required for administrative activities, The budget amount displayed as a candidate is the sum of the amounts of the administrative objects subordinate to the registered administrative object. The administrative management system according to claim 1 .

11. 1. A computer-implemented administrative management method, comprising: The administrative object holds budget items and budget amounts for each stage of budget preparation, and is registered in a series associated with other administrative objects related to the same administrative activity. When a request for creating a new administrative object relating to the same administrative activity is received, and displaying the budget amounts and budget items of registered administrative objects relating to the approved budgets identified based on the stage of budget compilation as candidates for data of the new administrative object; registering the new administrative object in association with the registered administrative object relating to the same administrative activity along the same line; Administrative management methods.

12. A computer program that causes a computer to execute the administrative management method according to claim 11.

Images