JP2016021130A - Information processing device, information processing system, information processing method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing device allowing a user to simultaneously confirm user's transaction history and user's anticipated transaction, an information processing system, an information processing method, and a program.SOLUTION: An information processing device includes: an acquisition part which acquires user's transaction history data from a management device; a transaction reservation part 106 which receives reservation of an anticipated transaction inputted by the user; and a display control part 102 which displays scheduled transaction data containing the data of the anticipated transaction in which reservation is received and the acquired transaction history data, on a passbook screen.SELECTED DRAWING: Figure 2

Description

  The present invention relates to an information processing apparatus, an information processing system, an information processing method, and a program.

  Conventionally, financial institutions such as banks issue paper passbooks and provide them to users when an account is opened.

  Conventionally, there has been proposed a technique that enables a user to check the contents of a transaction scheduled by a user on a display screen or the like. For example, in Patent Document 1, in the ATM (Automated Teller Machine), when the user selects “Account Usage Inquiry”, the ATM obtains future scheduled transfer and withdrawal information recorded in the center. In addition, a technique for printing the acquired information on a statement slip is described. Patent Document 2 discloses a technique in which an automatic transaction apparatus receives transaction data in a customer's account and transaction data for automatic withdrawal within a predetermined period scheduled from a host computer and displays it on a customer operation unit. Is described. Patent Document 3 describes a technique for displaying the budget data and the actual data so that they can be switched in one cell including the budget data and the actual data when the balance schedule table is displayed.

  In addition, a technique for facilitating user operations on the operation screen has been proposed. For example, Patent Document 4 describes a technique for analyzing an operation history of an automated teller machine by a customer and generating an operation menu to be displayed on the automated teller machine according to the analyzed operation history. Yes.

JP-A-6-259644 JP 2000-235612 A JP 2008-129983 A JP 2012-38171 A

  By the way, assuming that the above technology is applied to a scene in which the transaction history of the user and the scheduled transaction of the user are displayed on the display screen, in the above technology, the transaction history of the user or the Only one of the scheduled transactions of the seller. For this reason, when the user wants to confirm both the transaction history of the user and the scheduled transaction of the user, the user needs to switch the display of the screen, which is inconvenient for the user and also confirms the confirmation. It ’s hard.

  Therefore, the present invention has been made in view of the above problems, and the object of the present invention is that the user can confirm the transaction history of the user and the scheduled transaction of the user at the same time. A new and improved information processing apparatus, information processing system, information processing method, and program are provided.

  In order to solve the above-described problem, according to an aspect of the present invention, an acquisition unit that acquires user transaction history data from a management device, and a transaction reservation unit that receives a reservation for a scheduled transaction input by the user; There is provided an information processing apparatus comprising: transaction schedule data including scheduled transaction data for which a reservation has been accepted; and a display control unit that displays the acquired transaction history data on a book screen.

  The transaction schedule data may further include data of transactions not reserved among the scheduled transactions input by the user.

  The transaction reservation unit may accept the reservation of the input scheduled transaction when the input type of the planned transaction is the type of the transaction to be reserved.

  The type of transaction to be reserved may be a type of transaction voluntarily performed by the user.

  The type of transaction to be reserved may include transfer, deposit, or withdrawal.

  The type of transaction that is not a reservation target may include withdrawal or transfer from another bank.

  The display control unit displays an inquiry as to whether or not to reserve the input scheduled transaction on the display screen when the type of the input scheduled transaction is the type of the target transaction. The reservation unit may accept the reservation of the input scheduled transaction when the user inputs the reservation.

  The information processing apparatus may further include a transaction execution requesting unit that requests the management apparatus to execute a scheduled transaction for which a reservation has been accepted.

  The display control unit may display the transaction schedule data on the passbook screen in a different display mode according to whether or not the transaction schedule data is reserved scheduled transaction data.

  In order to solve the above problem, according to another aspect of the present invention, an acquisition unit that acquires transaction history data of a user from a management device, and a transaction that accepts a reservation for a scheduled transaction input by the user There is provided an information processing system comprising: a reservation unit; transaction schedule data including accepted transaction reservation data; and a display control unit that displays the acquired transaction history data on a book screen.

  Moreover, in order to solve the said subject, according to another viewpoint of this invention, The step which acquires the transaction history data of a user from a management apparatus, The step which receives the reservation of the scheduled transaction input by the said user, A transaction schedule data including received transaction reservation data, and a step of displaying the acquired transaction history data on a book screen.

  In order to solve the above problems, according to another aspect of the present invention, a computer, an acquisition unit that acquires transaction history data of a user from a management device, and reservation of a scheduled transaction input by the user A program for functioning as a display control unit for displaying the transaction schedule data including the received transaction reservation data and the acquired transaction history data on the book screen is provided.

  As described above, according to the present invention, the user can simultaneously confirm the transaction history of the user and the scheduled transaction of the user.

It is explanatory drawing which showed the structural example of the information processing system by embodiment of this invention. 2 is a functional block diagram showing a configuration of a mobile terminal 10 according to the embodiment. FIG. It is explanatory drawing which showed the example of a display of the transaction statement screen by the embodiment. It is explanatory drawing which showed the example of a display of the scheduled transaction input screen by the embodiment. It is explanatory drawing which showed the example of a display of the transaction plan data in a transaction statement screen. It is explanatory drawing which showed the example of a display of the transaction statement screen by the embodiment. It is explanatory drawing which showed the example of a display of the scheduled transaction input screen by the embodiment. It is explanatory drawing which showed the example of a display of the transaction plan data in a transaction statement screen. It is the table | surface which showed an example of the execution result of the real transaction in a predetermined period. It is explanatory drawing which showed the example of a display of the transaction details screen after the real transaction execution by the embodiment. It is the sequence diagram which showed the operation example at the time of the input of the scheduled transaction by the same embodiment. It is the flowchart which showed the operation example at the time of the update of the transaction plan data by the embodiment. It is explanatory drawing which showed the hardware constitutions of the mobile terminal 10 by the embodiment.

  Exemplary embodiments of the present invention will be described below in detail with reference to the accompanying drawings. In addition, in this specification and drawing, about the component which has the substantially same function structure, duplication description is abbreviate | omitted by attaching | subjecting the same code | symbol.

Further, the “DETAILED DESCRIPTION OF THE INVENTION” will be described according to the following item order.
1. 1. Basic configuration of information processing system 2. Detailed description of embodiments 2-1. Configuration 2-2. Operation 2-3. Effect 3. Hardware configuration Modified example

<< 1. Basic configuration of information processing system >>
<1-1. Basic configuration>
The present invention can be implemented in various forms as will be described in detail in “2. Detailed Description of Embodiments” as an example. First, a basic configuration of an information processing system according to an embodiment of the present invention will be described with reference to FIG.

  As shown in FIG. 1, the information processing system according to the present embodiment includes a mobile terminal 10, a communication network 12, a WEB / DB server 20, and an IB (Internet Banking) server 22.

[1-1-1. Mobile terminal 10]
The mobile terminal 10 is an example of an information processing apparatus according to the present invention. This mobile terminal 10 is a portable terminal possessed by a user. The mobile terminal 10 may be, for example, a smartphone or a tablet terminal.

  In addition, the mobile terminal 10 can implement a smartphone passbook application. This smartphone passbook application is an application for causing the display to display almost the same content as the content printed on the paper passbook. For example, the mobile terminal 10 displays on the display a transaction details screen listing user transaction details acquired from the IB server 22 by a smartphone passbook application. The transaction statement screen is an example of a bankbook screen in the present invention. The transaction details are an example of transaction history data in the present invention. This transaction statement is detailed data for one transaction in the transaction history of the user.

  In addition, the mobile terminal 10 can accept an input of a future scheduled transaction by the user.

[1-1-2. Communication network 12]
The communication network 12 is a wired or wireless transmission path for information transmitted from a device connected to the communication network 12. For example, the communication network 12 includes a public line network such as a telephone line network, the Internet, a satellite communication network, various LANs including Ethernet (registered trademark), a WAN (Wide Area Network), and the like. Further, the communication network 12 may include a dedicated line network such as an IP-VPN (Internet Protocol-Virtual Private Network).

[1-1-3. WEB / DB server 20]
The WEB / DB server 20 is a device that relays communication between the mobile terminal 10 and the IB server 22. The WEB / DB server 20 is installed mainly for the purpose of enhancing the security of the IB server 22.

  For example, when receiving a transaction details acquisition request from the mobile terminal 10, the WEB / DB server 20 transfers the received acquisition request to the IB server 22. When the transaction details of the user of the mobile terminal 10 are received from the IB server 22, the WEB / DB server 20 transfers the received transaction details to the IB server 22.

[1-1-4. IB server 22]
The IB server 22 is an example of a management device in the present invention. The IB server 22 is a device for managing an Internet banking system of a financial institution. For example, the IB server 22 stores the transaction details of the user in association with the user of the mobile terminal 10. Further, the IB server 22 processes the actual transaction from the account of the user of the mobile terminal 10 based on the execution request for the actual transaction received from the mobile terminal 10, for example.

  The basic configuration of the information processing system according to this embodiment has been described above. The mobile terminal 10 described above can allow the user to simultaneously confirm the transaction history of the user and the scheduled transaction of the user. Hereinafter, such an embodiment of the present invention will be described in detail.

<< 2. Detailed Description of Embodiment >>
<2-1. Configuration>
First, the configuration according to the present embodiment will be described in detail. FIG. 2 is a functional block diagram showing the configuration of the mobile terminal 10 according to the present embodiment. As illustrated in FIG. 2, the mobile terminal 10 includes a control unit 100, a communication unit 120, an operation display unit 122, and a storage unit 124.

[2-1-1. Control unit 100]
The control unit 100 generally controls the operation of the mobile terminal 10 using hardware such as a CPU (Central Processing Unit) 150 and a RAM (Random Access Memory) 154, which will be described later, built in the mobile terminal 10. As shown in FIG. 2, the control unit 100 includes a display control unit 102, a scheduled transaction input unit 104, a transaction reservation unit 106, a transaction execution request unit 108, and a transaction details request unit 110.

[2-1-2. Display control unit 102]
(2-1-2-1. Display example 1)
The display control unit 102 displays various display screens on the operation display unit 122 described later. For example, the display control unit 102 generates a transaction details screen including transaction schedule data received by the scheduled transaction input unit 104 to be described later and transaction details received by the communication unit 120 to be described later, and the generated transaction details The screen is displayed on the operation display unit 122.

  More specifically, the display control unit 102 causes the transaction schedule data to be displayed on the transaction details screen in different display modes depending on whether or not an actual transaction is reserved for the accepted transaction schedule data. For example, the display control unit 102 changes a character string and an image displayed on the transaction details screen in association with the transaction schedule data depending on whether or not an actual transaction is reserved. Or the display control part 102 changes the display area of transaction plan data according to whether the reservation of an actual transaction is made.

-A. Example of displaying transaction schedule data with reservations for actual transactions-
Here, the above function will be described in more detail. First, with reference to FIGS. 3-5, the example of a display of the transaction plan data by which the actual transaction is reserved is demonstrated. For example, the display control unit 102 displays a transaction details screen 30a in which transaction details data 300 received from the IB server 22 is listed as shown in FIG. Display on the unit 122. In this transaction detail screen 30a, for each transaction detail data 300, for example, date 310, transaction content 311, payment amount 312, deposit amount 313, balance 314, and remarks 315 are displayed in association with each other.

  When the scheduled transaction addition button 302 is selected by the user on the transaction details screen 30a, the display control unit 102 causes the operation display unit 122 to display a scheduled transaction input screen 32a as shown in FIG.

  The scheduled transaction input screen 32a is a screen for the user to input a scheduled transaction. As shown in FIG. 4, the scheduled transaction input screen 32a includes a transaction reservation selection field 320a for selecting whether or not to reserve an actual transaction for the input scheduled transaction. When it is desired to make a reservation for an actual transaction, the user selects “Also perform an actual transaction reservation” in the transaction reservation selection field 320a, and when the user does not wish to make an actual transaction reservation, In the transaction reservation selection field 320a, the user selects “Do not make an actual transaction reservation”.

  The planned transaction date input field 320b is an input field for inputting the transaction date of the planned transaction. The transaction content selection field 320c is an input field for selecting the transaction type of the scheduled transaction. When “actual transaction reservation is also performed” is selected in the transaction reservation selection field 320a, the display control unit 102 selects the transaction type in the transaction content selection field 320c so that only the type of transaction to be reserved can be selected. Can also be displayed. Here, the type of transaction to be reserved is, for example, the type of transaction voluntarily performed by the user. More specifically, the type of transaction to be reserved is a type of transaction that allows actual transactions from an Internet banking account, such as a transfer transaction, a deposit transaction, or a withdrawal transaction. The type of transaction that is not a reservation target is, for example, a withdrawal transaction or a transfer transaction from another bank.

  When “transfer” is selected by the user in the transaction content selection field 320c, the display control unit 102, as shown in FIG. 4, displays a plurality of input items corresponding to the transfer transaction, that is, the transfer destination. A financial institution input field 320d, a transfer destination account number input field 320e, a transfer destination account type input field 320f, a transfer amount input field 320g, and the like are displayed on the scheduled transaction input screen 32a.

  When a confirmation button 322 is selected by the user after input for each input item 320 on the scheduled transaction input screen 32a, the display control unit 102 displays the user as shown in the transaction details screen 30b shown in FIG. The transaction schedule data 304 input by the above is added under the transaction details data 300 and the transaction details screen 30 is displayed.

  Further, as illustrated in FIG. 5, the display control unit 102 displays, for example, a character string “plan (transaction reservation)” around the transaction schedule data 304 on the transaction details screen 30 b. According to this display example, the user can understand at a glance that an actual transaction is reserved for the transaction schedule data 304.

  As shown in FIG. 5, the display control unit 102 may display the transaction schedule data 304 in a font different from the transaction detail data 300 such as bold.

-B. Example of displaying transaction schedule data that has not been booked for actual transactions-
Next, with reference to FIGS. 6-8, the example of a display of the transaction plan data in which the reservation of an actual transaction is not made is demonstrated. Here, an example in which the user copies the contents of any of the transaction details data displayed on the transaction details screen 30 and inputs the planned transaction, and inputs that the planned transaction is repeatedly performed. Will be described.

  FIG. 6 is an explanatory view showing the same transaction details screen 30b as in FIG. When transaction detail data 300a (data surrounded by a thick line in FIG. 6) desired to be copied by the user is selected on the transaction statement screen 30b by double tapping, the display control unit 102 displays, for example, FIG. The scheduled transaction input screen 32b as shown in FIG.

  In the scheduled transaction input screen 32b, when the user desires not to make a reservation for an actual transaction, as shown in FIG. 7, select "Do not make an actual transaction reservation" in the transaction reservation selection field 320a. .

  In addition, on the planned transaction input screen 32b, the display control unit 102 displays a plurality of input items 320 corresponding to the transaction details data 300a selected by the user, and each of the plurality of input items 320 includes a transaction. The same contents as the detail data 300a are automatically input. For example, in the example shown in FIG. 7, the display control unit 102 displays a transaction content input field 320d and a withdrawal destination input field 320e, and deducts “withdrawal” in the transaction content input field 320d. “A gas” is automatically entered in the first entry field 320e.

  The scheduled transaction input screen 32b includes a repeated registration selection column 320b and a registration unit input column 320c (unlike the scheduled transaction input screen 32a shown in FIG. 4). The repetitive registration selection field 320b is a selection field for selecting whether or not input transaction schedule data is repeatedly registered. The registration unit input field 320c is an input field for inputting a unit for repeating the contents of the input transaction schedule data such as “once a week” and “once a month”. FIG. 7 shows an example in which the user inputs the transaction schedule data to be input “once a month”.

  When a confirmation button 322 is selected by the user after input for each input item 320 on the scheduled transaction input screen 32b, the display control unit 102 displays the user as in the transaction details screen 30c shown in FIG. The newly entered transaction schedule data 304b to 304d are added further below the already entered transaction schedule data 304a to display the transaction details screen 30.

  Further, as shown in FIG. 8, the display control unit 102 displays, for example, a character string “schedule (detail display only)” around the transaction schedule data 304b to 304d on the transaction detail screen 30c. According to this display example, the user can understand at a glance that an actual transaction is not reserved for the transaction schedule data 304b to 304d.

  Although FIG. 8 shows an example in which the display control unit 102 displays only three transaction schedule data 304 that have been repeatedly input, the present invention is not limited to this example. For example, the display control unit 102 may repeatedly display four or more transaction schedule data 304, such as twelve, or the transaction schedule for the current month in the transaction schedule data 304 (which has been repeatedly input). Only the data 304 may be displayed.

-C. Example of transaction schedule data display after execution of scheduled transaction-
Next, with reference to FIGS. 9-10, the example of a display of the transaction detail screen after the input scheduled transaction is performed is demonstrated.

  FIG. 9 is a table showing the execution results of actual transactions at, for example, Internet banking, ATMs, financial institutions, etc. during a predetermined period such as “March 1, 2014 to March 31, 2014”. In FIG. 9, “5,000 yen transfer” was made from the user's account on “March 4”, and “25,000 yen was withdrawn from the user account on“ March 26 ”. This indicates that “Shi” has been performed.

  FIG. 10 is an explanatory diagram showing a display example (transaction details screen 30d) of the transaction details screen at the time when the actual transaction having the contents shown in FIG. 9 is executed. As shown in FIG. 10, when the execution result of the actual transaction shown in FIG. 9 is received from, for example, the WEB / DB server 20, the display control unit 102 displays transaction schedule data corresponding to the actual transaction, that is, The transaction schedule data 304a and the transaction schedule data 304b on the transaction statement screen 30c shown in FIG. 8 are replaced with the transaction statement data 300a and the transaction statement data 300b, respectively, and displayed.

  The display control unit 102 displays the transaction schedule data as transaction detail data after correcting the transaction schedule data that is not reserved for the actual transaction to the content according to the execution result of the actual transaction. For example, in the transaction schedule data 304b shown in FIG. 8, the payment amount is scheduled to be “20,000 yen”, but as shown in FIG. 9, in the actual transaction, the payment amount is “25,000 yen”. It is. For this reason, the display control unit 102 displays “25,000 yen” as the payment amount 312 of the transaction details data 300 b as shown by the broken line frame 306 in FIG. 10 and the payment amount as the balance 314. , That is, “450,000 yen (= 475,000 yen−25,000 yen)” is displayed.

-D. Modified example
As a modification, the display control unit 102 may display the transaction schedule data in different display areas on the transaction details screen depending on whether or not the actual transaction is reserved for the received transaction schedule data. Is possible. For example, the display control unit 102 may display only the scheduled transaction data for which the actual transaction is reserved, for example, at a position away from the display area of the transaction detail data 300, such as the lower part of the transaction detail screen 30.

  In this modified example, after the transaction corresponding to the transaction schedule data is executed, the display control unit 102 moves the corresponding transaction schedule data to the display area of the transaction details data 300 and displays it as described above. Let

(2-1-2-2. Display example 2)
In addition, the display control unit 102 can additionally display various types of information on the displayed display screen. For example, when the type of the scheduled transaction input by the user is the type of the transaction to be reserved, the display control unit 102 may display an inquiry as to whether or not to reserve the input scheduled transaction. Is possible.

[2-1-3. Scheduled transaction input unit 104]
The scheduled transaction input unit 104 accepts input of transaction schedule data via the operation display unit 122 by the user, for example. For example, when the confirmation button 322 is selected by the user on the scheduled transaction input screen 32 shown in FIG. 4 or 7, the scheduled transaction input unit 104 uses the content input on the scheduled transaction input screen 32 as the scheduled transaction data. Accept.

[2-1-4. Transaction reservation unit 106]
The transaction reservation unit 106 receives a reservation for an actual transaction with respect to the transaction schedule data received by the scheduled transaction input unit 104. For example, the transaction reservation unit 106 is input when the type of the scheduled transaction input by the user is the type of the transaction to be reserved, and the user inputs that the scheduled transaction is reserved. Accept reservations for scheduled transactions.

[2-1-5. Transaction execution request unit 108]
The transaction execution request unit 108 causes the communication unit 120 to transmit a request for execution of the scheduled transaction for which the reservation is accepted by the transaction reservation unit 106 to the WEB / DB server 20. For example, the transaction execution request unit 108 causes the communication unit 120 to transmit a request for execution of a scheduled transaction for which an actual transaction reservation has been accepted, to the WEB / DB server 20 on the scheduled transaction date of the scheduled transaction.

[2-1-6. Transaction details request unit 110]
The transaction detail request unit 110 causes the communication unit 120 to transmit an acquisition request for an unacquired transaction detail to the IB server 22 to the WEB / DB server 20 according to, for example, a user operation on the operation display unit 122.

[2-1-7. Communication unit 120]
The communication unit 120 is an example of an acquisition unit in the present invention. The communication unit 120 transmits / receives information to / from other devices via the communication network 12. For example, the communication unit 120 receives the transaction details of the user from the WEB / DB server 20. Further, the communication unit 120 transmits an execution request for the reserved scheduled transaction to the WEB / DB server 20 according to the control of the transaction execution request unit 108.

[2-1-8. Operation display unit 122]
The operation display unit 122 displays various display screens such as a transaction details screen according to the control of the display control unit 102.

  The operation display unit 122 also accepts various input operations on the mobile terminal 10 by the user. For example, the operation display unit 122 accepts user input for each input item displayed on the scheduled transaction input screen.

[2-1-9. Storage unit 124]
The storage unit 124 stores, for example, various data such as user transaction details received from the WEB / DB server 20, planned transaction data received by the scheduled transaction input unit 104, and various software such as a smartphone passbook application. To do.

<2-2. Operation>
The configuration according to this embodiment has been described above. Next, operations according to the present embodiment will be described in “2-2-1. Operation when inputting scheduled transaction” to “2-2-2. Operation when updating planned transaction data”.

[2-2-1. Operation when entering a scheduled transaction]
FIG. 11 is a sequence diagram showing an operation when inputting a scheduled transaction. As illustrated in FIG. 11, first, the control unit 100 of the mobile terminal 10 activates the smartphone passbook application stored in the storage unit 124 in accordance with, for example, a user operation on the operation display unit 122 (S101). .

  Thereafter, the transaction detail request unit 110 transmits an unacquired transaction detail acquisition request to the WEB / DB server 20 to the communication unit 120 in accordance with, for example, a user operation on the operation display unit 122 (S102).

  Thereafter, the WEB / DB server 20 transfers the transaction details acquisition request received in S102 to the IB server 22 (S103).

  Thereafter, the IB server 22 extracts unprovided transaction details from the transaction details of the user of the mobile terminal 10 in response to the transaction details acquisition request received in S103. Then, the IB server 22 transmits the extracted transaction details to the WEB / DB server 20. Thereafter, the WEB / DB server 20 transfers the transaction details received from the IB server 22 to the mobile terminal 10 (S104).

  Thereafter, the transaction details request unit 110 of the mobile terminal 10 records the transaction details received in S104 in the storage unit 124 (S105).

  Thereafter, the scheduled transaction input unit 104 accepts input of the scheduled transaction data on the scheduled transaction input screen as shown in FIG. 4 or 7 by the user (S106).

  Subsequently, the control unit 100 determines whether or not the scheduled transaction type input in S106 is a transaction type that can be traded by Internet banking (S107). If it is not a transaction type that can be traded by Internet banking (S107: No), the control unit 100 performs an operation of S110 described later.

  On the other hand, in the case of a transaction type that can be traded by Internet banking (S107: Yes), the control unit 100 determines whether or not an actual transaction reservation has been made by the user with respect to the entered transaction schedule data. (S108). When an actual transaction is not reserved (S108: No), the control unit 100 sets a “schedule (detail display only)” flag for the transaction schedule data, and stores the transaction schedule data in the storage unit 124. (S110).

  On the other hand, when an actual transaction is reserved (S108: Yes), the control unit 100 sets a “plan (transaction reservation)” flag for the transaction schedule data, and stores the transaction schedule data in the storage unit It records in 124 (S109).

  In S106, when the user inputs to make a reservation for the actual transaction, the transaction reservation unit 106 accepts the reservation for the actual transaction with respect to the transaction schedule data. Thereafter, the transaction execution request unit 108 causes the WEB / DB server 20 to transmit the execution request for the scheduled transaction for which the reservation is accepted to the communication unit 120 on the scheduled transaction date of the scheduled transaction. Then, the WEB / DB server 20 transfers the received execution request of the scheduled transaction to the IB server 22. Then, the IB server 22 executes the scheduled transaction based on the received scheduled transaction execution request.

[2-2-2. Operation when updating planned transaction data]
FIG. 12 is a flowchart showing an operation at the time of updating the transaction schedule data. The operation shown in FIG. 12 is repeatedly executed by the mobile terminal 10 at predetermined time intervals, for example.

  As shown in FIG. 12, first, the control unit 100 of the mobile terminal 10 extracts one piece of transaction schedule data stored in the storage unit 124 (S121). Subsequently, the control unit 100 determines whether or not a “plan (transaction reservation)” flag is set in the extracted transaction plan data (S122).

  When the “plan (transaction reservation)” flag is not set (S122: No), the control unit 100 performs an operation of S125 described later. On the other hand, when the “schedule (transaction reservation)” flag is set (S122: Yes), the control unit 100 next determines whether or not the transaction corresponding to the transaction schedule data has been executed ( S123). For example, the control unit 100 determines whether or not a corresponding transaction has been executed by confirming whether or not a transaction completion notification corresponding to the transaction schedule data has been received from the WEB / DB server 20.

  When the transaction corresponding to the transaction schedule data is not executed (S123: No), the control unit 100 performs the operation of S125 described later. On the other hand, when the transaction corresponding to the transaction schedule data is executed (S123: Yes), the control unit 100 deletes the “schedule (transaction reservation)” flag set in the transaction schedule data, and Then, the transaction schedule data is replaced with transaction details data and recorded again in the storage unit 124 (S124).

  Subsequently, the control unit 100 determines whether or not the “schedule (detail display only)” flag is set in the transaction schedule data (S125). When the “schedule (detail display only)” flag is not set (S125: No), the control unit 100 performs an operation of S133 described later. On the other hand, when the “schedule (detail display only)” flag is set (S125: Yes), the control unit 100 next passes the scheduled transaction date set in the scheduled transaction data. It is determined whether or not (S126).

  If the current transaction date has not elapsed (S126: No), the control unit 100 performs an operation of S133 described later. On the other hand, when the current transaction date has passed (S126: Yes), the control unit 100, for example, receives all transaction details received from the WEB / DB server 20 on the transaction date and the transaction schedule data. (S127).

  Based on the result of the match, the control unit 100 determines whether there is a transaction specification corresponding to the transaction schedule data among all the transaction details received from the WEB / DB server 20 (S128). . When there is no transaction details corresponding to the transaction schedule data (S128: No), the control unit 100 deletes the transaction schedule data from the storage unit 124 (S129). And the control part 100 performs operation | movement of S133 mentioned later.

  On the other hand, when the transaction details corresponding to the transaction schedule data are present (S128: Yes), the control unit 100 determines, for example, the amount of money between the transaction schedule data and the transaction details corresponding to the transaction schedule data. It is determined whether or not there is a difference in content (S130). When there is no difference in content (S130: No), the control unit 100 performs an operation of S132 described later. On the other hand, when there is a difference in the contents (S130: Yes), the control unit 100 corrects the contents of the transaction schedule data according to the corresponding transaction details (S131).

  Thereafter, the control unit 100 deletes the “schedule (transaction details display only)” flag set in the transaction schedule data corrected in S131, and replaces the transaction schedule data with the transaction details data to store the storage unit 124. (S132).

  Subsequently, the control unit 100 determines whether or not the above confirmation (that is, the processing of S121 to S131) has been completed for all the transaction schedule data stored in the storage unit 124 (S133). When the confirmation of any transaction schedule data is not completed (S133: No), the control unit 100 performs the operation of S121 again. On the other hand, when the confirmation of all the transaction schedule data is completed (S133: Yes), the mobile terminal 10 ends the operation.

<2-3. Effect>
As described above, for example, as described with reference to FIGS. 2, 11, and 12, the mobile terminal 10 according to the present embodiment uses the transaction schedule data input by the user received from the IB server 22. To be displayed under the transaction details screen. For this reason, a user can confirm a user's transaction details and a user's scheduled transaction simultaneously. For example, the user can compare the estimated future account balance with the past or current account balance on the same screen.

  In addition, the mobile terminal 10 determines, for example, “schedule (transaction reservation)” or “schedule (detail display only)” depending on whether or not an actual transaction is reserved for the transaction schedule data input by the user. The transaction schedule data is displayed on the transaction details screen in a different display mode such as displaying any character string. For this reason, since the user can distinguish at a glance whether or not an actual transaction is reserved for one or more transaction schedule data displayed on the transaction statement screen, the user can It is possible to grasp at a glance a confirmed transaction (a reserved transaction) and an undefined transaction in the data. As a result, the user can estimate the transition of the future account balance more precisely.

<< 3. Hardware configuration >>
The embodiment of the present invention has been described above. Next, the hardware configuration of the mobile terminal 10 according to the present embodiment will be described with reference to FIG. As shown in FIG. 13, the mobile terminal 10 includes a CPU 150, a ROM (Read Only Memory) 152, a RAM 154, an internal bus 156, an input / output interface 158, an input device 160, an output device 162, an HDD (Hard Disk Drive) 164, And a network interface 166.

<3-1. CPU 150>
The CPU 150 functions as an arithmetic processing device and a control device, and controls the overall operation in the mobile terminal 10 according to various programs. Further, the CPU 150 realizes the function of the control unit 100 in the mobile terminal 10. The CPU 150 is configured by a processor such as a microprocessor.

<3-2. ROM152>
The ROM 152 stores programs used by the CPU 150, calculation parameters, and the like.

<3-3. RAM154>
The RAM 154 temporarily stores programs used in the execution of the CPU 150, parameters that change as appropriate during the execution, and the like.

<3-4. Internal bus 156>
The internal bus 156 is composed of a CPU bus and the like. The internal bus 156 connects the CPU 150, the ROM 152, and the RAM 154 to each other.

<3-5. Input / output interface 158>
The input / output interface 158 connects the HDD 164 and the network interface 166 to the internal bus 156. For example, the HDD 164 exchanges data with the RAM 154 or the like via the input / output interface 158 and the internal bus 156.

<3-6. Input device 160>
The input device 160 includes, for example, an input unit for a user to input information such as a touch panel, a button, a microphone, and a switch, an input control circuit that generates an input signal based on an input by the user, and outputs the input signal to the CPU 150. It is configured. The user can input various data to the mobile terminal 10 and instruct processing contents by operating the input device 160.

<3-7. Output device 162>
The output device 162 includes display devices such as a liquid crystal display (LCD) device, an organic light emitting diode (OLED) device, and a lamp. Further, the output device 162 can include an audio output device such as a speaker.

<3-8. HDD164>
The HDD 164 is a data storage device that functions as the storage unit 124. The HDD 164 includes, for example, a storage medium, a recording device that records data on the storage medium, a reading device that reads data from the storage medium, and a deletion device that deletes data recorded on the storage medium. The HDD 164 stores programs executed by the CPU 150 and various data.

<3-9. Network Interface 166>
The network interface 166 is a communication interface composed of a communication device for connecting to a communication network such as the Internet, for example. This network interface 166 functions as the communication unit 120. The network interface 166 may be a wireless LAN compatible communication device, an LTE (Long Term Evolution) compatible communication device, or a wire communication device that performs wired communication.

<< 4. Modification >>
Although the preferred embodiments of the present invention have been described in detail with reference to the accompanying drawings, the present invention is not limited to such examples. It is obvious that a person having ordinary knowledge in the technical field to which the present invention pertains can come up with various changes or modifications within the scope of the technical idea described in the claims. Of course, it is understood that these also belong to the technical scope of the present invention.

<4-1. Modification 1>
For example, in section 2-2-1, the mobile terminal 10 (the transaction execution request unit 108) transmits a reserved scheduled transaction execution request to the WEB / DB server 20 on the scheduled transaction date of the scheduled transaction. However, the present invention is not limited to this example. For example, the mobile terminal 10 (the transaction execution request unit 108) can also transmit a reserved scheduled transaction execution request to the WEB / DB server 20 at the time of S106. The IB server 22 can execute the scheduled transaction after waiting for the scheduled transaction date of the scheduled transaction based on the execution request for the scheduled transaction received from the WEB / DB server 20.

  Alternatively, after the WEB / DB server 20 waits until the scheduled transaction date of the scheduled transaction, it is possible to transfer the execution request of the scheduled transaction received from the mobile terminal 10 to the IB server 22.

<4-2. Modification 2>
Further, the operations described in section 2-2-1 and the operations described in section 2-2-2 may be processed in parallel instead of being processed in time series. Further, the steps described in the section 2-2-1 or the operations described in the section 2-2-2 do not necessarily have to be processed in the order described, and the order may be changed as appropriate. May be processed.

<4-3. Modification 3>
In addition, according to the present embodiment, it is possible to provide a computer program for causing hardware such as the CPU 150, the ROM 152, and the RAM 154 to perform the same functions as the components of the mobile terminal 10 described above. A recording medium on which the computer program is recorded is also provided.

10 mobile terminal 12 communication network 20 WEB / DB server 22 IB server 100 control unit 102 display control unit 104 scheduled transaction input unit 106 transaction reservation unit 108 transaction execution request unit 110 transaction details request unit 120 communication unit 122 operation display unit 124 storage unit 150 CPU
152 ROM
154 RAM
156 Internal bus 158 Input / output interface 160 Input device 162 Output device 164 HDD
166 Network interface

Claims (12)

An acquisition unit for acquiring user transaction history data from the management device;
A transaction reservation unit that accepts reservations for scheduled transactions entered by the user;
Transaction control data including data of scheduled transactions for which a reservation has been accepted, and a display control unit for displaying the acquired transaction history data on a book screen;
An information processing apparatus comprising:   The information processing apparatus according to claim 1, wherein the transaction schedule data further includes data of a transaction that is not reserved among the scheduled transactions input by the user.   The information processing apparatus according to claim 2, wherein the transaction reservation unit accepts a reservation for an input planned transaction when the input type of the planned transaction is a type of a transaction to be reserved.   The information processing apparatus according to claim 3, wherein the type of transaction to be reserved is a type of transaction that the user voluntarily performs.   The information processing apparatus according to claim 3 or 4, wherein the type of transaction to be reserved includes a transfer, deposit, or withdrawal.   The information processing apparatus according to any one of claims 3 to 5, wherein the type of transaction that is not a reservation target includes a withdrawal or a transfer from another bank. In the case where the type of the planned transaction input is the type of the transaction to be reserved, the display control unit displays an inquiry as to whether or not to perform the reservation of the input planned transaction on the display screen,
The information processing apparatus according to any one of claims 3 to 6, wherein the transaction reservation unit receives a reservation of an input scheduled transaction when reservation is input by the user.   The information processing apparatus according to any one of claims 1 to 7, further comprising a transaction execution request unit that requests the management apparatus to execute a scheduled transaction for which a reservation is accepted.   The said display control part displays the said transaction plan data on the said bankbook screen in a different display mode according to whether the said transaction plan data is the data of the scheduled transaction reserved. The information processing apparatus according to any one of claims. An acquisition unit for acquiring user transaction history data from the management device;
A transaction reservation unit that accepts reservations for scheduled transactions entered by the user;
Transaction control data including received transaction reservation data, and a display control unit for displaying the acquired transaction history data on a book screen;
An information processing system comprising: Obtaining user transaction history data from the management device;
Receiving a reservation for a scheduled transaction entered by the user;
Displaying transaction schedule data including received transaction reservation data and the acquired transaction history data on a book screen; and
An information processing method comprising: Computer
An acquisition unit for acquiring user transaction history data from the management device;
A transaction reservation unit that accepts reservations for scheduled transactions entered by the user;
Transaction control data including received transaction reservation data, and a display control unit for displaying the acquired transaction history data on a book screen,
Program to function as

Images