Program, processing unit, and processing method

Abstract

To improve a convenience in a technique of receiving an advance payment of a use charge, and then registering a carry-over amount obtained by subtracting an accounting sum from a sum of the advance payment.SOLUTION: A program is configured to make a computer execute: processing of displaying a surplus balance of an amount paid to a first service; processing of displaying a screen demanding an additional payment when a surplus balance is not sufficient to a countervalue of a second service; and processing of displaying an outstanding balance of digital money used for the additional payment when the additional payment is conducted after the displaying the screen.SELECTED DRAWING: Figure 8

Description

Technical Field

[0004] , , , , , , , , , , , ,

[0005]

[0001] The present invention relates to an accounting device, an accounting method, and an accounting program.

Background Art

[0002] Technologies related to the present invention are disclosed in Patent Documents 1 and 2.

[0003] Patent Document 1 discloses a technology in which an advance payment amount is deducted from an IC card at the entrance of a parking lot, the advance payment amount is registered together with a vehicle ID (identifier), an IC card ID, and an entry time, only the vehicle ID is acquired by wireless communication at the exit of the parking lot, the parking fee is calculated, the difference obtained by subtracting the parking fee from the advance payment amount is registered as a deposit, and the deposit is refunded to the IC card at the entrance at the next use.

[0004] Patent Document 2 includes a measurement unit that determines an entry date and time based on a signal of a vehicle's entry into a warehouse and measures the parking time from the entry date and time, a reading unit that reads a vehicle number from a vehicle image, a recording unit that records the vehicle number, the vehicle image, and the entry date and time in association with each other, a panel unit that includes an operation unit for input operations and a display unit that displays the vehicle number and the vehicle image, a settlement unit for settling the parking fee, and a first control unit for performing settlement based on the vehicle number and a second control unit for performing settlement based on the entry date and time. The first control unit displays a plurality of images based on the input vehicle number, and the second control unit displays a plurality of images based on the input entry date and time, thereby providing a determination of whether the vehicle to be settled is valid.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Patent Document 2

Summary of the Invention

[0006] In some cases, the total amount charged is determined based on the services used, and the final amount is not fixed at the start of use. Examples include parking lots, rental offices, shared bicycles, and shared cars where the charge is determined by the usage time; charging services where the charge is determined by the amount of charge used; restaurants where the charge is determined by the order placed; amusement facilities such as bowling alleys where the charge is determined by the number of games played; and supermarkets, convenience stores, vending machines for beverages, and gas stations where the charge is determined by the items purchased. However, these examples are not limited to these.

[0007] In such cases, it is common practice to pay after the service has ended, once the total amount has been determined. However, some users prefer to pay at the start of service to avoid waiting in line for payment. Some kind of arrangement is necessary to allow payment at the start of service, before the total amount is determined.

[0008] The above problem can be solved by the "technology disclosed in Patent Document 1, which involves having users pay the fee in advance, registering the amount remaining after deducting the final fee from the advance payment as a deposit, and refunding it upon the next use." However, with the technology described in Patent Document 1, users cannot know the existence or amount of the deposit until they receive it back. Therefore, users cannot manage their deposits, resulting in poor convenience. Patent Document 2 does not describe or suggest the technical concept or problems related to advance payment of usage fees.

[0009] The present invention aims to improve convenience in a technology that allows users to pay usage fees in advance and registers the carry-over amount obtained by subtracting the accounting amount from the advance payment amount. [Means for solving the problem]

[0010] According to the present invention, A means of obtaining the advance payment amount that the user pays before starting to use the service, A means for obtaining the accounting amount corresponding to the user's usage record of the service, A means for displaying on a screen the carry-over amount that will be used preferentially when the user makes a payment, based on the aforementioned prepaid amount and the aforementioned accounting amount, An accounting device having the following is provided.

[0011] Furthermore, according to the present invention, One or more computers, The process of obtaining the prepayment amount that the user pays before starting to use the service, A process to obtain the accounting amount corresponding to the user's usage of the service, A process to display on the screen the carry-over amount that will be used preferentially when the user makes a payment, based on the aforementioned prepayment amount and the aforementioned accounting amount, An accounting method is provided to perform this task.

[0012] Furthermore, according to the present invention, On one or more computers, The process of obtaining the prepayment amount that the user pays before starting to use the service, A process to obtain the accounting amount corresponding to the user's usage of the service, A process to display on the screen the carry-over amount that will be used preferentially when the user makes a payment, based on the aforementioned prepayment amount and the aforementioned accounting amount, An accounting program is provided to perform this task. [Effects of the Invention]

[0013] According to the present invention, the convenience of a technology that allows users to pay usage fees in advance and registers the carry-over amount obtained by subtracting the accounting amount from the advance payment amount is improved. [Brief explanation of the drawing]

[0014] [Figure 1] This is an example of a functional block diagram of the accounting device of this embodiment. [Figure 2]This is a diagram showing an example of the hardware configuration of the accounting device according to the present embodiment. [Figure 3] This is a flowchart showing an example of the processing flow realized by the accounting device according to the present embodiment. [Figure 4] This is a flowchart showing an example of the processing flow realized by the accounting device according to the present embodiment. [Figure 5] This is a flowchart showing an example of the processing flow realized by the accounting device according to the present embodiment. [Figure 6] This is an example of a screen realized by the accounting device according to the present embodiment. [Figure 7] This is an example of a screen realized by the accounting device according to the present embodiment. [Figure 8] This is an example of a screen realized by the accounting device according to the present embodiment. [Figure 9] This is a diagram schematically showing an example of the information processed by the accounting device according to the present embodiment. [Figure 10] This is a diagram schematically showing an example of the information processed by the accounting device according to the present embodiment. [Figure 11] This is a diagram schematically showing an example of the information processed by the accounting device according to the present embodiment. [Figure 12] This is an example of a functional block diagram of the accounting device according to the present embodiment. [Figure 13] This is an example of a screen realized by the accounting device according to the present embodiment.

Mode for Carrying Out the Invention

[0015] <First Embodiment> First, an overview of the accounting device of this embodiment will be described. The accounting device of this embodiment is suitable for use in stores and facilities where the accounting amount is determined according to the content of use, and the accounting amount is not fixed at the start of use. Examples of such stores and facilities include, but are not limited to, parking lots and rental offices where the accounting amount is determined according to the time of use, shared bicycles, shared cars, charging services where the accounting amount is determined according to the amount of charge, restaurants where the accounting amount is determined according to the content of the order, amusement facilities such as bowling where the accounting amount is determined according to the number of games played, etc., supermarkets and convenience stores where the accounting amount is determined according to the content of the purchase, vending machines for beverages, gas stations, etc.

[0016] The accounting device of this embodiment performs a prepayment process for a predetermined amount at the start of use (e.g., when using a parking lot) and registers the prepayment amount linked to that user. Then, at the end of use (e.g., when using a parking lot), the accounting device of this embodiment compares the prepayment amount with the finalized accounting amount. If the prepayment amount exceeds the accounting amount, it registers the excess amount as a carryover amount linked to that user and outputs the carryover amount in a way that is visible to the user (e.g., displayed on a screen). With this accounting device of this embodiment, the user can understand the existence and amount of the deposit by visually checking the outputted carryover amount.

[0017] Next, the configuration of the accounting device of this embodiment will be described in detail. Figure 1 shows an example of a functional block diagram of the accounting device 100. As shown in the figure, the accounting device 100 includes a reader / writer unit 11, an input receiving unit 12, an input information acquisition unit 13, a registration unit 14, a storage unit 15, a prepayment processing execution unit 16, a confirmation unit 17, an accounting unit 18, and an output unit 19.

[0018] The accounting device 100 may consist of a single device that is physically and / or logically integrated, or it may consist of multiple devices that are physically and / or logically separate. For example, the accounting device 100 may be realized by a terminal installed in a store or facility and operated by a user, and a server that communicates with the terminal. Alternatively, the accounting device 100 may be realized by a single terminal installed in a store or facility and operated by a user. Hereafter, the explanation will be based on the premise that the accounting device 100 is realized by a single terminal installed in a store or facility and operated by a user.

[0019] Each of the functional units of the accounting device 100 is realized by any combination of hardware and software, centered around the CPU (Central Processing Unit) of any computer, memory, programs loaded into memory, a storage unit such as a hard disk that stores those programs (which can store programs pre-installed at the time of shipment, as well as programs downloaded from storage media such as CDs (Compact Discs) or from servers on the Internet), and a network connection interface. It will be understood by those skilled in the art that there are various modifications to the implementation method and the device.

[0020] Figure 2 is a block diagram illustrating the hardware configuration of the accounting device 100. As shown in Figure 2, the accounting device 100 includes a processor 1A, memory 2A, input / output interface 3A, peripheral circuitry 4A, and bus 5A. Peripheral circuitry 4A includes various modules. Note that peripheral circuitry 4A is optional. If the accounting device 100 is composed of multiple physically and / or logically separated devices, each of the multiple devices may have the above hardware configuration.

[0021] Bus 5A is a data transmission path for the processor 1A, memory 2A, peripheral circuits 4A, and input / output interface 3A to send and receive data to and from each other. Processor 1A is a processing unit such as a CPU or GPU (Graphics Processing Unit). Memory 2A is a memory such as RAM (Random Access Memory) or ROM (Read Only Memory). Input / output interface 3A includes interfaces for acquiring information from input devices, external devices, external servers, external sensors, cameras, etc., and interfaces for outputting information to output devices, external devices, external servers, etc. Input devices include, for example, keyboards, mice, microphones, touch panels, physical buttons, cameras, etc. Output devices include, for example, displays, speakers, printers, mailers, etc. Processor 1A can issue commands to each module and perform calculations based on the results of those calculations.

[0022] Next, let's return to Figure 1 and explain the configuration of each functional part.

[0023] The reader / writer unit 11 communicates wirelessly with the electronic money information storage device to acquire and update the information stored in the electronic money information storage device. The electronic money information storage device is a portable device having the function of storing electronic money information and the function of wireless communication with a short range of range, and examples include, but are not limited to, IC cards, IC tags, smartphones, mobile phones, tablet terminals, smartwatches, etc. In the following explanation, the case in which the electronic money information storage device is an IC card will be used as an example.

[0024] The input receiving unit 12 receives various types of information from the user via an input device. Examples of input devices include, but are not limited to, touch panels, physical buttons, microphones, keyboards, and mice.

[0025] The input information acquisition unit 13 acquires various types of information input from the reader / writer unit 11 and the input reception unit 12.

[0026] The registration unit 14 manages the information stored in the storage unit 15. This management includes updating, deleting, and registering new information.

[0027] The memory unit 15 stores various types of information.

[0028] The prepayment processing execution unit 16 performs the prepayment processing.

[0029] The confirmation unit 17 determines the total amount due. For example, the confirmation unit 17 determines the total amount due based on usage time, charge level, order details, number of games played, purchase details, etc. Note that this is merely an example, and the confirmation unit 17 may determine the total amount due based on other information.

[0030] The accounting department 18 performs accounting processing based on the accounting amount confirmed by the finalization department 17 and the prepayment amount in the prepayment process.

[0031] The output unit 19 outputs various information via any output device such as a display, speaker, warning lamp, or projection device.

[0032] Next, an example of the processing flow realized by the above-mentioned functional unit will be explained using the flowcharts in Figures 3 to 5 and the screen examples in Figures 6 to 8. Here, the explanation will take the case where the accounting device 100 is used in a parking lot as an example. The processing flow will then be explained by dividing it into "processing upon entry for first-time use," "processing upon entry for subsequent uses (using the same IC card as the previous time)," "processing upon entry for subsequent uses (using a different IC card than the previous time)," and "processing upon exit."

[0033] "Processing upon entry for first-time users" After parking their vehicle at any location in the parking lot, the user operates the payment device 100, which is installed at any location in the parking lot. The payment device 100 displays the screen shown in Figure 6(A) and is in a waiting state. The user holds an IC card, which stores the electronic money information to be used for payment, over the reader / writer of the payment device 100. The input information acquisition unit 13 then acquires the card identification information stored on the IC card via the reader / writer unit 11 (S101 in Figure 3). The card identification information is an example of device identification information stored in the electronic money information storage device. The card identification information may also be a unique number for the IC card that is recorded on the IC chip during the manufacturing of the IC chip and cannot be rewritten. In addition, the card identification information may also be user identification information for the electronic money service related to the electronic money information stored on the IC card. The user identification information for the electronic money service is information used to identify users of the electronic money service to each other.

[0034] Next, the registration unit 14 determines whether the card identification information obtained in S101 is already registered in the user information (S102). The user information is information about the user who uses the parking lot, and is stored in the storage unit 15 and at least one of the storage devices of the server configured to communicate with the accounting device 100. Figure 9 schematically shows an example of user information. The user information shown links the card identification information, telephone number, and rollover amount to each other. Note that the user information shown is merely an example, and may also include other information such as gender and date of birth.

[0035] For first-time users, the user's card identification information is not registered in the user information. Therefore, S102 will be No, and the process will proceed to S112.

[0036] Next, the accounting device 100 displays a screen prompting the user to register their mobile phone number, as shown in Figures 6(B) and 6(C). Note that registering a mobile phone number is optional and not mandatory.

[0037] If the mobile phone number input is not accepted (No. in S112), the registration unit 14 newly registers the card identification information obtained in S101 into the user information as shown in Figure 9 (S119). Then, the process proceeds to S104.

[0038] On the other hand, if a mobile phone number is entered (Yes in S112), the input information acquisition unit 13 obtains the entered phone number by linking it to the card identification information obtained in S101. Subsequently, authentication processing using the mobile phone is performed (S113). In the authentication processing, a password is issued, the password is sent via SMS to the accepted mobile phone number, the input of the sent password is accepted, and the issued password is compared with the entered password. These processes may be performed by the registration unit 14, by a server configured to communicate with the accounting device 100, or by the registration unit 14 performing some of the processes and the server performing other parts. In addition, if the SMS is not received, authentication may be performed by telephone. During these processes, the accounting device 100 displays screens as shown in Figures 6(D) and 6(E).

[0039] If authentication fails (No. in S114), the registration unit 14 performs error processing (S118). For example, it displays information indicating that authentication failed and shows a screen like the one shown in Figure 6(C) prompting the user to re-enter the phone number. Then, it returns to S112 and repeats the process.

[0040] On the other hand, if authentication is successful (Yes in S114), the registration unit 14 checks whether the telephone number received in S112 is registered in the user information as shown in Figure 9 (S115).

[0041] For first-time users, the user's phone number is not registered in the user information. Therefore, S115 is No, and the process proceeds to S117. In S117, the registration unit 14 links the card identification information obtained in S101 with the phone number received in S112 and registers it as new user information as shown in Figure 9. The initial value of the carry-over amount is "0". Then, the accounting device 100 displays a screen as shown in Figure 6(F).

[0042] The process described above completes the initial registration of the information necessary to use the parking lot. In the parking lot's accounting service, the card identification information will be used to identify users of the service.

[0043] Subsequently, in S104, the registration unit 14 determines whether the card identification information acquired in S101 has already been registered in the usage status information. The usage status information is information indicating the usage status of the parking lot, and is stored in the storage unit 15 and at least one of the storage devices of the server configured to communicate with the accounting device 100. Figure 10 schematically shows an example of the usage status information. The usage status information shown is linked to the card identification information, vehicle number, prepaid amount, entry date and time, remaining time, overtime flag, and image ID. The usage status information may include other information, or it may not include some of the information shown as an example.

[0044] In the case of processing upon receiving a card, the card identification information is not registered in the usage status information. Therefore, S104 will be No, and the process will proceed to the receiving process of S106.

[0045] Next, we will explain the flow of the receiving process in S106 using the flowchart in Figure 4.

[0046] The registration unit 14 registers the card identification information obtained in S101 in Figure 3 into the usage status information as shown in Figure 10 (S201).

[0047] Next, the accounting device 100 displays a screen as shown in Figure 8(A) and prompts the user to enter the vehicle number. The input information acquisition unit 13 acquires the entered vehicle number via the input reception unit 12 (S202). Then, the registration unit 14 registers the acquired vehicle number in the usage information as shown in Figure 10, linking it to the card identification information registered in S201 (S202).

[0048] Next, the accounting device 100 displays a screen as shown in Figure 8(B) and prompts the user to specify their vehicle on the screen. For example, the accounting device 100 analyzes the image, identifies the vehicles present in the image, and displays a frame surrounding the identified vehicles. The accounting device 100 then accepts input to specify one of the vehicles within the displayed frame. The accounting device 100 may also display only the frames surrounding the identified vehicles that have not yet been specified.

[0049] The input information acquisition unit 13 acquires information specifying one of the vehicles in the image via the input reception unit 12 (S203). Then, the registration unit 14 registers information identifying the vehicle specified in the image (image ID) in the usage status information as shown in Figure 10, linking it to the card identification information registered in S201 (S203). The image ID may be, for example, the identification information of the frame surrounding each vehicle identified in the image.

[0050] Next, the accounting device 100 displays a screen as shown in Figure 8(C) and prompts the user to input the prepayment amount. The input information acquisition unit 13 acquires the entered prepayment amount via the input reception unit 12 (S203). Then, the registration unit 14 registers the acquired prepayment amount in the usage information as shown in Figure 10, linking it to the card identification information registered in S201 (S204).

[0051] Next, the prepayment processing execution unit 16 obtains the carryover amount linked to the card identification information registered in S201 from the user information as shown in Figure 9 (S205).

[0052] Then, the prepayment processing execution unit 16 executes the prepayment processing. Specifically, if the prepayment amount specified in S204 is greater than the carry-over amount obtained in S205 (Yes in S206), the prepayment processing execution unit 16 executes prepayment processing (accounting processing) that subtracts a predetermined amount from the electronic money balance based on the electronic money information stored in the IC card (S208).

[0053] For example, the prepayment processing execution unit 16 calculates a predetermined amount (=prepayment amount - carry-over amount) based on the prepayment amount specified in S204 and the carry-over amount obtained in S205. Then, as shown in Figure 8(D), the accounting device 100 displays the calculated predetermined amount ("payment amount" in the figure) and a screen prompting the user to hold the IC card over the reader / writer of the accounting device 100. When the IC card is held over the reader / writer of the accounting device 100 and communication between the accounting device 100 and the IC card is established, the prepayment processing execution unit 16 updates the electronic money information stored on the IC card via the reader / writer unit 11 and subtracts the predetermined amount from the electronic money balance.

[0054] Then, the registration unit 14 updates the carryover amount linked to the card identification information registered in S201 in the user information as shown in Figure 9 (S208). Specifically, it subtracts the amount of the carryover that was used to pay the prepaid amount. Note that if the carryover amount was not used to pay the prepaid amount, updating the carryover amount is unnecessary.

[0055] On the other hand, if the prepayment amount specified in S204 is less than or equal to the carry-over amount obtained in S205 (No. in S206), the prepayment processing execution unit 16 performs prepayment processing for the prepayment amount based on the carry-over amount (S208). Specifically, the prepayment processing execution unit 16 updates the carry-over amount linked to the card identification information registered in S201 in the user information as shown in Figure 9 via the registration unit 14 (S208). Specifically, it subtracts the amount of the carry-over amount used to pay the prepayment amount. This completes the processing at the time of receipt. The accounting device 100 displays a screen as shown in Figure 8(E), for example.

[0056] Note that the processing order of S202 to S205 is not limited to the order shown in Figure 4. Also, although not shown, the registration unit 14 registers the receiving date and time at any time, linked to the card identification information registered in S201. The receiving date and time is the time at any time after the card identification information input is received in S101.

[0057] "Processing upon entry for subsequent visits (using the same IC card as the previous visit)" After parking their vehicle at any location in the parking lot, the user operates the payment device 100, which is located at any location in the parking lot. The payment device 100 displays the screen shown in Figure 6(A) and is in a waiting state. The user holds an IC card containing the electronic money information to be used for payment over the reader / writer of the payment device 100. Here, it is assumed that the user holds the same IC card over the reader / writer as the one used the previous time they used the parking lot. The input information acquisition unit 13 then acquires the card identification information stored on the IC card via the reader / writer unit 11 (S101 in Figure 3).

[0058] Next, the registration unit 14 determines whether the card identification information obtained in S101 is already registered in the user information (S102). If it is the second or subsequent use and the same IC card is used as the previous time, the user's card identification information is already registered in the user information. Therefore, S102 is Yes, and the process proceeds to S103.

[0059] Next, the registration unit 14 determines whether a telephone number is registered in the user information shown in Figure 9, linked to the card identification information obtained in S101 (S103). If it is registered (Yes in S103), the process proceeds to S104.

[0060] On the other hand, if the phone number is not registered (No. S103), the accounting device 100 displays a screen prompting the user to register their mobile phone number, as shown in Figure 6(G). Note that registering a mobile phone number is optional and not required.

[0061] If the mobile phone number is not entered (No in S107), the process proceeds to S104. On the other hand, if the mobile phone number is entered (Yes in S107), the input information acquisition unit 13 obtains the entered phone number by linking it to the card identification information obtained in S101. After that, authentication processing using the mobile phone is performed (S108). The content of the authentication processing is the same as the authentication processing in S113 described in "Processing upon entry for first-time users".

[0062] If authentication fails (No. in S109), the registration unit 14 performs error processing (S111). For example, it displays information indicating that authentication failed on the screen, and also displays a screen like the one shown in Figure 6(C) to prompt the user to re-enter the phone number. Then, it returns to S107 and repeats the process.

[0063] On the other hand, if authentication is successful (Yes in S109), the registration unit 14 registers the entered telephone number in the user information shown in Figure 9, linked to the card identification information obtained in S101 (S110). Then, it proceeds to S104.

[0064] In S104, the registration unit 14 determines whether the card identification information obtained in S101 is already registered in the usage status information. In the case of processing upon receipt of a card, the card identification information is not registered in the usage status information. Therefore, S104 is No, and the process proceeds to the receipt processing in S106. The contents of the receipt processing in S106 are the same as those described in "Processing upon receipt for first-time use".

[0065] "Processing upon entry for subsequent visits (using a different IC card than the previous visit)" This example assumes a scenario where a different IC card (electronic money) is used than the one used during the previous parking session, due to any reason such as loss, expiration, not possessing the card, or insufficient balance. As mentioned above, in the parking lot's accounting service, card identification information is used to identify users of the service. Therefore, if a different IC card is used than the one used during the previous parking session, the carried-over balance registered and linked to the card identification information of the IC card used during the previous parking session will not be available. However, as will become clear from the explanation below, users who have registered their mobile phone number can still use their carried-over balance even in such cases.

[0066] After parking their vehicle at any location in the parking lot, the user operates the payment device 100, which is located at any location in the parking lot. The payment device 100 displays the screen shown in Figure 6(A) and is in a waiting state. The user holds an IC card containing the electronic money information to be used for payment over the reader / writer of the payment device 100. Here, it is assumed that the user holds a different IC card over the reader / writer than the one used the previous time they used the parking lot. The input information acquisition unit 13 then acquires the card identification information stored on the IC card via the reader / writer unit 11 (S101 in Figure 3).

[0067] Next, the registration unit 14 determines whether the card identification information obtained in S101 is already registered in the user information (S102). If the user is using a different IC card than the one used the previous time for parking, the user's card identification information is not registered in the user information. Therefore, S102 is No, and the process proceeds to S112.

[0068] Next, the accounting device 100 displays a screen prompting the user to register their mobile phone number, as shown in Figures 6(B) and 6(C). Note that registering a mobile phone number is optional and not mandatory.

[0069] If the mobile phone number input is not accepted (No. in S112), the registration unit 14 registers the card identification information obtained in S101 into the user information as shown in Figure 9 (S119). Then, the process proceeds to S104. In this case, the card identification information of the IC card used in the current use will be registered separately from the card identification information of the IC card used in the previous use. The carried-over amount linked to the card identification information of the IC card used in the previous use will then become unavailable.

[0070] On the other hand, if a mobile phone number is entered (Yes in S112), the input information acquisition unit 13 obtains the entered phone number by linking it to the card identification information obtained in S101. Subsequently, authentication processing using the mobile phone is performed (S113). The content of the authentication processing is the same as that described in "Processing upon entry for first-time users".

[0071] If authentication fails (No. in S114), the registration unit 14 performs error processing (S118). For example, it displays information indicating that authentication failed and shows a screen like the one shown in Figure 6(C) prompting the user to re-enter the phone number. Then, it returns to S112 and repeats the process.

[0072] On the other hand, if authentication is successful (Yes in S114), the registration unit 14 checks whether the telephone number received in S112 is registered in the user information as shown in Figure 9 (S115).

[0073] For subsequent uses, if a different IC card is used than the previous time, and the user's phone number has already been registered during previous parking use, the user's phone number is registered in the user information. Therefore, S115 is Yes, and the process proceeds to S116. In S116, the registration unit 14 updates the card identification information registered in the user information shown in Figure 9, which is linked to the phone number obtained in S112, with the card identification information obtained in S101. As a result, for example, the user information shown in Figure 9 is updated as shown in Figure 11. Comparing the user information in Figure 9 and Figure 11, it can be seen that the card identification information linked to the phone number "090-xxxx-xxxx" has been updated from "C1131923" to "C0037279".

[0074] Note that even if a different IC card is used for the second or subsequent use, if the user did not register their phone number during previous parking use, that user's phone number will not be registered in the user information. Therefore, S115 will be No, and the process will proceed to S117. In S117, the registration unit 14 links the card identification information obtained in S101 with the phone number received in S112 and registers it as new user information as shown in Figure 9. Note that the initial value of the carryover amount is "0". In this case, the card identification information of the IC card used in the current use will be registered separately from the card identification information of the IC card used in the previous use. The carryover amount linked to the card identification information of the IC card used in the previous use will then become unavailable.

[0075] In S104, the registration unit 14 determines whether the card identification information obtained in S101 is already registered in the usage status information. In the case of processing upon receipt of a card, the card identification information is not registered in the usage status information. Therefore, S104 is No, and the process proceeds to the receipt processing in S106. The contents of the receipt processing in S106 are the same as those described in "Processing upon receipt for first-time use".

[0076] In this example, the user held the IC card to be used over the reader / writer of the accounting device 100 from the screen shown in Figure 6(A). However, the process may also proceed as follows: First, the user touches "How to Use" from the screen shown in Figure 7(A) (the same screen as shown in Figure 6(A)) to transition to the screen shown in Figure 7(B), then touches "Registered Card Users" to transition to the screen shown in Figure 7(G). Then, on that screen, touches "Lost Card" to transition to the screen shown in Figure 7(H), and from there, the process proceeds in the same order as in the example described above, as shown in Figures 7(D), 7(E), 7(F), and 7(I).

[0077] "Processing upon shipment" When exiting the parking lot, the user operates the payment device 100, which is installed at any location in the parking lot. The payment device 100 displays the screen shown in Figure 6(A) and is in a waiting state for operation. The user holds the IC card that they held over the payment device 100 when entering the parking lot over the reader / writer of the payment device 100. The input information acquisition unit 13 then acquires the card identification information stored on the IC card via the reader / writer unit 11 (S101 in Figure 3).

[0078] Next, the registration unit 14 determines whether the card identification information obtained in S101 is already registered in the user information (S102). The card identification information of the IC card is registered in the user information when it is brought into storage. Therefore, S102 is Yes, and the process proceeds to S103.

[0079] Next, the registration unit 14 determines whether a telephone number is registered in the user information shown in Figure 9, linked to the card identification information obtained in S101 (S103). If it is registered (Yes in S103), the process proceeds to S104.

[0080] On the other hand, if the phone number is not registered (No. S103), the accounting device 100 displays a screen prompting the user to register their mobile phone number, as shown in Figure 6(G). Note that registering a mobile phone number is optional and not required.

[0081] If the mobile phone number is not entered (No in S107), the process proceeds to S104. On the other hand, if the mobile phone number is entered (Yes in S107), the input information acquisition unit 13 obtains the entered phone number by linking it to the card identification information obtained in S101. After that, authentication processing using the mobile phone is performed (S108). The content of the authentication processing is the same as the authentication processing in S113 described in "Processing upon entry for first-time users".

[0082] If authentication fails (No. in S109), the registration unit 14 performs error processing (S111). For example, it displays information indicating that authentication failed on the screen, and also displays a screen like the one shown in Figure 6(C) to prompt the user to re-enter the phone number. Then, it returns to S107 and repeats the process.

[0083] On the other hand, if authentication is successful (Yes in S109), the registration unit 14 registers the phone number entered in the user information, linked to the card identification information obtained in S101, as shown in Figure 9 (S110). Then, the process proceeds to S104.

[0084] In S104, the registration unit 14 determines whether the card identification information obtained in S101 is already registered in the usage status information. In the case of a checkout process, the card identification information is already registered in the usage status information. Therefore, S104 is Yes, and the process proceeds to the checkout process in S105.

[0085] Next, we will explain the outbound processing flow of S105 using the flowchart in Figure 5.

[0086] The confirmation unit 17 retrieves the deposit date and time registered in the usage information shown in Figure 10, which is linked to the card identification information acquired in S101 in Figure 3, and calculates the accounting amount based on the deposit date and time and the withdrawal date and time (S301). The withdrawal date and time is the time when the card identification information was received in S101 at the time of withdrawal, or at any time thereafter.

[0087] When the prepaid amount (A) exceeds the accounting amount (B) (i.e., "A > B" in S302), the accounting department 18 calculates the carry-over amount for the excess (S303). Then, the accounting department 18 causes the registration department 14 to register (update) the calculated carry-over amount in association with the card identification information obtained in S101 in the user information as shown in FIG. 9 (S304). Also, the accounting department 18 causes the calculated carry-over amount to be output in a user-visible manner (S304). The accounting department 18 may display the carry-over amount on the display of the accounting device 100. For example, the accounting device 100 may display a screen as shown in (F) of FIG. 8. Then, the accounting department 18 causes the registration department 14 to delete the card identification information obtained in S101 from the user information as shown in FIG. 10 (S305).

[0088] In addition, when the prepaid amount (A) is equal to the accounting amount (B) (i.e., "A = B" in S302), the accounting department 18 causes the registration department 14 to delete the card identification information obtained in S101 from the user information as shown in FIG. 10 (S305).

[0089] Also, when the prepaid amount (A) is less than the accounting amount (B) (i.e., "A < B" in S302), the accounting department 18 executes an accounting process to receive payment for the shortfall (S306). For example, the accounting department 18 calculates the shortfall and outputs information requesting the user to pay that amount. For example, the accounting device 100 displays a screen as shown in (G) of FIG. 8, notifies the shortfall amount (the "payment amount" in the figure), and displays a screen prompting the user to hold the IC card over the reader / writer of the accounting device 100. In response, when the IC card is held over the reader / writer of the accounting device 100 and the accounting device 100 and the IC card are in a communicable state, the accounting department 18 updates the electronic money information stored in the IC card via the reader / writer unit 11 and subtracts a predetermined amount from the remaining balance of the electronic money. Then, the accounting department 18 causes the registration department 14 to delete the card identification information obtained in S101 from the user information as shown in FIG. 10 (S305).

[0090] According to the accounting device 100 described above, the usage fee can be paid in advance, and the carry-over amount, which is the advance payment minus the accounting amount, can be registered. Furthermore, the accounting device 100 can notify the user of the registered carry-over amount. In addition, the accounting device 100 allows the carry-over amount to be used for payment on the next use. Moreover, according to the accounting device 100, even if a different IC card is used than the one used last time, if the phone number is registered, the user information can be updated using that phone number (Figure 9 → Figure 11), and the carry-over amount generated when using the other IC card can be used. In addition, by taking pictures of the parking lot, identifying each user's vehicle, and managing the images, it is possible to verify fraudulent use, and these images can also be used as evidence of fraudulent use. In this way, the accounting device 100 provides a high level of convenience.

[0091] Here, a modified version of this embodiment will be described. Instead of the mobile phone number (user identification information) used in the example described above, other information such as name, nickname, driver's license number, or My Number may be used. In this case, authentication using the mobile phone used in the example described above will not be possible, but authentication may be performed by other means, or authentication may be eliminated.

[0092] Furthermore, although the above example requested the input and registration of the vehicle number, this process is not required. Also, although the above example requested the selection and registration of the vehicle within the image, this process is not required.

[0093] Furthermore, the accounting device 100 may be equipped with a camera to photograph the customer operating the accounting device 100. The accounting device 100 may also register the customer's facial information (facial image or features generated from the facial image) in the user information (see Figure 9), linked to the card identification information. For example, the accounting device 100 may accept the capture and registration of a facial image before or after the registration of the telephone number in the processing flow described above, or at other timings.

[0094] Furthermore, the accounting device 100 may take a picture of the customer's face and perform facial recognition before the customer holds the IC card over the reader / writer of the accounting device 100, as shown in Figure 6(A), etc. For example, the accounting device 100 may detect when a person is standing in front of it using a motion sensor or the like and take a picture automatically in response to the detection, or it may take a picture in response to a manual operation by the customer.

[0095] Furthermore, if facial recognition is successful, the accounting device 100 may execute the processes from S101 onwards in Figure 3 without requiring the customer to hold their IC card over the reader / writer of the accounting device 100. In this case, in S101, the accounting device 100 reads the card identification information of the authenticated customer from the user information (see Figure 9) and executes the processes from S102 onwards based on that information.

[0096] On the other hand, if facial recognition fails, the accounting device 100 displays a screen as shown in Figure 6(A) and accepts the operation to hold the IC card over the reader / writer of the accounting device 100 (S101 in Figure 3).

[0097] <Second Embodiment> The accounting device 100 of this embodiment differs from the first embodiment in that it has a function to present various functions in response to operations from the administrator (the party providing services such as parking).

[0098] Figure 12 shows an example of a functional block diagram of the accounting device 100. As shown in the figure, the accounting device 100 includes a reader / writer unit 11, an input reception unit 12, an input information acquisition unit 13, a registration unit 14, a storage unit 15, a prepayment processing execution unit 16, a confirmation unit 17, an accounting unit 18, an output unit 19, an administrator screen control unit 20, and an authentication unit 21.

[0099] The configuration of the reader / writer unit 11, input reception unit 12, input information acquisition unit 13, registration unit 14, storage unit 15, prepayment processing execution unit 16, confirmation unit 17, and accounting unit 18 is the same as in the first embodiment.

[0100] The authentication unit 21 performs authentication processing based on administrator identification information and password. If authentication is successful, the administrator screen control unit 20 outputs the administrator screen via the output unit 19.

[0101] Next, using the example screen in Figure 13, we will explain an example of the processing flow realized by the above-mentioned functional unit. Here, we will explain using the case where the accounting device 100 is used in a parking lot as an example.

[0102] The accounting device 100 displays the screen shown in Figure 13(A) and is in a waiting state for operation. When the administrator touches "Password here," the screen transitions to Figures 13(B) and 13(C). The input information acquisition unit 13 acquires the administrator identification information and password entered from these screens via the input reception unit 12. The authentication unit 21 then performs authentication processing based on the administrator identification information and password. Authentication is achieved by comparing the acquired administrator identification information and password combination with a pre-registered combination of administrator identification information and password for a legitimate authorized user. The comparison may be performed by the authentication unit 21 or by a server configured to communicate with the accounting device 100. The combination of administrator identification information and password for a legitimate authorized user is stored in the storage unit of the entity performing the comparison. When the server performs the comparison, the authentication unit 21 sends the acquired administrator identification information and password combination to the server and performs authentication processing to obtain the comparison result from the server.

[0103] If authentication fails, the authentication unit 21 performs error processing. For example, the authentication unit 21 displays information indicating that authentication failed on the screen via the output unit 19, and also displays a screen like the ones shown in Figures 13(B) and 13(C) again, and accepts re-entry of the administrator identification information and password.

[0104] On the other hand, if authentication is successful, the administrator screen control unit 20 outputs the administrator screen via the output unit 19. The accounting device 100 displays a screen such as those shown in Figures 13(D), 13(E), and 13(F).

[0105] As shown in Figure 13(D), the administrator screen control unit 20 may display information on the administrator screen indicating whether or not receipts need to be replenished.

[0106] Furthermore, the administrator screen control unit 20 may display information indicating the parking lot usage status on the administrator screen, as shown in Figure 13(F). This screen is created based on the usage status information shown in Figure 10. The "remaining time" shown indicates the remaining time from the time of entry until the time equal to the prepaid amount has elapsed. If the time has already elapsed, the elapsed time is indicated by a negative number. The overdue flag indicates whether or not the time equal to the prepaid amount has elapsed from the time of entry.

[0107] Furthermore, information indicating the usage status of the parking lot (see Figure 13(F)) may be transmitted to the administrator's terminal by any wired and / or wireless communication means. For example, the administrator's terminal and the accounting device 100 may communicate using short-range wireless communication. Alternatively, the administrator's terminal and the accounting device 100 may be connected by a wired connection. In addition, if an email address is entered into the accounting device 100, information indicating the usage status of the parking lot may be sent to that email address.

[0108] Furthermore, as shown in Figure 13(E), the administrator screen control unit 20 may display a settings screen on the administrator screen that allows for the modification of various settings. For example, a setting permission level may be registered in association with each administrator's identification information, and based on this registration, the system may control the content that each administrator can configure on the settings screen displayed when they log in.

[0109] The other components of the accounting device 100 are the same as those in the first embodiment.

[0110] As described above, the accounting device 100 of this embodiment can achieve the same effects and advantages as the first embodiment. Furthermore, the accounting device 100 of this embodiment can not only accept user operations but also operations from administrators and output information to administrators. Since it can accept operations from both users and administrators with a single device, a high level of convenience is achieved.

[0111] Here, a modified version of this embodiment will be described. In the example described above, authentication was performed using administrator identification information and a password, but this may be replaced with biometric authentication using biometric information such as facial images, fingerprints, voiceprints, or iris scans.

[0112] Here, we will describe some modifications applicable to all embodiments. As described above, the accounting device 100 of this embodiment can be used in a variety of situations, such as parking lots, rental offices, shared bicycles, shared cars, charging services, restaurants, amusement facilities such as bowling alleys, supermarkets, convenience stores, vending machines, and gas stations. User information (see Figure 9) may be managed separately for each service provider, or a single set of user information may be managed collectively for multiple service providers. If a single set of user information is managed collectively for multiple service providers, the user information referenced by the accounting device 100 when accounting for a parking lot will be the same as the user information referenced by the accounting device 100 when accounting for a rental office. In this case, for example, the amount carried over from the use of a parking lot can be used when using other services such as rental offices. Also, if card identification information and telephone number are registered when using a parking lot, registration work will not be required when using other services such as rental offices.

[0113] Furthermore, the carryover amount may be used at stores and facilities other than those where the total amount is determined based on usage and the total amount is not fixed at the start of use. For example, vending machines are one example, but the system is not limited to these. In this case, when paying a predetermined amount, the payment device reads the information of the IC card linked to the carryover amount in the user information (see Figure 9). The payment device then refers to the user information and checks whether a carryover amount exists. If a carryover amount exists, the payment device prioritizes using the carryover amount for payment.

[0114] Furthermore, although the above explanation uses the case where the electronic money information storage device is an IC card as an example, the electronic money information storage device may be other devices such as IC tags, smartphones, mobile phones, tablet terminals, or smartwatches. In this case, the device identification information may be information that identifies each individual device, or it may be user identification information for the electronic money service stored in each device.

[0115] In this specification, "acquisition" includes at least one of the following: "active acquisition" based on user input or program instructions, such as "the device going to retrieve data stored in another device or storage medium," for example, requesting or querying another device to receive data, accessing and reading data from another device or storage medium; and "passive acquisition" based on user input or program instructions, such as "the device inputting data output from another device," for example, waiting in a state where it can receive data transmitted from an external device and receiving data transmitted from the external device, receiving data distributed (or transmitted, push notification, etc.) from an external device, selecting and acquiring data from the received data or information; and "generating new data by editing data (converting to text, rearranging data, extracting some data, changing file format, etc.) and acquiring said new data."

[0116] Some or all of the above embodiments may also be described as follows, but are not limited to these. 1. An input information acquisition means for acquiring device identification information stored in an electronic money information storage device, A prepayment processing execution means that performs a prepayment process to deduct a predetermined amount from the balance of electronic money based on the electronic money information stored in the electronic money information storage device, If the prepayment amount exceeds the accounting amount, a registration means is provided to register the excess amount, which is the carry-over amount, in association with the aforementioned device identification information. An accounting means that performs accounting processing to output the carry-over amount in a way that is visible to the user, An accounting device having the following features. 2. The input information acquisition means acquires user identification information linked to the device identification information, The registration means is If the user identification information is not registered, the user identification information is registered in association with the device identification information. If the user identification information is already registered, the accounting device according to 1 updates the device identification information registered in association with the user identification information to the acquired device identification information. 3. The input information acquisition means acquires the prepayment amount specified by the user, The prepayment processing execution means is an accounting device according to 1 or 2 that calculates the predetermined amount based on the prepayment amount specified by the user and the carry-over amount registered in association with the device identification information. 4. The accounting means is an accounting device according to any one of 1 to 3 that performs the accounting process of accepting payment of the difference if the prepayment amount is less than the accounting amount. 5. The input information acquisition means acquires administrator identification information and password, Authentication means that performs authentication processing based on the administrator identification information and the password, If authentication is successful, an administrator screen control means is provided to display the administrator screen, An accounting device according to any one of 1 to 4, having the following features. 6. The accounting device according to 5, wherein the administrator screen control means displays information indicating whether or not receipts need to be replenished on the administrator screen. 7. As part of the procedures upon entering the parking lot, The input information acquisition means acquires the device identification information, The aforementioned prepayment processing execution means performs the prepayment processing and registers the prepayment amount. As part of the process when exiting the parking lot, The input information acquisition means acquires the device identification information, The accounting means is an accounting device according to any one of 1 to 6 that performs the accounting process based on the prepayment amount registered in association with the device identification information and the accounting amount. 8. The administrator screen control means is an accounting device according to 7 that is subordinate to 5 or 6 and causes the administrator screen to display information indicating the usage status of the parking lot. 9. The computer, The device identification information stored in the electronic money information storage device is obtained, Based on the electronic money information stored in the electronic money information storage device, a prepayment process is performed to deduct a predetermined amount from the electronic money balance. If the prepayment amount exceeds the total amount due, the excess amount, which is the carry-over amount, is registered in association with the aforementioned device identification information. An accounting method that performs accounting processing to output the aforementioned carry-over amount in a way that is visible to the user. 10. Computers, Input information acquisition means for acquiring device identification information stored in an electronic money information storage device, Prepayment processing execution means that performs a prepayment process to deduct a predetermined amount from the balance of electronic money based on the electronic money information stored in the electronic money information storage device. If the prepayment amount exceeds the accounting amount, a registration means for registering the carry-over amount (the excess amount) and the device identification information linked together, and An accounting means that performs accounting processing to output the carry-over amount in a way that is visible to the user, A program that makes it function as such.

[0117] Although the present invention has been described above with reference to embodiments (and examples), the present invention is not limited to the above embodiments (and examples). Various modifications to the structure and details of the present invention can be made, as can be understood by those skilled in the art within the scope of the present invention.

[0118] This application claims priority based on Japanese Patent Application No. 2019-127813, filed on 9 July 2019, and incorporates all of its disclosures herein. [Explanation of symbols]

[0119] 1A Processor 2A Memory 3A input / output I / F 4A Peripheral Circuits 5A bus 100 accounting devices 11 Reader / Writer Section 12 Input reception section 13 Input Information Acquisition Unit 14 Registration Department 15 Storage section 16 Prepayment Processing Execution Unit 17 Determined part 18 Accounting Department 19 Output section 20 Administrator Screen Control Unit 21 Certification Department

Claims

1. In the process of receiving payment for the second service, before executing the payment for the second service and before the price for the second service is determined in response to user input, a process is performed to display the surplus amount paid for the first service. If the surplus is insufficient to cover the cost of the second service, a process is performed to display a screen requesting additional payment. If an additional payment is made after the aforementioned screen is displayed, the process will be to display the balance of the electronic money used for the additional payment. A program that causes a computer to execute something.

2. The program according to claim 1, which stores the electronic money information and causes the computer to execute a process to display the screen in response to communication between a portable device having a short-range wireless communication function and an accounting device for paying the price of the second service with the electronic money.

3. The program according to claim 1, wherein the price for the second service is determined according to the amount of charge.

4. The program according to claim 1, wherein the price for the second service is determined according to the service usage time.

5. A process for displaying candidates for identifying the price of the second service, A process to determine the compensation corresponding to the identified candidate, The program according to claim 1, which causes the computer to execute the program.

6. The second service mentioned above is a vehicle-related service, The program according to claim 5, wherein the process for displaying the candidates encloses multiple vehicles individually and includes a process for displaying selectable frames.

7. In the process of receiving payment for the second service, before executing the payment for the second service and before the price for the second service is determined in response to user operations, means for displaying the surplus amount paid for the first service, If the surplus is insufficient to cover the cost of the second service, means for displaying a screen requesting additional payment, If an additional payment is made after the aforementioned screen is displayed, a means for displaying the balance of the electronic money used for the additional payment is provided. A processing device.

8. One or more computers, In the process of receiving payment for the second service, before executing the payment for the second service and before the price for the second service is determined in response to user input, a process is performed to display the surplus amount paid for the first service. If the surplus is insufficient to cover the cost of the second service, a process is performed to display a screen requesting additional payment. If an additional payment is made after the aforementioned screen is displayed, the process will be to display the balance of the electronic money used for the additional payment. A method for executing this process.

Images