JP4966624B2 - Checklist management method, checklist management device, checklist management system, and checklist management program - Google Patents

Description

  The present invention relates to a checklist management apparatus that generates and manages a checklist before submission of a corporate tax return document.

  When a corporation makes a corporate tax return, the national tax must be filed with the tax office of the head office, the prefectural tax with each prefecture where the office is located, and the municipal tax must be filed with the municipality where the office is located. .

  Accounting firms act as final tax returns for many corporations, but each corporation has different submission destinations, so to prevent omissions, use a checklist just before submitting (mailing) the final tax return. It is often checked against the light. Conventionally, spreadsheets such as Excel are generally used as these checklists, and accounting firms create, input, and manage this spreadsheet software.

  On the other hand, accounting firms generally use corporate tax filing application software (hereinafter referred to as corporate tax software) when filing a corporate tax return. This software uses prefectural tax and municipalities. In order to create a tax return for the private tax, the contents of the checklist, such as the information on the above-mentioned submission destination, are entered.

  Further, as an example of a method for managing the checklist, techniques as disclosed in Patent Documents 1 and 2 below are disclosed. The following Patent Document 1 is to display a check list for each deadline in order to manage the deadline, and the following Patent Document 2 is to attach a checklist or checklist to perform a reliable check by the checklist. Is used to manage the pass / fail judgment by. These are all techniques for managing the created checklist, and the generation and management of the checklist itself are not described.

JP-A-6-168252 JP 2000-132576 A

  However, despite the fact that basic information on each company, the tax office in charge, and information on the prefecture and municipality where the business is located are entered in the above-mentioned conventional corporate tax software, a checklist is created using spreadsheet software. In the case of creating a new one, it is necessary to input the same contents again, and there is a problem that a lot of labor is required to create a checklist format.

  In addition, if there is a change due to an increase or decrease in the number of establishments, it is necessary to perform final tax return processing based on the new information after the change and reflect the change contents in the checklist. Since the management of the list is performed independently, there is a problem that the check list is delayed and the correct check may not be performed.

  Further, as described above, the prior art described in Patent Documents 1 and 2 does not describe generation and management of the checklist itself, and cannot reduce labor in the checklist creation processing.

  The present invention has been made in view of the above, and it is an object of the present invention to obtain a checklist management apparatus capable of automatically generating a checklist from information related to a filing destination of a tax return input to corporate tax software. Objective.

In order to solve the above-described problems and achieve the object, a checklist management method according to the present invention includes a company basic information storage unit that stores company basic information including a company basic information input unit and verification data for identifying a company. Section, linked data interface section, application data including collation data created in financial or tax application and stored in disk section, linked data storage section for storing predetermined linked data included in the application data, checklist generation A check list management device comprising a check list storage unit for storing the generated check list, a check result input unit, a storage unit for storing the check results, and a display unit. Checklist for checking when submitting The basic company information input unit acquires the basic company information by inputting from the input unit or reading from basic company data stored in the company master device. The basic company information is stored in the basic company information storage unit. On the other hand, when the basic company information is already stored in the basic company information storage unit, the stored basic company information is referred to. The company basic information acquisition step, the linked data interface unit reads the application data from the disk unit, and stores the application data in the linked data storage unit, and the linked data interface unit includes the linked data interface unit, Included in the company basic information stored in the company basic information storage Combined data is read, the application data stored in the linked data storage unit is read, and the linked data that is the data of the check items necessary for generating the checklist is read from the application data for each of the read matching data. An interlocking data extraction step for storing the extracted interlocking data together with the corresponding collation data in the interlocking data storage unit, and the checklist generation unit reads the checklist format data stored in advance in the disk unit, A check list is generated by reading the link data stored in the link data storage unit and associating the link data as data of each check item of the read check list format data. A checklist generation step for storing in a storage unit, and a check result input unit for receiving a check result for each check item, and a check result input step for storing the check result for each check item in the storage unit; The display unit includes a display step of displaying the check list stored in the check list storage unit, or displaying the check list and the check result stored in the storage unit .

  Since the checklist management device according to the present invention automatically generates a checklist from information related to the filing destination of the final tax return input to the corporate tax software, the checklist can be efficiently created. In addition, there is an effect that consistency with the contents of the final income tax return input to the corporate tax software can be obtained.

  Hereinafter, embodiments of a checklist management method, a checklist management apparatus, a checklist management system, and a checklist management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  FIG. 1 is a diagram showing a configuration example of a computer system which has a function as a check list management apparatus for realizing a check list management method according to the present invention and can execute a check list management program according to the present invention. The computer system includes, for example, a control unit 1, an input unit 2, a storage unit 3, a disk unit 4, a display unit 5, a CD-ROM drive 6 and an external I / F unit 7, which are connected via a system bus 8. It is connected.

  In FIG. 1, the control unit 1 executes a check list management program according to the present invention. The input unit 2 is composed of, for example, a keyboard and a mouse, and is used by a computer system user to input various information. The storage unit 3 includes various memories such as a RAM and a ROM, and stores programs to be executed by the control unit 1 and necessary data obtained in the course of processing. The disk unit 4 is composed of a magnetic disk or the like, and stores programs and data. The display unit 5 is composed of a CRT, LCD (liquid crystal display panel), etc., and displays various screens for the computer system user.

  Here, an example of the operation of the computer system until the check list management program according to the present invention becomes executable will be described. In the computer system having the above-described configuration, for example, a check list management program is installed in the disk unit 4 from a CD-ROM set in the CD-ROM drive 6. Then, when the check list management program is executed, the check list management program read from the disk unit 4 is stored in a predetermined location in the storage unit 3. In this state, the control unit 1 executes a check list management process according to a program stored in the storage unit 3.

  In this embodiment, a program describing the checklist management processing is provided using a CD-ROM as a recording medium. However, the present invention is not limited to this, and it depends on the configuration of the computer system, the capacity of the provided program, and the like. For example, it is also possible to use a recording medium such as a magnetic disk such as a floppy (registered trademark) disk, a magneto-optical disk, or a magnetic tape. Moreover, it is good also as using the program provided by transmission media, such as an email and the internet.

  In this embodiment, the computer system also has a function as a company master device in addition to a function as a corporate tax application device. The corporate tax application program for realizing the function as the corporate tax application device and the management program for realizing the function as the company master device are installed in the disk unit 4 in the same manner as the checklist management program. When each program is executed, each installed program is stored in a predetermined location in the storage unit 3 and each process is executed.

  FIG. 2 is a diagram illustrating a functional configuration example of the checklist management apparatus 10 according to the present embodiment. The check list management apparatus 10 includes a control unit 1, an input unit 2, a storage unit 3, a disk unit 4, and a display unit 5 of the computer system shown in FIG.

  The control unit 1 includes a check list management control unit 11, an interlocking data I / F unit 14, and a check list generation unit 16. The storage unit 3 includes a company basic information storage unit 13, a linked data storage unit 15, and a check list storage unit 18. The disk unit 4 includes check list format data 17, company basic information data 22, and check result input data 20. The company basic information input unit 12 and the check result input unit 19 are configured by the input unit 2, the control unit 1, and the display unit 5, and the check list display unit 21 is configured by the display unit 5 and the control unit 1. The storage unit 3 includes a work memory area that is used when each unit of the control unit 1 performs each process, and each unit of the control unit 1 may include all or part of the work memory area as necessary. The process described later is executed using.

  The checklist management apparatus 10 includes a corporate tax information data 111, a corporate prefectural tax information data 112, a corporate municipal tax information data 113, which are created by the corporate tax application apparatus 100 and stored in the disk unit 4. The company basic information data 201 created by the master device 200 and stored in the disk unit 4 is read as necessary.

  FIG. 3 shows a configuration example of the corporate tax application device 100. The corporate tax application device 100 performs processing for corporate tax filing, and includes a corporate tax application control unit 101, a company basic information input unit 102, a company basic information storage unit 103 that stores the input information, and a corporate tax. Information input unit 104, corporate tax information storage unit 105 for storing the input information, corporate prefectural tax information input unit 106, corporate prefectural tax information storage unit 107 for storing the input information, and corporate municipal tax information An input unit 108 and a corporation municipal inhabitant tax information storage unit 109 for storing the input information are provided. The data of the company basic information storage unit 103, the corporate tax information storage unit 105, the corporate prefectural tax information storage unit 107, and the corporate municipal inhabitant tax information storage unit 109 are stored in the disk unit 4 as company basic information data 110 and corporate tax, respectively. Information data 111, corporate prefectural tax information data 112, and corporate municipal tax information data 113 are stored.

  FIG. 3 shows an example of the configuration, and any configuration may be used as long as data including linked data described later is stored in the disk unit 4.

  The company master device 200 is a device that manages common information about each company. The company master device 200 receives input of company basic information of the operator from the input unit 2, generates company basic information, and stores the company basic information in the disk unit 4. Saved as information data 201.

  FIG. 4 shows an example of the contents of the company basic information data 201 of the company master device 200. In the example of FIG. 4, the trade name code, trade name, representative name, settlement date, classification (corporate or individual), business type, main person in charge, address, telephone number, and update date are shown. FIG. 4 shows an example of basic information of a company that is generally required. In the present embodiment, the trade name code and trade name are the minimum required items. The items other than the trade name are not limited to the example of FIG. 4 and may be any items. Further, the present invention is not limited to this, and a taxpayer number, a user identification number (for national tax electronic declaration), and other numbers for identifying other companies may be used.

  The company basic information data 201 generated here, the company basic information data 110 of the corporate tax application apparatus 100, and the company basic information data 22 of the checklist management apparatus 10 need to match. Therefore, in the present embodiment, the company basic information input unit 12 of the checklist management apparatus 10 reads the company basic information data 201 and uses the contents as the company basic information data 22, via the input unit 2 from the operator. The company basic information data 22 is updated when there is an update operation. Similarly, the corporate tax application apparatus 100 reads out the company basic information data 201 and uses the contents as the company basic information data 110. When the operator performs an update operation via the input unit 2, the company basic information data 110 is read out. Update. Furthermore, when any one or more of the company basic information data 110, the company basic information data 22, and the company basic information data 201 is updated, the updated contents are reflected in other company basic information data.

  The company basic information data 22 of the checklist management apparatus 10 and the company basic information data 110 of the corporate tax application apparatus 100 have the same contents as in FIG. 4 in this embodiment, but as described above, the trade name code and trade name are the same. As long as it is included, other items need not be limited to this. In addition, the three basic data items of the checklist management device 10, the company basic information data 110 of the corporate tax application device 100, and the company basic information data 201 of the company master device 200 have a trade name code and trade name. It may be included, and other items may be different. However, since it is necessary to maintain the consistency of the contents of the common items, if any one or more of the company basic information data 22, the company basic information data 110, and the company basic information data 201 are changed as described above, Reflect in other company basic information data.

  5, 6, and 7 are diagrams showing examples of corporate tax information data 111, corporate prefectural tax information data 112, and corporate municipal tax information data 113 created by the corporate tax application device 100. For each trade name and trade name (for each company), the destination and tax amount are recorded for each year. Tax amounts generally vary from year to year, and the location of a company or office may also vary from year to year. Therefore, as shown in FIGS. In addition, the target year is not necessarily uniform for each company, since the time of establishment of the company and the time of management of the accounting office differ.

  5, 6, and 7 are examples, and other items are not limited as long as the check list management apparatus 10 includes necessary data. In this embodiment, the data required by the checklist management device 10 is a trade name code and trade name used for identification of company identity, and linked data (data read from the corporate tax application device 100), the target year, The destination of the documents such as tax returns, and the tax amount (corporate tax, prefectural tax, business tax, municipal tax, etc.).

  Subsequently, the operation of the checklist management apparatus 10 will be described. First, the checklist management apparatus 10 is activated by an operation of the input unit 2 by the operator. When activated, the checklist management control unit 11 instructs the company basic information input unit 12 to start a data linkage operation at predetermined intervals set in advance. Also, when the operator requests to start the data linkage operation by operating the input unit 2, the start of the data linkage operation is similarly instructed. The reason why the data linkage operation is performed periodically is to reflect the updated contents when the data of the corporate tax application apparatus 100 is updated. In this embodiment, the start of the data linkage operation is periodically instructed, but the checklist management control unit 11 detects the data update of the corporate tax application device 100 based on the data update date, etc. The start of the data linkage operation may be instructed only when there is an update.

  FIG. 8 is a flowchart showing the operation of the checklist management apparatus 10. First, the company basic information input unit 12 that receives an instruction to start the data linkage operation from the checklist management control unit 11 acquires the company basic information in response to an input from the operator, and stores the data in the company basic information storage unit 13. Is stored (step S1). The stored company basic information is simultaneously stored in the disk unit 4 as company basic information data 22.

  Here, the acquisition method of company basic information is demonstrated. First, when starting for the first time, no information is stored in the company basic information storage unit 13 of the checklist management apparatus 10 and the company basic information data 22 is not created, so the operator manually uses the input unit 2. The company basic information is stored in the company basic information storage unit 13 using the information input in the above or information read from the company basic information data 201 of the data of the company master device 200. The contents stored here are the same as those shown in FIG. 4 in the present embodiment as described above, but it is sufficient that at least the trade name code and trade name are included. Reading of the company basic information data 201 of the company master device 200 is performed, for example, by displaying a data reading button on the display unit 5 and being executed by the company basic information input unit 12 when the button is pressed by the operator. Alternatively, the company basic information input unit 12 may automatically read when an instruction to start the data linkage operation is received. The information read from the company basic information data 201 can be changed (updated, added, etc.) by the operator using the input unit 2 and the company basic information input unit 12 is operated by the input unit 2. The user's change content input operation is received, and the change content is reflected in the company information storage unit 13.

If information has already been stored in the company basic information storage unit 13 and no change has been input by the operator, the company basic information input unit 12 does not perform processing and proceeds to the next step.

Next, the linked data I / F unit 14 reads the corporate tax information data 111, the corporate prefectural tax information data 112, and the corporate municipal tax information data 113 created by the corporate tax application device 100 from the disk unit 4, It stores in the interlocking data storage part 15 (step S2). In this embodiment, the storage location of the corporate tax information data 111, the corporate prefectural tax information data 112, and the corporate municipal tax information data 113 is set in the checklist management apparatus 10 by initial setting or the like. The interlocking data I / F unit 14 of the check list management device 10 may search the disk unit 4 and automatically detect it.

  Further, the interlocking data I / F unit 14 sequentially refers to the trade name code and the trade name stored in the company basic information storage unit 13, and the interlocking data storage unit 15 covers the number of trade name codes (the same as the number of trade name names). Then, necessary item data (hereinafter referred to as interlocking data) is taken out and stored again in the interlocking data storage unit 15 (step S3). The fetching of linked data will be described with reference to the examples of FIGS. 5, 6, and 7. The trade name code and the trade name are used as a collation key for identifying the same company. The linked data about the company that matches the information stored in the company basic information storage unit 13 is taken out. The linked data in the present embodiment is the target year, jurisdiction tax office, and corporate tax amount for corporate tax information data 111, and the target year, submission destination, prefectural tax amount, business for corporate prefectural tax information data 112. It is a tax amount, and the corporate municipal inhabitant tax information data 113 is a target year, a destination, and a municipal inhabitant tax amount.

  FIG. 9 is a diagram illustrating an example of fetching linked data. FIG. 9 shows an example of the corporate prefectural tax information data 112. From the corporate prefectural tax information data 112, the target year, the destination, the prefectural tax, and the business tax are extracted.

  Next, the check list generating unit 16 reads the check list format data 17 from the disk unit 4 (step S4), and based on this format, the trade name code extracted in step S3 and stored in the interlocking data storage unit 15 and Check list data is generated using the trade name and linkage data, and stored in the check list storage unit 18 (step S5). The check list format data 17 includes linked data format (including option types), general items to be displayed as a check list in addition to linked data, their formats (including option types), and check results ( The format of the input field of the result of the check performed by the operator is stored in advance. The contents of the check list format data 17 may be changed by the check list generation unit 16 receiving an input from the operator.

  Next, the check list display unit 21 reads the check list data from the check list storage unit 18, processes it into display data, and displays it on the display unit 5 (step S6). FIG. 10 shows a screen display example of a check list related to corporate prefectural tax. FIG. 11 shows a screen display example of a check list related to corporate municipal tax. The display contents of the check list are the check items set in the check list format data 17 and the check result input fields. However, all items may be displayed simultaneously, or when there are many items. A plurality of display screens may be provided. Although the corporate tax is not shown, it is displayed including the destination and tax amount. 10 and 11 are examples, and any display method may be used as long as check items can be displayed and check results can be input.

  Based on this display content, the operator confirms a document such as a tax return created by a corporate tax application or the like, and inputs the check result field using the input unit 2 (step S7). In the example of FIG. 10, since the report type can be discriminated simultaneously, the operator checks any one of “intermediate”, “correct”, and “none” in the report type column using the input unit 2. Check the existence of documents.

  Next, the check result input unit 19 stores the input content of the check result by the operator in the storage unit 3 and also as the check result input data 20 of the disk unit 4 (step S8). For example, in the example of FIG. 10, when the operator selects the button corresponding to any one of the types of declarations by clicking in step S7, the check result input unit 19 displays the input type. Information (numerical value corresponding to the type) indicating that it has been checked, and information indicating that it has been checked (numerical value corresponding to two types of checked and unchecked, respectively) and check result input data 20 of the disk unit 4 Store as.

  Further, the check list display unit 21 reads the input content of the check result stored in the storage unit 3, converts it into display data, and displays the check result on the display unit 5 (step S9).

  If there is an instruction to start the next data linkage operation from the checklist management control unit 11, the process returns to step S1 and repeats up to step S10 (Yes in step S10). Further, when an end instruction is given by the operation of the input unit 2 by the operator, the operation is ended (step S11 Yes), and when there is no end instruction, step S7 to step S11 are repeated (No at step S11).

  In this embodiment, the input field is displayed on the check list display unit 21 so that the check result can be input on the screen. However, the check list display unit 21 does not include the input field, and for example, a printed check list is displayed. The operator may make a check using.

  As described above, the case of data linkage with the corporate tax application device 100 has been described. However, the object of data linkage is not limited to this, and can be managed by a checklist such as a statutory record application device, a depreciation application device, a year-end adjustment application device, or the like. Other financial or tax application devices that include the subject item can also be targeted.

  For example, an example in which data is linked with a statutory record application device will be described. FIG. 12 shows a configuration example of the statutory record application device 300. The legal application apparatus 300 includes a control unit 301, a company basic information input unit 302, a salary income withholding slip input unit 303, a retirement income withholding slip input unit 304, and a payment record input unit 305 for remuneration and fees. , An input unit 306 for payment records for real estate usage fees, etc., an input unit 307 for payment records for real estate consideration, an input unit 308 for salary and payment records for non-resident salaries, a company basic information storage unit 309, a salary income Withholding slip storage unit 310, retirement income withholding slip storage unit 311, remuneration / payment payment record storage unit 312, real estate use payment payment record storage unit 313, real estate consideration payment record Storage unit 314, non-resident salary and other salary and payment record storage unit 315, company basic information data 316, salary income withholding slip data 317, retirement income withholding slip data 31 , Consisting of compensation and charges, etc. of payment written statement data 319, payment written statement data 320 of the fee for use of real estate, payment written statement data 321 of the consideration of the real estate, salary and compensation payments written statement data 322 such as a non-resident salaries.

  When data is linked to the statutory record application device 300, the linked data includes the number of salary income withholding slips, the number of retirement income withholding slips, the number of payment records for remuneration and fees, real estate The number of preparations for payment records such as usage fees, the number of preparations for payment records for the sale and sale of real estate, the number of preparations for payment records for consideration of real estate, the number of preparations for salary and compensation payment records for non-resident salaries, etc. Respectively, withholding slip data 317 for salary income, withholding slip data 318 for retirement income, payment record data 319 for remuneration, fees, etc., payment record data 320 for real estate usage fees, etc., payment record data 321 for compensation for real estate , And salary / reward payment record data 322 such as non-resident salary. The number of payment records prepared for the sale and purchase of real estate is included in the payment record data 321 of the consideration for the real estate together with the number of payment records for the real estate consideration.

Then, in step S2 of the flowchart shown in FIG. 8 , the interlocking data I / F unit of the checklist management device 10 stores the corporate tax information data 111, the corporate prefectural tax information data 112, and the corporate municipal tax information data 113. Instead, salary income withholding slip data 317, retirement income withholding slip data 318, payment record data 319 for remuneration, fees, etc., payment record data 320 for real estate usage fees, etc., payment record data 321 for compensation for real estate , Salary / reward payment record data 322 such as non-resident salary is read. In step S3, as linked data, the number of salary income withholding slips, the number of withdrawn retirement income withholding slips, the number of payment records for remuneration, fees, etc., the number of payment records for real estate usage fees, etc. The number of sheets of payment records for real estate sales, the number of payment records for consideration of real estate, and the number of sheets of salary / remuneration payment records such as non-resident salary are taken out. Thereafter, it changed similarly linked data, it is possible to perform the data link operates in a similar process as in FIG.

  FIG. 13 shows a display example by the checklist display unit 21 when data linkage is performed with the legal record application device 300.

  Next, an example of data linkage with the depreciation application apparatus will be described. FIG. 14 shows a configuration example of the depreciation application apparatus 400. The depreciation application device 400 includes a control unit 401, a company basic information input unit 202, a depreciable asset declaration submission destination input unit 203, an asset data input unit 204, a depreciable asset declaration input unit 205, and a company basic information storage unit. 406, storage section 407 of depreciable asset declaration submission destination, asset data storage section 408, storage section 409 of depreciable asset declaration, company basic information data 410, depreciation asset declaration submission destination data 411, asset data 412 It consists of asset declaration data 413.

  When data linkage is performed with the depreciation application device 400, the linkage data is a depreciable asset report submission destination and a taxable standard amount of the depreciable asset report. These are assumed to be included in the depreciable asset report submission destination data 411 and depreciable asset report data 413, respectively.

In step S2 of the flowchart shown in FIG. 8 , the interlocking data I / F unit of the checklist management apparatus 100 replaces the corporate tax information data 111, the corporate prefectural tax information data 112, and the corporate municipal tax information data 113. The depreciable asset report submission destination data 411 and the depreciable asset report data 413 are read out. In step S3, the depreciable asset report submission destination and the taxable standard amount of the depreciable asset report are extracted as linked data. Thereafter, it changed similarly linked data, it is possible to perform the data link operates in a similar process as in FIG.

  FIG. 15 shows a display example by the checklist display unit 21 when data is linked with the depreciation application apparatus 400.

  Next, an example of performing data linkage with the year-end adjustment application device will be described. FIG. 16 shows a configuration example of the year-end adjustment application device 500. The year-end adjustment application device 500 includes a control unit 501, a company basic information input unit 502, an employee information input unit 503, a salary payment report input unit 504, a company basic information storage unit 505, an employee information storage unit 506, and a destination municipality storage. A unit 507, a salary payment report storage unit 508, company basic information data 509, employee information data 510, submission destination municipal data 511, and salary payment report data 512.

  When data linkage is performed with the year-end adjustment application device 500, the linkage data includes the payee payment report submission destination, the number of salary payment report submissions, and the employee name of the salary payment report. These are assumed to be included in the submission destination municipal data 511, employee information data 510, and salary payment report data 512, respectively.

In step S2 of the flowchart shown in FIG. 8 , the interlocking data I / F unit of the checklist management apparatus 100 replaces the corporate tax information data 111, the corporate prefectural tax information data 112, and the corporate municipal tax information data 113. The submission destination municipal data 511, employee information data 510, and salary payment report data 512 are read out. In step S3, the salary payment report submission destination, the number of salary payment report submissions, and the employee name of the salary payment report are extracted as linked data. Thereafter, it changed similarly linked data, it is possible to perform the data link operates in a similar process as in FIG.

  FIG. 17 shows a display example by the checklist display unit 21 when data linkage is performed with the year-end adjustment application device 500. In the example of FIG. 17, the employee name is not displayed, but only the number of sheets is displayed. The employee name is displayed separately for each company. When displaying up to the employee name, the number of columns for each company increases, so such a display method is used. However, the employee name may also be displayed at the same time.

  The linked data shown in the present embodiment is merely an example, and the present invention is not limited thereto, and any data item created by the linked application can be set.

  12, 14, and 16 are configuration examples, and any configuration may be used as long as data including interlocking data necessary in each case is generated and stored in the disk unit 4.

  In this embodiment, the company basic information data 201 of the company master device 200, the company basic information data 110 of the corporate tax application device 100, and the company basic information data 22 of the checklist management device 10 are always consistent. The company basic information input unit 12 reads from the company basic information data 201 of the company master device 200. However, the company basic information data 22 and the corporate tax application of the checklist management device 10 are used without using the company master device 200. The contents of the company basic information data 110 of the device 100 may be matched. In this case, for example, the company basic information data 110 of the corporate tax application device 100 may be read, or the company basic information data 22 of the check list management device 10 and the corporate basic information data 110 of the corporate tax application device 100 may be read. If either one is changed, the change may be reflected on the other, and the company basic information data 22 of the checklist management apparatus 10 may be directly read out.

In the present embodiment, the same computer system has the three functions of the company master device 200, the corporate tax application device 100, and the checklist management device 10. However, each device is realized by a separate computer system. You may do it. In this case, it is desirable that each computer has a network connection function, and each computer is connected by a network. When each computer is connected via a network, in the above embodiment, the company master device 200 and the corporate tax application device 100 are stored in the disk unit of the device on which each application operates instead of the disk unit 4. Will be. Then, the checklist management apparatus 10 reads data from the disk unit of each computer system via the network. Further, when each device is not connected via a network, the data created by the company master device 200 and the corporate tax application device 100 is copied to a recording medium, and the checklist management device 10 reads the data from the medium. An operation similar to that of the present embodiment can be realized. However, in this case, periodic updating is not possible.

  As described above, in the checklist management apparatus 10 according to the present embodiment, the submission destination and the tax amount of the declaration form and the like are read from the data created by the corporate tax application apparatus 100 and reflected in the checklist. It is not necessary for the person to re-enter the submission destination of the document such as the return form and the tax amount for creating the check list, and the consistency with the data created by the corporate tax application device 100 can be maintained.

  As described above, the checklist management method, the checklist management apparatus, the checklist management system, and the checklist management program according to the present invention are useful for a system for managing electronically created documents. It is suitable for generating and managing checklists necessary for checking the submitted documents.

It is a figure which shows the structural example of the computer system which is provided with the function as a check list management apparatus for implement | achieving the check list management method concerning this invention, and can execute the check list management program concerning this invention. It is a figure which shows the function structural example of a check list management apparatus. It is a figure which shows the structural example of a corporate tax application apparatus. It is a figure which shows the example of the content of the company basic information data of a company master apparatus. It is a figure which shows the example of corporate tax information data. It is a figure which shows the example of corporation prefectural tax information data. It is a figure which shows the example of corporation municipalities tax information. It is a flowchart which shows operation | movement of a check list management apparatus. It is a figure which shows the example of taking out linked data. It is a figure which shows the example of a screen display of the check list regarding a corporation prefectural tax. It is a figure which shows the example of a screen display of the check list regarding a corporation municipal inhabitant tax. It is a figure which shows the structural example of a statutory record application apparatus. It is a figure which shows the example of a display by a check list display part at the time of performing data linkage with a statutory record application apparatus. It is a figure which shows the structural example of a depreciation application apparatus. It is a figure which shows the example of a display by a check list display part at the time of performing data linkage with a depreciation application apparatus. It is a figure which shows the structural example of a year-end adjustment application apparatus. It is a figure which shows the example of a display by a check list display part at the time of performing data linkage with a year-end adjustment application apparatus.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Control part 2 Input part 3 Storage part 4 Disk part 5 Display part 6 CD-ROM drive 7 External I / F part 10 Check list management apparatus 11 Check list management control part 12 Company basic information input part 13 Company basic information storage part 14 Linked data I / F unit 15 Linked data storage unit 16 Check list generation unit 17 Check list format data 18 Check list storage unit 19 Check result input unit 20 Check result input data 21 Check list display unit 22, 110, 201 Company basic information data DESCRIPTION OF SYMBOLS 100 Corporate tax application apparatus 101 Corporate tax application control part 102 Company basic information input part 103 Corporate basic information storage part 104 Corporate tax information input part 105 Corporate tax information storage part 106 Corporate prefectural tax information input part 107 Corporate prefectural tax Information storage unit 08 Corporate municipal tax information input unit 109 Corporate municipal tax information storage unit 111 Corporate tax information data 112 Corporate prefectural tax information data 113 Corporate municipal tax information data 200 Company master device 300 Legal record application device 301 Control unit 302 Company Basic information input section 303 Salary income withholding slip input section 304 Retirement income withholding slip input section 305 Remuneration / fee payment record input section 306 Real estate usage payment payment input section 307 Compensation payment record input unit 308 Salary / reward payment record input unit such as non-resident salary 309 Company basic information storage unit 310 Salary income withholding slip storage unit 311 Retirement income withholding slip storage unit 312 Remuneration・ Storage unit for payment records such as charges 313 Storage unit for payment records such as usage fees for real estate 314 Storage unit for payment record of compensation for mobile property 315 Storage unit for salary and remuneration payment record for non-residents' salary 316 Company basic information data 317 Salary income withholding slip data 318 Retirement income withholding slip data 319 Remuneration / fees, etc. Payment record data 320 Real estate usage fee payment record data 321 Real estate consideration payment record data 322 Non-resident salary payroll / reward payment record data 400 Depreciation application device 401 Control unit 402 Company basic information input unit 403 Input section for depreciable asset declaration 404 Asset data input section 405 Input section for depreciable asset declaration 406 Company basic information storage section 407 Storage section for depreciable asset declaration submission 408 Asset data storage section 409 Depreciable asset declaration Storage section 410 company basic information data 411 412 Asset data 413 Depreciable asset declaration data 500 Year-end adjustment application device 501 Control unit 502 Company basic information input unit 503 Employee information input unit 504 Salary payment report input unit 505 Company basic information storage unit 506 Employee information storage unit 507 Submission Earlier municipalities storage section 508 Salary payment report storage section 509 Company basic information data 510 Employee information data 511 Submission destination municipal data 512 Salary payment report data

Claims (13)

Company basic information input department,
Company basic information storage unit for storing company basic information including collation data for identifying the company,
Interlocking data interface part,
Application data including collation data created by a financial or tax application and stored in the disk unit, and a linked data storage unit for storing predetermined linked data included in the application data,
Checklist generator,
A checklist storage unit for storing the generated checklist,
Check result input part,
A storage unit for storing the check results;
Display,
A checklist management apparatus comprising : a checklist management method for managing a checklist for performing a check at the time of submission of a document created by the financial or tax application,
The Company basic information input unit is inputted from the input unit, or by reading from the company basic information stored in the company master device data, said the company basic information to acquire the company basic information Company basic information storage stored in the parts, whereas, in the state where the company basic information has already been stored in the company basic information storage unit, and company basic information obtaining step of referring to the company basic information stored,
The linked data interface unit reads the application data from the disk unit, an application data reading step of storing the application data in the linked data storage unit,
The linked data interface unit reads the collation data included in the company basic information stored in the company basic information storage unit, reads the application data stored in the linked data storage unit, and from among the application data , every read verification data, takes out the linked data is the data of check items necessary for generating the checklist extraction linked data for storing linked data taken out the more the linked data storage unit together with the corresponding verification data step When,
The check list generation unit reads the checklist format data stored in advance disk unit reads the linked data stored before Symbol linked data storage unit, each of the linked data checklist format data read the generates a checklist by associating a data check items, the checklist generation step of storing the checklist to the check list storage unit,
The check result input unit accepts the input of the check results for each check item, and the check result input step of storing the check results for each the check item in the storage unit,
The display unit displays a check list stored in the check list storage unit, or a display step of displaying the check list and a check result stored in the storage unit;
A checklist management method comprising: According to said Company basic information obtaining step, and application data reading step, a step is taken out the linked data, and checklists generating step, a check result input step, a display step, characterized in that the repeatedly at a predetermined cycle execution Item 2. A checklist management method according to item 1. The company basic information is acquired by reading out company basic information data created in a company master device that manages company data and stored in a disk unit in the company basic information acquisition step. Or the checklist management method according to 2.   4. The checklist management method according to claim 1, wherein the collation data is a trade name code, a trade name, or a trade name code and a trade name. The financial or tax application is a corporate tax application, and the linked data includes the corporate tax amount and corporate tax document submission destination, the prefectural tax amount and prefectural tax document submission destination, and the business tax amount and business tax document. submission destination, checklists management method according to any one of claims 1 to 4, characterized in that a submission destination of the documents relating to municipal tax amount and municipal taxes.   The checklist according to any one of claims 1 to 4, wherein the financial or tax application is a statutory record application, and the linked data is the number of each document created by the statutory record application. Management method.   The financial or tax application is a depreciation application, and the linked data is a depreciable asset report submission destination and a taxable standard amount of the depreciable asset report. The checklist management method described.   The financial or tax application is an end-of-year adjustment application, and the linked data includes a payee report submission destination, a salary payment report submission number, and an employee name of the salary payment report. 5. The checklist management method according to any one of 4. A checklist management device for performing a check at the time of submission of a document created by a financial or tax application device,
A company basic information storage unit for storing company basic information including collation data for identifying the company;
The company basic information, input from the input unit, or reads from the company basic information stored in the company master device data, acquired by, that stores the acquired company basic information on the company basic information storage unit and the company basic information input unit,
Application data including collation data created in the financial or tax application and stored in the disk unit , and a linked data storage unit for storing predetermined linked data included in the application data ;
Reading the application data from the disk unit, and stores the application data in the linked data storage unit further reads the verification data contained in the company basic information stored in said company basic information storage unit, before Symbol interlocking read application data stored in the data storage unit, from among of the application data, for each the read verification data, takes out the linked data is the data of check items necessary for generating the checklist linked data fetched the Together with the corresponding collation data, the interlocking data interface unit for further storing in the interlocking data storage unit ,
A check list storage unit for storing the check list;
Rukoto previously read the checklist format data stored in the disk unit and the linked data stored in the linked data storage unit, associates the linked data as the check item data of the checklist format data and checklist generator which generates a check list, and stores the checklist to the check list storage unit by,
A storage unit for storing the check results;
Accepting an input of a check result of each check item, and the check result input unit for storing the check results for each the check item in the storage unit,
Displaying a check list stored in the check list storage unit or a display unit for displaying the check result stored in said check list and the storage unit,
A checklist management device comprising: The said company basic information input part acquires the said company basic information by reading the company basic information data created with the company master apparatus which manages company data, and preserve | saved at the disk part. The checklist management device described. The checklist management device according to claim 9,
Financial or tax application equipment;
A checklist management system characterized by comprising: The checklist management device according to claim 10;
Financial or tax application equipment;
A company master device that manages company data;
A checklist management system characterized by comprising:   A check list management program that causes a computer to execute the check list management method according to claim 1.

Images