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

Abstract

To provide an allocation device, an allocation method, and an allocation program capable of reducing a work load on a person in charge necessary for allocation of common expenses or the like to a plurality of fixed assets and streamlining the work of registering purchased fixed assets.SOLUTION: An allocation device according to the present invention comprises a control unit and a storage unit. The control unit executes: an identification process of identifying an allocation source record and an allocation destination record corresponding to allocation sources and an allocation destination(s) linked by linking data, from a detail table in accordance with an execution order; and an allocation process of allocating an amount of money associated with the allocation source to a purchase price associated with the allocation destination. The control unit proportionally divides the amount of money based on a purchase price after the amount of money is allocated in the allocation up to the previous execution order when multiple allocation destinations are identified, and allocates the proportionally divided amount of money obtained by the proportional division to the purchase price.SELECTED DRAWING: Figure 1

Description

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

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

Japanese Unexamined Patent 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 specify a part of the fixed assets among the plurality of fixed assets as the allocation destination of common expenses, etc., which is the allocation source. It was difficult. Further, in the prior art, it has been difficult to apportion a plurality of common expenses and the like to the purchase price of fixed assets in multiple stages. For this reason, the person in charge of a company, etc. allocates common expenses, etc. to each fixed asset by manual calculation, and it is required to reduce the workload required for allocation and improve the efficiency of registration work of purchased fixed assets. Was being done.

The present invention has been made in view of the above, and it is intended to reduce the workload of the person in charge of allocating common expenses, etc. to a plurality of fixed assets, and to improve the efficiency of registration work of 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 the above.

In order to solve the above-mentioned problems and achieve the object, the allocation device according to the present invention has a plurality of fixed assets as allocation destinations and is included in the acquisition price of at least one of the plurality of fixed assets. It is provided with a control unit and a storage unit that allocate each amount of the allocation source to each purchase price of the allocation destination with the cost or common cost of the allocation source as the allocation source. The storage unit stores the detail table including the allocation destination and the record corresponding to the allocation source, the data indicating the execution order of the allocation, and the associated data that links the allocation source and the allocation destination in association with each other. Remember the table. The allocation source and the amount are registered in association with each other in the allocation source record, which is a record corresponding to the allocation source, and the allocation destination record, which is a record corresponding to the allocation destination, contains the allocation source and the amount. The allocation destination and the purchase price are registered in association with each other. The control unit associates the allocation source record and the allocation destination record corresponding to the allocation source and the allocation destination associated with the association data with the specific process for specifying the allocation source record from the detail table according to the execution order. The allocation process of allocating the allocated amount to the purchase price associated with the allocation destination is executed. In the allocation process, when multiple allocation destinations are specified, the control unit prorates the amount based on the purchase price after the amount has been allocated in the allocation up to the previous execution order. Allocate the apportioned amount obtained in the above to the purchase price.

Further, in the allocation device according to the present invention, in the allocation process, the control unit measures the ratio of the purchase price of each of the allocation destinations to the total purchase price associated with the plurality of allocation destinations. The amount is apportioned accordingly.

Further, in the allocation device according to the present invention, in the allocation process, the control unit controls the total amount of consumption tax on a plurality of fixed assets with respect to the purchase price for each allocation destination after the amount has been allocated. Is apportioned and the acquisition price including tax for each fixed asset is calculated.

Further, the allocation method according to the present invention is an allocation method executed by an information processing apparatus including a storage unit and a control unit. The storage unit contains a detail table containing records corresponding to the allocation destination, which is a plurality of fixed assets, and the allocation source, which is a common expense or a plurality of expenses included in the acquisition price of at least one of the plurality of fixed assets. , The apportionment table that stores the data indicating the execution order of allocation and the associated data that associates the allocation source and the allocation destination in association with each other is stored. In the allocation source record, which is a record corresponding to the allocation source, the allocation source and the amount of the allocation source are registered in association with each other, and the allocation destination is a record corresponding to the allocation destination. In the record, the allocation destination and the purchase price of each of the allocation destinations are registered in association with each other. Further, the allocation method according to the present invention details the allocation source record and the allocation destination record corresponding to the allocation source and the allocation destination associated with the association data according to the execution order executed by the control unit. It includes a specific step specified from the table and an allocation 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 prorates the amount based on the purchase price after the amount is allocated in the allocation up to the previous execution order, and apportions the amount. Allocate the apportioned amount obtained in the above to the purchase price.

Further, the allocation program according to the present invention is an allocation program for being executed by an information processing apparatus including a storage unit and a control unit. The storage unit contains a detail table containing records corresponding to the allocation destination, which is a plurality of fixed assets, and the allocation source, which is a common expense or a plurality of expenses included in the acquisition price of at least one of the plurality of fixed assets. , The apportionment table that stores the data indicating the execution order of allocation and the associated data that associates the allocation source and the allocation destination in association with each other is stored. In the allocation source record, which is a record corresponding to the allocation source, the allocation source and the amount of the allocation source are registered in association with each other, and the allocation destination is a record corresponding to the allocation destination. In the record, the allocation destination and the purchase price of each of the allocation destinations are registered in association with each other. Further, 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 associated with the association data according to the execution order for the control unit to execute. It includes a specific step specified from the detail table and an allocation 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 prorates the amount based on the purchase price after the amount is allocated in the allocation up to the previous execution order, and apportions the amount. Allocate the apportioned amount obtained in the above to the purchase price.

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

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

Hereinafter, embodiments of an allocation device, an allocation method, and an allocation program according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to this embodiment.

[1. Overview]
When a company, etc. purchases multiple fixed assets such as land, buildings, furniture, etc. at once, the amount of various costs and common costs such as discounts for the purchase are collectively described on the delivery note. In some cases. However, in terms of accounting, companies, etc. record the acquisition amount including the amount of common expenses such as various expenses and discounts for each fixed asset. Hereinafter, when such various expenses and various common expenses are collectively referred to, they are referred to as common expenses and the like.

In addition, the carry-in and installation costs and discounts for furniture, etc. included in the common costs may be applied to only some of the fixed assets purchased in bulk. In addition, common expenses, etc. are apportioned and allocated to the purchase price of fixed assets, and another common expenses, etc. are apportioned and allocated to the amount after the allocation. May be done. However, with the conventional technology, it has been difficult to specify the allocation destination and perform multi-step allocation. For this reason, the person in charge of a company, etc. allocates common expenses, etc. to each fixed asset by manual calculation, and it is required to reduce the workload required for allocation and improve the efficiency of registration work of purchased fixed assets. Was being done.

Therefore, in the present embodiment, for example, an allocation device capable of reducing the workload of the person in charge of allocating common expenses to a plurality of fixed assets and streamlining the registration work of purchased fixed assets. , Offers allocation methods and programs. Hereinafter, a specific configuration and operation will be described.

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

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

As shown in FIG. 1, 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. Each part of the allocation device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the allocation device 100 to the network 300 so as to be communicable 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 distribution device 100 and the server 200 so as to be communicable with each other, and is, for example, the Internet, a LAN (Local Area Network), or the like. The data stored in the storage unit 106, which will be described later, may be stored in the server 200. Further, each functional unit included in the control unit 102 may be provided in the server 200.

An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). As the input device 112, a keyboard, a mouse, and a microphone, as well as a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving an instruction to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) / ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used.

As shown in FIG. 1, the storage unit 106 distributes the estimation header database (DB) 106a, the estimation detail database (DB) 106b, the estimation detail database (DB) 106c, and the allocation header database (DB) 106d. A schedule 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 are stored.

The quotation header database 106a is a database in which summary information of quotation data regarding the purchase of fixed assets is registered. The summary information of the quotation data is information on the entire transaction of a plurality of fixed assets purchased in a batch.

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

The item "estimate number" is an item in which the estimate number is registered. A quote number is a number or code that identifies a purchase transaction for a fixed asset. The quotation number may be numbered in the unit of the quotation (delivery note) at the time of purchasing the fixed asset, or may be a product that integrates a plurality of quotation. The quotation number is the primary key of the quotation header database 106a, and the data stored in other items are associated with the quotation number. Further, the item "estimate number" is an item for associating the estimate header database 106a with the estimate detail database 106b described later.

The item "acquisition date" is an item for registering the date when the fixed asset to be registered is acquired. Alternatively, the acquisition date may be the input date of the quotation data, the delivery date described in the quotation, or the like.

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

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

The item "allocation number" is an item in which an allocation number that specifies the allocation process is stored after the allocation process such as common expenses is performed by the allocation unit 102d described later. Further, the item "allocation number" is an item for associating the estimation header database 106a with the allocation header database 106d described later.

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

As shown in FIG. 2, the quotation detail database 106b has the quotation number, the quotation internal line number, the asset cost common cost classification, the asset name, the quotation amount, the quotation quantity, and the tax-excluded amount after apportionment as items. , The apportioned consumption tax, the amount including tax after apportionment, and the apportioned total amount.

The item "quotation number" is an item in which the quotation number is registered, and is an item for associating the quotation detail database 106b with the quotation header database 106a.

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

Further, the item "estimate number" and the item "estimate internal line number" are items for associating the estimate detail database 106b with the estimate detail database 106c and the allocation detail database 106e, which will be described later.

The item "asset expense common expense category" is an item in which the value or code of the category for identifying whether the information registered for each record is a fixed asset, an expense or a common expense is set. In other words, in the asset expense common expense category, whether each record included in the quotation detail database 106b corresponds to the fixed asset that is the allocation destination or the record that corresponds to the common expense that is the allocation source. To distinguish. For example, when the value set in the item "Asset expense common expense category" is "1", the registered information is a fixed asset. If 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 cost common cost category of this embodiment is an example, and is not limited to this.

Among the records included in the quotation detail database 106b, the record corresponding to the fixed asset as the allocation destination is an example of the allocation destination record in the present embodiment. Further, the record corresponding to the common cost or the like as the allocation source is an example of the allocation source record in the present embodiment.

The item "asset name" is an item in which the name of a fixed asset or common expense is registered.

The item "estimated amount" is an item in which an individual estimated amount for each fixed asset is registered. In addition, the estimated amount of common expenses and the like is 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. The estimated amount of common expenses and the like is an example of the amount in the present embodiment.

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

For the item "Amount excluding tax after apportionment", the purchase price to which common expenses, etc. are allocated for each fixed asset is registered after the allocation processing of common expenses, etc. is performed by the allocation unit 102d, which will be described later. It is an item. The tax-excluded amount after apportionment is an example of the acquisition price in this embodiment. The tax-excluded amount after apportionment is an example of the purchase price for each allocation destination after the amount has been allocated.

In the item "proportional consumption tax", the order consumption tax of the estimation header database 106a is apportioned according to the value of the tax-excluded amount after apportionment after the allocation processing of common expenses etc. is performed by the allocation unit 102d described later. This is the item for which the value is set.

The item "Amount including tax after apportionment" is an item in which a value obtained by adding the apportioned consumption tax to the amount excluding tax after apportionment is set. The tax-included amount after apportionment is an example of the tax-included acquisition price in this embodiment.

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

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

The item "quotation number" is an item in which the quotation number is registered, and is an item for associating the quotation detail database 106c with the quotation detail database 106b.

The item "estimate internal line number" is an item in which the estimated internal line number is registered, and is an item for associating the estimated detailed database 106c and the estimated detailed database 106b.

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

The item "correspondence apportionment code" is an item in which the corresponding apportionment code corresponding to the fixed asset or common cost specified by the estimate number and the estimate internal line number is registered. The corresponding apportionment code is data that links common expenses, etc., which are the allocation source, with fixed assets, which are the allocation destination. For example, if there is a common cost, etc. for only some of the fixed assets purchased in bulk, the common cost, etc. that is the allocation source and some of the allocation destinations according to the corresponding apportionment code. Fixed assets are identified by the corresponding apportionment code. Further, when a plurality of corresponding apportionment codes are set in the same corresponding apportionment level, for example, the apportionment may be performed in ascending order of the corresponding apportionment codes. The corresponding apportionment code is an example of the associative data that links the allocation source and the allocation destination in the present embodiment.

Further, the item "correspondence apportionment level" and the item "correspondence apportionment code" are items for associating the estimation detail database 106c with the allocation detail database 106e described later.

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

The quotation number, the quotation internal line number, the corresponding apportionment level, and the corresponding apportionment code are the primary keys of the estimation 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 summary information of allocation data, which is the allocation result of expenses or common expenses for each fixed asset, is registered. As shown in FIG. 2, the allocation header database 106d includes the allocation number and the registration date as items.

The item "allocation number" is an item in which the allocation number for specifying the allocation process is stored, and is an item for associating the allocation header database 106d with the estimation header database 106a. Further, the item "allocation number" is also an item for associating the allocation header database 106d with 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 is 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 allocation result of expenses or common expenses for each fixed asset, is registered. The detailed information of the allocation data is data including the amount allocated to each fixed asset for each allocation level (stage).

As shown in FIG. 2, the allocation detail database 106e has, as items, an allocation number, an estimate number, an estimate internal line number, a corresponding apportionment level, a corresponding apportionment code, a common cost number, and a common cost inside. Includes line number and apportioned split amount.

The item "allocation number" is an item in which the allocation number is stored, and is an item for associating the allocation detail database 106e with the allocation header database 106d.

The item "estimate number" is an item in which an estimate number for specifying the estimate data to be allocated is registered, and is an item for associating the allocation detail database 106e with the estimate detail database 106b.

The item "estimated internal line number" is an item in which the estimated internal line number that specifies the fixed asset to be allocated in the allocation process is registered. Further, the item "estimate internal line number" is an item for associating the allocation detail database 106e with the quotation detail database 106b.

The item "correspondence apportionment level" is an item in which the correspondence apportionment level is registered, and is an item for associating the allocation detail database 106e with the estimation detail database 106c.

The item "correspondence apportionment code" is an item in which the correspondence apportionment code is registered, and is an item for associating the allocation detail database 106e with the estimation detail database 106c.

The item "common cost number" is an item in which a quotation number that specifies estimation data including common costs that are the allocation source in the allocation process is registered.

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

The item "Apportioned split amount" is the corresponding apportionment level and correspondence for the fixed assets registered in the item "Estimated internal line number" from the amount of common expenses etc. registered in the item "Common cost internal line number". It is an item to register the apportioned split equivalent amount apportioned for each apportioned code. The apportioned split amount is an example of the apportioned amount in the present embodiment.

The allocation number, the estimate number, the estimate internal line number, the corresponding apportionment level, the corresponding apportionment code, the common expense number, and the common expense internal line number are the primary keys of the allocation detail database 106e, and are apportioned. Minute allocation amounts are associated with these items.

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

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

The monthly depreciation database 106h is a database in which the amount of depreciation expense related to the purchased fixed assets converted by month is registered.

The journal database 106i is a database in which journal data generated by the purchase or depreciation of fixed assets is 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 include other items in addition to the above items. Further, among the above-mentioned databases, 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 collectively controls the allocation device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

As shown in FIG. 1, the control unit 102 includes a display control unit 102a, a reception unit 102b, an estimation 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 estimation data input screen, an allocation execution screen, an approval screen, and the like. The quotation data input screen is a screen for the person in charge to input the information described in the quotation or the like sent from the purchaser regarding the purchase of fixed assets. The allocation execution screen is a screen for executing the allocation process for the registered quotation data. The approval screen is a screen for displaying an estimate of fixed assets after common expenses and the like are allocated, and for an administrator or the like to approve the displayed result.

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

Further, the reception unit 102b receives information for specifying the estimation data of the allocation target input to the allocation execution screen by the person in charge and an execution command for the allocation process. In this case, the reception unit 102b sends the input information for specifying the estimation data of the allocation target, for example, the estimation number, to the allocation unit 102d.

In addition, the reception unit 102b accepts that the administrator or the like has input to approve the estimate of the fixed asset from the approval screen. In this case, the reception unit 102b sends information that identifies the approved quotation, for example, a quotation number, to the fixed asset information generation unit 102e.

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

The allocation unit 102d identifies the quotation data to be allocated received by the reception unit 102b from the quotation data registered in the quotation header database 106a, the quotation detail database 106b, and the quotation detail database 106c, and sets common costs and the like as fixed assets. To distribute. In other words, the allocation unit 102d identifies the allocation source record and the allocation destination record corresponding to the allocation source and the allocation destination associated with the quotation internal line number from the quotation detail database 106b. Further, 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 allocates the estimated amount of common expenses, etc., and the estimated amount of common expenses, etc. in the allocation up to the previous apportionment level. After that, the fixed assets are apportioned based on the estimated amount, and the apportioned split amount obtained by the apportionment is allocated to the estimated amount associated with the fixed assets.

In addition, the allocation unit 102d prorates the total amount of consumption tax on a plurality of fixed assets to the estimated amount for each fixed asset after the common expenses are allocated, and sets 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 detail database 106b, and the quotation detail database 106c.

When the reception unit 102b accepts the approval of the estimate, the fixed asset information generation unit 102e generates various information about the fixed asset from the approved estimation data after the allocation process, and the generated information is used as each information. Register in the database corresponding to. For example, the fixed asset information generation unit 102e registers information about the purchased fixed asset in the asset database 106f. Further, the fixed asset information generation unit 102e registers the depreciation cost related to the purchased fixed asset in the depreciation database 106g. Further, the fixed asset information generation unit 102e registers the amount of depreciation expenses related to the purchased fixed assets converted by month in the monthly depreciation database 106h. Further, the fixed asset information generation unit 102e registers the journal data generated by the purchase or depreciation of the fixed asset in the journal database 106i.

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

[3. Processing flow]
Next, the allocation process of the present embodiment configured as described above will be described. FIG. 3 is a diagram showing an example of a flow of a series of processes including the allocation according to the present embodiment. As shown in FIG. 3, first, in the quotation data input processing, 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 estimation data input screen according to the present embodiment. As shown in FIG. 4, the quotation data input screen includes a plurality of input fields for inputting information included in the quotation data. Further, as shown in FIG. 4, the estimate data input screen includes a header unit, an asset detail unit, and an expense common expense detail unit.

In the header part, summary information of estimation data regarding the purchase of fixed assets is input. Further, in the asset detail unit, detailed information for each fixed asset of the estimation data regarding the purchase of the fixed asset is input. In addition, detailed information such as common expenses related to the purchase of fixed assets is input to the expense common expense detail section.

As an example of the display layout of the estimate data input screen, the header part is displayed at the top of the screen, the asset details part is displayed at the center of the screen, and the expense common expense details part is displayed at the bottom of the screen, but the display layout is limited to this. It is not something that will be done.

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

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

As shown in FIG. 5, the quotation data registration unit 102c registers the quotation number input in the header unit, the acquisition date, the order tax-excluded amount, and the order consumption tax in the estimate header database 106a in association with each other. .. Further, the quotation number may be automatically numbered by the quotation data registration unit 102c or the like.

Further, the estimate data registration unit 102c has an estimate number input in the header unit, detailed information for each fixed asset input in the asset detail unit, and detailed information such as common expenses input in the expense common cost detail unit. Are registered in the quotation detail database 106b and the quotation detail database 106c in association with each other.

Specifically, the data input in the "row number" of the asset detail section and the expense common cost detail section is registered in the item "estimate internal line number" of the quotation detail database 106b and the quotation detail database 106c.

In addition, the "asset classification" in the asset details section indicates the name of the fixed asset. The data entered in the item is registered in the item "asset name" of the quotation detail database 106b. In addition, the "asset classification" in the expense common expense statement section indicates the name of the common expense, etc. The data entered in the 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 expense common cost details section is registered in the item "estimated amount" of the estimate details database 106b.

"Proportion 1" to "Proportion 5" in the asset details section and the expense common cost details section indicate the corresponding apportionment level of fixed assets or common expenses. Further, the data input in "Proportion 1" to "Proportion 5" indicates a corresponding apportionment code such as fixed assets or common expenses. For example, the quotation data registration unit 102c registers the corresponding quotation code input in “correspondence 1” in the estimation detail database 106c as “correspondence apportionment level” = “1” and “correspondence apportionment code” = “10”. ..

In FIG. 4, the input fields up to the corresponding proportional division level 5 are displayed, but a configuration may be adopted in which the display control unit 102a adds an input field by an operation of a person in charge of inputting the estimation data or the like.

Further, the values of the estimation data shown in FIGS. 4 and 5 are examples, and the values are not limited thereto. For example, the data set as the corresponding apportionment code only needs to be able to associate the allocation source and the allocation destination, and characters and codes such as "A", "B", and "C" are set instead of numerical values. You may.

By registering the quotation data by the quotation data registration unit 102c, the quotation data in the state before allocation is registered in each database as shown in the lower part of FIG. Further, the corresponding apportionment level and the corresponding apportionment code related to the fixed assets, the common expenses, etc. registered in the quotation detail database 106b are registered in association with the quotation detail database 106c.

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

FIG. 7 is a diagram showing an example of the allocation execution screen according to the present embodiment. The display control unit 102a controls the monitor 114 to display the allocation execution screen. The person in charge inputs the quotation number for specifying the quotation data to be the target of the allocation process in the input field of "target quotation 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 quotation number input from the allocation execution screen (S1).

The allocation unit 102d generates an allocation number for specifying the allocation process (S2). Further, the allocation number may be determined by the person in charge or the like and input from the allocation execution screen. Further, 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 in the display control unit. Send to 102a. The display control unit 102a displays the acquired order tax-excluded amount as an estimated amount on the allocation execution screen. Further, 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 a person in charge or the like.

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

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

Then, the allocation unit 102d executes the apportionment processing of the common cost and the like according to the corresponding apportionment level registered in the estimation detail database 106c. In this embodiment, as shown in FIG. 5, the corresponding apportionment levels 1 to 3 are registered. In this case, the allocation unit 102d first executes the apportionment processing of the apportionment level 1 (S4).

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

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

The allocation unit 102d acquires the estimated internal line numbers “1” to “4” and “901” corresponding to the corresponding apportionment code “10” at the beginning of the sort result (S43).

As shown in FIG. 9A, the allocation unit 102d has the fixed assets (allocation destinations) corresponding to the acquired estimated internal line numbers “1” to “4” and the expenses corresponding to the estimated internal line numbers “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 by the asset expense common expense category.

Then, the allocation unit 102d prorates the estimated amount of expenses or common expenses according to the ratio of the estimated amount of each fixed asset to the total value of the estimated amounts of the fixed assets to be allocated (S45). FIG. 9B is a diagram illustrating an example of the apportionment processing of the apportionment level 1 according to the present embodiment. As shown in FIG. 9B, the allocation unit 102d sets the estimated amount of each of the fixed assets "equipment A" to "equipment D" corresponding to the estimated internal line numbers "1" to "4" to "equipment equipment". Divide by the total value of the estimated amount of "A" to "equipment D". Then, the allocation unit 102d obtains the calculation result by multiplying the division result by the estimated amount "300" of the "installation cost 1" which is the cost of the allocation source. In the calculation result, the allocation unit 102d rounds down to the nearest whole number.

Then, the allocation unit 102d adjusts the fraction with respect to the calculation result (S46). Specifically, as shown in FIG. 9B, the allocation unit 102d compares the calculation result with the estimated amount “300” of the “installation cost 1”, and sets the difference “2” from the above calculation results. , Add to the one with the largest value. In the example shown in FIG. 9B, since the calculation result “140” corresponding to “equipment A” is the largest, the difference is added to obtain “142”, which is the proportional division result at the proportional division level 1.

Since the example shown in FIG. 9B is the apportionment level 1 and is the first apportionment process in the present allocation process, the allocation unit 102d uses the estimated amount of fixed assets as the calculation base amount of the apportionment process. If the apportionment process of the level before the currently executed apportionment level process has already been performed, the allocation unit 102d is a fixed asset to which the result of the apportionment process up to the previous level is distributed. Prorate processing is performed using the estimated amount of money. The apportionment processing after the apportionment level 2 will be described later.

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

In the example shown in FIG. 9A, since the corresponding apportionment code related to the apportionment level 1 is only “10”, the allocation unit 102d determines that the apportionment processing has been completed for all the corresponding apportionment codes (S47 “Yes””. ), 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 the apportionment level 1 according to the present embodiment. As shown in FIG. 9C, the allocation unit 102d registers the apportionment result obtained by the mathematical formula shown in FIG. 9B in the allocation detail database 106e as the apportionment split equivalent amount. Further, at this time, the allocation unit 102d corresponds the apportioned division amount to the allocation number and the estimation number related to the allocation processing, the estimated internal line number related to the apportionment level 1, and the corresponding apportionment level. The apportionment code, the common cost number (estimated number of common cost, etc.), and the common cost internal line number (estimated internal line number of common cost, etc.) are registered in the allocation detail database 106e in association with each other.

Further, the allocation unit 102d calculates the tax-excluded amount after apportionment by adding the apportioned split 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. , Registered in the quotation detail database 106b (S50). The tax-excluded amount after apportionment may be referred to in the next apportionment level 2 and 3 processing, and the storage method is not limited to registration in the database. For example, the allocation unit 102d may hold the calculated tax-excluded amount after apportionment in a temporary table, a variable, or the like formed on the memory while the allocation process shown in FIG. 6 is being executed.

At this point, the processing of the flowchart shown in FIG. 8 ends. Next, the allocation unit 102d returns to the flowchart of FIG. 6 and executes the apportionment processing of the apportionment level 2 (S5). The basic flow of the apportionment processing of the apportionment level 2 is the same as the flow of the apportionment processing of the apportionment level 1 shown in FIG. The parts that are partially different from the apportionment processing of the apportionment level 1 will be described individually.

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

Next, as in the process of S42, the allocation unit 102d sorts the records extracted from the estimation detail database 106c in ascending order by the corresponding proportional division code. As shown in FIG. 10A, the record of the estimation number = “DEN001” and the corresponding apportionment level = “2” includes the corresponding apportionment codes “20” and “30”.

Next, as in the process of S43, the allocation unit 102d acquires the estimation internal line number corresponding to the corresponding proportional division code at the beginning of the sort result from the estimation detail database 106c. In the apportionment processing of the apportionment level 2, the allocation unit 102d has the estimated internal line numbers “2”, “3”, “902” corresponding to the corresponding apportionment code “20” at the beginning of the sort result, and the beginning of the sort result. Correspondence The estimated internal line numbers "4" and "904" corresponding to the proportional division code "30" are acquired.

Next, as in the process of S44, the allocation unit 102d searches the estimated detail database 106b for the fixed asset corresponding to the acquired estimated internal line number and the expense or the common expense. As shown in FIG. 10A, in the apportionment processing of the apportionment level 2, the allocation unit 102d corresponds to the fixed assets corresponding to the estimated internal line numbers “2” and “3” and the estimated internal line numbers “902”. Expenses or common expenses are searched from the quotation detail database 106b. Further, the allocation unit 102d searches the fixed assets corresponding to the estimated internal line number “4” and the expenses or common expenses corresponding to the estimated internal line number “904” from the estimated detailed database 106b.

Then, the allocation unit 102d apportioned the estimated amount of the expense or the common expense. Unlike the processing of S45, the allocation unit 102d prorates the total value of the tax-excluded amount after apportionment calculated at the apportionment level 1 of the fixed assets to be allocated to the apportionment level 1 of each fixed asset. Estimated amount of expenses or common expenses is apportioned according to the ratio of the amount excluding tax. As described above, the tax-excluded amount after apportionment is the amount to which the apportioned split amount calculated by the apportionment process up to the previous level is allocated to the estimated amount.

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

FIG. 10B is a diagram illustrating an example of the apportionment processing of the apportionment level 2 according to the present embodiment. As shown in FIG. 10B, the allocation unit 102d first performs apportionment processing on fixed assets and expenses or common expenses corresponding to the corresponding apportionment code “20”. The allocation unit 102d sets the tax-excluded amount of the fixed assets "equipment / fixture B" and "equipment / fixture C" corresponding to the estimated internal line numbers "2" and "3" to "equipment / fixture B" and "equipment". Divide by the total value of the tax-excluded amount after apportioning the equipment C ". Then, the allocation unit 102d obtains the calculation result by multiplying the division result by the estimated amount “60” of the “installation cost 2” which is the cost of the allocation source. In the calculation result, the allocation unit 102d rounds down to the nearest whole number.

Then, as in the process of S46, the allocation unit 102d adjusts the fraction with respect to the calculation result.

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

In this case, as in the process of S48, the allocation unit 102d acquires the estimated internal line number corresponding to the next corresponding apportionment code “30”.

Next, the allocation unit 102d performs apportionment processing on the fixed assets and expenses or common expenses corresponding to the corresponding apportionment code “30”. As shown in FIG. 10B, the allocation unit 102d adds the tax-excluded amount of the fixed asset “equipment D” corresponding to the estimated internal line number “4” to the tax-excluded amount of the “equipment D”. Divide by value. Then, the allocation unit 102d obtains the calculation result by multiplying the division result by the estimated amount “70” of the “installation cost 3” which is the cost of the allocation source. In the calculation result, the allocation unit 102d rounds down to the nearest whole number. Then, as in the process of S46, the allocation unit 102d adjusts the fraction with respect to the calculation result.

Then, as in the process of S47, the allocation unit 102d again determines whether or not the apportionment process has been completed for all the corresponding apportionment codes included in the extracted records after the fraction adjustment. In the examples shown in FIGS. 10A and 10B, since the corresponding apportionment codes related to the apportionment level 2 are only “20” and “30”, the allocation unit 102d determines that the apportionment processing has been completed for all the corresponding apportionment codes. do.

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

Further, similarly to the processing of S50, the allocation unit 102d calculates the tax-excluded amount after apportioning and registers it in the estimation detail database 106b. In the apportionment processing of the apportionment level 2, the allocation unit 102d divides the apportionment amount for each fixed asset calculated at the apportionment level 2 and the apportionment amount for each fixed asset calculated at the apportionment level 1. Calculate the tax-excluded amount after apportioning by adding to the estimated amount of the fixed asset.

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

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

Next, as in the process of S42, the allocation unit 102d sorts the records extracted from the estimation detail database 106c in ascending order by the corresponding proportional division code. As shown in FIG. 11A, the record of the estimation number = “DEN001” and the corresponding apportionment level = “10” includes the corresponding apportionment code “10”.

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

Next, as in the process of S44, the allocation unit 102d searches the estimated detail database 106b for the fixed asset corresponding to the acquired estimated internal line number and the expense or the common expense. As shown in FIG. 10A, in the apportionment processing of the apportionment level 3, the allocation unit 102d has the fixed assets corresponding to the estimated internal line numbers “1”, “3”, “4” and the estimated internal line number “904”. The expense or common expense corresponding to "" is searched from the quotation detail database 106b.

Then, the allocation unit 102d shall refer to the total value of the apportioned tax-excluded amount calculated up to the apportioned level 2 of the fixed assets to be allocated, and the apportioned tax-excluded amount calculated up to the apportioned level 2 of each fixed asset. Prorate the estimated amount of expenses or common expenses according to the proportion of the amount. FIG. 11B is a diagram illustrating an example of the apportionment processing of the apportionment level 3 according to the present embodiment. As shown in FIG. 11B, the allocation unit 102d has the fixed assets “equipment A”, “equipment C”, and “equipment D” corresponding to the estimated internal line numbers “1”, “3”, “4”. The tax-excluded amount after apportioning is divided by the total value of the tax-excluded amount after apportioning of "equipment A", "equipment C", and "equipment D". Then, the allocation unit 102d obtains the calculation result by multiplying the division result by the estimated amount “−120” of the “discount” which is the expense of the allocation source. In the calculation result, the allocation unit 102d rounds down to the nearest whole number.

Then, as in the process of S46, the allocation unit 102d adjusts the fraction with respect to the calculation result. The process from the determination of whether or not the apportionment process is completed for all the corresponding apportionment codes to the registration of the apportionment result is the same as the process of S47 and S49 in FIG. FIG. 11C is a diagram illustrating an example of the apportionment processing result of the apportionment level 3 according to the present embodiment. As shown in FIG. 11C, the allocation unit 102d registers the apportionment result obtained by the mathematical formula shown in FIG. 11B in the allocation detail database 106e as an apportionment split equivalent amount in association with other items.

Then, similarly to the processing of S50, the allocation unit 102d calculates the tax-excluded amount after apportionment and registers it in the estimation detail database 106b. In the apportionment processing of the apportionment level 3, the allocation unit 102d adds the apportioned split amount for each fixed asset calculated at the apportionment levels 1 to 3 to the estimated amount of the fixed asset, and calculates the tax-excluded amount after the apportionment. calculate.

Next, the allocation unit 102d returns to the flowchart of FIG. 6 and calculates the apportioned consumption tax and the apportioned tax-included amount (S7). Specifically, the allocation unit 102d apportionably divides the order consumption tax registered in the estimation header database 106a to the tax-included amount after the apportionment for each fixed asset after the apportionment processing of the apportionment levels 1 to 3, and fixes it. Calculate the apportioned consumption tax for each asset. Further, the allocation unit 102d adds the calculated apportioned consumption tax for each fixed asset to the estimated amount of the fixed asset, and calculates the apportioned tax-included amount.

In other words, the allocation unit 102d pays the consumption tax on a plurality of fixed assets to the estimated amount for each fixed asset after the estimated amount such as common expenses is allocated in the apportionment processing of the apportionment levels 1 to 3. The total amount is apportioned and the acquisition price including tax for each fixed asset is calculated.

Next, the allocation unit 102d registers the allocation result in each database (S8). Further, the allocation unit 102d updates the data of the allocation detail database 106e, the estimation detail database 106b, etc., which were updated each time in the above-mentioned apportionment processing, and registers the final processing result in the allocation processing.

FIG. 12A is a diagram showing an example of data registered in the allocation header database 106d and the allocation detail database 106e after the allocation process according to the present embodiment. As shown in FIG. 12A, the allocation unit 102d registers an allocation number specifying the above-mentioned 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 associated with each other by the allocation number. Further, the allocation unit 102d registers the registration date, which is the date on which the allocation data of the allocation process is registered, in the allocation header database 106d. Further, the allocation unit 102d registers the apportioned division equivalent amount calculated by the apportionment processing of each apportionment level in the allocation detail database 106e.

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

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

Further, the allocation unit 102d registers the apportioned tax-excluded amount, the apportioned consumption tax, the apportioned tax-included price, and the apportioned total amount in the quotation detail database 106b in association with the quotation number and the quotation internal line number, respectively. The apportioned total amount is the sum of the apportioned level amounts registered in the estimation detail database 106c for each fixed asset.

In the above-mentioned example shown in FIGS. 8 to 11C, the value is registered in the allocation detail database 106e, the estimation 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 value in a temporary table, a variable, or the like formed in the memory during the allocation process, and at the timing of the process of S8 in FIG. 6, the allocation detail database 106e and the estimate detail database. A value may be registered in 106b or the like.

By registering the allocation result, the allocation process shown in the flowchart of FIG. 6 is completed.

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

When the reception unit 102b accepts the approval of the estimate, the fixed asset information generation unit 102e generates various information about the fixed asset from the approved estimation data after the allocation process, and the generated information is used in the asset database. Register in 106f, depreciation database 106g, monthly depreciation database 106h, journal database 106i, etc.

As described above, in the allocation device 100 of the present embodiment, a plurality of fixed assets are allocated, and at least one of the plurality of fixed assets, a plurality of costs or common costs included in the tax-excluded amount after apportionment. The allocation source includes a control unit 102 and a storage unit 106 that allocate each estimated amount of the allocation source to each estimated amount of the allocation destination. Further, the storage unit 106 stores an estimation detail database 106b including records corresponding to the allocation destination and the allocation source, and an estimation detail database 106c for storing the corresponding apportionment level and the corresponding apportionment code in association with each other. The control unit 102 identifies the allocation source record and the allocation destination record corresponding to the allocation source and the allocation destination associated with the corresponding apportionment code from the quotation detail database 106b according to the corresponding apportionment level, and the cost. Alternatively, the allocation process of allocating the estimated amount of common expenses to the estimated amount of fixed assets is executed. Further, in the allocation process, when a plurality of fixed assets are specified, the control unit 102 allocates the estimated amount of the cost or the common cost to the estimated amount of the cost or the common cost in the apportionment process of the previous apportionment level. It is apportioned based on the estimated amount of fixed assets after it has been calculated, and the apportioned split amount obtained by the apportionment is allocated to the estimated amount of fixed assets. In other words, the allocation device 100 of the present embodiment can specify an allocation source and an allocation destination, and can allocate a plurality of common costs and the like in multiple stages. Therefore, according to the allocation device 100 of the present embodiment, the workload of the person in charge of allocating common costs and the like to a plurality of fixed assets is reduced, and the registration work of the purchased fixed assets is streamlined. Can be done.

Further, in the allocation device 100 of the present embodiment, in the allocation process, the control unit 102 receives an expense or a ratio according to the ratio of the estimated amount of each fixed asset to the total value of the estimated amounts of the plurality of fixed assets. Prorate the estimated amount of common expenses. Therefore, according to the allocation device 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 the person in charge or the like manually calculating. Can be allocated.

Further, in the allocation device 100 of the present embodiment, in the allocation process, the control unit 102 sets the estimated amount of expenses or common expenses to the estimated amount for each fixed asset after allocation, excluding tax. On the other hand, the order consumption tax, which is the total amount of consumption tax on multiple fixed assets, is apportioned. Then, the allocation unit 102d calculates the tax-included amount after apportionment for each fixed asset. Therefore, according to the allocation device 100 of the present embodiment, it is possible to obtain the consumption tax for each fixed asset in consideration of the allocated common expenses and the like.

[4. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical ideas described in the claims.

Further, for example, among the processes described in the embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed. It is also possible to automatically perform all or part of the above by a known method.

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

Further, with respect to the allocation device 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, with respect to the processing functions included in the allocation device 100, particularly each processing function performed by the control unit 102, all or any part thereof is realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the allocation apparatus is required. Read mechanically to 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form a control unit.

Further, this computer program may be stored in an application program server connected to the allocation device 100 via an arbitrary network, and all or a part thereof can be downloaded as needed. be.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registration). Trademarks) (Electrically Erasable and Protocol Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disc), MO (Magnet-Optical Disc), DVD (Digital), DVD (Digital) It shall include any "portable physical medium". Therefore, a recording medium containing a program for executing a process or a process method as described herein also constitutes the present invention.

Further, the "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by an 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 and the installation procedure after reading in each device shown in the embodiment.

Various databases and the like stored in the storage unit 106 are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, 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 an arbitrary peripheral device is connected. Further, the allocation device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

Further, 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 a user's input operation from a personal computer or the like connected via a network and execute the process. Further, the allocation device 100 may be provided in a cloud environment or the like.

Furthermore, the specific form of distribution / integration of the device is not limited to the one shown in the figure, and all or part of the device may be functionally or physically in any unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

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

100 Distributor
102 Control unit
102a Display control unit
102b Reception department
102c Estimate data registration unit
102d Allocation unit
102e Fixed asset information generation unit
104 Communication interface section
106 Storage unit
106a Estimated Header Database (DB)
106b Quotation details database (DB)
106c Estimate details database (DB)
106d Allocation Header Database (DB)
106e Allocation details database (DB)
106f Asset database (DB)
106g depreciation database (DB)
106h Monthly depreciation database (DB)
106i Journal database (DB)
108 Input / output interface section
112 Input device
114 Output device (monitor)
200 servers 300 networks

Claims (1)

The purchase price of each of the allocation destinations is set to a plurality of fixed assets as allocation destinations and a plurality of expenses or common expenses included in the acquisition price of at least one of the plurality of fixed assets as the allocation source. It is an allocation device equipped with a control unit and a storage unit that allocates each amount of the allocation source.
The storage unit corresponds to a detail table including the allocation destination and records corresponding to the allocation source, data indicating the execution order of allocation, and associating data linking the allocation source and the allocation destination. Memorize and save the apportionment table,
In the allocation source record, which is a record corresponding to the allocation source, the allocation source and the amount are registered in association with each other.
In the allocation destination record, which is a record corresponding to the allocation destination, the allocation destination and the purchase price are registered in association with each other.
The control unit specifies the allocation source record and the allocation destination record corresponding to the allocation source and the allocation destination associated with the association data according to the execution order from the detail table. And the allocation process of allocating the amount associated with the allocation source to the purchase price associated with the allocation destination.
In the allocation process, when the control unit specifies a plurality of the allocation destinations, the purchase price after the amount is allocated in the allocation up to the previous execution order. The apportioned amount obtained by the apportionment is allocated to the purchase price.
Allocation device.

Images