Autonomous change support system, its program, and autonomous display support method

Abstract

We provide an autonomous change support system that reduces the burden on personnel in outputting data from the original source in a strictly defined format. [Solution] In transaction data where at least the date of occurrence, settlement date, and amount are known, The record based on the date of occurrence shall be the occurrence record. When the record based on the settlement date is considered a settlement record, A display unit 23 displays the settlement record screen M1 for a predetermined period, The autonomous change support system includes an execution unit 25 that enables a one-button process to change from the settlement record screen M1 to the occurrence record screen M2 in essentially one button, and / or an automatic process to change automatically at a predetermined timing during the aforementioned period.

Description

Technical Field

[0001] The present invention relates to an autonomous change support system, its program, and an autonomous display support method.

Background Art

[0002] Conventionally, since there is original data, it may seem at first glance that the workload is light. However, strict rules are defined for the output format, and the work of conforming to those rules depends on the personal response of the person in charge. As a result, there are not a few cases where an excessive burden is placed on the person in charge.

[0003] The accounting field is an example. In institutional accounting, discrepancies between books or in processing are generally not allowed. There was a culture where users (for example, accounting staff) had to manually handle the discrepancies, and thus bookkeeping or specialized knowledge related to it was required. From the perspective of reducing the burden on the person in charge, for example, an automatic journal entry system for transaction data has been proposed (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, even with a conventional automatic journal entry system such as Patent Document 1, there are situations where personal responses from the person in charge are required. Especially in recent years, as the scope in this field has expanded and the number of scenes where light users handle the work has increased, there is still room for improvement from the perspective of reducing the burden on the person in charge.

[0006] For example, while accurate period profit and loss can only be grasped based on the accrual basis, which recognizes revenue and expenses at the time a transaction occurs, even under prior art such as Patent Document 1, there were situations where the person in charge was required to track the flow of transactions and manage journal entries. Furthermore, perhaps because it is assumed that the person in charge will handle the matter in a person-dependent manner using their specialized knowledge, the flexibility of searching for various transaction data is extremely limited, and this was not considered at all in the prior art such as Patent Document 1.

[0007] Such problems are widespread in fields other than accounting, where raw data exists but strict rules are established for the output format, and the process of conforming to those rules relies on the individual skills of the person in charge.

[0008] Therefore, the object of the present invention is to provide an autonomous change support system, a program therefor, and an autonomous display support method that can support autonomous output when the output format from the original data is strictly defined, and reduce the burden on the person in charge. [Means for solving the problem]

[0009] Examples of embodiments of the present invention are as follows: [1] In transaction data where the occurrence date, settlement date, and amount are known, The record based on the date of occurrence shall be the occurrence record. When the record based on the settlement date is considered a settlement record, A display unit that displays the payment record screen for the specified period, An execution unit that enables the execution of a one-button process that essentially changes from the settlement record screen to the occurrence record screen with a single button during the aforementioned period, and / or an automatic process that changes automatically at a predetermined timing, An autonomous change support system equipped with the following features. [2] The execution unit enables the one-button process to be executed by essentially clicking an icon on the screen once, as described in item 1. [3] The execution unit enables the automated processing to be executed at at least one time interval: daily, weekly, monthly, and yearly, according to item 1 or 2. [4] The execution unit is capable of changing the timing of displaying the occurrence record screen for the automatic processing, as described in any one of items 1 to 3. [5] The aforementioned period is at least one of the following: a day, a week, a month, and a year, as described in any one of items 1 to 4. [6] The execution unit is, For settlement records that include the settlement date but do not include the occurrence date within the aforementioned period, they will be omitted from the occurrence record screen for the aforementioned period: For settlement records in which the aforementioned period includes the settlement date and also includes the occurrence date, change the settlement date to the occurrence date: and For settlement records that do not include the settlement date within the aforementioned period but do include the occurrence date, add the occurrence record corresponding to the settlement record to the occurrence record screen for the aforementioned period: A system according to any one of items 1 to 5, which performs at least one of the aforementioned processes. [7] The execution unit is, The system according to any one of items 1 to 6, wherein the settlement record screen and the occurrence record screen can be displayed in a reversible manner and / or in parallel. [8] The aforementioned transaction data includes two or more text fields, A system described in any one of items 1 to 7, further comprising a search unit that performs a cross-sectional refinement search targeting the content entered in the two or more text fields mentioned above. [9] The text field is the system described in field 8, which includes at least one of the following: summary, customer, item, remarks, transaction details, memo tag, segment, deal name, person in charge, department name, and management number.

[10] The system further includes an acquisition unit that divides the aforementioned transaction data into two or more word sequences and arbitrarily combines these word sequences to obtain word sequence data. The system according to item 8 or 9, wherein the search unit is capable of performing at least one of the following searches on the word sequence data: OR search, AND search, partial match search, prefix match search, suffix match search, NOT search, and wildcard search.

[11] The execution unit is a system described in any one of items 1 to 10, which divides a single settlement record into multiple corresponding occurrence records, records them, and makes them displayable.

[12] The execution unit is capable of creating at least one of the three financial statements based on the occurrence record after the processing, as described in any one of items 1 to 11.

[13] The execution unit is capable of calculating at least one management indicator of profitability, safety, efficiency, and productivity based on the occurrence record after the processing, according to any one of items 1 to 12.

[14] A system described in any one of items 1 to 13, which is a SaaS (Software as a Service) type system with each component installed on the host side.

[15] Based on cash basis accounting, from the settlement journal entry screen for the specified period, An autonomous change support program for performing a one-button process that essentially changes the screen to the journal entry screen for the period in question, based on accrual accounting, and / or an automated process that changes the screen automatically at a predetermined timing.

[16] When outputting output data in a specified format from the original data, An autonomous change support program for executing a one-button process that substantially changes the output data from the original data with a single button, and / or an automatic process that automatically changes at a predetermined timing.

[17] Targeting the content entered in the two or more text items in transaction data where at least the occurrence date, settlement date, and amount are known, and further including two or more text items, perform a cross-cutting narrowing search, and An occurrence record, which is a record based on the occurrence date, and A settlement record, which is a record based on the settlement date, and An autonomous change support system that changes to at least one of the above record screens after the narrowing search.

[18] In transaction data where at least the occurrence date, settlement date, and amount are known, Regarding the record based on the occurrence date as the occurrence record, When regarding the record based on the settlement date as the settlement record, A step of displaying the settlement record screen in a predetermined current period; A step of making it possible to display the occurrence record screen in the current period at a predetermined timing, an autonomous display support method.

Effect of the Invention

[0010] According to the present invention, it is possible to provide an autonomous change support system, its program, and an autonomous display support method that support autonomous output and reduce the burden on the person in charge while the output format from the original data is strictly defined.

Brief Explanation of Drawings

[0011] [Figure 1] A diagram showing the outline of the autonomous change support system according to Embodiment 1. [Figure 2] A diagram for explaining the flexibility of the search according to Embodiment 1. [Figure 3] A further diagram for explaining the flexibility of the search according to Embodiment 1. [Figure 4]A diagram showing an example of a payment record screen and an occurrence display screen according to Embodiment 1. [Figure 5] A diagram showing an example of the division of the breakdown lines according to Embodiment 1. [Modes for carrying out the invention]

[0012] Hereinafter, an aspect of the present invention will be described with reference to the drawings. The following description is illustrative for illustrating an aspect of the present invention, and has been appropriately omitted or simplified for further clarity. The same applies to the drawings. In this specification, unless otherwise specified, each component may be singular or plural, and identical components are denoted by the same reference numeral. In this specification, the term "process" is not limited to independent processes, and is included in the term "process" even if it cannot be clearly distinguished from other processes, as long as the function of that process is achieved.

[0013] One aspect of the present invention is applicable to fields where source data exists but strict rules are established for the output format, and the process of conforming to those rules depends on the individual's discretion; the accounting field is one example of such a field. The following describes an example of applying one aspect of the present invention to the accounting field.

[0014] [Embodiment 1] <Autonomous Change Support System> ≪Overview≫ The autonomous change support system according to this embodiment (hereinafter sometimes simply referred to as "this system"; the same applies hereinafter, including other embodiments, etc.) In transaction data where the occurrence date, settlement date, and amount are known, The record based on the date of occurrence shall be the occurrence record. When the record based on the settlement date is considered a settlement record, A display unit that displays the above payment record screen for the specified period, The system includes an execution unit that enables a one-button process to effectively switch from the settlement record screen to the accrual record screen during the aforementioned period, and / or an automatic process to switch at a predetermined timing. This allows for the autonomous output of source data (in this case, transaction data) where the output format is strictly defined (in this case, a format based on the accrual basis), and reduces the burden on the person in charge.

[0015] Figure 1 shows an overview of this system. In the figure, the overview of this system is represented using functional blocks. This system 101 is configured as a SaaS type system with each part that provides, for example, an accounting processing service (autonomous change support function) on the host side, and is connected to the user terminal 1 via a network 2 such as the internet so that they can communicate with each other.

[0016] User terminal 1 is an information processing device on the user's side, and can be any hardware resource with browser functionality, such as a PC (personal computer), smartphone, or tablet. Users can receive various services from this system 101 through user terminal 1.

[0017] This system 101 is composed of, for example, a database 11 and a host computer 12 (hereinafter sometimes referred to as "server"). This system 101 can also be connected to an external computer system (not shown), in which case transaction data can be imported from the external computer system via network 2. Examples of external computer systems include, but are not limited to, information processing systems operated by businesses that conduct various economic transactions, such as financial institutions, electronic money service providers, credit card companies, and vendors.

[0018] Database 11 is configured using, for example, ROM (Read Only Memory) and RAM (Random Access Memory), and stores journal entry templates and transaction data. This type of data stored in database 11 is read from server 12 and used to implement various functions in system 101.

[0019] Server 12 is configured using at least one terminal equipped with a CPU (Central Processing Unit), and programs that realize each service function are stored in a predetermined information storage medium within Server 12. Server 12 also functions as the control unit of System 101, and by executing pre-prepared programs, it is possible to control the entire System 101.

[0020] Furthermore, server 12 can perform automatic journal entries based on transaction data manually entered by users; transaction data captured as images by user operations (for example, images of receipts, invoices, and usage statements captured by cameras or scanners); and transaction data imported from the external computer system via network 2. For automatic journal entries, known methods may be used, such as methods that refer to past journal entry information and predict journal entries.

[0021] Furthermore, the server 12 includes, for example, a storage unit 21, an acquisition unit 22, a display unit 23, a search unit 24, and an execution unit 25. Each unit may be configured as a single terminal, or it may be configured across multiple terminals. This type of terminal can also be realized using various hardware resources. However, the server configuration is not limited to this example, and at least a part of each unit may be configured in a cloud environment connected via network 2.

[0022] In this specification, "transaction data" means data relating to a transaction, including at least the date of occurrence, the settlement date, and the transaction amount. Transaction data may be information relating to a journal entry, or it may be the journal entry itself. In addition to the date and amount, transaction data may include further information relating to the transaction, for example, content entered in at least one of the following text fields: description, trading partner, item, remarks, transaction details, memo tag, segment, project name, person in charge, department name, and management number. Here, it is preferable that the transaction data includes two or more text fields. This makes it easier to benefit from the flexible search function in this system.

[0023] Furthermore, in this specification, “acquisition record” refers to a record based on the date of occurrence in transaction data, which includes at least the date of occurrence and the amount. An acquisition record is information related to the journal entry made at the time the transaction occurs, and may also be the journal entry itself. Acquisition records are recorded using accounts such as accounts receivable and prepaid expenses (both of which have the characteristics of receivables), and accounts payable and unearned revenue (both of which have the characteristics of liabilities).

[0024] Furthermore, in this specification, “settlement record” refers to a record in transaction data based on the settlement date, which includes at least the settlement date and the amount. A settlement record is information related to the settlement journal entry made when a deposit or payment is completed, and may also be the settlement journal entry itself. Settlement records, for example, clear accounts receivable and accounts payable recorded in the accrual journal entry.

[0025] In this type of transaction data, the settlement date may be later than the transaction date, or conversely, the settlement date may be earlier than the transaction date. In any case, accurate period profit and loss can only be determined by the accrual basis of accounting, which recognizes revenue and expenses at the time the transaction occurs, i.e., on the transaction date.

[0026] ≪Storage section≫ The memory unit 21 is configured using, for example, ROM or RAM, and stores various programs executed by each part of the system 101. The memory unit 11 is also used as working memory during the execution of various processes by the system 101.

[0027] The database 11 may also serve as at least a part of the storage unit 21, or conversely, the storage unit 21 may also serve as at least a part of the database 11. Depending on the function, the database 11 or the storage unit 21 can be omitted. Here, as one embodiment, a configuration in which the server 12 side also has a storage unit 21 in addition to the database 11 will be described, but even in such a configuration, it is not limited to which one stores what.

[0028] ≪Acquisition Department≫ The acquisition unit 22 divides a single transaction data into two or more word sequences and arbitrarily combines these word sequences to obtain word sequence data. This type of transaction data is generally treated as a single exact match data, where the date, amount, and arbitrary text content are combined. In this respect, the acquisition unit 22 divides a single transaction data into two or more word sequences and, if necessary, further combines these word sequences to obtain word sequence data that can be used for various fuzzy searches, making it easy to utilize.

[0029] In one embodiment, the acquisition unit 22 acquires word sequence data from the viewpoint of making it easier to narrow down and search the text content. In another embodiment, the acquisition unit 22 acquires word sequence data from the viewpoint of making it easier to link data with other systems.

[0030] For splitting transaction data, known methods for splitting numerical or textual data are used. For example, the acquisition unit 22 can divide a single transaction data into meaningful minimum units, arbitrarily combine them further, and then acquire word sequence data (morphological analysis). For example, the acquisition unit 22 can divide a single transaction data into n consecutive characters, arbitrarily combine them, and then acquire word sequence data (n-gram method).

[0031] ≪Display section≫ The display unit 23 displays a settlement record screen for a predetermined period. This period is at least one of a day, a week, a month, and a year. The display unit 23 displays the settlement record screen on the browser screen of the user terminal 1, and the user can check the movement of cash and / or deposits on a daily, weekly, monthly, and yearly basis.

[0032] On the settlement record screen, for example, a specified settlement record for the current period is displayed, and if there are multiple settlement records, they are displayed in a list. If the transaction data associated with the settlement record contains text content, the display unit 23 may display this text together with the settlement record.

[0033] ≪Exploration Department≫ The search unit 24 targets word sequence data in transaction data, settlement records, and / or occurrence records, and performs a refined search. Once the relevant records are extracted through the refinement, the display unit 23 can display the screen containing those records on the user terminal 1. Because it targets word sequence data rather than exact match data, various types of fuzzy searches are possible, providing high flexibility.

[0034] In refined searches, for example, when targeting text content, at least one of the following searches is possible: OR search, AND search, partial match search, prefix match search, suffix match search, NOT search, and wildcard search. Wildcard searches, in particular, refer to searches performed by substituting any character, and even if there is ambiguity regarding various symbols (slashes, interpuncts, hyphens, etc.) and spaces, it is easy to extract matching records, making the search highly flexible.

[0035] Furthermore, in refined searches, you can use at least one of the following search methods: greater than or equal to a date, less than or equal to a date, and range search. A greater than or equal to a date search narrows the results to values ​​greater than or equal to the input number or date, while a less than or equal to a date search narrows the results to values ​​less than or equal to the input number or date. In both cases, the search offers a very high degree of flexibility. You can also search for information such as the expected payment timing, for example, "within how many days the payment is expected to be received."

[0036] Figure 2 illustrates the search flexibility in this system. The figure shows an example of the interface displayed on the user's terminal.

[0037] As illustrated, for example, various search targets can be selected, and it is also possible to select only account titles. Furthermore, for "Short-term borrowings" Sd and "Long-term borrowings" Ld, search methods such as "applies to either category," "applies to either category," "does not apply to either category," "name matches," "name does not match," "contains the name," "does not contain the name," "starts with the name," "does not start with the name," "ends with the name," and "does not end with the name" can be selected from the list Mn.

[0038] Of course, "Short-term borrowings" (Sd) and "Long-term borrowings" (Ld) can be easily deleted by clicking the corresponding "×" mark. This, along with the visually clear search menu content and search steps and processes, makes it truly groundbreaking in the field of accounting.

[0039] Regarding refined searches, the system 101 can be pre-configured with candidate name rules (first rules). These rules define a group of candidate names that can be used as input, and users can freely add or delete candidate names from this group. The candidate name rules can be stored, for example, in the storage unit 21, but they may also be stored in the database 11.

[0040] Figure 3 is a further diagram illustrating the search flexibility in this system. The figure shows one aspect of refined search within this system.

[0041] In one embodiment, let's assume that a candidate name rule is stored that connects a group of candidate names consisting of the customer names "Tsubasa Construction", "Tsubasa Construction", "TSUBASA Construction", "Tsubasa Construction Co., Ltd.", "(Co., Ltd.) Tsubasa Construction", "(Co., Ltd.) Tsubasa Construction" ("(Co., Ltd.)" is an environment-dependent character), and "Tsubasa Construction Co., Ltd." using an OR condition. As shown in the figure, in this case, for example, if the text "Tsuba" is entered into text box 25a using a prefix match search, a provisional display 25b of the above candidate name group is generated, which includes "Tsubasa Construction" that matches at least one of the candidate names (some details are omitted in the figure). The generation of the provisional display 25b allows the user to confirm at this stage that the relevant records that match their purpose are listed. As a result of executing this search, a group of the above candidate names that include "Tsubasa Construction" is listed.

[0042] In this system, where transaction data includes two or more text fields, the search unit 24 can perform a cross-sectional refined search targeting the text content entered in two or more text fields. While dates and amounts are defined separately, the input location (which text field to input into) and input content (what kind of text to input) for text fields are loosely defined. In this respect, the search unit 24, using the example in Figure 3, can extract "Tsubasa Construction," etc., cross-sectionally, regardless of whether it is described in the summary or in the remarks.

[0043] ≪Executive Team≫ The execution unit 25 is capable of performing a one-button change process that essentially changes from the settlement record screen to the occurrence record screen with a single button click during the period, and / or an automatic process that changes automatically at a predetermined timing.

[0044] Figure 4 shows an example of a payment record screen and an occurrence display screen according to this embodiment. In the figure, the payment record screen and the occurrence display screen are shown together.

[0045] First, as a premise, for example, under assumption (1) (symbol H1 in the diagram), let's assume that in a credit sales transaction, goods worth 900,000 yen were shipped on May 1st (acquisition record), and the receipt of 900,000 yen was confirmed on June 1st (settlement record). In this case, The journal entry for this transaction is as follows: May 1st: Debit Accounts Receivable 900,000 yen / Credit Sales 900,000 yen The settlement journal entry for June 1st is: Debit: Bank Deposit 900,000 yen / Credit: Accounts Receivable 900,000 yen Therefore, the occurrence date will be one month earlier.

[0046] On the other hand, under assumption (2) (symbol H2 in the diagram), in a prepayment transaction, the receipt of a prepayment of 1 million yen was confirmed on May 1st (settlement record), and goods worth 1 million yen were shipped on May 2nd (accrual record). In this case, The settlement journal entry for May 1st is: Debit: Deposit 1 million yen / Credit: Unearned revenue 1 million yen The journal entry for this transaction is as follows: May 2nd: Debit: Unearned Revenue 1,000,000 yen / Credit: Sales 1,000,000 yen Therefore, the date of occurrence will be delayed by one day.

[0047] Furthermore, under assumption (3) (indicated as H3 in the diagram), in a prepayment transaction, 1 million yen in expenses is prepaid on May 1st (settlement record), and 1 million yen in rent expenses is incurred on June 1st (incurrence record). In this case, The settlement journal entry for May 1st is: Debit: Prepaid expenses 1 million yen / Credit: Bank deposit 1 million yen The journal entry for this expense is as follows: June 1st: Debit: Rent 1 million yen / Credit: Prepaid expenses 1 million yen Therefore, the occurrence date will be delayed by one month.

[0048] In the assumptions illustrated above, for example, when determining the period profit and loss for May, the transaction records (for May) related to assumptions (1) and (2) are included, but the transaction records (for June) related to assumption (3), where the transaction date is the following month even though the expenditure occurred in the current month, are not included. In this regard, according to the execution unit 25, the settlement record screen M1, which displays records related to assumptions (2) and (3), is changed to the transaction record screen M2, which displays records related to assumptions (1) and (2).

[0049] In detail, the above processing in the execution unit 25 omits, for example, settlement records (relevant records) that include a settlement date but do not include an occurrence date within the current period from the occurrence record screen M2 for the current period. In the example given above, in order to grasp the period profit and loss for May, the record H3 related to assumption (3) that was included in the settlement record screen M1 is omitted from the occurrence record screen M2.

[0050] Furthermore, in the above processing in the execution unit 25, for settlement records (relevant records) that include both the settlement date and the occurrence date within the current period, the settlement date is changed to the occurrence date. In the assumption illustrated above, in order to grasp the period profit and loss for May, the settlement record H2: May 1st dated in assumption (2) included in the settlement record screen M1 is changed to occurrence record H2: May 2nd dated in the occurrence record screen M2.

[0051] Furthermore, in the above processing in the execution unit 25, for settlement records (relevant records) that do not include a settlement date but do include an occurrence date, the occurrence record corresponding to that settlement record is added to the occurrence record screen M2 for the current period. In the assumption illustrated above, in order to grasp the period profit and loss for May, the occurrence record H1 of assumption (1), which was not included in the settlement record screen M1, is added to the occurrence record screen M2.

[0052] The execution unit 25 is capable of executing at least one, more preferably at least two, and particularly preferably all of the processes described above (processing to omit settlement records, processing to change dates, and processing to add occurrence records). These processes can be executed with a single button or automatically.

[0053] The execution unit 25 is capable of reversibly displaying the settlement record screen M1 and the occurrence record screen M2, and / or displaying them in parallel. Therefore, the user can display the settlement record screen M1 again from the occurrence record screen M2 based on the same one-button processing or automatic processing, and can also compare the two by displaying the settlement record screen M1 and the occurrence record screen M2 side by side, for example. The settlement record screen M1 and the occurrence record screen M2 do not necessarily need to be separated by boxes, dividers, arrows, etc., in terms of display, and it is also possible for them to be displayed as a single unit as one form of parallel display.

[0054] Furthermore, the execution unit 25 can divide a single settlement record into multiple corresponding transaction records based on similar one-button processing or automatic processing, and then display them. Even with such division of the breakdown lines, it is possible to revert to the display before the division, and reversible or parallel display is possible before and after the division.

[0055] Figure 5 shows an example of the breakdown of line items according to this embodiment. In the figure, an example of borrowings is shown.

[0056] In one embodiment, the execution unit 25 divides and records the breakdown of actual inflows and outflows that are treated as a single amount. For example, although a payment amount as "loan" (75,000 yen in the diagram) is treated as a single amount in the settlement record, it can be divided and recorded as principal (65,000 yen in the diagram) and interest (7,500 yen in the diagram) when changing to an occurrence record display. The notation of the payment amount itself is also retained, making it easy to see at a glance that it has been changed to the amount of principal. The added interest is marked with an "additional" mark 25c, making it easy to understand at a glance that it has been added and recorded in multiple parts by splitting the breakdown line.

[0057] In other words, the interest portion of the loan repayment is calculated using arithmetic operations, subtracted, and the remaining amount is recorded as the principal. This process is not limited to loan repayments; it can also be applied to other payments, such as lease payments (principal and interest). Of course, it is not limited to these.

[0058] In one embodiment, the execution unit 25 can, while changing the display of the transaction record, separate the amount before withholding tax is deducted as "sales (remuneration)" in the settlement record, into the collected amount (for example, a deposit account) and the full amount of sales revenue. In other words, it derives and separates the collected amount from the amount before withholding tax is deducted using arithmetic operations, and then records it together with the full amount of sales revenue. This is not limited to sales (remuneration), but can also be processed similarly for other items, such as credit card payment processing fees (where the payment processing company deducts the fee before receiving the payment). Of course, it is not limited to these.

[0059] Furthermore, in one embodiment, the execution unit 25 can, while changing to displaying the occurrence record, allocate the profits to departments at a predetermined rate based on similar one-button processing or automatic processing, and then display the allocation. This makes it easier to accurately grasp the period profit and loss for each department, and is one of the preferred embodiments.

[0060] (One-button operation) The execution unit 25 can execute the process by essentially clicking an icon on the screen once. For example, when the execution unit 25 receives a press of the "Execute" button 31 from the user, it executes the above process and displays the generated process screen M2.

[0061] The length of the period to be displayed can be selected from options such as one day, one week, one month, and one year. The specific start date and length of the period can also be freely set (for example, a monthly display starting on the 1st, or a weekly display starting on Monday).

[0062] Here, "one button" means that the number of button presses (e.g., mouse clicks) by the user is one, which is essentially necessary to send an instruction signal to the execution unit 25 to execute the above process, and serves as the direct trigger for the execution unit 25 to begin executing the above process. Therefore, it does not include foolproof statements such as "Do you really want to execute?", optional operations on screens that may pop up after pressing the execute button, or optional operations such as moving to another tab.

[0063] (Automated processing) Furthermore, the execution unit 25 can automatically perform the above processing at predetermined timings set by the user. The timing for performing the change processing can be selected from, for example, daily, weekly, monthly, and yearly. The specific timing can also be freely set (for example, every Monday, the 1st of every month, or between certain times each day).

[0064] (Resolved name inconsistency) Here, system 101 is equipped with a name variation resolution rule (second rule) from the start. This rule assigns a single unified name to multiple candidate names, and users can freely add or delete candidate names, change the unified name, etc.

[0065] In other words, when the execution unit 25 performs the above process to display the generation processing screen M2, it can further resolve name inconsistencies. Specifically, it can change multiple candidate names to a unified name according to the name inconsistency resolution rules. This makes it easier to support autonomous name inconsistency resolution.

[0066] Regarding the resolution of name inconsistencies, "multiple candidate names" refers to a group of candidate names that can be used as input candidates, as defined in the candidate name rules mentioned above. For example, the name inconsistency resolution rule defines a single unified name, "Tsubasa Construction," for a group of confusing candidate names such as "Tsubasa Construction." The name inconsistency resolution rule can be stored in the memory unit 21, for example, but it may also be stored in the database 11.

[0067] <Application Examples> (Financial statement preparation system) One application example of this system 101 is a financial statement preparation system. According to this application example, based on the transaction records obtained using the system 101 for the current period, financial statements for that period can be created essentially with a single button or automatically.

[0068] Financial statements include at least one of the three main financial statements, such as the balance sheet, income statement, and cash flow statement. However, they are not limited to these, and various other known statements, such as the statement of changes in shareholders' equity and quarterly reports, can be prepared.

[0069] (System for calculating management indicators) One application example of this system 101 is a system for calculating management indicators (management indicators). According to this application example, various management indicators for the relevant period can be created virtually with a single button or automatically, based on the occurrence records for the period obtained using the system 101 described above.

[0070] Key performance indicators include those relating to at least one of the following: profitability, safety, efficiency, and productivity. For example, Profitability: Operating profit margin, ROE, and ordinary profit margin, Safety: equity ratio, current ratio, and debt ratio, Efficiency: Tangible fixed asset turnover rate, and inventory turnover rate, Productivity: Labor productivity and equipment productivity, These are some examples. The calculation formulas for these are well-known, so they will be omitted. Of course, they are not the only examples.

[0071] A further application example of this system 101 is a system for calculating various numerical targets and performance targets. According to this application example, various numerical targets and performance targets for the relevant period can be created virtually with a single button or automatically, based on the occurrence records for the period obtained using the system 101 described above.

[0072] Examples of numerical targets and performance targets include, Business innovation plan (prefecture): Labor productivity, Manufacturing subsidy: Value added, labor productivity, and equipment utilization rate, Business restructuring subsidy: Value added and labor productivity, These are some examples. The calculation formulas for these are well-known, so they will be omitted. Of course, they are not the only examples.

[0073] <Autonomous display support method> The autonomous display support method according to this embodiment (hereinafter sometimes simply referred to as "this method"; the same applies hereinafter, including other embodiments, etc.) In transaction data where the occurrence date, settlement date, and amount are known, The record based on the date of occurrence shall be the occurrence record. When the record based on the settlement date is considered a settlement record, The process of displaying the above payment record screen for the specified period, The process includes a step of enabling the display of the occurrence record screen during the above period at a predetermined timing.

[0074] An example of the flow of this method will be explained step by step. First, in step S1, the settlement record screen for the specified period is displayed (display step). For details of this step, please refer to the above explanation of this system 101.

[0075] In step S2, the occurrence record screen for the period described above is made available for display at predetermined timings (execution step). Through this step 2, the occurrence record screen may be updated and displayed at predetermined intervals as needed. The details of this step can also be found in the above description of the system 101.

[0076] The above describes one aspect of the present invention. According to this aspect of the present invention, while the output from transaction data is determined in accordance with the accrual principle, it can be executed with a single button or automatically, that is, it can support autonomous output. The technical concept of this invention can be widely applied to fields where raw data exists but strict rules are set for the output format, and the work of conforming to those rules depends on the individual response of the person in charge.

[0077] In this type of field, while efforts are generally made to improve the upstream aspects of the system, ultimately, it relies heavily on the knowledge and practical skills of those in charge of the downstream aspects. As a result, it often fails to reach the point of further improving functionality and convenience, i.e., the midstream improvements. In this context, one aspect of the present invention incorporates precisely these midstream improvements, and its advanced nature is significant.

[0078] The benefits of one aspect of the present invention are significant for both small and medium-sized enterprises and sole proprietors who manage their businesses with limited resources, and for listed companies and large corporations that are required to manage their accounts on an accrual basis. Of course, one aspect of the present invention can be widely applied to various organizations other than corporations, and they can also benefit from one aspect of the present invention.

[0079] Beyond the perspective of statutory accounting, management accounting, used for internal business management and decision-making, requires not only accuracy but also speed. From this perspective, there are concerns that it may place a burden on those in charge, but according to one aspect of the present invention, it is possible to alleviate such a burden on those in charge.

[0080] [Other embodiments] A further embodiment of the present invention is: Based on cash basis accounting, from the settlement journal entry screen for the specified period, This is an autonomous change support program that enables a one-button process to essentially change to the accrual journal entry screen for the above period based on accrual accounting, and / or an automated process to automatically change at a predetermined timing.

[0081] In this embodiment, the storage unit 12A on the server 12A side stores one or more programs that include instructions capable of executing the autonomous change support function related to this system, data temporarily stored during the processing therefor, data used in the processing, data obtained as a result of the processing, etc. Such a program corresponds to a further embodiment of the present invention.

[0082] For example, the execution unit 25 of this system may include at least one processor (CPU, etc.) that executes processing in accordance with program instructions stored in the storage unit 12A. The system operates as a computer when the processor executes the program instructions stored in the storage unit 12A.

[0083] A further embodiment of the present invention is: When outputting output data in a specified format from the original data, This is an autonomous change support program that enables a one-button process to essentially change the source data to the output data, and / or an automated process to change it automatically at a predetermined timing. Such a configuration is not limited to the field of accounting, for example, the field of journal entries.

[0084] Various details relating to this system can be found by referring to the above description of Embodiment 1. That is, this embodiment is a program that includes commands to cause an information processing terminal to perform autonomous change support, and the processing that the terminal performs in accordance with the above commands can be found by referring to the processing described in Embodiment 1.

[0085] Furthermore, another embodiment of the present invention is: For transaction data where at least the occurrence date, settlement date, and amount are known, and which also includes two or more text fields, a cross-sectional refined search is performed targeting the content entered in the two or more text fields, and The incident record is a record based on the date of the incident, The settlement record is a record based on the settlement date, This is an autonomous change support system that changes at least one of the screens to the record screen after the above-mentioned refined search.

[0086] In this embodiment, as in Embodiment 1, a single transaction data can be divided into two or more word sequences, and these word sequences can be arbitrarily combined to obtain word sequence data. This makes it easier to increase the flexibility of searches and, consequently, to integrate with other systems. One example of integration with other systems is when applying ERP (Enterprise Resource Planning). When accounting-specific data is to be centrally managed together with data from other fields, the fact that it can be utilized as predetermined word sequence data makes such management easier.

[0087] One aspect of the present invention is not limited to the above-described embodiment, and can be implemented with various modifications within the scope of the gist of the invention. Naturally, one embodiment can be combined with other embodiments. For example, at least one of the components described in the above embodiment—the storage unit, the acquisition unit, and the search unit—can be omitted depending on the overall configuration of the system.

[0088] Furthermore, while Embodiment 1 described an example of a SaaS-type system where each component is located on the host side, the system configuration is not limited to this. For example, it may consist of a single standalone PC, or it may consist of a workstation (WS) composed of multiple PCs. Of course, at least a part of it may be cloud-based. [Industrial applicability]

[0089] One aspect of the present invention, an autonomous change support system, its program, and an autonomous display support method, is applicable to fields where original data exists but strict rules are defined for the output format, and the work of conforming to those rules depends on the individual handling of the person in charge. One field suitable for one aspect of the present invention is the accounting field, but it is not limited to this and extends to a wide range of other fields. [Explanation of Symbols]

[0090] 101: Autonomous Change Support System 1: User terminal 2: Network 11: Database 12: Server 21: Storage section 22: Acquisition part 23:Display section 24: Search Department 25: Execution Department 25a: Text box 25b: Temporary display 25c: Mark M1: Payment Record Screen M2: Occurrence Record Screen

Claims

1. In transaction data where the occurrence date, settlement date, and amount are known, The record based on the date of occurrence shall be the occurrence record. When the record based on the settlement date is considered a settlement record, A database that stores at least the date of occurrence and the amount as the occurrence record, and at least the date of settlement and the amount as the settlement record, A display unit that displays the payment record screen for a specified period, An execution unit that, based on the occurrence date included in the said period, reads the occurrence record corresponding to the occurrence date and generates an occurrence record screen, thereby enabling a one-button process that essentially changes from the settlement record screen to the occurrence record screen in the said period with a single button, and / or an automatic process that changes automatically at a predetermined timing, An autonomous change support system equipped with the following features.

2. The system according to claim 1, wherein the execution unit enables the one-button process to be executed by substantially clicking an icon on the screen once.

3. The system according to claim 1, wherein the execution unit is capable of executing the automatic processing at at least one of the following timings: daily, weekly, monthly, and yearly.

4. The system according to claim 1, wherein the execution unit can change the timing of displaying the occurrence record screen for the automatic processing.

5. The system according to claim 1, wherein the said period is at least one of a day, a week, a month, and a year.

6. The execution unit is, For settlement records that include the settlement date but do not include the occurrence date within the aforementioned period, they will be omitted from the occurrence record screen for the aforementioned period: For settlement records in which the aforementioned period includes the settlement date and also includes the occurrence date, change the settlement date to the occurrence date: and For settlement records that do not include the settlement date within the aforementioned period but do include the occurrence date, add the occurrence record corresponding to the settlement record to the occurrence record screen for the aforementioned period: The system according to claim 1, which performs at least one of the above processes.

7. The execution unit is, Based on the occurrence date included in the aforementioned period, read the occurrence record corresponding to the occurrence date and generate the occurrence record screen, and / or Based on the settlement date included in the aforementioned period, the settlement record corresponding to the settlement date is read and the settlement record screen is generated. The system according to claim 1, wherein the settlement record screen and the occurrence record screen can be displayed in a reversible manner and / or in parallel.

8. The transaction data includes two or more text items stored in the database, The system according to claim 1, further comprising a search unit that performs a cross-sectional refinement search targeting the content entered in the two or more text fields.

9. The system according to claim 8, wherein the text item includes at least one of the following: summary, customer, item, remarks, transaction details, memo tag, segment, project name, person in charge, department name, and management number.

10. The system further includes an acquisition unit that divides the aforementioned transaction data into two or more word sequences and arbitrarily combines these word sequences to obtain word sequence data. The system according to claim 8, wherein the search unit is capable of performing at least one of OR search, AND search, partial match search, prefix match search, suffix match search, NOT search, and wildcard search on the word sequence data.

11. The system according to claim 1, wherein the execution unit divides a single settlement record into a plurality of corresponding occurrence records, accounts for them, and displays them.

12. The system according to claim 1, wherein the execution unit is capable of creating at least one of the three financial statements based on the occurrence record after the processing.

13. The system according to claim 1, wherein the execution unit is capable of calculating at least one management indicator of profitability, safety, efficiency, and productivity based on the occurrence record after the processing.

14. The system according to any one of claims 1 to 13, which is a SaaS (Software as a Service) type with each component provided on the host side.

15. A program for causing a computer that stores the date and amount of an occurrence journal entry and the date and amount of a settlement journal entry to perform a predetermined step, Based on cash basis accounting, from the settlement journal entry screen for the specified period, An autonomous change support program that causes a computer to perform steps to execute a one-button process that essentially changes to an accrual journal entry screen for the period based on the accrual date included in the aforementioned period, by reading the accrual record corresponding to the accrual date and generating an accrual record screen, and / or an automatic process that changes it automatically at a predetermined timing.

16. A cross-sectional refined search is performed on transaction data where at least the occurrence date, settlement date, and amount are known, and which also includes two or more text fields, targeting the content entered in those two or more text fields, and The incident record is a record based on the date of the incident, The settlement record is a record based on the settlement date, A system that changes at least one of the following to the record screen after the refined search, The following are stored as the occurrence record: at least the occurrence date, the content entered in the text field, and the amount; and at least the settlement date, the content entered in the text field, and the amount as the settlement record. An autonomous change support system that generates the record screen by reading the occurrence record and / or settlement record based on the content entered in the text field that is filtered and searched.

17. In transaction data where the occurrence date, settlement date, and amount are known, The record based on the date of occurrence shall be the occurrence record. When the record based on the settlement date is considered a settlement record, A step of storing at least the date of occurrence and the amount as the occurrence record, and at least the date of settlement and the amount as the settlement record, The process of displaying the payment record screen for the specified period, An autonomous display support method comprising the step of generating an occurrence record screen by reading the occurrence record corresponding to the occurrence date based on the occurrence date included in the said period, thereby enabling the occurrence record screen for the said period to be displayed at a predetermined timing.

Images