JP6731743B2 - Transaction statement information management device, transaction statement information management method, and transaction statement information management program - Google Patents

Description

The present invention relates to a transaction statement information management device, a transaction statement information management method, and a transaction statement information management program.

Patent Document 1 discloses a system for clearing processing that includes transaction detail registration means for registering data including an account number, a date, and a transfer amount (deposit amount) as one record in a transaction detail table. (See claim 1 and paragraph 0018). In the system described in Patent Document 1, when the record registered in the transaction detail table corresponds to the record registered in the billing data table, the record registered in the transaction detail table has a billing number or a payment number. It is configured to add a collation key and perform the erasing process based on this collation key.

JP, 2014-59667, A

However, the system described in Patent Document 1 can handle only records related to bank transactions. Further, in the system described in Patent Document 1, one collation key (for example, a different billing number for each record) is added to one record (see paragraph 0041), so that the erase process corresponds to one record. Can be performed only for each line, and a plurality of lines or a plurality of records cannot be collectively managed. As described above, with the conventional technology, it is possible to perform processing specialized for a single transaction, but it is necessary to aggregate all records again in order to perform analysis from a multifaceted and detailed financial accounting perspective. there were.

The present invention has been made in view of the above problems, and a transaction statement information management device, a transaction statement information management method, and a transaction that can facilitate aggregation from various and detailed financial accounting viewpoints. The purpose is to provide a detailed information management program.

In order to solve the above-mentioned problems and achieve an object, a transaction statement information management device according to the present invention includes a transaction statement including a control unit for managing information on transaction statements to be described in a transaction statement. In the information management device, the control unit includes management journal information setting means for performing a setting for associating the original transaction information of the financial accounting journal with the management journal information for journalizing the original transaction information for management accounting. It is characterized by having.

Also, in the transaction statement information management device according to the present invention, in the transaction statement information management device described above, the control unit fetches information corresponding to the management journal information from the original transaction information, and manages the account. It is characterized by comprising a transaction statement creating means for creating transaction statement data for journal entry.

In the transaction statement information management device according to the present invention, in the transaction statement information management device described above, the management journal information is financial management journal information for journalizing the original transaction information for the financial accounting journal. In addition, the transaction statement creating means may use the management journal information to create transaction statement data created from the original transaction information, the breakdown of which is in the financial accounting journal. Characterize.

In the transaction statement information management device according to the present invention, in the transaction statement information management device described above, the control unit includes a presentation unit that presents a list of management journal classification candidates that can be set as the management journal information. It is characterized by being provided.

A transaction statement information management method according to the present invention is a transaction statement information management method for managing information on transaction statements to be described in a transaction statement, which is executed in an information processing device including a control unit. And including a management journal information setting step, which is executed in the control unit, for making a setting for associating the original transaction information of the financial accounting journal with the management journal information for journalizing the original transaction information for management accounting. Is characterized by.

Further, the transaction statement information management program according to the present invention is a transaction statement information management program for managing information on transaction statements to be described in a transaction statement, which is executed by an information processing apparatus including a control unit. Therefore, there is a management journal information setting step for performing a setting for associating the original transaction information of the financial accounting journal with the management journal information for journalizing the original transaction information for management accounting, which is executed by the control unit. It is characterized by including.

According to the present invention, management journal information is added to original transaction information before financial accounting journal entry. As a result, the present invention has the effect of facilitating the aggregation from various and detailed financial accounting viewpoints.

FIG. 1 is a block diagram showing an example of the configuration of a transaction statement information management system including a transaction statement information management device. FIG. 2 is a diagram schematically and exemplarily showing a data flow in the transaction statement information management system 1000 of FIG. FIG. 3 is a diagram exemplifying details of the data flow in FIG. FIG. 4 is a flowchart showing a processing procedure of transaction detail information management processing executed in transaction detail information management system 1000 in FIG. FIG. 5 is a flowchart showing a processing procedure of a subroutine of the processing of step S410 of FIG. FIG. 6 is a diagram schematically showing an example of determining a list of journal category candidates to be presented in step S412 of FIG. FIG. 7 is a diagram showing an example of a display screen displayed when allocating the journal classifications for management accounting journals when the list of journal classification candidates described with reference to FIG. 6 is determined. FIG. 8 is a flowchart showing a processing procedure of a subroutine of the processing of step S450 of FIG. FIG. 9 is a diagram for schematically explaining the original transaction information relating to the transaction statement creation created by the processing of FIG. 8 (FIG. 9A is the original transaction information extracted in step S452 of FIG. 8). 9(b) is an example of transaction statement data in a long format created from the original transaction information of FIG. 9(a), and FIG. 9(c) is a long statement of FIG. 9(b). An example of the transaction details when the data of the transaction details in the format is changed to the short format). FIG. 10-1 is a diagram schematically showing an example of a group of original transaction information which is the target of the process of step S450 of FIG. FIG. 10-2 is a diagram schematically showing an example of a part of a long-format transaction statement created from the group of original transaction information shown in FIG. 10-1. FIG. 10-3 is a diagram schematically showing an example in which the transaction details in the long format shown in FIG. 10-2 are changed to the short format. FIG. 11 is a diagram showing an example of an income statement prepared from the transaction details shown in FIG. 10-3. FIG. 12-1 is a diagram schematically showing an example of transaction detail data created in step S450 of FIG. FIG. 12-2 is a diagram showing a first example of an income statement for management journals that can be created using the transaction statement data shown in FIG. 12-1. FIG. 12-3 is a diagram showing a second example of a profit and loss statement for management journals that can be created using the transaction statement data shown in FIG. 12-1. FIG. 12-4 is a diagram showing a third example of an income statement for management journals that can be created using the transaction statement data shown in FIG. 12-1. FIG. 13 is a diagram showing an example of a regional sales analysis table that can be created by the processing of FIG. FIG. 14 is a diagram showing an example of a customer-specific profit and loss analysis table that can be created by the processing of FIG. FIG. 15 is a diagram showing an example of a transaction statement creation image. FIG. 16 is a diagram showing an example of the entire transaction statement information management system. FIG. 17 is a diagram showing an outline of the transaction statement information management system. FIG. 18 is a diagram showing an example of the mechanism of the transaction statement DB. FIG. 19 is a diagram showing an example of an item mapping image regarding transaction detail data. FIG. 20 is a diagram showing an example of the cooperation image. FIG. 21 is a diagram showing an example of the cooperation image. FIG. 22 is a diagram showing an operation example. FIG. 23 is a diagram showing an operation example. FIG. 24 is a diagram showing an operation example. FIG. 25-1 is a diagram illustrating an example of a mapping image. 25-2 is a figure which shows an example of a mapping image. FIG. 26 is a diagram showing an example of a processing flow relating to general-purpose journal external import. FIG. 27 is a diagram illustrating an example of a processing flow relating to financial journal entry. FIG. 28 is a diagram showing an example of the transaction statement data creation processing screen. FIG. 29 is a diagram showing an example of a transaction statement cooperation API (application programming interface). FIG. 30 is a diagram illustrating an example of a processing flow relating to transaction detail creation. FIG. 31 is a diagram showing an example of a function list of the transaction statement information management system. 32-1 is a diagram illustrating an example of the transaction statement update work update process. 32-2 is a diagram illustrating an example of the transaction statement update work update process. 32-3 is a diagram illustrating an example of the transaction statement update work update process. FIG. 32-4 is a diagram illustrating an example of the transaction statement update work update process. FIG. 32-5 is a diagram of an example of the transaction statement update work update process. FIG. 32-6 is a diagram illustrating an example of the transaction statement update work update process. FIG. 32-7 is a diagram illustrating an example of the transaction statement update work update process. FIG. 33 is a diagram illustrating an example of a foreign currency cooperation journal entry history. FIG. 34 is a diagram illustrating an example of the transaction statement cooperation API. FIG. 35 is a diagram showing an example of object arrangement in creating transaction details. FIG. 36 is a diagram illustrating an example of a processing flow relating to transaction detail creation. FIG. 37 is a diagram showing an example of a function list of the transaction statement information management system. FIG. 38-1 is a diagram illustrating an example of the transaction statement update work update process. FIG. 38-2 is a diagram illustrating an example of the transaction statement update work update process. 38-3 is a figure which shows an example of a transaction statement update work update process. FIG. 38-4 is a diagram illustrating an example of transaction detail update work update processing. FIG. 38-5 is a diagram of an example of the transaction statement update work update process. FIG. 38-6 is a diagram of an example of the transaction statement update work update process. FIG. 38-7 is a diagram of an example of the transaction statement update work update process. FIG. 38-8 is a diagram illustrating an example of the transaction statement update work update process. FIG. 39 is a diagram showing an example of a table list in the transaction statement information management system. FIG. 40-1 is a diagram showing an example of transaction detail data. FIG. 40-2 is a diagram showing an example of transaction detail data. 40-3 is a figure which shows an example of transaction detailed data. FIG. 40-4 is a diagram showing an example of transaction detail data. FIG. 40-5 is a diagram showing an example of transaction detail data. FIG. 41-1 is a diagram showing an example of transaction detail attached information data. FIG. 41-2 is a diagram showing an example of transaction detail attached information data. 41-3 is a figure which shows an example of transaction detail attached information data. FIG. 41-4 is a diagram showing an example of transaction detail attached information data.

Embodiments of the present invention will be described in detail with reference to the drawings. The present invention is not limited to this embodiment.

[1. Constitution]
An example of the configuration of the transaction statement information management system including the transaction statement information management device according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of a transaction statement information management system including a transaction statement information management device.

The transaction statement information management system 1000 illustrated in FIG. 1 includes a transaction statement information management device 100 as an information processing device, a server 200, and a network 300 that communicatively connects the transaction statement information management device 100 and the server 200. I'm out.

The transaction statement information management device 100 is a commercially available desktop personal computer, and is an information processing device for managing the information regarding the transaction statement to be described in the transaction statement. The transaction statement information management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, tablet personal computer, or the like. It may be a portable information processing device.

The transaction statement information management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108. The respective units included in the transaction statement information management device 100 are communicably connected via an arbitrary communication path.

The communication interface unit 104 communicatively connects the transaction statement information management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the transaction statement information management device 100 and the server 200 to each other so that they can communicate with each other, and is, for example, the Internet, an intranet, a LAN (Local Area Network), or the like. Therefore, the communication interface unit 104 receives the input information from the business management system, the input information from the management subsystem, and the input information from other external systems not shown in FIG. It is configured to be able to receive via the network 300 and the server 200, and outputs predetermined information to a predetermined information processing device, business management system, management subsystem, core accounting system, and other external systems. It is configured to be able to.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program (including the transaction statement information management program of the present invention) for giving instructions to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes. It As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory)/ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. As the output device 114, a monitor (including a home-use television), a speaker, and a printer can be used. As the input device 112, a keyboard, a mouse, a microphone, and a monitor that realizes a pointing device function in cooperation with the mouse can be used.

The control unit 102 is a CPU or the like that comprehensively controls the transaction statement information management device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, and required data, and performs various information processing based on these stored programs. Execute.

As shown in FIG. 1, the control unit 102 specifically includes a management journal information setting unit 102a, a transaction statement creating unit 102b, and a presenting unit 102c. The management journal information setting means 102a is means for making a setting for associating the original transaction information of the financial accounting journal with the management journal information for journalizing the original transaction information for management accounting. The management journal information will be described later. The transaction statement creating means 102b is a means for taking in information corresponding to the management journal entry information from the original transaction information and creating transaction statement data for management accounting journal entry. The presentation unit 102c is a unit for presenting a list of management journal classification candidates that can be set as management journal information. A list of management journal category candidates will be described later.

[2. Concrete example]
A specific example of this embodiment will be described with reference to FIGS. 2 to 41.

A. Overview This embodiment relates to an option system (also referred to as “general-purpose transaction statement creation option”) that can be incorporated into a core accounting system or a business management system. The technical concept includes "a data structure that enables detailed analysis by adding journal information" and "a method that allows you to freely set the analysis viewpoint and items to be analyzed from the original transaction information". 2 schematically shows a data flow in the transaction statement information management system 1000 of FIG. 1 schematically and exemplarily, and FIG. 3 shows details of the data flow in FIG. Is exemplarily shown. Specifically, in this embodiment, the original transaction statement type journal is configured as shown in FIGS. 2 and 3 so that the original transaction statement type journal can be generated separately from the financial accounting journal (aggregated type). By setting (setting) journal information (sub-information) as an item to be retained in each of the original transaction information to be stored according to the predefined mapping information, (1) missing in the financial accounting journal aggregation By holding information (information that is not reflected in financial accounting journals), it becomes possible to analyze from a multifaceted and detailed financial accounting perspective. (2) The analysis perspective and analysis target can be freely selected by the user. The effect that it becomes possible, (3) the effect that it is possible to drill down from the financial accounting journal to the original transaction statement journal, and (4) the financial accounting journal necessary for system accounting can be created as before. The effect of not affecting the response of the financial accounting system can be achieved.

B. Conventional technology and its problems The system for managing original transactions (business management system such as sales management/production management) and the financial accounting system usually store data in separate databases. Then, when the financial accounting journal is generated from the original transaction, the information regarding the individual transactions constituting the original transaction is aggregated (aggregated) by items (department, date, subject, etc.) necessary for system accounting. As a result of this aggregation, the financial accounting journals no longer reflect information about the individual transactions that make up the underlying transaction, which makes it impossible to analyze the accounting figures in multiple and detailed ways. Met. For example, it was impossible to analyze from financial accounting journals from the viewpoint of products, regions, quantity trends, etc.

In addition, if there are multiple systems for managing the original transaction, then there will be multiple databases, so cross-sectional analysis across multiple systems is impossible from a financial accounting perspective, and the details of the original transaction are Since it is not a data structure from the perspective of financial accounting, detailed analysis from the perspective of financial accounting was also impossible.

C-1. First Embodiment FIG. 4 is a flowchart showing the processing procedure of transaction detail information management processing executed in the transaction detail information management system 1000 in FIG. In the present embodiment, most of the processing shown in FIG. 4 is executed by the control unit 102 of the transaction statement information management device 100 in FIG.

In FIG. 4, first, in step S410, management journal information is set. In general, for each transaction-related data (original transaction information) that may be used for financial accounting journals, management journal information is set as sub information to be added to the data. This management journal information is used in the transaction details creation process described later.

The details of the processing procedure of this step S410 are shown in the subroutine of FIG.

In FIG. 5, first, in step S411, the type of original transaction information for which management journal information is to be set is specified. A plurality of original transaction information for past or demonstration is read, and arbitrary original transaction information is selected from among them. For example, the transaction data relating to the purchase of the product is specified as the original transaction information regarding the purchase of the product at the specific establishment based on the establishment code. In addition, by inputting certain transaction data, information indicating that the transaction data is related to purchase of goods, and by inputting the business establishment code, the transaction data is original transaction information regarding purchase of goods at a specific business establishment. May be specified. Therefore, it is possible to specify the type of arbitrary data.

Then, in step S412, a list of journal classification candidates (journal classification format) is presented to the user. This journal category candidate may be set by default or may be read from a predetermined memory. Furthermore, it is preferable that the journal classification format is recorded in a predetermined memory as a format master, which enables the user to edit. Further, this journal classification format preferably includes both the journal classification for financial accounting journals and the journal classification for management accounting journals, more preferably the journal classification for financial accounting journals and the management accounting journals. And the journal entry category are presented so as to be distinguishable (for example, individually) to the user. The journal classification for management accounting journals and the journal classification for financial accounting journals may overlap. In addition, if the financial accounting journal is performed by another accounting system or if the journal classification for the financial accounting journal is set in advance, the journal classification format for the financial accounting journal may not be included in the above journal classification format. Good.

FIG. 6 is a diagram schematically showing an example of determining a list of journal category candidates to be presented in step S412 of FIG. In the left part of FIG. 6 (the lower part of the paper), a list of journal classifications read from a predetermined memory is shown. Then, as shown by the arrow in FIG. 6, the journal classification for financial accounting journals and the journal classification for management accounting journals are sorted from the list on the left side so that the journal classification candidates to be presented in step S412 are presented. The list of can be configured (mapping). As described above, since the journal classification format can be edited, if the number or types of journal classification candidates are insufficient in step S412 of FIG. 5, the journal classification format may be edited. FIG. 7 shows an example of a display screen that is displayed when allocating the journal classifications for management accounting journals when the list of journal classification candidates described with reference to FIG. 6 is determined. It is preferable to display the display screen as shown in FIG. 7 as the setting screen also when presenting the list of journal classification candidates in step S412, which can reduce the time and effort for customization by the user.

Next, in step S413, the journal classification for the management accounting journal selected through the above-mentioned journal classification format is set as the management journal information in the original transaction information identified in step S411. As a result, the original transaction information of a specific type and the journal classification for management accounting journal are associated with each other. Succeedingly, in a step S414, the combination of the original transaction information and the management accounting journal associated with each other is stored in a predetermined memory as a table (hereinafter, also referred to as “mapping master”).

Then, in step S415, it is determined whether or not to set the management journal information for other types of original transaction information. As a result of the determination, if there is another type of original transaction information (Yes in step S415), the process returns to step S411 and the processes of steps S411 to S414 are repeated. On the other hand, as a result of the above determination, when there is no other type of original transaction information (No in step S415), this subroutine is finished and the process returns to the process of FIG.

Returning to the processing of FIG. 4, in the subsequent step S420, the original transaction information to be the target of this processing is fetched. This original transaction information may be input from the business management system, the management subsystem, and other external systems as shown in FIG. 3, or is stored in the storage unit 106. May be. The acquired original transaction information is stored in a predetermined working area (hereinafter, also referred to as “work”) of the storage unit 106.

Then, in step S430, preset management journal information is added to each of the imported original transaction information by referring to the mapping master obtained in step S413. The management journal information added here includes, for example, loan history, account items, information for specifying a product (product code), quantity, unit price, slip number, and update history information regarding accounting month. In addition, information related to currency (for example, foreign currency flag), exchange rate, and the like are added as management journal information as necessary. Furthermore, the management journal information may be classified into classes, for example, the main store code is the main class and the branch code is the subclass, whereby both the main store code and the branch code can be managed by the store code. It may be allowed to handle as journal information or to handle the head office code and the branch code individually. Similarly, the office code may be the main class and the department code may be the subclass. Further, a plurality of original transaction information may be treated as a group of original transaction information, and the management journal information may be added to the group of original transaction information. The original transaction information having the data structure to which the management journal information is added as described above is saved by being updated on the work.

Next, in step S440, it is determined whether or not the original transaction information stored on the work needs to be updated for the accounting month. When the update is necessary (Yes in step S440), necessary information is added to the update history information, unnecessary information is deleted, and the like (step S445), and the next accounting month is set. Then, the process returns to step S430. When updating the update history information, it is preferable to save the original transaction information for the previous accounting month in another memory area and also create cumulative information such as the transaction amount for each original transaction information. , It is possible to speed up the calculation process in the closing period.

On the other hand, when it is not necessary to update the original transaction information on the work (No in step S440), the process proceeds to step S450 to perform the transaction statement creating process described in detail with reference to FIG.

FIG. 8 is a flowchart showing a processing procedure of a subroutine of the processing of step S450 of FIG.

In FIG. 8, first, in step S451, the system waits for journal information for designating a journal entry method for creating transaction details, and if the user inputs a journal entry method, the corresponding journal entry is entered. Get information.

Next, in step S452, required original transaction information is extracted from the original transaction information stored in the work according to the journalizing method corresponding to the journalizing information acquired in step S451. Here, when all the original transaction information is extracted, the transaction details according to the financial accounting journal are displayed on the balance sheet (B/S) or the income statement (P/L) through the process described below. It can be created. In the following step S453, the original transaction information extracted in step S452 is totaled for journal entry. If the extracted original transaction information is the original transaction information that has been aggregated in advance, the aggregation process of step S453 is skipped. Further, in step S454, the display format is adjusted so as to create the display screen data from the aggregated original transaction information according to a preset screen display method. At this time, necessary numbering processing and sorting processing are performed. Then, the obtained display screen data is saved on the work, and the update history information is updated as necessary (step S455).

Next, in step S456, it is determined whether or not an instruction input for changing to the short format has been input. Here, the short format means that the original transaction information tabulated in step S454 is displayed as it is (in long format), and the display is changed according to the format of the financial accounting journal. It is a collection of long format original transaction information. It should be noted that the process of step S456 is performed even when an instruction input for displaying both the long format and the short format is made. When changing to the short format, the previously obtained display screen data is saved on the work, and then the process returns to step S454 to change the necessary display format.

FIG. 9 is a diagram for schematically explaining the original transaction information regarding the transaction statement creation created by the process of FIG. 8, and FIG. 9A is the original transaction information extracted in step S452 of FIG. 9(b) is an example of transaction statement data in a long format created from the original transaction information of FIG. 9(a), and FIG. 9(c) is a long statement of FIG. 9(b). An example of the transaction details when the data of the transaction details in the format is changed to the short format is shown. As shown in FIG. 9B, in the present embodiment, the transaction statement data is managed so that the debit and the credit are a pair, which allows the conversion to the short format easily. You can do it.

Returning to FIG. 8, in step S457, the obtained display screen data is output. The output display screen data is displayed on a monitor which is an example of the output device 114. The output destination is not limited to the output device 114, and may be output to the server 200 or another information processing device via the network 300. For example, one or both of the long format original transaction information and the short format original transaction information are output to the core accounting system.

Note that part or all of the processing shown in FIG. 8 and part of the processing shown in FIG. 4 (particularly a series of processing using a work) can be performed using an API (application programming interface). In this case, the insert function and the delete function can be realized by using the insert and delete of the SQL command for updating the update history information.

When the creation of the transaction details is completed as described above, the subroutine of FIG. 8 is ended, and the process returns to the process of FIG. 4 to complete all the processes.

According to the process of FIG. 4, a mapping master is created by setting management journal information for each type of original transaction information (step S413). Therefore, by using this mapping master, management of arbitrary data is performed. Journal information can be added (step S430). That is, the management journal information can be added to the original transaction information before the financial accounting journal. Therefore, even after the original transaction information has been consolidated to create financial accounting journals, it is not necessary to collect and aggregate the original transaction information again, and the original transaction information can be used to add the original transaction information. It will be possible to carry out management journal entries.

Further, according to the processing of FIG. 4, when journal entry information for designating a journal entry method is accepted (step S451), necessary original transaction information is extracted according to the accepted journal entry information (step S452), and the transaction is performed. Since the data corresponding to the statement is created (step S450), the transaction statement created by an arbitrary journal entry method (for example, management accounting journal by department) can be obtained. As a result, it is possible to facilitate aggregation from various and detailed financial accounting viewpoints.

Furthermore, according to the process of FIG. 4, the created transaction statement data can be converted into the short format (Yes in step S456). Therefore, when all the original transaction information is used, the financial accounting journal (for example, It will be possible to create transaction data that matches the balance sheet or income statement. Therefore, when a balance sheet or income statement is obtained, or when a balance sheet or income statement is created in parallel, transaction statement data obtained in long format (that is, management accounting (Journals) can be easily compared.

Next, the above-described embodiment will be described with examples.

FIG. 10-1 is a diagram schematically showing an example of a group of original transaction information that is the target of the process of step S450 of FIG. 4 (process of FIG. 8), and FIG. FIG. 10 is a diagram schematically showing an example of a part of a long-format transaction statement created from the group of original transaction information shown in FIG. 10, and FIG. 10-3 is a long-format transaction statement shown in FIG. 10-2. FIG. 6 is a diagram schematically showing an example of a case where is changed to a short format. As shown in FIG. 10-2, in the long format, not only the business office code and department code that are accounting organizations are stored, but also the business office code and department code that are actual organizations are stored. Has been done. Furthermore, in FIG. 10-2, the same slip number is assigned to a plurality of original transaction information. On the other hand, in the short format, as shown in FIG. 10-3, as a result of aggregating a plurality of original transaction information based on the slip number and the business department code and department code that are accounting organizations. Although the information on the actual organization's office code and department code is no longer reflected in the daily transaction details, it has the advantage that it can be used as a financial accounting journal.

FIG. 11 is a diagram showing an example of an income statement prepared from the transaction details shown in FIG. 10-3. Although the income statement as shown in FIG. 11 can be created by the conventional technique, according to the above-described embodiment, the statement of transaction in the short format shown in FIG. It can also be created from the transaction details in the long format shown in. Further, in the prior art, since the original transaction information is only aggregated only for creating the income statement, it is necessary to newly create transaction details as shown in FIG. 10-2 or FIG. 10-3. Although it was necessary to refer to (collect) the original transaction information, in the above-described embodiment, since the journal entry information is held as described above, the transaction using the necessary original transaction information is performed at any timing. It is possible to create a statement.

12-1 is a diagram schematically illustrating an example of transaction detail data created in step S450 of FIG. 4, and FIGS. 12-2, 12-3, and 12-4 are illustrated in FIG. It is a figure which shows the example of the income statement for management journals which can be created using the data of the transaction details shown in FIG.

In the present embodiment, as shown in FIG. 12-1, the original transaction information is managed with a lot of information added. Therefore, in the present embodiment, by combining the journalizing information for designating the journalizing method (step S451), as shown in FIGS. 12-2, 12-3, and 12-4, respectively, by department. It is possible to create an income statement for each product type and region for management journal entries. Furthermore, by combining the journalizing information for specifying the journalizing method, a regional sales analysis table as shown in FIG. 13 or a customer profit/loss analysis table as shown in FIG. 14 can be created. It is also possible to do. Therefore, according to this embodiment, it is possible to easily create a material suitable for timely disclosure information.

C-2. More Specific Example of First Embodiment Here, referring to FIGS. 15 to 41, a transaction statement information management system 1000 (general-purpose transaction statement creating system) including the transaction statement information management apparatus 100 shown in FIG. A more specific example of will be described. The transaction statement information management device 100 and the transaction statement information management system 1000 can create the transaction statement as described above.

FIG. 15 is a diagram showing an example of a transaction statement creation image. FIG. 16 is a diagram showing an example of the entire transaction statement information management system. FIG. 17 is a diagram showing an outline of the transaction statement information management system. FIG. 18 is a diagram showing an example of the mechanism of the transaction statement DB. FIG. 19 is a diagram showing an example of an item mapping image regarding transaction detail data. FIG. 20 is a diagram showing an example of the cooperation image. FIG. 21 is a diagram showing an example of the cooperation image. Note that, in FIG. 21, the management accounting (transaction statement) journal data is shown as being divided into two because of the size of the space, but it is actually aggregated into one. FIG. 22 is a diagram showing an operation example. FIG. 23 is a diagram showing an operation example. Note that, in FIG. 23, the management accounting (transaction statement) journal data is shown as being divided into two because of the size of the space, but in reality it is aggregated into one. FIG. 24 is a diagram showing an operation example.

25-1 and 25-2 are diagrams showing an example of a mapping image. FIG. 26 is a diagram showing an example of a processing flow relating to general-purpose journal external import. FIG. 27 is a diagram illustrating an example of a processing flow relating to financial journal entry. FIG. 28 is a diagram showing an example of the transaction statement data creation processing screen.

29 to 33 relate to transaction statement API design for MA journal entries. FIG. 29 is a diagram showing an example of a transaction statement cooperation API (application programming interface). FIG. 30 is a diagram illustrating an example of a processing flow relating to transaction detail creation. FIG. 31 is a diagram showing an example of a function list of the transaction statement information management system. 32-1 to 32-7 are diagrams illustrating an example of the transaction statement update work update process. FIG. 33 is a diagram illustrating an example of a foreign currency cooperation journal entry history.

34 to 38-8 are related to the transaction statement API design for general-purpose journal cooperation. FIG. 34 is a diagram illustrating an example of the transaction statement cooperation API. FIG. 35 is a diagram showing an example of object arrangement in creating transaction details. FIG. 36 is a diagram illustrating an example of a processing flow relating to transaction detail creation. FIG. 37 is a diagram showing an example of a function list of the transaction statement information management system. 38-1 to 38-8 are diagrams illustrating an example of transaction detail update work update processing.

FIG. 39 is a diagram showing an example of a table list in the transaction statement information management system. 40-1 to 40-5 are diagrams showing examples of transaction detail data. 41-1 to 41-4 are diagrams illustrating examples of transaction detail attached information data.

C-3. Other Embodiments In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

For example, of the processes described in the embodiment, all or part of the processes described as being automatically performed may be manually performed, or all of the processes described as manually performed. Alternatively, a part thereof can be automatically performed by a known method.

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

Further, regarding the transaction statement information management device 100 and the transaction statement information management system 1000, each constituent element shown in the drawings is functionally conceptual, and does not necessarily have to be physically configured as illustrated.

For example, the processing functions of the transaction statement information management device 100, particularly the respective processing functions performed by the control unit 102, are implemented in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, the hardware may be realized by wired logic. The program is recorded on a non-transitory computer-readable recording medium that includes programmed instructions for causing the information processing apparatus to execute the processing described in the present embodiment, and transaction detail information as necessary. It is mechanically read by the management device 100. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded in the RAM, and constitutes a control unit in cooperation with the CPU.

Further, this computer program may be stored in an application program server (for example, the server 200 connected via the network 300) connected to the transaction statement information management device 100 via an arbitrary network, It is also possible to download all or a part of it as needed.

Further, the program for executing the processing described in the present embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registered). (Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), MO (Magneto-Optical disk), etc. It shall include any "portable physical medium". Therefore, the recording medium that stores the program for executing the processes described in the present specification also constitutes the present invention.

The "program" is a data processing method described in any language or description method, and may be in any format such as source code or binary code. Note that the "program" is not necessarily limited to a single configuration, and it achieves its function in cooperation with a plurality of modules or libraries that are distributed and configured, or with a separate program represented by an OS. Including things. Note that known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, and the installation procedure after reading.

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

Further, the transaction statement information management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Further, the transaction statement information management device 100 may be realized by mounting software (including a program or data) for realizing the processing described in the present embodiment on the device.

Further, the specific form of the dispersion/integration of the devices is not limited to that shown in the drawings, and all or a part of the devices may be functionally or physically arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be implemented in any combination, or the embodiments may be selectively implemented.

The present invention is particularly useful in the accounting field.

100 transaction statement information management device 102 control section 102a management journal information setting means 102b transaction statement creating means 102c presenting means 104 communication interface section 106 storage section 108 input/output interface section 112 input device 114 output device 200 server 300 network 1000 transaction statement information management system

Claims (5)

A transaction statement information management device having a control unit for managing information on transaction statements to be described in a transaction statement,
The control unit is
Transaction details for management accounting journals by referring to the management journal information for journalizing for management accounting set for each financial transaction journal's original transaction information and adding the management journal information to one original transaction information A transaction statement information management device comprising: transaction statement creating means for creating transaction statement data that includes both data regarding a debit item and information regarding a credit item of a loan category . The management journal information includes financial management journal information for journaling the original transaction information for the financial accounting journal,
The transaction statement creating means creates transaction statement data created from the original transaction information, the transaction statement data of which the item is in financial management agreement with the financial accounting journal, using the management journal information. The transaction statement information management device according to claim 1 . The control unit is
The transaction statement information management device according to claim 1 or 2 , further comprising: a unit that reads out a list of management journal classification candidates that can be set as the management journal information and displays the list on a display screen . A transaction statement information management method for managing information on transaction statements to be described in a transaction statement, which is executed in an information processing device including a control unit,
Executed in the control unit,
Transaction details for management accounting journals by referring to the management journal information for journalizing for management accounting set for each financial transaction journal's original transaction information and adding the management journal information to one original transaction information A transaction statement information management method comprising: a transaction statement creating step of creating transaction statement data which is data and includes both information regarding a debit item of a credit category and information regarding a credit item . A transaction statement information management program for managing information about transaction statements to be described in a transaction statement, which is executed by an information processing device including a control unit,
To be executed in the control unit,
Transaction details for management accounting journals by referring to the management journal information for journalizing for management accounting set for each financial transaction journal's original transaction information and adding the management journal information to one original transaction information A transaction statement information management program comprising a transaction statement creating step of creating transaction statement data that includes both data relating to a debit item and information relating to a credit item of a credit category .