JP7131936B2 - Common expense management device, common expense management method, and common expense management program - Google Patents

Description

The present invention relates to a common expense management device, a common expense management method, and a common expense management program.

Cost allocation calculation processing is complicated. For example, Patent Literature 1 discloses an apparatus that performs allocation calculation processing for water supply, electricity, heat supply, or gas used in a building (see claim 1, for example).

JP 2017-182766 A

By the way, a business operator may borrow goods or receive services from other business operators for a specified contract period (for example, use of software, rental of mobile phones or landline phones, personal computer , car leasing) and may pay costs accordingly. The cost of such goods or services is normally treated as a common cost included in the cost of the business.

However, since business operators use goods and services in a wide variety of ways and individual contract terms differ, managing common costs is complicated. In particular, contract documents with users and invoices from users usually do not specify the destination of goods and services. Allocating costs (allocation sources) by specifying or estimating usage destinations (allocation destinations) of goods and services is a time-consuming management task. In particular, after allocating common expenses, it is difficult to identify or guess the unit (e.g., office, department, or department) that uses goods and services, and the accuracy is low. It is extremely difficult to grasp the details such as which employee belonging to which department is using the service, and which business (business unit) is receiving what kind of service.

On the other hand, if the above details can be grasped, it can be used for management decisions, so it is required to be able to manage common expenses easily and with high accuracy.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a common expense management device, a common expense management method, and a common expense management program capable of easily and accurately managing common expenses. aim.

In order to solve the above-described problems and achieve the object, a common expense management device according to the present invention is a common expense management device for managing common expenses as allocation sources, wherein When one or more allocation destinations are individual employees of a business operator, a predetermined proportional distribution rate generated based on the involvement period in which the individual said employee was involved in said goods or said services during said predetermined period by the fixed amount of money generated for the goods or services in the predetermined period to create allocation data for each of the employees .

Further, the common expense management device according to the present invention is characterized in that the predetermined period is a contract period for the article or the service or a period obtained by subdividing the contract period.

Further, in the common expense management device according to the present invention, the allocation data creation means acquires the participation period from work performance information related to the work performance of the individual employee.

Further, in the common expense management device according to the present invention, when the allocation destination is a business unit of a business operator, the allocation data creating means creates the allocation data directly charged to the business unit. characterized by :

Further, in the common expense management device according to the present invention, the allocation data creating means creates allocation data directly charged to the belonging unit when the allocation destination is the belonging unit of the business operator. characterized by :

Further, in the common expense management device according to the present invention, the allocation data includes information on allocation destination items and information on allocation source items.

Further, the common expense management device according to the present invention is characterized by further comprising journal data creation means for creating journal data corresponding to the allocation data .

Further, a common cost management method according to the present invention is a common cost management method for managing common costs to be allocated, wherein the allocation data creation means generates one or a plurality of goods or services during a predetermined period When the allocation destination is an individual employee of a business operator, a predetermined proportional distribution rate generated based on the involvement period in which the individual said employee was involved in the said goods or said services during said predetermined period It is characterized by comprising an allocation data creation step of creating allocation data for each of the employees by multiplying the fixed amount of money generated for the service in the predetermined period .

In addition, a common expense management program according to the present invention is a common expense management program for managing common expenses that are allocation sources, wherein the computer is operated by one or more allocation destinations in a predetermined period of goods or services. In the case of individual employees of a business operator, a predetermined proportional distribution rate generated based on the period of involvement in which the individual employee was involved in the goods or services during the predetermined period It is characterized by functioning as allocation data creation means for creating allocation data for each of the employees by multiplying a fixed amount generated in a predetermined period .

ADVANTAGE OF THE INVENTION According to this invention, it is effective in being able to manage common expenses easily and accurately.

FIG. 1 is a block diagram showing an example configuration of a common expense management system including a common expense management device according to an embodiment of the present invention. FIG. 2 is a flow chart showing an overview of the processing procedure of the common expense management method executed by the common expense management device 100 in the common expense management system 1000 of FIG. FIG. 3 is a diagram schematically showing an example of project information registered in step S210 of FIG. FIG. 4 is a diagram schematically showing an example of property information registered in step S230 of FIG. FIG. 5 is a diagram schematically showing a configuration example of an allocation item master created in association with the classification information included in the property information of FIG. FIG. 6 is a diagram schematically showing an example of allocation destination information registered in step S230 of FIG. FIG. 7 is a diagram schematically showing an example of a group of records read out by the debt accounting process in step S240 of FIG. FIG. 8 is a diagram schematically showing an example of daily report data used in the allocation data creation process in step S250 of FIG. FIG. 9 is a diagram schematically showing an example of aggregated data obtained by aggregating the daily report data shown in FIG. 8 for the target month. FIG. 10 is a diagram schematically showing a first example of tabulated data obtained during the allocation data creation process in step S250 of FIG. FIG. 11 is a diagram schematically showing a second example of tabulated data obtained during the allocation data creation process in step S250 of FIG. FIG. 12 is a diagram schematically showing a first example of allocation data obtained as a result of the allocation data creation process in step 250 of FIG. FIG. 13 is a diagram schematically showing a second example of allocation data obtained as a result of the allocation data creation process in step 250 of FIG. FIG. 14 is a diagram for explaining the details of the allocation data and pre-allocation cost data shown in FIG. 13 shows details of the allocation data shown in FIG. 12; FIG. 15 is a diagram for explaining details of the allocation data and pre-allocation cost data shown in FIG. 14 shows details of the allocation data shown in FIG. 13; FIG. 16 is a diagram schematically showing a group of allocation data and cost data shown in FIGS. 14 and 15. FIG. FIG. 17 is a diagram schematically showing a first example of a record to be subjected to the divisional expense tabulation process in the allocation data creation process of step S250 of FIG. FIG. 18 is a diagram schematically showing a second example of a record to be subjected to department cost totalization processing in the allocation data creation processing of step S250 of FIG. FIG. 19 shows an example of a group of aggregated data obtained as a result of aggregating the group of records shown in FIGS. 17 and 18 for each belonging unit (for example, department). FIG. 20 is a diagram schematically showing allocation data obtained by allocating the aggregated data shown in FIG. 19 to each department. FIG. 21 is a diagram used to explain intra-departmental project allocation processing that can be performed during allocation data creation processing in step S250 of FIG. (b) is aggregated data for each project (project cost data), (c) is the first example of allocation data obtained as a result of processing, and (d) is the result of processing A second example of allocation data obtained is shown. FIG. 22 is a diagram schematically showing journal data created for each property as a result of the journal data creation process in step S250 of FIG. b) shows journal data for the second property, (c) shows journal data for the third property, and (d) shows journal data for the fourth property.

An embodiment of the present invention will be described in detail based on the drawings. In addition, this invention is not limited by this embodiment.

[1. Constitution]
An example configuration of a common expense management system including a common expense management apparatus according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example configuration of a common expense management system including a common expense management device according to an embodiment of the present invention.

A common expense management system 1000 shown in FIG. 1 includes a common expense management apparatus 100 as an information processing apparatus, a server 200, and a network 300 that communicably connects the common expense management apparatus 100 and the server 200. FIG.

The common expense management device 100 is a commercially available desktop personal computer, and is an information processing device for managing common expenses that are allocation sources. For example, one common expense management device 100 is installed in a department, such as a management department, that manages common expenses in an enterprise. Note that the common expense management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but can be a mobile device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), a smart phone, or a tablet personal computer. type information processing device. Further, a plurality of common expense management apparatuses 100 may be installed in the common expense management system 1000, and by synchronizing the plurality of common expense management apparatuses 100, a single common expense management apparatus 100 can be used. may function.

Common expense management device 100 includes control unit 102 , communication interface unit 104 , storage unit 106 , and input/output interface unit 108 . Each unit included in the common expense management device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicably connects the common expense management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with another device via a communication line. Here, the network 300 has a function of connecting the common expense management apparatus 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Therefore, the communication interface unit 104 is configured to be able to receive input information and the like from other information processing devices via the network 300 or via the network 300 and the server 200, and is capable of receiving input information from other information processing devices. is configured to be able to output predetermined information to.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores computer programs (including the program of the present invention) for performing various processes by giving commands to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used. Also, in this storage unit 106, various data used for executing the program of the present invention are stored in a writable/readable manner.

An input device 112 and an output device 114 are connected to the input/output interface unit 108 . The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that realizes a pointing device function in cooperation with a mouse.

The control unit 102 is a CPU or the like that comprehensively controls the common expense management device 100 . The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

Furthermore, the configuration of the storage unit 106 and the control unit 102 will be described in detail with reference to FIG.

As shown in FIG. 1, the storage unit 106 includes a project information storage area 106a, an allocation destination information storage area 106b, a performance record information storage area 106c, an allocation data storage area 106d, and a journal data storage area 106e. including.

The project information storage area 106a is an area for storing project information relating to a project, which will be described later, and holds the project information so that it can be output as necessary. The allocation destination information storage area 106b is an area for storing allocation destination information relating to allocation destinations, which will be described later, and holds the allocation destination information so that it can be output as necessary. The work record information storage area 106c is an area for storing work record information (for example, daily report data and aggregated data thereof) related to work record, which will be described later, and holds the work record information so that it can be output as necessary.

The allocation data storage area 106d is an area for storing allocation data indicating allocation results created by the common expense management device 100, and holds the allocation data so that it can be output as necessary. The journal data storage area 106e is an area for storing the journal data created by the common expense management device 100, and holds the journal data so that it can be output as necessary.

The control unit 102 comprises a plurality of modules, as shown in FIG. In the example shown in FIG. 1, the control unit 102 includes an allocation data creation unit 102a and a journal data creation unit 102b.

The allocation data creation unit 102a is a module that functions as an allocation data creation unit that creates allocation data by, for example, the process of FIG. 2, which will be described later. The journal data creation unit 102b is a module that functions as journal data creation means for creating journal data by, for example, the process of FIG. 2, which will be described later.

[2. process]
Next, a common expense management method executed in the common expense management system 1000 shown in FIG. 1 will be exemplified.

FIG. 2 is a flow chart showing an overview of the processing procedure of the common expense management method executed by the common expense management device 100 in the common expense management system 1000 of FIG. The processing shown in FIG. 2 is, in general, allocation data indicating allocation results for each item or each service and for each allocation destination when managing the common expenses that are the sources of allocation. is automatically created, and most of this processing is executed in the control unit 102 of the common expense management device 100. FIG.

In FIG. 2, first, in step S210, the common expense management device 100 accepts registration of project information.

Here, a project is a business unit that is a revenue and expenditure management unit. Projects registered in step S210 may borrow goods or receive services from other business operators (customers) (for example, use of software, rental of mobile phones, fixed-line phones, etc.). , PC, car lease), and work to pay expenses accordingly (i.e., management of expenses). , for the sake of convenience, it is also referred to as the “allocation source project”). Here, the term "predetermined period" refers to the term of a contract for goods or services with a business partner or a subdivided term of the contract term, such as a month in which accounting is totaled. In step S210, the registration may be performed by reading the project information corresponding to the expenditure management work among the existing project information. Further, in this step S210, maintenance (editing) of already registered project information may be performed.

FIG. 3 is a diagram schematically showing an example of project information registered in step S210 of FIG.

As shown in FIG. 3, the project information includes information identifying the project (for example, the project name and project number), information about the business partner, and furthermore, the subject of the expenditure management work or the subject of the contract with the business partner Include information about the management department (eg, management office and management department) that will be responsible.

Also, in step S220, registration of information on goods and services is accepted.

The goods and services registered in step S220 are registered as goods for convenience. The goods or services registered here are the goods or services for which the amount of money generated in a predetermined period is fixed, among the projects corresponding to the project information registered in step S210. Specifically, it refers to goods borrowed for a fixed amount (eg monthly or annual fee) or services provided for a fixed amount (eg monthly or annual fee). It should be noted that, even for goods or services whose accrual amount is not fixed during the contract period, goods or services whose accrual amount is fixed during a predetermined period may be registered. For example, in the case of goods or services for which the amount generated is fixed every other month, the monthly fixed amount may be divided into two and registered, or may be registered every other month.

FIG. 4 is a diagram schematically showing an example of property information registered in step S230 of FIG.

As shown in FIG. 4, the property information includes information (for example, property name, property number, and property classification) that specifies the goods or services (property) for which the amount generated in a predetermined period is fixed, and the amount generated in the predetermined period. It contains an amount and information identifying the source project of the allocation. The amount of money generated in a predetermined period is, for example, a monthly usage fee. Therefore, for example, in the case of a property with an annual fee system, an amount equivalent to the monthly fee is registered. By including the information specifying the allocation source project in the property information, it becomes possible to associate the property with the allocation source project. The property number may include property classification information. For example, a character string specifying the property classification information may be added to the character string that constitutes the property number.

Furthermore, as shown in FIG. 4, the property information preferably includes information on the contract period, so that the relationship between the predetermined period and the contract period can be easily grasped. Moreover, even if properties that are not within the contract period can be held as property information, they may not be recognized or extracted at the time of allocation.

FIG. 5 is a diagram schematically showing a configuration example of an allocation item master created in association with the classification information included in the property information of FIG.

The allocation item master as shown in FIG. 5 is a master that is referred to when creating journal data in step S260, which will be described later. Therefore, it is not necessary to prepare the allocation item master shown in FIG. 5 unless journal data is created. The allocation item master shown in FIG. 5 sets the transfer item and the transfer source item according to the transfer destination for each property classification information included in the property information shown in FIG. This makes it possible to quickly create journal data. Instead of preparing the allocation item master shown in FIG. 5, a master in which the transfer item and the transfer source item are set according to the transfer destination may be prepared for each property.

Subsequently, in step S230, registration of allocation destination information is accepted. The process of step S230 is performed before the last day of the predetermined period so that the allocation result of the common expenses for the predetermined period can be obtained. For example, if the predetermined period is in units of months, the process of step S230 may be performed before the predetermined closing date of the current month (the target month for common cost allocation), or if no new contract is made, for example May be done in the previous month.

In the present embodiment, allocation destination information refers to information relating to allocation destinations to which common costs are imposed, which are allocation sources. Any constituent unit or business unit in a business operator can be set as an allocation destination. department) is preferably set, and it is preferable that "none" indicating that there is no setting can be set as the allocation destination.

FIG. 6 is a diagram schematically showing an example of allocation destination information registered in step S230 of FIG.

In the example of allocation destination information shown in FIG. 6, information specifying allocation destinations (allocation destination name, allocation destination code, and allocation destination classification) is registered for each target month and for each property. The allocation destination indicated by the allocation destination information shown in FIG. project) and affiliation unit (eg department).

For example, if the property is a personal computer lent to an employee, the employee is selected as the destination of the property. If an employee cannot or does not need to be specified as an allocation destination, either the business unit or the department unit is selected as the allocation destination. Specifically, when the property is a leased vehicle and the vehicle is used in a contracted construction project, the project corresponding to the construction work is selected as the allocation destination. If it is not possible or necessary to identify the employees involved in the property, the business unit, or the unit they belong to (for example, if the property is registered but there is no actual usage), the distribution "None" is selected as the destination. Then, when "none" is selected as the destination of allocation, the common expenses of the property can be used for management decisions, for example, assuming that there is no actual usage (that is, useless). As shown in FIG. 6, it is preferable to include the above-mentioned allocation destination options in the property information as allocation destination classification information, so that it is possible to aggregate for each allocation destination classification. . The allocation destination classification information is automatically obtained from the employee code (e.g., 4-digit number), project number (e.g., code symbol "PJ" at the beginning), and department code (e.g., 5-digit number). It is preferable to configure, thereby saving the trouble of setting the allocation destination classification information. In addition, since the allocation destination information for each target month and for each property registered as described above is usually the same during the contract period, it is easy to copy the previous month's information for the next month as well. Information can be registered.

Also, as shown in FIG. 6, the allocation destination information includes information specifying the allocation source project. As a result, the allocation source and the allocation destination are linked to each other. The allocation source project number as the information specifying the allocation source project can be obtained, for example, by referring to the property information (property name or property number) included in the allocation destination information with the property information registered in step S220. Since it can be obtained, it is preferable that the allocation source project number is automatically set at the stage when the property information is set in the allocation destination information. Alternatively, at the stage when the information specifying the allocation source project is set in the allocation destination information, the property information registered in step S220 can be referred to in the allocation destination information. may be configured to list automatically. As a result, it is possible to reduce the time and effort required to register the allocation destination information.

Further, in step S240, the debt is recorded for a predetermined period (debt recording process). The process of step S240 is preferably executed on or after the last day of the predetermined period (target month). For example, it may be automatically executed on a preset date and time.

Specifically, in this step S240, the records relating to the debts (expenses) corresponding to the use of the property (goods or services) for which the date belonging to the predetermined period is the recording date are read. Records relating to obligations are usually created based on contracts with business partners or statements of delivery or invoices from business partners, and are readable, for example, stored in the storage unit 106 . In step S240, for example, if the target month is April, the day the accounting date belongs to the target month (March 26 to April 25 as an example, or April 1 to April 30 as another example) are retrieved and retrieved. Records to be read include records for which expenses have actually been paid, and records for properties for which expenses have not actually been paid (for example, the payment date or scheduled payment date is later than the recording date). dated records) may be included. Therefore, the records related to debts (expenses) may be referred to as expense payment schedule data.

FIG. 7 is a diagram schematically showing an example of a group of records read out by the debt accounting process in step S240 of FIG. As shown in Fig. 7, since records related to debt are usually created based on contracts with business partners or delivery notes or invoices from business partners, information that identifies the source project but does not include information on the users (allocation destinations) of the corresponding goods or services.

Then, in step S250, allocation data creation processing is performed. In the allocation data creation process, at least the project information registered in step S210, the allocation destination information registered in step S230, and the debt information obtained in the debt recording process in step S240 are used. Debt information corresponds to the common expense that is the source of allocation for the target month. In this embodiment, the process of creating allocation data is performed according to a preset procedure for each allocation destination classification information included in the allocation destination information. That is, different processing is performed according to the allocation destination classification information.

First, a case where the allocation destination classification information is an employee (employee) will be described.

When the allocation destination classification information is an employee (employee), the common expense management device 100 first acquires the involvement period information regarding the involvement period in which each employee was involved in goods or services in the target month (predetermined period). do. The involvement period information can be acquired, for example, by aggregating daily reports on the employee's work performance in the target month. Therefore, in order to acquire involvement period information, aggregated information related to daily reports aggregated in advance for the target month may be acquired, but the following description includes processing for directly aggregating daily report data.

FIG. 8 is a diagram schematically showing an example of daily report data used in the allocation data creation process in step S250 of FIG.

In the example of the daily report data shown in FIG. 8, the work performance of each employee is recorded, and the working day (target day) or working unit (eg project) or belonging unit (eg department) involved in working hours is also recorded. ing. Therefore, it is possible to acquire the involvement period information regarding the period of involvement in the goods or services on the target date. Therefore, by aggregating the daily report data of the dates belonging to the target month, it is possible to acquire the involvement period information regarding the involvement period in which the goods or services were involved in the target month.

FIG. 9 is a diagram schematically showing an example of aggregated data obtained by aggregating the daily report data shown in FIG. 8 for the target month.

The aggregated data shown in FIG. 9 is data obtained by aggregating the daily report data shown in FIG. 8 for the target month, and may be created by the common expense management device 100, or data read from another device. may be The example of aggregated data shown in FIG. 9 further includes proportional division ratio information regarding the proportional division ratio. For example, when aggregating the daily report data for the target month, this proportional division rate is calculated using the number of aggregated daily report data (corresponding to the number of working days in the target month) as the denominator, and the involved work unit (project) or department unit (for example, department) as the numerator. The method of calculating the proportional division ratio is not limited to the method described above, but it is preferable to use a method that reflects the work record of the employee as much as possible.

Subsequently, the common cost management device 100 performs direct cost totalization processing. Note that this direct cost tallying process may be performed prior to or in parallel with the acquisition of the involvement period information described above.

In the direct cost totaling process, firstly, records relating to the debts of properties whose recording date falls on a day belonging to a predetermined period are totaled for each project. Specifically, among the records related to debts read out as a result of the debt recording process in step S240, the records including the information specifying the project are tabulated for each project. It should be noted that it is not necessary to tally records that do not contain information specifying allocation destination projects. Through this tabulation process, tabulated data for each project is obtained. In addition, since the accounting department is determined for each project, the aggregated data may include accounting department information regarding the accounting department.

FIGS. 10 and 11 are diagrams schematically showing examples of aggregated data obtained during the allocation data creation process in step S250 of FIG. FIG. 10 is an example of a group of aggregated data obtained as a result of aggregating the group of records shown in FIG. 7 for each allocation source project, and FIG. 11 is a group of aggregated data different from FIG. is an example of The group of aggregated data shown in FIG. 10 is the same as the group of records shown in FIG. 7 except that it includes accounting department information. Because there was one. A group of aggregated data shown in FIG. 10 or FIG. 11 is original data before common cost allocation, that is, cost data.

Next, the common expense management device 100 creates allocation data for each property based on the proportional division ratio information acquired as described above and the cost data for each allocation source project. Specifically, by multiplying the amount information included in the cost data by the numerical value indicated by the proportional division ratio information for each property, allocation data indicating the result of charging the corresponding employee for each property can be obtained. That is, the obtained allocation data for each property indicates the allocation results for each allocation source project, each employee, and each property.

Next, a case where the allocation destination classification information is a business unit (project) will be described. In this case, the common cost management device 100 directly charges the cost data for each allocation source project obtained as described above to the allocation destination business units (projects). That is, the allocation source amount is transferred to the allocation destination amount. In addition, the method of imposition is not limited to the above method, and other methods may be employed.

Also, if the allocation destination classification information is a unit of affiliation (for example, department), the common cost management device 100 converts the cost data for each allocation source project obtained as described above to the unit of affiliation of the allocation destination. (e.g. department) directly. That is, the allocation source amount is transferred to the allocation destination amount. In addition, the method of imposition is not limited to the above method, and other methods may be employed.

12 and 13 are diagrams schematically showing examples of allocation data obtained as a result of the allocation data creation processing in step 250 of FIG. FIG. 12 shows allocation data corresponding to the first record shown in FIG. 10, and FIG. 13 shows allocation data corresponding to the second record shown in FIG. 12 and 13 are obtained by referring to the allocation item master shown in FIG.

As shown in FIGS. 12 and 13, allocation data is created for each allocation source project, each employee, and each property. For this reason, the common cost, which is the allocation source, is charged to the allocation destination with high accuracy. Although not shown in FIGS. 12 and 13, for common costs for which "none" is set as allocation destination classification information, for example, it is possible to directly charge the management department of the allocation source project. Allocation data should be created. As a result, it is possible to easily identify the management division of the idle property, which can be used for management decisions.

14 and 15 are diagrams for explaining the details of the allocation data and pre-allocation cost data shown in FIGS. 12 and 13, respectively. (b) shows the details of the allocation data shown in FIGS. 12 and 13. FIG. FIG. 16 is a diagram schematically showing a group of allocation data and cost data shown in FIGS. 14 and 15. FIG. As shown in FIGS. 14 to 16, allocation data and cost data before and after generation of allocation data in step S250 of FIG. 2 can be expressed. In particular, by creating materials such as those shown in Figures 14 to 16, it is possible to easily grasp how the allocation source project, which was recorded as a common cost, was allocated to the allocation destination. . In this way, it is possible to obtain materials that can be utilized in management decisions.

In addition, in the above description of direct cost totalization processing, totalization was performed for records containing information identifying a project. (department expense aggregation process).

FIGS. 17 and 18 are diagrams schematically showing examples of records to be subjected to department cost totalization processing in the allocation data creation processing of step S250 of FIG. The records shown in FIGS. 17 and 18 are obtained by excluding records including information specifying allocation destination projects from among records relating to debts of properties whose recording date falls on a day belonging to a predetermined period. FIG. 19 shows an example of a group of aggregated data obtained as a result of aggregating the group of records shown in FIGS. 17 and 18 for each belonging unit (for example, department). The group of totalized data shown in FIG. 19 is the original data before the inter-departmental allocation process described below, that is, the cost data.

Subsequently, inter-departmental allocation processing is performed using the tabulated data tabulated for each department shown in FIG. In the interdepartmental allocation process, the apportionment rate is set in advance for each department and for each allocation source item for multiple departments that are allocation destinations. You can get additional data. For example, when the allocation source item is "Travel Expenses" and the allocation source department is the Administration Headquarters (department code: 10000), the allocation destination departments are the Administrative Management Section, the Accounting Section, and the Construction Section. In addition, the proportional division rate is set to 0.25 for each of the management section, accounting section, and construction section. Thus, by allocating the aggregated data shown in FIG. 19 to each department, allocation data as shown in FIG. 20 is obtained.

Also, in the above description of the department cost totalization process, allocation is made for each allocation destination department, but it is also possible to perform allocation for each allocation destination project within the department (intra-department project allocation process). Specifically, by setting the apportionment rate for each department and each allocation source item in advance for multiple projects that are allocation destinations, the apportionment data for each project can be obtained by using the apportionment rate. Obtainable. For example, when the allocation source item is "Travel Expenses" and the allocation source department is the construction section (department code: 92000), multiple projects (for example, two projects) can be selected as allocation destination projects. and set the apportionment rate to 0.1 and 0.2 respectively for the two projects. As a result, allocation is performed using aggregated data for each department (department cost data) as shown in FIG. 21(a) and aggregated data for each project (project cost data) shown in FIG. 21(b) , the allocation data shown in FIGS. 21(c) and 21(d) can be obtained. Here, FIG. 21(c) shows cost data for each department obtained after intra-departmental project allocation processing, and FIG. 21(d) shows cost data for each project obtained after intra-departmental project allocation processing. is shown.

Next, in step S260, the common expense management device 100 performs journal data creation processing. Journal data is created as needed. The journal data is created by setting items by referring to the allocation item master shown in FIG. 5 based on the allocation data indicating the allocation results created in step S250. FIG. 22 shows the journal data created for each property. (a) is the journal data for the first property, (b) is the journal data for the second property, ( c) shows journal data for the third property, and (d) shows journal data for the fourth property. Note that, instead of the common expense management device 100 executing the journal data creation process in step S260, another information processing device may execute the processing. In this case, allocation data is supplied from the common expense management apparatus 100 to the other information processing apparatus, and journal data is created based on the allocation item master.

As described in detail above, according to the process of the common cost management method shown in FIG. and allocation destination information regarding one or more allocation destinations in the predetermined period of time, and the result of charging the accrued amount to the one or more allocation destinations for each of the goods or for each service. Allocation data is created (step S250). This allows the user to easily and accurately manage common expenses. Further, according to the process of FIG. 2, journal data is also created (step S260). As a result, the user can easily obtain the journal data, and as a result, can make use of it for management decisions.

[3. Other embodiments]
The present invention may be implemented in various different embodiments other than the embodiments described above within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all of the processes described as being manually performed Alternatively, some can be done automatically by known methods.

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

Also, with respect to the common expense management device 100 and the common expense management system 1000, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, all or any part of the processing functions of the common expense management device 100, particularly the processing functions performed by the control unit, are realized by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware using wired logic. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing apparatus to execute the processing described in the present embodiment, and can be used for common cost management as necessary. It is read mechanically by the device 100 . That is, a storage unit such as a ROM or HDD (Hard Disk Drive) stores a computer program for giving commands to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM and constitutes a control section in cooperation with the CPU.

Also, this computer program may be stored in an application program server connected to common expense management apparatus 100 via an arbitrary network (for example, network 300). It is also possible to download.

Also, the program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered (trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Disc (registered trademark) such as Blu- shall include any "portable physical medium". Therefore, a recording medium storing a program for executing the processing described in this specification also constitutes the present invention.

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single configuration, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, the installation procedure after reading, and the like.

The various databases stored in the storage unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks. programs, tables, databases, and files for web pages.

Further, the common expense management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which arbitrary peripheral devices are connected. Moreover, the common expense management device 100 may be implemented by installing software (including programs, data, etc.) that causes the device to implement the processes described in this specification.

Furthermore, the specific forms of distribution and integration of devices are not limited to those shown in the figures, and all or part of them can be functionally or physically arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be implemented selectively.

The present invention is particularly useful in managing common costs that are allocation sources.

100 common expense management device 102 control unit 102a allocation data creation unit 102b journal data creation unit 104 communication interface unit 106 storage unit 106a project information storage area 106b allocation destination information storage area 106c work performance information storage area 106d allocation data storage area 106e journal data storage area 108 input/output interface unit 112 input device 114 output device 200 server 300 network 1000 common expense management system

Claims (9)

A common cost management device for managing common costs to be an allocation source,
When one or more allocation destinations of goods or services during a predetermined period are individual employees of a business operator, generated based on the involvement period in which the individual said employees were involved in said goods or said services during said predetermined period allocation data creation means for creating allocation data for each of the employees by multiplying the fixed amount of money generated for the goods or services in the predetermined period by the predetermined proportional division rate;
A common expense management device characterized by: The predetermined period is a contract period for the goods or services or a subdivided period of the contract period ;
The common expense management device according to claim 1, characterized by: said allocation data creation means acquiring said involvement period from work record information relating to said individual employee's work record ;
3. The common expense management device according to claim 1 or 2, characterized by: The allocation data creating means is
creating allocation data directly charged to the business unit when the allocation destination is a business unit in the business operator;
The common expense management device according to claim 1, characterized by: The allocation data creating means is
When the allocation destination is a unit of belonging to a business operator, creating allocation data directly charged to the unit of belonging;
The common expense management device according to claim 1, characterized by: the allocation data includes information on allocation destination items and information on allocation source items ;
The common expense management device according to any one of claims 1 to 5, characterized by: further comprising journal data creation means for creating journal data corresponding to the allocation data;
The common expense management device according to any one of claims 1 to 6, characterized by: A common cost management method for managing common costs to be allocated, comprising :
When the allocation data creation means determines that one or more allocation destinations of goods or services in a predetermined period are individual employees of a business operator, the individual employees are assigned to the goods or services in the predetermined period. Allocation that creates allocation data for each of said employees by multiplying a fixed accrued amount of said goods or said services for said predetermined period by a predetermined proration rate generated based on the period of involvement. providing a data creation step;
A common expense management method characterized by: A common cost management program for managing common costs that are allocation sources,
the computer,
When one or more allocation destinations of goods or services during a predetermined period are individual employees of a business operator, generated based on the involvement period in which the individual said employees were involved in said goods or said services during said predetermined period functioning as an allocation data creation means for creating allocation data for each employee by multiplying the fixed amount of money generated for the goods or services in the predetermined period by the predetermined proportional division ratio ,
A common expense management program characterized by:

Images