JP2012230582A - Confirmation method and program of transaction compatibility between enterprise groups - Google Patents

Abstract

Provided is a method and program for checking the consistency of intra-group transaction data to be performed before settlement processing in order to perform consolidated settlement processing in a corporate group in a short period of time.
SOLUTION: In a consolidated accounting system of group companies connected by a network, the consolidated account balances of each company's business partners and the business transaction data of each company's daily, business partner, and account item are consolidated through the network. Consolidate in a data integrity verification system. Reconciliation is performed based on a combination of elimination of internal transactions (matching company combination, consolidated account item combination) in which the financial information collected above is pre-registered, and a difference for each consolidated account item is extracted. Further, by referring to and comparing the business transaction data of each company based on the difference information for each consolidated account item extracted as described above, the amount difference in the daily transaction data is extracted and displayed on the screen.
[Selection] Figure 1

Description

  The present invention relates to a technology for confirming transaction consistency between groups in a corporate consolidated accounting system.

  With the diversification and globalization of corporate activities, the importance of consolidated financial statements that show the financial status and business performance of a corporate group is increasing. As corporate groups develop, the number of companies and organizations that should collect financial data also increases. In the consolidated financial statements, transactions within the corporate group must not be described, so it is necessary to exclude intra-group transactions from the data sent from each company.

  The financial data sent from each company contains a lot of human errors, so it is necessary to check the contents and correct them. However, it is necessary to investigate a huge amount of data with limited personnel in a short period of time. There is a limit, and there is a need for efficient checks.

  There is known a technique (see Patent Document 1) in which financial data sent from each company is arranged using a matching key for each company and subject and displayed so as to be easily confirmed.

JP 2003-271798 A

  By using the previous technology (Patent Document 1), it can be expected that the data received from each company will be confirmed efficiently. There is a problem that it is necessary to check all data including data, and it is difficult to know which slip should be corrected when inconsistency is found.

  This invention is made | formed in view of such a situation, and makes it a subject to provide the confirmation method and program of transaction consistency between groups in a company's consolidated accounting system.

  One means for solving the above problem will be described. The present invention is a method for confirming the consistency of mutual transactions within a company group in a consolidated accounting system for group companies connected by a network. As a confirmation method, the consolidated account item balance of each company's business partner and the business transaction data of each company are collected in a consolidated data consistency confirmation system through the network.

  The financial data collected from each company is reconciled with a combination of elimination of internal transactions registered in advance (by company and by consolidated account item) to create differential data. Next, acquire and reconcile the transaction amount data for each company's single account item, daily / customer based on the difference data of the created consolidated account, and extract and display the data of the transaction where the difference has occurred .

  According to the present invention, the consistency of data can be checked efficiently and in a short time, thereby increasing the speed of consolidated settlement processing. Therefore, a lot of time can be used for management judgment using the consolidated settlement data.

It is a figure which shows the example of a consolidated account settlement system whole block diagram including a consolidated data consistency confirmation system. The hardware block diagram of a connection data consistency confirmation system. The hardware block diagram of a system management terminal. The layout diagram of the matching company table. Layout diagram of the matching account table. The layout figure of a consolidated-single account item correspondence table. The layout figure of a processing order table. Layout diagram of each company consolidated account table. Layout diagram of each company's single account table. The layout figure of a consolidated account difference table. The layout figure of a single account difference table. Verification company table creation processing flow diagram. Verification account table creation process flow diagram. Processing sequence table creation processing flow diagram. Consolidated account difference extraction processing flowchart. Single account difference extraction processing flow diagram. The figure which shows the collation company registration screen example. The figure which shows the example of a collation account item registration screen. The figure which shows the example of a process order registration screen. The figure which shows the example of a process result output screen.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram illustrating an example of the overall configuration of a computer network system 100 according to the present embodiment. The consolidated accounting system 100 includes a plurality of group company single accounting systems 101 to 104, a system management terminal 108, a consolidated data consistency management system 109, and a consolidated accounting system 110.

  The consolidated data consistency management system 109 receives the accounting data (consolidated account data, single account data) of the individual company accounting systems 101 to 104 of each company in the consolidated group through the network, and confirms the consistency of the accounting data between the companies.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of the concatenated data consistency confirmation system 109. The linked data consistency confirmation system 109 includes a control unit 202 such as a CPU, a storage unit 201, and a network interface unit 203 that transmits and receives information to and from the network 107. The storage unit 201 also includes a program 211 having a matching company table creation function, a program 212 having a matching account item table creation function, a program 213 having a processing order table creation function, and a linked account difference extraction executed by the control unit 002. A program 214 having a function and a program 215 having a single account difference extraction function are stored.

The processing order table creation function 213 has a function of registering the input information on the master registration screen in FIG. 19 in the matching company table, the matching account item table, and the consolidated-single account correspondence table.
The consolidated account difference extraction function 214 extracts the difference between the consolidated account item balances by business partner in the consolidated group according to the flow of FIG. The single account difference extraction function 215 performs matching of transaction data between companies that have a difference in the balance item balance according to the flow of FIG. Perform data matching at the daily business data level.

  FIG. 3 is a diagram illustrating an example of a hardware configuration of the system management terminal 110. The system management terminal 110 includes a control unit 304 such as a CPU, a storage unit 301, a network interface unit 305 that transmits and receives information to and from the network 107, a screen display unit 302, and an input unit 303 such as a keyboard / mouse.

  FIG. 4 is a diagram illustrating a configuration example of the verification company table 220. In the verification company table, a company to be paired when deleting internal transactions is registered. It consists of a standard company that serves as a standard, its business partners, and the numbers that manage them.

  FIG. 5 is a diagram illustrating a configuration example of the matching account item table 221. In the matching account item table, a linked account item that is paired when intercompany elimination is performed is registered. It consists of a standard consolidated account item serving as a reference, a business partner consolidated account item, and a number for managing them.

  FIG. 6 is a diagram illustrating a configuration example of the consolidated-single account correspondence table 222. The relationship between the consolidated account item and the individual account item of each company is registered in the consolidated-single account correspondence table. It consists of standard consolidated account items, corresponding single account items of each company, and numbers for managing them.

  FIG. 7 is a diagram illustrating a configuration example of the processing order table 223. In the processing order table, the collation contents of the consolidated account items performed for each collation company are registered. The matching company number 22302 corresponds to the matching company number 2201 of the matching company table 220, and the matching account item numbers 1 to N correspond to the matching account item number 2211 of the matching account item table 221. Flag the verification account number to be checked for each verification company number.

  FIG. 8 is a diagram illustrating a configuration example of each company consolidated account table 224. The consolidated account balances received from the group companies are registered in each consolidated company table. It consists of a base company, consolidated account items, business partners, and balance.

  FIG. 9 is a diagram illustrating a configuration example of each company single account table 225. In the company single account table, the single item balance received from each group company is registered. It consists of a base company, a single account item, a business partner, a transaction date, and a transaction amount.

  FIG. 10 is a diagram illustrating a configuration example of the consolidated account difference table 226. The consolidated account difference table is a table that stores the difference between the results of comparing the company consolidated account item balances according to the order of the processing order table, and is updated when the consolidated account difference extraction function 214 is executed. The record having the difference stores the reference company of the transaction, the matching account item that has been verified, and the balance of the reference company and the business partner.

  FIG. 11 is a diagram illustrating a configuration example of the single account difference table 227. The single account difference table is based on the records of the consolidated account difference table 226, referring to the data of the consolidated-single account table and each company's single account table, and the difference is calculated from the balance difference generated for each matching company and matching account item. This is a table for extracting and storing each company transaction data that is occurring, and is updated when the consolidated account difference extraction function 215 is executed.

FIG. 12 is a diagram showing a verification company table creation processing flow. In S121, the verification company registration data (data 1701-1703 shown in FIG. 17) input at the system management terminal is received. The verification company registration data received in S122 is stored in the verification company table 220. However, all the registered data shall be deleted before storing the data in the verification company table. (All cases will be updated at once)
FIG. 13 is a diagram showing a verification account item table creation processing flow. In S131, the verification account item registration data (data 1801 to 1803 shown in FIG. 18) input from the system management terminal is received. The matching account item registration data received in S132 is stored in the matching account item table 221. However, all registered data shall be deleted before data is stored in the matching account item table. (All cases will be updated at once)
FIG. 14 is a diagram showing a processing sequence table creation processing flow. In S141, the processing order registration data (data 1901 to 1908 shown in FIG. 19) input at the system management terminal is received. The processing order registration data received in S142 is stored in the processing order table 223. However, all registered data is deleted before data is stored in the processing order table. (All cases will be updated at once)
FIG. 15 is a diagram illustrating a processing flow of the consolidated account difference extraction function. In S151, the processing order table 223 is read, and the priority order number 22301, the matching company number 22302, and the matching account item numbers 22303 to 22307 whose flag is set to 1 are acquired. The matching company table 220 is searched using the matching company number 22302 as a key, and the reference company 2202 and the business partner 2203 of the corresponding record are extracted. Next, the matching account item table 221 is searched using the matching account item numbers 22303 to 22307 as a key, and the reference consolidated account item 2212 and the business partner consolidated account item 2213 of the corresponding record are extracted. Next, each company consolidated account table 224 is searched using the standard company 2202, the standard consolidated account item 2212, and the business partner 2203 as keys, and the consolidated account balance 2244 of the corresponding record is extracted. The consolidated account balance is similarly extracted for the business partner. (At the time of data extraction, considering the reversal of the extraction company, the data is extracted by replacing the business partner with the base company and the base company with the business partner.) If the balances do not match, the extracted data is stored in the consolidated account difference table 226.

  FIG. 16 is a diagram showing a processing flow of the single account difference extraction function. In S161, the consolidated account difference table 226 is read, and the base company 22603, the base company account item 22605, the supplier 22607, and the supplier account item 22608 are acquired. Next, the consolidated-single account correspondence table 222 is searched using the reference company 22603 and the reference company account item 22605 as keys, and the individual account items 2223 to 2226 of the corresponding record are acquired. (At the time of data extraction, consider the reversal of the extraction company, and extract the data by replacing the business partner with the base company and the base company with the business partner.) Next, each company alone with the base company, non-consolidated account item, business partner as the key The account table 225 is searched, and the transaction amount by transaction date of the corresponding record is acquired. (At the time of data extraction, considering the reversal of the extraction company, the data is extracted by replacing the business partner with the standard company and the standard company with the business partner.) Next, the single company account balance and business partner extracted in the previous process If the balances do not match, the extracted data is stored in the single account difference table 227.

  FIG. 17 is a diagram showing a verification company registration screen. In the collation company registration screen 1700, a combination of companies for checking the elimination of internal transactions is registered. Data is registered in the verification company table 220 by designating the reference company 1701 and the business partner 1702 and pressing the registration button.

  FIG. 18 is a diagram showing a matching account item registration screen. On the matching account item registration screen 1800, a combination of consolidated account items to be checked for elimination of internal transactions is registered. Data is registered in the matching account item table 221 by designating the standard consolidated account item 1802 and the business partner consolidated account item 1803 and pressing the registration button.

  FIG. 19 is a diagram showing a processing order registration screen. In the processing order registration screen 1900, a combination of companies and account items for which internal transactions are eliminated and their order are registered. First, the verification company number 1902 and the verification account items 1905 to 1907 are specified, and then the combination of the verification company to be checked and the verification account item is specified. Flag the check box for the target.

  FIG. 20 is a diagram showing a collation result display screen. On the verification result display screen 2000, the result processed by the single account difference extraction function 215 is displayed. An inquiry can be made to the business system and the slip input department based on the information of the reference company 2001, the reference company account item 2002, the transaction date 2003, the transaction amount 2005, the business partner 2006, and the difference 2009.

  The embodiment of the present invention has been described above.

  According to the above-described embodiment, the consistency check of the financial data collected from each company is efficiently performed, thereby reducing the total work time of the consolidated settlement work. Therefore, a lot of time can be spent on management decisions using the consolidated financial statements.

  Although the embodiment of the present invention has been described above, the present invention is not limited to this, and various modifications can be made without departing from the scope of the invention.

101, 102, 103, 104 ... Individual accounting system for each company, 105, 106, 107 ... Network, 108 ... System management terminal, 109 ... Consolidated data consistency management system, 110 ... Consolidated accounting system.

Claims (4)

In a consolidated accounting system in a corporate group, a method for confirming transaction consistency, particularly between corporate groups,
From each social accounting system, receive the balance of consolidated account items by business partner and business transaction data of each company via the network,
The two companies that carry out intra-group transactions by matching the received consolidated account balances by business partner based on the matching company registered in the matching company table and the account item registered in the matching item account table. Store the difference for each company's consolidated account item in the consolidated account difference table,
Search each company's stand-alone account table based on the standard company, business partner, and standard company account item of the data stored in the consolidated account difference table, obtain the transaction information of each company, and calculate the unmatch in the daily transaction data And store the calculated result in the single account difference table,
Outputting the calculation result to a terminal;
A method for confirming transaction consistency between corporate groups. In a consolidated accounting system in a corporate group, a method for confirming transaction consistency, particularly between corporate groups,
Display the screen to enter the combination of companies to check the consistency of internal transactions on the display,
Receiving the company combination via the input unit;
Control the contents of the matching company table,
A method for confirming transaction consistency between corporate groups. In a consolidated accounting system in a corporate group, a method for confirming transaction consistency, particularly between corporate groups,
Display the screen to enter the combination of accounts to check the consistency of internal transactions on the display,
Receiving the combination of account items via the input unit;
Control the contents of the matching account table,
A method for confirming transaction consistency between corporate groups.   The program which controls a computer and performs the confirmation method of the transaction consistency between the corporate groups of any one item of Claim 1 thru | or 3.

Images