JP6937448B1 - Cash payout equipment, programs, cash payout methods, cash payout systems and servers - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a cash payout device or the like which can be shared by a plurality of recipients. A cash payout device receives a user's biometric information and authenticates the user based on the received biometric information. When the cash payout device can authenticate the user, the cash payout device pays out a set amount of cash to the user. The cash payout device also authenticates the administrator who manages the user. When the administrator can be authenticated, the cash withdrawal device accepts and sets cash withdrawal conditions for a plurality of users associated with the administrator. [Selection diagram] Fig. 2

Description

The present invention relates to a cash payout device, a program, a cash payout method, a cash payout system and a server.

Elderly people and persons with disabilities who have difficulty managing their own money should not be wasted by, for example, being given cash regularly by a caregiver such as a family member and purchasing products with the given cash. There may be. In such cases, the caregiver must give cash on a regular basis, and the recipient who receives the cash may not receive the cash at the timing he / she wants, which can be a great stress for both parties. ..

Therefore, the applicant of the present application has proposed a cash payout machine that pays out cash stored in the device according to preset conditions (see Patent Document 1). In the cash payout machine of Patent Document 1, when the recipient is authenticated by biometric authentication, the set amount of cash is paid out if the set payout conditions are met. In such a cash payout machine, by setting the payout conditions, the caregiver can prevent the recipient from wasting cash because the cash exceeding the set conditions is not paid out, and the recipient wants himself / herself. You can receive cash at the right time.

Utility Model Registration No. 3223914

In Patent Document 1, since one recipient is assumed to receive cash from the cash dispenser, it is not assumed that a plurality of recipients share one cash dispenser.

The present invention has been made in view of such circumstances, and an object of the present invention is to provide a cash payout device or the like that can be shared by a plurality of recipients.

The cash payout device according to one aspect of the present invention is set for a biometric information receiving unit that receives the biometric information of the user, a user authentication unit that authenticates the user based on the received biometric information, and an authenticated user. A cash withdrawal device including a withdrawal unit for paying out a certain amount of cash, for an administrator authentication unit that authenticates an administrator who manages the user, and for a plurality of users associated with the authenticated administrator. It is equipped with a setting unit that accepts and sets cash withdrawal conditions.

In one aspect of the present invention, it is possible to provide a cash payout device or the like that can be shared by a plurality of recipients.

It is a perspective view which shows the appearance of the cash payout device. It is a block diagram which shows the internal structure example of a cash payout device. It is a schematic diagram which shows the structural example of the DB stored in the cash payout apparatus. It is a flowchart which shows an example of the setting processing procedure by a cash payout apparatus. It is a schematic diagram which shows the screen example. It is a schematic diagram which shows the screen example. It is a schematic diagram which shows the screen example. It is a flowchart which shows an example of the withdrawal processing procedure by a cash withdrawal apparatus. It is a flowchart which shows an example of the deposit processing procedure by a user. It is a schematic diagram which shows the screen example. It is a schematic diagram which shows the structural example of the user information DB of Embodiment 3. It is a flowchart which shows an example of the deposit processing procedure in Embodiment 3. It is a schematic diagram which shows the screen example. It is a block diagram which shows the internal structure example of a cash payout device and a terminal device. It is a flowchart which shows an example of the setting processing procedure for a cash payout apparatus. It is a flowchart which shows an example of the setting processing procedure for a cash payout apparatus. It is a block diagram which shows the internal structure example of the cash payout device of Embodiment 5. It is a flowchart which shows an example of the monitoring processing procedure by a cash payout apparatus. It is a flowchart which shows an example of the exchange necessity determination processing procedure. It is a flowchart which shows an example of the balance collation processing procedure. It is a block diagram which shows the configuration example of the cash withdrawal system. It is a schematic diagram which shows the structural example of the apparatus information DB. It is a flowchart which shows an example of the management processing procedure by a server. It is a flowchart which shows an example of the management processing procedure by a server.

The cash payout device, program, cash payout method, cash payout system and server of the present disclosure will be described in detail based on drawings showing embodiments thereof.

(Embodiment 1)
FIG. 1 is a perspective view showing the appearance of the cash payout device, and FIG. 2 is a block diagram showing an example of the internal configuration of the cash payout device. The cash payout device 10 of the present embodiment is installed and used in a private house, a common area of an apartment house, a medical facility, a welfare facility, or the like. Further, in the cash payout device 10 of the present embodiment, the number of users (cash recipients) who receive cash payouts may be one or more, and there is also an administrator who manages deposits and withdrawals of each user. It may be one person or a plurality of people. In the following, a case where the cash payout device 10 is installed in a facility in which a plurality of managers manage a plurality of users will be described as an example.

The cash payout device 10 of the present embodiment has, for example, a square columnar housing, and a cash storage unit (shown) in which bills and money (cash) are stored for each denomination (amount) inside the housing. Is provided. A touch panel 13 is provided on one side of the cash payout device 10, and one side on which the touch panel 13 is provided is the front surface of the cash payout device 10. A cash slot 10b (first slot) for inserting banknotes and money is provided on the front surface of the cash payout device 10, and the cash inserted from the cash slot 10b is denominated by the denomination determination unit 16a. After the seed (amount) is determined, each of the determined denominations is stored in the cash storage unit. Further, on the front surface of the cash payout device 10, a payout outlet and a payout tray 15a for discharging the cash paid out by the cash payout unit 15 are provided. Further, a speaker 17 is provided in front of the cash payout device 10. The arrangement positions of the touch panel 13, the cash slot 10b, the payout tray 15a, and the speaker 17 are not limited to the example shown in FIG. 1, and even if any of these is provided on a surface other than the front surface of the cash payout device 10. good. For example, the touch panel 13 may be provided at a position where the operator who operates the cash payout device 10 can easily operate, and the speaker 17 may be provided at a position where the output voice can reach the operator. Further, the cash slot 10b may be provided at a position where cash can be easily inserted into the cash payout device 10, and the payout outlet and the payout tray 15a may be provided at a position where cash paid out from the cash payout device 10 can be easily taken. good.

A biometric authentication sensor 14 is provided on the upper surface of the cash payout device 10. The biometric authentication sensor 14 (biological information receiving unit) of the present embodiment is a vein sensor that reads the veins of the palm, and the cash payout device 10 of the present embodiment has a configuration that performs biometric authentication using the veins of the palm. However, the biometric authentication by the cash payout device 10 is not limited to the vein authentication of the palm, and may be the biometric authentication by the vein of the finger, the fingerprint, the iris of the pupil, the voice print, the face shape, etc., and a plurality of biometric information is combined. It may be configured to perform authentication. The biometric authentication sensor 14 may be provided on a surface other than the upper surface of the cash payout device 10, and a position where the operator can easily perform an operation necessary for biometric authentication (for example, an operation of holding the palm) depending on the type of biometric authentication. It may be provided in. Further, a batch insertion port 10a (second insertion port) for collectively inserting banknotes and money is provided on the side surface of the cash withdrawal device 10, and a lid with a key is attached to the batch insertion port 10a. be. The cash inserted from the batch insertion port 10a is also stored in the cash storage unit for each determined denomination after the denomination (amount) is determined by the denomination determination unit 16a. The batch insertion port 10a may be provided on a surface other than the side surface of the cash payout device 10, and may be provided at a position where the operator can easily insert cash in a batch. The cash payout device 10 having the above-described configuration is mounted on, for example, a horizontal mounting table, and is fixed to a mounting table, a wall, a pillar, or the like with a mounting bracket 10c for use.

The cash payout device 10 includes a control unit 11, a storage unit 12, a touch panel 13, a biometric authentication sensor 14, a cash payout unit 15, a cash reception unit 16, a speaker 17, a communication unit 18, and the like, and each of these units is via a bus. They are interconnected. The control unit 11 includes one or a plurality of processors such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit). The control unit 11 appropriately executes the control program 12P stored in the storage unit 12 to execute various information processing and control processing to be performed by the cash payout device 10.

The storage unit 12 includes a RAM (Random Access Memory), a flash memory, a hard disk, an SSD (Solid State Drive), and the like. The storage unit 12 stores in advance various data and the like necessary for executing the control program 12P and the control program 12P executed by the control unit 11. Further, the storage unit 12 temporarily stores data or the like generated when the control unit 11 executes the control program 12P. Further, the storage unit 12 stores the administrator information DB (database) 12a, the user information DB 12b, and the like, which will be described later. The administrator information DB 12a and the user information DB 12b may be stored in another storage device connected to the cash payout device 10, or may be stored in another storage device that the cash payout device 10 can communicate with.

The touch panel 13 has a display unit 13a and an input unit 13b. The display unit 13a is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 11. The input unit 13b is a touch sensor, receives an operation input by an operator who operates the cash payout device 10, and sends a control signal corresponding to the operation content to the control unit 11. The display unit 13a and the input unit 13b may be provided separately, and the input unit 13b may include an operation button such as a pressing type in addition to the touch sensor.

The biometric authentication sensor 14 reads the vein of the palm held over within a predetermined detection range to acquire vein data, and sends the acquired vein data to the control unit 11. The biometric authentication sensor 14 has, for example, a light emitting unit that emits near-infrared light and a light receiving unit that receives reflected light from the palm of the near infrared light emitted by the light emitting unit, and veins are based on the received reflected light. Acquire data (vein image). As shown in FIG. 1, the biometric authentication sensor 14 may be a built-in sensor integrally configured with the cash payout device 10, or may be a sensor externally attached to the cash payout device 10. When the biometric sensor 14 is externally attached, the cash payout device 10 may be connected to an external sensor via, for example, a USB (Universal Serial Bus) cable, or wirelessly capable of wireless communication with the external sensor. It is provided with a communication unit, and is configured to acquire vein data acquired by an external sensor via a connection unit or a wireless communication unit.

The cash payout unit 15 has, for example, a transport path for transporting cash stored in the cash storage section to the payout tray 15a for each denomination, and an opening / closing section for opening and closing each transport path. The cash payout unit 15 opens and closes each transport path at the opening / closing unit according to the instruction from the control unit 11, and thereby conveys (pays out) the amount of cash in accordance with the instruction from the control unit 11 to the payout tray 15a. The cash reception unit 16 is, for example, a denomination determination unit 16a for determining the denomination (amount) of banknotes and money (cash) inserted from the batch insertion slot 10a or the cash insertion slot 10b, and the inserted cash for each denomination. It has a transport path for transporting to the cash storage section and a guide section for guiding the inserted cash to each transport path for each denomination. The cash receiving unit 16 guides the inserted cash to each transport path by the guide unit according to the denomination determined by the denomination determination unit 16a, so that the inserted cash corresponds to the amount (denomination). It is transported to the cash storage section by the transport route. When the denomination determination unit 16a determines the denomination of cash inserted from the batch insertion port 10a or the cash insertion port 10b, the denomination determination unit 16a notifies the control unit 11 of the determined denomination.

The speaker 17 is an audio output unit that outputs audio according to an instruction from the control unit 11, and outputs a message instructed by the control unit 11 by audio. The communication unit 18 has an interface for connecting to a network such as the Internet or a LAN (Local Area Network) by wired communication or wireless communication, and transmits / receives information to / from another device via the network.

FIG. 3 is a schematic diagram showing a configuration example of DB 12a and 12b stored in the cash payout device 10. FIG. 3A shows the administrator information DB 12a, and FIG. 3B shows the user information DB 12b. The administrator information DB 12a stores information about an administrator who manages the cash and deposit / withdrawal status of the user who uses the cash withdrawal device 10. Here, the manager is, for example, an employee of a facility in which the cash payout device 10 is installed, and is a person in charge of managing deposits and withdrawals of a user who uses the cash payout device 10. The administrator information DB 12a shown in FIG. 3A includes an administrator ID column, an authentication data string, a user information column in charge, a work history column, and the like, and stores each information about the administrator in association with the administrator ID. The administrator ID column stores identification information (administrator ID) assigned to each administrator, and the authentication data string stores data used for authenticating each administrator. The administrator authentication data may be, for example, a password (character string data) specified by the administrator, and is biometric data (in this embodiment, palm vein data) that can be read by the biometric authentication sensor 14. You may. In the present embodiment, a configuration in which both the password and the biometric data are stored in the administrator information DB 12a will be described as an example, but only one of them may be stored in the administrator information DB 12a. The user information column in charge stores the user information assigned to each administrator, and specifically stores the user identification information (user ID) assigned to the user in charge of each administrator. The work history column stores history information including the content and date and time of the work performed by each administrator on the cash payout device 10. The work history information includes, for example, the date and time when the administrator logged in to the cash payout device 10, the date and time when various setting processes were performed on the user in charge of the administrator, and the deposit / withdrawal history of the user in charge of the administrator. Includes history information about all the work performed by the administrator on the cash payout device 10, such as the date and time when the above is confirmed. In addition to being stored in the administrator information DB 12a, the authentication data and work history may be stored in a predetermined area of the storage unit 12 or another storage device. In this case, the authentication data string and work history column are stored. Information for reading each data (for example, a file name indicating a data storage location) is stored.

The administrator ID stored in the administrator information DB 12a is issued and stored by the control unit 11 when a new administrator is added. The authentication data stored in the administrator information DB 12a and the user information in charge are stored by the control unit 11 when input via the input unit 13b or the communication unit 18 when a new administrator is added. When a change instruction is input via the input unit 13b or the communication unit 18, the control unit 11 changes the change. When the vein data of the palm is used as the authentication data, the authentication data is input via the biometric authentication sensor 14. The work history stored in the administrator information DB 12a is stored in association with the work date and time and the work content by the control unit 11 when the administrator performs an operation (work) on the cash payout device 10 via the input unit 13b. Will be done. The stored contents of the administrator information DB 12a are not limited to the example shown in FIG. 3A, and various information related to the administrator can be stored. For example, the name of the administrator, the department to which the administrator belongs, and the like may be stored.

The user information DB 12b stores information about a user who deposits cash in the cash payout device 10 and receives a regular payout. The user is, for example, a user or a resident of a facility in which the cash payout device 10 is installed. The user information DB 12b shown in FIG. 3B includes a user ID column, a biometric authentication data column, a name column, a withdrawal schedule column, a deposit / withdrawal history column, and the like, and stores each information about the user in association with the user ID. The user ID column stores identification information (user ID) assigned to each user, and the biometric authentication data string stores biometric data (venous data) used when performing biometric authentication for each user. The name column stores the name of each user. The withdrawal schedule column stores the withdrawal schedule indicating the withdrawal schedule set for each user, and the deposit / withdrawal history column is the history including the contents and date and time of the deposit / withdrawal made corresponding to each user. Memorize information. The deposit / withdrawal history information includes, for example, history information such as the date and time of deposit by the administrator and the deposit amount, the date and time of withdrawal by the user, and the withdrawal amount. In addition to being stored in the user information DB 12b, the biometric authentication data and the deposit / withdrawal history may be stored in a predetermined area of the storage unit 12 or another storage device. In this case, the biometric authentication data string and the deposit / withdrawal history are stored. The column stores information for reading each data (for example, a file name indicating a storage location of the data).

The user ID stored in the user information DB 12b is issued and stored by the control unit 11 when a new user is added. The biometric authentication data stored in the user information DB 12b is stored by the control unit 11 when it is input via the biometric authentication sensor 14 when a new user is added, and is stored via the input unit 13b or the communication unit 18. When the change is instructed, the change is made by the control unit 11 when the change is input via the biometric authentication sensor 14. The name stored in the user information DB 12b is stored by the control unit 11 when the name is input via the input unit 13b or the communication unit 18 when a new user is added. The withdrawal schedule stored in the user information DB 12b is stored by the control unit 11 when it is input via the input unit 13b or the communication unit 18 when a new user is added, and is stored in the input unit 13b or the communication unit. When the change instruction is input via 18, the change is made by the control unit 11. The deposit / withdrawal history stored in the user information DB 12b is stored in association with the deposit date and time and the deposit amount by the control unit 11 when the deposit is made in association with the user, and when the withdrawal is made by the user. The control unit 11 stores the withdrawal date and time and the withdrawal amount in association with each other. The stored contents of the user information DB 12b are not limited to the example shown in FIG. 3B, and various information about the user can be stored. For example, the user's age, gender, medical institution consultation ticket number and hospital room number, room number when living in a welfare facility, address, telephone number, contact information for family members (telephone number, etc.) ) And other personal information may be stored.

Hereinafter, in the present embodiment, when the administrator operates the cash withdrawal device 10 to set various information for the user, confirm the deposit / withdrawal history of the user, and register the deposit for the user. The processing performed by the cash payout device 10 will be described. FIG. 4 is a flowchart showing an example of the setting processing procedure by the cash payout device 10, and FIGS. 5 to 7 are schematic views showing a screen example. The following processing is realized by the control unit 11 according to the control program 12P stored in the storage unit 12 of the cash payout device 10, but a part of the processing may be realized by a dedicated hardware circuit.

When the cash payout device 10 of the present embodiment is in the standby state, for example, an initial screen (login screen) as shown in FIG. 5A is displayed on the touch panel 13 (display unit 13a). The login screen has an input field for entering a login ID and password, a login button for instructing execution of login processing based on the entered login ID and password, and a living body for instructing reading of biometric data. It has a data read button. When operating the cash payout device 10, the administrator instructs the execution of the login process by inputting the login ID and password on the login screen and operating the login button or operating the biometric data reading button. For the login ID, for example, an administrator ID assigned to each administrator is used.

In the cash payout device 10 displaying the login screen as shown in FIG. 5A, the control unit 11 determines whether or not the administrator authentication data necessary for the login process has been acquired (S11). For example, when the administrator inputs a login ID and password on the login screen and operates the login button, the control unit 11 acquires the login ID and password as authentication data. The login ID and password are entered, for example, via the keyboard or numeric keypad displayed on the touch panel 13 (display unit 13a). Further, when the cash payout device 10 has, for example, a card reader that reads card information stored in an IC (Integrated Circuit) card, it is managed by the card reader from the IC card in which the administrator ID and password of each administrator are stored. The person ID and password may be read. When the administrator operates the biometric data reading button on the login screen, the control unit 11 displays a message prompting the reading of vein data on the touch panel 13 or outputs a voice from the speaker 17, and then the biometric authentication sensor 14 is used by the administrator. Get vein data. The message prompting the reading of the vein data may be, for example, "hold the palm over the biometric authentication sensor", "hold the palm over the upper surface of the device", or the like. Further, a light may be provided in the vicinity of the biometric authentication sensor 14, and the control unit 11 may notify the location of the biometric authentication sensor 14 and prompt the reading of vein data by turning on or blinking the light.

When the control unit 11 determines that the administrator authentication data has not been acquired (S11: NO), the control unit 11 waits until the data is acquired. When it is determined that the administrator authentication data has been acquired (S11: YES), the control unit 11 (administrator authentication unit) authenticates the administrator based on the acquired authentication data (S12). Specifically, when the control unit 11 acquires the administrator ID and password as the authentication data, the control unit 11 uses the authentication data (password) stored in the administrator information DB 12a in association with the acquired administrator ID. It is judged whether or not the acquired passwords match, and if it is judged that they match, it is judged that the authentication is successful. Further, when the control unit 11 acquires the vein data as the authentication data, the control unit 11 determines whether or not the acquired vein data matches any of the authentication data (vein data) stored in the administrator information DB 12a. If it is judged that they match, it is judged that the authentication is successful. At this time, the control unit 11 identifies the administrator (administrator ID) corresponding to the authentication data matching the acquired vein data, and determines that the authentication has succeeded for the identified administrator.

The control unit 11 determines whether or not the administrator's authentication based on the acquired authentication data has succeeded (S13), and if it determines that the authentication has failed (S13: NO), returns to the process of step S11. At this time, the control unit 11 may display or output a message indicating that the authentication has failed, and after displaying or outputting the message, returns to the display of the login screen shown in FIG. 5A. When it is determined that the administrator's authentication based on the acquired authentication data is successful (S13: YES), the control unit 11 generates a list screen of users in charge of the authenticated administrator as shown in FIG. 5B. Is displayed on the touch panel 13 (S14). The screen shown in FIG. 5B displays the administrator ID of the logged-in (authenticated) administrator, and the name and user ID list (list of responsible users) of the user in charge of this administrator. The name and user ID of each user can be selected in the list of users in charge. Further, the screen shown in FIG. 5B has an end button for instructing the end of the operation by the administrator. The control unit 11 reads out the user information (user ID) in charge stored in the administrator information DB 12a in association with the administrator ID of the authenticated administrator, and reads the user name of the read user ID from the user information DB 12b. Generate a list of responsible users who read and displayed the name and user ID of the user in charge. Then, the control unit 11 generates the screen shown in FIG. 5B by adding the administrator ID of the logged-in administrator and the end button to the generated user list in charge. After the administrator authentication is successful, the control unit 11 includes the date and time at this time as the work history corresponding to the authenticated administrator's administrator ID, and the login history information indicating that the login process has been performed. Is stored in the administrator information DB 12a.

On the screen shown in FIG. 5B, the administrator selects a user who wants to be operated from the users displayed in the user list in charge via the input unit 13b. The control unit 11 determines whether or not the selection for any user has been accepted through the list of users in charge (S15), and if it determines that the selection has not been accepted (S15: NO), waits until it is accepted. When the end button is operated in the user list in charge, the control unit 11 ends the display of the user list in charge and returns to the display of the login screen shown in FIG. 5A.

When it is determined in the list of users in charge that the selection for any user has been accepted (S15: YES), the control unit 11 generates a menu screen corresponding to the selected user on the touch panel 13 as shown in FIG. 5C. Display (S16). The menu screen shown in FIG. 5C shows the administrator ID of the logged-in administrator, the name and user ID of the selected user, the current balance (remaining amount) of this user, and the last cash of this user. Displays the date and time when the last payout was made. Further, the menu screen shown in FIG. 5C has a menu button for instructing the user to execute a process (operation) that can be operated by the administrator, and an end button for instructing the user to end the operation. .. The menu buttons are an operation menu, a withdrawal schedule setting button for instructing the user to execute the withdrawal schedule setting process, a deposit / withdrawal history confirmation button for instructing the user to display the deposit / withdrawal history, and a deposit / withdrawal history confirmation button for the user. It has a deposit button for depositing in association with each other. Further, as a management menu, it has a user information change button for instructing the setting change of information about the user and an administrator information change button for instructing the setting change of the information about the administrator. The control unit 11 reads out the information on the menu screen stored in the storage unit 12 in advance, and records the current balance and the final withdrawal from the deposit / withdrawal history stored in the user information DB 12b in association with the user ID of the selected user. Read the execution date and time. Then, the control unit 11 generates the menu screen shown in FIG. 5C by adding the administrator ID of the administrator, the name and user ID of the user, the current balance of the user, and the final payout execution date and time to the read screen information. do. The menu screen is not limited to the configuration shown in FIG. 5C.

On the menu screen shown in FIG. 5C, the administrator instructs the user to execute the withdrawal schedule setting process by operating the withdrawal schedule setting button, and operates the deposit / withdrawal history confirmation button to deposit / withdraw the user. By instructing the display of the gold history and operating the deposit button, the user is instructed to accept the deposit. In addition, the administrator instructs to change the setting of the registration information about the user by operating the user information change button, and instructs to change the setting of the registration information about the administrator himself by operating the administrator information change button. The control unit 11 determines whether or not the execution instruction of the withdrawal schedule setting process for the user has been accepted via the menu screen (S17), and if it is determined that the instruction has been accepted (S17: YES), it is shown in FIG. Such a withdrawal schedule setting screen is displayed on the touch panel 13 (S18).

The withdrawal schedule setting screen shown in FIG. 6 is a screen for the cash withdrawal device 10 to set a schedule (condition) for withdrawing cash corresponding to the user. Specifically, on the withdrawal schedule setting screen, as a withdrawal schedule, the number of withdrawals per day is set, the day of the week for withdrawals is set, and whether or not the amount not withdrawn is carried over. It has an input field for inputting information related to the carry-forward setting for setting the amount and the amount setting for setting the amount. The input field for setting the number of times has a check box for selecting either once or multiple times per day, and an input field for the payout time zone that enables cash withdrawal, and the payout time zone is input. The column is provided with a pull-down menu that allows an arbitrary time to be selected as the start time and end time of the payout time zone. In the input field for setting the day of the week, a check box for selecting one of daily, weekly, and cycle, and any day of the week from Monday to Sunday can be selected as the selectable day of the week when weekly is selected. It has a check box that allows you to enter a withdrawal cycle (for example, once every two days or once every three days) when a cycle is selected. The input field of the carry-forward setting is a check box for selecting whether to withdraw (carry over) the amount that was not withdrawn (unpaid amount) at the time of withdrawal at the time of the next and subsequent withdrawals. , Has an input field in which the number of days that can be carried forward or the amount that can be carried forward (upper limit amount that can be carried forward) can be entered as the limit that can be carried forward when "can be carried forward and paid out" is selected. The input field for setting the amount of money has an input field in which the amount of money to be withdrawn at one time can be input. In addition, the withdrawal schedule setting screen is, for example, a detailed setting button for instructing execution of detailed settings that can set the withdrawal time zone and amount for each date, and the contents entered via the withdrawal schedule setting screen. It has a setting button for instructing the setting of the withdrawal schedule. The control unit 11 reads out the information on the withdrawal schedule setting screen stored in the storage unit 12 in advance, and uses the read screen information as the administrator ID, the user's name and user ID, the user's current balance, and the final payout execution. By adding the date and time, the withdrawal schedule setting screen shown in FIG. 6 is generated. When the withdrawal schedule has already been set for the user to be operated, the control unit 11 reads the withdrawal schedule of this user from the user information DB 12b, and inputs the information corresponding to the read withdrawal schedule. You may generate and display the withdrawal schedule setting screen in the state entered in the field. The withdrawal schedule setting screen is not limited to the configuration shown in FIG.

On the withdrawal schedule setting screen shown in FIG. 6, the administrator inputs the setting contents into each input field via the touch panel 13 (input unit 13b) according to the withdrawal schedule requested by the user or the user's family or the like. For example, when setting a withdrawal schedule with a withdrawal amount of 500 yen from 8:00 am to 6:00 pm once a day, the administrator can set the withdrawal amount to 1 per day in the input field for setting the number of times. Select the check box for times, enter 8:00 to 18:00 as the payout time zone, and enter 500 yen in the amount setting input field. Then, the administrator operates the setting button when instructing the setting (registration) of the withdrawal schedule with the input contents.

When the control unit 11 receives the setting contents (withdrawal conditions) related to the withdrawal schedule via the withdrawal schedule setting screen, the control unit 11 displays the received setting contents in each input field (S19). Then, the control unit 11 determines whether or not the withdrawal schedule setting instruction based on the input contents has been accepted by operating the setting button on the withdrawal schedule setting screen (S20), and determines that the withdrawal schedule setting instruction has not been accepted. If so (S20: NO), the process of step S19 is repeated. When it is determined that the setting instruction based on the input contents has been accepted (S20: YES), the control unit 11 (setting unit) stores the withdrawal schedule with the set contents input via the withdrawal schedule setting screen (S21). ). Specifically, the control unit 11 stores the input setting contents in the user information DB 12b as a withdrawal schedule corresponding to the user ID of the user to be set. After storing the withdrawal schedule, the control unit 11 includes the date and time at this time and the user ID of the user as the work history corresponding to the administrator ID of the administrator here, and the withdrawal schedule is set. The history information indicating that is stored in the administrator information DB 12a. Further, the control unit 11 may return to the display of the menu screen shown in FIG. 5C after the processing of step S21.

Although not shown, when the detailed setting button is operated on the withdrawal schedule setting screen, the control unit 11 displays the detailed schedule setting screen on the touch panel 13 and relates to the withdrawal schedule via the detailed schedule setting screen. Accepts detailed settings. The detailed schedule setting screen displays, for example, a calendar for one month, and has an input field for accepting input of a payout time zone and a payout amount for each date. The control unit 11 receives the setting contents for each date via the detailed schedule setting screen, and stores the withdrawal schedule with the set contents for each received date in the user information DB 12b.

When it is determined in step S17 that the withdrawal schedule setting instruction is not accepted (S17: NO), the control unit 11 confirms the deposit / withdrawal history to the user by operating the deposit / withdrawal history confirmation button on the menu screen. It is determined whether or not the processing execution instruction has been accepted (S22). When it is determined that the execution instruction of the deposit / withdrawal history confirmation process has been accepted (S22: YES), the control unit 11 (history display unit for the administrator) generates a deposit / withdrawal history screen as shown in FIG. 7A and touches the touch panel. It is displayed on 13 (S23). The deposit / withdrawal history screen shown in FIG. 7A shows the date and time and amount of cash withdrawn from the cash withdrawal device 10 (withdrawal history) by the user to be processed, and the date and time and amount of money deposited with the cash withdrawal device 10 corresponding to the user. (Payment history) and the balance at each date and time are displayed. The control unit 11 reads the deposit / withdrawal history stored in the user information DB 12b in association with the user ID of the user to be processed, generates a deposit / withdrawal history list, and displays the administrator ID and the user in the deposit / withdrawal history list. The deposit / withdrawal history screen shown in FIG. 7A is generated by adding the name and user ID, the current balance of the user, and the date and time of the last withdrawal execution. The deposit / withdrawal history screen is not limited to the configuration shown in FIG. 7A. After displaying the deposit / withdrawal history screen, the control unit 11 includes the date and time at this time and the user ID of the user as the work history corresponding to the administrator ID of the administrator here, and displays the deposit / withdrawal history screen. The history information indicating that the information has been lost is stored in the administrator information DB 12a.

The deposit / withdrawal history screen shown in FIG. 7A has a close button for instructing the end of the screen display, and the control unit 11 displays the deposit / withdrawal history screen when the close button of the deposit / withdrawal history screen is operated. The display is terminated, and the display is returned to, for example, the menu screen shown in FIG. 5C. The control unit 11 may be configured so that the deposit / withdrawal history screen can be transmitted to the printer via, for example, the communication unit 18, or may be configured to be transmitted to another device via the communication unit 18. good. With such a configuration, the deposit / withdrawal history screen can be displayed not only on the display unit 13a of the cash withdrawal device 10 but also printed on paper by a printer or transmitted to another device. In this case, the deposit / withdrawal history screen may have a print button for instructing printing of the screen and a sending button for instructing transmission of the screen.

When it is determined that the confirmation instruction of the deposit / withdrawal history is not accepted via the menu screen (S22: NO), the control unit 11 accepts the deposit acceptance instruction to the user by operating the deposit button on the menu screen. It is determined whether or not it is (S24). When it is determined that the payment acceptance instruction has been accepted (S24: YES), the control unit 11 displays the amount acceptance screen as shown in FIG. 7B on the touch panel 13 (S25). The amount reception screen shown in FIG. 7B has an input field for inputting an amount to be deposited in the cash withdrawal device 10 in association with the user to be processed, and an OK button for registering the amount input in the input field. Have. The administrator inputs the amount of cash deposited by the user or the user's family in the input field, and operates the OK button when instructing the registration of the input amount. The control unit 11 accepts the deposit amount via the amount acceptance screen (S26), and when the OK button is operated, the date and time at this point and the accepted amount are set as the deposit history corresponding to the user ID of the user to be processed. The payment history information including the payment history information is stored in the user information DB 12b (S27). After storing the deposit history, the control unit 11 includes the date and time at this time and the user ID of the user as the work history corresponding to the administrator ID of the administrator here, and history information indicating that the deposit has been made. Is stored in the administrator information DB 12a. Further, the administrator may collectively store cash in the cash payout device 10 when registering the deposit amount for each user or when registering the deposit amount for a plurality of users. Cash may be inserted into the cash storage unit from the batch insertion port 10a. When cash is inserted from the batch insertion port 10a, the control unit 11 determines the amount of the inserted cash by the denomination determination unit 16a, and the determined amount is the deposit amount registered by the administrator by the deposit process. It is determined whether or not they match, and if they match, the deposit process is completed. On the other hand, if the amount determined by the denomination determination unit 16a does not match the deposit amount, the control unit 11 may display an error message on the touch panel 13 to prompt the administrator for confirmation. Further, the control unit 11 displays the amount determined by the denomination determination unit 16a as the input amount on the touch panel 13 to prompt the administrator to confirm the input amount, and displays the deposit amount registered by the administrator by the deposit process. The input process may be completed after confirming that the input amount matches the input amount.

When it is determined that the payment acceptance instruction is not accepted via the menu screen (S24: NO), the control unit 11 skips the processes of steps S25 to S27 and ends the process. When the user information change button is operated in the management menu in the menu screen, the control unit 11 displays the user information change screen (not shown) and sets the operation target user via the user information change screen. Accepts information change instructions. For example, the user information change screen is configured to receive a user's vein data change instruction, and when the control unit 11 receives the vein data change instruction via the user information change screen, it is stored in the user information DB 12b. The biometric authentication data is updated to the received vein data. The user information change screen is configured to receive a change instruction for the user information stored in the user information DB 12b. When the administrator information change button is operated, the control unit 11 displays the administrator information change screen (not shown) and changes the setting information about the administrator being operated via the administrator information change screen. Accept instructions. For example, the administrator information change screen is configured to accept administrator authentication data such as passwords or vein data, or change instructions of the user in charge. When the control unit 11 receives the authentication data or the change instruction of the user in charge via the administrator information change screen, the control unit 11 receives the authentication data stored in the administrator information DB 12a and the user information in charge of the authentication. Update to the data and user ID of the user in charge. The administrator information change screen is configured to receive a change instruction for the administrator information stored in the administrator information DB 12a. Even when the user information and the administrator information are changed as described above, the control unit 11 includes the date and time at this time as the work history corresponding to the administrator ID of the administrator, and the processing contents are performed. The history information indicating the above is stored in the administrator information DB 12a.

By the above-mentioned process, the administrator can set and change the withdrawal schedule of the user in charge of himself / herself via the touch panel 13, can check the deposit / withdrawal history of each user, and can use the cash of each user. You can register for deposit. The administrator can operate the cash payout device 10 after being authenticated as an administrator having appropriate authority by an authentication process based on his / her own authentication data. Therefore, the administrator is safe with respect to the cash payout device 10. Sex can be secured.

Next, a process performed by the cash payout device 10 when the user receives cash payout from the cash payout device 10 will be described. FIG. 8 is a flowchart showing an example of a withdrawal processing procedure by the cash withdrawal device 10. The following processing is realized by the control unit 11 according to the control program 12P stored in the storage unit 12 of the cash payout device 10, but a part of the processing may be realized by a dedicated hardware circuit.

In the cash payout device 10 in the standby state, the control unit 11 determines whether or not the biometric data (here, vein data) has been acquired by the biometric authentication sensor 14 (S31), and determines that the biometric data has not been acquired. (S31: NO), wait until acquisition. In the standby state, the control unit 11 may display the login screen shown in FIG. 5A on the touch panel 13 and display or output a message prompting the reading of vein data. Further, when a light is provided in the vicinity of the biometric authentication sensor 14, the control unit 11 may notify the location of the biometric authentication sensor 14 and prompt the reading of vein data by turning on or blinking the light.

When it is determined that the vein data has been acquired by the biometric authentication sensor 14 (S31: YES), the control unit 11 (user authentication unit) authenticates the user based on the acquired vein data (S32). Here, the control unit 11 determines whether or not the acquired vein data matches any of the biometric authentication data stored in the user information DB 12b, and if it determines that they match, the user whose vein data matches. Is specified, and it is determined that the authentication is successful for the specified user. The control unit 11 determines whether or not the user authentication based on the vein data has succeeded (S33), and if it determines that the user authentication has failed (S33: NO), returns to the process of step S31. At this time, the control unit 11 may display or output a voice indicating that the user authentication has failed. When it is determined that the user authentication based on the vein data is successful (S33: YES), the control unit 11 can withdraw cash (withdrawal) at this point based on the withdrawal schedule of the authenticated user. It is determined whether or not there is (S34). Here, the control unit 11 reads the withdrawal schedule of the authenticated user from the user information DB 12b, determines whether or not the withdrawal at this point matches the timing according to the read withdrawal schedule. If they match, it is judged that withdrawal is possible. For example, if the withdrawal schedule is registered once a day and today's cash has already been paid out, the withdrawal at this point does not match the withdrawal schedule, so the control unit 11 Judge that withdrawal is not possible. Further, the control unit 11 reads the current balance of the user from the deposit / withdrawal history stored in the user information DB 12b, determines whether or not the read balance is less than the amount to be withdrawn, and the balance is withdrawn. If the amount is less than the planned amount, it may be determined that the withdrawal is not possible.

If it is determined that withdrawal is possible at this point (S34: YES), the control unit 11 (withdrawal unit) pays the amount of cash set in the withdrawal schedule by the cash withdrawal unit 15. Withdraw (withdraw) (S35). If there is unpaid money (cash that has not been paid out) by the previous withdrawal timing, the control unit 11 can withdraw money based on the unpaid amount and the set maximum carry-forward amount. The amount of money is calculated, and the calculated amount of cash is paid out by the cash payout unit 15. Then, the control unit 11 sets the withdrawal history information including the date and time at this time and the withdrawn amount as the withdrawal history corresponding to the user ID of the user who paid out the cash, that is, the user authenticated in step S32, in the user information DB 12b. (S36). If it is determined that withdrawal is not possible at this point (S34: NO), the control unit 11 displays a message indicating that withdrawal is not possible at this time on the touch panel 13 or outputs voice from the speaker 17 to withdraw money. Notify the user of the inability (S37). When notifying that withdrawal is not possible, the control unit 11 may specify the next possible withdrawal date and time from the user's withdrawal schedule and notify the specified date and time. For example, the control unit 11 may display or output a message such as "You can withdraw money at 1:00 pm today" or "Next time is 8:00 am tomorrow".

When the control unit 11 of the cash payout device 10 performs the above-mentioned process each time the biometric authentication sensor 14 acquires the vein data, and the user is authenticated by the authentication process based on the user's vein data. In addition, cash is paid out to the user. Therefore, the safety of the cash stored in the cash payout device 10 can be ensured, and the user can acquire the cash at the timing he / she wants, and can purchase the desired product with the acquired cash. Further, since the cash withdrawal process performed for each user is performed according to the withdrawal schedule set for each user, cash more than the amount set in the withdrawal schedule is not paid out. Therefore, there is no waste by the user. Further, since the withdrawal schedule can be set for each user, the cash withdrawal device 10 can be shared by a plurality of users. Further, since the administrator who manages the user's money may set the withdrawal schedule for each user, it is possible to reduce the work burden related to the money management.

(Embodiment 2)
A cash payout device 10 that allows a user to deposit his / her own cash in addition to the administrator will be described. Since the cash payout device 10 of the present embodiment has the same configuration as the cash payout device 10 of the first embodiment, the description of the configuration will be omitted. Further, the cash payout device 10 of the present embodiment executes the same process as the process shown in FIG. As a result, also in the cash withdrawal device 10 of the present embodiment, the administrator authenticated based on the authentication data sets and changes the withdrawal schedule of each user, confirms the deposit / withdrawal history of each user, and each You can deposit the user's cash. Further, the cash payout device 10 of the present embodiment executes the same process as the process shown in FIG. As a result, even in the cash payout device 10 of the present embodiment, cash can be paid out when the user is authenticated based on his / her own vein data. The cash payout device 10 of the present embodiment performs the following processes while performing the processes shown in FIGS. 4 and 8.

FIG. 9 is a flowchart showing an example of a deposit processing procedure by a user, and FIG. 10 is a schematic view showing a screen example. In the cash payout device 10 in the standby state, the control unit 11 determines whether or not the cash input from the cash input port 10b has been accepted by the cash reception unit 16 (S41), and when it is determined that the cash has not been accepted. (S41: NO) Waits while performing other processing until it is accepted. In the standby state, the control unit 11 may display the login screen shown in FIG. 5A on the touch panel 13 and display a message indicating that payment is possible on the touch panel 13, and output voice from the speaker 17. You may.

When it is determined that the cash inserted from the cash slot 10b has been accepted (S41: YES), the control unit 11 determines the amount of cash inserted from the cash slot 10b by the denomination determination unit 16a (S42). , As shown in FIG. 10, the determined amount of money is displayed on the touch panel 13 as the input amount (S43). Further, when the control unit 11 receives the cash inserted from the cash insertion slot 10b, the control unit 11 outputs authentication request information requesting user authentication necessary for registering the inserted cash for deposit (S44). For example, on the screen shown in FIG. 10, the control unit 11 displays the current input amount and prompts the user to read the vein data of the palm as a message prompting the user authentication, such as "Please hold the palm over the upper surface of the device". Display a message. The control unit 11 may output a message prompting the reading of vein data by voice as information requesting user authentication. Also here, when a light is provided in the vicinity of the biometric authentication sensor 14, the control unit 11 may notify the location of the biometric authentication sensor 14 and prompt the reading of vein data by turning on or blinking the light. good.

The control unit 11 determines whether or not biometric data (palm vein data) has been acquired by the biometric authentication sensor 14 (S45), and if it determines that the data has been acquired (S45: YES), the control unit 11 (user). The authentication unit) authenticates the user based on the acquired vein data (S46). The control unit 11 determines whether or not the user authentication based on the vein data is successful (S47), and if it is determined that the user authentication is successful (S47: YES), the control unit 11 determines the payment history corresponding to the user ID of the authenticated user. The payment history information including the date and time at this point and the amount of cash inserted is stored in the user information DB 12b (S48). As a result, the control unit 11 (addition unit) can add the input amount to the balance corresponding to the user who is operating.

The screen shown in FIG. 10 has a stop button for instructing the end (stop) of the deposit process for the cash inserted from the cash slot 10b, and the user who has inserted the cash wants to cancel the deposit process. , The stop button is operated via the input unit 13b. When the control unit 11 determines that the biometric data has not been acquired (S45: NO), for example, when the stop button on the screen shown in FIG. 10 is operated, or the user authentication based on the acquired vein data fails. If it is determined that the cash has been processed (S47: NO), the cash inserted from the cash input port 10b is discharged as it is to the payout tray 15a by the cash payout unit 15 (S49), and the process is terminated. If the user authentication fails, the control unit 11 may discharge the inserted cash and display or output a message indicating that the user authentication has failed.

By the above-described processing, in the cash withdrawal device 10 of the present embodiment, the user authenticated based on the vein data can perform not only the withdrawal processing but also the deposit processing. Further, the cash withdrawal device 10 of the present embodiment may be configured so that the user authenticated based on the vein data can confirm the deposit / withdrawal history for his / her own cash. For example, after the process of step S48 in FIG. 9, the control unit 11 displays an operation button on the touch panel 13 for instructing the display of the deposit / withdrawal history of the user authenticated based on the vein data, and this operation button operates. If so, the deposit / withdrawal history screen of the authenticated user may be generated and displayed on the touch panel 13. In this case, the user authenticated based on the vein data can check the deposit / withdrawal history in addition to the deposit / withdrawal process.

In this embodiment, the same effect as that of the first embodiment described above can be obtained. Further, in the present embodiment, the user can not only receive cash withdrawal from the cash withdrawal device 10 but also perform payment processing. As a result, for example, the change purchased from the product using the cash paid out from the cash payout device 10 can be returned to the cash payout device 10. Further, since the cash deposit / withdrawal history for the cash withdrawal device 10 is accumulated in the user information DB 12b, the deposit / withdrawal history of each user can be confirmed. When the cash withdrawal device 10 is configured so that the user himself / herself can confirm the deposit / withdrawal history, the user can confirm the deposit / withdrawal history made by himself / herself. Also in this embodiment, it is possible to apply the modification described as appropriate in the above-described first embodiment.

(Embodiment 3)
A cash payout device 10 that allows a user's family and the like to deposit the user's cash in addition to the administrator will be described. The person who deposits money in the cash payout device 10 is a guardian associated with the user, including the user's family, the user, the requester requested by the user's family, and the like. In the present embodiment, the persons who deposit money into the cash payout device 10 are collectively referred to as a user's family. Since the cash payout device 10 of the present embodiment has the same configuration as the cash payout device 10 of the first embodiment, the description of the configuration will be omitted. Since the user information DB 12b stored in the cash payout device 10 of the present embodiment is slightly different from the configuration of the first embodiment shown in FIG. 3B, only the different parts will be described.

FIG. 11 is a schematic diagram showing a configuration example of the user information DB 12b of the third embodiment. The user information DB 12b of the present embodiment has a family biometric authentication data string in addition to the configuration of the user information DB 12b shown in FIG. 3B. The family biometric data string stores biometric data (vein data) used when performing biometric authentication on each user's family. Therefore, the user information DB 12b of the present embodiment stores the authentication data of the user's family in addition to the information about the user in association with the user ID. The biometric authentication data of the family is stored by the control unit 11 when it is input via the biometric authentication sensor 14 when a new family is added corresponding to the user, and is stored via the input unit 13b or the communication unit 18. When the change is instructed, the change is made by the control unit 11 when the change is input via the biometric authentication sensor 14. In addition to being stored in the user information DB 12b, the family bioauthentication data may be stored in a predetermined area of the storage unit 12 or another storage device. In this case, the family bioauthentication data string is stored. Stores information (for example, file name) for reading each data.

The cash payout device 10 of the present embodiment having the above-described configuration executes the same process as the process shown in FIG. As a result, also in the cash withdrawal device 10 of the present embodiment, the administrator authenticated based on the authentication data sets and changes the withdrawal schedule of each user, confirms the deposit / withdrawal history of each user, and each You can deposit the user's cash. Further, the cash payout device 10 of the present embodiment executes the same process as the process shown in FIG. As a result, even in the cash payout device 10 of the present embodiment, cash can be paid out when the user is authenticated based on his / her own vein data. The cash payout device 10 of the present embodiment performs the following processing while performing the processing shown in FIGS. 4 and 8.

FIG. 12 is a flowchart showing an example of the deposit processing procedure in the third embodiment, and FIG. 13 is a schematic view showing a screen example. The process shown in FIG. 12 is obtained by adding steps S61 to S66 between NO in step S47 and step S49 in the process shown in FIG. The same steps as in FIG. 9 will be omitted. In the cash payout device 10 of the present embodiment, the control unit 11 performs the same processing as in steps S41 to S47 in FIG. When it is determined in step S47 that the user authentication is successful (S47: YES), the control unit 11 proceeds to the process of step S48 and stores the payment history information corresponding to the user ID of the authenticated user in the user information DB 12b. (S48).

When it is determined in step S47 that the user authentication has failed (S47: NO), the control unit 11 (guardian authentication unit) authenticates the user's family based on the vein data acquired in step S45 (S61). Here, the control unit 11 determines whether or not the acquired vein data matches any of the family biometric authentication data stored in the user information DB 12b, and if it determines that the vein data matches, the vein data matches. The family of the identified user is identified, and it is determined that the authentication is successful for the identified user's family. The control unit 11 determines whether or not the family authentication based on the vein data is successful (S62), and if it is determined that the authentication is unsuccessful (S62: NO), the process proceeds to the process of step S49, and the process proceeds from the cash slot 10b. The inserted cash is discharged as it is to the payout tray 15a by the cash payout unit 15 (S49). At this time, the control unit 11 may display or output a message indicating that both the user authentication and the family authentication have failed.

When it is determined that the family authentication based on the vein data is successful (S62: YES), the control unit 11 sets the deposit history corresponding to the user ID of the user whose family has been authenticated at the date and time at this time and the cash inserted. The payment history information including the amount of money and the authenticated family information (for example, name) is stored in the user information DB 12b (S63). As a result, the control unit 11 (addition unit) can add the amount of cash put in by the family to the balance for the user corresponding to the family. After that, the control unit 11 displays a family-use operation screen as shown in FIG. 13 on the touch panel 13 (S64). The operation screen for the family shown in FIG. 13 displays the user ID and name of the user whose family has been authenticated, and has a deposit / withdrawal history confirmation button for instructing the display of the deposit / withdrawal history corresponding to the user, and the user's withdrawal. It has a withdrawal schedule change button for instructing execution of the money schedule change process. The control unit 11 reads the user ID and name of the user whose family has been authenticated from the user information DB 12b, and reads the information on the operation screen for the family stored in the storage unit 12 in advance. Then, the control unit 11 adds the user ID and name of the user to the read screen information to generate the operation screen for the family shown in FIG. The operation screen for the family is not limited to the configuration shown in FIG.

The control unit 11 determines whether or not the display instruction of the deposit / withdrawal history has been accepted via the operation screen for the family (S65). When it is determined that the deposit / withdrawal history display instruction has been accepted (S65: YES), the control unit 11 (history display unit for parents) has a deposit / withdrawal history screen having the same configuration as the deposit / withdrawal history screen shown in FIG. 7A. Is generated and displayed on the touch panel 13 (S66). The deposit / withdrawal history screen here can have a configuration in which the administrator ID is deleted from the deposit / withdrawal history screen shown in FIG. 7A, and further, the depositor's information (for example, the name of the family member who made the deposit) can be added to the deposit history. ) May be included. Further, when the depositor is the administrator or the user himself / herself, the name of the administrator or the name of the user may be included in the deposit history as the information of the depositor. When it is determined that the display instruction of the deposit / withdrawal history is not accepted via the operation screen for the family (S65: NO), the control unit 11 skips the process of step S66 and ends the process. When the withdrawal schedule change button in the family operation screen is operated, the control unit 11 displays the withdrawal schedule change screen as shown in FIG. 6 on the touch panel 13 and uses the withdrawal schedule change screen. The withdrawal schedule may be changed by accepting the withdrawal schedule change instruction and changing the withdrawal schedule stored in the user information DB 12b. By the above-described processing, in the cash withdrawal device 10 of the present embodiment, the family of the user authenticated based on the vein data can confirm the cash deposit and deposit / withdrawal history to the user.

In this embodiment, the same effects as those in each of the above-described embodiments can be obtained. Further, in the present embodiment, the user's family can confirm the history of deposits to the cash withdrawal device 10 and the deposit / withdrawal processing by the cash withdrawal device 10. Therefore, by having each user's family perform the deposit processing and the confirmation processing of the deposit / withdrawal history corresponding to each user, it is possible to reduce the work burden on the employees and staff of the facility where the cash withdrawal device 10 is installed, and also to have financial troubles. Can be suppressed. Also in this embodiment, it is possible to apply the modifications described as appropriate in each of the above-described embodiments.

Since the cash payout device 10 of the present embodiment has a configuration of accepting payment to the user's family when the vein authentication is successful, only the family whose vein data is registered in advance can make the payment, and the cash payout device The safety at 10 can be ensured. In addition, since the family member who makes the deposit can specify the user to be deposited by holding his / her palm over the biometric authentication sensor 14, the operation is easy by holding the palm over after the cash is inserted. Further, the family ID and password may be used as the authentication data instead of the family vein data.

(Embodiment 4)
A cash withdrawal device capable of setting a withdrawal schedule for each user for the cash withdrawal device 10, confirming a deposit / withdrawal history corresponding to each user, and registering a deposit corresponding to each user via another device. 10 will be described. As a device capable of processing the cash payout device 10, for example, a terminal device composed of a smartphone, a tablet terminal, a personal computer, or the like can be used. FIG. 14 is a block diagram showing an example of internal configurations of the cash payout device 10 and the terminal device. Since the cash payout device 10 of the present embodiment has the same configuration as the cash payout device 10 of the first embodiment, the description of the cash payout device 10 will be omitted. Although not shown in FIG. 14, in the cash payout device 10 of the present embodiment, the storage unit 12 stores the control program 12P, the administrator information DB 12a, and the user information DB 12b, and the touch panel 13 stores the display unit 13a. And the input unit 13b, and the cash reception unit 16 has a denomination determination unit 16a.

The terminal device 20 includes a control unit 21, a storage unit 22, a communication unit 23, a display unit 24, an input unit 25, and the like, and each of these units is connected to each other via a bus. The control unit 21, storage unit 22, communication unit 23, display unit 24, and input unit 25 of the terminal device 20 are the control unit 11, storage unit 12, communication unit 18, display unit 13a, and input unit of the cash payout device 10. Since it can be realized by the same configuration as each part of 13b, detailed description thereof will be omitted. The display unit 24 and the input unit 25 of the terminal device 20 may be separately provided or may be a touch panel integrally configured. In addition to the control program 22P, the storage unit 22 of the terminal device 20 stores an operation application program 22AP (hereinafter referred to as an operation application 22AP) for operating the cash payout device 10.

In the present embodiment, the configuration in which the cash payout device 10 and the terminal device 20 transmit and receive information via the network N will be described as an example, but the cash payout device 10 and the terminal device 20 can be directly connected via, for example, a USB cable. It may be configured, for example, it may be configured to send and receive information by wireless communication by Bluetooth (registered trademark). In the case of a configuration in which the cash payout device 10 and the terminal device 20 can be directly connected via the USB cable, each of the cash payout device 10 and the terminal device 20 has a connection portion for connecting the USB cable. Then, by connecting the terminal device 20 to the cash payout device 10 via the USB cable, the administrator can operate the cash payout device 10 via the terminal device 20. Further, in the case of a configuration for performing wireless communication by Bluetooth, each of the cash payout device 10 and the terminal device 20 has an interface for performing wireless communication. Then, the administrator can operate the cash payout device 10 via the terminal device 20 by setting the pairing between the cash payout device 10 and the terminal device 20.

Hereinafter, in the present embodiment, the administrator operates the terminal device 20 to set various information for the user in the cash withdrawal device 10, a process for confirming the deposit / withdrawal history of the user, and a process for registering the deposit for the user. The processing performed by the cash payout device 10 and the terminal device 20 when performing the processing will be described. 15 and 16 are flowcharts showing an example of the setting processing procedure for the cash payout device 10. In FIGS. 15 and 16, the processing performed by the terminal device 20 is shown on the left side, and the processing performed by the cash payout device 10 is shown on the right side. The following processing is realized by the control unit 11 according to the control program 12P stored in the storage unit 12 of the cash payout device 10, and according to the control program 22P and the operation application 22AP stored in the storage unit 22 of the terminal device 20. It is realized by the control unit 21. Of the processes by the cash payout device 10 in FIG. 15, detailed description of the same processes as those by the cash payout device 10 shown in FIG. 4 will be omitted. A part of the following processing may be realized by a dedicated hardware circuit.

In the case where the cash payout device 10 and the terminal device 20 are directly connected via the USB cable, the administrator performs the following processing after connecting the terminal device 20 to the cash payout device 10 via the USB cable. I do. Further, in the case where the cash payout device 10 and the terminal device 20 perform wireless communication by Bluetooth, the administrator sets the pairing mode for the cash payout device 10 and the terminal device 20 to ON, thereby causing the cash payout device 10 and the terminal device 20 to perform wireless communication. After performing the pairing process between the 10 and the terminal device 20, the following process is performed.

In the present embodiment, the administrator can perform various operations on the cash payout device 10 via the operation application 22AP by activating the operation application 22AP on the terminal device 20. When the control unit 21 of the terminal device 20 receives the execution instruction of the operation application 22AP via the input unit 25, the control unit 21 executes the operation application 22AP and displays a login screen as shown in FIG. 5A as the initial screen. Is displayed in (S81). The login screen here has a configuration in which the biometric data reading button is deleted from the login screen shown in FIG. 5A. The administrator inputs his / her own login ID (administrator ID) and password from the input unit 25 on the login screen displayed on the terminal device 20 and operates the login button to operate the cash withdrawal device via the terminal device 20. Instructs the execution of the login process for 10.

The control unit 21 of the terminal device 20 determines whether or not the login ID and password (administrator authentication data) have been acquired via the login screen (S82), and when it is determined that the login ID and password (administrator authentication data) have not been acquired (S82). S82: NO), wait until it is acquired. When the control unit 21 determines that the administrator's authentication data has been acquired (S82: YES), the control unit 21 transmits the acquired authentication data from the communication unit 23 to the cash payout device 10 (S83). When the control unit 11 of the cash payout device 10 receives the authentication data of the administrator via the communication unit 18, the control unit 11 authenticates the administrator based on the received authentication data (S84). Here, the control unit 11 performs the same processing as in step S12 in FIG. Specifically, the control unit 11 succeeds in authentication when the received password matches the authentication data (password) stored in the administrator information DB 12a in association with the received login ID (administrator ID). Judge.

The control unit 11 determines whether or not the administrator authentication based on the administrator authentication data received from the terminal device 20 is successful (S85), and if it is determined to be unsuccessful (S85: NO), the authentication fails. Information indicating that this has been done (authentication failure) is transmitted from the communication unit 18 to the terminal device 20 (S86). When the control unit 21 of the terminal device 20 receives the information indicating the authentication failure from the cash payout device 10 via the communication unit 23, the control unit 21 notifies the administrator by displaying the received information on the display unit 24, for example (S87). ). When the control unit 11 of the cash payout device 10 determines that the administrator authentication is successful (S85: YES), for example, as shown in FIG. 5B, the control unit 11 generates a list screen of users in charge of the authenticated administrator (S88). ), The generated user list screen is transmitted from the communication unit 18 to the terminal device 20 (S89).

When the control unit 21 of the terminal device 20 receives the user list screen from the cash payout device 10 via the communication unit 23, the control unit 21 displays the received user list screen on the display unit 24 (S90). As a result, the user list screen as shown in FIG. 5B is displayed on the display unit 24 of the terminal device 20. On the displayed user list screen, the control unit 21 determines whether or not the selection for any user has been accepted (S91), and if it determines that the selection has not been accepted (S91: NO), waits until the selection is accepted. When it is determined that the selection for any of the users has been accepted (S91: YES), the control unit 21 displays a menu screen as shown in FIG. 5C on the display unit 24 in response to the selected user (S92). .. The menu screen here may have a configuration in which the user's current balance and the final payout execution date and time are deleted from the menu screen shown in FIG. 5C. Further, the control unit 21 may generate the menu screen shown in FIG. 5C by acquiring the user's current balance and the final payout execution date and time from the cash payout device 10.

The control unit 21 determines whether or not the execution instruction of the withdrawal schedule setting process for the user has been accepted via the displayed menu screen (S93), and when it is determined that the instruction has been accepted (S93: YES), FIG. The withdrawal schedule setting screen as shown is displayed on the display unit 24 (S94). The withdrawal schedule setting screen here may have a configuration in which the user's current balance and the final withdrawal execution date and time are deleted from the withdrawal schedule setting screen shown in FIG. Further, the control unit 21 may generate the withdrawal schedule setting screen shown in FIG. 6 by acquiring the user's current balance and the final withdrawal execution date and time from the cash withdrawal device 10.

When the control unit 21 receives the setting contents related to the withdrawal schedule from the input unit 25 via the withdrawal schedule setting screen, the control unit 21 displays the received setting contents in each input field (S95). Then, the control unit 21 determines whether or not the withdrawal schedule setting instruction based on the input contents has been accepted by operating the setting button on the withdrawal schedule setting screen (S96), and determines that the withdrawal schedule setting instruction has not been accepted. If so (S96: NO), the process of step S95 is repeated. When it is determined that the setting instruction in the input contents has been accepted (S96: YES), the control unit 21 transfers the withdrawal schedule indicated by the set contents received via the withdrawal schedule setting screen from the communication unit 23 to the cash withdrawal device 10. Send (S97). When the control unit 11 of the cash payout device 10 receives the withdrawal schedule from the terminal device 20, the control unit 11 stores the received withdrawal schedule (setting contents) in the user information DB 12b in association with the user ID of the user to be set. (S98). As a result, the withdrawal schedule for the user input via the terminal device 20 can be registered in the cash withdrawal device 10. Here, too, the control unit 11 stores the withdrawal schedule, and then includes the date and time at this time and the user ID of the user to be set as the work history corresponding to the administrator ID of the administrator who set the withdrawal schedule. The history information indicating that the gold schedule has been set is stored in the administrator information DB 12a.

If it is determined in step S93 that the withdrawal schedule setting instruction has not been accepted (S93: NO), the control unit 11 determines whether or not the execution instruction of the deposit / withdrawal history confirmation process has been accepted via the menu screen. (S99). When it is determined that the execution instruction of the deposit / withdrawal history confirmation process has been accepted (S99: YES), the control unit 11 requests the cash withdrawal device 10 for the deposit / withdrawal history screen of the user to be processed (S100). When the control unit 11 of the cash withdrawal device 10 receives the request for the deposit / withdrawal history screen from the terminal device 20, the control unit 11 reads the requested deposit / withdrawal history of the user from the user information DB 12b, and the deposit / withdrawal history screen as shown in FIG. 7A. Is generated (S101). Then, the control unit 11 transmits the generated deposit / withdrawal history screen from the communication unit 18 to the terminal device 20 (S102). When the control unit 21 of the terminal device 20 receives the deposit / withdrawal history screen from the cash withdrawal device 10, the control unit 21 displays the received deposit / withdrawal history screen on the display unit 24 (S103). As a result, the history of deposit / withdrawal processing for the user performed by the cash withdrawal device 10 can be confirmed by the terminal device 20.

When it is determined that the deposit / withdrawal history confirmation instruction is not accepted via the menu screen (S99: NO), the control unit 21 determines whether or not the deposit acceptance instruction to the user has been accepted (S104). When it is determined that the payment acceptance instruction has been accepted (S104: YES), the control unit 21 displays the amount acceptance screen as shown in FIG. 7B on the display unit 24 (S105). The amount reception screen here may have a configuration in which the user's current balance and the final payout execution date and time are deleted from the amount reception screen shown in FIG. 7B. Further, the control unit 21 may generate the amount acceptance screen shown in FIG. 7B by acquiring the user's current balance and the final payout execution date and time from the cash payout device 10.

The control unit 21 receives the deposit amount via the input unit 25 on the amount reception screen (S106), and when the OK button on the amount reception screen is operated, the received amount and the user are used as the payment information of the user to be processed. The ID is transmitted to the cash payout device 10 (S107). When the control unit 11 of the cash payout device 10 receives the payment information from the terminal device 20 via the communication unit 18, the control unit 11 includes the date and time at this time and the received amount as the payment history corresponding to the received user ID. The information is stored in the user information DB 12b (S108). As a result, the deposit amount for the user input via the terminal device 20 can be registered in the cash withdrawal device 10. Here, too, the control unit 11 stores the deposit history, and then includes the date and time at this time and the user ID of the user as the work history corresponding to the administrator ID of the administrator who performed the deposit process, and the deposit is made. The history information indicating the above is stored in the administrator information DB 12a. Even if the administrator registers the deposit amount for each user by the above-mentioned process or registers the deposit amount for a plurality of users, the administrator can collectively store the cash in the cash withdrawal device 10. Often, at this time, cash may be inserted into the cash storage unit from the batch insertion port 10a. Again, when cash is inserted from the batch insertion port 10a, the control unit 11 determines the amount of the inserted cash by the denomination determination unit 16a, and the determined amount is deposited via the terminal device 20. It is determined whether or not it matches the instructed deposit amount, and if it matches, the deposit process is completed. On the other hand, when the amount determined by the denomination determination unit 16a does not match the deposit amount, the control unit 11 displays an error message on the touch panel 13 or sends an error message to the terminal device 20 to prompt the administrator for confirmation. You may. Further, the control unit 11 displays the amount determined by the denomination determination unit 16a as the input amount on the touch panel 13 or transmits it to the terminal device 20 to prompt the administrator to confirm the input amount, and the administrator registers the input amount by the deposit process. The input process may be completed after confirming that the deposit amount and the displayed input amount match.

When it is determined that the payment acceptance instruction is not accepted via the menu screen (S104: NO), the control unit 21 skips the processes of steps S105 to S107 and ends the process. By the above-described processing, the administrator can set and change the withdrawal schedule of the user in charge of himself / herself, confirm the deposit / withdrawal history of each user, and register the deposit to each user from the terminal device 20. Also in this embodiment, the administrator can operate the cash payout device 10 after being authenticated to have appropriate authority based on his / her own authentication data, so that the safety of the cash payout device 10 can be improved. Can be secured.

The cash payout device 10 of the present embodiment having the above-described configuration executes the same process as the process shown in FIG. As a result, even in the cash payout device 10 of the present embodiment, when the user is authenticated based on his / her own vein data, cash is paid out to the user. Therefore, in this embodiment, the same effect as that of each of the above-described embodiments can be obtained. Further, in the present embodiment, the terminal device 20 can perform various setting processes for the cash payout device 10, confirmation process of deposit / withdrawal history corresponding to each user, and registration process of deposit corresponding to each user. As a result, the administrator does not have to go to the installation location of the cash payout device 10 when performing these processes, and the work load can be reduced. Further, even when the cash payout device 10 is installed in a large-scale facility and a plurality of managers are dispersed in a plurality of work places, each manager can use the terminal device 20 from his / her own work place. Since the cash payout device 10 can be processed via the above, the efficiency of business can be improved. Also in this embodiment, it is possible to apply the modifications described as appropriate in each of the above-described embodiments. Further, the configuration of the present embodiment can be applied to the cash payout device 10 of the second to third embodiments, and the same effect can be obtained even when applied to the cash payout device 10 of the second to third embodiments. ..

(Embodiment 5)
A cash payout device 10 having a configuration for monitoring the state of the cash payout device 10 and notifying when an abnormality occurs will be described. FIG. 17 is a block diagram showing an example of the internal configuration of the cash payout device 10 according to the fifth embodiment. The cash payout device 10 of the present embodiment has a sensor 31, a notification unit 32, and a camera 33 in addition to the configuration of the first embodiment shown in FIG. The description of the same configuration as that of the first embodiment will be omitted.

The sensor 31 is, for example, any sensor such as an acceleration sensor, a geomagnetic sensor, an inclination sensor, a vibration sensor, a GPS (Global Positioning System), or a combination of a plurality of sensors, such as impact and vibration applied to the cash payout device 10. Is detected. The sensor 31 constantly performs detection processing, and each time the detection processing is performed, a detection signal indicating the detection result may be sent to the control unit 11, and when the detection result changes, the detection signal is sent to the control unit. It may be sent to 11.

The notification unit 32 includes a lamp, a rotating light, a buzzer, and the like, and by turning on or blinking the lamp, turning on the rotating light, ringing the buzzer, and the like, a predetermined situation (for example,) is given to a person around the cash payout device 10. Notify the occurrence of an abnormality). The notification unit 32 realizes the notification process by performing a predetermined process in accordance with the instruction from the control unit 11. Further, the notification unit 32 may perform the notification processing using the display unit 13a or the speaker 17, or may be configured to perform the notification processing by displaying the notification message on the display unit 13a and outputting the notification message by the voice of the speaker 17.

The camera 33 is an image pickup apparatus having a lens, an image pickup device, and the like, and acquires image data of a subject image through the lens. The camera 33 may be provided, for example, so that the front side of the cash payout device 10 can be photographed, or may be configured so that the periphery of the cash payout device 10 can be photographed by using a wide-angle lens or the like. The camera 33 performs a shooting process according to an instruction from the control unit 11, and sequentially sends the acquired image data (photographed image) to the storage unit 12 for storage. The camera 33 may have a configuration built in the cash payout device 10 or an external configuration in the cash payout device 10. In this case, the cash payout device 10 includes a connection unit to which an external camera can be connected or a wireless communication unit capable of wireless communication with the external camera, and image data taken by the external camera is transmitted via the connection unit or the wireless communication unit. To get. The camera 33 may be provided as a sensor 31 (image sensor).

The cash payout device 10 of the present embodiment executes the same process as the process shown in FIGS. 4 and 8. As a result, also in the cash withdrawal device 10 of the present embodiment, the administrator can set and change the withdrawal schedule of each user, check the deposit / withdrawal history of each user, and deposit the cash of each user. In addition, the user can receive cash withdrawal when the user is authenticated based on his / her vein data. The cash payout device 10 of the present embodiment performs the following processing while performing the processing shown in FIGS. 4 and 8.

FIG. 18 is a flowchart showing an example of the monitoring processing procedure by the cash payout device 10. The following processing is realized by the control unit 11 according to the control program 12P stored in the storage unit 12 of the cash payout device 10, but a part of the processing may be realized by a dedicated hardware circuit. In the cash payout device 10 of the present embodiment, the control unit 11 (detection unit) has applied some kind of impact, vibration, or the like to the cash payout device 10 based on the detection signal sent from the sensor 31, or cash payout. It is determined whether or not an abnormality has occurred, such as that the device 10 is moving (S111). When the control unit 11 determines that no abnormality has occurred (S111: NO), the control unit 11 repeats the process of step S111.

When it is determined that an abnormality has occurred (S111: YES), the control unit 11 performs notification processing by the notification unit 32 (S112). For example, the control unit 11 turns on or blinks the lamp when the notification unit 32 has a lamp, turns on the rotating light when the notification unit 32 has a rotating light, and turns on the rotating light when the notification unit 32 has a buzzer. Sounds. As a result, when an abnormality occurs in the cash payout device 10, it is possible to notify the surrounding people of the occurrence of the abnormality. Further, the control unit 11 may notify the occurrence of an abnormality by displaying the notification message on the display unit 13a or outputting the notification message by the speaker 17.

Further, the control unit 11 performs a shooting process by the camera 33 (S113). As a result, when an abnormality occurs in the cash payout device 10, the surrounding state of the cash payout device 10 can be photographed and recorded. Further, the control unit 11 performs a process of storing the detection signal transmitted from the sensor 31 in the storage unit 12 (S114). As a result, when an abnormality occurs in the cash payout device 10, the state of the cash payout device 10 detected by the sensor 31 can be recorded. The control unit 11 may be configured to constantly perform a process of storing the detection signal in the storage unit 12 as well as when an abnormality occurs in the cash payout device 10. By the above-described processing, the cash payout device 10 of the present embodiment can notify the surrounding people when any abnormality occurs, can record the surroundings of the cash payout device 10, and can record the surroundings of the cash payout device 10. The detection result of the state can be recorded.

In this embodiment, the same effects as those in each of the above-described embodiments can be obtained. Further, in the present embodiment, since it is possible to notify the surrounding people that an abnormality has occurred in the cash payout device 10, the administrator or the like can grasp the occurrence of the abnormality at an early stage. Therefore, it is possible to solve the abnormality generated in the cash payout device 10 at an early stage. Abnormalities that occur in the cash payout device 10 include, for example, theft or damage to the cash payout device 10, when a user or the like falls down while operating the cash payout device 10, or traffic near the cash payout device 10. It also includes the case where a shock is applied to the cash payout device 10 when a person falls down. Therefore, in such a case, it is possible to quickly deal with the fallen user or the like. Further, in the present embodiment, since the surrounding image after the abnormality occurs in the cash payout device 10 and the detection signal by the sensor 31 are accumulated, the status of the abnormality that has occurred in the cash payout device 10 can be determined by using this information. It becomes possible to grasp. Therefore, it is possible to smoothly solve the abnormality that has occurred in the cash payout device 10.

In the present embodiment, the cash payout device 10 may be configured to notify a predetermined device of the occurrence of an abnormality when an abnormality occurs. For example, the destination information of a predetermined device is stored in the storage unit 12, and when the control unit 11 determines that an abnormality has occurred, the control unit 11 uses the stored destination information to specify a message indicating the occurrence of the abnormality. It may be transmitted to the device of. With such a configuration, when an abnormality occurs in the cash payout device 10, it is possible to transmit the information of the current location (longitude and latitude information) determined by the GPS of the sensor 31 to a predetermined device. Therefore, for example, when the cash payout device 10 is stolen and carried out, the cash payout device 10 can be tracked, which can contribute to the early resolution of the theft case. Also in this embodiment, it is possible to apply the modifications described as appropriate in each of the above-described embodiments. Further, the configuration of the present embodiment can be applied to the cash payout device 10 of the second to fourth embodiments, and the same effect can be obtained even when applied to the cash payout device 10 of the second to fourth embodiments. ..

(Embodiment 6)
In the cash payout device 10 of the above-described first to fifth embodiments, the cash payout device 10 having further other functions will be described. The cash payout device 10 of the present embodiment pays cash inside the device based on the storage balance for each denomination stored in the device and the planned payout amount for each denomination based on the withdrawal schedule of each user. It has a function to determine whether or not it is necessary to exchange money. Further, the cash withdrawal device 10 of the present embodiment is the total amount of the cash storage balance stored in the device and the balance of each user (hereinafter referred to as the book balance) calculated based on the deposit / withdrawal history of each user. It has a balance matching function to check whether or not the items match. Since the cash payout device 10 of the present embodiment has the same configuration as the cash payout device 10 of the first embodiment, the description of the configuration will be omitted. Further, the cash payout device 10 of the present embodiment can execute the same processing as the processing shown in FIGS. 4 and 8, and performs the following processing while performing the processing shown in FIGS. 4 and 8.

FIG. 19 is a flowchart showing an example of the exchange necessity determination processing procedure. In the cash payout device 10 of the present embodiment, the control unit 11 manages the total amount (storage balance) of each denomination of cash stored in the cash storage unit, and stores the storage balance for each denomination 12 I remember in. Further, the control unit 11 determines the total amount of cash for each denomination for cash to be paid out to each user within a predetermined period such as 3 days or 1 week based on the withdrawal schedule set for each user. The planned payout amount) is managed, and the planned payout amount for each denomination is stored in the storage unit 12. The control unit 11 may manage the planned payout amount for each denomination for one day.

The control unit 11 determines whether or not the cash input from the batch input port 10a or the cash input port 10b is stored in the cash storage unit by, for example, the administrator, the user himself or the user's family performing the deposit processing. Yes (S121). When it is determined that the inserted cash has been stored (S121: YES), the control unit 11 (calculation unit) stores the amount of the stored cash for each denomination (input amount) for each denomination at this point. Add to the balance (S122). The control unit 11 stores the storage balance for each denomination after addition in the storage unit 12. As a result, the control unit 11 can update the storage balance (total amount) for each denomination of cash stored in the cash payout device 10 each time the cash is stored in the cash payout device 10. After updating the storage balance for each denomination, the control unit 11 determines the storage balance for each denomination after the update and the planned payout amount for each denomination stored in the storage unit 12 at this time. It is determined whether or not the planned payout amount can be paid out (S123). Here, the control unit 11 determines whether or not the storage balance is equal to or greater than the planned payout amount for each denomination, determines that the denomination whose storage balance is equal to or greater than the planned payout amount can be paid out, and stores the denomination. It is determined that the denomination whose balance is less than the planned payout amount cannot be paid out and needs to be exchanged. That is, the control unit 11 (specific unit) specifies the denomination that needs to be exchanged based on the storage balance and the planned payout amount for each denomination.

When the control unit 11 determines that the payout is possible for all denominations (S123: YES), the processing is completed, and when it is determined that the payout is not possible for any of the denominations (S123: NO), the exchange is performed. Notify that it is necessary (S124). For example, the control unit 11 notifies by displaying a message indicating that there is a denomination requiring exchange on the touch panel 13 or outputting voice from the speaker 17. Further, the control unit 11 may notify that exchange is necessary by the notification process by the notification unit 32. Further, when the cash payout device 10 is configured to transmit the notification information to the predetermined device, the control unit 11 may transmit a message indicating that there is a denomination requiring exchange to the predetermined device. good.

When it is determined that the cash is not stored (S121: NO), the control unit 11 determines whether or not the cash withdrawal unit 15 has paid out the cash by performing the withdrawal process (S125). When it is determined that the cash has been paid out (S125: YES), the control unit 11 (calculation unit) calculates the amount (withdrawal amount) of the paid out cash for each denomination from the storage balance for each denomination at this time. Subtraction (S126) is performed, and the storage balance for each denomination after subtraction is stored in the storage unit 12. As a result, the control unit 11 can update the storage balance (total amount) for each denomination of cash stored in the device each time the cash payout device 10 pays out cash. After updating the storage balance for each denomination, the control unit 11 shifts to the process of step S123, and the storage balance for each denomination after the update and each denomination stored in the storage unit 12 at this time Based on the planned payout amount, it is determined whether or not the planned payout amount can be paid out (S123).

When it is determined that cash has not been paid out (S125: NO), the control unit 11 withdraws from one of the users, for example, by setting or changing the withdrawal schedule of the user by the administrator or the user's family. It is determined whether or not the schedule has been changed (S127). When it is determined that the withdrawal schedule of any user has been changed (S127: YES), the control unit 11 (scheduled withdrawal amount calculation unit) is set for each denomination within a predetermined period based on the changed withdrawal schedule. The amount to be paid out is calculated (S128). For example, the control unit 11 adds or subtracts the amount of increase or decrease for each denomination to be paid out within a predetermined period due to the change of the withdrawal schedule to the amount to be paid out for each denomination at this time. Update the planned payout amount for each species. The control unit 11 stores the planned payout amount for each denomination after addition in the storage unit 12. As a result, the control unit 11 can update the scheduled payout amount for each denomination scheduled to be paid out within a predetermined period each time the withdrawal schedule of each user is changed. After updating the planned payout amount for each denomination, the control unit 11 shifts to the process of step S123, and the updated planned payout amount for each denomination and the denomination stored in the storage unit 12 at this time. Based on the storage balance for each, it is determined whether or not the planned payout amount can be paid out (S123). If it is determined that the withdrawal schedule of any user has not been changed (S127: NO), the control unit 11 returns to the process of step S121.

By the above-described processing, in the cash payout device 10 of the present embodiment, the storage balance for each denomination is calculated each time the cash stored in the cash payout device 10 increases (deposits) or decreases (pays out), and each user. Each time the withdrawal schedule is changed, the planned withdrawal amount for each denomination to be paid out during the predetermined period is calculated. Whether or not the planned payout amount for each denomination to be paid out within the predetermined period is insufficient based on the storage balance for each denomination calculated in this way and the planned payout amount for each denomination in the predetermined period. Can be managed and can be notified that exchange is required if there is a shortage.

In the cash payout device 10 of the present embodiment, the control unit 11 calculates how many days later the payout will not be possible based on the storage balance for each denomination and the planned payout amount for each denomination for one day. May be notified. In this case, the administrator can grasp the timing when the exchange is necessary. Further, the cash payout device 10 of the present embodiment is provided with a currency exchange mode so that when the currency exchange mode is selected, the banknotes stored in the cash storage unit are discharged from the cash slot 10b. May be good. According to such a configuration, for example, when the administrator inserts 10 100-yen coins from the cash slot 10b and instructs to exchange them for 1000-yen banknotes, the control unit 11 stores them in the cash storage unit. The exchange process is completed by discharging the existing 1000-yen bill from the cash slot 10b at the cash payout unit 15. In this case, since the exchange process can be performed via the cash slot 10b on the front side of the cash payout device 10, the administrator can easily exchange money without opening and closing the key of the batch slot 10a.

FIG. 20 is a flowchart showing an example of the balance collation processing procedure. In the process shown in FIG. 20, the control unit 11 of the cash payout device 10 manages the total amount of cash (storage balance) stored in the cash storage unit, and stores the storage balance (total storage amount) in the storage unit 12. doing. Further, the control unit 11 manages the balance (book balance) of each user based on the history of deposit / withdrawal processing for each user, and stores the total amount of the book balance of each user in the storage unit 12. The control unit 11 may store the book balance for each user in the storage unit 12.

Similar to step S121 in FIG. 19, the control unit 11 determines whether or not the cash inserted from the batch input port 10a or the cash input port 10b is stored in the cash storage unit (S131). When it is determined that the inserted cash has been stored (S131: YES), the control unit 11 (storage amount calculation unit) uses the stored cash amount (input amount) as the storage balance (total storage amount) at this point. Add (S132). The control unit 11 can update the total amount of cash (storage balance) stored in the cash payout device 10 each time the cash is stored in the cash payout device 10 by storing the storage balance after the addition in the storage unit 12. .. After updating the storage balance, the control unit 11 (judgment unit) determines whether or not the updated storage balance matches the total amount of the book balances of each user stored in the storage unit 12 at this time. Judgment (S133).

When the control unit 11 determines that the updated storage balance and the total amount of the book balances of each user match (S133: YES), ends the process and determines that they do not match (S133: NO). Mismatch information including the difference between the date and time at the time point and the total amount of the storage balance and the book balance is stored in the storage unit 12 (S134). Then, the control unit 11 notifies that the total amount of the storage balance and the book balance does not match (S135). For example, the control unit 11 notifies by displaying a message indicating that the total amount of the stored balance and the book balance does not match on the touch panel 13 or outputting the voice from the speaker 17. Further, the control unit 11 may notify that the total amount of the storage balance and the book balance does not match by the notification process by the notification unit 32. Further, when the cash payout device 10 is configured to transmit the notification information to the predetermined device, the control unit 11 sends a message to the predetermined device indicating that the total amount of the storage balance and the book balance does not match. You may send it.

When it is determined that the cash is not stored (S131: NO), the control unit 11 determines whether or not the cash withdrawal unit 15 has paid out the cash by performing the withdrawal process (S136). When it is determined that the cash has been paid out (S136: YES), the control unit 11 (storage amount calculation unit) subtracts the paid out cash amount (withdrawal amount) from the storage balance at this point (S137). The stored balance after subtraction is stored in the storage unit 12. As a result, the control unit 11 can update the cash storage balance (total amount) stored in the cash payout device 10 each time the cash payout device 10 pays out cash. Further, the control unit 11 (balance calculation unit) subtracts the amount of cash paid out (withdrawal amount) from the total amount of the book balance at this point (S138), and stores the subtracted book balance in the storage unit 12. Remember. As a result, the control unit 11 can update the total amount of the book balance that changes based on the withdrawal processing of each user each time the cash withdrawal device 10 pays out cash. After updating the total amount of the book balance, the control unit 11 proceeds to the process of step S133, and the total amount of the updated book balance matches the storage balance stored in the storage unit 12 at this time. Whether or not it is determined (S133).

When it is determined that the cash has not been paid out (S136: NO), the control unit 11 determines whether or not the user's deposit processing (payment registration) has been performed by, for example, the administrator or the user's family (S139). When it is determined that the deposit processing of any user has been performed (S139: YES), the control unit 11 (balance calculation unit) sets the amount (deposit amount) deposited by the deposit processing as the book balance at this point. It is added to the total amount (S140), and the book balance after the addition is stored in the storage unit 12. As a result, the control unit 11 can update the total amount of the book balance that changes based on the deposit processing of each user each time the deposit is registered for any user. After updating the total amount of the book balance, the control unit 11 proceeds to the process of step S133, and the total amount of the updated book balance matches the storage balance stored in the storage unit 12 at this time. Whether or not it is determined (S133). If it is determined that the payment has not been registered for any of the users (S139: NO), the control unit 11 returns to the process of step S131.

By the above-described processing, in the cash payout device 10 of the present embodiment, the storage balance is calculated each time the cash stored in the cash payout device 10 increases (deposits), and the stored cash decreases (pays out) each time. , The total amount of the storage balance and the book balance of each user is calculated, and the total amount of the book balance of each user is calculated each time the payment process of each user is performed. Based on the total amount of the storage balance and the book balance calculated in this way, the balance of cash actually stored in the cash withdrawal device 10 and the balance on the book based on the deposit / withdrawal processing of each user match. You can manage whether or not to do it, and if it does not match, you can notify that it does not match.

In the cash payout device 10 of the present embodiment, when the control unit 11 determines in step S133 that the updated storage balance and the total amount of the book balances of each user match (S133: YES), the date and time at this time. And, the matching information indicating that the total amount of the storage balance and the book balance matches may be stored in the storage unit 12. In this case, the match information and the mismatch information can be accumulated, and it is possible to analyze at what point in time the mismatch occurs. Further, the control unit 11 is configured to periodically perform balance matching processing based on the current storage balance stored in the storage unit 12 and the total amount of the current book balance, and accumulate the processing results at any time. You may be.

Further, in the cash payout device 10 of the present embodiment, the control unit 11 may execute the process of FIG. 19 and the process of FIG. 20 together. For example, when the control unit 11 determines that the inserted cash has been stored in the cash storage unit (S121, S131: YES), the control unit 11 performs the process of step S122 and the process of step S132, and then the process of step S123. The process of step S133 may be performed. When the control unit 11 determines that the cash has been paid out (S125, S136: YES), the control unit 11 performs the processing of step S126 and the processing of steps S137 to S138, and then performs the processing of step S123 and the processing of step S133. You may go. Further, when the control unit 11 determines in step S127 that the withdrawal schedule of any user has not been changed (S127: NO), the control unit 11 may perform the processes after step S139.

In this embodiment, the same effects as those in each of the above-described embodiments can be obtained. Further, in the present embodiment, since it is possible to notify when it is necessary to exchange cash inside the device, the administrator can grasp the balance for each denomination inside the device. Therefore, the administrator does not need to check the balance of each denomination stored in the device, and may perform the exchange when notified that the exchange is necessary. Further, in the present embodiment, it is possible to collate whether or not the balance of cash actually stored in the device and the total amount of the balance on the books of each user match, and if they do not match, it is possible to notify. , The manager can grasp the discrepancy of the balance at an early stage. Therefore, the administrator does not need to confirm whether or not the balance stored in the device and the total amount of the balance on the books of each user match. As described above, the cash payout device 10 of the present embodiment can reduce the work burden of the administrator. Also in this embodiment, it is possible to apply the modifications described as appropriate in each of the above-described embodiments. Further, the configuration of the present embodiment can be applied to the cash payout device 10 of the second to fifth embodiments, and the same effect can be obtained even when applied to the cash payout device 10 of the second to fifth embodiments. ..

In each of the above-described embodiments, the cash withdrawal device includes various setting processes and deposit processes performed on the cash withdrawal device 10, withdrawal processing performed by the cash withdrawal device 10, output processing of deposit / withdrawal history of each user, and the like. The history information of various processes in No. 10 may be configured to be periodically transmitted to a predetermined device. For example, the history of the withdrawal schedule setting process performed on the cash payout device 10 once a day (information on the set time, the user to be set and the setting contents), and the history of the deposit process performed on the cash payout device 10. (Information on deposit time, user to be deposited and deposit amount), history of withdrawal processing performed by cash withdrawal device 10 (information on withdrawal time and withdrawal user), various types performed on cash withdrawal device 10. The history of the setting process (information on the set time and the set contents) and the like may be configured to be transmitted to a predetermined device. In this case, the manager of the cash payout device 10 can periodically check various processing contents of the cash payout device 10 with a predetermined device.

Further, in each of the above-described embodiments, the notification destination device is registered in advance for each user, and the history of various setting processes performed for each user and the deposit / withdrawal history of each user are periodically transmitted to the notification destination device. It may be configured to do so. For example, once a month, the history of withdrawal processing performed by the user, the history of deposit processing performed in response to the user, the setting contents set for the user, etc. are transmitted to the notification destination device. It may be configured. In this case, the user's family can confirm the withdrawal status and the deposit status from the cash withdrawal device 10 by the user, and various setting contents set for the user through the notification destination device registered in advance. .. Therefore, the user's family can check the withdrawal status and the balance by the user without operating the cash withdrawal device 10, so that high convenience can be realized. In particular, a family member who is separated from the user not only eliminates the trouble of handing cash to the user on a regular basis, but also can remotely grasp the withdrawal status of the user, which can further improve convenience.

(Embodiment 7)
A plurality of cash payout devices 10 of the above-described embodiments 1 to 6 are provided, and the balance of each user based on the withdrawal process and the deposit process performed by each cash payout device 10 and the storage balance of each cash payout device 10 are stored on the server. The cash withdrawal system to be managed will be described. In the cash withdrawal system of the present embodiment, when the administrator or the user's family uses one of the cash withdrawal devices 10 to set various information including the user's withdrawal schedule, the setting contents are sent to the server. be registered. FIG. 21 is a block diagram showing a configuration example of a cash withdrawal system. In the present embodiment, the cash payout device 10 will be described as a device similar to the cash payout device 10 of the first embodiment. The cash payout system of the present embodiment has a plurality of cash payout devices 10 and a server 40, and each cash payout device 10 and the server 40 are connected to, for example, a LAN. The cash payout device 10 and the server 40 may be connected via a network such as the Internet. The plurality of cash payout devices 10 are installed and used on each floor or each area of various facilities such as medical facilities, welfare facilities, and accommodation facilities for isolation for preventing the transmission of specific infectious diseases. The server 40 may be provided in each facility or may be shared by a plurality of facilities.

The server 40 is an information processing device capable of transmitting and receiving various types of information processing and information, and is configured by using, for example, a server computer or a personal computer. A plurality of servers 40 may be provided for distributed processing, may be realized by a plurality of virtual machines provided in one server, or may be realized by using a cloud server. .. The server 40 includes a control unit 41, a storage unit 42, a communication unit 43, a display unit 44, an input unit 45, and the like, and each of these units is connected to each other via a bus. Each of the control unit 41, the storage unit 42, the communication unit 43, the display unit 44, and the input unit 45 of the server 40 is the control unit 11, the storage unit 12, the communication unit 18, the display unit 13a, and the input unit 13b of the cash payout device 10. Since the configuration is the same as that of the above, detailed description thereof will be omitted. The storage unit 42 of the server 40 stores the device information DB 42a, the administrator information DB 42b, and the user information DB 42c in addition to the control program 42P executed by the control unit 41.

FIG. 22 is a schematic view showing a configuration example of the device information DB 42a. The device information DB 42a stores information about the cash payout device 10 installed in one facility. The device information DB 42a shown in FIG. 22 includes a device ID column, an administrator ID column, a user ID column, a balance information column, and the like, and stores each information of the cash payout device 10 in association with the device ID. The device ID column stores identification information (device ID) assigned to each cash payout device 10. The administrator ID column stores the administrator ID of the administrator who is in charge of the management work of each cash payout device 10, and the user ID column stores the user ID of the user who uses each cash payout device 10. The balance information column stores the storage balance of cash stored in the cash payout device 10, and specifically, stores the number of stored cash for each denomination. The device information DB 42a shown in FIG. 22 has a configuration for storing the number of each denomination of 100-yen coins, 500-yen coins, and 1000-yen bills. Any configuration may be used as long as the number of stored coins or the amount of stored coins is stored. The balance information may include deposit history information and withdrawal history information for each denomination. For example, the deposit history information may include the deposit date and time, the deposit amount (number of deposits), and the user ID of the user to be deposited, and the withdrawal history information includes the withdrawal date and time, the withdrawal amount (number of withdrawals), and the withdrawing user. User ID and the like may be included. By storing such balance information in the device information DB 42a (device balance storage unit), it is possible to manage the cash storage balance stored in each cash payout device 10.

The device ID stored in the device information DB 42a is issued and stored by the control unit 41 when a new cash payout device 10 is installed. The balance information stored in the device information DB 42a is updated by the control unit 41 according to the processing content when the cash payout device 10 performs the deposit process or the withdrawal process. The storage content of the device information DB 42a is not limited to the example shown in FIG. 22, and various information related to the cash payout device 10 can be stored. The administrator in charge of each cash payout device 10 may not be assigned, and in this case, the administrator ID column may not be provided. Further, each user basically uses, for example, the cash payout device 10 installed on the floor where he / she is occupying or hospitalized, but the cash payout device 10 installed on another floor, specifically May perform the withdrawal process using the cash withdrawal device 10 which is not associated with the user. Therefore, the user ID column may not be provided.

The administrator information DB 42b has the same configuration as the administrator information DB 12a stored in the cash payout device 10 of the first embodiment shown in FIG. 3A. The manager information DB 42b of the present embodiment has, for example, a device ID string when a cash payout device 10 in charge of management work is assigned to each manager, and each manager is associated with the device ID. It may be configured to store the information of. Further, the user information DB 42c of the present embodiment has the same configuration as the user information DB 12b stored in the cash payout device 10 of the first embodiment shown in FIG. 3B. The user information DB 42c of the present embodiment has, for example, a device ID string when the cash payout device 10 to be used is assigned to each user, and stores the information of each user in association with the device ID. It may be configured to be used. Further, the deposit / withdrawal history information stored in the user information DB 42c includes the date and time and amount of deposit / withdrawal and the balance at the time of deposit / withdrawal, and such deposit / withdrawal history information is stored in the user information DB 42c (user balance storage unit). ), The balance (book balance) of each user can be managed.

In the present embodiment, the information about the administrator and the information about the user may be managed only by the server 40. For example, the server 40 may store the administrator information DB 42b and the user information DB 42c, and each cash payout device 10 may not store the administrator information DB 12a and the user information DB 12b. In this case, for example, the cash payout device 10 may be configured to acquire administrator information or user information from the server 40 as needed. In the following, each cash payout device 10 is configured to store the administrator information DB 12a and the user information DB 12b. In this configuration, when the information about the administrator or the information about the user is updated by using the server 40 or any of the cash payout devices 10, the stored contents of the administrator information DB 12a or the user information DB 12b in each cash payout device 10 The update process of each DB is performed so that the stored contents of the administrator information DB 42b or the user information DB 42c in the server 40 match.

Next, in the cash withdrawal system of the present embodiment, when any of the cash withdrawal devices 10 performs the withdrawal schedule setting process, the withdrawal process (withdrawal process), or the deposit process of the user, the server 40 uses the user. The withdrawal schedule and balance of the above, and the process of managing the storage balance in the cash withdrawal device 10 will be described. The cash payout device 10 of the present embodiment can execute the same processing as the processing shown in FIGS. 4 and 8, and performs the following processing while performing the processing shown in FIGS. 4 and 8. do.

23 and 24 are flowcharts showing an example of the management processing procedure by the server 40. In the cash payout device 10 of the present embodiment, the control unit 11 determines whether or not the withdrawal schedule setting process for any user has been executed (S151). For example, when it is determined in step S20 in FIG. 4 that the control unit 11 has received the withdrawal schedule setting instruction via the withdrawal schedule setting screen (S20: YES), the control unit 11 has executed the withdrawal schedule setting process. to decide. When the cash withdrawal device 10 is configured to store the user information DB 12b, the control unit 11 sets the withdrawal schedule when the user's withdrawal schedule is stored in the user information DB 12b in step S21 in FIG. It may be determined that the process has been executed. When the control unit 11 (condition output unit) determines that the withdrawal schedule setting process has been executed (S151: YES), the date and time (set date and time) at this point, the device ID of the own device, and the management that performed the setting process. The setting information including the administrator ID of the person, the user ID of the user to be set, and the setting contents (withdrawal conditions) is transmitted to the server 40 (S152). It is assumed that the device ID is stored in the storage unit 12 of the cash payout device 10.

The control unit 41 (setting unit) of the server 40 acquires the setting information transmitted by the cash payout device 10, and sets the setting contents included in the setting information as the withdrawal schedule corresponding to the user ID included in the setting information. It is stored in the DB 42c (S153). After that, the control unit 41 includes the set date and time, the device ID, and the user ID included in the setting information as the work history corresponding to the administrator ID included in the setting information, and indicates that the withdrawal schedule has been set. The history information is stored in the administrator information DB 42b. As a result, the work history of the withdrawal schedule setting process performed by the administrator can be managed by the server 40.

If the control unit 11 determines in step S151 that the withdrawal schedule setting process has not been executed (S151: NO), the process shifts to step S154 and whether or not cash withdrawal (withdrawal process) is executed. Is determined (S154). For example, in step S35 in FIG. 8, when the control unit 11 withdraws (withdraws) the amount of cash set in the withdrawal schedule, it determines that the cash withdrawal has been executed. When the cash payout device 10 is configured to store the user information DB 12b, the control unit 11 pays out cash when the user's withdrawal history information is stored in the user information DB 12b in step S36 in FIG. You may judge that it has been executed. When the control unit 11 (output unit, payout information output unit) determines that the cash has been paid out (S154: YES), the date and time (withdrawal date and time) at this time, the device ID of the own device, and the withdrawing user The user ID (information about the user) and the withdrawal information including the withdrawn amount are transmitted to the server 40 (S155). The amount included in the payout information is the payout amount or the number of payouts for each denomination.

The control unit 41 (acquisition unit) of the server 40 acquires the payout information transmitted by the cash payout device 10. Then, the control unit 41 stores the withdrawal history information including the withdrawal date and time and the withdrawn amount included in the withdrawal information in the user information DB 42c as the withdrawal history corresponding to the user ID included in the withdrawal information (S156). ). The control unit 41 may also include the device ID included in the withdrawal information in the withdrawal history information and store it in the user information DB 42c. Further, the control unit 41 calculates the balance of this user when storing the withdrawal history information in the user information DB 42c, and stores the calculated balance in the withdrawal history information. By accumulating the balance together with the withdrawal history of the user in the user information DB 42c in this way, the control unit 41 (user balance update unit) stores the balance in the user information DB 42c based on the payout information acquired from the cash payout device 10. The balance (book balance) of each user can be updated.

The control unit 41 determines whether or not it is necessary to notify the user or the user's family of the balance based on the calculated balance of the user (S157). For example, when the balance to be notified is registered for each user and the control unit 41 calculates the balance of each user, whether or not the balance of this user is less than the registered balance to be notified. Depending on the situation, it is determined whether or not the balance needs to be notified. When it is determined that it is necessary to notify the balance (S157: YES), that is, when the balance of the user is less than the registered balance to be notified, the control unit 41 (transmitting unit) is the user or the user. A process of notifying a terminal used by a family member (a terminal associated with a user) that the balance is less than a predetermined balance is executed (S158). The notification process here can be performed using an application for sending and receiving messages, such as e-mail, SMS (Short Message Service), and LINE (registered trademark). Further, it is preferable that the notification destination is the user's family. When it is determined that it is not necessary to notify the balance (S157: NO), the control unit 41 skips the process of step S158.

Next, the control unit 41 (device balance update unit) updates the storage balance (balance information) in the cash payout device 10 that has transmitted the payout information (S159). Specifically, the control unit 41 uses the balance information stored in the device information DB 42a for the balance information corresponding to the device ID included in the payout information, and the withdrawal amount (for each denomination) included in the payout information. Update based on the payout amount or the number of payouts). More specifically, the control unit 41 subtracts the number of payouts from the number of each denomination in the balance information stored in the device information DB 42a, and stores the number of each denomination after the subtraction in the device information DB 42a. do. The control unit 41 may store the withdrawal history information including the withdrawal date and time and the number of withdrawals for each denomination in the device information DB 42a, and further stores the withdrawal history information including the user ID of the withdrawing user. You may remember.

The control unit 41 determines whether or not it is necessary to notify the administrator of this balance information based on the updated storage balance of the cash payout device 10 (S160). For example, the remaining number of sheets to be notified is registered for each denomination, and the control unit 41 stores the number of each denomination according to whether or not it is less than the registered number of sheets to be notified. Determine if you need to notify your balance. The remaining number of sheets to be notified for each denomination may be set for each cash payout device 10. In this case, the number of sheets to be notified can be set according to the usage status (payout status) of the cash payout device 10. .. When it is determined that it is necessary to notify the storage balance (S160: YES), that is, when the storage balance of the cash payout device 10 is less than the remaining number of registered cash payout devices 10 to be notified, the control unit 41 (balance notification). The unit) executes a process of notifying the terminal used by the administrator (the terminal associated with the administrator) that the storage balance of the cash payout device 10 is less than a predetermined number (S161). As a result, the manager can grasp the cash payout device 10 having a small storage balance at an early stage. Here, too, it is possible to perform notification processing using various applications for sending and receiving messages. When it is determined that it is not necessary to notify the storage balance (S160: NO), the control unit 41 skips the process of step S161.

When the control unit 11 determines in step S154 that the cash withdrawal has not been executed (S154: NO), the process shifts to step S162 and determines whether or not the deposit process has been executed (S162). For example, when the control unit 11 stores the user's deposit history information in the user information DB 12b in step S27 in FIG. 4, it determines that the deposit process has been executed. Further, the control unit 11 receives the deposit amount via the amount reception screen in step S26 in FIG. 4, and determines the amount of cash (amount for each denomination) inserted from the batch input port 10a or the cash input port 10b. If so, it may be determined that the deposit process has been executed. Further, when the cash payout device 10 of the present embodiment has the configuration of the cash payout device 10 of the second embodiment, the control unit 11 stores the user's payment history information in the user information DB 12b in step S48 in FIG. In some cases, it may be determined that the deposit process has been executed. Further, when the cash payout device 10 of the present embodiment has the configuration of the cash payout device 10 of the third embodiment, the control unit 11 stores the user's payment history information in the user information DB 12b in step S63 in FIG. In some cases, it may be determined that the deposit process has been executed.

When the control unit 11 determines that the payment process has been executed (S162: YES), the date and time (payment date and time) at this time, the device ID of the own device, the user ID of the user to be paid, and the payment information including the payment amount Is transmitted to the server 40 (S163). The amount of money included in the deposit information is the amount of money for each denomination or the number of coins inserted for each denomination. The control unit 41 of the server 40 acquires the deposit information transmitted by the cash payout device 10. Then, the control unit 41 stores the deposit history information including the deposit date and time and the deposit amount included in the deposit information in the user information DB 42c as the deposit history corresponding to the user ID included in the deposit information (S164). The control unit 41 may also include the device ID included in the payment information in the payment history information and store it in the user information DB 42c. Further, the control unit 41 calculates the balance of this user when storing the payment history information in the user information DB 42c, and stores the calculated balance in the payment history information. As a result, the control unit 41 can update the balance (book balance) of each user stored in the user information DB 42c based on the deposit information acquired from the cash payout device 10.

Next, the control unit 41 updates the storage balance (balance information) in the cash payout device 10 that has transmitted the deposit information (S165). Specifically, the control unit 41 uses the balance information stored in the device information DB 42a for the balance information corresponding to the device ID included in the deposit information, and the deposit amount (for each denomination) included in the deposit information. Update based on the deposit amount or the number of input sheets). More specifically, the control unit 41 adds the input number to the number of each denomination in the balance information stored in the device information DB 42a, and stores the number of each denomination after the addition in the device information DB 42a. .. The control unit 41 may store the deposit history information including the deposit date and time and the number of inserted sheets in the device information DB 42a for each denomination, and further stores the deposit history information including the user ID of the user to be deposited. May be good.

When the control unit 11 determines that the deposit process has not been executed (S162: NO), the control unit 11 ends a series of processes. The control unit 11 determines that the setting process (setting of the withdrawal schedule) for any user has been executed, the cash withdrawal has been executed, or the deposit process has been executed. The above-mentioned process is repeated each time. As a result, the withdrawal schedule of the user registered in the user information DB 42c is updated, the deposit / withdrawal history for the user is accumulated in the user information DB 42c, and the cash withdrawal device 10 stored in the device information DB 42a The storage balance is updated. Therefore, in the present embodiment, when the setting process, the deposit process, or the withdrawal process is performed by each of the plurality of cash withdrawal devices 10 installed in the facility, the setting contents or the deposit / withdrawal history information for each user is sent to the server. It is stored in the user information DB 42c of 40, and the deposit / withdrawal history information (balance information) for each cash payout device 10 is stored in the device information DB 42a of the server 40. Therefore, since the withdrawal schedule of each user, the balance of each user, and the storage balance of each cash withdrawal device 10 are collectively managed by the server 40, the user performing the withdrawal process can withdraw from any cash withdrawal device 10 in the facility. Money may be paid, and the manager or the family of the user who performs the payment processing may make a payment to any cash payout device 10 in the facility. Therefore, a user (user, administrator, user's family, etc.) who uses the cash payout device 10 can use the cash payout device 10 installed in an easily accessible place.

In the present embodiment, a plurality of cash withdrawal devices 10 capable of setting a withdrawal schedule and executing cash deposit (insertion) and withdrawal (withdrawal) are provided, and the settings made by each cash withdrawal device 10 are used. The server 40 manages the setting of the above, the balance of the user according to the deposit / withdrawal (deposit / withdrawal history), and the storage balance (deposit / withdrawal history) of the cash withdrawal device 10, but the configuration is not limited to such a configuration. For example, the server 40 can set various conditions of the user, manage the balance of the user (deposit / withdrawal history) and the storage balance of the cash withdrawal device 10 (deposit / withdrawal history), and manage the cash of one of the plurality of cash withdrawal devices 10. It may be configured to be performed by the payout device 10 (cash payout device 10 for management). In this case, each cash payout device 10 transmits the setting information to the cash payout device 10 for management when the setting process for any user is performed, and manages the payout information when the withdrawal process is performed. It is transmitted to the cash payout device 10, and further, when the deposit process is performed, the deposit information is transmitted to the cash payout device 10 for management. Then, the cash payout device 10 for management sets the withdrawal schedule of each user, the balance of each user, and each cash payout based on the setting information, the payout information, and the deposit information acquired from the other cash payout device 10. The storage balance of the device 10 is managed. Even in such a configuration, the same processing as in the present embodiment can be performed, and the same effect can be obtained.

In the present embodiment, each cash withdrawal device 10 is configured to execute a setting process and a deposit process for the user, a withdrawal process by the user, and a confirmation process of the deposit / withdrawal history of the user. In the cash withdrawal device 10 having such a configuration, for example, a withdrawal mode that executes only withdrawal processing, a family mode that executes deposit processing and confirmation processing of deposit / withdrawal history, an administrator that executes setting processing and deposit processing. Modes and the like may be provided so that these modes can be switched and used. In this case, by setting the mode according to the installation location of each cash payout device 10, the processing performed by each cash payout device 10 can be reduced, and the processing load by the cash payout device 10 can be reduced. For example, a withdrawal mode may be set for a cash withdrawal device 10 installed on a hospital room floor of a medical institution and used only for withdrawal by a user who is an inpatient. In addition, a family mode may be set for the cash payout device 10 installed at the entrance of a medical institution and used by the user's family and the like for payment and history confirmation. Further, the administrator mode may be set for the cash payout device 10 installed near the nurse station or the staff station of the medical institution and used by the administrator for the setting process and the deposit.

In the present embodiment, the information about the administrator (administrator information DB 42b) and the information about the user (user information DB 42c) may be managed only by the server 40, and in this case, the cash payout device 10 is connected to the server 40. Send and receive necessary information. For example, when the cash payout device 10 performs withdrawal processing, in step S32 in FIG. 8, the control unit 11 transmits biometric data (vein data) acquired from the user to the server 40, and executes user authentication to the server 40. To request. The server 40 collates the acquired vein data with the biometric authentication data stored in the user information DB 42c to perform user authentication, and transmits the authentication result to the cash payout device 10. As a result, the cash payout device 10 can acquire the authentication result by the server 40 and determine whether or not the authentication is successful based on the acquired authentication result. Further, the control unit 11 acquires the withdrawal schedule of the authenticated user from the server 40 in step S34 in FIG. 8, whereby the withdrawal can be made based on the withdrawal schedule set for each user. It is possible to judge whether or not it is. Further, the control unit 11 transmits the authentication data acquired from the administrator to the server 40 in step S12 in FIG. 4, and requests the server 40 to execute the administrator authentication. Then, the control unit 11 can determine whether or not the administrator's authentication is successful by acquiring the authentication result from the server 40. Further, in step S23 in FIG. 4, the control unit 11 obtains the deposit / withdrawal history stored in the user information DB 42c in association with the user to be processed from the server 40 to obtain a list of deposit / withdrawal histories of the user. Can be generated.

The cash payout device 10 of each of the above-described embodiments is limited to a usage mode in which a user who moves into the facility or a user who uses the facility performs the withdrawal process and the user's family or the like performs the deposit process. Not done. For example, it can be used in a company with an employment form in which wages are paid in cash, where the employer who pays the wages processes the deposit and the employee processes the withdrawal and receives the wages. In this case, by registering the biometric authentication data of the employee, the employee can acquire the wage at the timing desired by himself / herself. In addition, by setting the withdrawal amount as the withdrawal schedule, it is possible to prevent the employee from wasting wages.

The embodiments disclosed this time should be considered as exemplary in all respects and not restrictive. The scope of the present invention is indicated by the scope of claims, not the above-mentioned meaning, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

10 Cash payout device 11 Control unit 12 Storage unit 13 Touch panel 14 Biometric sensor 15 Cash payout unit 16 Cash reception unit 17 Speaker 18 Communication unit 31 Sensor 32 Notification unit 33 Camera 40 Server 10a Bulk input port 10b Cash input port 13a Display unit 13b Input section

Claims (19)

The biometric information reception unit that accepts the user's biometric information and
A user authentication unit that authenticates the user based on the received biometric information,
A cash withdrawal device equipped with a withdrawal unit that pays out a set amount of cash to an authenticated user.
An administrator authentication unit that authenticates the administrator who manages the user,
A cash withdrawal device that includes a setting unit that accepts and sets cash withdrawal conditions for multiple users associated with an authenticated administrator. The cash withdrawal device according to claim 1, wherein the setting unit sets a cash withdrawal schedule and an amount for each of the plurality of users. The setting unit
If the withdrawal is not made at the timing that meets the withdrawal conditions for the user, the selection of whether to carry over the unwithdrawn amount to the next timing is accepted.
The cash withdrawal device according to claim 1 or 2, which accepts and sets an upper limit amount for one withdrawal when carry-over is selected. The cash payout device according to any one of claims 1 to 3, wherein the administrator authentication unit authenticates a plurality of administrators. The cash reception department that accepts cash input and
The cash payout device according to any one of claims 1 to 4, further comprising an addition unit for adding the cash inserted in association with the user to the balance corresponding to the user. When the biometric information receiving unit receives the biometric information after the cash receiving unit accepts the cash input, the user authentication unit authenticates the user based on the received biometric information.
The addition unit adds the inserted cash to the balance corresponding to the authenticated user when the user authentication unit authenticates the user after the cash reception unit accepts the input of cash. Cash withdrawal device described in. A guardian authentication unit that authenticates the guardian associated with the user is further provided.
When the guardian authentication unit authenticates the guardian after the cash reception unit accepts the cash input, the addition unit transfers the inserted cash to the user associated with the authenticated guardian. The cash payout device according to claim 5 or 6, which is added to the corresponding balance. The withdrawal history indicating the amount paid to the user associated with the administrator authenticated by the administrator authentication unit and the deposit history indicating the amount deposited associated with the user are displayed. The cash payout device according to any one of claims 1 to 7, further comprising a history display unit for an administrator. A guardian authentication unit that authenticates the guardian associated with the user,
The withdrawal history indicating the amount paid to the user associated with the guardian authenticated by the guardian authentication unit and the deposit history indicating the amount deposited associated with the user are displayed. The cash payout device according to any one of claims 1 to 8, further comprising a history display unit for parents. A cash storage unit that stores cash for each denomination,
A calculation unit that calculates the total amount of cash stored in the cash storage unit for each denomination,
Based on the withdrawal conditions set for the plurality of users, the planned withdrawal amount calculation unit that calculates the total amount of cash to be paid to the plurality of users within a predetermined period for each denomination, and
A claim including a specific unit that specifies a denomination that needs to be exchanged based on the total amount for each denomination calculated by the calculation unit and the total amount for each denomination calculated by the planned payout amount calculation unit. The cash payout device according to any one of 1 to 9. A cash storage unit for storing cash and
A storage amount calculation unit that calculates the total amount of cash stored in the cash storage unit,
A balance calculation unit that calculates the balances of the plurality of users based on the deposit history and the withdrawal history for the plurality of users.
Claims 1 to 10 include a determination unit for determining whether or not the total amount calculated by the storage amount calculation unit and the total amount of the balances of the plurality of users calculated by the balance calculation unit match. The cash payout device described in any one. A first slot for accepting cash to be inserted in association with each of the users, and
The cash payout device according to any one of claims 1 to 11, further comprising a second slot for collectively inserting cash associated with the plurality of users. A detector that detects the occurrence of an abnormality and
The cash payout device according to any one of claims 1 to 12, further comprising a notification unit for notifying when an abnormality has been detected. One of claims 1 to 13 further comprising an output unit that outputs the amount paid out and information about the authenticated user to a predetermined device when cash is paid out by the withdrawal unit. The cash payout device described. A program that authenticates a user based on biometric information and causes a computer to execute a setting process for a cash payout device that pays out a set amount of cash to the authenticated user.
Authenticate the administrator who manages the user,
Accepts cash withdrawal conditions for users associated with authenticated administrators,
A program that causes a computer to execute a process of setting the received withdrawal conditions for the user for the cash withdrawal device. Accepts user's biometric information
Authenticate the user based on the received biometric information
Withdraw the set amount of cash to the authenticated user,
Authenticate the administrator who manages the user,
A cash withdrawal method in which a computer performs a process of accepting and setting cash withdrawal conditions for multiple users associated with an authenticated administrator. When the user is authenticated based on the biometric information of the user, a plurality of cash payout devices for paying out the amount of cash set for the user are communicably connected to the plurality of cash payout devices. It is a cash withdrawal system including a server
The cash payout device is
An administrator authentication unit that authenticates the administrator who manages the user,
A condition output unit that accepts cash withdrawal conditions for multiple users associated with the authenticated administrator and outputs them to the server.
When cash is paid out, it is provided with a payout information output unit that outputs payout information including information about the own device, the amount paid out, and information about the user to the server.
The server
A setting unit for setting withdrawal conditions for the plurality of users acquired from the cash withdrawal device, and
A user balance storage unit that stores balances corresponding to each of a plurality of users,
A device balance storage unit that stores the balance stored in each of the plurality of cash payout devices, and a device balance storage unit.
Based on the acquired payout information, a user balance update unit that updates the balance corresponding to the user stored in the user balance storage unit, and a user balance update unit.
A cash payout system including a device balance update unit that updates the balance corresponding to the cash payout device stored in the device balance storage unit based on the acquired payout information. The server
A transmission unit that transmits information about the balance of the user to a terminal associated with the user based on the balance of the user updated by the user balance update unit.
The cash payout system according to claim 17, further comprising a balance notification unit for notifying information regarding the balance of the cash payout device based on the balance corresponding to the cash payout device updated by the device balance update unit. A server that is communicably connected to a cash payout device that pays out a set amount of cash to the user when the user is authenticated based on the user's biometric information.
A setting unit that acquires and sets cash withdrawal conditions for the user from the cash withdrawal device, and
A user balance storage unit that stores balances corresponding to each of a plurality of users,
A device balance storage unit that stores the balance stored in each of the plurality of cash payout devices, and a device balance storage unit.
An acquisition unit that acquires payout information from the cash payout device, including the amount of cash paid out by the cash payout device and information about the user who has paid out the cash.
Based on the acquired payout information, a user balance update unit that updates the balance corresponding to the user stored in the user balance storage unit, and a user balance update unit.
A server including a device balance update unit that updates the balance corresponding to the cash payout device stored in the device balance storage unit based on the acquired payout information.

Images