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] The present embodiment relates to an automatic accounting 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 contents of various transactions described in documents such as invoices are journalized into account items according to various predefined rules, such as tax rules, accounting rules, and company rules. In general, automatic journal entries are prone to errors in journal entries for transactions that require different journal entries depending on individual circumstances. Although it is possible to deal with this to some extent by setting rules for each individual circumstance, the automatic journal entry process becomes complicated, making it difficult to identify the journal entry results, and journal entry processing takes time. In addition, when setting rules, it is difficult to understand the relationship between the rules and the journal entry results, and it is also expected that setting rules in the first place will be difficult.

[0005] The embodiment aims to provide an automatic accounting program that can improve accounting accuracy while suppressing the complexity of accounting processing, 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 embodiment, the automatic journal entry program causes a processor to search for past journal entry data in accordance with search conditions set by a user, display the searched past journal entry data on a display screen, set debit data from the past journal entry data in the debit column of the journal entry work area for journal entry work displayed on the display screen based on copy and paste operations on the past journal entry data displayed on the display screen, and generate credit data corresponding to the set debit data by automatic journal entry. Effect of the Invention

[0007] According to an embodiment, an automatic accounting program can be provided that can improve accounting accuracy while suppressing the complexity of accounting processing, even when transactions include transactions in which the accounting results need to be changed depending on individual circumstances. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of a terminal according to an embodiment. [Diagram 2] FIG. 2 is a flowchart showing the automatic accounting process in the terminal. [Diagram 3] FIG. 3 is a diagram showing an example of a top screen. [Figure 4A] FIG. 4A is a diagram showing an example of a search screen for past journal entry data. [Figure 4B] FIG. 4B is a diagram showing an example of a search screen for past journal entry data. [Diagram 5] FIG. 5 is a diagram showing an example of display of past journal entry data. [Figure 6] FIG. 6 is a diagram showing a drag operation of past journal entry data. [Figure 7] FIG. 7 is a diagram showing a screen on which past journal entry 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 PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment will be described with reference to the drawings. FIG. 1 is a diagram showing a 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 according to 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. In addition, 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, for example, 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 implementing 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. The automatic journalizing processing is a process of classifying input transactions into appropriate account items according to their contents and calculating the amount for each account item. The contents of the transactions are entered in documents such as invoices or data containing contents equivalent to documents. The automatic journalizing program 132 may be installed in the terminal 1 as necessary. Note that the transactions in the embodiment are not particularly limited as long as they are transactions that can be subject to automatic journalizing. The automatic journalizing may be performed on a rule 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 journalizing result data selected by the user is copied. Specifically, only journalizing result data that may vary depending on individual circumstances and is therefore prone to errors in the automatic journalizing results is copied, and journalizing result data that is less likely to vary depending on individual circumstances and is therefore less likely to cause errors in the automatic journalizing results is not copied. As will be explained in detail later, journalizing result data that may vary depending on individual circumstances and is therefore prone to cause errors in the automatic journalizing results is the debit journalizing result data of expense journalizing.

[0016] The journal data 133 is journal data created by the automatic journal 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 of an invoice. 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, a keyboard, and a 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 according 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 printer 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, or the like. Alternatively, the communication module 16 is configured to connect to a device in the vicinity of the terminal 1 by short-range wireless communication such as Bluetooth (registered trademark).

[0020] Next, an operation of the terminal 1 based on the automatic journalizing program 132 in the embodiment will be described. Fig. 2 is a flowchart showing the automatic journalizing process in the terminal 1. The process in Fig. 2 is started, for example, when 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 on the display 15 the top screen of the automatic accounting program 132. Fig. 3 is a diagram showing an example of the top screen.

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

[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 performing application processing by sending accounting data to a predetermined application destination. The application destination is a department that receives invoices, a department that settles expenses, etc., and is determined in advance 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 journalization data without saving it. The setting button 104 is a button selected by the user when making various settings related to the automatic journalization program 132, such as journalization rule settings and display settings.

[0026] The past journalizing button 105 is a button selected by the user when referring to previously created journalizing data 133. When the past journalizing 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 is the source of automatic journalization. Here, the journalization target data to be uploaded may be data in various formats such as text data representing the contents described in a document such as an invoice, tabular data representing the contents described in a document such as an invoice, image data of a document such as an invoice, etc. 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 copied by selecting the copy button 107, etc.

[0029] The journal entry classification check box 109 is a check box for the user to select whether or not to perform journal entry work separately into expense journal entry and payment journal entry. When the journal entry classification check box 109 is checked, the expense journal entry and the payment journal entry are performed separately. The expense journal entry is a journal entry related to the expense generated by the transaction, and is performed so that an increase in expense or asset is debited and an increase in liability accompanying the increase in expense or asset is credited. The payment journal entry is a journal entry related to the payment generated by the transaction, and is performed so that a decrease in liability is debited and a decrease in asset accompanying the decrease in liability is credited. When the journal entry classification check box 109 is not checked, one payment journal entry in which the expense journal entry and the payment journal entry are integrated is performed. In the integrated payment journal entry, journal entries are performed so that an increase in expense or asset generated by the transaction is debited and a decrease in asset accompanying the increase in expense or asset is credited.

[0030] Furthermore, when the journal entry classification checkbox 109 is checked, the top screen in one 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 contents in the expense journal entry work area 110. Furthermore, when automatic journal entry is performed, the result of the automatic journal entry is 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. For example, the current date is displayed in the date display field 111. 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 date read. Alternatively, the date in the date display field 111 may be set by input from the user.

[0033] The item name display field 112 is a display field for the item names of incurred expenses. 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 an 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 is an item name that should be accounted for under multiple account items, there are provided an amount display column 1131 corresponding to each item name, an account item display column 1132, a sub-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-purpose code display column 1139.

[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 based on reading from data such as an invoice. The amount display field 1131 displays an amount including tax. On the other hand, the amount display field 1131 displays an 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 title display field 1132 is a display field for the account title to be journalized. The account title is specified based on the result of automatic journalization based on the item name, amount, etc. The account title 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 when displaying a drop-down list of account titles. The user can select a desired account title from the drop-down list displayed by selecting the drop-down button 1132a and set it in the account title display field 1132. The delete button 1132b is a button selected by the user when deleting an account title displayed in the account title display field 1132. The drop-down button 1132a and the delete button 1132b allow the user to correct an error in an account title due to automatic journalization.

[0037] The subaccount display field 1133 is a display field for the subaccount to be journalized. The subaccount is specified based on the result of automatic journalization based on the item name, amount, etc., in the same way as the account. 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 when displaying a drop-down list of subaccounts. The user can select a 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 when deleting a subaccount displayed in the subaccount display field 1133. The drop-down button 1133a and the delete button 1133b allow the user to correct an error in the subaccount due to automatic journalization.

[0038] The tax category display field 1134 is a display field for the tax category of the consumption tax to be accounted for. The tax category is specified based on the result of automatic accounting based on the item name, etc., in the same way as 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 when displaying a drop-down list of tax categories. The user can select a 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 when deleting a 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 an error in the tax category due to automatic accounting.

[0039] The tax rate category display field 1135 is a display field for tax rate categories that indicate the meaning of the tax rate of the consumption tax to be accounted for. For example, the tax rate category is provided to indicate whether the tax rate is a standard tax rate or a reduced tax rate. The tax rate category is specified based on the setting of the tax category display field 1134 and the result of automatic accounting 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 a desired tax rate from a drop-down list that is displayed by selecting the drop-down button 1135a and set it in the tax rate category display field 1135.

[0040] The appropriation department code display field 1136 is a display field for displaying the appropriation department code. The appropriation department code is a code assigned to each department to which an expense is appropriated. The appropriation department code is identified based on the results of automatic accounting based on the item name, amount, etc., in the same way as with account items. The appropriation department code display field 1136 is provided with a drop-down button 1136a. The user can select the desired appropriation department code from the drop-down list displayed by selecting the drop-down button 1136a and set it in the appropriation 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 specified based on the supplier name, etc., read from the data of the invoice, etc.

[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 cost 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 client, expenses not related to a project, etc.

[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 has, for example, an amount display field 1141, an account item display field 1142, a sub-account item display field 1143, a tax classification display field 1144, a tax rate classification 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 the debit and credit sides correspond to each other in a N-to-N manner in journalizing, the same display fields are provided. In other words, the credit information display field 114 is also provided for each account item to be journalized. Therefore, when there are item names to be accounted for under a plurality of account items, there are provided an amount display column 1141 corresponding to each item name, an account item display column 1142, a sub-item display column 1143, a tax category display column 1144, a tax rate category display column 1145, an accounting department code display column 1146, a client code display column 1147, a project code display column 1148, and a general-purpose code display column 1149. Here, the debit information display column 113 and the 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 field 1141, account title display field 1142, sub-account display field 1143, tax category display field 1144, tax rate category display field 1145, recording department code display field 1146, customer code display field 1147, project code display field 1148, and general code display field 1149 of the credit information display field 114 are the same as the corresponding display fields of the debit information display field 113, except that the information of expenses or assets as the debit side is replaced with the information of liabilities as the credit side and displayed. Therefore, the explanation of the amount display field 1141, account title display field 1142, sub-account display field 1143, tax category display field 1144, tax rate category display field 1145, recording department code display field 1146, customer code display field 1147, project code display field 1148, and general code display field 1149 of the credit information display field 114 will be omitted.

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

[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 to 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 to 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. A user can input journal entry content in the payment journal entry work area 117. Furthermore, when automatic journal entry is performed, the result of the automatic journal entry is displayed in the payment journal entry work area 117. Furthermore, payment journal entry may be performed automatically based on the result of expense journal entry.

[0049] The payment journalizing 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 FIG. 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 date read. Alternatively, the date in the date display field 118 may be set by input from the user.

[0051] Payment count display field 119 is a display field for displaying the number of payments to a 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 a 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 journalizing work area 117. Like the debit information display field 113 in the expense journalizing work area 110, the debit information display field 121 has, for example, an amount display field, an account item display field, a sub-item display field, a tax category display field, a tax rate category display field, an accounting department code display field, a client code display field, a project code display field, and a general-purpose code display field. The contents displayed in these display fields are the same as the corresponding display fields in the debit information display field 113, except that the information displayed is information about the debit 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 displayed to the right of the payment journalizing work area 117. Like the credit information display field 114 in the expense journalizing work area 110, the credit information display field 122 has, for example, an amount display field, an account item display field, a sub-item display field, a tax category display field, a tax rate category display field, an accounting department code display field, a client code display field, a project code display field, and a general-purpose code display field. The contents displayed in these display fields are 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] The summary display field 123 is a display field for displaying a summary of the corresponding payment accounting results. The user may enter details of the transaction, such as the transaction date, control number, business partner, amount, and item name, as a summary in the summary display field 123. Alternatively, the system may be configured so that details read from data such as an invoice are automatically inserted into the summary display field 123 by using reserved words or the like.

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

[0057] Returning now to the explanation of Fig. 2, in step S2, processor 11 determines whether or not a request for uploading of the journalization target has been made by the user. 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, the processor 11 displays an upload screen for the journalization target. On the upload screen, the user may select a journalization target file to be uploaded. Alternatively, on the upload screen, the user may start up 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 one file, and uploading multiple files at once may also be performed.

[0059] In step S4, processor 11 determines whether or not 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, the processor 11 recognizes information necessary for automatic journalizing from the uploaded journalizing target. For example, the 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 journalizing target. When the uploaded journalizing target is an image, the processor 11 recognizes the necessary information by OCR (Optical Character Recognition) processing. When recognition is performed, the processor 11 holds the recognized information. After that, the process proceeds to step S6.

[0061] In step S6, the processor 11 determines whether or not the user has instructed the completion of the upload of the journalizing object. If it is determined in step S6 that the user has instructed the completion of the upload of the journalizing object, 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 journalizing object, the process returns to step S4.

[0062] In step S7, the processor 11 executes automatic journal entry based on the recognized information. When the journal entry classification checkbox 109 is checked, automatic journal entry is performed separately for expense journal entry and payment journal entry. Then, based on the result of the automatic journal entry, the display of the expense journal entry work area 110 and the payment journal entry work area 117 is updated. On the other hand, when the journal entry classification checkbox 109 is not checked, automatic journal entry is performed by integrating expense journal entry and payment journal entry. Then, based on the result of the automatic journal entry, the display of the payment journal entry work area 117 is updated. As described above, the user may edit the automatically journalized content. After the processing of step S7, the process returns to step S4.

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

[0064] In step S9, a search screen for past journal data is displayed on the display 15. Figures 4A and 4B are diagrams showing examples of search screens for past journal data. The search screen 200 in Figure 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 Figure 4B is displayed when detailed search 201b is selected from the search mode selection radio buttons.

[0065] 4A includes an item name / summary input field 202 and a search execution button 206. A user can input a search keyword into 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 of the detailed search shown in FIG. 4B has 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 may input 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 may also check each of the debit check box 205c and the credit check box 205d. The user may also check each of the journal classification selection check boxes 204a, 204b, and 204c.

[0068] After a search keyword is input in at least one of the item name / description input field 202, the payee input field 203, the account title input field 205a, and the sub-account 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 input by the user in the item name or description, the payee, the account title, or the sub-account is searched for. Here, if the debit check box 205c is checked, past journal data that includes the search keyword input by the user in the account title input field 205a in the debit account title or past journal data that includes the search keyword input by the user in the sub-account input field 205b in the debit sub-account is searched for. Similarly, if the credit check box 205d is checked, past journal data that includes the search keyword input by the user in the account title input field 205a in the credit account title or past journal data that includes the search keyword input by the user in the sub-account input field 205b in the credit sub-account is searched for. Furthermore, when the journal classification selection checkbox 204a is checked, past journal data that includes the search keyword entered by the user in the item name or summary of the expense journal, the payee or account, or the sub-item is searched for. When the journal classification selection checkbox 204b is checked, past journal data that includes the search keyword entered by the user in the item name or summary of the payment journal, the payee or account, or the sub-item is searched for. When the journal classification selection checkbox 204c is checked, past journal data that includes the search keyword entered by the user in the item name or summary of the expense journal, the payee or account, or the sub-item is searched for journal data that is divided into expense journal and payment journal, and past journal data that includes the search keyword entered by the user in the item name or summary of the payment journal, the payee or account, or the sub-item is searched for journal data that is not divided into expense journal and payment journal.

[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 process is put on hold. If it is determined that a search is to be executed in step S10, the process 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 display of past journal data.

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

[0072] The search number display field 301 is a display field for displaying the total number of past journal data searched by the search in step S10 and the number of journal data displayed in a list. In FIG. 5, the search 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 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 top back button 302c. The page forward button 302a is a button selected by the user when sending the display of the search result display field 304 to the previous page. The page back button 302b is a button selected by the user when returning the display of the search result display field 304 to the previous page. The top back button 302c is a button selected by the user when returning the display of the search result display field 304 to the first page. Although not shown in FIG. 5, the search page display field 302 may be provided with a last page forward button. The last page forward button is a button selected by the user when sending the display of 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 sorting the display order of searched past journal data. The accounting date button 303a is a button selected by the user when sorting the display order of past journal data in descending or ascending order of accounting date. The journal status button 303b is a button selected by the user when sorting the display order of past journal data to give priority to journal data that has been completed or has not been completed. The management number button 303c is a button selected by the user when sorting the display order of past journal data in descending or ascending order of management number. The payment destination button 303d is a button selected by the user when sorting the display order of past journal data in descending or ascending order of 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 according to 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 management 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 recording date. When the recording date of the expense and the recording date of the payment are different, the respective recording 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 the presence or absence of attached data. When there is attached data, 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 side by side with the corresponding journal data, or may be displayed in a separate window. The management number display field 3044 is a display field for a management number assigned to the journal data. The journal status display field 3045 is a display field for an icon indicating whether the creation of the corresponding journal data has been completed. When the creation of the corresponding journal data has been completed, for example, an icon including the character string "journal data created" is displayed in the journal status display field 3045.

[0077] The all selection button 3046 is provided, for example, in the upper left corner of each 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 data. Specifically, the journal data display field 3047 displays the item name 3047a, the journal result 3047b such as the debit amount, account item, and subitem, the journal result 3047c such as the credit amount, account item, and subitem, and the summary 3047d. Furthermore, when journalization is performed separately for expense journalization and payment journalization, the journal data display field 3047 also displays the result of expense journalization and the result of payment journalization separately. Furthermore, when journalization is performed separately for expense journalization and payment journalization, each row selection button 3047e is displayed at the upper left of each expense journalization result and each payment journalization result. When each row selection button 3047e is selected, the data of the corresponding row is selected.

[0079] Moreover, the search result display field 304 in one example is provided with a scroll bar 3048. The user can check the display of the journalization data display field 3047 that cannot be displayed on the display 15 by operating the scroll bar 3048.

[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, the apply button 102, the cancel button 103, the settings button 104, the past journal button 105, the upload button 106, the copy button 107, the paste button 108, and the journal classification check box 109 displayed in the button display area 100 are not hidden by the display 300 of past journal data.

[0081] Returning now to the explanation of FIG. 2, in step S12, the processor 11 determines whether or not a copy operation of past journal data has been performed. The copy operation of past journal data may be, for example, a selection operation of the copy button 107 after the selection of the all selection button 3046 or the individual row selection button 3047e, or a drag operation with the all selection button 3046 or the individual 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 determined in step S12 that a copy operation of past journal data has not been performed, the process proceeds to step S16.

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

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

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

[0085] Specifically, when the journal entry classification check box 109 is checked and the journal entry is divided into an expense journal entry and a payment journal entry, if the paste destination is the expense journal entry work area 110, the processor 11 pastes the debit data of the past journal entry data stored in the 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, the processor 11 does not paste the credit data of the past journal entry data stored in the memory 12 into each input field of the credit information display field 114 of the expense journal entry work area 110. For example, when the data 400 of the result of the expense journal entry copied as shown in FIG. 6 is dragged to the expense journal entry work area 110, the processor 11 pastes the debit data of 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. FIG. 7 shows an example in which the amount in the data 400 resulting from expense journalization is pasted in an amount display field 1131, the account item in an account item display field 1132, the sub-account in a sub-account display field 1133, and the tax category in a tax category display field 1134.

[0086] Also, although not shown in the figure, when the journal entry classification checkbox 109 is not checked and the journal entry is not separated into an expense journal entry and a payment journal entry, the processor 11 pastes the debit data of the past journal entry data stored in the memory 12 into each display field of the debit information display field 121 of the payment journal entry work area 117. On the other hand, the processor 11 does not paste the credit data of the past journal entry data stored in the memory 12 into each input field of the credit information display field 122 of the payment journal entry work area 117. This is because when the expense journal entry and the payment journal entry 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 the amount, account title, sub-title, and tax category are pasted. Here, the amount may be input based on the results of reading an invoice or the like. The amount input based on the results of reading is more likely to be accurate than that of past journal data. Therefore, if the amount has already been input, it may be configured not to be pasted from past journal data.

[0088] Also, as shown in FIG. 7, when pasting journal data, the item name may also be pasted. Here, when pasting the item name, if the item name of the journal data to be copied contains a word indicating the month, such as "August," it is desirable to automatically replace the month before pasting. In such automatic month replacement, it is determined whether the month written 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 paste destination is obtained and replaced with that month. If the billing month and accounting month of the copy 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 copy destination and replaced with the month. For example, if the billing date of the copy source is "August 30, 2023" and the item name of the copy source is "September rent," the billing date of the copy destination is "September 30, 2023," so the item name of the copy destination is pasted as "October rent" shifted by one month.

[0089] Usually, the item name includes the month but not the year. Therefore, if the billing date of the copied item is "August 30, 2023" and the item name of the copied item 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 the three patterns of 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 copied item 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] Also, the item name may be input based on the results of reading an invoice or the like. The item name input based on the results of reading is more likely to be accurate than those in past journal data. Therefore, if the item name has already been input, it may be configured not to be pasted from past journal data.

[0091] Furthermore, summaries of past journal entry data may be set using reserved words, and pasting them may actually cause errors, so there is no need to paste them.

[0092] Returning now to the explanation of FIG. 2, after pasting, the process proceeds to step S7, where processor 11 executes automatic journalizing. At this time, processor 11 does not subject display columns that already have entries to automatic journalizing, but subjects only display columns that have not yet been entered to automatic journalizing. For example, when debit data is entered into debit information display column 113 of expense journalizing work area 110 as shown in FIG. 7, processor 11 creates credit data to be displayed in credit information display column 114 of expense journalizing work area 110 by automatic journalizing. As a result of automatic journalizing, the results of automatic journalizing are displayed in each display column of credit information display column 114 as shown in FIG. 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 of 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, we return to the explanation of FIG. 2. In step S16, when 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, when 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 be ended. In step S16, when it is determined that the display of the past journal data is to be ended, the process proceeds to step S17. In step S16, when it is determined that the display of the past journal data is not to be ended, the process returns to step S2.

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

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

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

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

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

[0100] As described above, according to the embodiment, the 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 of ​​the current work. When pasting in the embodiment, the debit data of the past expense journal entry is pasted into the debit data of the expense journal entry, while the credit data of the past expense journal entry is not pasted into the credit data of the expense journal entry.

[0101] In general, in accounting work, it is often the debit entries that change mainly depending on individual circumstances. Automatic journal entries for such entries that change depending on individual circumstances are prone to errors. On the other hand, credit entries are often uniquely determined depending on the conditions of the transaction, and errors due to automatic journal entries are few. For this reason, in the embodiment, it is possible to paste past journal entry data for debit entries that are prone to automatic journal entry errors, and to perform automatic journal entries for credit entries that are less likely to cause automatic journal entry errors, thereby suppressing the complexity of journal entry processing and improving journal entry accuracy even when transactions are included that require the journal entry 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. In contrast, 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 read the program stored in the storage medium of the external storage device, and the processor 11 can execute the above-described process by having its operation controlled by the read program.

[0104] The present invention is not limited to the above-mentioned embodiment, and various modifications can be made in the implementation stage without departing from the gist of the invention. In addition, the embodiments may be implemented in appropriate combination, and in that case, the combined effect can be obtained. Furthermore, the above-mentioned embodiment includes various inventions, and various inventions can be extracted by combinations selected from the multiple components disclosed. For example, if the problem can be solved and the effect can be obtained even if some components are deleted from all the components shown in the embodiment, the configuration from which the components 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 accounting program.

Claims

1. Searching for past journal entry data according to search conditions set by a user; Displaying the searched past journal entry data on a display screen; Setting the debit data of the past journal data displayed on the display screen in a debit column of a journal work area for journal work displayed on the display screen based on a copy operation and a paste operation for the past journal data displayed on the display screen; generating credit data corresponding to the set debit data by automatic journal entry; An automatic accounting program for having a processor 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 journal entry includes generating credit data corresponding to the debit data set in the debit column of the expense journal entry work area by automatic journal entry and setting the credit data in the credit column of the expense journal entry work area.

2. The automatic accounting program according to claim 1.

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

Images