Money handling apparatus, settlement processing apparatus, money handling system, and money handling apparatus

Abstract

To enable each securities processing device to use an appropriate database.SOLUTION: The securities processing device 210 includes a storage device 215 that stores, as a database used to identify the inserted securities GT, a note type table TBL12 in which a plurality of securities GT are registered, a registering section 214 that registers the securities GT in the note type table TBL12, and an image information acquiring section 212 that acquires to-be-registered image information indicating an image of the securities GT to be registered. Each of the plurality of securities GT registered in the note type table TBL12 belongs to either a first type of security GT or a second type of security GT. When the target security GT is the first type of security GT, the registering section 214 registers the target security GT in the document type table TBL12 based on the target image information, and when the target security GT is the second type of security GT, the registering section 113 does not register the target security GT in the document type table TBL12 and ends the process for the target security GT.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a securities processing device, a settlement processing device, a currency processing system, and a currency processing device. [Background technology]

[0002] In stores such as supermarkets, in addition to currency, valuable securities such as gift certificates may be handled. For example, stores that handle gift certificates use gift certificate deposit machines to process the deposit of gift certificates. A typical gift certificate deposit machine has a function of identifying whether a gift certificate inserted into the machine is usable at the store. For example, a gift certificate deposit machine is known that sends gift certificates that meet predetermined conditions, among those identified by an identification unit, to a storage unit within the machine and ejects gift certificates that do not meet the predetermined conditions outside the machine (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-200938 Summary of the Invention [Problem to be solved by the invention]

[0004] In order to identify securities (gift certificates) inserted into a securities processing device, such as a gift certificate processing device, a database in which reference gift certificates are registered must be stored in advance in a storage device. For example, when there are multiple gift certificate processing devices, a server device typically transmits the database in which reference gift certificates are registered to the multiple gift certificate processing devices in a batch. This allows each gift certificate processing device to store in advance in a storage device the database in which reference gift certificates are registered.

[0005] Here, for example, securities used in stores and the like include gift certificates issued by credit card companies, department stores, and the like that are valid nationwide, regional promotion certificates that are valid only in specific regions, and service certificates and coupons that are valid only at specific stores. In recent years, the types of securities used in stores and the like have been increasing. As a result, a server device must transmit a database containing a huge number of securities to each gift certificate processing device. In this case, the amount of data transmitted from the server device becomes enormous. Furthermore, each store's gift certificate processing device must store a database containing unnecessary securities information because the server device transmits the database containing securities information about securities that are not required for that store. This unnecessarily increases the storage capacity of the storage device storing the database. Furthermore, if the recognition process for recognizing securities is performed using a database containing securities information about unnecessary securities, the load on the processor of the gift certificate processing device increases, which may reduce the processing speed and accuracy of the recognition process. Therefore, it is desirable to enable each gift certificate processing device to use an appropriate database. [Means for solving the problem]

[0006] A preferred embodiment of the present invention provides a securities processing device that processes inserted securities, and includes an image input device that generates image information indicating an image of the inserted securities, a memory unit that stores a securities database in which multiple securities are registered as a database used when identifying the inserted securities, a registration unit that registers the securities in the securities database, and an acquisition unit that can acquire the image information generated by the image input device as registration target image information indicating an image of the security to be registered, wherein each of the multiple securities registered in the securities database belongs to either a first type of security or a second type of security, and the registration unit, if the security to be registered is the first type of security, registers the security to be registered in the securities database based on the registration target image information, and if the security to be registered is the second type of security, terminates processing for the security to be registered without registering it in the securities database.

[0007] In addition, a settlement processing device according to a preferred embodiment of the present invention comprises the above-mentioned securities processing device, a POS register, and a settlement device, wherein the acquisition unit is capable of acquiring the image information generated by the image input device as settlement target image information indicating an image of the securities to be settled, and the securities processing device further has an identification unit that identifies the inserted securities by comparing the settlement target image information with each of a plurality of reference image information indicating images of the plurality of securities registered in the securities database, and the POS register and the settlement device perform settlement processing for the goods according to the identification result of the identification unit.

[0008] A preferred embodiment of the present invention provides a currency handling system having a management computer and a plurality of settlement processing devices communicatively connected to the management computer, each of the plurality of settlement processing devices having a POS register, a settlement device, and a securities processing device for processing inserted securities, the securities processing device including an image input device for generating image information showing an image of the inserted securities, a memory unit for storing a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities, a registration unit for registering securities in the securities database, and a registration unit for converting the image information generated by the image input device into the securities to be registered. and an acquisition unit capable of acquiring registration target image information indicating an image of a security, wherein each of the plurality of securities registered in the securities database belongs to either a first type of security or a second type of security, and when the security to be registered is the first type of security, the registration unit registers the security to be registered in the securities database based on the registration target image information, and when the security to be registered is the second type of security, the registration unit does not register the security to be registered in the securities database and terminates processing for the security to be registered, and when registration target image information indicating an image of the second type of security is sent from the management computer, the registration unit registers the security to be registered in the securities database.

[0009] Furthermore, a preferred embodiment of the present invention provides a settlement processing device having a POS register including a display unit and an input unit, a settlement device, and a securities processing device that processes inserted securities, wherein the securities processing device comprises an image input device that generates image information showing an image of the inserted securities, a memory unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities, a registration unit that registers the securities in the securities database, and an acquisition unit that is capable of acquiring the image information generated by the image input device as registration target image information showing an image of the securities to be registered, wherein each of the plurality of securities registered in the securities database belongs to either a first type of security or a second type of security, and the registration unit displays an input screen on the display unit that accepts input of specified information other than the registration target image information among the securities information for registering the securities to be registered in the securities database, and if it determines that the securities to be registered are the second type of security based on the registration target image information or the information input on the input screen, it displays a warning on the display unit that the securities to be registered will not be registered in the securities database.

[0010] Furthermore, a preferred embodiment of the present invention provides a settlement processing device having a POS register including a display unit and an input unit, a settlement device, and a securities processing device that processes inserted securities, wherein the securities processing device comprises an image input device that generates image information showing an image of the inserted securities, a memory unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities, a registration unit that registers the securities in the securities database, and an acquisition unit that acquires the image information generated by the image input device as registration target image information showing an image of the securities to be registered, wherein each of the plurality of securities registered in the securities database belongs to either a first type of security or a second type of security, and the registration unit displays on the display unit an input screen that accepts input of specified information other than the registration target image information among the securities information for registering the securities to be registered in the securities database, and if the securities to be registered are the first type of security, registers the securities to be registered in the securities database based on the securities information, and displays on the display unit a selection screen that allows the user to select whether or not to register the securities to be registered in the securities database of another settlement processing device.

[0011] In addition, a preferred embodiment of the present invention provides a currency processing device having a cash processing device, a securities processing device, and a display device, wherein the securities processing device comprises an image input device that generates image information showing an image of an inserted security, a memory unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted security, a registration unit that registers the security in the securities database, and an acquisition unit that acquires the image information generated by the image input device as registration target image information showing an image of the security to be registered, wherein each of the plurality of securities registered in the securities database belongs to either a first type of security or a second type of security, and the registration unit displays an input screen on the display device that accepts input of specified information other than the registration target image information among the securities information for registering the security to be registered in the securities database, and if it determines that the security to be registered is the second type of security based on the registration target image information or the information input on the input screen, it displays a warning on the display device that the security to be registered will not be registered in the securities database.

[0012] In addition, a preferred embodiment of the present invention provides a currency processing device having a cash processing device, a securities processing device, an image input device, and a display device, wherein the image input device generates image information showing an image of an inserted security, and the securities processing device is equipped with a memory unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted security, a registration unit that registers the security in the securities database, and an acquisition unit that acquires the image information generated by the image input device as registration target image information showing an image of the security to be registered, wherein each of the plurality of securities registered in the securities database belongs to either a first type of security or a second type of security, and the registration unit displays an input screen on the display device that accepts input of specified information other than the registration target image information among the securities information for registering the security to be registered in the securities database, and if the security to be registered is the first type of security, registers the security to be registered in the securities database based on the security information, and displays a selection screen on the display device that allows the user to select whether or not to register the security to be registered in the securities database of another currency processing device. [Effects of the Invention]

[0013] According to the present invention, the database in which the reference securities are registered can be made an appropriate database. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is an explanatory diagram for explaining an overview of a currency handling system according to an embodiment. [Figure 2] 2 is a block diagram showing an example of the configuration of the POS register system shown in FIG. 1. FIG. [Figure 3] 2 is a block diagram showing an example of the configuration of a server device and a computer device shown in FIG. 1. FIG. [Figure 4] FIG. 4 is an explanatory diagram for explaining an example of the bill type table shown in FIG. 3. [Figure 5] FIG. 3 is an explanatory diagram for explaining an example of a bill type table shown in FIG. 2. [Figure 6] 2 is a flowchart showing an example of the operation of the server device shown in FIG. [Figure 7] 2 is a flowchart showing an example of the operation of the securities processing device shown in FIG. 1. [Figure 8] FIG. 10 is an explanatory diagram illustrating an example of an operation screen for checking an image of a security read by an image input device. [Figure 9] FIG. 10 is an explanatory diagram illustrating an example of an operation screen that accepts input of the name, face value, and type of a security to be registered. [Figure 10] 2 is a flowchart showing an example of the operation of the POS register system shown in FIG. 1. [Figure 11] 10 is a flowchart showing an example of the operation of the securities processing device according to the first modified example. [Figure 12] FIG. 10 is an explanatory diagram for explaining an example of an operation screen according to a first modified example. [Figure 13] 10 is a flowchart showing an example of the operation of the securities processing device according to the second modification. [Figure 14] 10 is a sequence chart showing an example of the operation of a money handling system according to a second modified example. [Figure 15] FIG. 10 is an explanatory diagram for explaining an example of an operation screen according to a second modified example. [Figure 16] FIG. 10 is an explanatory diagram illustrating an example of an operation screen when executing a registration request. [Figure 17] 10 is a flowchart showing an example of the operation of a securities processing device according to a third modified example. [Figure 18] 10 is a flowchart showing an example of the operation of a securities processing device according to a third modified example. [Figure 19] FIG. 11 is an explanatory diagram illustrating an example of an operation screen according to a third modified example. [Figure 20] FIG. 10 is an explanatory diagram for explaining an overview of a currency handling system according to a fourth modified example. [Figure 21] FIG. 21 is a block diagram showing an example of the configuration of the currency handling device shown in FIG. 20. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that in each drawing, the dimensions and scale of each part are appropriately different from those of the actual parts. Furthermore, the embodiments described below are preferred examples of the present invention, and therefore various technically preferable limitations are applied. However, the scope of the present invention is not limited to these embodiments unless otherwise specified in the following description to the effect that the present invention is limited.

[0016] [1. Embodiment] First, an example of an overview of a currency handling system 1 according to an embodiment will be described with reference to FIG.

[0017] FIG. 1 is an explanatory diagram for explaining an overview of a currency handling system 1 according to an embodiment.

[0018] In this embodiment, the currency handling system 1 is a system that handles security GTs such as gift certificates. While this embodiment mainly uses gift certificates as an example of the security GT handled by the currency handling system 1, the security GT is not limited to gift certificates and may be other securities or non-securities. For example, security GTs include gift certificates issued by credit companies, department stores, etc. that can be used nationwide, regional promotion coupons that can only be used in specific regions, and service coupons and coupons that can only be used at specific stores. Hereinafter, security GTs such as gift certificates that can be used nationwide may be collectively referred to as common coupons or security GTs that can be used nationwide. Hereinafter, security GTs such as regional promotion coupons that can only be used in specific regions, and service coupons and coupons that can only be used at specific stores may be collectively referred to as unique coupons or security GTs that can only be used at specific stores. The terms common coupon and unique coupon are also used to indicate the type (category) of security GT. A common coupon is an example of a "second type of security," and a unique coupon is an example of a "first type of security."

[0019] The currency handling system 1 includes, for example, a server device 10, a computer device 12, an image scanner 14, and a plurality of POS (Point Of Sales) register systems 20 (20a, 20b, and 20c) communicatively connected to the server device 10. In FIG. 1, in order to distinguish the plurality of POS register systems 20 from one another, a lowercase alphabet (a, b, or c) is added to the end of the reference numeral of each POS register system 20. For example, a security GT that can be used in a plurality of POS register systems 20 including POS register systems 20a, 20b, and 20c corresponds to a common security GT, and a security GT that can be used only in POS register systems 20a and 20b of the plurality of POS register systems 20 corresponds to a unique security GT.

[0020] The server device 10 and each of the multiple POS register systems 20 are connected to a network NW. The network NW may include the Internet and a local area network. For example, the network NW may include one or both of a wired network and a wireless network. Furthermore, the connection between the multiple elements, including the POS register system 20, and the network NW may be, for example, a connection that enables communication between the multiple elements, and may be a wired or wireless connection, or a connection that uses both wired and wireless connections. The server device 10 is an example of a "management computer" and an "external device," and the POS register system 20 is an example of a "payment processing device."

[0021] In this embodiment, a POS register system 20 is installed in each of a plurality of stores (e.g., a chain store) that handles securities GT. That is, in this embodiment, a plurality of POS register systems 20 installed in each of the plurality of stores are communicatively connected to a server device 10. However, the currency handling system 1 may also have a server device 10 installed in a store and a plurality of POS register systems 20 installed in the same store as the store in which the server device 10 is installed. In this embodiment, a plurality of POS register systems 20 installed in a store may be communicatively connected to the server device 10 installed in the store.

[0022] The server device 10 may be any information processing device connectable to the network NW. The server device 10 is connected to a computer device 12 having a display device 128 and an operation device 129. The computer device 12 may be any information processing device. The computer device 12 may include, for example, a display device 128, which is an output device such as a display that outputs to the outside, and an operation device 129, which is an input device (e.g., a keyboard, a mouse, a switch, a button, a sensor, etc.) that accepts input from the outside. For example, the display device 128 displays images, etc., and the operation device 129 accepts operations by an administrator of the server device 10, etc. Note that the display device 128 and the operation device 129 may be integrated (e.g., a touch panel). The computer device 12 is also connected to an image scanner 14 that reads securities GT. The image scanner 14, for example, captures an image of the securities GT to generate image information representing an image of the securities GT. The image information generated by the image scanner 14 is transmitted to the server device 10 via the computer device 12. The configurations of the server device 10 and the computer device 12 will be explained later with reference to FIG.

[0023] Each of the multiple POS register systems 20 has a security processing device 210 that processes security GT such as gift certificates, a POS register 220, and a change dispenser 230. The security processing device 210 has, for example, an input / output port IOP. For example, the input / output port IOP functions as an input port for inserting security GT into the security processing device 210 and as an output port for removing security GT from the security processing device 210. The input port and output port may be located in different locations. In the security processing device 210 shown in FIG. 1, for example, insertion of security GT into the security processing device 210 is achieved by inserting the security GT into the input / output port IOP of the security processing device 210.

[0024] The POS register 220 and the change machine 230 execute the settlement process for the merchandise. For example, the change calculated by the POS register 220 is taken out from the change machine 230. When a security GT is used to settle the merchandise, the POS register 220 and the change machine 230 execute the settlement process for the merchandise in accordance with the recognition result of the security GT by the security processing device 210. The change machine 230 is an example of a "settling device."

[0025] As described above, each POS register system 20 is connected to the server device 10 via the network NW. This allows data to be transmitted and received between each POS register system 20 and the server device 10.

[0026] The configuration of the currency handling system 1 is not limited to the example shown in Fig. 1. For example, if the server device 10 has a display device 128 and an operation device 129, the computer device 12 may be omitted. Furthermore, the device that reads the securities GT is not limited to the image scanner 14.

[0027] Next, the configuration of the POS register system 20 will be described with reference to FIG.

[0028] FIG. 2 is a block diagram showing an example of the configuration of the POS register system 20 shown in FIG.

[0029] The POS register system 20 includes a bill processing device 210, a POS register 220, and a change dispenser 230, as described with reference to FIG.

[0030] The securities processing device 210 has a processing device 211 that controls the entire securities processing device 210, a storage device 215 that stores various information, a communication device 216, and an image input device 217. Before explaining the processing device 211, a brief explanation will be given of the storage device 215, the communication device 216, and the image input device 217.

[0031] The storage device 215 includes, for example, one or both of a volatile memory such as a random access memory (RAM) that functions as a working area for the processing device 211, and a non-volatile memory such as an electrically erasable programmable read-only memory (EEPROM) that stores various information such as the control program PG20. The storage device 215 may be detachable from the securities processing device 210. Specifically, the storage device 215 may be a storage medium such as a memory card that is detachable from the securities processing device 210. The storage device 215 may also be, for example, a storage device (e.g., online storage) that is communicatively connected to the securities processing device 210 via a network NW or the like.

[0032] In this embodiment, the storage device 215 stores a denomination table TBL12 in addition to the control program PG20. The denomination table TBL12 is a database used to identify a security GT inserted into the security processing device 210, and multiple security GTs are registered in the denomination table TBL12. The security GT being registered in the denomination table TBL12 means that security information including, for example, image information showing an image of the security GT, the face value of the security GT, and the security type of the security GT is stored in the denomination table TBL12. Details of the denomination table TBL12 will be described later in FIG. 5. For example, the denomination table TBL12 is a denomination table TBL10 (see FIGS. 3 and 4) transmitted from the server device 10, in which security GTs (unique security GTs) that can only be used at specific stores are appropriately registered. The denomination table TBL12 is an example of a "securities database," and the storage device 215 is an example of a "storage unit."

[0033] The communication device 216 is hardware for communicating with external devices such as the server device 10 and the POS register 220 that exist outside the securities processing device 210 .

[0034] The image input device 217 is an optical device such as a camera or an image scanner. For example, the image input device 217 captures an image of a security GT inserted into the security processing device 210, thereby generating image information representing the image of the security GT. The image information generated by the image input device 217 is referenced by the processing device 211. For example, when a security GT is used to settle a purchase, a user such as an employee of a store in which the POS register system 20 is installed inserts the security GT to be used to settle a purchase into the security processing device 210, causing the image input device 217 to read the security GT. Alternatively, when a user registers a security GT in the security type table TBL12, the user causes the image input device 217 to read the security GT to be registered. The image input device 217 generates image information representing the image of the read security GT, for example, and transmits the generated image information to the processing device 211. If the processing device 211 has a memory, the image information transmitted from the image input device 217 may be stored in the memory of the processing device 211. The image input device 217 may store the image information in the storage device 215. In this case, the processing device 211 may read out the image information from the storage device 215.

[0035] The processing device 211 is a processor that controls the entire securities processing device 210, and may include, for example, one or more central processing units (CPUs). For example, the processing device 211 executes a control program PG20 stored in the storage device 215 to function as an image information acquisition unit 212, a recognition unit 213, and a registration unit 214. The control program PG20 may be transmitted from another device via the network NW. In this embodiment, the processing device 211 can control the display device 228 (described later) of the POS register 220 via the communication device 216, etc. The processing device 211 may also function as an operation control unit that controls operations related to the transportation of inserted securities GT.

[0036] Furthermore, for example, when the processing device 211 is configured to include multiple CPUs, some or all of the functions of the processing device 211 may be realized by these multiple CPUs operating in cooperation with each other in accordance with a program such as the control program PG20. Furthermore, the processing device 211 may be configured to include hardware such as a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), or an FPGA (Field Programmable Gate Array) in addition to one or more CPUs, or instead of some or all of the one or more CPUs. In this case, some or all of the functions of the processing device 211 may be realized by hardware such as a DSP.

[0037] Thus, in this embodiment, the control program PG20 includes application programs for causing the processing device 211 to function as the image information acquisition unit 212, the identification unit 213, and the registration unit 214. The control program PG20 may include, for example, an operating system program for causing the processing device 211 to function as an overall operation control unit for the securities processing device 210. The image information acquisition unit 212 is an example of an "acquisition unit." Of the multiple function blocks realized by the processing device 211, FIG. 2 shows the main function blocks for identifying and registering securities GT.

[0038] The image information acquisition unit 212 acquires, for example, image information showing an image of the security GT read by the image input device 217 from the image input device 217. Hereinafter, the image information showing the image of the security GT may be simply referred to as image information of the security GT. Furthermore, when the image input device 217 stores the image information of the security GT in the storage device 215, the image information acquisition unit 212 may acquire the image information of the security GT from the storage device 215. Note that in this embodiment, the image information acquisition unit 212 acquires both image information showing an image of the front side of the security GT and image information showing an image of the back side of the security GT as the image information of the security GT. However, the image information acquisition unit 212 may also acquire image information showing an image of either the front side or the back side of the security GT as the image information of the security GT.

[0039] For example, when a security GT is used to settle a commodity, the recognition unit 213 recognizes the security GT inserted into the security processing device 210 using the image information acquired by the image information acquisition unit 212 and the security type table TBL12. Hereinafter, the image information acquired by the image information acquisition unit 212 when a security GT is used to settle a commodity may be referred to as settlement target image information. For example, the recognition unit 213 recognizes the security GT by comparing the settlement target image information with each of a plurality of reference image information indicating images of a plurality of security GTs registered in the security type table TBL12. The operation of the processing device 211 and the like when settling a commodity will be described later with reference to FIG. 10.

[0040] The registration unit 214 registers the security GT in the security type table TBL12. Registering the security GT in the security type table TBL12 means storing security information including, for example, image information showing an image of the security GT, the face value of the security GT, and the security type of the security GT in the security type table TBL12. Hereinafter, the security GT read by the image input device 217 when the registration unit 214 registers the security GT in the security type table TBL12 may be referred to as the security GT to be registered. Hereinafter, image information showing an image of the security GT to be registered may be referred to as image information to be registered.

[0041] In this embodiment, the registration unit 214 can register a security GT (unique security note) that can only be used at a specific store in the security type table TBL12, but cannot independently register a security GT (common security note) that can be used nationwide in the security type table TBL12. Here, independently registering a common security note in the security type table TBL12 means, for example, registering a common security note that is not registered in the security type table TBL10 (see FIGS. 3 and 4) managed by the server device 10 in the security type table TBL12. Therefore, for example, the registration unit 214 may be able to register a security GT (common security note) that has been newly registered in the security type table TBL10 by updating the security type table TBL10 in the security type table TBL12 in accordance with an instruction from the server device 10. In addition, in this embodiment, the registration unit 214 can delete a unique security note from the security type table TBL12. The operation of the processing device 211 and the like when the registration unit 214 registers the security GT in the security type table TBL12 will be described later with reference to FIG.

[0042] The POS register 220 includes a processing device 221 that executes settlement processing and the like, a display device 228, and an operation device 229. The processing device 221 is a processor that controls the entire POS register 220 and is configured similarly to the processing device 211 of the securities processing device 210, for example. For example, the processing device 221 is configured to include one or more CPUs. The display device 228 is an output device such as a display that outputs to the outside, and for example, displays images and the like under the control of the processing device 221. The operation device 229 is an input device that accepts input from the outside, and for example, accepts operations by an operator operating the POS register 220. Note that the display device 228 and the operation device 229 may be integrated (for example, a touch panel). In this embodiment, the processing device 211 of the securities processing device 210 can acquire information indicating the result of the input accepted by the operation device 229. The display device 228 is an example of a "display unit," and the operation device 229 is an example of an "input unit."

[0043] The change dispenser 230 is connected to the POS register 220 and exchanges money and the like with the customer based on information from the POS register 220 .

[0044] The configuration of the POS register system 20 is not limited to the example shown in Fig. 2. For example, the POS register system 20 may have a processor that controls the entire POS register system 20. Alternatively, for example, the processing device 211 may control the entire POS register system 20. Furthermore, for example, the POS register system 20 may have a display device 228 and an operation device 229 outside the POS register 220.

[0045] Next, the configuration of the server device 10 and the computer device 12 will be described with reference to FIG.

[0046] FIG. 3 is a block diagram showing an example of the configuration of the server device 10 and the computer device 12 shown in FIG.

[0047] First, the configuration of the server device 10 will be described.

[0048] The server device 10 includes a processing device 111, a storage device 115 that stores various information such as a control program PG10 and a bill type table TBL10, and a communication device .

[0049] The processing device 111 is a processor that controls the entire server device 10, and is configured, for example, similarly to the processing device 211 of the securities processing device 210 described in Fig. 2. For example, the processing device 111 is configured to include one or more CPUs. Furthermore, for example, the processing device 111 functions as an image information acquisition unit 112 and a registration unit 114 by executing a control program PG10 stored in the storage device 115. Note that Fig. 3 shows the main functional block for registering securities GT, among the multiple functional blocks realized by the processing device 111.

[0050] The image information acquisition unit 112 is, for example, similar to the image information acquisition unit 212 of the securities processing device 210 described in Fig. 2. For example, the image information acquisition unit 112 acquires image information indicating an image of the securities GT read by the image scanner 14 from the image scanner 14 via the computer device 12.

[0051] The registration unit 114 is similar to the registration unit 214 of the securities processing device 210 described in FIG. 2, for example. For example, the registration unit 114 registers a securities GT in the security type table TBL10. However, in this embodiment, the types of securities GT that the registration unit 114 can register in the security type table TBL10 are different from the types of securities GT that the registration unit 214 can register in the security type table TBL12. For example, the registration unit 114 can register a securities GT (common security note) that can be used nationwide in the security type table TBL10, but cannot register a securities GT (unique security note) that can be used only at a specific store in the security type table TBL10. Furthermore, the registration unit 114 can delete a securities GT (common security note) registered in the security type table TBL10 from the security type table TBL10. The operation of the processing device 111 and the like when the registration unit 114 registers a securities GT in the security type table TBL10 will be described later with reference to FIG. 6.

[0052] The storage device 115 is configured, for example, in the same manner as the storage device 215 of the securities processing device 210 described in Fig. 2. For example, the storage device 115 includes one or both of a volatile memory such as a RAM that functions as a working area for the processing device 111 and a non-volatile memory such as an EEPROM that stores various information such as the control program PG10.

[0053] In this embodiment, as described above, the storage device 115 stores the control program PG10 as well as the denomination table TBL10. The denomination table TBL10 is a database transmitted from the server device 10 to the securities processing device 210, and stores securities GTs (common securities) that can be used uniformly throughout the country. The denomination table TBL10 also stores securities GTs (unique securities) that can only be used at specific stores, and this table is used by the securities processing device 210 to identify securities GTs inserted into the securities processing device 210 as the denomination table TBL12. Details of the denomination table TBL10 will be described later with reference to FIG. 4.

[0054] The communication device 116 is hardware for communicating with external devices such as the POS register system 20 and the computer device 12 that exist outside the server device 10.

[0055] Next, the configuration of the computer device 12 will be described.

[0056] 1, the computer device 12 has a processing device 121, a storage device 125 that stores various information, and a communication device 126. The processing device 121, the storage device 125, and the communication device 126 will be described with reference to FIG.

[0057] The processing device 121 is a processor that controls the entire computer device 12, and is configured, for example, in the same manner as the processing device 211 of the securities processing device 210 described in Fig. 2. For example, the processing device 121 is configured to include one or more CPUs.

[0058] The storage device 125 is configured, for example, in the same manner as the storage device 215 of the securities processing device 210 described in Fig. 2. For example, the storage device 125 includes one or both of a volatile memory such as RAM that functions as a working area for the processing device 121 and a non-volatile memory such as EEPROM that stores various information. The storage device 125 may store, for example, image information indicating an image of the securities GT read by the image scanner 14.

[0059] The communication device 126 is hardware for communicating with an external device such as the server device 10 that exists outside the computer device 12 .

[0060] The configurations of the server device 10 and the computer device 12 are not limited to the example shown in Fig. 3. For example, the server device 10 may have a display device 128 and an operation device 129. In this case, the computer device 12 may be omitted from the currency handling system 1.

[0061] Next, the bill type table TBL10 stored in the storage device 115 of the server device 10 will be described with reference to FIG.

[0062] Fig. 4 is an explanatory diagram for explaining an example of the security type table TBL10 shown in Fig. 3. The security type table TBL10 has, for example, one or more records. In the example shown in Fig. 4, the security type table TBL10 has a plurality of records that correspond one-to-one to the plurality of types of securities GT registered in the security type table TBL12.

[0063] Each record in the security type table TBL10 has, for example, information indicating the identification number, name, face value, and type, as well as image information. The identification number is a number that serves as an ID (identifier) ​​for identifying each type of security GT from among multiple types. The name is the name of the type of security GT that corresponds to the identification number. Specifically, the name is the name of each security GT, such as "XX Gift Card 5000 Yen Certificate" and "YY Gift Card 1000 Yen Certificate." The face value is the amount written on the security GT. In other words, the face value indicates the unit price of the security GT.

[0064] The type indicates whether the security GT is a common security or a unique security. Unique security certificates are not registered in the security type table TBL10, so in the security type table TBL10 shown in Figure 4, all three security GTs with identification numbers "001", "002", and "003" are common security certificates.

[0065] The image information indicates an image of the security GT. In this embodiment, the image information held by each record includes both image information indicating an image of the front side of the security GT and image information indicating an image of the back side of the security GT. However, the image information held by each record may be either image information indicating an image of the front side of the security GT or image information indicating an image of the back side of the security GT. Furthermore, the image information held by each record may be the storage destination of the image information (for example, an address indicating the memory area where the image information is stored).

[0066] Information including image information and information indicating the name, face value, and type of each record corresponds to, for example, security information about the security GT corresponding to the identification number. The security information is also information for registering the security GT in the security type table TBL10. For example, by storing security information about the security GT in the security type table TBL10, the security GT is registered in the security type table TBL10. When the image information is stored in the security type table TBL10, the image information of the security GT may be stored in the storage device 115 in which the security type table TBL10 is stored, or may be stored in a storage device different from the storage device 115. The security information may also include the identification number.

[0067] In this way, in the denomination table TBL12, for each type of security GT, the identification number, name, face value, type, and image information are associated with one another.

[0068] Here, the type of securities GT is classified by, for example, a combination of the issuer and face value of the securities GT. Therefore, for example, if face values ​​are different among multiple securities GTs issued by the same issuer (for example, "XX gift card 1000 yen certificate," "XX gift card 5000 yen certificate," and "XX gift card 10000 yen certificate"), the multiple securities GTs are of different types. Also, for example, if issuers are different among multiple securities GTs with the same face value (for example, "XX gift card 1000 yen certificate," "YY gift card 1000 yen certificate," and "ZZ gift card 1000 yen certificate"), the multiple securities GTs are of different types.

[0069] The type of security GT is not limited to a combination of the issuer and face value of the security GT. For example, if a single company that issues a security GT issues multiple different types of security GT, the type of security GT may be classified by a combination of the issuer, face value, and type of security GT. The types of security GT may include nationwide security GTs and regionally-limited security GTs. However, since regionally-limited security GTs are unique securities, they are registered in the security type table TBL12 but not in the security type table TBL10.

[0070] The configuration of the security type table TBL12 is not limited to the example shown in Fig. 4. For example, each record of the security type table TBL12 may further include information indicating the issuer of the security GT, or may include information indicating the issuer of the security GT instead of the name. Also, for example, each record of the security type table TBL12 may further include information indicating the expiration date of the security GT.

[0071] Next, the bill type table TBL12 stored in the storage device 215 of the securities processing device 210 will be described with reference to FIG.

[0072] FIG. 5 is an explanatory diagram for explaining an example of the bill type table TBL12 shown in FIG.

[0073] As explained in Fig. 2, the denomination table TBL12 is a denomination table TBL10 transmitted from the server device 10 to the POS register system 20 (more specifically, the securities processing device 210) in which securities GTs (unique securities) that can only be used at specific stores are appropriately registered. In other words, the denomination table TBL12 may be considered to include the denomination table TBL10. For example, in a POS register system 20 installed in a store that does not handle unique securities, the denomination table TBL12 stored in the storage device 215 is the same as the denomination table TBL10 transmitted from the server device 10. Fig. 5 explains the denomination table TBL12 used in a POS register system 20 installed in a store that handles unique securities.

[0074] The certificate type table TBL12 is similar to the certificate type table TBL10, except that unique certificates are registered in the certificate type table TBL12. In the example shown in FIG. 5, a "5,000 yen AA Regional Promotion Certificate," which is a security GT (unique certificate) that can be used only in the AA region including the store where the POS register system 20 is installed, is newly registered in the certificate type table TBL10 shown in FIG. 4. As a result, the certificate type table TBL10 is updated to the certificate type table TBL12 in which unique certificates handled in the store where the POS register system 20 is installed and common certificates that can be used uniformly nationwide are registered. In this way, unique certificates are registered in addition to common certificates in the certificate type table TBL12. In the certificate type table TBL12 shown in FIG. 5, the three security GTs with identification numbers "001," "002," and "003" are common certificates, and the security GT with identification number "004" is a unique certificate.

[0075] In the denomination table TBL12, for example, by storing security information relating to a security GT (unique security) in the denomination table TBL12, the security GT is registered in the denomination table TBL12.

[0076] The portion of the note type table TBL12 that corresponds to the note type table TBL10 (the portion where common notes are registered) is an example of the "common database." In the example shown in Fig. 5, the portion of the three records with identification numbers "001," "002," and "003" corresponds to the "common database." In addition, the note type table TBL10 may also be considered as the "common database."

[0077] The security GT registered in the security type table TBL12 is referenced by the processing device 211 (more specifically, the recognition unit 213) of the security processing device 210, for example, when the security GT is used to settle a commodity. Hereinafter, the image information of the security GT registered in the security type table TBL12 may be referred to as reference image information.

[0078] The configuration of the note type table TBL12 is not limited to the example shown in Fig. 5. For example, the note type table TBL12 may have a note type table for common notes and a note type table for unique notes. In this embodiment, the note type table TBL10 transmitted from the server device 10 to the POS register system 20 may be used as the note type table for common notes, and unique notes may be registered and deleted from the note type table for unique notes. In an embodiment in which the note type table TBL12 has a note type table for common notes and a note type table for unique notes, the note type table for common notes is an example of a "common database."

[0079] Next, the operation of the server device 10 when registering a security GT (common note) in the security type table TBL10 will be described with reference to Fig. 6. Note that Fig. 6 describes the operation of the server device 10 when registering a security GT (common note) in the security type table TBL10, but the server device 10 can also delete a security GT (common note) registered in the security type table TBL10 from the security type table TBL10.

[0080] Fig. 6 is a flowchart showing an example of the operation of the server device 10 shown in Fig. 1. The operation shown in Fig. 6 is executed when a security GT (common security) is registered in the security type table TBL10.

[0081] First, in step S100, the processing device 111 functions as the image information acquisition unit 112 and acquires image information of the security GT to be registered in the security type table TBL10 from the computer device 12. For example, the image information acquisition unit 112 acquires image information of the security GT read by the image scanner 14 from the image scanner 14 via the computer device 12. Note that the image information acquisition unit 112 may also acquire image information of the security GT read by an image input device other than the image scanner 14 (for example, a smartphone, a camera, etc.).

[0082] Next, in step S120, the processing device 111 functions as the registration unit 114 and specifies the name, face value, and type of the security GT to be registered in the security type table TBL10. The method of specifying the identification number, name, face value, and type of the security GT is not particularly limited.

[0083] For example, the registration unit 114 may cause the display device 128 of the computer device 12 to display a screen for accepting input of the name, face value, and type of security GT to be registered in the security type table TBL10. In this embodiment, the registration unit 114 identifies the name, face value, and type of security GT based on the results of input on the screen.

[0084] Incidentally, for example, either a common note or a unique note is input as the type of security GT. However, since only common notes can be registered in the security type table TBL10, it is preferable that the type of security GT is automatically input as "common note" and cannot be rewritten. Furthermore, in an aspect in which a screen in which "unique note" can be input as the type of security GT is displayed on the display device 128, if "unique note" is input, it is preferable that a warning be displayed on the display device 128 to the effect that the server device 10 cannot register a unique note in the security type table TBL10.

[0085] Furthermore, the registration unit 114 may identify the name, face value, and type of the security GT, for example, based on the image information of the security GT acquired in step S100. In this embodiment as well, if the type of the security GT is identified as a unique security based on the image information of the security GT, it is preferable that the server device 10 displays on the display device 128 a warning that the unique security cannot be registered in the security type table TBL10.

[0086] A series of processes in steps S100 and S120 provides security information on the security GT to be registered in the security type table TBL10. After executing the process in step S120, the processing device 111 advances the process to step S140.

[0087] In step S140, the processing device 111 functions as the registration unit 114 and registers the security GT in the denomination table TBL10 based on the image information, identification number, name, face value, and type of the security GT. For example, the registration unit 114 registers the security GT in the denomination table TBL10 by storing the security information (such as the name, face value, type, and image information of the security GT) obtained by the series of processes in steps S100 and S120 in the denomination table TBL10. Note that the identification number for identifying the security GT to be registered in the denomination table TBL10 may be automatically assigned to the security GT when the security GT is registered in the denomination table TBL10, for example. Alternatively, input of the identification number may be accepted in the process of step S120, etc.

[0088] Next, in step S160, the processing device 111 functions as the registration unit 114 and determines whether there is another security GT to be registered in the security type table TBL10. For example, the registration unit 114 displays a screen for accepting input as to whether there is another security GT to be registered in the security type table TBL10 on the display device 128 of the computer device 12. Then, based on the result of input on the screen, the registration unit 114 determines whether there is another security GT to be registered in the security type table TBL10. In this way, in step S160, it is determined whether or not another security GT is to be registered in the security type table TBL10.

[0089] If the result of the determination in step S160 is positive, that is, if there is another security GT to be registered in the security type table TBL10, the processing device 111 returns the process to step S100. On the other hand, if the result of the determination in step S160 is negative, that is, if there is no other security GT to be registered in the security type table TBL10, the processing device 111 ends the process of registering the security GT (common security) in the security type table TBL10 (the operation shown in FIG. 6).

[0090] In this way, if the security GT whose image information has been acquired in step S100 is a common security, the registration unit 114 registers the security GT in the security type table TBL10 based on the image information acquired in step S100, etc. As described above, only common security GTs can be registered in the security type table TBL10. Therefore, if the security GT whose image information has been acquired in step S100 is a unique security, the registration unit 114 does not register the security GT in the security type table TBL10 and terminates processing for the security GT. That is, in this embodiment, the server device 10 does not need to manage security GTs (unique security) that can only be used at specific stores. Therefore, the server device 10 only needs to manage, for example, currently usable common security. In this way, in this embodiment, management of the security GT by the server device 10 can be facilitated.

[0091] The operation of the server device 10 is not limited to the example shown in FIG. 6. For example, a process of determining whether to stop the process of registering the security GT in the security type table TBL10 may be executed between step S100 and step S120, or between step S120 and step S140. Also, for example, all of the image information indicating images of the security GT to be registered in the security type table TBL10 may be acquired before executing step S120. In this embodiment, if the result of the determination in step S160 is positive, that is, if there is a security GT not registered in the security type table TBL10 among the security GTs whose image information was acquired in step S100, the processing device 111 returns the process to step S120. Also, for example, in an embodiment in which the series of processes of steps S100, S120, and S140 are executed for each security GT, the process of step S160 may be omitted.

[0092] Next, the operation of the securities processing device 210 when registering a securities GT (unique note) in the security type table TBL12 will be described with reference to Figure 7. Note that Figure 7 describes the operation of the securities processing device 210 when registering a securities GT (unique note) in the security type table TBL12, but the securities processing device 210 can also delete a securities GT (unique note) registered in the security type table TBL12 from the security type table TBL12.

[0093] Figure 7 is a flowchart showing an example of the operation of the securities processing device 210 shown in Figure 1. The operation shown in Figure 7 is executed when registering a securities GT (unique note) in the note type table TBL12. Figure 7 will mainly explain the operation of the processing device 211 that the securities processing device 210 has.

[0094] First, in step S200, the processing device 211 functions as the image information acquisition unit 212 and acquires image information of the security GT to be registered in the security type table TBL12 from the image input device 217. For example, the image information acquisition unit 212 acquires image information of the security GT to be registered (image information to be registered) from the image input device 217. For example, when a user such as a store employee inserts the security GT to be registered into the security processing device 210, the image input device 217 reads the front and back of the security GT inserted into the security processing device 210 and generates image information of the security GT. Then, the image information of the security GT to be registered (image information to be registered) generated by the image input device 217 is acquired by the image information acquisition unit 212. Note that the image information acquisition unit 212 may acquire image information of the security GT read by an image input device other than the image input device 217 (for example, a smartphone, a camera, etc.).

[0095] Next, in step S220, the processing device 211 functions as the registration unit 214 and accepts input of the name, face value, and type of the security GT to be registered.

[0096] For example, the registration unit 214 displays a screen (for example, the operation screen G21 shown in FIG. 9) for accepting input of the name, face value, and type of the security GT to be registered on the display device 228 of the POS register 220. The name, face value, and type of the security GT to be registered are examples of "predetermined information."

[0097] Incidentally, for example, either a common note or a unique note is input as the type of security GT. However, since the registration unit 214 can only register unique notes in the security type table TBL12, it is preferable that the type of security GT is automatically input as unique note and cannot be rewritten. Furthermore, in an aspect in which a screen in which common note can be input as the type of security GT is displayed on the display device 228, if common note is input, it is preferable that a warning be displayed on the display device 228 to the effect that common notes cannot be registered in the security type table TBL12 in the POS register system 20.

[0098] After executing the process of step S220, the processing device 211 advances the process to step S230.

[0099] Next, in step S230, the processing device 211 functions as the registration unit 214 and determines whether or not the input of the name, face value, and type of the security GT to be registered has been completed. For example, when the confirmation button BT20 on the operation screen G21 shown in Fig. 9 is pressed, the registration unit 214 determines that the input of the name, face value, and type of the security GT to be registered has been completed.

[0100] If the result of the determination in step S230 is positive, i.e., if the input of the name, face value, and type of the security GT to be registered is complete, the processing device 211 proceeds to step S240. On the other hand, if the result of the determination in step S230 is negative, i.e., if the input of the name, face value, and type of the security GT to be registered is not complete, the processing device 211 proceeds to step S232.

[0101] In step S232, the processing device 211 functions as the registration unit 214 and determines whether or not to cancel the process of registering the securities GT to be registered in the security type table TBL12. For example, when the cancel button BT22 on the operation screen G21 shown in Fig. 9 is pressed, the registration unit 214 determines to cancel the process of registering the securities GT to be registered in the security type table TBL12.

[0102] If the result of the determination in step S232 is positive, that is, if the process of registering the securities GT to be registered in the security type table TBL12 is to be stopped, the processing device 211 proceeds to step S260. On the other hand, if the result of the determination in step S232 is negative, that is, if the process of registering the securities GT to be registered in the security type table TBL12 is not to be stopped, the processing device 211 returns the process to step S230.

[0103] A series of processes from step S200 to step S232 allows obtaining securities information on the securities GT to be registered. Specifically, the securities information on the securities GT to be registered is obtained by completing the acquisition of image information on the securities GT to be registered and the input of the name, face value, and type of the securities GT to be registered. For example, the registration unit 214 identifies the name, face value, and type of the securities GT to be registered based on the results of the input received in step S220. After the input of the name, face value, and type of the securities GT to be registered is completed (i.e., when the result of the determination in step S230 is positive), the process of step S240 is executed.

[0104] In step S240, the processing device 211 functions as the registration unit 214 and registers the security GT to be registered in the security type table TBL12 based on the image information, identification number, name, face value, and type of the security GT. For example, the registration unit 214 stores security information including the image information to be registered acquired in step S200 and the name, face value, and type of the security GT to be registered identified based on the result of the input accepted in step S220 in the security type table TBL12. As a result, the security GT to be registered is registered in the security type table TBL12. Note that the identification number for identifying the security GT to be registered may be automatically assigned to the security GT to be registered when the security GT to be registered is registered in the security type table TBL12, for example. Alternatively, input of the identification number may be accepted in the processing of step S220.

[0105] After executing the process of step S240, the processor 211 advances the process to step S260.

[0106] In step S260, the processing device 211 functions as the registration unit 214 and determines whether there is another security GT to be registered in the security type table TBL12. For example, the registration unit 214 displays a screen for receiving input as to whether there is another security GT to be registered in the security type table TBL12 on the display device 228 of the POS register 220. Then, based on the result of input on the screen, the registration unit 214 determines whether there is another security GT to be registered in the security type table TBL12. In this way, in step S260, it is determined whether or not another security GT is to be registered in the security type table TBL12.

[0107] If the result of the determination in step S260 is positive, that is, if there is another security GT to be registered in the security type table TBL12, the processing device 211 returns the process to step S200. On the other hand, if the result of the determination in step S260 is negative, that is, if there is no other security GT to be registered in the security type table TBL12, the processing device 211 ends the process of registering the security GT (unique security) in the security type table TBL12 (the operation shown in FIG. 7).

[0108] In this way, when the security GT to be registered is a unique security, the registration unit 214 registers the security GT to be registered in the security type table TBL12 based on the registration target image information, etc., acquired in step S200. As mentioned above, the security GT that the registration unit 214 can independently register in the security type table TBL12 is only a unique security. Therefore, when the security GT (security GT to be registered) whose image information is acquired in step S200 is a common security, the registration unit 214 does not register the security GT in the security type table TBL12 and terminates processing for the security GT.

[0109] In this embodiment, the POS register system 20 can register a security GT (unique certificate) that can only be used at a specific store in the certificate type table TBL12, and delete a security GT (unique certificate) that can only be used at a specific store from the certificate type table TBL12. Therefore, in this embodiment, it becomes possible for each store or region to use security GT (unique certificate) such as a negotiable security or a non-negotiable security at its own discretion, thereby increasing the degree of freedom in management at each store.

[0110] Furthermore, in this embodiment, the POS register system 20 installed in each store registers and deletes unique notes in the note type table TBL12, which prevents unnecessary unique notes that can only be used in other stores from being registered in the note type table TBL12. As a result, in this embodiment, it is possible to prevent an unnecessary increase in the usage capacity of the storage device 215 that stores the note type table TBL12.

[0111] Furthermore, the POS register system 20 cannot register common tickets to the certificate type table TBL12 or delete common tickets from the certificate type table TBL12. Therefore, in this embodiment, compared to the comparative example in which the server device manages both unique tickets and common tickets, it is possible to prevent the server device 10 from making management of securities GT (for example, keeping track of currently available common tickets) more complicated.

[0112] Furthermore, in this embodiment, as described with reference to FIG. 6 and the like, the server device 10 does not register unique notes in the note type table TBL10. Therefore, in this embodiment, compared to the above-mentioned comparative example, it is possible to suppress an increase in the amount of data in the note type table TBL10 transmitted from the server device 10 to the POS register system 20. Furthermore, in this embodiment, it is possible to reduce the number of types of securities GT managed by the server device 10 compared to the above-mentioned comparative example. As a result, in this embodiment, the note type table TBL10 tends to be updated less frequently, and therefore the note type table TBL10 can be transmitted less frequently from the server device 10 to the POS register system 20.

[0113] Furthermore, in this embodiment, the server device 10 only needs to distribute recognition software for common securities to the POS register systems 20 to identify security GTs; it is not necessary to distribute recognition software for unique securities. With typical recognition software using AI (artificial intelligence), when a new security GT is registered, a large amount of reference data (teaching data) must be prepared and used to train the recognition software for that security GT. Because unique securities are not registered in the security type table TBL10, the server device 10 does not need to learn about unique securities, nor does it need to distribute recognition software for unique securities. Furthermore, because recognition software for unnecessary unique securities (recognition software for unnecessary unique securities that can only be used at other stores) is not transmitted from the server device 10 to each POS register system 20, the storage of unnecessary recognition software can be prevented. Therefore, in this embodiment, unnecessary increases in the usage capacity of the storage device 215 can be prevented.

[0114] The operation of the securities processing device 210 is not limited to the example shown in FIG. 7. For example, a process for determining whether to stop the process of registering the securities GT in the security type table TBL12 may be executed between steps S100 and S120. Furthermore, for example, all of the image information representing images of the securities GT to be registered in the security type table TBL12 may be acquired before executing step S220. In this embodiment, if the result of the determination in step S260 is positive, i.e., if there is a securities GT not registered in the security type table TBL12 among the securities GT whose image information was acquired in step S200, the processing device 211 returns the process to step S220. Furthermore, for example, in an embodiment in which the series of processes from step S200 to step S240 is executed for each security GT, the process of step S260 may be omitted.

[0115] Next, examples of operation screens G20 and G21 when registering a security GT (unique security) in the security type table TBL12 will be described with reference to Figures 8 and 9. Hereinafter, the operation screen G20 shown in Figure 8 and the operation screen G21 shown in Figure 9 may be collectively referred to as operation screen G.

[0116] 8 is an explanatory diagram illustrating an example of an operation screen G20 for confirming the image of the security GT read by the image input device 217. In this embodiment, an operation screen G such as the operation screen G20 is displayed on the display device 228 of the POS register 220. For example, when the processing device 211 of the security processing device 210 acquires image information of the security GT to be registered (when the processing of step S200 shown in FIG. 7 is executed), the display device 228 displays the operation screen G20 under the control of the processing device 211.

[0117] The operation screen G20 includes, for example, a text area TX, security image areas IA1 and IA2, a confirm button BT20, and a cancel button BT22. Hereinafter, the security image areas IA1 and IA2 may be collectively referred to as the security image area IA, and the confirm button BT20, the cancel button BT22, etc. may be collectively referred to as the button BT.

[0118] The text area TX displays explanatory text for operations performed by the user of the POS register 220. In the example shown in Fig. 8, the text area TX displays the message "If there are no problems with the read result, please touch [Confirm]."

[0119] In the security image area IA1, for example, an image of the front side of security GT read by the image input device 217 is displayed. In addition, in the security image area IA2, for example, an image of the back side of security GT read by the image input device 217 is displayed. That is, in the security image areas IA (IA1 and IA2), an image of security GT indicated by the registration target image information acquired by the processing device 211 of the security processing device 210 (more specifically, the image information acquisition unit 212) is displayed.

[0120] The confirmation button BT20 and the cancel button BT22 are buttons BT for a GUI (Graphical User Interface). Selection of a button BT such as the confirmation button BT20 or the cancel button BT22 may be achieved by, for example, a pointing device such as a mouse. Alternatively, selection of a button BT may be achieved by contacting the button BT (more precisely, an image showing the button BT) in the operation screen G20 displayed on the display device 228 with an object such as a finger, or by pressing the button BT. In the following, selection of a button BT is achieved by pressing the button BT.

[0121] For example, the confirmation button BT20 is pressed when there is no problem with the image of the security GT read by the image input device 217. Pressing the confirmation button BT20 causes the operation screen G displayed on the display device 228 to transition from the operation screen G20 to the operation screen G21 shown in Fig. 9. The operation screen G21 shown in Fig. 9 is a screen for accepting input of the name, face value, and type of the security GT to be registered. In other words, pressing the confirmation button BT20 causes the processing of step S220 shown in Fig. 7 to be executed.

[0122] Furthermore, for example, the cancel button BT22 is pressed when there is a problem with the image of the security GT read by the image input device 217, or when the registration of the security GT read by the image input device 217 in the security type table TBL12 is to be canceled. By pressing the cancel button BT22, for example, the processing of step S260 shown in Fig. 7 is executed. Alternatively, by pressing the cancel button BT22, the operation shown in Fig. 7 ends.

[0123] It should be noted that the operation screen G20 is not limited to the example shown in Fig. 8. For example, the image of the security GT may be displayed in a manner that allows it to be enlarged or reduced.

[0124] 9 is an explanatory diagram illustrating an example of an operation screen G21 that accepts input of the name, face value, and type of securities GT to be registered. The operation screen G21 is an example of an "input screen." For example, when the processing of step S220 shown in FIG. 7 is executed, the display device 228 displays the operation screen G21 under the control of the processing device 211.

[0125] The operation screen G21 includes, for example, a text area TX, an input interface IIF20, a confirm button BT20, and a cancel button BT22.

[0126] In the example shown in FIG. 9, the text area TX displays, for example, a sentence such as "Enter each item, and when you have completed entering all the items, touch [Confirm]."

[0127] The input interface IIF20 is a GUI for inputting, for example, the name, face value, type, and expiration date of the securities GT to be registered. For example, the name, face value, type, and expiration date of the securities GT to be registered are input via the operating device 229 of the POS register 220. In the example shown in FIG. 9, the name and face value of the securities GT to be registered are required fields. The type of securities GT to be registered may be input by selecting from various pre-registered individual certificates using a pull-down menu, such as a local gift certificate, a store coupon, a store service certificate, or a Company A beer certificate. In this embodiment, if the securities GT scanned by the image input device 217 is a common certificate, such as a gift certificate issued by a credit company or a department store, there is no option to select from the pull-down menu, making it impossible to input the type of securities GT. This prevents common certificates from being erroneously registered in the certificate type table TBL12. The pull-down menu for selecting the type of securities GT may display both unique certificates and common certificates, allowing only individual certificates to be selected.

[0128] The Confirm button BT20 is pressed, for example, when the input of the name, face value, type, and expiration date of the security GT to be registered is completed. By pressing the Confirm button BT20, for example, the process of step S240 shown in FIG. 7 is executed.

[0129] The Cancel button BT22 is pressed, for example, when canceling the registration of the security GT read by the image input device 217 in the type table TBL12. Pressing the Cancel button BT22 causes the processing of step S260 shown in Fig. 7 to be executed. Note that if neither the Confirm button BT20 nor the Cancel button BT22 is pressed, the processing returns to step S230 shown in Fig. 7.

[0130] It should be noted that the operation screen G21 is not limited to the example shown in FIG. 9. For example, the operation screen G21 may include a button BT for returning the operation screen G displayed on the display device 228 from the operation screen G21 to the operation screen G20. Also, for example, a common ticket may be input as the type of the security GT. In this aspect, when the confirmation button BT20 is pressed with information indicating a common ticket (for example, "department store gift certificate") input as the type of the security GT, the processing for the security GT may be terminated without registering the security GT to be registered in the security type table TBL12. In this case, the registration unit 214 may cause the display device 228 to display a warning that the security GT to be registered will not be registered in the security type table TBL12.

[0131] Next, the operation of the POS register system 20 when paying for merchandise will be described with reference to FIG.

[0132] Fig. 10 is a flowchart showing an example of the operation of the POS register system 20 shown in Fig. 1. Note that Fig. 10 shows the operation of the POS register system 20 when a customer pays for merchandise using a security GT, focusing on the operation of the security processing device 210. Fig. 10 does not provide a detailed description of the operation of the POS register system 20 when paying for merchandise using cash, a credit card, electronic money, or the like.

[0133] A series of processes from step S290 to step S294 shown in Fig. 10 is executed by the processing device 211 of the securities processing device 210. Then, the process of step S298 is executed by the POS register 220 and the change dispenser 230. In Fig. 10, the operation of the POS register system 20 will be explained using an example in which the securities GT are gift certificates. For example, the process of step S290 is executed when a customer pays for goods using a gift certificate.

[0134] First, in step S290, the processing device 211 functions as the image information acquisition unit 212 and acquires image information (image information to be settled) of the security GT inserted into the security processing device 210 from the image input device 217. For example, when an employee who has received a security GT (gift certificate) from a customer inserts the security GT into the security processing device 210, the image input device 217 reads the front and back of the security GT inserted into the security processing device 210 and generates image information of the security GT. Then, the image information acquisition unit 212 acquires the image information of the security GT (image information to be settled) generated by the image input device 217.

[0135] Next, in step S292, the processing device 211 functions as the recognition unit 213 and compares the security GT inserted into the security processing device 210 with the security GT registered in the security type table TBL12. For example, the recognition unit 213 compares each of the image information (reference image information) of the multiple security GTs registered in the security type table TBL12 with the image information (settlement target image information) acquired in step S290, thereby identifying the security GT inserted into the security processing device 210.

[0136] The identification of the security GT performed by the identification unit 213 is, for example, to identify the type of security GT specified by a combination of the issuer and face value of the security GT. For example, the identification unit 213 compares each of the plurality of reference image information with the settlement target image information to search for a security GT of the same type as the security GT inserted into the security processing device 210 from among the security GTs registered in the security type table TBL12. This identifies whether or not a security GT of the same type as the security GT inserted into the security processing device 210 is registered in the security type table TBL12. Note that the method of comparing the reference image information with the settlement target image information is not particularly limited, and any known method (for example, a method of comparing the feature amount of the image indicated by the reference image information with the feature amount of the image indicated by the settlement target image information) can be used.

[0137] Next, in step S294, the processing device 211 functions as the recognition unit 213 and determines whether the type of security GT inserted into the security processing device 210 matches any of the security GTs registered in the security type table TBL12. For example, the recognition unit 213 determines whether a security GT of the same type as the security GT inserted into the security processing device 210 is registered in the security type table TBL12.

[0138] If the result of the determination in step S294 is positive, i.e., if a security GT of the same type as the security GT inserted into the securities processing device 210 is registered in the security type table TBL12, the processing device 211 proceeds to step S298. On the other hand, if the result of the determination in step S294 is negative, i.e., if a security GT of the same type as the security GT inserted into the securities processing device 210 is not registered in the security type table TBL12, the processing device 211 proceeds to step S296.

[0139] In step S296, the processing device 211 functions as the recognition unit 213 and returns the security GT inserted into the security processing device 210. As a result, for example, the security GT inserted into the security processing device 210 is returned to the input / output port IOP. After executing the process of step S296, the processing device 211 proceeds to step S298.

[0140] In step S298, the POS register 220 and the change dispenser 230 execute the settlement process for the product in accordance with the recognition result in the securities processing device 210 (more specifically, the recognition unit 213). For example, if the result of the determination in step S294 is positive, the POS register 220 and the change dispenser 230 execute the settlement process for the product based on the securities information (e.g., face value, etc.) related to the securities GT inserted into the securities processing device 210. Also, for example, if the result of the determination in step S294 is negative, the securities GT inserted into the securities processing device 210 is returned, and the POS register 220 and the change dispenser 230 execute the settlement process for the product without using the securities information related to the securities GT.

[0141] By executing the process of step S298, the payment process for the product is completed, and the operation shown in FIG. 10 ends.

[0142] As described above, in this embodiment, it is possible to prevent unnecessary unique notes that can only be used at other stores from being registered in the note type table TBL12. That is, in this embodiment, an appropriate note type table TBL12 can be used in each securities processing device 210. As a result, in this embodiment, it is possible to reduce the load on the processing device 211 when identifying a security GT, compared to an aspect in which a security GT is identified using a note type table in which unnecessary unique notes are registered. Furthermore, in this embodiment, it is possible to improve the processing speed and identification accuracy when identifying a security GT, compared to an aspect in which a security GT is identified using a note type table in which unnecessary unique notes are registered.

[0143] The operation of the POS register system 20 when a customer uses a security GT to pay for merchandise is not limited to the example shown in Fig. 10. For example, after the processing of step S296 is executed, a determination may be made as to whether to return the processing to step S290 or to proceed to step S298. Specifically, for example, after the processing of step S296 is executed, a screen may be displayed on the display device 228 of the POS register 220, prompting the customer to select whether to read the security GT again or to perform the payment process without using the security GT.

[0144] As described above, in this embodiment, the currency handling system 1 includes a server device 10 and multiple POS register systems 20 communicatively connected to the server device 10. Each of the multiple POS register systems 20 includes a POS register 220, a change dispenser 230, and a security processing device 210 that processes inserted security GTs. The security processing device 210 includes an image input device 217 that generates image information of the inserted security GTs, a storage device 215 that stores a security type table TBL12 in which multiple security GTs are registered as a database used to identify the inserted security GTs, a registration unit 214 that registers the security GTs in the security type table TBL12, and an image information acquisition unit 212 that can acquire the image information generated by the image input device 217 as registration target image information that indicates an image of the security GT to be registered. Each of the multiple security GTs registered in the security type table TBL12 belongs to either a first type of security GT (unique security GT) or a second type of security GT (common security GT). If the security GT to be registered is a first type of security GT, the registration unit 214 registers the security GT to be registered in the security type table TBL12 based on the registration target image information, and if the security GT to be registered is a second type of security GT, the registration unit 214 does not register the security GT to be registered in the security type table TBL12 and terminates processing for the security GT to be registered.

[0145] As described above, in this embodiment, each securities processing device 210 can independently register the first type of securities GT (unique securities) in the security type table TBL12. This allows each securities processing device 210 to use the appropriate security type table TBL12. Furthermore, in this embodiment, for example, the store where the securities processing device 210 is installed can independently manage the first type of securities GT, thereby increasing the degree of management flexibility of each store. Furthermore, the securities processing device 210 does not independently register the second type of securities GT (common securities) in the security type table TBL12. Therefore, in this embodiment, for example, the server device 10 (a device external to the securities processing device 210) can easily manage the second type of securities GT registered in the security type table TBL12 in common among multiple securities processing devices 210. In other words, this embodiment facilitates the server device 10's management of the second type of securities GT registered in the security type table TBL12. Furthermore, in this embodiment, for example, the server device 10 does not need to transmit information indicating the first type of securities GT registered in the type table TBL12 to each securities processing device 210. Therefore, in this embodiment, it is possible to prevent an increase in the amount of information data transmitted from the server device 10 to each securities processing device 210.

[0146] Furthermore, in this embodiment, the second type of security GT is a security GT that can be used in common among the multiple security processing devices 210, and the first type of security GT is a security GT that can be used only in a predetermined security processing device 210 among the multiple security processing devices 210. In other words, the second type of security GT is a security GT that can be used in common among the multiple POS register systems 20, and the first type of security GT is a security GT that can be used only in a predetermined POS register system 20 among the multiple POS register systems 20. For example, in this embodiment, the security processing device 210 can independently register the first type of security GT that can be used only in the predetermined security processing device 210, including the security processing device 210, in the security type table TBL12.

[0147] In this embodiment, the image information acquisition unit 212 may acquire settlement target image information indicating an image of the security GT inserted into the security processing device 210. The security processing device 210 may further include a recognition unit 213 that identifies the inserted security GT by comparing the settlement target image information with each of a plurality of reference image information indicating images of a plurality of security GTs registered in the security type table TBL12. In this case, the POS register 220 and the change dispenser 230 execute a settlement process for the product according to the recognition result of the recognition unit 213. As described above, in this embodiment, the process of recognizing the security GT inserted into the security processing device 210 is executed using the security type table TBL12. In this embodiment, the process of recognizing the security GT is executed using the security type table TBL12 in which the first type of security GT is appropriately registered, thereby reducing the load on the recognition unit 213 when identifying the security GT. In addition, in this embodiment, the process of recognizing the security GT is executed using the security type table TBL12 in which the first type of security GT is appropriately registered, thereby improving the processing speed and recognition accuracy when identifying the security GT.

[0148] In addition, in this embodiment, the registration unit 214 displays on the display device 228 an operation screen G21 that accepts input of predetermined information other than the registration target image information among the securities information for registering the securities GT to be registered in the security type table TBL12. If the securities GT to be registered is a first type of securities GT, the registration unit 214 registers the securities GT to be registered in the security type table TBL12 based on the securities information. If the securities GT to be registered is a second type of securities GT, the registration unit 214 displays on the display device 228 a warning that the securities GT to be registered will not be registered in the security type table TBL12, and terminates processing for the securities GT to be registered without registering the securities GT to be registered in the security type table TBL12. Thus, in this embodiment, if the securities GT to be registered is a second type of securities GT, the display device 228 displays a warning that the securities GT to be registered will not be registered in the security type table TBL12. Therefore, in this embodiment, the user of the POS register system 20 can easily understand that they were attempting to register a second type of securities GT in the security type table TBL12 or that the securities information regarding the securities GT to be registered was incorrect. As a result, in this embodiment, it is possible to prevent the second type of security GT from being erroneously registered in the security type table TBL12.

[0149] [2. Modifications] The present invention is not limited to the above-described exemplary embodiments. Specific modified embodiments are exemplified below. Two or more embodiments selected from the following examples may be combined.

[0150] [First Modification] In the above-described embodiment, the securities processing device 210 may identify the type of the securities GT to be registered based on the registration target image information of the securities GT.

[0151] Figure 11 is a flowchart showing an example of the operation of the securities processing device 210 according to the first modified example. The operation shown in Figure 11 is executed when registering a securities GT (unique security) in the security type table TBL12. The operation shown in Figure 11 is similar to the operation shown in Figure 7, except that a series of processes in steps S210 and S212 are executed. The process in step S210 is executed, for example, after the process in step S200 has been executed and before the process in step S220 is executed.

[0152] In step S210, the processing device 211 functions as the registration unit 214 and determines whether the security GT to be registered read by the image input device 217 is a common note or not based on the registration target image information acquired in step S200. The method of determining whether the security GT to be registered is a common note or not is not particularly limited.

[0153] For example, the registration unit 214 may determine whether the security GT to be registered is a common security by using a database in which the names of the security GT that is a common security (e.g., "Department Store Gift Certificate") are registered in advance. Specifically, the registration unit 214 identifies the product name (the name of the security GT) written on the security GT to be registered by performing OCR (Optical Character Recognition) processing or the like using the registration target image information acquired in step S200. Then, the registration unit 214 determines whether the security GT to be registered is a common security by comparing the product name identified by OCR processing or the like with the name of the common security registered in the database. Note that the registration unit 214 may use the certificate type table TBL10 (more specifically, the "Name" item of the certificate type table TBL10) transmitted from the server device 10 as the database in which the names of the security GT that is a common security (e.g., "Department Store Gift Certificate") are registered in advance. The registration unit 214 may also recognize the name of the security GT to be registered by reading the barcode of the security GT to be registered.

[0154] Furthermore, for example, the registration unit 214 may determine whether the securities GT to be registered is a common certificate without using a database in which the names of securities GT that are common certificates (for example, "department store gift certificates") are pre-registered. Specifically, the registration unit 214 may determine whether the securities GT to be registered is a common certificate based on the name of the securities GT recognized by OCR processing or reading a barcode. In this method, the recognition accuracy can be improved by using AI.

[0155] If the result of the determination in step S210 is positive, that is, if the security GT to be registered is a common security, the registration unit 214 issues a warning in step S212 that the security GT to be registered will not be registered in the security type table TBL12, and urges the user to cancel the registration. For example, in step S212, the registration unit 214 displays a warning on the display device 228 that the security GT to be registered will not be registered in the security type table TBL12. The method of issuing the warning is not particularly limited, and the color of the area where the type is to be entered on the operation screen G (for example, the operation screen G24 shown in FIG. 5) may be changed to highlight it, or the area where the type is to be entered may be made to blink. Alternatively, the warning may be issued by audio. After executing the process of step S212, the processing device 211 advances the process to step S260.

[0156] On the other hand, if the result of the determination in step S210 is negative, that is, if the security GT to be registered is not a common security, the processing device 211 proceeds to step S220. That is, the processing in step S220 (accepting input of the name, face value, and type of the security GT to be registered) is executed when the security GT to be registered is a unique security. The name, face value, type, etc. of the security GT to be registered may be automatically input based on the registration target image information acquired in step S200. For example, the name, face value, type, etc. of the security GT recognized by OCR processing or barcode reading may be automatically input.

[0157] The operation of the securities processing device 210 is not limited to the example shown in Fig. 11. For example, the series of processes in steps S210 and S212 may be executed after the process in step S220 and before the process in step S230. Also, for example, the processing device 211 may execute the process in step S212 and then proceed to step S232.

[0158] Next, with reference to FIG. 12, an example of the operation screen G24 used to warn that the security GT to be registered will not be registered in the security type table TBL12 will be described.

[0159] Fig. 12 is an explanatory diagram for explaining an example of the operation screen G24 according to the first modified example. Fig. 12 shows an example of the operation screen G24 when a warning is displayed that the security GT to be registered will not be registered in the security type table TBL12. For example, when the processing of step S212 shown in Fig. 11 is executed, the display device 228 displays the operation screen G24 under the control of the processing device 211.

[0160] The operation screen G24 includes, for example, a text area TX, an input interface IIF20, and a cancel button BT22.

[0161] In the example shown in FIG. 12, the text area TX displays, for example, a message such as "This is a common ticket and cannot be registered. Please touch [Cancel]."

[0162] The input interface IIF20 is similar to the input interface IIF20 of the operation screen G21 shown in Fig. 9, for example. However, it is preferable that the operation screen G24 is in a state where it is not possible to input each item such as the name of the security GT to be registered. Also, on the operation screen G24, the type of security GT (for example, "department store gift certificate") recognized based on the registration target image information acquired in step S200 shown in Fig. 11 is automatically input as the type of security GT. Furthermore, in the example shown in Fig. 12, the area where the type is input is highlighted by being changed to a different color from the areas where other items are input.

[0163] The cancel button BT22 is pressed, for example, when canceling the registration in the type table TBL12 of the security GT read by the image input device 217. When the cancel button BT22 is pressed, for example, the process of step S260 shown in FIG.

[0164] In this manner, in this modified example, if the security GT to be registered is a common security, the registration unit 214 displays a warning on the display device 228 to the effect that the security GT to be registered will not be registered in the security type table TBL12, and terminates processing for the security GT to be registered without registering the security GT to be registered in the security type table TBL12.

[0165] The operation screen G24 is not limited to the example shown in FIG. 12. For example, the type that is automatically input may simply be either "individual note" or "common note." Furthermore, for example, the operation screen G24 may include a button BT (hereinafter referred to as ) that allows input of the name, face value, type, etc. of the security GT to be registered. For example, if the type of security GT recognized based on the image information to be registered is incorrect, i.e., if a unique note is mistakenly recognized as a common note, the button BT that allows input of the type, etc. is pressed. By pressing the button BT that allows input of the type, etc., the process of step S220 shown in FIG. 11 is executed, for example.

[0166] As described above, this modification can also achieve the same effects as the above-described embodiment. Furthermore, this modification can automatically determine whether the securities GT to be registered that are input into the securities processing device 210 are common securities. Therefore, this modification can reduce erroneous registrations, such as when a user, such as a store employee, registers a securities GT as a unique security in the security type table TBL12 even though the security is a common security. Furthermore, this modification can automatically input predetermined information, such as the name, face value, and type, of the securities GT to be registered, based on the registration target image information. This reduces the burden on users, such as employees, and reduces erroneous input of predetermined information, such as the name, face value, and type, of the securities GT to be registered.

[0167] [Second Modification] In the above-described embodiment and modified examples, the POS register system 20 may execute a registration request to register a security GT (unique security) newly registered in the security type table TBL12 in the security type table TBL12 of another POS register system 20.

[0168] Figure 13 is a flowchart showing an example of the operation of the securities processing device 210 according to the second modified example. The operation shown in Figure 13 is executed when registering a securities GT (unique security) in the security type table TBL12. The operation shown in Figure 13 is similar to the operation shown in Figure 7, except that a series of processes in steps S250 and S252 are executed. The process in step S250 is executed, for example, after the process in step S240 has been executed and before the process in step S260 is executed.

[0169] In step S250, the processing device 211 functions as the registration unit 214 and determines whether or not the security GT (unique security) registered in step S240 should also be registered in the security type table TBL12 of another security processing device 210.

[0170] For example, when an operation to request registration of a security GT (unique security) (for example, pressing the registration request button BT24 on the operation screen G22 shown in FIG. 15) is performed, the registration unit 214 determines to register the security GT in the security type table TBL12 of the other security processing device 210. Also, for example, when an operation to make a registration request for a security GT (unique security) unnecessary (for example, pressing the request no longer necessary button BT26 on the operation screen G22 shown in FIG. 15) is performed, the registration unit 214 determines not to register the security GT in the security type table TBL12 of the other security processing device 210.

[0171] If the result of the determination in step S250 is positive, i.e., if a registration request for the security GT (unique security) is to be executed, the registration unit 214 transmits security information regarding the security GT to be registered to the server device 10 in step S252. The security information is, for example, information for registering the security GT to be registered in the security type table TBL12 of another security processing device 210, and includes the name, face value, type, image information, etc. of the security GT to be registered. The security information transmitted to the server device 10 in step S252 is an example of "first security information." After executing the processing of step S252, the processing device 211 advances the processing to step S260.

[0172] On the other hand, if the result of the determination in step S250 is negative, that is, if the registration request for the security GT (unique certificate) is not to be executed, the processing device 211 advances the process to step S260.

[0173] The operation of the securities processing device 210 is not limited to the example shown in Fig. 13. For example, a series of processes in steps S250 and S252 may be added to the operation shown in Fig. 11.

[0174] Next, with reference to FIG. 14, an example of the operation of the currency handling system 1 when a registration request for a security GT (unique certificate) is executed will be described.

[0175] Fig. 14 is a sequence chart showing an example of the operation of the currency handling system 1 according to the second modified example. Fig. 14 illustrates the operation of the currency handling system 1 when a security GT (unique note) newly registered in the note type table TBL12 of the POS register system 20a is registered in the note type table TBL12 of another POS register system 20b.

[0176] First, the registration unit 214 of the POS register system 20a transmits to the server device 10 the securities information on the securities GT that have been newly registered in the security type table TBL12 of the POS register system 20a (S252).

[0177] The server device 10 stores the securities information transmitted from the POS register system 20a, for example, in the storage device 115 (S180). Note that the securities information transmitted from the POS register system 20a is securities information related to a unique note, and therefore is stored in the storage device 115 but is not stored in the note type table TBL10. The server device 10 transmits the securities information stored in the storage device 115, i.e., the securities information transmitted from the POS register system 20a, to the POS register system 20b (S182). After transmitting the securities information to the POS register system 20b, the server device 10 may delete the securities information from the storage device 115.

[0178] The registration unit 214 of the POS register system 20a registers the security GT to be registered in the security type table TBL12 based on the security information transmitted from the server device 10 (S280). For example, the registration unit 214 of the POS register system 20a stores the securities information transmitted from the server device 10 in the security type table TBL12, thereby registering the securities GT to be registered in the security type table TBL12. As a result, the security GT (unique security) newly registered in the security type table TBL12 of the POS register system 20a is newly registered in the security type table TBL12 of the POS register system 20b.

[0179] Next, an example of an operation screen G22 when registering a security GT (unique security) registered in the security type table TBL12 in the security type table TBL12 of another POS register system 20 will be described with reference to FIGS.

[0180] Fig. 15 is an explanatory diagram for explaining an example of an operation screen G22 according to the second modified example. Fig. 15 shows an example of the operation screen G22 displayed on the display device 228 when the security GT to be registered has been registered in the security type table TBL12. The operation screen G22 corresponds to, for example, a selection screen for selecting whether or not to register the security GT (unique security) registered in the security type table TBL12 in the security type table TBL12 of another POS register system 20. For example, after the processing of step S240 shown in Fig. 13 has been executed, that is, when the security GT to be registered has been registered in the security type table TBL12, the display device 228 displays the operation screen G22 under the control of the processing device 211.

[0181] The operation screen G22 includes, for example, a text area TX, an input interface IIF20, a registration request button BT24, and a no request required button BT26.

[0182] In the example shown in Figure 15, the text area TX displays, for example, the following sentence: "Registration of your unique ticket has been completed. If you wish to register it on another device, touch [Request registration]. If you do not wish to register it, touch [No request required]."

[0183] The input interface IIF20 is, for example, the same as the input interface IIF20 of the operation screen G21 shown in Fig. 9. However, since the registration of the securities GT to be registered has been completed on the operation screen G22, the contents of the registered securities GT are displayed in each field such as the name of the securities GT to be registered, and each field cannot be entered.

[0184] The registration request button BT24 is pressed, for example, when making a registration request to register a security GT (unique security) registered in the security type table TBL12 in the security type table TBL12 of another POS register system 20. When the registration request button BT24 is pressed, for example, the operation screen G displayed on the display device 228 transitions from the operation screen G22 to the operation screen G23 shown in FIG.

[0185] The "No Request Required" button BT26 is pressed, for example, when a registration request is not made to register a security GT (unique security) registered in the security type table TBL12 in the security type table TBL12 of another POS register system 20. When the "No Request Required" button BT26 is pressed, for example, the process of step S260 shown in FIG. 13 is executed.

[0186] Fig. 16 is an explanatory diagram illustrating an example of an operation screen G23 when a registration request is made. The operation screen G23 is displayed on the display device 228 when the registration request button BT24 on the operation screen G22 shown in Fig. 15 is pressed. For example, when the registration request button BT24 on the operation screen G22 shown in Fig. 15 is pressed, the processing device 211 causes the display device 228 to display the operation screen G23.

[0187] The operation screen G23 includes, for example, a text area TX, a cancel button BT22, a same store button BT28, and a same area button BT29.

[0188] In the example shown in FIG. 16, the text area TX displays, for example, a sentence such as "Please select the group you wish to register in."

[0189] The Same Store button BT28 is pressed, for example, when registering the securities GT to be registered in the security type table TBL12 of another POS register system 20 installed in the same store. Pressing the Same Store button BT28 causes the processing of step S252 shown in Fig. 13 to be executed. In this case, securities information regarding the securities GT to be registered is transmitted via the server device 10 to the other POS register system 20 set up in the same store.

[0190] Furthermore, the Same Region button BT29 is pressed, for example, when registering the securities GT to be registered in the security type table TBL12 of the POS register system 20 set up in a store in the same region. Pressing the Same Region button BT29 causes the processing of step S252 shown in Fig. 13 to be executed. In this case, the securities information on the securities GT to be registered is transmitted via the server device 10 to the POS register system 20 set up in a store in the same region.

[0191] The cancel button BT22 is pressed, for example, when canceling the registration request. For example, when the cancel button BT22 is pressed, the registration unit 214 executes the process of step S260 without executing the process of step S252 shown in FIG.

[0192] The operation screen G23 is not limited to the example shown in Fig. 16. For example, the operation screen G23 may include a GUI that allows a user to specify, from a list or the like, a store to which securities information related to securities GT to be registered is to be sent.

[0193] As described above, in this modification, in one POS register system 20 of the multiple POS register systems 20, when the registration unit 214 registers the security GT to be registered in the security type table TBL12, it transmits the first security information including the image information to be registered to a predetermined other POS register system 20 via the server device 10. In the other POS register systems 20, the registration unit 214 registers the security GT to be registered in the security type table TBL12 based on the first security information transmitted from the one POS register system 20 via the server device 10. For example, when the security GT to be registered is a first type of security GT, the registration unit 214 may register the security GT to be registered in the security type table TBL12 based on the security information, and may cause the display device 228 to display an operation screen G22 for selecting whether or not to register the security GT to be registered in the security type table TBL12 of the other POS register system 20.

[0194] This modified example also achieves the same effects as the above-described embodiment. Furthermore, in this modified example, by transmitting securities information about a securities GT (unique security) registered in the security type table TBL12 to the server device 10, the securities GT can be quickly registered in the security type table TBL12 of another POS register system 20. For example, in this embodiment, if a securities GT that can be used only in multiple POS register systems 20 installed in the same store or multiple stores in the same region needs to be quickly made usable in the multiple POS register systems 20, the securities information can be transmitted to the server device 10. By transmitting the securities information to the server device 10, the securities GT that can be used only in the multiple POS register systems 20 installed in the same store or multiple stores in the same region is quickly registered in the security type table TBL12 of the multiple POS register systems 20. As a result, the securities GT that can be used only in the multiple POS register systems 20 installed in the same store or multiple stores in the same region can be quickly made usable in the multiple POS register systems 20.

[0195] [Third Modification] In the above-described embodiment and modified examples, the POS register system 20 may request the server device 10 to register a security GT (common security) that can be used uniformly nationwide in the security type table TBL10.

[0196] 17 and 18 are flowcharts showing an example of the operation of the securities processing device 210 according to the third modified example. The operation shown in Fig. 17 is executed when a securities GT (unique certificate) that can only be used at a specific store is registered in the certificate type table TBL12, or when a request is made to the server device 10 to register a securities GT (common certificate) that can be used uniformly nationwide in the certificate type table TBL10. The operation shown in Fig. 17 is the same as the operation shown in Fig. 7, except that a series of processes from step S234 to step S238 shown in Fig. 18 are executed.

[0197] The processing of step S234 is executed, for example, when the result of the determination in step S230 is positive, that is, when the input of the name, face value, and type of the security GT to be registered is completed. The type of security GT to be registered may be automatically input based on the registration target image information acquired in step S200, or may be input by selecting a common note or an individual note using a pull-down menu. The name, face value, etc. of the security GT to be registered may also be automatically input based on the registration target image information.

[0198] In step S234, the processing device 211 functions as the registration unit 214 and determines whether the type input in the series of processes in steps S220 and S230 is a unique note. In other words, the registration unit 214 determines whether the security GT to be registered, which is read by the image input device 217, is a unique note.

[0199] If the result of the determination in step S234 is positive, that is, if the security GT to be registered is a unique security, the registration unit 214 proceeds to step S240. On the other hand, if the result of the determination in step S234 is negative, that is, if the security GT to be registered is not a unique security, the registration unit 214 proceeds to step S236 shown in Fig. 18. That is, the processing of step S236 shown in Fig. 18 is executed when the security GT to be registered is a common security.

[0200] In step S236 shown in FIG. 18, the processing device 211 functions as the registration unit 214 and issues a warning that the security GT to be registered will not be registered in the security type table TBL12.

[0201] Next, in step S237, the processing device 211 functions as the registration unit 214 and determines whether or not to register the security GT (common security) to be registered read by the image input device 217 in the security type table TBL10 of the server device 10.

[0202] For example, when an operation to request registration of a securities GT (common ticket) (for example, pressing the registration request button BT24 on the operation screen G26 shown in FIG. 19) is performed, the registration unit 214 determines that the securities GT should be registered in the certificate type table TBL10 of the server device 10. Also, for example, when an operation to cancel the registration of the securities GT (common ticket) (for example, pressing the cancel button BT22 on the operation screen G26 shown in FIG. 19) is performed, the registration unit 214 determines that the securities GT should not be registered in the certificate type table TBL10 of the server device 10.

[0203] If the result of the determination in step S237 is positive, that is, if a registration request for the securities GT (common note) is to be executed, the registration unit 214 transmits securities information on the securities GT to be registered to the server device 10 in step S238. The securities information is, for example, information for registering the securities GT to be registered in the certificate type table TBL10 of the server device 10, and includes the name, face value, type, image information, etc. of the securities GT to be registered. The securities information transmitted to the server device 10 in step S238 is an example of "second securities information."

[0204] The server device 10 stores the gift certificate information transmitted from the POS register system 20 in the denomination table TBL10, thereby registering the security GT (common security certificate) to be registered in the denomination table TBL10. This updates the denomination table TBL10. The server device 10 may check the contents of the gift certificate information transmitted from the POS register system 20 and determine whether to register the security GT as a common security certificate in the denomination table TBL10. When the server device 10 registers the security GT (common security certificate) to be registered in the denomination table TBL10 based on the gift certificate information transmitted from the POS register system 20, the server device 10 may transmit the denomination table TBL10 in which the security GT is registered to the POS register system 20. Alternatively, the server device 10 may transmit update information to the POS register system 20 indicating the difference between the updated denomination table TBL10 and the denomination table TBL10 already transmitted to the POS register system 20 (i.e., the update contents of the denomination table TBL10). The update information may be, for example, security information related to the security GT to be registered. In a mode in which update information is transmitted from the server device 10, the POS register system 20 may update the portion of the note type table TBL12 corresponding to the note type table TBL10 based on the update information transmitted from the server device 10.

[0205] After executing the process of step S238, the processor 211 advances the process to step S260 shown in FIG.

[0206] If the result of the determination in step S237 is positive, that is, if the security GT is not to be registered in the type table TBL10 of the server device 10, the processing device 211 advances the process to step S260 shown in FIG.

[0207] 17 and 18. For example, the processing device 211 (more specifically, the registration unit 214) may determine whether the securities GT (common security) to be registered read by the image input device 217 has already been registered in the security type table TBL12 before executing the process of step S236. If the securities GT to be registered has already been registered in the security type table TBL12, the registration unit 214 may also warn in step S236 that the securities GT to be registered has already been registered in the security type table TBL12. Furthermore, if the securities GT to be registered has already been registered in the security type table TBL12, the registration unit 214 may prevent the selection of a registration request for the securities GT.

[0208] Also, for example, a series of processes from step S236 to step S238 may be added to the operation shown in Fig. 11. Specifically, in the operation shown in Fig. 11, a series of processes from step S236 to step S238 may be executed instead of the process of step S212. However, in this embodiment, the registration unit 214 completes input of the name, face value, and type of the security GT to be registered by, for example, executing the process of step S220 before executing the process of step S238.

[0209] Also, for example, a series of processes from step S234 to step S238 may be added to the operation shown in FIG.

[0210] Next, with reference to FIG. 19, an example of the operation screen G26 when the security GT to be registered read by the image input device 217 is a common security will be described.

[0211] Fig. 19 is an explanatory diagram for explaining an example of the operation screen G26 according to the third modified example. Fig. 19 shows an example of the operation screen G26 displayed on the display device 228 when the securities GT to be registered is a common ticket. The operation screen G26 corresponds to a selection screen for selecting, for example, whether or not to transmit securities information related to the securities GT (common ticket) that can be used uniformly nationwide to the server device 10, which is an external device of the POS register system 20. For example, when the result of the determination in step S234 shown in Fig. 17 is negative, that is, when the securities GT to be registered is a common ticket, the display device 228 displays the operation screen G26 under the control of the processing device 211.

[0212] The operation screen G26 includes, for example, a text area TX, an input interface IIF20, a cancel button BT22, and a registration request button BT24.

[0213] In the example shown in Figure 19, the text area TX displays, for example, the following sentence: "This is a common ticket. If you want to cancel registration, touch [Cancel]. If you want to request registration, touch [Request Registration]."

[0214] The input interface IIF20 is, for example, the same as the input interface IIF20 of the operation screen G21 shown in Fig. 9. However, on the operation screen G26, since input of each item such as the name of the security GT to be registered has been completed, the input results are displayed in each item in a state where they cannot be rewritten.

[0215] The cancel button BT22 is pressed, for example, when the security GT to be registered, which has been read by the image input device 217, is not to be registered in the security type table TBL10 of the server device 10, that is, when the registration of the security GT to be registered is to be canceled. When the cancel button BT22 is pressed, the registration request to register the security GT to be registered, which has been read by the image input device 217, in the security type table TBL10 of the server device 10 is not executed. Therefore, when the cancel button BT22 is pressed, the registration unit 214 executes the process of step S260 shown in FIG. 17 without executing the process of step S238 shown in FIG. 18.

[0216] Furthermore, the registration request button BT24 is pressed, for example, when making a registration request to register the security GT to be registered that has been read by the image input device 217 in the security type table TBL10 of the server device 10. Pressing the registration request button BT24 causes the processing of step S238 shown in Fig. 18 to be executed, for example. That is, when the registration request button BT24 is pressed, the registration unit 214 transmits securities information related to the security GT to be registered to the server device 10 in step S238 shown in Fig. 18.

[0217] As described above, in this modified example, the denomination table TBL12 includes the denomination table TBL10 transmitted from the server device 10, and common securities (e.g., securities GTs that can be used nationwide) are registered in the denomination table TBL10. When the securities GT to be registered is a common security, the registration unit 214 transmits second securities information including registration target image information to the server device 10 as securities information for registering the securities GT to be registered in the denomination table TBL10. The server device 10 registers the securities GT to be registered in the denomination table TBL10 based on the second securities information transmitted from the securities processing device 210. For example, when the securities GT to be registered is a second type of securities GT, the registration unit 214 may display on the display device 228 an operation screen G26 for selecting whether or not to transmit the securities information to the server device 10, which is an external device to the POS register system 20.

[0218] In this modified example, the same effects as those of the above-described embodiment can be obtained. Furthermore, in this modified example, by transmitting securities information about the securities GT (common securities) to be registered that has been read by the image input device 217 to the server device 10, the securities GT can be promptly registered in the security type table TBL10 of the server device 10. For example, in this embodiment, when a new common security GT (unregistered security GT) that is not registered in the security type table TBL12 at each store needs to be quickly made usable at the store, securities information about the new common security GT can be transmitted to the server device 10.

[0219] By transmitting the securities information to the server device 10, securities GTs (common securities) that are not registered in the security type table TBL10 are promptly registered in the security type table TBL10. Then, the server device 10 transmits the updated security type table TBL10 or update information indicating the update contents of the security type table TBL10 to the POS register system 20. The POS register system 20 updates the security type table TBL12 based on the update information transmitted from the server device 10 or the updated security type table TBL10. This updates the portion of the security type table TBL12 that corresponds to the security type table TBL10. As a result, in this modified example, security GTs that a customer wishes to use can be promptly used in the POS register system 20. Furthermore, the updated security type table TBL10 or the update information of the security type table TBL10 is uniformly transmitted from the server device 10 to the POS register systems 20 of multiple stores. Therefore, in this modified example, new common securities can be promptly used in other stores as well.

[0220] [Fourth Modification] In the above-described embodiment and modified example, the securities processing device 210 is included in the POS register system 20, but the present invention is not limited to this. For example, the securities processing device 210 may be included in a currency processing device used in the backroom of a store.

[0221] Figure 20 is an explanatory diagram for explaining an overview of a currency handling system 1A according to a fourth modified example. The currency handling system 1A is similar to the currency handling system 1 shown in Figure 1, except that it has a currency handling device 21 instead of the POS register system 20 shown in Figure 1. In this modified example, the currency handling device 21 will be mainly described.

[0222] The currency handling system 1 includes, for example, a server device 10, a computer device 12, an image scanner 14, and multiple currency handling devices 21 (21a, 21b, and 21c) communicatively connected to the server device 10. In FIG. 20, in order to distinguish the multiple currency handling devices 21 from one another, a lowercase alphabet (a, b, or c) is added to the end of the symbol of each currency handling device 21. The server device 10 and each of the multiple currency handling devices 21 are connected to a network NW. In this modified example, for example, a security GT that can be used in multiple currency handling devices 21 including currency handling devices 21a, 21b, and 21c corresponds to a common security, and a security GT that can be used only in currency handling devices 21a and 21b of the multiple currency handling devices 21 corresponds to a unique security.

[0223] In this modification, a currency handling device 21 is installed in each of a plurality of stores (e.g., a chain of stores) that handle securities GT. That is, in this modification, a plurality of currency handling devices 21 installed in each of the plurality of stores are communicatively connected to a server device 10. However, currency handling system 1A may also have a server device 10 installed in a store and a plurality of currency handling devices 21 installed in the same store as the store in which server device 10 is installed. In this embodiment, a plurality of currency handling devices 21 installed in a store may be communicatively connected to a server device 10 installed in the store.

[0224] Next, the configuration of the currency handling device 21 will be described with reference to FIG.

[0225] FIG. 21 is a block diagram showing an example of the configuration of the currency handling device 21 shown in FIG.

[0226] The currency processing device 21 includes a securities processing device 210A, a communication device 216A, an image input device 217A, a display device 218, an operation device 219, and a cash processing device 240. In the example shown in Fig. 21, the communication device 216A and the image input device 217A are provided outside the securities processing device 210A, but one or both of the communication device 216A and the image input device 217A may be included in the securities processing device 210A.

[0227] The securities processing device 210A is similar to the securities processing device 210, except that it has an external communication device 216A and an external image input device 217A that correspond to the communication device 216 and the image input device 217, respectively, of the securities processing device 210 shown in Figure 2. For example, the securities processing device 210 has a processing device 211A and a storage device 215 that stores various information such as a control program PG21 and a bill type table TBL12.

[0228] The processing device 211A is a processor that controls the entire securities processing device 210A, and is configured, for example, in the same manner as the processing device 211 of the securities processing device 210 described in Figure 2. For example, the processing device 211A is configured to include one or more CPUs. Furthermore, the processing device 211A functions as an image information acquisition unit 212, a recognition unit 213, and a registration unit 214, for example, by executing a control program PG21 stored in the storage device 215. Note that the control program PG21 may be transmitted from another device via the network NW. Furthermore, in this modified example, the processing device 211A is capable of controlling the display device 218, the operation device 219, etc. Note that the processing device 211A may also control the entire currency processing device 21.

[0229] The image information acquisition unit 212, the recognition unit 213, and the registration unit 214 of the processing device 211A are similar to the image information acquisition unit 212, the recognition unit 213, and the registration unit 214 described in Fig. 2 etc., and therefore description thereof will be omitted. For example, registration and deletion of securities GT in the bill type table TBL12 is performed in the same manner as in the above-described embodiment and modified example.

[0230] The storage device 215 is configured, for example, in the same manner as the storage device 215 of the securities processing device 210 described in Fig. 2. For example, the storage device 215 includes one or both of a volatile memory such as a RAM that functions as a working area for the processing device 211A, and a non-volatile memory such as an EEPROM that stores various information such as the control program PG21 and the bill type table TBL12.

[0231] The communication device 216A is hardware for communicating with an external device such as the server device 10 that exists outside the currency handling device 21.

[0232] The image input device 217A is configured, for example, in the same manner as the image input device 217 of the securities processing device 210 described in Fig. 2. For example, the image input device 217A generates image information showing an image of the securities GT by capturing an image of the securities GT inserted into the currency processing device 21. The image information generated by the image input device 217A is referenced by the processing device 211.

[0233] The display device 218 is an output device such as a display that outputs to the outside, and for example displays images etc. under the control of the processing device 221A. The operation device 219 is an input device that accepts input from the outside, and for example accepts operations by an operator operating the currency processing device 21. The display device 218 and the operation device 219 may be integrated into one structure (for example, a touch panel). Furthermore, in this modified example, the processing device 211A of the securities processing device 210A can acquire information indicating the results of the input accepted by the operation device 219.

[0234] The cash processing device 240 has a processing device 241, a coin processing device 242 that processes coins, and a banknote processing device 243 that processes banknotes. The processing device 241 is a processor that controls the entire cash processing device 240, and is configured similarly to the processing device 211 of the securities processing device 210 described in Fig. 2, for example. For example, the processing device 241 is configured to include one or more CPUs.

[0235] As described above, in this modified example, the currency handling device 21 includes a cash handling device 240, a securities handling device 210A, an image input device 217A, and a display device 218. The image input device 217A generates image information of the inserted securities GT. The securities handling device 210A includes a storage device 215 that stores a denomination table TBL12 in which multiple securities GTs are registered as a database used to identify the inserted securities GT, a registration unit 214 that registers the securities GT in the denomination table TBL12, and an image information acquisition unit 212 that acquires the image information generated by the image input device 217A as registration target image information indicating an image of the securities GT to be registered. Each of the multiple securities GTs registered in the denomination table TBL12 belongs to either a first type of securities GT (unique securities GT) or a second type of securities GT (common securities GT). The registration unit 214 displays an operation screen G21 on the display device 218 that accepts input of predetermined information, other than the registration target image information, of the securities information for registering the securities GT to be registered in the denomination table TBL12. In addition, if the registration unit 214 determines that the security GT to be registered is a second type of security GT based on the image information to be registered or the information entered on the operation screen G21, it displays a warning on the display device 218 to the effect that the security GT to be registered will not be registered in the security type table TBL12.

[0236] Also in this modified example, the second type of security GT is a security GT that can be used in common among the multiple security processing devices 210A, and the first type of security GT is a security GT that can be used only in a predetermined security processing device 210A among the multiple security processing devices 210A. In other words, the second type of security GT is a security GT that can be used in common among the multiple currency processing devices 21, and the first type of security GT is a security GT that can be used only in a predetermined currency processing device 21 among the multiple currency processing devices 21.

[0237] As described above, in this modification, the same effects as those of the above-described embodiment and modification can be obtained. [Explanation of symbols]

[0238] 1, 1A...currency processing system, 10...server device, 12...computer device, 14...image scanner, 20, 20a, 20b, 20c...POS register system, 21, 21a, 21b, 21c...currency processing device, 111...processing device, 112...image information acquisition unit, 114...registration unit, 115...storage device, 116...communication device, 121...processing device, 125...storage device, 126...communication device, 128...display device, 129...operation device, 210, 210A...securities processing device, 211, 211A ...processing device, 212...image information acquisition unit, 213...recognition unit, 214...registration unit, 215...storage device, 216, 216A...communication device, 217, 217A...image input device, 220...POS register, 221...processing device, 228...display device, 229...operation device, 230...change machine, 240...cash processing device, 241...processing device, 242...coin processing device, 243...banknote processing device, TBL10, TBL12...note type table, PG10, PG20, PG21...control program, GT...securities.

Claims

1. A securities processing device that processes inserted securities, an image input device that generates image information showing an image of the inserted security; a storage unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities; a registration unit that registers securities in the securities database; an acquisition unit capable of acquiring the image information generated by the image input device as registration target image information indicating an image of the securities to be registered; Equipped with each of the plurality of securities registered in the securities database belongs to either a first type of securities or a second type of securities; The registration unit If the securities to be registered are the first type of securities, registering the securities to be registered in the securities database based on the registration target image information; If the securities to be registered are the second type of securities, the securities to be registered are not registered in the securities database, and processing for the securities to be registered is terminated. A securities processing device characterized by:

2. The second type of securities are: The security is usable in common on a plurality of security processing devices; The first type of securities are: The security is usable only at a predetermined security processing device among the plurality of security processing devices.

2. The securities processing device according to claim 1.

3. A securities processing device according to claim 1 or 2, a POS register, and a settlement device, the acquisition unit is capable of acquiring the image information generated by the image input device as settlement target image information indicating an image of a security to be settled, The securities processing device comprises: an identification unit that identifies the inserted securities by comparing the liquidation target image information with each of a plurality of reference image information indicating images of the plurality of securities registered in the securities database; The POS register and the settlement device and executing a payment process for the product according to the recognition result of the recognition unit. A settlement processing device characterized by:

4. A currency processing system having a management computer and a plurality of settlement processing devices communicatively connected to the management computer, each of the plurality of settlement processing devices includes a POS register, a settlement device, and a securities processing device that processes inserted securities; The securities processing device comprises: an image input device that generates image information showing an image of the inserted security; a storage unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities; a registration unit that registers securities in the securities database; an acquisition unit capable of acquiring the image information generated by the image input device as registration target image information indicating an image of the securities to be registered; Equipped with each of the plurality of securities registered in the securities database belongs to either a first type of securities or a second type of securities; The registration unit If the securities to be registered are the first type of securities, registering the securities to be registered in the securities database based on the registration target image information; If the securities to be registered are the second type of securities, the processing for the securities to be registered is terminated without registering the securities to be registered in the securities database; When registration target image information indicating an image of the second type of security is transmitted from the management computer, the image information is registered in the security database. A currency processing system characterized by:

5. In one of the plurality of settlement processing devices, when the registration unit registers the first type of securities in the securities database, it transmits first securities information including the registration target image information of the registered first type of securities to another predetermined clearing processing device via the management computer; In the other settlement processing device, the registration unit registers the securities to be registered in the securities database based on the first securities information transmitted from the one clearing processing device via the management computer; 5. The currency handling system according to claim 4.

6. one of the plurality of clearing processing devices, when the securities to be registered are the second type of securities, transmits second securities information to the management computer, the second securities information including the registration target image information indicating an image of the second type of securities; the management computer is capable of transmitting the second securities information to another clearing processing device; 5. The currency handling system according to claim 4.

7. A settlement processing device having a POS register including a display unit and an input unit, a settlement device, and a securities processing device that processes inserted securities, The securities processing device comprises: an image input device that generates image information showing an image of the inserted security; a storage unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities; a registration unit that registers securities in the securities database; an acquisition unit capable of acquiring the image information generated by the image input device as registration target image information indicating an image of the securities to be registered; Equipped with each of the plurality of securities registered in the securities database belongs to either a first type of securities or a second type of securities; The registration unit displaying on the display unit an input screen for receiving input of predetermined information other than the registration target image information among securities information for registering the registration target securities in the securities database; when it is determined that the securities to be registered are the second type of securities based on the registration target image information or the information input on the input screen, a warning is displayed on the display unit to the effect that the securities to be registered will not be registered in the securities database. A settlement processing device characterized by:

8. A settlement processing device having a POS register including a display unit and an input unit, a settlement device, and a securities processing device that processes inserted securities, The securities processing device comprises: an image input device that generates image information showing an image of the inserted security; a storage unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities; a registration unit that registers securities in the securities database; an acquisition unit that acquires the image information generated by the image input device as registration target image information indicating an image of the securities to be registered; Equipped with each of the plurality of securities registered in the securities database belongs to either a first type of securities or a second type of securities; The registration unit displaying on the display unit an input screen for receiving input of predetermined information other than the registration target image information among securities information for registering the registration target securities in the securities database; If the securities to be registered are the first type of securities, register the securities to be registered in the securities database based on the securities information, and display on the display unit a selection screen for selecting whether or not to register the securities to be registered in the securities database of another clearing processing device. A settlement processing device characterized by:

9. The second type of securities are: The securities are usable in common at a plurality of settlement processing devices; The first type of securities are: The security is usable only at a predetermined settlement processing device among the plurality of settlement processing devices.

9. The settlement processing device according to claim 7 or 8.

10. A currency processing device having a cash processing device, a securities processing device, and a display device, The securities processing device comprises: an image input device that generates image information showing an image of the inserted security; a storage unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities; a registration unit that registers securities in the securities database; an acquisition unit that acquires the image information generated by the image input device as registration target image information indicating an image of the securities to be registered; Equipped with each of the plurality of securities registered in the securities database belongs to either a first type of securities or a second type of securities; The registration unit displaying on the display device an input screen for receiving input of predetermined information other than the registration target image information among securities information for registering the registration target securities in the securities database; When it is determined that the securities to be registered are the second type of securities based on the registration target image information or the information input on the input screen, a warning is displayed on the display device to the effect that the securities to be registered will not be registered in the securities database. A currency processing device characterized by:

11. A currency processing device having a cash processing device, a securities processing device, an image input device, and a display device, the image input device generates image information representing an image of the inserted security; The securities processing device comprises: a storage unit that stores a securities database in which a plurality of securities are registered as a database used when identifying the inserted securities; a registration unit that registers securities in the securities database; an acquisition unit that acquires the image information generated by the image input device as registration target image information indicating an image of the securities to be registered; Equipped with each of the plurality of securities registered in the securities database belongs to either a first type of securities or a second type of securities; The registration unit displaying on the display device an input screen for receiving input of predetermined information other than the registration target image information among securities information for registering the registration target securities in the securities database; If the securities to be registered are the first type of securities, register the securities to be registered in the securities database based on the securities information, and display on the display device a selection screen for selecting whether or not to register the securities to be registered in the securities database of another currency processing device. A currency processing device characterized by:

12. The second type of securities are: The security can be used in common on multiple currency processing devices, The first type of securities are: The security is usable only in a predetermined currency processing device among the plurality of currency processing devices.

12. A currency processing device according to claim 10 or 11.

Images