Business support device, business support method, and business support program

Abstract

To provide a business support device, a business support method, and a business support program that reduce a burden of journal entry input work.SOLUTION: A display control unit displays a journal input screen on a display unit for performing a journal input. A determination unit determines whether or not to input a business-place to the journal input screen. A head / branch office journal generation unit generates, when obtaining a determination result indicating that a debit business-place or a credit business-place has been input, head / branch office journal detail data for journal contents corresponding to the journal input information input to the journal input screen. In addition, the journal detail generation unit generates, when obtaining a determination result indicating that there is no business-place input, on the basis of the journal input information input to the journal input screen, journal detail data equivalent to a regular voucher for an own business-place. On the other hand, the journal detail generation unit generates, when the determination result indicates that the debit business-place or the credit business-place has been input, a journal voucher for each business-place, namely, journal detail data in which an allocation business-place is identification information of the own business-place, and journal detail data in which identification information of another business-place that is a trading partner of the own business-place is an allocation business-place.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a business support device, a business support method, and a business support program. [Background technology]

[0002] Patent document 1 (JP 2020-160823 A) discloses a journal entry creation device that creates internal management accounting journal entries for labor costs related to the manufacture of products between business locations at the appropriate time and without requiring the operator's effort.

[0003] This journal entry creation device is equipped with a control unit that creates management accounting journal entries for sales and purchases between business locations within a company that has multiple business locations and adopts an independent accounting system. This journal entry creation device has a predetermined screen for inputting information about manufactured products, and the quantity of the product, the production line on which the product was manufactured, and the business location that is the recipient of labor costs related to the manufacture of the product from the perspective of the business location that manufactured the product, are input.

[0004] When this input is made, the control unit functions as a labor cost journal creation means, and calculates the labor cost based on the labor cost unit price set for the input production line and the input quantity.The labor cost journal creation means then creates a journal entry for the purchase and sale of labor costs between business establishments based on the calculated labor cost, the input business establishment, and the business establishment that manufactured the preset product. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2020-160823 Summary of the Invention [Problem to be solved by the invention]

[0006] Nowadays, the journal entry input work is a burden for the person in charge, and therefore, there is a demand for the development of a device that can reduce the burden of the journal entry input work on the person in charge.

[0007] The present invention has been made in view of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that can reduce the burden of journal entry input work. [Means for solving the problem]

[0008] The business support device according to the present invention is a business support device that supports journal entry work for transactions between business establishments, and in order to solve the above-mentioned problems and achieve the object, the business support device includes a display control unit that displays a journal entry screen for performing journal entry on a display unit, a determination unit that determines whether or not a business establishment has been entered on the journal entry screen, a head office / branch journal entry generation unit that generates head office / branch journal entry detail data of the journal entry content corresponding to the journal entry information entered on the journal entry screen and stores the data in a head office / branch journal entry detail data storage unit when a determination result indicating that a debit business establishment or a credit business establishment has been entered is obtained, and If the determination result indicates that there is no such business, the journal entry detail generation unit generates journal entry detail data equivalent to a normal voucher for the business office based on the journal entry information entered on the journal entry input screen and stores the journal entry detail data storage unit; if the determination result indicates that a debit business office or a credit business office has been entered, the journal entry detail generation unit generates journal entry detail data for each business office, with the recording business office as the identification information for the business office, and with the identification information of another business office that is a trading partner of the business office as the recording business office, and stores the journal entry detail data storage unit.

[0009] Furthermore, the business support method according to the present invention is a business support method for supporting journal entry work for transactions between business establishments, and in order to solve the above-mentioned problems and achieve the object, the method includes a display control step in which a display control unit displays a journal entry input screen for performing journal entry input on a display unit, a determination step in which a determination unit determines whether or not a business establishment has been entered on the journal entry input screen, and a head office / branch journal entry generation step in which, when a determination result indicating that a debit business establishment or a credit business establishment has been entered is obtained, a head office / branch journal entry generation step in which a head office / branch journal entry detail data of the journal entry content corresponding to the journal entry information entered on the journal entry input screen is generated and stored in a head office / branch journal entry detail data storage unit. and a journal entry detail generation step in which, if the journal entry detail generation unit obtains a determination result indicating that no business establishment input has been made, it generates journal entry detail data equivalent to a normal voucher for its own business establishment based on the journal entry information entered on the journal entry screen and stores the generated journal entry detail data in the journal entry detail data storage unit, and, if the determination result indicates that a debit business establishment or a credit business establishment has been made, it generates journal entry detail data, which are journal entry vouchers for each business establishment, with the recording business establishment as identification information for the own business establishment and with identification information for another business establishment that is a trading partner of the own business establishment as the recording business establishment, and stores the generated journal entry detail data in the journal entry detail data storage unit.

[0010] Furthermore, the business support program of the present invention is a business support program that causes a computer of a business support device to function to support journal entry work for transactions between business establishments, and in order to solve the above-mentioned problems and achieve the object, the business support program includes a display control unit that displays a journal entry screen for performing journal entry on a display unit, a discrimination unit that determines whether or not a business establishment has been entered on the journal entry screen, and when a discrimination result indicating that a debit business establishment or a credit business establishment has been entered is obtained, generates head office / branch journal entry detail data of the journal entry content corresponding to the journal entry information entered on the journal entry screen and stores the generated data in a head office / branch journal entry detail data storage unit. and if a determination result indicates that there is no business office input, generates journal entry detail data equivalent to a normal voucher for the own business office based on the journal entry information entered on the journal entry input screen and stores it in the journal entry detail data storage unit, and if a determination result indicates that a debit business office or a credit business office has been entered, generates journal entry detail data for each business office, which are journal entry vouchers, with the recording business office as the identification information of the own business office and journal entry detail data with the identification information of another business office that is a trading partner of the own business office as the recording business office, and stores them in the journal entry detail data storage unit. [Effects of the Invention]

[0011] The present invention can reduce the burden of journal entry input work. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing an example of a journal entry system to which the present invention is expected to be applied. [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of a business support device according to an embodiment, and a journalization system including the business support device. [Figure 3] FIG. 3 is a diagram showing the overall flow of operations related to journalization in a journalization system including a business support device according to an embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a journal entry input screen for explaining an example in which a new journal entry slip for an expense transfer between the Yokohama office and the Tokyo office is created at the Tokyo office. [Figure 5] FIG. 5 is a diagram showing an example of newly issued head office / branch office journal entry detail data. [Figure 6] FIG. 6 is a diagram showing an example of a head office / branch account item master that is referenced on the journal entry input screen when the business establishment and the creditor business establishment are different. [Figure 7] FIG. 7 is a diagram showing an example of detailed journal entry data for each business establishment newly issued based on the head office / branch office detailed journal entry data. [Figure 8] FIG. 8 is a diagram showing an example of a journal inquiry screen displayed on the Yokohama office terminal device. [Figure 9] FIG. 9 is a diagram showing how journal vouchers for the Yokohama office are detected from the journal book of the server device when a journal voucher for the Yokohama office is inquired about at the Yokohama office. [Figure 10] FIG. 10 is a diagram showing how the head office / branch office voucher of the Tokyo office, which is the source of the journal voucher of the Yokohama office, is detected from the journal book of the server device. [Figure 11] FIG. 11 is a diagram showing how the head office / branch office voucher of the Tokyo office, which was the source of the journal entry voucher of the Yokohama office, is inquired at the Yokohama office terminal device. [Figure 12] FIG. 12 is a diagram showing the state in which journal entry detail data with an approval status of "application (in progress)" is displayed on the approver terminal device of the intermediate approver in the Tokyo office. [Figure 13] FIG. 13 is a diagram showing how head office / branch office journal entry detail data with an approval status of "application (in progress)" is displayed on the approver terminal device of the intermediate approver at the Tokyo office. [Figure 14] FIG. 14 is a diagram showing an example of head office / branch office journal entry detail data after interim approval. [Figure 15] FIG. 15 is a diagram showing an example of journal entry detail data after interim approval. [Figure 16] FIG. 16 is a diagram showing an example of head office / branch office journal entry detail data after final approval. [Figure 17] FIG. 17 is a diagram showing an example of journal entry detail data after final approval. [Figure 18]FIG. 18 is a diagram illustrating the process of issuing a regular slip in the business support system according to the embodiment. [Figure 19] FIG. 19 is a diagram showing how the processing category to be entered into the journal entry history data is detected from the new registration processing category storage unit when a new regular slip is created. [Figure 20] FIG. 20 is a diagram showing how head office / branch journal data is not generated when a normal slip is issued. [Figure 21] FIG. 21 is a diagram showing an example of detailed journal entry data generated when a regular slip is issued. [Figure 22] FIG. 22 is a diagram showing an example of journal entry history data generated when a regular slip is issued. [Figure 23] FIG. 23 is a diagram showing an example of correction input on the journal entry input screen for explaining the operation of correcting a normal voucher to a head office / branch voucher. [Figure 24] FIG. 24 is a diagram showing an example of a correction registration processing classification storage unit that stores processing classifications to be included in journal entry history data when a normal voucher is corrected to a head office / branch office voucher. [Figure 25] FIG. 25 is a diagram showing the business establishment and slip number acquired from the journal entry detail data before correction when a regular slip is corrected to a head office / branch office slip. [Figure 26] Figure 26 shows the business establishments that exist before and after the correction, the voucher number to be used, and the processing classification to be included in the journal entry history data before and after the correction, which are detected when a regular voucher is corrected to a head office / branch voucher. [Figure 27] FIG. 27 is a diagram showing an example of head office / branch office detail data generated in response to the correction of a regular slip to a head office / branch office slip. [Figure 28] FIG. 28 is a diagram showing an example of detailed journal entry data generated in response to the correction of a regular voucher to a head office / branch office voucher. [Figure 29] FIG. 29 is a diagram showing an example of journal entry history data generated in response to the correction of a regular voucher to a head office / branch office voucher. [Figure 30]FIG. 30 shows an example in which the business establishment with which the Tokyo business establishment conducted a transaction has been changed from "Osaka business establishment" to "Yokohama business establishment." [Figure 31] FIG. 31 is a diagram showing a list of business establishments that exist in the journal entry detail data before the business establishment with which the Tokyo business establishment conducted transactions was changed from "Osaka business establishment" to "Yokohama business establishment." [Figure 32] Figure 32 shows the business offices that existed before and after the correction, the document number to be used, and the processing classification to be included in the journal entry history data before and after the correction, which are detected when the business office with which the Tokyo business office conducted a transaction is corrected from "Osaka business office" to "Yokohama business office." [Figure 33] FIG. 33 is a diagram showing an example of head office / branch office journal entry detail data that is generated by correcting the office with which the Tokyo office conducted a transaction from "Osaka office" to "Yokohama office." [Figure 34] FIG. 34 is a diagram showing an example of detailed journal entry data that is generated by changing the business establishment with which the Tokyo business establishment has made a transaction from "Osaka business establishment" to "Yokohama business establishment." [Figure 35] FIG. 35 is a diagram showing an example of journal entry history data that is generated by changing the establishment with which the Tokyo establishment conducted a transaction from "Osaka establishment" to "Yokohama establishment." [Figure 36] FIG. 36 shows an example in which a head office / branch office slip is deleted. [Figure 37] FIG. 37 is a diagram showing a state in which the head office / branch account journal entry detail data corresponding to the deletion operation of the head office / branch account slip has been deleted from the head office / branch account journal entry detail data storage unit. [Figure 38] FIG. 38 is a diagram showing a state in which the journal entry detail data corresponding to the deletion operation of the head office / branch office slip has been deleted from the journal entry detail data storage unit. [Figure 39] FIG. 39 is a diagram showing journal entry history data corresponding to a deletion operation of a head office / branch office slip. [Figure 40] FIG. 40 is a diagram showing a deletion registration processing classification storage unit that stores processing classifications to be included in journal entry history data, which are referenced when a slip is deleted. [Figure 41]FIG. 41 is a diagram for explaining an example of a query on journal entry history data for the Tokyo office. [Figure 42] FIG. 42 is a diagram for explaining an example of a query on journal entry history data for the Yokohama office. DETAILED DESCRIPTION OF THE INVENTION

[0013] (overview) For companies that use head office / branch accounting, when there is a transaction between business locations, journal entries must be recorded for each business location. Because separate entries are issued, there is a possibility of discrepancies between the head office accounts and each branch account, which creates the hassle of checking and correcting at the time of closing the books. Note that "transactions" between business locations are a concept that includes not only "commercial transactions" between business locations, but also "transfers of expense burdens." For example, it is a concept that includes transactions such as transferring "advertising expenses," which are expenses paid to external business partners, from the Tokyo business location to the Yokohama business location.

[0014] In order to reduce the frequency of discrepancies between accounts at the head office and branches and to reduce the effort required for confirmation and correction, many companies operate in a way that journal entries for each branch are recorded and approved only at the branch that receives the supporting documents that form the basis of the document. In other words, for example, when data is entered at the head office, it is not registered at other branches, and only the document issued at the head office is confirmed and communication with the head office is made outside the system.

[0015] Here, the applicant of the present invention has disclosed in Patent No. 6753709 (Patent Application No. 2016-131051) a head office / branch journal entry input device, a head office / branch journal entry input method, and a head office / branch journal entry input program that attempt to solve such problems.

[0016] The head office / branch journal entry input device, head office / branch journal entry input method, and head office / branch journal entry input program of Patent No. 6753709 provide head office / branch vouchers and automatically create regular journal entry vouchers for each business location, making the format of the vouchers easy to input and check. In addition, the head office / branch journal entry input device, head office / branch journal entry input method, and head office / branch journal entry input program of Patent Application No. 2016-131051 set the same voucher number in the summary information of vouchers for each business location, thereby making each voucher related and simplifying searches.

[0017] However, in the case of the head office / branch journal entry input device, head office / branch journal entry input method, and head office / branch journal entry input program of Patent No. 6753709, the normal journal entry input screen and the head office / branch journal entry input screen are separate screens, which means that before issuing the document, the person in charge must determine whether the transaction is between organizations or between business locations, and then switch input screens depending on the content of the document to enter the journal entry, which can be time-consuming and can make the work complicated.

[0018] In addition, when making corrections between regular journal entries and head office / branch journal entries, it is necessary to register the information on both screens. Also, when new slip numbers are assigned, it becomes difficult to check the correction history later.

[0019] The business receiving the transfer can check the input contents based on the journal, but if the input contents differ from what was recognized in advance, the journal data recorded in the journal cannot be changed after approval is complete, which means that unnecessary red and black vouchers must be issued, making operations cumbersome.

[0020] Furthermore, the head office / branch account journal entry input device, head office / branch account journal entry input method, and head office / branch account journal entry input program in Patent No. 6753709 made it possible to recognize related documents from text information by updating the same document number in the summary information of the transfer destination and transfer source documents, but did not associate regular documents by business location with head office / branch account documents.As a result, when a transfer was received, if one wanted to check the status of the regular documents at the time of input (head office / branch account documents) after checking the regular documents by business location, it was necessary to launch the input screen and the form for head office / branch account documents again, and search for and check the head office / branch account documents.

[0021] For this reason, the applicant of the present invention has conducted further research and development into the head office / branch office journal entry input device, head office / branch office journal entry input method, and head office / branch office journal entry input program of Patent No. 6753709. As a result, the applicant has come up with the present invention, which is useful for supporting journal entry work, and hereby discloses it.

[0022] Figure 1 shows an example of a journal entry system to which the present invention is expected to be applied. As shown in this figure, the present invention realizes both normal journal entry input and journal entry input for head office and branch accounting on a single input screen. In addition, immediately after invoicing, vouchers for all business locations are recorded and approvals are made simultaneously.

[0023] In addition to the input office of the voucher, there are input fields for the debit office and the credit office in the details section of the voucher, so that transactions within one's own office and transactions between offices can be entered on the same screen. If there is no input in the details section office, the voucher is treated as a regular voucher recorded only in the input office, but if there is input in the details section office, it is judged as a voucher to be recorded in the details section office, that is, a head office / branch voucher (a voucher for transactions between offices).

[0024] In addition, the system uses a slip format (head office / branch slip) that is easy to input and check, and regular slips for each business location are automatically created. At the time of issuing the head office / branch slip, the slips for each business location are also updated to the application status (unapproved status). This makes it possible to check slips, including unapproved ones, immediately after input in the journal.

[0025] In addition, by assigning the same approval key to head office / branch invoices and regular invoices, approval is carried out simultaneously for all recorded invoices, making it possible to always match the approval status of head office / branch invoices and regular invoices for each business location.

[0026] In addition, it is possible to register regular vouchers and head office / branch office vouchers on one screen, and it is also possible to change regular vouchers to head office / branch office vouchers, and to change head office / branch office vouchers to regular vouchers.

[0027] In addition, when updating the history at the time of correction, the system assigns new voucher numbers to regular vouchers for each business location only for the new business location, and uses the pre-correction voucher numbers for existing business locations, thereby maintaining the historical voucher numbers and making it possible to track the change history of automatically created regular vouchers for each business location.This process is carried out based on the results of a comparison of the journal entry detail data before correction and the update schedule data after correction, as will be described later.

[0028] In addition, the registration or update history for transfer receiving business offices (business offices other than the input business office) is updated in a separate processing category so that it is possible to recognize that the update is due to the addition, correction, or deletion of head office / branch slips.

[0029] In addition, by assigning the document number of the head office / branch document as a subdocument number to regular documents for each business location, it is possible to transition between screens for regular documents and head office / branch documents. In other words, it is possible to easily search for and display head office / branch documents from regular documents for each business location. Furthermore, when transitioning from the journal to the journal entry screen, if it is a head office / branch document (if head office / branch journal entry detail data is available), it is displayed in the layout of the head office / branch document at the time of entry, making it easy to check the head office / branch document.

[0030] (System Configuration) A business support device according to an embodiment of the present invention will be described below. This business support device functions on the journal entry system shown in Fig. 1. That is, the journal entry system shown in Fig. 1 is configured with the business support device 1 according to the embodiment, an approver terminal device 51, a server device 53, and a Yokohama office terminal device 54.

[0031] The business support device 1, approver terminal device 51, server device 53, and Yokohama office terminal device 54 are owned by the same company. The approver terminal device 51 is connected to the business support device 1 via a private network 50 such as a LAN (Local Area Network) so that they can communicate with each other. The approver terminal device 51 approves journal vouchers created by the business support device 1.

[0032] The server device 53 is connected to the business support device 1 via a wide area network 52 such as the Internet. The server device 53 is equipped with a journal memory unit 55 and a journal history memory unit 56 that store head office / branch slips, regular slips by business location, and slip history sent from the business support device 1, for example, when a slip inquiry is made from another business location. When a slip inquiry is made, the server device 53 inquires about the slip or slip history transferred from the business support device 1 and stored in the journal memory unit 55 or journal history memory unit 56 at a terminal device of the other business location.

[0033] The Yokohama office terminal device 54 is a terminal device provided at the Yokohama office, which is an example of an office, and is connected to the wide area network 52 together with the server device 53. Although not shown, it should be understood that in addition to the Yokohama office terminal device 54, terminal devices at each of the base offices, such as the Osaka office or the Fukuoka office, are also connected to this journal entry recording system.

[0034] (Hardware configuration of business support device) Next, as shown in FIG. 2, the business support device 1 of the embodiment provided in such a journal entry recording system includes a memory unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function. The communication interface unit 4 is connected to a network, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0035] A storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used as the storage unit 2. The storage unit 2 stores a business support program that aims to reduce the burden of journal entry input work.

[0036] The storage unit 2 also includes a head office / branch account item master table 11, a head office / branch journal entry detail data storage unit 12, a journal entry detail data storage unit 13, a journal entry history data storage unit 14, a new registration processing classification storage unit 15, a correction registration processing classification storage unit 16, and a deletion registration processing classification storage unit 17, which are storage areas. These will be described in more detail later.

[0037] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the memory unit 2, and thereby functions as a display control unit 21, a head office / branch journal entry generation unit 22, a discrimination unit 23, a journal entry detail generation unit 24, a journal entry history data generation unit 25, a communication control unit 26, a search unit 27, and an output control unit 28, as shown in Figure 2.

[0038] The display control unit 21 displays the journal entry screen (see FIG. 4) via the output device 7, which is an example of a display unit. The discrimination unit 23 determines whether or not a business office has been entered on the journal entry screen. When the discrimination result indicates that a debit business office or a credit business office has been entered, the head office / branch account journal entry generation unit 22 generates head office / branch account journal entry detail data of the journal entry content corresponding to the journal entry information entered on the journal entry screen and stores it in the head office / branch account journal entry detail data storage unit 12 (see FIG. 5).

[0039] If the journal entry detail generation unit 24 obtains a determination result indicating that there is no business establishment input, it generates journal entry detail data equivalent to a regular voucher for its own business establishment based on the journal entry information entered on the journal entry input screen and stores it in the journal entry detail data storage unit 13 (see Figure 21).

[0040] In addition, when the journal entry detail generation unit 24 obtains a judgment result indicating that a debit business office or a credit business office has been entered, it generates journal entry vouchers for each business office, namely, journal entry detail data in which the recording business office is used as the identification information of the business office itself, and journal entry detail data in which the identification information of another business office that is a trading partner of the business office itself is used as the recording business office, and stores these in the journal entry detail data storage unit 13 (see Figure 7).

[0041] Specifically, if the identification information of the own business office, which is the recording business office included in the head office / branch office journal entry detail data, differs from the identification information of the debit business office, the journal entry detail generation unit 24 generates journal entry detail data in which the debit account item of the journal entry detail data, which has the recording business office as the identification information of the own business office, is set as the branch account item corresponding to the other business office that is the trading partner, and the credit account item of the journal entry detail data, which has the recording business office as the identification information of the other business office, is set as the own business office account item; and if the identification information of the own business office, which is the recording business office included in the head office / branch office journal entry detail data, differs from the identification information of the credit business office, the credit account item of the journal entry detail data, which has the recording business office as the identification information of the own business office, is set as the branch account item corresponding to the other business office that is the trading partner, and the debit account item of the journal entry detail data, which has the recording business office as the identification information of the other business office, is set as the own business office account item (see Figures 5 and 7).

[0042] In addition, the head office / branch journal entry generation unit 22 and the journal entry detail generation unit 24 attach approval status information indicating the approval status of the head office / branch journal entry detail data and each journal entry detail data by business location to the head office / branch journal entry detail data and each journal entry detail data by business location that they generate, and generate them with the same approval key (see Figures 5 and 7).

[0043] In addition, the journal entry detail generation unit 24 generates each journal entry detail data by assigning the voucher number assigned to the head office / branch journal entry detail data from which this journal entry detail data was generated to the journal entry detail data for which the identification information of another business establishment is used as the recording business establishment (see Figures 5 and 7).

[0044] The journal entry history data generation unit 25 generates journal entry history data including the data corresponding to the data before the correction or the data corresponding to the data after the correction, or the processing classification indicating the reason for generation, the voucher number, the sub-voucher number that is the same as the voucher number of the corresponding head office / branch journal entry detail data, and the journal entry data, and stores the data in the journal entry history data storage unit 14.

[0045] In addition, when a correction is made to change a normal journal entry voucher to a head office / branch journal entry voucher, the head office / branch journal entry generation unit 22 generates head office / branch journal entry detail data of the journal entry content corresponding to the correction using the same voucher number as the voucher number assigned to the journal entry detail data before the correction, and adds and stores it in the head office / branch journal entry detail data storage unit 12 (see Figure 27).

[0046] In addition, the journal entry detail generation unit 24 deletes the journal entry detail data before the correction, generates corrected journal entry detail data that is a local business voucher assigned the same voucher number as the voucher number of the journal entry detail data before the correction, and adds and stores it in the head office / branch journal entry detail data storage unit 12. In addition, the journal entry detail generation unit 24 generates corrected journal entry detail data that is a local business voucher, having the newly assigned voucher number and the voucher number used when generating the head office / branch journal entry detail data of the journal entry content corresponding to the correction as a sub-voucher number, and adds and stores it in the journal entry detail data storage unit 13 (see Figure 28). In addition, the journal entry history data generation unit 25 generates journal entry history data for the local business of the processing classification before and after the correction, and adds and stores it in the journal entry history data storage unit 14 (see Figure 29), and also generates journal entry history data corresponding to the local business voucher, including the processing classification of the reason for generation, and adds and stores it in the journal entry history data storage unit 14 (see Figure 29).

[0047] In addition, when a correction is made to change the transfer destination of a head office / branch journal entry voucher, the head office / branch journal entry generation unit 22 corrects the transfer destination business office of the head office / branch journal entry detail data before correction stored in the head office / branch journal entry detail data storage unit 12 to the changed business office (see Figure 33).

[0048] Furthermore, the journal entry detail generation unit 24 deletes the pre-correction journal entry detail data stored in the journal entry detail data storage unit 13, generates corrected journal entry detail data for its own business office corresponding to the correction that changes the transfer destination, by assigning the voucher number of the head office / branch office journal entry detail data, and adds and stores it in the journal entry detail data storage unit 13 (see Figure 34). Furthermore, the journal entry detail generation unit 24 generates corrected journal entry detail data for other business offices by assigning a sub-voucher number that is the same as the voucher number of the head office / branch office journal entry detail data, and adds and stores it in the journal entry detail data storage unit 13 (see Figure 34).

[0049] The journal entry history data generation unit 25 also generates journal entry history data for its own business establishment with processing classifications before and after correction, and adds it to and stores it in the journal entry history data storage unit 14 (see Figure 35). The journal entry history data generation unit 25 also generates journal entry history data for other business establishments, including processing classifications indicating that the data is data before correction of the transfer destination of the head office / branch office journal entry voucher and that the data is data after correction of the transfer destination of the head office / branch office journal entry voucher, and adds it to and stores it in the journal entry history data storage unit 14 (see Figure 35). The journal entry history data generation unit 25 also generates journal entry history data of the journal entry detail data corresponding to the business establishment that is the transfer destination before the change of the head office / branch office journal entry voucher that was deleted from the journal entry detail data storage unit 13, including a processing classification indicating that the deletion is due to a change to the head office / branch office journal entry voucher, and adds it to and stores it in the journal entry history data storage unit 14 (see Figure 35).

[0050] Furthermore, when deletion of a head office / branch journal entry voucher is specified, the head office / branch journal entry generation unit 22 deletes the head office / branch journal entry detail data specified for deletion from the head office / branch journal entry detail data storage unit 12 (see Figure 37). Furthermore, the journal entry detail generation unit 24 deletes the journal entry detail data corresponding to the head office / branch journal entry detail data specified for deletion from the journal entry detail data storage unit 13 (see Figure 38).

[0051] Furthermore, the journal entry history data generation unit 25 generates journal entry history data for its own business establishment including a processing class indicating that journal entry detail data has been deleted, and adds and stores the data in the journal entry history data storage unit 14 (see FIG. 39). Furthermore, the journal entry history data generation unit 25 generates journal entry history data for other business establishments including a processing class indicating that the deletion of a head office / branch journal entry voucher was the reason for the data generation, and adds and stores the data in the journal entry history data storage unit 14 (see FIG. 39).

[0052] Next, the search unit 27 refers to the journal entry history data storage unit 14 and searches for journal entry history data containing a processing category corresponding to the specified search criteria, based on at least one of the desired update type corresponding to the processing category, the desired business establishment, and the desired slip number (see FIG. 40), which are specified as search criteria. The output control unit 28 outputs the searched journal entry history data containing the processing category corresponding to the search criteria to the output target device (see FIG. 41).

[0053] As output target devices, in addition to monitor devices (display units), storage devices such as printers, speaker devices, internal memory devices, external memory devices, and server devices on a specified network can be used. The output control unit 28 converts the searched journalization history data into a data format appropriate for the output form and supplies it to each such device. This makes it possible to obtain a display output, print output, or audio output of the searched journalization history data. In addition, the searched journalization history data can be stored and saved in a storage device.

[0054] (Journal entry operation) The following describes the journalizing operation in the business support device 1 of the embodiment. The control unit 3 of the business support device 1 of the embodiment functions as a display control unit 21, a head office / branch journal entry generation unit 22, a discrimination unit 23, a journal entry detail generation unit 24, a journal entry history data generation unit 25, a communication control unit 26, a search unit 27, and an output control unit 28 based on the business support program stored in the storage unit 2, and executes the journalizing operation described below.

[0055] In this example, the display control unit 21 to the output control unit 28 are realized by software based on the business support program, but some or all of the display control unit 21 to the output control unit 28 may be realized by hardware. In either case, the same effects as those described below can be obtained.

[0056] First, Fig. 3 is a diagram showing the overall flow of operations related to journal entry in a journal entry system including a business support device according to an embodiment. The business support device 1 shown in Fig. 3 corresponds to a terminal device at the Tokyo office. When a journal entry is input by a person in charge at the Tokyo office, the business support device 1 generates head office / branch office journal entry detail data (accounting slip for the office itself = head office / branch office slip) and journal entry detail data (regular slip for each office), as will be described later, and stores them in the memory unit 2.

[0057] Regular invoices for each business location can be checked by, for example, a person in charge at the Yokohama business location via the Yokohama business location terminal device 54. In addition, regular invoices for each business location have the invoice number of the head office / branch office invoice added as a sub-invoice number (see Figure 9). Therefore, it is possible to search for and check the head office / branch office invoice that was the source of the regular invoice for each business location using this sub-invoice number.

[0058] In addition, the head office / branch office slips and the regular slips for each business office are approved via the approver terminal device 51 of the approver at the Tokyo business office.

[0059] Furthermore, the business support device 1 generates head office / branch office journal entry detail data and journal entry history data relating to the generation, modification, and deletion of the journal entry detail data, and stores the data in the storage unit 2.

[0060] (New journal entry voucher creation behavior for expense transfer journal entries between business locations) The journal entry operation of the business support device 1 of this embodiment will be described below with a specific example. Figure 4 shows an example in which a new journal entry voucher for an expense transfer between the Yokohama and Tokyo offices is created at the Tokyo office. In this case, when the person in charge at the Tokyo office (Tokyo user 01) specifies the display of the journal entry input screen, the display control unit 21 displays the journal entry input screen shown in Figure 4 via the output device 7. In this case, the processing mode of the control unit 3 is the "new" processing mode, which performs input processing for a new voucher.

[0061] This journal entry screen has a header area where you can enter the voucher number, a selection field for the name of the business establishment where you are entering the journal entry, an entry field for the date of occurrence, the name of the department to which the user who issued the journal entry belongs, and an entry field for the name of the user who issued the journal entry. This journal entry screen also has an entry field for the journal entry voucher in the details area.

[0062] In this example, the person in charge at the Tokyo office selects the Tokyo office in the office name selection field in the header area, and enters the filing date, such as "February 3, 2024," in the occurrence date field. They also enter the department name of the filing user, such as "Tokyo Accounting Department," and the user name of the user filing, such as "Tokyo User 01."

[0063] The person in charge at the Tokyo office also performs a journal entry input operation in the details area, entering the general account item, office name, department, amount, etc., relating to the transaction between the Tokyo office and the Yokohama office into the debit and credit input fields. The example in Figure 4 shows an example where "Advertising Expenses" is entered as the general account item on the debit and credit sides, "Yokohama Office" is entered as the debit office, "Tokyo Office" is entered as the credit office, and "3,000 yen" is entered as the debit and credit amount.

[0064] Here, the discrimination unit 23 discriminates whether or not a business establishment has been input on the journal entry screen. If it is determined that there is no business establishment input, the head office / branch office journal generation unit 22 generates regular voucher data for a regular voucher for its own business establishment based on the journal entry information entered on the journal entry screen, and stores the data in the memory unit 2 (regular voucher processing).

[0065] On the other hand, if it is determined that a debit office or a credit office has been entered, the head office / branch journal entry generation unit 22 generates head office / branch journal entry detail data of the journal entry content corresponding to the journal entry input information entered on the journal entry input screen and stores it in the head office / branch journal entry detail data storage unit 12. The record in the bottom row of Figure 5 is an example of newly issued head office / branch journal entry detail data. As shown in Figure 5, the head office / branch journal entry generation unit 22 sets the business name to "Tokyo Office" and generates head office / branch journal entry detail data corresponding to the input content on the journal entry input screen and stores it in the head office / branch journal entry detail data storage unit 12.

[0066] In addition, the journal entry detail generation unit 24 generates the journal entry detail data shown in Fig. 7 based on the debit business office and credit business office of the head office / branch office journal entry detail data, and adds and stores it in the journal entry detail data storage unit 13. When generating this journal entry detail data, if the business office and the debit business office are different, or if the business office and the credit business office are different, the journal entry detail generation unit 24 refers to the head office / branch account item master shown in Fig. 6 and generates journal entry detail data in which the account items and departments are replaced with head office accounts and branch accounts.

[0067] That is, the journal entry detail generation unit 24 generates journal entry detail data in which the account items of other business offices in the journal entry detail data of the own business office are entered into the same side (debit or credit) as the other business offices are recorded in the head office / branch office journal entry detail data. Also, the journal entry detail generation unit 24 generates journal entry detail data in which the account items of the own business office in the journal entry detail data of other business offices are entered into the same side (debit or credit) as the other business office is recorded in the head office / branch office journal entry detail data. The journal entry detail generation unit 24 may perform either one or both of these journal entry detail data generation operations.

[0068] The examples in Figures 5 and 7 are examples in which detailed journal entry data was generated by entering the account item (Yokohama Branch) of another business office (Tokyo Office) in the detailed journal entry data of the own business office (Tokyo Office) into the same debit side where the other business office (Yokohama Office) is recorded in the head office / branch detailed journal entry data. Also, the examples in Figures 5 and 7 are examples in which detailed journal entry data was generated by entering the account item (Head Office) of the own business office in the detailed journal entry data of another business office into the same credit side where the own business office is recorded in the head office / branch detailed journal entry data.

[0069] 5 and 7, the journal entry detail generation unit 24 generates the journal entry detail data to be used in updating at the time of approval with the same approval key as the head office / branch journal entry detail data (in this example, key "3") (the approval key for the related head office / branch journal entry detail data and journal entry detail data is the same approval key). At this stage, the approval status of the head office / branch journal entry detail data and journal entry detail data is "application (in progress)".

[0070] This allows the approver to display the head office / branch journal entry detail data and journal entry detail data based on the same approval key and perform approval work simultaneously, making it possible to match the approval status of the head office / branch journal entry detail data and the journal entry detail data by business location.In addition, it is possible to perform approval work for the head office / branch journal entry detail data and journal entry detail data immediately after the head office / branch journal entry detail data and journal entry detail data are generated.

[0071] (Inquiry by Yokohama office) Figure 8 is a diagram showing an example of a journal inquiry screen displayed on the Yokohama office terminal device 54 when a Yokohama office staff member (Yokohama verifier) ​​inquires about head office / branch journal entry detail data and journal entry detail data. The Yokohama verifier uses this journal inquiry screen to input the business name of the voucher to be inquired about, the department to which the issuing user belongs, and the approval status of the voucher to be inquired about. In this example, the business name is entered as "Yokohama Office," which is the business office, and the department to which the user at the Tokyo office belongs, "Tokyo Accounting Department," is entered as the department to which the issuing user belongs. The approval status of the voucher can be selected from "including unapproved" or "approved only." The example in Figure 8 shows an example where an inquiry about "including unapproved" vouchers has been selected.

[0072] When such input is made by the Yokohama checker, the Yokohama office terminal device 54 transmits the input contents to the server device 53 as inquiry request data via the wide area network 52. Data for all offices, such as the Tokyo office and the Yokohama office, is centrally managed by the business support device 1. For this reason, the control unit of the server device 53 transfers the inquiry request data to the business support device 1 via the wide area network 52. The business support device 1 reads out the journal entry detail data and journal entry history data corresponding to the transferred inquiry request data from the journal entry detail data storage unit 13 and the journal entry history data storage unit 14, and transfers them to the server device 53.

[0073] The control unit of the server device 53 temporarily stores the transferred journal detail data and journal history data in the journal book storage unit 55 and journal history storage unit 56. When inquiring about journal details, the control unit of the server device 53 reads out the journal detail data from the journal book storage unit 55 and transmits it to the Yokohama office terminal device 54. This makes it possible to inquire about journal detail data corresponding to the input content entered via the journal inquiry screen on the Yokohama office terminal device 54.

[0074] Specifically, when inquiry request data from Yokohama office terminal device 54 is transferred from server device 53, control unit 3 of business support device 1 refers to journal entry detail data storage unit 13 shown in FIG. 9, detects vouchers whose business establishment is "Yokohama Office" and whose issuer affiliation is "Tokyo Accounting Department", and transmits them to server device 53. In this example, journal entry detail data with voucher numbers "YK2401002" and "YK2402002" shown in FIG. 9 is detected by control unit 3, transmitted to server device 53, and then transmitted to Yokohama office terminal device 54. As a result, the journal entry detail data with voucher numbers "YK2401002" and "YK2402002" is displayed (queried) on the journal inquiry screen of Yokohama office terminal device 54, as shown in FIG. 8.

[0075] Furthermore, because the approval status of the head office / branch journal entry detail data and the journal entry detail data are linked using the same approval key, when the approver at the Tokyo office updates the approval status from "Application (in progress)" to "Approval in progress" to "Approved," the person in charge at the Yokohama office can track and view the head office / branch journal entry detail data from the journal entry detail data with the same approval status, as specified in the "Approval Status" in the journal ledger, etc.

[0076] Next, when inquiring about the head office / branch office detailed journal entry data that is the source of the journal entry detail data, the Yokohama reviewer operates the voucher inquiry button 60. As a result, inquiry request data is transferred from the Yokohama office terminal device 54 to the business support device 1 via the server device 53. In this example, because the approval status of "Include unapproved" is selected on the journal entry inquiry screen shown in FIG. 8, the control unit 3 of the business support device 1 references the sub-voucher number of the journal entry detail data for the voucher number "YK2402002" that has the approval status "Application (in progress)" among the journal entry detail data for the voucher numbers "YK2401002" and "YK2402002," and detects the voucher number of "TK2402001," which is the voucher number of the head office / branch office voucher that is the source of the journal entry detail data for the voucher number "YK2402002."

[0077] Then, as shown in FIG. 10 , the control unit 3 of the business support device 1 references the head office / branch office journal entry detail data stored in the head office / branch office journal entry detail data storage unit 12, detects the head office / branch office journal entry detail data for the voucher number "TK2402001," and transmits it to the server device 53. The server device 53 transfers this head office / branch office journal entry detail data to the Yokohama office terminal device 54. As a result, the head office / branch office voucher that is the source of the journal entry detail data for the voucher number "YK2402002" is queried (displayed) on the Yokohama office terminal device 54, as shown in FIG. 11 . At this time, the control unit of the server device 53 queries the Yokohama office terminal device 54 for the head office / branch office voucher that is the source of the journal entry detail data for the voucher number "YK2402002," in a data format that corresponds to the layout at the time of input at the Tokyo office. As a result, the head office / branch office voucher can be viewed on the Yokohama office terminal device 54 in the layout at the time of input at the Tokyo office, as shown in FIG. 11 .

[0078] (Approval of slips) Next, of the head office / branch account journal detail data generated by the head office / branch account journal entry generation unit 22 and stored in the head office / branch account journal detail data storage unit 12 and the journal detail data generated by the journal detail generation unit 24 and stored in the journal detail data storage unit 13, when the head office / branch account journal detail data and journal detail data with approval statuses of "application (in progress)" and "approval in progress" are approved by an approver, the approving user and approval status are updated. In this example, as an example, intermediate approval is given by an intermediate approver and final approval is given by a final approver, and the approval becomes "completed."

[0079] First, in Fig. 12, when the intermediate approver (Tokyo user 02) operates the approver terminal device 51 to specify the display of the unapproved list screen, the control unit of the approver terminal device 51 acquires the head office / branch journal entry detail data with an approval status of "Application (in progress)" from the business support device 1, and displays it on the display unit of the approver terminal device 51 as shown in Fig. 12. The intermediate approver (Tokyo user 02) recognizes the displayed head office / branch journal entry detail data and operates the individual approval button 61.

[0080] When the individual approval button 61 is operated, the control unit of the approver terminal device 51 obtains the head office / branch journal entry detail data with an approval status of "application (in progress)" from the business support device 1, and displays it on the display unit of the approver terminal device 51 as shown in FIG. 13. The intermediate approver (Tokyo user 02) recognizes the displayed head office / branch journal entry detail data. Then, if the intermediate approver (Tokyo user 02) approves the head office / branch journal entry detail data shown in FIG. 13, he or she operates the approval button 62 shown in FIG. 13.

[0081] When this approval button 62 is operated, the control unit of the approver terminal device 51 sends interim approval data to the business support device 1 indicating that interim approval has been given to the ``application (in progress)'' journal entry detail data and head office / branch journal entry detail data.

[0082] When the head office / branch journal entry generation unit 22 of the business support device 1 receives the intermediate approval data, it inputs the intermediate approver "Tokyo User 02" as the approval user for the head office / branch journal entry detail data with an approval status of "application (in progress)", as shown in Figure 14, and updates the approval status from "application (in progress)" to "approval in progress".

[0083] Furthermore, when the journal entry detail generation unit 24 of the business support device 1 receives the interim approval data, it inputs the interim approver "Tokyo User 02" as the approving user of the journal entry detail data with an approval status of "application (in progress)", and updates the approval status from "application (in progress)" to "approval in progress", as shown in Fig. 15. This completes the interim approval of the head office / branch journal entry detail data and the journal entry detail data.

[0084] Next, when the final approver (for example, Tokyo user 03, not shown) operates the approver terminal device 51 and specifies the display of the unapproved list screen, the control unit of the approver terminal device 51 acquires the head office / branch journal entry detail data in the approval state of "approval in progress" from the business support device 1, as shown in Fig. 14, and displays it on the approver terminal device 51 of the final approver. The final approver (Tokyo user 03), like the above-mentioned intermediate approver, recognizes the displayed head office / branch journal entry detail data and operates the individual approval button 61.

[0085] When the individual approval button 61 is operated, the control unit of the approver terminal device 51 obtains the head office / branch journal entry detail data in the approval state of "approval in progress" as shown in FIG. 14 from the business support device 1, and displays it on the approver terminal device 51 of the final approver as shown in FIG. 13. The final approver (Tokyo user 03) recognizes the displayed head office / branch journal entry detail data. Then, if the final approver (Tokyo user 03) approves the branch journal entry detail data shown in FIG. 14, he or she operates the approval button 62 shown in FIG. 13.

[0086] When this approval button 62 is operated, the control unit of the approver terminal device 51 sends final approval data to the business support device 1, indicating that final approval has been given to the journal entry detail data that is "under approval" and the head office / branch journal entry detail data.

[0087] When the final approval data is received, the head office / branch journal entry generation unit 22 of the business support device 1 updates the approval user of the head office / branch journal entry detail data with an approval status of "approval in progress" from "Tokyo User 02" to the final approver, "Tokyo User 03," as shown in Figure 16, and also updates the approval status from "approval in progress" to "completed."

[0088] In addition, when the final approval data is received, the journal entry detail generation unit 24 of the business support device 1 updates the approval user of the journal entry detail data with an approval status of "under approval" to the final approver, "Tokyo User 03," as shown in Figure 17, and updates the approval status from "under approval" to "completed."

[0089] This completes the final approval of the head office / branch journal entry detail data and the journal entry detail data.

[0090] (Normal document issuing behavior) Next, we will explain how to issue a regular voucher at the Tokyo office. In this case, the person in charge at the Tokyo office launches the journal entry entry screen described above, as shown in Figure 18, and enters "Tokyo office" in the office entry field in the header area, without entering the office name in the details area. In this case, the discrimination unit 23 determines that no office entry has been made.

[0091] If the discrimination unit 23 determines that "there is no input for the business establishment," the head office / branch journal entry generation unit 22 determines that a normal voucher is being created and does not generate head office / branch journal entry detail data as shown in Figure 20.

[0092] In contrast, if the discrimination unit 23 determines that "there is no business establishment input," the journal entry detail generation unit 24 determines that a normal voucher is being created, generates journal entry detail data corresponding to the normal voucher as shown in Figure 21, and adds it to the journal entry detail data storage unit 13 for storage.

[0093] Furthermore, when the discrimination unit 23 gives a discrimination result that "there is no input for the business establishment," the journal entry history data generation unit 25 determines that a normal voucher has been created and references the new registration processing classification storage unit 15 shown in Figure 19. Then, it acquires the processing classification of "new" as the processing classification for the normal voucher. The journal entry history data generation unit 25 generates journal entry history data with the acquired processing classification of "new" attached, as shown in Figure 22, and adds it to and stores it in the journal entry history data storage unit 14.

[0094] (Correction from normal voucher to branch voucher) Next, we will explain the operation of correcting a regular voucher issued in this way into a head office / branch office voucher. In this case, the person in charge at the Tokyo office enters the business office that conducted the inter-office transaction on the regular voucher in the details area, as shown in Figure 23. The example in Figure 23 is an example where, of two vouchers, "Yokohama Office" is entered as the business office on the debit side of one voucher, and "Osaka Office" is entered as the business office on the debit side of the other regular voucher. Note that the business office on the credit side of both vouchers is "Tokyo Office." In this case, the discrimination unit 23 determines that a business office has been entered in the details area.

[0095] When the discrimination unit 23 gives a discrimination result that "entry for a business establishment has been made," the head office / branch account journal generation unit 22 determines that a head office / branch account slip is being created, generates head office / branch account journal detail data corresponding to the correction content as shown in Figure 27, and adds it to the head office / branch account journal detail data storage unit 12 for storage.

[0096] On the other hand, if the discrimination unit 23 obtains a discrimination result that "entry for business establishment has been made," the journal entry detail generation unit 24 refers to the journal entry detail data storage unit 13 shown in Figure 21 and obtains the voucher number of "TK2402001" of the journal entry detail data before correction, as shown in Figure 25.

[0097] Furthermore, the journal entry detail generation unit 24 compares the journal entry detail data before correction with the corrected journal entry detail data generated by reflecting the correction contents, and determines whether each office exists before and after correction, as shown in Fig. 26. In this example, the Yokohama office and Osaka office have been newly entered, so the Yokohama office and Osaka office, which did not exist before correction, are determined to exist after correction.

[0098] Next, the journal entry detail generation unit 24 temporarily deletes the pre-correction journal entry detail data stored in the journal entry detail data storage unit 13. Then, the journal entry detail generation unit 24 generates journal entry detail data for the Tokyo office based on the corrected journal entry input contents. At this time, the journal entry detail generation unit 24 generates the corrected journal entry detail data for the Tokyo office by assigning the same voucher number as the pre-correction voucher number "TK2402001," and stores this in the journal entry detail data storage unit 13 in place of the deleted pre-correction journal entry detail data. As a result, as shown in Figure 28, journal entry detail data with the voucher number "TK2402001," the office "Tokyo office," and the debit account item "Yokohama branch" or "Osaka branch" is stored in the journal entry detail data storage unit 13.

[0099] Furthermore, the journal entry detail generation unit 24 generates new journal entry detail data for the Yokohama office and the Osaka office based on the revised journal entry input contents. At this time, since the voucher number for the Yokohama office and the voucher number for the Osaka office did not exist before the revision, the journal entry detail generation unit 24 assigns new voucher numbers for the Yokohama office and the Osaka office, generates journal entry detail data, and adds and stores the data in the journal entry detail data storage unit 13 as shown in Figure 28. In the example of Figure 28, the journal entry detail data for the voucher number "YK2402002" is the journal entry detail data for the Yokohama office, and the journal entry detail data for the voucher number "OS2402003" is the journal entry detail data for the Osaka office.

[0100] Furthermore, the journal entry detail generation unit 24 adds the voucher number "TK2402001", which is the voucher number of the head office / branch office journal entry detail data shown in Fig. 27, as a sub-voucher number to the journal entry detail data for the Yokohama office and the Osaka office. Based on this sub-voucher number, head office / branch office journal entry detail data related to the journal entry detail data can be searched for and displayed.

[0101] Next, the journal entry history data generation unit 25 references the correction registration processing classification storage unit 16 shown in Figure 24, and detects the processing classification for the journal entry history data before correction and the processing classification for the journal entry history data after correction when a regular voucher is corrected to a head office / branch office voucher. In this example, as shown in Figure 26, the setting is such that the processing classification of "before correction" is entered for the journal entry history data for the Tokyo office before correction, and the processing classification of "after correction" is entered for the journal entry history data for the Tokyo office after correction. In addition, the setting is such that the processing classification of "addition due to head office / branch transfer" is entered for the journal entry history data for the Yokohama office and the Osaka office after correction, respectively.

[0102] Based on such processing classification settings, the journal entry history data generation unit 25 generates journal entry history data corresponding to the pre-correction journal entry detail data for the Tokyo office for which the processing classification is set to "before correction," as shown in Figure 29, and adds the generated data to the journal entry history data storage unit. Also, the journal entry history data generation unit 25 generates journal entry history data corresponding to the post-correction journal entry detail data for the Tokyo office for which the processing classification is set to "after correction," and adds the generated data to the journal entry history data storage unit 14 for storage.

[0103] As a result, the slip numbers for the Tokyo office slips are the same before and after the correction, so they can be treated as a series of correction history.

[0104] In addition, the journal entry history data generation unit 25 generates journal entry history data for the Yokohama office and the Osaka office, each with the processing category set to "addition by head office / branch transfer" as shown in Figure 29, and adds and stores the data in the journal entry history data storage unit 14.

[0105] This makes it possible to indicate that the journal entry history data for the Yokohama office and the Osaka office is journal entry history data created by head office / branch transfer (addition due to changes in head office / branch slips).

[0106] (Modification of transfer destination for head office / branch slips) Next, we will explain how to correct the transfer destination of a head office / branch office slip. For example, let's assume that a person in charge at the Tokyo office corrects "Osaka office" to "Yokohama office" as the office where the Tokyo office conducted the transaction, as shown in Figure 30.

[0107] In this case, the head office / branch journal entry generation unit 22 changes the debit office of the head office / branch journal entry detail data stored in the head office / branch journal entry detail data storage unit 12 as the Osaka office, as shown in Figure 27, to the Yokohama office, as shown in Figure 33.

[0108] Meanwhile, the journal entry detail generation unit 24 refers to the journal entry detail data storage unit 13 shown in Figure 28 and obtains the voucher number "TK2402001" for the Tokyo office, the voucher number "YK2402002" for the Yokohama office, and the voucher number "OS2402003" for the Osaka office, which exist in the journal entry detail data before correction, as shown in Figure 31.

[0109] Furthermore, the journal entry detail generation unit 24 compares the journal entry detail data before correction with the corrected journal entry detail data generated by reflecting the correction contents, and determines whether each business office exists before and after correction, as shown in Figure 32. In this example, the Osaka business office is changed to the Yokohama business office, so after correction, the Osaka business office is determined to be a non-existent business office.

[0110] Next, the journal entry detail generation unit 24 temporarily deletes the journal entry detail data that includes the same voucher number or sub-voucher number as the one to be corrected from each of the pre-correction journal entry detail data for the Tokyo office, Yokohama office, and Osaka office that is stored in the journal entry detail data storage unit 13. Then, based on the corrected journal entry input contents, the journal entry detail generation unit 24 generates journal entry detail data for the Tokyo office with the debit account item set to Yokohama Branch, and adds and stores this in the journal entry detail data storage unit 13 as shown in Figure 34.

[0111] In addition, the journal entry detail generation unit 24 generates the journal entry detail data for the Yokohama office for which no corrections were made, assigning the same voucher number as the voucher number before the correction, and adding the voucher number "TK2402001" of the head office / branch office journal entry detail data shown in Figure 33 as a sub-voucher number, and adds and stores this in the journal entry detail data storage unit 13 as shown in Figure 34.

[0112] In addition, the journal entry detail generation unit 24 generates the journal entry detail data corrected from the Osaka office to the Yokohama office by assigning the same voucher number as the voucher number before the correction, and by adding the voucher number of ``TK2402001'' of the head office / branch journal entry detail data shown in Figure 33 as a sub-voucher number, and adds and stores this in the journal entry detail data storage unit 13 as shown in Figure 34.

[0113] Next, the journal entry history data generation unit 25 references the correction registration processing classification storage unit 16 shown in FIG. 24 to detect the processing classification for the journal entry history data before correction and the processing classification for the journal entry history data after correction when both the data before and after correction are head office / branch vouchers. In this example, as shown in FIG. 32, the setting is such that the processing classification "before correction" is entered for the journal entry history data for the Tokyo office before correction, and the processing classification "after correction" is entered for the journal entry history data for the Tokyo office after correction. Also, the setting is such that the processing classification "before correction of head office / branch transfer" is entered for the journal entry history data for the Yokohama office before correction, and the processing classification "after correction of head office / branch transfer" is entered for the journal entry history data after correction. Also, the setting is such that the processing classification "deletion of head office / branch transfer" is entered for the journal entry history data for the Osaka office before correction.

[0114] Based on this setting of the processing category, the journal entry history data generation unit 25 generates journal entry history data corresponding to the pre-correction journal entry detail data for the Tokyo office for which the processing category is set to "before correction," as shown in Figure 35, and adds this data to and stores it in the journal entry history data storage unit. Also, the journal entry history data generation unit 25 generates journal entry history data corresponding to the post-correction journal entry detail data for the Tokyo office for which the processing category is set to "after correction," and adds this data to and stores it in the journal entry history data storage unit 14.

[0115] As a result, the slip numbers for the Tokyo and Yokohama offices are the same before and after the correction, so they can be treated as a series of correction histories.

[0116] Furthermore, the journal entry history data generation unit 25 generates journal entry history data for the Yokohama office (journal entry history data for the Yokohama office for which no changes or corrections to the office have been made) with the processing classification set to "before correction of head office / branch transfer" as shown in Figure 35, and adds this data to and stores it in the journal entry history data storage unit 14. Furthermore, the journal entry history data generation unit 25 generates journal entry history data for the Yokohama office (journal entry history data for the Yokohama office for which no changes or corrections to the office have been made) with the processing classification set to "after correction of head office / branch transfer" as shown in Figure 35, and adds this data to and stores it in the journal entry history data storage unit 14.

[0117] Furthermore, the journal entry history data generation unit 25 generates the journal entry history data for the Yokohama office, where changes to the office have been made, as a processing category of "after correction of head office / branch transfer" as shown in Figure 35, and adds it to and stores it in the journal entry history data storage unit 14.

[0118] As a result, the journal entry history data of the Yokohama office and the Osaka office can be shown as journal entry history data created by head office / branch transfers.

[0119] (Action for deleting head office / branch slips) Next, the operation for deleting a head office / branch office voucher will be described. For example, suppose that a head office / branch office voucher for a transaction between the Tokyo office and the Yokohama office shown in Figure 36 is deleted. In this case, the head office / branch office journal entry generation unit 22 deletes the deleted head office / branch office journal entry detail data from the head office / branch office journal entry detail data storage unit 12, as shown in Figure 37.

[0120] In addition, the journal entry detail generation unit 24 also deletes from the journal entry detail data storage unit 13 any journal entry detail data that includes the same voucher number or sub-voucher number as the voucher number "TK2402001" attached to the deleted head office / branch branch journal entry detail data.

[0121] Furthermore, the journal entry history data generation unit 25 references the deletion registration processing classification storage unit 17 shown in Fig. 40 to detect the processing classification to be assigned to the journal entry history data when a head office / branch office voucher is deleted. In the example of Fig. 40, the processing classification of "deletion" is set to be assigned to the journal entry history data for the Tokyo office, which is the input office, and the processing classification of "deletion of head office / branch office transfer" is set to be assigned to the journal entry history data for the Yokohama office, which is the transfer destination office.

[0122] For this reason, the journal entry history data generation unit 25 generates journal entry history data for the Tokyo office with the processing category set to "deletion," and adds and stores it in the journal entry history data storage unit 14. In addition, the journal entry history data generation unit 25 generates journal entry history data for the Yokohama office with the processing category set to "deletion of head office / branch transfer," and adds and stores it in the journal entry history data storage unit 14. This allows the person in charge, etc., to recognize that the journal entry voucher for the Yokohama office has been deleted as a result of the deletion of the head office / branch office voucher.

[0123] (Journal entry history inquiry behavior) Next, the journalization history data stored in the journalization history data storage unit 14 of the business support device 1 can be referenced at any desired time. That is, when a person in charge at the Tokyo office specifies a query for the journalization history data, the display control unit 21 displays a journalization history list query screen, as shown in FIG. 41, via the output device 7.

[0124] As shown in Figure 41, this journal entry history list inquiry screen has a selection field for the update type (new, edit, or delete) of the journal entry history data you wish to inquire about, an input field for the desired business establishment, and an input field for the desired voucher number.

[0125] The search unit 27 refers to the journal entry history data storage unit 14 using one or more of the update type, business office, and voucher number entered by the person in charge at the Tokyo business office as search conditions, and searches for journal entry history data that corresponds to these search conditions. The output control unit 28 displays a list of the journal entry history data that corresponds to the search conditions found on the output device 7, as shown in Figure 41. In the example of Figure 41, the update types "New," "Edit," and "Delete" are selected, and the voucher number "TK2402001" is specified.

[0126] As a result, the new, pre-correction, post-correction, and deleted journal entry history data with the voucher number "TK2402001" are displayed in a list on the journal entry history list inquiry screen, as shown in Figure 41. Therefore, the journal entry history data for the input business office can be confirmed as a change history in the same way as the history of regular vouchers.

[0127] Next, the communication control unit 26 transfers the journal entry history data stored in the journal entry history data storage unit 14 to the server device 53. The server device 53 stores the transferred journal entry history data in the journal entry history storage unit 56 and also transfers it to the Yokohama office terminal device 54. This allows the person in charge at the Yokohama office to inquire about the journal entry voucher history of the Yokohama office. Furthermore, because the voucher number does not change consistently, all update history can be confirmed using a single voucher number.

[0128] That is, when the person in charge at the Yokohama office specifies an inquiry about journalization history data, the Yokohama office terminal device 54 displays a journalization history list inquiry screen, an example of which is shown in FIG.

[0129] As shown in Figure 42, this journal entry history list inquiry screen has a selection field for the update type (new, edit, or delete) of the journal entry history data you wish to inquire about, an input field for the desired business establishment, and an input field for the desired voucher number.

[0130] The Yokohama office terminal device 54 transmits inquiry request data using one or more of the update type, office, and slip number entered by the person in charge at the Yokohama office as search conditions to the business support device 1 via the server device 53. The control unit 3 of the business support device 1 reads out the journal entry history data corresponding to the search conditions from the journal entry history data storage unit 14 and transmits it to the Yokohama office terminal device 54 via the server device 53.

[0131] The example in Figure 42 shows an example in which the update types "New," "Edit," and "Delete" are selected, and the slip number "YK2402002" is specified. Therefore, as shown in Figure 42, the journal entry history data for new, before edit, after edit, and deletion, each with the slip number "YK2402002," is displayed in a list on the journal entry history list inquiry screen of the Yokohama office terminal device 54.

[0132] The person in charge at the Yokohama office can check the journal entry history data for the Yokohama office as a change history in the same way as the history of regular vouchers. Also, because the voucher number remains consistent, it is possible to check all update history with a single voucher number. It is also easy to recognize that the history is the result of input (registration and update of head office / branch vouchers) from the Tokyo office, which is a different office.

[0133] (Effects of the embodiment) As is clear from the above description, the task support device 1 according to the embodiment can achieve the following effects.

[0134] 1. It is no longer necessary to switch screens depending on the organization (business location or department), which significantly reduces the judgment and workload of the person in charge.

[0135] 2. Approvers can view regular vouchers and then switch to the layout used when inputting data. They can also easily check the update history of each voucher, allowing them to efficiently approve journal entry vouchers.

[0136] 3. Also, by issuing regular invoices for all business locations immediately after issuing the invoices, the party receiving the transfer (the Yokohama business location in the above example) can also point out errors early on.

[0137] 4. It reduces the work of creating unnecessary red and black vouchers and provides an easy-to-read journal and journal history.

[0138] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of goals "8" and "9" of the SDGs.

[0139] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs goals 12, 13, and 15.

[0140] Furthermore, the present invention can contribute to strengthening control and governance, thereby contributing to the achievement of Goal 16 of the SDGs.

[0141] [Other embodiments] The present invention can be implemented in various different forms other than the above-described embodiments within the scope of the technical concept described in the claims.

[0142] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually, or all or part of the processes described as being performed manually may be performed automatically using a known method or the like.

[0143] Furthermore, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in the specification or drawings may be changed as desired unless otherwise specified.

[0144] Furthermore, the components of the business support device 1 shown in the figure are conceptual functional components and do not necessarily have to have the physical configuration shown in the figure. For example, all or any part of the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0145] The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in the embodiments, and is mechanically read by the business support device 1 as needed. That is, a computer program is recorded in the storage unit 2, such as a ROM or HDD, for working with an OS (Operating System) to give instructions to a control unit 3 (CPU) and perform various processes. The computer program is loaded into RAM, expanded, and executed by the control unit 3 as appropriate.

[0146] In addition, the business support program of this business support device 1 may be stored in another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0147] Furthermore, the business support program for executing the processes described in the embodiments may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0148] Here, the "recording medium" can be any "portable physical medium" such as 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), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical Disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0149] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code.

[0150] It should be noted that a "program" is not necessarily limited to a single structure, but includes a structure that is distributed as multiple modules or libraries, and a structure that achieves its function by working together with other programs, such as an OS.

[0151] Furthermore, the specific configuration for reading the recording medium in the task support device 1 of the embodiment, the reading procedure, and the installation procedure after reading can be any known configuration or procedure.

[0152] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, web page files, etc. used for various processes or providing websites.

[0153] The business support device 1 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may be implemented with software (including programs or data) that realizes the processes described in the embodiments.

[0154] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be selectively implemented by combining them in any way. [Industrial Applicability]

[0155] The present invention is applicable to various types of businesses that perform accounting journal entry work, and is particularly suitable for application to accounting journal entry work in companies that operate multiple bases. [Explanation of symbols]

[0156] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / Output Interface Section 6 Input Devices 7 Output Devices 11 Head office / branch account master table 12 Head office and branch journal entry detail data storage section 13 Journal entry detail data storage section 14 Journal entry history data storage unit 15 New registration processing classification memory section 16. Correction registration processing classification memory section 17. Processing classification memory section for deletion registration 21 Display control unit 22 Head Office and Branch Journal Entry Generation Department 23 Discrimination part 24 Journal Entry Detail Generation Section 25 Journal entry history data generation unit 26 Communication control section 27 Search Section 28 Output control section 50 Private Network 51 Approver terminal device 52 Wide Area Network 53 Server equipment 54 Yokohama Office Terminal Device 55 Journal memory section 56 Journal entry history memory section 60 Invoice inquiry button 61 Individual approval button 62 Approval button

Claims

1. A business support device that supports accounting work for transactions between business establishments, a display control unit that displays a journal entry input screen on a display unit for performing journal entry input; a determination unit that determines whether or not a business establishment has been entered on the journal entry input screen; a head office / branch account journal generation unit that generates head office / branch account journal detail data of the journal entry content corresponding to the journal entry information entered on the journal entry input screen and stores the data in a head office / branch account journal detail data storage unit when a determination result indicating that a debit office or a credit office has been entered is obtained; a journal entry detail generation unit that, when a determination result indicates that there is no business establishment input, generates journal entry detail data equivalent to a normal voucher for the business establishment based on the journal entry information entered on the journal entry screen and stores the journal entry detail data storage unit; and, when a determination result indicates that a debit business establishment or a credit business establishment has been entered, generates journal entry detail data for each business establishment, in which the recording business establishment is used as identification information for the business establishment, and in which identification information for another business establishment that is a trading partner of the business establishment is used as the recording business establishment, and stores the journal entry detail data storage unit; A business support device having the above.

2. The journal entry detail generation unit If the identification information of the own business office, which is the recording business office included in the head office / branch office journal entry detail data, differs from the identification information of the debit business office, the debit account item of the journal entry detail data, which has the recording business office as the identification information of the own business office, is set as the branch account item corresponding to the other business office that is the trading partner, and the credit account item of the journal entry detail data, which has the recording business office as the identification information of the other business office, is set as the own business account item, generating the journal entry detail data; and When the identification information of the own business office, which is the recording business office included in the head office / branch office journal entry detail data, differs from the identification information of the credit business office, the credit account item of the journal entry detail data in which the recording business office is the identification information of the own business office is set as the branch account item corresponding to the other business office that is the trading partner, and the debit account item of the journal entry detail data in which the recording business office is the identification information of the other business office is set as the own business account item, during the generation of the journal entry detail data, Doing either or both of the following:

2. The business support device according to claim 1, wherein:

3. the head office / branch journal entry generation unit and the journal entry detail generation unit respectively generate the head office / branch journal entry detail data and each of the journal entry detail data by business establishment by attaching approval status information indicating the approval status of the head office / branch journal entry detail data and each of the journal entry detail data by business establishment, and by attaching the same approval key to the generated head office / branch journal entry detail data and each of the journal entry detail data by business establishment, 3. The business support device according to claim 2, wherein:

4. the journal entry detail generation unit generates, among each of the journal entry detail data, journal entry detail data in which the identification information of another business establishment is used as the accounting business establishment, by assigning a slip number assigned to the head office / branch branch journal entry detail data from which the journal entry detail data is generated; 4. The business support device according to claim 3, wherein:

5. Further provided is a journal history data generation unit that generates journal history data including a processing category indicating whether the data is corresponding to data before correction or corresponding to data after correction, or a reason for generation, a voucher number, a sub-voucher number that is the same as the voucher number of the corresponding head office / branch journal entry detail data, and journal data, and stores the data in the journal history data storage unit; 5. The business support device according to claim 4, wherein:

6. When a correction is made to change a regular journal entry voucher to a branch journal entry voucher, the head office / branch office journal entry generation unit generates head office / branch office journal entry detail data of the journal entry content corresponding to the correction using the same voucher number as the voucher number assigned to the journal entry detail data before the correction, and adds and stores the data in the head office / branch office journal entry detail data storage unit; The journal entry detail generation unit deletes the journal entry detail data before correction, generates the corrected journal entry detail data which is a self-office voucher assigned with the same voucher number as the voucher number of the journal entry detail data before correction, and adds and stores the corrected journal entry detail data to the head office / branch journal entry detail data storage unit, and also generates the corrected journal entry detail data which is a other-office voucher having a newly assigned voucher number and the voucher number used when generating the head office / branch journal entry detail data of the journal entry content corresponding to the correction as a sub-voucher number, and adds and stores the corrected journal entry detail data to the journal entry detail data storage unit, the journal entry history data generation unit generates the journal entry history data for its own business establishment for the processing classification before and after the correction, and adds and stores it in the journal entry history data storage unit, and also generates the journal entry history data corresponding to the other business establishment slip, including the processing classification of the reason for the generation, and adds and stores it in the journal entry history data storage unit; 6. The business support device according to claim 5,

7. When a correction is made to change the transfer destination of a head office / branch journal entry, The head office / branch office journal entry generation unit amends the transfer destination business establishment of the head office / branch office journal entry detail data before amendment stored in the head office / branch office journal entry detail data storage unit to the changed business establishment, The journal entry detail generation unit deletes the pre-correction journal entry detail data stored in the journal entry detail data storage unit, generates corrected journal entry detail data for its own business office corresponding to the correction that changes the transfer destination by assigning the voucher number of the head office / branch journal entry detail data, adds and stores the data to the journal entry detail data storage unit, generates corrected journal entry detail data for other business offices by assigning a sub-voucher number that is the same as the voucher number of the head office / branch journal entry detail data, and adds and stores the data to the journal entry detail data storage unit, the journal entry history data generation unit generates the journal entry history data for its own business establishment with processing classifications before and after correction, and adds and stores it in the journal entry history data storage unit, and generates the journal entry history data for other business establishments including processing classifications indicating that the data is the data before correction of the transfer destination of the head office / branch office journal entry voucher and that the data is the data after correction of the transfer destination of the head office / branch office journal entry voucher, and adds and stores it in the journal entry history data storage unit, and generates the journal entry history data of the journal entry detail data corresponding to the business establishment that is the transfer destination before the change of the head office / branch office journal entry voucher that was deleted from the journal entry detail data storage unit, including the processing classification indicating that the deletion is due to the change of the head office / branch office journal entry voucher, and adds and stores it in the journal entry history data storage unit; 7. The business support device according to claim 6, wherein:

8. When deletion of head office / branch journal vouchers is specified, The head office / branch account journal entry generation unit deletes the head office / branch account journal entry detail data designated for deletion from the head office / branch account journal entry detail data storage unit, The journal entry detail generation unit deletes the journal entry detail data corresponding to the head office / branch office journal entry detail data designated for deletion from the journal entry detail data storage unit, the journal entry history data generation unit generates journal entry history data for its own business establishment including the processing category indicating that the journal entry detail data has been deleted, and adds and stores the data in the journal entry history data storage unit, and generates journal entry history data for other business establishments including the processing category indicating that the deletion of the head office / branch journal entry voucher was the reason for the data generation, and adds and stores the data in the journal entry history data storage unit; 8. The business support device according to claim 7, wherein:

9. A search unit that refers to the journal entry history data storage unit based on at least one of a desired update type corresponding to the processing category, a desired business establishment, and a desired slip number, which are specified as search conditions, and searches for the journal entry history data including the processing category corresponding to the specified search conditions; an output control unit that outputs the searched journalization history data including the processing classification corresponding to the search conditions to an output target device; 9. The business support device according to claim 8, further comprising:

10. A business support method for supporting journal entry work for transactions between business establishments, comprising: a display control step in which a display control unit displays a journal entry input screen for performing journal entry input on a display unit; a determination step in which a determination unit determines whether or not a business establishment has been input on the journal entry input screen; a head office / branch account journal generation step in which, when the head office / branch account journal generation unit obtains a determination result indicating that a debit office or a credit office has been entered, it generates head office / branch account journal detail data of the journal content corresponding to the journal entry information entered on the journal entry input screen and stores the data in a head office / branch account journal detail data storage unit; a journal entry detail generation step in which, when the journal entry detail generation unit obtains a determination result indicating that the business office has not been entered, it generates journal entry detail data equivalent to a regular voucher for its own business office based on the journal entry information entered on the journal entry screen and stores the data in the journal entry detail data storage unit; and, when the journal entry detail generation unit obtains a determination result indicating that a debit business office or a credit business office has been entered, it generates journal entry detail data for each business office, with the recorded business office as the identification information of the own business office, and journal entry detail data with the identification information of another business office that is a trading partner of the own business office as the recorded business office, and stores the data in the journal entry detail data storage unit; A business support method comprising:

11. A business support program that causes a computer of a business support device to function to support accounting work for transactions between business establishments, The computer a display control unit that displays a journal entry input screen on a display unit for performing journal entry input; a determination unit that determines whether or not a business establishment has been entered on the journal entry input screen; a head office / branch account journal generation unit that generates head office / branch account journal detail data of the journal entry content corresponding to the journal entry information entered on the journal entry input screen and stores the data in a head office / branch account journal detail data storage unit when a determination result indicating that a debit office or a credit office has been entered is obtained; If a determination result is obtained indicating that there is no business office input, the journal entry detail generation unit generates journal entry detail data equivalent to a normal voucher for the business office based on the journal entry information entered on the journal entry input screen and stores it in the journal entry detail data storage unit; if a determination result is obtained indicating that a debit business office or a credit business office has been entered, the journal entry detail generation unit generates journal entry details for each business office, with the recorded business office as the identification information of the business office, and journal entry detail data with the identification information of another business office that is a trading partner of the business office as the recorded business office, and stores these in the journal entry detail data storage unit; A business support program that features:

Images