PROGRAM, PROCESSING APPARATUS 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]

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

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

[0003] Patent document 1 discloses a technology in which a prepaid amount is deducted from an IC card at the entrance to a parking lot, the prepaid amount is registered along with a vehicle ID (identifier), the IC card ID, and the time of entry, and at the exit of the parking lot, only the vehicle ID is obtained via wireless communication to calculate the parking fee, the amount remaining after deducting the parking fee from the prepaid amount is registered as a deposit, and is then refunded to the IC card at the entrance the next time the parking lot is used.

[0004] Patent Document 2 has a measuring unit that determines the entry date and time based on the entry signal of the vehicle and measures the parking time from the entry date and time, a reading unit that reads the vehicle number from the vehicle image, a recording unit that correlates and records the vehicle number, the vehicle image, and the entry date and time, a panel unit equipped with an operation unit for input operation and a display unit that displays the vehicle number and the vehicle image, a settlement unit for settling the parking fee, a first control unit for settling based on the vehicle number and a second control unit for settling based on the entry date and time. The first control unit displays multiple images based on the input vehicle number, and the second control unit displays multiple images based on the input entry date and time to determine whether the vehicle is the one being settled. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2008-152588 A [Patent Document 2] JP 2018-22366 A Summary of the Invention [Problem to be solved by the invention]

[0006] There are cases where the billing amount is determined according to the content of use and is not fixed at the start of use. Examples of such cases include, but are not limited to, parking lots and rental offices where the billing amount is determined according to the duration of use, shared bicycles and shared cars, charging services where the billing amount is determined according to the amount of charge, restaurants where the billing amount is determined according to the content of an order, amusements such as bowling where the billing amount is determined according to the number of games played, supermarkets and convenience stores where the billing amount is determined according to the content of purchases, vending machines for beverages, gas stations, etc.

[0007] In such cases, it is common to pay at the end of use when the bill amount is fixed. However, some users may wish to pay at the beginning of use in order to avoid waiting in line to pay. Some kind of ingenuity is required to make the payment at the beginning of use when the bill amount is not yet fixed.

[0008] The above problem can be solved by the technology disclosed in Patent Document 1, which "registers the amount remaining after deducting the final fee from the prepaid amount as a deposit and refunds it the next time the service is used." However, with the technology described in Patent Document 1, the user cannot know the existence of the deposit or its amount until the deposit is refunded. This makes it difficult for users to manage their deposits, resulting in poor convenience. Patent Document 2 does not describe or suggest the technical idea behind prepayment of usage fees or the issues involved.

[0009] An object of the present invention is to improve the convenience of a technology for having a user prepay a usage fee and registering a carried-over amount obtained by subtracting an accounting amount from the prepaid amount. [Means for solving the problem]

[0010] According to the present invention, A means for acquiring an advance payment amount to be paid by a user before the user starts using the service; means for acquiring an accounting amount according to the user's usage record of the service; a means for displaying on a display a carry-over amount to be preferentially used when the user makes a payment, based on the advance payment amount and the billing amount; A payment device having a

[0011] Further, according to the present invention, One or more computers A process of acquiring an amount to be prepaid by a user before the user starts using the service; A process of acquiring an accounting amount according to the user's usage record of the service; a process of displaying on a display a carry-over amount to be preferentially used when the user makes a payment, based on the prepaid amount and the billing amount; An accounting method is provided that performs the above steps.

[0012] Further, according to the present invention, On one or more computers, A process of acquiring an amount to be prepaid by a user before the user starts using the service; A process of acquiring an accounting amount according to the user's usage record of the service; a process of displaying on a display a carry-over amount to be preferentially used when the user makes a payment, based on the prepaid amount and the billing amount; An accounting program is provided that performs the above steps. Effect of the Invention

[0013] According to the present invention, the convenience of the technology in which a usage fee is paid in advance and the carried-over amount obtained by subtracting the billing amount from the prepaid amount is registered is improved. [Brief description of the drawings]

[0014] [Figure 1] FIG. 2 is an example of a functional block diagram of the accounting device of the present embodiment. [Diagram 2]2 is a diagram illustrating an example of the hardware configuration of the accounting device of the present embodiment. FIG. [Diagram 3] 10 is a flowchart showing an example of the flow of processing implemented by the accounting device of the present embodiment. [Figure 4] 10 is a flowchart showing an example of the flow of processing implemented by the accounting device of the present embodiment. [Diagram 5] 10 is a flowchart showing an example of the flow of processing implemented by the accounting device of the present embodiment. [Figure 6] 11 is an example of a screen realized by the accounting device of the present embodiment. [Figure 7] 11 is an example of a screen realized by the accounting device of the present embodiment. [Figure 8] 11 is an example of a screen realized by the accounting device of the present embodiment. [Figure 9] 1 is a diagram illustrating an example of information processed by the accounting device of the present embodiment. FIG. [Figure 10] 1 is a diagram illustrating an example of information processed by the accounting device of the present embodiment. FIG. [Figure 11] 1 is a diagram illustrating an example of information processed by the accounting device of the present embodiment. FIG. [Figure 12] FIG. 2 is an example of a functional block diagram of the accounting device of the present embodiment. [Figure 13] 11 is an example of a screen realized by the accounting device of the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[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 or 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 or 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 and 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 order content, amusements such as bowling where the accounting amount is determined according to the number of games played, supermarkets and convenience stores where the accounting amount is determined according to the purchase content, vending machines for beverages, gas stations, etc.

[0016] The accounting device of this embodiment executes a prepayment process for a specified amount at the start of use (e.g., when starting to use a parking lot), and registers the prepayment amount linked to the user. Then, at the end of use (e.g., when finishing using the parking lot), the accounting device of this embodiment compares the prepayment amount with the final billing amount, and if the prepayment amount exceeds the billing amount, it registers the excess carryover amount linked to the user, and outputs the carryover amount so that it can be seen by the user (e.g., shows it on a display). With this accounting device of this embodiment, the user can visually check the output carryover amount to know the existence of a deposit and its 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 has 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, and an output unit 19.

[0018] The accounting device 100 may be configured as a single device that is physically and / or logically integrated, or may be configured as 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 stand-alone terminal installed in a store or facility and operated by a user. The following explanation will be given on the assumption that the accounting device 100 is realized by a stand-alone terminal installed in a store or facility and operated by a user.

[0019] Each of the above-mentioned functional parts of the accounting device 100 is realized by any combination of hardware and software, centered on the CPU (Central Processing Unit) of any computer, memory, programs loaded into the memory, a storage unit such as a hard disk that stores the programs (in addition to programs that are stored before the device is shipped, it can also store programs downloaded from storage media such as CDs (Compact Discs) or servers on the Internet), and a network connection interface.Those skilled in the art will understand that there are many variations in the methods of realizing this and the devices.

[0020] FIG. 2 is a block diagram illustrating an example of the hardware configuration of the accounting device 100. As shown in FIG. 2, the accounting device 100 has a processor 1A, memory 2A, an input / output interface 3A, a peripheral circuit 4A, and a bus 5A. The peripheral circuit 4A includes various modules. Note that the peripheral circuit 4A is not necessarily required. Note that when the accounting device 100 is made up of multiple devices that are physically and / or logically separated, each of the multiple devices can have the above hardware configuration.

[0021] The bus 5A is a data transmission path for the processor 1A, memory 2A, peripheral circuit 4A, and input / output interface 3A to transmit and receive data to each other. The processor 1A is an arithmetic processing device such as a CPU or a GPU (Graphics Processing Unit). The memory 2A is a memory such as a RAM (Random Access Memory) or a ROM (Read Only Memory). The input / output interface 3A includes an interface for acquiring information from an input device, an external device, an external server, an external sensor, a camera, etc., and an interface for outputting information to an output device, an external device, an external server, etc. Examples of the input device include a keyboard, a mouse, a microphone, a touch panel, a physical button, a camera, etc. Examples of the output device include a display, a speaker, a printer, a mailer, etc. The processor 1A can issue commands to each module and perform calculations based on the results of those calculations.

[0022] Next, returning to FIG. 1, the configuration of each functional unit will be described.

[0023] The reader / writer unit 11 performs short-distance wireless communication with the electronic money information storage device, and acquires and updates information stored in the electronic money information storage device. The electronic money information storage device is a portable device having a function of storing electronic money information and a function of short-distance wireless communication, and examples of such a device include, but are not limited to, an IC card, an IC tag, a smartphone, a mobile phone, a tablet terminal, and a smart watch. In the following, an example will be described in which the electronic money information storage device is an IC card.

[0024] The input receiving unit 12 receives various information input from a user via an input device, which may be, but is not limited to, a touch panel, a physical button, a microphone, a keyboard, a mouse, etc.

[0025] The input information acquiring unit 13 acquires various pieces of information input from the reader / writer unit 11 and the input accepting unit 12 .

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

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

[0028] The prepayment process execution unit 16 executes the prepayment process.

[0029] The determination unit 17 determines the billing amount. For example, the determination unit 17 determines the billing amount based on the usage time, the amount of charge, the order details, the number of games, the purchase details, etc. Note that the example given here is merely an example, and the determination unit 17 may determine the billing amount based on other information.

[0030] The accounting unit 18 performs accounting processing based on the bill amount finalized by the finalization unit 17 and the prepaid amount in the prepayment processing.

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

[0032] Next, an example of the process flow realized by the above-mentioned functional unit will be described using the flowcharts in Figures 3 to 5 and the example screens in Figures 6 to 8. Here, an example will be described in which the accounting device 100 is used in a parking lot. The process flow will be described divided into "processing at the time of entry for first-time use", "processing at the time of entry for second or subsequent use (using the same IC card as last time)", "processing at the time of entry for second or subsequent use (using a different IC card from last time)", and "processing at the time of leaving the parking lot".

[0033] "Processing when entering the facility for the first time" After parking the vehicle at any position in the parking lot, the user operates the accounting device 100 installed at any position in the parking lot. The accounting device 100 displays the screen of FIG. 6(A) and is in a state of waiting for an operation. The user holds the IC card storing the electronic money information used for payment over the reader / writer of the accounting device 100. Then, the input information acquisition unit 13 acquires the card identification information stored in the IC card via the reader / writer unit 11 (S101 in FIG. 3). The card identification information is an example of the device identification information stored in the electronic money information storage device. The card identification information may be a number unique to the IC card that is not rewritable and is recorded in the IC chip mounted on the IC card when the IC chip is manufactured. Alternatively, the card identification information may be user identification information of the electronic money service related to the electronic money information stored in the IC card. The user identification information of the electronic money service is information for identifying users of the electronic money service from each other.

[0034] Next, the registration unit 14 determines whether the card identification information acquired in S101 has been registered in the user information (S102). The user information is information about a user who uses the parking lot, and is stored in at least one of the storage unit 15 and a storage device of a server configured to be able to communicate with the accounting device 100. FIG. 9 shows an example of user information. The user information shown in the figure links card identification information, telephone number, and carryover amount to each other. Note that the user information shown in the figure is merely an example, and may further include other information such as gender and date of birth.

[0035] If this is the first time the user has used the card, the user's card identification information has not been registered in the user information, so S102 is No and the process proceeds to S112.

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

[0037] If the input of the mobile phone number has not been accepted (No in S112), the registration unit 14 newly registers the card identification information acquired in S101 in the user information as shown in Fig. 9 (S119). Next, the process proceeds to S104.

[0038] On the other hand, if the input of a mobile phone number is accepted (Yes in S112), the input information acquisition unit 13 acquires the input phone number by linking it to the card identification information acquired in S101. After that, authentication processing is performed using the mobile phone (S113). In the authentication processing, a password is issued, the password is sent by short mail addressed to the accepted mobile phone number, the input of the sent password is accepted, and the issued password is compared with the input password. These processes may be performed by the registration unit 14, or by a server configured to be able to communicate with the accounting device 100, or some of the processes may be performed by the registration unit 14 and the other parts may be performed by the server. Also, if the short mail is not received, authentication may be performed by telephone. During these processes, the accounting device 100 displays screens such as those shown in FIG. 6(D) and FIG. 6(E).

[0039] If the authentication fails (No in S114), the registration unit 14 performs error processing (S118). For example, information indicating that the authentication failed is displayed on a screen, and a screen such as that shown in Fig. 6(C) is displayed to prompt the user to re-enter the phone number. Then, the process returns to S112 and is repeated.

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

[0041] If this is the first time the user is using the card, the user's phone number is not registered in the user information. Therefore, S115 returns No and the process proceeds to S117. In S117, the registration unit 14 links the card identification information acquired in S101 with the phone number accepted in S112, and registers them as new user information as shown in Fig. 9. The initial value of the carried-over amount is "0". The checkout device 100 then displays a screen as shown in Fig. 6 (F).

[0042] By carrying out the above steps, the initial registration of the information required to use the parking lot is completed. In the accounting service of the parking lot, the card identification information is used to mutually identify users who use the service.

[0043] Thereafter, in S104, the registration unit 14 determines whether the card identification information acquired in S101 has 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 at least one of the storage unit 15 and a storage device of a server configured to be able to communicate with the accounting device 100. FIG. 10 shows an example of the usage status information. The usage status information shown in the figure links the card identification information, the vehicle number, the prepaid amount, the entry date and time, the remaining time, the overtime flag, and the in-image ID to each other. Note that the usage status information may include other information, or may not include some of the exemplified information.

[0044] In the case of processing at the time of warehousing, the card identification information is not registered in the usage status information, so the result in S104 is No, and the process proceeds to warehousing processing in S106.

[0045] Next, the flow of the warehousing process in S106 will be described with reference to the flowchart in FIG.

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

[0047] Next, the accounting device 100 displays a screen as shown in Fig. 8(A) to prompt 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). The registration unit 14 then registers the acquired vehicle number in the usage information as shown in Fig. 10, linking it to the card identification information registered in S201 (S202).

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

[0049] The input information acquisition unit 13 acquires information specifying any vehicle in the image via the input reception unit 12 (S203). Then, the registration unit 14 registers information identifying the vehicle specified in the image (intra-image ID) in the usage information as shown in Fig. 10 in association with the card identification information registered in S201 (S203). The intra-image ID may be, for example, identification information of a frame surrounding each vehicle identified in the image.

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

[0051] Next, the prepayment process execution unit 16 acquires the carried-over amount linked to the card identification information registered in S201 from the user information as shown in FIG. 9 (S205).

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

[0053] For example, the prepayment process execution unit 16 calculates a predetermined amount (=prepayment amount-carryover amount) based on the prepayment amount specified in S204 and the carryover amount acquired in S205. Then, as shown in Fig. 8(D), the checkout device 100 displays the calculated predetermined amount ("Payment Amount" in the figure) and displays a screen prompting the user to hold the IC card over the reader / writer of the checkout device 100. In response, the IC card is held over the reader / writer of the checkout device 100, and the checkout device 100 and the IC card are able to communicate with each other. When this occurs, the prepayment process execution unit 16 updates the electronic money information stored in the IC card via the reader / writer unit 11 and subtracts the predetermined amount from the balance of electronic money.

[0054] Then, the registration unit 14 updates the carry-over amount linked to the card identification information registered in S201 in the user information as shown in Fig. 9 (S208). Specifically, the carry-over amount used to pay the prepaid amount is subtracted. Note that if the carry-over amount has not been used to pay the prepaid amount, there is no need to update the carry-over amount.

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

[0056] The processing order of S202 to S205 is not limited to the processing order shown in Fig. 4. Although not shown, the registration unit 14 registers the entry date and time at any timing in association with the card identification information registered in S201. The entry date and time is a time at any timing after the input of the card identification information is accepted in S101.

[0057] "Processing when entering the parking lot for the second or subsequent use (using the same IC card as last time)" After parking the vehicle anywhere in the parking lot, the user operates the accounting device 100 installed anywhere in the parking lot. The accounting device 100 displays the screen in FIG. 6(A) and is in a waiting state for operation. The user holds an IC card that stores electronic money information to be used for payment over the reader / writer of the accounting device 100. Here, it is assumed that the user holds over the reader / writer the same IC card that was used the previous time the user 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 FIG. 3).

[0058] Next, the registration unit 14 judges whether the card identification information acquired in S101 has been registered in the user information (S102). If the second or subsequent use is the same IC card as the previous use, the card identification information of the user is registered in the user information. Therefore, S102 is Yes, and the process proceeds to S103.

[0059] Next, the registration unit 14 determines whether or not a phone number is registered in association with the card identification information acquired in S101 in the user information as shown in Fig. 9 (S103). If the phone number has already been registered (Yes in S103), the process proceeds to S104.

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

[0061] If the input of the mobile phone number is not accepted (No in S107), proceed to S104. On the other hand, if the input of the mobile phone number is accepted (Yes in S107), the input information acquisition unit 13 acquires the input phone number by linking it to the card identification information acquired in S101. Then, authentication processing is performed using the mobile phone (S108). The contents of the authentication processing are the same as the authentication processing in S113 described in "Processing at the time of parking when using for the first time".

[0062] If the authentication fails (No in S109), the registration unit 14 performs error processing (S111). For example, information indicating that the authentication failed is displayed on a screen, and a screen such as that shown in FIG. 6C is displayed to prompt the user to re-enter the phone number. Then, the process returns to S107 and is repeated.

[0063] On the other hand, if the authentication is successful (Yes in S109), the registration unit 14 registers the input phone number in the user information as shown in Fig. 9 by linking it to the card identification information acquired in S101 (S110). Then, the process proceeds to S104.

[0064] In S104, the registration unit 14 judges whether the card identification information acquired in S101 has been registered in the usage status information. In the case of processing at the time of warehousing, the card identification information has not been registered in the usage status information. Therefore, the result of S104 is No, and the process proceeds to the warehousing process of S106. The contents of the warehousing process of S106 are the same as those explained in "Processing at the time of warehousing for the first time use".

[0065] "Processing when entering the parking lot for the second or subsequent use (using a different IC card than last time)" This example assumes a case where an IC card (electronic money) different from the one used the parking lot the previous time is used due to any reason such as loss, expiration, non-possession, or insufficient charge amount. As described above, in the accounting service of the parking lot, the card identification information is information that identifies users who use the service. Therefore, if an IC card different from the one used the parking lot the previous time is used, the carried-over amount registered in association with the card identification information of the IC card used the previous time the parking lot was used cannot be used. However, as will become clear in the following explanation, if a user has registered a mobile phone number, the user can use his / her own carried-over amount even in such a case.

[0066] After parking the vehicle anywhere in the parking lot, the user operates the accounting device 100 installed anywhere in the parking lot. The accounting device 100 displays the screen in FIG. 6(A) and is in a waiting state for operation. The user holds an IC card that stores electronic money information to be used for payment over the reader / writer of the accounting device 100. Here, it is assumed that the user holds over the reader / writer an IC card that is different from the one used the parking lot last time. 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 FIG. 3).

[0067] Next, the registration unit 14 judges whether the card identification information acquired in S101 has been registered in the user information (S102). If the user is using a different IC card from the previous time he / she used the parking lot for the second or subsequent time, the card identification information of the user is not registered in the user information. Therefore, the result in S102 is No, and the process proceeds to S112.

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

[0069] If the input of the mobile phone number is not accepted (No in S112), the registration unit 14 newly registers the card identification information acquired in S101 in the user information as shown in Fig. 9 (S119). Next, proceed to S104. In this case, the card identification information of the IC card used this time is registered separately from the card identification information of the IC card used last time. Then, the carried-over amount linked to the card identification information of the IC card used last time becomes unavailable.

[0070] On the other hand, if the input of the mobile phone number is accepted (Yes in S112), the input information acquisition unit 13 acquires the input phone number by linking it to the card identification information acquired in S101. Then, an authentication process is performed using the mobile phone (S113). The contents of the authentication process are the same as those described in "Processing at the time of entry when using for the first time".

[0071] If the authentication fails (No in S114), the registration unit 14 performs error processing (S118). For example, information indicating that the authentication failed is displayed on a screen, and a screen such as that shown in Fig. 6(C) is displayed to prompt the user to re-enter the phone number. Then, the process returns to S112 and is repeated.

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

[0073] If a different IC card is used for the second or subsequent use and the phone number has already been registered when the user used the parking lot, the phone number of the user 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 association with the phone number acquired in S112 in the user information as shown in FIG. 9 to the card identification information acquired in S101. As a result, for example, the user information shown in FIG. 9 is updated to that shown in FIG. 11. Comparing the user information in FIG. 9 and FIG. 11, it can be seen that the card identification information associated with the phone number "090-XXX-XXX" has been updated from "C1131923" to "C0037279".

[0074] Even if a different IC card is used for the second or subsequent use, if the user has not registered a phone number when using the parking lot up to that point, the phone number of the user is not registered in the user information. Therefore, S115 is No, and the process proceeds to S117. In S117, the registration unit 14 associates the card identification information acquired in S101 with the phone number accepted in S112, and newly registers them in the user information as shown in FIG. 9. The initial value of the carryover amount is "0". In this case, the card identification information of the IC card used this time is registered separately from the card identification information of the IC card used last time. The carryover amount associated with the card identification information of the IC card used last time becomes unavailable.

[0075] In S104, the registration unit 14 judges whether the card identification information acquired in S101 has been registered in the usage status information. In the case of processing at the time of warehousing, the card identification information has not been registered in the usage status information. Therefore, the result of S104 is No, and the process proceeds to the warehousing process of S106. The contents of the warehousing process of S106 are the same as those explained in "Processing at the time of warehousing for the first time use".

[0076] Note that here, the user holds the IC card to be used this time over the reader / writer of the accounting apparatus 100 on the screen of Fig. 6(A), but the process may also proceed in the following manner. First, the user touches "How to use" on the screen shown in Fig. 7(A) (the same as the screen shown in Fig. 6(A)) to transition to the screen of Fig. 7(B), and then touches "For those with a registered card" to transition to the screen of Fig. 7(G). Then, after touching "Lost card" on that screen to transition to the screen of Fig. 7(H), the process proceeds in the same manner as in the above example, following the flow of Fig. 7(D), Fig. 7(E), Fig. 7(F), and Fig. 7(I).

[0077] "Processing at the time of issue" When leaving the parking lot, the user operates the accounting device 100 installed at any position in the parking lot. The accounting device 100 displays the screen in Fig. 6(A) and is in a waiting state for operation. The user holds the IC card that was held over the accounting device 100 when entering the parking lot over the reader / writer of the accounting device 100. The input information acquisition unit 13 then acquires the card identification information stored in the IC card via the reader / writer unit 11 (S101 in Fig. 3).

[0078] Next, the registration unit 14 judges whether the card identification information acquired in S101 has been registered in the user information (S102). The card identification information of the IC card was registered in the user information at the time of entry. Therefore, S102 becomes Yes, and the process proceeds to S103.

[0079] Next, the registration unit 14 determines whether or not a phone number is registered in association with the card identification information acquired in S101 in the user information as shown in Fig. 9 (S103). If the phone number has already been registered (Yes in S103), the process proceeds to S104.

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

[0081] If the input of the mobile phone number is not accepted (No in S107), proceed to S104. On the other hand, if the input of the mobile phone number is accepted (Yes in S107), the input information acquisition unit 13 acquires the input phone number by linking it to the card identification information acquired in S101. Then, authentication processing is performed using the mobile phone (S108). The contents of the authentication processing are the same as the authentication processing in S113 described in "Processing at the time of parking when using for the first time".

[0082] If the authentication fails (No in S109), the registration unit 14 performs error processing (S111). For example, information indicating that the authentication failed is displayed on a screen, and a screen such as that shown in FIG. 6C is displayed to prompt the user to re-enter the phone number. Then, the process returns to S107 and is repeated.

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

[0084] In S104, the registration unit 14 judges whether the card identification information acquired in S101 has been registered in the usage status information. In the case of processing at the time of withdrawal, the card identification information has been registered in the usage status information. Therefore, S104 becomes Yes, and the process proceeds to withdrawal processing in S105.

[0085] Next, the flow of the shipping process in S105 will be described with reference to the flowchart in FIG.

[0086] The determination unit 17 obtains the entry date and time registered in association with the card identification information obtained in S101 of Fig. 3 from the usage information as shown in Fig. 10, and calculates the billing amount based on the entry date and time and the withdrawal date and time (S301). The withdrawal date and time is the time when the input of the card identification information is accepted in S101 at the time of withdrawal, or 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 the user information as shown in FIG. 9, associating it with the card identification information obtained in S101 (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 card identification information obtained in S101 to be deleted from the user information as shown in FIG. 10 via the registration department 14 (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 card identification information obtained in S101 to be deleted from the user information as shown in FIG. 10 via the registration department 14 (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 accounting processing to accept payment for the shortfall (S306). For example, the accounting department 18 calculates the shortfall and outputs information requesting the user to make a payment for 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 card identification information obtained in S101 to be deleted from the user information as shown in FIG. 10 via the registration department 14 (S305).

[0090] According to the accounting device 100 described above, the user can pay the usage fee in advance, and the carryover amount obtained by subtracting the billing amount from the advance payment amount can be registered. The accounting device 100 can notify the user of the carryover amount to be registered. Furthermore, according to the accounting device 100, the carryover amount can be used for payment the next time the user uses the parking lot. Furthermore, according to the accounting device 100, even if a different IC card is used from the one used last time, if the user registers a telephone number, the user information can be updated using the telephone number (FIG. 9 to FIG. 11), and the carryover amount generated when using another IC card can be used. Furthermore, by taking an image of the parking lot, identifying and managing the vehicle of each user, it is possible to verify fraudulent use and to use the image as evidence of fraudulent use. In this way, the accounting device 100 achieves high convenience.

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

[0092] In the above example, the input and registration of the vehicle number is requested, but this process may be omitted. In the above example, the vehicle is specified in the image and requested to be registered, but this process may be omitted.

[0093] Additionally, the checkout apparatus 100 may be equipped with a camera that captures an image of a customer operating the checkout apparatus 100. The checkout apparatus 100 may also be able to register the customer's face information (a face image or features generated from a face image) in the user information (see FIG. 9) in association with the card identification information. For example, the checkout apparatus 100 may accept the capture and registration of a face image before or after the registration of a phone number in the above process flow, or at another time.

[0094] Then, the accounting device 100 may photograph the face of the customer and perform facial authentication before the customer holds the IC card over the reader / writer of the accounting device 100 as in Fig. 6(A) etc. For example, the accounting device 100 may detect that a person is standing in front of the accounting device 100 using a human presence sensor etc. and automatically photograph the person in response to the detection, or may photograph the person in response to manual operation by the customer.

[0095] If face authentication is successful, the checkout apparatus 100 may execute the process from S101 onwards in Fig. 3 without the customer having to hold the IC card over the reader / writer of the checkout apparatus 100. In this case, in S101, the checkout apparatus 100 reads the card identification information of the successfully authenticated customer from the user information (see Fig. 9), and executes the process from S102 onwards based on that information.

[0096] On the other hand, if face authentication fails, the checkout apparatus 100 displays a screen as shown in FIG. 6(A) and accepts an operation to hold the IC card over the reader / writer of the checkout apparatus 100 (S101 in FIG. 3).

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

[0098] 12 shows an example of a functional block diagram of the accounting device 100. As shown in the figure, the accounting device 100 has 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 process 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 reader / writer unit 11, input reception unit 12, input information acquisition unit 13, registration unit 14, storage unit 15, prepayment process execution unit 16, confirmation unit 17 and accounting unit 18 are configured in the same manner as in the first embodiment.

[0100] The authentication unit 21 executes authentication processing based on the administrator identification information and password. If the authentication is successful, the administrator screen control unit 20 causes the output unit 19 to output an administrator screen.

[0101] Next, an example of the flow of processing realized by the above-mentioned functional units will be described using the example screen of Fig. 13. Here, the explanation will be given taking as an example a case where the accounting apparatus 100 is used in a parking lot.

[0102] The accounting device 100 displays the screen of FIG. 13(A) and is in a state of waiting for an operation. When the administrator touches "Click here for password", the screen transitions to FIG. 13(B) and FIG. 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 executes authentication processing based on the administrator identification information and password. Authentication is achieved by comparing a combination of the administrator identification information and password of a legitimate authority registered in advance with the acquired combination of the administrator identification information and password. The matching may be performed by the authentication unit 21 or by a server configured to be able to communicate with the accounting device 100. The combination of the administrator identification information and password of the legitimate authority is stored in the memory unit of the entity that performs the matching. When the server performs the matching, the authentication unit 21 performs authentication processing to transmit the acquired combination of the administrator identification information and password to the server and obtain the matching result from the server.

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

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

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

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

[0107] The information indicating the parking lot usage status (see FIG. 13(F)) may be sent to the manager's terminal by any wired and / or wireless communication means. For example, the manager's terminal and the accounting device 100 may communicate by short-range wireless communication. Alternatively, the manager's terminal and the accounting device 100 may be connected by wire. Alternatively, when an email address is entered into the accounting device 100, the information indicating the parking lot usage status may be sent to that email address.

[0108] Furthermore, the administrator screen control unit 20 may display a setting screen for changing various settings on the administrator screen, as shown in Fig. 13(E). For example, a setting authority level may be registered in association with each administrator identification information, and the contents that each administrator can set on the setting screen displayed at login may be controlled based on the registered contents.

[0109] Other configurations of the accounting device 100 are similar to those in the first embodiment.

[0110] As described above, the accounting device 100 of this embodiment can achieve the same effects as the first embodiment. Furthermore, the accounting device 100 of this embodiment can not only accept user operations, but also accept operations from an administrator and output information intended for the administrator. A single device can accept operations from users and administrators, achieving high convenience.

[0111] Here, a modified example of this embodiment will be described. In the above-mentioned example, authentication is performed using administrator identification information and a password, but this may be replaced with biometric authentication using biometric information such as a face image, a fingerprint, a voiceprint, or an iris.

[0112] Here, a modified example applicable to all the embodiments will be described. As described above, the accounting device 100 of this embodiment can be used in all kinds of situations, such as parking lots, rental offices, shared bicycles, shared cars, charging services, restaurants, amusement facilities such as bowling, supermarkets, convenience stores, vending machines, and gas stations. However, user information (see FIG. 9) may be managed by each service provider, or one piece of user information may be managed collectively among multiple providers. When one piece of user information is managed collectively among multiple providers, the user information referred to by the accounting device 100 when accounting for a parking lot and the user information referred to by the accounting device 100 when accounting for a rental office are the same information. In this case, for example, a carryover amount generated when using a parking lot can be used when using other services such as a rental office. Also, if card identification information and a phone number are registered when using a parking lot, registration work is not required when using other services such as a rental office.

[0113] The carryover amount may be used in places other than stores or facilities where the bill amount is determined according to the content of use and the bill amount is not fixed at the start of use. For example, vending machines are an example, but are not limited to these. In this case, when paying a specified amount, the payment device reads the information of an IC card linked to the carryover amount in the user information (see FIG. 9), and the payment device refers to the user information and checks whether there is a carryover amount. If there is a carryover amount, the payment device uses the carryover amount preferentially to make the payment.

[0114] In the above description, the electronic money information storage device is an IC card, but the electronic money information storage device may be other devices such as an IC tag, a smartphone, a mobile phone, a tablet terminal, a smart watch, etc. In this case, the device identification information may be information that identifies each individual device, or may be user identification information of an electronic money service stored in each device.

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

[0116] A part or all of the above-described embodiments can be described as follows, but is not limited to the following. 1. An input information acquisition means for acquiring device identification information stored in an electronic money information storage device; a prepayment processing execution means for executing a prepayment processing for subtracting a predetermined amount from the balance of electronic money based on the electronic money information stored in the electronic money information storage device; a registration means for registering, when the prepaid amount exceeds the billing amount, a carried-over amount which is the excess amount, in association with the device identification information; a checkout means for performing checkout processing to output the carryover amount in a manner that is visible to a user; An accounting device having: 2. The input information acquisition means acquires user identification information linked to the device identification information; The registration means includes: If the user identification information is not registered, the user identification information is registered in association with the device identification information; The accounting device described in 1, wherein if the user identification information has already been registered, the device identification information registered in association with the user identification information is updated to the obtained device identification information. 3. The input information acquisition means acquires the advance payment amount designated by the user, The prepayment processing execution means of the accounting device described in 1 or 2 calculates the specified amount based on the prepayment amount specified by the user and the carried-over amount registered in association with the device identification information. 4. A payment device according to any one of 1 to 3, wherein the payment means executes the payment process to accept payment for the shortfall if the advance payment falls short of the payment amount. 5. The input information acquisition means acquires administrator identification information and a password, an authentication means for executing an authentication process based on the administrator identification information and the password; an administrator screen control means for outputting an administrator screen when the authentication is successful; 5. An accounting device according to any one of 1 to 4, comprising: 6. The accounting device according to 5, wherein the administrator screen control means causes information indicating whether or not receipts need to be replenished to be displayed on the administrator screen. 7. When entering the parking lot, The input information acquiring means acquires the device identification information, The prepayment processing execution means performs the prepayment processing and registers the prepayment amount, As a process when exiting the parking lot, The input information acquiring means acquires the device identification information, The accounting means executes the accounting process based on the prepaid amount registered in association with the device identification information and the accounting amount. 8. An accounting device as described in 7, which is subordinate to 5 or 6, wherein the administrator screen control means displays information indicating the parking lot usage status on the administrator screen. 9. The computer: Acquire device identification information stored in an electronic money information storage device; execute a prepayment process for subtracting 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 prepaid amount exceeds the billing amount, the excess amount, that is, the carried-over amount, is linked to the device identification information and registered; An accounting method for performing accounting processing that outputs the carried-over amount in a manner that is visible to the user. 10. Computer input information acquiring means for acquiring device identification information stored in an electronic money information storage device; a prepayment processing execution means for executing a prepayment processing for subtracting a predetermined amount from the balance of electronic money based on the electronic money information stored in the electronic money information storage device; a registration means for registering, when the prepaid amount exceeds the billing amount, a carryover amount which is the excess amount, in association with the device identification information; accounting means for performing accounting processing to output the carried-over amount in a manner that is visible to the user; A program that functions as a

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

[0118] This application claims priority based on Japanese Patent Application No. 2019-127813, filed on July 9, 2019, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]

[0119] 1A Processor 2A Memory 3A input / output I / F 4A Peripheral circuit 5A Bus 100 Accounting device 11 Reader / writer section 12 Input reception section 13 Input information acquisition section 14 Registration Department 15 Storage section 16 Advance payment processing execution unit 17 Determined part 18 Accounting Department 19 Output section 20 Administrator screen control section 21 Authentication Section

Claims

1. displaying a surplus of the amount paid for the first service; a process of displaying a screen requesting additional payment if the surplus is insufficient for the price of the second service; a process for displaying the balance of electronic money used for an additional payment when an additional payment is made after the display of the screen; A program that causes a computer to execute the following.

2. The program described in claim 1, which causes the computer to execute a process to display the screen in response to communication between a portable device having short-range wireless communication capability and an accounting device for paying for the second service.

3. The program described in claim 1, wherein the price of the second service is determined according to the amount of charging.

4. The program described in claim 1, wherein the compensation for the second service is determined according to the duration of service use.

5. A process for displaying candidates for identifying the price of the second service; A process of obtaining a compensation according to the identified candidate; The program according to claim 1 , which causes the computer to execute the steps of:

6. The program described in claim 5, wherein the process of displaying the candidates includes a process of surrounding multiple vehicles by vehicle.

7. A means for displaying a surplus of an amount paid for the first service; a means for displaying a screen requesting additional payment when the surplus money is insufficient for the price of the second service; a means for displaying a balance of electronic money used for an additional payment when the additional payment is made after the screen is displayed; A processing device having

8. One or more computers, displaying a surplus of the amount paid for the first service; a process of displaying a screen requesting additional payment if the surplus is insufficient for the price of the second service; a process for displaying the balance of electronic money used for an additional payment when an additional payment is made after the display of the screen; The processing method to be performed.

Images