JP7220263B2 - Information processing device, information processing method and program - Google Patents

Description

The present invention relates to an allocation device, an allocation method, and an allocation program.

Patent Literature 1 discloses a fixed asset ledger management device that divides each part that constitutes a building into groups and distributes the common cost of the entire new building construction to each group proportionally according to the direct cost of each group. (See paragraphs 0022, 0040, 0042, etc.).

Japanese Unexamined Patent Application Publication No. 2013-218500

However, in the conventional technology, when a company or the like purchases a plurality of fixed assets, it is possible to designate some fixed assets among the plurality of fixed assets as allocation destinations such as common expenses that are allocation sources. It was difficult. In addition, in the conventional technology, it is difficult to apportion a plurality of common costs and the like to the purchase price of fixed assets in multiple stages. For this reason, the person in charge at companies etc. allocates common expenses to each fixed asset by manual calculation, and there is a demand for reducing the workload related to allocation and improving the efficiency of the registration work of purchased fixed assets. had been

The present invention has been made in view of the above, and aims to reduce the workload of the person in charge of allocating common expenses to multiple fixed assets and to streamline the work of registering purchased fixed assets. It is an object of the present invention to provide an allocation device, an allocation method, and an allocation program capable of

In order to solve the above-described problems and achieve the object, an allocation apparatus according to the present invention has a plurality of fixed assets as allocation destinations, and a plurality of fixed assets included in the acquisition cost of at least one of the plurality of fixed assets. and a storage unit for allocating each amount of the allocation source to each purchase price of the allocation destination, with the cost or common cost as the allocation source. The storage unit stores a detail table that includes records corresponding to allocation destinations and allocation sources, data indicating the execution order of allocation, and pegging data that links the allocation sources and allocation destinations, in association with each other. Store the table and . In the allocation source record, which is the record corresponding to the allocation source, the allocation source and the amount are registered in correspondence, and in the allocation destination record, which is the record corresponding to the allocation destination, Allocation destinations and purchase prices are registered in association with each other. The control unit, in accordance with the order of execution, identifies from the detail table the allocation source record and the allocation destination record corresponding to the allocation source and allocation destination linked by the linkage data, and associates it with the allocation source. an allocation process for allocating the calculated amount to the purchase price associated with the allocation destination. In the allocation process, when a plurality of allocation destinations are specified, the control unit divides the amount proportionally based on the purchase price after the amount has been allocated in the allocation up to one before in the order of execution. The prorated amount obtained by is distributed to the purchase price.

Further, in the allocation apparatus according to the present invention, in the allocation process, the control unit determines the ratio of the purchase price of each of the allocation destinations to the total value of the purchase prices associated with the plurality of allocation destinations. The amount will be apportioned accordingly.

In addition, in the allocation apparatus according to the present invention, in the allocation process, the control unit calculates the total amount of consumption tax applied to a plurality of fixed assets for the purchase price for each allocation destination after the amount has been allocated. is proportionally divided to calculate the tax-included acquisition price for each fixed asset.

Also, an allocation method according to the present invention is an allocation method executed by an information processing apparatus having a storage unit and a control unit. The storage unit includes a detail table that includes records corresponding to allocation destinations that are a plurality of fixed assets and allocation sources that are a plurality of expenses or common expenses that are included in the acquisition cost of at least one of the plurality of fixed assets; , and an apportionment table that associates and saves data indicating the execution order of allocation and linking data linking the allocation source and the allocation destination. In the allocation source record, which is the record corresponding to the allocation source, the allocation source and the amount of the allocation source are registered in correspondence, and the allocation destination, which is the record corresponding to the allocation destination In the record, allocation destinations and respective purchase prices of the allocation destinations are associated and registered. Further, the allocation method according to the present invention is executed by the control unit, and according to the order of execution, allocation source records and allocation destination records corresponding to the allocation source and the allocation destination linked by the linked data are specified. It includes a specifying step of specifying from the table and an allocating step of allocating the amount associated with the allocation source to the purchase price associated with the allocation destination. In the allocation step, when a plurality of allocation destinations are specified, the control unit divides the amount proportionally based on the purchase price after the amount has been allocated in the allocation up to one before in the order of execution, and The prorated amount obtained by is distributed to the purchase price.

Also, an allocation program according to the present invention is an allocation program to be executed by an information processing apparatus having a storage unit and a control unit. The storage unit includes a detail table that includes records corresponding to allocation destinations that are a plurality of fixed assets and allocation sources that are a plurality of expenses or common expenses that are included in the acquisition cost of at least one of the plurality of fixed assets; , and an apportionment table that associates and saves data indicating the execution order of allocation and linking data linking the allocation source and the allocation destination. In the allocation source record, which is the record corresponding to the allocation source, the allocation source and the amount of the allocation source are registered in correspondence, and the allocation destination, which is the record corresponding to the allocation destination In the record, allocation destinations and respective purchase prices of the allocation destinations are associated and registered. In addition, the allocation program according to the present invention creates an allocation source record and an allocation destination record corresponding to the allocation source and the allocation destination linked by the linked data in accordance with the order of execution for the control unit to execute. It includes a specifying step of specifying from the detail table and an allocating step of allocating the amount associated with the allocation source to the purchase price associated with the allocation destination. In the allocation step, when a plurality of allocation destinations are specified, the control unit divides the amount proportionally based on the purchase price after the amount has been allocated in the allocation up to one before in the order of execution, and The prorated amount obtained by is distributed to the purchase price.

According to the present invention, it is possible to reduce the work load of the person in charge of allocating common costs and the like to a plurality of fixed assets, and to improve the efficiency of the work of registering purchased fixed assets.

1 is a block diagram illustrating an example of a configuration of an allocation device according to an embodiment; FIG. FIG. 2 is a diagram illustrating an example of a table configuration of a database according to the embodiment; FIG. 3 is a diagram illustrating an example of the flow of a series of processes including allocation according to the embodiment; FIG. 4 is a diagram illustrating an example of an estimate data input screen according to the embodiment; FIG. 5 is a diagram illustrating an example of registration of estimate data according to the embodiment; FIG. 6 is a flowchart illustrating an example of the flow of allocation processing according to the embodiment. FIG. 7 is a diagram illustrating an example of an allocation execution screen according to the embodiment; FIG. 8 is a flowchart illustrating an example of the flow of apportionment processing at apportionment level 1 according to the embodiment. 9A is a diagram illustrating an example of estimation data to be apportioned at apportionment level 1 according to the embodiment; FIG. FIG. 9B is a diagram illustrating an example of apportionment processing at apportionment level 1 according to the embodiment; 9C is a diagram for explaining an example of the apportionment processing result of apportionment level 1 according to the embodiment; FIG. 10A is a diagram illustrating an example of estimation data to be apportioned at apportionment level 2 according to the embodiment; FIG. FIG. 10B is a diagram illustrating an example of apportionment processing at apportionment level 2 according to the embodiment. FIG. 10C is a diagram illustrating an example of a result of apportionment processing at apportionment level 2 according to the embodiment; 11A is a diagram illustrating an example of estimation data to be apportioned at apportionment level 3 according to the embodiment; FIG. FIG. 11B is a diagram illustrating an example of apportionment processing at apportionment level 3 according to the embodiment; FIG. 11C is a diagram illustrating an example of the apportionment processing result of apportionment level 3 according to the embodiment; 12A is a diagram illustrating an example of data registered in an allocation header database and an allocation detail database after allocation processing according to the embodiment; FIG. FIG. 12B is a diagram illustrating an example of data registered in the quotation header database, the quotation detail database, and the quotation detail database after allocation processing according to the embodiment;

Embodiments of an allocation device, an allocation method, and an allocation program according to the present invention will be described in detail below with reference to the drawings. In addition, this invention is not limited by this embodiment.

[1. overview]
When a company purchases multiple fixed assets such as multiple lands, buildings, and fixtures at once, the amount of common expenses such as miscellaneous expenses and discounts incurred at the time of purchase are listed together on the delivery note. Sometimes. However, companies, etc. record the acquisition amount including the amount of common expenses such as miscellaneous expenses and discounts for each individual fixed asset in the accounting process. Hereinafter, when such various expenses and various common expenses are collectively referred to as common expenses and the like.

In addition, there are cases where delivery and installation costs and discounts for fixtures and the like included in common expenses and the like are applied only to some fixed assets among a plurality of fixed assets that are collectively purchased. In addition, multi-stage allocation such as allocating common expenses proportionally to the purchase price of fixed assets, and further dividing and allocating other common expenses etc. to the amount after the allocation may be performed. However, with the conventional technology, it is difficult to specify allocation destinations and perform multi-step allocation. For this reason, the person in charge at companies etc. allocates common expenses to each fixed asset by manual calculation, and there is a demand for reducing the workload related to allocation and improving the efficiency of the registration work of purchased fixed assets. had been

Therefore, in this embodiment, for example, an allocation device that can reduce the workload of a person in charge of allocating common expenses to a plurality of fixed assets and improve the efficiency of the work of registering purchased fixed assets. , provides allocation methods and allocation programs. Specific configurations and operations will be described below.

[2. composition]
The configuration of the allocation device 100 according to this embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of an allocation device 100 according to this embodiment.

The allocation device 100 is a commercially available desktop personal computer. Note that the allocation device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable type computer such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), a smart phone, or a tablet personal computer. It may be an information processing device.

The allocation device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108, as shown in FIG. Each unit included in the allocation device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicably connects the allocation 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 allocation device 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). Note that data stored in the storage unit 106 to be described later may be stored in the server 200 . Moreover, each functional unit included in the control unit 102 may be included in the server 200 .

An input device 112 and an output device 114 are connected to the input/output interface section 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 cooperates with the mouse to provide a pointing device function. Note that, hereinafter, the output device 114 may be referred to as the monitor 114 and the input device 112 may be referred to as the keyboard 112 or the mouse 112 .

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program 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.

As shown in FIG. 1, the storage unit 106 includes an estimate header database (DB) 106a, an estimate detail database (DB) 106b, an estimate detail database (DB) 106c, an allocation header database (DB) 106d, an allocation Stores an itemization database (DB) 106e, an asset database (DB) 106f, a depreciation database (DB) 106g, a monthly depreciation database (DB) 106h, and a journal database (DB) 106i.

The estimate header database 106a is a database in which outline information of estimate data relating to the purchase of fixed assets is registered. The summary information of the estimate data is information related to the entire transaction of multiple fixed assets purchased in a lump.

FIG. 2 is a diagram showing an example of the table structure of the database according to this embodiment. As shown in FIG. 2, the quotation header database 106a includes, as items, quotation number, date of acquisition, order amount excluding tax, order consumption tax, and allocation number.

The item "estimate number" is an item in which an estimate number is registered. The quotation number is a number or code that identifies a fixed asset purchase transaction. The quotation number may be assigned for each quotation (delivery statement) when purchasing a fixed asset, or may be a number obtained by integrating a plurality of quotations. The estimate number is the primary key of the estimate header database 106a, and the data stored in other items are associated with the estimate number. The item "estimate number" is an item that links the estimate header database 106a and the estimate detail database 106b, which will be described later.

The item “acquisition date” is an item for registering the date when the fixed asset to be registered was acquired. Alternatively, the date of acquisition may be the date of input of the estimate data, or the date of delivery described in the estimate.

The item "order tax excluded amount" is an item in which the total acquisition price for each fixed asset purchase transaction is registered. In addition, the tax-excluded order amount does not include consumption tax.

The item "order consumption tax" is an item for registering the amount of consumption tax to be applied to the order tax-excluded amount. In other words, the order consumption tax is the total amount of consumption tax for each fixed asset purchase transaction.

The item "allocation number" is an item in which an allocation number specifying the allocation process is stored after the allocation process such as the common cost is performed by the allocation unit 102d, which will be described later. The item "allocation number" is an item that links the quotation header database 106a and the allocation header database 106d described later.

Returning to FIG. 1, the estimate detail database 106b is a database in which the detail information for each fixed asset of the estimate data regarding the purchase of fixed assets is registered. In addition, detailed information such as common costs related to the purchase of fixed assets is also registered in the estimate detailed database 106b. The estimate detail database 106b is an example of a detail table in this embodiment.

As shown in FIG. 2, the quotation detail database 106b includes items such as quotation number, quotation internal line number, asset expense common expense category, asset name, quotation amount, quotation quantity, and tax-excluded amount after apportionment. , apportionment consumption tax, apportionment tax included amount, and apportionment total amount.

The item "estimate number" is an item in which an estimate number is registered, and is an item that links the estimate detail database 106b and the estimate header database 106a.

The item "estimation internal line number" is an item in which the estimate internal line number is registered. The estimated internal line number is a number or code for specifying a fixed asset or common expense related to a fixed asset purchase transaction. One quotation number is associated with one or more quotation internal line numbers. The quotation number and the quotation internal line number are the primary keys of the quotation detail database 106b. Data stored in other items of the quotation detail database 106b are associated with the quotation number and the quotation internal line number.

Also, the item "estimate number" and the item "estimate internal line number" are items that link the estimate details database 106b with the estimate details database 106c and allocation details database 106e, which will be described later.

The item "asset expense common expense category" is an item in which a category value or code for identifying whether the information registered for each record is a fixed asset, an expense, or a common expense is set. In other words, the asset expense common expense classification indicates whether each record included in the estimate detail database 106b is a record corresponding to a fixed asset that is an allocation destination or a record that corresponds to a common expense etc. that is an allocation source, distinguish between For example, when the value set in the item "asset expense common expense category" is "1", the registered information is a fixed asset. Also, when the value set in the item "asset expense common expense category" is "9", the registered information is expense or common expense. The value of the asset expense common expense category in the present embodiment is an example, and the present invention is not limited to this.

Among the records included in the estimate detail database 106b, the record corresponding to the fixed asset that is the allocation destination is an example of the allocation destination record in this embodiment. Also, the record corresponding to the common cost or the like, which is the allocation source, is an example of the allocation source record in this embodiment.

The item "asset name" is an item in which names such as fixed assets or common expenses are registered.

The item "estimated amount" is an item in which an individual estimated amount for each fixed asset is registered. Estimated amounts of common expenses and the like are individually registered in the item "estimated amount". The individual estimated amount for each fixed asset is an example of the purchase price in this embodiment. Also, the estimated amount of money such as the common cost is an example of the amount in the present embodiment.

The item "estimated quantity" is an item in which the quantity of each fixed asset to be purchased is registered.

In the item "tax-excluded amount after apportionment", the purchase price to which the common costs etc. are distributed is registered for each fixed asset after the common costs etc. have been allocated by the allocation unit 102d, which will be described later. item. The tax-excluded amount after apportionment is an example of the acquisition price in this embodiment. Also, the tax-excluded amount after apportionment is an example of the purchase price for each destination after the amount is allocated.

The item "proportionally divided consumption tax" is obtained by dividing the order consumption tax in the estimate header database 106a proportionally according to the value of the after-tax-excluded amount after the allocation processing of common costs, etc., is performed by the allocation unit 102d, which will be described later. This is an item for which a value is set.

The item "amount including tax after apportionment" is an item in which a value obtained by adding the consumption tax to the amount after apportionment before tax is set. The tax-included amount after proportional division is an example of the tax-included acquisition price in the present embodiment.

The item "proportionally divided total amount" is an item in which the amount of common expenses etc. allocated to each fixed asset to be purchased after the allocation processing of the common expenses etc. is performed by the allocation unit 102d described later is set. is.

Returning to FIG. 1, the estimate detail database 106c is a database in which the execution order of allocation and linking data linking the allocation source and the allocation destination are registered for the estimation data related to the purchase of fixed assets. . The estimate detail database 106c is an example of a proportional division table in this embodiment. As shown in FIG. 2, the quotation detail database 106c includes items such as quotation number, quotation internal line number, corresponding apportionment level, corresponding apportionment code, and apportionment level amount.

The item "estimate number" is an item in which an estimate number is registered, and is an item that links the estimate detail database 106c and the estimate detail database 106b.

The item "estimation internal line number" is an item in which an estimate internal line number is registered, and is an item that links the estimate detail database 106c and the estimate detail database 106b.

The item "corresponding apportionment level" is an item in which a corresponding apportionment level corresponding to a fixed asset or common expense specified by an estimate number and an estimate internal line number is registered. The corresponding apportionment level is a value or code that indicates the execution order of allocation when common expenses are divided into multiple levels (multiple levels) and allocated. The corresponding apportionment level is an example of data indicating the execution order of allocation in this embodiment. The details of apportionment based on the corresponding apportionment level will be described later.

The item "corresponding apportionment code" is an item in which a corresponding apportionment code corresponding to a fixed asset or common expense specified by an estimate number and an estimate internal line number is registered. The corresponding apportionment code is data that associates the common cost, etc., which is the source of allocation, with the fixed asset, which is the destination of allocation. For example, if there are common expenses, etc., that only some of the fixed assets purchased in bulk have, the corresponding common expenses, etc., that are the source of allocation and some of the A fixed asset is identified by a corresponding apportionment code. Also, when a plurality of corresponding apportionment codes are set within the same corresponding apportionment level, for example, apportionment may be performed in ascending order of the corresponding apportionment codes. The corresponding apportionment code is an example of linking data linking the allocation source and the allocation destination in this embodiment.

Also, the item "corresponding apportionment level" and the item "corresponding apportionment code" are items that link the detailed quotation database 106c and the allocation details database 106e, which will be described later.

The item "amount of apportionment level" is allocated for each corresponding apportionment level and each corresponding apportionment code for each fixed asset to be purchased after the allocation processing of common expenses, etc., is performed by the allocation unit 102d, which will be described later. This is an item in which the amount of common expenses, etc., is set.

The estimate number, the estimate internal line number, the corresponding apportionment level, and the corresponding apportionment code are the primary keys of the estimate detail database 106c, and the apportionment level amount is associated with these items.

Returning to FIG. 1, the allocation header database 106d is a database in which outline information of allocation data, which is the result of allocation of costs or common costs to fixed assets, is registered. As shown in FIG. 2, the allocation header database 106d includes items such as allocation number and registration date.

The item "allocation number" is an item in which an allocation number specifying an allocation process is stored, and is an item that links the allocation header database 106d and the estimate header database 106a. The item "allocation number" is also an item that links the allocation header database 106d and the allocation detail database 106e, which will be described later.

The item "registration date" is an item in which the date when the allocation data was registered is stored.

Returning to FIG. 1, the allocation detail database 106e is a database in which detailed information of allocation data, which is the result of allocation of costs or common costs to fixed assets, is registered. The detailed information of the allocation data is data including the amount allocated to each fixed asset for each level (stage) of allocation.

As shown in FIG. 2, the allocation detail database 106e has items such as allocation number, quotation number, quotation internal line number, corresponding apportionment level, corresponding apportionment code, common cost number, common cost internal Includes line number and pro rata amount.

The item "allocation number" is an item that stores an allocation number, and is an item that links the allocation detail database 106e and the allocation header database 106d.

The item "estimate number" is an item in which an estimate number specifying estimate data to be subjected to allocation processing is registered, and is an item that links the allocation detail database 106e and the estimate detail database 106b.

The item "estimate internal line number" is an item in which an estimate internal line number that identifies fixed assets to be allocation destinations in allocation processing is registered. The item "estimate internal line number" is an item that links the allocation detail database 106e and the estimate detail database 106b.

The item "corresponding apportionment level" is an item in which a corresponding apportionment level is registered, and is an item that links the allocation detail database 106e and the estimate detail database 106c.

The item "corresponding apportionment code" is an item in which a corresponding apportionment code is registered, and is an item that links the allocation detail database 106e and the quotation detail database 106c.

The item "common cost number" is an item in which an estimate number for identifying estimate data including common costs, etc., which is the source of allocation in the allocation process is registered.

The item "common cost internal line number" is an item in which an estimate internal line number that specifies the common cost or the like that is the source of allocation in the allocation process is registered.

The item "Proportional division amount" is the corresponding apportionment level and corresponding This is an item for registering the apportionment equivalent amount apportioned for each apportionment code. The proportionally divided equivalent amount is an example of the proportionally divided amount in this embodiment.

The allocation number, quotation number, quotation internal line number, corresponding apportionment level, corresponding apportionment code, common cost number, and common cost internal line number are the primary keys of the allocation details database 106e. A split amount is associated with these items.

Returning to FIG. 1, the asset database 106f is a database in which information on purchased fixed assets is registered.

The depreciation database 106g is a database in which depreciation costs related to purchased fixed assets are registered.

The monthly depreciation database 106h is a database in which monthly conversion amounts of depreciation costs related to purchased fixed assets are registered.

The journal database 106i is a database in which journal data generated by purchase of fixed assets and depreciation are registered.

The items of each database described above are examples, and the configuration of each database is not limited to this. For example, each database may contain other items in addition to the above items. Further, among the databases described above, the database divided into the header and the details or details may be configured as one database.

The control unit 102 is a CPU or the like that controls the allocation device 100 in a centralized manner. 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. Execute.

As shown in FIG. 1, the control unit 102 includes a display control unit 102a, a reception unit 102b, an estimate data registration unit 102c, an allocation unit 102d, and a fixed asset information generation unit 102e.

The display control unit 102a controls the monitor 114 to display an estimate data input screen, an allocation execution screen, an approval screen, and the like. The estimate data input screen is a screen for the person in charge to input the information described in the estimate sent from the purchaser regarding the purchase of fixed assets. The allocation execution screen is a screen for executing allocation processing for registered estimate data. The approval screen is a screen for displaying an estimate of fixed assets after allocation of common expenses and the like, and allowing the manager or the like to approve the displayed result.

The reception unit 102b receives the estimate data input by the person in charge on the estimate data input screen. In this case, the reception unit 102b sends the input estimate data to the estimate data registration unit 102c.

In addition, the receiving unit 102b receives information specifying estimation data to be allocated, which is input by the person in charge on the allocation execution screen, and an execution command for the allocation process. In this case, the reception unit 102b sends information specifying the input estimate data to be allocated, such as an estimate number, to the allocation unit 102d.

The receiving unit 102b also receives an input from the administrator or the like to approve the fixed asset estimate from the approval screen. In this case, the reception unit 102b sends information identifying the approved estimate, such as an estimate number, to the fixed asset information generation unit 102e.

The estimate data registration unit 102c registers the estimate data received by the reception unit 102b in the estimate header database 106a, the estimate detail database 106b, and the estimate detail database 106c.

The allocating unit 102d identifies the estimate data to be allocated, which is received by the receiving unit 102b, from the estimate data registered in the estimate header database 106a, the estimate detail database 106b, and the estimate detail database 106c, and assigns common expenses and the like to fixed assets. To distribute. In other words, the allocation unit 102d identifies, from the quotation detail database 106b, allocation source records and allocation destination records corresponding to the allocation sources and allocation destinations linked by the quotation internal line numbers. Also, the allocation unit 102d allocates the estimated amount associated with the common cost or the like, which is the allocation source, to the estimated amount associated with the fixed asset, which is the allocation destination.

Further, when a plurality of fixed assets are specified as allocation destinations, the allocation unit 102d does not allocate the estimated amount of the common cost, etc. in allocation up to one level before the allocation level. Proportional division is performed based on the estimated amount of the fixed assets after the calculation, and the proportional division equivalent amount obtained by the proportional division is allocated to the estimated amounts associated with the fixed assets.

In addition, the allocation unit 102d divides the total amount of consumption tax applied to a plurality of fixed assets proportionally to the estimated amount of each fixed asset after the common expenses etc. have been allocated, and calculates the acquisition price including tax for each fixed asset. calculate. The allocation unit 102d registers the data generated by the allocation process in the quotation header database 106a, the quotation details database 106b, and the quotation details database 106c.

When the receiving unit 102b receives approval of the estimate, the fixed asset information generation unit 102e generates various types of information about fixed assets from the approved estimate data after the allocation process, and converts the generated information into each information. be registered in the corresponding database. For example, the fixed asset information generation unit 102e registers information on purchased fixed assets in the asset database 106f. In addition, the fixed asset information generation unit 102e registers the depreciation costs related to the purchased fixed assets in the depreciation database 106g. In addition, the fixed asset information generation unit 102e registers the monthly depreciation amount for the purchased fixed asset in the monthly depreciation database 106h. In addition, the fixed asset information generation unit 102e registers journal data generated by purchase and depreciation of fixed assets in the journal database 106i.

Information generated by the fixed asset information generation unit 102e is not limited to the above example.

[3. Process flow]
Next, the allocation processing of this embodiment configured as described above will be described. FIG. 3 is a diagram showing an example of the flow of a series of processes including allocation according to this embodiment. As shown in FIG. 3, first, in the quotation data input process, the quotation data is registered in the quotation header database 106a, the quotation detail database 106b, and the quotation detail database 106c.

Specifically, in the estimate data input process, the display control unit 102a controls the monitor 114 to display the estimate data input screen. FIG. 4 is a diagram showing an example of an estimate data input screen according to this embodiment. As shown in FIG. 4, the estimate data entry screen has a plurality of input fields for entering information included in the estimate data. Further, as shown in FIG. 4, the estimate data input screen includes a header portion, an asset detail portion, and a common expense detail portion.

In the header part, outline information of estimate data regarding the purchase of fixed assets is input. Further, in the asset details section, detailed information for each fixed asset of the estimate data relating to the purchase of the fixed asset is entered. In addition, detailed information such as common expenses related to the purchase of fixed assets is entered in the common expense details section.

As an example of the display layout of the estimate data input screen, the header section is displayed at the top of the screen, the asset details section is displayed in the middle of the screen, and the common expense details section is displayed at the bottom of the screen, but the display layout is limited to this. not to be

FIG. 5 is a diagram showing an example of registration of estimate data according to the present embodiment. The input data shown in the upper part of FIG. 5 are estimate data to be entered in the header section, the asset detail section, and the common expense detail section of the estimate data input screen shown in FIG. The reception unit 102b receives the estimate data input by the person in charge on the estimate data input screen.

The estimate data registration unit 102c also registers the input estimate data in the estimate header database 106a, the estimate detail database 106b, and the estimate detail database 106c, as shown in the lower part of FIG. Note that FIG. 5 shows main items of input data and data registered in the database, and some items are omitted.

As shown in FIG. 5, the estimate data registration unit 102c associates the estimate number input in the header, the date of acquisition, the amount excluding tax on the order, and the consumption tax on the order, and registers them in the estimate header database 106a. . Also, the estimate number may be automatically numbered by the estimate data registration unit 102c or the like.

In addition, the estimate data registration unit 102c includes the estimate number input in the header portion, detailed information for each fixed asset input in the asset detail portion, and detailed information such as common expenses input in the common expense detail portion. are associated with each other and registered in the quotation detail database 106b and the quotation detail database 106c.

Specifically, the data entered in the "line number" of the asset details section and the common expense details section are registered in the item "estimate internal line number" of the estimate detail database 106b and the estimate detail database 106c.

"Asset classification" in the asset details section indicates the name of the fixed asset. The data entered in this item is registered in the item "asset name" of the quotation detail database 106b. In addition, the "asset classification" in the common expense details section indicates the name of the common expense. The data entered in this item is registered in the item "asset name" of the quotation detail database 106b.

The data entered in the "estimated amount" of the asset details section and the common expense details section are registered in the item "estimated amount" of the estimate details database 106b.

"Proportion 1" to "proportion 5" of the asset detail part and the common expense detail part indicate corresponding proportional division levels of fixed assets or common expenses. The data input to "proportion 1" to "proportion 5" indicate corresponding proportional division codes of fixed assets or common expenses. For example, the estimate data registration unit 102c registers the corresponding apportionment code input to "proportion 1" in the estimate detail database 106c as "corresponding apportionment level" = "1" and "corresponding apportionment code" = "10". .

In FIG. 4, input columns up to corresponding apportionment level 5 are displayed, but a configuration may be employed in which the display control unit 102a adds input columns by operation of the person in charge of inputting the estimate data.

Also, the values of the estimate data shown in FIGS. 4 and 5 are examples, and the present invention is not limited to these. For example, the data set as the corresponding apportionment code only needs to be able to link the allocation source and the allocation destination. may

When the estimate data registering unit 102c registers the estimate data, the estimate data before allocation is registered in each database as shown in the lower part of FIG. Also, corresponding apportionment levels and corresponding apportionment codes related to fixed assets and common expenses registered in the estimate detail database 106b are registered in association with the estimate detail database 106c.

As shown in FIG. 3, allocation processing is performed after estimation data input processing. FIG. 6 is a flowchart showing an example of the flow of allocation processing according to this embodiment. The processing of this flowchart is started, for example, when the person in charge inputs an operation of pressing an execution button displayed on the allocation execution screen.

FIG. 7 is a diagram showing an example of an allocation execution screen according to this embodiment. The display control unit 102a controls the monitor 114 to display the allocation execution screen. The person in charge enters the estimate number that identifies the estimate data to be allocated, in the input field for "target estimate number" on the allocation execution screen. Here, the person in charge can also input a plurality of quotation numbers in the input field of "target quotation number" on the allocation execution screen.

When the person in charge presses the execution button displayed on the allocation execution screen, the reception unit 102b receives the target estimate number input from the allocation execution screen (S1).

The allocation unit 102d generates an allocation number for specifying the allocation process (S2). Alternatively, the allocation number may be determined by the person in charge and input from the allocation execution screen. In addition, the allocation unit 102d searches the quotation header database 106a for the quotation number corresponding to the target quotation number input from the allocation execution screen, and displays the order tax-excluded amount associated with the quotation number as the display control unit. 102a. The display control unit 102a displays the acquired order tax-excluded amount as an estimated amount on the allocation execution screen. The registration date shown in FIG. 7 may be generated by the display control unit 102a or the allocation unit 102d and displayed on the allocation execution screen, or may be input by the person in charge.

Also, when a plurality of quotation numbers are input from the allocation execution screen shown in FIG. 7, the allocation unit 102d generates one allocation number for the quotation data corresponding to the plurality of quotation numbers. . As a result, the allocation unit 102d can integrate the estimate data created for each estimate and perform allocation in one allocation process.

Next, the allocation unit 102d extracts the estimate data corresponding to the estimate number input as the target estimate number from the allocation execution screen from the estimate header database 106a, the estimate detail database 106b, and the estimate detail database 106c ( S3).

Then, the allocating unit 102d executes proportional division processing of the common cost and the like according to the corresponding proportional division level registered in the detailed estimate database 106c. In this embodiment, corresponding apportionment levels 1 to 3 are registered as shown in FIG. In this case, the allocating unit 102d first executes apportionment processing at apportionment level 1 (S4).

FIG. 8 is a flowchart showing an example of the flow of apportionment processing at apportionment level 1 according to the present embodiment. The allocating unit 102d extracts the record of the quotation number=“DEN001” and corresponding apportionment level=“1” from the quotation detail database 106c (S41).

FIG. 9A is a diagram showing an example of estimation data to be apportioned at apportionment level 1 according to the present embodiment. The allocation unit 102d sorts the records extracted from the detailed estimate database 106c in ascending order by corresponding apportionment code (S42). In the example shown in FIG. 9A, the corresponding apportionment codes are all "10", but a case where a plurality of corresponding apportionment codes are included will be described later.

The allocation unit 102d acquires the estimated internal row numbers "1" to "4" and "901" corresponding to the corresponding apportionment code "10" at the top of the sort result (S43).

As shown in FIG. 9A, the allocation unit 102d allocates the fixed assets (allocation destinations) corresponding to the acquired estimated internal line numbers "1" to "4" and the expenses or expenses corresponding to the estimated internal line number "901". The common cost (allocation source) is searched from the quotation detail database 106b (S44). The allocation unit 102d determines whether the data registered in the record corresponding to each estimated internal line number is a fixed asset, an expense, or a common expense, based on the asset expense common expense category.

Then, the allocation unit 102d apportions the estimated amount of expenses or common expenses according to the ratio of the estimated amount of each fixed asset to the total estimated amount of the fixed assets to be allocated (S45). FIG. 9B is a diagram illustrating an example of apportionment processing at apportionment level 1 according to the present embodiment. As shown in FIG. 9B, the allocating unit 102d divides the estimated amounts of fixed assets “fixtures and fixtures A” to “fixtures and fixtures D” corresponding to the estimate internal line numbers “1” to “4” into “fixtures and fixtures A” to “Equipment D” divided by the total estimated amount. Then, the allocation unit 102d obtains a calculation result by multiplying the division result by the estimated amount "300" of "installation cost 1", which is the allocation source expense. In the calculation result, the allocating unit 102d rounds off fractions after the decimal point.

Then, the allocating unit 102d adjusts the fraction of the calculation result (S46). Specifically, as shown in FIG. 9B, the allocating unit 102d compares the calculation result with the estimated amount of "300" for "installation cost 1" and assigns the difference "2" to , add to the one with the largest value. In the example shown in FIG. 9B , the calculation result “140” corresponding to “fixture A” is the largest, so the difference is added to obtain “142”, which is the apportionment result at apportionment level 1 .

The example shown in FIG. 9B is at apportionment level 1, which is the first apportionment process in this apportionment process, so the apportioning unit 102d uses the estimated amount of fixed assets as the calculation base amount for the apportionment process. If apportionment processing at a level prior to the processing at the apportionment level currently being executed has already been performed, the allocating unit 102d distributes the results of apportionment processing up to the previous level to the distributed fixed assets. Proportional division processing is performed using the estimated amount of The apportionment processing for apportionment level 2 and later will be described later.

After adjusting the fraction, the allocating unit 102d determines whether or not the proportional division processing has been completed for all corresponding proportional division codes included in the records extracted in S41 (S47). If it is determined that the apportionment process has not been completed for all corresponding apportionment codes (S47 "No"), the allocation unit 102d acquires the estimated internal line number corresponding to the next corresponding apportionment code (S48). The allocating unit 102d repeats the processes of S44 to S48 until the apportionment process is completed for all corresponding apportionment codes.

In the example shown in FIG. 9A, the corresponding apportionment code for apportionment level 1 is only "10", so the allocating unit 102d determines that apportionment processing has been completed for all the corresponding apportionment codes ("Yes" in S47). ), and the apportionment result is registered in the allocation detail database 106e (S49).

FIG. 9C is a diagram illustrating an example of the apportionment processing result of apportionment level 1 according to the present embodiment. As shown in FIG. 9C, the allocating unit 102d registers the proportional division result obtained by the formula shown in FIG. 9B in the allocation detail database 106e as the proportional division equivalent amount. Also, at this time, the allocation unit 102d assigns the apportionment equivalent amount to the allocation number related to the allocation process, the estimate number, the estimate internal line number related to apportionment level 1, the corresponding apportionment level, and the corresponding apportionment level. The apportionment code, common cost number (estimation number of common cost, etc.), and common cost internal line number (estimation internal line number of common cost, etc.) are associated and registered in the allocation detail database 106e.

In addition, the allocation unit 102d adds the apportionment equivalent amount for each fixed asset calculated at the apportionment level 1 registered in the allocation detail database 106e to the estimated amount of the fixed asset to calculate the tax-excluded amount after apportionment. , is registered in the quotation detail database 106b (S50). The tax-excluded amount after apportionment should be able to be referenced in the processing of the next apportionment levels 2 and 3, and the storage method is not limited to registration in the database. For example, the allocating unit 102d may hold the calculated proportionally divided tax-excluded amount in a temporary table, variable, or the like formed on the memory during execution of the allocation process shown in FIG.

Here, the processing of the flowchart shown in FIG. 8 ends. Next, the allocating unit 102d returns to the flowchart of FIG. 6 and executes the apportionment processing of apportionment level 2 (S5). The basic flow of apportionment processing at apportionment level 2 is the same as the flow of apportionment processing at apportionment level 1 shown in FIG. Parts that are partially different from the apportionment processing of apportionment level 1 will be described separately.

As in the process of S41 in FIG. 8, the allocation unit 102d extracts records to be subjected to proportional division processing from the detailed quotation database 106c. FIG. 10A is a diagram showing an example of estimation data to be apportioned at apportionment level 2 according to the present embodiment. In the apportionment processing of apportionment level 2, as shown in FIG. 10A, the allocating unit 102d extracts the record of the estimate number=“DEN001” and corresponding apportionment level=“2” from the estimate detail database 106c.

Next, similarly to the process of S42, the allocation unit 102d sorts the records extracted from the detailed estimate database 106c in ascending order by the corresponding apportionment code. As shown in FIG. 10A, the record with quotation number=“DEN001” and corresponding apportionment level=“2” includes corresponding apportionment codes “20” and “30”.

Next, similarly to the process of S43, the allocating unit 102d acquires the estimated internal row number corresponding to the corresponding apportionment code at the top of the sort result from the estimated detailed database 106c. In the apportionment processing of apportionment level 2, the allocation unit 102d assigns estimated internal line numbers "2", "3", and "902" corresponding to the corresponding apportionment code "20" at the top of the sort result, Estimated internal line numbers "4" and "904" corresponding to corresponding apportionment code "30" are obtained.

Next, similarly to the process of S44, the allocation unit 102d searches the estimate detail database 106b for fixed assets and expenses or common expenses corresponding to the acquired estimate internal line number. As shown in FIG. 10A, in apportionment processing at apportionment level 2, the allocation unit 102d assigns fixed assets corresponding to estimated internal line numbers "2" and "3" and fixed assets corresponding to estimated internal line number "902". Expenses or common expenses are retrieved from the estimate detail database 106b. Also, the allocation unit 102d searches the estimate detail database 106b for fixed assets corresponding to the estimated internal line number "4" and expenses or common costs corresponding to the estimated internal line number "904".

Then, the allocating unit 102d apportions the estimated amount of expenses or common expenses. Unlike the process of S45, the allocation unit 102d performs the proportional division calculated at the proportional division level 1 for each fixed asset with respect to the total value of the tax-excluded amount after the proportional division calculated at the proportional division level 1 for the fixed assets to be allocated. Estimated expenses or common expenses will be apportioned according to the ratio of the post-tax amount. As described above, the tax-excluded amount after apportionment is the amount obtained by allocating the apportioned amount calculated by the apportionment processing up to the previous level to the estimated amount.

In this embodiment, when a plurality of corresponding apportionment codes are included in the same apportionment level, apportionment processing is executed in ascending order of the corresponding apportionment codes. Note that the execution order of the apportionment processing at the same apportionment level is not limited to this.

FIG. 10B is a diagram illustrating an example of apportionment processing at apportionment level 2 according to the present embodiment. As shown in FIG. 10B, the allocating unit 102d first performs apportionment processing for fixed assets and expenses or common expenses corresponding to the corresponding apportionment code "20". The allocating unit 102d divides the prorated tax-excluded amounts of fixed assets "fixtures and fixtures B" and "fixtures and fixtures C" corresponding to the estimated internal line numbers "2" and "3" into "fixtures and fixtures B" and "fixtures and fixtures B" and "fixtures and fixtures C", respectively. Divide by the total value of the tax-excluded amount after apportionment of fixtures C”. Then, the allocation unit 102d obtains a calculation result by multiplying the division result by the estimated amount "60" of the "installation cost 2", which is the allocation source expense. In the calculation result, the allocating unit 102d rounds off fractions after the decimal point.

Then, similarly to the process of S46, the allocating unit 102d adjusts the fractions of the calculation result.

Next, similarly to the process of S47, the allocating unit 102d determines whether or not the apportionment process has been completed for all corresponding apportionment codes included in the extracted records after adjusting the fractions. In the example shown in FIGS. 10A and 10B, since there are a plurality of corresponding apportionment codes for apportionment level 2, the allocation unit 102d determines that apportionment processing has not been completed for all of the corresponding apportionment codes.

In this case, similarly to the process of S48, the allocation unit 102d acquires the estimated internal line number corresponding to "30", which is the next corresponding apportionment code.

Next, the allocation unit 102d performs proportional division processing on the fixed assets and expenses or common expenses corresponding to the corresponding proportional division code "30". As shown in FIG. 10B, the allocation unit 102d calculates the apportioned tax-excluded amount of the fixed asset "fixtures and fixtures D" corresponding to the estimate internal line number "4" as the sum of the apportioned tax-excluded amounts of the "fixtures and fixtures D" Divide by value. Then, the allocation unit 102d obtains a calculation result by multiplying the division result by the estimated amount "70" of the "installation cost 3" which is the allocation source expense. In the calculation result, the allocating unit 102d rounds off fractions after the decimal point. Then, similarly to the process of S46, the allocating unit 102d adjusts the fractions of the calculation result.

After adjusting the fraction, the allocating unit 102d again determines whether or not the apportionment processing has been completed for all corresponding apportionment codes included in the extracted record, as in the process of S47. In the example shown in FIGS. 10A and 10B, the corresponding apportionment codes for apportionment level 2 are only "20" and "30", so the allocating unit 102d determines that apportionment processing has been completed for all the corresponding apportionment codes. do.

In this case, similar to the process of S49, the allocation unit 102d registers the apportionment result in the allocation detail database 106e. FIG. 10C is a diagram illustrating an example of the apportionment processing result of apportionment level 2 according to the present embodiment. As shown in FIG. 10C, the allocation unit 102d associates the proportional division result obtained by the formula shown in FIG. 10B with other items, and registers the proportional division equivalent amount in the allocation detail database 106e.

Also, in the same manner as in the process of S50, the allocation unit 102d calculates the tax-excluded amount after apportionment, and registers it in the quotation detail database 106b. In the apportionment processing of apportionment level 2, the apportioning unit 102d divides the apportionment amount for each fixed asset calculated at apportionment level 2 and the apportionment amount for each fixed asset calculated at apportionment level 1 into Add it to the estimated amount of the fixed asset to calculate the tax-excluded amount after apportionment.

Next, the allocating unit 102d returns to the flowchart of FIG. 6 and executes apportionment processing at apportionment level 3 (S6). The basic flow of apportionment processing at apportionment level 3 is the same as the flow of apportionment processing at apportionment level 2 described above.

As in the process of S41 in FIG. 8, the allocation unit 102d extracts records to be subjected to proportional division processing from the detailed estimate database 106c. FIG. 11A is a diagram showing an example of estimation data to be apportioned at apportionment level 3 according to the present embodiment. In the apportionment processing of apportionment level 3, as shown in FIG. 11A, the allocating unit 102d extracts the record of the estimate number=“DEN001” and corresponding apportionment level=“3” from the estimate detail database 106c.

Next, similarly to the process of S42, the allocation unit 102d sorts the records extracted from the detailed estimate database 106c in ascending order by the corresponding apportionment code. As shown in FIG. 11A, the record with quotation number=“DEN001” and corresponding apportionment level=“10” includes a corresponding apportionment code of “10”.

The process from sorting the extracted records to obtaining the estimated internal line number corresponding to the corresponding apportionment code is the same as the process of S42 and S43 shown in FIG.

Next, similarly to the process of S44, the allocation unit 102d searches the estimate detail database 106b for fixed assets and expenses or common expenses corresponding to the acquired estimate internal line number. As shown in FIG. 10A , in apportionment processing at apportionment level 3, the allocation unit 102d assigns fixed assets corresponding to estimated internal line numbers “1”, “3”, and “4” and estimated internal line number “904”. ” is retrieved from the quotation detail database 106b.

Then, the allocation unit 102d assigns the after-tax-excluded amount calculated up to the apportionment level 2 of each fixed asset to the total value of the after-tax-excluded amount calculated up to the apportionment level 2 of the fixed assets that are allocation destinations. Proportion the estimated amount of expenses or common expenses according to the percentage of the amount. FIG. 11B is a diagram illustrating an example of apportionment processing at apportionment level 3 according to the present embodiment. As shown in FIG. 11B, the allocating unit 102d selects the fixed assets "fixtures and fixtures A", "fixtures and fixtures C", and "fixtures and fixtures D" corresponding to the estimate internal line numbers "1", "3", and "4". are divided by the total value of the apportioned tax-excluded amounts of "fixtures A", "fixtures C", and "fixtures D". Then, the allocation unit 102d obtains a calculation result by multiplying the division result by the estimated amount "-120" of the "discount" which is the allocation source expense. In the calculation result, the allocating unit 102d rounds off fractions after the decimal point.

Then, similarly to the process of S46, the allocating unit 102d adjusts the fractions of the calculation result. The processing from judging whether or not the apportionment processing has been completed for all the corresponding apportionment codes to registering the apportionment result is the same as the processing of S47 and S49 in FIG. FIG. 11C is a diagram illustrating an example of the apportionment processing result of apportionment level 3 according to the present embodiment. As shown in FIG. 11C, the allocation unit 102d associates the proportional division result obtained by the formula shown in FIG. 11B with other items, and registers the proportional division equivalent amount in the allocation detail database 106e.

Then, similarly to the process of S50, the allocating unit 102d calculates the tax-excluded amount after apportionment and registers it in the detailed quotation database 106b. In the apportionment processing of apportionment level 3, the apportionment unit 102d adds the apportionment equivalent amount for each fixed asset calculated at apportionment levels 1 to 3 to the estimated amount of the fixed asset to obtain the tax-excluded amount after apportionment. calculate.

Next, the allocating unit 102d returns to the flowchart of FIG. 6 to calculate the proportionally divided consumption tax and the tax-included amount after proportional division (S7). Specifically, the allocation unit 102d apportions the order consumption tax registered in the estimate header database 106a proportionally to the tax-included amount after apportionment for each fixed asset after the apportionment processing of apportionment levels 1 to 3, Calculate the prorated consumption tax for each asset. Further, the allocating unit 102d adds the calculated proportionally divided consumption tax for each fixed asset to the estimated amount of money of the fixed asset, and calculates the amount of tax after proportional division.

In other words, the allocation unit 102d calculates the amount of consumption tax on a plurality of fixed assets with respect to the estimated amount of each fixed asset after the estimated amount of common expenses etc. has been allocated by the apportionment processing of apportionment levels 1 to 3. Divide the total amount proportionally and calculate the tax-included acquisition price for each fixed asset.

Next, the allocation unit 102d registers the allocation result in each database (S8). Also, the allocation unit 102d updates the data of the allocation detail database 106e and the estimate detail database 106b, etc., which have been updated each time in the apportionment process, and registers the final processing result of the allocation process.

FIG. 12A is a diagram showing an example of data registered in the allocation header database 106d and the allocation detail database 106e after allocation processing according to this embodiment. As shown in FIG. 12A, the allocation unit 102d registers an allocation number specifying the above-described allocation process in the allocation header database 106d and the allocation detail database 106e. The allocation header database 106d and the allocation detail database 106e are linked by the allocation number. The allocation unit 102d also registers the registration date, which is the date when the allocation data of the allocation process was registered, in the allocation header database 106d. In addition, the allocation unit 102d registers the proportional division equivalent amount calculated by the proportional division processing of each proportional division level in the allocation detail database 106e.

FIG. 12B is a diagram showing an example of data registered in the estimate header database 106a, the estimate detail database 106b, and the estimate detail database 106c after allocation processing according to this embodiment. As shown in FIG. 12B, the allocation unit 102d registers an allocation number specifying the above-described allocation process in the quotation header database 106a.

The allocation unit 102d also registers the estimate internal line number, the corresponding apportionment level, and the apportionment level amount for each corresponding apportionment code in the estimate detail database 106c.

In addition, the allocation unit 102d registers the apportioned tax-excluded amount after apportionment, the apportioned consumption tax, the apportioned tax-included price, and the apportioned total amount in the estimate detail database 106b in association with the estimate number and the estimate internal line number, respectively. The proportional division total amount is an amount obtained by totaling the proportional division level amounts registered in the estimate detail database 106c for each fixed asset.

In the examples shown in FIGS. 8 to 11C described above, values are registered in the allocation detail database 106e and the estimate detail database 106b, etc. for each apportionment process at each apportionment level. is not limited to this. For example, the allocation unit 102d holds the calculated values in temporary tables, variables, etc. formed on the memory during the allocation process, and at the timing of the process of S8 in FIG. 106b or the like may be registered.

By registering the allocation results, the allocation processing shown in the flowchart of FIG. 6 ends.

As shown in FIG. 3, approval processing and fixed asset information generation processing are performed after allocation processing. The display control unit 102a controls the monitor 114 to display the approval screen. The reception unit 102b receives an input from the administrator or the like to approve the estimate of fixed assets from the approval screen.

When the acceptance unit 102b accepts approval of the estimate, the fixed asset information generation unit 102e creates various types of information about fixed assets from the approved estimate data after the allocation process, and stores the generated information in the asset database. 106f, depreciation database 106g, monthly depreciation database 106h, journal database 106i, and the like.

As described above, in the allocation apparatus 100 of the present embodiment, a plurality of fixed assets are used as allocation destinations, and a plurality of expenses or common expenses that are included in the apportioned tax-excluded amount of at least one of the plurality of fixed assets are calculated. As an allocation source, a control unit 102 and a storage unit 106 are provided for allocating each estimated amount of allocation source to each estimated amount of allocation destination. The storage unit 106 also stores an estimate detail database 106b that includes records corresponding to allocation destinations and allocation sources, and an estimate detail database 106c that stores corresponding apportionment levels and corresponding apportionment codes in association with each other. The control unit 102, in accordance with the corresponding apportionment level, performs an identification process of identifying the allocation source record and the allocation destination record corresponding to the allocation source and the allocation destination linked by the corresponding apportionment code from the quotation detail database 106b, Alternatively, an allocation process for allocating the estimated amount of common expenses to the estimated amount of fixed assets is executed. In addition, in the allocation process, when a plurality of fixed assets are specified, the control unit 102 allocates the estimated amount of expenses or common expenses in the apportionment process of the immediately preceding apportionment level. Proportionally divided based on the estimated amount of fixed assets after the calculation, and allocating the proportionally divided equivalent amount obtained by the proportional division to the estimated amount of fixed assets. In other words, the allocation device 100 of the present embodiment can designate an allocation source and an allocation destination, and allocate a plurality of common costs or the like in multiple stages. Therefore, according to the allocation apparatus 100 of the present embodiment, it is possible to reduce the work load of the person in charge of allocating common costs and the like to a plurality of fixed assets and to improve the efficiency of the work of registering purchased fixed assets. can be done.

Furthermore, in the allocation apparatus 100 of the present embodiment, in the allocation process, the control unit 102 calculates the expenses or Proportion the estimated amount of common expenses. Therefore, according to the allocation apparatus 100 of the present embodiment, the estimated amount of expenses or common expenses can be calculated according to the ratio of the estimated amount of each fixed asset without manual calculation by the person in charge. can be allocated.

Furthermore, in the allocation apparatus 100 of the present embodiment, in the allocation process, the control unit 102 converts the post-distribution tax-excluded amount, which is the estimated amount for each fixed asset after the estimated amounts of expenses or common expenses have been allocated, On the other hand, the order consumption tax, which is the total amount of consumption tax on multiple fixed assets, is proportionally distributed. Then, the allocation unit 102d calculates the tax-included amount after proportional division for each fixed asset. Therefore, according to the allocation apparatus 100 of the present embodiment, the consumption tax for each fixed asset can be obtained by taking into consideration the allocated common expenses and the like.

[4. 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.

Further, 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 the processes described as being performed manually can be performed manually. can also be performed 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 distribution apparatus 100, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, the processing functions of the allocation device 100, particularly the processing functions performed by the control unit 102, may be implemented in whole or in part 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 device to execute the processing described in the present embodiment, and the allocation device if necessary. 100 mechanically read. 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 the distribution apparatus 100 via any network, and it is possible to download all or part of it as necessary. be.

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 or processing method 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 and the like 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, and are used for various processes and website provision. programs, tables, databases, and files for web pages.

Also, the allocation 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 any peripheral device is connected. Also, the allocation device 100 may be implemented by installing software (including programs, data, etc.) that causes the device to implement the processing described in the present embodiment.

Also, the allocation device 100 may be a server connected to a personal computer or the like via a network. When adopting this configuration, the distribution device 100, which is a server, may receive user input operations from a personal computer or the like connected via a network and execute processing. Also, the allocation device 100 may be provided in a cloud environment or the like.

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.

INDUSTRIAL APPLICABILITY The present invention is useful in various industries, particularly in the distribution industry and the like.

100 allocation device
102 control unit
102a display control unit
102b reception unit
102c Quotation data registration unit
102d Allocation Department
102e fixed asset information generation unit
104 communication interface unit
106 storage unit
106a Quotation Header Database (DB)
106b Quotation details database (DB)
106c Quotation details database (DB)
106d Allocation header database (DB)
106e Allocation details database (DB)
106f Asset database (DB)
106g Amortization database (DB)
106h Monthly depreciation database (DB)
106i journal database (DB)
108 input/output interface
112 input device
114 output device (monitor)
200 server 300 network

Claims (5)

An information processing device comprising a control unit,
The control unit
a first input area for inputting the total estimated amount of each of the plurality of fixed assets and the estimated amount of each of the plurality of expenses or common expenses, and inputting the estimated amount of each of the plurality of fixed assets; , a second input area for inputting pegging information for linking costs or common costs and fixed assets in order of execution of allocation, inputting estimated amounts for each of a plurality of costs or common costs, and , and a third input area for inputting the pegging information according to the execution order of allocation;
When information is entered in the first screen, a first table storing the total entered in the first input area and the first identification information and the information entered in the second input area a second table storing all estimated amounts, all estimated amounts entered in the third input area, first identification information, and a plurality of mutually different second identification information, respectively; All the pegging information and the execution order of allocation entered in the input area of , all the pegging information and the execution order of allocation entered in the third input area, the first identification information and the plurality of second means for generating a third table in which each piece of identification information is stored;
to provide
An information processing device characterized by: The control unit
means for displaying, on the display unit, a second screen including an input area for inputting first identification information to be subjected to allocation processing;
When execution of the allocation process is instructed from the second screen, it is linked to the first identification information input to the input area stored in each of the second table and the third table. Based on the attached information, calculate the allocation amount of expenses or common expenses to be allocated to each fixed asset according to the execution order of allocation included in the information, and transfer each calculated allocation amount to the second a means for storing in a table of
to further provide
The information processing apparatus according to claim 1, characterized by: The control unit
means for displaying on the display unit a third screen for approval of the amount of fixed assets;
When an input to approve the amount of fixed assets is received from the third screen, based on the information of the fixed assets subject to approval stored in the second table, fixed assets including depreciation a means for generating information;
to further provide
3. The information processing apparatus according to claim 2, characterized by: The control unit of an information processing device comprising a control unit,
a first input area for inputting the total estimated amount of each of the plurality of fixed assets and the estimated amount of each of the plurality of expenses or common expenses, and inputting the estimated amount of each of the plurality of fixed assets; , a second input area for inputting pegging information for linking costs or common costs and fixed assets in order of execution of allocation, inputting estimated amounts for each of a plurality of costs or common costs, and , and a third input area for inputting the pegging information according to the execution order of allocation, displaying on the display unit a first screen;
When information is entered in the first screen, a first table storing the total entered in the first input area and the first identification information and the information entered in the second input area a second table storing all estimated amounts, all estimated amounts entered in the third input area, first identification information, and a plurality of mutually different second identification information, respectively; All the pegging information and the execution order of allocation entered in the input area of , all the pegging information and the execution order of allocation entered in the third input area, the first identification information and the plurality of second generating a third table in which each piece of identification information is stored;
to run
An information processing method characterized by: The control unit of an information processing device comprising a control unit,
a first input area for inputting the total estimated amount of each of the plurality of fixed assets and the estimated amount of each of the plurality of expenses or common expenses, and inputting the estimated amount of each of the plurality of fixed assets; , a second input area for inputting pegging information for linking costs or common costs and fixed assets in order of execution of allocation, inputting estimated amounts for each of a plurality of costs or common costs, and means for displaying on the display unit a first screen including a third input area for inputting the pegging information according to the execution order of allocation;
When information is entered in the first screen, a first table storing the total entered in the first input area and the first identification information and the information entered in the second input area a second table storing all estimated amounts, all estimated amounts entered in the third input area, first identification information, and a plurality of mutually different second identification information, respectively; All the pegging information and the execution order of allocation entered in the input area of , all the pegging information and the execution order of allocation entered in the third input area, the first identification information and the plurality of second means for generating a third table in which each piece of identification information is stored;
A program to function as

Images