JP5447082B2 - Accounting support apparatus, accounting support program, and accounting support method - Google Patents

Description

  The present invention relates to an accounting support apparatus, an accounting support program, and an accounting support method that support accounting processing.

  Conventionally, data transfer processing between devices such as transferring data acquired by one device to another device has been frequently used. Therefore, many techniques have been provided to prevent the occurrence of errors associated with data transfer processing, such as data being lost during transfer or being associated with other unrelated data.

  A technique for maintaining the accuracy of data transfer processing is applied to data processing in various fields. For example, if the system for managing the purchase and sale of goods and services and the accounting system for managing the deposit processing and withdrawal processing generated by the trading are provided as independent systems, omissions or errors in accounting content There is a need to know exactly whether there are any unprocessed items. Therefore, the data accumulated by the two systems is transferred to a dedicated database or management device for matching.

  Therefore, the transfer process as described above is also used for the accounting process. For example, when a management device finds an error in data received from one system, a technique for sharing information related to the occurrence of the error by notifying the other related systems in addition to the one system (For example, refer to Patent Document 1 below.) In addition, there is a technique for managing data transfer histories between a plurality of systems (see, for example, Patent Document 2 below), which is useful for identifying the cause when an error occurs.

JP-A-1-318134 JP 2001-14285 A

  However, in the case of the prior art, since it is not a technique designed with application to accounting processing in mind, there is a case where sufficient information for identifying the cause cannot be obtained when an error occurs due to accounting processing. In particular, in the accounting process, a large number of data accumulation processes are performed, such as collecting individually input sales slips by business partners or settlement categories.

  In the prior art, when an error occurs, data that causes the error to surface can be specified. However, if an error occurs when certain data is accumulated in other data, it is impossible to determine whether the cause of the error is in the accumulated data or in the accumulated data was there.

  Further, when the occurrence of an error is investigated with reference to the transfer history, it is determined whether or not an error has occurred from data accumulated at predetermined timings such as every several hours or every several days. Therefore, since the transfer history to be referred to is after the actual error occurrence, there is a problem that it is not suitable for an error check at an early stage.

  In order to solve the above-described problems caused by the conventional technology, the disclosed technology checks whether or not an error has occurred due to input data at an early stage, and also supports an accounting support apparatus, an accounting support program, and an identification of a cause when an error occurs. The purpose is to provide accounting support methods.

  In order to solve the above-described problems and achieve the object, the present disclosure technology provides the slip data from a trading system that accepts slip data representing a trading transaction, and a journal that represents deposits and withdrawals for each business partner corresponding to the slip data. In a computer accessible to a database storing the journal data from an accounting system that accepts data, a process for obtaining one slip data from the trading system, and one slip data obtained from the database A process for extracting journal data that is common to a business partner, a process for extracting other slip data having the same unit of the sales transaction and the one slip data from the database, and the one slip data A process for associating the extracted journal data with other slip data, the sales transaction represented by the one slip data, Processing for determining whether the deposit / withdrawal represented by the journal data associated with the slip data satisfies a predetermined relationship, and when it is determined that the predetermined relationship is not satisfied, the associated slip data And processing for outputting the journal data and the other slip data.

  According to this accounting support apparatus, accounting support program, and accounting support method, it is possible to check whether or not an error has occurred based on input data at an early stage and to assist in specifying the cause when an error occurs.

It is explanatory drawing which shows an example of an accounting support process. It is explanatory drawing which shows the structure of the accounting system provided with the accounting assistance apparatus. It is a block diagram which shows the hardware constitutions of an accounting assistance apparatus. It is a block diagram which shows the functional structure of an accounting assistance apparatus. It is a flowchart which shows the procedure of an accounting support process. It is a flowchart which shows the procedure of the data storage process to traceability DB. It is explanatory drawing which shows the front information stored in traceability DB. It is explanatory drawing which shows the example of storage of traceability DB. It is explanatory drawing which shows the relationship between traceability DB, an abnormal value check master, and error data. It is a flowchart which shows the procedure of an abnormal value check process. It is explanatory drawing which shows the example of a setting of an abnormal value check master. It is explanatory drawing which shows the example of a production | generation of error data. It is a flowchart which shows the procedure of the relevance check process of error data. It is a flowchart which shows the procedure of an error notification process. It is explanatory drawing which shows the example of a system error notification.

  Exemplary embodiments of an accounting support apparatus, an accounting support program, and an accounting support method according to the present invention will be explained below in detail with reference to the accompanying drawings.

  FIG. 1 is an explanatory diagram illustrating an example of an accounting support process. As shown in FIG. 1, the accounting support processing according to the present embodiment uses a common database 110 to perform accounting processing using input data from a plurality of systems (for example, the trading system 210 and the accounting system 220). I have prepared it.

  In the accounting support apparatus 100, when each system 210, 220 newly stores data in the database 110, data related to the data to be stored is extracted from the stored data, and each data is exchanged. They are associated with each other (step S12). Specifically, the related data is, for example, data referred to when performing accounting processing or data having the same transaction unit as the data to be stored. That is, when an error occurs in the data to be stored, data that may cause the error and data useful for identifying the cause are associated as related data.

  Thereafter, the accounting support apparatus 100 performs an error check on the data to be stored (step S12). The error check is a determination as to whether or not the data to be stored is an appropriate value. For example, if the data to be stored is slip data from the buying and selling system 210, accounting data in which the slip data and the business partner are common and other slip data in common transaction units are associated in step S11.

  As an error check, for example, it is determined whether the correspondence between the sales amount indicated by the slip data and the deposit / withdrawal amount indicated by the accounting data is appropriate. Judgment is made as to whether it matches the gold classification. In addition to the items to be referred to at the time of the accounting process, what kind of determination is made as the error check may be set individually by the user of the accounting support apparatus 100 and used as an error check item.

  Thereafter, when an error is detected by the error check in step S12, the accounting support apparatus 100 includes a series of related data associated in step S11 as data that may cause the error together with the error result. Extracted (step S13). The extracted related data may be output from the accounting support apparatus 100, or may be transmitted to the target system and output on the target system. Further, the related data itself may be output as an index representing the related data without being output as it is.

  Specifically, in the case of FIG. 1, when the slip data A is stored in the database 110 from the trading system 210, the accounting support apparatus 100 performs database processing based on the information of the slip data A by the process of step S <b> 11. The slip data C stored in 110 is associated with the accounting data B.

  Thereafter, the accounting support apparatus 100 performs an error check on the slip data A by the process of step S12. If an error has occurred for the slip data A, the accounting support apparatus 100 extracts related data (slip data A, slip data C, accounting data B) by the process of step S13. The extracted related data is output to the user of the accounting support apparatus 100 and the user of the corresponding system (the trading system 210 in the example of FIG. 1), and is used as information for assisting in identifying the cause of the error occurrence. Is done.

  As described above, by providing the accounting support apparatus 100, the new data and the stored data are associated with each other when the new data is stored in the database 210 from the systems 210 and 220. . Therefore, the data is newly stored in the database 110 in a state in which it is possible to specify what kind of data is accumulated in relation to the data, not single data.

  Moreover, since the accounting support apparatus 100 performs an error check at a timing when new data is stored in the database 110, the occurrence of an error can be specified at an early stage. In addition, when an error occurs, information related to the occurrence of the error is linked, making it easier to identify the cause of the error than in the past. In addition, what data is extracted as related data, what error check is performed, and the like can be appropriately set. Therefore, the rule of thumb in the accounting process can be reflected in the accounting support apparatus 100 to improve the usability and convenience for the user.

  Hereinafter, a specific system configuration for realizing the above-described accounting support processing, and a specific configuration and processing contents of the accounting support apparatus 100 will be described.

(Structure of accounting system)
FIG. 2 is an explanatory diagram illustrating a configuration of an accounting system including an accounting support apparatus. FIG. 2 shows a configuration example of an accounting system 200 using a plurality of systems. In the accounting system 200, a sales system 211, a purchase system 212, and other systems 21x are prepared as the trading system 210. On the other hand, the accounting system 220 is a system that handles deposits and withdrawals corresponding to sales transactions by the sales system 210.

  Various data are stored in the database 110 (which will be described as a traceability DB (database) as an example) 110 from the trading system 210 and the accounting system 220. In the case of the accounting system 200 illustrated in FIG. 2, the traceability DB 110 has a configuration built in the accounting support apparatus 100, but may be prepared outside the accounting support apparatus 100.

  As illustrated in FIG. 2, in the sales system 211, a sales slip accompanying a sales transaction is input by the sales slip input processing unit and stored in a sales data DB (database). The sales data 201 stored in the sales data DB is stored in the traceability DB 110 via the capture processing unit 101 of the accounting support apparatus 100 for the purpose of reconciliation with the accounting system 220.

  As shown in FIG. 2, the trading system 210 includes a plurality of systems such as a purchasing system 212 in addition to the sales system 211, but in the following description, sales data 201 from the sales system 211 is used for convenience. The description will be limited to this example. However, regarding the data from the purchasing system 212 and other systems 21x, the same behavior is shown only with the data names and items being different.

  On the other hand, in the accounting system 220, information on deposits and withdrawals corresponding to trading transactions in the trading system 210 is stored in the journal data DB (database) by the external data capture processing unit. The journal data 202 stored in the journal data DB is stored in the traceability DB 110 via the accounting system cooperation processing unit 102 of the accounting support apparatus 100 for the purpose of matching with the trading system 210.

  When the new sales data 201 is stored in the traceability DB 110, the accounting support apparatus 100 associates the sales data 201 with other related data stored in the traceability DB 110. Thereafter, the accounting support apparatus 100 checks whether or not the new sales data 201 is an abnormal value by the abnormal value check processing unit 103. In addition, when the abnormal value check is performed by the abnormal value check processing unit 103, the preset abnormal value check master 120 is referred to.

  In the abnormal value check processing unit 103, when new sales data 201 corresponds to the abnormal value check master 120, the new sales data 201 and related data are output as error data 130. The output error data 130 is displayed on the accounting support apparatus 100 (not necessarily displayed), and is transmitted to the sales system 211 that is the source of the error. The transmitted error data 130 is provided to the user of the sales system 211 by displaying it as an error confirmation screen.

  Further, the error data 130 output by the accounting support apparatus 100 can further check whether or not there is a relationship between the error data 130 using the error data related check unit 104. In addition to basic check items, such as comparing the difference in the amount of sales data 201 output as error data 130 in the error data related check unit 104, the user sets an original check item and executes check processing as appropriate. You may let them.

(Hardware configuration of accounting support device)
FIG. 3 is a block diagram illustrating a hardware configuration of the accounting support apparatus. In FIG. 3, the accounting support apparatus 100 includes a CPU (Central Processing Unit) 301, a ROM (Read-Only Memory) 302, a RAM (Random Access Memory) 303, a magnetic disk drive 304, a magnetic disk 305, and an optical disk. A drive 306, an optical disk 307, a communication I / F (Interface) 308, an input device 309, and an output device 310 are provided. Each component is connected by a bus 320.

  Here, the CPU 301 governs overall control of the accounting support apparatus 100. The ROM 302 stores various programs such as a boot program and an accounting support program. The RAM 303 is used as a work area for the CPU 301. The magnetic disk drive 304 controls the reading / writing of the data with respect to the magnetic disk 305 according to control of CPU301. The magnetic disk 305 stores data written under the control of the magnetic disk drive 304.

  The optical disk drive 306 controls the reading / writing of the data with respect to the optical disk 307 according to control of CPU301. The optical disk 307 stores data written under the control of the optical disk drive 306, and causes the computer to read data stored on the optical disk 307.

  The above-described magnetic disk 305 and optical disk 307 may be used as the traceability DB 110. However, if the environment in which data is stored in combination with other data is not preferred due to data confidentiality, the traceability DB 110 is used. A storage medium to be used may be prepared independently.

  A communication interface (hereinafter abbreviated as “I / F”) 308 is connected to a network 311 such as a LAN (Local Area Network), a WAN (Wide Area Network), and the Internet through a communication line, and the other via this network 311. Connected to other devices. The communication I / F 308 controls an internal interface with the network 311 and controls data input / output from an external device. For example, a modem or a LAN adapter may be employed as the communication I / F 308.

  The input device 309 receives input from the outside to the accounting support apparatus 100. Specific examples of the input device 309 include a keyboard and a mouse.

  In the case of a keyboard, for example, keys for inputting letters, numbers, various instructions and the like are provided, and data is input. Moreover, a touch panel type input pad or a numeric keypad may be used. In the case of a mouse, for example, the cursor is moved and a range is selected, or a window is moved and the size is changed. Further, a trackball or a joystick may be used as long as they have the same function as a pointing device.

  The output device 310 outputs error data 130 and related data output for specifying the cause of the error data 130. Specific examples of the output device 310 include a display and a printer.

  In the case of a display, for example, data such as a cursor, an icon or a tool box, a document, an image, and function information is displayed. Further, a CRT, a TFT liquid crystal display, a plasma display, or the like can be employed as this display. In the case of a printer, for example, image data and document data are printed. Further, a laser printer or an ink jet printer can be employed.

(Functional configuration of accounting support device)
FIG. 4 is a block diagram showing a functional configuration of the accounting support apparatus. The accounting support apparatus 100 includes an acquisition unit 401, an extraction unit 402, an association unit 403, a determination unit 404, an output unit 405, and a transmission unit 406. Specifically, the functions (acquisition unit 401 to transmission unit 406) serving as the control unit are, for example, a program stored in a storage device such as the ROM 302, RAM 303, magnetic disk 305, and optical disk 307 shown in FIG. The function is realized by executing the function or by the I / F 308.

  As illustrated in FIG. 4, the accounting support apparatus 100 can access the traceability DB 110. In addition, as described above, the traceability DB 110 includes slip data (for example, sales data 201) from the trading system 210 that accepts slip data representing sales transactions, and journal data that represents deposits and withdrawals for each business partner corresponding to the slip data. Journal data from an accounting system that accepts (for example, journal data 202) is stored.

  The acquisition unit 401 has a function of acquiring new slip data (hereinafter referred to as “one slip data”) from the trading system 210. In other words, when new slip data is stored in the traceability DB 110, the acquiring unit 401 acquires it as one slip data and uses it for the subsequent processing. The acquired slip data is stored in a storage area such as the RAM 303, the magnetic disk 305, and the optical disk 307.

  In addition, a function unit (not shown) that determines whether one piece of acquired slip data satisfies a predetermined format may be provided after the acquisition unit 401. By providing such a determination unit, data that does not satisfy the form as slip data can be excluded from the beginning as an error.

  The extraction unit 402 has a function of extracting predetermined data from the traceability DB 110. Specifically, as the first function, the extraction unit 402 extracts, from the traceability DB 110, journal data that has a common business partner with one slip data acquired by the acquisition unit 401. As the second function, the extraction unit 402 extracts, from the traceability DB 110, other slip data having a common unit of sales transaction and one slip data. The extraction result is stored in a storage area such as the RAM 303, the magnetic disk 305, and the optical disk 307.

  The associating unit 403 has a function of associating arbitrary data. Specifically, the associating unit 403 associates one slip data, the journal data extracted by the extracting unit 402, and other slip data. The association result is stored in a storage area such as the RAM 303, the magnetic disk 305, and the optical disk 307.

  The determination unit 404 has a function of determining whether one slip data is data that satisfies a predetermined condition. Specifically, the determination unit 404 determines whether the sales transaction represented by one slip data and the deposit / withdrawal represented by the journal data associated with the one slip data by the association unit 403 satisfy a predetermined relationship. To do. The determination result is stored in a storage area such as the RAM 303, the magnetic disk 305, and the optical disk 307. Note that the determination conditions by the determination unit 404 can be changed as appropriate.

  The output unit 405 has a function of outputting data associated by the associating unit 403 together with the determination result when the determining unit 404 determines that one slip data does not satisfy a predetermined condition. Specifically, the output unit 405 determines that the sales transaction represented by one slip data by the determination unit 404 and the deposit / withdrawal represented by the journal data associated with the one slip data by the association unit 403 satisfy a predetermined relationship. Only when it is determined, a series of determination results and related data (one slip data, other slip data, and journal data) are output.

  Examples of the output format by the output unit 405 include display on a display, print output to a printer, and transmission to an external device via a communication I / F 308. Alternatively, the data may be stored in a storage area such as the RAM 303, the magnetic disk 305, and the optical disk 307.

  The transmission unit 406 has a function of transmitting data from the accounting support apparatus 100 to each of the systems 210 and 220. Specifically, the transmitting unit 406 transmits the determination result output from the output unit 405, one slip data, journal data, and other slip data to the trading system 210 that stores the one slip data in the traceability DB 110. . That is, the transmission unit 406 has a role of notifying the error occurrence source of the error content when an error occurs.

  The accounting support apparatus 100 has a function of storing, in the traceability DB 110, aggregated data obtained by aggregating one piece of slip data, journal data, and other slip data associated by the association unit 403 in addition to the above-described function unit. You may prepare.

(Accounting support procedure)
FIG. 5 is a flowchart showing the procedure of the accounting support process. The flowchart of FIG. 5 shows a procedure for performing an error check on the slip data stored from the trading system 210 and outputting related data for identifying the cause of the error when an error occurs. Yes. By executing each process of FIG. 5, it is possible to detect the occurrence of an error due to the slip data at an early stage.

  In FIG. 5, the accounting support apparatus 100 first determines whether the acquisition unit 401 has acquired the slip data (step S <b> 501). When the slip data is stored in the traceability DB 110 from the trading system 210, the acquiring unit 401 acquires the stored slip data, and thus the determination in step S501 is linked to the processing of the trading system 210.

  In step S501, the process is on standby until the slip data is acquired (step S501: No loop). When the slip data is acquired (step S501: Yes), the accounting support apparatus 100 satisfies the predetermined format of the acquired slip data. Whether or not (step S502).

  If it is determined in step S502 that the slip data satisfies a predetermined format (step S502: Yes), the accounting support apparatus 100 extracts journal data in which the slip data and the business partner are common by the extraction unit 402 ( Step S503), slip data having the same unit for the slip data and the sales transaction is extracted (Step S504).

  Thereafter, the accounting support apparatus 100 associates the extracted data with the association unit 403. Then, the accounting support apparatus 100 determines whether or not the relationship between the slip data and the journal data is appropriate by the determination unit 404 (step S506). Whether or not the relationship between the slip data and the journal data is appropriate can be determined according to whether or not a preset condition is satisfied.

  If the relationship between the slip data and journal data is appropriate in step S506 (step S506: Yes), the accounting support apparatus 100 ends the series of processes as it is because no error has occurred. On the other hand, if the relationship between the slip data and the journal data is not appropriate (step S506: No), since an error has occurred, the accounting support apparatus 100 receives all the data associated in step S505 from the output unit 405. Output (step S507), and the series of processing ends.

  If it is determined in step S502 that the slip data does not satisfy the predetermined format (step S502: No), the accounting support apparatus 100 outputs a slip data format error (step S508), and a series of processes. Exit.

  As described above, the accounting support apparatus 100 according to the present embodiment starts a series of accounting support processing triggered by the storage of slip data used for accounting processing in the traceability DB 110, so that an error occurs at an early stage. Can be detected. Further, when newly storing the slip data, since the related data is extracted and associated, the cause of the error can be easily identified as compared with the conventional case even if an error occurs.

  Next, in the accounting support processing described above, specific examples of data storage in the traceability DB, error check, generation of error data, relevance check of the generated error data, and error notification to each sensor I will give a description. Further, in the following description, an execution example is given in which a procedure for realizing a function equivalent to the functions of FIGS. 4 and 5 is appropriately changed according to the implementation. That is, in practice, a function equivalent to the functions of FIGS. 4 and 5 can be realized by various procedures.

(Data storage processing in the traceability DB)
FIG. 6 is a flowchart showing a procedure of data storage processing in the traceability DB. The flowchart in FIG. 6 shows a procedure until the sales slip data acquired by the sales system 211 is stored in the traceability DB 110. That is, the execution subject is the sales system 211. Since the sales system 211 itself is a widely available system, a detailed description of the configuration is omitted.

  In the flowchart of FIG. 6, the sales system 211 first determines whether sales slip data has been acquired (step S601). In step S601, the system enters a standby state until the sales slip data is acquired (step S601: No loop). When the sales slip data is acquired (step S601: Yes), the sales system 211 stores the sales slip data that is correct as the sales system. Whether or not (step S602).

  If it is determined in step S602 that the sales slip data is not correct as the sales system (step S602: No), the sales system 211 returns to the processing in step S601 and remains in a standby state until the next sales slip data is acquired. Become.

  On the other hand, if it is determined in step S602 that the sales slip data is correct as the sales system (step S602: Yes), the sales system 211 stores the sales slip data in the sales slip data run (step S603). Thereafter, the sales system 211 refers to the accounting system 220 or the traceability DB 110 to determine whether or not data for cooperation with the accounting system 220 has been acquired (step S604).

  If it is determined in step S604 that the cooperation data has been acquired (step S604: Yes), the sales data stored in the sales slip data transaction and the cooperation data are stored in the traceability DB 110 as they are (step S606). Then, a series of processing is completed.

  On the other hand, if it is determined in step S604 that the cooperation data has not been acquired (step S604: No), the sales system 211 creates data for cooperation with the accounting system 220 (step S605), and then the sales slip. The sales data and the linkage data stored in the data transaction are stored in the traceability DB 110 (step S606), and the series of processes is terminated.

  As described above, in the case of the sales system 211 described with reference to FIG. 6, after preparing the data for cooperation for associating the sales slip data with the accounting system 220 (acquisition or creation), each data is transferred to the traceability DB 110. Storing.

  FIG. 7 is an explanatory diagram showing the front information stored in the traceability DB. In FIG. 7, each data stored in the traceability DB 110 from the trading system 210 is represented as front information. Therefore, in the case of the processing described with reference to the flowchart of FIG. 6, the sales slip is stored in the sales slip transaction 701 using the sales entry screen and then stored in the traceability DB 110.

  Similarly, when receivable application occurs, it is stored in the receivable application slip transaction 702 using the receivable application screen and then stored in the traceability DB 110. The front information stored in the traceability DB 110 is stored in association with the accounting information represented by the journal data 202 stored from the accounting system 220. As described in FIG. 6, the association process may use the data for cooperation, or may associate the front information with the transaction information or the transaction unit of the accounting information.

  FIG. 8 is an explanatory diagram showing a storage example of the traceability DB. As shown in FIG. 9, the traceability DB 110 associates the front information and the accounting information on a one-to-one basis. That is, the traceability DB 110 enables tracking (trace) from accounting information to front information.

  The traceability DB 11 does not need to reflect all the input data, and as a main item, the front information side may hold the slip item in the trading system 210 and the accounting information side hold the slip item in the accounting system 220. . The following items 801 to 804 represent the following categories, respectively.

Item 801: Origin Category that represents the origin system of the corresponding data Item 802: Attribute Category that represents the transaction attribute of the relevant data (what transaction) Item 803: Error Category that represents the result of the abnormal value check process (only when an error)
Item 804: Accounting acquisition Classification representing data linked to the accounting system

  FIG. 9 is an explanatory diagram showing the relationship between the traceability DB, the abnormal value check master, and error data. As shown in FIG. 9, the accounting support apparatus 100 compares the item 801: the source and the item 802: attribute in the front information stored in the traceability DB 110 with the abnormal value check master 120, and determines whether or not the abnormal value. Deciding. As the abnormal value check process as shown in FIG.

1. 1. Is the origin and business partner correct? 2. Whether the subject is the same as the deposit amount Is the partner course less than the previous month's sales amount?

  As described above, the determination result for the front information that does not satisfy each determination is extracted as error data 130. The determinations 1 to 3 may be selected from templates prepared in advance, or may be set by the user of the accounting support apparatus 100. Depending on what kind of judgment is set as the abnormal value check master 120, the priority and tendency of the front information extracted as the error data 130 may change. That is, it is possible to set an effective abnormal value check master 120 by making use of past accounting processing experience. In addition, depending on the items checked by the abnormal value check master 120, the items essential to the front information and the accounting information stored in the traceability DB 110 may change and may change as appropriate.

  Further, the accounting support apparatus 100 may output the extracted error data 130 as it is, but may further check the relation between the error data. Although the relationship is not necessarily identified by the relationship check between the error data, if the information for identifying the cause of the error is positively provided to the user of the accounting support apparatus 100, the accounting process Regardless of the level of proficiency, it is an easy-to-use device for various users.

  Therefore, the abnormal value check process using the abnormal value check master 120 described with reference to FIG. 9 and the error data relevance check process using the error data 130 will be described in detail below.

(Abnormal value check processing)
FIG. 10 is a flowchart showing the procedure of the abnormal value check process. FIG. 11 is an explanatory diagram showing a setting example of an abnormal value check master. The flowchart in FIG. 10 can check whether or not each front information stored in the traceability DB 110 has an abnormal value by using the abnormal value check master 120 illustrated in FIG.

  In FIG. 10, the accounting support apparatus 100 first reads out the check target data (any front information) from the traceability DB 110 (step S1001). Then, the accounting support apparatus 100 reads the check master based on the check target data (step S1002).

  As illustrated in FIG. 11, the abnormal value check master 120 includes a key part and check items. Journal entry pattern is set in the key part, and transaction auxiliary information such as department and business partner, check subject, range condition, etc. are set in the check item. In the example of FIG. Represents a category such as

Item 1101: Subject Subject of applicable data Item 1102: Standard subject Category of subject subject to check, own subject or counterpart subject Item 1103: Attribute Category indicating classification transaction attribute subject to check Item 1104: Value condition check Condition for value to be checked Item 1105: Summary condition Summary condition for value to be checked

  Returning to the description of FIG. 10, in the process of step S1002, the abnormal value check master 120 as described above is read. Then, the accounting support apparatus 100 first determines whether data exists in the check master (step S1003). If it is determined in step S1003 that data exists in the check master (step S1003: Yes), the transaction support apparatus 100 determines whether the data is check category = “1” (step S1004).

  If it is determined in step S1004 that the check category is not “1” (step S1004: No), the transaction support apparatus 100 proceeds to the process of step S1008 as it is. If it is determined in step S1003 that no data exists in the check master (step S1003: No), the process returns to step S1001.

  If it is determined in step S1004 that the check category = “1” (step S1004: Yes), the accounting support apparatus 100 determines whether the check master matches the generation source, department, and business partner of the traceability DB 110. Judgment is made (step S1005). If it is determined in step S1005 that the generation source, department, or business partner matches the check master (step S1005: Yes), the accounting support apparatus 100 proceeds to the process of step S1008 as it is.

  If it is determined in step S1005 that the origin, department, or business partner does not match the check master (step S1005: No), the accounting support apparatus 100 stores data (here, front information) stored in the traceability DB 110. Is written out as error data 130 (step S1006), and an error flag is set in the traceability DB 110 (step S1007).

  Thereafter, the accounting support apparatus 100 determines whether or not the data is check category = “2” (step S1008). If it is determined in step S1008 that the check category is not “2” (step S1008: No), the transaction support apparatus 100 proceeds to the process of step S1012 as it is. If it is determined in step S1008 that the check category = “2” (step S1008: Yes), the accounting support apparatus 100 determines whether or not the front information matches the generation amount of the attribute journal (step S1009). ). If it is determined in step S1009 that the front information matches the generated amount of attribute journal entry (step S1009: Yes), the transaction support apparatus 100 proceeds to the process of step S1012 as it is.

  If it is determined in step S1009 that the front information does not match the amount of occurrence of the attribute journal entry (step S1009: No), the accounting support apparatus 100 writes the data of the own journal entry and the check target journal entry as error data 130 (step S1009). Further, an error flag is set in the traceability DB 110 (S1010).

  Thereafter, the accounting support apparatus 100 determines whether or not the data is check category = “3” (step S1012). In step S1012, when it is determined that the check classification = “3” is not satisfied (step S1012: No), the transaction support apparatus 100 proceeds to the process of step S1017 as it is. In step S1012, when it is determined that the check category = “3” (step S1012: Yes), the accounting support apparatus 100 extracts from the traceability DB 110 the attribute journal of the previous month with the same business partner and department (step S1013). ), It is determined whether or not it matches the amount generated in the previous month of the attribute journal (step S1014). In step S1014, when it is determined that the previous month's generation amount of the attribute journal matches (step S1014: Yes), the transaction support apparatus 100 proceeds to the process of step S1017 as it is.

  In step S1014, when it is determined that the amount does not match the previous month generation amount of the attribute journal (step S1014: No), the accounting support apparatus 100 writes out the data of the self journal and the check target journal as error data 130 (step S1015). Further, an error flag is set in the traceability DB 110 (step S1016).

  Thereafter, the accounting support apparatus 100 determines whether there is target data (step S1017). If there is target data (step S1017: Yes), the process returns to step S1001 and repeats the same process. If there is no target data (step S1017: No), a series of processing is ended as it is.

  Thereafter, the accounting support apparatus 100 determines whether there is target data (step S1017). If there is target data (step S1017: Yes), the process returns to step S1001 and repeats the same process. If there is no target data (step S1017: No), a series of processing is ended as it is.

  FIG. 12 is an explanatory diagram of an example of generating error data. By executing the processing described with reference to FIG. 11, error data 130 as shown in FIG. 12 is generated. The configuration of the error data 130 basically depends on the configuration of the front information in which the error has occurred, but represents an item 1201 for determining whether the error is generated from its own data or other data, and the error content. An item 1202 is added. The item 1201 of the error data 130 is used for error data relevance check processing described below.

(Error data relevance check process)
FIG. 13 is a flowchart illustrating a procedure of error data relevance check processing. In FIG. 13, the accounting support apparatus 100 first reads the error code of the category [O] from the error data 130 (Step S1301), and then reads the error code of the next category [O] (Step S1302). ), It is determined whether or not the difference is the same (step S1303).

  If it is determined in step S1303 that the difference is the same (step S1303: Yes), the accounting support apparatus 100 writes that the difference is the same in the error code (step S1304), and performs the processing in step S1305. Transition. On the other hand, when it is determined that the difference does not match (step S1303: No), the transaction support apparatus 100 proceeds to the process of step S1305 as it is.

  Thereafter, the accounting support apparatus 100 determines whether or not any error check determined by the user or the designer is satisfied (step S1305). If it is determined in step S1305 that the specified error check is satisfied (step S1305: Yes), the accounting support apparatus 100 writes the check content into an error code (step S1306), and proceeds to the processing of step S1307. On the other hand, if it is determined that it does not correspond to any error check (step S1305: No), the transaction support apparatus 100 proceeds to the process of step S1307 as it is.

  Thereafter, the accounting support apparatus 100 determines whether or not there is unprocessed data (step S1307). If there is unprocessed data (step S1307: Yes), the process returns to the process of step S1301 and the unprocessed data is processed. The same processing is performed on the data. Thereafter, when it is determined that there is no unprocessed data (step S1307: No), the accounting support apparatus 100 ends the series of processes.

(Error notification processing)
FIG. 14 is a flowchart illustrating a procedure of error notification processing. The flowchart of FIG. 14 shows a procedure until the accounting support apparatus 100 notifies the error data generated by the abnormal value check process to the system that has generated the error. By executing each process of FIG. 14, it is possible to confirm whether or not the contents of the error data generated for the user of the system that has become the error generation source can be notified.

  In the following description, an error notification process when an error occurs due to the sales data 201 input from the sales system 210 will be described. In FIG. 14, the accounting support apparatus 100 first reads data for the sales system from the error data, and instructs the accounting system 210 to display a screen (step S1401).

  Here, FIG. 15 is an explanatory diagram showing an example of a system error notification. When a screen display instruction is issued in step S1401, a system error notification table such as the data table 1500 in FIG. 15 is displayed on the display screen. In the data table 1500, five pieces of error data are displayed. When error data to be referred to in detail is selected, related data is displayed in order to grasp the error contents.

  Further, the data table 1500 represents a state in which the error data relevance check process described with reference to FIG. 13 is being performed. That is, the description on the sixth line of the data table 1500 corresponds to the check result of the error data relevance check process.

  Returning to the description of FIG. 14, the accounting support apparatus 100 confirms the OK flag of the error data when the [Confirm] button is pressed in the accounting system 210 (step S1402). Thereafter, the accounting support apparatus 100 determines whether or not the OK flag confirmed in step S1402 is OFF (step S1403). In step S1403, when it is determined that the OK flag is not OFF (step S1403: No), the accounting support apparatus 100 sets the corresponding data stored in the traceability DB 110, that is, the OK flag is ON. The error flag of the error data is cleared (step S1404).

  Then, the accounting support apparatus 100 reflects the processing in step S1404 in the journal data 202 input from the accounting system 220 in order to perform the accounting linkage processing by the accounting system linkage processing unit 102 (step S1405). Thereafter, the accounting support apparatus 100 deletes the error data processed in step S1404 from the error data (step S1406).

  When the processing of the target error data is completed in step S1406, the accounting support apparatus 100 returns to the processing of step S1401 and performs the same processing for the other error data. Then, the accounting support apparatus 100 repeats the processing of steps S1401 to S1406 (step S1403: No loop) until the OK flag becomes OPFF in step S1403, triggered by the fact that the OK flag is turned off (step S1403). In step S1403: Yes), a series of processing ends.

  As described above, according to the disclosed technique, when new slip data is stored in the database 110, new slip data is associated with stored slip data and related accounting data. Is called. Furthermore, an error check is performed on the new slip data. Therefore, when an error has occurred, the error can be detected at an early stage, and the related data is linked, so that the cause of the error can be identified.

  Further, in the disclosed technology, when an error occurs, a function of transmitting slip data related to the occurrence of the error to a system that stores the slip data that has triggered the occurrence of the error may be provided. As a result, related data is sent immediately to the system that caused the error, so the same slip data is stored to prevent the next error from occurring and the cause of the error can be identified efficiently. Can be expected.

  In addition, the disclosed technology may have a function of collecting related data associated with newly stored data and storing it in the database 110. The slip data stored from each system may include items that are not used for actual accounting processing as they are. Therefore, the data reading speed can be expected to be reduced by reducing the amount of data and consolidating related data including a plurality of data into one data.

  Further, in the disclosed technology, a determination is made as to whether or not newly stored slip data satisfies a predetermined format, and an association process is performed only for data satisfying the predetermined format. Also good. As a result, if the slip data clearly causes an error, the error is immediately notified to the storage source system without performing the associating process. As a result, the frequency of occurrence of the error is pushed. be able to.

  Further, in the disclosed technique, the user can arbitrarily set a condition for determining whether or not the newly stored slip data causes an error. Therefore, the tendency of accounting processing according to the system and the rule of thumb and proficiency of accounting processing by the user can be utilized for efficient error checking and extraction of related data.

  The accounting support method described in this embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. The accounting support program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read from the recording medium by the computer. The accounting support program may be distributed via a network such as the Internet.

  The following additional notes are disclosed with respect to the embodiment described above.

(Additional remark 1) The said slip data from the trading system which receives the slip data showing a trading transaction, and the said journal data from the accounting system which receives the journal data showing the deposit or withdrawal for every customer corresponding to the said slip data are stored. On a computer that has access to the database
An acquisition step of acquiring one slip data from the trading system;
A first extraction step for extracting journal data common to a customer and one slip data acquired in the acquisition step from the database;
A second extraction step for extracting, from the database, the other slip data in which the unit of the sales transaction is common with the one slip data;
Associating the one slip data with the journal data extracted by the first and second extraction steps and other slip data;
A determination step of determining whether the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data associated with the one slip data by the association step satisfy a predetermined relationship;
An output step of outputting the one slip data, the journal data and the other slip data associated by the association step when it is determined by the determination step that the predetermined relationship is not satisfied;
An accounting support program characterized by having

(Supplementary Note 2) The transmission step of transmitting the one slip data, the journal data, and the other slip data output by the output step to the trading system storing the one slip data in the database, The accounting support program according to appendix 1, which is executed by a computer.

(Additional remark 3) Let the said computer perform the storage process which stores the aggregate data which aggregated said one slip data, the said journal data, and said other slip data by the said correlation process in the said database,
In the output step, when it is determined by the determination step that the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data do not satisfy a predetermined relationship, the storage step stored in the storage step The accounting support program according to appendix 1 or 2, characterized by outputting aggregated data.

(Additional remark 4) Let the said computer perform the format determination process of determining whether one slip data acquired by the said acquisition means satisfy | fills the predetermined format,
In the first extracting step, when it is determined in the format determining step that the one slip data satisfies a predetermined format, the transaction is performed with the one slip data acquired by the acquiring step from the database. The accounting support program according to any one of appendices 1 to 3, wherein journal data having a common destination is extracted.

(Supplementary Note 5) In the transmission step, when it is determined in the format determination step that the one slip data does not satisfy a predetermined format, the one slip is stored in the trading system storing the one slip data. The accounting support program according to appendix 4, wherein an error notification about data is transmitted.

(Supplementary Note 6) When it is determined by the determining step that the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data do not satisfy a predetermined relationship, the one associated by the association step And causing the computer to execute a correlation determination step of determining whether or not the amounts represented by the slip data, the journal data, and the other slip data are correlated,
The accounting support program according to any one of appendices 1 to 4, wherein in the output step, a determination result in the correlation determination step is output.

(Additional remark 7) The said slip data from the trading system which receives the slip data showing a trading transaction, and the said journal data from the accounting system which receives the journal data showing the deposit / withdrawal for every customer corresponding to the said slip data are stored An accounting support device that can access a database to be
Obtaining means for obtaining one slip data from the trading system;
A first extraction unit for extracting journal data common to a customer and one slip data acquired by the acquisition unit from the database;
A second extraction means for extracting, from the database, the other slip data in which the unit of the sales transaction is common with the one slip data;
Association means for associating the one slip data with the journal data extracted by the first and second extraction means and other slip data;
Judgment means for judging whether the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data associated with the one slip data by the association means satisfy a predetermined relationship;
An output unit that outputs the one slip data, the journal data, and the other slip data associated by the association unit when the determination unit determines that the predetermined relationship is not satisfied;
An accounting support apparatus comprising:

(Additional remark 8) The said slip data from the trading system which receives the slip data showing a trading transaction, and the said journal data from the accounting system which receives the journal data showing the deposit / withdrawal for every customer corresponding to the said slip data are stored. A computer that can access the database
An acquisition step of acquiring one slip data from the trading system;
A first extraction step for extracting journal data common to a customer and one slip data acquired in the acquisition step from the database;
A second extraction step for extracting, from the database, the other slip data having the same unit of the sales transaction as the one slip data;
Associating the one slip data with the journal data extracted by the first and second extraction steps and other slip data;
A determination step of determining whether the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data associated with the one slip data by the association step satisfy a predetermined relationship;
An output step of outputting the one slip data, the journal data and the other slip data associated by the association step when it is determined by the determination step that the predetermined relationship is not satisfied;
An accounting support method characterized by executing

100 Accounting support device 110 Database (traceability DB)
210 Trading System 211 Sales System 212 Purchasing System 220 Accounting System 401 Acquisition Unit 402 Extraction Unit 403 Association Unit 404 Judgment Unit 405 Output Unit 406 Transmitter

Claims (7)

Access to the database storing the slip data from the trading system that accepts slip data representing sales transactions, and the journal data from the accounting system that accepts journal data representing deposits and withdrawals for each business partner corresponding to the slip data On a possible computer,
An acquisition step of acquiring one slip data from the trading system;
A first extraction step for extracting journal data common to a customer and one slip data acquired in the acquisition step from the database;
A second extraction step for extracting, from the database, the other slip data in which the unit of the sales transaction is common with the one slip data;
Associating the one slip data with the journal data extracted by the first and second extraction steps and other slip data;
A determination step of determining whether the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data associated with the one slip data by the association step satisfy a predetermined relationship;
An output step of outputting the one slip data, the journal data and the other slip data associated by the association step when it is determined by the determination step that the predetermined relationship is not satisfied;
An accounting support program characterized by having   Causing the computer to execute a transmission step of transmitting the one slip data, the journal data, and the other slip data output by the output step to the trading system storing the one slip data in the database. The accounting support program according to claim 1. Causing the computer to execute a storing step of storing in the database aggregated data obtained by aggregating the one slip data, the journal data, and the other slip data associated by the associating step;
In the output step, when it is determined by the determination step that the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data do not satisfy a predetermined relationship, the storage step stored in the storage step The accounting support program according to claim 1 or 2, wherein the aggregated data is output. Causing the computer to execute a format determination step of determining whether one slip data acquired by the acquisition means satisfies a predetermined format;
In the first extracting step, when it is determined in the format determining step that the one slip data satisfies a predetermined format, the transaction is performed with the one slip data acquired by the acquiring step from the database. The accounting support program according to any one of claims 1 to 3, wherein journal data having a common destination is extracted. If it is determined by the determining step that the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data do not satisfy a predetermined relationship, the one slip data associated by the association step; Causing the computer to execute a correlation determination step of determining whether or not there is a correlation between the amount of money represented by the journal data and the other slip data;
5. The accounting support program according to claim 1, wherein in the output step, a determination result in the correlation determination step is output. Access to the database storing the slip data from the trading system that accepts slip data representing sales transactions, and the journal data from the accounting system that accepts journal data representing deposits and withdrawals for each business partner corresponding to the slip data A possible accounting support device,
Obtaining means for obtaining one slip data from the trading system;
A first extraction unit for extracting journal data common to a customer and one slip data acquired by the acquisition unit from the database;
A second extraction means for extracting, from the database, the other slip data in which the unit of the sales transaction is common with the one slip data;
Association means for associating the one slip data with the journal data extracted by the first and second extraction means and other slip data;
Judgment means for judging whether the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data associated with the one slip data by the association means satisfy a predetermined relationship;
An output unit that outputs the one slip data, the journal data, and the other slip data associated by the association unit when the determination unit determines that the predetermined relationship is not satisfied;
An accounting support apparatus comprising: Access to the database storing the slip data from the trading system that accepts slip data representing sales transactions, and the journal data from the accounting system that accepts journal data representing deposits and withdrawals for each business partner corresponding to the slip data Computer
An acquisition step of acquiring one slip data from the trading system;
A first extraction step for extracting journal data common to a customer and one slip data acquired in the acquisition step from the database;
A second extraction step for extracting, from the database, the other slip data having the same unit of the sales transaction as the one slip data;
Associating the one slip data with the journal data extracted by the first and second extraction steps and other slip data;
A determination step of determining whether the sales transaction represented by the one slip data and the deposit / withdrawal represented by the journal data associated with the one slip data by the association step satisfy a predetermined relationship;
An output step of outputting the one slip data, the journal data and the other slip data associated by the association step when it is determined by the determination step that the predetermined relationship is not satisfied;
An accounting support method characterized by executing

Images