Program, method, information processing device, and system

Abstract

To solve a problem with the inability to present information relating to the collection of credits related to cancellation fees.SOLUTION: A program to be executed by a computer including a processor and a memory unit, the program causing the processor to execute: a cancellation information acquisition step of acquiring, for reservation information relating to multiple reservations, cancellation information indicating that the reservation information has been canceled; a billing information acquisition step of acquiring billing information indicating that a cancellation fee has been charged for the reservation information, based on the cancellation information acquired in the cancellation information acquisition step; and a collection presentation step of presenting collection information relating to collection of a claim concerning cancellation fees, based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step.SELECTED DRAWING: Figure 15

Description

[Technical Field]

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

[0002] BACKGROUND ART Techniques for making reservations for facilities such as accommodations and restaurants online are known. Patent Document 1 discloses a technique for reflecting a change in a user's behavior resulting from an operation performed on the user in an estimation of the user score. Patent Document 2 discloses a technology that enables provision of appropriate services relating to the purchase of receivables. Patent Document 3 discloses an information processing device, an information processing method, and an information processing program that appropriately estimate a credit score based on the handling of counterfeit goods. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2023-148438 [Patent Document 2] Japanese Patent Publication No. 2023-075565 [Patent Document 3] Japanese Patent Publication No. 2023-140951 Summary of the Invention [Problem to be solved by the invention]

[0004] There is an issue in that information regarding the collection of receivables related to cancellation fees is not provided. Therefore, the present disclosure has been made to solve the above problem, and its purpose is to provide a technology that presents information regarding the collection of claims related to cancellation fees. [Means for solving the problem]

[0005] A program to be executed by a computer having a processor and a memory unit, the program executing the following steps: a cancellation information acquisition step in which the processor acquires cancellation information indicating that reservation information relating to multiple reservations has been canceled; a billing information acquisition step in which, based on the cancellation information acquired in the cancellation information acquisition step, it acquires billing information indicating that a cancellation fee has been charged for the reservation information; and a collection presentation step in which it presents collection information regarding the collection of a debt relating to the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step. [Effects of the Invention]

[0006] According to the present disclosure, information regarding the collection of receivables related to cancellation fees can be presented. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 2 is a block diagram showing the functional configuration of the system 1. [Figure 2] FIG. 2 is a block diagram showing the functional configuration of the server 10. [Figure 3] FIG. 2 is a block diagram showing the functional configuration of a user terminal 20. [Figure 4] FIG. 10 is a diagram showing the data structure of a user table 1012. [Figure 5] FIG. 10 is a diagram showing the data structure of a reservation table 1013. [Figure 6] FIG. 10 is a diagram showing the data structure of a billing table 1014. [Figure 7] 10 is a flowchart showing the operation of a reservation acquisition process. [Figure 8] 10 is a flowchart showing the operation of a reservation presentation process. [Figure 9] 10 is a flowchart showing the operation of billing processing. [Figure 10] 10 is a flowchart showing the operation of a debt processing; [Figure 11]10 is a screen example showing the operation of a reservation presentation process. [Figure 12] 10 is a screen example showing a linkage content page in billing processing. [Figure 13] 10 is a screen example showing a billing creation page in billing processing. [Figure 14] 10 is an example of a screen showing a message sent to the customer's information processing terminal. [Figure 15] 10 is a screen example showing a debt processing page in debt processing. [Figure 16] 10 is a screen example showing a debt details page in debt processing. [Figure 17] FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all drawings describing the embodiments, common components are designated by the same reference numerals, and repeated description will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each drawing is a schematic diagram and is not necessarily a precise illustration.

[0009] <System 1 Configuration> The system 1 in the present disclosure is an information processing system for providing an information processing service for efficiently making facility reservations and charging cancellation fees for facility reservations. The system 1 includes information processing devices, such as a PMS 501, an OTA 511, a site controller 521, a server 10, and a user terminal 20, which are connected via a network N. FIG. 1 is a block diagram showing the functional configuration of the system 1. As shown in FIG. FIG. 2 is a block diagram showing the functional configuration of the server 10. As shown in FIG. FIG. 3 is a block diagram showing the functional configuration of the user terminal 20. As shown in FIG.

[0010] Each information processing device is composed of a computer having an arithmetic unit and a storage unit. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. Regarding each of PMS501, OTA511, site controller 521, server 10, and user terminal 20, descriptions overlapping with the basic hardware configuration of the computer and the basic functional configuration of the computer described later will be omitted.

[0011] <Configuration of PMS501> PMS501 (Property Management System) is a system that provides information processing services such as reservation management functions, front desk management functions, customer management functions, data aggregation, and analysis functions as an in-house system of a facility. For example, PMS501 includes innto, HOTEL SMART, Airhost PMS, etc. Usually, it is common for a facility to contract with and use one PMS system as an in-house system.

[0012] <Configuration of OTA511> OTA511 (Online Travel Agency) is a system that provides a reservation management service for accepting facility reservations from customers on the Internet. A plurality of operators provide different services according to reservation contents such as accommodation and restaurant reservations. For example, OTA511 related to accommodation facilities includes jalan, Rakuten Travel, ichibiru.com, etc. Normally, it is common for a facility to contract with and use one OTA.

[0013] <Configuration of site controller 521> The site controller 521 is a system that provides information processing services that centrally manage facility reservations received from customers via multiple OTAs. Facilities typically use multiple different OTAs to improve their utilization rates. However, performing tasks such as facility inventory and fee management, reservation management, and fee structure setting for each individual OTA creates cumbersome work and is prone to errors such as double bookings. By using the site controller 521, facilities can efficiently manage reservations. Examples of site controllers include Temachirazu, TL Lincoln, and Rakutsu with. It is common for facilities to sign contracts with and use multiple OTA systems. The PMS 501, OTA 511, and site controller 521 are generally provided as cloud services via the Internet. Employees of the facility can receive the services by accessing each system via the Internet. Additionally, customers who wish to use facilities can make reservations via OTAs. Information about customer facility reservations stored in the OTA is acquired by the site controller and reflected in the PMS. Information about the same facility reservation is stored in the PMS, OTA, site controller, etc. Information about the same facility reservation is linked by a unique number called a reservation number, which will be described later.

[0014] <Server 10 configuration> The server 10 is an information processing device that provides an information processing service for efficiently charging cancellation fees for facility reservations, etc. Specifically, the server 10 is connected to the Internet. It is possible to obtain reservation information related to facility reservations made for the provision of accommodations, restaurants, and other optional services from multiple PMSs 501, 502, etc., multiple OTAs 511, 512, etc., multiple site controllers 521, 522, etc. (details will be described later) that are also connected to the Internet. In this disclosure, a reservation management service for accommodations, restaurants, etc. will be described as an example, but the present disclosure is also applicable to reservation management services for skill sharing, lessons, etc. that do not require facilities. Specifically, the server 10 can access API (Application Programming Interface) endpoints provided by reservation management services such as multiple PMSs 501, 502, etc., multiple OTAs 511, 512, etc., and multiple site controllers 521, 522, etc., upload data such as CSV files obtained from the reservation management services by employees managing the facilities, and automatically or manually obtain various information from the reservation management services by scraping using robots such as web crawlers. The server 10 includes a storage unit 101 and a control unit 104 .

[0015] <Configuration of the storage unit 101 of the server 10> The storage unit 101 of the server 10 includes an application program 1011 , a user table 1012 , a reservation table 1013 , and a billing table 1014 .

[0016] The application program 1011 is a program for causing the control unit 104 of the server 10 to function as each functional unit. Application programs 1011 include applications such as a web browser application.

[0017] The user table 1012 is a table that stores and manages information on member users (hereinafter referred to as users) who use the service. In the present disclosure, employees who manage and operate facilities, etc. are users of the information processing service according to the present disclosure. When a user registers to use the service, the user's information is stored in a new record in the user table 1012. This allows the user to use the service according to the present disclosure. The user table 1012 is a table having a user ID as a primary key and columns of user ID, user name, user data, service data, and linked reservation service. FIG. 4 is a diagram showing the data structure of the user table 1012. As shown in FIG.

[0018] The user ID is an item that stores user identification information for identifying a user. The user identification information is an item that is set with a unique value for each user. The user name is an item for storing the name of the user. The user name may be set to any character string such as a nickname instead of a name. User data is an item that stores information about a user. User data includes information such as the user's name, address, and contact details. The user data may include information about the facility that the user provides to the customer, such as the facility name, facility address, and facility contact information. The service data is an item for storing information about services that a user provides to a customer. The service data includes information such as the type of service the user provides to the customer, the content of the service, the service fee, and the cancellation policy in case of cancellation. The type of service includes information that specifies the type of service, such as accommodation, food and drink, transportation (airplane, train, bus, etc.), lessons, etc. Multiple types of services may be included. The service content includes information that identifies the service content, such as accommodation plans, dining menus, courses, transportation routes, seat types, etc. It may also include the content of multiple services. The service fee includes a fee for each service content. The service fee may be set in multiple amounts depending on the reservation date and time (weekdays, holidays) and time period (early morning, daytime, nighttime). The reservation date and time is the date and time when the service is provided. The cancellation policy includes information that specifies the obligations that apply to customers when they cancel a reservation. For example, if a customer cancels a reservation and the reservation date and time meets certain time requirements (for example, if the customer cancels within a certain period of time after the reservation date and time), the customer is obligated to pay the user part or all of the service fee as a cancellation fee. The service data may include information about facilities that the user provides to customers, such as the facility name, facility address, and facility contact information. The linked reservation service is an item that stores information that identifies the reservation management service, such as a PMS, site controller, or OTA, that the user is using. Specifically, the item stores reservation management service identification information (reservation management service ID) for identifying the reservation management service that the user is using. The user can edit the content of the linked reservation service on a management screen (not shown) or the like provided by the server 10.

[0019] The reservation table 1013 is a table for storing and managing information relating to facility reservations (reservation information). The reservation table 1013 is a table having a reservation ID as a primary key and columns of reservation ID, reservation management service ID, user ID, reservation number, facility reservation data, customer data, cancellation data, bond data, priority, and update date and time. FIG. 5 is a diagram showing the data structure of the reservation table 1013.

[0020] The reservation ID is an item that stores reservation identification information for identifying a reservation. The reservation ID is an item in which a unique value is set for each reservation information. The reservation management service ID is an item for storing service identification information for identifying the reservation management service. Specifically, the service identification information is a character string for identifying each of the multiple PMSs 501, 502, . . . , the multiple OTAs 511, 512, . . . , and the multiple site controllers 521, 522, . . . The user ID is an item for storing user identification information for identifying a user. The reservation number is an item for storing a number for identifying reservation information. The facility reservation data is an item that stores information about the contents of the facility reservation. The facility reservation information includes information such as the planned date and time of use of the facility, the desired use plan, the number of users, and the use fee. The customer data is an item for storing information (customer information) about a customer who has made a facility reservation. The customer information includes the customer's name, address, and contact information (phone number, email address, and SNS ID). The customer information may also include information about customer attributes such as gender and age. The cancellation data is an item for storing cancellation information for reservation information. The cancellation information includes information indicating that the reservation information identified by the reservation identification information has been canceled, the cancellation date and time, the applicable cancellation policy, the cancellation fee, and the like. The debt data is an item for storing information (debt information) indicating the possibility of collecting debt for canceled reservation information. Specifically, the debt data includes at least one of the following: collection status, discount rate, debt value, debtor information, legal action history, payment terms, debt collection agency information, and accounting procedures. Collection status: Information indicating the collection status of the receivable. For example, the collection status may include information such as "Cancellation fees have been charged more than 10 times, and no payment has been received in the four months since the last payment" or "The address of the cancellation fee invoice email has been attached." The collection status may also be calculated based on the following information: · Discount rate for receivables: The discount rate for receivables calculated based on collectibility, risk, etc. · Receivables value (present value): Information showing the current value, amount, etc. of the receivables. Usually, the present value (receivables value) of the receivables is calculated by multiplying the cancellation fee by the receivables discount rate. Debtor information: Information such as the debtor's (reservation holder, reservation user) contact information, payment history, creditworthiness regarding payment, credit score, etc. Legal Action History: Information showing legal actions taken to collect debts, such as sending notices or filing lawsuits. Payment terms: Information indicating payment deadlines, possibility of installment payments, late payment interest rates, etc. - Information about debt collection agents: Information about agents who act as agents for debt collection. For example, the name, address, contact information, etc. of the agent. Accounting treatment: Information indicating how the receivables are treated in the accounting books, for example, how the receivables are treated in the accounting books, such as impairment treatment of the receivables. The priority is an item for storing information relating to the priority of reservation information. The update date and time is an item for storing the update date and time of the reservation information.

[0021] The billing table 1014 is a table for storing and managing information (billing information) relating to billing of cancellation fees for reservation information. The billing table 1014 is a table having columns for reservation ID, billing date and time, billing data, billing amount, and payment data. FIG. 6 is a diagram showing the data structure of the billing table 1014.

[0022] The reservation ID is an item for storing reservation identification information for identifying reservation information that has been canceled by a customer. The billing date and time is an item for storing the date and time when a message invoicing the customer for the cancellation fee was sent by the billing process described below. The billing data is an item that stores information regarding the billing of cancellation fees. The billing data includes character string information such as one or more billing dates and times, notification means (telephone, email, SMS, etc.) for each billing date and time, and the content of the notification message for each billing date and time. The billing data may also include the content of a message requesting a cancellation fee. The billing amount is an item that stores information about the cancellation fee. The payment data is an item for storing information when a cancellation fee is paid by a customer. The deposit data includes information such as the date and time of deposit and the amount of deposit.

[0023] <Configuration of the control unit 104 of the server 10> The control unit 104 of the server 10 includes a user registration control unit 1041, an acquisition unit 1042, a presentation unit 1043, a billing unit 1044, and a credit unit 1045. The control unit 104 executes an application program 1011 stored in the memory unit 101, thereby realizing each functional unit.

[0024] The user registration control unit 1041 performs processing to store information about users who wish to use the service according to the present disclosure in the user table 1012. The information stored in the user table 1012 is generated when a user opens a web page operated by a service provider from any information processing terminal, enters information into a predetermined input form, and transmits the information to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, completing the user registration. This allows the user stored in the user table 1012 to use the service. Before the user registration control unit 1041 registers the user information in the user table 1012, the service provider may conduct a predetermined examination to restrict whether or not the user is permitted to use the service. The user ID may be any character string or number that can identify the user, any character string or number desired by the user, or may be automatically set by the user registration control unit 1041.

[0025] The acquisition unit 1042 executes a reservation acquisition process, the details of which will be described later.

[0026] The presentation unit 1043 executes a reservation presentation process, the details of which will be described later.

[0027] The billing unit 1044 executes billing processing, the details of which will be described later.

[0028] The credit section 1045 executes credit processing, the details of which will be described later.

[0029] <Configuration of User Terminal 20> The user terminal 20 is an information processing device operated by a user who uses a service. The user terminal 20 may be, for example, a mobile terminal such as a smartphone or tablet, a stationary personal computer (PC) or a laptop PC, or a wearable terminal such as a head mounted display (HMD) or a wristwatch terminal. The user terminal 20 includes a storage unit 201 , a control unit 204 , an input device 206 , and an output device 208 .

[0030] <Configuration of the storage unit 201 of the user terminal 20> The storage unit 201 of the user terminal 20 includes a user ID 2011 and an application program 2012 .

[0031] The user ID 2011 is the user's account ID. The user transmits the user ID 2011 from the user terminal 20 to the server 10. The server 10 identifies the user based on the user ID 2011 and provides the user with the service according to the present disclosure. The user ID 2011 includes information such as a session ID temporarily assigned by the server 10 to identify the user using the user terminal 20.

[0032] The application program 2012 may be stored in advance in the storage unit 201, or may be configured to be downloaded from a web server or the like operated by a service provider via a communication IF. The application programs 2012 include applications such as a web browser application. The application program 2012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored on the user terminal 20.

[0033] <Configuration of the control unit 204 of the user terminal 20> The control unit 204 of the user terminal 20 includes an input control unit 2041 and an output control unit 2042. The control unit 204 executes an application program 2012 stored in the storage unit 201, thereby realizing each functional unit.

[0034] <Configuration of the input device 206 of the user terminal 20> The input device 206 of the user terminal 20 includes a camera 2061 , a microphone 2062 , a position information sensor 2063 , a motion sensor 2064 , and a touch device 2065 .

[0035] <Configuration of the output device 208 of the user terminal 20> The output device 208 of the user terminal 20 includes a display 2081 and a speaker 2082 .

[0036] <System 1 Operation> Each process of the system 1 will be explained below. FIG. 7 is a flowchart showing the operation of the reservation acquisition process. FIG. 8 is a flowchart showing the operation of the reservation presentation process. FIG. 9 is a flowchart showing the operation of the billing process. FIG. 10 is a flowchart showing the operation of the debt processing. FIG. 11 is an example of a screen showing the operation of the reservation presentation process. FIG. 12 is an example of a screen showing a linkage content page for billing processing. FIG. 13 is a screen example showing a billing creation page in billing processing. FIG. 14 is an example of a screen showing a message sent to the customer's information processing terminal. FIG. 15 is an example of a screen showing a debt processing page in debt processing. FIG. 16 is an example of a screen showing a debt details page in debt processing.

[0037] <Reservation acquisition process> The reservation acquisition process is a process for acquiring reservation information related to a reservation from the reservation management service.

[0038] <Overview of reservation acquisition process> The reservation acquisition process is a series of processes that identify user information, acquire facility reservation data, customer data, cancellation data, etc. from the reservation management service used by the user, and store the reservation information. Specifically, the acquisition unit 1042 of the server 10 acquires reservation information for each user at each predetermined period from an external reservation management service used by the user. The acquisition unit 1042 of the server 10 stores the acquired reservation information in the reservation table 1013 of the server 10 in association with user identification information for identifying the user. The acquisition unit 1042 of the server 10 periodically executes the reservation acquisition process. The reservation acquisition process may be configured to be executed in response to an input operation by a user using the service. Alternatively, the reservation acquisition process may be configured to be executed automatically prior to the reservation presentation process and billing process described later.

[0039] The reservation acquisition process enables the reservation number, facility reservation data, customer data, and cancellation data acquired for each user from multiple reservation management services operated by different external businesses to be associated and stored in reservation table 1013. This allows reservation information that is stored in a distributed manner across multiple reservation management services operated by different external businesses to be consolidated in reservation table 1013 and managed centrally. The multiple reservation management services operated by different external operators include at least a property management system, a site controller, and an online travel agent system.

[0040] <Details of reservation acquisition process> The reservation acquisition process will be described in detail below.

[0041] In step S101, the acquisition unit 1042 of the server 10 acquires user information including a user ID, user data, service data, and linked reservation services by searching the user table 1012. The acquisition unit 1042 of the server 10 executes the processes from step S102 onward, which will be described below, for each piece of acquired user information. The acquisition unit 1042 of the server 10 may change the frequency at which the reservation acquisition process is executed depending on the acquired user data and service data. For example, the acquisition unit 1042 of the server 10 calculates a priority depending on the user data and service data, and changes the frequency at which the reservation acquisition process is executed based on the priority. For example, the acquisition unit 1042 of the server 10 executes the external reservation acquisition process at shorter intervals as the priority increases. This makes it possible to better maintain synchronization between the reservation information stored in the external reservation management service and the reservation information stored in the reservation table 1013 of the server 10. In this disclosure, for simplicity, the reservation acquisition process for one specific user (identified by a specific user ID) will be described below. Note that the processes from step S102 onwards are also executed for other user information stored in the user table 1012.

[0042] In step S102, the acquisition unit 1042 of the server 10 executes a reservation acquisition step of acquiring reservation information relating to a plurality of reservations from a plurality of reservation management services operated by different external businesses. Specifically, the acquisition unit 1042 of the server 10 acquires the reservation management service ID of the reservation management service used by the user, which is included in the items of the linked reservation service acquired in step S101. Specifically, the acquisition unit 1042 acquires and identifies a character string for identifying the reservation management service, such as a PMS, site controller, or OTA, that the user uses (contracts with) to manage their own facility reservations. Typically, one user will have contracts with one PMS, one site controller, and multiple OTAs. The acquisition unit 1042 of the server 10 refers to a database (not shown) or the like based on the acquired reservation management service identification information to identify an API endpoint for accessing each reservation management service. The acquisition unit 1042 of the server 10 sends a request to the acquired API endpoint to acquire reservation information including a specific user ID or a user ID for each reservation management service identified based on the specific user ID. The reservation management service sends a reservation number, facility reservation data, customer data, and cancellation data in response to the request. This allows the acquisition unit 1042 of the server 10 to acquire the reservation number, facility reservation data, customer data, and cancellation data from the external reservation management service for each reservation management service ID. It is sufficient for the acquisition unit 1042 of the server 10 to be able to acquire reservation information related to multiple reservations from multiple reservation management services operated by different external businesses, such as multiple PMSs, multiple site controllers, or multiple OTAs. It is not necessary for the acquisition unit 1042 to be able to simultaneously acquire reservation information related to multiple reservations from multiple reservation management services operated by all types of different external businesses, such as multiple PMSs, multiple site controllers, and multiple OTAs. It is sufficient for the acquisition unit 1042 to be able to acquire reservation information from any two or more reservation management services.

[0043] The reservation information acquired in the reservation acquisition step may include information on the reservation amount, reservation date and time, and cancellation date and time regarding the reservation. Specifically, the facility reservation data acquired by the acquisition unit 1042 of the server 10 includes information such as the reservation fee as the reservation amount and the reservation date and time. Furthermore, the cancellation data acquired by the acquisition unit 1042 of the server 10 includes information on the cancellation date and time. Specifically, in reservation management services such as OTAs, customers can cancel past reservations by accessing the OTAs. In such cases, the OTAs store and accumulate information related to the cancellation as cancellation data. The acquisition unit 1042 of the server 10 can acquire the cancellation data stored and accumulated in the OTAs. Note that cancellation data is not necessarily input by the customer; a user may directly input the cancellation data into a PMS, site controller, OTA, etc. upon receiving a customer's contact. Furthermore, in the case of a cancellation due to a no-show, the user may also directly input the cancellation data into a PMS, site controller, OTA, etc. The user may also edit the cancellation data in the reservation table 1013 by operating the input device 206 of the user terminal 20 to access the server 10 according to the present disclosure. For example, in the case of a no-show, the user operates the input device 206 of the user terminal 20 to input cancellation information into the cancellation data field included in the record of reservation information related to the no-show in the reservation table 1013. This allows the cancellation procedure to be carried out for the reservation information reserved by the customer.

[0044] In step S102, the acquisition unit 1042 of the server 10 executes a terms acquisition step of acquiring a cancellation policy that defines cancellation conditions for the plurality of reservation information acquired in the reservation acquisition step. Specifically, the cancellation data acquired by the acquisition unit 1042 of the server 10 includes a cancellation policy that defines the cancellation conditions that are applied when facility reservation data is canceled. The acquisition unit 1042 of the server 10 does not need to acquire a cancellation policy for each reservation management service, but may acquire it from a specified reservation management service such as a PMS or site controller, and use the acquired cancellation policy for other reservation management services such as OTAs. The acquisition unit 1042 of the server 10 may acquire the cancellation policy from the cancellation policy included in the service data acquired in step S101. In this case, the user accesses the user management screen provided by the server 10 according to the present disclosure in advance, inputs and edits the cancellation policy of the facility that the user manages, and stores it in advance in the service data item of the user table 1012. Furthermore, the user may input and edit the cancellation policy by operating the input device 206 of the user terminal 20 to edit the cancellation data for each reservation information.

[0045] In this disclosure, a configuration in which facility reservation data, customer data, and cancellation data are obtained from API endpoints provided by each reservation management service, such as a PMS, a site controller, and multiple OTAs, has been disclosed as an example, but this is not limited to this. For example, facility reservation data, customer data, and cancellation data may be obtained from a reservation management service, such as a PMS or multiple OTAs, via an API endpoint of a site controller. This case also falls under the case in which reservation information regarding multiple reservations is obtained from multiple reservation management services operated by different external businesses. Furthermore, the user operates a web browser application or the like using the input device 206 of the user terminal 20 to access each website provided by the PMS, the site controller, multiple OTAs, etc., and downloads files such as CSV files that store reservation numbers, facility reservation data, customer data, and cancellation data. The user may also operate the input device 206 of the user terminal 20 to transmit the downloaded files to the server 10 by uploading them from an upload page (not shown) provided by the server 10. In this case as well, the acquisition unit 1042 of the server 10 can acquire facility reservation data, customer data, and cancellation data from each reservation management service such as the PMS, the site controller, multiple OTAs, etc. Alternatively, the acquisition unit 1042 of the server 10 may be configured to acquire facility reservation data, customer data, and cancellation data from each reservation management service such as a PMS, a site controller, or multiple OTAs by executing a web scraping program stored in the storage unit 101 of the server 10 without going through an API endpoint. Also, the user may operate the input device 206 of the user terminal 20 to acquire the reservation number, facility reservation data, customer data, cancellation data, etc. in the reservation table 1013.

[0046] In step S103, the acquisition unit 1042 of the server 10 stores the reservation management service ID, the specific user ID identified in step S101, the reservation number acquired from the reservation management service identified by the reservation management service ID, facility reservation data, customer data, and cancellation data in the reservation management service ID, user ID, facility reservation data, customer data, and cancellation data fields, respectively, of a new record in the reservation table 1013. At this time, the reservation ID is automatically assigned. The acquisition unit 1042 of the server 10 may store the priority determined based on the reservation management service ID in the priority field of the newly created record. For example, in the present disclosure, the priority is assigned in the order of PMS, site controller, and OTA. Note that different priorities may be assigned to multiple PMSs, multiple site controllers, and multiple OTAs. Even in this case, it is preferable that the priority order of PMS, site controller, and OTA does not change. This is because the higher the priority of a reservation management service, the more reliable the reservation information stored therein.

[0047] Although the present disclosure has been described as an example of acquiring all reservation information from an external reservation management service, the acquisition unit 1042 of the server 10 may execute processing to acquire only reservation information associated with cancellation data. Specifically, the acquisition unit 1042 of the server 10 may be configured to acquire only reservation information for which cancellations have been accepted from customers and reservation information for no-shows who do not actually use the service from the external reservation management service, and not acquire other reservation information. This allows only reservation information for which a cancellation fee is to be charged to the customer to be acquired, thereby reducing communication traffic.

[0048] <Reservation presentation process> The reservation presentation process is a process of presenting the reservation information acquired by the reservation acquisition process to the user.

[0049] <Reservation presentation process overview> The reservation presentation process is a series of processes that displays a reservation presentation screen to the user, and when the user enters their user ID, retrieves the reservation information managed by that user and displays a list of the reservation information.

[0050] <Reservation presentation process details> The reservation presentation process will be described in detail below.

[0051] In step S301, the user operates the input device 206 of the user terminal 20 to execute a browser application or the like, and opens the reservation presentation page D1 by inputting the URL of a web page (reservation presentation page) for executing the reservation presentation process. The control unit 204 of the user terminal 20 transmits a request including the user ID 2011 for opening the reservation presentation page to the server 10.

[0052] In step S302, upon receiving the request, the presentation unit 1043 of the server 10 searches the reservation ID item in the reservation table 1013 based on the user ID 2011 to obtain multiple pieces of reservation information.

[0053] In step S303, the presenting unit 1043 of the server 10 executes a list presenting step of presenting a list of the plurality of reservation information acquired in the reservation acquisition step. Specifically, the presentation unit 1043 of the server 10 generates a reservation presentation page based on the acquired reservation information and transmits it to the user terminal 20. The control unit 204 of the user terminal 20 displays and presents the reservation presentation page on the display 2081 of the user terminal 20. The presentation unit 1043 of the server 10 may be configured to list only reservation information that is associated with cancellation data among the reservation information obtained from an external reservation management service on the reservation presentation page, and not display reservation information that is not associated with cancellation data on the reservation presentation page.

[0054] 11 is an example of a reservation presentation screen in the reservation presentation process. A reservation presentation page D1 is displayed on the display 2081 of the user terminal 20. The reservation presentation page D1 includes a reservation presentation screen D11. The reservation presentation screen D11 includes a request button D110, a list D111 of reservation management services to which the user has subscribed, the name D112 of the currently displayed reservation management service, and reservation information D121 and D122 acquired from the reservation management service named D112 by the reservation acquisition process. The reservation information D121 and D122 include request buttons D1211 and D1221, and cancellation fees D1212 and D1222, respectively.

[0055] The user can execute the billing process by operating the input device 206 of the user terminal 20 and pressing the billing button D110. At this time, the user manually executes the billing process by operating the input device 206 of the user terminal 20 without using the information stored in the reservation table 1013. The details of the billing process will be described later.

[0056] The reservation management service list D111 is created by removing duplicate reservation management service IDs from the acquired reservation information, and displaying a list of reservation management service names by referencing a table or the like (not shown). The user operates the input device 206 of the user terminal 20 to select a specific reservation management service for which they wish to display reservation information from the list D111 of reservation management services. The control unit 204 of the user terminal 20 presents the name D112 of the selected reservation management service on the reservation presentation page D1 in response to the user's operation of the input device 206 of the user terminal 20. The control unit 204 of the user terminal 20 also presents a list of records from the acquired reservation information that include the selected specific reservation management service ID in reservation information D121, D122. Furthermore, the control unit 204 of the user terminal 20 transmits a request to the server 10 to acquire billing information including the reservation IDs of the reservation information D121 and D122. The presentation unit 1043 of the server 10 searches the reservation ID item in the billing table 1014 based on the reservation ID included in the request, and acquires the billing information associated with the reservation information D121 and D122. The presentation unit 1043 of the server 10 transmits the acquired billing information to the user terminal 20. The control unit 204 of the user terminal 20 changes the display mode of the billing buttons D1211 and D1221 according to the acquired billing information. Specifically, if there is no billing information corresponding to the reservation information, the billing button D1211 is labeled "Claim for this reservation" and is presented in a manner that can be pressed by the user. If there is billing information corresponding to the reservation information, the billing button D1221 is labeled "Claimed" and is presented in a manner that cannot be pressed by the user. Note that even if there is billing information corresponding to the reservation information, it is possible to perform billing processing again, so the button color may be an inconspicuous color such as gray and presented in a manner that can be pressed by the user.

[0057] The user can execute billing processing for the reservation information D121 associated with the billing button D1211 by operating the input device 206 of the user terminal 20 to press the billing button D1211. Details of the billing processing will be described later.

[0058] In step S303, the presentation unit 1043 of the server 10 executes a calculation step of calculating cancellation fees for the multiple reservation information based on the reservation amount, reservation date and time, cancellation date and time, and cancellation policy of the multiple reservation information selected in the reservation acquisition step. Specifically, the presentation unit 1043 of the server 10 may calculate a cancellation fee for each piece of reservation information based on the facility reservation data and cancellation data included in the acquired reservation information. For example, the presentation unit 1043 of the server 10 compares the reservation date and time with the cancellation date and time based on the usage fee included in the facility reservation data, and calculates a cancellation fee if a cancellation fee specified in the cancellation policy applies. If the cancellation policy stipulates a 100% cancellation fee for cancellation on the day of the reservation, a 70% cancellation fee for cancellation the day before, and a 50% cancellation fee for cancellation within three days before, and if a customer cancels on the day of the reservation or does not show up to use the service, the usage fee included in the facility reservation data is calculated as the cancellation fee. If a customer cancels the day before the reservation, 70% of the usage fee included in the facility reservation data is calculated as the cancellation fee. If a customer cancels within three days before the reservation, 50% of the usage fee included in the facility reservation data is calculated as the cancellation fee. The acquisition unit 1042 of the server 10 transmits the cancellation fees to the user terminal 20. The control unit 204 of the user terminal 20 associates the received cancellation fees D1212, D1222 with the reservation information for which they are to be calculated, and displays them as a list in the reservation information D121, D122.

[0059] In step S303, the presentation unit 1043 of the server 10 executes a candidate presentation step of presenting reservation information candidates that are candidates for creating a message requesting a cancellation fee in the creation step, based on the cancellation fee calculated in the calculation step. Specifically, the control unit 204 of the user terminal 20 may display reservation information for which a cancellation fee is calculated to be zero yen or more on the display 2081 of the user terminal 20 as reservation information candidates for executing the billing process, which will be described later. For example, the control unit 204 of the user terminal 20 highlights the billing buttons D1211 and D1221 to display them on the display 2081 of the user terminal 20 as reservation information candidates for executing the billing process. Alternatively, the control unit 204 of the user terminal 20 may present the reservation information candidates by displaying them in a pop-up dialog box or the like that displays a list of reservation information candidates on the display 2081 of the user terminal 20. This allows the user to execute the billing process without overlooking customers who will incur cancellation fees. The control unit 204 of the user terminal 20 may highlight reservation information candidates whose cancellation fee is equal to or greater than a predetermined amount in an identifiable manner. Specifically, the background of reservation information D121 whose cancellation fee is equal to or greater than a predetermined amount may be drawn on the reservation presentation screen D11 in an identifiable manner, such as a background color, text color, font, or drawing style that is different from that of other reservation information D122. For example, the control unit 204 of the user terminal 20 may display reservation information candidates whose cancellation fee is equal to or greater than 2,000 yen in an identifiable manner. Alternatively, the control unit 204 of the user terminal 20 may draw the reservation information candidates on the reservation presentation screen D11 in descending order of the amount of the cancellation fee. This allows the user to execute billing processing in order of cancellation fees even when there are many reservation information candidates. Reservation information candidates with large cancellation fees can be given priority over reservation information candidates with small cancellation fees. From among the multiple reservation information acquired, the user can identify customers or reservation information for which to create a message requesting a cancellation fee, taking cancellation fees into consideration.

[0060] In step S303, the listing step may include listing the reservation information acquired from a plurality of reservation management services operated by different external businesses in a manner that allows overlapping reservation information to be identified. Specifically, the acquisition unit 1042 of the server 10 identifies, among the multiple pieces of reservation information acquired from the reservation table 1013 in step S302, records of different reservation information having the same reservation number as duplicate reservation information. For example, the acquisition unit 1042 of the server 10 counts the number of reservation numbers included in the multiple pieces of reservation information, and identifies reservation information with a reservation number whose count is 2 or more as duplicate reservation information. Specifically, in the present disclosure, it is assumed that different pieces of reservation information having the same reservation number are acquired from the PMS, the site controller, and multiple OTAs, and stored in the reservation table 1013. The acquisition unit 1042 of the server 10 draws the background of the overlapping reservation information D121 on the reservation presentation screen D11 in a distinguishable manner, such as a background color, text color, font, or drawing style, that is different from that of the other reservation information D122. This allows users to easily identify duplicate reservation information when a list of reservation information for the same reservation is displayed that is stored in duplicate across multiple reservation management services operated by external businesses, such as PMSs, site controllers, and OTAs. For example, this makes it possible to avoid sending messages to customers requesting duplicate cancellation fees based on duplicate reservation information.

[0061] In step S303, a listing step is executed to list reservation information acquired from a plurality of reservation management services operated by different external businesses, excluding duplicate reservation information. Specifically, the acquisition unit 1042 of the server 10 excludes one piece of reservation information from among the multiple pieces of reservation information acquired from the reservation table 1013 in step S302, and other pieces of reservation information having the same reservation number, and presents the reservation information D121 and D122 in a list on the reservation presentation screen D11. This allows users to filter out duplicate reservation information when viewing a list of reservation information for the same reservation that is stored in multiple reservation management services operated by external businesses, such as PMS, site controllers, and OTAs. For example, this can prevent messages from being sent to customers requesting duplicate cancellation fees based on duplicate reservation information.

[0062] The list presentation step is a step of presenting only one piece of reservation information identified according to the reservation management service from which the reservation information was obtained from among the multiple pieces of overlapping reservation information. Specifically, among the multiple pieces of overlapping reservation information, only one piece of reservation information with the highest priority is presented according to the order of priority of the property management system, the site controller, and the online travel agent system. For example, assume that the acquisition unit 1042 of the server 10 acquires multiple reservation information pieces with overlapping reservation numbers, each of which includes a reservation management service ID that identifies a travel management service related to a PMS, a site controller, or an OTA as the reservation management service ID. In this case, the acquisition unit 1042 of the server 10 deletes reservation information pieces with reservation management service IDs that are not related to a PMS and that are related to a site controller or an OTA. The acquisition unit 1042 of the server 10 presents a list of reservation information pieces D121 and D122 with reservation management service IDs related to a PMS on the reservation presentation screen D11. This allows the user to see only one specific reservation information according to the priority of multiple reservation management services operated by external businesses. The customer can create a message requesting a cancellation fee based on the latest reservation information obtained.

[0063] In step S303, the listing step may include a step of listing, from among the plurality of reservation information, reservation information for which the customer who made the reservation has paid a cancellation fee, excluding such reservation information. Specifically, the acquisition unit 1042 of the server 10 searches the reservation ID field in the billing table 1014 based on the reservation ID included in the multiple pieces of reservation information acquired from the reservation table 1013 in step S302, and acquires the payment data. The acquisition unit 1042 of the server 10 excludes, from the multiple pieces of reservation information, records in which information indicating that a cancellation fee has been paid by the customer is stored in the payment data, and presents a list of the reservation information D121 and D122 on the reservation presentation screen D11. This allows you to display a list of reservations that exclude reservations for which customers have paid cancellation fees, preventing you from sending a message requesting a cancellation fee for reservations for which a cancellation fee has already been paid.

[0064] In step S303, the listing step may include a step of excluding all of the duplicate reservation information from the reservation information obtained from multiple reservation management services operated by different external businesses and listing the duplicate reservation information if a cancellation fee has been paid by the customer for at least one of the duplicate reservation information. Specifically, among the multiple reservation information pieces acquired from the reservation table 1013 in step S302, if the acquisition unit 1042 of the server 10 finds that one of the multiple overlapping reservation information pieces with the same reservation number contains information indicating that the customer has paid a cancellation fee in the payment data of the billing information corresponding to the reservation ID of that reservation information, the acquisition unit 1042 of the server 10 also excludes that record and presents a list of the reservation information pieces D121 and D122 on the reservation presentation screen D11. This allows the user to easily identify duplicate reservation information, even when there are multiple duplicate reservation information, for which at least one cancellation fee has been paid. This prevents the user from sending a message requesting a cancellation fee for reservation information for which a cancellation fee has already been paid.

[0065] In step S303, the listing step may include a step of listing the duplicate reservation information in an identifiable manner when a cancellation fee has been paid by the customer for at least one of the duplicate reservation information obtained from multiple reservation management services operated by different external businesses. Specifically, if, among the multiple pieces of reservation information acquired from the reservation table 1013 in step S302, there are multiple overlapping pieces of reservation information having the same reservation number, and the acquisition unit 1042 of the server 10 finds that the payment data of the billing information corresponding to the reservation ID of one piece of reservation information contains information indicating that a cancellation fee has been paid by the customer, the acquisition unit 1042 may draw the background of that reservation information D121 on the reservation presentation screen D11 in an identifiable manner, such as a background color, text color, font, drawing style, etc., that is different from that of the other pieces of reservation information D122. This allows the user to easily identify duplicate reservation information, even when there are multiple duplicate reservation information, for which at least one cancellation fee has been paid. This prevents the user from sending a message requesting a cancellation fee for reservation information for which a cancellation fee has already been paid.

[0066] In step S303, the listing step executes a step of listing two or more pieces of reservation information in an identifiable manner if the cancellation fee amounts calculated for at least two or more pieces of overlapping reservation information obtained from multiple reservation management services operated by different external businesses do not match. Specifically, the acquisition unit 1042 of the server 10 calculates a cancellation fee for each of the multiple pieces of reservation information having the same reservation number, based on the facility reservation data and cancellation data, from among the multiple pieces of reservation information acquired from the reservation table 1013 in step S302. The acquisition unit 1042 of the server 10 compares the calculated cancellation fees for the multiple pieces of reservation information, and if they do not match, draws the relevant reservation information D121, D122 on the reservation presentation screen D11 in an identifiable manner, such as a background color, text color, font, drawing style, etc., that is different from the other reservation information. In addition, if the cancellation fees calculated for multiple overlapping reservation information do not match, the control unit 204 of the user terminal 20 may indicate this by displaying a pop-up dialog box or the like to indicate that the cancellation fees do not match. This allows the user to easily identify any reservation information that has inconsistent cancellation fee amounts when there are multiple duplicate reservation information, and avoid sending a message requesting a cancellation fee with an incorrect amount.

[0067] <Billing processing> The billing process is a process for billing a cancellation fee for the reservation information acquired in the reservation acquisition process.

[0068] <Billing process overview> The billing process is a series of processes that selects reservation information to send a message to from the reservation information displayed in the reservation presentation process, acquires the selected reservation information, calculates the billing amount, creates a message, sends the message to the customer, and notifies the customer of the message.

[0069] <Billing processing details> The billing process is described in detail below.

[0070] In step S501, the billing unit 1044 of the server 10 executes a reservation selection step of accepting a selection operation of predetermined reservation information that does not satisfy the contents of the reservation from among the plurality of reservation information acquired in the reservation acquisition step. The reservation selection step executes a step of accepting a selection operation for the plurality of reservation information listed in the list presentation step. Specifically, the user operates the input device 206 of the user terminal 20 to press the request button D1211 displayed on the reservation presentation screen D11. The control unit 204 of the user terminal 20 sends a request to the server 10 to display a web page (linked content page) displaying details of the reservation information, including the reservation ID of the reservation information D121 corresponding to the request button D1211. This causes the billing unit 1044 of the server 10 to accept a selection operation for reservation information that has been canceled by the customer or specific reservation information that does not fulfill the reservation-related content, such as a no-show. Based on the received reservation ID, the billing unit 1044 of the server 10 searches the reservation ID item in the reservation table 1013 to acquire the reservation information. Based on the received reservation ID, the billing unit 1044 of the server 10 searches the reservation ID item in the billing table 1014 to acquire the billing information. Upon receiving the request, the billing unit 1044 of the server 10 generates a link content page and transmits it to the user terminal 20. The control unit 204 of the user terminal 20 displays the link content page on the display 2081 of the user terminal 20 and presents it.

[0071] 12 is an example of a screen of the collaboration content page. Collaboration content page D2 is displayed on display 2081 of user terminal 20. Collaboration content page D2 includes a cancellation fee D201, a billing status D202, a message button D203, an edit button D204, facility reservation information D211 based on facility reservation data, customer information D212 based on customer data, and billing information D213.

[0072] The facility reservation information D211 includes the reservation number included in the reservation information, the reservation site identified based on the reservation management service ID, the reservation date and time included in the facility reservation data, the reservation amount, the check-in date, the check-out date, and the cancellation date and time included in the cancellation data if the reservation information includes cancellation data.

[0073] In step S502, the billing unit 1044 of the server 10 executes a customer identification step of identifying customer information related to the customer who made the reservation for the predetermined reservation information selected in the reservation selection step. The customer information identified in the customer identification step includes information related to the name and contact information of the customer who made the reservation. Specifically, the customer information D212 includes the customer number included in the customer data, the name of the person making the reservation (the name of the customer who made the reservation), contact information such as a telephone number and an email address, and information included in the facility reservation data such as the number of guests. Note that the customer data may be included in the facility reservation data.

[0074] In step S502, the billing unit 1044 of the server 10 executes a calculation step of calculating a cancellation fee based on the reservation amount, reservation date and time, cancellation date and time, and cancellation policy of the predetermined reservation information selected in the reservation selection step. Specifically, the cancellation fee D201 is calculated based on the facility reservation data and cancellation data. The calculation of the cancellation fee D201 is similar to the calculation of the cancellation fee in step S303 of the reservation submission process, and therefore will not be explained further. The billing status D202 displays the text "Not yet billed" if there is no billing information associated with the selected reservation information, and "Billed" if there is billing information. If billing information exists, additional information such as the billing date and time, billing amount, etc. may also be displayed. Note that calculating the cancellation fee is optional and not mandatory in step S502. Specifically, if the user is prompted to input the cancellation fee in step S503 and billing information including the input cancellation fee is stored in the billing amount field of billing table 1014, the billing amount field stored in billing table 1014 may be displayed in cancellation fee D201.

[0075] The billing unit 1044 of the server 10 displays the billing date and time included in the acquired billing information and billing information identification information (billing ID) for identifying the billing information in the billing information D213.

[0076] The user presses the message button D203 by operating the input device 206 of the user terminal 20. The control unit 204 of the user terminal 20 sends a request to the server 10 to display a page for creating a billing message (bill creation page) including the reservation ID displayed on the collaboration content page.

[0077] The user can edit the facility reservation information D211, customer information D212, and billing information D213 displayed on the collaboration content page D2 by operating the input device 206 of the user terminal 20 and pressing the edit button D204. The control unit 204 of the user terminal 20 transmits the edited content to the server 10. The billing unit 1044 of the server 10 updates the corresponding values in the reservation table 1013 and the billing table 1014 based on the received information. This allows the user to edit the collaboration content page D2 displayed on the display 2081 of the user terminal 20. Alternatively, the user may be configured to edit the facility reservation data, customer data, cancellation data, etc. stored in the reservation table 1013 by operating the input device 206 of the user terminal 20.

[0078] In step S503, when the billing unit 1044 of the server 10 receives the request, it searches the reservation ID item in the reservation table 1013 based on the reservation ID and obtains reservation information including the reservation management service ID, reservation number, facility reservation data, customer data, and cancellation data.

[0079] In step S503, the acquisition unit 1042 of the server 10 executes a terms acquisition step of acquiring a cancellation policy that defines the cancellation conditions for the predetermined reservation information selected in the reservation selection step. Specifically, the billing unit 1044 of the server 10 obtains the cancellation policy included in the cancellation data.

[0080] When the billing unit 1044 of the server 10 receives the reservation information, it generates a billing creation page and transmits it to the user terminal 20. The control unit 204 of the user terminal 20 displays the billing creation page on the display 2081 of the user terminal 20 and presents it. 13 is an example of a billing creation screen for billing processing. A billing creation page D3 is displayed on the display 2081 of the user terminal 20. The billing creation page D3 includes input fields for billing name D301, billing destination and billing amount information including billing amount D302, telephone number D311, contact information including email address D312, language to be used for billing D321, reservation site name D331, reservation number D332, check-in date D333, check-out date D334, accommodation fee D335, memo field D341, and send button D351.

[0081] In step S504, the billing unit 1044 of the server 10 executes a creation step of creating a message invoiced for a cancellation fee for the specified reservation information based on the specified reservation information selected in the reservation selection step and the customer information identified in the customer identification step. The creation step is a step of creating a message invoiced for a cancellation fee from the customer who made a reservation for the specified reservation information, including the cancellation fee calculated in the calculation step. The billing unit 1044 of the server 10 may also execute a fee presentation step of presenting the cancellation fee calculated in the calculation step to the user. Specifically, the user can create a message charging the customer a cancellation fee for the reservation information selected in step S501 by operating the input device 206 of the user terminal 20 to enter and edit each input field included in the billing creation page D3.

[0082] The billing unit 1044 of the server 10 may generate a billing creation page with values entered in the input fields of the billing creation page D3 based on the reservation information acquired in step S502, and transmit the generated page to the user terminal 20. The control unit 204 of the user terminal 20 displays and presents the billing creation page D3 on the display 2081 of the user terminal 20 with values entered in the input fields based on the reservation information. Specifically, the billing unit 1044 of the server 10 generates a billing creation page D3 with the customer name included in the customer data entered as the billing name D301, the cancellation fee calculated based on the facility reservation data and cancellation data entered as the billing amount D302, the customer's telephone number and email address included in the customer data entered as the telephone number D311 and email address D312, respectively, the language used by the customer if included in the customer data, the language entered as the language D321, the name of the reservation site identified based on the reservation management service ID entered as the reservation site name D331, the reservation number entered as the reservation number D332, the check-in date and check-out date and time included in the facility reservation data entered as the check-in date D333 and the check-out date D334, respectively, the usage fee included in the facility reservation data entered as the accommodation fee D335, and any additional information and cancellation policy included in the facility reservation data, customer data, cancellation data, etc. entered into the memo field D341, and sends the generated page to the user terminal 20. The calculation of the billing amount D302 is the same as the calculation of the cancellation fee in step S303 of the reservation submission process, and therefore a description thereof will be omitted. This allows the user to avoid the need for tedious input work into the input fields on the bill creation page D3, and also reduces input errors.

[0083] The user presses the send button D351 by operating the input device 206 of the user terminal 20. This causes the control unit 204 of the user terminal 20 to send to the server 10 a request to send a message requesting a cancellation fee to the customer who made a reservation based on the specified reservation information, including the information entered in the input fields of the billing creation page D3.

[0084] In the present disclosure, the link content page D2 is displayed in step S502, and the cancellation fee is calculated in step S503. However, steps S502 and S503 may be skipped, and the billing creation page D3 may be displayed instead of the link content page D2, and processing may begin with step S504. The link content page D2 may also be displayed by pressing a button or the like for viewing "detailed information" provided for each of the reservation information D121 and D122.

[0085] In step S504, the creating step may include a step of automatically creating a message requesting the cancellation fee based on the cancellation fee calculated in the calculating step. In the present disclosure, a configuration has been disclosed as an example in which the billing section 1044 of the server 10 generates a billing creation page D3 on which the user can edit billing information based on reservation information, and presents it on the display 2081 of the user terminal 20 in a manner that allows the user to input and edit it, but the user may omit creating a message in step S504. That is, the billing unit 1044 of the server 10 may automatically create a message based on the reservation information, assuming that the relevant input values have been entered into the input fields of the billing creation page D3. This allows the user to easily create a message billing the customer for the cancellation fee without having to calculate the cancellation fee.

[0086] In step S505, upon receiving the request, the billing unit 1044 of the server 10 generates a message charging the customer for the cancellation fee based on the values in the input fields on the billing creation page D3, and sends the message to the customer's contact information, such as the telephone number D311 and email address D312. Specifically, the message includes a document charging the customer for the cancellation fee specified by the billing amount D302. The billing unit 1044 of the server 10 stores the message including the reservation ID, sending date and time, and destination information (telephone number D311, email address D312, etc.), and the billing amount D302 in new records for the reservation ID, billing date and time, billing data, and billing amount in the billing table 1014. This stores in the billing table 1014 that the billing process has been carried out for the customer. Furthermore, the information entered in the input fields of the billing creation page D3 may be stored in the billing data item of the billing table 1014.

[0087] In step S506, the billing unit 1044 of the server 10 executes a notification step of notifying the message created in the creation step to the customer identified based on the customer information identified in the customer identification step. Specifically, when the information processing terminal of the customer receives the message from the server 10, it displays and presents the message content to the customer. As a result, the message generated by the billing unit 1044 of the server 10, which bills the customer who made the reservation for a cancellation fee, is presented to the customer.

[0088] 14 shows an example of a billing message sent to a customer during billing processing. The billing message D4 includes a subject, sender information (user name, email address, address, etc.), recipient name, name of the recipient, and a document requesting the cancellation fee.

[0089] The customer who receives the message can pay the cancellation fee by payment method such as bank transfer, credit card, etc. When the customer pays the cancellation fee, the billing unit 1044 of the server 10 stores information such as the date and time of payment and the amount of payment in the payment data field of the corresponding record in the billing table 1014. This records that the customer has made a payment in response to the billing information. The payment information may be input by the user operating the input device 206 of the user terminal 20 instead of through the billing unit 1044 of the server 10.

[0090] In step S506, the notification step may execute a step of notifying the customer of a message again if the customer has not paid the cancellation fee after a predetermined period of time has elapsed after notifying the customer of a message in the notification step. Specifically, the billing unit 1044 of the server 10 searches the payment data field in the billing table 1014 and acquires billing information including the billing date and time when the cancellation fee has not yet been paid by the customer. The billing unit 1044 of the server 10 references the billing date and time field in the acquired billing information and identifies billing information that is more than a predetermined period before the current date and time. For example, billing information that is more than one week old may be presented. The billing unit 1044 of the server 10 may urge the customer who made the reservation to pay the cancellation fee by sending a new message to bill the customer based on the identified billing information. The message may also be sent automatically. This allows the user to re-bill customers who have not yet paid without having to go through the hassle of resending the message. The billing unit 1044 of the server 10 updates the billing table 1014 by storing the resent date and time in the billing date and time field of the record in which the message was resent. Alternatively, the billing information may be stored in a new record in the billing table 1014.

[0091] <Debt Processing> Debt processing is processing related to information (debt information) that indicates the collectability of debt calculated based on reservation information, cancellation information, and billing information.

[0092] <Outline of debt processing> Debt processing is a series of processes that acquire cancellation information, acquire billing information, calculate debt information based on the acquired cancellation information and billing information, present the debt information to the user, accept selection operations for debt transfer for the presented bond information, and transfer the debt related to the selected debt information.

[0093] <Details of debt processing> The details of the debt settlement are explained below.

[0094] Specifically, a user such as an employee of a restaurant, hotel, or other business operates the input device 206 of the user terminal 20, executes a browser application, and opens the debt processing page D5 by inputting the URL of a web page (debt processing page) for executing debt processing. The control unit 204 of the user terminal 20 transmits a request including the user ID 2011 for opening the debt processing page to the server 10.

[0095] Upon receiving the request, the server 10 generates a debt processing page and transmits it to the user terminal 20. The control unit 204 of the user terminal 20 displays the debt processing page on the display 2081 of the user terminal 20 and presents it. 15 is an example of a screen of a debt processing page D5 in debt processing. The debt processing page D5 is displayed on the display 2081 of the user terminal 20. The debt processing page D5 is substantially the same as the reservation presentation page D1, and a description of the common parts will be omitted. Specifically, the debt processing page D5 includes a debt processing screen D51. The debt processing screen D51 includes a transfer button D510, a list D511 of reservation management services to which the user has subscribed, the name D512 of the currently displayed reservation management service, and reservation information D521, D522 obtained from the reservation management service named D512 through the reservation acquisition process. The reservation information D521, D522 includes transfer buttons D5211, D5221, and debt buttons D5212, D5222 that display detailed information about the debt, respectively. The process of acquiring and presenting the reservation information D521 and D522 by the credit unit 1045 of the server 10 is similar to the process of acquiring and presenting the reservation information D121 and D122 on the reservation presentation page D1 by the presentation unit 1043 of the server 10, so a description thereof will be omitted. The debt section 1045 of the server 10 may list only reservation information associated with cancellation data on the debt processing page D5, and may not display reservation information not associated with cancellation data on the debt processing page D5. The claims section 1045 of the server 10 may list only reservation information for which claims related to cancellation fees have not been transferred on the claims processing page D5, and may not display reservation information for which claims related to cancellation fees have been transferred on the claims processing page D5.

[0096] In step S701, the credit section 1045 of the server 10 executes a condition receiving step of receiving desired conditions regarding the credit value from the business operator. Specifically, when executing a claim processing, the user may accept desired conditions regarding the claim value input by the user. Note that in the present disclosure, a configuration for accepting input from a user of a business operator such as a restaurant or hotel will be described as an example. The user selects reservation information D521, D522 by operating the input device 206 of the user terminal 20. The control unit 204 of the user terminal 20 displays an input field on the display 2081 of the user terminal 20 for each of the reservation information D521, D522, in which desired conditions regarding the claim value for a cancellation fee can be accepted from the user, and presents the input field to the user. The user inputs desired conditions regarding the claim value into the input field by operating the input device 206 of the user terminal 20. Specifically, the desired conditions include the desired transfer amount for the receivable related to the cancellation fee, desired conditions regarding payment conditions such as the payment timing, and other optional conditions regarding the transfer and transaction of the receivable related to the cancellation fee. The control unit 204 of the user terminal 20 transmits the input desired conditions regarding the bond value for the cancellation fee to the server 10. The bond unit 1045 of the server 10 receives and accepts the desired conditions regarding the bond value.

[0097] In step S702, the user presses the bond buttons D5212, D5222 by operating the input device 206 of the user terminal 20. The control unit 204 of the user terminal 20 sends to the server 10 a request including a reservation ID for generating a bond details page that displays detailed information about the bond for the cancellation fee associated with the reservation information D521, D522 corresponding to the pressed bond buttons D5212, D5222.

[0098] In step S702, the credit unit 1045 of the server 10 executes a cancellation information acquisition step of acquiring cancellation information indicating that the reservation information has been canceled for the reservation information relating to multiple reservations. The cancellation information acquisition step may acquire cancellation information indicating that the reservation information has been canceled for the reservation information relating to multiple reservations managed by a reservation management service operated by an external business operator. Specifically, the credit section 1045 of the server 10 searches the reservation ID item in the reservation table 1013 based on the acquired reservation ID, and acquires the cancellation data item. The cancellation data does not need to be data that the server 10 according to the present disclosure has directly accepted as input, but may be cancellation data accepted from users, customers, etc. in multiple reservation management services operated by different external operators, such as multiple PMSs, multiple site controllers, or multiple OTAs connected to the server 10. The cancellation data acquired in the debt processing may be the same as the cancellation data acquired in step S102 of the reservation acquisition processing.

[0099] In step S703, the credit section 1045 of the server 10 executes a billing information acquisition step to acquire billing information indicating that a cancellation fee has been charged for the reservation information, based on the cancellation information acquired in the cancellation information acquisition step. Specifically, the credit section 1045 of the server 10 searches the reservation ID item in the billing table 1014 based on the acquired reservation ID and acquires the billing information. The billing information is stored in such a way that one or more pieces of billing information are associated with one piece of reservation information in response to the notification of a message charging the customer a cancellation fee in the billing process already described.

[0100] In step S703, the billing information acquisition step executes a step of acquiring billing information including at least one of the following information: whether or not the customer has responded to the request for the cancellation fee for the reservation information; whether or not the customer has received a message requesting the cancellation fee for the reservation information; and the customer's payment status for the request for the cancellation fee for the reservation information. Specifically, the billing information acquired by the credit section 1045 of the server 10 may include, in addition to the billing information included in the billing table 1014, additional information regarding the customer's response to the billing related to the billing information. Specifically, the billing information may include information indicating whether or not there was a reply to the cancellation fee billing message, whether or not the email address, telephone number, etc. to which the cancellation fee billing message is sent are valid, whether or not the customer has paid the cancellation fee bill, and whether or not the customer has paid other cancellation fee bills in the past.

[0101] In step S703, a billing information acquisition step executes a step of acquiring billing information including information on the customer's behavior history in the reservation management service related to the reservation information. Specifically, the credit section 1045 of the server 10 searches the reservation ID item in the reservation table 1013 based on the acquired reservation ID, and acquires the customer data. Based on the acquired customer data, the credit department 1045 of the server 10 queries and acquires information regarding the customer's behavioral history from multiple reservation management services operated by different external operators, such as multiple PMSs, multiple site controllers, or multiple OTAs connected to the server 10. Specifically, the behavioral history includes the following information: Login history: when and how often you log in to the Booking Management Service, and what device and browser you use. · Page Views: The pages customers visited, the content they viewed, and how long they stayed there. · Search History: Keywords and search results of searches performed by customers within the Booking Management Service. Click History: Links, buttons, ads, etc. that customers clicked. · Booking process: the steps leading up to a booking and the customer's actions at each step. · Frequency of service usage: How often do customers use the booking management service? Correspondence: correspondence with customer support and inquiries. In-app behavior: If you use a mobile app, your in-app behavior patterns. Social media integration: Behavioral data from your social media accounts. Feedback and review history: The content and date of any feedback or reviews you have provided.

[0102] In step S704, the credit section 1045 of the server 10 executes a credit value calculation step of calculating a credit value related to the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step. The claim value calculation step executes a step of calculating a discount rate for the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step, and a step of calculating the claim value by discounting the cancellation fee based on the discount rate. Specifically, the debt section 1045 of the server 10 uses the acquired cancellation data and billing information as input data and applies it to a learning model such as a machine learning model, a deep learning model, or other artificial intelligence model, or a model (including a function) that can calculate the debt value or discount rate, thereby obtaining the debt value or discount rate as output data. As an example, a method for creating a learning model capable of outputting a discount rate for cancellation fees will be described. The credit section 1045 of the server 10 uses cancellation data and billing information for reservation information canceled within a certain period of time in the past as input data to create learning data such that the probability of a cancellation fee being paid, the amount of the cancellation fee paid, etc., become output data (teaching data). Based on the learning data, the credit section 1045 of the server 10 creates datasets such as training data, test data, and verification data for training the deep neural network of the learning model. Based on the created dataset, the credit section 1045 of the server 10 uses deep learning to train the learning parameters of the deep neural network included in the learning model. For example, the learning model may take cancellation data and billing information as input data and output the probability that a cancellation fee will be paid. In this case, the discount rate is calculated by subtracting the output probability that the cancellation fee will be paid from 1. For example, if the output probability that the cancellation fee will be paid is 0.8 (80%), the discount rate is 0.2 (20%). The learning model may take cancellation data and billing information as input data and calculate at least some of the information related to the value of the claim, such as the present value of the claim, the discount rate, and the expected value of recovering the cancellation fee. The learning model may output the discount rate or directly output the claim value. The claim unit 1045 of the server 10 can calculate the claim value by discounting the cancellation fee by the discount rate. Note that the receivable value or discount rate does not necessarily have to be calculated using a learning model, but may be calculated according to predetermined conditions based on information contained in the cancellation data and billing information. For example, based on a table storing discount rates and receivable values associated with each condition, the discount rate or receivable value may be calculated as follows: if there are no replies to the cancellation fee request message four or more times, XX yen, if the cancellation fee request message is not delivered to the customer, etc.

[0103] In step S704, the debt value calculation step includes a step of calculating the debt value relating to the cancellation fee based on the credit information of the customer to whom the cancellation fee for the reservation information is to be charged. Specifically, the credit department 1045 of the server 10 obtains credit information from the customer's credit information contained in the acquired customer data, or by querying an external credit information providing service, etc. for the customer's credit information based on the acquired customer data. The credit section 1045 of the server 10 calculates the discount rate and credit value for the cancellation fee based on the credit information. The calculation method for the discount rate and credit value is the same as the calculation method for the discount rate and credit value based on the cancellation data and billing information already explained. Specifically, the calculation can be performed by including information on the credit information in addition to the cancellation data and billing information as input parameters for the learning model, function, condition, etc. The customer's credit information includes the following information. Specifically, the credit information may include an index indicating the customer's credit status, such as a credit rating or credit score. The credit information may also include information indicating the customer's credit status, such as payment history and the amount of credit currently being used. Payment history: Past payment history for credit cards, loans, etc. Late or missed regular payments will hurt your credit score. Credit in Use: The amount of credit currently being used relative to the available credit limit. A high credit limit indicates a high credit risk and a good credit score. Length of credit history: How long you have held a credit account. Maintaining a good payment history over a long period of time is a sign of good credit. · Delinquent or bankruptcy records: Negative records such as late payments, foreclosures, or bankruptcies will hurt your credit score. · Public Records: Matters of public record, such as unpaid taxes or court judgments.

[0104] In step S704, a claim value calculation step executes a step of calculating a claim value relating to the cancellation fee based on the desired conditions accepted in the condition acceptance step. Specifically, the credit section 1045 of the server 10 may calculate the credit value based on the desired conditions received from the user in step S701. For example, the credit section 1045 of the server 10 may reduce or increase the credit value calculated based on the cancellation data, billing information, and credit information already described, taking into account the desired conditions.

[0105] The credit section 1045 of the server 10 stores the calculated credit value and discount rate for the cancellation fee in the credit data item of the target record in the reservation table 1013. In addition, the debt section 1045 of the server 10 may calculate the collection status, debt discount rate, debt value, debtor information, legal action history, payment terms, information on debt collection agents, accounting procedures, etc. based on cancellation data, billing information, credit information, etc., and store this in the debt data item of the target record in the reservation table 1013. In this way, the item of debt data in the reservation table 1013 stores information indicating the collectability of debt (debt information).

[0106] In the present disclosure, in steps S702 to S704, as an example, in response to the user pressing the bond button D5212 or D5222, the bond information for the reservation information corresponding to the bond button is calculated, but this is not limited to this. For example, the bond unit 1045 of the server 10 periodically (every hour, daily, weekly, monthly, or other fixed period, or irregularly) searches the reservation table 1013 to obtain a record of reservation information in which information indicating cancellation is stored in the cancellation data field, obtains the cancellation data and billing information corresponding to the reservation information, and calculates the bond information using steps similar to steps S702 to S704. The bond unit 1045 of the server 10 may store the calculated bond information in the bond data field of the target record in the reservation table 1013. In this case, the bond data field in the reservation table 1013 is periodically updated to the latest status.

[0107] In step S705, the debt section 1045 of the server 10 executes a collection presentation step of presenting collection information indicating the collectibility of the debt related to the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step. The collection presentation step executes a step of presenting collection information including collection status information indicating the collection status of the debt related to the cancellation fee. The collection presentation step executes a step of presenting a debt assignment button that can be operated to give instructions for assigning the debt in association with the collection information. Specifically, the debt section 1045 of the server 10 searches the reservation ID item in the reservation table 1013 based on the acquired reservation ID and acquires debt data (collection information). The debt section 1045 of the server 10 transmits the acquired debt data to the user terminal 20. The control unit 204 of the user terminal 20 generates a debt details page D7 based on the received debt data, and displays and presents it on the display 2081 of the user terminal 20. 16 is an example of a claim details screen during claim detail processing. A claim details page D7 is displayed on the display 2081 of the user terminal 20. The claim details page D7 includes a collection status D701 based on the claim data, a claim discount rate D711, a claim value D712, debtor information D721, and an assignment button D731. In addition, the claim details page D7 may include content indicating any information included in the claim data.

[0108] In step S705, the collection information is presented to a business that can charge a cancellation fee for the reservation information. The collection information may be presented to the business without being presented to the customer who will be charged the cancellation fee for the reservation information. The collection presentation step may include a step of presenting the claim value calculated in the claim value calculation step to the business operator. Specifically, the bond details page D7 may be configured to be viewable only to users of restaurants, hotels, and other businesses, and not to customers who will be billed for cancellation fees. The credit section 1045 of the server 10 may also be configured to send a message including the credit information calculated in accordance with the calculation of the credit information in step S704 to the user of the restaurant, hotel, or other business. In this case, the credit section 1045 of the server 10 may also be configured not to send the message including the calculated credit information to the customer, etc., to whom the cancellation fee will be charged. In this manner, in the present disclosure, collection information is presented to users who are business operators such as restaurants and hotels, but cannot be viewed by customers who will be billed for cancellation fees.

[0109] In step S705, a recovery presentation step is executed to present recovery information indicating the possibility of recovering the debt related to the cancellation fee for which a cancellation fee has been claimed but not paid, among the plurality of cancellation information. Specifically, the reservation information D521 and D522 listed on the debt processing page D5 may be configured to list reservation information associated with cancellation data that includes information indicating that the cancellation fee has not been paid, among the reservation information associated with cancellation data. In this case, a user of a restaurant, hotel, or other business can execute steps S702 to S705 of the claim processing for the reservation information associated with the cancellation data including information indicating that the cancellation fee has not been paid by operating the input device 206 of the user terminal 20 and pressing the claim buttons D5212 and D5222. In this case, the claim information calculated for the reservation information associated with the cancellation data including information indicating that the cancellation fee has not been paid is presented to the user of the restaurant, hotel, or other business. This allows users of restaurants, hotels, and other businesses to receive collection information for reservations for which cancellation fees have not been paid. Based on the collection information provided, they can consider how to handle the debt related to the cancellation fees.

[0110] In step S706, the debt section 1045 of the server 10 executes a debt selection step of accepting a selection of debt information from the user. The user presses the transfer button D731 on the bond details page D7 by operating the input device 206 of the user terminal 20. Alternatively, the user may press the transfer buttons D5211, D5221 on the bond processing page D5 by operating the input device 206 of the user terminal 20. The control unit 204 of the user terminal 20 sends to the server 10 a request to transfer the bond, including the reservation ID of the reservation information associated with the pressed transfer button. This allows the user to transfer the claim for the cancellation fee associated with the presented reservation information.

[0111] In step S707, the credit section 1045 of the server 10 executes a process to transfer the credit related to the credit information selected in step S706. Specifically, the credit section 1045 of the server 10 searches the reservation ID item in the reservation table 1013 based on the reservation ID included in the received request, and acquires the reservation information. The credit section 1045 of the server 10 searches the reservation ID item in the billing table 1014 based on the reservation ID included in the received request, and acquires the billing information. The claim unit 1045 of the server 10 stores information indicating that a claim has been assigned in the claim data field of the target record in the reservation table 1013. For example, the information indicating that a claim has been assigned includes the creditor (e.g., the operator of a restaurant, hotel, etc.), the assignee of the claim, the conditions of the assignment, the date of assignment, etc. The assignee of the claim may be selected by the user by operating the input device 206 of the user terminal 20, or a business operator or the like may be designated as a predetermined assignee in advance. Alternatively, the business operator or the like as a predetermined assignee may be specified according to any conditions such as reservation information, billing information, etc. In response to an update of the debt data item of the target record in the reservation table 1013, the debt section 1045 of the server 10 notifies all parties related to the debt of a message including information indicating that the debt data has been transferred. The message may include the debt data, the debtor, the debt transferee, the terms of the transfer, and the date of the transfer. Specifically, the message may include information about businesses such as restaurants and hotels, businesses that provide the information processing services disclosed herein, different external businesses such as multiple PMSs, multiple site controllers, or multiple OTAs connected to the server 10, and customers to whom cancellation fees for reservation information will be charged.

[0112] In addition, although the present disclosure provides an example of a configuration in which the assignment of a claim is stored in an electronic storage means, it is also possible to have an assignment agreement concluded with the assignee of the claim based on a paper document, an electronic document created using word processing software, etc.

[0113] Furthermore, the claims section 1045 of the server 10 identifies accounting procedures etc. according to the claims data (conditions of transfer etc.) and stores information indicating the accounting procedures etc. in the claim data item of the target record in the reservation table 1013. In this way, the claim relating to the cancellation fee is transferred from the restaurant, hotel or other business operator to the transferee.

[0114] <Basic computer hardware configuration> 17 is a block diagram showing the basic hardware configuration of a computer 90. The computer 90 includes at least a processor 901, a main memory device 902, an auxiliary memory device 903, and a communication IF 991 (interface), which are electrically connected to one another by a communication bus 921.

[0115] The processor 901 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

[0116] The main memory device 902 is used to temporarily store programs, data to be processed by the programs, etc. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0117] The auxiliary storage device 903 is a storage device for saving data and programs, such as a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, or a semiconductor memory.

[0118] The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using wired or wireless communication standards. The network is composed of the Internet, a LAN, various mobile communication systems constructed by wireless base stations, etc. For example, the network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks (e.g., Wi-Fi (registered trademark)) that can connect to the Internet via a predetermined access point. In the case of a wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), and Bluetooth (registered trademark). In the case of a wired connection, the network also includes a direct connection using a USB (Universal Serial Bus) cable, etc.

[0119] It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration across multiple computers 90 and interconnecting them via a network. In this way, the computer 90 is a concept that includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

[0120] <Basic functional configuration of computer 90> The following describes the functional configuration of a computer realized by the basic hardware configuration (FIG. 17) of the computer 90. The computer includes at least the functional units of a control unit, a storage unit, and a communication unit.

[0121] The functional units of the computer 90 can also be realized by distributing all or part of the functional units among multiple computers 90 interconnected via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

[0122] The control unit is realized by the processor 901 reading out various programs stored in the auxiliary storage device 903, expanding them in the main storage device 902, and executing processing in accordance with the programs. The control unit can realize functional units that perform various types of information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0123] The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Furthermore, the processor 901 can allocate a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with the programs. Furthermore, the control unit can cause the processor 901 to execute processes for adding, updating, and deleting data stored in the storage unit in accordance with the various programs.

[0124] A database refers to a relational database, which manages data sets called masters and tables in a tabular format structurally defined by rows and columns, by relating them to each other. In a database, a table is called a table, a master, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables and masters can be set and associated. Typically, each table and each master has a column set as a primary key to uniquely identify a record, but setting a primary key to a column is not essential. The control unit can cause the processor 901 to add, delete, or update records in specific tables and masters stored in the storage unit according to various programs. Furthermore, by storing data, various programs, and various databases in the storage unit, it can be considered that the information processing device and information processing system according to the present disclosure have been manufactured.

[0125] Note that the databases and masters in this disclosure may include any data structure in which information is structurally defined (such as a list, dictionary, associative array, or object). The data structure also includes data that can be considered as a data structure by combining data with functions, classes, methods, etc. written in any programming language.

[0126] The communication unit is realized by the communication IF 991. The communication unit realizes a function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input the information to the control unit. The control unit can cause the processor 901 to execute information processing on the received information in accordance with various programs. In addition, the communication unit can transmit information output from the control unit to other computers 90.

[0127] <Additional Notes> The matters described in the above embodiments will be supplemented below.

[0128] (Appendix 1) A program to be executed by a computer having a processor and a memory unit, the program executing a cancellation information acquisition step (S702) in which the processor acquires cancellation information indicating that reservation information relating to multiple reservations has been canceled, a billing information acquisition step (S703) in which, based on the cancellation information acquired in the cancellation information acquisition step, it acquires billing information indicating that a cancellation fee has been charged for the reservation information, and a collection presentation step (S705) in which it presents collection information regarding the collection of receivables relating to the cancellation fees based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step. This allows restaurants, hotels, and other businesses to be presented with information indicating the possibility of collecting receivables related to cancellation fees based on cancellation information and billing information. Based on the presented collection information, restaurants, hotels, and other businesses can consider how to handle receivables related to the cancellation fees.

[0129] (Appendix 2) The program according to appendix 1, wherein the collection presentation step (S705) is a step of presenting a claim transfer button operable to give instructions for transferring the claim in association with the collection information. This allows restaurant, hotel, and other business operators to seamlessly complete the bond transfer procedure by operating the bond transfer button displayed in association with the presented collection information, making it easy for restaurant, hotel, and other business operators to complete the bond transfer procedure.

[0130] (Appendix 3) The program according to Appendix 2, wherein the processor executes a claim assignment step (S707) of assigning a claim in response to a user's operation of a claim assignment button. This allows business operators such as restaurants and hotels to seamlessly carry out the debt transfer procedure by performing operations such as pressing a debt transfer button in accordance with the presented collection information.

[0131] (Appendix 4) A program described in any of Appendices 1 to 3, in which a processor executes a claim value calculation step (S704) in which the processor calculates the claim value for the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step. This allows businesses such as restaurants and hotels to calculate information about the value of their claims based on billing information and cancellation information.

[0132] (Appendix 5) The program described in Appendix 4, wherein the receivable value calculation step (S704) includes a step of calculating the receivable value for the cancellation fee based on the credit information of the customer to whom the cancellation fee for the reservation information is to be charged. This allows for more accurate calculation of the customer's credit information, taking into account the credit information of the customer to whom the cancellation fee is to be charged.

[0133] (Appendix 6) The program described in Appendix 4, wherein the claim value calculation step (S704) is a step of calculating a discount rate for the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step, and a step of calculating the claim value by discounting the cancellation fee by the discount rate. This allows businesses such as restaurants and hotels to calculate information about the value of their claims based on billing information and cancellation information.

[0134] (Appendix 7) A program described in any of Appendices 1 to 6, wherein the cancellation information acquisition step (S702) is a step of acquiring cancellation information indicating that reservation information regarding multiple reservations managed in a reservation management service operated by an external business operator has been canceled, and the billing information acquisition step (S703) is a step of acquiring billing information including information regarding the customer's behavioral history in the reservation management service regarding the reservation information. This makes it possible to manage, at a glance, cancellation information related to reservation information that is stored in a distributed manner across multiple reservation management services operated by external businesses, such as PMSs, site controllers, and OTAs, each with different roles and hierarchies. Taking into account the customer's behavioral history in the reservation management service, it is possible to present restaurant, hotel, and other business operators with collection information that indicates the possibility of collecting receivables more accurately.

[0135] (Appendix 8) The program according to any one of appendices 1 to 7, wherein the recovery presentation step (S705) is a step of presenting recovery information to a business that can charge a cancellation fee for the reservation information. This allows restaurants, hotels, and other businesses to receive collection information indicating the possibility of collecting receivables related to cancellation fees.

[0136] (Appendix 9) The program according to appendix 8, wherein the recovery presentation step (S705) is a step of presenting the recovery information to the business operator without presenting the recovery information to the customer who will be billed for the cancellation fee for the reservation information. This allows restaurants, hotels, and other businesses to receive collection information indicating the collectibility of debts without presenting the collection information to customers.

[0137] (Appendix 10) A program described in any one of Appendices 4 to 6, wherein the recovery presentation step (S705) is a step of presenting recovery information to a business operator that is able to charge a cancellation fee for the reservation information, and the recovery presentation step (S705) is a step of presenting the receivable value calculated in the receivable value calculation step to the business operator. This allows restaurants, hotels, and other businesses to receive a presentation of the receivable value along with recovery information indicating the possibility of recovering the receivable related to cancellation fees.

[0138] (Appendix 11) A program as described in Appendix 10, in which a processor executes a conditions reception step (S701) in which the processor receives desired conditions regarding the value of the claim from the business operator, and a claim value calculation step (S704) in which the processor calculates the value of the claim regarding the cancellation fee based on the desired conditions received in the conditions reception step. This allows the value of a claim to be calculated in accordance with the desired conditions for the claim value received from businesses such as restaurants and hotels.

[0139] (Appendix 12) The billing information acquisition step (S703) is a step of acquiring billing information including at least one of the following information: whether or not the customer has responded to the request for the cancellation fee for the reservation information; whether or not the customer has received a message requesting the cancellation fee for the reservation information; and whether or not the customer has paid the request for the cancellation fee for the reservation information. A program described in any of Appendices 1 to 11. This makes it possible to present to restaurants, hotels, and other businesses information indicating the possibility of collecting claims related to cancellation fees based on billing information, including whether or not the customer has responded to the cancellation fee bill, whether or not the billing message has been received by the customer, and the customer's payment status.

[0140] (Appendix 13) The program according to any one of appendices 1 to 11, wherein the collection presentation step (S705) is a step of presenting collection information including collection status information indicating the collection status of the receivable related to the cancellation fee. This allows restaurants, hotels, and other businesses to consider how to handle the receivables related to the cancellation fees in accordance with the presented collection information, including the collection status.

[0141] (Appendix 14) A program described in any one of Appendices 1 to 11, wherein the recovery presentation step (S705) is a step of presenting recovery information regarding the recovery of claims related to cancellation fees, among multiple cancellation information, for which cancellation fees have been claimed but not paid. This allows businesses such as restaurants and hotels to receive information on recovery of reservations for which cancellation fees have not yet been paid. Depending on the collection information provided, we can consider how to handle the receivables for the cancellation fee.

[0142] (Appendix 15) A computer-implemented method comprising a processor and a memory, wherein the processor performs all of the steps performed in the invention according to any one of appendixes 1 to 11. This allows restaurants, hotels, and other businesses to be presented with information indicating the possibility of collecting receivables related to cancellation fees based on cancellation information and billing information. Based on the presented collection information, restaurants, hotels, and other businesses can consider how to handle receivables related to the cancellation fees.

[0143] (Appendix 16) An information processing device comprising a control unit and a memory unit, wherein the control unit executes all of the steps executed in the invention according to any one of Supplementary Note 1 to Supplementary Note 11. This allows restaurants, hotels, and other businesses to be presented with information indicating the possibility of collecting receivables related to cancellation fees based on cancellation information and billing information. Based on the presented collection information, restaurants, hotels, and other businesses can consider how to handle receivables related to the cancellation fees.

[0144] (Appendix 17) A system comprising means for performing all steps performed in any of the inventions according to any one of appendixes 1 to 11. This allows restaurants, hotels, and other businesses to be presented with information indicating the possibility of collecting receivables related to cancellation fees based on cancellation information and billing information. Based on the presented collection information, restaurants, hotels, and other businesses can consider how to handle receivables related to the cancellation fees. [Explanation of symbols]

[0145] 1 System, 501 PMS, 5011 Memory unit, 5014 Control unit, 5016 Input device, 5018 Output device, 511 OTA, 5111 Memory unit, 5114 Control unit, 5116 Input device, 5118 Output device, 521 Site controller, 5211 Memory unit, 5214 Control unit, 5216 Input device, 5218 Output device, 10 Server, 101 Memory unit, 104 Control unit, 106 Input device, 108 Output device, 20 User terminal, 201 Memory unit, 204 Control unit, 206 Input device, 208 Output device

Claims

1. A program to be executed by a computer having a processor and a storage unit, the processor: a cancellation information acquisition step of acquiring cancellation information indicating that the reservation information relating to a plurality of reservations has been canceled; a billing information acquisition step of acquiring billing information indicating that a cancellation fee has been charged for the reservation information based on the cancellation information acquired in the cancellation information acquisition step; a collection presentation step of presenting collection information regarding the collection of the debt related to the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step; A program that executes.

2. The collection presentation step is a step of presenting a debt assignment button operable to give an instruction to assign the debt in association with the collection information. The program according to claim 1.

3. The processor: executing a claim assignment step of assigning the claim in response to an operation of the claim assignment button by a user; The program according to claim 2.

4. the processor: a claim value calculation step of calculating a claim value related to the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step; To execute The program according to claim 1.

5. the claim value calculation step includes a step of calculating the claim value related to the cancellation fee based on credit information of a customer to whom the cancellation fee for the reservation information is to be charged; The program according to claim 4.

6. The claim value calculation step includes: a step of calculating a discount rate for the cancellation fee based on the cancellation information acquired in the cancellation information acquisition step and the billing information acquired in the billing information acquisition step; a step of calculating the value of the claim by discounting the cancellation fee by the discount rate; The program according to claim 4.

7. the cancellation information acquisition step is a step of acquiring cancellation information indicating that the reservation information has been canceled, regarding reservation information relating to the plurality of reservations managed in a reservation management service operated by an external business; the billing information acquisition step is a step of acquiring the billing information including information about a customer's behavior history in the reservation management service related to the reservation information; The program according to claim 1.

8. The collection information presentation step is a step of presenting the collection information to a business that can claim the cancellation fee for the reservation information. The program according to claim 1.

9. the collection presentation step is a step of presenting the collection information to the business operator without presenting the collection information to a customer to whom the cancellation fee for the reservation information is to be charged; The program according to claim 8.

10. the collection presentation step is a step of presenting the collection information to a business that can claim the cancellation fee for the reservation information, The collection presentation step is a step of presenting the claim value calculated in the claim value calculation step to the business operator. The program according to claim 4.

11. the processor: a condition receiving step of receiving desired conditions regarding the claim value from the business operator; Run The claim value calculation step is a step of calculating the claim value related to the cancellation fee based on the desired conditions accepted in the condition acceptance step. The program according to claim 10.

12. The billing information acquisition step includes: Whether or not the customer has responded to the cancellation fee request for the reservation information; Whether or not the customer has received a cancellation fee request message for the reservation information; The customer's payment status for the cancellation fee for the reservation information; and acquiring the billing information including at least one of the following information.

12. The program according to claim 1.

13. The collection presentation step is a step of presenting the collection information including collection status information indicating the collection status of the debt related to the cancellation fee.

12. The program according to claim 1.

14. The collection presentation step is a step of presenting the collection information regarding the collection of the debt related to the cancellation fee for which a cancellation fee has been claimed but not paid, among the plurality of cancellation information.

12. The program according to claim 1.

15. A method implemented on a computer having a processor and a memory, wherein the processor performs all of the steps performed in the invention according to any one of claims 1 to 11.

16. 12. An information processing device comprising a control unit and a storage unit, wherein the control unit executes all of the steps executed in the invention according to any one of claims 1 to 11.

17. A system comprising means for executing all steps performed in any one of the inventions according to claims 1 to 11.

Images