JP2008234579A - Declaration preparation method, declaration preparation device, declaration preparation system and declaration preparation program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a declaration preparation method for keeping a tabulation method and a form consistent, by achieving reflection of financial data and carry-over processing by simple operation. <P>SOLUTION: This declaration preparation method makes a declaration based on the financial data created by the financial application, and includes a step of storing the financial data in a fiscal year database of a corresponding fiscal year by constructing the fiscal year database in a storage part, a step of writing the financial data of a fiscal year of a carry-over source and declaration data in the fiscal year database of the carry-over side, a step S2 of acquiring a tabulation condition, a step S5 of creating the declaration data by tabulating data by acquiring data of the fiscal year database based on the tabulation condition, and a step S15 of writing the created declaration data in the fiscal year database. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a report creation method for creating a report such as a corporate tax return, a report creation apparatus, a report creation system, and a report creation program. The present invention relates to a method for preparing a return for creating a new return based on the data.

  Conventionally, a tax return such as a corporate tax return (including documents attached to the tax return) has been created on a computer. When using the data created by various application systems (hereinafter referred to as financial application system) such as accounting system, sales management system, salary system, financial statement creation system, etc. The data that was created and managed by was used. The data managed by these financial application systems often includes items common between financial applications and items related to each other.

  Therefore, it is desirable to use data in conjunction with each other from the viewpoint of efficient data management and prevention of inconsistencies. As a technique for performing such interlocking, for example, there are techniques described in Patent Documents 1 to 4 below. In the following Patent Document 1, a technique for linking previously created report data is disclosed. Patent Document 2 below discloses a technique for creating a separate table in conjunction with a depreciation / asset management system in the preparation of a corporate tax / local tax return.

  Patent Document 3 below discloses a technique for generating an account item breakdown statement attached to a corporate tax return and a corporate business overview in conjunction with a financial accounting system. In Patent Document 4 below, a technique for linking data created by a plurality of systems related to an accounting system is disclosed.

  On the other hand, when creating a report, the creation efficiency of the report is improved by creating the office information, company address, etc. that are not changed by the year based on the report of the previous year. In this case, it is necessary to carry over the carry-over process to carry over the data of the report for the previous year. In general, however, the accounting data is carried over at the turn of the fiscal year, whereas the tax return is carried over when the next tax return is created. Therefore, there is usually a difference of six months to one year between the time when the tax return is carried forward and the time when the accounting data is carried forward.

  As the carry-over processing in the conventional report preparation technology, for example, a new report is created based on the report of the previous year by the following procedure. First, accounting data is carried forward at the turn of the previous year. Then, for example, it is assumed that the report data for the current period is created based on the report for the previous year six months to one year after the carry-over of the accounting data. For this purpose, first, the report for the previous year is selected as the carry-over source of the report data. Then, as the carry-over method, the next year carry-over process is selected.

  Then, the report for the current period (declared report) is selected as the carry-over destination of the report data. After that, specify the linkage source accounting data, and further specify the linkage method to instruct the start of linkage. Then, a tax return was prepared for the current term.

JP 2003-202996 A JP 2001-125969 A JP 2001-142959 A JP 2001-306776 A

  However, in the above conventional report creation technique, report data is created in advance and linked with accounting data, other report data, and the like. Also, accounting data and tax return data were managed for each application. For this reason, there is a problem that it takes time and effort to link existing accounting data and data with other report forms.

  In addition, in the above carry-over processing of the conventional report creation technology, when creating a report based on the data of the previous year, the carry-over time of accounting data differs from the carry-over time of the report data, and each carry-over process is independent. Need to do. For this reason, operation and processing became complicated, and further, there was a problem that data management for the previous year had to be performed separately.

  In order to solve the above problem, it is conceivable to manage all financial application data as a single database, but the database becomes enormous and difficult to implement in a small system. is there. In addition, because the data structure and output format are changed due to the revision of the tax system and laws, the contents of the aggregation process and the data contents are not the same in all years, so the consistency of the application period of the aggregation method, format, etc. There was a problem that was difficult.

  The present invention has been made in view of the above, and is capable of reflecting the contents of relevant financial data and carrying forward processing with a simple operation, and creating a report that can keep the tabulation method and format consistent. An object is to provide a method, a report creation device, a report creation system, and a report creation program.

  In order to solve the above-described problems and achieve the object, the report creation method according to the present invention holds the financial data generated by the financial application in the storage unit, and the report creation apparatus reports based on the financial data. A method for creating a report in a financial application system, in which a database management unit constructs a year database, which is a yearly database, in the storage unit, and generates financial data generated by the financial application In the year management step to be stored in the year database of the year to which the data belongs and the carry-over of the next year in the year database, the carry-over management department reads the financial data of the carry-forward source year from the storage part and reads the declaration data of the carry-over year. Write the read data to the year database for the year carried forward The fiscal year carry-over step, the aggregation condition setting unit of the declaration creation device, the aggregation condition acquisition step of acquiring the aggregation condition including the type of the declaration to be created and the aggregation period, and the aggregation interlocking unit of the declaration creation device, Based on the aggregation condition, a data acquisition instruction step for instructing the database management unit to acquire data of the year database or to aggregate the data of the year database, and the database management unit is instructed to acquire data from the aggregation interlocking unit. If there is, the data is read from the year database based on the instruction and returned to the aggregation interlocking unit. On the other hand, if there is an instruction for aggregation from the aggregation interlocking unit, the year database is based on the instruction. A database counting step of reading data from the database and returning the counting result to the counting interlocking unit; The accounting interlocking unit generates declaration data based on the data returned from the database management unit or the aggregated result, and the termination processing unit of the declaration generating device includes the generated declaration data And a declaration data registration step of writing in the annual database of the declaration year.

  The report creation method according to the next invention, the aggregation condition setting unit of the report creation device further acquires a creation method indicating whether to create a report based on the prepared report, A read step for reading and holding the created report data from the year database when it is determined that a report corresponding to the total condition has already been created in the storage unit, and corresponding to the total condition If it is determined that the tax return to be created has not been created, and the creation method specifies that a tax return should be created based on the tax return that has already been created, the The report data acquisition step that receives the selection of the declaration form to be selected and reads and holds the declaration data corresponding to the selected declaration form from the database of the year, and the creation corresponding to the aggregation condition A new empty report data is created and retained when it is determined that an elephant report has not been created and the creation method specifies that the report has not been created. And a data creation step, wherein the aggregation interlocking unit updates the held report data based on the data returned from the database management unit or the aggregation result.

  In the report preparation method according to the next invention, the termination processing unit further submits information indicating whether or not a report corresponding to the report data has already been submitted and writes the information in the storage unit in association with the report A completed information writing step, wherein the prepared report is used as a submitted report.

  The report preparation method according to the next invention is characterized in that the information can be changed.

  In the report creation method according to the next invention, the snapshot processing unit of the report creation apparatus starts the aggregation condition acquisition step and ends the report data registration step. Snapshot data storage step of reading financial data related to the tax return from the fiscal year database, generating a copy of the financial data, and storing the generated replica in the storage unit as snapshot data in association with the creation target report , Further included.

  In the report creation method according to the next invention, the snapshot processing unit calculates update identification information for obtaining update identification information for identifying whether or not financial data related to the creation target report is updated, and An update identification information storage step of storing the update identification information in the storage unit in association with the creation target declaration when the aggregation condition setting unit determines that the preparation target declaration has not been created; When the condition setting unit determines that the report to be created has already been created, the snapshot processing unit reads the update identification information from the storage unit and calculates the update identification information for each type of financial data. The update identification information obtained in the step is compared with the read update identification information, and snapshot data for financial data having different comparison results And snapshot data updating step of updating, and further comprising a.

  The report preparation method according to the next invention is characterized in that the update identification information is a Hash value.

  The method for preparing a report according to the next invention is characterized in that the types of the report include a final tax return, an intermediate report, and a revised report for a consumption tax return.

  The report preparation method according to the next invention is characterized in that a depreciable asset report is included as a type of the report.

  The method for preparing a report according to the next invention is characterized in that the types of the report include a final tax return, an interim return, a scheduled return, and a revised return as a local tax return.

  The next report preparation method according to the present invention is characterized in that the tax return includes a final tax return, an interim return, a scheduled return, and a revised return as a type of the return.

  The report preparation method according to the next invention is characterized in that the type of the report further includes an account item breakdown statement, a corporate business overview, and a company business overview.

  In the report creation apparatus according to the next invention, the database management unit constructs a year database, which is a yearly database, in the storage unit, and stores the financial data generated by the financial application in the year database of the year to which the data belongs. In a financial application system, a report creation apparatus for creating a report based on the financial data, a totaling condition setting unit for acquiring a totaling condition including a type of a declaration to be generated and a totaling period, and based on the totaling condition A totaling interlocking unit for instructing the database management unit to acquire data of the fiscal year database or totaling the data of the fiscal year database, and to generate report data based on the data returned from the database management unit or the aggregated result, and the generation The written declaration data is stored in the storage section. Characterized in that it comprises a termination processing unit for writing the annual database year, the.

  In the report creation device according to the next invention, the tabulation condition setting unit further acquires a creation method indicating whether or not to create a report based on the already created report, and stores the tabulation in the storage unit If it is determined that a report corresponding to the conditions has already been created, the created report data is read from the database for the year and held, and the report to be created corresponding to the aggregate condition has not been created. Judgment and if the creation method specifies to create a return based on the created return, accept the selection of the return based on the created return and select The tax return data corresponding to the completed tax return is read from the database of the year and retained, it is determined that the target tax return corresponding to the aggregation condition has not been created, and the creation method has been created If it is specified not to be based on the data, a new empty report data is created and retained, and the aggregation interlocking unit retains the data based on the data returned from the database management unit or the aggregation result. It is characterized by updating the report data.

  In the report creation device according to the next invention, the end processing unit writes information indicating whether or not a report corresponding to the report data has been submitted in association with the report in the storage unit The prepared report is used as a completed report.

  A report creation apparatus according to the next invention is characterized in that the information can be changed.

  A report creation apparatus according to the next invention reads financial data related to a report to be created from a year database, generates a copy of the financial data, and associates the generated copy with the report to be created and snaps it. A snapshot processing unit that stores the shot data in the storage unit as shot data is further provided.

  In the report creation apparatus according to the next invention, the snapshot processing unit obtains update identification information for identifying whether or not the financial data is updated for each type of financial data related to the creation target report, When the aggregation condition setting unit determines that the creation target report has not been created, the update identification information is stored in the storage unit as update identification information in association with the creation target report, and the snapshot When the processing unit determines that the creation target report has already been created by the aggregation condition setting unit, the processing unit reads update identification information from the storage unit, and the snapshot processing unit The obtained update identification information is compared with the read update identification information, and the snapshot data is updated for financial data having different comparison results. And features.

  The report creation apparatus according to the next invention is characterized in that the update identification information is a Hash value.

  The report creation apparatus according to the next invention is characterized in that the types of the report include a final tax return report, an intermediate report, and a revised report.

  The report creation apparatus according to the next invention is characterized in that the type of the report includes a depreciable asset report.

  The report preparation apparatus according to the next invention is characterized in that it includes a final tax return, an interim return, a scheduled return, and a revised return as a type of the return.

  The report creation apparatus according to the next invention is characterized in that the types of the report include a final tax return, an interim return, a scheduled return, and a revised return as a corporate tax return.

  The report preparation apparatus according to the next invention further includes an account item breakdown statement, a corporate business overview, and a company business overview.

  The tax return system according to the next invention is a database management unit that builds a fiscal year database, which is a fiscal unit database, in a storage unit, and stores financial data generated by the financial application in the fiscal year database to which the data belongs, In the report preparation apparatus according to any one of claims 11 to 20 and carry-over to the next year of the year database, the report data of the carry-forward year is read from the storage unit together with the financial data of the carry-forward year from the storage unit. A carry-over management unit that writes the read data into a year-to-date database of a carry-forward destination, and when the database management unit is instructed to acquire data from the report creation device, the Read data from the annual database and send it back to the report creation device. When instructed aggregated from adult device, characterized in that it returns the result of the counting to the preparation and filing device reads data from the year database based on the instruction.

  A report creation system according to the next invention is a report creation system comprising a server and a terminal connected to the server via a network, and creates a report based on financial data generated by a financial application device. The server includes a storage unit, and a database management unit that builds a fiscal year database, which is a yearly database, in the storage unit, and stores financial data generated by the financial application in a fiscal year database to which the data belongs, The database management unit reads data from the year database based on the instruction and sends it back to the terminal when there is an instruction to acquire data from the terminal. If there is an instruction, the data from the year database is based on the instruction. The result is read and returned to the terminal, and the terminal sends a totaling condition setting unit for acquiring a totaling condition including the type of report to be created and a totaling period to the database management unit based on the totaling condition. An aggregation interlocking unit for instructing acquisition of data in the year database or aggregation of data in the year database, and generating report data based on data returned from the database management unit or a result of aggregation, and the generated report data And an end processing unit for writing into the year database of the year of the report in the storage unit.

  In the declaration creation system according to the next invention, the aggregation condition setting unit further acquires a creation method indicating whether to create a declaration based on the already created declaration, and the aggregation is stored in the storage unit. If it is determined that a report corresponding to the conditions has already been created, the created report data is read from the database for the year and held, and the report to be created corresponding to the aggregate condition has not been created. Judgment and if the creation method specifies to create a return based on the created return, accept the selection of the return based on the created return and select The tax return data corresponding to the completed tax return is read from the database of the year and held, it is determined that the target tax return corresponding to the aggregation condition has not been created, and the creation method has been created. If it is specified not to be based on a report, a new empty report data is created and held, and the aggregation interlocking unit is based on the data returned from the database management unit or the aggregation result. The retained report data is updated.

  A report creation program according to the next invention is characterized by causing a computer to execute the report creation method according to any one of claims 1 to 12.

  The report creation method, the report creation apparatus, the report creation system, and the report creation program according to the present invention manage the financial data database on a yearly basis and automatically carry out the report data automatically at the time of carrying over to the next year. Since carrying over is carried out, the reflection of the contents of the related financial data and carrying over processing can be realized with a simple operation, and the effect of keeping the aggregation method and format consistent can be achieved.

  Hereinafter, embodiments of a report creation method, a report creation apparatus, a report creation system, and a report creation 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 shows the configuration of a computer system that has a function as a report creation apparatus for realizing the report creation method according to the first embodiment of the present invention and can execute the report creation program according to the embodiment of the present invention. It is a figure which shows an example. This computer system includes, for example, a control unit 1, an input unit 2, a storage unit 3, a display unit 4, a communication unit 5, and a printing unit 6, which are connected via a system bus 7.

  In FIG. 1, the control unit 1 executes a report creation 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 a storage device such as a hard disk, and stores programs to be executed by the control unit 1 and necessary data obtained in the course of processing. The storage unit 3 is also used as a temporary storage area for programs. The display unit 4 is composed of a CRT, LCD (liquid crystal display panel), etc., and displays various screens for the user of the computer system.

  Here, an example of the operation of the computer system until the report creation program according to the present invention becomes executable will be described. In the computer system having the above-described configuration, for example, a report creation program is installed in the storage unit 3 from a CD-ROM set in a CD-ROM drive (not shown). Then, when executing the report creation program, the report creation program read from the storage unit 3 is stored in a predetermined location of the storage unit 3. In this state, the control unit 1 executes the report creation process according to the program stored in the storage unit 3.

  In the present embodiment, a program in which the above-described report creation processing is described is provided using a CD-ROM as a recording medium. However, the present invention is not limited to this, depending 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.

  FIG. 2 is a block diagram illustrating a functional configuration example of the report creation apparatus according to the present embodiment. The report creation apparatus of the present embodiment includes a report creation unit 10 on the control unit 1, a database management unit 15 that manages a relational database, an input unit 2, a storage unit 3, a display unit 4, and a printing unit. 6. The report creation unit 10 includes a totaling condition setting unit 11, a totaling / interlocking unit 12, an editing unit 13, and an end processing unit 14. The database management unit 15 of the report creation apparatus of this embodiment is a common function of the entire computer system that manages the relational database.

  Here, the database of the present embodiment will be described. In the present embodiment, all data related to the creation of a report, including data created by other applications, are centrally managed as one database via the database management unit 15. In addition, it is assumed that the database of the present embodiment is written and held in the storage unit 3 on a yearly basis. The form and tabulation method of the tax return are changed with the revision of the tax system and laws, but there is a problem that the management becomes very complicated if data for different years are mixed. By holding in, the management of style and tabulation method is simplified. In order to hold the database on a year-by-year basis, for example, each financial application writes directly to the database for each year via the database management unit 15 when the database is generated. Alternatively, each financial application independently writes data to the storage unit 3, and the database management unit 15 reads out the data written to the storage unit 3, generates a database for each fiscal year, and holds it. Also good. In this embodiment, the index data is stored in the database via the database management unit 15. However, the present invention is not limited to this, and the index data may be stored in the storage unit 3 separately from the database.

  In general, the fiscal year indicates April 1 to March 31 of the following year. In this embodiment, the fiscal year indicates the business year of each company. Therefore, the fiscal year in the present embodiment is not limited to April 1 to March 31 of the following year, but is a period according to the date of settlement.

  Specifically, in the database of the present embodiment, for example, as shown in FIG. 2, accounting data (journal data, etc.), asset data, company information data, salary data, and the report creation unit 10 of the present embodiment An index table storing information about the created report data and the created report is stored. In the report creation unit 10 of the present embodiment, if the year in which the report is created is N, a database for N year (N year database) is used. Of these, accounting data (such as journal data), asset data, company information data, and salary data are data created by other financial applications. In addition, in the report preparation part 10, when there is no assumption that the report for the previous year or before is prepared, only the database for the current year may be stored in the storage part 3. For this reason, the data up to the previous year can be deleted or moved to another medium. When it is assumed that a report for the previous year or earlier is to be created, it is necessary to store in the storage unit 3 a database for the year that is expected to be created. In this embodiment, the index table is included in the database. However, the index table may be stored in the storage unit 3 separately from the database and read / written without going through the database management unit 15.

  FIG. 3 is a diagram illustrating a configuration example of the financial application system according to the present embodiment. In the example of FIG. 3, the financial application system manages the common items of the financial application and the journal data processing apparatus that inputs and corrects accounting data, the asset data processing apparatus that inputs and corrects asset data, and the like. Consists of a master management device, a financial statement creation device that creates financial statements using accounting data, etc., a salary management device that performs salary management, a report creation device, and a carry-over management device that performs database carry-over processing Is done. In FIG. 3, the journal data processing unit 21, the asset data processing unit 22, the master management unit 23, the financial statement creation unit 24, the salary management unit 25, the report creation unit 10, and the carry-over management unit 26 are each a journal data processing device. The control means on the control unit 1 of the asset data processing device, master management device, financial statement creation device, salary management device, report creation device, and carry-over management device is shown.

  For example, accounting data is generated by a journal data processing device, asset data is generated by an asset data processing device, company information data is generated by a master management device, and salary data is generated by a salary management device. Each of these devices (control means of the financial application device) refers to each data on the database created by each other. In addition, a device other than the device that first generated data may correct the data. The database management unit 15 manages the data related to each other in a consistent manner. The database management unit 15 can also perform simple calculation processing and search processing using data on the database.

  FIG. 4 is a diagram illustrating an example of items of company information data. FIG. 5 is a diagram showing an example of journal data items which are a part of the accounting data. As shown in FIG. 4, the company information data includes common information for each company that conducts financial management, such as company code, company name, address (or address), telephone number, representative (or representative name), and the like. It is out. As shown in FIG. 5, the journal data includes data of journal entry category, date, debit item, credit item, amount, and summary item. 4 and 5 are examples, the data items are not limited to this, and necessary items may be set according to the financial application system.

  In the present embodiment, in addition to the N-year report data, the previous-year report data ((N-1) -year report data) is also stored as the N-year database. In the present embodiment, the previous year report data is stored as a database for N years simultaneously with accounting data and the like by the carry-over management unit 26 when carrying over from the (N-1) year to the N year. . The carry-over process performed by the carry-over manager 26 will be described later. In this example, only the previous year's report data is described, but this is not limiting, and there should be any multiple years of report data such as the previous year or the previous year. Also good.

  In this example, accounting data (journal data, etc.), asset data, company information data, and salary data are given as examples of data generated by other devices. Further data to be linked or linked may be added. Further, it is not necessary to include all of these data, and for example, only journal data may be included.

  Next, the report creation process of this embodiment will be described. In the report preparation device of this embodiment, not only the declaration form but also the documents attached to the declaration form and related documents shall be prepared as declaration documents, and the documents to be created are collectively referred to as the declaration form. And For example, in this embodiment, a consumption tax return, a corporate tax return, and a depreciable asset return are set as the return types to be created in the return creation process. Each report type is further subdivided. For example, for consumption tax returns, it can be further classified into the types of returns such as final return, interim return (planned tax payment), intermediate return (provisional settlement), revised final return, and revised interim return (provisional settlement). Subdivided. For corporate income tax returns, the types of tax returns such as final tax return, interim tax return, scheduled tax return, amendment tax return, account breakdown statement, corporate business overview, etc., which are attached to the corporate tax return It is subdivided into. Since the depreciable asset declaration is not subdivided, the type is also depreciable asset declaration. In this embodiment, the corporate tax summary is not included in the corporate tax return, but the corporate business summary may also be created. Further, in this embodiment, the consumption tax return and the corporate tax return are described as examples. However, other tax returns such as a local tax return can also be implemented.

  FIG. 6 is a flowchart showing an example of a report creation process according to the present embodiment. As shown in FIG. 6, first, the report creation unit 10 of the present embodiment is activated by an operation of the input unit 2 by the operator, and the report creation process is started. When the report creation process is started, the aggregation condition setting unit 11 displays a screen for prompting the input of the type of report (type of report document) on the display unit 4, and the operator inputs from the input unit 2. Accept (step S1). FIG. 7 is a diagram showing an example of a report type input screen. FIG. 7 shows an example when a final tax return for a consumption tax return is selected, and an input reception screen that can be selected step by step. This input reception screen is an example, and any screen may be used as long as the report to be created by the report creation apparatus can be selected.

  Next, the totaling condition setting unit 11 displays a screen for prompting the input of the totaling condition on the display unit 4 according to the type of the report entered in step S1, and the input of the totaling condition by the operator from the input unit 2 is performed. Is received (step S2). The items of the totaling condition input at this time are a totaling period, a creation method (whether or not to create based on a submitted report), and a totaling condition for each type. The aggregation period and creation method are items that need to be specified depending on the type of return. The type-by-type aggregation condition is a condition necessary for creating the report document set for each report type. A screen that prompts the user to input these aggregation conditions is set in advance for each type of return.

  FIGS. 8A and 8B show an example of a screen for accepting input of aggregate conditions for the final tax return for consumption tax and the final tax return for corporate tax displayed in step S2. In the screen shown in Fig. 8-1, input is accepted for each item of aggregation period, declaration method, calculation method, tax processing of statement regarding purchase deduction tax amount, aggregation setting of subject statement, and correction of declaration / attachment table . In FIG. 8A, items other than the total period are the above-described type-specific total conditions.

  In the screen of FIG. 8-2, input is made for each item of creation method, creation condition, and creation method of depreciable assets. As a preparation method, select whether to create based on the submitted declaration (edit a copy of the submitted declaration) or not, and create based on the submitted declaration In addition, the user selects which report is to be created. At this time, the original report can be selected from among the submitted reports with reference to a report index table described later. These display screens and display items are merely examples, and any screen may be used as long as necessary conditions for preparing the report are input.

  Next, the tabulation condition setting unit 11 searches the index table in the storage unit 3 and determines whether or not the report data corresponding to the input report type and the tabulation period exists in the index table (step). S3). FIG. 9 is a diagram illustrating an example of the index table of the present embodiment. It is assumed that the index table is held in the storage unit 3 and only the item column is generated when the report creation apparatus is activated for the first time. As shown in FIG. 9, the index data includes an ID (IDentifier) for identifying the created report, the type of the report, the type of the report, and the counting period (counting start date, counting end date) ), And items such as data status indicating whether or not it has been submitted.

  Further, in the present embodiment, as described above, a report whose data state is “submitted” in the index table can be selected as a creation source on the creation method input screen in step S2. The reason that only the submitted report is created is that if data is created using a report that has not been submitted, uncorrected erroneous data may be included. For the data status item, “editing” is written when the ID is assigned for the first time, and it is changed to “submitted” when the report is submitted. The index data in the storage unit 3 is read and updated by the standard function of the control unit 1 or the like, thereby changing to submitted. For example, the index data is read from the storage unit 3 by an editor which is a standard function of the control unit 1, directly edited, and written again in the storage unit 3. Although the data states are “submitted” and “editing” here, the information indicating whether or not the data has been submitted is not limited to the flag, and any information may be used.

  If it is determined that there is a report corresponding to the type of the input report and the total period in the report index table (Yes in step S3), the total condition setting unit 11 further creates a creation method in step S2. It is determined whether or not an input has been made based on the submitted report (step S6a). If it is determined that the input has been made based on the submitted report (Yes in step S6a), the process proceeds to step S8. When it is determined that the input is made based on the submitted report (No in step S6a), the aggregation condition setting unit 11 stores the report data of the corresponding report via the database management unit 15 in the storage unit 3 Are stored in the storage unit 3 (step S4). Then, the aggregation / interaction unit 12 receives the type of the input report from the aggregation condition setting unit 11 and uses the target data on the N-year database used for the creation of the declaration (the interlock used for the creation of the declaration). Data and reference data), and the report data held in the storage unit 3 is updated and written in the primary use area of the storage unit 3 (step S5).

  Here, the aggregation in step S5 will be specifically described. First, the database management unit 15 modularizes common processes that are assumed to be used in other apparatuses of the financial application system for each aggregation condition. For the modularized processing, the totaling / interlocking unit 12 does not perform totalization, but the database management unit 15 totals and sends the result to the totaling / interlocking unit 12. Specifically, first, the aggregation / linkage unit 12 sends an acquisition instruction for target data or an instruction for a totaling condition for acquiring the aggregation result of the target data to the database management unit 15. The database management unit 15 reads the instructed target data and sends it to the tabulation / interlocking unit 12 when it is an instruction to acquire the target data. If the aggregation condition is an instruction for obtaining the aggregation result of the target data, the aggregation result is calculated by executing the module corresponding to the aggregation condition, and the aggregation result is calculated by the aggregation / linkage unit. 12 to send.

  The tabulation processing other than the common tabulation processing is performed by the tabulation / linkage unit 12 using the target data acquired from the database management unit 15 and the acquired tabulation result. The aggregation processing method (calculation formula for performing aggregation) of the aggregation / linkage unit 12 is determined in advance for each report and is held by the aggregation / linkage unit 12.

  For example, in the creation of the consumption tax return, “details of the top 10 purchase amounts” are calculated, and the database management unit 15 tabulates them. The aggregation / linkage unit 12 instructs the database management unit 15 to acquire “details of the top 10 purchase amounts”, and the database management unit 15 searches the accounting data in the N-year database and searches for the top 10 purchase amounts. Is collected and output to the tabulation / interlocking unit 12.

  It should be noted that the target data differs depending on the type of return, but the correspondence between the target data and the return type is assumed to be held by the tabulation / linkage unit 12. The correspondence between the target data and the report type is provided in a table in the storage unit 3, the correspondence between the target data and the report type is stored in the table, and the corresponding target data is obtained by referring to the table. You may do it.

  On the other hand, when it is determined that the report corresponding to the type of the input report and the total period does not exist in the report index table (No in step S3), the total condition setting unit 11 further performs step S2. It is determined whether or not an input is made based on the submitted report as a creation method (step S6). If it is determined that the input has been made based on the submitted report (No in step S6), empty report data (data for each item is blank with only item settings) is created and stored. 3 and assigns a new ID to the report data (step S7). Then, a record is added to the index data, and the assigned ID and the contents input in steps S1 and S2 are written, and the process proceeds to step S5. For the data state, “editing” is written.

  If it is determined that the input has been made based on the submitted report (Yes in Step S6), the data of the report selected as the original report in Step S2 is stored in the storage unit 3 via the database management unit 15. Is stored in the storage unit 3 (step 8), and the process proceeds to step S5.

  When step S5 ends, the editing unit 13 reads the report data created in step S5 from the storage unit 3, forms the read data into an editing format, and displays it on the display unit 4 (step S9). . Next, the editing unit 13 accepts input of editing content by an operation of the input unit 2 by an operator, and updates report data stored in the primary storage area of the storage unit 3 based on the input content ( Step S10).

  Next, the termination processing unit 14 displays a screen prompting selection of termination, condition change, recounting, or registration on the display unit 4 and accepts selection by an operation of the operator's input unit 2 (step S11). . When the end is selected (end of step S11), the end processing unit 14 further displays on the display unit 4 a screen prompting selection of “end after registration” or “end without registration”. The selection by the operation of the operator's input unit 2 is accepted (step S12). When “Register and end” is selected (Yes in step S12), the end processing unit 14 further displays on the display unit 4 a screen that prompts the user to select whether or not the submission has been completed. The selection by the operation of the input unit 2 is accepted (step S13). If it is selected that it has not been submitted (No at Step S13), the process proceeds to Step S15. When it is selected that it has been submitted (step S13 Yes), the data status column of the index data in the storage unit 3 corresponding to the registered report is updated to submitted (step S14). Then, the end processing unit 14 writes the report data stored in the primary storage area of the storage unit 3 into the database via the database management unit 15 (step S15).

  In addition, if “end without registration” is selected by the operator's operation of the input unit 2 in step S12 (No in step S12), the process ends as it is. In this example, step S12 and step S14 are separated, but these are combined into one, “Register and end”, “Exit without registration”, “Present”, and “Not submitted” These two sets of selections may be entered on a single screen.

  In step S11, if it is selected that registration is to be performed (registration in step S11), a screen prompting the user to select whether or not to submit is further displayed on the display unit 4, and the operator operates the input unit 2 The selection by is accepted (step S13a). If it is selected that the submission has not been made (No at Step S13a), the process proceeds to Step S15a. When it is selected that it has been submitted (step S13a Yes), the data status column of the index data in the storage unit 3 corresponding to the registered report is updated to submitted (step S14a). Then, the termination processing unit 14 writes the report data stored in the primary storage area of the storage unit 3 into the database via the database management unit 15 (step S15a). Then, returning to step S10, the processing after step S10 is performed again.

  In step S11, when it is selected that the aggregation condition is changed (condition change in step S11), the process returns to step S2 and the processes in and after step S2 are performed again. If it is selected that re-aggregation is performed (step S11 re-aggregation), the process returns to step S5 and the processes in and after step S5 are performed again.

  Although FIG. 6 does not describe the printing process, for example, in step S <b> 9, the termination processing unit 14 performs the printing execution in addition to selecting one of termination, condition change, recounting, and registration. The screen for accepting the instruction may be displayed, and the report data may be printed in a predetermined format when the operator is instructed to execute printing by operating the input unit 2. Further, the present invention is not limited to this, and printing may be executed in other steps.

  In this example, only the report that has been submitted is used as the original report. However, the present invention is not limited to this. Good. In this case, in step S2, instead of the submitted report, the original report may be selected from the prepared reports.

  Next, the carry-over management unit 26 of this embodiment will be described. FIG. 10 is a diagram illustrating a functional configuration example of the carry-over management unit 26 of the present embodiment. As illustrated in FIG. 10, the carry-over management unit 26 according to the present embodiment performs an input reception unit 31 that receives an input such as a carry-over type, a carry-over processing unit 32 that performs a carry-over process for the next year, and a re-carry-over process. And a re-carry processing unit 33.

  In the present embodiment, processing corresponding to two carry-overs of carry-over and re-carry-over in the next year is performed. The carry-over for the next year is, for example, carry-over processing that is performed when accounting data for the current year is input for the first time at the beginning of the fiscal year, or when financial processing for the next fiscal year is performed at the end of the fiscal year. As the contents of the process, all the data necessary for the N year out of the data for the N-1 year is carried over. For example, since the company information is not changed every year, the contents of the (N-1) year are copied as they are. For example, for accounting data, the balance at the end of (N-1) year is copied as the beginning balance of N year. It is decided in advance which data will be carried over.

  Such carry-forward processing for the next year has been performed in the conventional financial application, but only data necessary for the financial processing for the next year is generally copied. In this embodiment, not only the data necessary for financial processing in N year but also the (N-1) year report data created by the report creation system is used as the previous year report data in the N year database. Copy to. In this way, by including the previous year's tax return data in the N year database at the same time as carrying forward, the tax return is created based on the previous year's tax return data and the current year's tax return data. The operation can be unified between the case of performing and the operation becomes simple.

  On the other hand, the reversal process is a carry-forward process that is performed when the settlement process is finalized, such as by submitting a financial statement. It is processing. In this embodiment, the data to be rewritten by re-forwarding is accounting data, asset data, salary data, and previous year declaration data. The company information data is not a re-forwarding item because it is not changed by the re-forwarding process.

  The data to be carried forward again is not limited to this, and may be set appropriately according to the financial application system. For example, if there is an item in the company information data that may change due to re-forwarding, the company information data may be subject to re-forwarding.

  FIG. 11 is a flowchart illustrating an example of a carry-over process performed by the carry-over management unit 26 according to the present embodiment. First, the carry-over management unit 26 is activated by the operation of the operator. Then, as shown in FIG. 11, the input receiving unit 31 displays a screen that prompts input of the carry-over source database, and receives input from the operator input unit 2 (step S <b> 21).

  Next, the input receiving unit 31 displays a screen for prompting selection of whether to carry over the next year or to carry over again on the display unit 4, and receives an input by an operation by the input unit 2 of the operator (step S22). When the input acceptance unit 31 accepts the selection of carry-over for the next year (step S22, carry-over to the next year), the carry-in processing unit 32 instructs the carry-over processing unit 32 to carry over the next year. 1) Read data for the next year carry-over determined in advance from the year database and store it in the primary storage area of the storage unit 3 (step S23). Then, the carry-over processing unit 32 creates an N-year database via the database management unit 15 and writes the data held in the storage unit 3 to the N-year database (step S24).

  On the other hand, when the selection of re-forwarding is accepted (step S22, re-forwarding), the input receiving unit 31 displays a screen for prompting selection of the carry-over destination database on the display unit 4 and the operator's input unit 2 inputs the screen. Accept and instruct the re-carry processing unit 33 to perform re-carry (step S25). The re-forwarding processing unit 33 reads data other than the company information from the database specified in step S21 and holds it in the primary storage area of the storage unit 3 (step S26). Then, the re-forwarding processing unit 33 overwrites the data held in the storage unit 3 via the database management unit 15 on the corresponding part of the database selected in step S25 (step S27).

  Here, the carry-over management unit 26 has been described as a device control unit independent of the report creation unit 10. However, the present invention is not limited to this, and the report creation unit 10 and the carry-over management unit 26 are controlled by one device. You may integrate as a means. Then, it is only necessary to select whether to perform the report creation process or the carry-over process when the integrated apparatus is activated.

  In this embodiment, the database management unit 15 that performs common management is used to perform database management and common tabulation, but the database management unit 15 is included in the report creation unit 10. It may be included.

  As described above, in this embodiment, in the financial application system related to the report preparation, each device manages the generated financial data on a year-by-year basis. The N year database includes the (N-1) year report data (previous year report data) and carries it over. And in the report creation system, a new report can be created based on the report data including the previous year's report data. For this reason, in the report creation process, the reflection of the contents of the related financial data and the carry-over process can be realized with a simple operation. In addition, since yearly management is used, it is easy to match the counting methods and styles, and complicated style management can be eliminated.

  FIG. 12 is a block diagram illustrating a functional configuration example of the report creation unit 10a according to the second embodiment. The report creation unit 10a of the present embodiment operates on the same computer system as in FIG. The configuration example of the financial application system of the present embodiment is the same as that of the first embodiment except that the report creation unit 10 is replaced with the report creation unit 10a in FIG. As shown in FIG. 12, the report creation unit 10a of the present embodiment adds a snapshot processing unit 34 to the report creation unit 10 of FIG. 2, but otherwise creates the declaration form of the first embodiment. This is the same as the unit 10. Components having the same functions as those in the first embodiment are denoted by the same reference numerals and description thereof is omitted.

  The processing in this embodiment is the same as that in the first embodiment except for the snapshot processing. Only the parts different from the first embodiment will be described below.

  First, snapshot data of this embodiment will be described. For the snapshot data of this example, data (accounting data, etc.) related to the creation of the declaration on the database at the time when the declaration is created is saved for each type of declaration. Data. As described above, data on a database generated by another device such as accounting data is used when creating a report. On the other hand, accounting data and the like are updated daily, and it is not possible to confirm the accounting data itself based on a report created in the past. Therefore, when it is desired to refer to the original accounting data, it is necessary to save the data at that time. The snapshot data is data for that purpose. In this embodiment, data related to the creation of the declaration form is saved as snapshot data. However, in addition to this, the declaration form data of the declaration form may be saved. In this embodiment, the snapshot data and the hash value management table are stored in the database via the database management unit 15. However, the present invention is not limited to this, and may be stored in the storage unit 3 separately from the database. Good.

  In this embodiment, when the report creation process is started, the target data on the database at that time is copied and stored in the database as snapshot data. Snapshot data is stored for each created report. However, there is a possibility that the declaration creation process for creating one declaration may be performed over several days. If snapshot data is generated at the start of the process, it is generated each time the declaration creation process is performed. That is, a plurality of snapshot data are created for one report.

  For this reason, in this embodiment, whether or not the data related to the preparation of the report (hereinafter referred to as target data) has been updated from the data stored in the previous snapshot data in the same report. If it is determined that the snapshot data has not been updated, no new snapshot data is created. At the time when the snapshot is generated, the Hash value of the target data is calculated. And only the data of the classification from which the stored Hash value differs from the calculated Hash value are saved.

  Specifically, in this embodiment, the ID assigned to the created report and the hash value of the target data are stored in association with each other. This ID is the ID (ID stored in the index table) assigned in step S7 of the report creation process of FIG. 6 described in the first embodiment. FIG. 13 is a diagram illustrating an example of a hash value management table for managing target data and hash values for each ID. Thus, for each ID, a Hash value is stored for the target data corresponding to the ID.

  Further, in the case of large accounting data, the processing time for storing snapshot data can be shortened by generating a Hash value for each data divided every month. Furthermore, the data to be updated can be set in detail by subdividing the target data by month or category and storing the hash value for each. Thereby, unnecessary data in the target data can be reduced, so that the processing time can be shortened and the processing can be executed with less resources. In that case, in FIG. 13, you may add the column showing a month or a division.

  FIG. 14 is a flowchart illustrating an example of processing related to saving and updating of snapshot data according to the present embodiment. First, the snapshot processing unit 34 acquires the ID of the report input as a report creation process target from the total condition setting unit 11 (step S31). Specifically, after the report creation unit 10a is activated, the aggregation condition setting unit 11 performs the processing of steps S1 to S3 in FIG. 6 and when it is determined in step S3 that the report exists in the index table. The ID corresponding to the report stored in the index table is passed to the snapshot processing unit 34. If it is determined in step S3 that the report does not exist in the index table, the aggregation condition setting unit 11 passes the assigned ID to the snapshot processing unit 34 after assigning the ID in step S7.

  Next, the snapshot processing unit 34 calculates a Hash value for each of the target data corresponding to the type of report based on the type of report corresponding to the ID (step 32). It is assumed that the snapshot processing unit 34 holds the correspondence between the type of report and the target data. For example, in the report creation processing of the final tax return for the consumption tax return, when aggregation is performed using accounting data and company information data, these two are the target data.

  Next, the snapshot processing unit 34 searches the Hash value management table stored in the storage unit 3, and data with an ID that matches the ID acquired from the aggregation condition setting unit 11 (hereinafter referred to as a selection ID) is found. It is determined whether or not it exists (step S33). If it is determined that there is data with a matching ID (Yes in step S33), the snapshot processing unit 34 reads all the data corresponding to the selected ID from the Hash value management table. It is determined whether or not the Hash value is the same as the Hash value of the target data calculated in Step S32 (Step S34). When it is determined that it is not the same as the Hash value calculated in step S32 (No in step S34), the snapshot processing unit 34 updates the snapshot data of the target data (step S35). Specifically, the snapshot processing unit 34 reads the target data on the database via the database management unit 15, creates a replica, and writes it as snapshot data to the database via the database management unit 15. Then, the Hash value column of the target data of the selection ID in the Hash value management table of the storage unit 3 is updated to the value calculated in Step S32 (Step S36).

  Next, when the processing of step S34 to step S36 is performed for all target data corresponding to the selection ID, the processing ends, and the target of the target data corresponding to the selection ID that has not been processed. If data remains, the process returns to step S34. At this time, the processing of step S34 to step S36 is performed on the target data that has not been processed instead of the first target data (step S37).

  If it is determined in step S34 that the Hash value of the target data calculated in step S32 is the same (Yes in step S34), the process proceeds to step S37.

  If it is determined in step S33 that there is no data with a matching ID (No in step S33), snapshot data of all target data corresponding to the selected ID is stored (step S38). Specifically, the snapshot processing unit 34 reads all target data corresponding to the selected ID on the database via the database management unit 15, creates a copy, and stores it as snapshot data in the database via the database management unit 15. Write.

  Next, the snapshot processing unit 34 registers the data corresponding to the selection ID in the hash value management table on the database via the database management unit 15 (step S39). Specifically, the snapshot processing unit 34 adds a new record to the Hash value management table in the database via the database management unit 15, and corresponds to the selection ID in the ID column and the ID in the target data column. In the Hash value column, the Hash value for each target data calculated in step S32 is written.

  In this embodiment, the hash value is calculated for each target data and it is determined whether or not it has been updated. However, some of the target data (for example, accounting data and asset data) is combined. One target data classification may be used, a hash value may be generated for each classification, and it may be determined whether or not it has been updated in that classification unit. If classifications that are likely to be updated at the same time are classified into the same classification, the number of hash values to be calculated can be reduced and the processing time can be reduced.

  In this embodiment, the hash value is calculated to determine whether or not the target data is updated. However, the present invention is not limited to this. For example, a method that can determine the update such as using a time stamp of the target data. Any method may be used for determination.

  In this embodiment, the snapshot data and the hash value management table are stored in the database via the database management unit 15. However, the present invention is not limited to this, and may be stored in the storage unit 3 separately from the database. Good.

  As described above, in this embodiment, in addition to the processing similar to that in the first embodiment, for each report, data related to the preparation of the report at the time when the report is generated is stored as snapshot data. did. In addition, only one set of target data is saved for one report, and when the same tax form is processed for the same report for the second time or more, the previous snapshot data and update are updated. Only the snapshot data of the target data was updated. For this reason, in addition to the effects of the first embodiment, it is possible to correctly refer to related data such as accounting data at the time of creating the report.

  FIG. 15 is a diagram illustrating a configuration example of a report creation system according to the third embodiment. As shown in FIG. 15, in the present embodiment, a server 41 that is a computer system that holds a database, and WS (workstations) 42-1 to 42- that are computer systems (terminals) that perform a report creation process. 6 is configured. Components having the same functions as those in the first embodiment or the second embodiment are denoted by the same reference numerals and description thereof is omitted.

  FIG. 16 is a diagram illustrating a functional configuration example of the server 41 and the WSs 42-1 to 42-6 constituting the report creation system of the present embodiment. WSs 42-1 to 42-6 of the present embodiment are the same as the computer system shown in FIG. Each of the WSs 42-1 to 42-6 has a configuration obtained by removing the N-year database, index data, and snapshot data stored in the database management unit 15 and the storage unit 3 from the computer system according to the second embodiment. . Further, other financial applications share the same functions, and each financial application writes the generated data in the storage unit 3a of the server 41 via the network instead of the storage unit 3.

  The server 41 is a computer system including a control unit 1a, a storage unit 3a, and a communication unit 5a. In the server 41, the database management unit 15 manages the N-year database in the storage unit 3a. The function of the database management unit 15 is the same as that of the database management unit 15 of the first embodiment or the second embodiment except that it receives an instruction from the communication unit 5a instead of receiving an instruction from the aggregation / interlocking unit 12. The N-year database on the storage unit 3a is the same as the N-year database on the storage unit 3 of the first or second embodiment. The communication units 5 of the WSs 42-1 to 42-6 and the communication unit 5a of the server 41 are connected to the same LAN (Local Area Network) or a network such as the Internet.

  Hereinafter, only parts different from the first embodiment or the second embodiment will be described. First, the report creation process of the present embodiment will be described. The report creation process of the present embodiment includes the operations via the database management unit 15 and the operations (search, write, etc.) for the index data in the flowchart shown in FIG. Or via the Internet and the communication part 5a. Further, instead of the N year database and index data in the storage unit 3, the N year database and index data in the storage unit 3a are used. For example, in the process of step S4 in FIG. 6, the tabulation condition setting unit 11 reads report data from the N-year database in the storage unit 3a via the communication unit 5, the network, the communication unit 5a, and the database management unit 15. Other processes are the same as those in the first embodiment.

  As with the report creation process, the WS 42-1 to 42-6 are also provided for the carry-over management unit 26 of the present embodiment. In the carry-over processing shown in FIG. 11 of the first embodiment, the operation via the database management unit 15 is assumed to be via the communication unit 5, the network, and the communication unit 5a. Other processes are the same as those in the first embodiment.

  Further, the processing related to saving and updating snapshot data according to the present embodiment is the same as the processing described with reference to FIG. , Via the communication unit 5a. The other processes are the same as those in the second embodiment.

  In the present embodiment, the WS 42-1 to 42-6 are provided with the function of the report creation unit 10a described in the second embodiment. However, the present invention is not limited to this, and the WS 42-1 to 42-6 are provided. You may make it give the function of the report preparation part 10 of Example 1. FIG. The report creation process and carry-over process in this case are the same as in the present embodiment.

  In the example of FIG. 16, a single server 41 is used. However, a plurality of servers having the same configuration may hold the same yearly database replica. In this case, operation is possible even if the server fails, and durability can be improved. In addition, data may be distributed by dividing a server that holds a database for each year, for example, for each year or for each type of financial data. In this case, the load on the server can be distributed.

  As described above, in this embodiment, the server 41 holds a database for storing financial data, and the WSs 42-1 to 42-6 having the function of a report creation apparatus access the server via the network and return the report. Was created. For this reason, the plurality of WSs 42-1 to 42-6 can create a report using the same data.

  As described above, the report creation method, the report creation apparatus, the report creation system, and the report creation program according to the present invention use the data created by other financial applications to create a report. It is useful for an application system, and is particularly suitable for a financial application system that creates a new report based on a prepared report and the latest financial data.

It is a figure which shows the structural example of the computer system which has the function as a report preparation apparatus for implement | achieving the report preparation method of Example 1, and can execute the report preparation program of the Example concerning this invention. It is a block diagram which shows the function structural example of the report creation apparatus of Example 1. FIG. It is a figure which shows the structural example of a financial application system. It is a figure which shows an example of the item of company information data. It is a figure which shows an example of the item of journal data. It is a flowchart which shows an example of a report preparation process. It is a figure which shows an example of the input screen of the kind of report. It is a figure which shows an example of the input reception screen of the total condition of the final income tax return of a consumption tax return. It is a figure which shows an example of the input reception screen of the total condition of the final income tax return of a corporate tax return. It is a figure which shows an example of an index table. It is a figure which shows the function structural example of a carry-over management part. It is a flowchart which shows an example of a carry-over process. It is a block diagram which shows the function structural example of the report preparation apparatus of Example 2. FIG. It is a figure which shows an example of a Hash value management table. It is a flowchart which shows an example of the process regarding preservation | save and update of snapshot data. It is a figure which shows the structural example of the report preparation system of Example 3. FIG. It is a figure which shows the function structural example of a server and WS.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1,1a Control part 2 Input part 3, 3a Storage part 4 Display part 5, 5a Communication part 6 Printing part 7 System bus 10 Declaration document creation part 11 Totaling condition setting part 12 Totaling / interlocking part 13 Editing part 14 End processing part 15 Database management unit 21 Journal data processing unit 22 Asset data processing unit 23 Master management unit 24 Financial statement creation unit 25 Salary management unit 26 Carry-over management unit 31 Input reception unit 32 Carry-over processing unit 33 Re-carry-over processing unit 34 Snapshot processing unit

Claims (28)

A financial statement creation method in a financial application system, in which financial data generated by a financial application is stored in a storage unit, and a declaration creation device creates a declaration based on the financial data,
A database management unit constructs a year database, which is a yearly database, in the storage unit, and stores financial data generated by the financial application in the year database of the year to which the data belongs,
In the next year's carry-over of the year database, the carry-over management section reads the financial data of the carry-forward source year together with the financial data of the carry-forward year from the storage section, and stores the read data in the year database of the carry-forward year. The next year carry-forward step to write, and
A totaling condition acquisition step in which the totaling condition setting unit of the report preparation device acquires a totaling condition including a type and a totaling period of the report to be created;
A data acquisition instruction step for instructing the database management unit to acquire data of the year database or total data of the year database based on the aggregation condition, the aggregation interlocking unit of the report creation device,
When the database management unit is instructed to acquire data from the aggregation interlocking unit, the database management unit reads data from the year database based on the instruction and returns the data to the aggregation interlocking unit. When there is an instruction, a database aggregation step of reading data from the year database based on the instruction and returning the aggregation result to the aggregation interlocking unit;
The summary interlocking unit generates a declaration data based on data returned from the database management unit or a summary result;
A completion data processing unit of the declaration preparation device, a declaration data registration step of writing the generated declaration data in a year database of the declaration year,
A method for preparing a return, characterized by including: The tabulation condition setting unit of the report creation device,
In addition, a creation method that indicates whether to create a return based on the completed return,
Further, when it is determined that a report corresponding to the totaling condition has already been created in the storage unit, a read step of reading and holding the created report data from the year database,
If it is determined that the report to be created corresponding to the aggregation condition has not been created, and the creation method specifies that a report should be created based on the created report, A declaration data acquisition step of accepting selection of a declaration based on the declaration and reading and holding the declaration data corresponding to the selected declaration from the year database;
When it is determined that the report to be created corresponding to the aggregation condition has not been created, and the creation method specifies that the created report is not based on the created report, new empty report data A new data creation step to create and hold
Run
The aggregation interlocking unit
2. The report creation method according to claim 1, wherein the held report data is updated based on data returned from the database management unit or a total result. Submitted information writing step in which the end processing unit further writes information indicating whether or not a report corresponding to the report data has been submitted to the storage unit in association with the report,
Including
3. The method for preparing a report according to claim 1, wherein the prepared report is used as a completed report.   4. The method for preparing a report according to claim 3, wherein the information is changeable. From the fiscal year database, the snapshot processing unit of the report creation device receives the financial data related to the report to be created from the start of the aggregation condition acquisition step to the end of the report data registration step. A snapshot data storage step of reading, generating a copy of the financial data, and storing the generated copy in the storage unit as snapshot data in association with the creation target report;
The method for creating a report according to any one of claims 1 to 4, further comprising: An update identification information calculation step for obtaining update identification information for identifying whether or not the financial data related to the creation target report is updated by the snapshot processing unit;
An update identification information storage step of storing the update identification information in the storage unit in association with the creation target report when the aggregation condition setting unit determines that the creation target report has not been created;
When it is determined by the aggregation condition setting unit that the creation target report has already been created, a snapshot processing unit reads the update identification information from the storage unit, and the update identification for each type of financial data A snapshot data update step of comparing the update identification information obtained in the information calculation step with the read update identification information, and updating the snapshot data for the financial data having different comparison results;
The method according to claim 5, further comprising:   7. The report creation method according to claim 6, wherein the update identification information is a hash value.   The tax return preparation method according to any one of claims 1 to 7, wherein the tax return includes a final tax return, an interim tax return, and a revised tax return as consumption tax returns.   9. The method for preparing a report according to claim 1, wherein the type of the report includes a depreciable asset report.   The tax return preparation method according to any one of claims 1 to 9, wherein the tax return includes a final tax return, an interim return, a scheduled return, and a revised return for a local tax return.   The tax return preparation method according to any one of claims 1 to 10, wherein the tax return includes a final tax return, an interim return, a scheduled return, and a revised return for a corporate tax return .   12. The method for creating a report according to claim 11, wherein the type of the report further includes an account item breakdown statement, a corporate business overview, and a company business overview. In the financial application system in which the database management department builds a fiscal year database, which is a yearly database, in the storage part, and stores the financial data generated by the financial application in the fiscal year database to which the data belongs, filing based on the financial data A report creation device for creating a certificate,
The aggregation condition setting section to obtain the aggregation condition including the type of report to be created and the aggregation period;
Aggregation interlocking that instructs the database management unit to acquire data of the year database or totals data of the year database based on the aggregation condition, and generates report data based on the data returned from the database management unit or the aggregation result And
A termination processing unit for writing the generated report data into the year database of the year of the report in the storage unit;
A report preparation apparatus characterized by comprising: The aggregation condition setting unit
In addition, a creation method that indicates whether to create a return based on the completed return,
When it is determined that a report corresponding to the aggregation condition has already been created in the storage unit, the created report data is read from the year database and held,
If it is determined that the report to be created corresponding to the aggregation condition has not been created, and the creation method specifies that a report should be created based on the created report, Accept the selection of the original declaration from the declarations, read the declaration data corresponding to the selected declaration from the database for the year, and hold it,
When it is determined that the report to be created corresponding to the aggregation condition has not been created, and the creation method specifies that the created report is not based on the created report, new empty report data Create and hold
The aggregation interlocking unit
14. The report creation apparatus according to claim 13, wherein the retained report data is updated based on data returned from the database management unit or a total result. The termination processing unit writes information indicating whether or not a report corresponding to the report data has been submitted, and writes it in the storage unit in association with the report,
15. The report creation apparatus according to claim 13 or 14, wherein the created report is a submitted report.   16. The report creation apparatus according to claim 15, wherein the information can be changed. Snapshot that reads financial data related to the report to be created from the annual database, generates a copy of the financial data, and stores the generated copy in the storage unit as snapshot data in association with the report to be created Processing section,
The report creation device according to claim 13, further comprising: The snapshot processing unit obtains update identification information for identifying the presence or absence of update of the financial data for each type of financial data related to the creation target report,
When the aggregation condition setting unit determines that the creation target report has not been created, stores the update identification information in the storage unit as update identification information in association with the creation target report,
The snapshot processing unit reads the update identification information from the storage unit when the summary condition setting unit determines that the creation target report has already been created, and stores the snapshot for each type of financial data. 18. The report creation apparatus according to claim 17, wherein the update identification information obtained by the processing unit is compared with the read update identification information, and the snapshot data is updated for the financial data having different comparison results.   19. The report creation apparatus according to claim 18, wherein the update identification information is a Hash value.   20. The tax return creation apparatus according to claim 13, wherein the tax return type includes a final tax return, an interim tax return, and a revised tax return for a consumption tax return.   21. The report creation apparatus according to claim 13, wherein the type of the report includes a depreciable asset report.   22. The tax return creation apparatus according to any one of claims 13 to 21, wherein the tax return type includes a final tax return, an interim tax return, a scheduled tax return, and a revised tax return for a local tax return.   23. The tax return creation apparatus according to claim 13, wherein the tax return type includes a final tax return, an interim tax return, a scheduled tax return, and a revised tax return for a corporate tax return. .   24. The report creation apparatus according to claim 23, wherein the type of report further includes an account item breakdown statement, a corporate business overview, and a company business overview. A database management unit that builds a year database, which is a yearly database, in the storage unit, and stores the financial data generated by the financial application in the year database of the year to which the data belongs,
The report preparation device according to any one of claims 13 to 24;
In the carry-over of the next year of the year database, a carry-over management unit that reads from the storage unit the financial data of the year carried forward together with the financial data of the year carried forward and writes the read data into the year database of the year carried forward ,
With
When there is an instruction to acquire data from the report creation device, the database management unit reads data from the year database based on the instruction and sends it back to the report creation device. When there is a totaling instruction from the apparatus, the report creation system is characterized in that data is read from the year database based on the instruction and the totalization result is returned to the report creation apparatus. A report creation system comprising a server and a terminal connected to the server via a network and creating a report based on financial data generated by a financial application device,
The server
A storage unit;
A database management unit that builds a year database, which is a database for each year, in the storage unit, and stores the financial data generated by the financial application in the year database of the year to which the data belongs;
With
When there is an instruction for data acquisition from the terminal, the database management unit reads out data from the year database based on the instruction and sends it back to the terminal, while there is an instruction for aggregation from the terminal. In this case, the data is read from the year database based on the instruction and the counting result is returned to the terminal.
The terminal
The aggregation condition setting section to obtain the aggregation condition including the type of report to be created and the aggregation period;
Aggregation for instructing the database management unit to acquire data of the year database or totaling data of the year database based on the aggregation condition, and to generate report data based on the data returned from the database management unit or the aggregation result Interlocking part,
A termination processing unit for writing the generated report data into the year database of the year of the report in the storage unit;
A report creation system characterized by comprising: The aggregation condition setting unit
In addition, a creation method that indicates whether or not to create a return based on the completed return is obtained,
When it is determined that a report corresponding to the aggregation condition has already been created in the storage unit, the created report data is read from the year database and held,
If it is determined that the report to be created corresponding to the aggregation condition has not been created, and the creation method specifies that a report should be created based on the created report, Accept the selection of the original declaration from the declarations, read the declaration data corresponding to the selected declaration from the database for the year, and hold it,
When it is determined that the report to be created corresponding to the aggregation condition has not been created, and the creation method specifies that the created report is not based on the created report, new empty report data Create and hold
The aggregation interlocking unit
27. The report creation system according to claim 26, wherein the held report data is updated based on data returned from the database management unit or a total result.   A program for creating a report, which causes a computer to execute the report creation method according to any one of claims 1 to 12.

Images