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

Abstract

To provide a mechanism capable of improving the usability of paying a payment using a payment slip. [Solution] An information processing device comprising: a first setting unit that sets a tax item code indicating the tax item of a local government for the tax items of multiple local governments; a second setting unit that sets setting information for multiple local governments to be referenced when creating a collection history file indicating the collection history of payment amounts; and a creation unit that creates the collection history file for a selected local government and tax item based on the collection records of payment amounts for the selected local government and tax item, the tax item code corresponding to the selected local government and tax item, and the setting information for the selected local government.

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing 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. A known example of a device used in such collection systems is a customer-operated cash processing device (hereinafter also referred to as a self-service cash processing machine). Typically, a self-service cash processing machine is installed at a counter or the like of a specific local government, and accepts payments made by customers themselves using payment slips issued by the local government.

[0003] The payment slips used in such collection systems store a variety of information. For example, Patent Document 1 below discloses a technology for outputting payment slips that include information specific to a local government. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2016-218701 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the payment slips that can be accepted by self-service cash processing machines are limited to those issued by the local government where the machines are installed, and there is still room for improvement in the usability of paying payments using payment slips.

[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 system that can improve the usability of paying payments using payment slips. [Means for solving the problem]

[0007] In order to solve the above problem, according to one aspect of the present invention, an information processing device is provided, comprising: a first setting unit that sets a tax item code indicating a tax item of a local government for the tax items of a plurality of the local governments; a second setting unit that sets setting information for a plurality of the local governments to be referenced when creating a payment history file indicating the payment payment history; and a creation unit that creates the payment history file for a selected local government and tax item based on the payment payment record for the selected local government and tax item, the tax item code corresponding to the selected local government and tax item, and the setting information for the selected local government.

[0008] The creation unit may create the payment history file including the tax item code corresponding to the selected combination of the local government and the tax item.

[0009] The tax item code indicating a particular tax item may be different for each local government.

[0010] The system may further include a third setting unit that sets a local government code indicating the local government for a plurality of the local governments, and the tax item code may be associated with the local government code.

[0011] The setting information may include information for identifying the scheduled payment date from the local government to the financial institution, and the creation unit may identify the scheduled payment date of the payment based on the setting information and information included in the collection record indicating the date and time the payment was collected, and create the collection history file including information indicating the identified scheduled payment date.

[0012] The setting information may include information indicating stores in the local government, and the creation unit may identify the stores in the selected local government based on the setting information and create the collection history file including information indicating the identified stores.

[0013] In addition, in order to solve the above problem, according to another aspect of the present invention, an information processing system is provided, comprising: a terminal device that accepts an operation to select a local government and a tax item for which a collection history file of payments to a local government is to be created; and an information processing device that creates the collection history file of the local government and the tax item selected in the operation accepted by the terminal device, wherein the information processing device has a first setting unit that sets a tax item code indicating the tax item of the local government for the tax items of a plurality of the local governments; a second setting unit that sets setting information for a plurality of the local governments to be referenced when creating a collection history file indicating the collection history of payments; and a creation unit that creates the collection history file of the selected local government and the selected tax item based on the collection records of the payments for the selected local government and the selected tax item, the tax item code corresponding to the selected local government and the selected tax item, and the setting information for the selected local government.

[0014] The information processing system may further include a cash processing device that accepts payment of the payment and creates a collection record based on information stored in an information code attached to a payment slip, and the information processing device may create the collection history file based on the collection record created by the cash processing device.

[0015] The information processing device may further have a third setting unit that sets a municipal code indicating the municipality for a plurality of the municipalities, and the cash processing device may identify the tax item of the payment and the municipality to which it is to be paid based on the information stored in the information code, the tax item code set by the first setting unit, and the municipality code set by the third setting unit, and create the collection record including information indicating the identified tax item and information indicating the identified municipality.

[0016] The cash processing device may execute the payment of the payment if the information stored in the information code corresponds to the tax item code set by the first setting unit and the local government code set by the third setting unit, and may refuse to pay the payment if the information does not correspond to the tax item code set by the first setting unit and the local government code set by the third setting unit.

[0017] The local government corresponding to the location where the cash processing device is installed may be different from the local government to which the payment is to be made.

[0018] 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, which includes setting a tax item code indicating the tax item of a local government for the tax items of a plurality of the local governments, setting setting information for the plurality of the local governments to be referenced when creating a payment history file indicating the payment payment history, and creating the payment history file for the selected local government and the tax item based on the payment payment records for the selected local government and the tax item, the tax item code corresponding to the selected local government and the tax item, and the setting information for the selected local government.

[0019] 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 to function as a first setting unit that sets a tax item code indicating the tax item of a local government for the tax items of a plurality of the local governments, a second setting unit that sets setting information for a plurality of the local governments to be referenced when creating a collection history file indicating the collection history of payment payments, and a creation unit that creates the collection history file for a selected local government and tax item based on the collection record of the payment for the selected local government and tax item, the tax item code corresponding to the selected local government and tax item, and the setting information for the selected local government. [Effects of the Invention]

[0020] As described above, the present invention provides a mechanism that can improve the usability of paying payments using payment slips. [Brief explanation of the drawings]

[0021] [Figure 1] 1 is a block diagram showing an example of the configuration of a system 1 according to an embodiment of the present invention. [Figure 2] FIG. 10 is a diagram illustrating an example of barcode information. [Figure 3] FIG. 10 is a diagram showing an example of the configuration of a storage history file. [Figure 4] 10 is a flowchart showing an example of the flow of a setting process for a local government code table 211 and a collection history file setting table 213, which is executed by the system 1 according to this embodiment. [Figure 5] 10 is a flowchart showing an example of the flow of a process for setting a tax item code table 212, which is executed by the system 1 according to the present embodiment. [Figure 6] 10 is a flowchart showing an example of the flow of processing related to the receipt of payment, which is executed by the system 1 according to this embodiment. [Figure 7] 10 is a flowchart showing an example of the flow of a storage history file creation process executed by the system 1 according to the present embodiment. [Figure 8] 10 is a flowchart showing an example of the flow of a storage history file creation process executed by the system 1 according to the present embodiment. [Figure 9] 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

[0022] 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.

[0023] <1. Overview> 1 is a block diagram showing an example of the configuration of a system 1 according to one embodiment of the present invention. An overview of the system 1 according to this embodiment will be described below with reference to FIG.

[0024] As shown in Fig. 1, the system 1 according to this embodiment includes a cash processing device 10, a control server 20, and a management terminal 30. The control server 20, the cash processing device 10, and the management terminal 30 are communicatively connected to each other. The control server 20 and the local government server 40 are communicatively connected to each other. These communication paths may be established by any network, such as a local network, a business operator network, or the Internet. Although Fig. 1 illustrates one cash processing device 10, the system 1 may include multiple cash processing devices 10.

[0025] The cash processing device 10 is a self-service cash processing machine that can be operated by a customer (i.e., a taxpayer) to pay taxes and other payments by itself. The cash processing device 10 can be installed at a local government counter, a convenience store, or the like. The customer can pay the payment at the cash processing device 10 using a payment slip. Note that when a customer pays the payment, it means that the cash processing device 10 receives the payment.

[0026] The payment slip is provided with an information code that stores various information related to the payment, such as the amount to be paid and the payment deadline. Therefore, the cash processing device 10 reads the information code attached to the payment slip and stores the payment based on the information stored in the read information code. A barcode, a two-dimensional code, or the like may be used as the information code. In the following, it is assumed that the payment slip is provided with a barcode.

[0027] The control server 20 is an information processing device that controls the overall operation of the system 1. For example, when a payment is collected by the cash processing device 10, the control server 20 requests the local government server 40 to update the collection history of the payment managed by the local government server 40. At that time, the control server 20 creates a file (hereinafter also referred to as a collection history file) that includes information stored in the information code read by the cash processing device 10, and transmits the file to the local government server 40.

[0028] The management terminal 30 is a terminal device operated by an administrator of the system 1. The management terminal 30 functions as an interface between the control server 20 and the administrator. For example, the management terminal 30 accesses the control server 20 based on an operation by the administrator and causes the control server 20 to execute a predetermined function.

[0029] The local government server 40 is an information processing device managed / operated by the local government that issues the payment slip. The local government server 40 manages a master database (DB) 41 that stores various information related to payments, such as the tax type, amount, payment deadline, and payment history (i.e., whether payment has been made or not). In particular, the local government server 40 updates the master DB 41 based on the payment history file received from the control server 20. Specifically, the local government server 40 deletes records related to payments that have been made from the master DB 41.

[0030] Typically, self-service cash handling machines are installed at the counters of specific local governments and accept payments made by customers using payment slips from that local government. Therefore, it has been difficult for self-service cash handling machines to accept payments using payment slips from local governments other than the one in which they are installed.

[0031] Therefore, in the system 1 according to this embodiment, various information is preset so that the cash processing device 10 can collect payments from any local government. When a payment is collected by the cash processing device 10, the system 1 creates a collection history file for that local government by referencing the preset information. That is, no matter which cash processing device 10 collects a payment for which local government, the system 1 creates a collection history file for that local government and reflects this in the master DB 41 managed by the local government server 40.

[0032] According to this configuration, it becomes possible to accept payments of any local government levies at the cash processing device 10. As a result, it becomes possible to significantly improve usability for customers, for example, to make payments to a local government in Hokkaido using a cash processing device 10 installed in Okinawa.

[0033] <2.Configuration example> Hereinafter, with reference to FIG. 1 again, a detailed description will be given of an example of the configuration of the system 1 according to this embodiment.

[0034] (1) Cash processing device 10 Referring again to FIG. 1, 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.

[0035] 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. The operation display unit 11 displays screens that guide the customer through operations related to payment of the payment, such as a screen that guides the customer to hold the barcode on the payment slip over the reading unit 12, or a screen that guides the customer to insert cash equivalent to the payment. The customer then inputs various information for making the payment on such screens.

[0036] The reading unit 12 has the function of reading various information contained in the payment slip. The reading unit 12 is configured, for example, with an optical reader, and can read the information stored in the barcode from the barcode. The information stored in the barcode will hereinafter also be referred to as barcode information.

[0037] An example of barcode information will be described below with reference to FIG.

[0038] FIG. 2 is a diagram showing an example of barcode information. As shown in FIG. 2, numbers are stored in the barcode, and it is predetermined which digits each store the meaning of. In the example shown in FIG. 2, the barcode information includes a header, payment deadline, usage code, item code, municipality code, amount, flag, and end. By referencing the usage code, item code, and municipality code included in the barcode information, it is possible to identify which municipality and which tax item the payment slip relates to.

[0039] The issuing unit 13 has a function of issuing a medium storing various information. The issuing unit 13 may be, for example, a receipt printer that prints information on a paper medium. For example, the issuing unit 13 issues a usage statement after the payment has been received.

[0040] 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 cabinet 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 amount, and dispenses change, if any.

[0041] 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.

[0042] The output of information and acquisition of input information by the operation display unit 11, 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 creation of a deposit record when a payment is deposited and the transmission of the record to the control server 20 are also examples of objects controlled by the control unit 15. The deposit record is a record of various information related to the deposited payment, and is created when the cash processing device 10 deposits the payment.

[0043] (2) Control Server 20 Referring again to FIG. 1, the control server 20 includes a storage unit 21 and a control unit 22.

[0044] (Storage unit 21) The memory unit 21 has a function of storing various information for the operation of the control server 20. The memory unit 21 stores a local government code table 211, a tax item code table 212, a payment history file setting table 213, and a payment record DB (Data Base) 214.

[0045] (Municipality Code Table 211) The local government code table 211 is a table showing the correspondence between local government codes and local government names. A local government code is identification information that indicates a local government. An example of information stored in the local government code table 211 is shown in Table 1 below.

[0046] [Table 1]

[0047] The local government code table 211 is set for each cash processing device 10. For example, the local government code table 211 is set based on an operation by an administrator on the management terminal 30 when the cash processing device 10 is installed. The local government code table 211 can also be interpreted as indicating the local governments that can be handled by the cash processing device 10 for which the local government code table 211 is set. Therefore, if the number of local governments that can be handled by the cash processing device 10 increases or decreases, the local government code table 211 can be revised.

[0048] The cash processing device 10 assigns a local government code to the deposit record. With this configuration, it becomes possible to identify which local government the deposit record belongs to.

[0049] (Tax Code Table 212) The tax item code table 212 is a table showing the correspondence between tax items and tax item codes for each local government. The tax item code is identification information that indicates the tax item. An example of information stored in the tax item code table 212 is shown in Table 2 below.

[0050] [Table 2]

[0051] The tax item names shown in Table 2 are the names of the tax items. The usage code and subject code are information that indicates the tax item. In other words, the combination of the usage code and subject code corresponds to the tax item code. The municipality code is the municipality code of the municipality in which the relevant tax item is set. Note that the subject code "-" indicates that the subject code is not used.

[0052] As shown in Table 2, the tax item code is associated with the local government code. With this configuration, it is possible to uniquely identify a specific tax item of a specific local government by combining the local government code and the tax item code.

[0053] As shown in Table 2, different types of taxes can be set by each local government. There are also tax items that are common to multiple local governments, such as light vehicle tax and childcare fees.

[0054] As shown in Table 2, the tax item code indicating a specific tax item may differ for each local government. This configuration allows flexible setting of tax item codes for each local government.

[0055] As shown in Table 2, the use of usage codes and subject codes differs from one local government to another. As an example, some local governments set a usage code that is common to all tax items, and a different subject code for each tax item. As another example, some local governments set a different usage code for each tax item, and a different subject code for each tax item. As another example, some local governments only set a usage code. In any case, the combination of usage code and subject code is unique, and by using these two values ​​and the local government code, it is possible to identify the local government and tax item indicated by the barcode on the payment slip.

[0056] The tax item code table 212 is set for each cash processing device 10. For example, the tax item code table 212 is set based on an operation by an administrator on the management terminal 30 when the cash processing device 10 is installed. The tax item code table 212 can also be considered to indicate the tax items that can be handled by the cash processing device 10 for which the tax item code table 212 is set.

[0057] (Storage History File Setting Table 213) The storage history file setting table 213 is setting information that is referenced when creating a storage history file. An example of the storage history file setting table 213 is shown in Table 3 below.

[0058] [Table 3]

[0059] As shown in Table 3, the collection history file setting table 213 includes the municipality code, store code, store name, and scheduled payment date changeover time. When creating a collection history file for a specific municipality, a record including the municipality code that identifies the municipality is referenced. The store code and store name are information that indicates the municipality store to which the payment is to be paid (i.e., the jurisdiction over the payment). The scheduled payment date changeover time is information for identifying the scheduled payment date from the municipality to the financial institution. If the collection time of the payment is before the scheduled payment date changeover time, the scheduled payment date will be the day the payment is received. On the other hand, if the collection time of the payment is after the scheduled payment date changeover time, the day after the payment is received will be the scheduled payment date.

[0060] The specifications of the collection history file are determined for each collection agent. Therefore, the specifications can be the same for multiple municipalities, but the values ​​for each item included in the collection history file can differ depending on the municipality. In this regard, by setting records for each municipality in the collection history file setting table 213 and referencing them when creating a collection history file, it is possible to create an appropriate collection history file for each municipality.

[0061] The deposit history file setting table 213 is set for each cash processing device 10. For example, the deposit history file setting table 213 is set based on an operation by an administrator on the management terminal 30 when the cash processing device 10 is installed. The deposit history file setting table 213 can also be interpreted as indicating the local governments that can be handled by the cash processing device 10 for which the deposit history file setting table 213 is set. Therefore, if the number of local governments that can be handled by the cash processing device 10 increases or decreases, the deposit history file setting table 213 can be modified.

[0062] (Storage record DB214) The deposit record DB 214 is a DB that stores deposit records created by the cash processing device 10. An example of information stored in the deposit record DB 214 is shown in Table 4 below.

[0063] [Table 4]

[0064] As shown in Table 4, the collection record DB214 may include a collection number, tax item name, barcode information, amount, collection date and time, and municipal code. The collection number is a number assigned when the payment is collected using a payment slip. The tax item name is the name of the tax item of the collected payment. The barcode information is all digits of the barcode information read from the barcode attached to the payment slip when the payment is collected. The amount is the amount of the payment. The collection date and time indicates the date and time the payment was collected. The municipal code is information indicating the municipality where the payment is collected.

[0065] A single record in Table 4 is a payment record for one payment.

[0066] Here, the cash processing device 10 (for example, the control unit 15) accepts payment of the payment based on the barcode information stored in the barcode attached to the payment slip and creates a receipt record. In particular, the cash processing device 10 can appropriately create a payment record for any combination of local governments and tax items from among multiple local governments and multiple tax items by referring to the information stored in the memory unit 21. This point will be explained in detail below.

[0067] The cash processing device 10 identifies the tax type of the payment on the payment slip and the local government to which the payment is to be made based on the barcode information stored in the barcode attached to the payment slip, the local government code table 211, and the tax item code table 212. The cash processing device 10 then creates a deposit record including information indicating the identified local government and information indicating the identified tax item. In more detail, the cash processing device 10 identifies the local government to which the payment is to be made by referencing the local government code table 211 for the local government code included in the barcode information, and creates a deposit record including the local government code of the identified local government. The cash processing device 10 also identifies the tax type of the payment by referencing the tax item code table 212 for the combination of the local government code and tax item code included in the barcode information, and creates a deposit record including information indicating the identified tax item. This configuration makes it possible for the cash processing device 10 to accept payments issued by any local government it can handle and create a deposit record.

[0068] The local government code table 211 and the tax item code table 212 may be set for each cash processing device 10. The cash processing device 10 may then refer to the local government code table 211 and the tax item code table 212 set for the cash processing device 10 to determine whether to accept a payment slip. Specifically, the cash processing device 10 may execute payment of the payment if the barcode information stored in the barcode corresponds to the local government code table 211 and the tax item code table 212 set for the cash processing device 10. Note that the correspondence of the barcode information to the local government code table 211 and the tax item code table 212 means that the local government code included in the barcode information is included in the local government code table 211, and the combination of the local government code and the tax item code included in the barcode information is included in the tax item code table 212. On the other hand, the cash processing device 10 may refuse payment of the payment if the barcode information stored in the barcode does not correspond to the local government code table 211 and the tax item code table 212 set for the cash processing device 10. According to this configuration, it becomes possible for each cash processing device 10 to appropriately determine whether or not a payment slip can be accepted.

[0069] The local government corresponding to the location where the cash processing device 10 is installed may be different from the local government to which the levy is to be paid. For example, a cash processing device 10 installed in a convenience store in City A may accept a levy for City B. This is possible by the cash processing device 10 referring to various information stored in the memory unit 21. This configuration makes it possible to significantly improve the usability of paying levies.

[0070] (control unit 22) The control unit 22 has a function of controlling the overall operation of the control server 20. The control unit 22 functions as a setting unit 221, a storage control unit 222, and a storage history file creation unit 223.

[0071] (Setting unit 221) The setting unit 221 has a function of making various settings related to the system 1.

[0072] The setting unit 221 sets tax item codes (i.e., usage codes or combinations of usage codes and subject codes) indicating local government tax items for multiple local government tax items. That is, the setting unit 221 sets the tax item code table 212 shown in Table 2. The setting unit 221 is an example of a first setting unit in this embodiment.

[0073] The setting unit 221 sets, for multiple local governments, setting information to be referenced when creating a payment history file showing the payment history of payments. That is, the setting unit 221 sets the payment history file setting table 213 shown in Table 3. The setting unit 221 is an example of a second setting unit in this embodiment.

[0074] The setting unit 221 sets a local government code indicating a local government for a plurality of local governments. That is, the setting unit 221 sets the local government code table 211 shown in Table 1. The setting unit 221 is an example of a third setting unit in this embodiment.

[0075] The function of the setting unit 221 may be realized as an application accessible via the management terminal 30. This application is also referred to as a setting tool below. The settings of the local government code table 211, the tax item code table 212, and the collection history file setting table 213 can be executed based on operations on the setting tool by an administrator operating the management terminal 30.

[0076] (Storage control unit 222) The receipt control unit 222 has a function of controlling processing related to the receipt of payments by the cash processing device 10. In detail, the receipt control unit 222 controls processing for storing a receipt record of payments made by the cash processing device 10. For example, the receipt control unit 222 receives, from the cash processing device 10, a receipt record obtained when a payment is received in the cash processing device 10, and adds a record indicating the receipt record to the receipt record DB214.

[0077] The deposit control unit 222 also controls the operation of the cash processing device 10 when depositing a payment using a payment slip.

[0078] As an example, the collection control unit 222 may control the cash processing device 10 to execute or reject payment of the payment based on the payment slip by referring to the local government code table 211 and / or the tax item code table 212.

[0079] (Storage History File Creation Unit 223) The collection history file creation unit 223 has a function of creating a collection history file showing the collection history of the payment, based on the collection record created by the cash processing device 10 when the payment is collected using a payment slip and stored in the collection record DB 214. The collection history file creation unit 223 is an example of a creation unit in this embodiment.

[0080] The collection history file creation unit 223 creates a collection history file for each local government. For example, the collection history file creation unit 223 creates a separate collection history file for City A and a separate collection history file for City B. This configuration makes it possible to create an appropriate collection history file for each local government.

[0081] An example of the structure of the storage history file will be described below with reference to FIG.

[0082] Figure 3 is a diagram showing an example of the structure of a storage history file. As shown in Figure 3, the storage history file may include four types of sections: a header record, a data record, a trailer record, and an end record. An example of the format of a storage history file is shown in Table 5 below.

[0083] [Table 5]

[0084] In the content column shown in Table 5, "n" indicates a number, "YYYYMMDD" indicates the date, and "HHMM" indicates the time.

[0085] As shown in Fig. 3, one storage history file may contain multiple data records. The number of data records contained in one storage history file corresponds to the number of storage records.

[0086] In addition, there are cases where a single collection history file is created for a single tax item, and cases where a single file is created for multiple tax items. When multiple tax items are created as a single file, a collection history file is created by linking together a combination of one header record, one or more data records, and one trailer record for each tax item, followed by one end record.

[0087] Here, the collection history file creation unit 223 creates a collection history file for the selected municipality and tax item based on the collection records of payments for the selected municipality and tax item, the tax item code corresponding to the selected municipality and tax item, and the information for the selected municipality in the collection history file setting table 213. The selection of the municipality and tax item can be performed by the administrator via the management terminal 30. With this configuration, it is possible to create a collection history file for any municipality and any tax item from among multiple municipalities and multiple tax items.

[0088] The collection history file creation unit 223 creates a collection history file including a tax item code corresponding to the combination of the selected local government and tax item. In detail, as shown in Table 5, the collection history file creation unit 223 creates a collection history file for the selected local government that includes a usage code and an item code corresponding to the selected tax item. With this configuration, the local government server 40 can appropriately determine which tax item the received collection history file corresponds to.

[0089] The collection history file creation unit 223 identifies the scheduled payment date of the payment based on the information of the selected local government in the collection history file setting table 213 and the information indicating the date and time the payment was collected, which is included in the collection record, and creates a collection history file containing information indicating the identified scheduled payment date. In more detail, if the collection time of the payment (the time portion of the collection date and time) shown in Table 4 is before the scheduled payment date switching time shown in Table 3, the collection history file creation unit 223 identifies the day after the collection date as the scheduled payment date if the collection time of the payment shown in Table 4 is after the scheduled payment date switching time shown in Table 3. This configuration makes it possible to create a collection history file containing an appropriate scheduled payment date for each local government.

[0090] The deposit history file creation unit 223 identifies the stores of the selected municipality based on the information of the selected municipality in the deposit history file setting table 213, and creates a deposit history file including information indicating the identified stores. In more detail, as shown in Tables 3 and 5, the deposit history file created includes the store code and store name for each municipality. With this configuration, it becomes possible to appropriately update the master DB 41 in the municipality server 40.

[0091] The function of the storage history file creation unit 223 may be realized as an application accessible via the management terminal 30. This application is also referred to as a storage history file creation application below. The creation of the storage history file may be executed based on operations on the storage history file creation application by an administrator operating the management terminal 30.

[0092] (3) Management terminal 30 1 again, the management terminal 30 includes an operation display unit 31. 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 the display unit is realized by, for example, a display. The function as the operation unit is realized by, for example, a keyboard and a mouse.

[0093] As an example, the operation display unit 31 displays the screen of the setting tool, accepts various inputs to the setting tool, and creates and stores a local government code table 211, a tax item code table 212, and a collection history file setting table 213 in the control server 20.

[0094] As another example, the operation display unit 31 displays the screen of a payment history file creation application, accepts various inputs to the payment history file creation application, and causes the control server 20 to create a payment history file and transmit it to the local government server 40. In more detail, the operation display unit 31 accepts an operation to select the local government and tax item for which a payment history file is to be created, and causes the control server 20 to create a payment history file related to the selected tax item for the selected local government and transmit it to the local government server 40.

[0095] These operations of the control server 20 via the management terminal 30 may be performed via a web browser. Of course, a display, a keyboard, etc. may be connected to the control server 20, and various operations may be performed directly on the control server 20. In this case, the management terminal 30 may be omitted from the system 1.

[0096] (4) Municipal Server 40 1 again, the local government server 40 stores and updates the master DB 41. The master DB 41 stores a collection history including various information such as the tax item for each payment and information indicating whether payment has been made or not. The local government server 40 updates the master DB 41 based on the collection history file received from the control server 20.

[0097] <3. Processing flow> (1) Setting process of the local government code table 211 and the collection history file setting table 213 4 is a flowchart showing an example of the flow of a process for setting the local government code table 211 and the deposit history file setting table 213, which is executed by the system 1 according to this embodiment. The process according to this flow can be executed based on an operation by an administrator on the management terminal 30 when the cash processing device 10 is installed.

[0098] As shown in FIG. 4, first, the management terminal 30 displays an initial screen and starts up a setting tool installed in the control server 20 based on an operation on the initial screen (step S101).

[0099] Next, the management terminal 30 selects the local government code registration function based on the operation on the screen of the setting tool (step S102).

[0100] Next, the management terminal 30 registers the local government code and local government name of the local government that can be accepted by the cash processing device 10 (steps S103 and S104). As a result, one record is added to the local government code table 211.

[0101] Next, the management terminal 30 registers the store code, store name, and scheduled payment date change time, which are referenced when creating a collection history file for the local government, in association with the local government code (steps S105 to S107). This adds one record to the collection history file setting table 213.

[0102] The registration process for one local government is completed through the process described above. Therefore, the management terminal 30 determines whether there are any other local governments to be registered (step S108).

[0103] If it is determined that there are other local governments to be registered (step S108: YES), the process returns to step S103 again.

[0104] If it is determined that there are no other local governments to be registered (step S108: NO), that is, if it is determined that information registration for all local governments that can be handled by the cash processing device 10 has been completed, the process ends.

[0105] By the process described above, before the start of operation of the cash processing device 10, records of local governments that can be handled by the cash processing device 10 are registered in the local government code table 211 and the deposit history file setting table 213. The registered records can be added / deleted / changed at any timing even after the start of operation of the cash processing device 10 based on operations by the administrator on the management terminal 30.

[0106] Although the processing using the above-mentioned setting tool is described with the management terminal 30 as the subject for convenience, the management terminal 30 merely functions as an input / output interface, and processing other than input / output is executed by the control server 20.

[0107] (2) Setting process for tax code table 212 5 is a flowchart showing an example of the flow of a process for setting the tax item code table 212, which is executed by the system 1 according to this embodiment. The process according to this flow can be executed based on an operation by an administrator on the management terminal 30 when the cash processing device 10 is installed.

[0108] As shown in FIG. 5, first, the management terminal 30 displays an initial screen and starts up a setting tool installed in the control server 20 based on an operation on the initial screen (step S201).

[0109] Next, the management terminal 30 selects the tax item code registration function based on the operation on the screen of the setting tool (step S202).

[0110] Next, the management terminal 30 accepts input of the local government code of any one of the one or more local governments for which the tax item code is to be registered (step S203).

[0111] Next, the management terminal 30 determines whether or not there is a registered tax item in the tax item code table 212 (step S204).

[0112] If it is determined that there is no tax item registered in the tax item code table 212 (step S204: NO), the process proceeds to step S208.

[0113] On the other hand, if it is determined that there is a tax item registered in the tax item code table 212 (step S204: YES), the management terminal 30 displays a list of the tax items registered in the tax item code table 212 (step S205). Here, the tax items registered in the tax item code table 212 refer to tax items registered in other municipalities other than the municipality to which the tax item is to be registered.

[0114] Next, the management terminal 30 selects all tax items that exist in the local government to which the tax is to be registered from the list of tax items displayed, and accepts input of a usage code and an item code for each tax item (step S206).

[0115] Next, the management terminal 30 determines whether or not there are any tax items other than the tax items listed in step S205 that require registration in the local government that is the registration target (step S207).

[0116] If it is determined that there are no tax items that require registration in the local government to which registration is to be made (step S207: NO), the process proceeds to step S211.

[0117] On the other hand, if it is determined that there is a tax item that needs to be registered in the local government to which registration is to be made (step S207: YES), the management terminal 30 accepts the input of the tax item name, usage code, and subject code, and registers them in association with the local government code of the local government to which registration is to be made (steps S208 and S209). As a result, one record is added to the tax item code table 212.

[0118] Next, the management terminal 30 determines whether there are any other tax items to be registered (step S210).

[0119] If it is determined that there are other tax items to be registered (step S210: YES), the process returns to step S208 again.

[0120] On the other hand, if it is determined that there are no other tax items to be registered (step S210: NO), the management terminal 30 determines whether there are any other local governments to be registered (step S211).

[0121] If it is determined that there is another local government to be registered (step S211: YES), the process returns to step S203 again.

[0122] On the other hand, if it is determined that there are no other local governments to be registered (step S211: NO), the process ends.

[0123] Through the process described above, before the start of operation of the cash processing device 10, records of local governments and tax items that can be handled by the cash processing device 10 are registered in the tax item code table 212. The registered records can be added / deleted / changed at any timing even after the start of operation of the cash processing device 10 based on operations by the administrator on the management terminal 30.

[0124] Although the processing using the above-mentioned setting tool is described with the management terminal 30 as the subject for convenience, the management terminal 30 merely functions as an input / output interface, and the actual processing is performed by the control server 20.

[0125] (3) Processing of payment receipts 6 is a flowchart showing an example of the flow of processing related to the receipt of payment, which is executed by the system 1 according to this embodiment. The processing according to this flow is executed when a customer operates the cash processing device 10 to pay a payment using a payment slip.

[0126] As shown in Fig. 6, first, the cash processing device 10 displays an initial screen and reads the barcode on the payment slip that the customer brings to make the payment (step S301). This starts the procedure for making the payment.

[0127] Next, the cash processing device 10 executes a storing process based on the read barcode information (step S302). For example, the cash processing device 10 stores cash equivalent to the payment, dispenses change if any, and issues a receipt.

[0128] Thereafter, the cash processing device 10 starts the process of creating a storage record (step S303).

[0129] That is, the cash processing device 10 extracts the local government code, the usage code, and the subject code from the barcode information read in step S301 (steps S304 to S306).

[0130] Then, based on the extracted information, the cash processing device 10 identifies the tax item of the payment from the tax item code table 212 (step S307). In detail, the cash processing device 10 identifies, in the tax item code table 212 set in the cash processing device 10, the tax item that has the same combination as the local government code, use code, and subject code extracted in steps S304 to S306.

[0131] Next, the cash processing device 10 sets the identified tax item as the tax item of the collection record, and creates a collection record in which the extracted local government code is set as the local government code of the collection record (step S308), and the process ends.

[0132] The cash processing device 10 may accept payments using multiple payment slips. In this case, the cash processing device 10 reads multiple barcodes attached to multiple payment slips in step S301. The cash processing device 10 then performs the processes of steps S303 to S308 for each payment slip. The cash processing device 10 can simultaneously collect payments and create collection records for different tax items and for different local governments.

[0133] (4) Storage history file creation process 7 and 8 are flowcharts showing an example of the flow of a collection history file creation process executed by the system 1 according to this embodiment. The process according to this flow can be executed once a day, at any timing, for example, after closing time of the store where the cash processing device 10 is installed, based on an operation by an administrator on the management terminal 30. As a result, a collection history file of the specified tax items is created for each specified local government.

[0134] As shown in FIG. 7, first, the management terminal 30 displays an initial screen, and starts a storage history file creation application installed in the control server 20 based on an operation on the initial screen (step S401).

[0135] Next, the management terminal 30 refers to the local government code table 211, displays on the screen all the names of local governments that can be handled, and accepts an operation to select a local government for which a deposit history file is to be created (step S402).

[0136] Next, the management terminal 30 refers to the tax item code table 212 and displays a list of all tax items registered in the local government selected in step S402 (step S403).

[0137] Next, the management terminal 30 accepts an operation to select a tax item for which a payment history file is to be created from the list of tax items displayed in step S403 (step S404).

[0138] Next, the management terminal 30 accepts an operation to specify the payment period for which the payment history file is to be created (step S405). For example, if a payment history file for payments up to 14:59:59 of the previous day has already been created, the period from 15:00 of the previous day to a specified time of the current day (for example, 14:59:59) can be specified.

[0139] Here, a button for creating a storage history file is pressed on the screen, and the subsequent processing is then executed within the control server 20.

[0140] First, the control server 20 acquires the usage code and the subject code of the tax item selected in step S404 for which a payment history file is to be created (step S406).

[0141] Next, the control server 20 refers to the collection history file setting table 213 and acquires the store code, store name, and scheduled payment date change time of the local government for which the collection history file is to be created, selected in step S402 (steps S407 to S409).

[0142] The processing relating to steps S410 to S415 described below is executed by selecting any one tax item for which a payment history file has not yet been created from among the tax items for which a payment history file is to be created selected in step S404.

[0143] First, the control server 20 creates a header record of the payment history file for the tax item for which the payment history file is to be created, using the usage code and subject code acquired in step S406 (step S410).

[0144] Next, as shown in Figure 8, the control server 20 obtains from the collection record DB 214 the collection records corresponding to the local government for which the collection history file is to be created, the tax item for which the collection history file is to be created, and the payment period for which the collection history file is to be created (step S411).

[0145] The processing in steps S412 and S413 described below is executed by selecting any one of the storage records acquired in step S411 for which a storage history file has not yet been created.

[0146] Next, the control server 20 determines the scheduled payment date based on the receipt date and time of the receipt record acquired in step S411 and the scheduled payment date switching time acquired in step S409 (step S412). For example, if the receipt date and time is 14:59:59 on Feb. 22, 2024, and the scheduled payment date switching time is 145959, the scheduled payment date is determined to be Feb. 22, 2024.

[0147] Next, the control server 20 creates a data record in the payment history file using the store code and store name obtained in steps S407 and S408, the payment record obtained in step S411, and the scheduled payment date determined in step S412 (step S413).

[0148] Next, the control server 20 determines whether or not there is any storage record for which a storage history file has not yet been created among the storage records acquired in step S411 (step S414).

[0149] If it is determined that there is a storage record for which a storage history file has not yet been created (step S414: YES), processing returns to step S412, and processing related to steps S412 and S413 is performed for the storage record for which a storage history file has not yet been created.

[0150] On the other hand, if it is determined that there are no collection records for which a collection history file has not yet been created (step S414: NO), the control server 20 creates a trailer record for the collection history file for the tax item for which the collection history file is to be created (step S415).

[0151] Next, the control server 20 determines whether or not there are any tax items for which a payment history file has not yet been created among the tax items selected in step S404 for which a payment history file is to be created (step S416).

[0152] If it is determined that there is a tax item for which a payment history file has not yet been created (step S416: YES), the process returns to step S410, and the processes of steps S410 to S415 are executed for the tax item for which a payment history file has not yet been created.

[0153] On the other hand, if it is determined that there is no tax item for which a payment history file has not yet been created (step S416: NO), the control server 20 creates an end record of the payment history file (step S417), and the process ends.

[0154] <4. Effects> According to the present embodiment described above, information on local governments and tax items for which payment slips can be handled by the cash processing device 10 can be registered as the local government code table 211 and the tax item code table 212. By referring to these, the cash processing device 10 can accept payments of payments using payment slips for any tax item of any local government. The control server 20 can then create a collection history file for each local government by referring to the collection history file setting table 213.

[0155] According to this configuration, a customer can pay taxes to a plurality of local governments using one cash processing device 10. This makes it possible to significantly improve usability for paying taxes and public fees.

[0156] Furthermore, with this configuration, the cash processing device 10, which previously could only be installed and used at the counters of specific local governments, can now be installed in various locations, such as banks, post offices, and convenience stores. Residents can now pay taxes and public fees without worrying about the local government on the payment slip they bring in. For example, a customer can pay taxes and public fees by bringing an Okinawa payment slip to a bank in Hokkaido. This significantly improves usability for paying taxes and public fees.

[0157] Furthermore, with this configuration, local governments can receive tax payments from various locations. Therefore, even if a resident travels far away with their tax payment slip, the payment can be reliably made. This reduces the risk of tax defaults.

[0158] <5. Hardware configuration example> Next, the hardware configuration of an information processing device according to this embodiment will be described with reference to Fig. 9. Fig. 9 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. 9 may realize, for example, the control server 20 or the management terminal 30 shown in Fig. 1. Information processing by the cash processing device 10, control server 20, management terminal 30 or local government server 40 according to this embodiment is realized by cooperation between software and hardware described below.

[0159] As shown in FIG. 9, 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.

[0160] 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 consisting of a CPU bus, etc. The CPU 901 may form, for example, the control unit 15 or the control unit 22. The CPU 901 may also be installed in the management terminal 30 and control the overall operation of the management terminal 30. The CPU 901 may also be installed in the local government server 40 and control the overall operation of the local government server 40.

[0161] 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.

[0162] 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 11 or the operation and display unit 31.

[0163] The output device 909 may include, for example, a display device that outputs visual information, such as a liquid crystal display (LCD) device, an OLED (Organic Light Emitting Diode) device, or a lamp. The output device 909 may include an audio output device that outputs auditory information, such as a speaker. The output device 909 may include a tactile presentation device that outputs tactile information, such as an eccentric motor. The output device 909 may form, for example, the operation display unit 11 or the operation display unit 31.

[0164] 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 deleting 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 form, for example, the memory unit 21 or the master DB 41.

[0165] 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.

[0166] 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.

[0167] <6. 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.

[0168] In the above embodiment, an example has been described in which the local government code table 211, the tax item code table 212, and the deposit history file setting table 213 are set for each cash processing device 10, but the present invention is not limited to such an example. At least one of the local government code table 211, the tax item code table 212, and the deposit history file setting table 213 may be set in common for a plurality of cash processing devices 10.

[0169] 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.

[0170] For example, the payment slip may be issued in paper form, or in a form other than paper, such as a web page or image.

[0171] Although the above description concerns the collection of taxes and public fees based on payment slips issued by local governments, the present invention can also be applied to the collection of other payments, such as payments based on payment slips issued by financial institutions.

[0172] 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.

[0173] 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]

[0174] 1 System 10 Cash handling equipment 11 Operation display section 12 Reading unit 13 Publishing Department 14 Cash Processing Section 15 Control Unit 20 Control Server 21 Memory section 211 Municipality Code Table 212 Tax Code Table 213 Storage History File Settings Table 214 Storage Record DB 22 Control Unit 221 Setting Section 222 Storage control unit 223 Storage History File Creation Department 30 Management terminal 31 Operation display section 40 Municipal Server 41 Master DB

Claims

1. a first setting unit that sets tax item codes indicating tax items of a local government for the tax items of a plurality of the local governments; a second setting unit that sets setting information for a plurality of said local governments to be referenced when creating a payment history file showing the payment history of said payments; a creation unit that creates the collection history file for the selected local government and tax item based on the collection records of the payments for the selected local government and tax item, the tax item code corresponding to the selected local government and tax item, and the setting information for the selected local government; An information processing device comprising:

2. The creation unit creates the payment history file including the tax item code corresponding to the selected combination of the local government and the tax item. The information processing device according to claim 1 .

3. The tax item code indicating the specific tax item differs for each local government. The information processing device according to claim 2 .

4. a third setting unit that sets a local government code indicating the local government for each of the plurality of local governments; The tax item code is associated with the local government code. The information processing device according to claim 3 .

5. The setting information includes information for specifying a scheduled payment date from the local government to the financial institution, The creation unit identifies the scheduled payment date of the payment based on the setting information and information included in the payment record indicating the date and time when the payment was received, and creates the payment history file including information indicating the identified scheduled payment date. The information processing device according to claim 1 .

6. The setting information includes information indicating a store in the local government, The creation unit identifies the store in the selected local government based on the setting information, and creates the deposit history file including information indicating the identified store. The information processing device according to claim 1 .

7. a terminal device that accepts an operation to select a local government and a tax item for which a payment history file of payments to the local government is to be created; an information processing device that creates the tax payment history file for the local government and the tax item selected in the operation accepted by the terminal device; Equipped with The information processing device includes: a first setting unit that sets a tax item code indicating the tax item of the local government for the tax items of a plurality of the local governments; a second setting unit that sets setting information for a plurality of said local governments to be referenced when creating a payment history file showing the payment history of said payments; a creation unit that creates the collection history file for the selected local government and tax item based on the collection records of the payments for the selected local government and tax item, the tax item code corresponding to the selected local government and tax item, and the setting information for the selected local government; having Information processing system.

8. The information processing system further includes a cash processing device that accepts payment of the payment based on information stored in an information code attached to a payment slip and creates a receipt record, The information processing device creates the deposit history file based on the deposit record created by the cash processing device. The information processing system according to claim 7 .

9. The information processing device further includes a third setting unit that sets a local government code indicating the local government for each of the plurality of local governments; The cash processing device identifies the tax item of the payment and the local government to which the payment is to be made based on the information stored in the information code, the tax item code set by the first setting unit, and the local government code set by the third setting unit, and creates the receipt record including information indicating the identified tax item and information indicating the identified local government. The information processing system according to claim 8 .

10. The cash processing device is configured such that the information stored in the information code is When the tax item code set by the first setting unit and the local government code set by the third setting unit correspond to each other, the payment of the payment is executed; rejecting the payment of the payment if the tax item code set by the first setting unit and the local government code set by the third setting unit do not correspond to each other; The information processing system according to claim 9 .

11. The local government corresponding to the location where the cash processing device is installed is different from the local government to which the payment is made. The information processing system according to claim 8 .

12. 1. A computer-implemented information processing method, comprising: Setting a tax item code indicating a tax item of a local government for the tax items of a plurality of the local governments; Setting setting information for a plurality of said local governments to be referenced when creating a payment history file showing the payment history of said payments; Creating the collection history file for the selected municipality and tax item based on the collection records of the payments for the selected municipality and tax item, the tax item code corresponding to the selected municipality and tax item, and the setting information for the selected municipality; An information processing method including:

13. Computer, a first setting unit that sets tax item codes indicating tax items of a local government for the tax items of a plurality of the local governments; a second setting unit that sets setting information for a plurality of said local governments to be referenced when creating a payment history file showing the payment history of said payments; a creation unit that creates the collection history file for the selected local government and tax item based on the collection records of the payments for the selected local government and tax item, the tax item code corresponding to the selected local government and tax item, and the setting information for the selected local government; A program to function as a

Images