JP5669164B1 - Information processing apparatus, program, information processing system - Google Patents

Abstract

An information processing device according to one embodiment of the present invention can access a storage device. This information processing device is transaction information related to a transaction that is either depositing into or withdrawing from an account according to a user instruction, and includes a transaction date, a transaction amount, a description of the transaction, , Acquisition means (S100) for acquiring transaction information, storage means (S112) for storing the transaction information acquired by the acquisition means in the storage device, and a transaction stored in the storage device in response to a user instruction Of the information, with reference to transaction information including the transaction date included in the future period specified by the user, for each scheduled transaction to be performed in the future period, the transaction date, deposit amount or withdrawal amount, transaction And a first output means (S132) for outputting fund trial calculation information including the account balance after the transaction is completed. [Selection] Figure 14

Description

  The present invention relates to an information processing technique for outputting information related to funds that will be required in the future.

  In general, a company manager makes a business plan in consideration of a balance on an arbitrary date in the future (hereinafter referred to as “attention date”). At this time, it is important to consider not only the balance on the attention date, but also the history of transactions performed in the past from the attention date (that is, the factor of the balance on the attention date).

As an example, an example in which a transaction to purchase goods (hereinafter referred to as “purchase transaction”) is performed on September 9, and a transaction for repayment of borrowings (hereinafter referred to as “repayment transaction”) is performed on September 10. Here, it is assumed that the balance after the purchase transaction is smaller than the withdrawal amount (that is, the repayment amount) of the repayment transaction (that is, if the purchase transaction is performed, the repayment transaction cannot be performed).
In general, repayment transactions are more important than purchase transactions. Accordingly, if the balance at the time of the repayment transaction is less than the repayment amount, the business manager may increase the balance (that is, the balance carried forward on September 10, which is the attention date) (for example, a purchase transaction). Plan to cancel or postpone it). For that purpose, it is necessary to consider the contents of the transaction and the balance after transaction for each of the purchase transaction and the repayment transaction.

  2. Description of the Related Art Conventionally, some software that executes accounting processing creates a balance trial calculation table by referring to information related to a transaction input by a user (hereinafter referred to as “transaction information”) (for example, Patent Document 1). . Business owners have made a business plan using a trial balance table created by such software.

JP 2003-167985 A

However, in Patent Document 1, the balance for each date is shown, but the factor of the balance is not shown.
Therefore, even if the business manager knows that the balance on the attention day is small, it cannot grasp which transaction before the attention date should be reviewed in order to increase the balance (that is, the factor of the balance). .
Therefore, a new work is generated to grasp the factor. This work takes a lot of time and effort (that is, the burden on business owners increases).

  The objective of this invention is providing the information processing apparatus, program, and information processing system which provided the user with the information for reducing the burden of the user who makes a business plan.

One aspect of the present invention is an information processing apparatus that can access a storage device,
Transaction information relating to a transaction that is either depositing into or withdrawal from an account and including transaction date, transaction amount, and description of the transaction in accordance with user instructions. Acquisition means for acquiring;
Storage means for storing the transaction information acquired by the acquisition means in the storage device;
In accordance with a user instruction, among the transaction information stored in the storage device, with reference to transaction information including a transaction date included in a future period designated by the user, a scheduled transaction to be performed in the future period A first output means for outputting fund calculation information including a transaction date, a deposit or withdrawal amount, a description of the transaction, and an account balance after the transaction is completed;
Is an information processing apparatus.

The figure which shows an example of a structure of the information processing system 1 of 1st Embodiment. The figure which shows an example of a structure of the client terminal 10 of 1st Embodiment. The figure which shows an example of a structure of the server 30 of 1st Embodiment. The figure which shows an example of the data structure of the user data table of 1st Embodiment. The figure which shows an example of the data structure of the account data table of 1st Embodiment. The figure which shows an example of the data structure of the department data table of 1st Embodiment. The figure which shows an example of the data structure of the account item data table of 1st Embodiment. The figure which shows an example of the data structure of the transaction data table of 1st Embodiment. The figure which shows an example of the main menu screen of 1st Embodiment. The figure which shows an example of the account setting screen of 1st Embodiment. The figure which shows an example of the transaction management screen of 1st Embodiment. The figure which shows an example of the accounting slip screen of 1st Embodiment. The flowchart of the process of registration of the transaction information of 1st Embodiment. The flowchart of the process of the fund trial calculation of 1st Embodiment. The flowchart of the accounting process of 1st Embodiment. The figure which shows an example of the transaction management screen of 2nd Embodiment. The flowchart of the process of registration of the transaction information of 2nd Embodiment. The flowchart of the process of a transaction information change of 3rd Embodiment.

(1) First Embodiment (1-1) Configuration of Information Processing System (FIG. 1)
The configuration of the information processing system of this embodiment will be described. FIG. 1 is a diagram illustrating an example of a configuration of an information processing system 1 according to the first embodiment.

As shown in FIG. 1, the information processing system 1 includes client terminals 10-1 to 10-n (hereinafter referred to as “client terminals 10” when commonly referred to the client terminals 10-1 to 10-n). And a server 30.
The client terminal 10 and the server 30 can communicate with each other via a communication network NW (for example, the Internet).

The client terminal 10 is an example of an information processing apparatus used by a user. The client terminal 10 is, for example, a smartphone, a tablet terminal, a personal computer, or the like.
The server 30 is an example of an information processing apparatus that executes predetermined processing based on a request transmitted from the client terminal 10. The server 30 is, for example, a web server.

(1-2) Configuration of client terminal (FIG. 2)
The configuration of the client terminal 10 will be described. FIG. 2 is a diagram illustrating an example of the configuration of the client terminal 10 according to the first embodiment.

  As illustrated in FIG. 2, the client terminal 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a storage 14, an operation input unit 15, and a display. Unit 16, a communication interface 17, and a bus 18 for transmitting signals between the devices.

The ROM 12 is a storage device that stores programs and data necessary for information processing.
The RAM 13 is a storage device that temporarily stores data necessary for information processing.
The storage 14 includes an OS (Operating System) program, an application (for example, web browser) program for executing information processing, data obtained by executing the information processing (that is, an execution result of information processing), Is a storage device. For example, the storage 14 is a flash memory or a hard disk.

  The CPU 11 is a device that realizes an application function by activating a program stored in the storage 14. The application stores data necessary for information processing in the RAM 13 and executes information processing with reference to the stored data. For example, when referring to the data stored in the storage 14, the application retrieves the data from the storage 14 and stores the retrieved data in the RAM 13.

  The operation input unit 15 is a device that receives a user instruction. The application executes information processing in accordance with a user instruction received by the operation input unit 15.

  The display unit 16 is a device that presents information to the user. The application causes the display unit 16 to display a screen indicating the execution result of the information processing.

  The communication interface 17 is a device that controls communication between the client terminal 10 and the communication network NW. The application transmits and receives programs and data necessary for information processing between the other client terminals 10 and the server 30 via the communication interface 17.

(1-3) Server configuration (FIG. 3)
The configuration of the server of this embodiment will be described. FIG. 3 is a diagram illustrating an example of the configuration of the server 30 according to the first embodiment.

  As illustrated in FIG. 3, the server 30 includes a CPU 31, a ROM 32, a RAM 33, a storage 34, a communication interface 35, and a bus 36 that transmits signals between the units.

The ROM 32 is a storage device that stores programs and data necessary for information processing.
The RAM 33 is a storage device that temporarily stores data necessary for information processing.
The storage 34 is a storage device that stores an OS program, an application program for executing information processing, and data (data table) necessary for information processing. For example, the storage 34 is a flash memory or a hard disk.

  The CPU 31 is a device that realizes an application function by activating a program stored in the storage 34. The application stores data necessary for information processing in the RAM 33, and executes information processing with reference to the stored data. For example, when referring to data stored in the storage 34, the application extracts the data from the storage 34 and stores the extracted data in the RAM 33.

  The communication interface 35 controls communication between the server 30 and the communication network NW. The application transmits and receives programs and data necessary for information processing to and from the client terminal 10 via the communication interface 35.

(1-4) Data table (FIGS. 4 to 8)
The data structure of the data table of this embodiment will be described.

(1-4-1) User data table (FIG. 4)
The data structure of the user data table of this embodiment will be described. FIG. 4 is a diagram illustrating an example of a data structure of the user data table according to the first embodiment.
Each record of the user data table (hereinafter referred to as “user data record”) stores information about the user.

As shown in FIG. 4, the user data table includes a “user ID” field, a “mail address” field, a “password” field, and a “user name” field.
In the “user ID” field, a unique user ID is stored for each user. The user ID is information that identifies a user. The user ID is referred to as a primary key that identifies the user data record.
In the “mail address” field and the “password” field, character strings indicating the mail address and password registered by the user are stored, respectively. The e-mail address and password are information referred to in user authentication.
In the “user name” field, a character string indicating the user name registered by the user is stored.

(1-4-2) Account data table (FIG. 5)
The data structure of the account data table of this embodiment will be described. FIG. 5 is a diagram illustrating an example of a data structure of the account data table according to the first embodiment.
Each record of the account data table (hereinafter referred to as “account data record”) stores information related to the account registered by the user (hereinafter referred to as “registered account”). The account data table is associated with the user ID (that is, the account data table is provided for each user).

As shown in FIG. 5, the account data record includes an “account ID” field, a “financial institution code” field, a “branch code” field, an “account number field”, an “account name” field, and a “balance”. Field.
In the “account ID” field, an account ID unique to each registered account is stored. The account ID is information that identifies a registered account. The account ID is referred to as a primary key that identifies the account data record.
In the “financial institution code” field, the “branch code” field, and the “account number” field, values indicating the financial institution, branch, and account number of the registered account are stored, respectively.
In the “account name” field, a character string indicating the account name of the registered account is stored.
The “balance” field stores a value indicating the balance of the registered account.

(1-4-3) Department data table (FIG. 6)
The data structure of the department data table of this embodiment will be described. FIG. 6 is a diagram illustrating an example of a data structure of the department data table according to the first embodiment.
Each record of the department data table (hereinafter referred to as “department data record”) stores information related to the department registered by the user. The department data table is associated with the user ID (that is, the department data table is provided for each user).

As shown in FIG. 6, the department data record includes a “department code” field and a “department name” field.
In the “department code” field, a department code unique to each department is stored. The department code is information for identifying the department registered by the user. The department code is referred to as a primary key that identifies the department data record.
The “department name” field stores a character string indicating the department name registered by the user.

(1-4-4) Account item data table (Fig. 7)
The data structure of the account item data table of this embodiment will be described. FIG. 7 is a diagram illustrating an example of a data structure of the account item data table according to the first embodiment.
Each record of the account item data table (hereinafter referred to as “account item data record”) stores information related to the account item registered by the user. The account item data table is associated with the user ID (that is, the transaction data table is provided for each user).

As shown in FIG. 7, the account item data record includes an “account item ID” field and an “account item” field.
In the “Account Item ID” field, a unique account item ID is stored for each account item. Account item ID is information which specifies the account item which the user registered. The account item ID is referred to as a primary key for specifying the account item data record.
In the “account item” field, a character string indicating the account item registered by the user is stored.

(1-4-5) Transaction data table (FIG. 8)
The data structure of the transaction data table of this embodiment will be described. FIG. 8 is a diagram illustrating an example of a data structure of a transaction data table according to the first embodiment.
Each record in the transaction data table (hereinafter referred to as “transaction data record”) includes information (hereinafter referred to as “transaction”) related to the transaction registered by the user (transaction performed in the past (hereinafter referred to as “end transaction”) or scheduled transaction). Information ”) is stored. The transaction data table is associated with the user ID (that is, the transaction data table is provided for each user).

As shown in FIG. 8, the transaction data record includes a “transaction ID” field, an “account ID” field, a “transaction type” field, a “transaction date” field, a “transaction amount” field, and a “summary”. A field, a "department code" field, an "account" field, a "status" field, and a "slip number" field.
In the “transaction ID” field, a unique transaction ID is stored for each transaction. The transaction ID is information that identifies a transaction registered by the user. The transaction ID is referred to as a primary key that identifies the transaction data record.
The “account ID” field stores the account ID of the account used for the transaction (any of the account IDs stored in the “account ID” field of the account data table).
In the “transaction type” field, a value indicating the type of transaction (any one of a deposit transaction, a withdrawal transaction, and a transfer transaction) is stored. For example, “0” indicates a deposit transaction, “1” indicates a withdrawal transaction, and “2” indicates a transfer transaction.
In the “transaction date” field, the date on which the transaction is performed is stored.
The “transaction amount” field stores the transaction amount (the amount deposited into the account or the amount withdrawn from the account).
In the “Summary” field, a character string indicating the contents of the transaction is stored.
The “department code” field stores the department code of the department involved in the transaction (one of the department codes stored in the “department code” field of the department data table).
The “status” field stores a value indicating the status of the transaction. For example, “0” indicates that the transaction has ended, but the creation of the accounting slip has not ended, and “1” indicates that the transaction has ended and the creation of the accounting slip has also ended. “2” indicates that the transaction has not ended.
The “slip number” field stores a value indicating the slip number of the created accounting slip. In the “slip number” field of the transaction data record in which “0” or “2” is stored in the “status” field, a value “N / A” indicating that the slip number does not exist is stored.

(1-5) Screens displayed in information processing (FIGS. 9 to 12)
The screen displayed on the display part 16 in the information processing of this embodiment is demonstrated.

(1-5-1) Main menu screen (Fig. 9)
The main menu screen of this embodiment will be described. FIG. 9 is a diagram illustrating an example of a main menu screen according to the first embodiment.

  The main menu screen P100 is a screen displayed when login authentication is successful.

As shown in FIG. 9, the main menu screen P100 includes an “account setting” button B100 and a “transaction management” button B102.
The “account setting” button B100 is an object designated by the user when displaying the account setting screen P110 (FIG. 10).
The “transaction management” button B102 is an object designated when the user displays the transaction management screen P120 (FIG. 11).

(1-5-2) Account setting screen (Fig. 10)
The account setting screen of this embodiment will be described. FIG. 10 is a diagram illustrating an example of an account setting screen according to the first embodiment.

  The account setting screen P110 is a screen displayed when the user designates the “account setting” button B100 in FIG.

As shown in FIG. 10, the account setting screen P110 includes a “financial institution code” form F110, a “branch code” form F112, an “account number” form 124, an “account name” form 126, and a “complete” button. B110.
A user enters a “financial institution code” form F110, a “branch code” form F112, an “account number” form 124, and an “account name” form 126, respectively, into a financial institution code, a branch code, an account number, and an account. When a name is entered and then the “Finish” button B110 is designated, the “Financial Institution Code” form F110, the “Branch Code” form F112, the “Account Number” form 124, and the “Account Name” form 126 are entered. An account data record storing information and a unique account ID is added to the account data table.

(1-5-3) Transaction management screen P120 (FIG. 11)
The transaction management screen of this embodiment will be described. FIG. 11 is a diagram illustrating an example of a transaction management screen according to the first embodiment.

  The transaction management screen P120 is a screen displayed when the user designates the “transaction management” button B102 in FIG.

As shown in FIG. 11, transaction management screen P120 includes an “add” button B120, a “period” form F120, an “account” form F122, and areas Q120 and Q122.
The “add” button B120 is an object designated when the user registers new transaction information.
The “period” form F120 is an object for the user to specify a period related to the transaction information to be displayed. When the user inputs an arbitrary period in the “period” form F120, the transaction information based on the transaction data record including the “transaction date” field in which the value indicating the transaction date within the input period is stored among the transaction data records. (That is, transaction information on transactions performed during the input period) is displayed in area Q122.
The “account” form F122 is an object for the user to specify an account related to the transaction information to be displayed. When the user designates the “account” form F122, “1. collective”, the account name of the registered account “2. accounting”, “3. development”, etc. (“account name” in the account data table (FIG. 5)) A string containing the character string stored in the field). When the user designates “1. collective” from the list, the transaction data record in which the value stored in the “transaction date” field is included in the period entered in the “period” form F120 among the transaction data records Is displayed in area Q122 (ie, transaction information regarding all registered accounts). On the other hand, when the user specifies a character string other than “1. collective” from the list (for example, “2. accounting”), the value stored in the “transaction date” field of the transaction data record is Based on a transaction data record including an “account ID” field that contains an account ID (eg, “A01”) that is included in the period entered in the “period” form F120 and that corresponds to the character string specified by the user Transaction information (that is, transaction information of a transaction using an account designated by the user) is displayed in area Q122.

  In the area Q120, the date on which the transaction management screen P120 is displayed (that is, the current date) is displayed.

In the area Q122, a transaction using the account indicated by the account name input in the “account name” form F122 (that is, the account specified by the user) and in the period input in the “period” form F120 is performed. The transaction information of the transaction that was performed is displayed. The area Q122 includes a “line number” field, a “transaction date” field, a “status” field, a “summary” field, a “payment amount” field, a “withdrawal amount” field, a “balance” field, “Account” column and “Department name” column are included. The “Account” field and the “Department name” field can be omitted (that is, when the user registers transaction information, a character string indicating the account and a character string indicating the department name are input. Even without it, the transaction management screen can be displayed.
In the “line number” column, a unique number is displayed for each transaction information to be displayed. When the user designates the number displayed in the “line number” column, the transaction related to the transaction information displayed in the line is designated.
In the “transaction date” column, the transaction date indicated by the value stored in the “transaction date” field of the transaction data table is displayed.
In the “status” column, the status of the transaction indicated by the value stored in the “status” field of the transaction data table is displayed.
In the “Summary” column, a character string stored in the “Summary” field of the transaction data table (that is, a description of the transaction) is displayed.
In the “deposit amount” column, the value stored in the “transaction amount” field of the transaction data record including the “transaction type” field in which “0” is stored (that is, the transaction amount of the deposit transaction) is displayed.
In the “withdrawal amount” column, the value stored in the “transaction amount” field of the transaction data record including the “transaction type” field in which “1” or “2” is stored (that is, the withdrawal transaction or transfer transaction) Transaction amount) is displayed.
In the “Balance” column, the sum of the balance before the transaction (hereinafter referred to as “Balance before transaction”) and the amount displayed in the “Payment amount” column, or the balance before transaction and the “Payment amount” column The difference from the displayed amount (that is, the balance after the transaction is completed (hereinafter referred to as “the balance after transaction”)) is displayed.
In the “Account” column, a character string (that is, an account) stored in the “Account” field of the transaction data table is displayed.
In the “department name” column, a character string stored in the “department name” field of the transaction data table is displayed.

  When the user designates “Add” button B120, a new line is added to region Q122 (for example, between line number 7 and line number 8). Next, when the user inputs information in each column of the row, a transaction data record storing the input information is added to the transaction data table.

  As described above, the transaction management screen P120 displays the fund calculation information of each registered account and the fund asset information of all registered accounts.

According to the fund calculation information displayed in the area Q122 of the transaction management screen P120, the user can determine the transaction status (whether or not the creation of the accounting slip has been completed), description (contents of the transaction), and the like for each transaction. It is possible to easily grasp the deposit or withdrawal amount and the balance. That is, the user can easily grasp the cash flow for each scheduled transaction and the balance after the scheduled transaction.
Further, according to the fund calculation information displayed in the area Q122 of the transaction management screen P120, the user can calculate the cash flow for each scheduled transaction and the balance after the scheduled transaction for each registered account or for all registered accounts. Can be easily grasped.

(1-5-4) Accounting slip screen P130 (FIG. 12)
The accounting slip screen of this embodiment will be described. FIG. 12 is a diagram illustrating an example of an accounting slip screen according to the first embodiment.

  The accounting slip screen P130 is a screen that is displayed when the user changes the “situation” field in FIG. 11 from “unconfirmed” to “confirmed”, and the “situation” changed to “confirmed”. It is a screen for displaying an accounting slip of a transaction corresponding to a column (hereinafter referred to as “designated transaction”).

  As shown in FIG. 12, accounting slip screen P130 includes areas Q130 to Q136.

  In the area Q130, the date on which the accounting slip screen P130 is displayed (that is, the current date) is displayed.

  In area Q132, a slip number for specifying an accounting slip is displayed.

  In the area Q134, a department name corresponding to the department code stored in the “department code” field of the transaction data table (a character string stored in the “department name” field of the department data table corresponding to the department code) is displayed. Is done. That is, in the area Q134, the department name of the department that has performed the specified transaction is displayed.

  In the area Q136, the accounting items of the designated transaction (counter account item, partner auxiliary item, amount, consumption tax amount, description, partner tax category) are displayed.

  When accounting slip screen P130 is displayed, the value indicating the slip number displayed in area Q132 is stored in the “slip number” field of the transaction data record of the specified transaction, and the transaction ends in the “status” field. In addition, a value “1” indicating that the creation of the accounting slip has also been completed is stored.

(1-6) Information processing flow (FIGS. 13 to 15)
A flow of information processing according to the present embodiment will be described.

(1-6-1) Transaction Information Registration Process Flow (FIG. 13)
The transaction information registration process of the present embodiment will be described. FIG. 13 is a flowchart of transaction information registration processing according to the first embodiment.

First, reception of a transaction information registration request (S100) is executed.
The transaction information registration request includes information indicating the account name of the account used for the transaction, the transaction date, the deposit amount or withdrawal amount, a description, and the name of the department that performed the transaction.
For example, when the user operates the operation input unit 15 and designates the “add” button B120 in FIG. 11, a new line is displayed in the area Q122. Next, when the user inputs information in the “transaction date” field, “summary” field, “deposit amount” field or “withdrawal amount” field, and “department name” field of the new row, the server 30 Accepts a request (request for registration of transaction information) including information input in the field from the web browser.

Next, the account ID is specified (S102).
For example, the server 30 extracts from the account data table (FIG. 5) an account ID corresponding to information indicating the account name included in the transaction information registration request. The extracted account ID is specified as an account ID to be included in the registered transaction information.

Next, the transaction type is specified (S104).
For example, when the transaction information registration request includes information indicating the deposit amount (for example, the user inputs information in the “deposit amount” field of the area Q122 in FIG. 11), the server 30 indicates that the transaction type is a deposit transaction. Specify that there is.
In addition, the transaction information registration request includes information indicating a withdrawal amount, and does not include a description indicating that the transfer is to a transfer account (for example, the user inputs information in the “withdrawal amount” column, and In the “Summary” field, the server 30 specifies that the transaction type is a withdrawal transaction.
Further, when the transaction information registration request includes information indicating a withdrawal amount and a description indicating that the transfer is to an account other than the account used for the transaction, A character string indicating that the transfer is to an account other than the account used for the transaction (hereinafter referred to as “transfer account”) in the “Description” field (for example, the character “transfer”) When the column and the account number of the transfer destination account are input), the server 30 specifies that the transaction type is a transfer transaction.

Next, the department code is specified (S106).
For example, the server 30 extracts a department code corresponding to information indicating the department name included in the transaction information registration request from the department data table (FIG. 6).
The identification of the department code (S106) can be omitted.

Next, the identification of the account item code is executed (S108).
For example, the server 30 extracts from the account item data table (FIG. 7) an account item code corresponding to information indicating an account item included in the transaction information registration request.
The identification of the account item code (S108) can be omitted.

Next, a transaction data record is created (S110).
For example, the server 30 stores a new transaction ID (transaction ID not stored in the transaction data table) in the “transaction ID” field, stores the account ID specified in S102 in the “account ID” field, and S104. Is stored in the “transaction type” field, and the value or character string included in the transaction information registration request received in S100 is stored in the “transaction date” field, the “transaction amount” field, And the “description” field is stored, the department code specified in S106 is stored in the “department code” field, and the value “0” indicating that the creation of the accounting slip for the transaction has not ended is “status”. The value “N / A” is stored in the “slip number” field. Thereby, a new transaction data record is created.

Next, the transaction data table is updated (S112).
For example, the server 30 stores the transaction data record created in S110 in the transaction data table. Thereby, the transaction data table is updated.

  As described above, transaction information including information input by the user is registered.

(1-6-2) Funds calculation process flow (Figure 14)
The fund calculation process of this embodiment will be described. FIG. 14 is a flowchart of fund trial calculation processing according to the first embodiment.

First, reception of a request for fund estimation (S120) is executed.
For example, when the user operates the operation input unit 15 to input information indicating an arbitrary period in the “period” form F120 of FIG. 11 and designates an arbitrary account of the “account” form F122, the server 30 Accepts a request (request for funding calculation) including information input in the “period” form F120 and information input in the “account” form F122 from the web browser.
Hereinafter, an example in which “1. collective” is designated in the “account” form F122 will be described.

Next, the transaction data record is extracted (S122).
For example, the server 30 includes, in the transaction data record included in the transaction data table (FIG. 8), the period input in the “period” form F120 and the account specified in the “account” form F122 (for example, “1. Transaction data records corresponding to “collective” (that is, transaction information of all transactions performed in the period input in the “period” form F120) are extracted.

Next, the balance carried forward calculation (S124) is executed.
For example, the server 30 calculates the sum of the values stored in the “balance” field of all the account data records included in the account data table (FIG. 5). This total value is a balance (hereinafter referred to as “carry forward balance”) at the time of the first day of the period input in the “period” form F120 (the time before the first transaction of the period is performed).

Next, a post-transaction balance is calculated (S126).
For example, for each transaction data record retrieved in S122, the server 30 refers to the value stored in the “transaction amount” field and the balance before the transaction related to the transaction data record is performed, Calculate the post-transaction balance.
More specifically, when a value “0” indicating a deposit transaction is stored in the “transaction type” field of the transaction data record extracted in S122, the server 30 relates to the transaction data record. Balance before the transaction is performed (if the transaction associated with the transaction data record is the first transaction performed in the period entered in the “period” form F120, the balance carried forward in S124, In this case, the value stored in the “transaction amount” field is added to (the balance after the transaction performed immediately before the transaction related to the transaction data record). Thereby, a post-transaction balance is calculated.
On the other hand, when the value “1” indicating a withdrawal transaction or the value “2” indicating a transfer transaction is stored in the “transaction type” field of the transaction data record retrieved in S122, the server 30 Subtracts the value stored in the “transaction amount” field from the balance before the transaction related to the transaction data record is performed. Thereby, a post-transaction balance is calculated.

Next, subtotal calculation (S128) is executed.
For example, for each transaction date, the server 30 calculates the sum of the values stored in the “deposit amount” field of the transaction data record retrieved in S122 and the sum of the values stored in the “withdrawal amount” field. To do. Thereby, a subtotal is calculated.
The subtotal calculation (S128) can be omitted.

Next, a total calculation (S130) is performed.
For example, the server 30 calculates the sum of the subtotal of the deposit amount calculated in S128 and the sum of the subtotal of the withdrawal amount.
The total calculation (S130) can be omitted.

Next, output of fund estimation information (S132) is executed.
For example, the server 30 generates HTML data of the transaction management screen P120 (FIG. 11) with reference to the transaction data record extracted in S122 and the calculation results of S124 to S130, and the generated HTML Send data to a web browser. Next, the web browser refers to the HTML data transmitted from the server 30 and displays the transaction management screen P120 on the display unit 16. As a result, the user knows the cash flow for each scheduled transaction to be performed during the specified period (the date on which the scheduled transaction is performed, the content of the scheduled transaction, the amount handled in the scheduled transaction), and the balance after the scheduled transaction. Can do. Further, the user can know the subtotal of the deposit amount, the subtotal of the withdrawal amount, and the balance for each date included in the designated future period.
As another example, the web browser transmits HTML data transmitted from the server 30 to a printer (not shown). Thereby, the user can obtain a hard copy of the transaction management screen P120.
As another example, the web browser transmits HTML data transmitted from the server 30 to a mail server (not shown). Thereby, the user can share fund estimation information with other users.
As another example, the web browser may convert the HTML data transmitted from the server 30 into data in a general-purpose format (for example, CSV format, text format, etc.) and store the converted data in the storage 14. Good. Accordingly, the user can use the fund calculation information in an application that supports the general-purpose format (for example, software that executes accounting processing, software that executes processing for inventory management of goods, etc.).

(1-6-3) Accounting process flow (Figure 15)
The accounting process of this embodiment will be described. FIG. 15 is a flowchart of the accounting process according to the first embodiment.

First, an accounting process request is received (S140).
The accounting process request includes one of the transaction IDs stored in the “transaction ID” field of the transaction data table.
For example, for a transaction in which “unconfirmed” is displayed in the “situation” column among transactions displayed in the area Q122 of the transaction management screen P120 (FIG. 11) by operating the operation input unit 15. When the display of the “situation” column is changed from “unconfirmed” to “confirmed”, the server 30 requests from the web browser an accounting process including a transaction ID that identifies the transaction whose display of the “situation” column has been changed. Accept.

Next, the transaction data record is extracted (S142).
For example, the server 30 includes a “transaction ID field” in which the transaction ID included in the request for the accounting process accepted in S140 is stored among the transaction data records included in the transaction data table (FIG. 8). (That is, the transaction information of the transaction specified by the user) is taken out.

Next, an accounting slip is output (S144).
For example, the server 30 refers to the transaction data record extracted in S142, generates HTML data of the accounting slip screen P130 (FIG. 12), and transmits the generated HTML data to the web browser. The web browser refers to the HTML data transmitted from the server 30 and displays the accounting slip screen P130 on the display unit 16. Thereby, the user can confirm the contents of the accounting slip.
As another example, the web browser transmits HTML data transmitted from the server 30 to the printer. As a result, the user can obtain a hard copy of the accounting slip screen P130.
As another example, the web browser transmits HTML data transmitted from the server 30 to the mail server. Thereby, the user can share an accounting slip with other users.
As another example, the web browser may convert the HTML data transmitted from the server 30 into data in a general-purpose format (for example, CSV format, text format, etc.) and store the converted data in the storage 14. Good. Thus, the user can use the information on the accounting slip in an application that supports the general-purpose format (for example, software for executing accounting processing, software for executing inventory management processing of merchandise, etc.).

Next, the transaction data record is updated (S146).
For example, the server 30 stores a value “1” indicating that the transaction has been completed and the creation of the accounting slip has been completed in the “status” field of the transaction data record retrieved in S142. Thereby, the transaction data record is updated.

Next, the transaction data table is updated (S148).
For example, the server 30 stores the transaction data record updated in S146 in the transaction data table. Thereby, the transaction data table is updated.

  As described above, the user can easily obtain an accounting slip based on the registered transaction information.

(1-7) Modified Example of First Embodiment A modified example of the first embodiment will be described.

(1-7-1) Modification 1 of the first embodiment
In the above-described embodiment, an example in which transaction information is registered based on information input by the user in the transaction information registration process (FIG. 13) has been described, but the scope of the present invention is not limited thereto. In this embodiment, instead of the user inputting information, data created by arbitrary software (for example, data created by software for calculating salary, data created by software for managing product orders, expense, etc.) Data created by software that manages data, data created by software that performs accounting processing, data managed by an online bank provided by a bank, etc.) may be imported. In this case, the server 30 stores the transaction data record in the transaction data table by converting the format of the data created by the arbitrary software into the format of the transaction data table (FIG. 8).
Thereby, a user's burden at the time of registering transaction information can be reduced, and the convenience of the user who uses these software can be improved.

(1-7-2) Modification 2 of the first embodiment
In the above-described embodiment, the example in which the account item code is specified based on the information input by the user in the transaction information registration process (FIG. 13) has been described, but the scope of the present invention is not limited thereto. In the present embodiment, when the user does not input information indicating the account item, the server 30 refers to dictionary data (not shown) indicating the correspondence between the summary and the account item, and the code indicating the account item May be specified.
Thereby, the user can register transaction information without being conscious of the account item. That is, even a user who does not have knowledge about account items can register transaction information.

(1-8) Summary of First Embodiment According to the present embodiment, the information processing apparatus is accessible to a storage device, and according to a user's instruction, depositing into or withdrawal from an account Acquisition means for acquiring transaction information relating to a transaction that is any one of the transaction information including a transaction date, a transaction amount, and a summary of the transaction; and storing the transaction information acquired by the acquisition means With reference to the transaction information including the transaction date included in the future period designated by the user, among the transaction information stored in the storage device, in accordance with the user's instruction and the storage means stored in the device, First output means for outputting fund calculation information including a transaction date, a deposit or withdrawal amount, a description of the transaction, and an account balance after the transaction is completed for each scheduled transaction to be performed in a future period And information with A processing device is provided.
Accordingly, when the user gives transaction information (information including at least a transaction date, a transaction amount, and a description of the transaction) to the information processing device, the transaction date, the deposit amount or the withdrawal amount for each transaction, and the transaction Information on the estimated amount of money and the post-transaction balance are provided. The user can make a business plan after grasping the cash flow for each transaction and the balance after the transaction through the fund calculation information. For example, when the user thinks that the balance of an arbitrary attention date is insufficient, among transactions performed before the attention date, a transaction having a lower importance than a transaction performed on the attention date (for example, repayment transaction) (for example, repayment transaction) , Purchase transactions) can be canceled or postponed. Therefore, the burden on the user when making a business plan can be reduced.

In addition, according to the present embodiment, the first output means, for each date included in the future period designated by the user, after the sum of the deposit amount, the sum of the withdrawal amount, and all transactions are completed. An information processing apparatus is provided that outputs fund calculation information further including the account balance.
Thus, when the user gives transaction information, fund calculation information including the total of the deposit amount for each date included in the future period specified by the user, the sum of the withdrawal amount, and the balance of the account is provided. . The user can make a business plan after grasping the daily cash flow in the future through the fund calculation information. Therefore, the burden on the user when making a business plan can be further reduced.

Moreover, according to this embodiment, according to a user's instruction, out of the transaction information stored in the storage device, the transaction information of the specified transaction that is a transaction specified by the user is referred to, and There is provided an information processing apparatus further comprising second output means for outputting an accounting slip.
According to the user's instruction, the transaction information stored in the storage device is referred to the transaction information of the specified transaction that is the transaction specified by the user, and is after the transaction date included in the transaction information. And estimating means for estimating a transaction amount of a scheduled transaction to be performed on a future date specified by the user, wherein the storage means is transaction information relating to the scheduled transaction and specified by the user Transaction information including a future date and the transaction amount estimated by the estimation means is stored in the storage device.
Thereby, the accounting slip of the transaction designated by the user is provided. The user can perform a predetermined operation (for example, an accounting operation) using the accounting slip. Therefore, the burden on the user in accounting work can be reduced.

(2) 2nd Embodiment In the above-mentioned 1st Embodiment, the example included in the transaction information newly registered about the transaction amount based on the information which the user input was demonstrated. On the other hand, this embodiment demonstrates the example included in the transaction information newly registered about the transaction amount estimated based on the transaction amount contained in the existing transaction information.
In addition, the description similar to the above-mentioned embodiment is abbreviate | omitted suitably.

(2-1) Transaction management screen displayed in information processing (FIG. 16)
The transaction management screen of this embodiment will be described. FIG. 16 is a diagram illustrating an example of a transaction management screen according to the second embodiment.

As shown in FIG. 16, the transaction management screen P220 includes a “copy” button B220 in addition to the same elements as the transaction management screen P120 (FIG. 11) of the first embodiment.
The “copy” button B220 is an object designated when the user makes a request for estimating the transaction amount of a new transaction.

  When the user designates at least one line whose number is displayed in the “line number” field and then designates the “copy” button B220, the date related to the date displayed in the “transaction date” field of the designated line (For example, the date one month after the date displayed in the “Transaction Date” field) and the description related to the description displayed in the “Description” field of the specified line (for example, displayed in the “Description” field) Information that is shared in whole or in part), the amount estimated based on the amount displayed in the "Payment amount" or "Withdrawal amount" column of the specified line, and the " Transaction information including the same account item and department name as the account item and department name displayed in the “Account” field and “Department name” field is newly registered.

(2-2) Transaction information registration process flow (FIG. 17)
The transaction information registration process of the present embodiment will be described. FIG. 17 is a flowchart of transaction information registration processing according to the second embodiment.

First, reception of transaction information registration request and transaction amount estimation request is executed (S200).
For example, when the user operates the operation input unit 15 and designates an arbitrary line (for example, a line of the line number “6”) in the area Q122 of FIG. 16 and a “copy” button B220, the area Q122 is displayed. A new line is added. In the new line, information related to the information displayed in the line designated by the user (for example, the line with the line number “6”) is displayed. The server 30 receives from the web browser a request including information displayed in the new line (a transaction information registration request) and a transaction amount estimation request. The request for estimating the transaction amount includes a transaction ID of a transaction related to the row designated by the user (hereinafter referred to as “designated transaction”).

Next, the transaction data record is extracted (S202).
As an example, the server 30 stores a transaction data record (that is, transaction information of a specified transaction) including a “transaction ID” field in which the transaction ID included in the transaction amount estimation request received in S200 is stored in the transaction data table. Remove from (FIG. 8).
Furthermore, as another example, the server 30 has a transaction data record (that is, transaction information of a specified transaction) including a “transaction ID” field in which a transaction ID included in the transaction amount estimation request received in S200 is stored. And a transaction data record that includes a “summary” field in which a character string that is at least partially in common with the character string stored in the “description” field of the transaction data record (that is, a transaction related to the specified transaction (hereinafter referred to as a transaction) Transaction information) of “related transactions”) and the transaction data table. In other words, the “related transaction” refers to a transaction in which the content of the transaction (for example, a deposit source, a withdrawal source, a purpose, etc.) is the same (same or similar) as the designated transaction.

Next, transaction amount estimation (S204) is executed.
As an example, when there is one transaction data record retrieved in S202, the server 30 newly registers the same value as the value stored in the “transaction amount” field of the transaction data record retrieved in S202. Estimated as the transaction amount included in the transaction information.
As another example, when there are a plurality of transaction data records retrieved in S202, the server 30 newly registers the average value stored in the “transaction amount” field of the transaction data record retrieved in S202. Estimated as the transaction amount included in the transaction information.
As another example, when there are a plurality of transaction data records extracted in S202, the server 30 stores values included in a predetermined period (for example, the past one year) among the transaction data records extracted in S202. The average value stored in the “transaction amount” field of the transaction data record including the “transaction date” field is estimated as the transaction amount to be included in the newly registered transaction information.

  Next, as in the first embodiment (FIG. 13), account ID identification (S102) to account item code identification (S108) are executed.

Next, a transaction data record is created (S206).
For example, as in the first embodiment (FIG. 13), the server 30 has a “transaction ID” field, an “account ID” field, a “transaction type” field, a “transaction date” field, and a “summary”. A value, a character string, or a code is stored in the field, “department code” field, and “status” field, and a value indicating the transaction amount estimated in S204 is stored in the “transaction amount” field. . Thereby, a new transaction data record is created.

  Next, as in the first embodiment (FIG. 13), the transaction data table is updated (S110).

  As described above, the transaction information including the transaction amount estimated based on the transaction amount of the designated transaction (related transaction information related to the designated transaction) is registered.

(2-3) Summary of Second Embodiment According to this embodiment, a transaction of a designated transaction that is a transaction designated by the user among the transaction information stored in the storage device in accordance with a user instruction. The storage means further comprises an estimation means for estimating a transaction amount of a scheduled transaction to be performed on a future date specified by a user after the transaction date included in the transaction information with reference to the information, Is an information processing apparatus that stores transaction information that is transaction information related to the scheduled transaction and includes a future date designated by a user and a transaction amount estimated by the estimation means in the storage device. Is provided.
Thereby, when a user registers new transaction information, transaction information including the transaction amount estimated based on the transaction amount of the transaction designated by the user is registered without inputting the transaction amount. Therefore, the burden on the user when registering transaction information can be reduced, and a more accurate transaction amount can be included in the transaction information.

(3) Third Embodiment In the above-described embodiment, an example in which new transaction information is registered has been described. On the other hand, in this embodiment, when the user edits the transaction amount included in the existing transaction information, the transaction amount included in the existing transaction information different from the transaction information is automatically edited. explain.
In addition, the description similar to the above-mentioned embodiment is abbreviate | omitted suitably.

(3-1) Transaction information change processing flow (FIG. 18)
Processing for changing transaction information according to the present embodiment will be described. FIG. 18 is a flowchart of transaction information change processing according to the third embodiment.

First, a request for changing transaction information is received (S300).
For example, the user operates the operation input unit 15 to display in the “Money amount” column or “Payment amount” column in an arbitrary row in the area Q122 in FIG. 11 or the “Amount” field in the area Q136 in FIG. When the edited information is edited, the server 30 transmits, from the web browser, the transaction ID included in the transaction information (transaction information of the designated transaction) displayed in the row and the edited information (that is, the edited transaction amount). And a request (a request for changing transaction information).

Next, the transaction data record of the designated transaction and related transaction is extracted (S302).
For example, the server 30 includes a transaction data record (transaction information of a specified transaction) that includes a transaction ID included in the transaction information change request received in S300, and characters recorded in the “summary” field of the transaction data record. A transaction data record (transaction information of related transactions) including a “Summary” field including at least a part of the column is extracted from the transaction data table (FIG. 8). There may be one or more transaction data records of related transactions to be retrieved.

Next, the transaction data record of the designated transaction is updated (S304).
For example, the server 30 uses the value indicating the transaction amount included in the transaction information change request received in S300 (that is, the transaction amount of the specified transaction edited by the user) as the transaction of the specified transaction extracted in S302. Store in the “Transaction amount” field of the data record. Thereby, the transaction data record of the designated transaction is updated.

Next, transaction amount estimation (S306) is executed.
For example, the server 30 stores the value stored in the “transaction amount” field in S304 and the “transaction date” field of the transaction data record of the specified transaction among the transaction data records of the related transaction extracted in S302. The value stored in the "Transaction Amount" field of the transaction data record containing the "Transaction Date Field" that contains a value less than the value, and the average value (that is, the transaction amount of the specified transaction after editing and the specified transaction) The average value of the transaction amount of the related transaction performed before is estimated as the transaction amount of the related transaction performed after the designated transaction.

Next, the transaction data record of the related transaction is updated (S308).
For example, the server 30 sets the value indicating the transaction amount estimated in S306 to be equal to or greater than the value stored in the “transaction date” field of the transaction data record of the specified transaction among the transaction data records of the related transaction extracted in S302. Is stored in the “transaction amount” field of the transaction data record including the “transaction date” field in which the value of is stored (that is, the transaction information of related transactions performed after the specified transaction). Thereby, the transaction data record of the related transaction performed after the designated transaction is updated.

Next, the transaction data table is updated (S310).
For example, the server 30 stores the transaction data record of the designated transaction updated in S304 and the transaction data record of the related transaction updated in S308 in the transaction data table. Thereby, the transaction data table is updated.

  As described above, when the user edits the transaction amount of the designated transaction, the transaction amount of the related transaction performed after the designated transaction is automatically edited.

(3-2) Summary of the Third Embodiment According to the present embodiment, the transaction amount included in the transaction information of the designated transaction is selected from the transaction information stored in the storage device in accordance with a user instruction. And a changing means for changing, wherein the estimating means estimates the transaction amount of the scheduled transaction based on the transaction amount changed by the changing means, and the changing means is further estimated by the estimating means. An information processing apparatus that changes a transaction amount included in transaction information including a transaction date after a transaction date included in the transaction information of the designated transaction, out of the transaction information stored in the storage device, based on a transaction amount Is provided.
Thereby, when the user edits the transaction amount included in the registered transaction information, the transaction amount included in the transaction information of the transaction similar to the transaction related to the transaction information is automatically edited. Therefore, the user can reduce the burden on the user when editing the transaction amounts of a plurality of transactions related to each other.

(4) Other Modifications In the above embodiment, an example in which the information processing of this embodiment is realized by the web browser installed in the client terminal 10 and the server 30 has been described. However, the scope of the present invention is It is not limited to this.
For example, the information processing of the present embodiment may be realized by a dedicated application (an application other than a web browser) installed in the client terminal 10 and a dedicated service provided by the server 30, or only by the dedicated application ( That is, it may be realized (without communication between the dedicated application and the server 30).

  As mentioned above, although embodiment of this invention was described in detail, the scope of the present invention is not limited to said embodiment. The above-described embodiment can be variously improved and changed without departing from the gist of the present invention. Moreover, said embodiment and modification can be combined.

1: Information processing system 10: Client terminal 11: CPU
12: ROM
13: RAM
14: Storage 15: Operation input unit 16: Display unit 17: Communication interface 18: Bus 30: Server 31: CPU
32: ROM
33: RAM
34: Storage 35: Communication interface 36: Bus NW: Communication network

Claims (5)

An information processing apparatus capable of accessing a storage device,
Transaction information relating to a transaction that is either depositing into or withdrawal from an account and including transaction date, transaction amount, and description of the transaction in accordance with user instructions. A plurality of acquisition means;
According to a user's instruction, out of a plurality of transaction information acquired by the acquisition means, an average value of transaction amounts included in a plurality of specified transaction information specified by the user is used as transaction information for each specified transaction. An estimation means for estimating the transaction amount of a scheduled transaction to be performed on a future date specified by the user after the included transaction date;
Storage means for storing the transaction information acquired by the acquisition means and the transaction information of a scheduled transaction including the transaction amount estimated by the estimation means, in the storage device;
In response to a user's instruction, among the plurality of transaction information stored in the storage device, the transaction information including the transaction date included in the future period designated by the user is referred to and performed in the future period. A first output means for outputting fund calculation information including a transaction date, a deposit amount or a withdrawal amount, a description of the transaction, and an account balance after the transaction is completed for each scheduled transaction;
According to a user's instruction, out of a plurality of transaction information stored in the storage device, a change means for changing the transaction amount included in the transaction information of the specified transaction specified by the user,
The estimating means estimates an average value based on the transaction amount changed by the changing means as a transaction amount of the scheduled transaction,
The storage means updates the transaction information of the scheduled transaction among a plurality of transaction information stored in the storage device, using the transaction amount estimated by the estimation means.
Information processing device. The first output means further includes, for each date included in a future period designated by the user, a total deposit amount, a total deposit amount, and an account balance after all transactions are completed. Output funding information,
The information processing apparatus according to claim 1. Second output means for referring to transaction information of a specified transaction that is a transaction specified by the user among the transaction information stored in the storage device in accordance with a user instruction, and outputting an accounting slip for the specified transaction Further equipped with,
The information processing apparatus according to claim 1 or 2 . A computer that can access the storage device.
Transaction information relating to a transaction that is either depositing into or withdrawal from an account and including transaction date, transaction amount, and description of the transaction in accordance with user instructions. A plurality of acquisition means;
According to a user's instruction, out of a plurality of transaction information acquired by the acquisition means, an average value of transaction amounts included in a plurality of specified transaction information specified by the user is used as transaction information for each specified transaction. An estimation means for estimating the transaction amount of a scheduled transaction to be performed on a future date specified by the user after the included transaction date;
Storage means for storing the transaction information acquired by the acquisition means and the transaction information of a scheduled transaction including the transaction amount estimated by the estimation means, in the storage device;
In response to a user's instruction, among the plurality of transaction information stored in the storage device, the transaction information including the transaction date included in the future period designated by the user is referred to and performed in the future period. A first output means for outputting fund calculation information including a transaction date, a deposit amount or a withdrawal amount, a description of the transaction, and an account balance after the transaction is completed for each scheduled transaction;
A program that functions as a changing means that changes a transaction amount included in transaction information of a specified transaction designated by a user among a plurality of transaction information stored in the storage device in accordance with a user instruction. And
The estimating means estimates an average value based on the transaction amount changed by the changing means as a transaction amount of the scheduled transaction,
The storage means updates the transaction information of the scheduled transaction among a plurality of transaction information stored in the storage device, using the transaction amount estimated by the estimation means.
program. An information processing system comprising a storage device, a server accessible to the storage device, and a client terminal accessible to the server and the storage device,
Transaction information relating to a transaction that is either depositing into or withdrawal from an account and including transaction date, transaction amount, and description of the transaction in accordance with user instructions. A plurality of acquisition means;
According to a user's instruction, out of a plurality of transaction information acquired by the acquisition means, an average value of transaction amounts included in a plurality of specified transaction information specified by the user is used as transaction information for each specified transaction. An estimation means for estimating the transaction amount of a scheduled transaction to be performed on a future date specified by the user after the included transaction date;
Storage means for storing the transaction information acquired by the acquisition means and the transaction information of a scheduled transaction including the transaction amount estimated by the estimation means, in the storage device;
In response to a user's instruction, among the plurality of transaction information stored in the storage device, the transaction information including the transaction date included in the future period designated by the user is referred to and performed in the future period. A first output means for outputting fund calculation information including a transaction date, a deposit amount or a withdrawal amount, a description of the transaction, and an account balance after the transaction is completed for each scheduled transaction;
Changing means for changing the transaction amount included in the transaction information of the designated transaction designated by the user among the plurality of transaction information stored in the storage device in accordance with a user instruction , respectively, the client terminal And provided in any of the servers ,
The estimating means estimates an average value based on the transaction amount changed by the changing means as a transaction amount of the scheduled transaction,
The storage means updates the transaction information of the scheduled transaction among a plurality of transaction information stored in the storage device, using the transaction amount estimated by the estimation means.
Information processing system.

Images