Fixed asset management device, fixed asset management method, and fixed asset management program

Abstract

To provide a fixed asset management device, etc., that can improve the listability of items missed during correction when confirming correction requests by enabling the display of whether items that should be corrected as a set with items corrected in the correction request have been corrected.SOLUTION: In one embodiment, the input values of each data item are compared between the first registration data and the second registration data to detect modified data items whose input values were changed in the second registration data (step S11), a set of configuration values associated with a key value that matches an input value of a key item in the second set of registration data is collated with the set of input values associated with a combination of related data items in the data items of the second set of registration data (step S12), a screen requesting confirmation containing the detection result from step S11 and the matching result from step S12 is displayed (step S13).SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a fixed asset management device, a fixed asset management method, and a fixed asset management program. [Background technology]

[0002] Patent Document 1 discloses a fixed asset system that reduces costs incurred due to registration errors, etc., by providing a simplified registration screen for field departments to register fixed assets, allowing the field departments to enter only the items that can be entered there, and then having the accounting department perform the actual registration using the data entered by the field departments. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2024-423 Summary of the Invention [Problem to be solved by the invention]

[0004] Registering a fixed asset ledger requires the input of numerous items. For this reason, in fixed asset management operations, it's not uncommon for a new document to be created when an acquisition, transfer, or disposal occurs, followed by an amendment request. However, when approving an amendment request, the revised content is simply displayed, so the user must first confirm which items have been amended. Furthermore, if the items amended in the amendment request contain other items linked to accounting procedures, the user must also confirm that no items that should be amended as a set have been omitted. These reasons create the challenge of making the process of confirming amendment requests cumbersome.

[0005] The present invention has been made in consideration of the above, and aims to provide a fixed asset management device, a fixed asset management method, and a fixed asset management program that can improve the visibility of items that have not been corrected when confirming a correction request by making it possible to display whether items that should be corrected in conjunction with items corrected in a correction request have been corrected. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, a fixed asset management device of the present invention is a fixed asset management device having a control unit that can access first registration data in which input values ​​are registered for each data item related to a fixed asset application, second registration data in which some of the input values ​​included in the first registration data have been corrected, and master data in which key values ​​corresponding to master key items among the data items related to the fixed asset application are associated with sets of setting values ​​corresponding to combinations of related data items that are correlated with the key items, and the control unit has a detection unit that compares the input values ​​of each data item between the first registration data and the second registration data to detect corrected data items in the second registration data whose input values ​​have been corrected, a matching unit that matches a set of setting values ​​included in the master data that are linked to the key value that matches the input value of the key item in the second registration data, with a set of input values ​​linked to the combination of the related data items among the data items included in the second registration data, and a display control unit that displays a correction application confirmation screen that includes the detection results by the detection unit and the matching results by the matching unit.

[0007] In addition, in the fixed asset management device of the present invention, the correction application confirmation screen may have a layout in which the first registered data and the second registered data associated with the detection results by the detection unit and the matching results by the matching unit are arranged side by side, either horizontally or vertically.

[0008] In the fixed asset management device according to the present invention, the display control unit may highlight the related data items in the collation results by the collation unit for which the set value and the input value do not match.

[0009] In addition, in the fixed asset management device of the present invention, the display control unit may distinguish the display form of the related data item depending on whether the related data item in the matching result by the matching unit, whose set value and input value do not match, is the modified data item.

[0010] In addition, in the fixed asset management device of the present invention, the master data may be an asset classification master that includes asset classification as a key item and asset type, tax useful life, and accounting useful life as related data items.

[0011] In addition, in the fixed asset management device according to the present invention, the master data may be an installation location master that includes an installation location as a key item and includes a department, a reporting municipality, and an expense category as related data items.

[0012] In addition, in the fixed asset management device according to the present invention, the master data may be an asset type master that includes asset type as a key item and asset classification, tax depreciation method, and accounting depreciation method as related data items.

[0013] In the fixed asset management device according to the present invention, the application for the fixed asset may correspond to a type of change, such as acquisition, transfer or disposal of the fixed asset.

[0014] Furthermore, a fixed asset management method according to the present invention is a fixed asset management method executed by a fixed asset management device having a control unit, wherein the control unit is configured to be able to access first registration data in which input values ​​are registered for each data item related to a fixed asset application, second registration data in which some of the input values ​​included in the first registration data have been corrected, and master data in which key values ​​corresponding to master key items among the data items related to the fixed asset application are associated with sets of setting values ​​corresponding to combinations of related data items that are correlated with the key items. The method includes the following steps executed by the control unit: a detection step of comparing the input values ​​of each data item between the first registration data and the second registration data to detect corrected data items in the second registration data whose input values ​​have been corrected; a collation step of matching a set of setting values ​​included in the master data that is linked to the key value that matches the input value of the key item in the second registration data with a set of input values ​​linked to the combination of the related data items among the data items included in the second registration data; and a display control step of displaying a correction application confirmation screen including the detection result from the detection step and the collation result from the collation step.

[0015] Furthermore, a fixed asset management program according to the present invention is a fixed asset management program to be executed by a fixed asset management device having a control unit, the control unit being configured to be able to access first registration data in which input values ​​are registered for each data item related to a fixed asset application, second registration data in which some of the input values ​​included in the first registration data have been corrected, and master data in which key values ​​corresponding to master key items among the data items related to the fixed asset application are associated with sets of setting values ​​corresponding to combinations of related data items that are correlated with the key items. To be executed by the control unit, the program includes: a detection step of comparing the input values ​​of each data item between the first registration data and the second registration data to detect corrected data items whose input values ​​have been corrected in the second registration data; a matching step of matching a set of setting values ​​included in the master data that is linked to the key value that matches the input value of the key item in the second registration data with a set of input values ​​linked to the combination of the related data items among the data items included in the second registration data; and a display control step of displaying a correction application confirmation screen including the detection result from the detection step and the matching result from the matching step. [Effects of the Invention]

[0016] The present invention has the effect of improving the visibility of uncorrected items when checking a correction request by making it possible to display whether or not items that should be corrected in combination with items corrected in a correction request have been corrected. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a diagram showing an example of a business flow assumed in this embodiment. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the fixed asset management device according to this embodiment. [Figure 3] FIG. 3 is a diagram showing an example of registered data in a fixed asset ledger. [Figure 4] FIG. 4 is a diagram illustrating an example of the master data. [Figure 5] FIG. 5 is a diagram illustrating an example of matching the second registration data and the installation location master. [Figure 6] FIG. 6 is a diagram showing an example of matching between the second registration data and the asset classification master. [Figure 7] FIG. 7 is a diagram showing an example of the correction request confirmation screen. [Figure 8] FIG. 8 is a diagram showing an example of a flowchart of processing executed by the fixed asset management apparatus according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0018] Hereinafter, embodiments of a fixed asset management device, a fixed asset management method, and a fixed asset management program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to these embodiments.

[0019] [1. Overview] First, as part of the fixed asset management according to this embodiment, an example of the workflow executed when approving an amendment application will be described. Fig. 1 is a diagram showing an example of the workflow assumed in this embodiment. As shown in Fig. 1, a terminal device used by an applicant (hereinafter referred to as applicant terminal) acquires first registration data registered in the fixed asset ledger when a fixed asset is acquired, moved, or disposed of, or when a free transfer occurs (step S01).

[0020] Next, the applicant terminal accepts corrections to input values ​​of some of the data items included in the first registration data acquired in step S01 (step S02).The applicant terminal then submits a correction request to the terminal device used by the approver (hereinafter, the approver terminal) for the second registration data in which some of the input values ​​of the first registration data have been corrected in step S02 (step S03).

[0021] The approver terminal that receives such a correction request compares the input values ​​of each data item between the first registered data and the second registered data, and detects the corrected data items whose input values ​​have been corrected in the second registered data (step S11).

[0022] Then, the approver terminal checks the input values ​​of the data items in the second registration data against the setting values ​​defined in the master data (step S12).

[0023] Here, the master data defines a set of associated values ​​corresponding to the key items of the master among the data items related to fixed asset applications, and the combination of related data items that are associated with the key items. One aspect of "association" here is the interrelationship in accounting processing. In this case, data items that have an impact on accounting are defined as related data items.

[0024] Among the sets of setting values ​​contained in such master data, the set of setting values ​​associated with key values ​​that match the input values ​​of the key items in the second registered data are compared with a set of input values ​​associated with combinations of related data items among the data items contained in the second registered data.

[0025] Then, the approver terminal displays a correction request confirmation screen including the detection result in step S11 and the collation result in step S12 (step S13).

[0026] For example, FIG. 1 shows a confirmation screen for an amendment request for acquisition of an asset named "R Forklift II (Note: the actual notation may be Roman numerals)" identified by asset number A10011-000.

[0027] On this correction application confirmation screen, the corresponding first registered data before the correction and the corresponding second registered data after the correction are arranged side by side, and the correction data items where there is a difference between the input values ​​of the first registered data and the second registered data are highlighted with an underline. This makes it possible to compare the fixed asset application contents before and after the correction and improves the visibility of the correction items. For example, it is possible to see at a glance that the installation location has been changed from "Kawasaki 2nd Factory Building A" to "Kawasaki 2nd Factory Building C."

[0028] Here, on the correction request confirmation screen, data items with differences between the input values ​​in the secondary registration data and the set values ​​in the master data are highlighted. For example, in the example shown in Figure 1, an asterisk (*) is associated with the accounting department "Second Manufacturing Department." This alert display allows the approver to notice that the accounting department "Second Manufacturing Department" has been applied for with content that differs from the master settings. The display of the asterisk for the accounting department "Second Manufacturing Department," in other words, the alert display indicating a difference from the master settings, combined with the highlighting of the correction data items, makes it easy for the approver to visually confirm the following: For example, among the various data items displayed in the fixed asset ledger, it is easy to confirm that when changing the installation location to "Kawasaki Second Factory Building C," the data item "Accounting Department," which should be corrected together with "Kawasaki Second Factory Building C," has been omitted.

[0029] As described above, in this embodiment, it is possible to display whether or not items that should be corrected in conjunction with items corrected in a correction request have been corrected, thereby improving the visibility of items that have not been corrected when confirming a correction request.

[0030] [2. Configuration] An example of the configuration of the fixed asset management apparatus 100 according to this embodiment will be described with reference to Fig. 2 etc. Fig. 2 is a block diagram showing an example of the configuration of the fixed asset management apparatus 100.

[0031] The fixed asset management apparatus 100 is constructed based on a commercially available desktop personal computer. Note that the fixed asset management apparatus 100 is not limited to those constructed based on stationary information processing devices such as desktop personal computers, but may also be constructed based on portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

[0032] The fixed asset management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units comprised in the fixed asset management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0033] The communication interface unit 104 communicatively connects the fixed asset management apparatus 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 exchanging data with other devices via the communication line. Here, the network 300 has a function of connecting the fixed asset management apparatus 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the memory unit 106 may also be stored in the server 200, for example.

[0034] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, 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.

[0035] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0036] The storage unit 106 stores a fixed asset DB (DateBase) 106a, master data 106c, and the like.

[0037] Of these, the fixed asset DB 106a is a database that manages a collection of registered data of a fixed asset ledger. For such a fixed asset ledger, a database may be created for each type of change, such as acquisition, transfer, and disposal.

[0038] Such fixed asset DB 106a may include multiple pieces of registered data relating to the same fixed asset and the same change, such as first registered data 106a1 corresponding to the asset before correction and second registered data 106a2 corresponding to the asset after correction.

[0039] Fig. 3 is a diagram showing an example of registered data in a fixed asset ledger. Fig. 3 shows first registered data 106a1 and second registered data 106a2 related to the acquisition of an asset named "R Forklift II (Note: the actual notation may be Roman numerals)" identified by asset number A10011-000.

[0040] 3, the first registration data 106a1 and the second registration data 106a2 may include data items related to fixed asset applications. The first registration data 106a1 and the second registration data 106a2 have common data items. However, since the first registration data 106a1 is the registration data before correction, and the second registration data 106a2 is the registration data after correction, the input values ​​of some data items may be different.

[0041] The master data 106c is a master in which key values ​​corresponding to key items of the master among data items related to fixed asset applications are associated with sets of setting values ​​corresponding to combinations of related data items having correlation with the key items.

[0042] 4 is a diagram illustrating an example of the master data 106c, which may include an asset classification master 106c1, an installation location master 106c2, and an asset type master 106c3.

[0043] Of these, the asset classification master 106c1 includes asset classification as a key item and can be realized by a table or the like containing related data items such as asset type, tax useful life, and accounting useful life related to the asset classification. Furthermore, the installation location master 106c2 includes installation location as a key item and can be realized by a table or the like containing related data items such as department, reporting municipality, and expense category related to the installation location. Furthermore, the asset type master 106c3 includes asset type as a key item and can be realized by a table or the like containing related data items such as asset type, tax depreciation method, and accounting depreciation method related to the asset type.

[0044] 2, the control unit 102 is a CPU or the like that performs overall control of the fixed asset management apparatus 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

[0045] The control unit 102 is configured to be able to access the fixed asset DB 106a, master data 106c, etc. stored in the storage unit 106. These masters and tables may be provided in other locations (for example, the server 200) as long as they are accessible by the control unit 102.

[0046] The control unit 102 conceptually includes a detection unit 102a, a matching unit 102b, a display control unit 102c, and the like.

[0047] The detection unit 102a detects data items to be corrected. When the detection unit 102a receives a request to display a correction request, it can start processing operations. For example, the request to display a correction request can be received via the input device 112, such as by selecting one correction request from a list of unapproved correction requests, or by specifying a unique key for the correction request, such as an asset number or asset name. When a request to display a correction request is received in this manner, the detection unit 102a accesses the first registration data 106a1 and the second registration data 106a2 corresponding to the correction request specified in the display request. Then, the detection unit 102a compares the input values ​​of each data item between the first registration data 106a1 and the second registration data 106a2, and detects correction data items whose input values ​​have been corrected in the second registration data 106a2.

[0048] The collation unit 102b collates the second registration data 106a2 with the master data 106c. For example, the collation unit 102b collates a set of setting values ​​included in the master data 106c, the set of setting values ​​being associated with key values ​​whose input values ​​for key items in the second registration data 106a2 match, with a set of input values ​​being associated with a combination of related data items among the data items included in the second registration data 106a2. This collation may be performed in parallel for each of the asset classification master data 106c1, installation location master data 106c2, and asset type master data 106c3 included in the master data 106c.

[0049] The display control unit 102c displays a correction request confirmation screen including the detection result by the detection unit 102a and the matching result by the matching unit 102b on an arbitrary output destination such as the output device 114. On this correction request confirmation screen, the first registered data 106a1 corresponding to the data before the correction and the second registered data 106a2 corresponding to the data after the correction are arranged vertically or horizontally, and correction data items for which there is a difference between the input value of the first registered data 106a1 and the input value of the second registered data 106a2 are highlighted by underlining. Furthermore, on the correction request confirmation screen, among the related data items of the second registered data 106a2, data items for which there is a difference between the input value of the second registered data 106a2 and the set value of the master data 106c are highlighted.

[0050] [3. Specific Examples] Hereinafter, the information processing from the detection of correction data items by the fixed asset management apparatus 100 according to the present invention to the display of the correction application confirmation screen will be described using a specific example with reference to FIGS.

[0051] As an example, a case will be taken where a display request for a correction application regarding the acquisition of an asset named "R Forklift II" identified by asset No. A10011-000 shown in FIG. 3 is accepted.

[0052] In this case, the detection unit 102a compares the input values ​​of each data item between the first registered data 106a1 and the second registered data 106a2. For example, in Fig. 3, the hatched areas indicate mismatches in the input values ​​between the first registered data 106a1 and the second registered data 106a2.

[0053] As shown in Figure 3, a mismatch is detected between the input value "Kawasaki 2nd Factory Building A" of the data item "Installation Location" in the first registration data 106a1 and the input value "Kawasaki 2nd Factory Building C" of the data item "Installation Location" in the second registration data 106a2.

[0054] Also, a mismatch is detected between the input value "4" of the data item "taxable useful life" of the first registered data 106a1 and the input value "5" of the data item "taxable useful life" of the second registered data 106a2.

[0055] Furthermore, a mismatch is detected between the input value "4" of the data item "accounting useful life" of the first registered data 106a1 and the input value "5" of the data item "accounting useful life" of the second registered data 106a2.

[0056] As a result, the detecting unit 102a can detect the data item "installation location", the data item "tax useful life", and the data item "accounting useful life" as corrected data items.

[0057] In parallel with the detection of such modified data items, the collating unit 102b collates the second registration data 106a2 with the master data 106c.

[0058] As one aspect, the matching unit 102b matches the second registration data 106a2 with the installation location master 106c2. Fig. 5 is a diagram showing an example of matching the second registration data 106a2 with the installation location master 106c2. Fig. 5 schematically shows a matching process performed between the second registration data 106a2 included in the correction request confirmation screen and the installation location master 106c2. Furthermore, Fig. 5 shows the correction data item "installation location" that differs between the first registration data 106a1 and the second registration data 106a2, as well as the input values ​​before and after the correction, framed in a thick dashed line.

[0059] Independently of detecting such a corrected data item "installation location," the collation unit 102b acquires from the installation location master 106c2 a set of setting values ​​linked to a key value that matches the input value "Kawasaki Second Factory Building C" of the key item "installation location" of the second registration data 106a2, as shown by the thick solid line frame in Fig. 5. That is, the set of setting values ​​"Kawasaki Second Factory Building C," "Third Manufacturing Department," "Kawasaki City," and "Manufacturing Cost," in other words, the record in the fourth row of the installation location master 106c2, is acquired as a set of setting values ​​linked to the key value "Kawasaki Second Factory Building C" shown by the thick solid line frame in Fig. 5 from the installation location master 106c2.

[0060] Then, the collating unit 102b collates the input values ​​of the second registration data 106a2 with the set values ​​of the installation location master 106c2 for each of the related data items "accounting department," "reporting local government," and "expense category" in the installation location master 106c2. That is, a set of input values ​​corresponding to the lightly hatched data entries in the second registration data 106a2 shown in Fig. 4 is collated with a set of set values ​​corresponding to the record in the fourth row of the installation location master 106c2 shown in Fig. 4.

[0061] Here, let us take as an example a comparison of the related data item "Accounting Department" out of the three related data items "Accounting Department," "Declaring Municipality," and "Expense Category." As shown by the bold dashed frame in Figure 5, the setting value "Third Manufacturing Department" in the installation location master 106c2 corresponding to the related data item "Accounting Department" does not match the input value "Second Manufacturing Department" in the second registration data 106a2 corresponding to the related data item "Accounting Department." As a result, the input value "Second Manufacturing Department" in the second registration data 106a2 for the related data item "Accounting Department" is extracted as a difference from the installation location master 106c2.

[0062] In another aspect, the matching unit 102b matches the second registered data 106a2 with the asset classification master 106c1. Fig. 6 is a diagram showing an example of matching the second registered data 106a2 with the asset classification master 106c1. Fig. 6 schematically shows the matching performed between the second registered data 106a2 included in the amendment request confirmation screen and the asset classification master 106c1.

[0063] Independently from detecting the above-mentioned correction data item "installation location," the collation unit 102b obtains from the asset classification master 106c1 a set of setting values ​​linked to the key value that matches the input value "vehicle forklift" of the key item "asset classification" in the second registration data 106a2, as shown by the thick solid line frame in Fig. 6. That is, as the set of setting values ​​linked to the key value "vehicle forklift" shown by the thick solid line frame in Fig. 6 from the asset classification master 106c1, the set of setting values ​​"vehicle transportation equipment," setting value "4," setting value "4," setting value "other than the above," and setting value "forklift" is obtained, in other words, the record in the first row of the asset classification master 106c1.

[0064] Then, the collating unit 102b collates the input values ​​of the second registered data 106a2 with the set values ​​of the asset classification master 106c1 for each of the related data items "asset type," "tax useful life," "accounting useful life," "structure," and "details" contained in the asset classification master 106c1. In other words, a set of input values ​​corresponding to the data entries with heavy hatching in the second registered data 106a2 shown in Fig. 4 is collated with a set of set values ​​corresponding to the record in the first row of the asset classification master 106c1 shown in Fig. 4.

[0065] Here, we will take as an example the matching of the related data item "tax useful life" among the five related data items excluding the key item asset classification: "asset type," "tax useful life," "accounting useful life," "structure," and "details." In this case, as shown by the bold dashed frame in Figure 6, the setting value "4" in the asset classification master 106c1 corresponding to the related data item "tax useful life" does not match the input value "5" in the second registered data 106a2 corresponding to the related data item "tax useful life." As a result, the input value "5" for the related data item "tax useful life" in the second registered data 106a2 is extracted as a difference from the asset classification master 106c1. Furthermore, we will take as an example the matching of the related data item "accounting useful life." 6, the set value "4" of the asset classification master 106c1 corresponding to the related data item "accounting useful life" does not match the input value "5" of the second registered data 106a2 corresponding to the related data item "accounting useful life." As a result, the input value "5" of the related data item "accounting useful life" in the second registered data 106a2 is extracted as a difference from the asset classification master 106c1.

[0066] After these collation results are obtained, the display control unit 102c causes the output device 114 to display a correction request confirmation screen including the collation results.

[0067] FIG. 7 is a diagram illustrating an example of a correction request confirmation screen. As shown in FIG. 7, the correction request confirmation screen displays first registration data 106a1 corresponding to the data before correction and second registration data 106a2 corresponding to the data after correction side by side. Furthermore, the correction request confirmation screen highlights, as a result of the detection of correction data items shown in FIG. 5, correction data items for which there is a difference between the input values ​​of first registration data 106a1 and second registration data 106a2, by underlining. This improves the comparison of the fixed asset application contents before and after correction and the visibility of the correction items. For example, it is possible to see at a glance that the installation location has been changed from "Kawasaki Second Factory Building A" to "Kawasaki Second Factory Building C."

[0068] Furthermore, on the correction request confirmation screen, as a result of comparing the second registration data 106a2 and the installation location master 106c2 shown in FIG. 5, data items for which there is a difference between the input value of the second registration data 106a2 and the set value of the installation location master 106c2 are highlighted. For example, in the example shown in FIG. 7, an asterisk "*" is associated with the recording department "Second Manufacturing Department." This alert display allows the approver to notice that the recording department "Second Manufacturing Department" has been applied for with different content than the set value "Third Manufacturing Department" in the installation location master 106c2. The display of the asterisk for the recording department "Second Manufacturing Department," in other words, the alert display indicating a difference from the master set value, combined with the highlighting of the correction data items, makes it easy for the approver to visually confirm the following: For example, when a wide variety of data items are displayed in the fixed asset ledger, the approver can easily confirm that when correcting the installation location to "Kawasaki 2nd Factory Building C," there is a missing correction to the data item "Accounting Department," which should be corrected together with "Kawasaki 2nd Factory Building C."

[0069] In addition, the correction request confirmation screen highlights data items where there are discrepancies between the input values ​​of the second registration data 106a2 and the asset classification master 106c1, as shown in Figure 6. For example, in the example shown in Figure 7, a double asterisk (**) is displayed in association with the input value "5" in the second registration data 106a2 corresponding to the related data item "tax useful life" and the input value "5" in the second registration data 106a2 corresponding to the related data item "accounting useful life." This allows the approver to understand that the applicant selected "Vehicle_Forklift" as the asset classification but applied for a useful life of 5 years, and therefore needs to confirm whether the useful life or asset classification is incorrect. Furthermore, the highlighting style, e.g., the number of asterisks, is displayed differently depending on the master type, making it easy to identify whether the cause of an omitted correction or input error lies in the asset classification, installation location, or asset type.

[0070] Furthermore, on the correction request confirmation screen, the display format of related data items whose set and input values ​​do not match in the collation results by the collation unit 102b is differentiated depending on whether the related data items are correction data items. For example, in the example shown in FIG. 7, of the three related data items whose set and input values ​​do not match—“Accounting Department,” “Tax Useful Life,” and “Accounting Useful Life”—two related data items, “Tax Useful Life” and “Accounting Useful Life,” are both correction data items, and are therefore highlighted with an underline, similar to the correction data item “Installation Location.” In this case, there is a high possibility that there is a difference with the master setting value. On the other hand, the related data item “Accounting Department” does not correspond to any of the correction data items “Installation Location,” “Tax Useful Life,” and “Accounting Useful Life.” In this case, there is a high possibility that the correction was omitted. In this way, by distinguishing the display format of related data items, such as whether or not to highlight the underline, depending on whether the related data items whose set and input values ​​do not match are correction data items, the possibility of classifying the cause and type of input error is increased.

[0071] [4. Processing performed by the fixed asset management device] Next, a description will be given of the processing executed by the fixed asset management apparatus 100. Fig. 8 is a diagram showing an example of a flowchart of the processing executed by the fixed asset management apparatus 100.

[0072] 8, first, the detection unit 102a receives a display request for a correction application (step S101). Next, the detection unit 102a accesses the first registration data 106a1 and the second registration data 106a2 corresponding to the correction application specified in the display request from the fixed asset DB 106a stored in the storage unit 106 (step S102).

[0073] Then, the detection unit 102a executes loop processing 1, which repeats the processing from step S103 to step S105 described below, the number of times corresponding to the total number K of data items related to fixed asset applications. Note that the processing from step S103 to step S105 described below may be executed in parallel for each data item.

[0074] That is, the detection unit 102a compares the input value of the k-th data item between the first registered data 106a1 and the second registered data 106a2 (step S103).

[0075] At this time, if there is a difference in the input value of the k-th data item (Yes in step S104), the detection unit 102a detects the k-th data item as the corrected data item (step S105). Note that if the input values ​​of the k-th data item match (No in step S104), the processing of step S105 is skipped.

[0076] By executing such loop process 1, M correction data items having different input values ​​can be detected from among K data items.

[0077] Next, the collation unit 102b executes loop process 2, which repeats the processes from step S106 to step S109 described below a number of times corresponding to the total number of masters N. Note that the processes from step S106 to step S109 described below may be executed in parallel for each master.

[0078] That is, the collation unit 102b acquires, from the n-th master, a set of setting values ​​associated with key values ​​that match the input values ​​of the key items in the second registration data 106a2 corresponding to the master n (step S106).

[0079] Then, the collation unit 102b executes loop process 3, which repeats the processes from step S107 to step S109 described below a number of times corresponding to the total number P of related data items included in the n-th master. Note that the processes from step S107 to step S109 described below may be executed in parallel for each related data item.

[0080] That is, the collation unit 102b compares the setting value of the p-th related data item with the input value of the data item in the second registered data 106a2 corresponding to the p-th related data item (step S107). At this time, if there is a difference between the setting value and the input value of the p-th related data item (step S108 Yes), the collation unit 102b sets the display mode of the input value of the p-th related data item to highlighted display (step S109). Note that if the setting value and the input value of the p-th related data item match (step S108 No), the processing of step S109 is skipped.

[0081] By executing such loop process 3, it is possible to extract, from among the P related data items, related data items that have a difference from the setting value of the nth master.

[0082] Furthermore, by executing loop process 2, it is possible to extract, for each of N masters, related data items that differ from the setting values ​​of each master.

[0083] Thereafter, the display control unit 102c arranges the first registered data 106a1 and the second registered data 106a2 accessed in step S102 side by side, and displays on the output device 114 a correction request confirmation screen in which the correction data items detected in step S105 are highlighted and the related data items of the second registered data 106a2 that were set to be highlighted in step S109 are highlighted (step S110), and the processing ends.

[0084] [5. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0085] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0086] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0087] 6. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0088] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0089] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0090] Furthermore, with regard to the fixed asset management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0091] For example, all or any part of the processing functions of the fixed asset management apparatus 100, particularly those performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or by hardware using wired logic. The program is stored on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the fixed asset management apparatus 100 as needed. That is, a computer program is stored in a storage unit such as a ROM or HDD (hard disk drive) for working with the OS to issue instructions to the CPU and perform various processes. The computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0092] This computer program may also be stored in an application program server connected to the fixed asset management apparatus 100 via any network, and all or part of it may be downloaded as needed.

[0093] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0094] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0095] The various databases stored in the memory unit 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 store various programs, tables, databases, and web page files used for various processes and providing websites.

[0096] The fixed asset management apparatus 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The fixed asset management apparatus 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

[0097] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0098] The present invention is useful in industries that manage fixed assets. [Explanation of symbols]

[0099] 100 Fixed asset management device 102 Control section 102a Detector 102b Matching section 102c Display control unit 104 Communication interface unit 106 Storage section 106a Fixed Assets DB 106a1 First registration data 106a2 Second registration data 106c Master Data 106c1 Asset Classification Master 106c2 Installation location master 106c3 Asset Type Master 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A fixed asset management device including a control unit, First registration data in which input values ​​are registered for each data item related to fixed asset applications; second registration data in which some of the input values ​​included in the first registration data have been corrected; master data in which key values ​​corresponding to master key items among data items related to the fixed asset application are associated with sets of setting values ​​corresponding to combinations of related data items having correlation with the key items; is accessible to The control unit a detection unit that compares input values ​​of each data item between the first registered data and the second registered data, and detects a modified data item whose input value has been modified in the second registered data; a collation unit that compares a set of setting values ​​included in the master data, which is linked to the key value that matches the input value of the key item of the second registration data, with a set of input values ​​that is linked to a combination of the related data items among the data items included in the second registration data; a display control unit that displays a correction request confirmation screen including the detection result by the detection unit and the matching result by the matching unit; A fixed asset management device comprising:

2. the correction request confirmation screen has a layout in which the first registered data and the second registered data associated with the detection result by the detection unit and the matching result by the matching unit are arranged side by side, either horizontally or vertically; 2. The fixed asset management device according to claim 1, wherein:

3. the display control unit highlights the related data items in the collation result by the collation unit where the set value and the input value do not match; 3. The fixed asset management device according to claim 2, wherein:

4. the display control unit distinguishes the display form of the related data item depending on whether the related data item in the collation result by the collation unit in which the setting value and the input value do not match is the correction data item; 3. The fixed asset management device according to claim 2, wherein:

5. The master data is an asset classification master including an asset classification as a key item and an asset type, a tax useful life, and an accounting useful life as related data items; 5. The fixed asset management device according to claim 1, wherein:

6. The master data is an installation location master including an installation location as a key item and a department, a reporting municipality, and an expense category as related data items; 5. The fixed asset management device according to claim 1, wherein:

7. The master data is an asset type master including an asset type as a key item and including an asset type, a tax depreciation method, and an accounting depreciation method as related data items; 5. The fixed asset management device according to claim 1, wherein:

8. The application for the fixed assets corresponds to the type of change in the acquisition, transfer or disposal of the fixed assets; 5. The fixed asset management device according to claim 1, wherein:

9. A fixed asset management method executed by a fixed asset management device having a control unit, The control unit First registration data in which input values ​​are registered for each data item related to fixed asset applications; second registration data in which some of the input values ​​included in the first registration data have been corrected; master data in which key values ​​corresponding to master key items among data items related to the fixed asset application are associated with sets of setting values ​​corresponding to combinations of related data items having correlation with the key items; It is configured to be accessible to Executed by the control unit, a detection step of comparing input values ​​of each data item between the first registered data and the second registered data, and detecting a modified data item whose input value has been modified in the second registered data; a collation step of comparing a set of setting values ​​included in the master data, which is linked to the key value that matches the input value of the key item of the second registered data, with a set of input values ​​linked to the combination of the related data items among the data items included in the second registered data; a display control step of displaying a correction request confirmation screen including the detection result obtained by the detection step and the matching result obtained by the matching step; containing, A fixed asset management method characterized by:

10. A fixed asset management program to be executed by a fixed asset management device having a control unit, The control unit First registration data in which input values ​​are registered for each data item related to fixed asset applications; second registration data in which some of the input values ​​included in the first registration data have been corrected; master data in which key values ​​corresponding to master key items among data items related to the fixed asset application are associated with sets of setting values ​​corresponding to combinations of related data items having correlation with the key items; It is configured to be accessible to To be executed by the control unit, a detection step of comparing input values ​​of each data item between the first registered data and the second registered data, and detecting a modified data item whose input value has been modified in the second registered data; a collation step of comparing a set of setting values ​​included in the master data, which is linked to the key value that matches the input value of the key item of the second registered data, with a set of input values ​​linked to the combination of the related data items among the data items included in the second registered data; a display control step of displaying a correction request confirmation screen including the detection result obtained by the detection step and the matching result obtained by the matching step; containing, A fixed asset management program featuring:

Images