Household Accounting Management Device

Abstract

To provide a technique with which it is possible to limit a problem from occurring as to the accuracy of a household account book due to point-utilizing payment being double accounted in the household account book.SOLUTION: A household account book management device comprises: an acquisition unit for acquiring first history data that indicates the use history of a first payment service and second history data that indicates the use history of a second payment service; and a reflection unit which, while the first history data includes first payment data that indicates a first payment that represents the payment of a payment amount having decreased by use of points, when the second history data includes second payment data resulting from the first payment, causes the first payment data to be reflected in household account book data that represents a household account book, with the second payment data not reflected.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to a household account book management device. [Background technology]

[0002] There is known a technique for managing a household account book using the usage history of each of a plurality of payment services. For example, Patent Document 1 discloses a technique for managing a household account book using the usage history of electronic money and the usage history of automatic transfer. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2000-181982 A Summary of the Invention [Problem to be solved by the invention]

[0004] In a technology for managing a household account book using the respective usage histories of a plurality of payment services, there is a possibility that a payment using points may be made in any of the payment services. For this reason, in a technology for managing a household account book using the respective usage histories of a plurality of payment services, it is necessary to restrict problems that may arise in the accuracy of the household account book due to double-counting of payments using points in the household account book.

[0005] An object of the present invention is to limit problems that may arise in the accuracy of a household account book due to double-entry of payments made using points in the household account book. [Means for solving the problem]

[0006] A household accounting management device according to one embodiment of the present invention includes an acquisition unit that acquires first history data indicating a usage history of a first payment service and second history data indicating a usage history of a second payment service, and a reflection unit that, when the first history data includes first payment data indicating a first payment, which is a payment of an amount reduced by the use of points, and the second history data includes second payment data resulting from the first payment, reflects the first payment data in household accounting data indicating the household accounting without reflecting the second payment data. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to limit problems that could arise in the accuracy of a household account book due to double-counting of payments made using points in the household account book. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing a management system HS. [Diagram 2] FIG. 2 is a diagram showing an example of household accounting data HD. [Diagram 3] FIG. 13 is a diagram showing an example of history data a1 to a4. [Figure 4] FIG. 2 is a diagram illustrating an example of a terminal device 5. [Diagram 5] FIG. 2 is a diagram illustrating an example of a household account book server 6. [Figure 6] FIG. 2 is a diagram showing an outline of the operation of the household account book server 6. [Figure 7] FIG. 4 is a diagram illustrating an example of the operation of the household account book server 6. [Figure 8] FIG. 4 is a diagram illustrating an example of the operation of the household account book server 6. [Figure 9] FIG. 4 is a diagram illustrating an example of the operation of the household account book server 6. [Figure 10] FIG. 4 is a diagram illustrating an example of the operation of the household account book server 6. [Figure 11] FIG. 13 is a diagram showing an example of an image D. [Figure 12] FIG. 2 is a diagram showing an example of an image DA. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] A: First embodiment A1: Management System HS 1 is a diagram showing a management system HS. The management system HS manages household account book data HD. The household account book data HD represents a household account book of a user U.

[0010] The management system HS includes a payment server 1, a communications company server 2, a card company server 3, a bank server 4, a terminal device 5, and a household account book server 6. The payment server 1, the communications company server 2, the card company server 3, the bank server 4, and the terminal device 5 communicate with the household account book server 6 via a network NW.

[0011] The payment server 1 is managed by a points management company that manages points that can be used for payment. The points management company uses the payment server 1 to provide a payment service P1 to the user U.

[0012] The payment service P1 is a service that provides one of the payment options. The payment service P1 is an example of a first payment service. The payment server 1 is a server that provides the payment service P1 to the user U.

[0013] The payment server 1 generates history data a1. The history data a1 indicates the usage history of the payment service P1. The usage history of the payment service P1 means the history of the usage of the payment service P1 made by the user U. The usage history of the payment service P1 is indicated by the payment data included in the history data a1. The payment data is also referred to as detailed data regarding the payment. The history data a1 is an example of first history data. When the payment server 1 is requested for the history data a1, it provides the history data a1.

[0014] Payment service P1 allows payment using points. When a payment using points occurs in payment service P1, payment data indicating the payment amount reduced by the use of points is added to history data a1. For example, when a payment using 300 yen worth of points occurs for a 500 yen product in payment service P1, payment data indicating a payment amount of 200 yen is shown in history data a1.

[0015] The payment server 1 provides the communication company server 2 with the payment data included in the history data a1. However, the payment server 1 does not provide the communication company server 2 with payment data indicating a payment in which the payment amount becomes 0 yen due to the use of points. The payment server 1 may provide the communication company server 2 with payment data indicating a payment in which the payment amount becomes 0 yen due to the use of points. A server different from the payment server 1 may provide the communication company server 2 with the payment data included in the history data a1.

[0016] The communication company server 2 is managed by a communication company. The communication company provides a payment service P2 to the user U by using the communication company server 2. The communication company may include a point management company that manages the payment server 1. The point management company may include a communication company that manages the communication company server 2.

[0017] The payment service P2 is a service that combines a payment made using the payment service P1 with a payment of communication charges. The payment of communication charges means the payment of communication charges billed to the user U. The payment service P2 may be a service that combines a payment made using the payment service P1 with a payment different from both the payment of communication charges and the payment using the payment service P1. The payment different from both the payment of communication charges and the payment using the payment service P1 is, for example, a payment of a fee different from the communication charges. The fee different from the communication charges is, for example, an electricity fee or a water fee. In this case, the provider of the payment service P2 may be different from the communication company. The payment service P2 is an example of a second payment service. The communication company server 2 is a server that provides the payment service P2 to the user U.

[0018] The communications company server 2 generates history data a2. The history data a2 indicates a usage history of the payment service P2. The usage history of the payment service P2 means a history of the usage of the payment service P2 by the user U. The usage history of the payment service P2 is indicated by the payment data included in the history data a2. The history data a2 is an example of second history data.

[0019] The communications company server 2 receives the payment data included in the history data a1 from the payment server 1. Based on the payment data received from the payment server 1, the communications company server 2 generates payment data resulting from the payment indicated by the payment data (the payment data received from the payment server 1). For example, the communications company server 2 generates payment data resulting from the payment indicated by the payment data received from the payment server 1 by changing the payee information indicated in the payment data received from the payment server 1 to information about the payment server 1. The information about the payment server 1 is, for example, information identifying the payment server 1 or information identifying the payment service P1 provided by the payment server 1.

[0020] Since payment service P2 is a service that combines payments made using payment service P1 with payments for communication fees, historical data a2 includes payment data resulting from payments made using payment service P1 and payment data indicating payments for communication fees.

[0021] The payment data resulting from a payment using the payment service P1 is the payment data resulting from the payment indicated by the payment data received from the payment server 1. When requested to provide the history data a2, the communication company server 2 provides the history data a2.

[0022] User U uses a credit card payment service for payment using payment service P2. For this reason, the communications company server 2 provides the payment data included in the history data a2 to a card company server 3 that provides a credit card payment service. A server different from the communications company server 2 may provide the payment data included in the history data a2 to the card company server 3.

[0023] The card company server 3 is managed by the card company. The card company provides a credit card payment service to the user U by using the card company server 3. The card company may include a points management company that manages the payment server 1. The points management company may include a card company that manages the card company server 3. The card company may include a communications company that manages the communications company server 2. The communications company may include a card company that manages the card company server 3.

[0024] The credit card payment service is an example of the third payment service. The card company server 3 is a server that provides the user U with a credit card payment service.

[0025] The card company server 3 generates history data a3. The history data a3 indicates a usage history of the credit card payment service. The usage history of the credit card payment service means a history of the use of the credit card payment service by the user U. The usage history of the credit card payment service is indicated by the payment data included in the history data a3. The history data a3 is an example of third history data.

[0026] The card company server 3 receives the payment data included in the history data a2 from the communications company server 2. Based on the payment data received from the communications company server 2, the card company server 3 generates payment data resulting from the payment indicated by the payment data (the payment data received from the communications company server 2). For example, the card company server 3 generates payment data resulting from the payment indicated by the payment data received from the communications company server 2 by changing the payee information indicated in the payment data received from the communications company server 2 to information related to the communications company server 2. The information related to the communications company server 2 is, for example, information identifying the communications company server 2 or information identifying the payment service P2 provided by the communications company server 2.

[0027] Because user U uses a credit card payment service for payments made using payment service P2, history data a3 includes payment data resulting from payments made using payment service P2.

[0028] The payment data resulting from a payment using the payment service P2 is the payment data resulting from the payment indicated by the payment data received from the communication company server 2. When requested to provide the history data a3, the card company server 3 provides the history data a3.

[0029] User U uses an account debit service for payments made using a credit card payment service. For this purpose, the card company server 3 provides the payment data included in the history data a3 to the bank server 4 that provides the account debit service. A server different from the card company server 3 may provide the payment data included in the history data a3 to the bank server 4.

[0030] The bank server 4 is managed by a bank. The bank provides an account debit service to the user U by using the bank server 4. The account debit service is also called an account transfer service. The bank may include a points management company that manages the payment server 1. The points management company may include a bank that manages the bank server 4. The bank may include a communications company that manages the communications company server 2. The communications company may include a bank that manages the bank server 4. The bank may include a card company that manages the card company server 3. The card company may include a bank that manages the bank server 4.

[0031] The direct debit service is an example of a fourth payment service. The bank server 4 is a server that provides the user U with a direct debit service.

[0032] The bank server 4 generates history data a4. The history data a4 indicates the usage history of the direct debit service. The usage history of the direct debit service means the history of the use of the direct debit service by the user U. The history data a4 further indicates the history of deposits into an account to which the direct debit service is applied. The usage history of the direct debit service is indicated by the payment data and deposit data included in the history data a4. The history data a4 is an example of fourth history data.

[0033] The bank server 4 receives the payment data included in the history data a3 from the card company server 3. Based on the payment data received from the card company server 3, the bank server 4 generates payment data resulting from the payment indicated by the payment data (the payment data received from the card company server 3). For example, the bank server 4 generates payment data resulting from the payment indicated by the payment data received from the card company server 3 by changing the payee information indicated in the payment data received from the card company server 3 to information related to the card company server 3. The information related to the card company server 3 is, for example, information identifying the card company server 3 or information identifying the credit card payment service provided by the card company server 3.

[0034] Since user U uses an account debit service for payments made using a credit card payment service, history data a4 includes payment data resulting from payments made using the credit card payment service.

[0035] The payment data resulting from a payment using the credit card payment service is the payment data resulting from a payment indicated by the payment data received from the card company server 3. When requested, the bank server 4 provides the history data a4.

[0036] The terminal device 5 is a smartphone. The terminal device 5 is not limited to a smartphone, and may be, for example, a personal computer or a tablet. The terminal device 5 is used by a user U.

[0037] The household account book server 6 is a server that manages household account book data HD that shows the household account book of the user U. The household account book server 6 acquires history data a1 to a4. The household account book server 6 manages the household account book data HD by using the history data a1 to a4. The household account book server 6 is an example of a household account book management device.

[0038] A2: Household Accounting Data HD Fig. 2 is a diagram showing an example of household accounting data HD. The household accounting data HD represents the income and expenditures of a user U. The expenditures of the user U include payments from the user U. The household accounting data HD is not limited to the household accounting data HD shown in Fig. 2. For example, the household accounting data HD may have multiple "content" items, or may not have a "content" item.

[0039] A3: Historical data 3 is a diagram showing an example of the history data a1 to a4 acquired by the household account book server 6. The history data a1 to a4 are not limited to the data shown in FIG.

[0040] The history data a1 to a4 include payment data indicating the payee, the payment amount, the date, and the content (such as the name of the purchased product). In FIG. 3, the date and content are omitted.

[0041] The payment data in the historical data a1 (for example, payment data b1 and b5) indicates "combined payment" instead of "payment amount" as the item indicating the payment amount. The payment data in the historical data a1 indicates the amount of points used in addition to the payee and payment amount (combined payment). The payment data in the historical data a1 indicates "points" as the item indicating the amount of points used. If the amount of points used is "0", the payment data in the historical data a1 does not need to indicate the item "points" and the amount of points used (0 yen).

[0042] The payment data in the history data a2 (for example, the payment data b2 and b6) indicates "communication charges" instead of "payment amount" as the item indicating the payment amount for payments to which the payee is a "communication company." The payment data in the history data a2 may also indicate "payment amount" as the item indicating the payment amount for payments to which the payee is a "communication company."

[0043] A4: Historical data a1 The history data a1 is generated by the payment server 1. The history data a1 includes payment data b1 and payment data b5.

[0044] Payment data b1 indicates payment f1. Payment f1 is a payment in which the payment amount of 500 yen to a seller named "AA" is reduced to 200 yen by using 300 yen worth of points. In other words, payment f1 is a payment of 200 yen reduced by using points. Payment f1 is an example of a first payment. The first payment is a payment of a payment amount reduced by using points. The first payment is not limited to payment f1. Payment data b1 indicates payment f1, which is an example of a first payment (a payment of a payment amount reduced by using points). Payment data b5 is an example of first payment data indicating the first payment.

[0045] Payment data b1 has information indicating "AA" as information on the payee. Payee information means information indicating the payee. Information indicating "AA" is information identifying a seller named "AA". Payment data b1 has information indicating "500 yen" as information indicating the amount to be paid to the payee. Payment data b1 has information indicating "300 yen" as information indicating the amount of points used. Payment data b1 has information indicating "200 yen" as information on the actual payment amount from user U (combined payment). Payment amount information means information indicating the payment amount.

[0046] Payment data b5 indicates payment f5. Payment f5 is a payment in which the payment amount of 100 yen to a seller named "BB" is reduced to a payment amount of 0 yen by using 100 yen worth of points. In other words, payment f5 is a payment of 0 yen reduced by using points. Payment f5 is another example of a first payment (a payment of a payment amount reduced by using points). Payment f5 is also an example of a payment of a payment amount that has become 0 by using points. Payments of a payment amount that has become 0 by using points are not limited to payment f5. Payment data b5 indicates payment f5, which is another example of a first payment. Payment data b5 is another example of first payment data indicating a first payment.

[0047] The payment data b5 has information indicating "BB" as information on the payee. The information indicating "BB" is information that identifies a seller named "BB". The payment data b5 has information indicating "100 yen" as information indicating the amount to be paid to the payee. The payment data b5 has information indicating "100 yen" as information indicating the amount of points used. The payment data b5 has information indicating "0 yen" as information on the actual payment amount from user U (combined payment).

[0048] A5: Historical data A2 The history data a2 is generated by the communication company server 2. The history data a2 includes payment data b2 and payment data b6.

[0049] The payment data b2 is generated from the payment data b1 received from the payment server 1. The payment data b2 results from a payment f1 which the payment data b1 indicates.

[0050] The payment data b2 has information c1 indicating "1st / AA" as the payment destination information. The information c1 indicating "1st / AA" is preset as information identifying the point management company that provides the payment service P1. The payment data b2 has information indicating "200 yen" as the payment amount information.

[0051] Payment data b2 is an example of second payment data resulting from a first payment (a payment of the payment amount reduced by using points). The second payment data includes first information identifying payment service P1 (an example of a first payment service) as information on the payee. The second payment data further includes information on the payment amount indicating an amount equal to the payment amount in the first payment.

[0052] The payment data b2 is an example of second payment data. The information c1 indicating "1st / AA" in the payment data b2 includes the keyword "1st". The keyword "1st" is a nickname for the payment service P1 and is a keyword that identifies the payment service P1. Therefore, the information c1 indicating "1st / AA" including the keyword "1st" is information that identifies the point management company, as well as information that identifies the payment service P1. Therefore, the information c1 indicating "1st / AA" is an example of first information that identifies the payment service P1. Furthermore, the payment data b2 has, as payment amount information, information indicating the same amount (200 yen) as the payment amount "200 yen" in the payment f1, which is an example of the first payment (payment of the payment amount reduced by using points). Therefore, the payment data b2 is an example of second payment data.

[0053] Payment data b6 indicates payment f6. Payment f6 is a payment of 1,000 yen in communication fees to a communications company. Payment data b6 has information indicating "communications company" as information on the payee. The information indicating "communications company" is information that identifies the communications company that provides payment service P2. Payment data b6 has information indicating "1,000 yen" as information on the payment amount.

[0054] A6: Historical data A3 History data a3 is generated by card company server 3. History data a3 indicates payment data b3, payment data b7, and payment data b8.

[0055] The payment data b3 is generated from the payment data b2 received from the communication company server 2. The payment data b2 is generated from the payment data b1 received from the payment server 1. Therefore, the payment data b3 originates from the payment f1 indicated by the payment data b1.

[0056] The payment data b3 includes information c21 indicating "telecommunications company payment" as payment destination information. The information c21 indicating "telecommunications company payment" is information that identifies the telecommunications company that provides the payment service P2. The payment data b3 includes information indicating "200 yen" as payment amount information.

[0057] The payment data b3 is an example of third payment data. The third payment data includes second information that identifies the payment service P2 (an example of the second payment service) as information on the payee.

[0058] The payment data b3 is an example of third payment data. Information c21 indicating "telecommunications company payment" in the payment data b3 includes the keyword "telecommunications company". The keyword "telecommunications company" is the name of the telecommunications company that provides the payment service P2, and is a keyword that identifies the payment service P2. Therefore, the information c21 indicating "telecommunications company payment" including the keyword "telecommunications company" is information that identifies the payment service P2, in addition to being information that identifies the telecommunications company. Therefore, the information c21 indicating "telecommunications company payment" is an example of second information that identifies the payment service P2. Therefore, the payment data b3 is an example of third payment data.

[0059] The payment data b7 is generated from the payment data b6 received from the communication company server 2. Therefore, the payment data b7 results from the payment f6 indicated by the payment data b6.

[0060] The payment data b7 includes information c22 indicating "telecommunications company communication fee" as payment destination information. The information c22 indicating "telecommunications company communication fee" is information that identifies the telecommunications company that provides the payment service P2. The payment data b7 includes information indicating "1000 yen" as payment amount information.

[0061] The payment data b7 is another example of the third payment data. The third payment data includes second information that identifies the payment service P2 as information on the payee.

[0062] The payment data b7 is another example of the third payment data. The information c22 indicating "telecommunications company communication fees" in the payment data b7 includes the keyword "telecommunications company". As described above, the keyword "telecommunications company" is a keyword that identifies the payment service P2. Therefore, the information c22 indicating "telecommunications company communication fees" including the keyword "telecommunications company" is information that identifies the payment service P2, in addition to being information that identifies the telecommunications company. Therefore, the information c22 indicating "telecommunications company communication fees" is another example of the second information that identifies the payment service P2. Therefore, the payment data b7 is another example of the third payment data.

[0063] Payment data b8 indicates payment f8. Payment f8 is a payment of 100 yen to a seller named "CC". Payment data b8 has information indicating "CC" as information on the payee. The information indicating "CC" is information that identifies the seller named "CC". Payment data b8 has information indicating "100 yen" as information on the payment amount.

[0064] A7: History data A4 The history data a4 is generated by the bank server 4. The history data a4 indicates the payment data b4.

[0065] Payment data b4 is generated from combined payment data b3, b7, and b8 received from the card company server 3. Payment data b3 is generated from payment data b2 received from the communications company server 2. Payment data b2 is generated from payment data b1 received from the payment server 1. Payment data b7 is generated from payment data b6 received from the communications company server 2. Therefore, payment data b4 results from payment f1 indicated by payment data b1, payment f6 indicated by payment data b6, and payment f8 indicated by payment data b8.

[0066] The payment data b4 includes information c3 indicating "card" as information on the payee. The information c3 indicating "card" is information that identifies a card company that provides credit card payment services. The payment data b4 includes information indicating "1,300 yen" as information on the payment amount.

[0067] The payment data b4 is an example of the fourth payment data. The fourth payment data includes third information that identifies a credit card payment service (an example of a third payment service) as information on the payee.

[0068] The payment data b4 is an example of the fourth payment data. The information c3 indicating "card" in the payment data b4 includes the keyword "card". The keyword "card" is an abbreviation for a card company that provides credit card payment services, and is a keyword that identifies the credit card payment service. Therefore, the information c3 indicating "card" that includes the keyword "card" is information that identifies the card company, as well as information that identifies the credit card payment service. Therefore, the information c3 indicating "card" is an example of third information that identifies the credit card payment service (an example of a third payment service). Therefore, the payment data b4 is an example of the fourth payment data.

[0069] A8: Example of payment data reflected in household accounting data HD Payment data b1, b2, b3, and b4 are payment data resulting from payment f1 (payment of the payment amount reduced by using points). Therefore, when payment data b1, b2, b3, and b4 are reflected in the household accounting data HD, payment f1 is reflected redundantly in the household accounting data HD. Therefore, among the payment data b1, b2, b3, and b4, the household accounting server 6 reflects only payment data b1 indicating payment f1 in the household accounting data HD.

[0070] A9: Terminal device 5 4 is a diagram showing an example of the terminal device 5. The terminal device 5 includes an input device 51, a display device 52, a communication device 53, a storage device 54, and a processing device 55.

[0071] The input device 51 includes a keyboard. The input device 51 may include at least one of a mouse and a touch panel. When the input device 51 includes a touch panel, it does not have to include at least one of a keyboard and a mouse. The input device 51 accepts operations performed by a user.

[0072] The display device 52 displays various information. The display device 52 may include a touch panel. The touch panel may be used as both the input device 51 and the display device 52.

[0073] The communication device 53 communicates with the household account book server 6 via the network NW. The communication device 53 may further communicate with one or more of the payment server 1, the communication company server 2, the card company server 3, and the bank server 4 via the network NW.

[0074] The storage device 54 is a recording medium readable by the processing device 55. The storage device 54 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a Read Only Memory (ROM), an Erasable Programmable Read Only Memory (EPROM), and an Electrically Erasable Programmable Read Only Memory (EEPROM). The volatile memory is, for example, a Random Access Memory (RAM). The storage device 54 stores an application program 541.

[0075] The processing device 55 includes one or more central processing units (CPUs). The one or more CPUs are an example of one or more processors. Each of the processor and the CPU is an example of a computer.

[0076] The processing device 55 reads the application program 541 from the storage device 54. The processing device 55 executes the application program 541 to function as an operation control unit 551.

[0077] The operation control unit 551 may be realized by a circuit such as a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA).

[0078] The operation control unit 551 controls the terminal device 5. For example, the operation control unit 551 communicates with the household accounting server 6 via the communication device 53.

[0079] A10: Household accounting server 6 5 is a diagram showing an example of the household accounting server 6. The household accounting server 6 includes a communication device 61, a storage device 62, and a processing device 63.

[0080] The communication device 61 communicates with each of the payment server 1, the communication company server 2, the card company server 3, the bank server 4, and the terminal device 5 via the network NW.

[0081] The storage device 62 is a recording medium that can be read by the processing device 63. The storage device 62 includes, for example, a non-volatile memory and a volatile memory. The storage device 62 stores a program 621 and household accounting data HD.

[0082] The processing device 63 is configured with one or more CPUs. The processing device 63 reads a program 621 from the storage device 62. The processing device 63 executes the program 621 to function as an acquisition unit 631, a reflection unit 632, and a display control unit 633. At least one of the acquisition unit 631, the reflection unit 632, and the display control unit 633 may be realized by a circuit such as a DSP, an ASIC, a PLD, or an FPGA.

[0083] The acquisition unit 631 acquires history data a1 to a4. The acquisition unit 631 acquires history data a1 from the payment server 1. The acquisition unit 631 acquires history data a2 from the communications company server 2. The acquisition unit 631 acquires history data a3 from the card company server 3. The acquisition unit 631 acquires history data a4 from the bank server 4.

[0084] The reflection unit 632 updates the household ledger data HD based on the history data a1 to a4. For example, when the history data a1 includes first payment data indicating a first payment and the history data a2 includes second payment data resulting from the first payment, the reflection unit 632 reflects the first payment data in the household ledger data HD without reflecting the second payment data.

[0085] The display control unit 633 causes the terminal device 5 to display an image based on the household account book data HD. For example, when the history data a1 includes target payment data indicating a payment of an amount that has become zero through the use of points, the display control unit 633 operates as follows: The display control unit 633 causes the terminal device 5 to display an image that does not show the payment indicated by the target payment data, but shows a payment in the usage history indicated by the history data a1 that is different from the payment indicated by the target payment data.

[0086] A11: Operation explanation Fig. 6 is a diagram showing an overview of the operation of the household accounting server 6. The operation shown in Fig. 6 is executed once a month. One month is an example of a predetermined period. The predetermined period is not limited to one month, and may be a period shorter or longer than one month. The predetermined period may be changed.

[0087] In step S101, the acquisition unit 631 acquires the history data a1 to a4. For example, the acquisition unit 631 acquires the history data a1 from the payment server 1 by requesting the payment server 1 for the history data a1. The acquisition unit 631 acquires the history data a2 from the communication company server 2 by requesting the communication company server 2 for the history data a2. The acquisition unit 631 acquires the history data a3 from the card company server 3 by requesting the history data a3 from the card company server 3. The acquisition unit 631 acquires the history data a4 from the bank server 4 by requesting the history data a4 from the bank server 4.

[0088] Next, in step S102, the reflecting unit 632 updates the household accounting data HD based on the history data a1 to a4. An example of step S102 will be described later.

[0089] Next, in step S103, the display control section 633 causes an image based on the household account book data HD to be displayed on the terminal device 5. An example of step S103 will be described later.

[0090] 7 to 10 are diagrams showing an example of step S102. In step S201, the reflection unit 632 determines whether the history data a1 includes first payment data (payment data indicating a payment of a payment amount reduced by using points).

[0091] In Fig. 4, each of the payment data b1 and the payment data b5 corresponds to the first payment data. Therefore, in Fig. 4, the history data a1 includes the first payment data.

[0092] When the reflection unit 632 determines in step S201 that the history data a1 includes the first payment data, it determines in step S202 whether or not the history data a2 includes second payment data (payment data resulting from the first payment).

[0093] The second payment data includes first information (information including the keyword “first”) that identifies the payment service P1 as information on the payee. The second payment data further includes information on the payment amount that is the same as the payment amount in the first payment.

[0094] In FIG. 4, payment data b2 has first information (information including the keyword "first") that identifies payment service P1 as payment recipient information. Payment data b2 further has information indicating the same amount (200 yen) as the payment amount in payment f1, which corresponds to the first payment. Therefore, payment data b2 corresponds to second payment data. Therefore, in FIG. 4, history data a2 includes second payment data.

[0095] When the reflection unit 632 determines in step S202 that the history data a2 includes the second payment data, it determines in step S203 whether the history data a3 includes the third payment data.

[0096] The third payment data includes second information (information including the keyword "communications company") that identifies the payment service P2 as payment recipient information.

[0097] In Fig. 4, payment data b3 and payment data b7 have second information (information including the keyword "communications company") that identifies payment service P2 as payment recipient information. Therefore, payment data b3 and payment data b7 correspond to the third payment data. Therefore, in Fig. 4, history data a3 includes the third payment data.

[0098] When the reflection unit 632 determines in step S203 that the history data a3 includes the third payment data, it determines in step S204 whether the history data a4 includes the fourth payment data.

[0099] The fourth payment data includes third information (information including the keyword "card") that identifies a credit card payment service as payment recipient information.

[0100] In Fig. 4, payment data b4 includes third information (information including the keyword "card") that identifies a credit card payment service as payment recipient information. Therefore, payment data b4 corresponds to fourth payment data. Therefore, in Fig. 4, history data a4 includes the fourth payment data.

[0101] If the reflection unit 632 determines in step S204 that the history data a4 includes the fourth payment data, it executes step S205 shown in FIG.

[0102] In step S205, the reflecting unit 632 does not reflect the second payment data, the third payment data, and the fourth payment data in the household account book data HD, but reflects the first payment data and the remaining payment data in the household account book data HD.

[0103] For example, the reflection unit 632 does not register the second payment data, the third payment data, and the fourth payment data as expenditures in the household account book data HD, but registers the first payment data and the remaining payment data as expenditures in the household account book data HD.

[0104] The remaining payment data refers to payment data different from any of the first, second, third, and fourth payment data in the payment data group made up of the payment data indicated in historical data a1 to a4. The payment data group is made up of the payment data included in historical data a1, the payment data included in historical data a2, the payment data included in historical data a3, and the payment data included in historical data a4.

[0105] In Fig. 4, for example, payment data b5, b6, and b8 correspond to the remaining payment data. The remaining payment data does not have to include payment data (e.g., payment data b5) indicating a payment in which the payment amount reduced by using points has become 0.

[0106] If there is no remaining payment data, the reflecting unit 632 reflects the first payment data in the household account book data HD without reflecting the second payment data, the third payment data, and the fourth payment data in the household account book data HD in step S205.

[0107] If the reflection unit 632 determines in step S204 that the history data a4 does not include the fourth payment data, the reflection unit 632 executes step S206.

[0108] In step S206, the reflection unit 632 reflects the first payment data and the remaining payment data in the household accounting data HD without reflecting the second payment data and the third payment data in the household accounting data HD. For example, the reflection unit 632 registers the first payment data and the remaining payment data in the expenditures in the household accounting data HD without registering the second payment data and the third payment data in the expenditures in the household accounting data HD. If there is no remaining payment data, the reflection unit 632 reflects the first payment data in the household accounting data HD without reflecting the second payment data and the third payment data in the household accounting data HD in step S206.

[0109] If the reflection unit 632 determines in step S203 that the history data a3 does not include the third payment data, then in step S207 it determines whether or not the history data a4 includes the fourth payment data.

[0110] If the reflection unit 632 determines in step S207 that the history data a4 includes the fourth payment data, the reflection unit 632 executes step S208.

[0111] In step S208, the reflection unit 632 reflects the first payment data and the remaining payment data in the household accounting data HD without reflecting the second payment data and the fourth payment data in the household accounting data HD. For example, the reflection unit 632 registers the first payment data and the remaining payment data in the expenditures in the household accounting data HD without registering the second payment data and the fourth payment data in the expenditures in the household accounting data HD. If there is no remaining payment data, the reflection unit 632 reflects the first payment data in the household accounting data HD without reflecting the second payment data and the fourth payment data in the household accounting data HD in step S208.

[0112] If the reflection unit 632 determines in step S207 that the history data a4 does not include the fourth payment data, the reflection unit 632 executes step S209.

[0113] In step S209, the reflection unit 632 reflects the first payment data and the remaining payment data in the household accounting data HD without reflecting the second payment data in the household accounting data HD. For example, the reflection unit 632 registers the first payment data and the remaining payment data in the expenditure in the household accounting data HD without registering the second payment data in the expenditure in the household accounting data HD. If there is no remaining payment data, the reflection unit 632 reflects the first payment data in the household accounting data HD without reflecting the second payment data in the household accounting data HD in step S209.

[0114] If the reflection unit 632 determines in step S202 that the history data a2 does not include the second payment data, then in step S210 it determines whether the history data a3 includes the third payment data.

[0115] When the reflection unit 632 determines in step S210 that the history data a3 includes the third payment data, it determines in step S211 whether the history data a4 includes the fourth payment data.

[0116] When the reflection unit 632 determines in step S211 that the history data a4 includes the fourth payment data, it executes step S212 shown in FIG.

[0117] In step S212, the reflection unit 632 reflects the first payment data and the remaining payment data in the household accounting data HD without reflecting the third payment data and the fourth payment data in the household accounting data HD. For example, the reflection unit 632 registers the first payment data and the remaining payment data in the expenditures in the household accounting data HD without registering the third payment data and the fourth payment data in the expenditures in the household accounting data HD. If there is no remaining payment data, in step S212, the reflection unit 632 reflects the first payment data in the household accounting data HD without reflecting the third payment data and the fourth payment data in the household accounting data HD.

[0118] If the reflection unit 632 determines in step S211 that the history data a4 does not include the fourth payment data, the reflection unit 632 executes step S213.

[0119] In step S213, the reflection unit 632 reflects the first payment data and the remaining payment data in the household accounting data HD without reflecting the third payment data in the household accounting data HD. For example, the reflection unit 632 registers the first payment data and the remaining payment data in the expenditure in the household accounting data HD without registering the third payment data in the expenditure in the household accounting data HD. If there is no remaining payment data, the reflection unit 632 reflects the first payment data in the household accounting data HD without reflecting the third payment data in step S213.

[0120] If the reflection unit 632 determines in step S210 that the history data a3 does not include the third payment data, then in step S214 it determines whether or not the history data a4 includes the fourth payment data.

[0121] If the reflection unit 632 determines in step S214 that the history data a4 includes the fourth payment data, the reflection unit 632 executes step S215.

[0122] In step S215, the reflection unit 632 reflects the first payment data and the remaining payment data in the household accounting data HD without reflecting the fourth payment data in the household accounting data HD. For example, the reflection unit 632 registers the first payment data and the remaining payment data in the expenditure in the household accounting data HD without registering the fourth payment data in the expenditure in the household accounting data HD. If there is no remaining payment data, the reflection unit 632 reflects the first payment data in the household accounting data HD without reflecting the fourth payment data in the household accounting data HD in step S215.

[0123] If the reflection unit 632 determines in step S214 that the history data a4 does not include the fourth payment data, the reflection unit 632 executes step S216.

[0124] In step S216, the reflecting unit 632 reflects the first payment data and the remaining payment data in the household accounting data HD. For example, the reflecting unit 632 registers the first payment data and the remaining payment data in expenditures in the household accounting data HD. If there is no remaining payment data, the reflecting unit 632 reflects the first payment data in the household accounting data HD in step S216.

[0125] If the reflection unit 632 determines in step S201 that the history data a1 does not include the first payment data, then in step S217 shown in FIG. 10, the reflection unit 632 determines whether the history data a3 includes the third payment data.

[0126] When the reflection unit 632 determines in step S217 that the history data a3 includes the third payment data, it determines in step S218 whether or not the history data a4 includes the fourth payment data.

[0127] If the reflection unit 632 determines in step S218 that the history data a4 includes the fourth payment data, the reflection unit 632 executes step S219.

[0128] In step S219, the reflection unit 632 does not reflect the third payment data and the fourth payment data in the household accounting data HD, and reflects the remaining payment data in the household accounting data HD. For example, the reflection unit 632 does not register the third payment data and the fourth payment data in expenditures in the household accounting data HD, and registers the remaining payment data in expenditures in the household accounting data HD. If there is no remaining payment data, the reflection unit 632 ends step S219 without reflecting the third payment data and the fourth payment data in the household accounting data HD in step S219.

[0129] If the reflection unit 632 determines in step S218 that the history data a4 does not include the fourth payment data, the reflection unit 632 executes step S220.

[0130] In step S220, the reflection unit 632 does not reflect the third payment data in the household accounting data HD, but reflects the remaining payment data in the household accounting data HD. For example, the reflection unit 632 does not register the third payment data in the expenditure in the household accounting data HD, but registers the remaining payment data in the expenditure in the household accounting data HD. If there is no remaining payment data, the reflection unit 632 does not reflect the third payment data in the household accounting data HD in step S220, and ends step S220.

[0131] If the reflection unit 632 determines in step S217 that the history data a3 does not include the third payment data, then in step S221 it determines whether or not the history data a4 includes the fourth payment data.

[0132] If the reflection unit 632 determines in step S221 that the history data a4 includes the fourth payment data, the reflection unit 632 executes step S222.

[0133] In step S222, the reflection unit 632 does not reflect the fourth payment data in the household accounting data HD, and reflects the remaining payment data in the household accounting data HD. For example, the reflection unit 632 does not register the fourth payment data in expenditures in the household accounting data HD, and registers the remaining payment data in expenditures in the household accounting data HD. If there is no remaining payment data, the reflection unit 632 does not reflect the fourth payment data in the household accounting data HD in step S222, and ends step S222.

[0134] If the reflection unit 632 determines in step S221 that the history data a4 does not include the fourth payment data, the reflection unit 632 executes step S223.

[0135] In step S223, the reflecting unit 632 reflects the remaining payment data in the household account book data HD. For example, the reflecting unit 632 registers the remaining payment data in expenditures in the household account book data HD. If there is no remaining payment data, the reflecting unit 632 ends step S223.

[0136] In this way, when history data a1 includes first payment data and history data a2 includes second payment data (YES in step S202), the reflection unit 632 reflects the first payment data in the household accounting data HD without reflecting the second payment data.

[0137] When history data a1 includes the first payment data, history data a2 includes the second payment data, and history data a3 includes the third payment data (YES in step S203), reflection unit 632 operates as follows: Reflection unit 632 reflects the first payment data in household account book data HD without reflecting the second payment data and the third payment data in household account book data HD.

[0138] When history data a1 includes the first payment data, history data a2 includes the second payment data, history data a3 includes the third payment data, and history data a4 includes the fourth payment data (YES in step S204), reflection unit 632 operates as follows: Reflection unit 632 reflects the first payment data in household account book data HD without reflecting the second payment data, the third payment data, and the fourth payment data in household account book data HD.

[0139] Next, an example of step S103 shown in Fig. 6 will be described. The display control unit 633 causes an image D based on the household accounting data HD to be displayed on the terminal device 5. Fig. 11 is a diagram showing an example of the image D.

[0140] When the history data a1 includes target payment data (for example, payment data b5 in FIG. 3) indicating a payment of an amount that has become zero through the use of points, the display control unit 633 causes the terminal device 5 to display an image D including image D1.

[0141] Image D1 does not represent the payment indicated by the target payment data (the payment whose amount has become zero due to the use of points), but represents a payment indicated by history data a1 that is different from the payment indicated by the target payment data. The payment indicated by history data a1 means the usage history indicated by history data a1.

[0142] The display control unit 633 provides image information e1 indicating image D including image D1 to the terminal device 5. The operation control unit 551 in the terminal device 5 causes the display device 52 to display image D including image D1 based on the image information e1.

[0143] When the history data a2 includes second payment data resulting from the first payment (for example, payment data b2 in FIG. 3), the display control unit 633 causes the terminal device 5 to display an image D including an image D2.

[0144] Image D2 does not represent the second payment data resulting from the first payment (e.g., payment data b2 in FIG. 3), but represents a payment represented by history data a2 that is different from the payment represented by the second payment data (e.g., payment f6 represented by payment data b6 in FIG. 3). The payment represented by history data a2 means the usage history represented by history data a2.

[0145] The display control unit 633 provides image information e2 indicating image D including image D2 to the terminal device 5. The operation control unit 551 in the terminal device 5 causes the display device 52 to display image D including image D2 based on the image information e2.

[0146] When the history data a3 includes the third payment data (payment data indicating a payment that overlaps with the payment indicated by the history data a2), the display control unit 633 causes the terminal device 5 to display the image D including the image D3.

[0147] Image D3 does not represent a payment indicated by the third payment data (e.g., payment data b3 and b7 in FIG. 3), but represents a payment indicated by the history data a3 that is different from the payment indicated by the third payment data (e.g., payment f8 indicated by payment data b8 in FIG. 3). The payment indicated by the history data a3 means the usage history indicated by the history data a3.

[0148] The display control unit 633 provides image information e3 indicating image D including image D3 to the terminal device 5. The operation control unit 551 in the terminal device 5 causes the display device 52 to display image D including image D3 based on the image information e3.

[0149] When the history data a4 includes the fourth payment data (payment data indicating a payment that overlaps with the payment indicated by the history data a3), the display control unit 633 causes the terminal device 5 to display an image D including an image D4.

[0150] Image D4 does not represent the fourth payment data (for example, payment data b4 in FIG. 3), but represents a payment that is different from the payment represented by the fourth payment data among the payments represented by the history data a4. The payment represented by the history data a4 means the usage history represented by the history data a4.

[0151] The display control unit 633 provides image information e4 indicating image D including image D4 to the terminal device 5. The operation control unit 551 in the terminal device 5 causes the display device 52 to display image D including image D4 based on the image information e4.

[0152] When image D includes images D1 to D4, the display control unit 633 provides image information e indicating image D including images D1 to D4 to the terminal device 5. The operation control unit 551 in the terminal device 5 causes the display device 52 to display image D including images D1 to D4 based on the image information e.

[0153] A12: Summary of the first embodiment According to the first embodiment, the acquisition unit 631 acquires the history data a1 and a2. In a situation where the history data a1 includes first payment data indicating a first payment, which is a payment of an amount reduced by using points, and the history data a2 includes second payment data resulting from the first payment, the reflection unit 632 operates as follows. The reflection unit 632 reflects the first payment data in the household account book data HD without reflecting the second payment data. This makes it possible to limit problems with the accuracy of the household account book caused by payments using points being double-counted in the household account book.

[0154] When the history data a1 includes target payment data indicating a payment of a payment amount that has become zero through the use of points, the display control unit 633 causes the terminal device 5 to display image D1. Image D1 does not indicate the payment indicated by the target payment, but indicates a payment in the usage history indicated by the history data a1 that is different from the payment indicated by the target payment data. This makes it possible to restrict the display of payments that do not affect the balance in the household account book (payments of an amount that has become zero through the use of points). Furthermore, the process for displaying payments that do not affect the balance in the household account book can be omitted.

[0155] B: Variation The following are modified aspects of the above-described embodiment. Two or more aspects selected from the following modified aspects may be combined as appropriate within the scope of not being mutually contradictory.

[0156] B1: First modified example In the first embodiment, the first payment (a payment of the payment amount reduced by the use of points) may be limited to a payment in which the payment amount reduced by the use of points is greater than 0. In this case, the payment f1 shown in Fig. 3 corresponds to the first payment, and the payment f5 shown in Fig. 3 does not correspond to the first payment.

[0157] In the first modified example, if the history data a2 includes, for example, payment data resulting from a payment 5f with a payment amount of 0 yen (payment data indicating a payment with a payment amount of 0 yen), the payment 5f with a payment amount of 0 yen is double-counted in the household accounting data HD. However, the double-counted payment 5f is a payment with a payment amount of 0 yen. Therefore, even if the payment 5f is double-counted in the household accounting data HD, the total amount of expenditures in the household accounting data HD is not affected by the double counting. Therefore, even if the first payment is limited to payments with a payment amount reduced by the use of points that is greater than 0, it is possible to limit the occurrence of problems with the accuracy of the household accounting data HD caused by double counting.

[0158] B2: Second variant In the first embodiment and the first variant, when the history data a1 includes target payment data (payment data indicating a payment of an amount that has become zero through the use of points), the display control unit 633 may cause the terminal device 5 to display image D1A shown in FIG. 12 instead of image D1.

[0159] Image D1A represents a payment indicated by the target payment data (e.g., payment f5 in FIG. 3) and a payment indicated by history data a1 that is different from the payment indicated by the target payment data (e.g., payment f1 in FIG. 3). The display control unit 633 provides image information e1A indicating image D1A to the terminal device 5, thereby causing the terminal device 5 to display image D1A. For example, the display control unit 633 causes the terminal device 5 to display image DA as shown in FIG. 12 instead of image D.

[0160] According to the second modified example, the user U can check the payment that has become zero by using the points by looking at the image D1A.

[0161] B3: Third variant In the first embodiment and the first to second modified examples, the history data a3 may be omitted.In the first embodiment and the first to second modified examples, the history data a4 may be omitted.

[0162] In the first embodiment and the first to second modifications, the communication company server 2 may generate payment data b2 including all information indicated by the payment data b1 received from the payment server 1 and information on the payee (first / AA) based on the sender of the payment data b1. In this case, the payment service P2 is another example of the first payment service. Furthermore, the payment service P1 is another example of the second payment service. Furthermore, the history data a2 is another example of the first history data. Furthermore, the history data a1 is another example of the second history data. Furthermore, the payment data b2 is another example of the first payment data. Furthermore, the payment data b1 is another example of the second payment data. Furthermore, the payment data b3 is not an example of the third payment data. Furthermore, the payment data b4 is not an example of the fourth payment data.

[0163] B4: Fourth variant In the first embodiment and the first to third modified examples, the household account book server 6 may be included in the payment server 1, the communications company server 2, the card company server 3, the bank server 4, or the terminal device 5.

[0164] B5: Fifth variant In the first embodiment and the first to fourth modified examples, the reflecting unit 632 may update the household accounting data HD based on an instruction from the terminal device 5.

[0165] In this case, the user U uses the input device 51 of the terminal device 5 to input an instruction to update the household ledger data HD to the terminal device 5. The operation control unit 551 of the terminal device 5 provides the instruction to update the household ledger data HD to the household ledger server 6 from the communication device 53.

[0166] According to the fifth modification, the user U can update the household accounting data HD as needed.

[0167] C:Other (1) In each of the first embodiment and the first to fifth modifications, the storage devices 54 and 62 may include a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory device (e.g., a card, a stick, a key drive), a CD-ROM (Compact Disc-ROM), a register, a removable disk, a hard disk, a floppy (registered trademark) disk, a magnetic strip, a database, a server, or other suitable storage medium. The program may also be transmitted from a network via a telecommunications line.

[0168] (2) Each of the first embodiment and the first to fifth variants may be applied to a system using LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other appropriate system, and / or a next-generation system extended based on these.

[0169] (3) The information and the like described in each of the first embodiment and the first to fifth modified examples may be represented using any of a variety of different technologies. For example, data, information, and the like that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields, magnetic particles, optical fields, photons, or any combination thereof. Note that terms described in this specification and / or terms necessary for understanding this specification may be replaced with terms having the same or similar meanings.

[0170] (4) In each of the first embodiment and the first to fifth modifications, the input and output information, etc. may be stored in a specific location (for example, a memory) or may be managed by a table. The input and output information, etc. may be overwritten, updated, or added. The output information, etc. may be deleted. The input information, etc. may be transmitted to another device.

[0171] (5) In each of the first embodiment and the first to fifth variants, the determination may be made based on a value represented by one bit (0 or 1), based on a Boolean value (true or false), or based on a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0172] (6) The order of the process procedures, sequences, or flow charts illustrated in the first embodiment and the first to fifth modifications may be changed as long as there is no inconsistency. For example, the methods described herein present elements of various steps in an exemplary order, and are not limited to the particular order presented.

[0173] (7) Each function illustrated in Figure 4 or 5 may be realized by any combination of hardware and software. Furthermore, each function may be realized by a single device, or may be realized by two or more devices configured separately from each other.

[0174] (8) The programs exemplified in the first embodiment and each of the first to fifth modified examples should be broadly construed to mean instructions, instruction sets, code, code segments, program code, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, or functions, regardless of whether they are called software, firmware, middleware, microcode, or hardware description language, or by other names. In addition, software, instructions, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using wired technologies such as coaxial cable, fiber optic cable, twisted pair, and digital subscriber line (DSL), and / or wireless technologies such as infrared, radio, and microwave, these wired and / or wireless technologies are included within the definition of a transmission medium.

[0175] (9) In each of the first embodiment and the first to fifth modifications, the terms "system" and "network" are used interchangeably.

[0176] (10) In each of the first embodiment and the first to fifth modifications, the terminal device 5 may be a mobile station. A mobile station may also be referred to by those skilled in the art as a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other appropriate term.

[0177] (11) In each of the first embodiment and the first to fifth modified examples, the term "based on" does not mean "based only on," unless otherwise specified. In other words, the term "based on" means both "based only on" and "based at least on."

[0178] (12) As used herein, any reference to an element using designations such as "first" and "second" does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0179] (13) In the first embodiment and each of the first to fifth modifications, to the extent that the terms "including," "comprising," and variations thereof are used in this specification or claims, these terms are intended to be inclusive, similar to the term "comprises." Furthermore, the term "or" used in this specification or claims is not intended to be an exclusive logical OR.

[0180] (14) Throughout this application, where articles have been added by translation, such as a, an and the in English, these articles include the plural unless the context clearly indicates otherwise.

[0181] (15) In this specification, the term "apparatus" may be replaced with other terms such as circuit, device, or unit.

[0182] (16) It is clear to those skilled in the art that the present invention is not limited to the embodiments described in this specification. The present invention can be implemented in modified and altered forms without departing from the spirit and scope of the present invention as defined by the claims. Therefore, the description in this specification is for illustrative purposes only and does not have any limiting meaning on the present invention. In addition, multiple aspects selected from the aspects exemplified in this specification may be combined.

[0183] D: Aspects understood from the above-mentioned embodiments or modifications The following aspects can be understood from at least one of the above-described embodiments or modified examples.

[0184] D1: First mode A household accounting management device according to a first aspect includes an acquisition unit and a reflection unit. The acquisition unit acquires first history data indicating a usage history of a first payment service and second history data indicating a usage history of a second payment service. When the first history data includes first payment data indicating a first payment that is a payment of an amount reduced by using points, and the second history data includes second payment data attributable to the first payment, the reflection unit reflects the first payment data in household accounting data indicating a household accounting book without reflecting the second payment data.

[0185] According to this embodiment, it is possible to limit problems that could arise in the accuracy of the household account book due to double-counting of payments made using points in the household account book.

[0186] D2: Second mode In the example of the first aspect (second aspect), the first payment is a payment in which the payment amount reduced by using the points is greater than 0. In this aspect as well, it is possible to limit the occurrence of problems with the accuracy of the household accounting data HD due to double counting.

[0187] D3: Third mode In an example of the first or second aspect (third aspect), when the first history data includes target payment data indicating a payment of a payment amount that has been made zero by using the points, the display control unit further includes a display control unit that causes a terminal device used by a user of the household account book to display an image that does not represent the payment indicated by the target payment data, but represents a payment in the usage history indicated by the first history data that is different from the payment indicated by the target payment data. According to this aspect, it is possible to restrict the display of payments that do not affect the balance of the household account book (payments of an amount that has been made zero by using points). Also, it is possible to omit processing for displaying payments that do not affect the balance of the household account book.

[0188] D4: Fourth mode In an example of the first or second aspect (fourth aspect), when the first history data includes target payment data indicating a payment of an amount that has been made zero by using the points, the display control unit further includes a display control unit that displays, on a terminal device used by a user of the household account book, an image representing the payment indicated by the target payment data and a payment in the usage history indicated by the first history data that is different from the payment indicated by the target payment data. According to this aspect, the user can confirm the payment that has been made zero by using the points by looking at the image displayed on the terminal device.

[0189] D5: Fifth mode In an example (fifth aspect) of any of the first to fourth aspects, the second payment data has first information identifying the first payment service as payee information, and has information indicating the same amount as the payment amount indicated by the first payment data as payment amount information.

[0190] The first information is, for example, information indicating the name, abbreviation, nickname, etc. of the first payment service. The first information may be information including a keyword identifying the first payment service. The first information may be information indicating the name, abbreviation, nickname, etc. of the business providing the first payment service. The first information may be a keyword identifying the business providing the first payment service.

[0191] According to this embodiment, the second payment data can be easily identified.

[0192] D6: Sixth mode In an example of the fifth aspect (sixth aspect), the first information includes a keyword that identifies the first payment service.

[0193] The keyword identifying the first payment service is, for example, the name, abbreviation, or nickname of the first payment service. The keyword identifying the first payment service may be the name, abbreviation, or nickname of the business entity providing the first payment service.

[0194] According to this embodiment, the second payment data can be easily identified by using a keyword that identifies the first payment service.

[0195] D7: Seventh mode In an example (seventh embodiment) of any of the first to sixth embodiments, the acquisition unit further acquires third history data indicating a history of payments using a third payment service. When the third history data indicates a third payment by second payment data having second information identifying the second payment service as payee information in a situation where the first history data indicates the first payment and the second history data indicates the second payment, the reflection unit reflects the first payment in the household account book data without reflecting the second payment and the third payment.

[0196] The second information is, for example, information indicating the name, abbreviation, nickname, etc. of the second payment service. The second information may be information including a keyword identifying the second payment service. The second information may be information indicating the name, abbreviation, nickname, etc. of the business providing the second payment service. The second information may be a keyword identifying the business providing the second payment service.

[0197] According to this embodiment, the third payment that overlaps with the second payment can be restricted from being recorded in the household account book.

[0198] D8: Eighth mode In an example of the seventh aspect (eighth aspect), the second information includes a keyword that identifies the second payment service.

[0199] The keyword identifying the second payment service is, for example, the name, abbreviation, or nickname of the second payment service. The keyword identifying the second payment service may be the name, abbreviation, or nickname of the business entity providing the second payment service.

[0200] According to this embodiment, it becomes possible to specify the third payment service by using a keyword that specifies the second payment service.

[0201] D9: 9th mode In an example of the first or second aspect (fourth aspect), the acquisition unit further acquires fourth history data indicating a history of payments made using a fourth payment service. When the fourth history data indicates a fourth payment by third payment data having third information identifying the third payment service as payee information in a situation where the first history data indicates the first payment, the second history data indicates the second payment, and the third history data indicates the third payment, the reflection unit reflects the first payment in the household account book data without reflecting the second payment, the third payment, and the fourth payment.

[0202] The third information is, for example, information indicating the name, abbreviation, nickname, etc. of the third payment service. The third information may be information including a keyword identifying the third payment service. The third information may be information indicating the name, abbreviation, nickname, etc. of a business providing the third payment service. The third information may be a keyword identifying a business providing the third payment service.

[0203] According to this embodiment, the fourth payment that overlaps with the third payment can be restricted from being recorded in the household account book.

[0204] D10: 10th mode In an example of the ninth aspect (tenth aspect), the third information includes a keyword that identifies the third payment service.

[0205] The keyword identifying the third payment service is, for example, the name, abbreviation, or nickname of the third payment service. The keyword identifying the third payment service may be the name, abbreviation, or nickname of the business entity providing the third payment service.

[0206] According to this embodiment, it becomes possible to specify the fourth payment service by using a keyword that specifies the third payment service. [Explanation of symbols]

[0207] 1...payment server, 2...communications company server, 3...card company server, 4...bank server, 5...terminal device, 51...input device, 52...display device, 53...communication device, 54...storage device, 55...processing device, 6...household accounting server, 61...communication device, 62...storage device, 63...processing device, 631...acquisition unit, 632...reflection unit, 633...display control unit, HS...management system.

Claims

1. an acquisition unit that acquires first history data indicating a usage history of the first payment service and second history data indicating a usage history of the second payment service; a reflection unit that reflects the first payment data in household account book data indicating a household account book without reflecting the second payment data when the first history data includes first payment data indicating a first payment, which is a payment of a payment amount reduced by using points, and the second history data includes second payment data resulting from the first payment; a display control unit that, when the first history data includes target payment data indicating a payment of a payment amount that has become zero through the use of the points, causes an image not to be displayed that is indicated by the target payment data, but to be displayed on a terminal device used by a user of the household account book, the image indicating a payment in the usage history indicated by the first history data that is different from the payment indicated by the target payment data; A household account book management device comprising:

2. an acquisition unit that acquires first history data indicating a usage history of the first payment service and second history data indicating a usage history of the second payment service; a reflection unit that reflects the first payment data in household account book data indicating a household account book without reflecting the second payment data when the first history data includes first payment data indicating a first payment, which is a payment of a payment amount reduced by using points, and the second history data includes second payment data resulting from the first payment; a display control unit that, when the first history data includes target payment data indicating a payment of an amount that has become zero through the use of the points, causes an image representing the payment indicated by the target payment data and a payment in the usage history indicated by the first history data that is different from the payment indicated by the target payment data to be displayed on a terminal device used by a user of the household account book; A household account book management device comprising:

3. an acquisition unit that acquires first history data indicating a usage history of the first payment service and second history data indicating a usage history of the second payment service; a reflection unit that reflects the first payment data in household account book data indicating a household account book without reflecting the second payment data when the first history data includes first payment data indicating a first payment that is a payment of a payment amount reduced by using points and the second history data includes second payment data resulting from the first payment; Including, The acquisition unit further acquires third history data indicating a usage history of a third payment service; When the third history data includes third payment data having second information identifying the second payment service as information of a payee in a situation where the first history data includes the first payment data and the second history data includes the second payment data, the reflecting unit reflects the first payment data in the household account book data without reflecting the second payment data and the third payment data. Household account management device.

4. the second information includes a keyword identifying the second payment service; The household account book management device according to claim 3.

5. The acquisition unit further acquires fourth history data indicating a usage history of a fourth payment service; the reflecting unit reflects the first payment data in the household account book data without reflecting the second payment data, the third payment data, and the fourth payment data in the household account book data when the fourth history data includes fourth payment data having third information identifying the third payment service as information of a payee, in a situation where the first history data includes the first payment data, the second history data includes the second payment data, and the third history data includes the third payment data, and the third history data includes the third payment data.

5. The household account book management device according to claim 3 or 4.

6. the third information includes a keyword identifying the third payment service; The household account book management device according to claim 5.

7. The first payment is a payment in which the payment amount reduced by using the points is greater than 0. The household account book management device according to any one of claims 1 to 6.

8. The second payment data is The first information for identifying the first payment service is included as information of a payee; The payment amount information includes information indicating an amount equal to the payment amount indicated by the first payment data. The household account book management device according to any one of claims 1 to 7.

9. The first information includes a keyword that identifies the first payment service. The household account book management device according to claim 8.

Images