Cash processing device, system, information processing method, and program

Abstract

To provide a mechanism capable of improving usability related to payment of a levy.SOLUTION: A cash processing device includes a control section for calculating arrears on the basis of levy information read from a first information code applied to a payment statement, so as to control processing for issuing an arrear payment slip to which a second information code storing later payment information for paying the calculated arrears at a later date is applied.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a cash processing device, a system, an information processing method, and a program. [Background technology]

[0002] In recent years, collection systems that execute predetermined transactions (e.g., collection transactions for payments such as taxes and public fees) based on payment slips have become known. As an example of a device used in such collection systems, a customer-operated cash processing device (hereinafter also referred to as a self-service cash processing machine) that is operated by a customer is known.

[0003] If the payment deadline for a tax payment has passed, a late fee may be incurred. Regarding late fees, the following Patent Document 1 discloses a technology for calculating the total amount of taxes and late fees based on information read from a barcode on a payment slip when the payment deadline for taxes and public fees has passed, and collecting cash equivalent to the total amount. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-203388 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the technology disclosed in Patent Document 1 leaves room for improvement in usability, as customers cannot pay the due amount and the late fee separately.

[0006] Therefore, the present invention has been made in consideration of the above problems, and an object of the present invention is to provide a mechanism that can improve the usability regarding the payment of levies. [Means for solving the problem]

[0007] In order to solve the above problem, according to one aspect of the present invention, there is provided a cash processing device comprising a control unit that controls the process of calculating late fees based on payment information read from a first information code attached to a payment slip, and issuing a late fee payment slip attached with a second information code that stores later payment information for later payment of the calculated late fees.

[0008] The control unit may calculate the late fee based on the tax type and payment deadline of the payment identified from the payment information, and the date on which the first information code is read.

[0009] The future payment information may include information indicating the calculated late fee.

[0010] The cash processing device may further include an operation unit that accepts a selection of same-day payment or later payment for each of the one or more late fees that have been incurred, and the control unit may control a process of storing cash equivalent to the late fees for which same-day payment has been selected, and a process of issuing a late fee payment slip for the late fees for which later payment has been selected.

[0011] When later payment is selected for multiple late fees, the operation unit accepts a selection of whether to issue multiple late fee payment slips each having the second information code storing one of the later payment information, or to issue one late fee payment slip each having the second information code storing multiple of the later payment information, and the control unit may control the process of issuing the late fee payment slips in accordance with the selection result accepted by the operation unit.

[0012] When the later payment information is read from the second information code attached to the late fee payment slip, the control unit may control the process of collecting cash equivalent to the late fee based on the read later payment information.

[0013] The first information code may be a barcode, and the second information code may be a two-dimensional code.

[0014] In addition, in order to solve the above problem, according to another aspect of the present invention, a system is provided which includes a management device that stores information regarding late fees, and a cash processing device that controls the process of calculating the late fees based on payment information read from a first information code attached to a payment slip and a calculation rule for the late fees stored in the management device, and issuing a late fee payment slip attached with a second information code that stores later payment information for making a later payment of the calculated late fees.

[0015] The management device may store, for each payment slip, whether or not a late fee to be paid at a later date has been incurred, and whether or not the late fee has already been paid.

[0016] In addition, in order to solve the above problem, according to another aspect of the present invention, there is provided an information processing method executed by a computer that controls a cash processing device, which includes controlling a process of calculating late fees based on payment information read from a first information code attached to a payment slip, and issuing a late fee payment slip attached with a second information code that stores later payment information for making a later payment of the calculated late fees.

[0017] In addition, in order to solve the above problem, according to another aspect of the present invention, a program is provided to cause a computer that controls a cash processing device to function as a control unit that controls the process of calculating late fees based on payment information read from a first information code attached to a payment slip, and issuing a late fee payment slip attached with a second information code that stores later payment information for later payment of the calculated late fees. [Effects of the Invention]

[0018] As described above, the present invention provides a mechanism that can improve usability regarding payment of fees. [Brief explanation of the drawings]

[0019] [Figure 1]1 is a diagram for explaining an overview of a cash processing device according to an embodiment of the present invention. [Figure 2] 1 is a block diagram illustrating an example of a configuration of a system according to an embodiment of the present invention. [Figure 3] 10 is a flowchart illustrating an example of the flow of pre-processing executed by the system according to the present embodiment. [Figure 4] 10 is a flowchart showing an example of the flow of payment collection processing executed by the system according to this embodiment. [Figure 5] 10 is a flowchart showing an example of the flow of payment collection processing executed by the system according to this embodiment. [Figure 6] 10 is a flowchart showing an example of the flow of a process for calculating late fees executed by a cash processing device according to the present embodiment. [Figure 7] 10 is a flowchart showing an example of the flow of a late fee collection process executed by the system according to this embodiment. [Figure 8] FIG. 2 is a block diagram showing an example of a hardware configuration of the information processing device according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0020] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant explanations will be omitted.

[0021] <1. Overview> FIG. 1 is a diagram illustrating an overview of a cash processing device 10 according to one embodiment of the present invention. The cash processing device 10 shown in FIG. 1 is a self-service cash processing machine that customers can operate themselves to pay taxes and other payments. The cash processing device 10 can be installed in stores such as convenience stores. Customers can use payment slip P to pay payments at the counter of the local government that issued the payment slip P, or at the cash processing device 10.

[0022] The payment slip P is provided with a barcode that stores various information related to the payment (hereinafter also referred to as payment information). The barcode is an example of a first information code in this embodiment. Examples of payment information include payment identification information (a payment ID, described below), information indicating the tax item of the late fee (a tax item code, described below), the payment amount, and the payment deadline. This information may be printed on the payment slip P in a format that can be read by the customer.

[0023] The cash processing device 10 accepts payment of a payment using a payment slip P (S10). Based on payment information read from the barcode attached to the payment slip P, the cash processing device 10 can present the amount to be paid to the customer, collect the cash paid by the customer, and upload the payment collection results to the management server 20, which will be described later. The cash processing device 10 then issues a usage statement R on which information indicating the payment collection results is printed (S11).

[0024] However, if the date on which the payment is made (i.e., the date on which the barcode on the payment slip P is read) exceeds the payment deadline read from the payment slip P, the cash processing device 10 can calculate the late fee by using the number of days exceeded as the number of overdue days and present it to the customer. Furthermore, the cash processing device 10 can accept a selection of whether the late fee is paid on the same day or at a later date.

[0025] Same-day payment means paying the late fee on the same day as the payment of the payment. When the customer selects same-day payment, the cash processing device 10 collects cash equivalent to the total amount of the payment and the late fee, and issues a usage statement R on which the collection results of the payment and the late fee are printed.

[0026] Payment at a later date refers to paying the late fee after paying the actual payment. If the customer selects payment at a later date, the cash processing device 10 collects cash equivalent to the payment, issues a usage statement R on which the payment collection result is printed, and further issues a late fee payment slip D for the late fee for which payment at a later date has been selected (S12). The customer can use the late fee payment slip D to pay the late fee at a time separate from the time of payment of the payment (for example, at a later date).

[0027] The late fee payment slip D is provided with a two-dimensional code that stores various information regarding the later payment of late fees (hereinafter also referred to as later payment information). The two-dimensional code is an example of a second information code. Examples of later payment information include identification information for the late fee (late fee ID, described below) and the amount. Furthermore, this information may be printed on the late fee payment slip D in a format that can be read by the customer, along with general information such as the date and time of issuance of the late fee payment slip D.

[0028] The cash processing device 10 can accept payment of late fees using the late fee payment slip D (S20). Based on the later payment information read from the two-dimensional code attached to the late fee payment slip D, the cash processing device 10 can present the amount to be paid to the customer, collect the cash paid by the customer, and upload the collection results to the management server 20 described below. Then, the cash processing device 10 issues a usage statement R on which information indicating the collection results of the late fee is printed (S21).

[0029] The outline of the cash processing device 10 according to this embodiment has been described above.

[0030] According to the cash processing device 10 of this embodiment, when a late fee is incurred, the customer can select whether to pay the late fee on the same day or at a later date. If the customer selects later payment, the customer can then use the issued late fee payment slip D to pay the late fee at a later date. This configuration allows the customer to pay the invoice and the late fee separately, thereby improving usability compared to the prior art described in Patent Document 1 and the like, which requires the invoice and the late fee to be paid on the same day.

[0031] <2.Configuration example> FIG. 2 is a block diagram showing an example of the configuration of the system 1 according to this embodiment. As shown in FIG. 2, the system 1 includes a cash processing device 10, a management server 20, and a management terminal 30. The cash processing device 10 and the management server 20, and the management server 20 and the management terminal 30 are connected to each other so that they can communicate with each other. The communication path may be established by a local network, a business operator network, an external network such as the Internet, or the like. Furthermore, although FIG. 2 shows one cash processing device 10, the system 1 may include multiple cash processing devices 10.

[0032] (1) Cash processing device 10 As described above with reference to Fig. 1, the cash processing device 10 is a self-service cash processing machine that can be operated by a customer to pay taxes and other payments. As shown in Fig. 2, the cash processing device 10 includes an operation and display unit 11, a reading unit 12, an issuing unit 13, a cash processing unit 14, and a control unit 15.

[0033] The operation display unit 11 has the function of a display unit that displays information to the customer, and the function of an operation unit that accepts information input from the customer. The function of the display unit is realized, for example, by a display. The function of the operation unit is realized, for example, by a touch panel. For example, the operation display unit 11 displays a screen that guides the customer through operations related to payment of the payment. The customer then inputs various information for paying the payment on this screen. For example, the operation display unit 11 accepts input of whether or not to read the payment slip P continuously, and whether or not to pay the late fee on the same day or at a later date.

[0034] The reading unit 12 has the function of reading various information contained in the payment slip P. The reading unit 12 is configured, for example, with an optical reader, and can read information stored in information codes such as barcodes or two-dimensional codes from these information codes. In detail, the reading unit 12 reads payment information from the barcode attached to the payment slip P, and later reads payment information from the two-dimensional code attached to the late fee payment slip D.

[0035] The issuing unit 13 has a function of issuing media that store various information. The issuing unit 13 may be, for example, a receipt printer that prints and issues information on paper media. For example, the issuing unit 13 issues a usage statement R after payment of the payment fee or late fees is completed, or issues a late fees payment slip D with a two-dimensional code that stores payment information when late payment of the late fees is selected.

[0036] The cash processing unit 14 has a function of processing cash. The cash processing unit 14 includes various components related to cash processing, such as an inlet for receiving cash, an outlet for discharging cash, a transport path for transporting cash, a storage facility for storing cash, and a mechanism for counting cash. The cash processing unit 14 stores the cash inserted by the customer that is equivalent to the payment or late fees, and dispenses change, if any.

[0037] The control unit 15 functions as an arithmetic processing device and a control device, and controls the overall operation of the cash processing device 10 in accordance with various programs. The control unit 15 is realized by electronic circuits such as a CPU (Central Processing Unit) or a microprocessor. The control unit 15 may include a ROM (Read Only Memory) that stores the programs to be used and arithmetic parameters, etc., and a RAM (Random Access Memory) that temporarily stores parameters that change as appropriate.

[0038] The output of information by the operation display unit 11 and the acquisition of input information, the reading of information by the reading unit 12, the printing and issuance by the issuing unit 13, and the cash processing by the cash processing unit 14 are examples of objects controlled by the control unit 15. The reading of information stored in the management server 20 and information processing based on the read information, as well as the registration of information in the management server 20 are also examples of objects controlled by the control unit 15.

[0039] The processing controlled by the control unit 15 will be described in detail below.

[0040] (Processing based on payment slip P) The control unit 15 controls the process of collecting the payment or the payment and late fees based on the payment slip P. For example, the control unit 15 controls the operation display unit 11 to display a screen that guides the customer in their operations regarding payment of the payment and to receive input from the customer, and controls the reading unit 12 to read the barcode attached to the payment slip P. The control unit 15 also controls the cash processing unit 14 to collect the cash, controls the issuing unit 13 to issue a usage statement slip R or a late fee payment slip D, and requests that information in a DB (Data Base) managed by the management server 20 be referenced or updated.

[0041] In particular, the control unit 15 controls the process of calculating the late fee based on payment information read from the barcode attached to the payment slip P, and issuing the late fee payment slip D with a two-dimensional code that stores later payment information for accepting later payment of the calculated late fee. With this configuration, the customer can pay the late fee at a later date, thereby improving usability.

[0042] The control unit 15 calculates the late fee based on the tax item and payment deadline of the payment specified based on the information read from the barcode attached to the payment slip P, and the date of the day the payment was made using the payment slip P (i.e., the day the barcode on the payment slip P was read). In detail, the control unit 15 first specifies the tax item of the payment based on the tax item code read from the barcode attached to the payment slip P and a tax item table 21 described later. Furthermore, if the day the payment was made exceeds the payment deadline read from the barcode attached to the payment slip P, the control unit 15 specifies the number of days exceeded as the number of overdue days. The control unit 15 then specifies the late fee corresponding to the number of overdue days by referring to a late fee table 22 described later that corresponds to the specified tax item. This configuration enables the cash processing device 10 to appropriately calculate late fees.

[0043] The number of days overdue before late fees are charged may differ for each tax item. For example, some taxes may be charged from the first day overdue, while other taxes may be charged from the tenth day overdue.

[0044] The later payment information stored in the two-dimensional code attached to the late fee payment slip D includes information indicating the calculated late fee. That is, the control unit 15 generates a two-dimensional code including information indicating the calculated late fee, and controls the process of issuing a late fee payment slip D with the generated two-dimensional code attached. With this configuration, it is possible to store information indicating the calculated late fee in the late fee payment slip D.

[0045] The control unit 15 provides the customer with the opportunity to select whether to pay the late fees on the same day or at a later date, and controls processing in accordance with the selection result. Specifically, the operation and display unit 11 first accepts the selection of whether to pay on the same day or at a later date for each of one or more late fees that have been incurred. For example, the operation and display unit 11 displays a screen indicating that late fees have been incurred, and displays, on the screen, buttons for selecting same-day payment and buttons for selecting later payment for each late fee, and accepts the customer's selection. The control unit 15 then controls the processing of storing cash equivalent to the late fees for which same-day payment has been selected, and controls the processing of issuing a late fee payment slip D for the late fees for which later payment has been selected. This configuration allows the customer to select whether to pay the late fees on the same day or at a later date, thereby improving customer usability.

[0046] When later payment is selected for multiple late fees, the control unit 15 provides the customer with the opportunity to select whether to issue late fee payment slips D in installments or all at once, and controls processing in accordance with the selection result. Specifically, when later payment is selected for multiple late fees, the operation and display unit 11 first accepts the customer's selection of whether to issue multiple late fee payment slips D with a two-dimensional code storing one later payment information item, or to issue a single late fee payment slip D with a two-dimensional code storing multiple later payment information items. The former corresponds to partial issuance, and the latter corresponds to bulk issuance. For example, the operation and display unit 11 displays a screen indicating that late fee payment slips D will be issued, and also displays buttons on the screen for selecting partial issuance of late fee payment slips D and for selecting bulk issuance, and accepts the customer's selection. The control unit 15 then controls processing to issue late fee payment slips D in accordance with the selection result accepted by the operation and display unit 11. That is, the issuing unit 13 issues multiple late fee payment slips D when separate issuance is selected, and issues one late fee payment slip D when collective issuance is selected. A customer can use one late fee payment slip D issued in separate installments to pay one late fee. On the other hand, a customer can use one late fee payment slip D issued in bulk to pay multiple late fees. With this configuration, a customer can select whether to issue late fee payment slips D in separate installments or in bulk, thereby improving usability for customers.

[0047] When the late payment fee is to be paid at a later date, the control unit 15 requests the management server 20 to register information about the late payment fee in a later payment late payment fee collection history DB 23 and a collection history DB 24, which will be described later. With this configuration, the cash processing device 10 can accept the later payment of the late payment fee based on the registered information. In particular, since multiple cash processing devices 10 can refer to information about the late payment fee via the management server 20, it is also possible for a cash processing device 10 other than the cash processing device 10 to which the payment was made to accept the later payment of the late payment fee.

[0048] (Processing based on late payment fee payment slip D) The control unit 15 controls the process of collecting late fees based on the late fee payment slip D. For example, the control unit 15 controls the operation display unit 11 to display a screen that guides the customer through operations related to the payment of late fees and to receive input from the customer, and controls the reading unit 12 to read the two-dimensional code attached to the late fee payment slip D. The control unit 15 also controls the cash processing unit 14 to collect the cash, controls the issuing unit 13 to issue a usage statement slip R, and requests that information in the DB managed by the management server 20 be referenced or updated.

[0049] In particular, when later payment information is read from the two-dimensional code attached to the late fee payment slip D, the control unit 15 controls the process of collecting cash equivalent to the late fee based on the read later payment information. More specifically, the control unit 15 controls the cash processing unit 14 to collect cash equivalent to the amount of late fee included in the later payment information, and controls the issuing unit 13 to issue a usage statement R on which information indicating the result of collection of the late fee is printed. With this configuration, the customer can pay the late fee using the late fee payment slip D at any time, thereby improving usability.

[0050] When the late fee is paid, the control unit 15 requests the management server 20 to update the information on the late fee registered in the later-paid late fee collection history DB 23 and collection history DB 24. With this configuration, it becomes possible to link the fact that the late fee has been paid to the local government system, as will be described later.

[0051] (2) Management Server 20 The management server 20 is a management device that stores various information related to payments and late fees. As shown in Figure 2, the management server 20 stores a tax item table 21, a late fee table 22, a later payment late fee collection history DB (Data Base) 23, and a collection history DB 24.

[0052] (Tax Item Table 21) The tax item table 21 is a table that stores combinations of tax item codes and tax items. An example of information stored in the tax item table 21 is shown in Table 1 below.

[0053] [Table 1]

[0054] The tax item code shown in Table 1 is identification information that uniquely identifies a tax item. The tax item code is stored in the barcode attached to the payment slip P.

[0055] The tax item name is the name of the tax item.

[0056] The cash processing device 10 can identify the tax item of the payment related to the payment slip P by referring to the tax item table 21. In detail, the cash processing device 10 can identify, by referring to the tax item table 21, the tax item corresponding to the tax item code read from the barcode attached to the payment slip P as the tax item of the payment.

[0057] (Late Fee Table 22) The late fee table 22 is a table that stores the calculation rules for late fees. The late fee table 22 can be created for each tax item. An example of information stored in the late fee table 22 regarding fixed asset tax is shown in Table 2 below.

[0058] [Table 2]

[0059] As shown in Table 2, the late fee table 22 may define the relationship between the number of days overdue and the late fee.

[0060] The cash processing device 10 can calculate the late fee by referring to the late fee table 22. More specifically, if the date on which the payment is made exceeds the payment deadline for the payment read from the barcode attached to the payment slip P, the cash processing device 10 identifies the number of days exceeded as the number of overdue days. Then, the cash processing device 10 identifies the late fee corresponding to the number of overdue days by referring to the late fee table 22 corresponding to the tax item identified from the barcode attached to the payment slip P.

[0061] (Later payment late fee collection history DB23) The later-payment late fee collection history DB 23 is a DB that manages the collection history of late fees for which later payment has been selected. An example of information stored in the later-payment late fee collection history DB 23 is shown in Table 3 below.

[0062] [Table 3]

[0063] The late fee ID shown in Table 3 is identification information for the late fee. The late fee ID is assigned when the late fee payment slip D is issued and is stored in the two-dimensional code attached to the late fee payment slip D.

[0064] The late fee ID may include a branch number at the end consisting of a hyphenated number, such as "789-1," "789-2," or "789-3." When multiple late fees are incurred and the option to issue late fee payment slips D in bulk is selected, a late fee ID with a different branch number added to this common number is assigned to each of the multiple late fees selected for bulk issuance. The two-dimensional code of a single late fee payment slip D issued in bulk stores all of the late fee IDs of the multiple late fees selected for bulk issuance (for example, all of "789-1," "789-2," and "789-3"). This configuration makes it possible to use the batch-issued late fee payment slips D to pay multiple late fees at different times, and also makes it possible to prevent double payment of late fees.

[0065] The payment flag indicates whether the late fee has been paid or not. A payment flag of "1" indicates that the fee has been paid, and a payment flag of "0" indicates that the fee has not been paid.

[0066] The tax type, number of days overdue, and late fee indicate the tax type, number of days overdue, and late fee of the late fee identified by the late fee ID.

[0067] When a late fee is incurred and the option to pay the late fee at a later date is selected, the cash processing device 10 requests the management server 20 to add a record relating to the late fee to the late payment late fee collection history DB 23. Thereafter, when the late fee is paid using the late fee payment slip D, the cash processing device 10 requests the management server 20 to update the payment completion flag.

[0068] (Storage history DB24) The payment history DB 24 is a DB for managing the payment slips P on which the payment has been made. An example of information stored in the payment history DB 24 is shown in Table 4 below.

[0069] [Table 4]

[0070] The payment ID is identification information for the payment. The payment ID is stored in the barcode attached to the payment slip P.

[0071] The full payment flag indicates whether the payment has been paid if no late fees have been incurred, or whether the payment and late fees have been paid if late fees have been incurred. "0" indicates that a portion is unpaid, i.e., the payment has been paid, but the late fees have not. "1" indicates that the entire amount has been paid, i.e., the payment and late fees have been paid.

[0072] The late fee ID is identification information for the late fee for which payment at a later date has been selected.

[0073] The late fee ID is assigned when a late fee is incurred and the option to pay the fee at a later date is selected. Therefore, the presence or absence of a late fee ID indicates whether or not a late fee to be paid at a later date has been incurred. In other words, if the late fee ID is blank ("-" in the table), this indicates that no late fee to be paid at a later date has been incurred. If the late fee ID is not blank, this indicates that a late fee to be paid at a later date has been incurred. Furthermore, the combination of the late fee ID and the full payment flag indicates whether or not the late fee to be paid at a later date has been paid.

[0074] When a payment is made, the cash processing device 10 requests the management server 20 to add a record relating to the payment to the collection history DB 24. At that time, the cash processing device 10 transmits to the management server 20 whether the full amount has been paid, whether a late fee to be paid at a later date has occurred, and if a late fee to be paid at a later date has occurred, a numbered late fee ID. The management server 20 then adds a record storing this information to the collection history DB 24. For late fees for which payment at a later date has been selected, the cash processing device 10 requests the management server 20 to update the full payment flag when the late fee is paid using a late fee payment slip D.

[0075] The local government that issued the payment slip P operates a local government system that manages a database for managing the payment receipt history. For example, the local government system adds a record of an uncollected payment when a payment is made, and deletes the corresponding record when the payment is paid at a local government counter or cash processing device 10.

[0076] Therefore, the management server 20 links the collection history of payments made using the cash processing device 10 to the local government system of the local government that issued the payment slip P. In detail, the management server 20 may create a collection history file for payments in the collection history DB 24 for which the full payment flag has become "1" in order to erase the records relating to the payments from the DB operated by the local government system, and send this to the local government system. The local government system updates the collection history of payments (i.e., erases uncollected payments) based on this collection history file.

[0077] (3) Management terminal 30 The management terminal 30 is a dedicated terminal for managing the management server 20. The management terminal 30 is operated, for example, by an administrator who is responsible for managing the cash processing device 10. As shown in FIG. 2 , the management terminal 30 includes an operation display unit 31 and a control unit 32.

[0078] The operation display unit 31 has a function as a display unit that displays information to the administrator, and a function as an operation unit that accepts information input from the administrator. The function as a display unit is realized, for example, by a display. The function as an operation unit is realized, for example, by a keyboard and a mouse. For example, the operation display unit 31 displays a screen that guides the customer in setting the calculation rules for late fees. The customer then sets the calculation rules for late fees on this screen.

[0079] The control unit 32 functions as an arithmetic processing unit and control device, and controls the overall operation of the management terminal 30 in accordance with various programs. The output of information by the operation display unit 31 and the acquisition of input information are examples of objects controlled by the control unit 32. The control unit 32 is realized by electronic circuits such as a CPU (Central Processing Unit) or a microprocessor. The control unit 15 may also include a ROM (Read Only Memory) that stores programs to be used and arithmetic parameters, and a RAM (Random Access Memory) that temporarily stores parameters that change as appropriate.

[0080] In particular, the control unit 32 may control the process for registering or updating information in a DB managed by the management server 20. For example, the control unit 32 may display a screen for registering information in the late fee table 22, control the operation display unit 31 to accept information input by the administrator, and transmit the input information to the management server 20.

[0081] <3. Operation processing> (Pretreatment) FIG. 3 is a flowchart showing an example of the flow of pre-processing executed by the system 1 according to this embodiment.

[0082] 3, first, the management terminal 30 displays an arrears fee table registration screen (step S102). The arrears fee table registration screen is a screen for registering the arrears fee table 22.

[0083] Next, the management terminal 30 selects the tax item for which the late fee table 22 is to be registered (step S104). For example, the management terminal 30 selects the tax item selected by the administrator as the tax item for which the late fee table 22 is to be registered.

[0084] Next, the management terminal 30 registers the correspondence between the number of overdue days and the overdue fees in the overdue fees table 22 (step S106). For example, the management terminal 30 requests the management server 20 to register the correspondence between the number of overdue days and the overdue fees input by the administrator. Then, based on this request, the management server 20 registers the correspondence between the number of overdue days and the overdue fees input by the administrator in the overdue fees table 22.

[0085] Next, the management terminal 30 determines whether or not the registration of the correspondence between the number of overdue days and the late fees has been completed (step S108). For example, the management terminal 30 accepts an operation to select whether or not the registration of the correspondence between the number of overdue days and the late fees has been completed.

[0086] If it is determined that the registration of the correspondence between the number of overdue days and the overdue fees has not been completed (step S108: NO), the process returns to step S106 again.

[0087] If it is determined that the registration of the correspondence between the number of overdue days and the late fees has been completed (step S108: YES), the management terminal 30 determines whether or not the registration of the late fee table for each tax item has been completed (step S110). For example, the management terminal 30 accepts an operation to select whether or not the registration of the late fee table for all tax items has been completed.

[0088] If it is determined that the registration of the late fee table for each tax item has not been completed (step S110: NO), the process returns to step S104 again.

[0089] If it is determined that the registration of the late fee table for each tax item is complete (step S110: YES), the process ends.

[0090] (Payment processing) 4 and 5 are flowcharts showing an example of the flow of the payment receipt process executed by the system 1 according to this embodiment.

[0091] As shown in Fig. 4, first, the cash processing device 10 displays an information code reading screen (step S202). For example, when a customer touches the initial screen, the cash processing device 10 displays the information code reading screen. The information code reading screen includes information that guides the cash processing device 10 to read, for example, a barcode attached to the payment slip P or a two-dimensional code attached to the late fee payment slip D. Here, it is assumed that the barcode attached to the payment slip P is read by the cash processing device 10.

[0092] Next, the cash processing device 10 reads payment information from the barcode attached to the payment slip P (step S204).

[0093] Next, the cash processing device 10 determines whether or not a late fee has been incurred (step S206). For example, the cash processing device 10 refers to the tax item table 21 and identifies the tax item corresponding to the tax item code read from the barcode attached to the payment slip P as the tax item of the payment. Then, the cash processing device 10 determines whether or not a late fee has been incurred based on the identified tax item and whether or not the payment date (i.e., the date the barcode on the payment slip P was read) exceeds the payment deadline read from the payment slip P. For this determination, the late fee table 22 for the identified tax item may be referenced.

[0094] If it is determined that a late fee has been incurred (step S206: YES), the cash processing device 10 calculates the late fee (step S208). For example, the cash processing device 10 refers to the late fee table 22 for the identified tax item to identify the late fee corresponding to the number of days of overdue.

[0095] Next, the cash processing device 10 displays details of the payment amount and the late fee (step S210). For example, the cash processing device 10 displays information indicating the tax item, payment deadline, the number of days of late payment, and the amount of each of the payment amount and the late fee for the read payment slip P.

[0096] On the other hand, if it is determined that no late fees have been incurred (step S206: NO), the cash processing device 10 displays the details of the payment for the read payment slip P (step S212). For example, the cash processing device 10 displays information indicating the tax item, the payment deadline, and the amount of the payment.

[0097] Next, the cash processing device 10 determines whether or not reading of the payment slip P is complete (step S214). For example, the cash processing device 10 accepts an operation to select whether or not there is still an unread payment slip P.

[0098] If it is determined that reading of the payment slip P is not complete (step S214: NO), the process returns to step S204 again.

[0099] When it is determined that the reading of the payment slip P is completed (step S214: YES), the cash processing device 10 displays the total amount of the payment and the late fee (step S216). When multiple payment slips P are read, the cash processing device 10 displays the total amount of the payment and the late fee for these multiple payment slips P.

[0100] Next, as shown in FIG. 5, the cash processing device 10 determines whether or not there is a late fee (step S218).

[0101] If it is determined that there are no overdue fees (step S218: NO), the cash processing device 10 collects cash equivalent to the total amount of all payments (step S236) and registers the collection result in the collection history DB 24 (step S238). At that time, the cash processing device 10 registers a record including the payment ID read from the barcode on the payment slip P, a full payment flag of "1", and a overdue fees ID of "-" in the collection history DB 24. Thereafter, the cash processing device 10 issues a usage statement R including information indicating the collection result of the payments (step S240), and ends the processing.

[0102] On the other hand, if it is determined that there are late fees (step S218: YES), the cash processing device 10 determines the payment schedule for the late fees (step S220). Specifically, the cash processing device 10 accepts an operation to select either paying all late fees on the same day, paying some late fees on the same day and paying the remaining late fees at a later date, or paying all late fees at a later date. For example, the cash processing device 10 may accept an operation to select whether to pay on the same day or at a later date for each late fee that has occurred.

[0103] If same-day payment of all late fees is selected, the cash processing device 10 calculates and displays the total amount of all payments and all late fees, and then collects cash equivalent to the calculated total amount (step S222). Thereafter, the cash processing device 10 registers the collection result in the collection history DB 24 (step S238). For example, the cash processing device 10 registers in the collection history DB 24 a record including the payment ID read from the barcode of the payment slip P, a full payment completion flag "1", and a late fee ID "-". Then, the cash processing device 10 issues a usage statement R including information indicating the collection result of the payments and late fees (step S240), and ends the processing.

[0104] If same-day payment of some of the late fees and later payment of the remaining late fees are selected, the cash processing device 10 calculates and displays the total amount of all payments and the partial late fees for which same-day payment was selected, and then stores cash equivalent to the calculated total amount (step S224).On the other hand, if later payment of all late fees is selected, the cash processing device 10 calculates and displays the total amount of all payments, and then stores cash equivalent to the calculated total amount (step S226).

[0105] Thereafter, the cash processing device 10 selects a method for issuing the late fee payment slip D (step S228). For example, the cash processing device 10 calculates and displays the total amount of all late fees for which later payment has been selected, and then accepts an operation to select whether to issue late fee payment slips D for all late fees for which later payment has been selected in one lump sum, or to issue late fee payment slips D for each late fee in installments.

[0106] Next, the cash processing device 10 registers information on the late fees for which later payment has been selected for each late fee payment slip D in the later-payment late fee collection history DB23 (step S230). Here, if batch issuance has been selected in step S228, the cash processing device 10 assigns late fee IDs, each of which has a different sub-number added to a common number, to the multiple payment slips P for which late fees have occurred. On the other hand, if installment issuance has been selected in step S228, the cash processing device 10 assigns one late fee ID to each payment slip P for which late fees have occurred. Then, the cash processing device 10 registers the assigned late fee ID, the paid flag "0", the tax item for which the late fee has occurred, the number of days overdue, and the late fee in the later-payment late fee collection history DB23.

[0107] Next, the cash processing device 10 issues a late fee payment slip D (step S232).

[0108] Next, the cash processing device 10 determines whether the issuance of the late fee payment slips D has been completed (step S234). As an example, if batch issuance of late fee payment slips D has been selected in step S228, the cash processing device 10 determines that the issuance of late fee payment slips D has been completed. As another example, if installment issuance of late fee payment slips D has been selected in step S228, the cash processing device 10 determines that the issuance has been completed if late fee payment slips D for all accrued late fees have been issued, and determines that the issuance has not been completed if there are still unissued late fee payment slips D.

[0109] If it is determined that the issuance of the late fee payment slip D has not been completed (step S234: NO), the process returns to step S230 again.

[0110] On the other hand, if it is determined that the issuance of the late fee payment slip D has been completed (step S234: YES), the cash processing device 10 registers the collection result in the collection history DB 24 (step S238). For example, with respect to a payment for which late fees have already been paid, the cash processing device 10 registers in the collection history DB 24 a record including the payment ID read from the barcode on the payment slip P, a full payment flag of "1", and a late fee ID of "-". On the other hand, with respect to a payment for which late fees have been selected to be paid at a later date, the cash processing device 10 registers in the collection history DB 24 a record including the payment ID read from the barcode on the payment slip P, a full payment flag of "0", and the late fee ID numbered in step S230. Then, the cash processing device 10 issues a usage statement R including information indicating the collection result (step S240), and ends the processing.

[0111] (Calculation of late fees) 6 is a flowchart showing an example of the flow of the process of calculating late fees executed by the cash processing device 10 according to this embodiment. The process according to this flow is executed in step S208 shown in FIG.

[0112] First, the cash processing device 10 identifies the tax item and the payment deadline based on the payment information read from the barcode attached to the payment slip P (step S302). For example, the cash processing device 10 identifies fixed asset tax as the tax item and May 1, 2023 as the payment deadline.

[0113] Next, the cash processing device 10 acquires the date of the day of payment (step S304). For example, it is assumed that the cash processing device 10 acquires May 4, 2023 as the date of the day of payment.

[0114] Next, the cash processing device 10 calculates the number of overdue days from the payment due date and the current date (step S306). For example, the cash processing device 10 calculates 3 days, which is the difference between the payment due date of May 1, 2023 and the current date of May 4, 2023, as the number of overdue days.

[0115] Next, the cash processing device 10 refers to the late fee table 22 for the tax item identified in step S302, and identifies the late fee corresponding to the number of days of overdue calculated in step S306 (step S308). For example, the cash processing device 10 identifies a late fee of 300 yen corresponding to the number of days of overdue, 3 days, from the late fee table 22 for fixed asset tax shown in Table 2.

[0116] The process then ends.

[0117] In the flow shown in FIG. 4, each time the payment slip P is read, the late fees are calculated in step S208 as explained above, and then the late fees are totaled and displayed in step S216.

[0118] (Collection of late fees) FIG. 7 is a flowchart showing an example of the flow of the late fee collection process executed by the system 1 according to this embodiment.

[0119] 7, first, the cash processing device 10 displays an information code reading screen (step S402). Here, it is assumed that the two-dimensional code attached to the late fee payment slip D is read by the cash processing device 10.

[0120] Next, the cash processing device 10 reads payment information from the two-dimensional code attached to the late fee payment slip D (step S404).

[0121] Next, the cash processing device 10 refers to the later-paid late fee collection history DB 23 to determine whether the late fee related to the late fee payment slip D is unpaid or not (step S406). For example, the cash processing device 10 determines that the late fee is unpaid when the payment completion flag corresponding to the late fee ID read from the two-dimensional code attached to the late fee payment slip D is "0", and determines that the late fee has been paid when the payment completion flag is "1".

[0122] If it is determined that the payment is unpaid (step S406: YES), the cash processing device 10 displays details of the late fees (step S408). For example, the cash processing device 10 displays information indicating the tax type, the number of days of lateness, and the amount of late fees for the read late fee payment slip D.

[0123] On the other hand, if it is determined that the payment has been made (step S406: NO), the cash processing device 10 displays information indicating that the payment has been made (step S410).

[0124] Thereafter, the cash processing device 10 determines whether or not the reading of the late fee payment slips D has been completed (step S412). For example, the cash processing device 10 accepts an operation to select whether or not there are any unread late fee payment slips D.

[0125] If it is determined that the reading of the late fee payment slip D has not been completed (step S412: NO), the process returns to step S404 again.

[0126] When it is determined that the reading of the late fee payment slip D is completed (step S412: YES), the cash processing device 10 displays a list of details of the late fee (step S414). When multiple late fee payment slips D are read, the cash processing device 10 displays a list of details of the late fee for these multiple late fee payment slips D.

[0127] Next, the cash processing device 10 accepts selection of the overdue fees to be paid (step S416). For example, the cash processing device 10 may accept an operation to select whether or not to pay each overdue fee listed in step S414.

[0128] Next, the cash processing device 10 stores cash equivalent to the total amount of late fees to be paid (step S418). For example, the cash processing device 10 calculates and displays the total amount of late fees to be paid, and stores cash equivalent to the calculated total amount.

[0129] Next, the cash processing device 10 registers the collection results in the later-paid late fees collection history DB23 and the collection history DB24 (step S420). For example, the cash processing device 10 updates the paid flag from "0" to "1" in the record in the later-paid late fees collection history DB23 that corresponds to the late fees ID read from the late fees payment slip D. Furthermore, the cash processing device 10 updates the full amount paid flag from "0" to "1" in the record in the collection history DB24 that corresponds to the late fees ID read from the late fees payment slip D.

[0130] Then, the cash processing device 10 issues a usage statement R including information indicating the result of collection of the late fee (step S422), and ends the process.

[0131] <4. Effects> The cash processing device 10 according to this embodiment has been described in detail above. The cash processing device 10 according to this embodiment allows a customer to pay the due amount and the late fee separately, which makes it possible to improve usability compared to the prior art described in Patent Document 1 and the like.

[0132] Specifically, there are cases where a customer plans to pay only the payment amount but does not have enough cash to cover the payment amount, making it impossible to pay the total amount of the payment amount and the late fee. Therefore, in conventional technologies that require the payment of the payment amount and the late fee on the same day, the customer is required to return with cash for the total amount of the payment amount and the late fee. In this regard, with the cash processing device 10 according to this embodiment, the customer can first pay only the payment amount by selecting to pay the late fee at a later date. For local governments, this allows them to collect only the payment amount first, which can improve the collection rate of payment amounts.

[0133] The amount of the late fee can be calculated based on the date on which the payment is made. Therefore, in the prior art, if a customer is unable to pay the total amount of the payment and the late fee and has to retry, the late fee may increase further depending on the number of days it takes to retry. In this regard, the cash processing device 10 according to the present embodiment can determine the amount of the late fee when the payment is made, thereby preventing unnecessary increases in the late fee for the customer.

[0134] Furthermore, in the prior art, even if the late fee increased depending on the number of days it took to retry, it was difficult for the customer to recognize the increase in the late fee until they actually retry. As a result, the customer may be unable to repay the total amount of the invoice and the late fee because the late fee has increased even after retrying at a later date. In this regard, in the cash processing device 10 according to this embodiment, the amount of the late fee is determined when the invoice is paid, and a late fee payment slip D is issued. Therefore, by referring to the late fee payment slip D, the customer can clearly recognize the amount of the late fee to be paid, and can prevent a shortage of cash when making a payment at a later date.

[0135] Furthermore, according to the cash processing device 10 of this embodiment, when multiple payment slips P are used and multiple late fees are incurred, it is possible to accept a selection of whether to pay each of the multiple late fees on the same day or at a later date. Therefore, it is possible to realize as many different requests as possible from customers, such as wanting to pay only the payment amount on the same day, wanting to pay only a portion of the late fees because they can pay only a portion of the late fees with cash on hand, or wanting to pay everything, including the late fees, on the same day.

[0136] <4. Hardware configuration example> Next, the hardware configuration of an information processing device according to this embodiment will be described with reference to Fig. 8. Fig. 8 is a block diagram showing an example of the hardware configuration of an information processing device according to this embodiment. Note that the information processing device 900 shown in Fig. 8 may realize, for example, the management server 20 or the management terminal 30 shown in Fig. 2. Information processing by the management server 20 or the management terminal 30 according to this embodiment is realized by cooperation between software and hardware described below.

[0137] As shown in FIG. 8, the information processing device 900 includes a CPU (Central Processing Unit) 901, a ROM (Read Only Memory) 902, a RAM (Random Access Memory) 903, a host bus 904, a bridge 905, an external bus 906, an interface 907, an input device 908, an output device 909, a storage device 910, and a communication device 911.

[0138] The CPU 901 functions as an arithmetic processing unit and control unit, and controls the overall operation of the information processing device 900 in accordance with various programs. The CPU 901 may also be a microprocessor. The ROM 902 stores programs used by the CPU 901, calculation parameters, etc. The RAM 903 temporarily stores programs used in the execution of the CPU 901, and parameters that change as appropriate during the execution. These are interconnected by a host bus 904 that is composed of a CPU bus, etc. The CPU 901 may, for example, control the operation of the management server 20 shown in FIG. 2, or form the control unit 32 shown in FIG. 2.

[0139] The host bus 904 is connected to an external bus 906, such as a PCI (Peripheral Component Interconnect / Interface) bus, via a bridge 905. It is not necessary to configure the host bus 904, bridge 905, and external bus 906 separately, and these functions may be implemented on a single bus.

[0140] The input device 908 is composed of input means for the user to input information, such as a mouse, keyboard, touch panel, buttons, microphone, switches, and levers, and an input control circuit that generates an input signal based on the user's input and outputs it to the CPU 901. A user who operates the information processing device 900 can input various data and instruct the information processing device 900 to perform processing operations by operating this input device 908. The input device 908 can form, for example, the operation and display unit 31 shown in FIG. 2.

[0141] The output device 909 includes, for example, a display device such as a CRT (Cathode Ray Tube) display device, a liquid crystal display (LCD) device, an OLED (Organic Light Emitting Diode) device, a lamp, etc., and an audio output device such as a speaker, etc. The output device 909 can form, for example, the operation display unit 31 shown in FIG.

[0142] The storage device 910 is a device for storing data. The storage device 910 may include a storage medium, a recording device for recording data on the storage medium, a reading device for reading data from the storage medium, and a deletion device for deleting data recorded on the storage medium. The storage device 910 is configured, for example, with an HDD (Hard Disk Drive). This storage device 910 drives a hard disk and stores programs executed by the CPU 901 and various data. The storage device 910 may store, for example, the tax item table 21, the late fee table 22, the later-paid late fee collection history DB 23, and the collection history DB 24 shown in FIG. 2.

[0143] The communication device 911 is, for example, a communication interface configured with a communication device for connecting to a network, etc. The communication device 911 may be compatible with either wireless communication or wired communication.

[0144] The above describes an example of a hardware configuration capable of realizing the functions of the information processing device 900 according to this embodiment. Each of the above components may be realized using general-purpose components, or may be realized by hardware specialized for the function of each component. Therefore, the hardware configuration used can be changed as appropriate depending on the technical level at the time of implementing this embodiment.

[0145] <5. Supplementary Information> Although the preferred embodiments of the present invention have been described in detail above with reference to the accompanying drawings, the present invention is not limited to these examples. It is clear that a person skilled in the art to which the present invention pertains can conceive of various modifications and alterations within the scope of the technical ideas set forth in the claims, and it is understood that these also naturally fall within the technical scope of the present invention.

[0146] In the above embodiment, an example was described in which the management terminal 30 was a dedicated terminal, but the present invention is not limited to such an example. The functions of the management terminal 30 may be realized as a program that can be stored in an external medium. Then, by installing the program in a personal computer (PC) other than the management terminal 30 using the external medium, the other PC may operate as the management terminal 30.

[0147] In the above embodiment, an example has been described in which the payment slip P and the late fee payment slip D are issued on paper media, but the present invention is not limited to such an example. The payment slip P and the late fee payment slip D may be issued on media other than paper, such as a web page or an image.

[0148] In the above embodiment, an example has been described in which the reading unit 12 optically reads the payment information stored in the payment slip P or the later payment information stored in the late fee payment slip D, but the present invention is not limited to such an example. The reading unit 12 may read this information magnetically or via a wireless communication path.

[0149] The series of processes performed by each device described herein may be implemented using software, hardware, or a combination of software and hardware. The software programs may be stored in advance, for example, on a recording medium (more specifically, a non-transitory computer-readable storage medium) internal or external to each device. Each program is loaded into a random access memory (RAM) and executed by a processing circuit such as a central processing unit (CPU). The recording medium may be, for example, a magnetic disk, an optical disk, a magneto-optical disk, or a flash memory. The computer program may be distributed, for example, via a network without using a recording medium. The computer may be an application-specific integrated circuit (ASIC), a general-purpose processor that executes functions by loading a software program, or a computer on a server used in cloud computing. The series of processes performed by each device described herein may be centrally processed by a single computer or distributed across multiple computers. Furthermore, in each of the above embodiments, two or more communication means present in one device may be physically implemented on a single medium.

[0150] Furthermore, the processes described herein using flowcharts or sequence diagrams do not necessarily have to be performed in the order shown. Some process steps may be performed in parallel. Furthermore, additional process steps may be employed, and some process steps may be omitted. [Explanation of symbols]

[0151] 1 System 10 Cash handling equipment 11 Operation display section 12 Reading unit 13 Publishing Department 14 Cash Processing Section 15 Control Unit 20 Management Server 21 Tax Item Table 22 Late Fee Table 23 Later payment late fee collection history DB 24 Collection history DB 30 Management terminal 31 Operation display section 32 Control Unit

Claims

1. a control unit that calculates late fees based on payment information read from the first information code attached to the payment slip, and controls the process of issuing a late fee payment slip attached with a second information code that stores later payment information for later payment of the calculated late fees; A cash processing device comprising:

2. The control unit calculates the late fee based on the tax item and payment deadline of the payment specified from the payment information and the date on which the first information code is read. The cash processing device according to claim 1 .

3. The later payment information includes information indicating the calculated late payment fee. The cash processing device according to claim 2 .

4. The cash processing device further includes an operation unit that accepts selection of same-day payment or later payment for each of the one or more accrued late fees, the control unit controls a process of storing cash equivalent to the late fees for which same-day payment has been selected, and controls a process of issuing the late fees payment slip for the late fees for which later payment has been selected. The cash processing device according to claim 1 .

5. When later payment is selected for the plurality of late fees, the operation unit accepts a selection of whether to issue a plurality of late fee payment slips to which the second information code storing one of the later payment information is attached, or to issue a single late fee payment slip to which the second information code storing the plurality of later payment information is attached, the control unit controls a process of issuing the late fee payment slip in accordance with the selection result accepted by the operation unit. The cash processing device according to claim 4.

6. When the later payment information is read from the second information code attached to the late payment fee payment slip, the control unit controls a process of storing cash equivalent to the late payment fee based on the read later payment information. The cash processing device according to claim 1 .

7. the first information code is a barcode, the second information code is a two-dimensional code; The cash processing device according to claim 1 .

8. a management device that stores information regarding late fees; a cash processing device that calculates the late fees based on payment information read from a first information code attached to the payment slip and the calculation rules for the late fees stored in the management device, and controls the process of issuing a late fee payment slip attached with a second information code that stores later payment information for later payment of the calculated late fees; A system comprising:

9. The management device stores, for each payment slip, whether or not a late fee to be paid at a later date has occurred and whether or not the late fee has been paid. The system of claim 8.

10. An information processing method executed by a computer that controls a cash processing device, The system controls a process of calculating late fees based on payment information read from a first information code attached to a payment slip, and issuing a late fee payment slip with a second information code stored therein that stores later payment information for later payment of the calculated late fees. An information processing method including:

11. A computer that controls a cash processing device a control unit that calculates late fees based on payment information read from the first information code attached to the payment slip, and controls the process of issuing a late fee payment slip attached with a second information code that stores later payment information for later payment of the calculated late fees; A program to function as a

Images