Automatic journal entry program

Abstract

To provide an automatic journal entry program capable of improving journal entry accuracy while suppressing the complexity of journal entry processing even when it includes a transaction requiring the change of journal entry results depending on individual circumstances.SOLUTION: An automatic journal entry program causes a processor to perform the steps of: searching past journal entry data according to the search conditions set by a user; displaying the searched past journal entry data on a display screen; setting debit data among the past journal entry data in a debit field of a journal entry work region displayed on the display screen on the basis of copy and paste operations performed on the past journal entry data displayed on the display screen; and generating the credit data corresponding to the set debit data through automatic journal entry.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] This embodiment relates to an automatic journalizing program. [Background technology]

[0002] In recent years, automation of accounting work has been promoted as one of the means to realize the efficiency of accounting work. For example, there are known devices that perform accounting work by inputting document data such as invoices to be accounted for. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2018 / 179411 Summary of the Invention [Problem to be solved by the invention]

[0004] In automatic journal entries, the details of various transactions described in documents such as invoices are journalized into account items in accordance with various pre-defined rules, including tax rules, accounting rules, and company rules. Generally, automatic journal entries are prone to errors when journalizing transactions whose journal entries need to be changed depending on individual circumstances. While this can be addressed to some extent by establishing rules for each individual circumstance, it can also complicate the automatic journal entry process, making it difficult to identify the journal entry results and taking a long time to process the entries. Furthermore, when setting rules, it can be difficult to understand the relationship between the rules and the journal entry results, and it can even be difficult to set the rules in the first place.

[0005] The embodiment aims to provide an automatic accounting program that can reduce the complexity of accounting processing while improving accounting accuracy, even when transactions include transactions where the accounting results need to be changed depending on individual circumstances. [Means for solving the problem]

[0006] According to one aspect, the automatic journalizing program searches for past journalizing data in accordance with search conditions set by a user, displays the searched past journalizing data on a display screen, and performs a copy operation and a paste operation on the past journalizing data displayed on the display screen. Debit and credit data Our debit data only The processor is caused to set the above in the debit column of the journal entry work area for journal entry work displayed on the display screen, and to generate credit data corresponding to the set debit data by automatic journal entry. [Effects of the Invention]

[0007] According to the embodiment, an automatic accounting program can be provided that can reduce the complexity of accounting processing while improving accounting accuracy, even when transactions include transactions where the accounting results need to be changed depending on individual circumstances. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of a terminal according to an embodiment. [Figure 2] FIG. 2 is a flowchart showing the automatic journalizing process in the terminal. [Figure 3] FIG. 3 is a diagram showing an example of the top screen. [Figure 4A] FIG. 4A is a diagram showing an example of a search screen for past journalization data. [Figure 4B] FIG. 4B is a diagram showing an example of a search screen for past journalization data. [Figure 5] FIG. 5 is a diagram showing an example of display of past journal data. [Figure 6] FIG. 6 is a diagram showing a drag operation of past journalization data. [Figure 7] FIG. 7 is a diagram showing a screen on which past journalization data is pasted. [Figure 8] FIG. 8 is a diagram showing a screen on which automatic journalization has been performed after past journalization data has been pasted. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment will be described with reference to the drawings. FIG. 1 is a diagram showing the configuration of an example of a terminal according to an embodiment. As shown in FIG. 1, the terminal 1 has a processor 11, a memory 12, a storage 13, an input interface 14, a display 15, and a communication module 16. The processor 11, the memory 12, the storage 13, the input interface 14, the display 15, and the communication module 16 are connected to a bus 17 so as to be able to communicate with each other. Here, the terminal 1 may be a terminal such as a smartphone, a tablet terminal, or a personal computer.

[0010] The processor 11 is a processor configured to control the operation of the terminal 1. The processor 11 executes various processes in accordance with various programs stored in the storage 13. The processor 11 is, for example, a CPU. The processor 11 may be an MPU, a GPU, or the like instead of a CPU. Furthermore, the processor 11 does not need to be configured by one CPU or the like, and may be configured by multiple CPUs or the like.

[0011] The memory 12 includes memories such as ROM and RAM. The ROM is a non-volatile memory. The ROM stores the startup program of the terminal 1 and the like. The RAM is a volatile memory. The RAM is used as a working memory during processing in the processor 11, for example.

[0012] The storage 13 is a storage such as a flash memory. The storage 13 stores various programs and data used in the terminal 1. In the embodiment, the storage 13 stores an OS (operating system) 131, an automatic journalizing program 132, journalizing data 133, and attached data 134. The storage 13 may store programs other than the OS 131 and the automatic journalizing program 132.

[0013] The OS 131 is a program for realizing the basic functions of the terminal 1. Various programs stored in the storage 13 are executed under the control of the OS.

[0014] The automatic journalizing program 132 is a program that causes the processor 11 to execute automatic journalizing processing. Automatic journalizing processing is a process of classifying input transactions into appropriate account items according to their content and calculating the amount for each account item. The content of the transaction is entered in a document such as an invoice or data containing content equivalent to a document. The automatic journalizing program 132 can be installed in the terminal 1 as needed. Note that the transactions in the embodiment are not particularly limited as long as they are transactions that can be subject to automatic journalizing. Automatic journalizing may be performed on a rule-based basis or using a trained model. Various classification models such as SVM (support vector machine) and neural networks may be used as the model.

[0015] In the automatic journalizing process by the automatic journalizing program 132 in the embodiment, the user can copy past journalizing results and use them in the current journalizing work. Here, when copying, not all of the journalizing result data selected by the user is copied. Specifically, only the journalizing result data that is likely to cause errors in the results of automatic journalizing because it can fluctuate depending on individual circumstances is copied, and the journalizing result data that is less likely to cause errors in the results of automatic journalizing because it is less likely to fluctuate depending on individual circumstances is not copied. As will be explained in detail later, the journalizing result data that is likely to cause errors in the results of automatic journalizing because it can fluctuate depending on individual circumstances is the journalizing result data for the debit side of expense journalizing.

[0016] The journal data 133 is journal data created by the automatic journalizing program 132. Each journal data is assigned a unique number and managed. The attached data 134 is data attached to the journal data 133, such as data on invoices. The attached data 134 is managed in association with the journal data 133. The journal data 133 and the attached data 134 may be stored in a storage separate from the storage 13 of the terminal 1.

[0017] The input interface 14 includes input devices such as a touch panel, keyboard, and mouse. When the input interface 14 is operated, a signal corresponding to the operation is input to the processor 11 via the bus 17. The processor 11 performs various processes in response to this signal. Here, the input device may include a camera. The camera is used to take an image of a document such as an invoice. A character string to be journalized can be recognized from the image of the document taken by the camera. The input device may be configured to receive an image read by a multifunction peripheral or the like.

[0018] The display 15 is a display device such as a liquid crystal display, an organic EL display, etc. The display 15 displays various images.

[0019] The communication module 16 is a module including an interface configured to perform processing when the terminal 1 communicates with various external devices. The communication module 16 is configured to connect to a network using a mobile phone line, a wireless LAN line, a wired LAN line, etc. Alternatively, the communication module 16 is configured to connect to devices near the terminal 1 by short-range wireless communication such as Bluetooth (registered trademark).

[0020] Next, we will explain the operation of the terminal 1 based on the automatic journalizing program 132 in this embodiment. Figure 2 is a flowchart showing the automatic journalizing process in the terminal 1. The process in Figure 2 starts when, for example, a user of the terminal 1 instructs the start of the automatic journalizing program 132.

[0021] In step S1, the processor 11 of the terminal 1 displays the top screen of the automatic journalizing program 132 on the display 15. Fig. 3 is a diagram showing an example of the top screen.

[0022] An example top screen has a button display area 100. The button display area 100 is an area where buttons for the user to execute various operations related to the automatic journalizing program 132 are arranged together. The button display area 100 is arranged with, for example, a save button 101, an apply button 102, a cancel button 103, a settings button 104, a past journalizing button 105, an upload button 106, a copy button 107, and a paste button 108. Furthermore, the button display area 100 is provided with a journalizing classification check box 109.

[0023] The save button 101 is a button selected by the user when saving the journal data currently being created or created as journal data 133 in, for example, the storage 13 .

[0024] The application button 102 is a button selected by the user when processing an application by sending journal data to a predetermined application destination. The application destination is a department that receives invoices, a department that settles expenses, etc., and is predetermined according to the applicant's department, the amount of the application, etc.

[0025] The cancel button 103 is a button selected by the user when canceling the currently created journal data without saving it. The setting button 104 is a button selected by the user when making various settings related to the automatic journalizing program 132, such as journalizing rule settings and display settings.

[0026] The past journalization button 105 is a button selected by the user when referring to previously created journalization data 133. When the past journalization button 105 is selected, a search process, which will be described in detail later, is executed.

[0027] The upload button 106 is a button selected by the user when reading journalization target data that will be the basis for automatic journalization. Here, the journalization target data to be uploaded may be data in various formats, such as text data representing the contents of a document such as an invoice, tabular data representing the contents of a document such as an invoice, or image data of a document such as an invoice. In addition, the journalization target data may be a digital invoice in a specified format.

[0028] The copy button 107 is a button selected by the user when copying data such as a character string, etc. The paste button 108 is a button selected by the user when pasting data that has been copied by selecting the copy button 107, etc.

[0029] The journal entry classification checkbox 109 is a checkbox that allows the user to select whether to perform journal entries separately for expense journal entries and payment journal entries. When the journal entry classification checkbox 109 is checked, expense journal entries and payment journal entries are performed separately. Expense journal entries are journal entries related to expenses incurred by transactions, and are performed by debiting increases in expenses or assets and crediting increases in liabilities resulting from increases in expenses or assets. Payment journal entries are journal entries related to payments incurred by transactions, and are performed by debiting decreases in liabilities and crediting decreases in assets resulting from decreases in liabilities. When the journal entry classification checkbox 109 is not checked, a single payment journal entry that combines expense journal entries and payment journal entries is performed. In this single combined payment journal entry, an increase in expenses or assets incurred by a transaction is debited and a decrease in assets resulting from increases in expenses or assets is credited.

[0030] Furthermore, when the journal entry classification checkbox 109 is checked, the top screen, as an example, has an expense journal entry work area 110. The expense journal entry work area 110 is an area for performing expense journal entry work. The user can input journal entry details in the expense journal entry work area 110. Furthermore, when automatic journal entry is performed, the results of the automatic journal entry are displayed in the expense journal entry work area 110.

[0031] The expense journalizing work area 110 has a date display field 111, an item name display field 112, a debit information display field 113, a credit information display field 114, a summary display field 115, and total amount display fields 116a and 116b.

[0032] The date display field 111 is a display field for the invoice date or the accounting date of the expense. The date display field 111 displays, for example, the current date. If a date is read from an invoice or the like, the date in the date display field 111 may be set based on the read date. Alternatively, the date in the date display field 111 may be set by input by the user.

[0033] The item name display field 112 is a display field for the item name of the incurred expense. The user can set an item name corresponding to the incurred expense in the item name display field 112. The display in the item name display field 112 may be updated according to the results of reading the invoice or the like.

[0034] The debit information display field 113 is a display field for various information about the debit displayed on the left side of the expense journalizing work area 110. The debit information display field 113 has, for example, an amount display field 1131, an account item display field 1132, a subaccount display field 1133, a tax category display field 1134, a tax rate category display field 1135, an accounting department code display field 1136, a customer code display field 1137, a project code display field 1138, and a general-purpose code display field 1139. A debit information display field 113 is provided for each account item to be journalized. Therefore, when there are item names that should be accounted for under multiple account items, an amount display column 1131, an account item display column 1132, a subsidiary account display column 1133, a tax category display column 1134, a tax rate category display column 1135, an accounting department code display column 1136, a customer code display column 1137, a project code display column 1138, and a general code display column 1139 are provided corresponding to each item name.

[0035] The amount display field 1131 is a display field for the amount to be journalized. The amount to be journalized can be input by the user or read from data such as an invoice. The amount display field 1131 displays the amount including tax. On the other hand, the amount display field 1131 displays the amount excluding tax, and when a tax rate is set in the tax category display field 1134 and the tax rate category display field 1135, the amount displayed in the amount display field 1131 may take the tax rate into consideration.

[0036] The account item display field 1132 is a display field for the account item to be journalized. The account item is identified based on the results of automatic journalization, which is based on the item name, amount, etc. The account item display field 1132 is provided with a drop-down button 1132a and a delete button 1132b. The drop-down button 1132a is a button selected by the user to display a drop-down list of account items. The user can select a desired account item from the drop-down list displayed by selecting the drop-down button 1132a and set it in the account item display field 1132. The delete button 1132b is a button selected by the user to delete an account item displayed in the account item display field 1132. The drop-down button 1132a and the delete button 1132b allow the user to correct errors in account items caused by automatic journalization.

[0037] The subaccount display field 1133 is a display field for the subaccount to be journalized. Similar to account items, subaccounts are identified based on the results of automatic journalization, which are based on item names, amounts, etc. The subaccount display field 1133 is provided with a drop-down button 1133a and a delete button 1133b. The drop-down button 1133a is a button selected by the user to display a drop-down list of subaccounts. The user can select the desired subaccount from the drop-down list displayed by selecting the drop-down button 1133a and set it in the subaccount display field 1133. The delete button 1133b is a button selected by the user to delete a subaccount displayed in the subaccount display field 1133. The drop-down button 1133a and the delete button 1133b allow the user to correct errors in the subaccounts caused by automatic journalization.

[0038] The tax category display field 1134 is a display field for the tax category of the consumption tax to be journalized. The tax category is identified based on the results of automatic journalization based on the item name, etc., just like the account title. The tax category display field 1134 is provided with a drop-down button 1134a and a delete button 1134b. The drop-down button 1134a is a button selected by the user to display a drop-down list of tax categories. The user can select the desired tax category from the drop-down list displayed by selecting the drop-down button 1134a and set it in the tax category display field 1134. The delete button 1134b is a button selected by the user to delete the tax category displayed in the tax category display field 1134. The drop-down button 1134a and the delete button 1134b allow the user to correct any errors in the tax category resulting from automatic journalization.

[0039] The tax rate category display field 1135 is a display field for the tax rate category that indicates the meaning of the tax rate of the consumption tax to be journalized. For example, the tax rate category is provided to indicate whether the tax rate is the standard tax rate or a reduced tax rate. The tax rate category is identified based on the setting of the tax category display field 1134 and the results of automatic journalization based on the item name, etc. The tax rate category display field 1135 is provided with a drop-down button 1135a. The user can select the desired tax rate from the drop-down list displayed by selecting the drop-down button 1135a and set it in the tax rate category display field 1135.

[0040] The accounting department code display field 1136 is a display field for displaying the accounting department code. The accounting department code is a code assigned to each department to which expenses are recorded. The accounting department code is determined based on the results of automatic accounting based on the item name, amount, etc., just like the account item. The accounting department code display field 1136 is provided with a drop-down button 1136a. The user can select the desired accounting department code from the drop-down list displayed by selecting the drop-down button 1136a and set it in the accounting department code display field 1136.

[0041] The supplier code display field 1137 is a display field for displaying the supplier code. The supplier code is a code assigned to each supplier. The supplier code is identified based on the supplier name, etc. read from data such as an invoice.

[0042] The project code display field 1138 is a display field for displaying the project code. The project code is a code assigned to each project when the expense is incurred in a specific project. The project code is identified based on the project name, etc. read from data such as an expense report.

[0043] The general-purpose code display field 1139 is a display field for displaying a general-purpose code. The general-purpose code is a code that is generally assigned to expenses incurred for other reasons, such as expenses with no business partner or expenses not related to a project.

[0044] The credit information display field 114 is a display field for various information about the credit side displayed on the right side of the expense journalizing work area 110. Like the debit information display field 113, the credit information display field 114 includes, for example, an amount display field 1141, an account item display field 1142, a subaccount display field 1143, a tax category display field 1144, a tax rate category display field 1145, an accounting department code display field 1146, a customer code display field 1147, a project code display field 1148, and a general-purpose code display field 1149. Since debits and credits correspond to each other in journalizing, the same display fields are provided. In other words, the credit information display field 114 is also provided for each account item being journalized. Therefore, when there are item names to be journalized under multiple account items, there are provided amount display column 1141, account item display column 1142, sub-account display column 1143, tax category display column 1144, tax rate category display column 1145, accounting department code display column 1146, customer code display column 1147, project code display column 1148, and general-purpose code display column 1149 corresponding to each item name. Here, debit information display column 113 and credit information display column 114 may be displayed in different colors so that they can be easily distinguished from each other.

[0045] The amount display column 1141, account title display column 1142, subaccount display column 1143, tax category display column 1144, tax rate category display column 1145, accounting department code display column 1146, customer code display column 1147, project code display column 1148, and general-purpose code display column 1149 of the credit information display column 114 are the same as the corresponding display columns of the debit information display column 113, except that information on expenses or assets as debits is replaced with information on liabilities as credits. Therefore, explanations of the amount display column 1141, account title display column 1142, subaccount display column 1143, tax category display column 1144, tax rate category display column 1145, accounting department code display column 1146, customer code display column 1147, project code display column 1148, and general-purpose code display column 1149 of the credit information display column 114 will be omitted.

[0046] Summary display field 115 is a display field for displaying a summary of the journal entry results for the corresponding expense. The user can enter details of the transaction, such as the transaction date, control number, customer, amount, and product name, as a summary in summary display field 115. Alternatively, by using reserved words or the like, the system may be configured so that details read from data such as an invoice are automatically inserted into summary display field 115.

[0047] The total amount display field 116a is a display field for displaying the total amount of the debit amount displayed in the amount display field 1131 of the debit information display field 113. As shown in FIG. 3, when the journalization target is journalized into only one account item, the display in the amount display field 1131 and the display in the total amount display field 116a match. On the other hand, when the journalization target is journalized into multiple account items, the total amount display field 116a displays the total amount of the amount display field 1131 for each account item. In addition, the total amount display field 116b is a display field for displaying the total amount of the credit amount displayed in the amount display field 1141 of the credit information display field 114. When the journalization is performed without error, the amount displayed in the total amount display field 116a matches the amount displayed in the total amount display field 116b.

[0048] Furthermore, regardless of whether the journal entry classification checkbox 109 is checked or not, the top screen in one example has a payment journal entry work area 117. The payment journal entry work area 117 is an area for performing payment journal entry work. The user can input journal entry content in the payment journal entry work area 117. Furthermore, if automatic journal entry is performed, the results of the automatic journal entry are displayed in the payment journal entry work area 117. Furthermore, payment journal entry may be performed automatically based on the results of expense journal entry.

[0049] The payment journalization work area 117 has a date display field 118, a payment number display field 119, an item name display field 120, a debit information display field 121, a credit information display field 122, a summary display field 123, and a total amount display field (not shown in Figure 3).

[0050] The date display field 118 is a display field for the payment date or accounting date of the payment. For example, the current date is displayed in the date display field 118. If a date is read from an invoice or the like, the date in the date display field 118 may be set based on the read date. Alternatively, the date in the date display field 118 may be set by user input.

[0051] Payment count display field 119 is a display field for displaying the number of payments to the business partner. A drop-down button 119a is provided in payment count display field 119. The user can select the desired number of payments from a drop-down list displayed by selecting drop-down button 119a and set it in payment count display field 119. When the number of payments to the business partner has been registered in advance, the registered number of payments may be automatically set in payment count display field 119.

[0052] The item name display field 120 is a display field for the item name of the payment that has occurred. The user can set an item name corresponding to the payment that has occurred in the item name display field 120. Input into the item name display field 112 may be made based on the results of reading an invoice or the like. Furthermore, the item name displayed in the item name display field 120 may be set based on the item name displayed in the item name display field 112.

[0053] The debit information display field 121 is a display field for various information about the debit displayed on the left side of the payment journalization work area 117. Similar to the debit information display field 113 in the expense journalization work area 110, the debit information display field 121 has, for example, an amount display field, an account item display field, a sub-account display field, a tax category display field, a tax rate category display field, a recording department code display field, a customer code display field, a project code display field, and a general code display field. The content displayed in these display fields is the same as the corresponding display fields in the debit information display field 113, except that the information displayed is information about the debit side of the payment. Therefore, a description of the debit information display field 121 will be omitted.

[0054] The credit information display field 122 is a display field for various information about the credit side that is displayed to the right of the payment journalization work area 117. Similar to the credit information display field 114 in the expense journalization work area 110, the credit information display field 122 has, for example, an amount display field, an account item display field, a sub-account display field, a tax category display field, a tax rate category display field, a recording department code display field, a customer code display field, a project code display field, and a general-purpose code display field. The content displayed in these display fields is the same as the corresponding display fields in the credit information display field 114, except that the information displayed is information about the credit side of the payment. Therefore, a description of the credit information display field 122 will be omitted.

[0055] Summary display field 123 is a display field for displaying a summary of the journal entry results for the corresponding payment. The user can enter details of the transaction, such as the transaction date, control number, customer, amount, and product name, as a summary in summary display field 123. Alternatively, by using reserved words or the like, the system may be configured so that details read from data such as an invoice are automatically inserted into summary display field 123.

[0056] Furthermore, the top screen is provided with a scroll bar 124. By operating the scroll bar 124, the user can check the contents of the top screen that cannot be displayed on the display 15, such as the debit information display field 121 and the credit information display field 122.

[0057] Now, returning to the explanation of Fig. 2, in step S2, processor 11 determines whether or not the user has requested uploading of the journalization target. For example, if upload button 106 is selected, it is determined that an upload request has been made. If it is determined in step S2 that an upload request has been made, the process proceeds to step S3. If it is determined in step S2 that an upload request has not been made, the process proceeds to step S8.

[0058] In step S3, processor 11 displays an upload screen for the journalization target. On the upload screen, the user can select the journalization target file to be uploaded. Alternatively, on the upload screen, the user can activate the camera and upload an image captured by the camera as the journalization target file. On the upload screen, uploading is not limited to being performed for a single file, and multiple files may be uploaded at once.

[0059] In step S4, processor 11 determines whether uploading has been performed on the upload screen. If it is determined in step S4 that uploading has been performed, the process proceeds to step S5. If it is determined in step S4 that uploading has not been performed, the process proceeds to step S6.

[0060] In step S5, processor 11 recognizes information necessary for automatic journalization from the uploaded journalization target. For example, processor 11 recognizes the date, amount, product name, business partner name, etc. that can be read as text on a document such as an invoice as the journalization target. If the uploaded journalization target is an image, processor 11 recognizes the necessary information by OCR (Optical Character Recognition) processing. Once recognition is complete, processor 11 stores the recognized information. Then, the process proceeds to step S6.

[0061] In step S6, processor 11 determines whether the user has instructed the completion of the upload of the journalization target. If it is determined in step S6 that the user has instructed the completion of the upload of the journalization target, the process proceeds to step S7. If it is determined in step S6 that the user has not instructed the completion of the upload of the journalization target, the process returns to step S4.

[0062] In step S7, the processor 11 performs automatic journalization based on the recognized information. When the journalization classification checkbox 109 is checked, automatic journalization is performed separately for expense journalization and payment journalization. Then, based on the results of the automatic journalization, the displays in the expense journalization work area 110 and the payment journalization work area 117 are updated. On the other hand, when the journalization classification checkbox 109 is not checked, automatic journalization is performed that aggregates expense journalization and payment journalization. Then, based on the results of the automatic journalization, the display in the payment journalization work area 117 is updated. As described above, the user can edit the automatically journalized content. After processing in step S7, the process returns to step S4.

[0063] In step S8, processor 11 determines whether or not to display past journal data. For example, when the user selects past journal button 105, it is determined that past journal data is to be displayed. If it is determined in step S8 that past journal data is to be displayed, the process proceeds to step S9. If it is determined in step S8 that past journal data is not to be displayed, the process proceeds to step S18.

[0064] In step S9, a search screen for past journalizing data is displayed on the display 15. FIGS. 4A and 4B are diagrams showing examples of search screens for past journalizing data. The search screen 200 in FIG. 4A is displayed when simple search 201a is selected from the search mode selection radio buttons. On the other hand, the search screen 200 in FIG. 4B is displayed when advanced search 201b is selected from the search mode selection radio buttons.

[0065] The simple search screen 200 shown in Fig. 4A has an item name / summary input field 202 and a search execution button 206. The user can input search keywords in the item name / summary input field 202. The search execution button 206 is a button selected by the user when instructing the execution of a search.

[0066] After a search keyword is entered in the item name / summary input field 202, a simple search is executed by selecting the search execution button 206. In the simple search, past journal entry data that includes the search keyword entered by the user in the item name or summary is searched for.

[0067] The search screen 200 for the advanced search shown in FIG. 4B includes an item name and summary input field 202, a payee input field 203, journal classification selection check boxes 204a, 204b, and 204c, an account title input field 205a, a subaccount input field 205b, a debit check box 205c, a credit check box 205d, and a search execution button 206. The user can enter search keywords in the item name and summary input field 202, the payee input field 203, the account title input field 205a, and the subaccount input field 205b. The user can also check each of the debit check box 205c and the credit check box 205d. The user can also check each of the journal classification selection check boxes 204a, 204b, and 204c.

[0068] After a search keyword is entered in at least one of the item name / summary input field 202, the payee input field 203, the account title input field 205a, and the subaccount input field 205b, a detailed search is executed by selecting the search execution button 206. In the detailed search, past journal data that includes the search keyword entered by the user in the item name, summary, payee, account title, or subaccount is searched for. Here, if the debit checkbox 205c is checked, past journal data that includes the search keyword entered by the user in the account title input field 205a as a debit account title or past journal data that includes the search keyword entered in the subaccount input field 205b as a debit subaccount is searched for. Similarly, if the credit checkbox 205d is checked, past journal data that includes the search keyword entered by the user in the account title input field 205a as a credit account title or past journal data that includes the search keyword entered in the subaccount input field 205b as a credit subaccount is searched for. Furthermore, if the journal entry classification selection checkbox 204a is checked, past journal entry data that includes the user-entered search keyword in the expense journal entry item name or summary, payee, account title, or sub-item is searched. If the journal entry classification selection checkbox 204b is checked, past journal entry data that includes the user-entered search keyword in the payment journal entry item name or summary, payee, account title, or sub-item is searched. If the journal entry classification selection checkbox 204c is checked, past journal entry data that includes the user-entered search keyword in the expense journal entry item name or summary, payee, account title, or sub-item is searched for journal entry data divided into expense journal entries and payment journal entries. For journal entry data that is not divided into expense journal entries and payment journal entries, past journal entry data that includes the user-entered search keyword in the payment journal entry item name or summary, payee, account title, or sub-item is searched for.

[0069] Returning now to the description of FIG. 2, in step S10, processor 11 determines whether or not to execute a search. For example, it is determined that a search is to be executed when search execution button 206 is selected. If it is not determined that a search is to be executed in step S10, the processing is put on hold. If it is determined that a search is to be executed in step S10, the processing proceeds to step S11.

[0070] In step S11, the processor 11 searches for past journal data, for example, from the storage 13, according to the search conditions input by the user, and displays the searched past journal data on the display 15. Figure 5 is a diagram showing an example of displaying past journal data.

[0071] The example past journal data display 300 includes a search result number display field 301, a search page display field 302, display order setting buttons 303a, 303b, 303c, and 303d, and a search result display field 304.

[0072] The search result number display field 301 is a display field for displaying the total number of past journal data retrieved by the search in step S10 and the number of journal data displayed in a list. In FIG. 5, the search result number display field 301 indicates that there are six past journal data, of which the first to sixth are displayed in a list. The search result number display field 301 is provided with a list display number display field 301a. The list display number display field 301a is a display field for displaying the number of past journal data to be displayed in a list. The user can input a desired number in the list display number display field 301a. If the total number of searched past journal data exceeds the number displayed in the list display number display field 301a, the number of past journal data displayed in the search result display field 304 is limited to the number displayed in the list display number display field 301a.

[0073] The search page display field 302 is a display field for displaying the page number of the past journal data currently displayed in the search result display field 304. The search page display field 302 is provided with a page forward button 302a, a page back button 302b, and a back to top button 302c. The page forward button 302a is a button selected by the user when sending the display in the search result display field 304 to the next page. The page back button 302b is a button selected by the user when returning the display in the search result display field 304 to the previous page. The back to top button 302c is a button selected by the user when returning the display in the search result display field 304 to the first page. Although not shown in FIG. 5, the search page display field 302 may also be provided with a last page forward button. The last page forward button is a button selected by the user when sending the display in the search result display field 304 to the last page.

[0074] The display order setting buttons 303a, 303b, 303c, and 303d are buttons selected by the user when rearranging the display order of searched past journal data. The accounting date button 303a is a button selected by the user when rearranging the display order of past journal data in descending or ascending order by accounting date. The journal status button 303b is a button selected by the user when rearranging the display order of past journal data to prioritize completed or incomplete journal data. The management number button 303c is a button selected by the user when rearranging the display order of past journal data in descending or ascending order by management number. The payee button 303d is a button selected by the user when rearranging the display order of past journal data in descending or ascending order by payee.

[0075] The search result display field 304 is a display field for displaying the searched past journal data. In the search result display field 304, a list of the searched past journal data is displayed in the display order set by the display order setting buttons 303a, 303b, 303c, and 303d. The search result display field 304 for one journal data has, for example, a date display field 3041, a payment destination display field 3042, an attached data display field 3043, a control number display field 3044, a journal status display field 3045, an all selection button 3046, and a journal data display field 3047.

[0076] The date display field 3041 is a display field for displaying the accounting date. If the accounting date for the expense and the accounting date for the payment are different, the respective accounting dates may be displayed in the date display field 3041. The payee display field 3042 is a display field for displaying the payee. The attached data display field 3043 is a display field for an icon indicating whether or not attached data is present. If attached data is present, a download button 3043a is displayed in the attached data display field 3043. When the download button 3043a is selected, the contents of the attached data are displayed. The contents of the attached data may be displayed alongside the corresponding journal data or in a separate window. The control number display field 3044 is a display field for the control number assigned to the journal data. The journal entry status display field 3045 is a display field for an icon indicating whether or not the creation of the corresponding journal data has been completed. If the creation of the corresponding journal data has been completed, an icon including the string "journal entry data created" is displayed in the journal entry status display field 3045.

[0077] The all selection button 3046 is provided, for example, in the upper left corner of each piece of past journal data displayed in the journal data display field 3047. When the all selection button 3046 is selected, all of the past journal data displayed in the corresponding journal data display field 3047 is selected.

[0078] The journal data display field 3047 is a display field for displaying the actual data of each past journal entry. Specifically, the journal data display field 3047 displays an item name 3047a, journal entry results 3047b such as the debit amount, account title, and sub-account, journal entry results 3047c such as the credit amount, account title, and sub-account, and a summary 3047d. Furthermore, if journal entries are performed separately for expense journal entries and payment journal entries, the journal data display field 3047 also displays the expense journal entry results and the payment journal entry results separately. Furthermore, if journal entries are performed separately for expense journal entries and payment journal entries, row selection buttons 3047e are displayed in the upper left corner of each expense journal entry result and each payment journal entry result. When a row selection button 3047e is selected, the data for the corresponding row is selected.

[0079] Furthermore, the example search result display field 304 is provided with a scroll bar 3048. By operating the scroll bar 3048, the user can check the display of the journal data display field 3047 that cannot be displayed on the display 15.

[0080] The initial display position of the display 300 of past journal data on the display 15 is, but is not limited to, the lower right corner of the top screen, for example, as shown in Fig. 5. By setting the initial display position of the display 300 of past journal data to the lower right corner of the top screen, the save button 101, apply button 102, cancel button 103, settings button 104, past journal button 105, upload button 106, copy button 107, paste button 108, and journal classification check box 109 displayed in the button display area 100 are not hidden by the display 300 of past journal data.

[0081] Now, returning to the explanation of Figure 2, in step S12, processor 11 determines whether or not a copy operation of past journal data has been performed. The copy operation of past journal data can be, for example, a selection operation of copy button 107 after selecting all selection button 3046 or each row selection button 3047e, or a drag operation with all selection button 3046 or each row selection button 3047e selected. If it is determined in step S12 that a copy operation of past journal data has been performed, the process proceeds to step S13. If it is not determined in step S12 that a copy operation of past journal data has been performed, the process proceeds to step S16.

[0082] In step S13, processor 11 copies the past journal data selected by the user and stores it in, for example, memory 12. For example, if the user performs a drag operation on data 400 of the expense journal entry results displayed in journal data display field 3047 as shown in FIG.

[0083] In step S14, processor 11 determines whether a paste operation of past journal data has been performed. The paste operation of past journal data can be, for example, a selection operation of paste button 108 after a copy operation has been performed and a paste destination has been specified, or a drop operation onto the paste destination after a drag operation of past journal data. If it is determined in step S14 that a paste operation of past journal data has been performed, processing proceeds to step S15. If it is not determined in step S14 that a paste operation of past journal data has been performed, processing proceeds to step S16.

[0084] In step S15, processor 11 pastes the debit data from the past journalization data stored in memory 12 into each debit display field of expense journalization work area 110 specified by the user. Thereafter, the process proceeds to step S7.

[0085] Specifically, when the journal entry classification checkbox 109 is checked and the journal entries are divided into expense journal entries and payment journal entries, and the paste destination is the expense journal entry work area 110, processor 11 pastes the debit data from the past journal entry data stored in memory 12 into each display field of the debit information display field 113 of the expense journal entry work area 110. On the other hand, processor 11 does not paste the credit data from the past journal entry data stored in memory 12 into each input field of the credit information display field 114 of the expense journal entry work area 110. For example, when data 400 of the expense journal entry results copied as shown in FIG. 6 is dragged to the expense journal entry work area 110, processor 11 pastes the debit data from the dragged expense journal entry data 400 into each display field of the debit information display field 113 of the expense journal entry work area 110, as shown in FIG. 7. Figure 7 shows an example in which the amount in the expense journal entry result data 400 is pasted in the amount display column 1131, the account item in the account item display column 1132, the sub-account in the sub-account display column 1133, and the tax category in the tax category display column 1134.

[0086] Furthermore, although not shown in the figure, when the journal entry classification checkbox 109 is not checked and the journal entry is not separated into expense journal entries and payment journal entries, the processor 11 pastes the debit data from the past journal entry data stored in the memory 12 into each display field of the debit information display field 121 in the payment journal entry work area 117. On the other hand, the processor 11 does not paste the credit data from the past journal entry data stored in the memory 12 into each input field of the credit information display field 122 in the payment journal entry work area 117. This is because when expense journal entries and payment journal entries are not separated, the debit account item of the aggregated payment journal entry matches the debit account item of the expense journal entry.

[0087] FIG. 7 shows an example in which amounts, account items, sub-accounts, and tax classifications are pasted. Here, amounts may be entered based on the results of scanning an invoice or the like. Amounts entered based on the results of scanning are likely to be more accurate than those in past journal data. Therefore, if amounts have already been entered, the system may be configured so that they are not pasted from past journal data.

[0088] As shown in Figure 7, when pasting past journal data, item names may also be pasted. Here, when pasting item names, if the item name of the source journal data contains a term indicating the month, such as "August," it is desirable to automatically replace the month before pasting. This automatic month replacement determines whether the month listed in the source matches the billing date or the accounting date. Then, the month of the same item name in the payment information of the destination is obtained and replaced with that month. If the billing month and accounting month of the source do not match, the difference in months between the month in the item name and the billing month is obtained, and the difference is added to the billing date of the destination. For example, if the billing date of the source is "August 30, 2023" and the item name of the source is "September Rent," the billing date of the destination is "September 30, 2023," so the item name of the destination is pasted as "October Rent," shifted by one month.

[0089] Typically, item names include the month but not the year. Therefore, if the billing date of the original is "August 30, 2023" and the item name of the original is "September Rent," in order to determine that the item name is actually off by one month, it is necessary to determine that the "September" in the item name is "September 2023." The year to which the month belongs can be determined by considering three options: this year, last year, and next year, and then determining which year's billing date the month is closest to. For example, if the billing date of the original is December 30, 2023, and the item name is "January Rent," the January in the item name should be determined to be "January 2024."

[0090] In addition, item names may be input based on the results of scanning an invoice or the like. Item names input based on the results of scanning are more likely to be accurate than those in past journal data. Therefore, if an item name has already been input, it may be configured so that it is not pasted from past journal data.

[0091] Furthermore, summaries of past journal data may be set using reserved words, and pasting them may actually cause errors, so they do not need to be pasted.

[0092] Returning now to the explanation of Figure 2, after pasting, the process proceeds to step S7, where processor 11 executes automatic journalization. At this time, processor 11 does not subject display fields that already have entries to automatic journalization, but subjects only display fields that have not yet been entered to automatic journalization. For example, when debit data is entered into debit information display field 113 of expense journalization work area 110 as shown in Figure 7, processor 11 creates credit data to be displayed in credit information display field 114 of expense journalization work area 110 by automatic journalization. As a result of the automatic journalization, the results of the automatic journalization are displayed in each display field of credit information display field 114, as shown in Figure 8.

[0093] Here, when expense journal entries and payment journal entries are separated, the debit account item of the payment journal entry matches the credit account item of the expense journal entry. Therefore, the credit data from the expense journal entry work area 110 obtained as a result of automatic journal entry may be pasted into the debit information display field 121 of the payment journal entry work area 117. In this case, automatic journal entry for payment journal entries only requires automatic journal entry of the credit data to be displayed in the credit information display field 122 of the payment journal entry work area 117.

[0094] Now, returning to the explanation of Figure 2, in step S16, if it is determined that a copy operation has not been performed in step S12 or that a paste operation has not been performed in step S14, the processor 11 determines whether or not to end the display of the past journal data. For example, if a display end button (not shown) displayed on the display 300 of the past journal data is selected, it is determined that the display of the past journal data is to end. If it is determined in step S16 that the display of the past journal data is to end, the processing proceeds to step S17. If it is determined in step S16 that the display of the past journal data is not to end, the processing returns to step S2.

[0095] In step S17, the processor 11 ends the display of the past journalizing data display 300. Thereafter, the processing returns to step S2.

[0096] In step S18, if it is determined in step S8 that past journal data will not be displayed, processor 11 determines whether or not to save the journal data. For example, if save button 101 is selected, it is determined that the journal data will be saved. If it is determined in step S18 that the journal data will be saved, the process proceeds to step S19. If it is determined in step S18 that the journal data will not be saved, the process proceeds to step S20.

[0097] In step S19, the processor 11 saves the journal data created based on the data set in the current expense journalizing work area 110 and payment journalizing work area 117 as journalizing data 133 in the storage 13. Then, the process returns to step S2.

[0098] In step S20, processor 11 determines whether or not to process the application. For example, if application button 102 is selected, it is determined that the application process is to be performed. If it is determined in step S20 that the application process is to be performed, the process proceeds to step S21. If it is determined in step S20 that the application process is not to be performed, the process returns to step S2.

[0099] In step S21, processor 11 executes application processing based on the data currently set in expense journal entry work area 110 and payment journal entry work area 117. For example, processor 11 transmits data such as invoices together with journal entry data to a predetermined application destination. Then, processing returns to step S2.

[0100] As described above, according to the embodiment, a user can search for and refer to past journal entry data during journal entry work. The user can then paste the contents of the past journal entry data into the journal entry work area during the current work. When pasting in the embodiment, debit data from past expense journal entries is pasted into the debit data from expense journal entries, while credit data from past expense journal entries is not pasted into the credit data from expense journal entries.

[0101] Generally, in accounting work, it is often the debit entries that change primarily depending on individual circumstances. Automatic journalization of such entries that change depending on individual circumstances is prone to errors. On the other hand, credit entries are often uniquely determined depending on the conditions of the transaction, and errors caused by automatic journalization are rare. Therefore, in the embodiment, past journal entry data can be pasted for debit entries that are prone to errors in automatic journalization, and automatic journalization is performed for credit entries that are less prone to errors in automatic journalization. This makes it possible to improve journalization accuracy while suppressing the complexity of journalization processing, even when transactions include transactions that require journalization results to be changed depending on individual circumstances.

[0102] Here, in the embodiment, the journalizing process by the automatic journalizing program 132 is performed in the terminal 1. However, the journalizing process may be performed in a device other than the terminal 1, such as a server with which the terminal 1 can communicate. In this case, the server or the like will hold the automatic journalizing program 132.

[0103] Furthermore, each process according to the above-described embodiment can be stored as a program that can be executed by the processor 11, which is a computer. Alternatively, the program can be stored in a storage medium of an external storage device such as a magnetic disk, an optical disk, or a semiconductor memory and distributed. The processor 11 can then load the program stored in the storage medium of the external storage device, and its operation can be controlled by the loaded program, thereby executing the above-described process.

[0104] The present invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in appropriate combinations, in which case the combined effects can be obtained. Furthermore, the above-described embodiments include various inventions, and various inventions can be extracted by combining selected elements from the disclosed elements. For example, if the problem can be solved and the desired effect can be obtained even if some elements are deleted from all elements shown in the embodiments, the configuration from which these elements are deleted can be extracted as an invention. [Explanation of symbols]

[0105] 1 Terminal, 11 Processor, 12 Memory, 13 Storage, 14 Input Interface, 15 Display, 16 Communication Module, 17 Bus, 132 Automatic Journal Program.

Claims

1. Searching for past journal data according to search conditions set by a user; Displaying the searched past journal data on a display screen; Based on a copy operation and a paste operation for the past journal data displayed on the display screen, only the debit data of the debit data and the credit data of the past journal data is set in a debit column of a journal work area for journal work displayed on the display screen; generating credit data corresponding to the set debit data by automatic journalization; An automatic journal entry program for causing a processor to execute the above.

2. The journal entry work area is divided into an expense journal entry work area for journalizing expenses incurred by a transaction, and a payment journal entry work area for journalizing payments incurred by a transaction, Setting the debit data of the past journal data in the debit column of the journal entry work area displayed on the display screen means setting the debit data of the past journal data in the debit column of the expense journal entry work area, Generating credit data corresponding to the set debit data by automatic journalization includes generating credit data corresponding to the debit data set in the debit column of the expense journalization work area by automatic journalization and setting the credit data in the credit column of the expense journalization work area. The automatic journalizing program according to claim 1.

3. 3. The automatic journalizing program according to claim 2, further causing the processor to set credit data set in the credit column of the expense journalizing work area as corresponding debit data in the debit column of the payment journalizing work area.

Images